Related
PROBLEM
After flashing to AOSP 6 I have problems with waking the screen up.
1. After or during the call
2. After longer sleep
It can take up to a minute to wake up. Usualy around 10-20 seconds after multiple presses (single press can sometimes doesn't wake the phone).
NO PROBLEMS WHEN:
1. I manualy sleep the screen, and press power again after a moment - I can bring it to a wake up state without any problems.
2. If the phone is connected through USB - there is also no problem to instantly bring the wakeup screen.
3. There is also no problem to bring the wakeup screen with adb
Code:
adb shell input keyevent 26
I was expecting it to be some sort of sensor problem, as it persists to other roms, even coming back to 5.1.1 which previously worked flawlessly in this department.
I've tried this: http://forum.xda-developers.com/opt...mpting-to-fix-broken-sensors-mm-e975-t3297566 without any results. I've also tried restoring factory settings.
Any ideas?
ZPZG said:
PROBLEM
I was expecting it to be some sort of sensor problem, as it persists to other roms, even coming back to 5.1.1 which previously worked flawlessly in this department.
Click to expand...
Click to collapse
What does CPU-Z think of your sensor data? it's being represented correctly?
blackbird5308 said:
What does CPU-Z think of your sensor data? it's being represented correctly?
Click to expand...
Click to collapse
The sensor as far as I know is binary, so either something is in proximity or not, and as that it works correctly under any system.
After reverting to stock 4.4.2 the problem does not appear.
Installing AOSP 6 again - the problem returns.
ZPZG said:
The sensor as far as I know is binary, so either something is in proximity or not, and as that it works correctly under any system.
After reverting to stock 4.4.2 the problem does not appear.
Installing AOSP 6 again - the problem returns.
Click to expand...
Click to collapse
well, i don't really know, my proximity sensor has been working well since first time i went 6.0 AOSP, even when no other sensor was working at all
blackbird5308 said:
well, i don't really know, my proximity sensor has been working well since first time i went 6.0 AOSP, even when no other sensor was working at all
Click to expand...
Click to collapse
Honestly I don't know what is the problem, but in every thread concerning wakup issues and E975 the sensors are blamed. The physical sensor is working properly as I am not having any problems running stock 4.4.2.
Haven't really found much about this issue but sometimes this gesture doesn't work, even after just barely putting the device to sleep. All the other gestures(flashlight, camera,music) work perfectly but the wake feature is hit or miss kinda thing.
Can amplify or something similar cause this issue?
Yes, same thing happened to me sometimes. Usually happens when I holding the phone on my hand or just pull it out of pocket, probably it's because the Pocket Mode turned on.
You can "force"-enable that feature into the kernel using for example Kernel Adiutor. It fixed the problem for me.
I also experience this issue when I take out the phone from my pocket. In this case, I need to do the double tap around three times to get it working. But in every other cases it is working without any issues.
Maybe we should report it on OP Bug report.
néonaloj said:
You can "force"-enable that feature into the kernel using for example Kernel Adiutor. It fixed the problem for me.
Click to expand...
Click to collapse
How do you happen to do that? I'm a complete noob when it comes to messing with the kernel
Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?
gt-kingz said:
Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?
Click to expand...
Click to collapse
You most likely got a bad part. OEM like One plus and xioami are known for using something called product binning. Which means their parts have a higher failure rate then other oems. They also dont make extra parts really so what you got was most likely just a generic screen like you can buy at any shop in China.
Nothing you can really do about it except try a different screen but to be honest I would get a different device and this time dont skip on the price. You get what you pay for and when a good device is cheap there is always a reason. (why do you think most of the owners and mods of XDA run Iphones as their daily drivers and leave android for a hobby)
gt-kingz said:
Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?
Click to expand...
Click to collapse
As an experiment, try stock OOS and see whether the issue goes away.
i too have this problem cant find any solution anywhere been trying for about a week now arrggghh
ireaper4592 said:
i too have this problem cant find any solution anywhere been trying for about a week now arrggghh
Click to expand...
Click to collapse
tnsmani said:
As an experiment, try stock OOS and see whether the issue goes away.
Click to expand...
Click to collapse
Hey there again. I know my answer is kinda late but I wanted to share my experience. So I tried like 10 different custom ROMs with different Android version. The problem got even worse sometimes.
Anyway a few days ago I installed stock OOS and the problem is fixed now. I could not believe at first, but after excessive testing I am 100% sure now.
Anyone can tell why? Is the stock display driver proprietary?
TBH I always used to use custom ROMs (mostly CyanogenMod and now Lineage. Now on stock rom O feel like everything is better than ever before. Battery life, performance. Some features even offer more customization than custom ROMs.
I always thought the opposite is the case since custom roms advertise things like this. I will definitely stick with stock rom for now!
gt-kingz said:
Hey there again. I know my answer is kinda late but I wanted to share my experience. So I tried like 10 different custom ROMs with different Android version. The problem got even worse sometimes.
Anyway a few days ago I installed stock OOS and the problem is fixed now. I could not believe at first, but after excessive testing I am 100% sure now.
Anyone can tell why? Is the stock display driver proprietary?
TBH I always used to use custom ROMs (mostly CyanogenMod and now Lineage. Now on stock rom O feel like everything is better than ever before. Battery life, performance. Some features even offer more customization than custom ROMs.
I always thought the opposite is the case since custom roms advertise things like this. I will definitely stick with stock rom for now!
Click to expand...
Click to collapse
Thanks for the confirmation. The cheaper screens seem to have an issue which is not faced by the costlier ones. I have found while roaming the threads that sometimes flashing OOS helps. May be a driver issue.
My understanding from what I've read, third party displays needed kernel support.
I paid OP to replace mine - no problems.
Hi!
I'm having a similar issue with my Oneplus 5. Had my screen replaced (new one: OEM) and now it doesn't wake up most of the time either using power button or double tap or fingerprint scanner. I tried everything that I read on forums but nothing worked. Now I seem to have found a solution that I haven't read anywhere yet: I turned off night mode and now it's working as it should. Actually, whenever I want to use any screen adjustment feature like night mode, reading mode etc the screen doesn't wake up. But if I keep the default settings, there is no problem. The issue is definitely the new screen because before that I used night mode all the time (I mean after dark). Now I'm still thinking if I should return the phone to the repair shop and ask for another screen (they offer one year warranty after the repair) or just deal with it... I mean these OEM screen are cheap for a reason (as someone had written here before) and there is no guarantee that the next one will be good, and I don't feel like waiting weeks again for an uncertain outcome, also I can live without said features (gonna miss night mode tho'). Any suggestion? Should I give it a try? Maybe the repair shop made a mistake during assembly? Anyway, I hope this comment will be helpful for those lurking for a solution for a similar problem.
csabatoro said:
Hi!
I'm having a similar issue with my Oneplus 5. Had my screen replaced (new one: OEM) and now it doesn't wake up most of the time either using power button or double tap or fingerprint scanner. I tried everything that I read on forums but nothing worked. Now I seem to have found a solution that I haven't read anywhere yet: I turned off night mode and now it's working as it should. Actually, whenever I want to use any screen adjustment feature like night mode, reading mode etc the screen doesn't wake up. But if I keep the default settings, there is no problem. The issue is definitely the new screen because before that I used night mode all the time (I mean after dark). Now I'm still thinking if I should return the phone to the repair shop and ask for another screen (they offer one year warranty after the repair) or just deal with it... I mean these OEM screen are cheap for a reason (as someone had written here before) and there is no guarantee that the next one will be good, and I don't feel like waiting weeks again for an uncertain outcome, also I can live without said features (gonna miss night mode tho'). Any suggestion? Should I give it a try? Maybe the repair shop made a mistake during assembly? Anyway, I hope this comment will be helpful for those lurking for a solution for a similar problem.
Click to expand...
Click to collapse
Did you try OOS?
OEM screen is not cheap (atleast compared to what is offerred online).
May be you are better off with what you have since you have found a work around. Who knows what you will get next time?
Yea I have same problem it works totally fine on oos but on custom roms it is ****ed up
skymera said:
My understanding from what I've read, third party displays needed kernel support.
I paid OP to replace mine - no problems.
Click to expand...
Click to collapse
How much plz?
Shreeram02 said:
Yea I have same problem it works totally fine on oos but on custom roms it is ****ed up
Click to expand...
Click to collapse
Thank you also for confirming that on OOS there is no issue. Looks like the cheaper of the online replacements have this issue while the costlier ones don't.
Funniest thing is I have a slim ROM backup on 7.1. and that works fine so like what the f--- any ideas people?
gt-kingz said:
Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?
Click to expand...
Click to collapse
Yes, I have the same issue and I wanted to revert back to Stock OOS, but I just tried Caesium latest kernel, and the display wakeup issue seems to have gone. I'm using Havoc OS 2.3 based on Android Pie.
Guys the latest mad kernal reborn it wakes up all the time
At least for my screen
It used to be worse on all the other kernals
Finally found a solution
I had same problem on custom roms after replacement of display of my oneplus3...i was on oos 5.0.8 i had no issues in that but am a custom rom user and now the solution is flash any rom clean flash not dirty flash and flash gapps then flash any module if you want like magisk and then reboot setup the device and after first boot flash mcd custom kernel and yippeee enjoy... Present am on havoc os with no issues... Try and let me know...
Mohammed Raihan said:
I had same problem on custom roms after replacement of display of my oneplus3...i was on oos 5.0.8 i had no issues in that but am a custom rom user and now the solution is flash any rom clean flash not dirty flash and flash gapps then flash any module if you want like magisk and then reboot setup the device and after first boot flash mcd custom kernel and yippeee enjoy... Present am on havoc os with no issues... Try and let me know...
Click to expand...
Click to collapse
post link to one u have plz
Mail me i have that file..
[email protected]
There is issue while sending here
Mohammed Raihan said:
[email protected]
There is issue while sending here
Click to expand...
Click to collapse
got anyway working fine cheers dude
Even i have the same problem as mentioned above..even i changed my oneplus 3 display
I always prefer custom roms..but screen wakeup issue had made my phone worse...then i tried oos 5.0.8 and it works like a charm...yeah i know its very old android version but no other option though...
Others who have same problem and have no issues going back to oos oreo then go for it...your problem is solved..
---------- Post added at 01:47 PM ---------- Previous post was at 01:43 PM ----------
ireaper4592 said:
got anyway working fine cheers dude
Click to expand...
Click to collapse
Is this kernel working for you!??
I have encountered this bug where I'm unable to use ambient display or wake up the display without the use of power button. Everytime I lock the screen it becomes unresponsive even the quick gestures don't work.
I have performed a soft reset but the problem has persisted.
Many other users seem to be suffering from this issue.
My device is full stock, no root or 3rd party apps on it.
Can anyone help me this this issue?
All users are facing this... It's because of battery optimisation.
No issues here. I am able to use the gestures just fine. Even the tap to wake and pick up to wake is working fine. I am 10.0.3 build.
I'm also having issues on tap to wake.
Happens to everyone. It's a hit or miss. Battery optimization makes the phone go into deep sleep and cause this issue is what i too understand.
Ya i did happen couple of times for me hope this bug get ironed out soon.
Sent from my HD1901 using Tapatalk
Same issue here also
Started encountering the issue recently - 3 days into ownership of the phone ?
The only peculiar thing I can remember is changing the override force dark toggle yesterday. And now that I recall, I don't remember seeing the ambient display since then. ?
Confirming I also have this issue. Very frustrating
I can trigger a black screen by holding the phone in landscape and launching the stock camera app. Then I have to hold Vol+/- and Power to reboot and it works again.
Hi guys. Found a fix on the OnePlus forum. Give it a try!
https://forums.oneplus.com/threads/fix-oneplus-7t-ambient-display-not-working.1128194/
i am also facing the same issue, where the tap on wake is not working when not using it for like 2hrs.
piyush.bhandari said:
Hi guys. Found a fix on the OnePlus forum. Give it a try!
https://forums.oneplus.com/threads/fix-oneplus-7t-ambient-display-not-working.1128194/
Click to expand...
Click to collapse
This worked for me at the first attempt . Thanks for the solution.
charan_55 said:
i am also facing the same issue, where the tap on wake is not working when not using it for like 2hrs.
Click to expand...
Click to collapse
Wow! A use for my work-issued iPhone! Yay, seems like its working.
Dt2w works fine for the first few minutes after locking phone but after that, it requires 7-8 taps to wake up. Anyone else experiencing this? Im using xiaomi.eu 12.5 stable.
ApexPrime said:
Dt2w works fine for the first few minutes after locking phone but after that, it requires 7-8 taps to wake up. Anyone else experiencing this? Im using xiaomi.eu 12.5 stable.
Click to expand...
Click to collapse
I'm on the weekly and I also have this issue. Not 7-8, but I have to tap twice. Like 2 taps then 2 taps again. Happens sometimes.
all good on ArrowOS, DT2W and sleep working great... i know it's possibly not what ur looking for... but it's a seriously good rom.
ApexPrime said:
Dt2w works fine for the first few minutes after locking phone but after that, it requires 7-8 taps to wake up. Anyone else experiencing this? Im using xiaomi.eu 12.5 stable.
Click to expand...
Click to collapse
Yes, this happens also for me
I'd assume this would also be an issue on the Global rom?
If so, we can bring it to Poco's attention via Poco community forum.
Otherwise, we'd have to bring it to Xiaomi's attention on the Mi community forum.
I noticed this too but for me it’s the very slight movement between taps where it presumes a gesture is upcoming. It also seems a little worse with a slippery tempered glass protector.
If I make a conscious effort not to move position between taps it works for me every time. Maybe they can adjust swipe detection sensitivity?
festor said:
I noticed this too but for me it’s the very slight movement between taps where it presumes a gesture is upcoming. It also seems a little worse with a slippery tempered glass protector.
If I make a conscious effort not to move position between taps it works for me every time. Maybe they can adjust swipe detection sensitivity?
Click to expand...
Click to collapse
this any good? or there's others if you search playstore....
this one maybe
(as a possible temporary solution, i mean)
EDIT: sorry, i read ur post as a touch sensitivity issue. have re-read, don't think those apps are of much use
Interestingly, don't have problems with double tap to wake, it works always, only with tapping for always on display to quick check time or notifications. Works 1 in 10 times. It's funny, tap, nothing, double tap ok.
Morak75 said:
I'm on the weekly and I also have this issue. Not 7-8, but I have to tap twice. Like 2 taps then 2 taps again. Happens sometimes.
Click to expand...
Click to collapse
same issue
Same issue, probably the biggest annoyance for me since I'm almost unable to use 10 second AOD tapping to conserve standby power.
Any power management active?... destroyer of worlds.
Try clearing system cache, and a hard reboot.
Try altering AOD settings or clearing apk data.
Maybe a firmware glitch... they happen.
blackhawk said:
Any power management active?... destroyer of worlds.
Try clearing system cache, and a hard reboot.
Try altering AOD settings or clearing apk data.
Maybe a firmware glitch... they happen.
Click to expand...
Click to collapse
Already done this to fix my drain problem one day one of receiving the device.
I know Android is just like any other OS installed on a computer sometimes needs clearing of cache, a shutdown of the OS or a manual reboot.
In fact I've done it many times just to make sure MIUI is not glitching on me.
Nemix77 said:
Already done this to fix my drain problem one day one of receiving the device.
I know Android is just like any other OS installed on a computer sometimes needs clearing of cache, a shutdown of the OS or a manual reboot.
In fact I've done it many times just to make sure MIUI is not glitching on me.
Click to expand...
Click to collapse
You be amazed how many have no clue or just don't think using of it.
It may be a settings glitch or again some sort of power management running amuck in the background. Play with it...
I posted the issue on Mi Community and Poco Community forum.
Not many people seem to use the double tab to wake feature with AOD set to 10 seconds.
I tried searching on Xiaomi and Poco both forums with keyword double tap and not a single thread for the Poco F3/Redmi K40.
festor said:
I noticed this too but for me it’s the very slight movement between taps where it presumes a gesture is upcoming. It also seems a little worse with a slippery tempered glass protector.
If I make a conscious effort not to move position between taps it works for me every time. Maybe they can adjust swipe detection sensitivity?
Click to expand...
Click to collapse
I think youre right bro. If i time my taps perfectly and dont move position between taps, it works most of the time. Same goes for the AOD. Single tap works but it takes almost 2 seconds for the AOD to pop up which is pretty slow imo.
I think figured it out, 3 fast taps without moving my finger always works with AOD now.
Whatever, I'll just leave the posts on the Mi and Poco forum...hopefully they can replicate the issue and improve single/double/triple tap detection with future updates.
Nemix77 said:
I think figured it out, 3 fast taps without moving my finger always works with AOD now.
Whatever, I'll just leave the posts on the Mi and Poco forum...hopefully they can replicate the issue and improve single/double/triple tap detection with future updates.
Click to expand...
Click to collapse
Bro did you try single tapping and waiting for ~2 seconds?
Everything magically works now, after I let the battery deplete to 0% (MIUI auto shutdown) for a second time and then charge to 100% (for initial battery calibration).
Of course I won't be letting the battery deplete past 20% anymore after this, and I'll only be charging up to 90% when I have the phone rooted.
I'm pretty sure there some other minor issues with MIUI I haven't encountered yet, but for now it's pretty enjoyable to use.
Nemix77 said:
Everything magically works now, after I let the battery deplete to 0% (MIUI auto shutdown) for a second time and then charge to 100% (for initial battery calibration).
Of course I won't be letting the battery deplete past 20% anymore after this, and I'll only be charging up to 90% when I have the phone rooted.
I'm pretty sure there some other minor issues with MIUI I haven't encountered yet, but for now it's pretty enjoyable to use.
Click to expand...
Click to collapse
One question, double tap to wake drains battery on Amoled screens? read somewhere that it was a function for LCD displays
colosocool said:
One question, double tap to wake drains battery on Amoled screens? read somewhere that it was a function for LCD displays
Click to expand...
Click to collapse
Might depend on the device. Doesn't use much at all on my Samsung Note 10+.
With AOD touch to view active and phone/text running I use less than .5% @HR.
Never tried deactivating Double Tap on though... it's too useful.
More than likely it's not the culprit. Cloud apps and trashware like WhatsApp, FB, Google system apks are prime suspects.
Easy enough to test...