Related
I've done a lot of searching, on here and on google in general, and still can't find a solution. Maybe I'm just not asking the right question...
I'm using Dutty's newest ROM, but had this problem when I was just using the stock Tilt ROM as well as when using an older one of Dutty's ROM's. I have the screen turn off after about 20 seconds, and when it comes back up the time is always off. It updates properly after about 1-2 seconds, but it's incorrect for the entire time the screen is off. This isn't normally an issue unless I want to use an alarm. With the clock not updating itself continually (like every non-PDA-type phone I've ever used), alarms don't work at all. I installed S2U2, and even with the screen waking up, once I hit the slide to unlock the phone that's when the clock updates. Not before. Any thoughts on how to fix this? Or am I missing something so obvious that I'm bound to get flamed for the question? Thanks in advance!
Mine does this too, stock AT&T Tilt OS for now, but my alarms and PhoneWeaver have absolutely no problem going off at their appropriate time. It looks like it's just not updating the video card with the current time while sleeping since the display isn't on. Not too much of a problem for me as I'm accustomed to wearing a watch, but I can see how it would be annoying for others.
Seems to me that's just normal for any computer when sleeping. My Vista machine and my Apple machines all do that too. When you wake them from sleep, the clock display is behind, but instantly updates once the system is back on line. The internal clock is still running the whole time of course, just the display does not update since the graphics system and cpu are in suspended mode.
Ya' can't very well have a computer go into power saving suspended mode AND keep real time things like screen graphics updated constantly.
P.S. My Tilt does it too, but alarms and reminders all work just fine.
gwnorth said:
Ya' can't very well have a computer go into power saving suspended mode AND keep real time things like screen graphics updated constantly.
P.S. My Tilt does it too, but alarms and reminders all work just fine.
Click to expand...
Click to collapse
I agree that the screen shouldn't need to be updated constantly during power saving mode, but my problem is that none of the alarms work, and I'm just assuming that the system clock isn't updated because the display is so far behind. I'll do some more testing today... thanks for the replies so far!
Hello,
I originally wanted to post in here http://forum.xda-developers.com/showthread.php?t=2497660&page=213 but I wasn't allowed to because i'm new and whatnot.. so if anyone who knows where this post belongs could put it there i'd be thankful
To my problem, i really don't know what's going on but something is keeping my phone awake. i already greenified every possible app i have there, i have removed all widgets from my home screen, turned every locationsetting i could find off and left my phone in flight mode for 4 hours after completely charging and it still won't sleep. I'd be really thankful for any help with this
Wakelock Detector http://forum.xda-developers.com/showthread.php?t=2179651
the 3rd screenshot is from wakelock detector.. but still thanks for the reply...
here are some more screenshots.. although they dont tell me that much honestly
info http://forum.xda-developers.com/nexus-4/help/suspendbackoff-wakelock-killing-battery-t2460576 and here http://www.reddit.com/r/nexus4/comments/1fhib2/suspend_backoff_wakelock/
ok again i am actually really thankful that you tried to help me it just sucks if you don't know whats wrong and have to find your way through all that stuff alone.
but the thing is that in these 4 hours where i had 9 seconds of deep sleep i didnt use the phone, i had wlan turned off, was in airplane mode, had all apps greenified, i dont have chrome installed or any other potential source so... and as far as i get it suspend backoff is activated if there are to many wakeup calls in a short period of time which somehow was the case...
but all that said i updated to cm 11 yesterday and the problem is gone. today i had it online connected to my wlan for a couple of hours without using it (still most apps marked in greenify) and well the pictures speek for themselves
ok scratch my last post.. we are back where we left >( and i have a feeling its one of the google apps. god i dont wanna delete apps one by one until i maaaaybe have it back to normal
http://tomhorsley.com/rants/doze-mode.html
I'm definitely reverting back to 5.1.1 when I get the time and energy to fool with it .
sounds like that was written by someone who hasn't even tried marshmallow yet. I have yet to experience any missed notifications, alarms or any issues relating to time in any way. If some apps are being affected by this then its a sign to the developer to fix their ****ty code because all of my apps relating to time at all have been working just fine and alot of them are still the same version they were on lollipop. Doze has improved my batter significantly. It sounds like this article was probably written by a developer who cant code properly and instead of improving his skills he'd rather complain and convince everyone to stay away from updates because he is unwilling to evolve. Even the article looks like it was written in paint...
I had indeed a wrong time bug some days ago...really strange and worrying, a reboot fixed it. First time ever since Android Froyo that I experienced something like that.
That author seems to think that Marshmallow's Doze is a horrible thing that breaks all apps that rely on background services, namely alarms and notifications, and couldn't possibly be fixed in 10 years (rather than a few months) due to Google's horrible mistake (rather than devs not fixing their code).
Frankly, it sounds like a bunch of hyperbole.
Sent from my ALCATEL ONE TOUCH Fierce using Tapatalk
He's wrong about how doze works. And if he's in the camp that doesn't understand it nor wants to rewrite his app. Then yeh he's the idiot group that Google is targeting and was writing garbage code anyway.
lol complete nonsense, my alarm has worked everyday since i flashed M, even on dev previews...the only issues i have with M are really the "slow to connect wifi when using toggles" and the weird wifi consumption on battery stats
Another annoying issue on M is that if your leave your phone longer in standby mode (display off), wifi turns off and you stop recieving notifications until you turn your phone on again. This is with wifi set to "never turn off", etc.
Kustaa said:
I had indeed a wrong time bug some days ago...really strange and worrying, a reboot fixed it. First time ever since Android Froyo that I experienced something like that.
Click to expand...
Click to collapse
This actually happened with me a couple of days back, I was travelling, so I put my phone connected to a power bank and went for a nap, woke up to see phone switched off, switching it on throws me a 2nd September date set on my device. Had to manually set the date as no network was available to automatically set the date from servers.
Ubichinon said:
Another annoying issue on M is that if your leave your phone longer in standby mode (display off), wifi turns off and you stop recieving notifications until you turn your phone on again. This is with wifi set to "never turn off", etc.
Click to expand...
Click to collapse
This I had been noticing these days just because of WhatsApp Web. When in standby, WhatsApp Web shows phone not connected error. Just waking the phone reconnects to the WiFi, but happens every 30-40mins.
I have a feeling that folks who never see these problems have their phones charging at night and doze mode doesn't happen when you are charging. I have no convenient way to charge my phone near my bed, so it is not charging and totally idle all night. Email and messaging completely stops. Only the stock alarm clock works. My medication reminder stops working. It might as well be turned off completely. Plus when you do wake up and turn on the phone, all the pent up alerts come through and scare the hell out of you. I hate doze mode.
Settings -> Battery -> ... (menu)-> Battery Optimization --> All apps --> Select whatsapp, etc... and select not optimized.
Test again.
You're welcome.
I already disabled optimization in the battery settings for all the apps that weren't working. They still don't work after sitting overnight. It looks as if that setting has absolutely no effect.
Claghorn said:
I already disabled optimization in the battery settings for all the apps that weren't working. They still don't work after sitting overnight. It looks as if that setting has absolutely no effect.
Click to expand...
Click to collapse
This is a real problem. I tested this on a Nexus 5. The device seems to enter Doze after about 1 hour and this is what happens.
What does work in Doze mode:
- Telephone: call can be heard.
- Alarm: alarm can be heard
What does NOT work in Doze mode:
- Receiving mail notifications directly: it seems to wait for the maintenance window. There is no "ping" from my GMail. No lock screen notification until I picked it up. I turned off battery optimalization as suggested. Like Claghorn says, it doesn't make a difference. When I was sleeping, the time difference between sending the mail and getting a notification can be hours. That is not acceptable: I want to determine whether or not I get a message. I got no control over Doze, except plugging it in. Also, when it sits on the desk at work I need to pick it up or turn the screen on every so often, because I don't know if it "dozed" off again.
Works partially:
- Notification light: It works once mail passes through the maintenance window. It does NOT work before the maintenance window.
I tested all of this with a unrooted, updated Nexus 5. Topic Starter and Claghorn have good points. Why can't I turn this off? I don't want this. I want notification on time, with ping, right now. If I don't I will turn the volume off or set priorities. They could have told me this behavior in a mail or during the update. Important mail from work, family comes in hours late. Not happy with this at all.
Tried all sorts of things, nothing seems to help. And no, battery optimalization is either not enough or has nothing to do with it. I love the Nexus 5. Marshmallow seems to be much smoother than Lollipop. I was happy with the update until I discovered this. Now, I am fustrated. I expect the phone to inform me when I need to be informed. Most days I don't need to save 10% of power anyway. For the first time I want to either root the phone and go back to Lollipop or even Kitkat. I don't know what else can be done. Fustrated.
Dennis de Swart said:
This is a real problem. I tested this on a Nexus 5. The device seems to enter Doze after about 1 hour and this is what happens.
What does work in Doze mode:
- Telephone: call can be heard.
- Alarm: alarm can be heard
What does NOT work in Doze mode:
- Receiving mail notifications directly: it seems to wait for the maintenance window. There is no "ping" from my GMail. No lock screen notification until I picked it up. I turned off battery optimalization as suggested. Like Claghorn says, it doesn't make a difference. When I was sleeping, the time difference between sending the mail and getting a notification can be hours. That is not acceptable: I want to determine whether or not I get a message. I got no control over Doze, except plugging it in. Also, when it sits on the desk at work I need to pick it up or turn the screen on every so often, because I don't know if it "dozed" off again.
Works partially:
- Notification light: It works once mail passes through the maintenance window. It does NOT work before the maintenance window.
I tested all of this with a unrooted, updated Nexus 5. Topic Starter and Claghorn have good points. Why can't I turn this off? I don't want this. I want notification on time, with ping, right now. If I don't I will turn the volume off or set priorities. They could have told me this behavior in a mail or during the update. Important mail from work, family comes in hours late. Not happy with this at all.
Tried all sorts of things, nothing seems to help. And no, battery optimalization is either not enough or has nothing to do with it. I love the Nexus 5. Marshmallow seems to be much smoother than Lollipop. I was happy with the update until I discovered this. Now, I am fustrated. I expect the phone to inform me when I need to be informed. Most days I don't need to save 10% of power anyway. For the first time I want to either root the phone and go back to Lollipop or even Kitkat. I don't know what else can be done. Fustrated.
Click to expand...
Click to collapse
A quick suggestion -
You may use Doze Mode Editor and edit the script so that your phone never enters Doze mode.
That way you can enjoy Marshmallow without Doze.
Sent from my Nexus 5
Achilles. said:
A quick suggestion -
You may use Doze Mode Editor and edit the script so that your phone never enters Doze mode.
That way you can enjoy Marshmallow without Doze.
Sent from my Nexus 5
Click to expand...
Click to collapse
Thanks, I will look into that. I'd like to keep Mashmallow as a whole if possible. I think it is a good update in general.
OK, I've looked at the doze mode editor thread and I find that the descriptions of the parameters I can set to be totally confusing, however, the flowchart pointed at in that thread seems to indicate that if I set the "inactive_to" value to something like 24 hours, then all the other doze mode nonsense is unlikely to ever happen (because I'll probably turn on my phone at least once every 24 hours). Does that seem like the best way to essentially turn off doze mode?
Claghorn said:
OK, I've looked at the doze mode editor thread and I find that the descriptions of the parameters I can set to be totally confusing, however, the flowchart pointed at in that thread seems to indicate that if I set the "inactive_to" value to something like 24 hours, then all the other doze mode nonsense is unlikely to ever happen (because I'll probably turn on my phone at least once every 24 hours). Does that seem like the best way to essentially turn off doze mode?
Click to expand...
Click to collapse
I will look into this over the weekend. I find it odd that there isn't simply a switch to turn Doze off, which is a pity. It seems to me it's part of saving energy in general. A switch under Battery would do nicely. It should not be this complicated. That said, I think the UI of Marshmallow is silky smooth, much better than Lollipop. Marshmallow in general in good. It' just this that annoys me.
i'm baffled by google's aversion to end user config. This kind of b.s. is how I found xda and drove me to become a chronic flashaholic. All or nothin I guess.
ElwOOd_CbGp said:
i'm baffled by google's aversion to end user config. This kind of b.s. is how I found xda and drove me to become a chronic flashaholic. All or nothin I guess.
Click to expand...
Click to collapse
I get the feeling Google assumes the customer is a developer. A few examples:
- The Nexus 5 does have a notification light: I didn't know until I read 5 reviews and even then I couldn't find any documentation on it. Needed an external app to get it working.
- Battery indicator: I like to have small numbers indicating battery charge: it could be done by hacking KitKat and Lollipop I think. Then at Marshmallow finally there's a (hidden) switch.
- I don't recall having any user guide in the Nexus 5 package. Not that I needed one. But some landing page doing a walkthrough would have been nice. Although there are some walkthroughs in every app
Not fatal flaws, but you wonder why does it need to be that difficult. It scares people away. Not me. I handed the Nexus 5 to some friends on numerous occasions and most found it too "empty". As for me, I want all developer stuff on. So it suprised me, there is no Doze fine tuning. Again, overall I give the Nexus a 8 or 9 out of 10. It fits me. In general I like it. So it's just constructive criticism. The empty layout and raw speed of the Nexus 5 works good in development of apps afterall.
Last night I ran an adb command (generated by the doze mode editor app) to set inactive_to to 24 hours (86400000 milliseconds). I then set an alarm for the next morning in the "Alarm Clock Plus" app (which completely ceased to function after Marshmallow showed up). This morning, the alarm actually went off on time, but the big "Dismiss" button it draws on the screen was totally non-functional. I had to hit the power button to get control (which then caused a popup saying alarm clock plus was non-responsive). I have no idea what caused all that behavior, but at least the alarm actually went off.
Also, with doze mode essentially disabled (in theory anyway), the power dropped from 100% in the evening all the way down to 97% in the morning.
With the exception to facebook and game type apps, Google's apps are the only ones I find that excessively waste resourxes and need to be forced to sleep. If they would get off the constant location polling, media scanning, and logging or at least tone it down a bit some they wouldnt need to implement thier half baked versions of solutions that they hijacked from xda devs
Was shocked to see the notification this morning, jumped in with the update before leaving for work and seems fine so far. Navigation Bar customization lost for now, Nav Star under Good Lock says they're working on an update so hopefully that takes care of things. Haven't had much time to explore yet but initially phone is much snappier, even after considering it restarts automatically once a week.
JLFitzpatrick said:
Was shocked to see the notification this morning, jumped in with the update before leaving for work and seems fine so far. Navigation Bar customization lost for now, Nav Star under Good Lock says they're working on an update so hopefully that takes care of things. Haven't had much time to explore yet but initially phone is much snappier, even after considering it restarts automatically once a week.
Click to expand...
Click to collapse
What version software were you on before?
Good question, don't really see an update Log. Last update was November so I assume it was SJ1. Updates have been running around 45 to 60 days on this phone.
I will say, and unfortunately not sure this option was around on Pie, but looked up Android 10 tips and enabled Adaptive Power Saving under Device Care / Battery / Power Mode and at least for the first day it seems battery draw has improved. Time will tell.
JLFitzpatrick said:
I will say, and unfortunately not sure this option was around on Pie, but looked up Android 10 tips and enabled Adaptive Power Saving under Device Care / Battery / Power Mode and at least for the first day it seems battery draw has improved. Time will tell.
Click to expand...
Click to collapse
Can you pull the update zip and post it?
JLFitzpatrick said:
Was shocked to see the notification this morning, jumped in with the update before leaving for work and seems fine so far. Navigation Bar customization lost for now, Nav Star under Good Lock says they're working on an update so hopefully that takes care of things. Haven't had much time to explore yet but initially phone is much snappier, even after considering it restarts automatically once a week.
Click to expand...
Click to collapse
Were you on a US or EU firmware?
Should be on US Firmware. Not sure what you mean by update ZIP, but see attached.
JLFitzpatrick said:
Should be on US Firmware. Not sure what you mean by update ZIP, but see attached.
Click to expand...
Click to collapse
You're using an N960U1 or an N960U but it has Unlocked US firmware on it, which just makes it an N960U1. Did you register for the beta on the Samsung Members app? Or can you tell us what your previous firmware was before you got Android 10?
Jammol said:
You're using an N960U1 or an N960U but it has Unlocked US firmware on it, which just makes it an N960U1. Did you register for the beta on the Samsung Members app? Or can you tell us what your previous firmware was before you got Android 10?
Click to expand...
Click to collapse
I see in all these post about the beta, you seem to never get a straight answer for that :fingers-crossed: maybe someone will actually respond instead of just asking questions
Dr.Lost said:
I see in all these post about the beta, you seem to never get a straight answer for that :fingers-crossed: maybe someone will actually respond instead of just asking questions
Click to expand...
Click to collapse
Yeah it's kind of.....odd.??* I don't even want the beta. I just want to know what the banking schemes are for the firmware itself. It'll give us a hint IF Samsung is leaving towards a bootloader update. Which will help tell us they fixed something nasty from the current bootloader. ?
I think I did register for the Beta so that makes sense, went to the Members Center looking for something else and tapped the icon for it, never got confirmation of anything though. The upgrade notification didn't state it was Beta either. Based on dates per Samsung Phone was probably on SJ1 Pie prior to this. I assumed this was the December 1 patch when it first popped up.
Notification popped up today when opening Settings that this is the Beta, a fact not communicated by Samsung during the update. Went into Settings upon noticing the Phone which was good all weekend today at work without using it started getting hot and draining the battery. Shut it down wiped partition cache a during startup then went into Battery / App Usage and found Camera, which had not been open since last night had used 62.7% of Battery over the past 6:43 hours. Toggled on 'Put App to sleep when not in use' for Camera App and will keep an eye on this along with everything else. All other App Usage seems to be normal. Charging phone now and it has cooled down.
Realize this was the Google Camera acting up that was installed from a link on this forum and mapped to activate by double tapping the Bixby button through BxActions (Samsung Camera activates by double tapping Power Button). Explains why it was acting up after the update. I like the G-Cam night mode and have been comparing the results to the S-Cam night mode including a few shots of Christmas decorations last night.
Updated this Thread Title to reflect what this upgrade actually is. Very happy with this upgrade so far, even though it wasn't labeled as the Beta version in the notification when it first popped up. Only real glitch I've noticed besides the G-Cam battery drain episode which is no fault of Samsung being a sideloaded App, is the settings security page. Phone is setup to require security log on when Settings is opened, currently the security pattern screen flashes then goes to Settings menu without requiring login fingerprint or pattern. Lost Navigation Bar customization I assume will be recovered when NavStar is updated, there is a notification in LockStar that let's you know they're working on an update.
Received another Beta update today.
Another Beta is pending, brings Security Patch up to January 1st, will install tonight.
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.