Aosp extended 5.6
Pixel experience
Miracledroid
All these roms "long press power button to light torch" is not working properly. It sometimes work but somtimes not.
Working perfectly at crdroid 4.2, sadly this rom discontinued.
Are there any workaround of this?
Gezine said:
Aosp extended 5.6
Pixel experience
Miracledroid
All these roms "long press power button to light torch" is not working properly. It sometimes work but somtimes not.
Working perfectly at crdroid 4.2, sadly this rom discontinued.
Are there any workaround of this?
Click to expand...
Click to collapse
Flash with power button works ok here, on Mdroid, misses rarely.
Another one with flash light issue.
But in my case Flash light don't work as dual tone.
Related
So the problem is obvious, the option to disable the lights of hardware buttons no longer works after updating to (stock) Gingerbread. It worked well while I was on Froyo btw.
Any suggestions? It really drives me nuts, I love to read at night and button lights really distract me every time I go to the next page.
solarspeed said:
So the problem is obvious, the option to disable the lights of hardware buttons no longer works after updating to (stock) Gingerbread. It worked well while I was on Froyo btw.
Any suggestions? It really drives me nuts, I love to read at night and button lights really distract me every time I go to the next page.
Click to expand...
Click to collapse
+1,good Question
If you're up for a ROM change, genokolar's CM7 works fine with the disabling lights feature of FBReader.
New ROM sounds good, but I also would like know the reason behing this weird behaviour. CM and Gingerbread must be very similar just because CM7 is based on GB, and I believe if CM lets FBReader to control button lights, stock GB too can be tweaked to do the same.
I summon a developer in this thread!
Hi, a bit of a weird problem... When I am getting a incoming call, I can hear my phone ring but nothing is displaying on the screen so I can't answer it. There is no option to answer or reject the call. When the screen is locked it stays locked and when I'm on the home screen it stays on the home screen.
GT-i9505 on stock rooted Lollipop 5.0.1
Anybody with a similar issue or a solution?
This also happens on CM12 roms. I've tried both AntaresOne & Alucard24's optimized CM12.1 builds and the CM12.1 nightlies. Phone used to work fine until about a week ago.
zambeezi said:
This also happens on CM12 roms. I've tried both AntaresOne & Alucard24's optimized CM12.1 builds and the CM12.1 nightlies. Phone used to work fine until about a week ago.
Click to expand...
Click to collapse
The screen doesn't turn on even when pressing home or power button?
GDReaper said:
The screen doesn't turn on even when pressing home or power button?
Click to expand...
Click to collapse
Screen comes on but you have no option to answer/reject the phone call and you have no idea who's calling either as there is no caller ID. You can still luanch other apps while phone is ringing...
Finally! Phone's working fine again :victory:
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.
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
I switched to custom rom and I know longer have a double tap power for flashlight while the phone is off. I miss it. Does anyone have a solution for this, all apps I tried don't work with the screen off.
Thanks
Same here, best feature of miui is double press power to turn on flash at any time. How to get it back on resurrection remix custom ROM?
Yes, found, it, there's an app called TapTap on GitHub that brings this feature back via double tapping the back cover of the phone to turn on the flash on my redmi Note 8, running resurrection remix is custom.