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.
Related
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
I've seen threads with this issue or that issue, but no single thread yet dedicated to issues that have cropped up for HTC Vivid users since the ICS OTA update.
I run stock-- No root, no custom rom, just stock the way it came from AT&T.
The phone has been wonderful. Battery standby time was phenomenal (on a full charge, I could expect to take my phone to work around 6:30 am, and see a minimum 60% to 75% left when I got home around 5:30 pm). I never experienced random reboots, crashes, etc.
Then I updated OTA to the new ICS using standard AT&T procedure-- This would be the official release, downloaded and installed last week.
Now, if I reboot the phone, I have to wait while it installs updates it already had when I installed ICS. This is a minor incovenience, but annoying.
I also see noticeably less standby time. I'm lucky now to have 50% left when I get home from work.
Most alarming, though, is the nightly crash on the charger. My dad is in and out of the hospital with heart issues, so turning off my phone to charge it isn't really an option. Every night since I updated, my phone random reboots on the charger (last night it did it twice).
So now I'm seriously wondering:
(1) Is anyone else having these new issues since updating to the official ICS release?
(2) Is there some way I can "downgrade" to the more stable version my phone had before (the extra features and tweaks aren't worth the tradeoff for stability and standby time)?
Thanks to any and all who take the time to consider this post and reply accordingly.
Why not try downloading the official RUU since you are still locked,
http://www.htc.com/us/support/vivid-att/downloads/ and install it
sounds like something scewed up when you uploded the OTA update via phone.
A little more detail...
I think it's important to note that these random reboots I've been getting since upgrading to ICS are only partially random.
They only happen when the phone is on the charger and "on." I recall a "charge death" issue with my old Samsung Captivate that perhaps I'm experiencing now with the upgraded HTC Vivid?
I know the obvious workaround is to charge it before going to bed, take it off the charger, then top it off the following morning. Perhaps I'll try that before doing the upgrade over again using the RUU. It's perplexing due to when it happens-- I know the phone doesn't require a full 3.5 hours to charge from, say, 35%, so it's some sort of charger keep-alive that must be forcing the reboot.
I'm still curious, though, to learn if anyone else is having these exact same issues after upgrade.
Thanks, Pumpiron579, for your suggestion! I've just downloaded the RUU and have it ready when I decide to try the update again.
I've upgraded to the latest ICS from AT&T and am not experiencing any of the reboot issues that you're speaking of. I put my Vivid on a charging dock and it goes into doc mode and is that way when I wake up in the morning. I even have it trip an alarm at 7AM. If it's rebooting overnight, I'm not aware of it. In GB there was a screen that told you the up time and sleep time. I can't find it on ICS otherwise I could confirm whether or not it is rebooting overnight.
As for battery life, it doesn't appear to be any worse than GB for me and for today, It's been on the battery over 1.5 hrs and still at 100% battery.
mug318ca said:
I've upgraded to the latest ICS from AT&T and am not experiencing any of the reboot issues that you're speaking of. I put my Vivid on a charging dock and it goes into doc mode and is that way when I wake up in the morning. I even have it trip an alarm at 7AM. If it's rebooting overnight, I'm not aware of it. In GB there was a screen that told you the up time and sleep time. I can't find it on ICS otherwise I could confirm whether or not it is rebooting overnight.
As for battery life, it doesn't appear to be any worse than GB for me and for today, It's been on the battery over 1.5 hrs and still at 100% battery.
Click to expand...
Click to collapse
Menu - Settings - Power - Battery Use
Select the Up time counter for more details
Thanks for that, homeslice, but I don't see overall up time. With GB, there was some counter that could show the hundreds of hours that it has been up since the last reboot.
mug318ca said:
Thanks for that, homeslice, but I don't see overall up time. With GB, there was some counter that could show the hundreds of hours that it has been up since the last reboot.
Click to expand...
Click to collapse
I've never paid too much attention to this...but when you go in and click on the battery time underneath the battery level, there's another uptime below the graph that i figured was total uptime?
I updated with the RUU and have had no problems with my phone what so ever, I have had no reboots when chargeing and the battery life is about the same for my phone.Also my phone is stock with bootloader locked.
My battery life seems to be about the same. However, I am getting a better LTE signal - 3 bars vs 1-2 bars before the upgrade.
The one thing that I've found to be an irritation is that before the upgrade, any photos attached to emails were automatically saved in a folder accessible by the Gallery. After the upgrade, they are saved in the Downloads; and that folder is not accessible from the Gallery. I have to use a file manager program like Astro to manually move the photo file to one of the Gallery accessible folders.
If there's a way to fix this, I would be all ears.
Battery life sucks after ICS upgrade
after I upgraded to ICS my batter life sucks, it used to come for a day, now its reaching 15% before evening.
Is this a known issue, is there a way to get a better battery life
Thanks
everything is fine fore me except the android is upgrading part every power on.
is that a problem?
houstonsveryown said:
everything is fine fore me except the android is upgrading part every power on.
is that a problem?
Click to expand...
Click to collapse
It's not a problem but a feature for all ICS installations.
mug318ca said:
It's not a problem but a feature for all ICS installations.
Click to expand...
Click to collapse
As far as I can tell you get the android is upgrading/optimizing every time dalvik cache is cleared..which from what I can tell happens on every reboot with a Rom that's not deodexed..like the stock Roms. Get on a Rom that's been deodexed and this won't happen. Otherwise enjoy the feature lol
Sent from my HTC PH39100 using xda premium
fix battery issues
Sorry to hear about the random reboots, and I hope a solution comes around. I personally have found no reboot issues at all. There is a problem with using Bluetooth hands free though, you can't press the call button on the device to make a voice call because Android removed the voice dialer so now you just hear a beep.
In regards to your battery, install Advanced Task Killer from the market. In the settings, set up the recommended kill list, the aggressiveness, and activate auto kill. I've been using it for a while and i can go all day with Bluetooth, Wi-Fi, Pandora, and other apps. After 10+ hours at work i get home with 35-40% battery still. Hope this helps. It also has a widget you can out on a homescreen so you can simply click and it kills what you set up already.
I used to have some random reboots in GB, turned to be an app or a widget that caused the problem. I did then a wipe amd installed minimal apps that I needed and didn't have the problem anymore. Then I started to install other apps one by one monitoring which one might be the problem, but I couldn't replicate it nomore. It was in the same time I experienced multiple (if not all of them) launchers and widgets so I don't even remember what I really had on it. This also might be for battery life too. Now I only use sense and the stock widgets and adw ex once in a while, I have >180 apps installed and no reboots and also battery life is very good.
Sent from my HTC Vivid via Tapatalk
Twice while streaming pandora over bluetooth I've had the phone just die. My music shuts off, screen is off, phones not responding, have to pull the battery. Also I've had issues with music skipping on bluetooth. Also third party apps won't show contact pictures that rely on Facebook. Worked fine before the
Update. Im considering wiping it and reinstalling everything.
Sent from my HTC PH39100 using XDA
Total newbie...delete if necessary
Downloaded the update last night and haven't sleep trying to fix this (OCD )...
I cannot see any updates on FriendStream event though I have my FB account linked to it.
I removed my FB account from "Accounts & Sync" synced it again received a notification "Allow HTC sense to access your FB account" and before Im able to click it the program keeps running and adds my FB account. Go to FriendStream and nothings there...
Found my issue
I have uninstalled few apps, seems to be that drained my batteries all day, now it looks better
Same Issue
WirelessMike said:
I've seen threads with this issue or that issue, but no single thread yet dedicated to issues that have cropped up for HTC Vivid users since the ICS OTA update.
I run stock-- No root, no custom rom, just stock the way it came from AT&T.
The phone has been wonderful. Battery standby time was phenomenal (on a full charge, I could expect to take my phone to work around 6:30 am, and see a minimum 60% to 75% left when I got home around 5:30 pm). I never experienced random reboots, crashes, etc.
Then I updated OTA to the new ICS using standard AT&T procedure-- This would be the official release, downloaded and installed last week.
Now, if I reboot the phone, I have to wait while it installs updates it already had when I installed ICS. This is a minor incovenience, but annoying.
I also see noticeably less standby time. I'm lucky now to have 50% left when I get home from work.
Most alarming, though, is the nightly crash on the charger. My dad is in and out of the hospital with heart issues, so turning off my phone to charge it isn't really an option. Every night since I updated, my phone random reboots on the charger (last night it did it twice).
So now I'm seriously wondering:
(1) Is anyone else having these new issues since updating to the official ICS release?
(2) Is there some way I can "downgrade" to the more stable version my phone had before (the extra features and tweaks aren't worth the tradeoff for stability and standby time)?
Thanks to any and all who take the time to consider this post and reply accordingly.
Click to expand...
Click to collapse
I am having the same issue. I am working with HTC on this issue. I have no idea what is causing this. You will find that it does it more frequently, not only when it is charging.
WirelessMike said:
So now I'm seriously wondering:
(1) Is anyone else having these new issues since updating to the official ICS release?
(2) Is there some way I can "downgrade" to the more stable version my phone had before (the extra features and tweaks aren't worth the tradeoff for stability and standby time)?
Thanks to any and all who take the time to consider this post and reply accordingly.
Click to expand...
Click to collapse
So are we able to go back to the Original Stock/Shipped Rom if we don't like this update?
I saw some things I liked about it in the recent reviews, but others that I didn't.
Hi all,
I have weird battery issue with my Razr i xt890 and I'd like some help. I have tried googling for information, but there's too much noise and I can't find anything suitable.
I'm asking on this site because I know the people on here are really knowledgeable.
My Razr i (with Jelly Bean) seems to have erratic battery readings. Sometimes it'll drop to 6%, and then go up to 90%, and jump around to points in between. I have even seen it drop to 1% and then go up to 6% (or something like that).
Needless to say, this makes the phone unusable because I don't know when it's on low battery so I can charge it. Furthermore, twice, it has reported low battery and then automatically shut itself down.
I hope someone can help with this, because I'm really stuck. I bought this phone overseas, and I don't really want to send it back overseas for warranty repairs.
So, some history.
Before the issue:
This is a stock Razr i, running Retail GB software. When I bought it, it was running 81.5.31002.Retail.en.GB 4.0.4. I upgraded to 81.5.39001.Retail.en.GB 4.0.4 and it's been running fine until this issue happened. I normally get about 4.5-5.5 days of battery before I recharge the phone.
This is stock software. No root. No bootloader unlock. No custom roms.
The issue:
I charged up my phone yesterday, and unplugged it from the charger at 100% battery. There was a notification that 91.2.29001.Retail.en.GB 4.1.2 was available. I selected 'Later' because I was busy at the time.
A bit later (maybe about an hour?), I went back to the phone and checked for updates, and selected to download the update. After it was downloaded, I noticed the battery was about 95%, and then I proceeded to install.
I figured 95% power should be sufficient to perform an upgrade.
The install took, maybe 10-15 minutes? At first glance, it seemed successful, but when the phone started up again, the battery reading was at 100%.
I distinctly remember thinking 'This is impossible. There's no way it could be 95% before the install, and 100% afterwards'.
I played around with the phone a bit (to try out Jelly Bean), and after a few minutes, the battery reading dropped to 60% or something.
That's when I knew something was wrong.
Since then, the phone battery reading has been erratic. If I plug it into a charger, it takes a few minutes and then shoots up to 100%. Unplug it, and it drops to a low level within minutes, and then goes up and down like a yo-yo. Twice, the phone went to a very low level, and then shut itself off.
I've tried various charging/unplugging cycles, and nothing has worked yet (Although I didn't have the patience to try an 8-hour charging cycle yet).
Please see the attached images to see what I mean.
The graphs are just bizarre.
I also did a factory reset (from the Privacy menu rather than 'recovery') but that didn't help.
At the moment, I haven't tried to root the phone or unlock the bootloader. I am still keeping the option of warranty open.
I can't think of a reason why this is happening. It doesn't seem to be a simple calibration or battery stats issue. I think the battery is working okay (because it was fine before the upgrade), just that the readings are wrong.
The phone is operating okay in all other respects. If I ignore the battery readings and the 'low battery' alerts, the phone continues to work ... except when it shuts itself down.
Another theory could be that ... because I upgraded without plugging the phone in, perhaps there was insufficient power during the upgrade and caused some corruption, and I have a faulty software/firmware? Not sure how I could test that though.
Any ideas, any one? Please?
Possibly related:
[Q] Randomly auto shutdown (battery problem)
http://forum.xda-developers.com/showthread.php?t=2195878
[Q] New phone battery jumping after JB
http://forum.xda-developers.com/showthread.php?t=2198772
MemendF Ranck
Looks like other people have a similar problem too.
Battery Fluctuation and Random Power off after JB
h t t p s:// forums.motorola.com / posts / cd3c7d3210
Jelly bean download issues
Hi, I have had exactly the same problem after downloading jelly bean. It even died when plugged in charging. As I had only had the phone for three weeks, I took it back to the shop, Phones 4 You, and they exchanged it for a new phone and told me not to download jelly bean until they let me know it's safe to do so. They said that it was a software problem. Prior to this the battery life was outstanding and I am very pleased with the phone. Phones 4 You gave me an excellent service.
Fixed!
For future readers ...
Someone on the motorola forums (see second reply on this thread) mentioned a possible solution which was to manually install the Jelly Bean version again. I decided to give this a try.
After some more research, I discovered that it should be possible to manually apply official Motorola (ie. OTA) updates using the stock bootloader (via the bootloader recovery feature). No unlocking, no root needed.
I gave this a try ... downloaded the software (keeping to the same version), placed it on an SD card, went to recovery and selected 'Updated from external card' (or something like that) and followed through ... and it has worked (Although this time I kept the phone connected to a usb cable throughout the upgrade). My battery readings are back to normal again. I didn't lose any data or apps as a result of this 'manual upgrade'.
And I am presumably still under warranty since I didn't root nor unlock the bootloader.
Other readers may consider trying this for themselves, however, I cannot guarantee that it will work for them. I can only say it worked for me.
Some references:
How to enter stock recovery in JB (razr i)
http://forum.xda-developers.com/showthread.php?p=38873652
(Apparently entering into stock recovery differs slightly between ICS and JB.)
The Unofficial Thread of Official OTA Updates
http://forum.xda-developers.com/showthread.php?t=2028814
I used the software package from the first post of this thread, labelled as 81.5.39001-91.2.29001.Retail.en.GB 4.0.4-4.1.2 (even though the filename is Blur_Version.81.5.39001.XT890.Retail.en.GB.zip).
I don't have the phone yet (supposed to get it tonight) but having read quite a bit it seems Moto suggests a factory reset after upgrading to JB in order to sort out battery drain etc. I think I saw it in the battery stats thread in RAZR i general.
I send my Razr I back to Germany (living in The Netherlands myself) yesterday! Had the same problem, only my battery get down to 0% all the time, so the phone shutsdown itself every 1 minute till 1 houre. (I'm from the topic: Auto shutdown (battery problem). I think i get my new one next week on wednesday. Dus the JB software manualy update works for more people?
mo976 said:
I don't have the phone yet (supposed to get it tonight) but having read quite a bit it seems Moto suggests a factory reset after upgrading to JB in order to sort out battery drain etc. I think I saw it in the battery stats thread in RAZR i general.
Click to expand...
Click to collapse
I think the problems described in this thread are relating to strange battery spikes in percentage and not a general drain of battery.
The problem is that everyone seems to be different. Some people report these spikes, some people are reporting high drains (which turning off google now or factory reset seem to fix) and some people (luckily me!) have had no issues at all - just an even faster phone
I did do a factory reset, though not immediately after the first JB upgrade. It didn't help.
I think describing this issue as battery drain or high battery usage is not quite correct. The battery is actually okay*, but the phone's indication of the battery capacity jumps all over the place (and sometimes causing automatic shutdown). I can see how it can be confused with battery drain though, especially if people only observe the reading going down (but didn't see the reading going up).
* At one point, I kept the phone screen on as an attempt to drain the battery. I got about 6 hours screen time (ignoring the intermittent battery low warnings) before I gave up.
Since I now have a phone with JB which is working, my guess is that this bug may not occur in all phones with JB. Instead, it seems to be triggered by something that happens during an upgrade.
OTA to JB on xt890 = battery problems
flashsam said:
I think the problems described in this thread are relating to strange battery spikes in percentage and not a general drain of battery.
The problem is that everyone seems to be different. Some people report these spikes, some people are reporting high drains (which turning off google now or factory reset seem to fix) and some people (luckily me!) have had no issues at all - just an even faster phone
Click to expand...
Click to collapse
i have the same problem. factory reset did not help me and i feel i made a mistake i have choosen this phone.i had motorola mobiles before even bought one to my wife.i know that motorola has a conservative atittude.i thought giving them a last chance now i know it was a mistake
Thanks bengtan.
I was having similar issues and a manual install of JB appears to have solved the issue.
Have you had any luck fixing your phone? I have the same problem since a few weeks ago. Bought a new battery and tried two calibration programs, but the issue persists.
Same here. I am on KK 4.4.2 and have the problem since yesterday. What to do?
Same here, my ROM is cm-11-20160524. After 3 years of usage I thought it's the battery and replaced it with a new one but the issue persists.
This is very odd, I'm here after my dad has the same issue and it looks like I'm the 4th poster to report the issue within 50 days after the thread hadn't any replies for over 3 years! Did any of you recent posters resolve the issue? I had a spare Razr-i and my dad took it to a phone repair shop where they swapped both batteries and the issue was still the same with the other battery, so it seems it's nothing to do with the battery itself for all the posters here so far.
Was there some recent update that spiralled all the phones into the erratic behaviour recently I wonder?
I'm trying to advise my dad what to do:
Try fix the issue on his current phone and keep using relatively old tech phone
Use my spare phone (same type) and keep using relatively old tech phone and try sell old XT890 for parts
Upgrade to brand new phone with latest tech and do him for a few years longer than the XT890 would.
Any feedback appreciated!
The issue flatened a bit now. After 2 weeks of brave usage the phone keeps the charge now normally with rare drops in between. So it's still not on an acceptable level but improved magically. I do not understand the physics of this behavior.
I'm having the same strange behaviour since yesterday!!
battery level drops when pluggin the charger,
after several minutes level is jumping to 100%.
whith unplugged charger, level in general inconsistent jumping up and down...!
could this be SW related? planned obsolescence?
edit: android 4.4.2. systemversion 990.43.74.XT890.Retail.en.EU
I have the same problem following an update to JB I don't even recall authorising
I'm now looking for a copy of the new firmware: 990.43.74.XT890.Retail.en.EU to try to resolve. If anyone knows where it can be found I'd be very grateful if you could point me in the right direction...
Same problem here.
I bought a new battery. No changes.
I than did a complete wipe, unlocked the bootloader and installed CyanogenMod 11 (this one http://forum.xda-developers.com/razr-i/development/rom-unofficial-cyanogenmod-11-t2966855). No changes.
I than completely drained the battery (made sure of it) and left it on the charger over night. Now I don't get those weird spikes, the battery just drains really fast (about an hour an the phone is powering off).
Maybe I try a different ROM, or go back to KitKat
I found this but I dunno how to use it ??
h t t p s : / / forum .xda-developers .com /showpost.php?p=69816145&postcount=39
android 4.4.2. systemversion 990.43.74.XT890.Retail.en.EU
ok, I recently replaced my bionic due to a shattered screen. the one verizon sent me didn't come with a battery so I'm using the same old one. so when I rooted my phone on ics, a couple weeks later I noticed that my phone was taking awhile to recharge. with the battery hd app it said that from about ted percent it would take nearly 4 hours to charge! as opposed to the usual hour, hour an a half. then I updated to jelly bean an due to my internal storage becoming unmounted, I had to fxz an lost root altogether. so after getting my internal storage back an waiting what seemed like a month for a root exploit, my battery was back to charging normally, which was pretty sweet. so today I booted ubuntu an rooted my bionic using the samba exploit recreated by the master genius of moto exploits himself, all hail Dan! after playing around an getting back to my old setup I drained a full battery. I plugged in an yet again battery hd. is reporting a 4 hour charge time, plugged into ac! so my question is, does anyone know what could be causing this?! from what I know so far it seems that having root access is the cause. but I can't put the two together an understand how that is an I don't have the kinda time for a 4 hour wait on a charge....somebody help!
Try to delete the battery stats. Maybe the phone is traiting the battery like a 10000mah one and recharges it a while.
Let me know if it worked!
yea i tried that right off the bat. in recovery, with a battery calibration app, and manually. nothin helps
It could be one of two things: one, there could be a problem with your ROM's battery app, therefore displaying incorrect data. Another issue could be the battery itself, as these batteries degrade over time so it could have gone flat and no longer hold an efficient charge.
syung said:
It could be one of two things: one, there could be a problem with your ROM's battery app, therefore displaying incorrect data. Another issue could be the battery itself, as these batteries degrade over time so it could have gone flat and no longer hold an efficient charge.[/QUOTE
hopeully its just the rom. i'm installing safestrap right now so i can jump over to another one and see how the battery acts there, maybe help narrow it down. an now i'm thinking it probly is the rom as the battery holds a charge like it always has. it just charges super slow. if i use the wifi tether or download any big files such as a zip file for a rom, it actually drains the battery very slowly while plugged in to ac. around 1 percent every five or ten min, depending how much i have goin on at the time. i clearly remember when it started happening. i checked once and it showed a normal charge time between 1 an 2 hours. i fiddled around did some things, of which i now cant remember what i did (install apps for example) an ten minutes later it was in this state where it takes 4 hours to charge. i've tried deleting apps, calibrating the battery, hopefully it works normal on a different rom its turning out to be quite the inconvience. Thanks for you help and input!!
Click to expand...
Click to collapse
ok so I installed a different rom on the safe system using safe strap an I was still having issues. tried a different rom and same thing. I went back to the unsafe side and did a master reset on the stock rom and it seems to have fixed the problem. I'm curious to see what it is um doing that's causing it as this is the second time its happened. gonna pay close attention to the possibility of it happening again to hopefully pin point the origin.
Sent from my DROID BIONIC using xda app-developers app
If you tried various versions of different ROMs, and you're still experiencing the same issues, it's probably an issue with the hardware, so I would check the battery to make sure.
its back to normal now. But I'm still pretty curious as to how my stock rom was causing the problem across different roms even using safestrap. an fxz fixed her right up
Sent from my DROID BIONIC using xda app-developers app
Hello, I've been looking for solutions to this problem for a while now. Basically when my screen is on and system is awake the top part of my screen and backside will heat up to about 50C, it burns on the touch. Betterbatterystats gave a temperature of 52C and avg of 50. Needless to say, my battery also runs out very quickly like this, also dropping about 5% an hour when the screen is off.
Another thing I've noticed is that SDcard takes 25% of my battery usage, and when I go to storage settings, it will infinitely calculate. I mounted my storages and chkdsked them, fixed some corrupted files but the problem still persists. The only storage I haven't mounted is the internal storage, which I'm unable to do. I can't seem to connect to adb from recovery and mounting /data alone does nothing. After about 10 mins of using the phone, it becomes too hot(burns my hand) and it will shut down.
I've replaced 2 batteries so it's very unlikely that it's a battery issue. Also tried other chargers and wiping everything.
Phone OS: 4.1.2 stock LT5 before.
Did factory wipe/dalvik wipe + flash to CM11 4.4.4 and the problem is still present.
Betterbatterystats doesn't indicate a draining app, just high temperature.
Removing the external SD card and sim card had no impact.
I'm getting deep sleep when I turn off the screen, so it's not media scan being stuck. Mediascan disabled and problem still persists.
Pretty much out of ideas here, and hoping that you guys could help me out.
Any help is very much appreciated.
Poopfeast said:
Hello, I've been looking for solutions to this problem for a while now. Basically when my screen is on and system is awake the top part of my screen and backside will heat up to about 50C, it burns on the touch.....
Pretty much out of ideas here, and hoping that you guys could help me out.
Any help is very much appreciated.
Click to expand...
Click to collapse
It's not just you. I experienced the same, as have others, for example see http://forum.xda-developers.com/galaxy-note/help/process-bug-kitkat-roms-t2834819.
If you really need Kitkat I suggest Omnirom as it didn't have the heat issues when I most recently tried it out again, about a week or two ago. The other Kitkat ROMs I tried all turned my GT-N7000 into a hand warmer/hot plate, as did some older ROMs. There are good reasons why GT-N7000 is no longer officially supported in CM - really serious bugs with very few people still willing to try to fix them. Otherwise stock Samsung + root works great with no killer bugs and huge battery life Anyone still remember when this device first appeared and it was famous for having longest battery life of any smart phone? Run stock Samsung, rooted or not, and disable all the stuff you don't use, enable the power saving mode and it still is one of the best. Not kewl tho.....:laugh:
julian67 said:
It's not just you. I experienced the same, as have others, for example see http://forum.xda-developers.com/galaxy-note/help/process-bug-kitkat-roms-t2834819.
If you really need Kitkat I suggest Omnirom as it didn't have the heat issues when I most recently tried it out again, about a week or two ago. The other Kitkat ROMs I tried all turned my GT-N7000 into a hand warmer/hot plate, as did some older ROMs. There are good reasons why GT-N7000 is no longer officially supported in CM - really serious bugs with very few people still willing to try to fix them. Otherwise stock Samsung + root works great with no killer bugs and huge battery life Anyone still remember when this device first appeared and it was famous for having longest battery life of any smart phone? Run stock Samsung, rooted or not, and disable all the stuff you don't use, enable the power saving mode and it still is one of the best. Not kewl tho.....:laugh:
Click to expand...
Click to collapse
Thanks for your response. I wasn't aware of this situation. But I was having this heating problem on Samsung stock firmware 4.1.2 too?
edit: just flashed to omnirom and it's still burning my hand.
In the team win recovery repairing internal storage gives me the error: unable to repair /emmc, so I just wiped it, problem is still there.
Poopfeast said:
Thanks for your response. I wasn't aware of this situation. But I was having this heating problem on Samsung stock firmware 4.1.2 too?
Click to expand...
Click to collapse
The heat comes when the CPU is working at max. This should be quite rare but can occasionally go on for a long time, for example if there is a lot of media content to be indexed. This would usually happen for just a few minutes after booting. Example: I use Archos video player and it indexes 1000s of movies on my home LAN via smb or upnp - this adds some overhead at startup but then settles to zero impact. It can also happen on connection changes as these are a trigger for lots of apps/services to activate/phone home/update profiles or content and so on. You could also experience heavy load on CPU if your 3G connection and/or wifi signals are poor and the device is constantly seeking better signal.
Some stuff you can do:
in stock Samsung enable power save mode - this limits the max CPU state to 1000MHz.
in a rooted custom ROM you can use any of several utilities to do the same.
This makes near enough no difference to normal use but will just throttle back the CPU when it is trying to max out.
You can disable notifications for open wifi networks.
In stock Samsung you can safely disable any of the apps that you don't use.
In rooted custom ROM you can do the same but you also have the ability to disable stuff which you need just to boot to a working environment so be careful.
Disable GPS when you don't need it. Disable bluetooth if you don't need it.
and so on....
If you use an external microSDHC card try it formatted as exfat instead of fat32/vfat. There is a horrible bug with spontaneous unmounting of the extra cards but it works better if they are formatted exfat.
On rooted stock Samsung my Note runs nice and cool and just warms up a bit if I spend hours playing games. It never gets hot like it did with custom ROMS. If I get into a mega brain dead bug eyed game session with sound high and screen on and very bright I get about 6 hours battery life. If I use it a bit more normally I get anything from 10 to 17 hours between battery changes, with screen time between 3 and 6 hours, and that includes using batteries that are a couple of years old. I never even got close to this kind of performance with custom ROMs. YMMV etc.
julian67 said:
The heat comes when the CPU is working at max. This should be quite rare but can occasionally go on for a long time, for example if there is a lot of media content to be indexed. This would usually happen for just a few minutes after booting. Example: I use Archos video player and it indexes 1000s of movies on my home LAN via smb or upnp - this adds some overhead at startup but then settles to zero impact. It can also happen on connection changes as these are a trigger for lots of apps/services to activate/phone home/update profiles or content and so on. You could also experience heavy load on CPU if your 3G connection and/or wifi signals are poor and the device is constantly seeking better signal.
Some stuff you can do:
in stock Samsung enable power save mode - this limits the max CPU state to 1000MHz.
in a rooted custom ROM you can use any of several utilities to do the same.
This makes near enough no difference to normal use but will just throttle back the CPU when it is trying to max out.
You can disable notifications for open wifi networks.
In stock Samsung you can safely disable any of the apps that you don't use.
In rooted custom ROM you can do the same but you also have the ability to disable stuff which you need just to boot to a working environment so be careful.
Disable GPS when you don't need it. Disable bluetooth if you don't need it.
and so on....
If you use an external microSDHC card try it formatted as exfat instead of fat32/vfat. There is a horrible bug with spontaneous unmounting of the extra cards but it works better if they are formatted exfat.
On rooted stock Samsung my Note runs nice and cool and just warms up a bit if I spend hours playing games. It never gets hot like it did with custom ROMS. If I get into a mega brain dead bug eyed game session with sound high and screen on and very bright I get about 6 hours battery life. If I use it a bit more normally I get anything from 10 to 17 hours between battery changes, with screen time between 3 and 6 hours, and that includes using batteries that are a couple of years old. I never even got close to this kind of performance with custom ROMs. YMMV etc.
Click to expand...
Click to collapse
Thanks for taking your time to write this. I've already disabled GPS/sync and turned on power saving. Clearing the storage now lets android calculate properly, and the Media/sdcard is gone from battery usage. But it's still running very hot and draining. CPUspy says 20% on 1400 and the rest on 800mhz when I'm using it. The system is freezing often and generally really slow.
EDIT: just used eMMC check and it says I'm brickbugged :'(
type VYL00M
Ran the test but it says passed.
Temperature seems to drop to a reasonable 35C when I'm in airplane mode.
With everything on and sync off it's not going above 40C even when watching videos or something, so I guess it's all good now.
So basically what I've done to fix it:
Wipe internal storage and repair all partitions
Flash to OmniROM
Turn off Sync/GPS
Problem seemed to be mainly on the internal storage corruption, maybe related to my bugged chip.
Poopfeast said:
.....
EDIT: just used eMMC check and it says I'm brickbugged :'(
type VYL00M
Ran the test but it says passed.......maybe related to my bugged chip.
Click to expand...
Click to collapse
According to eMMC Brickbug Check my Note is exactly the same as yours - supposedly "Insane chip" but Memory check passed with no problems, and guess what? It works 100% perfectly running 4.1.2 rooted. I have the full capacity of storage available to me, apps do not freeze, everything works as good as new. It is absolutely stable and reliable and terribly boring (just how I like it). It never surprises me or does any weird stuff at boot or crashes or freezes. All the hardware features work, all the supported video and audio codecs and formats work, the networking is rock solid, I can rely on my VPN when away from home, GPS gets a fix in no time, battery life is excellent, video playback is great etc. etc..
I bought my 16GB GT-N7000 a few months ago, a used item on ebay. It is an unlocked retail UK item (boxed with all manuals, paperwork, accessories etc) so no network/vendor bloatware but it was supplied by the seller with Supernexus ROM installed and was obviously suffering from the usual problems often described by users of custom ROMs on exynos. After various frustrating episodes and trials of different ROMs I used ODIN 3.09 to flash an official Samsung ICS 4.04 firmware and 16GB pit file to restore the partition table and stock firmware. Then I ran Kies on Windows XP on the "virgin" restoration. It recognised the hardware and the firmware and notified me of the update to 4.1.2. I went ahead and updated over ethernet and also captured the official 4.1.2 firmware for purpose of backup.
Since then I have tried out various ROMs and have always been able to revert to stock Samsung 4.1.2 via ODIN and without going back to the scary brickbug "insane" ICS versions. As far as I can tell the brick bug is irrelevant if you aren't stuck on ICS. After trying numerous ROMs of various android versions I am in no doubt at all that if you spend half the time setting up a rooted stock Samsung firmware as most people spend setting up ROM X/Y/Z you actually get a much more reliable and useful device.
If you need a known-good pit file for a 16GB GT-N7000 you can use this: ftp://takla.linuxd.org/Q1_20110914_16GB.pit
I had a similar issue lately. Go to developer settings and activate the cpu load display. Processes and their cpu load along with a bar graph will appear on the screen. I found out that google's music app was hanging on my phone. This did not show up in BetterBatteryStats!!!