I have a 20 day old galaxy s6 duos. It was bough new off ebay. I was functioning properly and when on holiday I dropped it onto a tiled concrete floor from a height of 2-3 feet.
Since then the battery has been draining abnormally.
I have disabled apps still no joy. Then ran the phone in safe mode with no improvement. Then did a reset using software with no improvement. Then wiped cache but still no joy. Then wiped cache and hardware reset. Finally disabled all apps and forced stopped a few more. Put the phone in airplane mode but despite that the phone is drains 10 %per hour with the phone not being used.
No apps running on the battery usage screen the only thing shown is device idle 1 %. .
I cant understand how dropping the phone can cause the battery to malfunction . Any ideas or suggestions ? Or something else I should be trying.
I wish it was easy to change the battery but that is not the case . I just wanted to see if anyone else has suggestions before I go down the route of replacing the battery.
Many thanks in advance.
Can
Try flashing stock 5.1.1 ROM via odin.
Thanks for the reply, It is already running android 5.1.1 baseband version G920FXXU2BOFJ . I dont understand the rest.
Do you think it worth reflashing the phone still ? Happy to provide more information.
Hi,
I'm getting some insane levels of idle battery drain recently. A bit of background,
- US Stock
- Rooted
- SuperCID
I was having this battery drain everyday for about 2 weeks, so I wiped my phone and started fresh. Since I did, I've been slowly introducing only a few apps everyday, and the battery was perfect until today.
All I did since yesterday when it was good, was tether to my laptop for an hour, and when I noticed a few hours later that the drain was back I removed the Bluetooth pairing completely. But the drain remains.
My phone sits in an awake state with the screen off for 99% of the time.
Here are some screenshots from Better Battery Stats and Wakelock Detector which don't seem to show much apart from a Google sensor.
http://imgur.com/a/eKqjl
Desperate for help because as much as I love this phone, with this situation it is barely usable.
Some more screenshots. Wakelock Detector and Android Settings.
The only red flag I can see is something called "Significant Motion(12)" which was awake for almost 7 hours. But I've been googling this and not finding anything about it.
Another screenshot now that I am at a computer - this is from a Google Historian report from a bugreport I just generated.
Something labelled "Abort:noirq suspend of c171000.uart device failed" woke the kernel up 89696 times. Wonder if this is the "significant motion" sensor that BBS is reporting?
I have the same problem.
It's started 3 days ago and i don't know how to fix the problem.
I hope that htc would fix this problem on this weak.
If someone know how to fix this problem until htc do something, please reply.
ShDorLq said:
I have the same problem.
It's started 3 days ago and i don't know how to fix the problem.
I hope that htc would fix this problem on this weak.
If someone know how to fix this problem until htc do something, please reply.
Click to expand...
Click to collapse
I don't even know what the problem is - so how do you know you have the same problem?
I'm not sure this is a problem for HTC, because my phone was perfect for 3 days after resetting it. It only started again last night. If it was great for 3 days and started on the 4th, odds are that it is something about my set-up rather than a problem with the stock firmware.
Zico 10 said:
I don't even know what the problem is - so how do you know you have the same problem?
I'm not sure this is a problem for HTC, because my phone was perfect for 3 days after resetting it. It only started again last night. If it was great for 3 days and started on the 4th, odds are that it is something about my set-up rather than a problem with the stock firmware.
Click to expand...
Click to collapse
I have not changed anything on my phone and the problem is surprising.
Last week I did not install apps or add files.
I also have Watsapep at the top of the table in the utilization of the battery.
android 8.0.0
software number 2.42.617.1
not rooted
stock rom
Try disabling google apps one by one
also try using your phone without wifi
I already tried disabling app by app when it first happened, and did this over 2-3 weeks basically going through all the main suspects and Google Apps.
About to go to sleep tonight, I am going to try,
1 - turning off wifi and Bluetooth and charging the phone to a decent charge level
2 - force restarting the phone after removing it from charge
3 - leaving it on the bedside table untouched until I wake up in ~7 hours
Someone with a U11+ said they need to force restart after charging, so it’s worth a shot right?
Also just posted this about the sensor in another thread. Anyone else having trouble, would appreciate if you could also try these steps,
Zico 10 said:
The ways I stumbled on this were,
1. Better Battery Stats
Under Sensors, you'll notice Google Play Services with a high percentage. Click/press it and you'll see a listing for "Sensor: Significant Motion". This to me indicates that the device thinks it is being moved and refuses to go into Doze mode.
2. Google Battery Historian
Charge your device and let it drain for a while. Then connect it to your computer and take a bug report using ADB - adb bugreport bugreport.zip .. visit an online version of the tool here https://bathist.ef.lc .. then upload the bug report. Under "kernel wake up reasons" you'll see "Abort:noirq suspend of c171000.uart device failed" with an abnormally high number.
3. Take a dumpsys of battery stats
Using ADB, after running your battery down a little, run - adb shell dumpsys batterystats > batterystats.txt .. read the file and you'll see the line I pasted above in my last post.
Would be interested to see if someone suffering from the same symptoms could try this and see if they get the same things. U11 or U11+.
Click to expand...
Click to collapse
Same problem of cell standby battery drain with U11+
EMEA U11 plus running 1.24.401.2
Abort:noirq suspend of c171000.uart device failed
Click to expand...
Click to collapse
repeating endlessly when i did a battery dump
hamdir said:
EMEA U11 plus running 1.24.401.2
repeating endlessly when i did a battery dump
Click to expand...
Click to collapse
With the associated battery drain I assume?
I did this overnight which actually seems to have worked,
1. Switch off Bluetooth and WiFi.
2. Charge phone (it got to 76% when I decided to sleep).
3. Remove from charger.
4. Force restart with vol down + power
Today I’ll experiment to see if I need to do the same 4 every time I charge, or if maybe it is related to only a few of these.
Overnight my battery lost only 5% in 8 hours.
When I get to work, I’ll do a battery dump to see if the noirq error is still present.
Guys today I update my google apps and the problem gone!
how your phone after the updates?
Still there. Seems to be related to charging my phone whilst Bluetooth is on.
When I disconnect from charge, I get battery drain until I charge again with Bluetooth first turned off, then restart the phone.
Zico 10 said:
Still there. Seems to be related to charging my phone whilst Bluetooth is on.
When I disconnect from charge, I get battery drain until I charge again with Bluetooth first turned off, then restart the phone.
Click to expand...
Click to collapse
Found my culprit to be related to Garmin Connect, Fenix 3 watch BT connection.
Could be related to bad firmware.
Edit: Found this same error in my logs a week or two ago when I was trying to track idle drain and lack of deep sleep.
Seems to have disappeared when I disconnected my Garmin watch.
Last night I just had the first occurrence that wasn't related to Bluetooth.
The drain happened despite having Bluetooth turned off when I charged the phone, however I didn't reboot either (and haven't been doing so unless I was trying to get rid of an ongoing battery drain).
I think until we hear of a new firmware release, I'm just going to go through and turn Bluetooth off whilst charging and then restart my phone when I unplug. A minor hassle but at least a working fix.
I had the exact same problem (Significant motion) not allowing my phone to go into deep sleep. For me, just a restart helped from what I remember. Haven't seen this issue since past 4-5 days since it last happened.
I have the same problem with battery drain since the last security update. I am able to fix it temporarily by disconnecting from my huawei smart watch. I will try disconnecting BT while charging and restart after it.
Got a security update today. Hopefully this will fix the drain.
Hello
the u11+ 1.24.401.7 update was just pushed, it is said to address standby issue, my battery dump after reboot no longer contains any reference to, Abort:noirq suspend of c171000.uart device failed
Also early this week a Chrome web view update was pushed in playstore which address issues from Google's side
Anyone experiencing excessive battery drain with the May patch update? Android system drains the battery too much. I just reset my phone 2 days ago, installed my usual apps, updated the system and then this happens now. Any fix on this?
Hello,
It's actually a well known problem in the community
1. I have submitted a report to Sony and request them to release a software update to fix the Kernel
- which means that our best chance here is to hope it is fixed with an update, the root cause is the Kernel not being optimized
2. I am on the verge of snapping this phone in half as I asked around the community and received no answers , been trying to fix this for 1 year straight
shadowhunter20 said:
Any fix on this?
Click to expand...
Click to collapse
Out of the blue: A factory reset could help.
You definitely have a problem that your phone does not idle (look at my screenshots (v ..128):
idle (Ruhezustand) should always be in the top three).
One of your messengers might the culprit.
Try to disable them all and switch them on one after another to find a possible culprit.
Hi,
I too have these issues. Did you manage to workout which app was at fault?
Yes, another case here. We are still investigating the problem and checking if it's some app or system itself. Most of battery was used by android system and battery was empty in 11 hours.
Problems started with 41.3.A.2.128.
So is it worth updating?
Wheelie74 said:
Yes, another case here. We are still investigating the problem and checking if it's some app or system itself. Most of battery was used by android system and battery was empty in 11 hours.
Problems started with 41.3.A.2.128.
Click to expand...
Click to collapse
In our case problem was either facebook or whatsapp. Both remove/disabled and now battery lasts as always.
Yes, it is horrible!! I woke up at 7 am, took my phone off the charger and never made a call, or even turned on wifi. I came back from being outside around 11:30 and I was down to %34!! Without the phone having done nothing but sit there and recieve 2 missed calls and 5 text messages!! I usually get 2-3 days on a charge with my XZS depending what I am doing. Needs to be fixed and fast!!!!
Dont factory reset, because the battery issue will not go away for rom issues.
But the "Messages" app do look suspicious for 5%.
There are some devs like to tell people factory reset for everything first and even reset for regular stock rom updates.
Its a bit excessive, like formatting Windows for every time it crashes or even for every Windows updates... Unless you enjoy restoring data & apps.
Should try something to troubleshoot and fix it first before resetting, so we know whats wrong.
The battery drain on idle is slightly better after a week, but we still have to wait and see.
i have problems too, with last existenz with this version battery its a joke
HI all,
I need help figuring out what drains my battery, it drops from 100 to 79% over night which is too much of course. I tried factory reseting but the issue persists. I'm on the latest firmware, rooted with magisk 19.2, have a ton of apps but none indicate battery drainage in the battery settings so I installed betterbatterystats and hope someone can tell me what's the issue
btw another issue that I had on my last phone as well, I get randomly three short vibration without any nottification, as it was present on the last phone like it it now it must be related to an app, how to figure out which one?
Has anyone else experienced more phone related battery drain after the recent UI update? It's not using alot of battery or anything, but I do see the symbol on the phone were Samsung accessory service is in use way more often now. And prior to update, the plug-in never registered at all in my battery usage. So basically it would use under 1% battery for the entire battery cycle. Now, it uses 2-3% per cycle and I've done nothing different with the phone. Has anyone else noticed this and know how to fix it?
I have the same problem after upgrade to new frameware One UI . Super fast Battery drain.
My friend had battery drain after update. A hard reset fixed it.
SimboXXX said:
My friend had battery drain after update. A hard reset fixed it.
Click to expand...
Click to collapse
Reset on the watch, the phone, or both?
mistermidas said:
Reset on the watch, the phone, or both?
Click to expand...
Click to collapse
He reset the watch.
I have got super fast battery drain as well...its so bad the watch drains even when it is turned off...I used to last 2 days without having to charge the watch but now by end of day I am down to 10% or so...really really baffling. I have reset the watch numerous times but it doesn't seem to get fixed...
And firmwares for this watch are so hard to come by...I wanted to do a downgrade...
Moe5508 said:
I have got super fast battery drain as well...its so bad the watch drains even when it is turned off...I used to last 2 days without having to charge the watch but now by end of day I am down to 10% or so...really really baffling. I have reset the watch numerous times but it doesn't seem to get fixed...
And firmwares for this watch are so hard to come by...I wanted to do a downgrade...
Click to expand...
Click to collapse
This is the reason is send my watch in for repair (warranty). It came back with a new motherboard, problem solved.