Related
Title pretty much says it all. Also, could you state what you sent it in for? I currently am having issues with it thinking it's charging when it's actually not, and am considering calling LG to send it in for repairs.
what do you mean by charging when its actually not? is it charging USB when its plugged into the wall?
plug it in the wall and then check about phone -> status.... does it say charging (USB) instead of charging (AC)?
nah, when it's unplugged the phone thinks it's charging. battery icon has the lightning symbol, lockscreen says charging
sounds like a software problem. flash a custom rom and kernel (optional)
not worth RMAing it just for that. if it still does it, then flash it back to stock and u may RMA if all else fails.
My phone is facing RED LED problem, should i send it for warranty ? whats the procedure ? Its over 15 days since purchase !
miku3191 said:
My phone is facing RED LED problem, should i send it for warranty ? whats the procedure ? Its over 15 days since purchase !
Click to expand...
Click to collapse
I read that you have one year of waranty.
My N4 have the same problem, but I dont know if Google accept it with the bootloader unlocked however I think my phone is fried, so, how can they know if phone even turn on..>>?
i sent mine in, dropped it and got a crack in the screen and the touch stopped working. Hopefully I'll have it repaired soon. Not covered under warranty because it was physical damage.
I just want you guys to help me diagnose the problem.
I was charging my phone yesterday with a cheap car charger.
My phone now produces lots of heat, eats lots of current (discharges quickly) and USB is not working (only charging).
I tried flashing different radios, kernels, stock rom and factory reset - didn't help.
Plugging a phone into Ubuntu PC doesn't add any logs about new USB device in dmesg, even in fastboot mode.
My questions:
1. What can cause SoC to produce heat and to discarge battery very quickly?
2. Is it a failure of a USB board or of the SoC itself?
I have two options on eBay: logic board and usb board.
It would be great to buy a 16GB motherboard instead of my current 8GB, but I want to address the problem with less money spent on it.
I don't know which one to buy.
same problem
Unforunetly I don't have a solution for you, I have been experiencing the same problem since last week. My phone no longer charges in AC mode, I can't connect it to any PC (fastboot doesn't work), and the battery is draining fast (from Phone Idle process). It is warm when the screen is off. I am on Android 4.3, it was working fine up until last week.
I'm about ready to RMA it, however it's interesting that I am not the only one experiencing this problem lately.
jasonsch said:
Unforunetly I don't have a solution for you, I have been experiencing the same problem since last week. My phone no longer charges in AC mode, I can't connect it to any PC (fastboot doesn't work), and the battery is draining fast (from Phone Idle process). It is warm when the screen is off. I am on Android 4.3, it was working fine up until last week.
I'm about ready to RMA it, however it's interesting that I am not the only one experiencing this problem lately.
Click to expand...
Click to collapse
What did you do with your phone before it started behaving this way?
reqmon said:
What did you do with your phone before it started behaving this way?
Click to expand...
Click to collapse
I'm not sure what caused it, I have a feeling it's similar to what happened to yours. I use a blackberry car charger in my car, and at work I use a non LG AC charger. So I'm thinking it was the car charger, but the weird thing is it has been working fine with both chargers for 6+ months.
jasonsch said:
I'm not sure what caused it, I have a feeling it's similar to what happened to yours. I use a blackberry car charger in my car, and at work I use a non LG AC charger. So I'm thinking it was the car charger, but the weird thing is it has been working fine with both chargers for 6+ months.
Click to expand...
Click to collapse
Another thing is that I was installing a faux kernel 3 days ago, but it didn't cause these symptoms instantaneously (instead, it made my nexus super power-efficient), so I don't think that was the cause, too.
P.S. Google's RMA policy doesn't allow to return phones after 15 days, so I think the best choice would be to buy a broken phone and interchange the parts.
reqmon said:
Another thing is that I was installing a faux kernel 3 days ago, but it didn't cause these symptoms instantaneously (instead, it made my nexus super power-efficient), so I don't think that was the cause, too.
P.S. Google's RMA policy doesn't allow to return phones after 15 days, so I think the best choice would be to buy a broken phone and interchange the parts.
Click to expand...
Click to collapse
I haven't used any custom kernels or ROMs. I am rooted with custom recovery though.
There is a 1 year warranty on the phone, and I am within that 1 year so I hope to be able to get a replacement. This appears to be a hardware problem.
edit: Have you tried taking the battery out? In previous phones when stuff like this would happen I was able to pull the battery out. I tried to open my phone but it's a pain to pry open without breaking something.
jasonsch said:
I haven't used any custom kernels or ROMs. I am rooted with custom recovery though.
There is a 1 year warranty on the phone, and I am within that 1 year so I hope to be able to get a replacement. This appears to be a hardware problem.
edit: Have you tried taking the battery out? In previous phones when stuff like this would happen I was able to pull the battery out. I tried to open my phone but it's a pain to pry open without breaking something.
Click to expand...
Click to collapse
No, but I will do this tomorrow. I don't know if this helps.
P.S. Sometimes I get this in dmesg:
Code:
[738145.499853] hub 2-1:1.0: unable to enumerate USB device on port 8
...which is not good either.
Well, I tried removing the battery - that didn't help.
What actually helped, is the following:
1. Bought cheap broken nexus.
2. Exchanged motherboard and usb board with my existing device.
3. Sold broken nexus for cheaper price.
4. ...Profit!
Now my nexus works again, and more than that, it has 16gb instead of 8gb. It wasn't hard.
I'm happy now.
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.
Hi there guys
Device : Land
Actually from 1 week facing a weird issue with my device.
1 week ago my battery was down to 0% and then the device got switched OFF(probably dead).
So i got it jump start from a local shop. After that my device only take charge when i restart the device and put the charger when while the device is starting. And again if I plug out and plug in the charger it won't take a charge.
The device doesn't charge even in recovery mode. Everytime to charge the device i have to restart.
Please help me and suggest some solution for this.
Note : when the device faced this issue i was on DOT OS with stock kernel
I'm using the fk smart buy charger that i bought 1 week back
Same problem
M having the same issue i tried oreo roms nougat roms... Didnt tried stock yet . when i switch off my phone charges otherwise not... Usb also not reading... Did you got any solution please tell...
Flash stock miui rom and check
If not working go to service center
s123raza said:
Hi there guys
Device : Land
Actually from 1 week facing a weird issue with my device.
1 week ago my battery was down to 0% and then the device got switched OFF(probably dead).
So i got it jump start from a local shop. After that my device only take charge when i restart the device and put the charger when while the device is starting. And again if I plug out and plug in the charger it won't take a charge.
The device doesn't charge even in recovery mode. Everytime to charge the device i have to restart.
Please help me and suggest some solution for this.
Note : when the device faced this issue i was on DOT OS with stock kernel
I'm using the fk smart buy charger that i bought 1 week back
Click to expand...
Click to collapse
I was facing the same issue and tried lots of things to correct that but what actually worked was flashing a stable or beta miui official rom only.. now it works all as new and battry performance is also improved.
Last night I've put my Mi 9t to charge and went to sleep. When I woke up, the phone was turned off.
I've tried to restart it and also pressed the volume + power button combinations to force the recovery mode - unsuccessfully.
No blinking lights, no MIUI entry, no vibration, zero response from the phone. (Is it bricked?)
I've started to research and since my computer can't find the Mi 9t (running Windows 10) the only solution seems that to disassemble it and do the EDL Mode Test Point, to acess the recovery mode and try to flash the phone.
Do you have other sugestions to try?
Martholas said:
Last night I've put my Mi 9t to charge and went to sleep. When I woke up, the phone was turned off.
I've tried to restart it and also pressed the volume + power button combinations to force the recovery mode - unsuccessfully.
No blinking lights, no MIUI entry, no vibration, zero response from the phone. (Is it bricked?)
I've started to research and since my computer can't find the Mi 9t (running Windows 10) the only solution seems that to disassemble it and do the EDL Mode Test Point, to acess the recovery mode and try to flash the phone.
Do you have other sugestions to try?
Click to expand...
Click to collapse
This is weird. Maybe it's not charged? Did you try another charger and/or cable? How can the phone get bricked overnight by doing nothing? Never heard of it.
edittt
attitude12 said:
This is weird. Maybe it's not charged? Did you try another charger and/or cable? How can the phone get bricked overnight by doing nothing? Never heard of it.
Click to expand...
Click to collapse
I've tried today during all day with a different charger, no response.
It's the first time a thing like this happened to me as well. I've never flashed it before or did any major modifications. I was running MIUI 11 still.
If the battery runned out how can I revive it?
On another forum a user told me it could be the integrated circuit broken or a battery problem.
Martholas said:
I've tried today during all day with a different charger, no response.
It's the first time a thing like this happened to me as well. I've never flashed it before or did any major modifications. I was running MIUI 11 still.
If the battery runned out how can I revive it?
On another forum a user told me it could be the integrated circuit broken or a battery problem.
Click to expand...
Click to collapse
Then I really don't know. Like I've said, never encountered this before. You could try going to a repair service.
you could open backcover and charge battery directly to see if thats usb problem
You can make an EDL cable. is very easy to do and you have a lot of videos and pictures about it.
Dont worry if you have to open the phone is really really easy. With a hot air gun or a hair dryer you can do it in 2 minutes. You are going to need also a piece of radiography to separate the cover
Then the test point is really easy to do it, check some pictures in google, also you can check the usb port if it is damaged or not once the phone is opened, but of course if the phone stoped working from day to night is weird a usb faulty port
Pls don't open anything or try an trick. Just take it to a repair service so u don't make things worse
I've tried the test point and didn't work, as well
So I took it to a repair shop that accepts xiaomi. They are going to order a new battery and a battery connector (2-3 Weeks).
I'll post when I'll get more updates.
I had a lg g3 that did the same thing. Charged it over night and it didn't work the next morning, could be power surge. Ever since then I never charge my phone over night
So, I've picked it from the repair shop and they couldn't fix it. They changed the battery, the battery connector and the display. They said they don't have a solution for the phone.
My next step is to contact gearbest to see if they have a solution for me.
Martholas said:
So, I've picked it from the repair shop and they couldn't fix it. They changed the battery, the battery connector and the display. They said they don't have a solution for the phone.
My next step is to contact gearbest to see if they have a solution for me.
Click to expand...
Click to collapse
It must be the mother board then, Same with my old lg g3.