Database Develop

[Q] Low-Battery Boot-Loop

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?

[Q] Battery Completely Died on CM9

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

Charging problem

So I have a touchpad charging problem. When I plug a charger it won't charge. I guess it's bad contact,but sometimes when it's start charging the touchpad freezes so I do the reset and it's won't charging again.
Please help me fix that issue till I have some battery left...
All helpful posts will be thanked.

The charger itself is 2 pieces, make sure that they are twisted together tightly. When I first received my touchpad a loose connection in the charger caused it not to be able to charge.

Also, if you have some charge left, reboot into WebOS and see if it'll charge that way. There's an odd glitch that happens to some people (has happened to me, too), where it changes to trickle-charge even when using the stock cable and AC adaptor. Reboot to WebOS, and it'll trip it so it'll charge normally again.

This charging problem just started with my HPTP today.
It would only trickle charge with both the HP microUSB Charger and the Touchstone. It's never done that before with any version CM9 I've flashed (Both Alpha and Nightlies). It started happening today.
I decided I would reboot into recovery and wipe the Battery Stats in the Advanced section of recovery. Now it's charging and the percentage is rising again instead of slowly dropping.
But if it continues to trickle I'm going to Boot into WebOS and see if what ve6ay says will work!
Edit, yeah it's still on trickle and dropping with the charger.. Gonna keep it on WebOS and see what happens..
Edit 2: ok so, with the Touchstone, the tablet only heats up quickly and continues to discharge while on the touchstone with WebOS running.
It also continues to discharge while on the Touchstone with Android running after running WebOS like ve6ay suggested we try.
But with the Stock Charger MicroUSB connected and running Android (After running WebOS) it seems to be charging normally.

I'm not sure if my TP is charging...

This is the second time I've had my TP hit 0% battery while in CM9 (relatively recent nightly build) and auto power off and not respond to charging or boot attemps. I can't say for sure which nightly but probably from 6-12 months ago. It's been realtively stable with no problems i could discern. Anyways. Recently, the first time it lost power down to 0% I searched for solutions to the problem. I found the solution, based on the symptoms, to be TPdebrick. I followed those directions to the letter and within a day or two my TP was back up and running after fully charging. I don't recall precisely what occured after completing TPdebrick and the TP booting up again as I had gone to sleep, then to work, had a bunch of other stuff to do after work, then sleep again before I went to check on the TP to use it.
I'm concerned that it isn't actually charging it this time, even though TPdebrick completed successfully. I have tested the USB cable and charger and they are both fuctioning and able to charge my smartphone. The wierd thing is it did charge for a short period of time right after using TPdebrick (according to the output the battery voltage was at 30xxxxx [I don't remember the numbers where I substituted xxxxx]). But not enough for it to reach minimum charge to boot. When after 24 hours on the charger it was still no responsive I thought I'd run TPdebrick again to try and jump start it again so to speak. This time around from the log is the following:
Starting battery authentication...
Battery authentication successful.
battery_info.percentage = 0, battery_info.voltage = 3225680, battery_info.current = 937, battery_info.temperature = 20
This appears to show that it did charge up a little bit from that brief time it began to charge. And that it was recieving a small amount of charge from the PC. Typically when it is charging the cylinder part that plugs into the outlet gets warm. But it isn't getting warm as expected when the TP is connnected. I've also twisted the plug part off and back on several times along with using my smartphone to test that it was able to charge each time. So I'm stuck not knowing if the TP is actually charging because I have no visual or physical indicators that I can determine if it is or not. Any help would be appreciated.

Install the attached file to your touchpad and run it with your charger plugged in. It will tell you if your battery is charging and what current it is receiving.
Just unzip the attachment and install the .apk
Peace

chris5s said:
Install the attached file to your touchpad and run it with your charger plugged in. It will tell you if your battery is charging and what current it is receiving.
Just unzip the attachment and install the .apk
Peace
Click to expand...
Click to collapse
Since I can't boot the TP how do I install that and use it to get the info? Unless there is a misunderstanding. TPdebrick fixes it so it can charge so it will boot but I don't know if it is for sure charging so that it will eventually boot or if I need to use TPdebrick again. Assuming that despite the appearance of TPdebrick having completed successfully running it somehow didn't fix something. I would assume that at this point my options are few. If software means of getting it to boot again don't work I would have to disassemble the TP to get inside and somehow charge the battery up with a crude hand made rig or something. Assuming that the failure to boot is simply lack of charge. As it was the last time this happened. And needed TPdebrick so that it would charge up in that too low state. The last resort option would be get inside it or whatever other method needed to copy the data off of the internal storage (part seen as SD card) in the state it is in. And if the storage can somehow be wiped from there sell it for parts if it ends up not repairable.

It could also be a dodgy Usb connection/board on the TP several people including myself have had this problem.

Well if tpdebrick got it up and running before can you not repeat the process to enable you to charge the tablet. Then you'd be able to install the tpcharge app and go from there ...

Does the back of the TP get warm/hot after charging? On my TP the back area near the volume buttons gets warm after being plugged in for a few hours.

sstar said:
It could also be a dodgy Usb connection/board on the TP several people including myself have had this problem.
Click to expand...
Click to collapse
chris5s said:
Well if tpdebrick got it up and running before can you not repeat the process to enable you to charge the tablet. Then you'd be able to install the tpcharge app and go from there ...
Click to expand...
Click to collapse
HKSpeed said:
Does the back of the TP get warm/hot after charging? On my TP the back area near the volume buttons gets warm after being plugged in for a few hours.
Click to expand...
Click to collapse
When charging any old day while I am using it I have noticed that area get warm. Just like the cylinder of the charger getting warm almost hot. Neither of that is happening which leads me to believe there may be something more wrong than just the simple yet not so simple problem that TPdebrick fixes. I've ran TPdebrick on it several times now twice before posting the thread and twice after. In completed it's execution with "all done" message. The port itself appears to function otherwise TPdebrick would fail before completing due to a USB connection failure. At least it seems to me it would fail as a result of that. Is there a way any of the parts can be tested for failure to figure out what has failed? Again assuming that something has gone bad internally on the TP. It has been plugged in for now 48 hours only interrupted by running TPdebrick. Of which I could run it again and get the info from the log I previously posted to see how it has changed. I have no idea what the numbers mean other than the battery percent being reported as 0.
I forgot to mention previously that it was plugged in at the time the battery went to 0%. Something I had not expected to occur. The battery icon in CM9 indicated charging with the lighting bolt icon as I had seen the icon just before it auto shutdown. Something I didn't give much thought to as that had happened one time a long time ago when I still had only webOS on it. Except webOS didn't let the battery get too low and it simply booted back up a minute or two after the charger was reconnected after it auto shutdown. So I guess if there is anything I can do to figure out why it isn't charging to know what needs to be fixed and if it is worth fixing and I'm able to fix it then I'd like to fix it. Otherwise I'll need a way to recover the data off of the storage so I can at least not have to start completely over with most of it. Nothing real important on it or anything that if lost would be detrimental just time lost in game progress and related and having to download oddball files for other apps again.

Just out of interest ... my touchpad that was not charging properly thru the usb port still managed to get thru the tpdebrick process to the "All Done" stage. However, it would only take a maximum of 100mA, even off the 2A mains charger. Changing the usb port resolved the chraging issue.
Peace
Edit: also, a touchstone - wireless - charger will eliminate a battery vs USB port fault ...

I have good news and bad news. The good news I'm able to charge my TP with a charger other than the official one. I tried my smartphone charger which is significantly lower amps. In 9 hours it has charged it 30% while it remained in the powered off state. I booted it up a few minutes ago hoping that it had charged it up. I powered it off again and will charge it to 100% before using it.
The bad news is the official chargers cylinder is shot. This is the second official one I have gone through since purchasing my TP during the fire sale. So I'm not sure what I'll do about that. I only really use it as an ebook reader right now and as an alternative to some things I use my smartphone for when I have both available to me. Considering my netbook is in need of replacing due to a failing charging port I am looking to get a windows 8 pro hybrid tablet (ex acer w700) which would effective replace both the netbook and TP. Leaving the TP as a much more of an experimentation device.

mine does not charge in android OS after installing CM 4.1.2 over old cherry kang
im getting current500mA in touchpad chargetest if connected to PC back 2.0 port, charge icon does not appear
charges if on webOS

Having the same issue as serialteg described. Just flashed to 10.2 (09/20 NIGHTLY) and TP cannot charge on CM. Switching back to WebOS, it's being charged.
Fixed. The infamous MTP issue was what I had. Solution found.

Completely dead battery

I know that it has been said that "if your touchpad completely dies, you must have the OEM charger to start it back up". At first this seems true. . .However! I would like to report that twice now, when it was completely dead and displaying the "plug in the original charger for reliable charging or die because im a juice nazi", I was able after about 4 hours of just leaving it alone plugged into a 1amp phone charger, to get it to charge up and boot. This may have already been discovered but I couldn't find mention of it. Just wanted to give hope to someone that might have given up on this.

einstein910 said:
I know that it has been said that "if your touchpad completely dies, you must have the OEM charger to start it back up". At first this seems true. . .However! I would like to report that twice now, when it was completely dead and displaying the "plug in the original charger for reliable charging or die because im a juice nazi", I was able after about 4 hours of just leaving it alone plugged into a 1amp phone charger, to get it to charge up and boot. This may have already been discovered but I couldn't find mention of it. Just wanted to give hope to someone that might have given up on this.
Click to expand...
Click to collapse
So when you connect 1 amp phone charger, does the TP says to connect the original charger? Even if it says to connect the original charger, and leaving it for 4 hours the TP charged is that right???
My problem is when I connect to cell phone charger, it says to connect original charger.
When I connect original charger, the TP stays at 0% even after connecting the charger overnight. I dont know what is the problem? is it charger, is it battery or is it TP..

atrix4nag said:
So when you connect 1 amp phone charger, does the TP says to connect the original charger? Even if it says to connect the original charger, and leaving it for 4 hours the TP charged is that right???
Click to expand...
Click to collapse
Yes.
atrix4nag said:
My problem is when I connect to cell phone charger, it says to connect original charger.
When I connect original charger, the TP stays at 0% even after connecting the charger overnight. I dont know what is the problem? is it charger, is it battery or is it TP..
Click to expand...
Click to collapse
The message will be displayed but it is gradually charging in the background. When it gets enough juice, it will start up and charge faster. In your case it sounds like either your port or battery are damaged somehow. Possibly the charging circuitry but that is unlikely. If you don't have an original charger or touchstone, then your options are limited. They aren't very expensive on ebay though. I would let it charge on a good 1 amp charger for a few days and see what happens then. Mine did the "soft brick" crap once where it was completely unresponsive and ran completely dead and i just charged it for 4 days and forgot about it and when i remembered it, it had powered on and booted. TPs are funny devices. Expect anything and report it if you don't mind. Maybe we can get this sorted out.

einstein910 said:
Yes.
The message will be displayed but it is gradually charging in the background. When it gets enough juice, it will start up and charge faster. In your case it sounds like either your port or battery are damaged somehow. Possibly the charging circuitry but that is unlikely. If you don't have an original charger or touchstone, then your options are limited. They aren't very expensive on ebay though. I would let it charge on a good 1 amp charger for a few days and see what happens then. Mine did the "soft brick" crap once where it was completely unresponsive and ran completely dead and i just charged it for 4 days and forgot about it and when i remembered it, it had powered on and booted. TPs are funny devices. Expect anything and report it if you don't mind. Maybe we can get this sorted out.
Click to expand...
Click to collapse
Thanks for prompt response..
I have original wall charger, and got a new cable from ebay. So I am hoping its equivalent to original charger. How can I debug if the port or battery is damaged.. any idea?
I left it on charge overnight yesterday. It was at 0, in the morning.. I left it on charge today before coming to office. i am expecting it to be at 0, when I go home.. When its connected to charger, its working normally (with 0 battery), but as soon as i remove from charger, it will shutdown..

Morning, when I was charging,
the battery monitor widget app showing Battery flow as "-600mA". I think this should be +ve while charging. the same app was showing status as "Charging AC plugged". I will try to charge my phone with the same cable and charger, if the phone shows +ve current flow, then, its deffinetly should be problem with the battery or touchpad right..
I wil test it in the evening.. and if its problem with battery or touchpad.. i will try to clean the TP and will try again.. Lets see how it goes

Ok so you have the original charger, great! And it boots into android/webos correct? It sounds like your A6 firmware might have crapped out or whatever it does to cause battery issues. Probably not bad battery if this happened rather suddenly, and its not a bad port if its booting and running while plugged, even if its not charging. . .so go here:
http://forum.xda-developers.com/showthread.php?t=2756314
and read it carefully! With this tool, you can do some really cool stuff including re-flashing the A6 battery monitor/control chip. It can (but might not) fix issues like this. Give it a try with a good cable and let me know what happens. Good luck!

einstein910 said:
Ok so you have the original charger, great! And it boots into android/webos correct? It sounds like your A6 firmware might have crapped out or whatever it does to cause battery issues. Probably not bad battery if this happened rather suddenly, and its not a bad port if its booting and running while plugged, even if its not charging. . .so go here:
http://forum.xda-developers.com/showthread.php?t=2756314
and read it carefully! With this tool, you can do some really cool stuff including re-flashing the A6 battery monitor/control chip. It can (but might not) fix issues like this. Give it a try with a good cable and let me know what happens. Good luck!
Click to expand...
Click to collapse
I rebooted to webOS, and TP charged normally.. now i updated to CM11, all good as of now.. Thanks for helping me..
only bad part is i disassembled, before booting to webOS

Aw dude....well hey it happens to the best of us lol. Now u know a lot more about ur tablet and i would still recommend reflashing the A6 and removing webos if u dont use it. Tptoolbox can also be "installed" by renaming the boot image .bin file to uImage.TPtoolbox and placing it in /boot on your android partition. This allows moboot to see it. Off topic i know but i thought you might be interested. Best of luck with the re-assembly!

einstein910 said:
Aw dude....well hey it happens to the best of us lol. Now u know a lot more about ur tablet and i would still recommend reflashing the A6 and removing webos if u dont use it. Tptoolbox can also be "installed" by renaming the boot image .bin file to uImage.TPtoolbox and placing it in /boot on your android partition. This allows moboot to see it. Off topic i know but i thought you might be interested. Best of luck with the re-assembly!
Click to expand...
Click to collapse
You can only install TPToolbox as described if you have removed WebOS.

shumash said:
You can only install TPToolbox as described if you have removed WebOS.
Click to expand...
Click to collapse
why is that?

einstein910 said:
why is that?
Click to expand...
Click to collapse
Because there's not enough room for both, and it's designed to run in the WebOS userspace. Don't even try it; I speak from experience.

einstein910 said:
why is that?
Click to expand...
Click to collapse
Because the boot folder is not big enough with the webOS uImage.

Fixed my Touchpad!
I had the same issue and just wanted to report what worked for me. My touchpad wasn't responding to any button pressing combos and even after sitting on the charger for two days, didn't want to turn on. After some google searching I found my Touchpad might be so dead that the charging circuity might not want to charge the battery and all the fixes were telling me to take apart the Touchpad and charge the battery directly. That's not something I really wanted to do. Then another person suggested to charge the Touchpad with a lower amp charger, so I plugged the Touchpad into an iPhone charger for about an hour. I came back, held the power button and home button - nothing. Tried power, volume up, and home - nothing. But then I held the power button and hit the home button ~10 times and then... the home button started blinking left and right. YES! I took the Touchpad and put it on the original charger, 15 minutes later it had the Low Battery Screen and another 15 minutes later, Cyanogenmod was booting.

I need help. When I try to transfer the Android files to the HP TouchPad using TPtoolbox, Windows says that there is an F drive that I have to format before I use it. In the tutorials, a drive labeled HP TOUCHPAD or something like that shows in Windows, and you can put the Android files inside of the ttinstall folder. Should I format the drive and if so, what format?

Oh sorry, I posted to the wrong thread.