Main thread + features + install instructions + dev support
http://forum.xda-developers.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
To take a screen shot, just long press outside a menu (2 sec and slightly change pressure after the delay)
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:
HTC One M8 (m8)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/m8
Click to expand...
Click to collapse
Big thanks for the debugging work done by @HolyAngel and @v1rk
XDA:DevDB Information
[m8][CWM Advanced Edition] PhilZ Touch, a Tool/Utility for the HTC One (M8)
Contributors
Phil3759
Version Information
Status: Stable
Created 2014-04-04
Last Updated 2014-04-04
Going official on goo.im (post 1)
Big thanks for the debugging work done by @HolyAngel and @v1rk
Phil3759 said:
Download Link
******** Untested First Release ********
Click to expand...
Click to collapse
pro4ever said:
Click to expand...
Click to collapse
Flash and report
flashed but not quite working at the moment, it just goes to the bootloader cannot get into recovery
New repack:
- based on stock 1.54.401.5
- load texfat modules (will be enabled later once stable)
- properly use dtb msm kernel image
Hope it boots at least so that we can start fixing up things
Uploaded again in Post 2
Phil3759 said:
New repack:
- based on stock 1.54.401.5
- load texfat modules (will be enabled later once stable)
- properly use dtb msm kernel image
Hope it boots at least so that we can start fixing up things
Uploaded again in Post 2
Click to expand...
Click to collapse
yep working now :good: although the ui is tiny (less than one inch on our 5 inch screens) but as you mentioned it's only the start
beanbean50 said:
yep working now :good: although the ui is tiny (less than one inch on our 5 inch screens) but as you mentioned it's only the start
Click to expand...
Click to collapse
Post a photo please
I will add proper exfat support on next realease
Phil3759 said:
Post a photo please
I will add proper exfat support on next realease
Click to expand...
Click to collapse
not quite sure how to take a photo, if I slide to the left it toggles the screen brightness, if I toggle to the right the screen goes blank and restarts the phone
edit
actually it's the other way round (slide right brightness, slide left blank and reboot)
beanbean50 said:
not quite sure how to take a photo, if I slide to the left it toggles the screen brightness, if I toggle to the right the screen goes blank and restarts the phone
Click to expand...
Click to collapse
Ah,
I forgot to edit op
Long press of 2 sec takes pic
But, since screen is tiner you say, a camera shot is better
Phil3759 said:
Ah,
I forgot to edit op
Long press of 2 sec takes pic
But, since screen is tiner you say, a camera shot is better
Click to expand...
Click to collapse
ok I ended up taking a real photo with my 'old' htc one..! (the ui actually looks bigger in the photo haha)
btw if recovery is untouched for 30 seconds it reboots itself not sure if thats normal
Phil3759 said:
Download Link
http://d-h.st/re1
******** Untested First Release ********
Click to expand...
Click to collapse
I love you! :laugh:
beanbean50 said:
ok I ended up taking a real photo with my 'old' htc one..! (the ui actually looks bigger in the photo haha)
btw if recovery is untouched for 30 seconds it reboots itself not sure if thats normal
Click to expand...
Click to collapse
Try to disable screen saver: set screen off to disabled and remove it from slide left gesture actions
I will increase font size too
Phil3759 said:
Try to disable screen saver: set screen off to disabled and remove it from slide left gesture actions
I will increase font size too
Click to expand...
Click to collapse
Did so and still restarts after a minute or two :/
Btw, THANK YOU FOR BUILDING THIS! I've been wanting to throw my phone and claw my eyes out over Twrp the last few days, corrupted my cache and system partitions among other things, fun time to fix it.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
idk if this will help you or not, restart happens regardless of touching it. tried doing a backup and later starting aromafm and it restarts. Log is attached ^^
Update fix2:
http://d-h.st/74F
- bigger font
- enable exfat on external storage (sorry, will need an extra derp on next update)
- fix mount point for external storage
- disable some QCOM display parts
- more stock parts, include selinux permissions
Let me know how it goes. Seems to be a long debugging step by step until we get a dev with a device release a proper device tree or repack from my base
Phil3759 said:
Update fix2:
http://d-h.st/74F
- bigger font
- enable exfat on external storage (sorry, will need an extra derp on next update)
- fix mount point for external storage
- disable some QCOM display parts
- more stock parts, include selinux permissions
Let me know how it goes. Seems to be a long debugging step by step until we get a dev with a device release a proper device tree or repack from my base
Click to expand...
Click to collapse
Downloaded and installed!
Menu Looks *perfect* now!
Still getting the same random reboots after about 2 minutes in recovery, already tried disabling 'Dim display' and "screen off" to no avail.
Is this working yet?
http://i36.photobucket.com/albums/e30/chancetgo/Mobile Uploads/thenugdestrroyerWS_zpsoshkw4hm.png
thenugdestrroyer said:
Is this working yet?
http://i36.photobucket.com/albums/e30/chancetgo/Mobile Uploads/thenugdestrroyerWS_zpsoshkw4hm.png
Click to expand...
Click to collapse
For me it's not yet, Idk about anyone else. I get about 2 minutes to do whatever I wanna do in recovery before it restarts the phone.. was successfully able to flash a couple small quick things tho.. just not enough time to flash a Rom or do a backup yet.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
HolyAngel said:
For me it's not yet, Idk about anyone else. I get about 2 minutes to do whatever I wanna do in recovery before it restarts the phone.. was successfully able to flash a couple small quick things tho.. just not enough time to flash a Rom or do a backup yet.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I need a log
When it reboots by its self, let it go to the rom
Grab all files in /cache/recovery and post them in a zip here.
That way i can see what is happening
Related
Disclaimer:
This ROM is currently in development stage.
Most things work, but there are few things that don't work and the device is slow.
Make sure you have a nandroid backup of your existing ROM before you flash this.
I know most of you guys are coming from CM7, so don't compare with it, as this is still an experimental build
Here is the CM9 (un-official) for Tattoo,
For chanages please refer to Gerrit
Download links
2012-07-10
http://www.mediafire.com/?tbvqxgtyyp484yn
Previous versions
2012-06-30
http://www.mediafire.com/?iibqddpd92sx288
2012-06-23
http://www.mediafire.com/?1vjdeanp24dvz3d
Click to expand...
Click to collapse
Gapps link
get latest gapps from http://goo-inside.me/gapps
Installation instructions
Wipe cache and data
Flash from recovery (Clockworkmod recovery only)
First boot takes about 5 to 8 mins
Framework, few apps and Dalvik-cache are moved to cache partition.
Credits
to following guys, without whom this ROM was not possible
Arco68 - for his invaluable work on Tattoo and Wildfire - his vendor config, kernel and lot of tweaks for ArmV6 are used for compiling from source and for his continuous support
ErwinP - for his collection of tweaks and the guys involved in them, which are used for CM9 compiling - check his github
Furious anger (helped in compiling CM9 from source)
CyanogenMod team
Zackconsole (helped in fixing touchscreen and audio issue),
Arif-ali
jaybob413 and his thread
TeamICS
mikegapinski
unforgiven512
and many others
here is my git for device config and notes for compiling
https://github.com/rallapag
What's working
Touchscreen
GPS
Wifi
Mobile and data
USB Mount
Sensors
Audio and
Rooted
What's not working
Camera
Bluetooth - working partially
some apps are force closing at the moment (not every time)
Gallery Not working
Live Wallpapers from CM9 are not working due to GPU requirement - so are removed,
Live Wallpapers from from market are working
And all bugs reported by users
Temporary fixes
See second post
Click to expand...
Click to collapse
Tricks to deal with some issues:
FM radio: Use SpiritiFM app from market
Turn bluetooth on before first start of SpiritFM
Settings -> Audio -> Method -> msm7x30
Settings -> Debug -> FM Chip -> TI(Motorola)
Settings -> Debug -> select use fm_hcitool
restart the app, and remember to turn media volume down.
Gallery: Use Quickpic app or
Just pictures app(thanks KingCreole)
Video player: Use MXplayer and MXplyaer ARMv6 codes from market
Preferences -> Decoder -> select S/W Decoder
Launcher alternative:
Launcher pro is very good replacement for memory hog Trebuchet launcher
Nova launcher is another one to try.
GPS location:
Use Fasterfix app to change the server to your region and location gets locked faster.
latest Gmail apk
This patch is only for Wildfireport - is removed
patch for minor graphic improvement - cm9-click-20120305-patch.zip
please flash the patch from recovery
Screenshots
Microphone does not work yet.
or?
pipko said:
Microphone does not work yet.
or?
Click to expand...
Click to collapse
Did you try the ROM posted in this thread??
donwloaded, istalled, but it desnt starts.
when booting, shows "tattoo" then a animated image and stays there forever!
marcolameirinhas said:
donwloaded, istalled, but it desnt starts.
when booting, shows "tattoo" then a animated image and stays there forever!
Click to expand...
Click to collapse
first boot takes about 5 to 8 mins.
rallapag said:
first boot takes about 5 to 8 mins.
Click to expand...
Click to collapse
ok, will wait!
there is nothing i should do before installing the rom?
its just the "usual" way?
i'm not a pro in this stuff
marcolameirinhas said:
ok, will wait!
there is nothing i should do before installing the rom?
its just the "usual" way?
i'm not a pro in this stuff
Click to expand...
Click to collapse
wipe cache and data..than flash rom..wait the first time about 10minutes..then you can use the rom.
installed. Its not fast, but is not that slooooooooow.
it crashed sometimes, not always booted, but it was nice to test it!
waiting for new and improved versions
marcolameirinhas said:
installed. Its not fast, but is not that slooooooooow.
it crashed sometimes, not always booted, but it was nice to test it!
waiting for new and improved versions
Click to expand...
Click to collapse
More work shall be done and will make those apps more stable as they should soon as current i and rallapag are working on them now just RC0
marcolameirinhas said:
installed. Its not fast, but is not that slooooooooow.
it crashed sometimes, not always booted, but it was nice to test it!
waiting for new and improved versions
Click to expand...
Click to collapse
If you use launcher pro it is very responsive
Dev :
Pushing this might help :
(system)
App http://www.mediafire.com/download.php?qculj816xcbz23c
Framework http://www.mediafire.com/download.php?k41wpb1cd5e62ht
Push this might help?
Libandroid_runtime.so http://www.mediafire.com/download.php?tgf42qk2nfegp09
Try out
Zackconsole said:
Pushing this might help :
(system)
App http://www.mediafire.com/download.php?qculj816xcbz23c
Framework http://www.mediafire.com/download.php?k41wpb1cd5e62ht
Push this might help?
Libandroid_runtime.so http://www.mediafire.com/download.php?tgf42qk2nfegp09
Try out
Click to expand...
Click to collapse
nerver done that before! its safe to do it? and how?
Flashed it, will test everything. Too bad the mic is not working, hope for a fix...
kemoba said:
Flashed it, will test everything. Too bad the mic is not working, hope for a fix...
Click to expand...
Click to collapse
The mic is working just fine
Testing right now, I will take a video later
Few problems I had;
- Wifi didn't connect (GB does connect)
- Every time I rebooted I had to give in my sim password +-17 times before I got to the home screen
And eventually it didn't booted up anymore (stuck on bootanimation)
Nice to see there is still new development for this oldie tho
My tattoo was the last place I thought to see ICS running on,,
Keep up the good work!!
Hitmax117 said:
Few problems I had;
- Wifi didn't connect (GB does connect)
- Every time I rebooted I had to give in my sim password +-17 times before I got to the home screen
And eventually it didn't booted up anymore (stuck on bootanimation)
Nice to see there is still new development for this oldie tho
My tattoo was the last place I thought to see ICS running on,,
Keep up the good work!!
Click to expand...
Click to collapse
There is a problem with your Tattoo. I have just made a video and wi-fi connected. I opened few sites.
I have removed the SIM password on boot, try. After all, I will stay with ICS
marcolameirinhas said:
nerver done that before! its safe to do it? and how?
Click to expand...
Click to collapse
FOR DEV ONLY
Push to system by adb n chmod 644
Sent from my LT18i using xda premium
I won't write long and fancy descriptions... I am planning to keep both kernel and the OP as clean as possible.
This kernel is for Xperia-T only and supports only Sony ICS ROMs for now.
FEATURES:
Autoroot
Some optimizations by cherrypicking from others & upstream
Some change-this-and-that kind of optimizations on governors
Some additional I/O Schedulers (sio, v/r)
Undervolting support
Overclocking support (192-1890MHz) with some modifications on thermal throttling to prevent overclocked values to be used during boot.
Custom CWM-based recovery with touch gestures (thanks to sk8erwitskil for the gesture support)
STweaks support (included in the kernel or from Google Play). it is an opensource app which generates dynamic UIs based on /res/uci.sh script interface and lets your set some kernel parameters easily. It will be auto-installed.
Fast-dormancy is disabled as default. You can enable it using STweaks.
KNOWN ISSUES:
Some STweaks settings are not effective
kernel needs some time to apply settings and you may feel some lag for the first 2-3 minutes. this will be fixed soon.
TODO:
cm10 support
Xperia TX support
dual-boot
more features...
THANKS TO: Codeworkx, Kali, all CyanogenMod contributors, sk8erwitskil, krabappel2548, Ninphetamine, Chainfire,... (please remind me if I forgot anyone)Download: http://d-h.st/users/siyah/sony-xtSources: http://github.com/gokhanmoral/siyah-xt
Ramfs: http://github.com/gokhanmoral/ramfs-xt (only updated each time I make a release. for test versions you will have to extract it from the kernel image)
reserved
for FAQ
Many thanks
I will test this on my rom and link it to the all in one thread.
Works fine ROM-Assaye
Touch recovery is excellent!
No vibration on prompt to recovery, but has purple LED, I would appreciate the vibraion back please.
Will test other feature in time.
EDIT:
Unexpected error in STweaks
i've just installed this kernel.....works great!! smoother and faster.... now trying !!! thanks!!!
Reserved for a probable, long and boring FAQ post...
Just installed
Thanks GM
TX can not flah cwm.zip, the script is wrong....
but use fastboot can.
Sent from my LT29i using xda app-developers app
r35471853 said:
TX can not flah cwm.zip, the script is wrong....
but use fastboot can.
Sent from my LT29i using xda app-developers app
Click to expand...
Click to collapse
I have not tested it on TX and that is why I wrote "Xperia-T only" to the first post.
also, make sure you read TODO..
if you use it on TX, use it at your own risk.
i will give this kernel a test on pacman and latest paranoid roms if you want.
y2grae said:
i will give this kernel a test on pacman and latest paranoid roms if you want.
Click to expand...
Click to collapse
I haven't tested it on cm10 although I put some init files to the ramfs.
it will probably not boot on CM10 or anything based on that.
it is still on my todo, but will send you a message when I need it to be tested on an additional device.
gokhanmoral said:
I haven't tested it on cm10 although I put some init files to the ramfs.
it will probably not boot on CM10 or anything based on that.
it is still on my todo, but will send you a message when I need it to be tested on an additional device.
Click to expand...
Click to collapse
no worries.
i know the cm10/paranoid kernels have no boot animations, which was offputting for the first few boots.
as greg asked before, can we keep the vibration for cm prompt if possible?
oops.. tested STweaks now and it doesn't work. seems like I will upload 0.2 in 20 mins
and I will put the vibration before cwm amber light toggle.
damn.. I think I will never be able to have a first release fully working
gokhanmoral said:
oops.. tested STweaks now and it doesn't work. seems like I will upload 0.2 in 20 mins
and I will put the vibration before cwm amber light toggle.
damn.. I think I will never be able to have a first release fully working
Click to expand...
Click to collapse
thats what first releases are for...just checking backup and restore in .tar mode now
---------- Post added at 02:28 PM ---------- Previous post was at 02:22 PM ----------
Another problem..sorry. its not really a bug, just something that could be made better
The backup option does not have a confirm option, which i found painful on non touch versions becuase i sometimes hit the power button instead of volume up or down and start a backup by mistake.
I have just done the same again because as son as it finished a backup I went to pick the phone up and touched the screen on the enter butoon and another backup started....could you implement an "are you sure" option like on other screens where you have to scroll up and down through a load of no options before you hit yes...
I have uploaded v0.2
-added vibration during boot, just before cwm prompt
-fixed stweaks xml file (the problem was related with a last minute addition of sched_mc parameter)
Hi gok, if you want it moving over to Original Development let me know as your work generally couldn't get much more original
I won't be round till later but will move it then if none of the other mods see it first.
Thanks as always for sharing your work :good:
AvRS said:
Hi gok, if you want it moving over to Original Development let me know as your work generally couldn't get much more original
I won't be round till later but will move it then if none of the other mods see it first.
Thanks as always for sharing your work :good:
Click to expand...
Click to collapse
thank you for your kind comment but for now the kernel is not so original.
it has some cherrypicks and influences from some other repos although some parts are carefully corrected.
I want to make an example of "it is not who you are which makes your posts to be placed in original development but it is what you do"... and kernels can be unoriginal work as well.
I will ask for your evaluation once I feel like the work is more original
thank you again.
V0.1 Restore failed twice in .tar mode.
gregbradley said:
V0.1 Restore failed twice in .tar mode.
Click to expand...
Click to collapse
thanks for reporting it. honestly I haven't checked it yet, but I will tonight.
updating known issues for now
gokhanmoral said:
thanks for reporting it. honestly I haven't checked it yet, but I will tonight.
updating known issues for now
Click to expand...
Click to collapse
no problem. It failed on both the backups i made with this recovery and now just failed on a known good .tar backup i made with a previous recovery.
It fails at different times, once on restoring system once on a md5 ismatch (On the new backups) and on the known good backup it failed on restoting data
"Error while restoring /sdcard/ .android /.androi_secure!"
But its a good looking recovery, I will be using it when these wrinkles are ironed out.
Again, many thanks, and if the confirm option for the backup is implemented as well, I would be over the moon.
gregbradley said:
no problem. It failed on both the backups i made with this recovery and now just failed on a known good .tar backup i made with a previous recovery.
It fails at different times, once on restoring system once on a md5 ismatch (On the new backups) and on the known good backup it failed on restoting data
"Error while restoring /sdcard/ .android /.androi_secure!"
But its a good looking recovery, I will be using it when these wrinkles are ironed out.
Again, many thanks, and if the confirm option for the backup is implemented as well, I would be over the moon.
Click to expand...
Click to collapse
did you backup to internal or external card?
and do you have any app moved to .android_secure? (move2sd)
I have just run backup to internal and restored it successfully. EDIT: no .android_secure backup
I will also try to backup to external sd
Hey guys,
The Android 4.3 update for the Nexus 4, in my opinion, has majorly improved the touch screen sensitivity of the Nexus 4, therefore I believe this mod is irrelevant. For those who still want to use it, its still here.
Hey guys,
First of all, I would like to say thanks to trter10 who made the original thread for this. Unfortunately, that thread has been abandoned by the OP and forgotten about. Therefore, I have decided to make this thread. In fact, the mod that I made, in my opinion, is much better than the one in that thread.
As many of us, Nexus 4 users, have come to realize, the device's touch screen sensitivity is way below par when it comes to today's day and age. It has been pointed out that this is due to some changes in the latest touch screen driver from Synaptics, E027. An earlier driver, E015, had much better sensitivity and therefore downgrading to it improves touch screen sensitivity significantly.
There are two ways to downgrade the driver. The first way is the easiest but it doesn't work for everybody, such as people (like me) who use custom kernels like Franco Kernel. I don't know why it doesn't work, but that's the way it is.
First Method:
What You Need:
Root - If you don't have it, go to this thread: http://forum.xda-developers.com/showthread.php?t=2010312
A custom recovery - If you don't have it, go to this thread: http://forum.xda-developers.com/showthread.php?t=2010312
Busybox - If you don't have it, get it here: https://play.google.com/store/apps/details?id=stericson.busybox
init.d support - If you don't have, go to this thread: http://forum.xda-developers.com/showthread.php?t=1933849
What This Does:
Puts an init.d script in the init.d folder. This script will install the E015 driver on boot.
Places the driver in /system for the script to use.
Instructions:
Extract Method 1.zip.
Boot in to your custom recovery.
Install E015-TouchDriver-Mako.zip
Reboot.
Instructions to Revert:
Boot in to your custom recovery.
Install E015-TouchDriver-Mako-Revert.zip
Reboot.
Notes:
After boot, your touchscreen will be unresponsive for around 30 seconds.
After flashing a ROM, you will need to install this zip again.
I am not responsible for any damage this modification may cause.
Second Method:
What You Need:
Root - If you don't have it, go to this thread: http://forum.xda-developers.com/showthread.php?t=2010312
Busybox - If you don't have it, get it here: https://play.google.com/store/apps/details?id=stericson.busybox
Script Manager - SManager - If you don't have it, get it here: https://play.google.com/store/apps/details?id=os.tools.scriptmanager
Instructions:
Extract Method 2.zip.
Using any android file explorer, place SynaImage.E015.bin in /sdcard.
Using any android file explorer, place the E015TouchDriverDowngrade script in any location you want on your internal SD card (I placed it in /sdcard/Scripts).
Go into Smanager, navigate to the E015TouchDriverDowngrade script and press on it.
Select the following options: Fav, Su.
Press Run.
The touch screen will be disabled for the next 15-30 seconds.
From now on, on every reboot you need to perform the following steps in order to downgrade the touchscreen driver:
Go into Smanager, click on options -> Scripts -> E015TouchDriverDowngrade -> Run.
Enjoy!
Notes:
After a reboot, your touchscreen will be unresponsive for around 20 seconds because the kernel is reflashing the new touch screen driver (E027).
After selecting Run your touch screen won't work for 15-30 seconds if it does work, the old touch driver is not being flashed.
I am not responsible for any damage this modification may cause.
Enjoy!
Click to expand...
Click to collapse
Known Issues
Known Issues
FAQ - Frequently Asked Questions
FAQ - Frequently Asked Questions
Like a known issue you could say the ~30 sec delay on boot and on recovery (I know its already in notes)
Re: [MOD] Improve Touch Screen Sensitivity
@OP what is different about your zip than the original one in the thread below. Does yours work with 4.2.2 and the original does not? Is that the main difference? If so please state that in your OP. Thanks
http://forum.xda-developers.com/showthread.php?p=34987520
Monk4Life said:
@OP what is different about your zip than the original one in the thread below. Does yours work with 4.2.2 and the original does not? Is that the main difference? If so please state that in your OP. Thanks
http://forum.xda-developers.com/showthread.php?p=34987520
Click to expand...
Click to collapse
There is a difference, I'm not home right now, I'll update the OP later.
Thanks!! Does this work with other custom roms? such as http://forum.xda-developers.com/showthread.php?t=2009561
tomho529 said:
Thanks!! Does this work with other custom roms? such as http://forum.xda-developers.com/showthread.php?t=2009561
Click to expand...
Click to collapse
Yes, it should.
Re: [MOD] Improve Touch Screen Sensitivity
I noticed this after a few hours with my n4 I actually have a replacement device shipping out to me soon. Ive only have the phone for 2 days. I guess this will be fixed in Android update?
Sent from my Nexus 4 using xda app-developers app
Sv: [MOD] Improve Touch Screen Sensitivity
Confirmed working om latest cm nightly with Franco kernel
Sendt fra min Nexus 4 med Tapatalk2
bxsteve31 said:
I noticed this after a few hours with my n4 I actually have a replacement device shipping out to me soon. Ive only have the phone for 2 days. I guess this will be fixed in Android update?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Well, from 4.2.1 to 4.2.2 they didn't fix it, so probably not.
Works fantastically, thank you!
on aokp build 3 for anyone who's curious.
Will not look back!!
Works as advertised on PA 3.0 (24FEB) I can finally type a message in portrait without it making me feel like I have no clue how to type. I would consistently hit letters and they would not register, just did a test and tapped a whole paragraph with not one error. Thank you very much.
Re: [MOD] Improve Touch Screen Sensitivity
Thanks for this! Going to install this now and try if the delay is shorter. The previous one was annoying that I disabled.
Beamed from my very paranoid and harsh Nexus⁴
Got rid of the 30 second delay being a known issue since it's part of the mod and is mentioned in notes.
I will be away for a week so I won't be able to support the thread for that time, happy flashing!
Re: [MOD] Improve Touch Screen Sensitivity
Works great thanks!
Sent from my Nexus 4 using xda premium
Now how can I flash things in the recovery since it's all touch..
rockneo said:
Now how can I flash things in the recovery since it's all touch..
Click to expand...
Click to collapse
When you boot into recovery just wait a minute for the touch screen to start responding then carry on as normal.
Whats happening is the touch driver is being reflahed back to 027 one.
meangreenie said:
When you boot into recovery just wait a minute for the touch screen to start responding then carry on as normal.
Whats happening is the touch driver is being reflahed back to 027 one.
Click to expand...
Click to collapse
Thank you.
Re: [MOD] Improve Touch Screen Sensitivity
Wow this really works. None of the placebo stuff here. Really responsive now. Thanks +1
Sent from my Nexus 4 using xda premium
Main thread + features + install instructions + dev support
http://forum.xda-developers.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
To take a screen shot, just slide left
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:
Xperia Z - CM kernel (yuga)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Xperia Z stock kernels
http://forum.xda-developers.com/showthread.php?p=46613286
Click to expand...
Click to collapse
XDA:DevDB Information
[yuga][CWM Advanced Edition] PhilZ Touch, Tool/Utility for the Sony Xperia Z
Contributors
Phil3759, shoey63, [NUT], DooMLoRD
Version Information
Status: Stable
Created 2014-03-29
Last Updated 2014-10-11
Cwm touch recovery sounds awesome. I'm not brave enough to try it yet though , until someone else has
Sent from my C6603 using XDA Premium 4 mobile app
So just flash with fastboot?
Sent from my C6602 using xda app-developers app
shoey63 said:
So just flash with fastboot?
Sent from my C6602 using xda app-developers app
Click to expand...
Click to collapse
It is the recovery.img outputted by cm-10.1 build
So, if you have a shared boot/recovery kernel, it will work only on cm-10.1 ROMs until someone repacks it for stock ROMs
If you have a dedicated recovery partition, you can flash without much trouble, in theory...
But, I am not responsible of any damage. This is mainly for devs or advanced users knowing what I am talking about
Consider it as really early preview until it is better tested.
@[NUT] compiled open source version and all was working he said. So, I do not expect big issues
Phil3759 said:
It is the recovery.img outputted by cm-10.1 build
So, if you have a shared boot/recovery kernel, it will work only on cm-10.1 ROMs until someone repacks it for stock ROMs
If you have a dedicated recovery partition, you can flash without much trouble, in theory...
But, I am not responsible of any damage. This is mainly for devs or advanced users knowing what I am talking about
Consider it as really early preview until it is better tested.
@[NUT] compiled open source version and all was working he said. So, I do not expect big issues
Click to expand...
Click to collapse
I can repack it into my kernel. I'll test it and let you know.
Thank you!
Don't worry Phil, I know how to get myself out of trouble
Looking forward to @alnikki25k's repack:thumbup:
Sent from my C6602 using xda app-developers app
shoey63 said:
Don't worry Phil, I know how to get myself out of trouble
Sent from my C6602 using xda app-developers app
Click to expand...
Click to collapse
Happy to see you back @shoey63
You did a huge debugging and contributed a lot to make this project last, when it started timidly a year ago
What you can do is:
fastboot flash it or in cwm if possible
Boot into recovery. Give me a feedback and then flash back your kernel for your daily ROM
But don't kill me if your XperiaZ dies
All good Phil:thumbup: Just need touch working
Sent from my C6602 using xda app-developers app
Yay!
I'll get a locked bootloader version out as soon as I get home.
Thanks!
Sent from my C6603 using xda app-developers app
Re-packed As reported, touch does not work.
I'll see what else is not working.
Also, the Aroma File Manager needs an additional zip no?
EDIT: Looks like the touch is registered. I get a haptic feedback when I tap anywhere on the screen. But just can't use it.
alnikki25k said:
Re-packed As reported, touch does not work.
I'll see what else is not working.
Also, the Aroma File Manager needs an additional zip no?
EDIT: Looks like the touch is registered. I get a haptic feedback when I tap anywhere on the screen. But just can't use it.
Click to expand...
Click to collapse
Great it boots and works
Maybe touch needs extra kernel enablers or echo to some /sys/.../touch path
Unless the device has flipped x/y axis. In that case, touch events should register but not considered most of the time
If screen reacts to touch under some parts/scrolls, it is second case, else first
Phil3759 said:
Great it boots and works
Maybe touch needs extra kernel enablers or echo to some /sys/.../touch path
Unless the device has flipped x/y axis. In that case, touch events should register but not considered most of the time
If screen reacts to touch under some parts/scrolls, it is second case, else first
Click to expand...
Click to collapse
Seems like the first case. It does not react except for the haptic feedback. However, when I open the log in the advanced menu and it prompts to press any key to continue, touching the screen registers as a key press and it returns to the previous menu.
EDIT: I could upload TWRP recovery which has touch working if that would help.
alnikki25k said:
Seems like the first case. It does not react except for the haptic feedback. However, when I open the log in the advanced menu and it prompts to press any key to continue, touching the screen registers as a key press and it returns to the previous menu.
EDIT: I could upload TWRP recovery which has touch working if that would help.
Click to expand...
Click to collapse
Humm
Seems like touch is working then, else you won't get any feedback
I will look at TWRP to see if device has flipped or inversed axis
Else, I will release a touch debug version to see what's going
If you need the TWRP release for this phone
https://mega.co.nz/#!IkI2XZCS!QeEcmBUWlbD7rBER8502Sx-cJ6lX_aIJq9aVcuGyNgo
Click to expand...
Click to collapse
@Phil3759
http://nut.xperia-files.com/
XZDualRecovery 2.7.10 BETA contains your PhilZ Touch Recovery. It (not very surprisingly) has the touch screen bug described as above by others. This version is now working fine on locked bootloader devices, except the bugs of course
[NUT] said:
@Phil3759
http://nut.xperia-files.com/
XZDualRecovery 2.7.10 BETA contains your PhilZ Touch Recovery. It (not very surprisingly) has the touch screen bug described as above by others. This version is now working fine on locked bootloader devices, except the bugs of course
Click to expand...
Click to collapse
Thank you a lot (out of my :good: today)
I will look at touch later
Le me know about any other bugs
Meanwhile, can someone repack with twrp recovery kernel and ramdisk files (init, *.rc and files in root) to see if it fixes touch
That's to be sure it is not a kernel issue not having touch enabled
Phil3759 said:
Thank you a lot (out of my :good: today)
I will look at touch later
Le me know about any other bugs
Meanwhile, can someone repack with twrp recovery kernel and ramdisk files (init, *.rc and files in root) to see if it fixes touch
That's to be sure it is not a kernel issue not having touch enabled
Click to expand...
Click to collapse
Will work on that now.
alnikki25k said:
Will work on that now.
Click to expand...
Click to collapse
Great
That would make my life easier to debug it
Phil3759 said:
Great
That would make my life easier to debug it
Click to expand...
Click to collapse
Ok, I replaced the init, *.rc files and same problem. No touch response. Anything else I need to replace from TWRP?
alnikki25k said:
Ok, I replaced the init, *.rc files and same problem. No touch response. Anything else I need to replace from TWRP?
Click to expand...
Click to collapse
you replaced the kernel too? and all files in root?
Hello Galaxy Tab s2 Users! Welcome to my thread. For the past few days I have been building a fully modified and upgraded tab s2 ROM. These upgrades include taking apps from the s8 and Note 8 and putting and optimizing them for the Tab S2.
Please follow my install instructions carefully as the ZIP is not flashable.
Requirements:
Android 7.0 Stock Nougat ROM
This ROM is based of the latest UK version of the 7.0 15 December. It's taken me quite a while to make this so please push that like button!
ROM DOES NOT COME PRE ROOTED.
Now what's in this ROM?
Well... Everything you could possibly imagine!
Updated Touchwiz Home to 9.0.xxx (don't remember the full version number!)
Updated Dream Calculator
Updated Dream Calendar
Updated Camera to Tab S3 icon
Updated Dream Clock
Updated Dream Contacts
Updated to newest Gallery (looks amazing [emoji16])
Updated Game Launcher to newest Rendition!
Added Game tuner as system app for further HW Control
Added Kernel Adiutor Mod as Kernel tuner (Synapse wasn't working[emoji24]. Feel free to try it though!)
Updated Dream Messages
Updated to Latest in callui (Basically the phone app)
Updated Quick Connect to Samsung Connect
Updated to Dream Music
Updated Memo to Samsung Notes (So much better [emoji106])
Updated Video List,editor and trimmer to Latest version
ADDED ALWAYS ON DISPLAY
This ROM also uses the N4N kernel by engine95 (Thank you so much for this kernel. You ROCK dude!)
I've also removed a lot of the Google apps to reduce size and further enhance the experience
BUGS:
Well I don't like talking about this but I'll admit there are a few bugs left over.[emoji22]
1.Samsung Account-FIXED
2.Samsung Connect- FIXED
3.Touchwiz Home: Can crash sometimes. FIX-Coming Soon
4.AOD: FIXED
Install Instructions: This is NOT a FLASHABLE ZIP. FOLLOW INSTRUCTION PROPERLY: DO NOT WIPE!!!!
1. Go to TWRP recovery and make a backup of your boot.
2.Then reboot to your original ROM
3. Now with the downloaded ZIP copy the full folder into the directory where you kept the boot backup (NOT in the boot folder. Outside of it) (see pictures). Also download Superuser 2.82. Also copy the folder , not it's contents.
4.Make sure it is in the correct place
5.Now charge your tab and get ready.
6. Make a backup of your current ROM or carry around a copy of lineage OS as a backup in case things go wrong so you can flash and get back in.
7. Reboot to recovery again.
8.if you've done the steps PROPERLY you should see a new file in the restore section of TWRP.
9. If step 8 is fulfilled then now WIPE system,dalvik cache, data and cache
10. Go to the restore option and restore the Dream.T715 folder. (Do not restore the boot you made earlier. That's just a reference point)
11. After the restore is completed install supersu and WIPE dalvik cache and then reboot!
Success. Sorry for the tedious install process. I'm not a very good dev and so don't or probably can't make a flashable ZIP.
Thank you and hopefully you enjoy my ROM!!!!!
Link:
V1.2: https://drive.google.com/file/d/1uoYgjtiwavGM16XYnppeLHn4VRCMmsBz/view?usp=drivesdk
V1.4: https://drive.google.com/file/d/1gJ-gCMGh61gpiSVdsee3b7XWvoYxJrMw/view?usp=sharing
Please flash 3.57 kernel from engine 95s thread. Will release optimal (in my case at least) kernel auditor settings soon. Enjoy!!!
Many Fixes!!!!
Enjoy!!! Here are the screen shots!
https://drive.google.com/file/d/1OEBkYUwCh16Seh5ABMenxkeWSWptoi5i/view?usp=drivesdk
Kernel Source:
N4N
https://github.com/engine95
Changelog v1.2
1. Added Google play Games (I felt it was annoying to keep going to the play store to download it.
2. Updated all of the remaining google apps.
3.Added app called 'backlight'. If your HW lights for recents and back fail after a long time of AOD then go to this app and click reset to 1.5 seconds.
4.Debloated a little more.
5.Shortened ROM size. Removed 500 megabytes
6. MAJOR: ALWAYS ON DISPLAY Backlight issues FIXED.
Enjoy everyone!
Changelog 1.4
1. ROM rebuilt using latest U.K sources and every mod rewritten and optimized. This means ROM size has reduced by around 100 - 200 MB and more ROM runs a lot faster.
2. Updated kernel (more of went down to 1.3). This kernel appears to run faster and is more stable. Update to 3.57 manually.
3. Updated some more google apps and made the ROM magisk compatible. This allows install of Audio mods such as Dolby Atmos. DO NOT INSTALL AM3D. IT WILL BOOTLOOP THE ROM DUE TO SAMSUNGS CUSTOM EXYNOS SOUND CHIP. After installing Dolby atmos you should create a blank file and replace audioeffects.config in /system/etc and replace it.
4. Various under the hood changes and bug fixes.
5. New optimal kernel adiutor mod settings will be released soon.
Enjoy another release!!!! (Last one for a while coz of exams) [emoji23]
There is only one real bug now.
BTW forum administrator, you're making this way more difficult than it needs to be. (next post)
Click to expand...
Click to collapse
Not sure why only you have problems. By the way, using "XDA legacy app" tells its own story.
Skulldron said:
One more bug: AOD: If you leave AOD on for sometime then there is a chance it will glitch and the recent keys backlight won't work. Unfortunately the only way to fix this is to delete AOD from /priv app and restart.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
what did u use to get aod work please tell since i am using t710 and cant restroe this rom......
---------- Post added at 09:27 AM ---------- Previous post was at 09:24 AM ----------
Skulldron said:
One more bug: AOD: If you leave AOD on for sometime then there is a chance it will glitch and the recent keys backlight won't work. Unfortunately the only way to fix this is to delete AOD from /priv app and restart.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
please tell!!!!!!!!!!!!!!!
dying to try aod on my t710!!!!!!!
Skulldron said:
One more bug: AOD: If you leave AOD on for sometime then there is a chance it will glitch and the recent keys backlight won't work. Unfortunately the only way to fix this is to delete AOD from /priv app and restart.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
too bad .. AOD would have been a great addition-anyway looking forward to your updated link. Thanks!
btw one of your screenshots had a washing machine shown
Screenshot_20171226-110333.png
@Mac331us AOD does work but its a little buggy. I found a temporary fix but it causes a different glitch. If you remove AOD plugins from priv app. this bug does not happen because AOD refreshes the hw lights every time. But this means that every time you lock your device and AOD pops up the recent key lights light up for a second and if you press the keys the lights become active... so yeah. But it is a working fix just little weird.
Link Updated
errr... you shouldn't put your efs files there. restoring efs from other device will copy your imei as well if i'm not mistaken. there will be multiple device with your emei later on. anyway its not that hard to learn making the zip files. its all here in xda.
Do not use other Device EFS Partition .. IMEI is unique for every device and every device which is manufactured will be given different IMEI no hence you cannot use any other device IMEI its against the law...
Click to expand...
Click to collapse
Hello everyone. I've released an update for this ROM and I've removed the copy of efs. Thankyou for being patient and you can now (hopefully) enjoy this ROM. Also look at changelog for some 'fixes' [emoji16]
Sent from my [device_name] using XDA-Developers Legacy app
mac231us said:
too bad .. AOD would have been a great addition-anyway looking forward to your updated link. Thanks!
btw one of your screenshots had a washing machine shown
Screenshot_20171226-110333.png
Click to expand...
Click to collapse
Also that washing machine if you look at bottom right is the Samsung connect video
Sent from my [device_name] using XDA-Developers Legacy app
Skulldron said:
Also that washing machine if you look at bottom right is the Samsung connect video
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
ah! got it!
---------- Post added at 11:29 AM ---------- Previous post was at 11:27 AM ----------
thanks so much! "MAJOR: ALWAYS ON DISPLAY Backlight issues FIXED." downloading now..
edit:
just bootloops does not get past Samsung Tab S2 white letters on black screen (followed exact instructions)
mac231us said:
ah! got it!
---------- Post added at 11:29 AM ---------- Previous post was at 11:27 AM ----------
thanks so much! "MAJOR: ALWAYS ON DISPLAY Backlight issues FIXED." downloading now..
edit:
just bootloops does not get past Samsung Tab S2 white letters on black screen (followed exact instructions)
Click to expand...
Click to collapse
Cool send in results and review [emoji4]
EDIT: Don't restore Radio file
Skulldron said:
Cool send in results and review [emoji4]
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
hi
not sure if you saw my post in its entirety-was NOT able to get this backup to boot. Thanks.
mac231us said:
hi
not sure if you saw my post in its entirety-was NOT able to get this backup to boot. Thanks.
Click to expand...
Click to collapse
Hey I saw it[emoji4]. Try restoring just the system and boot not radio.
Sent from my [device_name] using XDA-Developers Legacy app
Skulldron said:
Cool send in results and review [emoji4]
EDIT: Don't restore Radio file
Click to expand...
Click to collapse
I tried that too earlier (was just my guess as did not see a need for that)-will try again. Did with and without supersu too.
essentially wipe all, then restore the backup you posted without radio (not doing supersu), then dalvik wipe?
mac231us said:
I tried that too earlier (was just my guess as did not see a need for that)-will try again. Did with and without supersu too.
essentially wipe all, then restore the backup you posted without radio (not doing supersu), then dalvik wipe?
Click to expand...
Click to collapse
Try restoring a full stock nougat rom,then root with twrp and follow all instruction and don't restore Radio file.
Sent from my [device_name] using XDA-Developers Legacy app
Skulldron said:
Try restoring a full stock nougat rom,then root with twrp and follow all instruction and don't restore Radio file.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
maybe this is the issue-I am on stock rooted lollipop (had nougat but was trying other things-ok will work on this)...bootloader is different
mac231us said:
maybe this is the issue-I am on stock rooted lollipop (had nougat but was trying other things-ok will work on this)...bootloader is different
Click to expand...
Click to collapse
Oh... Well I'm still not sure about radio file but you can give it a shot i guess.
Sent from my [device_name] using XDA-Developers Legacy app
thank for the Rom. but I have to say, it is laggy and has very bad battery life. always on display is a cool feature but it has to be integrated deeper from Samsung because otherwise the device doesn't go into deepsleep and loses a lot of battery. my tablet got 11h stand by with aod and is fully out of charge. in bettery settings the display was on the full time. little bit sad but that's how it is when samsung doesn't give us support for aod. but thanks anyway for your efforts!
Skulldron said:
Oh... Well I'm still not sure about radio file but you can give it a shot i guess.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Works!...runs well-not sure about the other poster's 'lagginess'...imo everything is always laggy and never fast enough but I do not see difference in response versus stock so that in of itself is a testament to its smoothness. As for battery life too early to tell and that varies with use - hard for me to keep it on standby for extended periods but might try tonight
the AOD could use from a bigger display size (too small for the large screen imo-calendar option would be nice as on S8 and brighter setting definitely-too dim but then some may find that draining battery even further-will see if indeed this is battery draining - all relative to stock; SIM if present even if passive will drain battery more than just on wifi-right now have my SIM in a phone but will try later with SIM in T715) Thanks so much!
PaterProx said:
thank for the Rom. but I have to say, it is laggy and has very bad battery life. always on display is a cool feature but it has to be integrated deeper from Samsung because otherwise the device doesn't go into deepsleep and loses a lot of battery. my tablet got 11h stand by with aod and is fully out of charge. in bettery settings the display was on the full time. little bit sad but that's how it is when samsung doesn't give us support for aod. but thanks anyway for your efforts!
Click to expand...
Click to collapse
The worse than normal battery life is because by default the ROM is overclocked and DVFS is almost entirely disabled. You'll have too root it to adjust the clocks and I know AOD isnt perfect but it's a start.
mac231us said:
Works!...runs well-not sure about the other poster's 'lagginess'...imo everything is always laggy and never fast enough but I do not see difference in response versus stock so that in of itself is a testament to its smoothness. As for battery life too early to tell and that varies with use - hard for me to keep it on standby for extended periods but might try tonight
the AOD could use from a bigger display size (too small for the large screen imo-calendar option would be nice as on S8 and brighter setting definitely-too dim but then some may find that draining battery even further-will see if indeed this is battery draining - all relative to stock; SIM if present even if passive will drain battery more than just on wifi-right now have my SIM in a phone but will try later with SIM in T715) Thanks so much!
Click to expand...
Click to collapse
Any lag that is present right now will be ironed out in the future. This is just almost the second release of the ROM and the other two times have been just bug fixes! But I'm glad to see you are enjoying this ROM. I will keep pushing out updates to help further optimize it but be patient and it will come eventually. Also anyones thought s on adding Xposed into the system and also magisk support?
One last thing: I'm planning to port this ROM to t710,t810 and t815. I'm looking for beta testers so if there any private message me. This ROM also is being updated to android 7.1.1 Samsung Experience 8.1. Although I can't promise anything because it is being very difficult right now.
Sent from my [device_name] using XDA-Developers Legacy app