If I install a CM, will this useful function remain? Or it works only with stock ROM?
I have the same problem on Cyanogenmod 11
I turn on option "Double-tap to sleep" on "Status bar" but it not work.
Knock On is part of LG Ui software, will not work on CM. There are alternatives that perform the same function. Look for them in the CM forums for your CM rom.
knock on work on CM11
knock off, only work if u double tap on the status bar itself, not on other part of the screen
idk if anyone else is having problems with the proximity sensor with phone calls can not get the screen to come back on till caller on other line disconnects model number vs9800 running cyanfox 4.4
hi, i'm looking for a stable rom (even stock) with double tap to wake, the power button is almost dead, and it's my mom phone, actually i'm using cm13 with quanta tweaks, but sometimes i have issue, like double tap not working on boot or touch freezing in the lockscreen, do you know a stable rom/kernel with this function? thanks
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.
Has anybody figured out how you "unpin" a "pinned" app when you are using the one button nav fingerprint gestures? Normally you would hold the Back and Overview buttons, but with one button navigation, these are occulted. When I have pinned an app I have had to restart the phone.
P.S. I am using Lineage 14.1 but I suspect that the answer to this problem (if there is one) would be the same for stock.
My Moto G5+ is running stock rom and I have one button nav on.
When I try to pin an app the navigation bar appears and then I am able to get back to the normal situation by holding Back and Overview. So the problem is on LineageOS I reckon.
Simon761 said:
My Moto G5+ is running stock rom and I have one button nav on.
When I try to pin an app the navigation bar appears and then I am able to get back to the normal situation by holding Back and Overview. So the problem is on LineageOS I reckon.
Click to expand...
Click to collapse
Thanks it is also a problem on Resurrection Remix. The navigation doesn't appear. When the screen is pinned. So you have to reboot.
Hello,
I recently switched from an old lineageOS rom to the latest resurrection remix rom because I wanted new features (and mostly because I messed up big time and had to factory reset my phone).
Unfortunately, every time I brush past the home button the phone interprets it as an input and acts as if I pressed it. (I believe it is called u-touch but I dont know if u-touch encompasses other functions as well).
Apparently I am in the minority for preferring to physically press the button as I could only find fixes to activate it, and resurrection remix doesn't seem to have an option to turn it off.
Is there a way to deactivate the capacitive touch on resurrection remix without disabling the fingerprint sensor? And if not, are there mods that have this option or should I just go back to lineageOS (unless they added that too)?
For me, the best rom would be the one with the most features and control over the device (also battery life and stability, but I understand those things are hard to mesure).
Thank you for your help