I have a Samsung Galaxy A5 that has some battery oddities, I suspect it's a hardware issue but would like a second (or maybe third, fourth, and fifth) opinion about it. The model number is:
SM-A5000
Samsung Galaxy A5 (2015), China/Hong Kong region variant
It used to be my dad's, and he's used it for a couple of years so the lithium cell may have aged. Initially he charged it to >80%, then powered it off and took it on a 12-hour flight. By the time he landed and tried to power it on, the battery was dead. Initially it was running stock 4.4.4 KitKat (Chinese ROM), I first tried to charge it through a PC USB port, and it charged very slowly as expected. The battery level would reach about 30-something and fluctuate. The charging port seems fine, no loose connections or anything.
I next used Samsung Smart Switch to update it to stock 6.0.1 (still mainland Chinese ROM), then connected it to a 2A wall adaptor. The battery would charge up to 82%, then fail to go any further. I noticed that the battery level would often decrease while on the charger, both when idle and locked, or even when powered off and charging.
After flashing TWRP, I did a factory reset and wiped the cache but it didn't seem to do anything for the battery. At one point, the percentage jumped from 82% to 100%, but after a few minutes idle at the home screen, it immediately dropped back from 100% to 80-something%.
At the same time, I was trying to figure out how to install the Google Play Services framework since it's not included in the mainland Chinese ROMs (Open Gapps wouldn't work) and eventually I decided to flash the stock Hong Kong version of 5.0.2, which had all the Google apps. This seemed to somewhat alleviate the battery drops a little, but it still won't charge past 82%. At this point, I replaced TWRP with Carliv Touch Recovery (since it seems to work better) and used it to clear the battery stats. This made CTR detect the battery as 100%, but the OS still won't go past 82%.
I then rooted it and killed off any bloatware and prevented a bunch of stuff from backgrounding or wakelocking, but the battery still seems to drop 1% every 2 minutes or so while idle (and connected to a 2A charger). The battery may also occasionally drop even when powered off and connected to the same charger.
So, does this sound like a dying battery, or could it be a problem with the ROM? I've flashed custom ROMs to it before but that didn't seem to do anything for the battery. The next step would be to fully drain and recharge a few times, but since it's an old device I'm not expecting any miracles. The battery is also non-removable so it won't be easy to replace. My dad's got a new phone already and has pretty much given me this one to experiment with, I don't plan on using it as a daily driver so it's not much of an issue if it's an unrecoverable hardware failure. Just wanted your opinions.
Thanks
tl;dr version:
- Galaxy A5 (2015) SM-A5000
- rooted 5.0.2
- Battery won't go past 82%
- Percentage drops while on charge, even when powered off
Related
Im using Cyanogen Mod 10.1 build Jan 23 on my phone. Till recently (2 days specifically) my battery has started acting up. When i connect it to the wall charger it charges super slow. Also if I'm browsing or using the phone for an email or anything during charge the charge on the battery still drops. I also charged the phone using a blackberry charger same issue happens. The battery takes 6-8 hours to charge completely.
This also happened to me the first time i charged my phone when i got it. But it fixed itself after that.
It behaves the same when i switch off the phone and charge it.
Plz Help.
Samsung Galaxy S3 [I9300]
CyanogenMod 10.1
Sounds like a bad battery imo. You didn't turn down the charging rate in a custom kernel by anychance?
CM10 nightlies are still under DEV so you can expect a battery drain until stable versions comes out !!
Im using Stock Kernel on the device. No changes made to it or battery charge rate. Should I buy a new battery? Or can it be a hardware issue?
Like being said before CM10.1 is still in dev.
Try flashing back to stock and test.
Welcome to the baffled S3 charging issues thread....
http://forum.xda-developers.com/showthread.php?t=1727540
I'm pretty certain it's not a ROM or a kernel issue. The same is happening to me.
My suspicions lie in the actual charging port and/or the battery. I don't have a spare battery to test. But this happens no matter what rom I use. It tends to be fine after a fresh ROM install or a fresh wipe. But it goes back to 'acting up' after some time.
For example, I left it at around 4% last night only to wake up to it at around 33%. Where before, it would fully charge after around ~4 hours or even less.
Another symptom is that when on wifi/data (whilst plugged in) the phone still drains and even faster so when it is actually downloading something.. This isn't your typical battery drain.
NOT a rom/kernel issue as some would like to suggest (for a "quick thanks" maybe...? ) as this isn't your usual battery drain.
I've been using my Verizon Galaxy Note II since mid June (I got it brand new). It's rooted and always has been, however a couple days ago I was running Jelly Beans build 21 and I ended changing to the HTC Sense Recent apps (I don't think this is a problem, but a coincidence) and after a day or so I plugged my phone into the charger before I went to sleep. However I realize it wasn't charging. I tried unplugging it and plugging it back it and it didn't charge. I changed outlets and no charge so I restarted my phone and it started charging. Ever since then however, my phone has been dying quickly. Maybe losing 20% battery life within an hour. It also charges really slowly now, too. I used to get from 0% to 100% within 1.5 hours to 2. Now I'm at 25% and it says it'll take 3hr 45m to reach 100.
I don't know how to fix it. What heats up is not the battery, but the GPU/CPU area. I changed ROMs and it didn't fix. I also used ODIN to go back to unroot/stock which SEEMED to have fixed it (I lost 3% in 40min compared to 3% in 5 or 7m). But after using it for a little while, it seems to happen again. I then re-rooted and restored from back up to the new rom (not JB 21) and it's happening. I'm currently charging it to 100% and then I'll let it drain and monitor it just in case there is a main problem. I'll also try a different cable tomorrow.
However, I was wondering if this has happened to anyone else or if anyone else has suggestions?
As an FYI, I've
- Turned off DATA
- Tried charging while the phone was switched off (it does cool, but charge time doesn't seem to improve which might be because of the 700-900 amps I'm getting.)
-Underclocked to 1.4ghz and undervolted by 75mv on everything
-Turned on Power Saving mode
-used Greenify for many apps
-Factory Reset
-Reboot
I haven't:
-Let it go from 100 to 1% in order to correctly monitor battery killers
-Tried a clean unroot, back to stock, root, clean flash. (I've done it all except the clean flash [I restored a backup])
-Other things I can't think of
Ok so I have a galaxy s3 gt-i9300, which is about 20 months old, and it started to have this problem a month or so ago. The phone was running a kit Kat cyanogenmod rom, and it was draining the battery somewhat faster than the stock rom, and one day the screen started flickering at around 30% battery, which followed by the phone turning off itself. It can't be turned on until it's plugged in, and when I do so, the battery is at 0% charge, so I figured this was a battery problem and I replaced the battery for a new, original samsung battery. I thought this would make the trick. But I didn't, so my last thought was to return to stock software and this didn't solve the problem either. This always happens to me in every single charge at around 30%-40%. The rest of the charge lasts as long as expected, so the phone basically uses 60%-70% of a charge. I'm all ears for solutions to this and I also want to know what is causing it.
Try a battery from another phone, one that is known to be working correctly.
Else try a full wipe, including preload and internal sd, before you flash the latest stock rom for your country. Factory reset again in recovery after flash.
The phone will charge when the battery is not fully discharged. Once the battery is dead, it will not accept a charge when a charger is plugged in (tried various). This is a fairly new battery, being installed within the past few months. It will accept a charge when I remove the battery and put it back in. A Google search finds some people reporting this issue, but none has a fix. Most say to wait 10 seconds before replacing the battery, but I find I do not have to wait at all. I also noticed that removing the battery very long loses the date and time because Google Play Services complains about it. I wondered if this could mean it is an issue related to the BAT500 mainboard battery getting weak. I am running the CM-11 KitKat ROM.
Thanks.
i would go back to complete stock and see if charging works friend
Hey, I have an S2 (fairly old I know, but can't really change my phone right now :/). Since a few months back I started having problems like the phone shutting down at 12-15% battery left, reboots sometimes consumed 10-15% of the battery. So I bought a new battery but the problems continued.
Now leaving those problems aside, since a few weeks ago my phone started to discharge even thought it was connected to the charger, so I when to see a tech guy and he told me the charging port was loose so he fixed that apparently, bought a new charger after that but the problem persisted, the phone charges sometimes and sometimes doesn't and when it charges it takes hours to reach 100%.
Another thing it's that sometimes I left the phone charging at night and when I wake up the phone says it's 100% but when I take off the charger it drops down to 70-60%.
I'm using 5.1.1 so I thought it could be a ROM problem since Lollipop is a battery killer, I decided to change from Paranoid to CM but still the same story.
Now I'm trying to charge the phone while it's off and seems to be working, although very slowly.
I had the same problem with a Xperia X8, I've changed the battery and flash the stock ROM. Try to do this