Related
Hello,
Below is the message i wrote on the google support forum, but i havnt gotten a single reply yet, so i turn to you guys, in hope that you're able to help me
I have been experiencing this issue on and off for the past month or two. The issue being, that something called "Android OS", in the battery usage list, is eating up all my battery.
An example is, currently my phone has been unplugged for 1h30m(im down to 69% battery life remaining after i unplugged it at fully charged 100%) where the battery usage is ranked as follows:
Android OS: 72%
Display:18%
Wi-Fi: 2%
Cell standby 2%
Android System 2%
and so on and so forth.
The reason why i wrote (kernel) in the title of this question, is, that with the app "Powertutor" i have been shown that the main "app" or proccess eating up my battery, when this "Android OS" is eating up my battery as shown in the Battery Usage list, is the Kernel. Right now is shows the kernel is using 84,3% of the energy usage, Handscent has been using 3.1% and so on.
Often a reboot will bring the phone back to normal and the Android OS issue goes away for a while. A friend of mine, however, who has the exact same phone as I, has this issue, almost all the time, and a mere reboot doesnt seem to do the trick for him. His phone only lasts 6-7 hours tops, where it most of the time is just idle, and he isnt using the phone at all. While mine, when the Android OS issue isnt present, last up to 20 hours on a single charge, when i dont use it much.
When the Android OS process is eating up all the power, the phone grows really hot as well, and the difference is easilly felt. So when i feel that my phone is hot like that, i automaticly think "oh, time for a reboot".
I've been unable to find any info regarding this issue on the internet, and therefore I'm unsure what to do to fix it for real. Tried several factory setting resets on my friends phone, tried not installing many new apps, formatting the SD card, formatting the phone from bootloader (still testing his phone to see if this worked properly)things like that, but always, the issue returned, as on my phone where it only pops up once every other day.
Hopefully, someone will be able to help, or shred some light on the case.
Thank you,
Chris
Device: Nexus One
Carrier: AT&T Phone Version, Danish Carrier Bibob
Country / Language: Denmark / English
OS / Browser / build number (if applicable): Android 2.2 Froyo / Native / FRF91
Having Exchange sync on, by any chance? Try turning it off for a day, see if it helps.
Jack_R1 said:
Having Exchange sync on, by any chance? Try turning it off for a day, see if it helps.
Click to expand...
Click to collapse
"Exchange sync" being exactly what? The basic sync function on the phone that can be enables and disabled? The basic sync with your google account?
If thats the case, then yea im having that on all the time, so that it may sync whenever it wants to. The sync icon doesnt appear that often though, so cant see how this could be the reason why. But if you come back to me and tell me that this is what you meant, i will definetly give it a try
Thx for responding
No, Exchange sync means - MS Exchange account (in addition to your default Google account) that syncs calendar/email/both with Exchange server.
I'm guessing again that that is something extra you must install / set up, which i have not done. The only two accounts i have that can sync are my facebook and my default google account. I never sync the facebook one though.
Edit:
Update:
Reinstalled Watchdog Lite today, since my phone has been exceptionally sluggish, and SeePU graph keeps showing a full graph on cpu usage. I've had to reboot it twice today, in hopes of it returning to normal state. It does for a while, but then returns to a slow state where Android OS uses like 80% of the battery.
I made Watchdog Lite monitor the base android processes as well, and right now it keeps warning me that the "Base System", "Linux Process" uses up 89,6% of the CPU and 10,3MB of RAM, while nr 2 on the list is Android System, Foreground, with 3,8% and 27 MB.
I feel like the state of my phone is worsening, and I'll prolly do a full factory reset(again)/format of everything within a few days if i cant find the root of the issue this time around.
Please help I love my phone and i want it to be healthy again.
chris6647 said:
Hello,
...
Click to expand...
Click to collapse
"OS" is an abbreviation for "Operating System". That means ALL of the background stuff that eats battery and CPU time that isn't attributable to a process or function easily understood by the typical user. This includes, yes, the Linux kernel, but also all the other background things that your phone does in order to continue functioning in a normal synchronized state...
Your phone has a CPU. The kernel has a process scheduler, which swaps different programs in and out of the CPU in order to make it look like it is running more than one thing at a time. Each clock cycle consumes some amount of the power from the battery, so if it assigns 10 cycles to process A, 10 cycles to process B, and then waits for 20 cycles for I/O synchronization, then HALF of the power consumed in those last 40 cycles (attributable to CPU) will be "Android OS". Clear?
lbcoder said:
"OS" is an abbreviation for "Operating System". That means ALL of the background stuff that eats battery and CPU time that isn't attributable to a process or function easily understood by the typical user. This includes, yes, the Linux kernel, but also all the other background things that your phone does in order to continue functioning in a normal synchronized state...
Your phone has a CPU. The kernel has a process scheduler, which swaps different programs in and out of the CPU in order to make it look like it is running more than one thing at a time. Each clock cycle consumes some amount of the power from the battery, so if it assigns 10 cycles to process A, 10 cycles to process B, and then waits for 20 cycles for I/O synchronization, then HALF of the power consumed in those last 40 cycles (attributable to CPU) will be "Android OS". Clear?
Click to expand...
Click to collapse
Alright, I was wondering exactly what it meant when it just said Android OS, just that seemed like quite a broad description.
But what your saying is that it may be other applications that is actually eating up the power, just the kernel assigning the power to the program, and therefore the Battery Usage shows the kernel/Android OS as the culprit?
If its the case that its an app then, that through the kernel is triggering the usage that drains my phone, then how come my friend had this issues with an almost "naked" phone? He had installed just a few apps and still ran into this issue.
Am i understanding what you're telling me correctly?
chris6647 said:
Alright, I was wondering exactly what it meant when it just said Android OS, just that seemed like quite a broad description.
But what your saying is that it may be other applications that is actually eating up the power, just the kernel assigning the power to the program, and therefore the Battery Usage shows the kernel/Android OS as the culprit?
If its the case that its an app then, that through the kernel is triggering the usage that drains my phone, then how come my friend had this issues with an almost "naked" phone? He had installed just a few apps and still ran into this issue.
Am i understanding what you're telling me correctly?
Click to expand...
Click to collapse
It's not normal, something is causing it. Most likely some poorly written app or some other weird thing is causing the "Android OS" (which I assume is likely the virtual machine itself) to do bad things.
khaytsus said:
It's not normal, something is causing it. Most likely some poorly written app or some other weird thing is causing the "Android OS" (which I assume is likely the virtual machine itself) to do bad things.
Click to expand...
Click to collapse
Today the linux process "init" has been hogging up all my phones resources, as in 77%+ of all the CPU usage :/
Was wondering if rooting my phone and installing/ flashing some custom rom would solve the issue for sure? Or should I send the phone back to the states for at checkup or repair? (dont think this is needed but now I ask anyway)
Is there an app that could track down exactly what is sucking my phone dry? Cus all that I've found are those broad references or processes :/
Thx for all your responses
Same problem here:
http://forum.xda-developers.com/showthread.php?t=826507
http://www.google.mw/support/forum/p/android/thread?tid=7da0c666e8ffbc36&hl=en
Seems like there is no solution available yet...
chris6647 said:
Today the linux process "init" has been hogging up all my phones resources, as in 77%+ of all the CPU usage :/
Was wondering if rooting my phone and installing/ flashing some custom rom would solve the issue for sure? Or should I send the phone back to the states for at checkup or repair? (dont think this is needed but now I ask anyway)
Is there an app that could track down exactly what is sucking my phone dry? Cus all that I've found are those broad references or processes :/
Thx for all your responses
Click to expand...
Click to collapse
There is no solution, because you can't track the app that is causing the system to hang.
You can uninstall all the latest installed/updated apps and install them one by one, using Titanium - and that'll pinpoint the offender.
After updating to 2.3.3 using COS-DS, my phone seemed to work fine. I initially had a battery drain with nothing taking up large battery usage, so I reset the battery stats and all was well.
However, after unplugging my phone from charging all night (100% upon unplug), I checked my phone two hours later and saw that my charge was down to 22%. Upon checking Battery Usage, I found that Android OS is using 76%! The only thing I've done today was answer a couple SMS messages. I don't have Sync, GPS, or Wifi on, but I do have Mobiledata and 3G+2G on, as well as Background Data. The only widget I have is Google Voice, which I've removed to no avail. I've tried rebooting (twice), but it stays the same. I've turned off data, gone to 2G-only, and turned off background data, and it still continues. In Spare Parts, under Battery history it says that the only thing using up the battery is Suspend in CPU, and Battery Status says that the battery's health is good. Something really strange is that after the initial power-off upon the discovery of this issue, I immediately plugged it into the charger. After about 3 minutes I turned it back on, and found that it's already charged back up to 86%. WHAT.
Also, I haven't plugged it into the computer once in the last few days, so it's not USB-bug related. Any ideas on what's going on here?
EDIT: Ok, it's been a couple hours since this began, but just now I checked the phone (it was on the charger) and suddenly EVERYTHING is gone from the Battery Usage page, save for Display and Android OS, and Android OS is back down to 5% now. Really bloody weird, but the issue seems to have resolved itself.
I've had similar issues. When my battery runs flat, dead. I plug it up and switched it on, and it shown "Charging (32%)". I get different but similar results with different ROMs. It could simply mean the battery is wasted couldn't it?
Have you gone into the Recovery mode and wipe the Battery Status? I was having similiar issue (but not a fast drain), I did maybe about 5 wiped and reboot the phone. My problem seem to go away.
I went from 1 day or less from 100% to having to recharge, to 2 and 1/2 days then charge.
The issue came back later that night, and has been happening ever since.
I've done the bump charge + stats wipe, where I let it charge to 100%, shutdown until green LED, wipe stats, restart, let drain to 0, restart and use. I've tried this about 3 or 4 times, and the issue persists. I've removed my 2 widgets (two sound effects widgets), and it persists.
Also, I've downloaded OS Monitor, and it shows the CPU to be resting at its min, 246.
I'm hoping it's just the battery at this point, and have already ordered another one. I'll let you guys know if that fixes it.
In that case it might be your battery that need to be replace. How old is the battery?
I really have no idea. I bought this G1 used on eBay 9 months ago.
2 things to note:
1. It actually stopped booting last night even while on the charger: I restarted, and it kept getting stuck on the splash image. So I superwiped, reflashed, and the drain is still there even with no user-installed apps.
2. About a month ago, (when I was back on a stable Froyo, which I had been on since I got the phone 9 months ago) it started to randomly shut off. It seemed like if it got just a little too hot (battery got to maybe 30 C, never was able to check what the temp was when this happened), it would shut down and wouldn't get past the boot screen without a reset. I had to either charge it or wait an hour for it to successfully boot again.
In retrospect, this is sounding more and more like the battery. The only thing that's strange is that Android OS takes up such high percentage. Oh well, hopefully the new battery gets here today or tomorrow, hopefully that fixes everything.
Since you have brought the G1 9 months ago, more than likely it's had been over two year or more (about the same age as mine more or less). I doubt that the seller would be giving you a brand new battery.
I noticed the reboot on mine G1 too. Ever so often, my G1 will reboot on me. But I do not have the problem getting stuck at the splash or boot screen. But then I am using the SuperAosp ROM not Froyo.
Let me know how the new battery will work out, I might have to end up getting it myself. Eventhough my battery life got better after I did the wipe battery status, sometime it still drain depending on the day I guess.
I noticed the same result with COSDS.
I moved to Ginger Yoshi with much better results.
Better, but not as good as stock, obviously.
COSDS turned into a real hog on me by the time the second or third reboot happened.
Heeter
I'll stay with SuperAosp, I take the performance over the battery life any day. My battery status an't that bad. Once in the while I used it up in a day or less, other I can stick around for a few days.
The rebooting part was not too bad on my end. Just once in a while. Nothing I can't handle.
@ psychosonic - You might want to try that if you want, Gingerbread Yoshi was one of my first choice before I found what I had.
Alright, got my battery. After calibrating it for one day, then using it today post-calibration, it's functioning phenomenally. After using wifi + internet for a period of time, and sms throughout the day, it's still at 70% 6 hours after charge. Essentially, the only thing that drains the battery is heavy internet use, which seems to make it go down 1% per 2 or 3 minutes.
Internet usage seem to take a lot out of the battery for sure. I know mine take a lot more than 1% every 2 or 3 mins when I use my internet.
Let see how will the new battery pan out. See if it will last you 2 or more days. Keep using it as such, and see where it goes.
Android OS Battery bug
Hi!
1. Install SystemPanelLite Task Manager from the market.
2. Run SystemPanel and open settings and check the "System processes" option. Close settings.
3. Scroll down in the process list until you find the process "android.process.media". If you have a CPU usage of more then 10-30s and the process usage gauge to the left moves up and down you probably have the Android OS battery bug.
At this point you can try the following;
- Shut down your phone. (Not just turn it of. The complete shut-down-power-off-thingy)
- Remove your external SD card.
- Start up your phone again.
- When the scan media is complete, do step 3 above again. If you don't see the problem at step 3 your SD card has a corrupt filesystem. And needs to be reformated. Follow these steps;
- Backup your data first!!!
- Settings -> SD card & phone storage
- Unmount SD card
- Format SD card
- Restore files from your backup.
If the problem persists your internal SD card might have a corrupt filesystem and needs to be reformated. Follow these steps;
- Backup your data first!!!
- Settings -> SD card & phone storage
- Format internal storage
- Restore files from your backup.
More details; What happens when you have a corrupt filesystem is that android.process.media tries to read a file but fails over and over again. The filesystem might not look corrupt to you. And you can read and write files on the SD card without problems. But at some point the android.process.media failes to read the files and loops like crazy, draining your battery.
I had a corrupt filesystem (FAT32) on my external SD card. I also had Android OS battery usage of 60-70% and a fast draining battery. I hope this can help others.
Best regards,
/Pontus
cos & yoshi
cos dds sucks battery.... yoshi"s awesome..!! fr battery!!
if you applied a theme in theme chooser it could have affected it
7 hours off fully charged battery since the upgrade completed, and down to 10%. Anyone else with battery life issues since receiving the OTA?
edit: phone temperature also runs very hot now since the update-- Gingerbread was quite a bit cooler to run.
I briefly ran the 217 OTA build before installing safestrap and rolling to a Cyanogenmod image.
I noticed that my phone was MUCH hotter than it had been while running the older GB-based rom -- however, I can't comment on the battery life itself.
mattvirus said:
I briefly ran the 217 OTA build before installing safestrap and rolling to a Cyanogenmod image.
I noticed that my phone was MUCH hotter than it had been while running the older GB-based rom -- however, I can't comment on the battery life itself.
Click to expand...
Click to collapse
I've been running .217 leak for a few weeks, and found that if you have a lot of MP3s on an SDcard, the phone will run really hot while it builds the MP3 database.
mattvirus said:
I briefly ran the 217 OTA build before installing safestrap and rolling to a Cyanogenmod image.
I noticed that my phone was MUCH hotter than it had been while running the older GB-based rom -- however, I can't comment on the battery life itself.
Click to expand...
Click to collapse
It does indeed run much hotter with the screen on. Are you experiencing heat issues with Cyanogenmod, or was it only under the 217 OTA?
edit: added quote for context
danifunker said:
I've been running .217 leak for a few weeks, and found that if you have a lot of MP3s on an SDcard, the phone will run really hot while it builds the MP3 database.
Click to expand...
Click to collapse
Was it a one-time or some-time thing, or was the phone constantly hot? Did you remove any of the files, or was there a workaround to prevent building the database?
It's been stated that initially expect very poor battery life immediately after upgrading to ICS and I would expect heat to be another factor as the CPU is in constant use updating all the new databases, sync'ing etc...that is going on.
(stated in the Motorola soak test forums to expect this).
tcrews said:
It's been stated that initially expect very poor battery life immediately after upgrading to ICS and I would expect heat to be another factor as the CPU is in constant use updating all the new databases, sync'ing etc...that is going on.
(stated in the Motorola soak test forums to expect this).
Click to expand...
Click to collapse
+1 its expected. I always try to give new roms/updates at least 3 or 4 days to smooth itself out. Especially when upgrading from cupcake to froyo to gingerbread to ics.......
Sent from my DROID4 using xda premium
vprasad1 said:
Was it a one-time or some-time thing, or was the phone constantly hot? Did you remove any of the files, or was there a workaround to prevent building the database?
Click to expand...
Click to collapse
Mine ran hot for a day. The next day I restarted it and haven't ran hot for a while.
Sent from my XT894 running ICS
Yeah it should be better after a couple of three days. I can get 14-16 hours on network and 25-30 hours when on steady wifi.
vprasad1 said:
It does indeed run much hotter with the screen on. Are you experiencing heat issues with Cyanogenmod, or was it only under the 217 OTA?
edit: added quote for context
Click to expand...
Click to collapse
It ran quite hot in the 217 OTA itself. Once I flashed over to cyanogenmod, it got cooler and has been running at roughly the same temperature as when i ran the GB rom.
I have very few MP3's on the SD card. It's actually the card from my old D1 and mostly has nandroid and titanium backup data on it
Odd, I haven't noticed any increase in heat, battery life is still good for me.
Upgraded OTA on monday, so 2 days now. I have a 32gig sd card, and the internal sdcard and the 32gig are loaded full of mp3's, a few videos, and titanium backups.
I want to say battery life is better than normal. But I believe this is only due to fixing a few issues over the weekend with misbehaving apps.
tcrews said:
It's been stated that initially expect very poor battery life immediately after upgrading to ICS and I would expect heat to be another factor as the CPU is in constant use updating all the new databases, sync'ing etc...that is going on.
(stated in the Motorola soak test forums to expect this).
Click to expand...
Click to collapse
Alright, it's been four days and battery life still sucks-- the phone is now only charging to 60% capacity, and phone spontaneously reboots, runs hot and apps still crash... and then I read that V217 OTA is halted due to "software issues"-- what recourse do I have? I don't pay "insurance" (which works out to the price of a new phone in 2 years). Will VZW address or swap the phone given that this power issue and phone instability was due to software upgrade they prompted on the phone?
Strange... Powered off the Droid 4 before bed and plugged into charger. Woke up and it was at 100%. Powered on, rebooted into safestrap/cwm and wiped cache, Dalvik, and battery stats. Rebooted and left it on charger, in case of quick drain again.
Will see if wife still experiences issues during her day. If so then this is most likely software or OS issue and after I get home from work I'll have to try backup and FXZ to see if a clean OS and gradual install of apps / restore some old data resolves the issue.
Step 1 is hunting down D4 FXZ threads on XDA and checking what's involved.
Sent from my ADR6425LVW using Tapatalk 2
I've been finding that the battery life and heat has improved for me since installing the OTA. I came from stock, rooted, Gingerbread 219. For the past month or so, I had been noticing that my phone was getting very hot just by charging it (could be due to some app that I couldn't narrow down), but that stopped after the ICS OTA.
Additionally, after the last GB OTA, I noticed that the keyboard lighting would shut off even in complete darkness. That also seems to be fixed with the ICS OTA.
Sent from my DROID4 using xda premium
I've had a couple of interesting issues since I updated this morning. First, my media files on my microSD card "disappeared" in that My Gallery no longer displayed pix and vids on the microSD card and Winamp couldn't find any of my MP3s. A reformat of the card seems to have fixed it, for now.
The other issue is that the battery seemed to drain much more quickly than it did when I had Gingerbread. I hope what was said here about that being the case for about the first day or so is true. I would hate to think that this is the nature of ICS.
Didn't do the FXZ / destructive reinstall yet; was doing some more investigation last night-- phone was draining about battery 10% every 10 minutes. The only two things showing under Settings-->Battery were Screen at 60% and Media com.motorola.android.omadrm at 40%. Rebooted, set to charge before bed and now this morning I see other items listed under battery: Android System, Android OS, Mail. Phone is now at 80% battery running on battery for the last 30 minutes. When the screen goes off and I turn it back on, I sometimes see "Battery Extender" flash in the status bar.
Did an
Code:
adb reboot bootloader
to get to the bootloader. Then did a
Code:
fastboot devices
and saw that the phone was listed. Launched RSDLite and flashed the fxz xml.zip file and all seemed well...
phone started up, there was a little android icon with gears spinning inside of it and a progress bar crossing. phone rebooted again, "optimized" android applications, and finally came back to the same system as before-- nothing got wiped. I guess I'll have to do a Settings/Privacy/Factory Reset to get an actual wipe.
Rather than doing a wipe, debating setting up safestrap, going to the safe partition and installing an alternate ICS ROM.
Before going that route at all, there are 27GB of about 7000 mp3 files on the external SD. I'm going to pull the external SD and see how battery life is first.
No battery benefit after pulling out the external SD card; still about 10% battery drain every 10-15 mins.
Did the Settings/Privacy/Factory reset-- currently at 30% drain in 120 minutes. Seems improved, but this is also without the external SD in the device.
Saw a few different things in forums, including searching through some of the alternate ROMs for D4 and looking at some of the Razr ICS upgrade battery issue complaints:
--some said they were having battery issues until doing factory wipe and then reinstalling apps from Play Store without restoring old data
--some said there was something stuck on their external sd that required a full re-format and then restoring data back to the external sd which returned battery life to "normal"
--others said that media indexing is taking place and to give it a few days (seriously? is there no way to disable this or uninstall whichever application is doing this??? the wife said she wouldn't mind scrolling through folders rather than having fully indexed media by artist/album/genre)-- And she raises the valid point, "It used to work fine before!" What changed between Ginger Bread and Ice Cream Sandwich to require this much indexing and what's the fix for it given that people can't return back to GB? Which QA engineer at Verizon/GoogleRola thought it would be a good idea to release an update with this massive issue? Is the intent to discourage people from listening to their locally stored music and to have them rely on data plan intensive "cloud services"? Is there some application that can do the indexing on a more powerful machine like a PC and then upload the indices / export databases to the phone?
140 minutes at 60%-- still at full factory resetted stock from this morning, no external SD card in phone, no media on internal SD card.
I suppose Plan B is to call Verizon and tell them that the battery life is complete crap since their update and to request a CLN-- hoping that it's not running ICS.
to clarify: no apps have been restored / reinstalled-- what on earth could possibly be digesting battery like this?
edit: saw someone's post suggesting settings/more.../mobile networks/network mode - preferred network = LTE/CDMA instead of Global. Giving that a shot.
Not sure what did the trick, but after observing 4 hours at 60%, and Disabling a bunch of the bloatware, re-added the external memory card (with all gazillion mp3s on it) and began installing previously used software. A charge later and a few reboots after, was getting 4 more hours with battery at 90%. No idea what did the trick as I ran through too many variables and never reset them to be able to isolate one specific one.
Good luck to anybody else that may experience this issue in the future.
Thanks for the report. I too did the factory reset and reformatted my card. I think I've had a tiny bit of improvement, but still go down to about 60% capacity after two hours away from the charger with moderate use (Facebook, Twitter, Tapatalk, etc., no streaming or media play). I have my display set to auto, have changed the radio to CDMA/LTE only and have disabled as much bloatware as I can. I'm now trying the battery training FoxKat recommends to see if that will help.
Hello and sorry if this question has been asked before. Couldn't find one that matches.
The thing is last night, around 00:00 am I went to bed and my phone was fully charged (probably not full but 90% at least, I'd left it charging the entire evening up to 23:00 pm). Then at around 5:00 am I woke up and noticed the phone had less than 15% battery left and, what worries me, a Filesystem almost full notification.
I charged the phone until 8:00 am and the battery behavior has been normal for the entire day. However the storage full notification is still there (tried rebooting but couldn't get it to go). The thing is I don't have that many apps installed and I don't download many things into the phone. Only WhatsApp's videos and images. That was the first place I looked into, but its Media folder was less than 200 MB, which shouldn't hog the entire internal storage (5.5 GB reported by Android).
Perhaps (probably actually), I'm being too paranoid, but I think something of great size may have been downloaded last night which drained the battery. Is there any easy way to list the folders by size? I've tried dozen of apps that claim to do this, but always summing the sizes of the folders was way less than the filesystem capacity. I tried to do it mounting the device in my Debian machine but couldn't manage to do it at the time, but with some assist, I think that last way could be the way to go.
- Has anyone experienced the combination of battery drain + full storage without any other notification?
- Can someone help me in tracking internal storage usage?
My Moto G (2014) is unrooted and running official Marshmallow from Motorola.
In any case, thank you for your time if you've read until here.
Cheers,
I still haven't figured out why the battery drain. The storage problem was Messenger App (stupid Facebook). It was using 1.9 GB. Android (stupid Google LOL) was reporting 70MB (didn't have any photos or videos, as Messenger for this just sucks). Don't know why it the storage demands increased abruptly, but anyway, the symptoms seem over.
Anyway I'm starting using DISA for Facebook messaging service. I think Facebook Apps are a complete piece of utter and unoptimized crap, and noticed just yesterday of project DISA.
I have a T713 on Android 7. Once the battery level is below about 80%, the tablet will often crash into a bootloop when switching between screens/apps (not while using one app).
When the battery is below 45% it will always crash as above (e.g. wake the tablet to home screen, see that battery is 45%, launch an app = bootloop).
The only way to stop the bootloop is to plug in the tablet. On mains power, the tablet doesn't crash.
I've done a factory reset, wiped cache (after using it a while, of course), tried Safe Mode. Makes no difference. The crash is always reproducible below 45% battery. Battery charge logging does not show any sudden drop in battery reading immediately before/at/after the crash.
The Accubattery app says the battery is at 82% health.
There are reports of similar phenomena in other threads and sites, usually attributed to the battery, but I am sceptical that this is the issue because there is little evidence that people actually solve it by replacing the battery (and the symptoms don't seem to support the basic assumption that there is a loss of power). Any experiences/ideas?
bloomer2011 said:
I have a T713 on Android 7. Once the battery level is below about 80%, the tablet will often crash into a bootloop when switching between screens/apps (not while using one app).
When the battery is below 45% it will always crash as above (e.g. wake the tablet to home screen, see that battery is 45%, launch an app = bootloop).
The only way to stop the bootloop is to plug in the tablet. On mains power, the tablet doesn't crash.
I've done a factory reset, wiped cache (after using it a while, of course), tried Safe Mode. Makes no difference. The crash is always reproducible below 45% battery. Battery charge logging does not show any sudden drop in battery reading immediately before/at/after the crash.
The Accubattery app says the battery is at 82% health.
There are reports of similar phenomena in other threads and sites, usually attributed to the battery, but I am sceptical that this is the issue because there is little evidence that people actually solve it by replacing the battery (and the symptoms don't seem to support the basic assumption that there is a loss of power). Any experiences/ideas?
Click to expand...
Click to collapse
Have you reinstalled the factory image with Odin? That would be the logical place to start.
sliding_billy said:
Have you reinstalled the factory image with Odin? That would be the logical place to start.
Click to expand...
Click to collapse
Thanks for your suggestion. The device is currently stock, unrooted. Could you tell me why using a factory image could help? (The last official update to firmware on the device was a long time before this problem appeared in March this year.)
bloomer2011 said:
Thanks for your suggestion. The device is currently stock, unrooted. Could you tell me why using a factory image could help? (The last official update to firmware on the device was a long time before this problem appeared in March this year.)
Click to expand...
Click to collapse
Like any device, who knows what has managed to get jumbled up in the image. Security patches and other updates can only overwrite so much since they are doing in place updates. Even a factory reset has to be pulling the image from the device itself where a factory image is completely clean. I know it is a PITA to set a device up again, but the fact that you can do the system stuff before installing any apps or files or anything and then see if the problem shows up immediately after imaging. If so, then you pretty much have narrowed it down to at least a hardware problem and you have less places to look (the battery for example). The last time I flashed the stock image a month or so ago, it took a security updated Feb 2019 (maybe) before I rooted and such putting it in the "modified OS" world where it will not get updates again until I flash stock again. The last actual OS update might have been around the end of 2017 beginning of 2018. Too bad since the device can clearly run builds past Nugat and has never been deprecated.
sliding_billy said:
I know it is a PITA to set a device up again, but the fact that you can do the system stuff before installing any apps or files or anything and then see if the problem shows up immediately after imaging. If so, then you pretty much have narrowed it down to at least a hardware problem and you have less places to look (the battery for example)
Click to expand...
Click to collapse
Thanks for the extra info! I'll look into doing that.
A preliminary update, in case anyone visits this thread before I finish thorough testing:
The cause is emphatically NOT the battery. After reflashing firmware and then doing a factory reset, as sliding_billy suggested above, I am unable to reproduce the problem. The tablet appears to be working fine in its current fresh state, even running on low battery power. I'm now planning to gradually reinstall apps and system updates (if any) and continue testing.
bloomer2011 said:
A preliminary update, in case anyone visits this thread before I finish thorough testing:
The cause is emphatically NOT the battery. After reflashing firmware and then doing a factory reset, as sliding_billy suggested above, I am unable to reproduce the problem. The tablet appears to be working fine in its current fresh state, even running on low battery power. I'm now planning to gradually reinstall apps and system updates (if any) and continue testing.
Click to expand...
Click to collapse
Glad that at least the initial solution is working. We'll see as you reinstall apps and complete any settings if it really was that "simple."