Related
This happened to me yesterday and that was completely by mistake. I had the marshmallow update for sometime now and not experienced any major issues other than the random heating (while charging) and some drains at times.
The major issue occurred to me yesterday, when my mutli-window function got disabled by some how and then the phone did not respond to any of my finger touches anywhere on the screen. I have a password lock screen and that too stopped working because the touch response system was not usable. After a struggle for many hours and one sleepless night, the next morning, when I was just thinking of sending the phone to the service center; it just came to my mind and I tried out the SPen and that was working just fine. :victory:
So, using SPen I unlocked my phone and tried to understand what changed. As I normally enable a few functions on my phone, it easily came to my notice that the multi-window function was disabled. So, again using the SPen I enabled it and Voila!! the finger touch started working back.
This is pretty crazy and never experienced this before the marshmallow update.
PS: Even the backlit hard buttons ( left one, home, back right ) had stopped working for me for that instance.
Anyone has any clue on it?
Did you do a reset after the upgrade?
donalgodon said:
Did you do a reset after the upgrade?
Click to expand...
Click to collapse
Yes, as I said the upgrade was not the issue, the issue is disabling "multi-windows" made the phone unusable for sometime till I enabled it back and it started working fine. The issue is something with that "multi-window" on marshmallow update.
I don't intend to go back to older version now.
vaibhavgaikwad said:
Yes, as I said the upgrade was not the issue, the issue is disabling "multi-windows" made the phone unusable for sometime till I enabled it back and it started working fine. The issue is something with that "multi-window" on marshmallow update.
I don't intend to go back to older version now.
Click to expand...
Click to collapse
With all due respect, there's no way to know if the "upgrade was not the issue" unless you actually did a wipe/reset to rule out the crud remaining particularly between major version number leaps.
I tested what you described as the cause of your problem on my wiped/reset device and the problem is not happening for me. Enabling and disabling multi-window causes no issues in my case.
IT might be worth doing a wipe/reset if you haven't. (It's not clear from your response if you have or not done so).
donalgodon said:
With all due respect, there's no way to know if the "upgrade was not the issue" unless you actually did a wipe/reset to rule out the crud remaining particularly between major version number leaps.
I tested what you described as the cause of your problem on my wiped/reset device and the problem is not happening for me. Enabling and disabling multi-window causes no issues in my case.
IT might be worth doing a wipe/reset if you haven't. (It's not clear from your response if you have or not done so).
Click to expand...
Click to collapse
I think I have been more clear and transparent, if you says the multi-window is not an issue then it may be something else which I am not aware of. Though I know that over that particular day nothing new was installed on my phone (so I doubt it can be other software).
Why I am sure its the marshmallow update is because the older version I had tried disabling the mutli-window and the phone worked well, only with the marshmallow update the phone got weird (that too with that multi-window disabled) and enabling the multi-window made it work, so that's my point.
To answer you question on "Did I do a reset", the answer is no I did not, I rebooted (and shut) it couple of times thinking its overloaded but it did not change my situation. Only after I realized that SPen was working fine I could unlock the phone and enable the mutli-window and there after it started responding well to my finger touches too. It's working good today as I write this response. I can once again disable mutli-windows and check if it goes weird again. Let me know if you want me to do that?
Regards.
I recognize that doing a reset can be a pain, but it's probably worth it in the long term. It's up to you, but if it were me, I'd do a reset and start fresh.
When you make major version leaps, the chances of problems increases dramatically over point releases. (i.e. going from 5.x to 6.x is bigger than going from 5.0 to 5.1)
Solution:
Go to Settings (if you're stuck in an app, use the button in your notification panel)
Go to 'System' (try tapping above the broken screen area)
Go to 'About this phone'
That should be all that has to be done! Do note: this fix isn't permanent. Let's hope Nokia fixes this.
Old thread:
Hello all!
When i woke up today and unlocked my phone (while an app is open) the bottom part (starting just above the nav-buttons) of my touchscreen just stops working.
I've had this problem a couple times (at most once per day) since updating from Oreo.
The solution to this problem seems to just to reboot the phone.. (This won't fix it permanently, sadly)
I'm asking if anyone else has this same problem, because i don't know the source of this problem.. (Maybe its because of the app not being P compatible?)
Thanks!
Hi, I have the same problem after the last update (september). Android Pie beta. Almost every morning i have to restart ..
Before the update was enough to just torn off/on the screen .
i don't have this problem on TA-1046 with Pie DP2-DP4.1 or Pie stable... maybe some incompatible apps? you use some for changing NavBar/Gesture area?
although i use XDA NavigationGesture what replace NavBar/Gesture with own, still not having problem, maybe you can try too this replacement, have many more function/settings that stock Pie gesture
for u its bottom touch screen is not working , but for me top of my touch screen isnt working .. and iam facing some serious problems after updating to pie . my phone restarts all of a sudden while charging , app crashes and more , hope hmd fixes this kind of issues in upcoming oct security patch update .
k3dar7 said:
i don't have this problem on TA-1046 with Pie DP2-DP4.1 or Pie stable... maybe some incompatible apps? you use some for changing NavBar/Gesture area?
although i use XDA NavigationGesture what replace NavBar/Gesture with own, still not having problem, maybe you can try too this replacement, have many more function/settings that stock Pie gesture
Click to expand...
Click to collapse
The app i left open last when it happened was "Boost For Reddit"
I'm using the old navbar layout (so no swipe)
dexterboon said:
for u its bottom touch screen is not working , but for me top of my touch screen isnt working .. and iam facing some serious problems after updating to pie . my phone restarts all of a sudden while charging , app crashes and more , hope hmd fixes this kind of issues in upcoming oct security patch update .
Click to expand...
Click to collapse
That's soo weird! I really hope HMD will release a patch soon.. I don't want to downgrade back to oreo
Issue with charging
I am having a charging issue. My phone usb and adapter is working fine with other phones. But when I connect my Nokia 7 Plus below 50%,My phone shows charging And when I tap the screen it doesn't charge. It occurs couple of time. And then It becomes normal and shows rapid charge after 55%. My charging port is fine when I connect it with my Pc usb port. some how the rapid charge doesn't respond. Does anyone have this problem?
Rahul Deshmukh21 said:
I am having a charging issue. [...]
Click to expand...
Click to collapse
What is real time for charge? Rapidcharging is disabled while you activated LCD
Yeah I'm facing similar issues, or did... I'm not sure... but it's been a non-issue for the past ~36 hours now. Here's to hoping it's not an issue any longer. I speculated it might be adaptive battery related somehow, so I tried rebooting my phone just before going to bed Sunday night, but my navbar still worked Monday morning, and this Tuesday it's still working in fact. I did this to test if it stopped working based on time since last reboot, or because some background process being killed due to adaptive battery/doze putting the phone to sleep. But based on my recent experience I think my hypothesis can be rejected. And I'm still not sure what caused it.
STcraft said:
Hello all!
When i woke up today and unlocked my phone (while an app is open) the bottom part (starting just above the nav-buttons) of my touchscreen just stops working.
I've had this problem a couple times (at most once per day) since updating from Oreo.
The solution to this problem seems to just to reboot the phone.. (This won't fix it permanently, sadly)
I'm asking if anyone else has this same problem, because i don't know the source of this problem.. (Maybe its because of the app not being P compatible?)
Thanks!
Click to expand...
Click to collapse
Same for me ta-1046, happened to me twice now. bottom part of screen stops reacting to touch. reboot fixes it.
Hmm... After playing around in the settings while having this problem active, for some reason, going to the phone info section just fixed it... I'm not sure if going there actually did that. needs more testing, I suppose.
+1 I use navigation gestures
STcraft said:
Hmm... After playing around in the settings while having this problem active, for some reason, going to the phone info section just fixed it... I'm not sure if going there actually did that. needs more testing, I suppose.
Click to expand...
Click to collapse
Huh, I'll be damned. When my nav bar was frozen this morning I went into the "about phone" section in the menu, and, lo and behold, my nav bar sprang back to life instantly. Now it might still just be a coincident of course, but it's certainly interesting, and could potentially be a fix where you don't have to reboot.
silverphoenix87 said:
Huh, I'll be damned. When my nav bar was frozen this morning I went into the "about phone" section in the menu, and, lo and behold, my nav bar sprang back to life instantly. Now it might still just be a coincident of course, but it's certainly interesting, and could potentially be a fix where you don't have to reboot.
Click to expand...
Click to collapse
surprised me as well that it worked. He could be a good beta tester. lol
Capture of
I managed to capture a video of the bounds of the touch-registration when the bottom 1,5 centimeter of the screen stops registering.
https://imgur.com/xrRB906
Same problem for me after upgrading a couple of days ago. Bottom of the screen (navbar and a bit more) is not accessible. Always happens after a night charging.
Going to the "About phone" menu fixes it. Thanks!
I have seen reports of people with other phones saying this is due to the setup wizard being active and preventing using the navigation bar. Tried some suggested adb commands without success. I will still try to disable the setup wizard app and report back.
IT ACTUALLY WORKS!!
AssKiRK said:
surprised me as well that it worked. He could be a good beta tester. lol
Click to expand...
Click to collapse
oh thank you! XD
Updated the OP
Please put a comment here as well: https://community.phones.nokia.com/support/discussions/topics/7000036457?page=1
This might help getting a quicker fix from Nokia.
Looks like the recent October patch still has this issue.
Would be nice if i can get a logcat this issue, but given this issue gets triggered after hours of inactivity, it would take a looong time to sift through the log.
Maybe there's a way to trigger it without waiting?
I can try logging when i do the "about phone" fix, will come back to this.
same isue here.. after chsrging at night nav bar bottom inch not responsive.. will try the phone info thing in the morning... is this software related ? will there be a patch??
Hey there everyone,
Yesterday my phone started to have this odd issue where randomly the phone will actually die when I hit the power button to put the phone in standby. There's no errors, lights, or anything to go off... I have already re-formatted the phone, I saw another thread about taking the SD card out (which I've done with no luck) and the Andriod auto reboot setting is not on.
Now here's the kicker... I purchased the phone new from Amazon. However, because the phone is from Hong Kong and I live in Canada. Samsung won't service the phone. I'm not sure what else to do here... Is anyone else having this issue?
dude9946 said:
Hey there everyone,
Yesterday my phone started to have this odd issue where randomly the phone will actually die when I hit the power button to put the phone in standby. There's no errors, lights, or anything to go off... I have already re-formatted the phone, I saw another thread about taking the SD card out (which I've done with no luck) and the Andriod auto reboot setting is not on.
Now here's the kicker... I purchased the phone new from Amazon. However, because the phone is from Hong Kong and I live in Canada. Samsung won't service the phone. I'm not sure what else to do here... Is anyone else having this issue?
Click to expand...
Click to collapse
Can confirm your Problem with random Reboots as you described. Was horrible with last Updates but with CSDE things getting better i guess. I sent Samsung many Times reports with this Problem and they said this will be fixed. So with CSDE i had no reboot so far.
Treasarion said:
Can confirm your Problem with random Reboots as you described. Was horrible with last Updates but with CSDE things getting better i guess. I sent Samsung many Times reports with this Problem and they said this will be fixed. So with CSDE i had no reboot so far.
Click to expand...
Click to collapse
Sorry, whats CSDE? I've also found some articles on Samsung's support page where people are having the same issue... Over there the overwhelming remedy appears to be to disable the Fingerprint Sensor... I have just re-flashed the phone with Odin to see if this fixes anything before disabling the Fingerprint Sensor. I would hate to lose it, but I have no other choice with Samsung's disgusting policy on not fixing their international phones.
I kid you not, Samsung support advised me to board a plane to Hong Kong to visit a center....
Did you boot it?
mine works fine. 1
Disable Fingerprint unlock in settings.
This is an ongoing issue that I've been trying to raise awareness of and is occurring across both S9s and the note 9.
I believe it be a software issue since it began shortly after one UI update, but there are reports that replacing the FP sensor solves the issue.
I have been using my Note 9 without FP unlock for a little over a month now, and once you get used to intelligent scan only, its not that bad. You will still be able to use FP in apps and such without a problem.
Post everywhere you can and lets hope we can attract enough attention for a official Samsung response.
dude9946 said:
Sorry, whats CSDE? I've also found some articles on Samsung's support page where people are having the same issue... Over there the overwhelming remedy appears to be to disable the Fingerprint Sensor... I have just re-flashed the phone with Odin to see if this fixes anything before disabling the Fingerprint Sensor. I would hate to lose it, but I have no other choice with Samsung's disgusting policy on not fixing their international phones.
I kid you not, Samsung support advised me to board a plane to Hong Kong to visit a center....
Click to expand...
Click to collapse
CSDE is the actual Buildstring for our Note 9, means the actual Software Update Mai. That's the first time i heard abbout that issue with the Fingerprintsensor. If this is true, this is a hardly big problem. But as i said so far, with CSDE the Problem is gone for my device. Had no random reboot so far, and in the meantime, i must have between 4 & 5 random reboots normaly. But thats not the case, so i guess they are working on it or just fixed it with CSDE.
I hope Samung fix that, if this case is a Hardwareproblem or Manufacturproblem whatever. Mean that they have to replace it for 0 cost normaly..
---------- Post added at 11:59 AM ---------- Previous post was at 11:56 AM ----------
tyrell22 said:
Disable Fingerprint unlock in settings.
This is an ongoing issue that I've been trying to raise awareness of and is occurring across both S9s and the note 9.
I believe it be a software issue since it began shortly after one UI update, but there are reports that replacing the FP sensor solves the issue.
I have been using my Note 9 without FP unlock for a little over a month now, and once you get used to intelligent scan only, its not that bad. You will still be able to use FP in apps and such without a problem.
Post everywhere you can and lets hope we can attract enough attention for a official Samsung response.
Click to expand...
Click to collapse
Okay so far so good, but i guess this cant be a soloution for us Noteusers that we deactivate a pice of Hardware cause we have random reboots.
Maybe we can all spam Samsung via Samsung Members App with this Problem as i done so many times the last weeks. Dont forget to sent a systemreport with it, so they can check whats going wrong. Had no random reboots so far with new Build, but if it comes back, i report every time it appears.
tyrell22 said:
Disable Fingerprint unlock in settings.
This is an ongoing issue that I've been trying to raise awareness of and is occurring across both S9s and the note 9.
I believe it be a software issue since it began shortly after one UI update, but there are reports that replacing the FP sensor solves the issue.
I have been using my Note 9 without FP unlock for a little over a month now, and once you get used to intelligent scan only, its not that bad. You will still be able to use FP in apps and such without a problem.
Post everywhere you can and lets hope we can attract enough attention for a official Samsung response.
Click to expand...
Click to collapse
Sure enough, I went an entire day and this morning it happened again... I have now disabled the Finger Print Sensor and we shall see what happens.
have this same problem... the thing is.. once or twice I got see a popup about one UI stopped responding and the phone restarted... not sure if the FP scanner is causing it.
Try wiping the Cache Partition in Recovery Mode. If that doesn't help, back up your device and perform a hard factory reset.
So till this day no random Reboots..Think they fixed it. Im still on CSDE cause the Mai Update still not Aviable for German dbt
Hey all just checking to see if anyone has same issue, it is persisting beyond an update. I plug in for night and usually every morning screen is off. Takes me holding down power button for ten seconds for it to come back. Not sure if I'm rebooting phone and it was on or if it was off.
Same here. Got it 2 times. No idea!!!
Exactly same issue, happens every 3-4 days.
I have same problem. After last update, that hapoend 3 times already. I wonder why...
Guys you have to search before posting. Here is the topic i made a while back. Have had this issue since then and i notice it because i have the aod (always on display) and the screen disappears.
https://forum.xda-developers.com/ro...ly-to-hold-t3994037/post80721405#post80721405
Apps i suspect:
Blockada
Owntracks
Health mate
Spotify
Which of these are you guys using? Maybe we can deduce if its an app or some firmware issue.
From your list I'm using only Spotify. However I'm afraid that my phone was turning off even before I got this app. Will check anyway (already uninstalled it), and will let you know.
What I can say for sure is that my phone is switching off completely (not only display) as all my Bluetooth devices are disconnected straight away.
Hope we will find a solution for this issue!
it happened to me twice as well, having the phone for almost 2 months. It is a bit annoying and I dont understand why it happens. Among the list of these apps, I only have Spotify installed as well.
I dont have any apps from Your list. My phone turned off twice since last update, before that, for 1 month everything was ok. Now seems good aswell, we will see.
Seems like its none of the apps. My phone also completely disconnects from my devices and none of the buttons work (like double press volume button for camera). Have to hold the power button for a while and it starts up.
My Always on display is off
Random phone off was happening before the update and it's still happening after!
Also at times phone send to be so sluggish! 7gb+ram still available at that time.
North America 12gb/512gb.
All stock.
Sent from my ASUS_I001DC using Tapatalk
Ok, this issue together with the reported complaints of dust in camera lens has made me hold on the purchase of this phone.
Isn't there an official ROG II forum where all of you can complain so Asus can look into this issue maybe request dump files and resolve it once and for all?
baddar said:
Guys you have to search before posting. Here is the topic i made a while back. Have had this issue since then and i notice it because i have the aod (always on display) and the screen disappears.
https://forum.xda-developers.com/ro...ly-to-hold-t3994037/post80721405#post80721405
Apps i suspect:
Blockada
Owntracks
Health mate
Spotify
Which of these are you guys using? Maybe we can deduce if its an app or some firmware issue.
Click to expand...
Click to collapse
Well my doesn't randomly turn off and I'm using blockada if that sheds any light...
Also, I don't use Spotify
I have deleted all the apps. Literally done a reset to the factory settings to see what happen and this morning phone turned off again... That's really annoying.
I have found relevant topic on Asus forum: https://zentalk.asus.com/en/discussion/12715/rog-phone-2-12-512-freezes-and-auto-restart-problem
Looks like they are not fully aware of the problem....
Is there any update for this case?
I'm experiencing random hangs as well after updated the firmware to the latest. It reads my power button and will shows the options to reboot but the UI is totally not responsive, have to hard reset it Everytime.
Since factory reset everything seems to be fine, however it's just few days since I have done it.
09/12/2019 - I can confirm that after factory reset everything works fine. If anything change I will let you guys know straight away.
02/01/2020 - Annnnnd it's back... After few weeks phone started switching off again and tbh the whole thing intensified. Yesterday phone went off 9 times. On top of that when it's off it drains battery like crazy - 5mins and 20% is gone. Bluetooth doesn't work properly as well. I'm aware that others don't have any problems with ROGII, however I'm afraid that due to personal experience I won't buy Asus phone again and won't recommend it to anyone.
Rog phone 2 turns off automatically
Same problem here happened twice in 2 days everytime phone is off i have to hard restart to switch on the phone
Does anybody got any solution for this problem
Yes I have faced a similar issue since I have updated to android 10 beta. This happened once. I left my phone for charging and the screen blacked out. I had to press the vol up+dwn and power to restore the functionality. Strange.
Shahruq said:
Yes I have faced a similar issue since I have updated to android 10 beta. This happened once. I left my phone for charging and the screen blacked out. I had to press the vol up+dwn and power to restore the functionality. Strange.
Click to expand...
Click to collapse
What version of beta you use?
It happened to me twice in three months. The smartphone got stuck/freeze in standby mode: no response from the physical buttons or touch. I use the official android 9 rom.
I managed to restart it with the power button and volume up/down pressed for 15 seconds.
baddar said:
Guys you have to search before posting. Here is the topic i made a while back. Have had this issue since then and i notice it because i have the aod (always on display) and the screen disappears.
https://forum.xda-developers.com/ro...ly-to-hold-t3994037/post80721405#post80721405
Apps i suspect:
Blockada
Owntracks
Health mate
Spotify
Which of these are you guys using? Maybe we can deduce if its an app or some firmware issue.
Click to expand...
Click to collapse
No apps install in the list nd it randomly switch off my phone it's software issue
Mine started turning off after 1 minute of use. Couldn't stop it nor control it.
Managed to barely get the WhatsApp backup and then factory reset the device. So far things are ok. But setting up from scratch is a pain in the ass.
I suspect that I tried to enable twin apps on WeChat while being on Nova Launcher. That may have triggered something, But I'm not sure.
Have turned off AOD as I don't need it nor want it and the white fingerprint circle pops up every ten seconds or so even though I've said I don't want AOD.
Has anyone else got this crap behaviour??
dladz said:
Have turned off AOD as I don't need it nor want it and the white fingerprint circle pops up every ten seconds or so even though I've said I don't want AOD.
Has anyone else got this crap behaviour??
Click to expand...
Click to collapse
LoL! Try Settings-Personalizations-Fingerprint animation-None
galaxys said:
LoL! Try Settings-Personalizations-Fingerprint animation-None
Click to expand...
Click to collapse
Haha it is
Haha, well then select settings in there, and Fingerprint Off
Lol honestly mate, AOD is off and fingerprint animation is also off. Try it yourself, I think it's a bug.
I've just turned on AOD, going to leave that bitmoji thing on. Why not.
I've tried everything to get rid of the FP, it just won't go.
Yeh sounds like a , I don't use Fingerprint and I leave aod on...
Cheers
galaxys said:
Yeh sounds like a , I don't use Fingerprint and I leave aod on...
Cheers
Click to expand...
Click to collapse
I'm sure if you tried it would do the same thing. Probably one of the many issues.
It's definitely a beta this firmware
dladz said:
I'm sure if you tried it would do the same thing. Probably one of the many issues.
It's definitely a beta this firmware
Click to expand...
Click to collapse
Just tried on my Global usa model and I'm not seeing it. Also, I've never added a fingerprint to the device....
galaxys said:
Just tried on my Global usa model and I'm not seeing it. Also, I've never added a fingerprint to the device....
Click to expand...
Click to collapse
Lol no idea then mate.
Not the end of the world
dladz said:
Have turned off AOD as I don't need it nor want it and the white fingerprint circle pops up every ten seconds or so even though I've said I don't want AOD.
Has anyone else got this crap behaviour??
Click to expand...
Click to collapse
I even went so far as to disable the system AOD apk via an apk disabler tool & that did not work.
IDK if you ever found the actual toggle to turn it off......I finally found it by selecting the search result in Settings.
I typed in Always & stopped there,finding "Always-On Display".
The toggle is at the very top of the page (FWIW,I missed this earlier when in the settings,it was easy for me to overlook the toggle in dark mode).
If you've already tried this & it's still coming on,here's what I'm trying for the next day or so:
Turn Always-On Display back on & set a scheduled time for one minute.
For example,I've got it turning on at 4:00 A.M. & turning off at 4:01 A.M.
ATM,option 2,the scheduled on/off time,seems to be working.
EDIT;after a few minutes,AOD is coming back on.
This is annoying....... Not looking good as a keeper,not liking OxyColor OS at all,what a mess compared to the OP7T Pro.
Not just this,but,the settings layout (for individual app settings is a trainwreck & power/performance options not sticking,keeps reverting back to out-of-box settings.
Well I think I found a permanent fix for this...it's actually a bug (in my case anyway)
I was forced to wipe my phone, which was a huge pain due to a problem with a mod I'd installed..
Anyway on boot I set everything back up then realised it's got AOD on by default and I went a turned it off.
Low and behold it stayed off..no need to do anything.
So what I think has happened is the update that came recently (11_A.12) that could have caused issues, always good to wipe after an update.
I honestly don't know if this will fix things for you, but it did for me.
Couple that with the fact that I'm now getting unbelievable battery life...I think it's maybe a good idea to at least try, you may not fix your AOD but you may get better battery. As I did, I think you'll probably get both.
Here's a bunch of pics from the last 24 hours, midnight on Thursday evening /start of Friday up till now.
Absolutely amazing.
dladz said:
Well I think I found a permanent fix for this...it's actually a bug (in my case anyway)
I was forced to wipe my phone, which was a huge pain due to a problem with a mod I'd installed..
Anyway on boot I set everything back up then realised it's got AOD on by default and I went a turned it off.
Low and behold it stayed off..no need to do anything.
So what I think has happened is the update that came recently (11_A.12) that could have caused issues, always good to wipe after an update.
I honestly don't know if this will fix things for you, but it did for me.
Couple that with the fact that I'm now getting unbelievable battery life...I think it's maybe a good idea to at least try, you may not fix your AOD but you may get better battery. As I did, I think you'll probably get both.
Here's a bunch of pics from the last 24 hours, midnight on Thursday evening /start of Friday up till now.
Absolutely amazing.
Click to expand...
Click to collapse
Are you using an Unlocked model, or a carrier (T-Mobile US) model (& are you rooted or unrooted)?
THX.
Turn this off
KOLIOSIS said:
Are you using an Unlocked model, or a carrier (T-Mobile US) model (& are you rooted or unrooted)?
THX.
Click to expand...
Click to collapse
EU unlocked. Ne2213
Bliszcur said:
View attachment 5596247
Turn this off
Click to expand...
Click to collapse
It was mate, they all were, it was a bug.
dladz said:
Well I think I found a permanent fix for this...it's actually a bug (in my case anyway)
I was forced to wipe my phone, which was a huge pain due to a problem with a mod I'd installed..
Anyway on boot I set everything back up then realised it's got AOD on by default and I went a turned it off.
Low and behold it stayed off..no need to do anything.
So what I think has happened is the update that came recently (11_A.12) that could have caused issues, always good to wipe after an update.
I honestly don't know if this will fix things for you, but it did for me.
Couple that with the fact that I'm now getting unbelievable battery life...I think it's maybe a good idea to at least try, you may not fix your AOD but you may get better battery. As I did, I think you'll probably get both.
Here's a bunch of pics from the last 24 hours, midnight on Thursday evening /start of Friday up till now.
Absolutely amazing.
Click to expand...
Click to collapse
I just got the 1st system update for the T-Mobile US version.
The AOD option to turn it off is now working.
Here's what is/was strange, pre-update:
The only way I could see/access the Always-On Display settings/toggle was to have the stock OnePlus Launcher as the default home app.
Even then, AOD stayed on, whether toggled on or off.
I was able to figure this out from prior experience with the original Oppo Find X & VIVO NEX.
Very strange that certain (seemingly unrelated) settings would be hidden due to choice of home launcher,but,apparently,BBK doesn't see this as an issue/bug(feature, LOL) that needs to be addressed, guessing this "feature" is persistent on the home market China models/firmware.
Glad it was cleaned up for the T-Mobile US update.
On a somewhat related note, pre-update, I could not find a way to choose "No Lock Screen". I looked in the usual place to find such & it was not available, AFAIK.
Now, post-update, that setting is found in "Developer Options". (Why?????? LOL)
On an unrelated note, post-update, another bug has apparently been taken care of for the T-Mobile US version :
T-Mobile bloatware apps now stay disabled, if chosen to do so. Pre-update, they would re-appear after a reboot.
With these bug fixes, my outlook on keeping this phone has definitely changed for the positive. I still have about 10 days remaining before T-Mobile's buyer's remorse return window closes.