Database Users

I may have solved the famous battery problem on Nook & Nook Touch!

Hi,
I've been using Nook for two years and Nook Simple Touch for 5 months or so.
I've rooted both my devices and used them that way (until my original Nook got those screen problems and became unusable)
Starting from first days I realized that the battery life was quite shorter than advertised. In fact it was almost unacceptable, like draining %10-15 a day while standing by (at the regular screensaver)
First I thought this was caused by the rooting and custom firmware. I tried the regular disabling of services, but to no avail. After a while I decided to return to the stock 1.1 firmware (on NST). To my horror I saw that nothing changed. Then I rerooted the hardware, still same.
One day, while I was reading a book I got a call and had to leave the house very fast. Thus I bagged the NST and got out of the house.
After returning home, I left that bag in my living room and did not open it for five days. After five days I picked up the NST, which was %70 charged five days ago, sure that I had to charge it again. To my surprise I saw that the charge was still %62. How could this happen, I began to querry. And remembered that I did not manually activate the screensaver -which was my general behaviour.
After that day I did not manually activate the screensaver even once and the battery drain is never more than 1-2%/day.
I'm not an Android developer, I'm a regular computer guy (using computers for almost 30 years) but I have strong gut feeling that this may be the problem, that manually activating the screensaver is not same as activation after a time out.
I guess many people over here, being -not regular users but optimization obsessed technical people- prefer to activate the screensaver manually. Thus they have the drain problem.
If you are suffering the same problem, please test this and write your feedbacks over here. May be one of the coders can look into this problem in the end.
With kind regards

You may be onto something there.
I certainly believe that the problems are related to not fully going into sleep mode.
I have caught the Nook many times that it was supposed to be sleeping and the touch screen was still running.
I always used the power button when I'm done, I had the screen timeout set on one hour.
I just set my screen timeout to 10 seconds to play with this.
I couldn't get the Nook to act up with the power button shutdown.
To set your screen timeout to a arbitrary value (time in milliseconds):
Code:
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
sqlite3 settings.db
update system set value=10000 where name='screen_off_timeout';
.q
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db

foredog,
Could you clarify a bit, please?
Nook can go into screensaver via
timeout,
front button,
back power button or
"button savior Off" button.
Which button you referring too to manually activate the screensaver?

foredog said:
After that day I did not manually activate the screensaver even once and the battery drain is never more than 1-2%/day.
Click to expand...
Click to collapse
I use my Nook Simple Touch minimally and almost always use the back button to activate the screensaver. I see pretty good battery life upto 20+ days. The only thing I do differently from you is turn off wifi before I activate the screensaver. Maybe wifi is the main cause for the battery drain.
--

cbay said:
I use my Nook Simple Touch minimally and almost always use the back button to activate the screensaver. I see pretty good battery life upto 20+ days. The only thing I do differently from you is turn off wifi before I activate the screensaver. Maybe wifi is the main cause for the battery drain.
Click to expand...
Click to collapse
WiFi is definitely a big one.
Any easy way to "auto turn it off" with screensaver activation?

Don't know about that - I always use the "sleep" button to activate the "screensaver". Right now, I'm up to a month of use, and like 30% batt still. I turn wifi on when I need it, and off again when I don't. Glowlight on for like 20 min/day.
Actually really impressed with NST Glow.

Sorry I did not mention, that my wireless is always off.
@Apokrifx: I'm using the power button at the back to go to sleep mode.
What you all are saying is similar to general behavior. Everyone is not experiencing this drain among Nook users, only some.
In my case, letting NST time out really solved the problem.
What Renate says is really similar to my experience. Time and time I accidentally touched the screen (while it was on the screensaver and it asked for the swipe motion (meaning the touch interface is responding) which should not happen in the sleep mode.
I'll let you know if anything changes.
Thank you for the feedbacks.

I think the original post info is quite accurate. I notice when I don't go back to the home screen, and leave it on the stock reader when I put it down-- battery life is much better.
It appears that, when the stock reader is running, it shuts down most background services. But, that's just a theory.

i guess when u activate ur screensaver that wont drain power from ur battery ..... cuz in screensaver mood the animation on screen stopped like calculator screen ..... just display image and didnt move any pixels on screen ..... so .... ummm .... i guess ur problem may u not charge battery well .... let me tell u .... u must per month empty the battery until nook tells u that ur nook device cant power on .... and that will guarantee to u long life to ur battery also keep ur battery more efficiently and working perfect
hope i helped ..... best regards

Actually, I've had no battery problems in a while.
I've got rid of almost all the B&N stuff though.
USB host mode, with its polling seems to take a bunch of battery though.
It's still manageable.

I got my glowlight nook recently(after I stepped on my old Nook ST, ouch). When you have glowlight on and the Nook goes into sleep mode the glowlight turns off. It happens even if you press the back button. But... I had few instances when the screensaver activated and the glowlight didn't turn off... Can't reproduce this issue too often and with glowlight at least I know when it didn't turn off But other services might have simmilar issue.

I wonder whether this has anything to do with the wi-fi sleep mode you can tweak on normal Android phones... maybe the default sleep disconnects the wifi too, while the sleep button in the back just activates the screensaver.

Renate NST said:
You may be onto something there.
I certainly believe that the problems are related to not fully going into sleep mode.
I have caught the Nook many times that it was supposed to be sleeping and the touch screen was still running.
I always used the power button when I'm done, I had the screen timeout set on one hour.
I just set my screen timeout to 10 seconds to play with this.
I couldn't get the Nook to act up with the power button shutdown.
To set your screen timeout to a arbitrary value (time in milliseconds):
Code:
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
sqlite3 settings.db
update system set value=10000 where name='screen_off_timeout';
.q
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
Click to expand...
Click to collapse
Hi,
The UK went crazy with the Nook last week and I got one. I also got the problem with the battery. I have tried this:
This is taken from qvc forum. I cannot paste the link, as this my first post. This is what Bogeygirl says: (you will need to google the text below, and find this on qvc)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
I love my Nook Simple Touch that I purchased in February of this year. I was so disappointed that after this short time and charging to 100% it would drain to 8% over night..This happened twice. I did NOT have the wi-fi on and the automatic shutoff I had set to 2 minutes so no issue there. No recent updates had been done to cause an issue like this.
I was not worried because it was still under warranty and would be replaced. So I called B&N CS and went through all the steps with them to make sure it was in fact defective.
He asked me to totally shut it down and do a hard reset and re-re-register the unit. I was not hopeful that this would work at all. I know that a hard reset can fix a multitude of sins but I never would have thought it would work to fix this battery draining issue..To my surprise it worked.. Battery charge is holding just like before.. I read a lot and usually charge it once a month.. I am so glad that this worked. Such an easy fix but I will continue to monitor the battery charge just in case.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
I have tried it, and it seems to work fine, holding charge OK. Bogeygirl says hard reset, but it is the soft one. Foredog says that you don’t need to click the power button to sleep (just leave Nook to do the job for you), but I do click it to sleep, and I do also tap the screen, just to make sure that it is properly sleeping. It is fine at the moment. I think the whole problem with the battery is a software error with sleeping mode, as you say here. I think you are right.
I don’t have it rooted, as I only want it for reading.
Do you have any other advice for the battery? Or easier? I think everybody is having problems with the battery.:crying:
Thanks

Deep Sleep Battery Saver?
Does Deep Sleep Battery Saver help with the power-button not sleeping properly?
It performs several functions:
1. Supposedly automatically puts the device into sleep mode whenever the screen turns off (if you configure it properly).
2. Functions as a task killer, with a whitelist, to clear out buggy apps.
3. The Whitelist allows you to prevent useful apps from being killed.
I still use the power button to put the NST to sleep. Last night it drained about 7% overnight, although I leave WiFi on and read RSS feeds for an hour before putting it down. Also, DSBS is configured to wake up the device every four hours.

smayonak said:
Does Deep Sleep Battery Saver help with the power-button not sleeping properly?
It performs several functions:
1. Supposedly automatically puts the device into sleep mode whenever the screen turns off (if you configure it properly).
2. Functions as a task killer, with a whitelist, to clear out buggy apps.
3. The Whitelist allows you to prevent useful apps from being killed.
I still use the power button to put the NST to sleep. Last night it drained about 7% overnight, although I leave WiFi on and read RSS feeds for an hour before putting it down. Also, DSBS is configured to wake up the device every four hours.
Click to expand...
Click to collapse
The battery drain is due to some BN apps and Android System apps, mainly. I use the last version of "SystemApp Remover" for disabling apps (eg:AFfileDownloadService.apk,AccountAndSyncSettin gs.apk, BnAuthenticationService.apk, BnCloudRequestSvc.apk, DemoMode.apk, DeviceManager.apk, DeviceRegistrator.apk, Music.apk, NookCommunity.apk, Phone.apk, QuickStartActivity.apk, Shop.apk, Social.apk ,TelephonyProvider.apk, WaveformDownloader.apk).

kuskro said:
The battery drain is due to some BN apps and Android System apps, mainly. I use the last version of "SystemApp Remover" for disabling apps (eg:AFfileDownloadService.apk,AccountAndSyncSettin gs.apk, BnAuthenticationService.apk, BnCloudRequestSvc.apk, DemoMode.apk, DeviceManager.apk, DeviceRegistrator.apk, Music.apk, NookCommunity.apk, Phone.apk, QuickStartActivity.apk, Shop.apk, Social.apk ,TelephonyProvider.apk, WaveformDownloader.apk).
Click to expand...
Click to collapse
I thought it was due to the device not sleeping after the power button was pressed?
I also removed those APKs from the system directory, thanks to many of you guys.

Switching Wifi Off Worked Well
ApokrifX said:
WiFi is definitely a big one.
Any easy way to "auto turn it off" with screensaver activation?
Click to expand...
Click to collapse
I had a Kobo mini & was not happy with the formatting of PDFs, hence I *had* to get a Nook Simple Touch ... the PDF formatting is excellent. However, I soon suffered the battery problem & couldn't get it to charge. I followed the advice on this page and it works so much better now. This is what I did :-
1) Switch off the Wifi. I have no need for it anyway as everything I read is PDFs loaded via SD card.
2) To charge, make sure the device is fully off using the back power button.
3) I charge it using a wall socket, rather than a computer. I have heard that this makes a difference in charging times.
It's early days, regarding how long it stays charged, but I reckon I will be resorting to switching the power off, rather than putting it on standby. I'm just pleased I managed to get it to charge at all and I am back in business.

assembler31415 said:
I had a Kobo mini & was not happy with the formatting of PDFs, hence I *had* to get a Nook Simple Touch ... the PDF formatting is excellent. However, I soon suffered the battery problem & couldn't get it to charge. I followed the advice on this page and it works so much better now. This is what I did :-
1) Switch off the Wifi. I have no need for it anyway as everything I read is PDFs loaded via SD card.
2) To charge, make sure the device is fully off using the back power button.
3) I charge it using a wall socket, rather than a computer. I have heard that this makes a difference in charging times.
It's early days, regarding how long it stays charged, but I reckon I will be resorting to switching the power off, rather than putting it on standby. I'm just pleased I managed to get it to charge at all and I am back in business.
Click to expand...
Click to collapse
You probably don't want to resort to always powering off your Nook all the way, because the boot-up sequence uses about 3 or 4 times as much battery as regular use, making multiple reboots take up a large amount of battery.

Renate NST said:
To set your screen timeout to a arbitrary value (time in milliseconds):
Code:
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
sqlite3 settings.db
update system set value=10000 where name='screen_off_timeout';
.q
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
Click to expand...
Click to collapse
Is there a way to change default values?

I have a nook simple touch glowlight, it's about 5 years old. Recently it has been saying battery too low to use. I plug it in and it goes to restart right away. When I look at battery life it my be at 89% (this was today). Is there something I can do to make this stop? It's quite a pain to to this everyday. I read on this a lot about a 1000 pages per week. In the "old" days a charge would last 20-30 days! Please help, I hate to get a new on, I love my nook!

Screen Stays Awake

Hi,
The screen on my Nexus 4 has started to stay awake. I've noticed my battery drain a lot quicker over the last couple of days and I also noticed that every time I pulled my phone out the screen was lit so I've taken it out and watched it. It just stays awake all the time. If I turn the screen off the minute a message or anything comes in the screen wakes and stays awake so near impossible to keep it off for any length of time.
I do have the developer screen enabled and had stay awake whilst charging option enabled. I disabled that to make sure that this wasn't causing the screen to stay awake thinking it was somehow on the charger when it wasn't however the problem persists even with that option unchecked.
I have the screen timeout in display set to 30 secs.
Anybody else experiencing this or no how to solve?
The phone is stock and unrooted though I plan on rooting later today.

ktz84 said:
Hi,
The screen on my Nexus 4 has started to stay awake. I've noticed my battery drain a lot quicker over the last couple of days and I also noticed that every time I pulled my phone out the screen was lit so I've taken it out and watched it. It just stays awake all the time. If I turn the screen off the minute a message or anything comes in the screen wakes and stays awake so near impossible to keep it off for any length of time.
I do have the developer screen enabled and had stay awake whilst charging option enabled. I disabled that to make sure that this wasn't causing the screen to stay awake thinking it was somehow on the charger when it wasn't however the problem persists even with that option unchecked.
I have the screen timeout in display set to 30 secs.
Anybody else experiencing this or no how to solve?
The phone is stock and unrooted though I plan on rooting later today.
Click to expand...
Click to collapse
Does it stay awake but go very dim? I have this issue too.

can it be caused by the screen protector blocking the light sensor somehow?

Can you install BBS (BetterBatteryStats) and see what's keeping your phone awake?
Sounds like a FULL_WAKE_LOCK is constantly being imposed on your phone.

Questions
Is it only when you put it for 30s?
What's around your pocket when you put your phone in it?
Do you have any attachments onto your phone? e.g. skin protectors, cases...etc
Does this occur on any screen or just your home screen and the developer options screen?
Though some questions may be obvious, the best method is to be thorough with the situation. Answering these questions will help us better help you.

My phone shut itself down about an hour ago (plenty of battery left as I had to charge it earlier and was at 50% when it did come back on). It took several minutes before it would respond to getting turned back on again. I've got 2 messages since and the screen is now tuning off as it should. I had turned the phone off a few times to see if it rectified yesterday however that didn't work.
The problems wasn't anything to do with me having it in my pocket as the problem still existed when I had it sitting on my desk. I have no screen protectors or case and I never put it in any pocket that has anything else in it as I don't want to ruin too quickly.
So not sure what's going. All seems very odd. Hopefully not a sign that the phone is on the way out but looks ok for now. Will have to watch and see what happens over the next few days.
Thanks to all who took the time to respond. Hopefully I won't need to bother you again on this issue but not convinced just yet

Screen stays on after battery gets fully charged

Got a weird problem with my AT&T stock non-rooted S4. About 4 or 5 times since I got it on release day when I charge my phone and I get the notification that it's fully charged the screen won't turn back off. I use a Belkin Conserve socket that is set to shut off after 3 hours and I've woken up after charging to find the phone dead. I've managed to catch this happen once and when the fully charged notification comes on the screen won't go to sleep, it just stays on and flickers a little bit. For all but one of these instances I had blocking mode on so I'm not disturbed by email or text notifications in the middle of the night. It did happen one time when I didn't have blocking mode on. I use a pin lock for my lockscreen and usually have BeyondPod playing overnight (only one hour long podcast while it's still charging) if that makes a difference. Is the function that enables the screen to stay on when you're looking at it malfunctioning? Any help? I've attached two screenshots of battery life when this happens.

Tryptonite said:
Got a weird problem with my AT&T stock non-rooted S4. About 4 or 5 times since I got it on release day when I charge my phone and I get the notification that it's fully charged the screen won't turn back off. I use a Belkin Conserve socket that is set to shut off after 3 hours and I've woken up after charging to find the phone dead. I've managed to catch this happen once and when the fully charged notification comes on the screen won't go to sleep, it just stays on and flickers a little bit. For all but one of these instances I had blocking mode on so I'm not disturbed by email or text notifications in the middle of the night. It did happen one time when I didn't have blocking mode on. I use a pin lock for my lockscreen and usually have BeyondPod playing overnight (only one hour long podcast while it's still charging) if that makes a difference. Is the function that enables the screen to stay on when you're looking at it malfunctioning? Any help? I've attached two screenshots of battery life when this happens.
Click to expand...
Click to collapse
So in settings under the Developer Options, there is a setting "Stay awake" if checked screen will never sleep while charging. Now I see that your Belkin shuts off the power but your phones still detects the usb plugged into a power source.
I think things happen in this order: you hookup your phone to charge and shut off your screen, phone charges to 100% and screen lights up saying fully charged, it stays on because of that setting, Belkin kills the power, it is still hooked up to USB so ... you get the rest.
I would find that setting and disable it.
if your next question is "I don't see developers option" it is hidden by default in android 4.2.2 so to make it available, go to Settings > About phone and tap tap tap Build number seven times. Return to the previous screen to find Developer options. Or Indiana Jones might pop up and give you the cup to get eternal life !!!

Thanks for the reply Commodore64 but I already checked that setting when it happened the first time and it's not checked.

No one else has had this problem?

Tryptonite said:
No one else has had this problem?
Click to expand...
Click to collapse
I have this problem as well as my wife's S4. around 3am, I notice our room is bright with our two phones' screens on. It will stay on until the morning.
In the developer's section of the settings, the stay on when plugged in is NOT checked.
Also, on our phones, we notice the phones overheating because the screen is on for hours at a time at night.
I've just spent an hour looking through the internet, and while many report this, they are simply being dismissed by others as in having "checked" the setting in developer section.
Also, when the batttery does get fully charged, the "Battery if full, unplug the power" notification also rings the default notification ringtone. I've installed phoneweaver to set my phone to no sound overnight, but it only stops the sound, the screen still stays on and phone gets really hot.
This is turning out to be a huge problem for us.

pyrophilus said:
I have this problem as well as my wife's S4. around 3am, I notice our room is bright with our two phones' screens on. It will stay on until the morning.
In the developer's section of the settings, the stay on when plugged in is NOT checked.
Also, on our phones, we notice the phones overheating because the screen is on for hours at a time at night.
I've just spent an hour looking through the internet, and while many report this, they are simply being dismissed by others as in having "checked" the setting in developer section.
Also, when the batttery does get fully charged, the "Battery if full, unplug the power" notification also rings the default notification ringtone. I've installed phoneweaver to set my phone to no sound overnight, but it only stops the sound, the screen still stays on and phone gets really hot.
This is turning out to be a huge problem for us.
Click to expand...
Click to collapse
Do you use a PIN (number) lock? I did but switched to the pattern unlock and it hasn't happened since. Also, I've been trying to charge only during the day or evening, not overnight. Maybe, since I charge during the day and I use it periodically while it charges it doesn't go into a "deep sleep" like it would if it charges while sleeping and the full charge notification would keep it awake. I don't know exactly why but it hasn't happened since. Hope this helps.

Power Button Not Working SGS4 Not Sleeping SOLVED
For whatever it's worth, see http://forum.xda-developers.com/showthread.php?p=48871706#post48871706 - maybe that will be helpful.

Doze mode problems a OnePlus 5 issue or Nougat?

I'm not sure if my problem is with OxygenOS or Nougat, but I've scoured the internet for months and haven't found an answer
I have two problems that I think are linked to doze mode on my device, and they both occur under the same conditions. First is my alarm clock (Alarm Clock Xtreme) doesn't work in the morning, and second is my Samsung Gear Fit 2 needs manually reconnected each morning. And through troubleshooting I've determined the problem occurs under rather unique conditions. The problem ONLY occurs when my phone is plugged in and sits overnight (so fully charged sometime during the night). Which is most nights, because I want a full battery in the morning.
But if I happen to go to bed and leave the phone unplugged, the alarm clock WORKS in the morning and the smart watch stays connected all night. So unplugged overnight, no problems. Plugged in, alarm clock won't work and Bluetooth connection to smart watch is dropped.
I haven't been able to find an answer in the 3 months I've had my OnePlus 5. Any thoughts?
Specs: OnePlus 5, Oxygen OS 4.5.10, Nougat 7.1.1.

I can also move this post elsewhere if there is a more appropriate area of the forum for this question. But I don't have this problem with my old device.

You can try disabling battery optimization for selected apps.

doggie13_ said:
You can try disabling battery optimization for selected apps.
Click to expand...
Click to collapse
Thanks, but I already tried that. It doesn't work.

It's probably the apps man if you think about it. Try using a different application and report back.

Dchoi229 said:
It's probably the apps man if you think about it. Try using a different application and report back.
Click to expand...
Click to collapse
I actually had another alarm clock app before, that was doing the same thing. And I don't really have an alternate application for the watch.
I've researched this fairly extensively and have only been able to grasp small nuggets of insight. I did find one source on xda (but I can't remember where I saw it) that talked about doze mode acting funny when the phone is plugged in to charge. Basically an inability to wake from doze under certain circumstances.

Liam1694u said:
I actually had another alarm clock app before, that was doing the same thing. And I don't really have an alternate application for the watch.
I've researched this fairly extensively and have only been able to grasp small nuggets of insight. I did find one source on xda (but I can't remember where I saw it) that talked about doze mode acting funny when the phone is plugged in to charge. Basically an inability to wake from doze under certain circumstances.
Click to expand...
Click to collapse
You can always enable Developer Options and choose the option for the screen to stay awake while charging which should also keep your phone awake. You can also disable Doze completely in Developer Options.

jhs39 said:
You can always enable Developer Options and choose the option for the screen to stay awake while charging which should also keep your phone awake. You can also disable Doze completely in Developer Options.
Click to expand...
Click to collapse
Thanks! I don't want to disable doze, but I might try that other one. My other quick fix I juts thought of is to use a timer switch or smart switch to have the charger shut off after an hour. That's enough to give me a boost, but not fully charge. I tried it last night and everything worked this morning. Though my battery was only at 60%, it was better than nothing.

Liam1694u said:
Thanks! I don't want to disable doze, but I might try that other one. My other quick fix I juts thought of is to use a timer switch or smart switch to have the charger shut off after an hour. That's enough to give me a boost, but not fully charge. I tried it last night and everything worked this morning. Though my battery was only at 60%, it was better than nothing.
Click to expand...
Click to collapse
It's recommended these days to keep your battery charged between 40%—80% to prolong its life and not keep the phone plugged in overnight like in the old days. I charge mine to 80% before going to bed.
If it's actually a Doze issue I don't understand why it wouldn't happen when the phone isn't plugged in. Do you have a screen saver enabled?

Fellow OP5 user here, I have the EXACT same problem.
If I leave the phone charging for long time and doze kicks in, the phone basically shuts down for all purposes until I unlock it with my pattern. Meaning, only the built in alarm (that works even with the phone turned off) will work. Any other (Timely, radio...) won't.
Now here's the kicker: sometimes the deep sleep will cause a weird bootloop, upon which the screen will indefinitely hang on the spinning logo, with the screen turned on, requiring a reboot. And of course this makes the alarm not sound.
This last bit happens at random. If I disable the screen sleeping in Dev options, the alarm will work but when I wake up the pattern input screen would be there, after all night on, which isn't really healthy for the screen.
Turning doze off makes this problem apparently disappear, but I need to investigate some more to draw conclusions. For the time being I sleep without charging, quick charge and the phone's great battery makes it unnecessary to keep it connected all night.
Another fun tidbit of this deep sleep mode: it stops USB tethering. I would have imagined a wakelock in there, but apparently there isn't.
For information : I use vanilla kernel and OOS. I have Magisk on and Gravitybox via Xposed Magisk, but other than that I have nothing particular going on.

I've been hearing that from other sources as well, about not letting it sit overnight on the charger at 100%. Which is why I think I'm gonna keep using the smart switch of my nightstand charger. The OnePlus Dash charging system works great for a quick charge anyways, so having 100% fully charged to last all day long is no longer necessary. I have a normal USB cable at my night stand, so it's a slow charge. If I set the timer to stop after an hour it at least gives me a small charge overnight, without overdoing it. And I have dash charger at work to give me the full quick 20 minute charge that puts me at 60-70%.
No I don't have a screensaver running. It is weird that the phone locks in the doze mode for the alarm and boots me off my watch's BT connection, but only when plugged in and sitting at a full charge for an extended time (haven't stayed awake all night to test just how long it has to sit). But that IS what it IS. Those have been confirmed as the only conditions in which this problem arises. I've been using the smart switch for 3 days now to keep my phone from going to and staying at 100%, and the alarm clock is working again and the watch is staying connected.
It's not that it's a big of a deal for me to have to use a work around like this. I don't mind. But I hate finding a glitch in something and not being able to truly "fix" it. Work-arounds work. But they don't actually solve the problem. This is just a gripe I have in general whenever something like this happens. It's in my nature to want things to work properly. Which is why I haven't had a non-rooted device in at least 5 years. I NEED to have the ability to fix the [email protected]$$ sh1t the software developers and phone manufacturers screw up. Of course, that's probably the number one reason xda exist. This open up the full potential of these devices, because the manufacturers are either too dumb or are financially motivated to not fix things (ahem...Samsung). Thank you everyone who chimed in with advice. I appreciate it.

It has been my experience with this phone so far that doze mode doesn't work. At all. I regularly have widgets that won't update even though I have doze turned off...
Just one of the many annoyances that has me thinking about finally rooting and getting rid of this garbage os...

HD Fire 8 (7g) Is there a "Keep Alive" Option?

I have two of these (and an HD Fire 10) all running Lineage (running great) that I'm using as security/smart device panels in my house at key locations (every main door). The HD 8's are simply not as fast as the 10 and are slow to refresh to the point that every time they come out of sleep they have to restart the panel software (Fully Kiosk Browser running ActionTiles) which just looks terrible and takes a few seconds. This is clearly less than optimal.
I'm wondering if there's any feature or way to allow the device to continue to have the screen be dark while the WIFI connection and the data keeps active in the background. That way when the device "wakes", it won't need to refresh and the data will always be accurate . The HD 10 panel is fast enough that it refreshes before I even notice. It's just too big a panel for the other locations. I also want to keep these fully dark for two reasons: I'd rather not be running the backlight life down 24/7 and the glow, even when all black, is quite noticeable at night.

Agrajag27 said:
I have two of these (and an HD Fire 10) all running Lineage (running great) that I'm using as security/smart device panels in my house at key locations (every main door). The HD 8's are simply not as fast as the 10 and are slow to refresh to the point that every time they come out of sleep they have to restart the panel software (Fully Kiosk Browser running ActionTiles) which just looks terrible and takes a few seconds. This is clearly less than optimal.
I'm wondering if there's any feature or way to allow the device to continue to have the screen be dark while the WIFI connection and the data keeps active in the background. That way when the device "wakes", it won't need to refresh and the data will always be accurate . The HD 10 panel is fast enough that it refreshes before I even notice. It's just too big a panel for the other locations. I also want to keep these fully dark for two reasons: I'd rather not be running the backlight life down 24/7 and the glow, even when all black, is quite noticeable at night.
Click to expand...
Click to collapse
You can use Stay Awake option in developer options.
Stay Awake option is only works when connected to the charger.

AmznUser444 Dev said:
You can use Stay Awake option in developer options.
Stay Awake option is only works when connected to the charger.
Click to expand...
Click to collapse
According to another post that keeps the screen on, which I definitely don't want to do. Is that not correct? For example, one of the panels is our bedroom so having it always on would be a HUGE distraction and it would mean wear on the backlight.

You could try this wakelock app: https://play.google.com/store/apps/details?id=eu.thedarken.wldonate.

Will give the app a shot. I also tried Stay Awake. Not sure if I need to reboot first. For now it seemed a TOUCH more responsive, but the screen was still off and it still "awoke" with the wrong time and had to refresh.