I am using Nexus 4... is anyone aware to Wake up phone from sleep mode other than pressing power button ??
I have seen video once on you tube however i am unable to find that vidio now
Try this, you need a custom kernel and root for this: https://play.google.com/store/apps/details?id=me.paranoid.touchcontrolfree
Sent from my Nexus 4 using Tapatalk 4 Beta
Touch Control
If u r not rooted.. You can go for Smart Screen ON app
Sent from my Nexus 4 using xda premium
andyabc said:
Try this, you need a custom kernel and root for this: https://play.google.com/store/apps/details?id=me.paranoid.touchcontrolfree
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Currently incompatible with 4.3, however
I don't like the idea of the phone being in the pocket, and turning itself on because of pressure touches in the screen...
Also keeping the phone always 'listening' for touches will fore sure take a toll on the battery.
try this app "Gravity Screen - On / Off" , no root required
https://play.google.com/store/apps/details?id=com.plexnor.gravityscreenofffree&hl=en
Related
Anyone had this one? Since 4.2, the screen momentarily goes black, with a similar transition to hitting the task manage soft key, but transiting to the left in landscape, then flicks back to normal use. Happens in apps...screws up some games, puts others into pause mode as if a task has been switched. Thought it might have had something to do with auto rotation going a bit bonkers, but not sure....
Not heard any reports...have looked through the forum, couldn't find anything.
Weird...it just did it then....but the keyboard stayed on screen, xda disappeared to the left...
Any thoughts and thanks in advance
Sent from my Nexus 7 using xda app-developers app
Thank God! Thought it was just me!
Sent from my Nexus 7 using Tapatalk 2
Ok..just happened again while in portrait mode. Definitely saw it flick to landscape. Rotation is locked btw.
Hmmmmm.....
Sent from my Nexus 7 using xda app-developers app
It happened to me three times last night after update to 4.2 :crying:
Ok...so, while sitting in a tedious meeting, Nexus in landscape, propped up with its folding case the screened flipped upside down and stayed upside down. 3 times. My ipad using colleague giggled.
Any way to recalibrate the tilt sensor? Or any other suggestions?
It's not the end of the world but...there must be a patch solution or other? Before 4.1 I used the auto rotate app, I forget its correct name...
Thoughts?
Sent from my GT-I9100P using xda app-developers app
I used logcat to monitor the Nexus 7 until the random rotation happened. After looking at the log I realized that it was always the same process being activated and that process was nVision.
Since nVision always rotates into landscape mode I was suspicious that perhaps when it tried to update itself in the background it was changing the screen orientation. I disabled notifications and then uninstalled the app and the problem has completely gone away. I have had no random rotations at all in the last 24 hours.
Sent from my Nexus 7 using Tapatalk 2
Thanks very much. Ill give it a try and report back
Sent from my Nexus 7 using xda app-developers app
Okie doke.
For the record.... 48 hours and no random flips to landscape and back. I'd be willing to be a substantial amount of money this was the culprit. However, whether this is a 4.2 issue per se vs. Bad behavior in nVision is an open Question.
Sent from my Nexus 7 using Tapatalk 2
Ok. Disabling nvision notifications still flips out. Will uninstall later.
Thanks again
Sent from my GT-I9100P using xda app-developers app
Uninstall it. I still think it checks in and screws your screen, whether it shows you the notification or not.
Sent from my Nexus 7 using Tapatalk 2
Uninstalled...all good so far. Woooooo!
Cheers!
Sent from my Nexus 7 using xda app-developers app
This has been happening since I remember getting the device. About 3/5 times when I bring my device out of standby and I go to enter my pattern the touch is off. I have "show touches" enabled in developer options to verify this.
When I put my finger on the top left dot of the 3X3 pattern, which is around the middle-left of the screen, it is detecting that I'm touching the device all the way in the top left corner. If I drag my finger around the screen, the touch is offset. If I remove my finger from the screen and place it back on the screen, then it is properly detected.
I didn't run on stock for very long, maybe an hour or two, before I rooted and flashed AOKP. Right now I'm on WhiteHawkx's unnoficial AOKP nightly and Franco's Kernel (r122).
My plan is to flash back to stock and see if it still happens then. But currently I have a really busy week ahead and don't have time so looking for insight.
Anyone else experience something like this?
No one? So I guess I should call Google for a warranty exchange?
Sent from my Nexus 4 using xda premium
fone_fanatic said:
No one? So I guess I should call Google for a warranty exchange?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I would do that if I were you.
Sent from my Nexus 4 using xda app-developers app
Try recalibrating the touch screen, I think there's an option in settings.
Sent from my HTC One X using xda app-developers app
It's franco's kernel, I have it too.
.coomb. said:
It's franco's kernel, I have it too.
Click to expand...
Click to collapse
I posted in that thread a while ago about this issue and no one confirmed. Thanks for your reply. I'm going to go back to stock this weekend and run it for a couple days to verify.
Sent from my Nexus 4 using xda premium
fone_fanatic said:
I posted in that thread a while ago about this issue and no one confirmed. Thanks for your reply. I'm going to go back to stock this weekend and run it for a couple days to verify.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Let me know your results. If it persists, I might have to send mine back.
I'm on stock ROM. I have this issue too, when I power on and drag to unlock, I get a delayed mismatched response. I have to power off then back on again.
It started this recently, so might be app related.
Sent from my Nexus 4 using xda app-developers app
Vyker said:
I'm on stock ROM. I have this issue too, when I power on and drag to unlock, I get a delayed mismatched response. I have to power off then back on again.
It started this recently, so might be app related.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
What kernel are you running?
Vyker said:
I'm on stock ROM. I have this issue too, when I power on and drag to unlock, I get a delayed mismatched response. I have to power off then back on again.
It started this recently, so might be app related.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Turn on " show touches" in developer options to help verify if you the save thing happening.
I don't have to reboot mine but I have to lift finger of screen and put back on to get it to properly detect where the touch should be.
Sent from my Nexus 4 using xda premium
So just as a follow up I reverted to stock for 5 days and didn't see this issue. Flashed back to AOKP and Franco kernel and now it's happening randomly when I go to hang up a call. I tap on the red hang up bar and it detects the touch in the top left corner.
I called Google play support but since I didn't buy my device from them they directed me to lg.
I'm starting to think it's my screen protector.
Sent from my Nexus 4 using xda premium
lol, I had insensitivity issues on the bottom of the screen way back, I use a displayed pin pad on lockscreen so I just tap a certain spot to unlock, I sometimes wonder why the digitizer register incorrectly.
flashing a different kernel helped, I'm using motleys.
Have had this problem since launch, im on stock rooted, maybe its a certain app?
If anyone wants to compare their apps with me to find a similar problem, shoot me a pm
Hey guys, I need your help. I'm going berserk, because I've been searching a good kernel for my galaxy s3 (WITH CYANOGENMOD 10.2) that have the knock on function (double tap to wake the display) like the LG G2. Can you help with a list of kernel that have this function also COMPATIBLES with my CYANOGENMOD 10.2??
Thx
Sent from my GT-I9300 using xda app-developers app
Boeffla has an integrated Touch wake Feature.
Gesendet von meinem GT-I9300 mit Tapatalk
I will try boeffla, thx
Sent from my GT-I9300 using xda app-developers app
A question... In the boeffla can I set the double touch, or there is only a touch?
Sent from my GT-I9300 using xda app-developers app
_avirox_ said:
A question... In the boeffla can I set the double touch, or there is only a touch?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
This double tap feature does not exist for our phone. Touch2wake is also only available for a few seconds after the screen goes off. Everything else would just drain the battery. According to boeffla our hardware wouldnt support the double tap to wake feature without sucking battery
Sent from my GT-I9300 using XDA Premium 4 mobile app
Ok... I will put boeffla for the battery and others personalitations cause now I've already cyano kernel. Thanks
Sent from my Galaxy S3 with an airplane
boeffla just has a single tap wake not a double tap
it can be only used to wake for a few seconds after the screen is turned off
does anyone know how to "control" this function ?? i mean , without tweaking it manually. An app for example... Nexus has touch control but this kernel is not suported in touchcontrol..
cheers !
keemo.rom said:
does anyone know how to "control" this function ?? i mean , without tweaking it manually. An app for example... Nexus has touch control but this kernel is not suported in touchcontrol..
cheers !
Click to expand...
Click to collapse
Use Boeffla Config from the Playstore. You can change the delay of the Touchwake with that.
Check boeffla-kernel.de for the documentation.
ok installed Boeffla... Allllll right
Moster2 said:
This double tap feature does not exist for our phone. Touch2wake is also only available for a few seconds after the screen goes off. Everything else would just drain the battery. According to boeffla our hardware wouldnt support the double tap to wake feature without sucking battery
Click to expand...
Click to collapse
But there is a function to wake up with proximity sensor. It doesn't suck battery much. So, it would be good if someone could write a code to combine proximity wake up to implement knock2wake. 1) after pick up phone from pocket, proximity sensor could power on the touch layer,
and stay active for a defined period - 10-20 seconds. Then double tap should unlock the device.
What do you think about it?
Been having problems with my screen lately. Its hard to explain but some of the screen isn't responding to touch.
I'll click on find on page in chrome and it will go to the option below it. Seems to be very unresponsive too. Some of the keys dont work when typing. When I press the power and unlock they start to work again.
Running PA beta 4 and more recently beta 5 both with the same problem. Pretty sure the problem came half way through using beta 4.
Anyone know what's going on?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Basically when I go down from where that pointer is it is unresponsive. Anyone know why this is?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Id it very difficult orbimpossible to turn on screen using double tap like lg g2 ?
Sent from my SM-G900F using XDA Free mobile app
Why would you want this?? Stop being lazy and just press the damn home button!
Sent from my SM-G900F using XDA Premium 4 mobile app
majidshahab091 said:
Id it very difficult orbimpossible to turn on screen using double tap like lg g2 ?
Sent from my SM-G900F using XDA Free mobile app
Click to expand...
Click to collapse
up to now... I don't think it is visible AFAIK.
And if you try to google out there, there is/are app(s) which manipulate this function, by keep screen on, and make the color of the screen turn black (as if it is off). And it is working only with OLED display.
I never use/try it, because I don't really like the idea with my N3, whereby I have the s-view attached already.