My touchpad has been draining battery even when off. You can see in the picture attached represented by the blank sections. The first blank section represents about a day of the device being off without use. And when I say off, I mean powered down through the menu, not just in sleep mode.
Anyone else seen this? Seems to be something that has recently started happening.
A little background, I was running one of the cm9 camera enabled nightlies, but wanted to try JC CM10 so used ACME Uninstaller to completely remove android. Then installed cm10 using ACME installer 3. Played with it for a few days then wiped and restored a cm9 backup instead to go back to ICS until cm10 battery is better. Since then, this battery drain has been happening even when off.
I didn't know something could be sucking battery even when device is off. Any ideas? Maybe I need to use unistaller again and start android install fresh again.
Sent from my cm_tenderloin using Tapatalk 2
On the battery does it show what apps are consuning most battery? Did this barely start? Maybe it's an app that is constantly gathering info from online. I know my Hotmail app use to drain my battery so I had to go stock email
Sent from my GT-I9300 using xda premium
This is all the info it shows for battery info. And I'm not sure how it could be an app. The tablet is powered off completely. Shut Down.
It's really very strange.
Sent from my DROID RAZR using Tapatalk 2
Unfortunately it sounds like the battery might physically be going bad. How long have you had it and does it spend a lot of time plugged in while in use?
Sent from my Galaxy S III using Xda Premium
It's a JB thing. This happens as well on my Nexus 4. It's not a battery drain problem, but more so battery reporting is a little messed up. At least that's what I've read in the N4 section.
Boot into Webos, get Dr. Battery app from preware and read what the health is. Mine is at 93%, I've had it for a little over a year and brand new it read 95%. If you're losing juice even when its completley off, I'd expect your percentage to be much lower. There's also not much that can be done about it since you can't recalibrate a TP battery.
This issue has been discussed before. It is not necissarily a defective battery and in some cases is just simply a case of how the TP is being "shutdown" it was noted over at webos nation that in some cases the TP was failing to FULLY powering down...perhaps due to some location reliant apps that maybe continued scanning if shut down from within android...This AFAIK has never been confirmed however the issue has now been Solved for some users over at http://forums.webosnation.com/hp-to...tery-drains-when-off-webos-3-0-5-problem.html
Try the "fix" on page 6 to see if it solves your issue.. Hope it helps
Pickens said:
My touchpad has been draining battery even when off. You can see in the picture attached represented by the blank sections. The first blank section represents about a day of the device being off without use. And when I say off, I mean powered down through the menu, not just in sleep mode.
Anyone else seen this? Seems to be something that has recently started happening.
A little background, I was running one of the cm9 camera enabled nightlies, but wanted to try JC CM10 so used ACME Uninstaller to completely remove android. Then installed cm10 using ACME installer 3. Played with it for a few days then wiped and restored a cm9 backup instead to go back to ICS until cm10 battery is better. Since then, this battery drain has been happening even when off.
I didn't know something could be sucking battery even when device is off. Any ideas? Maybe I need to use unistaller again and start android install fresh again.
Sent from my cm_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
I had this issue for months and decided to do some research to rectify the problem. My touch pad would lose charge from 100% to zero within ten days even when the device was turned off. Doesnt matter of i shutdown from cm or webos or moboot.
Here's what I did.
Basically I did a full clear reinstall of cm9 / cm10
1. Backup all apps and system data
2. Remove cm by using acmeuninstaller
3. Remove all folders (format) the hard drive
4. Restore webos to 3.0.0 using webos doctor
5. Reinstall cm
6. Restore backup data.
Afterwards I made some tests
Turned off touch pad at 100 percent each time from moboot cm and webos. Check back 4 days later. All good
zaqq1 said:
I had this issue for months and decided to do some research to rectify the problem. My touch pad would lose charge from 100% to zero within ten days even when the device was turned off. Doesnt matter of i shutdown from cm or webos or moboot.
Here's what I did.
Basically I did a full clear reinstall of cm9 / cm10
1. Backup all apps and system data
2. Remove cm by using acmeuninstaller
3. Remove all folders (format) the hard drive
4. Restore webos to 3.0.0 using webos doctor
5. Reinstall cm
6. Restore backup data.
Afterwards I made some tests
Turned off touch pad at 100 percent each time from moboot cm and webos. Check back 4 days later. All good
Click to expand...
Click to collapse
Thanks for the reply. Here is what I have done to get a start fresh.
1. Remove cm by using acmeuninstaller
2. In WebOS, installed "Remove Android" from Preware to wipe remaining Android boot stuff.
3. Followed this guide to repartition and restore 3.0.0 WebOS. http://forum.xda-developers.com/showthread.php?t=1426244
4. Factory reset to wipe everything again.
5. Performed system update to WebOS 3.0.5 (tried to upgrade through WebOS doctor 3.0.5, but would not boot. Restored back to 3.0.0 and went through System Update, and that worked fine).
What I plan to do this afternoon (didn't have time last night):
6. Install Preware, UberKernal, and GovNah (I like my WebOS to be at its fastest before a CM install, even if I never use WebOS)
7. Reinstall cm10 (JC Sullins 12/16), moboot 3.8.0, new CWM, and gapps using ACMEInstaller3.
8. Install apps fresh (don't really have anything where I need to restore data).
Once I do this, I'll run some tests where I leave it off for a couple days. I'll post back with results. Hopefully getting a fresh start will fix things like it did in your case.
synchron50 said:
Boot into Webos, get Dr. Battery app from preware and read what the health is. Mine is at 93%, I've had it for a little over a year and brand new it read 95%. If you're losing juice even when its completley off, I'd expect your percentage to be much lower. There's also not much that can be done about it since you can't recalibrate a TP battery.
Click to expand...
Click to collapse
Before I did all the wiping, I checked this and health is at 94%. So it shouldn't be a bad battery. I'll update on the results of the full CM and WebOS wipe.
Pickens said:
Before I did all the wiping, I checked this and health is at 94%. So it shouldn't be a bad battery. I'll update on the results of the full CM and WebOS wipe.
Click to expand...
Click to collapse
Mine has been doing the same thing. When I turn it off and leave it for a day or so, I have battery loss. I thank it started when the camera was added to CM9.
I am looking forward to seeing your results.
Pickens said:
Thanks for the reply. Here is what I have done to get a start fresh.
1. Remove cm by using acmeuninstaller
2. In WebOS, installed "Remove Android" from Preware to wipe remaining Android boot stuff.
3. Followed this guide to repartition and restore 3.0.0 WebOS. http://forum.xda-developers.com/showthread.php?t=1426244
4. Factory reset to wipe everything again.
5. Performed system update to WebOS 3.0.5 (tried to upgrade through WebOS doctor 3.0.5, but would not boot. Restored back to 3.0.0 and went through System Update, and that worked fine).
What I plan to do this afternoon (didn't have time last night):
6. Install Preware, UberKernal, and GovNah (I like my WebOS to be at its fastest before a CM install, even if I never use WebOS)
7. Reinstall cm10 (JC Sullins 12/16), moboot 3.8.0, new CWM, and gapps using ACMEInstaller3.
8. Install apps fresh (don't really have anything where I need to restore data).
Once I do this, I'll run some tests where I leave it off for a couple days. I'll post back with results. Hopefully getting a fresh start will fix things like it did in your case.
Click to expand...
Click to collapse
I have three touchpads and did exactly as you. Afew of my observations:
1. the 94% does not appeared to be measured. It is the current Voltage (expressed as mA's)/manufactorers hard coded spec, (6612mAh). If in Android, (I'm onCM 10+camera+gyro), using Battery Monitor Widget, I can adjust the actual to 6100, (or anything else), and get 6039/6100=99%
2. My discharge rate on WebOS in Airplane mode was arround -613 to -850mA. Screen on, (brightness affects this).
3. My discharge rate on CM10 in Airplane mode is about -520mA!!
4. A PC's USB port puts out 500mA's!!!
5. On the touchstone, (doesn't seem to matter if WiFi is on or off), with screen on 1/3 brightness + Battery Monito Widget = +853 to 945mA
6. On HP charger & cable, same as above = +1,377mA
What suprised me was the greater drain in WebOS.
I've had this issue since the beginning of installing Android on both my TP. Really annoying but I always assumed it was because of Android since I had no problems with WebOS.
I get battery drain when leaving the device unused, but it's significantly lower than it used to be in early stages of cm9 and cm10 development. I find it to drain slightly faster than WebOS but you have to remember this device was not designed around android.
This has not been a discussion of power loss in an unused state. It is power loss in an "off" state. Powered down with neither WebOS or Android running.
Sent from my DROID RAZR using Tapatalk 2
After doing all the wipes listed above, I ended up just putting the newest CM9 nightly (with GAPPS) and moboot 035 back on instead.
Results. I believe these wipes have fixed my problem. Here are some of my results:
Turned off at 96% for 18 hours, still at 96 when I booted up.
Turned off at 77% for 12 hours, still at 76 when I booted up.
Turned off at 56% for 12 hours, still at 55 when booted up.
Before I would have lost about 10-15% over these same time periods. Not seeing the drop at all now. And all of these power downs were on the Android side so don't believe the hype about Android power-down being the problem.
Sent from my DROID RAZR using Tapatalk 2
Pickens said:
After doing all the wipes listed above, I ended up just putting the newest CM9 nightly (with GAPPS) and moboot 035 back on instead.
Results. I believe these wipes have fixed my problem. Here are some of my results:
Turned off at 96% for 18 hours, still at 96 when I booted up.
Turned off at 77% for 12 hours, still at 76 when I booted up.
Turned off at 56% for 12 hours, still at 55 when booted up.
Before I would have lost about 10-15% over these same time periods. Not seeing the drop at all now. And all of these power downs were on the Android side so don't believe the hype about Android power-down being the problem.
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
I restarted from scratch and it worked. I turned my TP off for 2 days and the battery read 100% after boot. Thanks for the help.
Checking back after a few weeks, glad to see that the fresh install solved the issue for some of u guys
battery health 91 % DR battery
so this means my battey is going bad
had my tp for over a year now
is that normal ?
anyone ?
Not sure how you got that from this thread. Some people suggested it might be a bad battery, but I think our results with restoring our touchpads would show that wasn't the case.
Follow the steps in post 9 and everything should be good to go. Worked for me. No more battery drain issues while the device is off. I've even returned to CM10 and still no problems.
Sent from my DROID RAZR using Tapatalk 2
Related
I just installed CM7, came from the community rom 2.1.
I am suffering from severely reduced battery life. It appears that 30% of my battery used comes from cell stand by - which is unusually high under my standards. I am not sure what is causing this, time spent without signal is only 1% for me. If I turn off 3g and only run on wifi, it is the same thing so I feel like it has to do with the cell radio. I did a *228 option #2 - but nothing, cell stand by still consumes massive amounts of my battery life. Does anybody know what is causing this, or have experience on how to fix it?
Thanks in advance.
Is anybody experiencing similar problems?
What radio are you using? Cm 7 doesn't need to use the ec09 radio but I've had the best results with it.
what kernel are you running?
You may have something running in the background eating up batt life.
Run terminal emulator and type exactly this minus the parentheses
su (hit enter)
Dumpsys power (make sure the space its there and hit enter) you should see a value of zero on the last two lines if you don't have anything keeping your phone awake (this is what I suspect is happening) if it says anything other then zero do a search for poke lock or wake lock...there is a way to fix it...its just not coming to mind right now and I don't have my pc in front of me
Edit: if all else fails reboot to recovery via power button menu reboot recovery.
Wipe everything and flash again from the recovery that came with cm7
Sent from my SCH-I500 using XDA App
I am currently using ED01 for my radio. I hear good things about EC01, but I also heard it can junk your SD card - so I am not sure what to think. Will it only junk the SD card during the install, or can it do that at any time?
I am using the glitch kernel.
This is what I got:
mLocks.size=0
mPokeLocks.size=1:
poke lock 'PhoneApp' : POKE_LOCK_IGNORE_CHEEK_EVENTS
What are the effects of that pokelock? How long does it take the phone to go into deep sleep that is being prevented?
Thanks a lot for your help.
The ec09 radio is not gonna hurt your sd card...its ec09 rom
that eats cards so no worries there, but considering you have a poke lock on that is what us keeping your phone from deep sleep and draining your battery...if you get good signal currently, I would get that poke lock off, and not worry now about the modem being your number 1 battery drain, I'm not sure how to get rid of it but I know it was discussed here a month or so ago I'll see if I can find the fix...and deep sleep should happened a few minutes after your screen shuts off maybe less
Sent from my SCH-I500 using XDA App
I'll look, too. Let me know if you know how to get that poke lock to go away.
Thanks so much for your help =)
No problem, You could also try going into recovery and run fix permission and then after you boot do a dump sys power and you will probably see its at zero...call your phone and the wake lock will probably be back
I can't seem to find a fix other then doing a full data wipe and rom re flash...I'm just thinking out loud, but did you wipe everything before flashing cm7?...our did you restore apps with titanium backup? I'm running the 7/17 build with the glitch m.l. kernel and I have no poke locks, I know its a pain but I think it may be your best bet to re flash the rom use the kernel cleaning script or at least make sure you wipe everything and re flash
Sent from my SCH-I500 using XDA App
Yeah, I wiped data before. So you suggest wiping data again and reflashing the rom? I restored my apps with titanium backup. Also, since you don't have that poke lock, what is your battery life usually? How many hours do you get out of your phone? How much screen on time, etc.
Chiming in. I have the same problem. Used to get over 2 days on ComRom. Now i'm lucky to get 24 hours.
alemondemon said:
Yeah, I wiped data before. So you suggest wiping data again and reflashing the rom? I restored my apps with titanium backup. Also, since you don't have that poke lock, what is your battery life usually? How many hours do you get out of your phone? How much screen on time, etc.
Click to expand...
Click to collapse
When you do a batch restore with tI-bu make sure you only use restore user apps and make sure you always choose to restore just the app and not data also.its possible restoring data may be causing the poke lock? Especially if you restored old system files, you only want to restore apps with titanium that you downloaded on the phone, not apps that came with the rom. which is also why doing a full data wipe and re flashing may be your best bet
If I don't look at my phone at all I can go the whole day and only be down to 75% at dinner time, and I've also had days where I need to charge it by 4 o'clock from web browsing, texting, flashing roms, or having to boot to recovery a lot, also listening to music with out the charger plugged in (about 2 and a half hours between
Commuting and going to lunch.over all I get better battery life then I did on com rom and its way faster
Sent from my SCH-I500 using XDA App
My phone discharges about 35% when it sits completely idle (untouched) for 8 hours. It used to lose about 8% charge in the same amount of time.
Hi all, I'm running Cyanogenmod 6.5.7 and in the last couple weeks I've picked up my phone only to find it was off, not sleeping. It still has plenty of charge left (I can't remember when my phone last went below 50%), and it boots back up without a problem. You wouldn't know there was anything wrong except for the fact that it sometimes turns off on its own.
My first problem is that I don't know where to look to see what could be the trouble. It's running ADWLauncher EX. Beyond that and the OS I don't know what could be relevant. I switched to CM7 last month, up to then I'd been running GingerLOL and I never had this issue.
Any help or advice is appreciated.
The devs would say do a full format and flash and see if it still happens.
Sent from my LG-P500 using XDA App
if you want to know what is happening install logcat from market and check for errors..
i used it to know why mms wont downlaoad and logcat showed that mms ip is wrong and changed it and it works
Oneiros42 said:
Hi all, I'm running Cyanogenmod 6.5.7 and in the last couple weeks I've picked up my phone only to find it was off, not sleeping. It still has plenty of charge left (I can't remember when my phone last went below 50%), and it boots back up without a problem. You wouldn't know there was anything wrong except for the fact that it sometimes turns off on its own.
My first problem is that I don't know where to look to see what could be the trouble. It's running ADWLauncher EX. Beyond that and the OS I don't know what could be relevant. I switched to CM7 last month, up to then I'd been running GingerLOL and I never had this issue.
Any help or advice is appreciated.
Click to expand...
Click to collapse
Try tuning down your overclock frequency... if you have overclocked it... it sometimes happens cuz of that... if you havent overclocked then theres some other problem...
Sent from my LG-P500 using xda premium
samrox144 said:
if you want to know what is happening install logcat from market and check for errors..
i used it to know why mms wont downlaoad and logcat showed that mms ip is wrong and changed it and it works
Click to expand...
Click to collapse
I've done that, but does logcat hold on to recent logs automatically, or do I have to turn on "save to sd card"?
I think I might be having this same issue. I left my phone on and plugged in to charge not even for a half hour or less then I came back to it later and pressed the power button to try to turn it back on but it wouldn't turn on. Then I pressed and held it a second and it wouldn't turn on. I unplugged the battery then plugged it back in then it powered up fine. I seem to be having this issue every once in awhile and I am not quite certain why it is doing this. Also it seems like it has an issue with charging on my computer. I plug it and it the computer is telling me that it can be connected to a higher speed port which makes no since as I have 2 usb 2.0 ports and 1 usb sata port. But basically I plug it in with a full charge and it has no problem keeping it charged but when it ends up going down to at least 50% the charge just keep deceasing and never charges. I just hope that I can make it stop this as it is getting quite annoying maybe it is just the battery or something but I can't see how as it isn't even 6 months old.
I've tried using Logcat but unless you set it to save the log every few seconds it doesn't help. If there's an error it doesn't get caught by Logcat because whatever it does, it turns off the whole phone.
What are you overclocked to?
I'm not, unless CM7 comes already set to overclock. I don't play games on my phone so not much point overclocking for me.
Oneiros42 said:
I'm not, unless CM7 comes already set to overclock. I don't play games on my phone so not much point overclocking for me.
Click to expand...
Click to collapse
Well then. I don't know. Have you tried reflashing the ROM?
Not yet. I was hoping Mik's CM7 6.6.1 would have been declared stable by now, but I guess I'll have to settle for 6.5.8.
Quick off-topic question: ADW Launcher always comes to a grinding halt immediately after a reboot, to the point it gives the force-close option window. Is that because there are widgets installed to the partition on the sdcard, thanks to app2sd? I checked under applications and it says they're installed to the phone, but I thought I heard that app2sd (I'm using Darktremor's, as suggested by Mik) effectively takes the option out of your hands, making it moot. If that's the case, how do I delete the partition, since I'll be doing a full wipe and reinstall when I flash the ROM again.
I don't play games 2
Dammit! Yesterday I did a complete wipe (return to factory, wipe dalvik), reformatted the sd card, and updated the ROM to 6.5.8 and it just shut down on its own again. I even saw it happen... while it was sleeping, I saw the buttons light up and blink once or twice, then it shut off. The screen stayed off.
I did a clean install and haven't touched the clock settings. I reinstalled my apps of course, but I don't have anything that runs constantly in the background that I'm aware of. I installed ADW Launcher EX, I don't know if that matters.
Does this mean it could have a physical fault somewhere? I'd really hate to have to go through the hassle of reloading the LG stock ROM and unrooting it (that's possible, right) to send it in for repair.
I had the same problem with gingerbread and the related roms.
But my problems were about the overclock frequencies. I used the italian rom GingerLoL 1.5.2 and I set the frequencies in this mode: 320-729 smartass v2. No more problems.
I don't know why I hadn't this problem with Froyo's rom...
I'm tempted to fiddle with the clock settings now that I know just reflashing the rom doesn't help. It seems by default CM7 is set to 245-600mhz, with the "smartass" governor. I figure I might as well bump the low end to 320, but where's the "v2" version of smartass you mention? It's not in the list.
I have exactly the same issue! Tried 3 different firmwares, 3 different roms and different kernels too, but it seems to reboot by itself and also really slow sometimes to scroll. Can't solve this... maybe some hardware troubles? some new defected cpu ? I sent this phone 1 month ago in warranty and they changed me the logic board, then when i got it back, it started to have this trouble. Before this, never had this trouble.
Oneiros42 said:
Hi all, I'm running Cyanogenmod 6.5.7 and in the last couple weeks I've picked up my phone only to find it was off, not sleeping. It still has plenty of charge left (I can't remember when my phone last went below 50%), and it boots back up without a problem. You wouldn't know there was anything wrong except for the fact that it sometimes turns off on its own.
My first problem is that I don't know where to look to see what could be the trouble. It's running ADWLauncher EX. Beyond that and the OS I don't know what could be relevant. I switched to CM7 last month, up to then I'd been running GingerLOL and I never had this issue.
Any help or advice is appreciated.
Click to expand...
Click to collapse
Make a full wipe and don't let your phone with low internal memory, it worked for me and i was having the same issue
FPChaim said:
Make a full wipe and don't let your phone with low internal memory, it worked for me and i was having the same issue
Click to expand...
Click to collapse
I have done a full wipe, but I don't understand your other suggestion. I'm using Darktremor's Apps2SD, so I'm pretty sure I'm not running low on ACTUAL internal memory.
As per my last comment, I bumped the low end of the governor to 320mhz and there was no trouble until two days ago when it turned off on its own again, making it the longest it went without the spontaneous shutdown. However, it then broke its record for SHORTEST time because it shutdown again five hours later.
Can anyone thing of anything else, or should I start looking for my warranty info?
Oneiros42 said:
I have done a full wipe, but I don't understand your other suggestion. I'm using Darktremor's Apps2SD, so I'm pretty sure I'm not running low on ACTUAL internal memory.
As per my last comment, I bumped the low end of the governor to 320mhz and there was no trouble until two days ago when it turned off on its own again, making it the longest it went without the spontaneous shutdown. However, it then broke its record for SHORTEST time because it shutdown again five hours later.
Can anyone thing of anything else, or should I start looking for my warranty info?
Click to expand...
Click to collapse
I'm my case the phone boots and when it load all the aplications it reboots... but one time i quickly go to setting>applications>manage applications and there has less than 1 mb... so i think it was building something like caches... I wiped everything and my phone worked as usually... but i installed a lot of things again and it keeps rebooting and rebooting... i wiped everything again and installed just few things, leaving my phone to have high internal memory... it worked!(actually i have 42 mbs of free space and it never happened again)
I apologize if this thread is a tad redundant, but I believe it goes beyond your run-of-the-mill glitches that one might post about in the ICS Bugs thread.
I got my OTA upgrade about 10 days ago, and since then my RAZR has been utterly useless.
The biggest problem is an obvious issue with power management. With GB I used to get almost a full day of heavy use. Now I get 2 hours, 3 if I'm lucky. I often find that the phone is extremely hot, as if the processor and radios are running at 100% for no reason.
Perhaps worse than that, it takes infinitely longer to charge than it used to. As in, 5+ hours to go from 0% to 100% -- and that's while the phone is powered off. Powered on, it'll take even longer.
I've experienced issues with almost every app, and with some I've had literally no success whatsoever. Facebook freezes half of the time before even loading up. The stock Browser will freeze a few times a day. Alarm Clock Xtreme freezes whenever I try to edit an alarm. Neither the stock Gallery nor third-party image apps will load up any of my photos without freezing. Google Talk won't initiate video chats. The list goes on and on.
Moreover, the phone will often just freeze outright. Sometimes the screen won't light up, regardless of how many times I press the power button. Sometimes the phone gets stuck on the home screen, and responds to nothing. Sometimes the phone becomes unresponsive, although pressing the capacitive buttons still triggers haptic feedback. Because of this, several times a day I just hold power+down to shut it off the hard way.
At this point, I actually avoid using it. It's that useless. It's more burdensome than it is helpful. It sucks because, when it's working, everything is really smooth and the ICS interface is really cool. I can tell it would be awesome, if only it worked.
Has anyone experienced such madness as this?
FYI, I'm running:
Android version 4.0.4
System version 6.16.211.XT912.Verizon.en.US
Baseband version CDMA_N_05.11.01PLTEDC_U_09.11.00
Kernel version 3.0.8-g29cf5e7, [email protected] #1
Build number 6.7.2-180_DHD-16_M4-31
I can't believe they would release something so unstable.
And yes I've gone into recovery and wiped the cache partition several times to no avail.
I admit there are some issues with the battery and heat and bugs, but i have not experienced any freezing with the stock browser or any program really, alarm clock extreme and it works for me, I don't use the Facebook app often but the few times i have, no real issues sometimes it lags trying to update. I will say thay the market SUCKS or play whatever they call it. Maybe you got a corrupt OTA file or something is wrong with your update installation. Maybe try doing a factory reset, i know that sucks to do but i do it before every OTA and im not really experiencing any of the software issues you are experiencing. If that doesn't help, root it and use the razr 1.7 utility to reinstall the system files.
Did you try to wipe the device (factory default)? It helped in my case.
Sent from my XT910
If you wana solution to some problems without wiping the phone, boot into recovery and wipe the cache, fixed my battery and a few other problems, It doesnt remove anything you have done, also it eliminated my lagg problem.
abw1987 said:
I apologize if this thread is a tad redundant, but I believe it goes beyond your run-of-the-mill glitches that one might post about in the ICS Bugs thread.
I got my OTA upgrade about 10 days ago, and since then my RAZR has been utterly useless.
The biggest problem is an obvious issue with power management. With GB I used to get almost a full day of heavy use. Now I get 2 hours, 3 if I'm lucky. I often find that the phone is extremely hot, as if the processor and radios are running at 100% for no reason.
Perhaps worse than that, it takes infinitely longer to charge than it used to. As in, 5+ hours to go from 0% to 100% -- and that's while the phone is powered off. Powered on, it'll take even longer.
I've experienced issues with almost every app, and with some I've had literally no success whatsoever. Facebook freezes half of the time before even loading up. The stock Browser will freeze a few times a day. Alarm Clock Xtreme freezes whenever I try to edit an alarm. Neither the stock Gallery nor third-party image apps will load up any of my photos without freezing. Google Talk won't initiate video chats. The list goes on and on.
Moreover, the phone will often just freeze outright. Sometimes the screen won't light up, regardless of how many times I press the power button. Sometimes the phone gets stuck on the home screen, and responds to nothing. Sometimes the phone becomes unresponsive, although pressing the capacitive buttons still triggers haptic feedback. Because of this, several times a day I just hold power+down to shut it off the hard way.
At this point, I actually avoid using it. It's that useless. It's more burdensome than it is helpful. It sucks because, when it's working, everything is really smooth and the ICS interface is really cool. I can tell it would be awesome, if only it worked.
Has anyone experienced such madness as this?
FYI, I'm running:
Android version 4.0.4
System version 6.16.211.XT912.Verizon.en.US
Baseband version CDMA_N_05.11.01PLTEDC_U_09.11.00
Kernel version 3.0.8-g29cf5e7, [email protected] #1
Build number 6.7.2-180_DHD-16_M4-31
I can't believe they would release something so unstable.
And yes I've gone into recovery and wiped the cache partition several times to no avail.
Click to expand...
Click to collapse
Data wipe, itll fix it. If you dont want to.do.that then root and wipe the cache and dalvik cache.
Sent from my DROID RAZR using Tapatalk 2
AndroidGreg said:
If you wana solution to some problems without wiping the phone, boot into recovery and wipe the cache, fixed my battery and a few other problems, It doesnt remove anything you have done, also it eliminated my lagg problem.
Click to expand...
Click to collapse
This is step 1... see if this fixes it... if not, full wipe.
Erik
Sent from my DROID RAZR using xda app-developers app
syrnett said:
This is step 1... see if this fixes it... if not, full wipe.
Erik
Sent from my DROID RAZR using xda app-developers app
Click to expand...
Click to collapse
+1
ICS is very different from GB, and Motonverizola tried really hard to get ICS to play well with existing GB cache data and GB settings. All of that stuff changed a LOT.
The problem isn't ICS: the problem is data conversion from GB to ICS.
Wipe the cache and dalvik. If that doesn't get it, then do a factory reset and set everything up again.
Mine runs for days with light use (1-3 hours a day), or a day+ with heavy use. It doesn't get hot, unless you mean that the other way. But that'd be kinda creepy.
Hi
This is my first post here at this forum and I'm not a Razr user but thinking about getting the Maxx because of it's hardware and big battery which fits my usage of a smartphone, I have a Galaxy S right now.
I have looked at some of the posts and screenshots of the battery usage on the new leaked/released ICS for the Razr and read about complains about the short lived battery and the devices that overheat, well, we had the same problem when GB has been released to the Galaxy S and that is all related to the Android OS app that is using the battery because it's got into a loop, this will not get fixed unless you make Motorola aware of the problem. I could be wrong but I think that is related to the dalvik-machine. Android OS should be using around a single-digit of the battery of all time (3%-7%), we don't have this issue anymore since Samsung fixed this bug in the later releases of GB firmwares.
A temporary fix of the Android OS is to reboot the phone when you can see that it's hijacking the battery, this is until Motorola fixes the issue.
I wish you all good luck and hope that you will get a better firmware soon.
Its always good practice to start fresh when accepting an update that big. Less variables = less problems.....
Id do a factory reset and start from scratch... that sux... i know, but so does a useless phone
Ics def wasnt all the hype.... but its also not that bad... just gotta start clean.
Good luck!
Complete disaster? How is it a disaster compared to my update? After the update I could no longer receive text messages, Consider the fact that I send a receive hundreds of text messages per day this is honestly the biggest cause of outrage I have with a flagship that can't perform even what a Nokia 6280 could, when I finally receive texts they come in 4 hours late and worse still, in DUPLICATES and I can't seem to find any solution to this as of yet. A factory reset fixes this for an hour at best but the problem suffices after that. Does anyone have a SOLUTION to this? Honestly driving me nuts
I agree with most others... do a factory reset. I always do after a major upgrade (and ICS is a major upgrade!)
Then check what apps you are putting on the machine; some cause issues. For instance, I put the new Starbucks 2.0 app upgrade on my phone yesterday - consumed battery like mad, phone ran hot (like cook-an-egg-on-it hot), runaway processes, etc. Turns out it was the new Starbucks app; after removing it the phone ran normal.
Otherwise I love ICS! So try the cache wipe; and if that doesn't help then do a factory reset and reinstall things. Takes time, but it saves in the long run.
Wow, this is crazy to hear. My update has been flawless but I did a factory reset after getting it. I bet if you did that it would fix 99% of your problems.
I also rooted after and now I'm running a cm9 rom. This is the best my phone has ever run.
Ultimately, even if you don't root you can fix most of these problems with a factory reset.
Sent from my Droid Razr using xda premium
Hold down the Home button to see what's running, download a task manager to see what's dominating the CPU. The phone won't get hot by itself, something is using up the CPU (like you said) if you don't want to factory reset you've got to figure out what it is. Rooting and setting the CPU governor to hotplug will save quite a bit in battery (shuts the 2nd core off when not needed).
I'm on a Canadian leak, the first day battery performance was terrible. By the 4th day, the battery lasted longer than GB
I concur with everyone here about the factory reset.
As other's have mentioned, going from GB to ICS is a major overhaul. I've read elsewhere what this really entails and it's not pretty. Suffice it to say, I backed up all my user apps and data (using Titanium Backup), saved off all other things that were on my internal SD card just to be safe and then applied the OTA update in stock recovery, wiped data and cache and rebooted. I then rooted, installed Safestrap and flashed Eclipse ICS v1.2 RC1 and restored my apps with TiBu.
I also tried stock ROM as well and restored my apps via TiBu.
In both cases, no performance issues nor forced closes. Runs like a champ.
I'm running the latest .214 leak and my battery life has improved over .211.
.214
Razr Maxx
I was having shorter battery life with the ICS .211 build and then updated to .214
My battery life is way better then it ever was with GB or ICS .211
I ran it the other day for 36hrs and 3 of it actually talking on the phone and had 20% battery life left.
It has currently been on for 4hrs 6 min and is at 90%. light email and phone use. I do have an IMAP email account that poles every 10 minutes with push for instant updates.
Mine is running fine after simple reboot
I am getting great battery life and my Razr Maxx is working almost flawlessly after the ICS OTA stock update. I just rebooted it shortly after the update when it was running hot and haven't had any problems since.
If .214 is even better, great.
Looking forward to Jelly Bean to get even more from my device.
Jeff
Was on the soak test and had the same battery problems. Only way to fix was via a factory reset. This did however fix all the problems.
Cant use motocast, it wont connect to my motocast on my mac. So i cant sync my media. How to solve this?
Sent from my XT910 using Tapatalk 2
Thanks for the replies everyone.
As mentioned I have tried booting into recovery and clearing the cache, but it doesn't help.
Some have suggested wiping the dalvik cache. However I don't see that as an option in the recovery menu. Do I need to root to have that option? Excuse my newness to this.
Worst case I guess I'll just have to do a factory reset
abw1987 said:
Thanks for the replies everyone.
As mentioned I have tried booting into recovery and clearing the cache, but it doesn't help.
Some have suggested wiping the dalvik cache. However I don't see that as an option in the recovery menu. Do I need to root to have that option? Excuse my newness to this.
Worst case I guess I'll just have to do a factory reset
Click to expand...
Click to collapse
Its under the advanced menu.
Sent from my DROID RAZR using Tapatalk 2
How stable is the cm10 18/04 ? I flashed the one before it and it would gave black screens and it would not let me download any music or documents from internet.
Try Chris's CM10 0.05.3, I've been using it for a few days now with no reboots or SODs.
Sent from my NOOK Tablet running CM10 0.05.3
Same with the sgt7 they use same kernel.
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
So they are both stable? because i tried sgt7 as I mentioned and it had download problems and I also tried another one Called alien Droid that was cm10 based and it also gave me the same problems
.....btw I did wipe cache and dalvinik cache and wiped.....
Sent from my Nook Tablet using xda app-developers app
I have flashed the last three releases of sgt7 cm10 and am very pleased battery life is exceptional on the 8/10 build and i don't recall any freezing or reboots happening ... now on the 3rd day using it.
..Note using twrp recovery..
Sent from my SPH-L710 using xda app-developers app
kobhomye said:
I have flashed the last three releases of sgt7 cm10 and am very pleased battery life is exceptional on the 8/10 build and i don't recall any freezing or reboots happening ... now on the 3rd day using it.
..Note using twrp recovery..
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I,average about two to three BSODs every other day. When they occur they seem to cluster, so I get a few, stops happening, and everything runs smooth for the next few days. Other than that, this rom has been smooth as silk and stable as can be.
billy8362 said:
Same with the sgt7 they use same kernel.
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
Click to expand...
Click to collapse
Kernel is based on cm10 kernel but not the same example 1.2ghz, new i/o schedulers etc
Have you had any trouble downloading anything or is that just me?
Sent from my Nook Tablet using xda app-developers app
Taking the plunge with the sgt7 cm10 2012-10-08 ROM
I just finished installing the 2012-10-08 ROM, and wanted to report my experience so far.
My Nook Tablet was already rooted and running CM7. I have been waiting to make the move to JB once the stability of the various ROMs seemed to be improving, and the recent work seemed promising. Thus, I decided to dive on in.
Here are the steps I took:
1. Downloaded 08/10 ROM, JB gApps, and CWM as referenced in the OP. Moved them over to my SD card.
2. From Rom Manager on the NT, I booted into recovery and flashed the new CWM. Rebooted the tablet.
3. Booted back into recovery again, did a factory reset (format data/ and cache/), then formatted Dalvik cache as well.
4. Flashed the 08/10 ROM.
5. Flashed JB gapps.
6. Rebooted the tablet.
After a short while, the OS booted up. I connected to my local WiFi, and then I configured the tablet with my Google account info, installed necessary apps, etc.
Everything seemed to work very well until the screen automatically turned off after the tablet stood idle for a while. Pressing the N button or power button did not turn the screen back on. I assume that this is the dreaded "Sleep of Death" (SOD) I have heard so much about.
I held down the power button for 10 seconds or so, released it, then held the power button down until the tablet rebooted. I thought that maybe turning WiFi off before it slept might help, so I experimented a bit, and it did seem to work.
I'm home now, and the battery life of the ROM seems very nice so far. I am playing around again with WiFi left on before it sleeps, to see if I can reproduce the same problem, but so far it is waking back up and working just fine.
All in all, it is a very impressive ROM, and I am glad (so far) that I decided to take the plunge!
Bug with 4/10 version
hi,
i also want to report few bugs with version 4/10: before i went to bed, and charged my NT 16G. from the screen, it confirmed that the charging started. but next morning when i checked again, the battery is still at the same level.
this means that it doesnt really charge, even it said the charging was under-way.
i can confirm that the charge cable was properly connected to my NT, so this is a software bug i think.
Besides, it seems i have the SOD problems sometimes. i tried to reboot, but the power button didnt seem to work. finally, i removed the microSD card, and it seemed to help to reboot my NT. another problem???
thanks.
I think I have to revise my endorsement. The 4/10 rom without enhancements is a buttery smooth, very reliable, daily driver. BSODs are rare, wifi dropping rarely happens. The enhancement pack and the 8/10 rom do fix the wifi dropping and imprive battery performance. Unfortunately they also seem to break a fairn number of apps, including com2us, scrabble, and words with friends I also experienced video freezing. on youtube and netflix. Also memory use seemed higher and I had to frequently (4 or 5 x per day) run fix.permissions to prevent force.closings.on apps . That ended up being a deal breaker, I ended up reverting back to the 4/10, the enhancements ended up causing more headaches then they fixed.
Still, the 4/10 is easily the most stable, functional rom currently running on the tablet. Huge thanks to everyone.who worked on this.
Just a quick update on the 2012-10-08 ROM. Last night, I picked up my NT after having it sit for a couple hours, and pressed the "N" button to wake it back up. The screen turned on, and I briefly saw a notification message scroll up top that said something along the lines of, "SD card unexpectedly removed", and then the tablet rebooted.
I saw that someone else had a similar issue on the DEV thread, and just wanted to confirm that I, too, seem to be having the same problem.
c600g said:
Just a quick update on the 2012-10-08 ROM. Last night, I picked up my NT after having it sit for a couple hours, and pressed the "N" button to wake it back up. The screen turned on, and I briefly saw a notification message scroll up top that said something along the lines of, "SD card unexpectedly removed", and then the tablet rebooted.
I saw that someone else had a similar issue on the DEV thread, and just wanted to confirm that I, too, seem to be having the same problem.
Click to expand...
Click to collapse
I've found that manually disabling Wifi before sleeping prevents the sdcard issue. The I have no idea why they seem related but it works here on 04/10 that way.
Sent from my Barnes & Noble Nook Tablet using xda premium
LifeWOutMilk said:
I've found that manually disabling Wifi before sleeping prevents the sdcard issue. The I have no idea why they seem related but it works here on 04/10 that way.
Click to expand...
Click to collapse
Thanks for the confirmation of my suspicion. It seeps that disabling WiFi before sleeping also prevents the SOD issues, so I will just try to remember to do that when I use it.
A couple of months ago I installed the AOKP ICS rom Then JB and found it about as good as you could want, but this is not about how good the rom is. I have been flashing a couple of years and know enough to get by. As much as I loved the rom i was almost ready to flash back to stock because I was unable to get any battery life. I would always use at least 8% at night and up to 15% during the day. I just couldn't understand how so many people were saying they were getting great battery life. I went through all the posts and tried every option i could find, watching wakelocks every time I picked up the phone, changing my router settings, turning off everything on the phone that made it a great phone. When I originally installed ICS I did a total factory reset, cleared all cashes. Spent hours reading everything I could find about battery life problems. When i flashed JB it was the same thing. I have been flashing the updates every week. Clearing everything every time.
Last night i was about done and figured I would try this one more time. I downloaded the rom and Gapps again, but this time i did a factory reset 3 times and cleared the cashes 3 times. Then when the system was installed I downloaded clean apps from the the Play store. I installed everything normal, all sync settings on, the phone is set up just like you would want it with full functional apps. This morning I woke up and checked the battery and it was down 2% for 5hrs! That is the best I have ever seen and I think about all you could ask for. The history had no wake locks, No awake times when the phone was sleeping. Now at 10 hrs and and 5 hrs of lite use I am at 82% and still no wake locks or anything unexpected by any apps like I always had before. Google Now is running, sync is on, like I said the phone is set up normal not everything shut off.
I am not saying that you need to clear everything 3 , 4 or 10 times when you flash a rom or not use TI to restore your Apps. What I am saying is, if after flashing a rom you are not getting good battery life or you are having any strange lock ups with your phone THEN start from scratch and make sure every app on your phone is perfect. BTW my phone was getting terrible battery life but working as smooth as butter all the time. I didint have to wait 3 battery cycles to get get 10 hrs out of my phone, it worked as I said from the start. If you phone isn't doing as good as other people are and your not expecting to get 2 days with 10 hrs of screen time, Clean out everything and start over, esp on a Rom like AOKP, these phones should work GREAT and it only takes one bad app to kill things.
So listen to the developers and clean house if things aren't right !!!!!!! It takes more time at first but over the last 2 months I have spent about 10 times more trying to fix the phone.
Do some of you other users get 8+ hours of screen on time? I got my i777 around launch time and I don't think I have seen over 4hrs of screen on time. I have tried a lot of different ROMs, like aokp, shoshock2, and currently cm10, and my general consensus is 3+ hours is good.
Sent from my SGH-I777 using xda premium
Trebla_Imein said:
Do some of you other users get 8+ hours of screen on time? I got my i777 around launch time and I don't think I have seen over 4hrs of screen on time. I have tried a lot of different ROMs, like aokp, shoshock2, and currently cm10, and my general consensus is 3+ hours is good.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Never seen 8 hours with stock battery. Max I have gotten is 5 and a half. I could probably get more on Shostock but I was on AOKP JB
I'm going to have to do this tonight. I'm really not looking forward to it though because I've been trying to unlock things in Fruit Ninja but I want to get this thing working right so that's how it goes.
Sent from my SGH-I777 using Tapatalk 2
SteveO390 said:
I'm going to have to do this tonight. I'm really not looking forward to it though because I've been trying to unlock things in Fruit Ninja but I want to get this thing working right so that's how it goes.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Just back up data
im going to try this, i was using the wipe 3 or 4 times method when i had a sony x10 phone a year ago and it seemed to make a difference.
aokp is a really great rom and on the previous version my phone could last a full 24 hours (about 9 of those hours probbaly not really any use)
latest version the battery is a bit trippy for me so im going to try this and i wont be surprised if this is all true.
thanks!
Just an update. 16 hrs, 1 hr screen 69% battery left.
To SteveO I would not restore any apps you have with a backup. If you do the complete wipe it seems that the Play store actually downloaded all the Apps fresh on its own. I think that may have something to do with really getting a clean plate. I have wiped many times and only one other time did the Play store auto load my apps.
I also recommend wiping internal and external storage everynow and then. Backup pics, music and the such
franksig said:
Just an update. 16 hrs, 1 hr screen 69% battery left.
To SteveO I would not restore any apps you have with a backup. If you do the complete wipe it seems that the Play store actually downloaded all the Apps fresh on its own. I think that may have something to do with really getting a clean plate. I have wiped many times and only one other time did the Play store auto load my apps.
Click to expand...
Click to collapse
I had a feeling that's what you meant, to NOT restore a back up.
As for the "auto load" from the Play store, are you referring to when it asks you on start up if I want to restore my apps from Google Play you're suggesting I say yes, correct? Is that what you did?
I was planning on making a list of what's on my phone now and manually downloading each one and installing.
Sent from my SGH-I777 using Tapatalk 2
So what's the point here?
In order to get great (or better in this case) battery life of AOKP, do
1. wipe 3 times
2. install and run one of the clean app from Google Play. Which app, actually?
For some reason, I "feel" that after performing TB backups (user data backups), the battery life gets worse.
There really isnt any "point". I was just letting others know what i did to GREATLY increase my battery life. I dont think it has anything to dowith this ROM. I think if you flash any Rom and your not happy with the Battery life it may be a bad apk that doesnt get cleaned out with the normal route.
I advise installing ALL your apps clean, not any one.
I mentioned that the PLAY store automatically offered to reinstall all my apps after this clean wipe. Other times i have flashed it didnt do this so it makes me think that for some reason something doesnt really get cleared as we think it should, again no expert, only telling what i found after about 20 Rom flashes over the last couple of years.
votinh said:
So what's the point here?
In order to get great (or better in this case) battery life of AOKP, do
1. wipe 3 times
2. install and run one of the clean app from Google Play. Which app, actually?
For some reason, I "feel" that after performing TB backups (user data backups), the battery life gets worse.
Click to expand...
Click to collapse
I just had a really good test of this procedure. My usb port crapped out so I returned my phone for a warranty replacement.
My old handset has been laggy since upgrading to Jelly Bean. I'd always restore apps through Tibu, only restored data on a few apps.
Fresh clean I777 stock Sammy, runs smooth on ICS.
Newly rooted, AOKP 11/9, basic GAPPS and the same Tibu restore => laggy.
So I factory reset, wiped everything including internal storage, let Play restore my apps, input all the app data manually, and this phone is smooth.
Sent from my SGH-I777 using xda app-developers app