Related
I am by no means an expert, i just dove into this project 4 days ago, and since then, I've had to reformat my SD card about 8 times before I figured out how to get it stable. But now I have it running pretty stable, there are some issues still, but it at least runs linux pretty well. I'm mainly posting this because this would have saved me a lot of digging 4 days ago, and I figured I would help out any n00bs that just got a lapdock and just started playing with webtop.
*Disclaimer* I am not an expert, if you have a problem with any of these steps, please do not post them here, but in their respective threads. I take no credit for developing any of this, im just posting a list of steps from multiple sources. Also, if you break something, its not my fault*
The Guide
By the end of this guide, you will have a more functional linux as your webtop, with the XFCE4 interface. This uses webtop2sd, so if you break anything, you should be able to start over.
You will need a rooted Atrix, a lapdock (or other external device for using webtop on), and a microSD card, I suggest 2GB or bigger. I have a 32GB PNY class 10 card, for example.
1. Lets format/partition the SD card. Sogarth explains here how to do that. I highly suggest NOT doing this on your phone,and use a PC instead.
http://forum.xda-developers.com/showpost.php?p=15109152&postcount=5
2. Here, he explains how to install it after you partition your SD card. The app you need is in the bottom of the first post.
http://forum.xda-developers.com/showpost.php?p=15109140&postcount=4
3. Now plug it in to your lapdock, and it should boot up into the new webtop. You should see 2 icons in the middle, the awn-dock config tool, and the webtop config tool. We just need to focus on the latter one. Open that up, click on Administration on the left,and click on Install by lxterminal. Try clicking on the terminal icon on the dock, if it comes up, you are gold. If it acts funky, like your screen goes black but doesn't open the terminal, open up the webtop config tool again, and the button to install it should be lit up again. You know its installed if you click install,close out the config tool, and reopen it to see Install grayed out.
4. If all goes well, you should be at a terminal. The first thing we want to do, is fix a really annoying and OS breaking bug, regarding the tzdata package. It seems to be corrupted, so we want to make sure it doesn't get in the way of installing other packages. This issue was the bane of my existence for 3 days.
following these steps, we will fix it
http://forum.xda-developers.com/showpost.php?p=18465066&postcount=3
type this into the terminal to bring up the said file so you can edit it
Code:
sudo leafpad /var/lib/dpkg/info/tzdata.postinst
then put exit 0 on the 3rd empty line
I would reboot your phone after doing this, just for good measure
5. When you get back into the webtop, lets run the Webtop Scripts, the files and instructions are here for that. This will fix many broken dependencies. Arvati did a great job with these fixes!
http://forum.xda-developers.com/showthread.php?t=1192488
just put that file in your downloads folder, then run the commands from that first code box, and I just said yes everytime it asked you what you wanted to do. I would reboot your phone again after this.
6. Now lets start installing stuff! Lets start with synaptic, which works a lot better if you install via command line instead of the webtop config tool.
So run this from the terminal:
Code:
sudo aptitude install synaptic
7. Open up synaptic by typing 'sudo synaptic' into the terminal. Lets install XFCE4 now, just search for that there,and install the XFCE4 package, it should install all of the other required packages to run the new interface.
8. Once it is installed,we need to disable the webtop interface,and enable xfce4. I referenced this thread to do that:
http://forum.xda-developers.com/showthread.php?t=1054213
Type this into the terminal to edit the right file
Code:
sudo leafpad /osh/usr/local/bin/start-oshwt-2.sh
put a # in front of
sfalv -i "awm-autostart"
sfalv -i "webtop-wallpaper"
so it looks like
#sfalv -i "awm-autostart"
#sfalv -i "webtop-wallpaper"
then add these 2 lines
sfalv -i "xfce4-session"
sfalv -i "xfce4-panel"
save it then reboot your phone. Hopefully you should be in XFCE4 now!
OPTIONAL:
*To fix an issue with mounting USB storage devices:
I had the same problem, got it to work by adding this to /etc/PolicyKit/PolicyKit.conf
Code:
<config version="0.1">
<match action="org.freedesktop.hal.storage.mount-removable">
<match user="myaccountnamehere">
<return result="yes"/>
</match>
</match>
</config>
Click to expand...
Click to collapse
http://www.linuxquestions.org/quest...b-storages-debian-squeeze-723251/#post3537149
* To Fix mounting Windows network shares
Chimpdaddy has posted a way to get Samba file shares to work, this requires having a custom kernel though:
http://forum.xda-developers.com/showpost.php?p=22018703&postcount=67
Chimpdaddy said:
Firstly you need to have a kernal, like Faux's, that supports CIFS.
Then install Samba4, via synaptic package manager if you like.
Probably an idea to reboot.
Then create a folder (using terminal) where you want yr share, 'sudo mkdir /media/SHARE' for eg..
then run this;
sudo mount -t cifs -o username=guest //YOURSHAREIP/SHARE /media/SHARE
if you get no errors yr golden
If you want it to mount on startup edit /etc/fstab to include
//YOURSHAREIP/SHARE /media/SHARE cifs username=guest,_netdev 0 0
check this with 'mount -a'
That should do you.
Click to expand...
Click to collapse
OR
You could use an app like ESFileExplorer on your phone to drag and drop files, this is what I have been using,and it works pretty well for both direct windows shares and FTP. The Mobile View is great for having a window open for secondary tasks like this.
EXPERIMENTAL:
This can be buggy,so use at your own risk!
To install chromium browser, follow these steps. This is said to have better performance than the built in firefox, but for me, it crashed a lot, I went back to firefox
http://forum.xda-developers.com/showthread.php?t=1374567
ISSUES STILL PENDING:
*currently no major issues*
LIST OF SUGGESTED APPS:
OpenOffice.org
Qalculator
XChat IRC
This looks good. I just got my lapdock on Thursday and I have been putting togther all of the Docs to get it the way I want, but this is pretty much the results I wanted. I will try your instructions and get back with you.
Thanks.
Which ROM are you running on?
stock ROM.....
Thanks for the guide.
There is one link that appears to be broken though,
On step 5, the thread goes nowhere. That's where I'm stuck right now
my bad,fixed
i actually managed to do all this on my own, but just recently came into a unexpected problem. i'm kind of a linux noob, and it seems like the file manager button on xfce4-panel doesn't lead to the stock file manager i was using before (doesn't lead to anything), does anyone have any suggestions for a good file manager to replace it with?
Thanks for the fix, I've completed all steps and it was working for about an hour. Until I installed chromium.
I have a weird problem where the lapdock doesn't detect webtop and says no hdmi input detected. Not sure if you know anything about that, but just wanted to let you guys know (might be a defect on my lapdock). I'm trying to figure out a fix for that now.
I would suggest starting over if that happened,sounds like something broke
as for an XFCE4 file manager, it should install Thunar by default
teeth_03 said:
I would suggest starting over if that happened,sounds like something broke
as for an XFCE4 file manager, it should install Thunar by default
Click to expand...
Click to collapse
sudo apt-get thunar fixed the problem for me, thanks though
followed your steps and it works great ,i've been messing with this for over a week trying to get this to work ,that ztdata bug fix did the job.. THANK YOU.....
toe451 said:
followed your steps and it works great ,i've been messing with this for over a week trying to get this to work ,that ztdata bug fix did the job.. THANK YOU.....
Click to expand...
Click to collapse
dont thank me, thank the guy who figured out how to fix it
webtop2sd app crashes on first run...any ideas?
Here's the answer
http://forum.xda-developers.com/showpost.php?p=19993891&postcount=671
bigworm50 said:
webtop2sd app crashes on first run...any ideas?
Click to expand...
Click to collapse
To the point of installing XFCE4, and synaptic just sits on preparing packages forever... I let it sit for 30+ minutes last night and going on almost 60 minutes currently...is something wrong or does it take that long?
you might want to cancel that, reboot your phone and try again, it should not take that long
can you do one on how to install Chrome instead of Firefox for a noob like myself. Thank you.
there is already a link to the chromium browser thread in the OT
I would caution that its kind of experimental, I installed it and it kept on crashing for me, so when I re-did my webtop after that,I just decided to use firefox
For step 1, can we partition this as ext4 as faux kernels support it?
added info on fixing an issue with mounting USB drives, and a note about chrome
Hi, I just installed the ubuntu webtop mod detailed in this thread:
http://forum.xda-developers.com/showthread.php?t=1119555
I now have Synaptic and LXterminal installed.
When I go into Synaptic, it tells me I have 25 broken packages. I click Edit then click Fix Broken Packages and hit Apply.
I get the error "E:/var/cache/apt/archives/coreutils_6.10-6ubuntu1_armel.deb: trying to overwrite '/usr/sbin/chroot', which is also in package rootfs.
Does anyone know how to fix this problem?
Thanks in advance.
I have the exact same issue. Has anyone ever posted a fix for it?
I had the same problem
This is an old thread but just in case someone comes looking again....
I had the same problem and "fixed" it by running the following for each package it failed on:
sudo dpkg -i --force-overwrite --root=/osh /var/cache/apt/archives/cpio_2.9-15ubuntu1_armel.deb
(this is for cpio but it works for other packages too). It looks as if the package manager is expecting the environment to hang off / when in fact it hangs off /osh.
Im building cyanogenmod 11 for the htc dna, this is my first attemt into building my own rom however I seemed unable to get a bootable zip until now.
I captured a screen.log to scan for any errors later (NO clue what im looking for in here)
So I searched the log for "waiting for unfinished jobs" because this is always what seems to happen to me and this time i was ready to find the errors. Well lucky for me every job finished so what I am wondering is does this mean that my build compiled correctly even though i have warnings like crazy in the 140000+ lines of the screen.log
as for the second question. Is there any easier eay to scan a screen.log for where the build errors are or do i just have to run through all the line blind because im not exactly sure what to look for yet (one day i plane to have more of an understanding this is just early in my rom building career.)
EDIT~!~!~!~!~!~!~
Okay new problem. When i originally synced my repo to cm11 i was on python 2.7.4 and thats how i tried the first build on this ubuntu and it failed. I updated to python 2.7.6 because every time i grabbed 2.7.5 i kept getting unsuspected End Of File errors. So I installed 2.7.6 with (sudo make install) instead of (sudo make altinstall) like some guides read (This is because when i used altinstall brunch always gets to waiting for unfinished jobs.)
What i was getting at was now that im on python 2.7.6 when i try to initialize another repo to another folder I receive this error.
fatal: Cannot get https://gerrit.googlesource.com/git-repo/clone.bundle
fatal: error unknown url type: https
Click to expand...
Click to collapse
However I can repo sync my cm11 repo still just can not initialize a new repo to another directory
Any help is appreciated
hipsh0t said:
Im building cyanogenmod 11 for the htc dna, this is my first attemt into building my own rom however I seemed unable to get a bootable zip until now.
I captured a screen.log to scan for any errors later (NO clue what im looking for in here)
So I searched the log for "waiting for unfinished jobs" because this is always what seems to happen to me and this time i was ready to find the errors. Well lucky for me every job finished so what I am wondering is does this mean that my build compiled correctly even though i have warnings like crazy in the 140000+ lines of the screen.log
as for the second question. Is there any easier eay to scan a screen.log for where the build errors are or do i just have to run through all the line blind because im not exactly sure what to look for yet (one day i plane to have more of an understanding this is just early in my rom building career.)
Click to expand...
Click to collapse
There are a ton of warnings, one error (failing to build modules, which you can ignore). The last thing printed is the path to the zip. If it printed that, the build completed successfully.
To find the errors, try searching from the end for Error (capital E).
@crpalmer
Yea I just found the zip its booting as we speak.
Thanks
So excited this is finally working I been messing with Ubuntu for like 2 weeks
hipsh0t said:
Okay new problem. When i originally synced my repo to cm11 i was on python 2.7.4 and thats how i tried the first build on this ubuntu and it failed. I updated to python 2.7.6 because every time i grabbed 2.7.5 i kept getting unsuspected End Of File errors. So I installed 2.7.6 with (sudo make install) instead of (sudo make altinstall) like some guides read (This is because when i used altinstall brunch always gets to waiting for unfinished jobs.)
What i was getting at was now that im on python 2.7.6 when i try to initialize another repo to another folder I receive this error.
However I can repo sync my cm11 repo still just can not initialize a new repo to another directory
Click to expand...
Click to collapse
I'm not expert so crpalmer or someone may be able to tell you more directly. But here is a few things:
Did you install SSL for python?
Code:
$ sudo apt-get install libssl1.0.0=1.0.1-4ubuntu5.3
$ sudo apt-get install libssl-dev
Try reinstalling Python. I installed it the simple way and its working fine for my builds.
Code:
$ sudo apt-get install python
What repo were you trying to initialize?
tes4p00ner said:
I'm not expert so crpalmer or someone may be able to tell you more directly. But here is a few things:
Did you install SSL for python?
Code:
$ sudo apt-get install libssl1.0.0=1.0.1-4ubuntu5.3
$ sudo apt-get install libssl-dev
Try reinstalling Python. I installed it the simple way and its working fine for my builds.
Code:
$ sudo apt-get install python
What repo were you trying to initialize?
Click to expand...
Click to collapse
It was every repo and I tried the normal way I must have started from a fresh Ubuntu install once every few days figuring out where I went wrong. I'm going to check on the ssl for Python. So far this is the furthest I've made it. One built cm11 rom and I'm only learning more every day I research
EDIT------------
[email protected]:~$ sudo apt-get install libssl1.0.0=1.0.1-4ubuntu5.3
[sudo] password for jk:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Version '1.0.1-4ubuntu5.3' for 'libssl1.0.0' was not found
Click to expand...
Click to collapse
Im trying to make sure my precise repos are in place for apt-get however im still getting this message.
I've been using CM12.1 for couple of months, love it. Found some bugs and waited a few nightlies (few weeks per "nightly") and after that tried to make a bug report.... not accepted, because CM12.1 is not developed anymore. CM13 is not available for Z2, so I tried to build CM13 myself, following the guide found on cyanogenmod site. Sorry, as a new member, can't link that URL here... It fails... I have gone past that point to extract the proprietary "blobs" from my phone (running the mentioned CM12.1) and tried again the breakfast sirius command. I'm unable to paste results here, because being a new member... look the result from pastebin com with /mwBfxHEL behind the URL...
The reason seems obvious, missing that msm8974-common-vendor.mk file. Can't find it on my computer using "locate". Can't find it using google. Don't know how to fix this or get past this... Any help appreciated!
Nobody has build CM13 for Z2???
The issue you are describing likely results from the blob extraction for msm8974-common not operating correcty: Please execute (or re-execute) the extraction scrip in this folder of the device tree as well (should be device/sony/msm8974-common). Could you paste the output after running that script, please?
Diewi said:
The issue you are describing likely results from the blob extraction for msm8974-common not operating correcty: Please execute (or re-execute) the extraction scrip in this folder of the device tree as well (should be device/sony/msm8974-common). Could you paste the output after running that script, please?
Click to expand...
Click to collapse
OK, that advice helped. Tried 'breakfast sirius' again, it went longer, complained about something missing in shinano-common folder. Used your approach again and got past that one too. After that, 'breakfast sirius' succeeded. I tried 'brunch sirius' and it failed. Tried it again, it got longer before failing again... did "while [ $? -ne 0 ]; do !! done" to try building until it succeeds. After quite a while, I stopped it, ran brunch sirius command and copied the output to pastebin.
Take a look at pastebin.com/Qz4hq1aZ
Something about libta.so?
Flexy75 said:
OK, that advice helped. Tried 'breakfast sirius' again, it went longer, complained about something missing in shinano-common folder. Used your approach again and got past that one too. After that, 'breakfast sirius' succeeded. I tried 'brunch sirius' and it failed. Tried it again, it got longer before failing again... did "while [ $? -ne 0 ]; do !! done" to try building until it succeeds. After quite a while, I stopped it, ran brunch sirius command and copied the output to pastebin.
Take a look at pastebin.com/Qz4hq1aZ
Something about libta.so?
Click to expand...
Click to collapse
Should I extract the blobs from a Z2 with OEM firmware? I vaguely remember that TA refers to something to do with DRMs that you lose when you unlock the phone to be able to install other firmwares...
Sorry for the delay.
This is an issue with the vendor files. I think that th extrction scripts are somewhat outdated, or didn't the extraction script didn't find some files. There should be a repo on github which should provide you with the needed files. Another possibility would be to extract and mount the system image of a stock and let the script process these files (there is a cmdline switch for pointing the script to it: please have a look into this script for the according switch).
Hope this helps.
Diewi said:
Sorry for the delay.
This is an issue with the vendor files. I think that th extrction scripts are somewhat outdated, or didn't the extraction script didn't find some files. There should be a repo on github which should provide you with the needed files. Another possibility would be to extract and mount the system image of a stock and let the script process these files (there is a cmdline switch for pointing the script to it: please have a look into this script for the according switch).
Hope this helps.
Click to expand...
Click to collapse
OK, found the repo. Got all the files, got the build to succeed! Thank you very much! Just few more questions... There is not just one zip file in the directory... which one to install? How do I install the zip file the build created? Perhaps via booting to recovery and installing it from there? And how does it behave? Like a upgrade, or a clean install?
Hi everyone
I've been working on getting twrp to boot on our borneo device for a week or so, borrowed I the device tree made by mistersmee for the g9 power since the two devices are almost completely the same
https://github.com/TeamWin/android_device_motorola_cebu
heres where I'm at:
https://github.com/touchpro/twrp_device_motorola_borneo
The only thing I cant seem to get working is the touchscreen. I realize others have tried before me already and had the same non working touchscreen, I believe the majority of us have an Ilitek touchscreen while others have focaltech or nova. I got the driver framework up and recognizing it exists from dmesg output but cant seem to get any actual touch input to register. You can look at my changes to android 11 twrp in the github above by selecting branch twrp-android-11 and using a diff program. I use meld in ubuntu.
if you want to build for yourself and help out: (i'd use ubuntu 20.04, i tried 20.10 first but one of the packages is too new and doesnt like the toolchain)
follow the instructions here to set up your build environment
mkdir twrp (you can name this whatever you want)
cd twrp
repo init --depth=1 -u git://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni.git -b twrp-10.0
repo sync
add the device tree above to twrp/device/motorola/borneo
also add this to device in twrp/device/qcom/twrp-common
make your changes inside device/motorola/borneo then
. build/envsetup.sh
export LC_ALL=C
lunch omni_borneo-eng
mka -jx clobber && mka -jx recoveryimage (-jx is number of cores you have, i have quad core i7 with hyperthreading so i use -j8. personal preference really)
your completed build will be in twrp/out/target/product/borneo as recovery.img
reboot to fastboot (adb reboot bootloader) and type
fastboot boot recovery.img
see if your changes worked! look forward to seeing what you guys can do
mine for later
Have not had the time to toss together a build environment for this, since I'd have set up the entire OS and beyond for that task, since my only Linux is Garuda in a much too small VM that is nowhere near right for that., been only hacking my way through it with Android Image Kitchen in Windows and some other utilities to get touch support in my 3.5.2.10-0 cebu source image.
It works perfectly if booted into TWRP just takes about 30-seconds before touch enables itself fully, but not when flashed (fastboot or applied internally via DD, or using a modified TWRP zip via Magisk that has had my ramdisk swapped into it).
When flashed, touch simply will not function, so something is obviously not being carried over properly so when being loaded from the recovery partition it seems, despite it being the exact same ramdisk (I extracted the recovery img, pulled out my ramdisk, popped it back into a whole new image, booted it and it had touch, so I know it's supposed to have the data there but likely needs a full from the ground up build of TWRP to behave on flashed installs.
@whoshotjr2006, had any more luck with your building of it? I can test or anything you may need in your own efforts, but just have no time for the actual building of it to tinker.
Oh, and thought you should know this works if you were wanting to go RW for System, but you'll have to use Linux due to falling prey to Error 73 https://forum.xda-developers.com/t/script-android-10-universal-mount-system-r-w-read-write.4247311/. I put mine back because it didn't seem to behave quite right there, but could be useful in your own tinkering.
OK, got it where it is fully flashable and bootable with touch for mine. Used Android Image Kitchen, unpacked TWRP image that boots with touch working, copied out the kernel and ramdisk from split_img folder, extracted stock recovery, replaced those 2 items with properly renamed versions and then repacked it with --original argument, and then it boots and flashes properly. Just a quick hack on it, but functional for those that need it.
This should be easy to combine in your /vendor/lib/modules from your own, as well as /vendor/firmware as long as you're rooted to pull it, into your TWRP ramdisk before putting it into the stock recovery this way. So you can get fully functioning touch for any display type in use.
whoshotjr2006 said:
Hi everyone
I've been working on getting twrp to boot on our borneo device for a week or so, borrowed I the device tree made by mistersmee for the g9 power since the two devices are almost completely the same
https://github.com/TeamWin/android_device_motorola_cebu
heres where I'm at:
https://github.com/touchpro/twrp_device_motorola_borneo
The only thing I cant seem to get working is the touchscreen. I realize others have tried before me already and had the same non working touchscreen, I believe the majority of us have an Ilitek touchscreen while others have focaltech or nova. I got the driver framework up and recognizing it exists from dmesg output but cant seem to get any actual touch input to register. You can look at my changes to android 11 twrp in the github above by selecting branch twrp-android-11 and using a diff program. I use meld in ubuntu.
if you want to build for yourself and help out: (i'd use ubuntu 20.04, i tried 20.10 first but one of the packages is too new and doesnt like the toolchain)
follow the instructions here to set up your build environment
mkdir twrp (you can name this whatever you want)
cd twrp
repo init --depth=1 -u git://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni.git -b twrp-10.0
repo sync
add the device tree above to twrp/device/motorola/borneo
also add this to device in twrp/device/qcom/twrp-common
make your changes inside device/motorola/borneo then
. build/envsetup.sh
export LC_ALL=C
lunch omni_borneo-eng
mka -jx clobber && mka -jx recoveryimage (-jx is number of cores you have, i have quad core i7 with hyperthreading so i use -j8. personal preference really)
your completed build will be in twrp/out/target/product/borneo as recovery.img
reboot to fastboot (adb reboot bootloader) and type
fastboot boot recovery.img
see if your changes worked! look forward to seeing what you guys can do
Click to expand...
Click to collapse
finally having time to try to build an environment. Making a generic VM and will post it when done and easy to use, but running into some issues in my getting it to a point to test its success even. The steps you provided, missed a needed command "sudo ln -s /usr/bin/python3 /usr/bin/python" if using the 20.04 Ubuntu. But then how do you "add the device tree" as you put it? I'm normally a repacker to get things working, versus building things. I'm sure downloading the zip of the code and loading it into those folders is bound to break something as it always does when it comes to using links and ramdisks.
Perhaps you can provide more clear instructions of what you mean by that and I could finally gladly be able to contribute to this as more than a hackish throw-together process, since the description you provided "add the device tree" yields no meaningful results for any process for that to be pieced together from other builders.
git clone -b main https://github.com/touchpro/twrp_device_motorola_borneo.git
or you can just download the zip from my github, the only time it breaks symlinks so far that i know of is when you download a kernel in a zip file instead of git cloning it
take the twrp_device_motorola_borneo files and put them in /device/motorola/borneo and you should be good to go
whoshotjr2006 said:
repo init --depth=1 -u git://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni.git -b twrp-10.0
Click to expand...
Click to collapse
That won't work, as it doesn't seem to have a twrp-10.0 as it looks to be depreciated, https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni/tree/twrp-10.0-deprecated. How'd you get yours, or did you mean 9.0?
repo init --depth=1 -u git://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni.git -b twrp-10.0-deprecated
Twrp has always been built in an omnirom build environment but with a11 they switched to being built in an aosp environment. Twrp-10.0-deprecated they recently renamed to add the deprecated tag on but thats the one for android 10 that I initially used
Got my build environment set up and can upload the image in a bit if anyone wants it. @whoshotjr2006
using your steps it builds, but even having modified the firmware and modules to include the changes I put into mine to have it have touch support, it still will not. But the hacked android image kitchen one works just fine, which makes absolutely no sense when there are no errors, only warnings reported, but even those all look to be minor type casting of variables that I've noticed.
remind me again where you found that twrp that youve used android image kitchen on? was it from moto g9 power or another device? if you can let me know ill look through device trees and see what they have that we dont
seems like maybe its not insmod'ing the .ko file for your touchscreen, or it is and your touchscreen needs a firmware check/update at load. you'll have to remind me again which touchscreen you have (sorry its been a minute i've been busy) and we can look through other's device trees at the firmware loading portion
whoshotjr2006 said:
remind me again where you found that twrp that youve used android image kitchen on? was it from moto g9 power or another device? if you can let me know ill look through device trees and see what they have that we dont
seems like maybe its not insmod'ing the .ko file for your touchscreen, or it is and your touchscreen needs a firmware check/update at load. you'll have to remind me again which touchscreen you have (sorry its been a minute i've been busy) and we can look through other's device trees at the firmware loading portion
Click to expand...
Click to collapse
Source I used in AIK was cebu's 3.5.2.10-0 from https://twrp.me/motorola/motorolamotog9power.html. used AIK to unpack it.
To get touch using my quick hack, I just dropped in my matching .bin's from /vendor/firmware plus my ilitek_fw.bin to go with their novatech*.bin's and NT36xxx_MP_Setting_Criteria_601E.csv in place of their NT36xxx_MP_Setting_Criteria_6026.csv (deleted theirs).
Then also popped in my /vendor/lib/modules (minus audio ones).
At that point in tinkering it boots with touch. But fails to keep touch on booting into recovery.
Then I stumbled upon some obscure guidance about something in the kernel in recovery not initializing the touch on some devices and potentially being able to hex edit it after manually extracting the kernel using a hex editor. And then unpacked my booting version again, saw the kernel already separated out and pulled that and my ramdisk from split_image folder. cleaned up. unpacked the stock recovery. replaced with appropriately named kernel and ramdisk files and used the repack --original. Flashed it and it booted with perfect touch, just takes about 30-seconds on start before it's responsive. I have mine encrypted still so must input a passcode and just tap on the log button a few times till I know it's working then input my code and off it goes working normally.
Should not have anything too crazy different. I think the only thing I did was delete the etc file from the cebu, replacing it with an etc folder with a recovery.fstab and twrp.fstab I had scavenged from @svoc 's 3.4.0.0 (https://forum.xda-developers.com/t/working-twrp-but-very-unofficial-but-very-useful.4313665/ of which touch did not work for me, but it booted perfectly enough to extract my firmware and lib modules initially to put into my 3.5.2.10-0). Since every time I'd use Android Image kitchen to extract the cebu image it complained about things in /etc, and that was the only difference I could find between 3.5.2.10-0 and the 3.4.0.0. That is the only potential thing I did that could be of unknown consequence.
whoshotjr2006 said:
(sorry its been a minute i've been busy)
Click to expand...
Click to collapse
And never be sorry, you're helping out here, we understand, just like if you're waiting on a response back, that you're as understanding too
Compiled, touch working when booting it. Only change I made was to add my files as I outlined before, but into the firmware and lib folders respectively, but also edited the load_ts_firmware.sh to ensure nova and chiptone are no longer commented out. Flashed and has touch fully working as well. So it should be an easy build if I can get it working.
Edit: And touch does not take 30+ seconds per the 3.4.0.0 @svoc version I believe because it's not re-flashing the display code. So that could be why some perm lose touch, and I just got VERY lucky with mine to not.
Yes you are right all I did was put the touch screen driver in the twrp and send it to you that is why it takes less then 30 secs to do no need to recomile it each time just add your files in it and rezip it