Noticed this today after messing around with GSam and BBS around 7PM or so. Sometimes on certain instances, repeated by repluging different cables to get screen read. Possibly causing bad calibration? This would not reverse (even on reboot) and read randomly until I replugged charge cable. Not sure what the issue is, thinking possibly Lux and negative brightness? Not sure why a replug fixes it. I'm negative most of the time and can't really repeat screen error changing brightness settings. I could try reducing to a positive +1 and see if it happens again, just sucks as the lower brightness is more comfortable to my eyes and saves battery. Would hate if it were a lux issue no matter, really only thing I could think would cause it. I'm pretty stock. First time I've noticed this. Stock auto blows. Don't want to have to "reset" battery keeping phone off 5-10 minutes randomly either. Just making you guys/woman aware. Hope this was isolated today. I'll be keeping an eye out on logs and make sure.
The phone screen was on and active during this screen prior to all reboots. Even system battery showed no count on screen time.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After replug.
I lost quite a bit of screen time during these bugs. Not sure if this is/will cause the calibration issue as well making need for resets.
Edit: SCREEN_FROZEN(Android System) wakelock was caused by quite/silent mode. Pressing vol directly increased the count w/prompt, as does whatever sound trying to go off, and whatever other random thing is increasing its count.
Update: After weeks of use, and updating to 12B, this issue has not resurfaced.
Related
Ever since I rooted the KF I've been having strange problems. I used my KF this morning battery was 98%, everything seemed fine. Tonight I went to turn it on and it wouldn't. The power button would light up green for a second then just turn off. I tried holding the power button in for 30 seconds, nothing.
So I plugged it in the outlet, maybe it needed charged? Once I plugged it in, it started up but the Kindle Fire splash screen did seem to bootloop once or twice, like a flicker. I don't know if that's normal or not?
Anyway, once it turned on it has a ? in the middle of the batter icon. I also went into Settings>Device and it showed my device as having 0% battery.
Any clue?
EDIT: Strange, I uninstalled WidgetLocker just to see if maybe the lockscreen was effecting something. Out of nowhere, my battery went from 0% to 30%. Still want to know what happened some I'm not stuck again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bal1985 said:
EDIT: Strange, I uninstalled WidgetLocker just to see if maybe the lockscreen was effecting something. Out of nowhere, my battery went from 0% to 30%. Still want to know what happened some I'm not stuck again.
Click to expand...
Click to collapse
Sounds like the problem was related to WidgetLocker.
I don't use the tool on my KF though I do use it on my Dinc. Last few times I've looked into it on the KF, there were enough issues reported in the posts to make me stay away for now.
Hi
These past few days the battery has been draining ridiculously fast.
I charged it before bed and then it's basically sat with the screen off since.
34% battery gone to AndroidOS and Android System.
Better Battery Stats hasn't been very helpful as I'm not rooted. It does say that it's been "awake" 100% since unplugged.
Here's some shots. Anyone know particular culprits?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Delete everything inside your android folder in internal memory and memory card.
That would wipe all of my game saves etc wouldn't it?
Seems a background processing is keeping the phone awake. It might be because Bluetooth is on.
You can try using Greenify to Force Stop most of the apps (Does not require root). I find that my phone does not wake up much after it Force stopped most apps.
Do note that you would want to leave messaging apps running or you will not receive messages.
I have a Gear S connected by BT LE but I thought the point of BT LE was it's low power. ..
Ok. Update. Having turned off the Gear S and killing it's connection, that wasn't the cause as it's still 100% awake whilst screen off.
Ok. It seems to be Samsung's Gear Manager app. Uninstalled and it goes into deep sleep straight away. With it installed, even when not connected to anything, it keeps the phone awake.
Ok guys it started since I migrate to 5.1.1 ROM, flashed clean DN 0.3 note 5 port, and the phone would just go black at least once per day, nothing seems to work even a hard restart (volume up + power button for 20 sec) only a battery pull would restart the phone. So I figured it must be the ROM ( noone in DN 0.3 thread seems to have this problem) . So I flashed the original 5.1 firmware for my country, rooted it and used it for a day to find out it does the same! I'm really not sure what seems to be the culprit. I couldn't find a conclusive pattern on the bsod however last time I noticed it happened right before I was disconnected from public wifi, perhaps it is the modem? Maybe it's root and bootloader conflict with 5.1 firmwares? (the phone boots up, so it cannot be bootloader? Or I don't understand something about what bootloader does?) Any one has encountered the same problem? Any clues on how to fix it?
Just happened again while wifi connection was weak and I think it happens right before it got disconnected or switched to other connection mode or different wifi
Read around the forums that people are having bsod in combination with Tasker and secure settings to switch off secure keyguard, I never use this option, just use Tasker to automate sync processes, Uninstalled it nevertheless. Will see if it helps
Happened again... Noticed that the battery percentage drops quote significantly after the battery pool, here is the screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just updated to fresh Oreo and factory reset . but phone is draining battery crazy as well as heat up too much. I always have this **** Sensor on ... I wanted to turn it off . any workaround would b greatly appreciated:good:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
zaighumjawad said:
Just updated to fresh Oreo and factory reset . but phone is draining battery crazy as well as heat up too much. I always have this **** Sensor on ... I wanted to turn it off . any workaround would b greatly appreciated:good:View attachment 4549214
Click to expand...
Click to collapse
well its the proximity sensor, if you disable it your phone if you have Always On Display active, and when you are in phone calls and things like that the phone screen wont be turned off, i mean, AOD in the pocket with that sensor disabled will keep the screen on everytime and the battery will drain even faster.
its possible, if you are rooted and can install xposed and have some tweaks you can do it, already have some mods for xposed with that trick.
Have you checked your wakelocks? There could be a rogue app disabling deep sleep in the background... I used BBS and found out for me it was onefootball
i have checked every single settings not sure about wakelock... proximity sensor should not light up when screen is off. so there is something...even with screen off no always on display its still on
Any solution mates,
buddies...!!!!! just checked it on lg astro 2 and two more devices it is always lighting ..so no problm i think...
My ZE553KL (I use it as a home device control, small tablet) keep loading/reloading for 3 hours now. I CANNOT SHUT IT DOWN. everytime I have this vibrate boot, ITS SUPER ANNOYING.
It show the bootloader then reboot, then show the bootloader and so on. Buttons are unresponsive.
Only think I can do is press up and get to screen number 2 for exactly 6 second (my computer then recognize it).
I cannot remove battery (hello soldered battery). or shut it down, I guess at some point It will drain battery but.
I have no idea what is happening, please help?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ouch
Play with it. Proper button sequence and timing is everything. It's easy to not hit the right button at the exact moment. Allowing the battery to auto shutdown may break the cycle. Don't attempt to solder the battery without a good iron and skillset. You need to be fast about it.
If the OS is pre Pie it's suspectable to rootkits that require a reflash to erraticate.
A hardware failure is also possible.
A bad coded 3rd party apk can also boot loop you. That's worse than a normal boot loop though.
It's definitely corrupted... hopefully someone here who has seen this before and/or knows more about that line of phones advanced troubleshooting can help you.