Dt2W Casuing On Call Vibrations - CM13 Based Rom's - OnePlus 2 Q&A, Help & Troubleshooting
There is an issue I have been facing with all CM13 based roms for the OP2. If Dt2W is active it causes sudden vibrations when am on call. To troubleshoot the issue I did the following.
1. Wipe everything except sd card.
2. Flash Rom (Any with CM13 base)
3. Flash Gapps (Tried Open Full and TBO)
4. After first boot set up everything and let the phone settee
5. Make a few calls.
My Observations.
1. The vibrations are not intermittent i.e. they don't happen on every call just few of them.
2. It mainly happens when I am moving and talking eg when I am calling someone and walking. If my hand is still it mostly doesn't happen.
3. NO apps or specific Setup is causing this since I tried to reproduce the issue without any apps or setting changes (just ROM and Gapps)
4. Back in April '16 at some point Dt2W was broken on CM 13 roms the issue seems to have started right after that(I may be mistaken though)
I have spent a lot of time on the custom rom forums but no one seems to mention this as a bug. The reply mostly I got was disable Dt2W and that is really not a solution. It makes me wonder if am the only one facing the issue.
Can anyone who is NOT facing the bug post steps they followed to setup their rom may be I can try and trouble shoot further.
Thanks
AshDroidG said:
There is an issue I have been facing with all CM13 based roms for the OP2. If Dt2W is active it causes sudden vibrations when am on call. To troubleshoot the issue I did the following.
1. Wipe everything except sd card.
2. Flash Rom (Any with CM13 base)
3. Flash Gapps (Tried Open Full and TBO)
4. After first boot set up everything and let the phone settee
5. Make a few calls.
My Observations.
1. The vibrations are not intermittent i.e. they don't happen on every call just few of them.
2. It mainly happens when I am moving and talking eg when I am calling someone and walking. If my hand is still it mostly doesn't happen.
3. NO apps or specific Setup is causing this since I tried to reproduce the issue without any apps or setting changes (just ROM and Gapps)
4. Back in April '16 at some point Dt2W was broken on CM 13 roms the issue seems to have started right after that(I may be mistaken though)
I have spent a lot of time on the custom rom forums but no one seems to mention this as a bug. The reply mostly I got was disable Dt2W and that is really not a solution. It makes me wonder if am the only one facing the issue.
Can anyone who is NOT facing the bug post steps they followed to setup their rom may be I can try and trouble shoot further.
Thanks
Click to expand...
Click to collapse
Just a shot in the dark , did u try enabling prevent accidental wake-up ? Could be possible that when you are on a call you end up tapping the screen to trigger the vibration (Double tap).
When the prevent accidental wake-up is enabled this wont happen.
Hope it helps.
mdaamir1989 said:
Just a shot in the dark , did u try enabling prevent accidental wake-up ? Could be possible that when you are on a call you end up tapping the screen to trigger the vibration (Double tap).
When the prevent accidental wake-up is enabled this wont happen.
Hope it helps.
Click to expand...
Click to collapse
Yup tried that too but still bug persist.
I did flash an AOSP and CAF based rom (Exodus) to test it and found that it does not have the bug (Have to mention that they have disabled vibrations for dt2w meaning when it is active and used to wake the screen there is no vibration) . I think my hunch of something being wrong with CM13 base is correct.
Are you using CM13?
Thnx for replying
AshDroidG said:
Yup tried that too but still bug persist.
I did flash an AOSP and CAF based rom (Exodus) to test it and found that it does not have the bug (Have to mention that they have disabled vibrations for dt2w meaning when it is active and used to wake the screen there is no vibration) . I think my hunch of something being wrong with CM13 base is correct.
Are you using CM13?
Thnx for replying
Click to expand...
Click to collapse
I was , but i am on Exodus now. Maybe the next time i flash CM13 i will try to reproduce the problem.
Sent from my ONE A2003 using XDA-Developers mobile app
mdaamir1989 said:
I was , but i am on Exodus now. Maybe the next time i flash CM13 i will try to reproduce the problem.
Click to expand...
Click to collapse
Sure:good: thank you for your time.
Update
So I went back and flashed OOS to check why these vibrations don't happen on OOS. Turns out this has nothing got to do withe Dt2W or dialer as such. This behavior happens because the Prevent Accidental Wake up disables the Screen Wake up but allows Dt2W inputs. This is what I found
On OOS.
a. Double tap screen normally and you will feel haptic feedback and screen will turn on.
b. Cover the proximity sensor and double tap, the screen will remain off and there will be NO haptic feedback. Which is how prevent accidental wakeup should actually work.
On CM13 Based Roms.
a. Cover the proximity sensor and double tap the screen the screen remain OFF but the phone register's the double tap to wake gesture. Ideally prevent accidental wakeup should not allow the gesture input as well.
This behavior is may be because prevent accidental wake has not been integrated the properly. I say this because when the phone rings and you cover the proximity sensor (Prevent Accidental Wakeup Active) the screen goes off, this is not the correct behavior. The Prevent accidental wake up option should actually ignore proximity sensor when there is a phone call.
As of now I am on RR 5.7.1 and have disabled Vibrate on touch (Meaning even if the gesture happens the phone wont vibrate) I find this a better workaround rather than disabling Dt2W. Disabling Vibrate on touch means no vibrations for button press and long press and stuff like that which is ok with me (this option could also be the reason why some user say they have not felt any vibrations when making calls.)
AshDroidG said:
So I went back and flashed OOS to check why these vibrations don't happen on OOS. Turns out this has nothing got to do withe Dt2W or dialer as such. This behavior happens because the Prevent Accidental Wake up disables the Screen Wake up but allows Dt2W inputs. This is what I found
On OOS.
a. Double tap screen normally and you will feel haptic feedback and screen will turn on.
b. Cover the proximity sensor and double tap, the screen will remain off and there will be NO haptic feedback. Which is how prevent accidental wakeup should actually work.
On CM13 Based Roms.
a. Cover the proximity sensor and double tap the screen the screen remain OFF but the phone register's the double tap to wake gesture. Ideally prevent accidental wakeup should not allow the gesture input as well.
This behavior is may be because prevent accidental wake has not been integrated the properly. I say this because when the phone rings and you cover the proximity sensor (Prevent Accidental Wakeup Active) the screen goes off, this is not the correct behavior. The Prevent accidental wake up option should actually ignore proximity sensor when there is a phone call.
As of now I am on RR 5.7.1 and have disabled Vibrate on touch (Meaning even if the gesture happens the phone wont vibrate) I find this a better workaround rather than disabling Dt2W. Disabling Vibrate on touch means no vibrations for button press and long press and stuff like that which is ok with me (this option could also be the reason why some user say they have not felt any vibrations when making calls.)
Click to expand...
Click to collapse
Actually I face similar issue on cm based Roms , this issue is from day one . Also on OOS , sometimes screen is being pressed and notification bar slides down and buttons are being pressed while on call. Disabling dt2w solves temporarily.
kunalshah912 said:
Actually I face similar issue on cm based Roms , this issue is from day one . Also on OOS , sometimes screen is being pressed and notification bar slides down and buttons are being pressed while on call. Disabling dt2w solves temporarily.
Click to expand...
Click to collapse
Its a problem with CM13 base. So any rom using CM 13 will have this behavior. I believe the people who say they don't face this behavior have disabled vibrate on touch like I have now. I never had an issue with OOS though.
Can you let me know does your screen goes off when ringing on CM 13 (when you cover the proximity sensor with prevent accidental wake enabled)
AshDroidG said:
Its a problem with CM13 base. So any rom using CM 13 will have this behavior. I believe the people who say they don't face this behavior have disabled vibrate on touch like I have now. I never had an issue with OOS though.
Can you let me know does your screen goes off when ringing on CM 13 (when you cover the proximity sensor with prevent accidental wake enabled)
Click to expand...
Click to collapse
i am on OOS , flashing cm13 soon , will let u know.
Related
[Q] Screen won't turn on after a call ends
Hey, I have a weird issue with the proximity sensor. When I answer a call, the screen turns off as usual, however, every now and then the screen won't turn on after the call ends. The phone is still responsive however, and pressing the power button simply gives the lock sound. I'm using CyanogenMod 6.1 Nightly 85 but I'm fairly certain it's happened before on other roms as well. Any ideas?
That Problem I've sometimes too! Dont know to fix it...
[WORKAROUND] Avoid suddenly call drop
Hi guys, since I've updated my Galaxy to ICS I'm often experiencing call drops when I place the phone near the head. I was thinking about a proximity sensor issue, but today I just discovered that disabling the accessibility function "Power button ends call" (Settings->Accessibility), the phone works correctly! So I think there is a bug in most CM9 derived roms, which ends the call when the screen goes off, not just when you press the power button. So I want to share my experience, let me know if unchecking that settings fixes the problem also for you.
Pattern Lock When On Calls
Hi guys Had a search and nobody else seems to be having this problem, but seems so basic that I'm sure I must be missing something obvious! When I'm in a call (either incoming or outgoing) I can't get the screen to turn on properly in order to hang up or use other programs (check calendar etc). This is particularly annoying on outgoing calls as it makes hanging up very difficult! To be more detailed, a single tap on the power button has no effect on the screen - it stays off. If I repeatedly click the power button, sometimes the screen will flash on for a miniscule moment - this is my hang up method at the moment, repeatedly press the power button and tap the screen near where the hang up icon will be, and eventually I'll catch it while the screen's on. Once I'm off a call, things act as normal. I have Pattern Lock set up, and am prompted to unlock the phone once I'm off a call, this is what I'd expect from previous Android phones but might be causing problems here? I found this previous thread where people have had very similar symptoms because their screen protector is over the proximity sensor, but I don't have a screen protector. Might I have a dodgy proximity sensor? Is there any way of testing it? Cheers for the help!
Moved to Q&A Sent from my Nocturnalized One XL using Forum Runner
DJGibbon said: Hi guys Had a search and nobody else seems to be having this problem, but seems so basic that I'm sure I must be missing something obvious! When I'm in a call (either incoming or outgoing) I can't get the screen to turn on properly in order to hang up or use other programs (check calendar etc). This is particularly annoying on outgoing calls as it makes hanging up very difficult! To be more detailed, a single tap on the power button has no effect on the screen - it stays off. If I repeatedly click the power button, sometimes the screen will flash on for a miniscule moment - this is my hang up method at the moment, repeatedly press the power button and tap the screen near where the hang up icon will be, and eventually I'll catch it while the screen's on. Once I'm off a call, things act as normal. I have Pattern Lock set up, and am prompted to unlock the phone once I'm off a call, this is what I'd expect from previous Android phones but might be causing problems here? I found this previous thread where people have had very similar symptoms because their screen protector is over the proximity sensor, but I don't have a screen protector. Might I have a dodgy proximity sensor? Is there any way of testing it? Cheers for the help! Click to expand... Click to collapse I have the same problem. It doesn't happen all the time, naturally, but it's been frequent enough to be irritating. If anyone figures this out, I'd love to hear a solution.
Frustratingly this does seem to happen to me every time - although it might only be once the timeout has activated the pattern lock. Or I could be barking up the wrong tree entirely! Think I might have to do some testing tonight . . .
After some fiddling it does seem that it's a problem with the proximity sensor - Elixir 2's settings show the proximity sensor always showing "near" If someone could run Elixir 2 on their N4 and confirm that they do get changing settings, it would be a great help!
Cannot unlocked ZUK Z1 after ending call with screen off
Hello all, I've been using ZUK Z1 for just about a week now and everything was fine until a couple of days ago when I could not unlock the phone after a call - the power button and the home button turned the screen on for a split of a second and then the screen went off again without reacting to any taps. I had to restart the phone by pressing the power button + the volume down button. I tried to reproduce the issue, but did not succeed. Yesterday, I had the same issue twice and then I finally got it how to reproduce the problem The main condition seems to be ending the call when the screen is off. That can be achieved by holding the phone close to your ear when the call it ended by the other party or ending the call by pressing the power button (you need to turn on that setting beforehand) again while holding the phone close to your ear. Another guy on another forum wrote that had experienced the same issue once and yet another guy mentioned that there was such an issue with Cyanogen on OnePlusOne, but it was fixed in one of the updates. I'm currently on 12.1-YOG4PAS3OH and I'm not sure whether it is a Cyanogen issue alone or an issue caused by interaction of Cyanogen and some of the applications installed. I'm inclined to believe that it's the latter, otherwise there would be a lot of people who ran into the issue. This weekend, if time permits, I'm going to try uninstalling the applications one by one to find out whether any of them contribute the issue, but maybe some of you have already done some investigation or know how fix the issue. I would appreciate your input. Thanks.
Hi there, i am facing the same issue since two days now First i am unable to come up with the physical home button issue and now there is this new issue. The phone does not respond after a call and the screen remains off and does not respond to any touch (double tap) or even the power button and home button pressed. I had to take the mobile into the recovery mode via home buttons power button and volume rockers. Is there any possibility of this getting fixed. I think i made a huge mistake purchasing this phone.. Slowly getting into problems one by one.. First the physical home button issue then this screen off issue. Checking for updates daily but seems like ZUK officials and Cyanogen are sleeping! Highly disappointed!!!!
In the meantime, I uninstalled most of the applications and the issue was still there Then I tried to play with different settings and it seems I have nailed it. After disabling turning on the screen by double tap (I'm not sure how the setting reads in English, I'm using the Russian interface), I cannot longer reproduce the issue. Sydarij, could you, please, check whether the setting is on in your case and, if it is, turn it off and try to reproduce the issue with the screen?
ingtrans said: In the meantime, I uninstalled most of the applications and the issue was still there Then I tried to play with different settings and it seems I have nailed it. After disabling turning on the screen by double tap (I'm not sure how the setting reads in English, I'm using the Russian interface), I cannot longer reproduce the issue. Sydarij, could you, please, check whether the setting is on in your case and, if it is, turn it off and try to reproduce the issue with the screen? Click to expand... Click to collapse Do you mean after turning off the tap to wake option on your ZUK, you are no longer facing such issue?
Sydarij said: Do you mean after turning off the tap to wake option on your ZUK, you are no longer facing such issue? Click to expand... Click to collapse Yes, that's what it seems. With the option turned on I could reproduce the issue (just 1 or 2 tries were needed), while with the option turned off I could not reproduce the issue at all.
ingtrans said: Yes, that's what it seems. With the option turned on I could reproduce the issue (just 1 or 2 tries were needed), while with the option turned off I could not reproduce the issue at all. Click to expand... Click to collapse After turning off this feature, the device unlocks by itself without me waking it up. Turning the feature off doesn't seem to help buddy!
Sydarij said: After turning off this feature, the device unlocks by itself without me waking it up. Turning the feature off doesn't seem to help buddy! Click to expand... Click to collapse This seems to be a different problem. How the option for preventing accidental wake-up is set? (It's just below the double tap option. ) In any case, one owner on another forum complained about the accidental wake-up issue despite the setting was on, but he meddled with the firmware before that...
ingtrans said: This seems to be a different problem. How the option for preventing accidental wake-up is set? (It's just below the double tap option. ) In any case, one owner on another forum complained about the accidental wake-up issue despite the setting was on, but he meddled with the firmware before that... Click to expand... Click to collapse Yes, the accidental wake up is set yet the issue cannot be resolved. Any other way you can resolve this and prevent the issue from reproducing? In my opinion, ZUK and Cyanogen officials are asleep after launching their new flagship. Dont see any updates coming from them since last 2 months. highly disappointed with this!
Sydarij said: Any other way you can resolve this and prevent the issue from reproducing? Click to expand... Click to collapse No idea. The solution I found seems to work well for me, at least I have not had any issues since I applied it.
Please turn on adaptive brightness. Issue will be resolved ingtrans said: Hello all, I've been using ZUK Z1 for just about a week now and everything was fine until a couple of days ago when I could not unlock the phone after a call - the power button and the home button turned the screen on for a split of a second and then the screen went off again without reacting to any taps. I had to restart the phone by pressing the power button + the volume down button. I tried to reproduce the issue, but did not succeed. Yesterday, I had the same issue twice and then I finally got it how to reproduce the problem The main condition seems to be ending the call when the screen is off. That can be achieved by holding the phone close to your ear when the call it ended by the other party or ending the call by pressing the power button (you need to turn on that setting beforehand) again while holding the phone close to your ear. Another guy on another forum wrote that had experienced the same issue once and yet another guy mentioned that there was such an issue with Cyanogen on OnePlusOne, but it was fixed in one of the updates. I'm currently on 12.1-YOG4PAS3OH and I'm not sure whether it is a Cyanogen issue alone or an issue caused by interaction of Cyanogen and some of the applications installed. I'm inclined to believe that it's the latter, otherwise there would be a lot of people who ran into the issue. This weekend, if time permits, I'm going to try uninstalling the applications one by one to find out whether any of them contribute the issue, but maybe some of you have already done some investigation or know how fix the issue. I would appreciate your input. Thanks. Click to expand... Click to collapse
Hi! I'm facing the same issue for the last 3 days. I felt everytime there is any moisture of sweat on the ear piece the phone hangs and doesn't get unlocked. Will try shutting the double tap options. Hope it works! This is the first time I've brought anything in the launch sale without reading reviews. Hope I don't regret this.
sir when call come rintone accor but calling display doesn,t show when i press phone icon in menu then it shows phone is lenovo zuk z1
screen freezes during/after call !! did you solve this problem? i too have posted the same problem here .. any sugesstions?
i am facing a black screen while calling and receiving calls on my zuk z1 .. any solution? and where do i find the proximity setting in my settings?
[Solved] Fingerprint scanner vibrates after screen goes off
Every time I turn the screen off, the phone vibrates 2 times with about 5 seconds delay. I have tracked this vibration down to fingerprint scanner. Its seems to be an indication of it going to sleep. When you turn the screen off, you can place your finger on the scanner and it will wake the screen up. This function is active for few seconds, and then the scanner goes to sleep (signalized by the vibration). Anyone know how to turn this notification off? Or even better, how to disable this whole function entirely so the scanner sleeps immediately after screen goes off? Additional information the Vibration occurs even if you turn the screen on after turning it off but before the vibration (seems irregular though) the time of the vibration changes with the lock time setting turning off notification vibrations entirely helps, but I dont want to do that not using the fingerprint unlock helps too, but I would prefer to keep using it
KowboyBebop said: Every time I turn the screen off, the phone vibrates 2 times with about 5 seconds delay. I have tracked this vibration down to fingerprint scanner. Its seems to be an indication of it going to sleep. When you turn the screen off, you can place your finger on the scanner and it will wake the screen up. This function is active for few seconds, and then the scanner goes to sleep (signalized by the vibration). Anyone know how to turn this notification off? Or even better, how to disable this whole function entirely so the scanner sleeps immediately after screen goes off? Additional information the Vibration occurs even if you turn the screen on after turning it off but before the vibration (seems irregular though) the time of the vibration changes with the lock time setting turning off notification vibrations entirely helps, but I dont want to do that not using the fingerprint unlock helps too, but I would prefer to keep using it Click to expand... Click to collapse Hey. My g928c is runnin on custom rom/kernel. Not sure that could be the same or not but when I turn off the screen, it doesnt wake without pressing home or power button. Maybe you use easyHome app or kind of app which uses fingerprint sensor. My device doesnt wake up after turned the screen off and placing a finger on the scanner or etc. As I remember, easyHome app has got that wake up option but in one of older versions. I hope you solve it..
Oh, I was sure this behavior was caused by the sensor, but now that I actually switched back default locker, it doesnt do it. So the issue is entirely in the Hi Locker I am using. I should have checked that in the first place. So thank you. Now my question changes. Are there any more locker options that use fingerprint scanners other than the default and hi locker?
KowboyBebop said: Oh, I was sure this behavior was caused by the sensor, but now that I actually switched back default locker, it doesnt do it. So the issue is entirely in the Hi Locker I am using. I should have checked that in the first place. So thank you. Now my question changes. Are there any more locker options that use fingerprint scanners other than the default and hi locker? Click to expand... Click to collapse Glad to know you solved it. Im using default lockscreen and never wondered any others lol. Maybe you try{if didnt} Go launcher's go locker etc. Dont know anything more in this case sorry, good luck.
I tried few other alternatives and honestly they were way too cumbersome and bloated. For now I revoked Hi Locker's permission to make notifications, which got rid of the vibration. I hope nothing broke with this modification. Thanks for getting me on track.