Related
Sometimes my backbutton fires twice. Its very annoying when browsing and going a page back and it actually jumps 2 pages back.
I checked the behaviour with the app "KeyEvent Display" and it clearly shows that sometimes 4 events are fired instead of 2 (keyup + keydown).
The app requests root, but you dont need it for only testing the keyevents. Can anyone confirm this? Thanks
Mine does exactly the same, from what I've worked out its related to the phone running slow but I have no idea how to fix it, if we find an answer if be very grateful its very annoying!
Sent from my R800i using XDA App
Mine has the same problem too it's really annoying when using root explorer and it backs right out of the app!
Sent using telepathy!
thatsupnow said:
Mine has the same problem too it's really annoying when using root explorer and it backs right out of the app!
Sent using telepathy!
Click to expand...
Click to collapse
same with me, only on some apps though like tapatalk and root exploerer
Same here. ButI figured a way-out. just press it and take you finger off quickly then it works normal.
same here and same solution, press it quickly.. been living with it for 3 months already.. it just makes me sick sometimes...
I have contacted se-support and pointed them to this thread. Waiting for reply
Sent from my R800i using XDA Premium App
Same problem here... Xperia Play bought in april.
Anyone have any idea if this is software or hardware related? Is it all types of xperia plays, out just certain types?
Sent from my R800i using XDA App
Tested a bit more. The menu button is also haunted here. Fires sometimes multiple events like a fukn uzi. I really hope its not hardware related and se will fix the softwarebug
Sent from my R800i using XDA Premium App
I feel left out haha ive never had this problem. I have however had an issue where the screen decides to freak out and decides to do things at random, it gets annoying when im typing and all of a sudden all the keys start being pressed on thier own.
locking and unlocking fixed is temporarily.
Does anyone have a custom rom flashed with this issue still happening? That would tell us pretty quick if it was hardware/software related.
I have had this problem too well since i upgraded to 2.3.3
I have a UK Sim free generic handset unmodded.
d31b0y said:
Does anyone have a custom rom flashed with this issue still happening? That would tell us pretty quick if it was hardware/software related.
Click to expand...
Click to collapse
All the custom roms except for CM7 are based on the SE stock rom anyway, so if anyone on CM7 dosent have this problem the info would be useful
I have same issues with this for the up and down arrow it always post two key strokes in Bruce lee. I can't do some special moves and finish moves because of this I am wondering if I should try and get a replacement Verizon stock ROM
Could the double back button issue be caused by the circle button?
Maybe as you press the back button the back of the screen also pushes the circle button?
I dont have this issue btw.
Tbh i have only noticed this problem if i have the phone in my right hand and i use my thumb to press the back button (reaching over the phone to the back key). If i use the phone in my left hand and use my thumb no problem lol.
If i use it normally (phone in 1 hand and using a finger from my other hand) to press the keys i do not have this problem..... Strange
Well, I think I worked out what's happening. Try holding the 'R' shoulder key and press the back button.
I imagine what is happening is android is picking up the shoulder button press but it doesn't do anything. Then pressing the back button fires the event twice. The same way you can fool windows into repeating the wrong key when you hold 2 buttons down (may be fixed in windows ).
Now the question is, how the hell fan you fix it?
I'll submit it to SE later on tonight and see what they say.
EDIT: definitely seems to be certain apps. It doesn't happen in settings but does happen in tapatalk.
Sent from my R800i using Tapatalk
Same problem here
Sent from my R800i using XDA App
I found that the R/L Button Changer app that is in the Theme/APP forum stopped the problem.
Sent from my R800x using XDA App
Heelo.
I have noticed that sometimes (happened to me 3 times in 4 weeks now) while doing random things (most recentone was when i was looking at a picture on facebook and wanted to exit the picture), back and menu buttons under the screen don't respond. Home button works, touchscreen works, but menu and back key doesn't. In order to make it work I have to turn the screen on and back on so that they start working. I am using OMEGA 3.1 ROM and Faux 003 kernel.
Is anyone else experiencing the same problem?
Sent from my GT-I9505 using Tapatalk 2
Check if on stock rom it doesn't work either, or ask in the rom/kernel thread.
Sent with Samsung Galaxy S4 (GT I9505)
As I mentioned it happened 3 times in about 4 weeks now, so it's not a kind of thing that I could test with other roms, because it's very very rare. But I have also noticed that sometimes the same two buttons are less responsive than other times (like sometimes I can barelly press it with a tip of my index finger and it responds, but other times it does not respond when touched with point of finger, it only responds when I touch it with the pad of my finger - does it have something to do with electricity or softer skin on pads of fingers?).
Thank you
I've had this a few times in a bit over a week. Doesn't bother me as it's pretty rare and most likely a bug that will be fixed or possibly bugs in the apps themselves.
Good thing home button still works.
Sent from my GT-I9505 using xda premium
I also think it's a bug. Just had to ask as I didn't find anything with google
Thank you!!
I think he asked if you could test on a stock rom so you can see if its a hardware issue. Ive had mine for almost 4 weeks now and my back and menu button never failed to respond so far. Im on stock btw.
Same thing has happened to me a few times also.
I will be using an app or something, attempt to push the back button to get out of that app, and all of a sudden both the back button AND menu buttons die.... u press the area where they are located and nothing happens, no vibration, no light up, no nothing. The only way to fix it, is to restart the phone.
Only happens very rarely - and hard to guage when it might occur and repeat, due to its random nature.
Same thing happens to me. Also very rare, it's happened twice in 1 month
Sent from my GT-I9505 using XDA Premium HD app
tclocki said:
I think he asked if you could test on a stock rom so you can see if its a hardware issue. Ive had mine for almost 4 weeks now and my back and menu button never failed to respond so far. Im on stock btw.
Click to expand...
Click to collapse
Rooted now but very sure it happened when I was on stock as well.
Sent from my GT-I9505 using xda premium
I also have it happen from time to time. Don't have to reboot tho, it will start working by itself after a while.
Sent from my boomstick!
I was on stock Rom when it happened
Sent from my GT-I9505 using XDA Premium HD app
bump:
I have still this issue.
Having a i9505.
I am on Kitkat 4.4.2 C-Rom with Ktoonsez kernel.
Same thing with whatever kernel.
Not sure what it is really.
But it is annoying for sure.
Well. It worked up until about 20 mins ago. Then randomly just stopped working. Ive rebooted, shut down, enabled and disabled the feature in settings. Fixed permissions for the heck of it. Cleaned the screen. Reset calibration, etc. Nothing seems to work. I can double tap to shut the screen off easily, and it works flawlessly, but trying double tap to wake is completely useless. Any suggestions?
Sent from my LG-LS980 using xda app-developers app
Burkettacb said:
Well. It worked up until about 20 mins ago. Then randomly just stopped working. Ive rebooted, shut down, enabled and disabled the feature in settings. Fixed permissions for the heck of it. Cleaned the screen. Reset calibration, etc. Nothing seems to work. I can double tap to shut the screen off easily, and it works flawlessly, but trying double tap to wake is completely useless. Any suggestions?
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
Wow this is happening to me as well. I'm running the optimus rom currently. I'm reverting to stock here shortly in hopes for the KK update soon so I'll see if that fixes it.
nope. up to date stock zva now and knock on doesnt work but knock off does work as you stated. well this is wierd.
Well thats ****ing depressing
Sent from my LG-LS980 using xda app-developers app
Tons of lg users are experiencing this issue. Its a design flaw with a hardware component that easily breaks. Wonderful build quality -_-...right. So only option is replacing the phone. But to how soon, until the other one breaks. So its kinda like. Well. This blows. I suppose Ill install a custom kernel and enable screen wake features that way.
Sent from my LG-LS980 using xda app-developers app
Okay. So after hours of tapping. Which might i add. My fingers hurt, I am now able to activate the screen. Pausing after each tap, using my finger print area to tap "not to be confused with finger tip". The screen will activate. Also note, the standard two taps works sometimes, but with four presses, i seem to get the best results. Give it a try people. I have a theory the hardware has not failed. But yet, the activation area pixel size value changed. Either due to a conflicting app install. A intermittent system glitch etc
Sent from my LG-LS980 using xda app-developers app
I'm having the same issue with my G2. Knock-on/off was working fine. Had the phone in the sun for a little while (maybe 2 hours) and the knock-on has stopped working completely. Used a drawing app on my screen and found no dead pixels or strips. Knock off still works perfectly though.
This could also be an issue with your proximity sensor. If something (screen protector, finger, dust, etc.) is blocking your proximity sensor, it could be reporting to the phone that it is in a pocket, and to keep the screen off. Try to clean that area, and avoid obstructing the sensors "view". As for the leaving it in the sun, you could have damaged the sensor? You could test it by making a call real quick and see if the screen turns on when you pull the phone away from your face.
Sent from my LG-LS980 using XDA Premium 4 mobile app
The sensor seems to be working fine. Just tested it.
DrZeuss said:
I'm having the same issue with my G2. Knock-on/off was working fine. Had the phone in the sun for a little while (maybe 2 hours) and the knock-on has stopped working completely. Used a drawing app on my screen and found no dead pixels or strips. Knock off still works perfectly though.
Click to expand...
Click to collapse
Ya i got the same problem....at home it works perfect but when i went outside in the sun i can double tap like hell and screen didnt turn on(it turns on but cant see anything because its too dark like screen brightness is lower than low)...also power button didnt work...the proxi sensor is ok...i run the test menu and it shows that everything is ok...i also sent it back to my carrier and after a week of testing got it back. They found nothing and said that my described problem is a "feature".... sometimes it turns on after tapping und pushing the power button like hell and sometimes it doesent..
Your screen turns also on with very very low brightness or it is off? When u look really really close u can see it...for example hold power button and u can hardly see the white power off/reboot popup...but i dont know where the problem can be...germany d802 version..(Sorry for my BAD english)
4NDR345 said:
Ya i got the same problem....at home it works perfect but when i went outside in the sun i can double tap like hell and screen didnt turn on(it turns on but cant see anything because its too dark like screen brightness is lower than low)...also power button didnt work...the proxi sensor is ok...i run the test menu and it shows that everything is ok...i also sent it back to my carrier and after a week of testing got it back. They found nothing and said that my described problem is a "feature".... sometimes it turns on after tapping und pushing the power button like hell and sometimes it doesent..
Your screen turns also on with very very low brightness or it is off? When u look really really close u can see it...for example hold power button and u can hardly see the white power off/reboot popup...but i dont know where the problem can be...germany d802 version..(Sorry for my BAD english)
Click to expand...
Click to collapse
My screen turns completely on and off when I use the button/knock-off feature. I'm going to take it to a technician today and see what they have to say about it.
First, What are you running on your device? Stock? Rooted...
Burkettacb said:
Tons of lg users are experiencing this issue. Its a design flaw with a hardware component that easily breaks. Wonderful build quality -_-...right. So only option is replacing the phone. But to how soon, until the other one breaks. So its kinda like. Well. This blows. I suppose Ill install a custom kernel and enable screen wake features that way.
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
That's odd, I have not seen much on this... if running stock
Burkettacb said:
Okay. So after hours of tapping. Which might i add. My fingers hurt, I am now able to activate the screen. Pausing after each tap, using my finger print area to tap "not to be confused with finger tip". The screen will activate. Also note, the standard two taps works sometimes, but with four presses, i seem to get the best results. Give it a try people. I have a theory the hardware has not failed. But yet, the activation area pixel size value changed. Either due to a conflicting app install. A intermittent system glitch etc
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
Or againg, a ROM you may be using.
More detail would be helpful:good:
For me it happend on stock and rooted with aospa... Dont know What can cause this. I Sent it to my Carrier they found nothing....
Gesendet von meinem LG-D802 mit Tapatalk
running stock myself. Technician was useless and told me nothing.
DrZeuss said:
running stock myself. Technician was useless and told me nothing.
Click to expand...
Click to collapse
Same here
Gesendet von meinem LG-D802 mit Tapatalk
Did you try the Stop Having Sprint fix?
Sent from my LG-D800 using XDA Premium 4 mobile app
I got the d802...
Gesendet von meinem LG-D802 mit Tapatalk
Burkettacb said:
Okay. So after hours of tapping. Which might i add. My fingers hurt, I am now able to activate the screen. Pausing after each tap, using my finger print area to tap "not to be confused with finger tip". The screen will activate. Also note, the standard two taps works sometimes, but with four presses, i seem to get the best results. Give it a try people. I have a theory the hardware has not failed. But yet, the changed. Either due to a conflicting app install. A intermittent system glitch etc
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
I had given up on knock on but tis actually works. (not 100%) but it actually turns it on. WOW
Is there a way to adjust the "activation area pixel size value"?
ingoljosh said:
I had given up on knock on but tis actually works. (not 100%) but it actually turns it on. WOW
Is there a way to adjust the "activation area pixel size value"?
Click to expand...
Click to collapse
This^. For me I have to use my entire thumb or even palm, but it occasionally works.(still like 1/30 tries). This leads me to believe that it is software related. This one issue is killing me. I hate using the power button on the back so I only used knock on. Now that it's not working I'm hating this phone. Knock off works great and I know knock on is kernel based so maybe someone can create a kernel that fixes this issue.
This did work for me. Fixed the knock on feature on my D802.
Credit: Smith I Run (Thread from android central. Can't post link to thread)
There is a solution; (not sure about it, my friend had the same problem and he fixed it with this method)
Open dialer menu and type;
5689#*980# (Sprint)
3845#*801# (T-Mobile)
3845#*803# (AT&T Canada)
3845#*802# (International)
3845#*800# (At&T)
3845#*980# (Verizon)
And when hidden menu is showed up, go to "Settings"
and go to "Update Touch Firmware".
The touchscreen won't work until after 5 seconds, Wait for it and if touchscreen gets working, exit the menu.
Lock the phone and try knocking on the screen, It should be working :laugh:
Click to expand...
Click to collapse
I was one of the unlucky persons to deal with the dreaded touchscreen problem. When on the 44s build, it sometimes got so bad the phone was almost completely useless. The touch screen problems didn't go away in spite of flashing countless Rome with almost every possible combination of kernels.. But nothing seemed to help. The touchscreen got noticeably worse when the phone got hot..i was almost at the verge of giving up.. But that's when it happened.. The 05Q update solved all of my touchscreen problems. I've checked with touch Explorer and even multi touch works flawlessly.. I understand that this problem was identified as a grounding defect.. And I did buy it.. But since the 05Q update seems to have completely solved this issue, my faith in oneplus has been restored.. Did anyone else notice this? What could be the reason?
Nothing's changed for me :c
Sent via Telnet
I never used to have problems with the touchscreen, but since update, the double tap to wake sometimes doesn't work.
It's really annoying to have to try it several times when you want to check the phone. (I already got used to not using physical buttons).
Anyone else with this issue?
alexbo said:
I never used to have problems with the touchscreen, but since update, the double tap to wake sometimes doesn't work.
It's really annoying to have to try it several times when you want to check the phone. (I already got used to not using physical buttons).
Anyone else with this issue?
Click to expand...
Click to collapse
For me, it got better. I would have terrible touchscreen problems.. I wouldnt be able to wake the device via D2W and mostly resorted to the wake up button.. but ever since the update, the battery's been a little bit on the downside..but the touchscreen problems have been completely eliminated and i'm okay with the tradeoff.. I just dont understand how they've managed to fix it if it was a hardware issue? im greatly confused..
my problems
onefanboy3556 said:
For me, it got better. I would have terrible touchscreen problems.. I wouldnt be able to wake the device via D2W and mostly resorted to the wake up button.. but ever since the update, the battery's been a little bit on the downside..but the touchscreen problems have been completely eliminated and i'm okay with the tradeoff.. I just dont understand how they've managed to fix it if it was a hardware issue? im greatly confused..
Click to expand...
Click to collapse
I've been facing touch issues after this update. The double tap is working hardly and even the top middle dot of the pattern lock seems unresponsive or experiencing ghost touches
Anyone have similar problems or with possible solutions ? Also for heavy battery drain
alexbo said:
I never used to have problems with the touchscreen, but since update, the double tap to wake sometimes doesn't work.
It's really annoying to have to try it several times when you want to check the phone. (I already got used to not using physical buttons).
Anyone else with this issue?
Click to expand...
Click to collapse
I'm having some issues too with this! Sometimes, even the physical power button doesn't work and I have to press it multiple times!
I m also facing same issue
Any solutions to resolve this issue?
Glad to hear it is better for you. Unfortunately, I still am experiencing ghost touches... Double tap on the other hand is fine.
For those who are still having touchscreen issues.
I wasn't having any issues at 44S. OTA update to 05Q and I immediately noticed issues with 'fast typing'. None of the hacks online worked ex. cat some touch-screen related system file..
Looks like 05Q is legitimately slower performance-wise and at least to me the keyboard is unusable.
Anyway, I spent quite a bit of time on this. Updated to a CM12 nightly and it's gotten a lot better although the issue is still there although less noticeable. Just try typing 'this' quickly. I get a swipe gesture activated once in a while (vs pretty much 90% of the time on 05Q).
02/23 Nightly CM seems very stable and clean. Very usable
kewlstuffdudez said:
For those who are still having touchscreen issues.
I wasn't having any issues at 44S. OTA update to 05Q and I immediately noticed issues with 'fast typing'. None of the hacks online worked ex. cat some touch-screen related system file..
Looks like 05Q is legitimately slower performance-wise and at least to me the keyboard is unusable.
Anyway, I spent quite a bit of time on this. Updated to a CM12 nightly and it's gotten a lot better although the issue is still there although less noticeable. Just try typing 'this' quickly. I get a swipe gesture activated once in a while (vs pretty much 90% of the time on 05Q).
02/23 Nightly CM seems very stable and clean. Very usable
Click to expand...
Click to collapse
From my experience I could say that these 'gost touches' are related to a system slowness more than a touch problem. Sometime I feel I could type fast without any problem, sometime I had to type very slow. Also this is rom related. Some are really snappy others not so. Another thing to mention is that keyboard feels better after a reboot, so maybe a memory leak!?
Inviato dal mio A0001 utilizzando Tapatalk
I just hope it's not the hardware touchscreen / sensor. My observations are consistent with everything you mentioned above. Memory leak feels possible or some unoptimized code. I don't see any issue in ex Chrome. It's mostly Hangouts app that's super slow so perhaps Google also pushed some update to Hangouts that slowed things down enough to be noticeable.
anuradha1208 said:
The double tap is working hardly and even the top middle dot of the pattern lock seems unresponsive or experiencing ghost touches
Click to expand...
Click to collapse
Yup, definitely noticed DTTP is not working as well on 05Q vs. 44S.
Steelpapi said:
Sometimes, even the physical power button doesn't work and I have to press it multiple times!
Click to expand...
Click to collapse
Yes, same here!
kewlstuffdudez said:
I wasn't having any issues at 44S. OTA update to 05Q and I immediately noticed issues with 'fast typing'. None of the hacks online worked ex. cat some touch-screen related system file..
Click to expand...
Click to collapse
Same here - things were perfect on 44S, but screen has just turned to crap on 05Q!
Did you try going back to 44S, or did you just go straight to CM12 nightlies?
Cheers,
Su
I went straighten to CM12 nighties. The touchscreen issues still does up but not as much. Makes me think is a hardware issue with the touchscreen independent of firmware perhaps just didn't notice before. When I went to CM12 I did a full wipe, so everything from scratch
Sumanji said:
Yup, definitely noticed DTTP is not working as well on 05Q vs. 44S.
Yes, same here!
Same here - things were perfect on 44S, but screen has just turned to crap on 05Q!
Did you try going back to 44S, or did you just go straight to CM12 nightlies?
Cheers,
Su
Click to expand...
Click to collapse
I think I may have found a solution! Recently I enable the touchscreen buttons, but yesterday I disabled the quick launch shortcuts and it seems to be working.
Go to DEVICE - Buttons and disable it there!
Hope that helps!
I have not faced touch screen issue.
Even i have broken my display from top..
Sent from my A0001 using XDA Free mobile app
Steelpapi said:
I think I may have found a solution! Recently I enable the touchscreen buttons, but yesterday I disabled the quick launch shortcuts and it seems to be working.
Go to DEVICE - Buttons and disable it there!
Hope that helps!
Click to expand...
Click to collapse
Hey,
Which touchscreen buttons do you mean?
I made a short video showing the problem using a multi-touch test app. Basically if I have two or more touch points that are horizontally near each other, the screen totally flips out!
Thanks,
Su
A thread i created in the oneplus one forum after a bit of research from my side
https://forums.oneplus.net/threads/major-touch-screen-issue.282231/
Sumanji said:
Hey,
Which touchscreen buttons do you mean?
I made a short video showing the problem using a multi-touch test app. Basically if I have two or more touch points that are horizontally near each other, the screen totally flips out!
Thanks,
Su
Click to expand...
Click to collapse
Crazy stuff.. Looking at the video, I have almost bought that it's a software problem..
Mine works fine if and only if you turn off all those double tap settings (wake/sleep) and turn off ambient display.
I've gone through all the settings menus and turned off everything gesture or touch related... also switched to onscreen buttons.
Still have the same problem
I emailed support to arrange an RMA, but they want me to wait for Lollipop... WTF?
Double tap to wake is the feature I almost explicitly use to wakeup my phone to look at the notifications, especially so in Zuk Z, which has this crazy fast fingerprint scanner.
Lately, it stopped to work. I was trying to figure out the latest changes I did in my phone and I couldn't think of anything but the last CyanogenOS OTA update (YOG4PAS3OH) but it might be just coincidental. I have done quite a bit of troubleshooting, involving (but not limited to) disabling/enabling the feature, removing proximity sensor check, rebooting, etc but haven't done factory reset (which I'd be very reluctant to do anyway). Double tap to sleep is working fine though.
Few questions for folks here:
1. Is it working for you after the latest OTA?
2. Could this a hardware issue?
3. Any suggestions for me to try and make this work again?
Thank you!
malikons said:
Double tap to wake is the feature I almost explicitly use to wakeup my phone to look at the notifications, especially so in Zuk Z, which has this crazy fast fingerprint scanner.
Lately, it stopped to work. I was trying to figure out the latest changes I did in my phone and I couldn't think of anything but the last CyanogenOS OTA update (YOG4PAS3OH) but it might be just coincidental. I have done quite a bit of troubleshooting, involving (but not limited to) disabling/enabling the feature, removing proximity sensor check, rebooting, etc but haven't done factory reset (which I'd be very reluctant to do anyway). Double tap to sleep is working fine though.
Few questions for folks here:
1. Is it working for you after the latest OTA?
2. Could this a hardware issue?
3. Any suggestions for me to try and make this work again?
Thank you!
Click to expand...
Click to collapse
1. if by "the latest OTA" you mean cm-12.1-YOG4PAS3AJ (About phone: Kernel version 3.4.0-cyanogenmod-gef06bf8), then that is what I have, and double tap is working just fine.
2. although i am no engineer nor software developer, i feel i could say with fair confidence it is definitely a software issue. why? because i have used custom kernels that added such a feature to phones that didn't come with it.
3. you can try disabling Display & lights | Prevent accidental wake-up; use a task manager or Apps to look at your running processes and stop any that shouldn't be running then try again.
Thanks for the reply. If you read my post again, you'll see that I've provided the name of the OTA that I was referring to. It's not the one you have, and now I'm curious which one is the latest and why are we on different versions. Can you go check for any pending updates for your phone ?
I also believe that it's software related . I've tried quite a few things and nothing seem to be helping resolve this issue so far. Changed settings, remove some apps i lately installed, etc but no luck. I guess I'll do a factory reset and see if that takes care if this issue.
Sent from my ONE A2003 using Tapatalk
Im on 3OH. Double tap to wake wasn't working straight after the update, but i did some fiddling like turning it on and off, played with settings and after a reboot it was working again.
Thank you sir. You just gave me a huge hope. I'll keep playing and will hopefully make it to work. Cheers,
Sent from my ONE A2003 using Tapatalk
malikons said:
Thanks for the reply. If you read my post again, you'll see that I've provided the name of the OTA that I was referring to. It's not the one you have, and now I'm curious which one is the latest and why are we on different versions. Can you go check for any pending updates for your phone ?
I also believe that it's software related . I've tried quite a few things and nothing seem to be helping resolve this issue so far. Changed settings, remove some apps i lately installed, etc but no luck. I guess I'll do a factory reset and see if that takes care if this issue.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
indeed you have (supplied your version no.), please excuse my oversight.
yours would appear to be newer than mine and, no, just checked & not available for me yet. sorry i can't be of help. hope someone else could. cheers.
I'm on 3OH and it works for me
After power on or reboot, go to settings-display, disable DTTS, turn off the screen with power button, turn on the screen, enable DTTS and now the DTTS will work until next reboot or power off. This is the way I manage to make it works. I hope Cyanogen will solve this bug in next build.
I have also problems with double tap, happened already 2 times in 5 days, reboot solves the problem...
Not sure what I did but the double tap to wake feature has started to work again. I messed around quite a bit with the settings and also rebooted the phone a few times. Although, the response is quite slow, like there is some lag between double tap and when the screen wakes up. It seems to be improving in response time as I play with it more, not sure if its psychological though . Hopefully cyanogen guys will take care of it in the future update.
Stopped working for me too! Seems since the last 2 updates things have gotten bad! If it ain't broke, why fix it?
Sent from my Z1 using Tapatalk
Double tap to wake is working again! I think my phone has a mind of it's own lol!
Sent from my Z1 using Tapatalk
Mine has been behaving much better now. I'm seriously considering cyanogenmod . I think it'll be a lot better than COS.
Sent from my ONE A2003 using Tapatalk
Double tap to wake has stopped working again! Bloody updates.
Sent from my Z1 using Tapatalk
Keep playing with the settings and it'll start to work again
Sent from my ONE A2003 using Tapatalk
Lol! Thanks will try that but shouldn't have to.
Sent from my Z1 using Tapatalk
---------- Post added at 05:58 PM ---------- Previous post was at 05:56 PM ----------
malikons said:
Keep playing with the settings and it'll start to work again
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Thanks it worked! Lol
Sent from my Z1 using Tapatalk
Agree , we shouldn't have to but this phone isn't very stable at the moment. Sometimes I wonder why I'm even using it there's something in this phone I really like though and I believe in cyanogen
My phone was perfect when I bought it. The problem started with the countless updates I've had since then.
Sent from my Z1 using Tapatalk
malikons said:
Mine has been behaving much better now. I'm seriously considering cyanogenmod . I think it'll be a lot better than COS.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
It also happens with CM nightlies
Thank you for saving me a lot of time and frustration