Apologies everyone for YET ANOTHER battery life thread -- I hope mine's slightly more actionable.
I've isolated my battery drain issues to bluetooth. As long as BT is on, my battery drains approx 4-6%/hr. With BT off, it's more like 1%/hr. It doesn't matter if I have devices paired or not, and nearby device scanning doesn't make much of a difference (but I keep it off).
1) Does anyone know why this is happening? Is anyone else having this problem or found a fix
2) I primarily use bluetooth in the car, but having to manually turn it on and off each time is a pain. Can anyone think of a Tasker profile that might automate this for me? Unfortunately, my cars are parked within range of my Wifi, so that's not an option.
Thanks everyone!
Not sure if I'm right...but did you check in settings -> more connection (1st screen)-> looking for devices (2nd) if it is active or not (3rd)?
Sorry for my bad English...I'm Swiss ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Gesendet von meinem SM-G930F mit Tapatalk
Your English beats the heck out of my German.
Yeah, it's called "Nearby device scanning" on the English phones, and I have it turned off.
Also just pulled the new VZW update. Things seem worse now than they were.
Cinco5 said:
Apologies everyone for YET ANOTHER battery life thread -- I hope mine's slightly more actionable.
I've isolated my battery drain issues to bluetooth. As long as BT is on, my battery drains approx 4-6%/hr. With BT off, it's more like 1%/hr. It doesn't matter if I have devices paired or not, and nearby device scanning doesn't make much of a difference (but I keep it off).
1) Does anyone know why this is happening? Is anyone else having this problem or found a fix
2) I primarily use bluetooth in the car, but having to manually turn it on and off each time is a pain. Can anyone think of a Tasker profile that might automate this for me? Unfortunately, my cars are parked within range of my Wifi, so that's not an option.
Thanks everyone!
Click to expand...
Click to collapse
I had the exact same issue with bluetooth battery drain. I posted something about it a while back. I never found a solution. I had to install an app called autobluetooth to turn off and on the bluetooth automatically. I use bluetooth mainly in my car and I use a wireless charger in my car. I set the bluetooth to only turn on while charging and my problem is solved. I drain about 1-2% per hour with the bluetooth off and about 3-4% per hour with it on.
Hope this helps.
Yeah, that wont work for me. Thanks anyway.
I think I am having the same problem since the update when I use my BT at work it's draining get horribly and getting hot. I really don't want to factory reset I just got everything how I wanted.
Sent from my SM-G930V using XDA-Developers mobile app
OK, so I think I found it. I enabled developer mode, and killed the Gattservice under Bluetooth Share. So far, things seem a lot better.
I have no idea which app is enabling that service, so unfortunately, I have to kill it each time I reboot the phone, but I can cope with that. It doesnt seem to affect anything else thus far.
I'll update again in a few hours. I'm only about 6 hours into this test.
Cinco5 said:
Apologies everyone for YET ANOTHER battery life thread -- I hope mine's slightly more actionable.
I've isolated my battery drain issues to bluetooth. As long as BT is on, my battery drains approx 4-6%/hr. With BT off, it's more like 1%/hr. It doesn't matter if I have devices paired or not, and nearby device scanning doesn't make much of a difference (but I keep it off).
1) Does anyone know why this is happening? Is anyone else having this problem or found a fix
2) I primarily use bluetooth in the car, but having to manually turn it on and off each time is a pain. Can anyone think of a Tasker profile that might automate this for me? Unfortunately, my cars are parked within range of my Wifi, so that's not an option.
Thanks everyone!
Click to expand...
Click to collapse
Which is the model of your phone?
I have the exact same issue. It started about a month back for me. I'm on the T-Mobile variant. I saw that Bluetooth share had high usage, so killed it and deleted data in that app. I suspect it might be a BLE app that I use - payrange.
Related
Hello,
So recently i've noticed the Battery performance on my Sony Xperia Z3 has become poor, I mainly use my device for socialising etc, I don't game alot. I'm currently Running Android 4.4 Kitkat (UK)
(I'm usually at home and connected to Wi-Fi)
See the results for yourself:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hussain_Salam said:
Hello,
So recently i've noticed the Battery performance on my Sony Xperia Z3 has become poor, I mainly use my device for socialising etc, I don't game alot. I'm currently Running Android 4.4 Kitkat (UK)
(I'm usually at home and connected to Wi-Fi)
See the results for yourself:
Click to expand...
Click to collapse
Check if the device is constantly awake at the detailed battery information if you click on the graph.
If that's the case, search xda for "wakelock" and how to get rid of it.
An easier attempt is, to think if it's a certain app you installed recently or a change you made to your system.
Aronuser said:
Check if the device is constantly awake at the detailed battery information if you click on the graph.
If that's the case, search xda for "wakelock" and how to get rid of it.
An easier attempt is, to think if it's a certain app you installed recently or a change you made to your system.
Click to expand...
Click to collapse
Thank you for your response,
I'll Go ahead and download a Wakelock Detector By someone who works here at XDA, and i'll see if it finds anything; But as of now my battery died again; So i left it dead for 15 minutes, and now i'm charging it back to 100% with no interruptions
Hussain_Salam said:
Thank you for your response,
I'll Go ahead and download a Wakelock Detector By someone who works here at XDA, and i'll see if it finds anything; But as of now my battery died again; So i left it dead for 15 minutes, and now i'm charging it back to 100% with no interruptions
Click to expand...
Click to collapse
You could also install the ota update for lollipop and see if that automatically solves your issue. (new versions are being created to be better)
Another option is to flash the lollipop stock rom and try if that solves it. (but that's a bit more advance)
I suddenly got a similar issue - not as bad as yours but a drop in battery life. I turned off scanning even when wifi is off and turned on location based wifi and my battery life went back to normal. I'd just had a Google Play Services update and have had this issue with various play services updates in the past on other devices which is why that was one of the first solutions I tried.
Might be worth a shot if you haven't already tried it :good:
There's always Greenify.
Repair it or flash another ftf file.
Same thing here. Since I've had this when I purchased it new I've not had any good battery life. My old z2 had way better battery life and stamina mode works.
Sent from my D6603 using Tapatalk 2
Was there any update to this matter, OP?
What brightness options are you using? (% and adaptive or not?)
Also, did you actually update it to Lollipop? Was there any problem with wakelock?
Best regards.
Network & Wake Lock
The last screenshot you posted clearly shows that the battery drain is because of your Mobile Network and a Wake Lock.
Network Signal:
As signal strength decreases, the device requires additional power resulting in battery drain.
The cost of 1 hour’s worth of calls is 150mA, assuming a strong signal
So, on a 2000mA battery, it takes 8% of total capacity (8% =150 / 2000)
This means the same 1 hour of calls could cost as much as 23% of battery life (23% = 450 / 2000)
Wake Lock:
WakeLocks are a Power Manager system Service feature, available to your applications to control the power state of the host device.
Wake Locks can be used to keep the CPU running, prevent the screen from dimming, prevent the screen from turning off, and prevent the keyboard backlight from turning off.
This is a simple question, but I'm wondering if the answer is complex...
With Android 5.1 and below, Google backed up Apps, and certain system settings, etc, but NEVER app data itself.
With 6.0, I noticed some apps (depending if they're compatible with google API's) back up and restore app data as well, included with the app restoration.
You may ask, why would this guy not want google to restore app data?
Simple... In my testing for a seperate issue, I ran into a serious wake lock problem. After a full RUU, full wipe, and reinstallation of a Marshmallow ROM on my M8, I am getting constant wakelocks and battery drains after all my apps are restored with their data.
I would like to test to see if it is faulty data possibly restored with an app, but that unfortunately gets restored with Google's App backup now.
Anyone know if there's a way to system wide wipe app data? NOT just the cache? Or just tell Google only to backup Apps and not data?
Thank you!
The answer is simple although it's probably not what you want to hear. Don't let Google restore your apps. Do it the old fashioned way. Start clean and install your apps as you need them.
If you're not willing to do that, I'd suggest using Titanium Backup to restore your apps instead of Google. With TB you can choose to restore apps without the data. If it were me though, I'd just bite the bullet and install them one at a time. Seems to me that in a case like yours, that would be the best way to go.
Make a backup of what you have now with TWRP. Then start fresh. If you figure out what's going on, you could maybe restore the backup and fix what needs fixing on it.
Sent from my HTC6525LVW using Tapatalk
@bigblueshock you aren't by chance using a 5ghz Wi-Fi network are you?
Sent from my Nexus 6 using Tapatalk
@robocuff - Yeah i suppose so. It doesn't take too much more time to install one by one. I guess an extra few minutes.
dottat said:
@bigblueshock you aren't by chance using a 5ghz Wi-Fi network are you?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I am... Bad idea? =/ I can always do 2.4 instead if that makes a difference.
I also made sure wifi scanning is off.
bigblueshock said:
I am... Bad idea? =/
Click to expand...
Click to collapse
There's a hellish 5ghz wakelock bug on MM. Try 2.4ghz or cellular and see if it sleeps.
Sent from my Nexus 6 using Tapatalk
dottat said:
There's a hellish 5ghz wakelock bug on MM. Try 2.4ghz or cellular and see if it sleeps.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Will try this too. Ill just completely turn off 5 GHZ in my wifi options, just to make sure it doesn't try to connect to any.
I will report back if this helps. Thanks again!
Well, just want to provide an update...
It may not be marshmallow causing this after all. I just did a full clean flash into Viper 4.6.1 (android 5.0.2)
During the day and evening phone was fine. Over night is when the wake locks started happening sporadically. In about 6 hours, dropped about 10%. I checked Wakelock Detector app, and it seems google play services is really pumping out those wakes.
I don't really use bluetooth, I only have 1 device even paired with my phone (my car which disconnects when turned off). But I do keep bluetooth Enabled
I just charged my phone to 100%, turned on Airplane mode + wifi. I'm going to monitor during the day. Is there a way to detect within wakelock detector exactly what part of android is causing this? It doesn't seem like an app itself, because the wakes are coming from android system. Or could an app be causing the google play services wake?
dottat said:
There's a hellish 5ghz wakelock bug on MM. Try 2.4ghz or cellular and see if it sleeps.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Hey @dottat and others. I ran into something funny I figured I'd share Not sure of the cause, but take a look. I posted in the respective ROM's thread, but I thought I'd share it in the Q&A as well.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
A day before this, I temporarily went back to a 5.0.1/5.0.2 ROM, found out it was an app or two trying to destroy my battery in the background with high GPS usage. After adjusting and fixing, Phone drained normally, maybe like 4% a whole nights of sleep.
Fast forward, I reflash Marshmallow ROM, set it up, and no more wakelocks/excessive battery drain. I charge the phone with my QC2.0 Charger (QC probably isn't enabled anyway in kernel, but didn't make a difference to me) from about 50% to 100% and unplug, and go to sleep.
This morning I woke up to phone at 86%. I check wakelock detector, and power history, nothing out of ordinary. Scratching my head at this point, I restart the phone, and BAM, phone is at 35%.
Some points below
1) I believe it was the first time I charged the phone fully, not sure if that had anything to do with it. I've never needed to calibrate battery in past...
2) Wifi was strictly on 2.4 Ghz. Cellular coverage is good. GPS is on, but not being used.
This sounds like a longshot, but I'm leaning to the kernel probably not supporting QC2.0, and it being detrimental to charging the phone. Possibly ROM thinking it's enabled, but kernel is disabled. So right now I'm charging the phone to 100% using a computer USB port (500mA max) just for testing purposes.
Have anyone ever seen this before?
There seems to be some sort of consensus that the LTE versions of the watch have more battery trouble
Has anyone actually given it some thought as to why?
When LTE is off it should not make a difference, but it does seem to exist.
Is the emergency service always connected, is there a bug where the modem drains power even when it should be off?
Curious to hear what you think
user822 said:
There seems to be some sort of consensus that the LTE versions of the watch have more battery trouble
Has anyone actually given it some thought as to why?
When LTE is off it should not make a difference, but it does seem to exist.
Is the emergency service always connected, is there a bug where the modem drains power even when it should be off?
Curious to hear what you think
Click to expand...
Click to collapse
I have discovered my mistake was thinking that I needed to have the LTE button in the quick menu lit up blue to work away from the watch, my battery life has improved since I discovered it doesn't need to be lit up blue as that is permanently "on", by having the button grey it's on "auto"
MilgeS said:
I have discovered my mistake was thinking that I needed to have the LTE button in the quick menu lit up blue to work away from the watch, my battery life has improved since I discovered it doesn't need to be lit up blue as that is permanently "on", by having the button grey it's on "auto"
Click to expand...
Click to collapse
What is "LTE button in the quick menu"?
I only see Mobile Data. Afair there was mobile network button in the Tizen, but I do not see it in the GW4
XorZone said:
What is "LTE button in the quick menu"?
I only see Mobile Data. Afair there was mobile network button in the Tizen, but I do not see it in the GW4
Click to expand...
Click to collapse
I think that's the same button I called LTE/mobile network, it's the up/down arrows design button, sorry for the wrong description!
I got mine the other day replacing my 1st gen galaxy watch. I set it up in the same way as my old watch and was amazed to see the battery drop 10% in one hour, since then I have made one change... I disabled the option for the screen to come on via gesture, settling for a tap if the screen... I took it off charge this morning at 5:30am and it is now 21:21BST... It has 58% remaining... a significant improvement over day 1
I have the same problem with LTE. Whenever I use "auto" for LTE settings, the watch would keep trying to find signal and that would drain the battery. Which is insane, especially because: 1) the phone is always nearby, bluetooth connected 2) i haven't set up any carrier yet!
I have the network connection on. For me, i have a good 2 days of battery life. Compared to my previous WearOS watches, it's excellent...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Did some testing and disabled everything (HR, Stress, Exercise detection, notifications, LTE/Mobile data, Wifi, NFC) all that was left on was the BT connection and I was still getting about 8% per Hour drain (12 hr 30 min life). Disabled BT and enabled Wifi for connection and drain now at 3.6% /H. (Stats as per Battery and Charge Monitor for Wear OS). So it doesnt appear to be a drain from any of the health monitoring or notifications etc, but possibly from the OS, which hopefully Google/Samsung will resolve/improve with updates.
stickydonkey said:
Did some testing and disabled everything (HR, Stress, Exercise detection, notifications, LTE/Mobile data, Wifi, NFC) all that was left on was the BT connection and I was still getting about 8% per Hour drain (12 hr 30 min life). Disabled BT and enabled Wifi for connection and drain now at 3.6% /H. (Stats as per Battery and Charge Monitor for Wear OS). So it doesnt appear to be a drain from any of the health monitoring or notifications etc, but possibly from the OS, which hopefully Google/Samsung will resolve/improve with updates.
Click to expand...
Click to collapse
There was a Health Services update yesterday and since then, my watch battery lasts WAY better. at 17hrs 33min i still have 64% left and i had re-enabled everything again as it should be. Continuous monitoring, sleep with SPO2, location, LTE, etc.
Hey there. I am noticing a big battery drain on my GW 4 40MM Bluetooth when I am going to sleep, for example last night I've gone to sleep with 83% of battery left and in the middle of the night the watch died, the same thing the night before. Normally I would get about 20-25% loss with previous firmware
This problem started after I updated to R860XXU1CUJ2. The strange thing is that I am not noticing bad battery life when I wear the watch in the day (maybe a little more draining compared to previous firmware), also note that I am just using regular sleep tracking not O2 or snore detection even though I have used this options with the previous firmware and still I had battery when I woke up.
Does anyone else has big battery drains when sleep tracking and also is there an official site where I can make a ticket?
Thanks!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Same here, happened to me twice already , can't track it back other than sleep mode
Stormingsoul said:
Same here, happened to me twice already , can't track it back other than sleep mode
Click to expand...
Click to collapse
I also posted here:
https://www.reddit.com/r/GalaxyWatch/comments/qe1eyb
I turn off Bluetooth at night and I want to try if keeping it on does anything, because as you can see from my screenshot it uses Wifi and maybe this affects the battery life at night. Do you keep Bluetooth on or off?
Lefty_Kas said:
I also posted here:
https://www.reddit.com/r/GalaxyWatch/comments/qe1eyb
I turn off Bluetooth at night and I want to try if keeping it on does anything, because as you can see from my screenshot it uses Wifi and maybe this affects the battery life at night. Do you keep Bluetooth on or off?
Click to expand...
Click to collapse
I would say you've got your answer. If you have enabled the option to continue receiving notifications via wifi or lte then turning off Bluetooth will inevitably use wifi all the time and result in high battery drain, most probably...
CUJ2 version as well, 28% battery drain during the night. I just left the watch on my table. No sleep tracking. No wifi. No app listed under battery usage. Nice!
Is there a way to get more details on battery consumption?
Lefty_Kas said:
Hey there. I am noticing a big battery drain on my GW 4 40MM Bluetooth when I am going to sleep, for example last night I've gone to sleep with 83% of battery left and in the middle of the night the watch died, the same thing the night before. Normally I would get about 20-25% loss with previous firmware
This problem started after I updated to R860XXU1CUJ2. The strange thing is that I am not noticing bad battery life when I wear the watch in the day (maybe a little more draining compared to previous firmware), also note that I am just using regular sleep tracking not O2 or snore detection even though I have used this options with the previous firmware and still I had battery when I woke up.
Does anyone else has big battery drains when sleep tracking and also is there an official site where I can make a ticket?
Thanks!
View attachment 5439437
Click to expand...
Click to collapse
Same problem here. In this update, I think the Watch WiFi is set on when I turn the phone WiFi or data off. It's not happening before this update.
Lefty_Kas said:
I turn off Bluetooth at night and I want to try if keeping it on does anything, because as you can see from my screenshot it uses Wifi and maybe this affects the battery life at night. Do you keep Bluetooth on or off?
Click to expand...
Click to collapse
I agree with DaReDeViL. You have your answer. Why do you turn off BT and leave on wifi? Wifi uses significantly more power. I'm on newer DUJA but I saw no issues with CUJA which I ran for several weeks. I have sleep tracking on without O2 or snore detection. I don't have BT or wifi on when I sleep though. I have no desire to get notifications when I sleep, I want to sleep. I actually use bedtime mode when I sleep. I loose between 4 - 6 % of battery when I sleep (I average about 7 hours). This has remained fairly consistent with every update.
Hello there!
I'm having problems with this device, the Mi 10 Lite 5G (Monet) in particular.
Out of nowhere it started having an insane battery drain. To the point that if i unplug it from the charger before i go to sleep so the phone starts at 100% battery, when I wake up between 6 and 8 hours later, I find it at 30 to 50%, at an average of 7-8%/h.
I'm on all stock: latest MIUI, no bootlocker unlocked, no root, ironically I chose this device 'cause i didn't want any headaches.
Remembering my olden modding days, I remembered about the wakelock hunts, so that's the first thing i thought about. I tried multiple apps to do so and even the Battery Historian tool via a bugreport. Everything points to some kernel wakelocks that pretty consistently activate, not letting my CPU sleep at all, which makes sense as to why It would drain battery like that. The problem is I can't figure out what causes it. There's no app that does it, it seems to be all kernel stuff, I even factory reset and tested without installing anything. Either it's something with the system itself, that I can't quite pinpoint, or i'm starting to think it might be hardware. I don't wanna sway anyone, but my best bet is it could be a faulty usb-c charging port. Although I don't know how it could make it this bad, and I'm obviously not sure it even is it. Would suck to change it, spend money on it, and still have the problem.
Aside from the wakelocks, there's also another bit of info that makes me think that: when off, if i plug the usb cable in to charge it, the phone doesn't get to the battery charging animation, but it keeps showing me the Xiaomi logo screen, over and over. I haven't tested if it actually charges in the background or not, for fear of making things worse.
I even checked if there was something weird in the hidden battery stats by dialing the code *#*#6485#*#*, but aside from the phone going into "sink attached" mode at random intervals, which apparently means it's trying to provide charge to something else through the port or wireless charge (that this phone doesn't even have)...? I can't tell if there's anything weird with it or not.
I know my way around android a little bit, but I'm a little bit lacking when it comes to intricate information like this, and I couldn't find any information about this (these) particular wakelock(s) and everything else around 'em.
I'd really appreciate it if someone who knows this kind of stuff better than me could help me out with it. Even just to know what the problem is and there's no real solution.
I'll attach a couple screenshots from Battery Historian (my phone's been factory reset, so I have no apps on it, and don't plan on putting any on aside from the ones I absolutely need, in case I have to send in in for repairs, or root/mod it to try and mitigate or solve this) and alsothe bugreport itself, in case someone needs to look at it in detail to try and sniff out the problem.
Also, if this wan't the right place to post this, let me know. I went for the device, but maybe there's a better section to more in general help with these types of issues, but if there is i couldn't find it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks in advance to anyone who even only just thinks about helping me out!
EDIT: For anyone reading this, the problem was indeed a broken usb-c port/module. I bought a replacement and swapped it out myself and my battery is back to being perfect. Well, almost perfect... This quickly discharging business has lowered its health obviously.
I suspect some sort of short would make my phone believe something was continously being inserted and removed into the usb port, so the CPU would keep being woken up, and kept consuming extra power to try and read something off of it.
I hope this helps someone!
From what I can tell there is no problem. The battery is being consumed at a normal rate by the cpu, wifi and Bluetooth. If you're not using them just deactivate them.
Check the USB port for fluff etc stuffed deep down by repetitive compacting. Use something pin like but not metallic to scrape any foreign objects out.
shivadow said:
From what I can tell there is no problem. The battery is being consumed at a normal rate by the cpu, wifi and Bluetooth. If you're not using them just deactivate them.
Check the USB port for fluff etc stuffed deep down by repetitive compacting. Use something pin like but not metallic to scrape any foreign objects out.
Click to expand...
Click to collapse
While it does appear that it is being used normally, that graph stays the same if i turn everything off, either through airplane mode or by manually disabling wi-fi, bluetooth, GPS, or anything else. I can't turn off the CPU, so there must be something that keeps it up and running for no reason while it should instead be sleeping, and I can't for the life of me figure out what it is. Which is why i think it might be hardware.
I will do the deeper cleaning operation as soon as I can get my hands on a pin-like object small enough that's not metal. Everything i have is either slightly too big to reach more than just the surface of the port, or thin enough but metallic.