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.
Related
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?
Hey guys,
I noticed this yesterday my Nexus 4 (running PA 3.6, franco milestone 1) shut down at 30% charge. I went home and charged it (it showed 0 when I started charging it) to 100% continuously.
Today too the phone shut down when it was around 32-31% and now charging has again started from 0%.
What could be the issue?
I have tried the battery calibration app even though I know it does nothing.
Any ideas?
japmeet said:
Hey guys,
I noticed this yesterday my Nexus 4 (running PA 3.6, franco milestone 1) shut down at 30% charge. I went home and charged it (it showed 0 when I started charging it) to 100% continuously.
Today too the phone shut down when it was around 32-31% and now charging has again started from 0%.
What could be the issue?
I have tried the battery calibration app even though I know it does nothing.
Any ideas?
Click to expand...
Click to collapse
I have been flashing nightlies merrily on the Nexus4, never had to recalibrate the battery, though it sounds like your does need that. (I had a Desire HD before this, and it was very sensitive to errors in battery calibration)
How about if you charge the phone fully then either reflash the ROM or flash a nandroid backup you've made? Either of those options will overwrite the battery stats file - if that's the problem.
It could be that the chip in the battery is malfunctioning, ie a new battery could be needed, but that sounds much less likely
paul c said:
I have been flashing nightlies merrily on the Nexus4, never had to recalibrate the battery, though it sounds like your does need that. (I had a Desire HD before this, and it was very sensitive to errors in battery calibration)
How about if you charge the phone fully then either reflash the ROM or flash a nandroid backup you've made? Either of those options will overwrite the battery stats file - if that's the problem.
It could be that the chip in the battery is malfunctioning, ie a new battery could be needed, but that sounds much less likely
Click to expand...
Click to collapse
Okay I'll try reflashing the ROM when I'm at a 100%, I know deleting the batterystats.bin file doesn't do anything but I did that anyways yesterday, but it seems it didn't fix the calibration issue.
Any other ideas I could try while I charge my phone to a 100%?
paul c said:
I have been flashing nightlies merrily on the Nexus4, never had to recalibrate the battery, though it sounds like your does need that. (I had a Desire HD before this, and it was very sensitive to errors in battery calibration)
How about if you charge the phone fully then either reflash the ROM or flash a nandroid backup you've made? Either of those options will overwrite the battery stats file - if that's the problem.
It could be that the chip in the battery is malfunctioning, ie a new battery could be needed, but that sounds much less likely
Click to expand...
Click to collapse
Hi, @paul c, I would like to inform you that my phone's discharging just fine (charged it to a 100% last night and it's currently at 48%, I didn't reflash my ROM but I did reboot it once. I also haven't charged it since then)
Could you tell me what's the minimum and maximum battery voltage? I am guessing that the max voltage is around 4200mV but what's the minimum? Also, can we calculate the REAL battery %age from the voltage that is displayed by apps like DashClock? If we can do that could you tell me how/what formula we use to do that?
I know I'm asking a lot of questions and I would really appreciate any help here !
Thanks!
paul c said:
How about if you charge the phone fully then either reflash the ROM or flash a nandroid backup you've made? Either of those options will overwrite the battery stats file - if that's the problem.
It could be that the chip in the battery is malfunctioning, ie a new battery could be needed, but that sounds much less likely
Click to expand...
Click to collapse
Okay the phone died at around 34-36% again, I'm gonna leave it to charge over night, I'm still stuck !
japmeet said:
Okay the phone died at around 34-36% again, I'm gonna leave it to charge over night, I'm still stuck !
Click to expand...
Click to collapse
Worth a try - charge the device to 100%, turn it off, open the back case, disconnect the battery flex cable, reconnect it ... try now.
PsyOr said:
Worth a try - charge the device to 100%, turn it off, open the back case, disconnect the battery flex cable, reconnect it ... try now.
Click to expand...
Click to collapse
Hi, I'm no pro when it comes to opening phones However I'll check out a video on LE55ON5 tomorrow on how to do it. Thanks for the tip.
PsyOr said:
Worth a try - charge the device to 100%, turn it off, open the back case, disconnect the battery flex cable, reconnect it ... try now.
Click to expand...
Click to collapse
I didn't open the phone but i'm taking it to a LG service centre today, no soft methods have worked so far
- please delete -
paul c said:
I have been flashing nightlies merrily on the Nexus4, never had to recalibrate the battery, though it sounds like your does need that. (I had a Desire HD before this, and it was very sensitive to errors in battery calibration)
How about if you charge the phone fully then either reflash the ROM or flash a nandroid backup you've made? Either of those options will overwrite the battery stats file - if that's the problem.
It could be that the chip in the battery is malfunctioning, ie a new battery could be needed, but that sounds much less likely
Click to expand...
Click to collapse
japmeet said:
Hi, @paul c, I would like to inform you that my phone's discharging just fine (charged it to a 100% last night and it's currently at 48%, I didn't reflash my ROM but I did reboot it once. I also haven't charged it since then)
Could you tell me what's the minimum and maximum battery voltage? I am guessing that the max voltage is around 4200mV but what's the minimum? Also, can we calculate the REAL battery %age from the voltage that is displayed by apps like DashClock? If we can do that could you tell me how/what formula we use to do that?
I know I'm asking a lot of questions and I would really appreciate any help here !
Thanks!
Click to expand...
Click to collapse
Hi,
I was inspecting the battery's voltage/charge the entire day today and I realized that at around 36% the voltage went around 3000mV (3100mV, Nexus 4's battery is rated at 3800mV and it maxes at around 4200mV). After that when I plugged it back in and turned it on it started charging from 0%.
I think the battery is at fault.
Is there any fix for this which does not involve replacing the battery?
Thanks!
PsyOr said:
Worth a try - charge the device to 100%, turn it off, open the back case, disconnect the battery flex cable, reconnect it ... try now.
Click to expand...
Click to collapse
Unfortunately this didn't work for me. I tried charging through the night and then discharging it completely and charging it completely again. I also tried deleting the batterystats file (even though I know it doesn't do anything)
So what do you suggest I should do? Get the phone replaced or get the battery changed?
I live in India and the phone is from Canada, so replacing the phone will take some time but I can get the battery replaced for around $20
Also my nexus is also showing +ve mA values while it's not charging, and the values are absolutely crazy, +268, +168, +1171 (in batter monitor widget)
Please tell me what I should do.
japmeet said:
Unfortunately this didn't work for me. I tried charging through the night and then discharging it completely and charging it completely again. I also tried deleting the batterystats file (even though I know it doesn't do anything)
So what do you suggest I should do? Get the phone replaced or get the battery changed?
I live in India and the phone is from Canada, so replacing the phone will take some time but I can get the battery replaced for around $20
Also my nexus is also showing +ve mA values while it's not charging, and the values are absolutely crazy, +268, +168, +1171 (in batter monitor widget)
Please tell me what I should do.
Click to expand...
Click to collapse
So you tried to disconnect the battery cable and reconnect it?
When you open the back case did you notice if the battery looks bigger/inflated? Maybe you should replace the battery.
PsyOr said:
So you tried to disconnect the battery cable and reconnect it?
When you open the back case did you notice if the battery looks bigger/inflated? Maybe you should replace the battery.
Click to expand...
Click to collapse
I didnt open it up, I was unable to separate the back cover from the front. But I've tried everything else.
japmeet said:
I didnt open it up, I was unable to separate the back cover from the front. But I've tried everything else.
Click to expand...
Click to collapse
Might as well replace it while you're at it. It's $20 on eBay OEM.
Sent from my neXus⁴ using Tapatalk 2
PsyOr said:
Click to expand...
Click to collapse
I tried doing as he did, but I wasn't able to open it, and yeah, I'll be replacing it first thing tomorrow. Hope it's not a hardware issue that needs the device to be RMA-ed
1slow4G said:
Might as well replace it while you're at it. It's $20 on eBay OEM.
Sent from my neXus⁴ using Tapatalk 2
Click to expand...
Click to collapse
Okay, I got my battery replaced, drained it to 0% (after a full charge) and going to charge it completely by the travel adapter that I purchased from the service center.
Attached are the pics of my old battery, I don't know if you can see it but it's swollen. If I recall I used a nexus s' charging cable to charge the phone from a computer and it was charging like AC (my kernel usb fast charge was OFF) and it also never detected my phone in the explorer (Windows)
My problem's solved now, it was a battery issue for me. I upgraded to PA 4.3 in the process by the way
So I guess I'll stick to my regular micro USB cable and charge via the travel adapter whenever possible, thank you everyone for your inputs!
1slow4G said:
Might as well replace it while you're at it. It's $20 on eBay OEM.
Sent from my neXus⁴ using Tapatalk 2
Click to expand...
Click to collapse
Link please?
japmeet said:
Okay, I got my battery replaced, drained it to 0% (after a full charge) and going to charge it completely by the travel adapter that I purchased from the service center.
Attached are the pics of my old battery, I don't know if you can see it but it's swollen. If I recall I used a nexus s' charging cable to charge the phone from a computer and it was charging like AC (my kernel usb fast charge was OFF) and it also never detected my phone in the explorer (Windows)
My problem's solved now, it was a battery issue for me. I upgraded to PA 4.3 in the process by the way
So I guess I'll stick to my regular micro USB cable and charge via the travel adapter whenever possible, thank you everyone for your inputs!
Click to expand...
Click to collapse
Yeah at your pics its looks a little bit swollen...
Glad you solved it :good:
PsyOr said:
Link please?
Yeah at your pics its looks a little bit swollen...
Glad you solved it :good:
Click to expand...
Click to collapse
I hope changing the battery fixes it for you too! And here you go : Nexus 4 battery
So, 2 days ago I was charging my device (XT - 1562 Indian Version 16GB) and when I saw the phone after 2 hours the battery was still at 15%... so I got into the battery options to check if the battery was charging and it was showing "Not charging"(SS attached) so I rebooted my phone and it was still showing not charging, I also did a factory reset and still the problem was not solved so I booted into the fastboot mode and there it was showing that the battery is charging. I was confused so I thought that there may be a firmware problem(6.0), so I downloaded factory images of 6.0.1 and flashed them(the BL was locked) and still the problem was there then I unlocked the BL and flashed 5.1.1 and problem still persists. Guys pls help me. :crying:
Also please tell me how can I flash 6.0.1 again via Fastboot mode. I am still at stock 5.1.1
Edit : Update : Now I have installed a custom ROM (CM 13.1 by Temasek) and now the phone is charging like it should but it charges till 82~85% and then stops charging. Cant give the phone to the service center because I unlocked the BL.
thesaurabh7777 said:
So, 2 days ago I was charging my device (XT - 1562 Indian Version 16GB) and when I saw the phone after 2 hours the battery was still at 15%... so I got into the battery options to check if the battery was charging and it was showing "Not charging"(SS attached) so I rebooted my phone and it was still showing not charging, I also did a factory reset and still the problem was not solved so I booted into the fastboot mode and there it was showing that the battery is charging. I was confused so I thought that there may be a firmware problem(6.0), so I downloaded factory images of 6.0.1 and flashed them(the BL was locked) and still the problem was there then I unlocked the BL and flashed 5.1.1 and problem still persists. Guys pls help me. :crying:
Also please tell me how can I flash 6.0.1 again via Fastboot mode. I am still at stock 5.1.1
Click to expand...
Click to collapse
Maybe fault in hardware.
Automated reply by JARVIS
K.khiladi said:
Maybe fault in hardware.
Automated reply by JARVIS
Click to expand...
Click to collapse
Thanks for the reply bro. I have updated the thread so can you tell me what is the problem.
are you using the original charger and cable ?? charge the Device when it's off then turn onforum.xda-developers.com/showthread.php?t=1782420
I'm having this exact same problem on my xt1575. I bought it from a nice dude on Swappa, but he seemed pretty green concerning phones in general. He rooted/unlocked it, then appears that he kept the stock ROM while flashing the franken kernel. I didn't notice this for the first day or two as I opened it and poked around for some signs of something loose/water damage: nothing.
I couldn't sleep last night, so all morning I've been doing what I can to play around with clearing caches, flashing different ROMs, and anything else I can find in the software side, but aside from somehow getting it to get past the previous cap of 4% to a whopping 25% before slamming down to 11% (percentages waver constantly), I'm stuck and desperate to figure it out. I've even tried the stock turbo charger, the stock charger for an old Moto X 2014, and as of writing this just now a Samsung quick charger for the giggles.
I have parts for all kinds of Moto X 2014/Nexus 6 lying around, so I took the risk of connecting a Moto X 2014 battery up to see how it behaved. It read the battery level around mid-seventies and didn't seem to drop at any exaggerated rate but still kind of bounced around a tad. It would charge at times, but otherwise still wouldn't show the battery as being charged. I didn't think too much of it because the 2014 is of course a different model at a much smaller capacity, so I didn't want to try leaving it on the charger for fear of overcharging. The only thing left that I haven't done is hook up the Play battery to another motorola because I don't have any screens to monitor progress and see how consistently it reads to determine if it's the battery that's somehow gone wonky.
So in summation/where I'm at right now: I'm having this same problem; I've tried both hardware and software tinkering to no avail; I feel this is still somehow kernel/software related, but I'm not sure how to completely obliterate everything to start from stock. Please forgive how scatterbrained I am right now, I'm tired yet wide awake and irritated with the whole situation; there's NOTHING I can find in the forums or elsewhere outside of stock replies like "are you using the original charger?"
My moto x play not change in normal it only charge in factory mode that to 75-82℅ only.
Let it discharge fully then put on charge without booting up
PSxplay said:
Let it discharge fully then put on charge without booting up
Click to expand...
Click to collapse
I have did that still it's not charging, it's showing power symbol without percentage showing.
Shajj99 said:
I have did that still it's not charging, it's showing power symbol without percentage showing.
Click to expand...
Click to collapse
I have tried after battery fully drain, still it's not charging again I am charging mobile in factory mode. Is there any solution please help me. In factory mode i am not getting signal.
So no change in behavior. I did notice that when in TWRP that the CPU Temp value is crazy, and any reporting software says the battery is at -23.8° C and always cold, even on a brand new replacement battery (obviously send like that is what's keeping it from charging). I even went as far as to put a heat gun on it from a distance to artificially actuate any sensors and got nothing. The one time it did report normal temps it charged fine for a whole day but hasn't returned to normal since. This **** is maddening...
I know this is a long shot, but have you tried resetting the battery stats?
http://forum.xda-developers.com/showthread.php?t=1699687
I had this problem but yesterday I can solve that
First I put stock firmware
Wait for fully discharge
And wait full shutdown
I put an moto g 2013 charger (550mA 5V)and led stay on around 5 min but not charge
After put Nokia n86 charger (1A 3.5V)5 min and not charge
After i put an orginal moto turbo charger
And start to charge wait for 9%
Turn on the phone
Clear battery stats with battery calibration app
Wait for full discharge
Wait for full turn off
I put a Nokia n86 charger wait 5 minutes vibrates and start to charge like the beginning
Any other suggestions or solutions? Still my phone only charges in recovery mode. I have a aukey fast charger. Tried different kernels and roms without success.
The solution with the nokia chargers seems really strange and i dont have that type of charger.
Regards
Someone fixed this? I have the same problem and can't solve it. I have cm 13 by temasek and the first time the x play charged up to 83% but after a full discharge and a clean of battery stats, I olny could charge it via factory mode, like in stock 6.0.1
I dont know why but after i opened the phone and disassembled the battery it worked after putting it back together. Disconnected the cable to mainboard as well as nfc antenna. Then carefully pried the battery out. Its slightly glued to the mb. Then I held power button down for a few sec as read in a different forum. Afterwards I connected power cable back but left the battery next to the phone. Booted the phone and charging worked. Than I reassembled the phone Ehen I was sure everything worked. I was about to change the battery but now it works. I flashed different Roms and kernels without any improvment before. After I got it working I flashed a nandroid backup of a resurection Rom image that didnt worked before. Now its running perfect.
pulpokraken said:
I dont know why but after i opened the phone and disassembled the battery it worked after putting it back together. Disconnected the cable to mainboard as well as nfc antenna. Then carefully pried the battery out. Its slightly glued to the mb. Then I held power button down for a few sec as read in a different forum. Afterwards I connected power cable back but left the battery next to the phone. Booted the phone and charging worked. Than I reassembled the phone Ehen I was sure everything worked. I was about to change the battery but now it works. I flashed different Roms and kernels without any improvment before. After I got it working I flashed a nandroid backup of a resurection Rom image that didnt worked before. Now its running perfect.
Click to expand...
Click to collapse
So, may the problem be in the pins when the battery is plugged into the mb? I'll try that! thanks!
Still having this issue, the solution with the chargers didn't work for me, neither the battery solution, suggestions?
How to solve the problem?
Please
Same issue
My Moto X Play has the same issue. It will only charge in Factory Mode. I had this issue before at 10-11 months old and had it 'fixed' under warranty, now 2-3 months later the same issue has occurred. Of course the warranty is only 1 year...
Glad I am not alone in this issue but i wish there was an easy fix! Putting me off getting another Moto...
Same problem occurred with me( Moto X Play).
My phone was not charging, it was stuck in some percentage and was not increasing or neither decreasing while plugged in to charger. But when i put it into recovery mode, it charges. But that was not the solution to the problem.
So, i have tried factory reset.
but problem was not solved.
i googled for the solution, but couldn't find the right solution. And i was stressed (I have a girlfriend, and living in very distance relationship, for me a smartphone is very important).
And was thinking of buying a new phone but not the Motorola, but couldn't afford at the time.
At the same time, i thought of repairing it by myself, by fixing the battery properly.
Without thinking about voiding the warranty and Motorola support, i unbolt every screw of the phone. and finally , finally, finally i made it by removing the battery and fixing it again(charger was plugged while removing the battery and fixing, and phone switched off while removing).
And now my phone is charging properly.
Hope I have helped every person concern to this same problem.
Thank you
My phone's battery level is stuck at 35% and doesn't change on charging it over and over again. Left the phone charging last night and it was still charging at 35% in the morning. However if there's a drop below 35% level it shows on the screen but again charging the phone drains complete battery within a minute or two. The phone gets switched off and starts charging from 0. On switching it on sometimes it again starts draining the battery fast or stuck at some another battery level. Please help what should i do.
I tried reflashing rr rom freshly but it didn't solve the issue. Twrp recovery shows the same battery %.
Screen recorded as below.
https://youtu.be/ubYYBRl2HVU
Charger or phone faulty, either requires exchange under warranty, take it you are using cable and charger supplied with phone.
Do a factory reset just in case something has screwed up the OS, trying to charge with the phone switched off usually will confirm whether hardware or software problem, ie will not charge when off says its hardware.
Smeagal192 said:
Charger or phone faulty, either requires exchange under warranty, take it you are using cable and charger supplied with phone.
Do a factory reset just in case something has screwed up the OS, trying to charge with the phone switched off usually will confirm whether hardware or software problem, ie will not charge when off says its hardware.
Click to expand...
Click to collapse
I left the phone on charge last night in switch off mode but the battery level shows only 10% in the morning. Internally however it's charged 100% but the level is not showing correctly. Also since I've unlocked the bootloader, the device isn't under warranty.
what a weird battery behaviour!!
Whenever I start charging my phone using stock charger, it drains the battery within minutes instead of charging. Once the battery is completely drained out the battery starts charging from 0% and after a full night of being plugged into the charger it shows partially charged at different level when it's switched on even though it's full.
Is there no way to troubleshoot this or the right way to calibrate the battery?
22sumit said:
what a weird battery behaviour!!
Whenever I start charging my phone using stock charger, it drains the battery within minutes instead of charging. Once the battery is completely drained out the battery starts charging from 0% and after a full night of being plugged into the charger it shows partially charged at different level when it's switched on even though it's full.
Is there no way to troubleshoot this or the right way to calibrate the battery?
Click to expand...
Click to collapse
Follow this guide also valid all Moto devices out there.
https://motorola-global-en-uk.custh...a/moto-g4-g4-plus/topic/battery/battery-reset
PSP07 said:
Follow this guide also valid all Moto devices out there.
https://motorola-global-en-uk.custh...a/moto-g4-g4-plus/topic/battery/battery-reset
Click to expand...
Click to collapse
already tried this in vain. The battery % doesn't change while discharging and decreases very fast while charging.
22sumit said:
already tried this in vain. The battery % doesn't change while discharging and decreases very fast while charging.
Click to expand...
Click to collapse
Contact Moto Service Center hope they will sort out.... Best of luck
Although I think it's a coin toss if it will help, try another charger and a factory reset... Moto service will want you to do a factory reset before sending it in anyway.
PSP07 said:
Follow this guide also valid all Moto devices out there.
https://motorola-global-en-uk.custh...a/moto-g4-g4-plus/topic/battery/battery-reset
Click to expand...
Click to collapse
Thank you, I'll try this one.
PSP07 said:
Follow this guide also valid all Moto devices out there.
https://motorola-global-en-uk.custh...a/moto-g4-g4-plus/topic/battery/battery-reset
Click to expand...
Click to collapse
Tried, it didn't worked.
22sumit said:
My phone's battery level is stuck at 35% and doesn't change on charging it over and over again.
Click to expand...
Click to collapse
Almost the same with different battery percentage.
My G5 plus is under amazon warranty so I'm fine but I would like to know if there is a way to solve by myself and would like to know what the hell happend.
Have you solved this battery issue?
Thank you.
MezzaLuna said:
Tried, it didn't worked.
Almost the same with different battery percentage.
My G5 plus is under amazon warranty so I'm fine but I would like to know if there is a way to solve by myself and would like to know what the hell happend.
Have you solved this battery issue?
Thank you.
Click to expand...
Click to collapse
Not yet, only solution is getting the battery replaced. Now I've learnt to live with it, since the mobile needs to be restarted after every charge and the % gets stuck at some random value despite being fully charged.
22sumit said:
Not yet, only solution is getting the battery replaced. Now I've learnt to live with it, since the mobile needs to be restarted after every charge and the % gets stuck at some random value despite being fully charged.
Click to expand...
Click to collapse
I'll ask for replacement after Christmas holidays. Thank you very much.
I do also have the same problem. It just started a few days ago and sometimes I'd restart the phone and it will fix it and show the actual percentage been charged. But now that isn't fixing it anymore. However, as mentioned before the battery is actually being charged. So let's say it's stuck in 11% and I charge it for a few hours. Then I can use the phone for hours without going below 11%.. but how annoying when it gets there and all of a sudden you are running out of battery ?
Charging with original charger/cable. Do you guys think it might have to do with the turbopower feature?
Has anyone found a solution to this? I'm still under warranty for two more months. But it's always a pain to deal with warranty, you know no phone for a week or more... It would be nice if it can be fixed without going through warranty.
I've been having power drain issues for a couple of months now, have tried almost everything but issue isn't resolved. Will replacing the motherboard solve the issue? Coz I suspect a wakelock issue. Below are what I've tried.
The battery has started to drain big time and the Android system is consuming most of the power.
1. Calibrating my battery.
2. Factory reset to January update.
3. Stopping the apps running in the background.
4. Turning off location, wifi and internet.
5. Tried disabling backup of photos.
6. Disabled app preview messages under Google.
7. Tried replacing the physical battery at the service center.
8. Currently running on the June 2018 patch.
Despite doing all this the battery drains big time, even when it's idle, when I'm sleeping.
I'm unable to upload screenshot because it keeps saying that there's a network issue. But the screenshot stats say that the android os consumes most of the battery and SoT was 30 minutes. Phone was idle for most of the time. It came down 100-20% in a few hours.
Android OS is eating away most of the battery.
AkCullen said:
I've been having power drain issues for a couple of months now, have tried almost everything but issue isn't resolved. Will replacing the motherboard solve the issue? Coz I suspect a wakelock issue. Below are what I've tried.
The battery has started to drain big time and the Android system is consuming most of the power.
1. Calibrating my battery.
2. Factory reset to January update.
3. Stopping the apps running in the background.
4. Turning off location, wifi and internet.
5. Tried disabling backup of photos.
6. Disabled app preview messages under Google.
7. Tried replacing the physical battery at the service center.
8. Currently running on the June 2018 patch.
Despite doing all this the battery drains big time, even when it's idle, when I'm sleeping.
I'm unable to upload screenshot because it keeps saying that there's a network issue. But the screenshot stats say that the android os consumes most of the battery and SoT was 30 minutes. Phone was idle for most of the time. It came down 100-20% in a few hours.
Android OS is eating away most of the battery.
Click to expand...
Click to collapse
No, motherboard replacement won't fix the issue. It looks like there's an issue with deep sleep. try a custom kernel and see if that helps
While my drain is not as bad as the OPs, it is bad. I have taken to turning on Airplane mode when the phone is not in use. Overnight drain is 20%+ when idle if not in Airplane mode, 1% if it is. SoT has gone from the original 6-7 hours to about 2.5 to 3 hours. Battery health is at 96% according to battery app. Held awake seems to be very high if not in Airplane mode, with almost 3 hours overnight when the phone is not in use. Main battery use is from Kernel and Phone. HOPEFULLY these issues will be resolved with 8.1 or P, but I won't hold my breath.
Unfortunately none of these issues were addressed in 8.1 and I'm not sure if they even recognized this issue, for it to be solved in future updates.
AkCullen said:
Unfortunately none of these issues were addressed in 8.1 and I'm not sure if they even recognized this issue, for it to be solved in future updates.
Click to expand...
Click to collapse
You're probably the only one or one of the very few with bad battery drain (80% in just a few hours while idle) on the stock rom so you probably got a lemon or its damaged from a fall.
Flashing the Jan 2018 rom wasn't smart at all since there was alot of news that the first Oreo update was very buggy and was pulled. 8.1 is also buggy and also got pulled. Best to flash the stock April rom for less problems.
barrack1 said:
You're probably the only one or one of the very few with bad battery drain (80% in just a few hours while idle) on the stock rom so you probably got a lemon or its damaged from a fall.
Flashing the Jan 2018 rom wasn't smart at all since there was alot of news that the first Oreo update was very buggy and was pulled. 8.1 is also buggy and also got pulled. Best to flash the stock April rom for less problems.
Click to expand...
Click to collapse
Thank you for your response. The phone does not have any physical damage. Flashing the Jan 2018 rom was a move by the service center despite telling them it wouldn't help.
I managed to figure out using GSAM that the issue is being caused by 700000.ssusb kernel wakelock and I have no clue how to fix it. Do you have a workaround for it?
As this option is USB related, you could try changing the usb mode in developer options:
Settings>System>Developer options>Select USB configuration - change it to "charging" (I note mine is currently MTP)
I'm 100% guessing here but maybe if it's set to charging it won't be looking for OTG devices?
kudos1uk said:
As this option is USB related, you could try changing the usb mode in developer options:
Settings>System>Developer options>Select USB configuration - change it to "charging" (I note mine is currently MTP)
I'm 100% guessing here but maybe if it's set to charging it won't be looking for OTG devices?
Click to expand...
Click to collapse
I've tried setting it to all possible modes under USB configuration including "charging", but doesn't seem to help.
OK, it was only a thought.
I did read on another thread someone say they plugged and OTG adaptor (no OTG device attached) and it stopped the problem, not a solution but worth a try, if you have one.
Have you inspected carefully with a torch inside the USB hole for any debsit that has got in there?
kudos1uk said:
OK, it was only a thought.
I did read on another thread someone say they plugged and OTG adaptor (no OTG device attached) and it stopped the problem, not a solution but worth a try, if you have one.
Have you inspected carefully with a torch inside the USB hole for any debsit that has got in there?
Click to expand...
Click to collapse
Yes I read about that work around too. Haven't tried it yet as I do not have an OTG adapter. Will post a response once I try.
Haven't inspected the USB port either, will do.
AkCullen said:
Yes I read about that work around too. Haven't tried it yet as I do not have an OTG adapter. Will post a response once I try.
Haven't inspected the USB port either, will do.
Click to expand...
Click to collapse
Can you try this:
Reboot phone, when its rebooted, plug the charger in and out once.
kudos1uk said:
Can you try this:
Reboot phone, when its rebooted, plug the charger in and out once.
Click to expand...
Click to collapse
Will do and update the thread.
AkCullen said:
Will do and update the thread.
Click to expand...
Click to collapse
Most of the threads have a reboot method that works for the user but they all vary a little bit, this works for this user:
In my case a kernel wakelock called "7000000.ssusb" was keeping my phone from entering deep sleep. I resolved it by plugging my charger, unplug it and turn it off immediately, wait a few minutes and reboot. However it is a specific solution for that bug.
Click to expand...
Click to collapse
I think you might need to play around a bit and see what works for you.
Don't forget to do the Better Battery Stats dump I posted in the other thread.
kudos1uk said:
Most of the threads have a reboot method that works for the user but they all vary a little bit, this works for this user:
I think you might need to play around a bit and see what works for you.
Don't forget to do the Better Battery Stats dump I posted in the other thread.
Click to expand...
Click to collapse
I've already tried the plug in - screen on - unplug - reboot, but did not work for me. I'll post the dump over the weekend.
kudos1uk said:
As this option is USB related, you could try changing the usb mode in developer options:
Settings>System>Developer options>Select USB configuration - change it to "charging" (I note mine is currently MTP)
I'm 100% guessing here but maybe if it's set to charging it won't be looking for OTG devices?
Click to expand...
Click to collapse
I'm just noticing this today,
When I click on the USB configuration and set it to "Charging" from "MTP", it doesn't actually change.
The pop up that shows different options shows that it's in charging but it's actually still in MTP. I'm not sure if this could be the cause.
Do you know how to fix this?
AkCullen said:
I've already tried the plug in - screen on - unplug - reboot, but did not work for me. I'll post the dump over the weekend.
Click to expand...
Click to collapse
Screenshots for USB configuration not getting switched.
AkCullen said:
Screenshots for USB configuration not getting switched.
Click to expand...
Click to collapse
You need to back out of developer options and go back in again to see the change.
Plug the charger in
Change mode to charging
Back out of developer options
Re enter developer option - should no be on charging.
Plugging in, changing the selection, backing out and going back in does not show changes: Change setting to Charging->back->back. Developer options-> Select USB Configuration shows Media Transfer Protocol, while the Selection itself shows charging. (it's plugged in, so makes sense) I tried changing this to Music Transfer Protocol last night and it made zero difference in the battery drain. I just tried the plug in, turn off, unplug thing. I will let you know if I see any difference. USB port is clean under 5x magnification. NETLINK and timerfd shows more activity than 7000000.ssusb on my device, but all of them are higher than they should be I think.. NETLINK shows 324644 wakelocks!!! Timerfd shows 65337 and 7000000.ssub shows 33256! The thing is, the phone has been used very little since the last full charge!
That's odd, I dont have the issue and when I choose "charging" it stays on that setting even after unplugging the charger. Each time I re-enter developer options it's still set to charging.
The fact yours changed links in with the wakelock, your phone appears to think something is plugged in which is why I asked you to check for debris in the port. I'm wondering if you have a damaged usb port?
If it's software related, I don't think resetting it will help, I'm no expert but I'm assuming as its a kernel wakelock & I'm sure a reset has no effect on the kernel? maybe others can advise.
I wonder if flashing the stock Kernel would help, I'm only thinking out loud, I'm sure others can give better flashing advice.
Do the wakelocks show up while charging?
Your next step really has to be to post a dump on the official thread, a few people are complaining about this battery drain but nobody has posted a dump to the official thread yet.
KB_Thailand said:
Plugging in, changing the selection, backing out and going back in does not show changes: Change setting to Charging->back->back. Developer options-> Select USB Configuration shows Media Transfer Protocol, while the Selection itself shows charging. (it's plugged in, so makes sense) I tried changing this to Music Transfer Protocol last night and it made zero difference in the battery drain. I just tried the plug in, turn off, unplug thing. I will let you know if I see any difference. USB port is clean under 5x magnification. NETLINK and timerfd shows more activity than 7000000.ssusb on my device, but all of them are higher than they should be I think.. NETLINK shows 324644 wakelocks!!! Timerfd shows 65337 and 7000000.ssub shows 33256! The thing is, the phone has been used very little since the last full charge!
Click to expand...
Click to collapse
Yes that's exactly what's happening as described in first point.
I observed NETLINK sends more wakelocks but if you see the time it kept the system awake in the background would be comparitively less.