Hey all,
Noob question. I recently went to JVP (doc kitchen) and tried out multiple kernels (speedmod, fugu, tegrak). I only noticed this issue after going to tegrak's kernel so suspect it's kernel related.
The issue I'm having/suspect is that after "100% charge" the battery would start to be consumed (even if it is plugged in). This is most noticeable if I'm at my desk at work all day (phone on charge) or when I leave my phone charging overnight. When I disconnect to go home/go to work, I can see the battery is at 85% or similar (as if the phone wasn't on charge). If I was to disconnect it as soon as it hit "100%" it'll be at 96/97/98% as expected.
I'm not an expert and logcat confuses the heck out of me to be honest, but would anyone know what strings I can search for to determine if the phone "stops charging" when it hits 100%? I'd prefer it to be on a trickle charge (ie keep the battery at 96/97/98%) so that when I disconnect, I have a near full battery.
Is this a kernel issue? or a battery level calibration issue?
TIA
cheddarchi said:
Hey all,
Noob question. I recently went to JVP (doc kitchen) and tried out multiple kernels (speedmod, fugu, tegrak). I only noticed this issue after going to tegrak's kernel so suspect it's kernel related.
The issue I'm having/suspect is that after "100% charge" the battery would start to be consumed (even if it is plugged in). This is most noticeable if I'm at my desk at work all day (phone on charge) or when I leave my phone charging overnight. When I disconnect to go home/go to work, I can see the battery is at 85% or similar (as if the phone wasn't on charge). If I was to disconnect it as soon as it hit "100%" it'll be at 96/97/98% as expected.
I'm not an expert and logcat confuses the heck out of me to be honest, but would anyone know what strings I can search for to determine if the phone "stops charging" when it hits 100%? I'd prefer it to be on a trickle charge (ie keep the battery at 96/97/98%) so that when I disconnect, I have a near full battery.
Is this a kernel issue? or a battery level calibration issue?
TIA
Click to expand...
Click to collapse
Please do this procedure and see... once u finish ur 2 or 3 cycle u'll get the result...
- Charge your battery full, bump charge to get the highest level possible ; note that it's not a big deal if it shows 97% when you unplug after bump-charging
- Drain your battery to 0% until it shuts down by itself (without plugging the charger or connecting the phone to a pc)
- Wait 2 minutes and reboot the phone to ensure the battery is completely flat (it might reboot fully, half way, not at all, don't worry) until it dies again
- Remove the battery and wait 2 minutes
- Replace the battery and plug the charger without switching the phone on until it shows 100%
- When phone shows 100%, boot in recovery (volume up + home + power) and go to > Advanced > Wipe Battery Stats > Confirm (move up/down using the volume keys)
- Reboot the phone and unplug the charger when the "battery full notification" comes (wait for the notification before you unplug the charger)
- Now use your phone until the battery is flat again and charge full (no need to have it turned off, unless you it to charge faster). Repeat 2 or 3 times and your battery will be calibrated
- Only wipe battery stats once, run a few cycles of full charge / discharge and after that just use your phone as normal (i.e. no need to deplete / charge fully anymore).
When I connect charger, TP starts and shows charging 1%, but within couple of mins charging goes to 0% and stucks there. i kept it charging overnight yesterday still it says 0. Even now, I kept it connected to charger and came to office, I am 100% usre, it will be at 0, after i go home.
Do you think battery is GONE? or the charger problem? (just got a new new cable) through the TP and get a new one? or is there a solution?
MY TP is rooted and i think its runnning CM 9 or 10.
SOLVED
I rebooted to webOS, and TP charged normally.
So my solution is, if TP doesnt charge, reboot to webOS and charge to 50%, once it got that much charge, it will charge in android also..
May be its a known solution, but I got in a lengthy way
i put charged on 93% and i see 19% charging but i plug in 93%. problem battery? today i chech how battery left until i not used before 2days i left with 85% and i see now 79% but i did reset default settings so battery dropped to 44 of 79 when i did reset default , not hard reset.
myka_1997 said:
i put charged on 93% and i see 19% charging but i plug in 93%. problem battery? today i chech how battery left until i not used before 2days i left with 85% and i see now 79% but i did reset default settings so battery dropped to 44 of 79 when i did reset default , not hard reset.
Click to expand...
Click to collapse
you have Used a Custom Rom Before?
Try calibrating the battery
drain battery 0% then charged it
then do it again and again
%
AnotherOneTest said:
you have Used a Custom Rom Before?
Try calibrating the battery
drain battery 0% then charged it
then do it again and again
Click to expand...
Click to collapse
i do nothing happens. my battery random shuts down at 19% and when i put charger shows 0 and i unplug usb to replug to do charge . when my phone turned off at 19% i put charger and shows 100% , i try boot up, restarted itself to homescreen and restart again. maybe motherboard ? when i press hard board near camera device shuts down. black screen. when i device incline to specific point i heard crack noise, then it shows 0% and booting fine not restarted when plugged in. before restarted even when i plug in to1charger and i see 100% after s but before shuts down at19% .sometimes when it shuts down at 19% . i plugged to charge i see 0% battery
myka_1997 said:
%
i do
Click to expand...
Click to collapse
How old is your battery?
4 years. Battery health 71%. 2200mah left
myka_1997 said:
4 years.
Click to expand...
Click to collapse
99.99% that is a reason
but discharge good not down dropped. i dont used phone for 3days battery was 78, when i did reset default settings not hard so when booted up phone shows battery 43
myka_1997 said:
but discharge good
Click to expand...
Click to collapse
Next step. Will come in month or two.
Nokono said:
Next step. Will come in month or two.
Click to expand...
Click to collapse
after 2 years battery random shuts down at 19%. when battery shuts down. phone shows battery thunder not charging. when i reinsert cable shows 0 or 40,or 100!!! but now strange thing when i unplug 93% and replug shows 19% charging how dropped??? when i power off when shows 19, that time i plug in charger when its off and it shows battery 40%
myka_1997 said:
after 2 years battery random shuts down at 19%. when battery shuts down. phone shows battery thunder not charging. when i reinsert cable shows 0 or 40,or 100!!! but now strange thing when i unplug 93% and replug shows 19% charging how dropped??? when i power off when shows 19, that time i plug in charger when its off and it shows battery 40%
Click to expand...
Click to collapse
May be power controller of the phone is broken too.
Try to charge to 100, then *#0228# and reset battery there, charge again till 100 and reset. Repeat untill battery stay 100 after reset.(on stock rom only)
If won't help go to service.
If you have root access then go with an explorer to "Devise\System\Media"
Look there if there are some files with ###.spi as file name.
Remove all these files and reboot the phone.
Hoop this will help you, on my phone it was working fine with the battery problems you described.
Scenic-3 said:
If you have root access then go with an explorer to "Devise\System\Media"
Look there if there are some files with ###.spi as file name.
Remove all these files and reboot the phone.
Hoop this will help you, on my phone it was working fine with the battery problems you described.
Click to expand...
Click to collapse
I dont root because pass the time
I'm stuck!
My touchpad was bumped off the wireless charger one night and the battery appeared to have died, and its never showed any lights, display, or signs of life since then. Tried multiple chargers and cables. I even replaced the battery which cost as much as another touchpad, disapppointingly no change, UGH
I found tpdebrick v005 and some instructions. Ran it on ubuntu 16, and got this error: https://imgur.com/a/D9AkT1c
I grabbed the typescript logs if those are useful to anyone ;-;
https://drive.google.com/file/d/1n9EvzIe3oPZaJDaIlDoropskC7Iq1IHn/view?usp=sharing
WOW
I was reading through this thread https://forum.xda-developers.com/showthread.php?t=2126307&page=14
I noticed @jaycee147 saying something about seeing the same error I have and using heat to get past it......IT WORKED!!!
I ran tpdebrick with the autoreset option, then kept applying 30 seconds of heat from my hair dryer, then retrying whenever any step failed. Each new attempt gave new behavior until it magically started booting itself!
When I shut it down to fully reattach the display and seal it up, it refused to power on and show any signs of life again....
Repeating the same process of heating and tpdebrick brought it back again.
I will leave it on the charger until it's full and for the sake of science try to reboot it again and post my results
it rebooted and survived
it was able to shut down for a few seconds, and power back on
but powering it off one last time and back on again its acting like its totally dead again. back at it again with the hairdryer and if I get it working again I assume I'll NEVER be able to let it shut off again?
Nillanic said:
it rebooted and survived
it was able to shut down for a few seconds, and power back on
but powering it off one last time and back on again its acting like its totally dead again. back at it again with the hairdryer and if I get it working again I assume I'll NEVER be able to let it shut off again?
Click to expand...
Click to collapse
Ambient temperature ( room temperature ) is very important when charging any Lithium ion battery. ( Warmer charges best than cold )
It is extremely important to never let the battery drain to zero capacity as it can go dormant and difficult to wake up.
The battery needs to be on charger for a full day, if the battery does not hold the charge check the " true capacity remaining"
I am way ahead of ya!
When I first got the tablet to boot up after reviving it, I let the battery charge to 100% for a few hours on the original touchpad charger
Once I shut it down and tried turning it back on, it refused.
Not sure what the battery charge has to do with this anymore? When I tore apart my old battery, the cells were still at 3.7 volts, so something else must have occured
Nillanic said:
I am way ahead of ya!
When I first got the tablet to boot up after reviving it, I let the battery charge to 100% for a few hours on the original touchpad charger
Once I shut it down and tried turning it back on, it refused.
Not sure what the battery charge has to do with this anymore? When I tore apart my old battery, the cells were still at 3.7 volts, so something else must have occured
Click to expand...
Click to collapse
The only way to really know the ( TRUE ) capacity of the battery is by doing the following:
open a command prompt or terminal on a PC with the novacom driver and enter:
novacom -t open tty://
then
battery status
To know all the details of the battery you can read this thread:
https://forum.xda-developers.com/showpost.php?p=80993173&postcount=17
The battery can be 100% charge but at what capacity?
I keep getting "unable to find device" after getting novacom to work : (
I searched these threads and can't find any solutions for this situation with novacom, supposedly there's supposed to be some sort of life from the tablet (buttons or display lighting up) for novacom to work?
I'm on ubuntu 12 32-bit using the same 32bit novacom drivers
Nillanic said:
I keep getting "unable to find device" after getting novacom to work : (
I searched these threads and can't find any solutions for this situation with novacom, supposedly there's supposed to be some sort of life from the tablet (buttons or display lighting up) for novacom to work?
I'm on ubuntu 12 32-bit using the same 32bit novacom drivers
Click to expand...
Click to collapse
For the novacom connection to work the Tablet needs to display the ( big white USB symbol )
select webOS Recovery from the moboot 0.3.8 menu.
When the USB symbol is shown then connect the tablet to PC using usb cable.
If the tablet is running low in memory, place the tablet on the wireless charger and use the usb cable to connect to PC at same time.
On this thread you can find a linux OS with the nocacom driver install, it can be boot from any PC or also be use in a virtual machine.
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-novacom-repair-android-t3960435
To automatically get into recovery mode with the tablet off.
Press and hold at the same time:
Power and volume down key ( closer to power )
The Tablet will boot into Recovery mode.
HP_TOUCHPAD said:
For the novacom connection to work the Tablet needs to display the ( big white USB symbol )
select webOS Recovery from the moboot 0.3.8 menu.
When the USB symbol is shown then connect the tablet to PC using usb cable.
If the tablet is running low in memory, place the tablet on the wireless charger and use the usb cable to connect to PC at same time.
On this thread you can find a linux OS with the nocacom driver install, it can be boot from any PC or also be use in a virtual machine.
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-novacom-repair-android-t3960435
Click to expand...
Click to collapse
I greatly appreciate you trying to help, but I've mentioned a few times now that I have no such signs of life on the tablet, so I don't know how this helps at all : /
Thanks
Nillanic said:
I greatly appreciate you trying to help, but I've mentioned a few times now that I have no such signs of life on the tablet, so I don't know how this helps at all : /
Thanks
Click to expand...
Click to collapse
Very contradicting information, on your #6 post the tablet did boot. You also tried heating the tablet with an air dryer and that made it to charge and also boot. If the Tablet did boot, then is not brick.
I will help, but can only provide proper guidance if the correct information is provided.
Correct! As I said in post #6, I heated the tablet up and I was able to get tpdebrick to run and the tablet booted up as if nothing wrong happened.
I charged the battery to 100%, then tested a reboot, which it survived.
I then tested a shutdown and power on, and it survived.
I finally tried shutting it down one last time, and at this point it refused to power on again, no show of any LEDs or display with any charger or cable.
I'm not contradicting, what I'm saying is after I got it to boot with heat and tpdebrick, I shut the tablet down, and now it's refusing to do anything again (no leds, no display with any charger)
I hope that clears it up
Nillanic said:
Correct! As I said in post #6, I heated the tablet up and I was able to get tpdebrick to run and the tablet booted up as if nothing wrong happened.
I charged the battery to 100%, then tested a reboot, which it survived.
The battery can show 100% charged, but the most important is the capacity.
If the capacity is very low, it will loose charge very quickly and go dormant.
I then tested a shutdown and power on, and it survived.
Then the Tablet is not brick, all components are working. It seems the issue is a battery with very low capacity.
I finally tried shutting it down one last time, and at this point it refused to power on again, no show of any LEDs or display with any charger or cable.
Was the Tablet connected to a charger or place on the wireless charger all the time while on and off?
I'm not contradicting, what I'm saying is after I got it to boot with heat and tpdebrick, I shut the tablet down, and now it's refusing to do anything again (no leds, no display with any charger)
Battery is depleted.
I hope that clears it up
Click to expand...
Click to collapse
Try to revived it as before, only with some heat. I do not know your ambient temperature, is better if is over 80F to take some charge. It will take longer or not work in cold.
Boot tablet while place on the wireless charger at all time, do not removed it from the charger.
Hmmmm...
When I had it charging, it started at 15%, and after a few hours it went to 100% . I see what you're saying re. capacity, wish I had checked that while it was working.
I did not have it on a charger when I tested my reboots / shutdowns : ( I had too much faith in the battery's charge and being able to bring it back if I goofed.
I've been trying to heat it up for a few hours this morning and run tpdebrick and I still get the fuse error, but it progresses, writes stuff, and aborts when waiting too long for fastboot.
I guess I'll keep trying the heat with tpdebrick while having it also on the wireless charger until it works
Nillanic said:
Hmmmm...
When I had it charging, it started at 15%, and after a few hours it went to 100% . I see what you're saying re. capacity, wish I had checked that while it was working.
It takes more than a couple of hours to charge at full capacity. It all depends on the capacity available or the battery health. If is less, it will take less time to charge.
I did not have it on a charger when I tested my reboots / shutdowns : ( I had too much faith in the battery's charge and being able to bring it back if I goofed.
The battery capacity must be very low, that is why it turned off after a couple of reboots or until the battery got empty.
I've been trying to heat it up for a few hours this morning and run tpdebrick and I still get the fuse error, but it progresses, writes stuff, and aborts when waiting too long for fastboot.
If the Tablet already rebooted, is not brick. It needs to be charge.
I guess I'll keep trying the heat with tpdebrick while having it also on the wireless charger until it works
Click to expand...
Click to collapse
Read this link very carefully, this is the real TRUTH of the tpdebrick process.
https://webos-internals.org/wiki/Last_Resort_Emergency_BootLoader_Recovery
If bootie on the flash disk has been damaged or corrupted in such a way that booting into recovery mode is not possible, the Pre is still not "bricked" as the OMAP3430 processor in the Pre provides for a mechanism to boot code from its USB interface.
The HP Touchpad uses the same OMAP3430 processor as the Pre and the same process to re-flash the bootie ( BIOS what is call on PC ) can be perform.
That is the process that tpdebrick is doing, reflashing the bootie.
Your tablet already booted, the bootie works.
I'm sorry, you're confusing me more.
How is it possible that when I put it on the OEM charger for a few hours and waited until it "reported" 100% that it still didn't have enough capacity to survive two shut-downs within a minute? The tablet wasn't off a charger for more than a few minutes total before it died.
The battery is brand new and still measures 3.7v at the cell. I have a hard time believing this is still the battery being a problem, but you certainly have more experience.
Are you saying I should follow the instructions on the link to recover, instead of tpdebrick?
Or are you saying my tablet is "working" right now and my battery is still too low? If this is the case shouldn't it show that it's charging? Shouldn't tpdebrick NOT fail at the fuse blown step in this case?
Thank you
Nillanic said:
I'm sorry, you're confusing me more.
I will try to explain it in a very generic and simple way.
How is it possible that when I put it on the OEM charger for a few hours and waited until it "reported" 100% that it still didn't have enough capacity to survive two shut-downs within a minute? The tablet wasn't off a charger for more than a few minutes total before it died.
Capacity or (battery health) = The amount of electricity it can be store in the active cells. (good cells ), dead cells or inactive does not store electricity.
The system reports 100% charge, but does not report the capacity. The only way to know is by entering the command using the novacom as mentioned before.
If the capacity is only 10% of active cells, it will show charge 100%, but it will lose charge very quickly.
This applies to all battery's.
The battery is brand new and still measures 3.7v at the cell. I have a hard time believing this is still the battery being a problem, but you certainly have more experience.
A battery can be new, but if stored improperly for many years can go bad.
The only way to know the battery health ( Capacity ) is by getting the reading of the A6 controller.
Are you saying I should follow the instructions on the link to recover, instead of tpdebrick?
The link I provided explains technically the reason a WebOS device may not boot.
And provides on how to re-flash the bootie and that is what the tpdebrick does.
tpdebrick is use to reflash the bootie to make the tablet to boot. It has nothing to do with the battery.
If a battery does not have enough electricity to power the internal components, the tablet can not boot.
If the bootie is damage, then it will not boot even if it has a brand new battery and full charge, then the tpdebrick needs to be done.
Or are you saying my tablet is "working" right now and my battery is still too low? If this is the case shouldn't it show that it's charging? Shouldn't tpdebrick NOT fail at the fuse blown step in this case?
Your tablet already booted, it shows all components were working, is not brick, by the way the tablet is un-brickable.
The tablet should show the LED light moving from side to side when connected to a charger. If not then try to warm it up and to intermittent charging, ON for 1 minute, OFF for 10 seconds. It can be done with the wireless charger. Place it on for one minute then remove it for 10 seconds. Do it many times, from time to time until it shows the LED light, then a low battery comes up and finally it will boot. Never remove it from the wireless charger.
Thank you
Click to expand...
Click to collapse
You are welcome, hopefully it resuscitates again !
Ok that all makes sense : )
I've been trying the intermittent charging w/ the wireless and heating it for the past hour and a half-ish, it's still not shown any signs of life. Should I keep going?
Oh, I have a kill-a-watt that tells me the power draw of anything plugged into it
Using the oem hp barrel charger, and the wireless pad, when plugging just the barrel into the socket, 0 amps. Plugging the wireless pad in, still 0 amps. Place touchpad on wireless charger, I see about 0.01-0.02 amps being drawn. The power draw never changes or fluctuates no matter how long it sits on the wireless pad
I don't see any amps pulled when trying to charge via microusb
Nillanic said:
Oh, I have a kill-a-watt that tells me the power draw of anything plugged into it
Using the oem hp barrel charger, and the wireless pad, when plugging just the barrel into the socket, 0 amps. Plugging the wireless pad in, still 0 amps. Place touchpad on wireless charger, I see about 0.01-0.02 amps being drawn. The power draw never changes or fluctuates no matter how long it sits on the wireless pad
I don't see any amps pulled when trying to charge via microusb
Click to expand...
Click to collapse
The wireless charger works better on charging a dead battery than the usb connection.
Make sure the ambient room temperature is over 80 F, or you can cover it while is been charge. You do this when you are home and supervising.
It can take time for the light to start blinking, some times like a week. Leave it on the charger and sometimes just pick it up and place it again, just when you are checking on it.
Leave it there for a couple of days.