OP includes a link to a flashable stock 4.2.2 kernel with enabled module support.
[APP/MOD] TouchControl (Nexus 4)
- Thread starter bponury
- Start date
- Status
OP includes a link to a flashable stock 4.2.2 kernel with enabled module support.
Re: [APP/MOD] TouchControl (a.k.a. PGM Nexus, a.k.a. Slide2Wake) - forget the buttons
Also facing the screen freezing issue here. Using Stock ROM and Franco kernel.
I noticed that freezing will happen if I put my phone inside my shirt pocket with the screen facing my body. If I turn the back of the phone touching my body, it will not freeze.
Sorry for my bad english.
Sent from my Nexus 4 using xda premium
Also facing the screen freezing issue here. Using Stock ROM and Franco kernel.
I noticed that freezing will happen if I put my phone inside my shirt pocket with the screen facing my body. If I turn the back of the phone touching my body, it will not freeze.
Sorry for my bad english.
Sent from my Nexus 4 using xda premium
AW: [APP/MOD] TouchControl (a.k.a. PGM Nexus, a.k.a. Slide2Wake) - forget the buttons
update for faux 007b06?
Gesendet von meinem Nexus 4 mit Tapatalk 2
update for faux 007b06?
Gesendet von meinem Nexus 4 mit Tapatalk 2
Re: [APP/MOD] TouchControl (a.k.a. PGM Nexus, a.k.a. Slide2Wake) - forget the buttons
People repeatedly asking isn't going to make it happen any quick.
You're just spamming the thread.
People repeatedly asking isn't going to make it happen any quick.
You're just spamming the thread.
Re: [APP/MOD] TouchControl (a.k.a. PGM Nexus, a.k.a. Slide2Wake) - forget the buttons
I am running latest CM10.1 nightly and r90 franco.Kernel and the module will not load. It has root access. Anything else I need to do? I just want to ensure it works then I'll probably buy the app
I am running latest CM10.1 nightly and r90 franco.Kernel and the module will not load. It has root access. Anything else I need to do? I just want to ensure it works then I'll probably buy the app
I am running latest CM10.1 nightly and r90 franco.Kernel and the module will not load. It has root access. Anything else I need to do? I just want to ensure it works then I'll probably buy the app
The free version doesn't get updated as frequently so you usually have to wait a few days after the paid one gets updated, before the free one will receive the same updates. I personally don't use Franco's kernel so I'm not sure which revision is compatible with Touch Control at the moment.
Re: [APP/MOD] TouchControl (a.k.a. PGM Nexus, a.k.a. Slide2Wake) - forget the buttons
Ahh so the paid one is the one that gets updated? Okay...I'll bit the bullet
Edit: Works perfect!
Ahh so the paid one is the one that gets updated? Okay...I'll bit the bullet
Edit: Works perfect!
Last edited:
Re: [APP/MOD] TouchControl (a.k.a. PGM Nexus, a.k.a. Slide2Wake) - forget the buttons
Anyone know the settings to make slidetowake a vertical motion from the bottom to top like the Z10?
Anyone know the settings to make slidetowake a vertical motion from the bottom to top like the Z10?
Re: [APP/MOD] TouchControl (a.k.a. PGM Nexus, a.k.a. Slide2Wake) - forget the buttons
And it works with r91
And it works with r91
I know a couple of people posted settings similar to it earlier in this thread. Try searching for it or hope one of them will post it again.
[APP/MOD] TouchControl (a.k.a. PGM Nexus, a.k.a. Slide2Wake) - forget the butto
Okay, I will dig through this thing. Thanks dude!
Okay, I will dig through this thing. Thanks dude!
Ok guys so I have an issue. I am running CM 10.1 (jb 4.2.2) on my Nexus 4 and I tried to flash the modified stock kernel posted on the first page but it ends up giving me a serious NFC or com.google.phone something like that error and I can't get past the error message. Pressing okay doesn't do anything...cuz the error message keeps popping up. So, I am unable to unlock the device to even test the touch control.
I flashed CM10.1 again to fix that issue but I am still stuck with non-working Touch control on CM10.1. I have the paid version of touch control which is updated for 4.2.2 (not using the free one).
Can anyone help?
Thanks
I flashed CM10.1 again to fix that issue but I am still stuck with non-working Touch control on CM10.1. I have the paid version of touch control which is updated for 4.2.2 (not using the free one).
Can anyone help?
Thanks
Did that at least 3 times. Same issue. Any other working kernel(s) <-- more than one, that you can recommend? which Touch Control will work with?
Actually I'm using that stock kernel right now. Have you tried re-downloading the .zip (it's md5 is: 793bbbd20694c662d8622e2bd1c8bfb5)
same here cant get touchcontrol to load properly.
using 1.16a pgm nexus paid version
just gives me the fail unable to load any module error.
using [ROM] XenonHD Stable-5.0 (23.02.13) and the kernel from the original post.
any ideas?
Actually I've installed CM and my kernel and yes there is a problem. But IMO this might be related to CM, maybe CM requires something in the kernel? I will investigate this further.
- Status
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
247**** ROOT NEEDED ****
I proudly announce - TouchControl V2
________________ DESCRIPTION
To all who don't know this yet, this is a kernel module with a control application which allows you to perform some gestures that will in turn will execute some action (like simulating power key press or turning volume up).
List of configurable gestures:
- slide - move finger (or fingers) on the screen in some way
- pinch - pinch screen with two or more fingers
- tap - tap the screen with one or more fingers in some place of the screen (or any place)
List of configurable actions:
- press POWER
- press VOLUME UP
- press VOLUME DOWN
- increase BRIGHTNESS
- decrease BRIGHTNESS
- play NEXT SONG
- play PREVIOUS SONG
- press HOME BUTTON
- press BACK BUTTON
________________ SCREENSHOTS
________________ FAQ
- will it work on kernel X
It is made to work on stock kernel. It might work on kernels which are close to stock. I will however try to find a way to make it as compatible as possible. I'm going to assume that you can safely try this mod on your kernel (but don't enable set-on-boot) worst case scenario is a reboot.
- does this consume battery
Short answer - Maybe.
Long answer - this might bring some drain, some users report quite a big battery drain some not, I will address this issue in some time. Check yourself how much an issue it is for you. Also this change from device to device so there is no short answer (look up)
- will it break my touchscreen
Short answer - No
Long answer - Digitizer is not mechanical so it shouldn't break. The same mod works for more then 2 years on my Galaxy Nexus and it never lost a bit of it's responsiveness
- why do I have to pay
Why did you pay for your phone? You did save a few bucks on the phone which was cheap. Now is your chance to make those savings worthy
- if I want to marry you where can I find you?
Oh... this question meant to go somewhere else ;P And I'm taken.
________________ DOWNLOADS
FREE: https://play.google.com/store/apps/details?id=me.paranoid.touchcontrolfree
PRO-TURBO: https://play.google.com/store/apps/details?id=me.paranoid.touchcontrol
________________ DISCLAIMER
THIS IS HIGHLY EXPERIMENTAL AND ALWAYS BE - PLEASE USE AT YOUR OWN RISK!
________________ HOW TO UPDATE
- Uninstall the app
- Reboot device
- Install fresh from play store
.
.
.
.
.
.
.
XDA:DevDB Information
TouchControl, a Tool/Utility for the Google Nexus 4
Contributors
bponury
Version Information
Status: Beta
Created 2013-10-03
Last Updated 2014-03-2240_____________________ CHANGELOG _____________________
- v1.8.1 - 2013-08-17
- fixed load issues and disappearing modules
- fixed 4.2.2 support for Franco kernels (please note that there will be no more updates to 4.2.2)
- v1.8.0 - 2013-08-16
- added support for some 4.3 kernels
- switched to online module downloading instead of in-app modules (thus internet access is required)
- added update/refresh feature for module update checking (top-right refresh icon)
- v1.7.5 - 2013-07-06
- Fixed notification bar pulldown issue
- Maybe it's not necessary anymore to do an uninstall to do update...
- v1.7.4 - 2013-06-19
- THIS WILL NOT WORK ON FRANCO MILESTONE 2 - PLEASE USE NIGHTLY
- added (again) disabling touchscreen in phone call
- fixed support for latest kernels
- screen freezes seem to be fixed
- v1.7.3 - 2013-06-06
- another attempt to fix screen freezes
- fixed support for Faux beta and PA kernel
- removed phone state receiver (TC is active during calls!)
- v1.7 - 2013-05-29
- fixed support for Franco kernel nightly 143
- fixed support for Air Kernel #10
- fixed support for HellsCore
- fixed support for ParanoidAndroid kernel
- another attempt to fix screen freezes
- v1.6 - 2013-03-24
- added auto stock-modified kernel flashing option
- disabled input filtering (might help with screen freezes)
- v1.5e - 2013-03-04
- added support for latest Trinity kernels
- modified some guts, might work with more kernels
- v1.5c - 2013-02-27
- fixed support for latest faux stable
- added permissions for SU
- v1.5b - 2013-02-22
- fixed support for 4.2.2 Franco, Motley, Trinity and Faux
- fixed support for 4.2.2 Franco, Motley, Trinity and Faux
- v1.5a - 2013-02-09
- fix for matr1x kernel
- v1.5 - 2013-02-06
- add support for faux beta kernel
- fix proximity bug during call
- v1.4 - 2013-01-30
- fix support for franco kernels
- v1.3 - 2013-01-26
- fix major bug with input subsystem with version 1.2
- fix major bug with input subsystem with version 1.2
- v1.2 - 2013-01-26
- added motley kernel support
- small fixes
- v1.1 - 2013-01-22
- fixes for start-on-boot
- added more custom kernels support (franco, faux, matr1x, trinity)
- v1.0 - 2013-01-17
- initial release
29I am working on a few things at the same time. First is a new version of touchcontrol (and I mean a maaaajor upgrade). Second is the standby-drain problem and I'm gradually getting to know where it lies But it takes time to track because I have to wait a few hours to see if I am going in the right direction. Consider you are walking in the night with a walkie-talkie and can't see a thing. And someone tells you each 5 hours that you either should go left or right That's why it's taking so much time.
