Related
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
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
Not quite sure if my touchpad is bricked or not. I had it set up to triple boot web os, android, and arch linux.
Due to an unknown error installing arch corrupts my android 'SD card.' So to fix this I was going to start over, doctor the tablet to stock, moboot, install arch then put on android.
I put the tablet into the USB/recovery mode (power + volume up,) started doctoring it (doctored as normal, rebooted tablet, showed the arrow pointing to the chip)
When it was done the tablet restarted, then it went into this infinite boot loop. I left it for about half an hour, when I came back it was still stuck, holding the power button doesn't do anything, so I power+volume+center button to force shut down. Now it won't start, when I plug it into my computer it registers as an unknown device with the name of "palm"
I've looked and no one has had the 'same' problem as I have.
2kool4u526 said:
Not quite sure if my touchpad is bricked or not. I had it set up to triple boot web os, android, and arch linux.
Due to an unknown error installing arch corrupts my android 'SD card.' So to fix this I was going to start over, doctor the tablet to stock, moboot, install arch then put on android.
I put the tablet into the USB/recovery mode (power + volume up,) started doctoring it (doctored as normal, rebooted tablet, showed the arrow pointing to the chip)
When it was done the tablet restarted, then it went into this infinite boot loop. I left it for about half an hour, when I came back it was still stuck, holding the power button doesn't do anything, so I power+volume+center button to force shut down. Now it won't start, when I plug it into my computer it registers as an unknown device with the name of "palm"
I've looked and no one has had the 'same' problem as I have.
Click to expand...
Click to collapse
Read this thread, it might help : http://forum.xda-developers.com/showthread.php?t=1426244
Good luck.
I went to try that out today, i pressed the power button and it came up with the Low Battery icon, so i plugged the charger into the tablet and it just hangs at the image. It charged for over an hour an a half, but still shows the dead battery symbol.
Condition just keeps getting worse :/
After leaving the touchpad disconnected since my last post, I got home tonight and tried something new, knowing the battery was dead again, I held the "power + volume up" until the device turned on. When it did, it displayed the dead battery symbol, WHILE STILL HOLDING THE POWER+VOLUME BUTTON, I plugged the tablet into the wall charger, and then left it to charge for about 45 min. When I came back it was displaying the usb connect mode, from there I used the guide posted above. I reformatted the logical volumes, starting webos doctor 3.0 my touchpad battery died again, so its charging now, ill try again in a bit. But many, many thanks to you for posting that guide, I thought my touchpad turned into a paperweight.
2kool4u526 said:
After leaving the touchpad disconnected since my last post, I got home tonight and tried something new, knowing the battery was dead again, I held the "power + volume up" until the device turned on. When it did, it displayed the dead battery symbol, WHILE STILL HOLDING THE POWER+VOLUME BUTTON, I plugged the tablet into the wall charger, and then left it to charge for about 45 min. When I came back it was displaying the usb connect mode, from there I used the guide posted above. I reformatted the logical volumes, starting webos doctor 3.0 my touchpad battery died again, so its charging now, ill try again in a bit. But many, many thanks to you for posting that guide, I thought my touchpad turned into a paperweight.
Click to expand...
Click to collapse
Try to not let the TP run out of power completely, it's definitely not good for it. I'm glad you got it running again.
chicle_11 said:
Read this thread, it might help : http://forum.xda-developers.com/showthread.php?t=1426244
Good luck.
Click to expand...
Click to collapse
I have similar issue as OP. My TP will not charge or even boot up after unsuccessful "visit" to the doctor (12% freeze error then strange pc disconnect)... I have same "palm" recognition in device manager. The screen had HP logo with chip. I messed up and reset the TP now won't start up...
I will let it sit on the charger for a bit. Any suggestions to recovery this is appreciated.
mexigga said:
I have similar issue as OP. My TP will not charge or even boot up after unsuccessful "visit" to the doctor (12% freeze error then strange pc disconnect)... I have same "palm" recognition in device manager. The screen had HP logo with chip. I messed up and reset the TP now won't start up...
I will let it sit on the charger for a bit. Any suggestions to recovery this is appreciated.
Click to expand...
Click to collapse
Leave it plugged in for at least a few hours, then try the link.
http://forum.xda-developers.com/showthread.php?t=1426244
chicle_11 said:
Leave it plugged in for at least a few hours, then try the link.
http://forum.xda-developers.com/showthread.php?t=1426244
Click to expand...
Click to collapse
Ok, I'll give it a shot.
thing is dead... Only pc picks it up as a palm device...
Will a battery pull do any good?
Bump.
mexigga said:
thing is dead... Only pc picks it up as a palm device...
Will a battery pull do any good?
Click to expand...
Click to collapse
I don't know if you've solved the problem or not, but take a look at this thread :
http://forum.xda-developers.com/showthread.php?t=1971859
I hope it helps.
BTW, it's a pain to get to the battery (opening the TP).
chicle_11 said:
I don't know if you've solved the problem or not, but take a look at this thread :
http://forum.xda-developers.com/showthread.php?t=1971859
I hope it helps.
BTW, it's a pain to get to the battery (opening the TP).
Click to expand...
Click to collapse
thanks...I checked this out and if only I could get the TP into USB mode I'd be home free. I believe it to be stuck in download mode. The last screen I saw was the white arrow with the micro chip
So my touchpad refuses to turn on / charge. Its a CM9 that had no prior problems. I do not own a touchstone nor an original touchpad charger anymore (idk where I lost it) but I have tried to charge the original battery with about 9 different chargers to no avail. I got a new battery off feebay and swapped it with no problems, but the new battery appears to be dead as well and still won't charge. I have plugged the touchpad into the computer and gotten it to pop up the "installing new hardware" thing but it always fails. Under device manager it has show "Palm" with the ! and "QHUSB_DLOAD" with the !. I tried to get Webos doctor to recognize it but it won't. Please help or I will have to buy a Nexus 7 this week as I work in an office alone as tech support and this is the slow season -.-.
This might be worth looking at http://forum.xda-developers.com/showthread.php?t=2010270
Sent from my SAMSUNG-SGH-T989 using xda premium
Hello guys,
I'm new here at the HP Touchpad Section and XDA-Dev Forums.
I am running CM7 on our HP Touchpad and my little brother has been fiddling with it(downloading many apps from the playstore using my personal account, thus forcing me to create a new google account/other shiz).
Then one time, the screen kept turning on and off without us even touching it. Our guess was it was dust on the screen which is being register as touch.
After a week or so that that was happening, the touchpad ran out of battery and was not charged right away.
The result, it won't charge anymore.
Is there anyway to open the device and shock the battery? It may be a dead battery just like what happened to my sister's iPhone.
I've also been reading some charging issues with CM7 and CM9 and tried some of their troubleshooting methods but non worked.
If I just get a little juice to boot it, I would reboot back to webOS as fast as I can and uninstall CM7.
Thanks in advance,
Raphael
SCPadgeebar said:
Hello guys,
I'm new here at the HP Touchpad Section and XDA-Dev Forums.
I am running CM7 on our HP Touchpad and my little brother has been fiddling with it(downloading many apps from the playstore using my personal account, thus forcing me to create a new google account/other shiz).
Then one time, the screen kept turning on and off without us even touching it. Our guess was it was dust on the screen which is being register as touch.
After a week or so that that was happening, the touchpad ran out of battery and was not charged right away.
The result, it won't charge anymore.
Is there anyway to open the device and shock the battery? It may be a dead battery just like what happened to my sister's iPhone.
I've also been reading some charging issues with CM7 and CM9 and tried some of their troubleshooting methods but non worked.
If I just get a little juice to boot it, I would reboot back to webOS as fast as I can and uninstall CM7.
Thanks in advance,
Raphael
Click to expand...
Click to collapse
Try leaving it on the stock charger for several hours, maybe days. If you have a touchstone, try that.
If you get it to charge (make sure it's fully charged), uninstall CM7 using acmeuninstaller, then boot into webos. If you have preware installed fine, if not install it and download 'remove android' (or something like that). Run it, then install either CM9 or cm10, using acmeinstaller3. There are several good how-to's which you can search for here or at webos nation forum.
When you have it installed, go to settings > storage and click on the 3 little squares on the upper right hand side, and click on usb computer connection. Then make sure the MTP box is checked.
Hope this helps. Good luck.
chicle_11 said:
Try leaving it on the stock charger for several hours, maybe days. If you have a touchstone, try that.
If you get it to charge (make sure it's fully charged), uninstall CM7 using acmeuninstaller, then boot into webos. If you have preware installed fine, if not install it and download 'remove android' (or something like that). Run it, then install either CM9 or cm10, using acmeinstaller3. There are several good how-to's which you can search for here or at webos nation forum.
When you have it installed, go to settings > storage and click on the 3 little squares on the upper right hand side, and click on usb computer connection. Then make sure the MTP box is checked.
Hope this helps. Good luck.
Click to expand...
Click to collapse
Thans for the reply chicle_11! Will try that on the weekends since I am very busy with school works. And thanks for the suggestion of installing CM9/CM10 but I will just stick to webOS and get an authentic Android Tablet(I'm choosing between Google Nexus 10 or Samsung Note 10.1).
I use webos at least 50% of the time. It's a shame that there aren't more apps compared to android. You don't have anything to lose by installing android. You'll have an excellent and unique dual boot tablet. CM10 is very stable now, I use it as my daily driver, I highly recommend it.
chicle_11 said:
I use webos at least 50% of the time. It's a shame that there aren't more apps compared to android. You don't have anything to lose by installing android. You'll have an excellent and unique dual boot tablet. CM10 is very stable now, I use it as my daily driver, I highly recommend it.
Click to expand...
Click to collapse
I still might reconsider flashing CM9/CM10 when I sort out the charging problems since I am just starting to save money for the Note 10.1/Nexus10.
Can you recommend a good CM10-based ROM for the HPTP or just the stock CM10 Jcsullins?
I use/recommend jcsullins' cm10.
Make sure MTP is checked (follow my first post) and that should take care of the charging problems.
Also, try to not let the battery run out of power. It could possibly brick the tablet.
It seems that I have somewhat sorted out the charging problems. I read an article last night that Samsung Chargers also work for the HPTP.
The process is fairly simple. Use the Samsung Charger first to charge a phone. After 2 hours or so, use that charger for the HPTP to charge the touchpad from a used/electrified wire. During the other process, use the HPTP Charger for the phone to power the cord up. After 10mins or so, switch both chargers. So the HPTP should be using the one that came with it by this time.
It worked for a while then the "Please use the charging cable that came blah blah blah to fully charge..." message came. I've read another article that the touchpad should be a little elevated or at least level with the cord so the cord will not fall down that is causing the message to pop up.
I've used both methods and the 2nd method is working like a charm. It shows a battery sign with a lightning bolt and the charging warning/message does not pop up. Will leave it overnight to see if it charges.
Then after, I might reinstall CM9(I've been from CM9 but downgraded to CM7 because of camera issues w/c my lil bro does not like).
So I left it overnight and it charged when I used the 2nd Method. Happy Days!
SCPadgeebar said:
During the other process, use the HPTP Charger for the phone to the cord up. After 10mins or so, switch both chargers. So the HPTP should be using the one that came with it by this time.
Click to expand...
Click to collapse
What?
*fixed*
Sorry, That was late night here in the PHL and was a bit sleepy when I was posting that.
Also have dead touchpad
I haven't been able to see any life from my touchpad after the battery completely drained. Its been 2 days since I haven't been able to use it.
I've tried charging it via the cable and adapter that came with it for a couple of hours, left my TP on the touchstone all afternoon to morning and no life either, the touchpad however is a bit warm at the back. Does that indicate its charging?
my TP is sitting on the touchstone now but I've replaced the AC adapter and currently using my HTC Sensation plug, I am running out of ideas and I'm going to presume its completely dead.........
I've tried connecting it to the pc but nothing happens, Can someone help me out, I've also tried the button combinations "Home, Home+Power and Home+Power+VolumeUp"
I tried both of the methods mentioned a couple of posts ago with no success.
I have also left it on the regular AC charger for 48+ hours and a Samsung cell phone charger for another 48+ hours and nothing.
It is sitting on the Touchstone now for 36+ hours and nothing yet.
I sent HP an email and here is what they said to try:
"We gather from your mail that your Touchpad is unresponsive and will not turn on. To be able to help you with this issue please take note of the following troubleshooting steps:
First of all leave the device on charge with charger for 48 hours after do the following:
Press and hold the power button + Center for 15 seconds. The device may take a few minutes to restart.
Please do the above with the device connected to the charger. (not charging dock nor PC).
Press and hold the power button + volume Up + Center and continue holding for 5 seconds after the Full Erase screen appears.
Also please try the above steps with another USB cable, also please try to connect the USB to the computer with the touchpad, if the computer doesn't recognize the device, the USB cable is faulty.
Please try your charger on another device to see if this charges the device. As the issue could be that the AC adaptor that is not working.
Have you tried another charger with the Touchpad? In order to verify where is the problem. Regarding to your problem ,do you know if the problem is with the charger itself or with the USB cable? Have you tried the complete charger with another Device, phone?
If the steps given do not help you with this issue, please send us a Proof of Purchase (scan of store`s receipt attached to your response) to validate your warranty or the order creation date of your device and your address.
If you need further assistance, please reply to this message and we will be happy to assist you further.
For information on keeping your webOS and Palm products up and running, please visit our website at: http://www.hpwebOS.com
Sincerely,
HP webOS SUPPORT"
None of that worked either. I just get the "Palm device" balloon on Windows XP when I hold the Power+Volume Up + Center button. It looks for drivers but never finds them.
Also try holding Home + Power button for 30 seconds instead of 15...This has been known to force some life back for some
Con500 said:
Also try holding Home + Power button for 30 seconds instead of 15...This has been known to force some life back for some
Click to expand...
Click to collapse
Nothing after trying that and leaving it on the Touchstone for 48+ hours. Time to leave it plugged up to the computer for 48+ hours and see what happens.
Nothing after 48+ with the factory USB cable connected to a desktop computer.
It would be nice to see a solution that works every time instead of a bunch of guesses.
abomb78 said:
Nothing after 48+ with the factory USB cable connected to a desktop computer.
It would be nice to see a solution that works every time instead of a bunch of guesses.
Click to expand...
Click to collapse
First my observations on three 32 GB TP's:
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.
You PC's USB port may be causing further discharge to the 2% TP's auto shut-off!
Actually none of these goofy button pressing and charging methods was right. A6 was faulty. It is fixed now.
My TouchPad is dead
abomb78 said:
Actually none of these goofy button pressing and charging methods was right. A6 was faulty. It is fixed now.
Click to expand...
Click to collapse
My TouchPad discharged overnight and now just has a black screen. None of the button pressing or charging suggestions described in these forums has worked for me. I was just running webOS 3.0.5. No version of Android was on the TouchPad.
Please tell me the trick you used to revive your dead TouchPad. Was it just a problem with your Andriod OS?
Much thanks.
bluechip64 said:
My TouchPad discharged overnight and now just has a black screen. None of the button pressing or charging suggestions described in these forums has worked for me. I was just running webOS 3.0.5. No version of Android was on the TouchPad.
Please tell me the trick you used to revive your dead TouchPad. Was it just a problem with your Andriod OS?
Much thanks.
Click to expand...
Click to collapse
http://rootzwiki.com/topic/36658-tpdebrick-v01/page__st__300