Hi Everyone here at XDA,
I've been a keen follower of the various ongoings at XDA, ever since my first Android phone the Motorola Defy. I've had quite a few phones since then (currently rocking a yet unmodified Nexus 6P) and I've mucked about with all of them, soft bricked a couple but I've always found a way back from the dead. However, this is something that has me well and truly mystified.
My fiancé bought a OnePlus One a little over a year ago, she had some problems with the microphone during phonecalls (most likely the issue a lot of people had with the noise-cancelling mess-up) so I switched her from stock onto CyanogenMod 13, and no problems since. Phone works a charm.
But recently everything has been going south.
About two months ago the phone started charging STUPIDLY slowly, so I used an energy monitor you plug into the socket to see what was going on. Charger would pull about 2-4 watts, but if you kept plugging and unplugging the phone eventually it would pull about 8 watts, which was adequate. Then things got worse. With the phone turned on, the charger would pull barely 2 watts, turn it off, immediately it would pull 9 watts.
Now it's started to randomly reboot, sometimes getting stuck in a bootloop for 5-10 minutes before booting again. I've spent all day today flashing various ROM's and kernels, and still the issue persists.
We've tried the phone with different chargers to the same result.
Has anybody got any idea what's wrong with the bloomin' thing?
Any advice on what I could try would be massively appreciated.
Cheers in advance
danieljh10 said:
Hi Everyone here at XDA,
I've been a keen follower of the various ongoings at XDA, ever since my first Android phone the Motorola Defy. I've had quite a few phones since then (currently rocking a yet unmodified Nexus 6P) and I've mucked about with all of them, soft bricked a couple but I've always found a way back from the dead. However, this is something that has me well and truly mystified.
My fiancé bought a OnePlus One a little over a year ago, she had some problems with the microphone during phonecalls (most likely the issue a lot of people had with the noise-cancelling mess-up) so I switched her from stock onto CyanogenMod 13, and no problems since. Phone works a charm.
But recently everything has been going south.
About two months ago the phone started charging STUPIDLY slowly, so I used an energy monitor you plug into the socket to see what was going on. Charger would pull about 2-4 watts, but if you kept plugging and unplugging the phone eventually it would pull about 8 watts, which was adequate. Then things got worse. With the phone turned on, the charger would pull barely 2 watts, turn it off, immediately it would pull 9 watts.
Now it's started to randomly reboot, sometimes getting stuck in a bootloop for 5-10 minutes before booting again. I've spent all day today flashing various ROM's and kernels, and still the issue persists.
We've tried the phone with different chargers to the same result.
Has anybody got any idea what's wrong with the bloomin' thing?
Any advice on what I could try would be massively appreciated.
Cheers in advance
Click to expand...
Click to collapse
Different cables as well? The cable seriously does make or break it.
If not that, not sure what it could be... What I can say is, replacing the battery isn't terribly difficult, so if you suspect that at all, it's a fix you can do yourself and for pretty cheap.
Sent from my A0001 using Tapatalk
Elius2676 said:
Different cables as well? The cable seriously does make or break it.
If not that, not sure what it could be... What I can say is, replacing the battery isn't terribly difficult, so if you suspect that at all, it's a fix you can do yourself and for pretty cheap.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Thanks for the advice, but sadly it's not the cable. Or the charger for that matter. The readings I get from the energy meter are too consistent. After plugging and unplugging several times the phone will eventually pull EXACTLY 3.8 watts. No more, no less, irregardless of battery percentage. As soon as the phone is turned off and plugged in, starts pulling anywhere from 7 - 12 watts, which is normal pull I expect.
Hence why I suspected a dodgy kernel, but no luck :'(
Hello
Hello, I had a not that much similar problem a month ago but i'm sharing and it might help (you never know). I was on a custom CM13 based rom and phone started overheating even when not in use, charging slow. When I let it charge overnight I would find it very hot and almost always stuck and 99%. Clean flashed different roms and the same continued to happen and it really got me worried!
Than I thought before ordering a new battery or charger lets try something really stock. I installed lastest OxygenOS and viola problem went away. (be careful and follow the steps you need to flash OxygenOS, it is NOT recommended you flash it via twrp). After that flashed twrp again and custom roms and havent had that problem again.
Hope it helps
Yeah, I would say your most probable culprit at this point might just be the OS. Try a clean flash and/or a different nightly or release. Try also a different Gapps package (you never know if it's not so much the OS, but maybe an interaction between OS and other software.
Sent from my A0001 using Tapatalk
Thanks for the advice, I've finally managed to free up an evening tonight so I'll try putting the phone back to stock. Hopefully it'll work! I'll post back to let you know if I've had any luck.
Put the phone back to stock Oxygen OS, and no luck. Going to use the Tamper Reset Script and try sending it back to Oneplus. Makes me sad that I couldn't sort it myself :crying:
Related
My Fuze recently stopped charging. It also gets warm to the touch now.
I bought a new OEM battery and it solved the problem for about three days, but then same problem.
I read somewhere that the Fuze has some sort of shut-off when the battery doesn't work to prevent overheating (or something like that).
It's still under warranty, but I would rather not have to flash back to stock AT&T ROM, etc.
Any ideas would be welcome.
So that's why you're sending it back! That sucks-I have no idea how to fix it, but since you now have two batteries, you could get one of those cradles that has a re-charging slot for spare batteries. Does it not recharge over usb as well as with a wall-charger? Perhaps the issue is with your charger, and not with the fuze. You might look into different charging methods, if you have them available.
No, FT, not getting an iPhone!
Weird that I woke up this morning and my phone did have a 92% charge (hadn't been getting over 20% in the last 10 days), but it is draining quickly without any use.
I'll try my USB charger, but I don't think that's it.
I can get a new one under warranty, but then I have to flash back, flash, set up again; lot of time involved.
i assume youve tried taking the battery out for over 30 mins, then putting it back in, leaving it shut off and charging for over 3 hours without interuptions or turning it on?
I also assume you are using original charger?
Have you considered that the rom/software you are using is wiping the battery out? Loathed to say it, but have you tried HR or reflash different rom as a last resort?
timmymarsh said:
i assume youve tried taking the battery out for over 30 mins, then putting it back in, leaving it shut off and charging for over 3 hours without interuptions or turning it on?
Click to expand...
Click to collapse
Haven't tried that exactly, but will try it now.
timmymarsh said:
I also assume you are using original charger?
Click to expand...
Click to collapse
Yes, original charger.
timmymarsh said:
Have you considered that the rom/software you are using is wiping the battery out? Loathed to say it, but have you tried HR or reflash different rom as a last resort?
Click to expand...
Click to collapse
Definitely. I removed some recently installed software, but no luck. Yes, a hard reset is scheduled for tonight. If that doesn't work, stock ROM flash and return to AT&T.
I'll try your ideas and let you know what happens.
I have a similar problem, however it still charges. Fuze gets really warm at sporadic times, and i'm starting to think it's because of the charger. I'm in Syria right now and using a converter and i'm starting to think it's because of it; swapping it in as soon as i get back.
kareem9nba said:
I have a similar problem, however it still charges. Fuze gets really warm at sporadic times, and i'm starting to think it's because of the charger. I'm in Syria right now and using a converter and i'm starting to think it's because of it; swapping it in as soon as i get back.
Click to expand...
Click to collapse
I went to India a few years ago, and my wife made me leave all electronic stuff behind because she'd heard of stuff like that. You might want to ease off on the usage while you're over there.
mm it is weird though, as the htc chargers are now designed for multi area usage with just the plug part fitting into the adaptor/transformer.... obviously a cost cutting excerise from htc, so in theroy it should it ok for multi area use. I went to the maldives recently and had no problems with my HD
I had the same problem with my Omnia, but I just had to buy a new battery and never had the Problem again.
Overheating Problem in my Samsung i780
I have this same problem where my unit overheats, really hot to the touch. After switiching similar same spec orig batteries, the problem stays on which only means it is the unit and/or the unit's charging system that is faulty.
Any simple in-house remedy for this?
Planning to upgrade fw, though.
Thanks!
Hi guys,
Had a very weird issue yesterday with my Rogers S4. I have flashed a bunch of ROMS in the past, but wanted to try the new MEA firmware based ROMS..
Well yesterday i tried Mint Jelly v2.1 (flashed via TWRP) and immediately without rebooting flashed 005 FAUX kernal to avoid boot loops. My battery was about 15% at the time. The flash took, and the phone rebooted into the ROM no issues.
Noticed that when i plugged in the charger to my S4 it was NO LONGER charging. I tried multiple 2.1amp chargers, and cables, including OEM, and it no longer charged. However it charged my NOTE2 with no issues.
This is when i was about to FREAK.. but i recall from my HP Touchpad days that sometimes if the battery dies, you need to do something special to get hte phone to charge back up again.
So what i did, was completely shut down the phone, and plug it back in the charger, and it started to charge again. But immediately booting into Android, it would still no longer charge!!.. So i let it charge up for an hour wiht the power off. Once i booted in again, the phone was able to charge again normally with all my chargers while booted in.
I thought my situation was a freak incident until i noticed another XDA member report the same issue. This is NOT a hardware issue, but something related to software.. So give my advice a shot incase you encounter this yourselves!
ED
minirx7 said:
Hi guys,
Had a very weird issue yesterday with my Rogers S4. I have flashed a bunch of ROMS in the past, but wanted to try the new MEA firmware based ROMS..
Well yesterday i tried Mint Jelly v2.1 (flashed via TWRP) and immediately without rebooting flashed 005 FAUX kernal to avoid boot loops. My battery was about 15% at the time. The flash took, and the phone rebooted into the ROM no issues.
Noticed that when i plugged in the charger to my S4 it was NO LONGER charging. I tried multiple 2.1amp chargers, and cables, including OEM, and it no longer charged. However it charged my NOTE2 with no issues.
This is when i was about to FREAK.. but i recall from my HP Touchpad days that sometimes if the battery dies, you need to do something special to get hte phone to charge back up again.
So what i did, was completely shut down the phone, and plug it back in the charger, and it started to charge again. But immediately booting into Android, it would still no longer charge!!.. So i let it charge up for an hour wiht the power off. Once i booted in again, the phone was able to charge again normally with all my chargers while booted in.
I thought my situation was a freak incident until i noticed another XDA member report the same issue. This is NOT a hardware issue, but something related to software.. So give my advice a shot incase you encounter this yourselves!
ED
Click to expand...
Click to collapse
Never flash anything or make major changes to your phone with a low battery (below 70%).
I may be the member he was talking about. I had a thread on this. Only difference was my phone wouldn't charge at all. When I plugged it in when it was off it would boot loop the charge screen. It was rooted and I had some bloat frozen, but the issue started after I installed Sugarsync. I had the same configuration for a few days with no problems, and my battery was about 50 percent when I tried to charge.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Just trying to help. I freaked yesterday because no matter what i did, it wasnt charging. But once i fully powered off, it started chargin!!
scott14719 said:
Never flash anything or make major changes to your phone with a low battery (below 70%).
Click to expand...
Click to collapse
I just flashed a ROM with 56%. I like to live dangerously.
AdePower said:
I just flashed a ROM with 56%. I like to live dangerously.
Click to expand...
Click to collapse
It's definitely possible and usually will work just fine. There are a couple of reasons to flash on a full battery. If something goes wrong and takes a lot longer than originally anticipated, there is less chance of the battery going dead while things are being fixed. Plus, many ROMs (Kernels actually) enact different power profiles for different stages of charge. If this is the case, flashing might not go as anticipated.
scott14719 said:
It's definitely possible and usually will work just fine. There are a couple of reasons to flash on a full battery. If something goes wrong and takes a lot longer than originally anticipated, there is less chance of the battery going dead while things are being fixed. Plus, many ROMs (Kernels actually) enact different power profiles for different stages of charge. If this is the case, flashing might not go as anticipated.
Click to expand...
Click to collapse
I bricked a S2 like that. Flashed a rom adn the battery drained in the process, causing it not flash properly. phone was dead, no download mode or anything.
Let me lay down the story first:
It all started when I tried out multiROM for the LG G3. I was running cm12 perfectly fine, unlocked and everything. Amazing battery life. But MultiROM barely worked, even though I followed the instructions exactly, I had many errors trying to get anything to boot properly. I got help with it, but ended up getting rid of multirom via internal storage (where it was) and flashing a normal, non modified TWRP 2.8.4.0. This is where stuff starts getting weird.
After getting rid of multiROM and flashing cm12 again from backup, I noticed my phone wouldn't take a charge at all. It was booted up and running at about 30% battery. My PC wouldnt do anything when I plugged it into my computer, too. I thought it was just Cyan being weird, so I rebooted into twrp and tried plugging in. No buzz, still wouldn't take a charge. For some reason, turning the phone off and plugging in the charger while it was off actually turned it on. So the charging port has to be working, the phones just being weird... but then I decided to smell the charging port. Smells like pure burning electronics. I rebooted the phone with the cable plugged in, and it boots up and charges. This is odd, because i can no longer plug the cable in while the phone is on, i have to reboot it with the cable in now in order to get it to charge. I tried flashing back to stock ROM, and same exact issue happens. Not only that, but the battery no longer holds a charge for more than a day on one full charge. It lasts about 3-4 hours now.
Please, xdaers, help a brotha out. I'm really pissed about whatever the hell is happening to my G3. It still works fine, I just have to reboot it with the cable in in order to get it to charge at all and the battery life sucks on top of that.
Note: One time after all this happened, the phone died fully. Plugging the charger in, the battery logo was flashing on and off. I tried multiple cables and chargers with the same problem. I pulled out the battery with the cable still in, and the battery logo actually stayed on the screen and once I put the battery back in, it charged again. THIS IS MAJORLY CONFUSING and hard to explain so I will clarify my issue if you are confused with my post.
Also, the phone likes to get really hot and die fast by itself even without the charger plugged in now.
thanks guys
Hi
Thanks for writing to us at XDA assist. Please standby while we have your thread/question moved to the appropriate sub-forum for your device.
For future reference you can find your device sub-forum here (bookmark/subscribe this):
http://forum.xda-developers.com/att-lg-g3
Within that section you will find a dedicated q&a sub-forum (this is where your thread is going to be moved to):
http://forum.xda-developers.com/att-lg-g3/help
Good luck!
So you flashtooled back to stock? And still persists? If so you next option is to buy both a battery and a charging port and do some trouble shooting.
2SHAYNEZ
King Ramen said:
Let me lay down the story first:
It all started when I tried out multiROM for the LG G3. I was running cm12 perfectly fine, unlocked and everything. Amazing battery life. But MultiROM barely worked, even though I followed the instructions exactly, I had many errors trying to get anything to boot properly. I got help with it, but ended up getting rid of multirom via internal storage (where it was) and flashing a normal, non modified TWRP 2.8.4.0. This is where stuff starts getting weird.
After getting rid of multiROM and flashing cm12 again from backup, I noticed my phone wouldn't take a charge at all. It was booted up and running at about 30% battery. My PC wouldnt do anything when I plugged it into my computer, too. I thought it was just Cyan being weird, so I rebooted into twrp and tried plugging in. No buzz, still wouldn't take a charge. For some reason, turning the phone off and plugging in the charger while it was off actually turned it on. So the charging port has to be working, the phones just being weird... but then I decided to smell the charging port. Smells like pure burning electronics. I rebooted the phone with the cable plugged in, and it boots up and charges. This is odd, because i can no longer plug the cable in while the phone is on, i have to reboot it with the cable in now in order to get it to charge. I tried flashing back to stock ROM, and same exact issue happens. Not only that, but the battery no longer holds a charge for more than a day on one full charge. It lasts about 3-4 hours now.
Please, xdaers, help a brotha out. I'm really pissed about whatever the hell is happening to my G3. It still works fine, I just have to reboot it with the cable in in order to get it to charge at all and the battery life sucks on top of that.
Note: One time after all this happened, the phone died fully. Plugging the charger in, the battery logo was flashing on and off. I tried multiple cables and chargers with the same problem. I pulled out the battery with the cable still in, and the battery logo actually stayed on the screen and once I put the battery back in, it charged again. THIS IS MAJORLY CONFUSING and hard to explain so I will clarify my issue if you are confused with my post.
Also, the phone likes to get really hot and die fast by itself even without the charger plugged in now.
thanks guys
Click to expand...
Click to collapse
Don't know about the charging port, but as far as battery life I'm getting the same thing, except mine lasts about 2 hours, I've decided I'm selling the phone while its still worth a bit of money, probably getting a Note 2 or Xperia Z2, I've been very unhappy with this phone, also my battery cover is falling apart and cracking,
SmokeyTech1 said:
Don't know about the charging port, but as far as battery life I'm getting the same thing, except mine lasts about 2 hours, I've decided I'm selling the phone while its still worth a bit of money, probably getting a Note 2 or Xperia Z2, I've been very unhappy with this phone, also my battery cover is falling apart and cracking,
Click to expand...
Click to collapse
Well I've had none of your problems. Note 2 or z2 is a downgrade. Have fun with that... Sucks your experience hasn't been a good one. Cheers
2SHAYNEZ
I get 13+ hours with 4 to 5 hours screen on time and 1to 2 hours of talk time. So I don't think your battery issue is normal for this phone. You have either a defective battery or phone or an app that is misbehaving.
I'm having the exact same problem with LG G3.
Can only charge when rebooted. And even then the charge indicator does not show charging.
I have to go into setting->battery where it shows 'charging'
I have tried new battery and cleaning port.
Anyone figure this out...?
My battery drained very fast before too after backed up to stock, but after I upgraded to 5.0, my phone can lives up to next morning!
Sent from my LG-D850 using XDA Free mobile app
I had been on stock MM for a while and decided to try some custom ROMs again since I am getting close to two years with this phone and stock is starting to feel not so fresh.
Did the procedure with LGflashtool and the LGup dll and was able to get stock ROM, Root, and TWRP installed.
Ran PAC ROM for a bit and seemed like I was getting terrible battery so I tried the newest build of fulmics since it was based on stock.
Battery was terrible on fulmics also, restored PAC.
During all this mess I noticed the phone did not seem like it was charging when I plugged it in. Most of the time I charge my batteries outside if the phone so not really a big deal but with the battery life I get now the one on the charger is not going to be done by the time I need to change it out.
Did notice that it will charge if the phone is off, so I turned it off and plugged it in.
Checked about an hour later and the phone was so hot at the bottom around the usb port it almost burned my hand.
Also noticed during all this that when I put the phone in download mode, it no longer registers as a port on the PC I just used LGflashtool on a week or so ago.
I am thinking the phone is dying, but I am not ready to give up yet.
Also pretty sure that the issues with the port are not related to the ROMS I have been running and it is just a coincidence that this happened when I decided to get back into flashing.
Both of my batteries are almost 2 years old. Had three and threw one away that was swelling a bit. the terrible battery life may be just that. Worth trying a new one?
TL,DR:
Phone does not charge at all when turned on, does charge some when off, but port gets super hot. Also not being recognized by PC anymore.
Any thoughts?
I'm having an issue with a 3 year old Google pixel where the phone is no longer bootable due to it dying anytime it is turned on. Symptoms started about a year ago, the device would occasionally die randomly when opening apps especially with a camera like Snapchat. The issue was originally very infrequent but got more and more common until every app that is opened would kill the device if not plugged in. At this stage anytime the device died it wouldn't use to boot until plugged in. About 4 months ago it started dying even if it is plugged in and now it refuses to boot rom or stay alive in recovery long enough to even decrypt the device. Device is also unstable if plugged into a computer as it constantly reconnects and disconnects. The really odd part about all of this is booting into fastboot works just fine and it will stay in fastboot as long as it's plugged in. I'm thinking I'm gonna have to tear down the device and replace the battery manually but I'm not 100% sure if this is the cause so I'm asking here for confirmation first. Any advice would be greatly appreciated as I need to get data off the device to move to my new pixel3
EDIT: Well, f*** me, after looking through q&a section for 2 minutes I found other people have started having this issue around same time frame as me and it turns out the problem is the motherboard is shot which I was also thinking in the back of my head but didn't want it to be true. I'm so not spending $300 to replace the Mobo of a 3 and a half year old phone, but I do need to get the data off of it. My understanding is that adb DOESNT work over fastboot so I think I'm gonna try to plug it into my laptop and see if I can get twrp alive long enough to get any kind of filesystem access.
Honestly, it sounds like the battery is just dead. The phone dying at X% when using snapchat is like the first sign that the battery is getting weak and can't push out the required power. The way you described it, it just sounds like it got progressively worse until the battery is complete trash. The batteries are like $5-15, so might as well try it if you think you can do it without breaking the screen. I just did it for mine.
uaDPJ said:
Honestly, it sounds like the battery is just dead. The phone dying at X% when using snapchat is like the first sign that the battery is getting weak and can't push out the required power. The way you described it, it just sounds like it got progressively worse until the battery is complete trash. The batteries are like $5-15, so might as well try it if you think you can do it without breaking the screen. I just did it for mine.
Click to expand...
Click to collapse
It's not the battery. Many other sources confirm that this is a motherboard problem. At first it definitely seemed like a battery problem given original symptoms but at this point there is a wide range of random symptoms that point to the board being shot.
On a brighter note I've managed to keep the device alive in twrp long enough to pull data off by plugging into a computer. Wall charger would cause it to die despite charger working fine with several other devices
A bad battery can leak onto the board and fry the board, so you may both be right.