[lt02xxx][CWM Advanced Edition] PhilZ Touch
- Thread starter Phil3759
- Start date
I have no time to compile it now and look at it closer, but sure it is not okay:
Your fstab on git looks like this:
Code:
/devices/platform/sdhci-pxav3.0/mmc_host/mmc1 auto auto defaults voldmanaged=extSdCard:autoIt means, minivold will mount to /storage/extSdCard
If not, then you probably messed something or you are symlinking it in rc files!
When I compile it like it is on my git, it displays as "storage/extSdCard" in recovery and appears to work correctly for everything I have tested.
If I change it to "sdcard1" as you suggested, it displays as "/storage/sdcard1" as expected. I just want to make sure that the "/storage" part isn't going to mess anything up.
I apologize for my lack of knowledge, I just don't want you to have to continue making changes due to my inability.
No, it is the way it is supposed to work
the root part is done in init.rc
The remaining in recovery sources
init.rc
Code:
mkdir /mnt 0775 root system
mkdir /storage 0050 root sdcard_r
mount tmpfs tmpfs /storage mode=0050,uid=0,gid=1028
# See storage config details at http://source.android.com/tech/storage/
mkdir /mnt/shell 0700 shell shell
# Directory for putting things only root should see.
mkdir /mnt/secure 0700 root root
# Create private mountpoint so we can MS_MOVE from staging
mount tmpfs tmpfs /mnt/secure mode=0700,uid=0,gid=0
# Directory for staging bindmounts
mkdir /mnt/secure/staging 0700 root root
# Fuse public mount points.
mkdir /mnt/fuse 0700 root system
mount tmpfs tmpfs /mnt/fuse mode=0775,gid=1000
@Phil3759 I'll make sure my device tree compiles it works and mounts correctly.
Updated to 6.16.3
I merged your device tree sources, looks better now in fact
I did not use your init.recovery.rc file
Please check if all is fine how I did it
I merged your device tree sources, looks better now in fact
I did not use your init.recovery.rc file
Please check if all is fine how I did it
Updated to 6.16.3
I merged your device tree sources, looks better now in fact
I did not use your init.recovery.rc file
Please check if all is fine how I did it
The virtual buttons at the bottom do not work on the 6.16.3 build. They appear much larger than before and touching a button does nothing. All other touch functions seem to be working correctly.
I have attached a picture from 6.16.2 (when the buttons were smaller and working correctly) and a picture of the 6.16.3 non-working buttons.
Thanks.
Attachments
Last edited:
Thank you very much for porting this recovery on our device. I have the same problem here with 6.16.3 and 6.16.2 was working as expected.
I would like to know if it is possible to have a portrait version too or the option to switch from landscape to portrait mode. I am used to portrait mode on my s3 and I prefer it.
Thank you again for your hard work.
"Envoyé depuis mon SM-T210 avec Tapatalk"
I would like to know if it is possible to have a portrait version too or the option to switch from landscape to portrait mode. I am used to portrait mode on my s3 and I prefer it.
Thank you again for your hard work.
"Envoyé depuis mon SM-T210 avec Tapatalk"
Really wired. Changing the height/width entries has no impact on touch code
Since I am in sync with kernel, could be something changed
Do slide left and right gesture actions work?
My bad, I see my mistake
Sorry, will fix it asap
There is a bug in my res sources
Sorry, will fix it asap
There is a bug in my res sources
thanks
It is not the touch as I said, since it has nothing to do with those settings
It's only that my 1024 vk png file is actually 1080 width, so it gets out of range during calculation of button areas
https://github.com/PhilZ-cwm6/philz_touch_cwm6/commit/0dc813826c2b06690fb9c0e6d0df5fc8a7f02363
I am uploading a fixed version
Does the "mount usb storage" work? Because after I tap on it and then hit back, cmw freezes as I said before and no replied but it's ok, I know that you are busy but could you have some time to reply to a noob non-dev person?
Sent from my SM-T210R using Tapatalk
Sent from my SM-T210R using Tapatalk
Update 6.16.4
Hope we're done
Could you make a flashable zip file?
Sent from my SM-T210R using Tapatalk
Update 6.16.4
Hope we're done
Virtual keys work now. :good:
Thank you so much.
P.S. Only the odin version was on goo.im
---------- Post added at 12:45 PM ---------- Previous post was at 12:44 PM ----------
No, and likely never will. Samsung has bad entries in the device vold.fstab for usb devices.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
41Main thread + features + install instructions + dev support
http://xdaforums.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
credits to @gr8nole and @ketut.kumajaya7
Thank you very much for making this for us.
I flashed it and noticed that the external sd does not mount and we can not use it. I repacked your version with my fstab and external sd works correctly.5
I keep up thanks to people like you, porting their devices trees
:good:
I use scripts to build recoveries and repack them
Compiling, repacking and creating zip + tar files classified in upload path for one or 130 devices is just one command line,
Adding a tar release is just:
Code:TAR_MD5_FLASH="yes"
However, it is still a huge impressive job mainly to port device trees, kernel sources, bugs...
the scripts must be maintained too, all the time
Hopefully I will soon be able to only focus on recovery sources and selected devices while devs can build full version at their will
New posts
-
[ROM][OFFICIAL][redfin] LineageOS 20
- Latest: OttoUsualConsumer
-
