When running the TP, it will shut down allegedly due to lack of power when battery reads something between 50% and 60%. This is when running CM7 or CM9 A0.5
If it does this, it will no longer boot into CM or WebOS, or CWM. It gets to Moboot, then when you chose a thing to boot, you get the inital splash, either CM splash or HP logo, then it powers straight off again.
Funny thing is, it will stay on the Moboot screen seemingly forever. Also, I can boot into bootie (USB) mode, and use novaterm to query the battery stats in Bootie shell, and I can see that it reports 53% (whatever it is) and a reasonable mAH life.
Under WebOS, Doctor Battery from Preware reports nothing unusual. 98% capacity left, and whatever percentage.
So when it's doing its 'power off' thing, I connect the charger and it will boot straight away. When it returns to the OS, be it CM or WebOS, it reports battery as 54% or whatever, and goes up to 100% from there.
When it reaches 100%, disconnect, and the battery will drain at normal rate to 50% or 60%, then power off again.
As an experiment, I charged it to 100% in WebOS, then left it on charge over night, and then I managed to run the battery down to 24% in WebOS before putting it on the touchstone, and it was still going at 24. I expect I could have got it down to much less.
Now it's doing it again, shut off last night at 51%.
My suspicion is, that it's not showing the correct charge, or something's not reporting the correct 'thing' to the OS.
What's more baffling is, that whilst it can't boot a uimage, like Clockwork or CM, or WebOS, it will remain powered on in Moboot or bootie. I really don't understand this.
Is this something I can fix with some software tweak? Will it need an RMA?
Hoping someone can help please, it's driving me nuts!
HarpingOn said:
When running the TP, it will shut down allegedly due to lack of power when battery reads something between 50% and 60%. This is when running CM7 or CM9 A0.5
If it does this, it will no longer boot into CM or WebOS, or CWM. It gets to Moboot, then when you chose a thing to boot, you get the inital splash, either CM splash or HP logo, then it powers straight off again.
Funny thing is, it will stay on the Moboot screen seemingly forever. Also, I can boot into bootie (USB) mode, and use novaterm to query the battery stats in Bootie shell, and I can see that it reports 53% (whatever it is) and a reasonable mAH life.
Under WebOS, Doctor Battery from Preware reports nothing unusual. 98% capacity left, and whatever percentage.
So when it's doing its 'power off' thing, I connect the charger and it will boot straight away. When it returns to the OS, be it CM or WebOS, it reports battery as 54% or whatever, and goes up to 100% from there.
When it reaches 100%, disconnect, and the battery will drain at normal rate to 50% or 60%, then power off again.
As an experiment, I charged it to 100% in WebOS, then left it on charge over night, and then I managed to run the battery down to 24% in WebOS before putting it on the touchstone, and it was still going at 24. I expect I could have got it down to much less.
Now it's doing it again, shut off last night at 51%.
My suspicion is, that it's not showing the correct charge, or something's not reporting the correct 'thing' to the OS.
What's more baffling is, that whilst it can't boot a uimage, like Clockwork or CM, or WebOS, it will remain powered on in Moboot or bootie. I really don't understand this.
Is this something I can fix with some software tweak? Will it need an RMA?
Hoping someone can help please, it's driving me nuts!
Click to expand...
Click to collapse
It looks like webos is working as it should, so in webOs (I'm pretty sure that it's in preware) run the uninstall Android app. Wipe (factory, cache, dalvik cache) 3 times and try flashing android again.
Hope this helps.
chicle_11 said:
It looks like webos is working as it should, so in webOs (I'm pretty sure that it's in preware) run the uninstall Android app. Wipe (factory, cache, dalvik cache) 3 times and try flashing android again.
Hope this helps.
Click to expand...
Click to collapse
I did pretty much this when I went from CM7 to CM9.
Also, I ran ACMEUninstaller, before doing WebOS Doctor when I thought I'd have to RMA it.
Interesting though - at that point I decided to try the all night charge, and it did hold and work as expected. Now that I've (re) installed CM9, I'm seeing the issue again.
But doesn't explain how it won't boot the WebOS kernel.
Next time it does this, I'm going to put it into Bootie mode and constantly try the
chg battery
command until it dies.
See if I can find out if it /really/ had 69% left (and wouldn't boot the WebOS or CM or CWM kernels), or whether or not it's /really/ only a few percentages left, and it's all being mis reported.
HarpingOn said:
I did pretty much this when I went from CM7 to CM9.
Also, I ran ACMEUninstaller, before doing WebOS Doctor when I thought I'd have to RMA it.
Interesting though - at that point I decided to try the all night charge, and it did hold and work as expected. Now that I've (re) installed CM9, I'm seeing the issue again.
But doesn't explain how it won't boot the WebOS kernel.
Next time it does this, I'm going to put it into Bootie mode and constantly try the
chg battery
command until it dies.
See if I can find out if it /really/ had 69% left (and wouldn't boot the WebOS or CM or CWM kernels), or whether or not it's /really/ only a few percentages left, and it's all being mis reported.
Click to expand...
Click to collapse
You don't mention whether you wiped battery stats in CWM.
pa49 said:
You don't mention whether you wiped battery stats in CWM.
Click to expand...
Click to collapse
Does that actually do anything? It was something I did do, but I'm not sure it's helpful at all
I've just had it go off in cm9 at 69%.
It wouldn't boot to cwm, webos or cm9. Powering straight off after the initial splash.
I booted it to cm9 with the charger in, then pulled the charger soon as it was booted.
It's still running now at 65%.
Could this be a weird boot loader issue? Plenty of things still cause cm9 to reboot, then I'm stuck if I don't have a charger with me.
All most odd.
Sent from my Touchpad using xda premium
Related
Hey,
I just installed CyanogenMod 7 on my milestone using openrecovery. Everything was working perfectly, but the battery was draining like there's no tomorrow.
Started at 50% when I first booted, I downloaded a couple of apps from the Market, and went down to 20% (in the space of about 10 minutes). So I plugged in the phone charger (USB into back of my computer), and then while configuring settings, battery went to 4% (it was checking in 1% increments, which I have since found out that drains the battery). The phone then died. So, the phone was using WAAAAAY more power than the USB port could supply. Anyway, thought I'd let it charge for a while, then go back into the settings, and remove the 1% increments, to try and get normal battery life.
The phone recharges, and automatically reboots. Its still on 4%, but I went in, turned off the 1% increments. Phone dies again.
Charges about 10 minutes, reboots itself again. During this period, I did some research, and found that the battery draining can be caused by excessive CPU usage, resulting in the screen staying on even when it's off (?).
But, alas, no luck. I don't have enough battery to flash the stock SBF.
All I really want is:
a) a way to just have the thing charge without turning itself on, and
b) a workaround to get at least half-decent battery on CM.
Thanks,
David.
[Disclaimer: not guaranteed to work, I don't take responsibility for anything you do your phone!]
Try deleting your /data/system/batterystats.bin before trying this procedure out. You can use an app like Root Explorer to do this. If you're unable to, proceed with bump charging.
Try bump charging:
1. Remove battery, put it back in after a good 2-3 minutes and connect phone to a wall charger. Make sure the phone is still switched off while it's charging.
2. After it finishes charging completely (green LED), let the charger be switched on and connected - remove the battery alone (without switching off charging).
3. After a few seconds, you will see a "?" on your screen, after which you insert the battery back in (while charger is still switched on).
4. Wait till charging completes again (green LED).
5. Plug out charger, wait for 2-3 minutes and plug charger back in and start charging again. It should now be fully charged.
6. Turn phone on while charging, after booting into CM, try OC'ing it to 800MHz interactive governor, apply settings on boot and restart your phone.
Hope this fixes your problem. Good luck!
Anyone can feel free to correct me if I'm wrong.
rampee said:
[Disclaimer: not guaranteed to work, I don't take responsibility for anything you do your phone!]
Try deleting your /data/system/batterystats.bin before trying this procedure out. You can use an app like Root Explorer to do this. If you're unable to, proceed with bump charging.
...
Click to expand...
Click to collapse
I had the same problem some time ago and tried all this to no avail. I even changed to froyomod for some time, but CM7 is far superior so I just came back to it. The problem happened again this morning just after using google maps. I then rebooted and uninstalled all google maps updates. Seems to be working o far.
hey, yeah, just one problem with that - i can't boot into android for longer than about 3 seconds, and now there is no way to revert, as the bootloader says Battery Low.
Can't you boot into recovery, flash another rom and then reboot into android?
Don't charge from usb, use wall charger. That way, the system will boot only to charge-only screen, android system itself not running.
Hey, kabaldan, I found that out.
Charged 100% using the bump method instructed above. Battery life is still worse than useless, 50% in about a half hour.
will performing those other steps help?
Can you try another fully charged Milestone/Droid battery?
If that doesn't work it might be a problem with your phone's hardware. I know it might be a long shot, try cleaning your phone's and your battery's leads (connectors) if they might've accumulated rust/dust or something. Not sure.
Don't know if this is a similar problem but mine goes down in % pretty fast too but then it can stay for 1% for half a day
No, mine definitely dies. At around 5%, although I did turn off the 1% increments, because I heard they guzzled battery.
The battery life is getting progressively better, but as soon as I use 3G, or open any half-decent games, it drops to about 40% in ~.00001 seconds.
Although, to be fair, I didn't get great battery life on stock rom, either. And my ram always seem chokkas. Like usually only have about 50mb, and I'm not running anything too hectic.
Unfortunately, I think I'll get the Samsung Epic as soon as they bring out the GSM version. I just want an android phone with an unlocked bootloader, insanely large screen, and hardware keyboard, not to mention ~20 days battery life. Is that too much to ask?
32GB TP, running 3/29 CM9 Tenderlion Nightly.
When plugged into USB-Computer, the drain outpaces the charge*
When plugged into USB-Charger, the drain outpaces the charge*
When put on a touchstone, the charge works correctly.
Why is the wall charger and or the computer not charging the TP fast enough?
*I used HP's TP cable
First, I turn off the device and fully charge. Takes about 3-5 hours for me, check using webOS. Leave it for another hour or so just to make sure. Then boot android and wipe battery stats. If that doesn't help you, try to figure out what's using your battery using watchdog or something.
Even though I don't believe wiping stats actually does anything to improve battery life, I think that it helps android system read voltage/current properly. Maybe I'm wrong, I dunno.
There's a glitch that sometimes happens, where when in Android, it sets your charging circuit to use a trickle charge mode, even when not using a non-HP charger. It happens, but nobody can really explain how.
What you do is reboot it into WebOS, plug it in, let it charge for 5-10 mins, then reboot into Android, and it should fix it.
This happens to me also with ICS roms. It's very frustrating. I haven't tried any of these methods though, really. I just figured that something was wrong with the rom. Anyone have a workaround for this besides what was said here?
I've recently received my Touchpad back from HP and getting the battery replaced.
I assume that the cause of the dead battery was from CM9 as it had completely drained it and so I wasn't even able to get it into charging mode.
I just wondered whether any of the new ROM releases address this issue and if not, is there a way to avoid this issue occurring in the feature (whilst using CM)?
first you are assuming that it was due to CM9 then u want to find out the fix? lol many people have battery issues on Android roms...but i dont think anyone have addressed it yet
viny2cool said:
first you are assuming that it was due to CM9 then u want to find out the fix? lol many people have battery issues on Android roms...but i dont think anyone have addressed it yet
Click to expand...
Click to collapse
I know that there is the standard battery issue (where the battery drains quickly), but I'm asking about the specific issue of the ROM causing the touchpad to die, without any way to charge it
Set it to boot to WebOS by default.
Seems there is an issue with letting the battery die in Android.
I set mine to boot to WebOS (where it will charge properly from drained) so if it happens to die while using Android, I just leave it on the charger and it will eventually power up enough to boot into WebOS and then let it charge fully, or let it get to 10% or so before switching to Android to complete the charge.
I am guessing you are getting the large Plug-In icon and then the large Battery icon when plugged in?
CyaN1de said:
Set it to boot to WebOS by default.
Seems there is an issue with letting the battery die in Android.
I set mine to boot to WebOS (where it will charge properly from drained) so if it happens to die while using Android, I just leave it on the charger and it will eventually power up enough to boot into WebOS and then let it charge fully, or let it get to 10% or so before switching to Android to complete the charge.
I am guessing you are getting the large Plug-In icon and then the large Battery icon when plugged in?
Click to expand...
Click to collapse
I have exactly same problem and I do exactly same thing as you do...
@OP: when i said battery issue, this is what I was referring too.
CyaN1de said:
Set it to boot to WebOS by default.
Seems there is an issue with letting the battery die in Android.
I set mine to boot to WebOS (where it will charge properly from drained) so if it happens to die while using Android, I just leave it on the charger and it will eventually power up enough to boot into WebOS and then let it charge fully, or let it get to 10% or so before switching to Android to complete the charge.
I am guessing you are getting the large Plug-In icon and then the large Battery icon when plugged in?
Click to expand...
Click to collapse
I didn't even get that when it died, hence why I'm quite reluctant to try and install android with the repaired one I just got back.
Is there maybe an app for android that can just shut it down when the battery gets low? (to avoid it dying completel)
CyaN1de said:
Set it to boot to WebOS by default.
Seems there is an issue with letting the battery die in Android.
I set mine to boot to WebOS (where it will charge properly from drained) so if it happens to die while using Android, I just leave it on the charger and it will eventually power up enough to boot into WebOS and then let it charge fully, or let it get to 10% or so before switching to Android to complete the charge.
I am guessing you are getting the large Plug-In icon and then the large Battery icon when plugged in?
Click to expand...
Click to collapse
How do you change the moboot default?
Sent from my cm_tenderloin using XDA
[EDIT]nvm, found Cyboot on Preware thatdoes it for you
I hope this gets fixed in the next update to CM9. Until then, thanks for the info on Cyboot.
When my tp completely dies. It takes ages to come back on. Sometimes I need to hold the home button and power button to get it to come back on.
Sent from my HP Touchpad
My tp will shut down at 80% battery. It then won't boot WebOS (shuts down after first hp logo) or cm9 (shuts off after first cyanogenmod splash). Clockwork mod recovery shuts down like cm9.
If I plug in and run Dr.Battery on WebOS, it reports 80ish% charge and good condition.
As an experiment tonight, I waited for a shutdown, then booted WebOS recovery, which is the one thing that will boot. Got the USB logo on the screen and left it. It sat like that for three more hours, with the screen on before shutting off.
Booting back to WebOS under mains, showed the battery at 20% and charging. So clearly the juice was there to be used.
What's going on here? Under WebOS and cm9 i can get very little run time, but in USB recovery mode, it'll run with the screen on for hours.
I'm confused. Can anyone shed light on this? Thanks folks.
Sent from my GT-I9000 using xda premium
I would suggest that you uninstall cm9 using acmeuninstaller then run webos doctor. After completing webos doctor, see if the touchpad still shuts off at the 80% battery level. If that is still the case, before reinstalling android, contact HP tech support and see if they have any suggestions. If you are still under warranty, you can always send it in to HP for repair knowing that you do not have to worry about HP blaming android for the issue.
Sent from my cm_tenderloin using Tapatalk 2
Recently updated from CM9 to jcsullin's CM11 (11-20140409). Most everything seems to be ok aside from an unusual battery issue, and I don't know what it's coming from. I've attached a screenshot with some battery stats to help out, but I can describe what was going on in this particular instance.
I've had my touchpad sitting on the touchstone nearly 100% of this time (only time it was not was when I picked it up and immediately returned it). At some point, loaded up and was playing Breach & Clear for a while. Finally stopped playing, and upon exiting, battery was reported at 1%. Now, I get that some things can drain the battery even while on a charger, but we're talking a span of maybe 60-90 minutes. At this point, I picked the pad up and the battery immediately went up to 100%, and I dropped it back onto the touchstone.
This is the second time I've had this happen. Yesterday, it actually shut itself off due to low battery when I picked it up. I turned it right back on, and it was reporting 100% (recovery also reports 100%). This morning, I reflashed the A6 firmware in case that was the issue, but it does not seem to have had any impact.
Really could use some advice here. I suspect the battery is more or less staying charged while on the touchstone, and that this is something related to bad reporting or (worst case) a defective tablet.
Thanks for any help.
Just a quick update. Shutting off the touchpad before leaving work, during the shutdown process, I saw the battery % drop from 100 to 0. As I was getting out the touchpad at work and turning it on, I got the battery-with-question mark symbol. Placed it on the touchstone and it booted itself. I decided to take it to recovery, and pulled it off the touchstone. Now, as I watch, the battery is changing % wildly. 100%, 29%, 0%, 67%, back to 100%, 0% again...
Really don't know what's going on. Did not have this happen on CM9. Could really use some help.
Edit: I just threw on a random game while off the touchstone to see what happened. Everything seemed normal, battery ran down to 93%. Exited the game, turned off the screen, and two seconds later it was shutting itself off with 0% battery. Immediately turned it back on, and it shows 93% again.
Did you do a clean install? Does the issue persist after reflashing?
Fresh install, used tptools to wipe and repartition the tablet, no WebOS, CM11 only. Reflashing A6 didn't help.
Still unresolved, possible more problematic.
I rotated my tablet from landscape to portrait and back (while on the touchstone) and it decided to shut itself off.
If anyone knows of/has similar issues (fixable or note), I'd really like to hear about it. Will be disappointed if it's dead, but it's better than spinning my wheels on it for something I can't resolve. If I have to buy a new tablet, I'd like to get it over with.
Edit:
Been a bit since I posted this, but I let the tablet sit for a bit. The battery stats are pretty crazy. Note that I've left it on the touchstone this entire time. I don't get why it's doing what it's doing at all. See newly attached screenshot.
there are 2 possibilities
1. your battery is ****ed, hardware issue, you cant fix unless you replace the battery
2. software issue, but from what you described, seems like you installed properly, so i would suggest to boot into webos (u gonna have to reinstall it), and use it for a few days to see if you get the same problem
- if you do get the same problem, then it's 100% ur battery is ****ed
- if no, then ur cm11 is messed up, try another rom
Ah well. Was hoping I might be able to fix it without any wipes.
I would think if the ROM itself was the issue, others with jcsullins' CM11 would have problems as well. Looks like that's not the case at this point. Perhaps I'll just retired the tablet and get a laptop.
Thanks for the input.
Hi, did you get anywhere with this?
I've got occasional battery percentage glitches on Jcsullins CM11 that I didn't get with the previous WebOS/CM9 setup. See attachment.
Sadly I don't have the time or motivation to launch a huge investigation by flashing ROMs, etc... Looking like I'll just restore WebOS and sell.
At this point, I can't get the thing to boot. I've had it on a charger for a month or two now. I've got the blinking home button. It booted once, but I wasn't in a position to hook it up to a computer and try to wipe it. I've not really put any energy into fixing it since.
I plan on getting it back on the touchstone at some point, and setting it next to my PC. If I ever get it to boot, I'm going to try to get webos back on it first thing, and go from there.
Thanks for the reply. I'm questioning the amount of time I'm spending tinkering with this 3.5 year old device when new tablets are so cheap.
Touchpads are still making a reasonable amount on eBay so sadly I think it's time to just restore webOS and move on. Shame because it runs 4.4 pretty well, at least as good as my Galaxy S3.