Hi Guys,
Since a few weeks I have a weird problem with my u8800. The first thing I noticed was that the phone didn't charge properly; after a night of charging it would still not be fully charged. I thought it would be the battery that died (tho that would be a bit quick after half a year) so I replaced it with a replacement battery. This battery showed the same behaviour within a few days. Then I replaced the charger for another one; this kept things working for some time but eventually the problem returned. I also tried Wipe Battery Stats to no avail.
What's wrong? I dont't get it. If the phone's on the charger now, the red light is blinking. It doesn't charge beyond 3% so I can never take it off the charger.
I have Aurora ICS since a few months, keeping in pace with updates.
Any help would be very welcome cause this thing makes it impossible to use the phone as a mobile phone..
Install the official android 2.2 and see if the problem persists
Wipe the battery stats (in recovery). Afterwards try to fully reload the battery (even if it keeps blinking red) and keep it on the charger for 1-2 more hours. Then disconnect the charger and do not reload the battery until the phone turns itself off. Charge it fully one more time.
After following this procedure your battery should be fine. If wiping the battery stats in recovery does not work, there should be a program on the market which does the same.
If the procedure does not resolve the problem please send the device in for repair. If the battery charge does not go up to 100% after following the procedure please do the same. This is a hardware error.
XphX
Hi,
I wiped battery stats but charging won't go beyond 5%. What is the name of the app you talk about?
FORGET wipe battery stats, everyone knows that is placebo!!
sr21 said:
Install the official android 2.2 and see if the problem persists
Click to expand...
Click to collapse
Try that, its the best solution.
Sent from my U8800 using xda premium
I would do that, but it seems risky on a battery with only 5% accu left. AFAIK you cant do these operations with the usb connection as power source right?
toeter80 said:
I would do that, but it seems risky on a battery with only 5% accu left. AFAIK you cant do these operations with the usb connection as power source right?
Click to expand...
Click to collapse
Plug your phone to the charger (not usb) and you shouldn't have problems...
But how do I flash 2.2 without usb connection?
Format sdcard and put update on it with some adapter or go CWM > mounts and storage > USB mount.
Sent from my U8800 using Tapatalk 2
toeter80 said:
But how do I flash 2.2 without usb connection?
Click to expand...
Click to collapse
Put update file into the sdcard/internal card, plug the phone to the charger, and start the update by simply press Vol+, Vol- and Power.
Simple
----
Sorry for asking, but is there any clear reason why you guys expect flashing 2.2 might help? I ask because I expect this will cost me quite some time and I am trying to see what my succes chance is.
And, do you think I would be able to go back to Aurora ICS after flashing 2.2? I wouldn't want te be stuck on 2.2..
Thanks!
mrasquinho said:
FORGET wipe battery stats, everyone knows that is placebo!!
Try that, its the best solution.
Sent from my U8800 using xda premium
Click to expand...
Click to collapse
toeter80 said:
Sorry for asking, but is there any clear reason why you guys expect flashing 2.2 might help? I ask because I expect this will cost me quite some time and I am trying to see what my succes chance is.
And, do you think I would be able to go back to Aurora ICS after flashing 2.2? I wouldn't want te be stuck on 2.2..
Thanks!
Click to expand...
Click to collapse
Because 2.2 is the most stable rom/kernel. This way you can see if the problem is with your actual Aurora, or it's an hardware problem.
And yes, if you flash 2.2 you can go again to 2.3 and then flash Aurora ICS.
And please, read/search a little bit on the forum before placing those questions. Those questions have been answered a million times!
mrasquinho said:
FORGET wipe battery stats, everyone knows that is placebo!!
Click to expand...
Click to collapse
Not everyone knows that, at least I did not. I thought that maybe the ROM just wasn't showing the information correctly and therefore suggested wiping the stats. But if it does not work, forget it.
In this case flashing a different ROM won't help. A battery that cannot be loaded is a hardware defect - there has not been a single report that switching to Android 3 or 4 leads to this problem. The charging of the battery is only hardware-related (if it was software-related you would not be able to charge your phone when it is turned off!) and therefore the only possibility is that the device is defect.
mrasquinho said:
Because 2.2 is the most stable rom/kernel. This way you can see if the problem is with your actual Aurora, or it's an hardware problem.
Click to expand...
Click to collapse
This is wrong as I just explained. The charging process does not depend on Android or any software the OP could modify/change.
XphX
Moved To Q&A
Please post questions in the Q&A section
XphX said:
Not everyone knows that, at least I did not. I thought that maybe the ROM just wasn't showing the information correctly and therefore suggested wiping the stats. But if it does not work, forget it.
In this case flashing a different ROM won't help. A battery that cannot be loaded is a hardware defect - there has not been a single report that switching to Android 3 or 4 leads to this problem. The charging of the battery is only hardware-related (if it was software-related you would not be able to charge your phone when it is turned off!) and therefore the only possibility is that the device is defect.
This is wrong as I just explained. The charging process does not depend on Android or any software the OP could modify/change.
XphX
Click to expand...
Click to collapse
As I said, it is one of two: it could be a problem with Aurora installation or an hardware problem.
Install 2.2. If it is a rom problem, it should work right with 2.2 (it could be some kind of problem during the installation that have corrupted some files.)
If it is an hardware problem, it'll continue to have the problem. Simple
Sent from my U8800 using xda premium
mrasquinho said:
As I said, it is one of two: it could be a problem with Aurora installation or an hardware problem.
Click to expand...
Click to collapse
Please read once more; I stated why the Aurora installation has nothing to do with this. I cannot explain this better than I already did, but I'll try again if there is something confusing.
XphX
I don't have this problem with X5, but I've tried to fix it on a friend's other android model.
The behaviour was similar, the battery never goes to 100 % and can show from 80% 1% after minutes, and phone deactivated.
First I thought that was rom' s problem(had a CM7 custom rom), so I made a full wipe.
Problem doesn' t solved. After I changed the rom with another one(Ligux), but problem still there. Then I tried to charge it with another cable and without to power on. No difference.
So, I've flash the official rom. After that I managed to charge it normally until 100%. And seems that working fine now. The official roms change more things on the device than any custom, and seems that this problem caused from another part of the software which doesn't belong to system or boot.img(these are the parts which custom roms usually replace).
If you read the official PDF file that comes with stock roms it actually specifies that you should REMOVE THE BATTERY and connect it directly via USB while flashing the ROM So 5% charge is not even needed, just remove the battery and flash a stock rom!
OK, somehow the problem spontaneously solved itself and my phone worked fine for some time. But now it's back unfortunately. This time however I saw how it started. I think this is what happens: the battery goes too empty. So the phone crashes because of that (no proper shutdown). Then when putting it on the charger it sees the battery that is too empty as a faulty battery (indicated by the red blinking led, no charging animation visible). The phone won't power on.
There's a trick to get it to turn on though: remove the battery, plug in the power cable and it turns on. As soon as the Huawei logo appears put the battery back in (or a boot loop will happen). Then, there's a chance it will start charging again (though sometimes that only happens after many attempts).
Now the question is, why does it go too empty and is it possible to prevent this?
Related
As the title says I have a strange yet very annoying problem. I am running my HD2 with hyperdroid cm7 Nand build (from april 29th). The problem is that when my battery is deleted, as is the case now, and I put my hd2 in the charger it will automatically boot. I think this is due to a setting or something. However since booting drains energy faster than the hd2 charges, the phone will by turned of before it has completely booted. After a while it get's stuck in a pattern of starting to boot and turning of. I don't know why this is the case because I think my phone just used to boot fine before when connected to a charger.
So my questions are:
1. does anyone has a suggestion how to turn on the phone?
2. this automatic booting, can it be turned off?
3. Why is it actually happening?
Maybe it's a very stupid or obvious problem, but I hope someone can help me though.
Do you have installed MGLRD?, it's a Known fact, search in the forum for answer (I'm sorry, I'm with SD Builds and don't use MGLRD, so I can not help you anymore).
I had the same problem with some rom i used earlier. The only way i could solve the issue was to remove the battery and put it back, then I could insert the charger without the phone booting up. Charge it for a while and start it.
Hope this way works for u 2.
Sent from my Desire HD using XDA App
I guess this is what I used to do as well. However now, if I remove the battery and put it back in it keeps automatically booting. Also if I put the charger in the phone and then remove the battery same thing happens. But thanks for the help though.
I am currently using the same ROM via MGLRD. Because of MGLRD, it will always turn on the phone from off when you plug your phone in. This is a known feature of MGLRD to preserve the battery. Checking just now, I turned my phone off, plugged in my charger and the phone automatically booted itself then the lockscreen came on then turned itself off after one minute. This is the cycle I see every time I charge my phone if it is off. I do not see it going into any boot cycle. What I see is after it goes through this, the orange LED light is on letting me know it is charging and will change to green when it is fully charged. Did you make sure before loading the ROM to do a complete wipe before installing? Usually most of the problems are associated due to not doing a complete wipe prior to loading a new ROM.
slbenz said:
I am currently using the same ROM via MGLRD. Because of MGLRD, it will always turn on the phone from off when you plug your phone in. This is a known feature of MGLRD to preserve the battery. Checking just now, I turned my phone off, plugged in my charger and the phone automatically booted itself then the lockscreen came on then turned itself off after one minute. This is the cycle I see every time I charge my phone if it is off. I do not see it going into any boot cycle. What I see is after it goes through this, the orange LED light is on letting me know it is charging and will change to green when it is fully charged. Did you make sure before loading the ROM to do a complete wipe before installing? Usually most of the problems are associated due to not doing a complete wipe prior to loading a new ROM.
Click to expand...
Click to collapse
Well, this cycle I think is caused by the fact that the charger is not strong enough. Normally if plugged in the phone would just boot. The reason that it fails to boot is that is doesn't have enough power to complete the boot cycle even though the phone is plugged in (don't know if booting consumes a lot of power?).
A month ago I bought a new usb cable. Maybe that's where the problem lies? Because I have been using the hyperdroid rom for a while now. Although I don't know if one cable can be stronger than the other.
I have found a solution btw: Though it is a bit hit and miss cause it didn't work a few hours ago. When booting I let it go into mgldr and let it charge there. After a while I'll let it boot when it has enough power to complete the boot.
slbenz said:
Usually most of the problems are associated due to not doing a complete wipe prior to loading a new ROM.
Click to expand...
Click to collapse
Humm, now you making me think lol, the 1st time I installed Android on my HTC HD2 was the NexusHd2 rom one and he had the same problem, no battery but once I plug it to the wall charger it would do the full(normal)boot, I thought was the rom so I changed to Hyperdroid Cm7, but, still does the same..
The wipe you talking is the one, wipe data/cache right?
if it happens to you a lot, I think it's time to invest in a third-party battery charger. you can charge it out of the phone for a bit, and then you're safe to put it back in a continue charging using the phone
Tried some different roms and all them do the same.. so I reckon its normal.. Thank You.
Hey guys
Im looking for some help, although im not sure theres much that can be done...
These are the steps i did on an Australian p6810 stock device:
Install ICS using odin
Using temporary CWM, root the device
Flash CM9 to it
Wiped dalvik, batt stats, cache, factory restore (in both stock and cwm)
Boot to CM9 fine, but wifi doesnt work
Apply the wifi.zip fix as well as gapps
Boot to CM9 fine, but wifi doesnt work and gapps arent visible (or installed)
Applied the fix and gapps again, still didnt fix
So i decided to reflash CM9
Flashed CM9 and straight after did gapps and wifi.zip
Did a CWM factory reset
During the reset process (which took a loooong time), my device turned off (pretty sure it had plenty of battery)
BRICK
Now i cant turn my tab on at all. The screen doesnt respond, no matter how long or how many times i press the power button
Any help?!
have you try to charge your tab... then try to go to download mode... if it still working... flash stock ics again...
edan1979 said:
have you try to charge your tab... then try to go to download mode... if it still working... flash stock ics again...
Click to expand...
Click to collapse
its been charging for about half an hour. still not turning on so cant get to download mode!
I was reading a post on here about bricking and battery issue with the tab 7.7 which should be easy for you to find...Google it
On that post they spoke about taking the tab to any cell shop and having different battery packs put to it and this had revived the tab, the two guys who had got it working again said they had used a bigger voltage / amp battery to kick it back to life again. do a search and see what you find.
Now dont get me wrong, I have no idea how they got to do that as the battery is built in and the power connection is through the 30pin cable....maybe they plugged in the 30pin and used a transformer on the USB side to jump the battery back to life, I have done something like that before on a old phone that didnt charge and it worked, but its not the safest as wrong voltage could pop something.
Or the only other thing I can think of is the battery is totally dead or broken, in that case I would suggest a repair shop....but thats last on the list!
I am sure it might not have been enough charge before you strated...I had my battery die over night and it took a good 30min on charge to start showing any charge life at all.
Once you get the power working, I am sure we can un-brick your baby for you
slide200sx said:
I was reading a post on here about bricking and battery issue with the tab 7.7 which should be easy for you to find...Google it
On that post they spoke about taking the tab to any cell shop and having different battery packs put to it and this had revived the tab, the two guys who had got it working again said they had used a bigger voltage / amp battery to kick it back to life again. do a search and see what you find.
Now dont get me wrong, I have no idea how they got to do that as the battery is built in and the power connection is through the 30pin cable....maybe they plugged in the 30pin and used a transformer on the USB side to jump the battery back to life, I have done something like that before on a old phone that didnt charge and it worked, but its not the safest as wrong voltage could pop something.
Or the only other thing I can think of is the battery is totally dead or broken, in that case I would suggest a repair shop....but thats last on the list!
I am sure it might not have been enough charge before you strated...I had my battery die over night and it took a good 30min on charge to start showing any charge life at all.
Once you get the power working, I am sure we can un-brick your baby for you
Click to expand...
Click to collapse
Thanks for the advice! I'm not sure it's a battery problem though? Is there anyway I can tell?
To be honest, the only way you are going to know if the battery is the issue is if you take it for a battery swop....will be a samsung outlet and cost you. I have heard that some 7.7's that have done wipes from in CWM and not the 3e recovery have caused bricking, it may be that this has happened to you. please check the other brick posts on here and I am sure after reading them all you will have a better idea of what is going on. before I do anything on mine I check all the bricking posts to see what could cause the problem and stay away from those changes or mods....if possible
sometimes plugging it in and out of the wall charger and then computer and back again to wall might help, I dont promise anything.
how long have tried holding the power button, and have you tried holding the power button while pluggin it in....
let me know what happen's please....
slide200sx said:
To be honest, the only way you are going to know if the battery is the issue is if you take it for a battery swop....will be a samsung outlet and cost you. I have heard that some 7.7's that have done wipes from in CWM and not the 3e recovery have caused bricking, it may be that this has happened to you. please check the other brick posts on here and I am sure after reading them all you will have a better idea of what is going on. before I do anything on mine I check all the bricking posts to see what could cause the problem and stay away from those changes or mods....if possible
sometimes plugging it in and out of the wall charger and then computer and back again to wall might help, I dont promise anything.
how long have tried holding the power button, and have you tried holding the power button while pluggin it in....
let me know what happen's please....
Click to expand...
Click to collapse
So i took apart my tab in hopes i could do a battery pull:
http://www.jtagbox.com/jtag-news/ri...y-tab-77-unbrick-boot-repair-supported-world/
and no luck, it doesnt auto power on
Im considering doing jtag... but hmmmmm
https://www.dropbox.com/sh/rqhhgs34vuzt4u4/fGwL0TiSYc
i pulled out the power/battery cable, plugged the tab into the computer and then plugged the power in. nothing.
it also didnt work when i plugged it into the wall
When plugged in my wifi chip gets warm... hmmm
@Scottyn...
Dude, you need to do the swopping of power from wall socket to computer then back again and again and again......all the time while doing this holding the power button in.....try it
Also, if you have puled the thing apart now you should be able to test the battery for power with a volt meter or something....
does the battery have power...
does the battery get power from the cable or pin running to the battery?
Can you turn the tablet on with a different power source to the battery terminal on the phone?
I would check these things first, then hold thumbs....I dont know, if it's not the battery then it may very well be a dead hardware issue and not a data issue or fried memory as they will normally boot the tablet to a point.....
May very well be the battery cooked
Im too scared to attach a an external powersource to replace the battery. I have the equipment, but it could easily fry the rest of the board
Ive closed the device back up, so ill have to reopen it before i chuck a voltmeter on the batteries
and ive swapped from computer to the wall about 10 times (swapping every 5 seconds). Nothing
Plus; if i diagnose the problem as a fried battery then cant really do anything about it
scottyn said:
Hey guys
Im looking for some help, although im not sure theres much that can be done...
These are the steps i did on an Australian p6810 stock device:
Install ICS using odin
Using temporary CWM, root the device
Flash CM9 to it
Wiped dalvik, batt stats, cache, factory restore (in both stock and cwm)
Boot to CM9 fine, but wifi doesnt work
Apply the wifi.zip fix as well as gapps
Boot to CM9 fine, but wifi doesnt work and gapps arent visible (or installed)
Applied the fix and gapps again, still didnt fix
So i decided to reflash CM9
Flashed CM9 and straight after did gapps and wifi.zip
Did a CWM factory reset
During the reset process (which took a loooong time), my device turned off (pretty sure it had plenty of battery)
BRICK
Now i cant turn my tab on at all. The screen doesnt respond, no matter how long or how many times i press the power button
Any help?!
Click to expand...
Click to collapse
We had a similar faith. It was when this wiping thingy messed up my Tab. My only consolation was that my Tab is under warranty and did some make up story at the service center. Had replaced the motherboard and now up and running. I'd promised myself that I'll limit my "genius" with rooting and flashing an official fw. Custom rom is a big no for me, no matter how great and stable it was. The wiping part is like kiss of brick. Yes, i know...there's a disclaimer.
sweet. Ive decided to send it all back over to australia. annoying, but ill get a guaranteed fix
I think ill stick to stock ICS from now on
scottyn said:
So i took apart my tab in hopes i could do a battery pull:
http://www.jtagbox.com/jtag-news/ri...y-tab-77-unbrick-boot-repair-supported-world/
Do you mean you opened up the tabs case?
how did you do this?
any pics?
I ve read you have to lift the screen from the back cover..
It scares me to think about levering it and cracking the screen or something..
Click to expand...
Click to collapse
Hi everyone
Hope you can help with this issue with my N4. It shuts down with the battery at 90%. Works fine before for some time, but as soon as it goes down to 90% (sometimes less) it starts acting as if the battery ran out. I try to turn it on again and it barely stays on for 30 seconds (if I'm lucky) before shutting down again. The battery is brand new (it was my first idea as the old one had blown up, but the issue persists). I'm using a CM11 up to date. I am now installing CWM recovery, because the other one I'm using now doesn't allow to wipe battery stats and will try to change the ROM tonight but I doubt that is going to do anything as I used the ROM for a long time before the issues appeared. Any ideas?
Thanks in advance
CWM recovery doesn't give me the option to wipe battery stats. I'll try to change the rom in a while, see if that works
Installed Paranoid Android (wiped data and cache) but issue still persists.
jmoren44 said:
Installed Paranoid Android (wiped data and cache) but issue still persists.
Click to expand...
Click to collapse
I would recommend you. to calibrate your battery if still problem persists flash the factory image
Yes, try flashing the 4.4.4 factory image, if thaf doesn't work go back to 4.2.2 using the factory image (testing on each one) and if it still happens, than I'm afraid it is most likely a hardware issue.
Sent from my Nexus 4 using XDA Free mobile app
I suspect it's the piece that connects the batter to the motherboard. Does this mean I will need to replace the whole motherboard?
jmoren44 said:
I suspect it's the piece that connects the batter to the motherboard. Does this mean I will need to replace the whole motherboard?
Click to expand...
Click to collapse
If it is not the small cable that links the battery to the motherboard, the answer is yes, you'll have to change the motherboard entirely.
If you still have the old battery, you can use it for a day to see if the same problem occurs.
To delete battery stats in CM11, you only need to push the delete bouton wich is in the battery settings just make sur the phone is fully charged before doing it.
TheDeathlord said:
If it is not the small cable that links the battery to the motherboard, the answer is yes, you'll have to change the motherboard entirely.
If you still have the old battery, you can use it for a day to see if the same problem occurs.
To delete battery stats in CM11, you only need to push the delete bouton wich is in the battery settings just make sur the phone is fully charged before doing it.
Click to expand...
Click to collapse
It definitely is the plastic piece in the motherboard with the four pins that connects to the battery, I get it to work for a couple of days if the screws are very tight, but after two days I' back opening the Nexus up again. I am having a hard time trying to find a motherboard (16GB if possible, though I'm willing to settle for 8). Any ideas? I'm in UK.
Thank you all very much for the help, by the way.
Hello guys, this is my first time posting up in XDA and I am encountering a very weird problem with my N4
Disclaimer, the following is a long write but please bear with me and give a read.
Here's my problem after flashing the simple asop 29/5 build for mako. I come from same rom build 21/5 but i did a clean flash for the latest build. As soon as success flashing the latest build with gapps, then as usual will proceed reboot the system. Just right before the boot animation, the phone immediately went dead. I am sure that the phone is still left with 50%+ of battery at the moment.
Anyhow, I decided to plug it into charger. And voila, the phone now able to go through the boot animation and everything just fine. After setting up and restoring backups, I unplugged the charger, its 75%+ on the battery. Within 10-15 seconds, the phone immediately go dead again. I hit the power button and tried to boot up. Again, right after the Google logo screen, the phone went dead.
Commonly this indicate a problem with the battery. Yeah, but I went into recovery twrp and disabled the screen timeout & max the brightness. Guess what, surprisingly it lasted more than an hour which proves that this wasn't battery fault.
What had I tried so far, is just switched off the phone and plugged into charge for 2 hours. And obviously it doesnt solve the problem. I am backing up all the data at the moment and plans to drain the battery all the way down just leaving it screen on at recovery.
Anyone who know what happening with my n4 or encounter similar experience, please feel free to share the solution. Many thanks
Jz Chong said:
Hello guys, this is my first time posting up in XDA and I am encountering a very weird problem with my N4
Disclaimer, the following is a long write but please bear with me and give a read.
Here's my problem after flashing the simple asop 29/5 build for mako. I come from same rom build 21/5 but i did a clean flash for the latest build. As soon as success flashing the latest build with gapps, then as usual will proceed reboot the system. Just right before the boot animation, the phone immediately went dead. I am sure that the phone is still left with 50%+ of battery at the moment.
Anyhow, I decided to plug it into charger. And voila, the phone now able to go through the boot animation and everything just fine. After setting up and restoring backups, I unplugged the charger, its 75%+ on the battery. Within 10-15 seconds, the phone immediately go dead again. I hit the power button and tried to boot up. Again, right after the Google logo screen, the phone went dead.
Commonly this indicate a problem with the battery. Yeah, but I went into recovery twrp and disabled the screen timeout & max the brightness. Guess what, surprisingly it lasted more than an hour which proves that this wasn't battery fault.
What had I tried so far, is just switched off the phone and plugged into charge for 2 hours. And obviously it doesnt solve the problem. I am backing up all the data at the moment and plans to drain the battery all the way down just leaving it screen on at recovery.
Anyone who know what happening with my n4 or encounter similar experience, please feel free to share the solution. Many thanks
Click to expand...
Click to collapse
Have you tried making a clean wipe and trying either stock or another ROM, to see if it works then?
Your test doesn't prove it's not the battery's fault. Flash back to stock, see if the problem persists and if it does then you know you have a hardware problem. Could be the battery.
DrFredPhD said:
Your test doesn't prove it's not the battery's fault. Flash back to stock, see if the problem persists and if it does then you know you have a hardware problem. Could be the battery.
Click to expand...
Click to collapse
Hello, much appreciate your reply. I flashed back to stock 5.1.1 now and yet this problem is still persisting. Thus pretty obvious thats an hardware faulty.
In another forum, a guy with Nexus 7 had similar situation as me, and he suggests that its the battery or the circuit board at the charging port went kaput.
Guess nothing else I could do right now, gonna send in the phone for repair and hope the bill wont cost as much as a used nexus 4
Looking for a little insight here my XT1563 will not charge unless its in TWRP. The battery will remain at a constant % when plugged but will not charge and the battery menu list it as not charging as well. The obvious has been checked such as cord and charger to no avail. The interesting thing is the battery temperature is listed as like 429493709 Celsius in TWRP, when I run adb shell dumpsys battery it shows the following:
Current Battery Service state:
AC powered: false
USB powered: true
Wireless powered: false
Max charging current: 500000
status: 3
health: 7
present: true
level: 77
scale: 100
voltage: 4152
temperature: -302
technology: Li-ion
Click to expand...
Click to collapse
The temperature again is what I'm drawn too, what would cause it to be listed as -30.2 Celsius? I'm sure that is the reason why TWRP numbers is all messed up as well.
Edit: I've also just looked up the definition of health level 7 which is BATTERY_HEALTH_COLD.
see if this helps. https://stanfy.com/blog/android-shell-part-1-mocking-battery-status/
try the last command - adb shell dumpsys battery reset
bablu048 said:
see if this helps. https://stanfy.com/blog/android-shell-part-1-mocking-battery-status/
try the last command - adb shell dumpsys battery reset
Click to expand...
Click to collapse
Thanks for the tip I was wondering if there was a way to mock battery status. Unfortunately running that command to reset it instantly sets it back to -302 temperature. Also that command can't mock the health so its not like I could just leave it mocked to allow the phone to charge.
Jeklund said:
Thanks for the tip I was wondering if there was a way to mock battery status. Unfortunately running that command to reset it instantly sets it back to -302 temperature. Also that command can't mock the health so its not like I could just leave it mocked to allow the phone to charge.
Click to expand...
Click to collapse
try flashing factory firmware. and see if the problem is still there.
I think there was some problem while flashing twrp truvit again.
bablu048 said:
try flashing factory firmware. and see if the problem is still there.
I think there was some problem while flashing twrp truvit again.
Click to expand...
Click to collapse
I did that yesterday and it unfortunately didn't solve the problem. I may try again today both flashing stock and maybe something like cm to see If i can fix it. My biggest fear at this point is that it's something internal with the hardware. The whole situation just seems really odd as I charged it up, went out for the night with it, then woke up the next morning (yesterday) and it just wouldn't charge.
Jeklund said:
I did that yesterday and it unfortunately didn't solve the problem. I may try again today both flashing stock and maybe something like cm to see If i can fix it. My biggest fear at this point is that it's something internal with the hardware. The whole situation just seems really odd as I charged it up, went out for the night with it, then woke up the next morning (yesterday) and it just wouldn't charge.
Click to expand...
Click to collapse
you had the same issue as these guys - https://productforums.google.com/forum/#!topic/nexus/7IX_6Bv-G_g
some fixed it by changing the battery, flashing older version firmware and use higher capacity chargers
pijes said:
you had the same issue as these guys - https://productforums.google.com/forum/#!topic/nexus/7IX_6Bv-G_g
some fixed it by changing the battery, flashing older version firmware and use higher capacity chargers
Click to expand...
Click to collapse
Thanks for the info, I fear its actually the battery. I'll give downgrading a try later today and see what happens.
It's a shame I really like this phone but in the last 2 days it's completely let me down with this battery issue and my sd card stopped reading for some reason. It's unfortunate that I've rooted the device because no motorola can just blame everything on that even though my phone had been running amazing for the last 3 months.
deleted
Sakshinyk said:
deleted
Click to expand...
Click to collapse
Nope, I'm lucky the battery life in the phone is good as the phone still functions as normal for the most part. The only way I can charge it is in TWRP.
i have the same problem XT1563 :crying:
Moto X Play Not Charging
i am Facing the same issue with my Moto X Play. a little difference is that dont have TWRP. I can only charge in Factory Mode of the phone.
Its very annoying . Morever giving Phone back to moto for repairs takes almost a week or 2 to get your phone back.
I hope one of you guys can get me to the solution.
Thanks
Amit Gupte
([email protected])
Did anyone solve the problem?
Somebody have news? I replace the battery and not charging yet...
Lenovo RIP Motorola
How to solve the problem?
Please
My phone has similar problems. Using Ampere I found out
a) when using car charger after some time of charging it switched every half of a second between charging and not charging
b) charge current is very different without obvious reason, and gets very low (from 2000 via QuickCharge down to 20!)
c) when I mechanically support the micro USB plug (just a finger without pressure) the current changes
d) sometimes the plug does not detect when the socket is empty!
e) sometimes Ampere shows blue "not charging"
f) without charger, the current differs. Usually the phone consumes 200 mA when idle. But sometimes it consumes 900 mAh!
My conclusion is that in my case the socket has problems. The is leakage current, and charging does always not work. I will send it to the vendor for repair/warranty/whatever after I've done a backup and have a working device for the time until repaired.
I hope they find something, as most of the time everything works fine! The vibrations of a car seem to nearly always cause the problem, but at least 95% of the charge processes just do as expected.
Same issue here. Exact same workaround (Recovery or fastboot)
I started a topic in the official forum but it was closed just because of links to custom recovery.
https://forums.lenovo.com/t5/Moto-X-Play/Battery-don-t-charge-anymore-Fastboot-OK/td-p/3196885
Here is the new topic I started:
https://forums.lenovo.com/t5/Moto-X-Play/bd-p/448
PLEASE grab the attention in the official forum.
Hello wazabe
You had put a link in this post "forums.lenovo.com/t5/Moto-X-Play/Battery-don-t-charge-anymore-Fastboot-OK/m-p/3487875"
Do you have the link you deleted? What flash did you use to fix it?
And what tools did you use to make the load? I have an XT1563 that does not load and I'm trying everything.
I was already fighting with AlphaDog in Motorola Forum because he does not want to help me and they are good for nothing.
Thank you!
Jeklund said:
Thanks for the tip I was wondering if there was a way to mock battery status. Unfortunately running that command to reset it instantly sets it back to -302 temperature. Also that command can't mock the health so its not like I could just leave it mocked to allow the phone to charge.
Click to expand...
Click to collapse
and why solve? because i have the same issue
Waza_Be said:
Same issue here. Exact same workaround (Recovery or fastboot)
I started a topic in the official forum but it was closed just because of links to custom recovery.
https://forums.lenovo.com/t5/Moto-X-Play/Battery-don-t-charge-anymore-Fastboot-OK/td-p/3196885
Here is the new topic I started:
https://forums.lenovo.com/t5/Moto-X-Play/bd-p/448
PLEASE grab the attention in the official forum.
Click to expand...
Click to collapse
This is a weird problem.
Have you tried flashing official firmware Maybe it will work.
My phone only charge in factory mode.
Actually i am using aicp 12.1 official.