Anyone have an Android Wear watch? I just got a Moto 360 and my G3's battery is getting killed by Android Wear:
{
"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"
}
I've been using the LG G Watch for just over two weeks now and haven't really noticed any battery life changes.
I do have Holy Angel's kernel running with intellidemand and Bluetooth is always enabled on my phone, even when I'm not wearing the G Watch.
But, I don't have NFC always running, if ever, unless I'm using my washer and dryer and feel frisky with NFC use.
Nor do I use Wi-Fi, it's always on mobile, screen brightness at full always and sync always enabled with all my widgets and apps set to update as often as possible.
It could be the Moto 360, but my wife has the G Watch as well with her G3 and her battery life is fine, comparable to before she had the G Watch about three weeks ago.
Someone was having a similar issue on the Reddit forum for Android Wear and a solution was brought up pretty quickly.
Go into settings --> Apps --> Android wear --> press "Clear Data" then try cycling your bluetooth antenna (off and back on) and try again.
I personally have noticed greater battery life from using my 360, bluetooth 4.0 is pretty light on power usage and not using the massive 5.5 inch display for texts and music controls saves me a ton of battery life.
The 360 is being pushed an update that improves bluetooth connection. May help with battery.
appledroid said:
Someone was having a similar issue on the Reddit forum for Android Wear and a solution was brought up pretty quickly.
Go into settings --> Apps --> Android wear --> press "Clear Data" then try cycling your bluetooth antenna (off and back on) and try again.
I personally have noticed greater battery life from using my 360, bluetooth 4.0 is pretty light on power usage and not using the massive 5.5 inch display for texts and music controls saves me a ton of battery life.
Click to expand...
Click to collapse
I uninstalled Android Wear and Motorola Connect (which is the same as clearing app data) and I no longer see Android Wear using all that battery, but now Android System is keeping my phone awake a lot. After a day, it had a total keep awake time of 2 hours. It didn't use to be that much.
stevessvt said:
The 360 is being pushed an update that improves bluetooth connection. May help with battery.
Click to expand...
Click to collapse
I just read that. No update for me yet, we'll see if it makes a difference.
I also have the same problem on my nexus 5.
I tried deleting the app data abd resetti g the bluetooth but that doesnt seem to do anything either. Im getting very frustrated with this drain
I also had noticed increased battery drain with my g watch and g3. After trying various things it seemed to be related to run keeper or edemodo. For some reason after using the watch with the apps for a run the battery drain his huge. It is android system using all the battery there is wake lock associated with it. Once I uninstall everything is back to normal battery. Installing the apps don't drain battery. It is only after using run keeper. I am wondering if for some reason the watch is keeping the app running somehow.
Related
While I own an international unlocked version of the S2, i assume the Sprint version must be very similar. After countless hours of trying to figure it out, this is what i discovered and solved my battery draining issue (it's been two months with no problems at all) i get 4 to 5 hrs display time and it lasts me all day. I was on stock 2.3.3 and recently upgraded to 2.3.4. with same results. The following tips are things i did prior to rooting, and they solved my battery drain issue.
1. Anything that tracks location is a battery drainer and i discovered that i was using wireless networks for location (it's also not that accurate) and it was the biggest culprit, so i disabled it and now i use gps (more accurate) as needed and turn it off when done. If you use Google maps with google latitude enabled, sign out of latitude when done using it.
2. App killers use more battery than saving it by closing apps and processes that run in backgroung that will automatically open right back again. Stay away from them.
3. Some apps if left in memory will constantly cause cpu spikes (suspend and events/0), in my case it was Facebook and Xfinity apps. So i close all active apps in task manager. Don't really clear ram, just close active apps.
4. Use Watchdog from Market to track any apps that might be using a lot of cpu.
5.Enabling Back up my data also drained my battery, so i disable it.
Hopes this helps...
AqueousBor said:
1. Anything that tracks location is a battery drainer and i discovered that i was using wireless networks for location (it's also not that accurate) and it was the biggest culprit, so i disabled it and now i use gps (more accurate) as needed and turn it off when done.
Click to expand...
Click to collapse
While I can't state for certain that it's causing any extra battery drain, Carrier IQ is hooking into the location service, and every time your location changes, grokking your latitude, longitude, accuracy, and a timestamp. This is new to the Epic Touch.
I constantly have alerts for suspend and event/0 in watchdog. In the stock task manager there really isnt much running to kill. It's driving me nuts. haha My battery life isnt horrible but I think it could be better..
{
"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"
}
I'm running AOKP 20 and Franco kernel but seem to be getting really bad battery life. I see folks claiming 1% battery loss over 8-9 hours of sleep. Mine loses 12-15% while I sleep and that is with WIFI on.
I'm not real familiar with the Better Battery Stats or Battery Monitor Widget. Can I use one of those to find out what is killing my battery life?
Does anyone know of something that might be causing this or how I can find out what it is?
Rogue app? Wich Franco are you using?
Sent from my Galaxy Nexus using xda premium
I tried 14.4 but went back to 13.1 hoping things would improve. Same on both.
Better Battery Stats' ugly interface really does mask what I feel is a great app. In your case, assuming you have it installed, change the top box in the app to Kernel Wakelocks and Partial Wakelocks and see what is preventing your phone from sleeping (post the screenshots of the two pages if they mean nothing to you).
I've also found CPU Spy to be an easier to understand quick overview of what's going on with my device. It'll list out the various clock speeds my kernel has and how much time was spent in each. If you notice "deep sleep" isn't the biggest bar, you likely have something going on.
Juvenall said:
I've also found CPU Spy to be an easier to understand quick overview of what's going on with my device. It'll list out the various clock speeds my kernel has and how much time was spent in each. If you notice "deep sleep" isn't the biggest bar, you likely have something going on.
Click to expand...
Click to collapse
Yup, yup. I was going to suggest CPUSpy, it's a decent little app. My phone will spend ~60-70% of the time in deep sleep over a nine hour or so period with WiFi on.
It looks like my phone is going into deep sleep and then something is waking it up and it can't go back. These processes don't mean much to me...
{
"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"
}
The audio out wake lock is caused by keyboard sounds, touch sounds and screen lock/unlock sounds. Turn those off.
The other wakelock seems to be your gallery syncing constantly.
Sent from my Galaxy Nexus using xda premium
Touch sounds were on, I turned those off. Why would those be waking my phone up in the middle of the night though?
How do I keep my gallery from syncing constantly? The only setting I see in the gallery options is to turn off my google account sync which I assume would turn off my gmail and other things as well?
Never mind, I found where to turn off photo sync.
Is it normal for touch sounds and gallery updates to keep your phone awake all the time? If so, what is the point of having them if they are going to eat your battery...
what franco are you using?
13.1
10 chars
Here is a screen of my overnight usage. I don't know why but I've just noticed the clock has gotten stuck. Stupid thing.
*Edit* I have a few things syncing over night, and the LED was literally flashing for the entire time, I didn't check my e-mails on purpose to see what nine and a half hours battery drain would do when that bright little LED was flashing all night, not bad I reckon!
recomand Apex rom
from bigxie
http://forum.xda-developers.com/showthread.php?t=1399238
15% after 63 hours, UV and OC
I have been having issues with cm10.1 "android OS" using too much battery. And i have seemed to squash out the bugs. nearly doubling screen time. (in the sense that by bed time i had about 4 hours screen time and 10% battery left and now can hit 8 hours in a day)
I am going to slowly try different things to see where hte main issues were. but here are the majority of the changes i made.
1. Wifi, this should be off during the day, simple but true. Also i noticed build.prop had wifi scan interval set to 15 instead of the recommended 120
2. Auto rotate screen, i have read this has bugs in some builds (not sure on ours) it should be disabled unless you absolutely need it, you can add a quick tile for quick toggling. (I honestly think this is the biggest cuplrit)
3. Dev options, try to have all unneeded dev options off. I had strict mode enabled, not sure if it made a difference, but its useless cpu cycles.
4. Battery apps, as helpful as they are, uninstall asap, unless you are isolating a problem they eat cpu cycles trying to figure out what is eating your cpu cycles...
5. Notification Light, its not the LED so much as it is the CPU cycles required for the timing of the led light.
6. sign out of or uninstall/freeze (disable) google talk.
7. disable gps (use quick toggle for when really needed)
8. go to system settings -> google (under accounts) -> maps & lattitude -> make sure "report from this device" is unchecked and if you dont move around a lot (aka you work really close to home) turn location reporting to either do not update, or set location...
9. and of course any other common place one, screen brightness etc...
I will slowly implement these back in to see if they cause the drain to come back.
I think its auto rotation honestly, but it could have been a combination of all of them.
I get 8-9 hours on stock 4.1.2
I get 6 hours screen time in 4.2.2 without doing any of that, and I still think that's pretty bad compared to touchwiz. I use all those functions mentioned (except gtalk) all the time, so cm10.1 is nowhere near usable as a daily driver for me.
So battery is not draining on its own anymore.
Now time to find the culprit.
If its autorotation then the cm team can fix it and that's a good thing
{
"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"
}
Sent from my GN2 using XDA app.
simonxliu said:
I get 6 hours screen time in 4.2.2 without doing any of that, and I still think that's pretty bad compared to touchwiz. I use all those functions mentioned (except gtalk) all the time, so cm10.1 is nowhere near usable as a daily driver for me.
Click to expand...
Click to collapse
I'm not saying cm10.1 is the culprit. I'm trying to figure out what is and so I can help squash it.
Sent from my GN2 using XDA app.
I get 8-9 hours on stock 4.1.2
I use Deviant's Xone rom. Get 2 days+ of use depending on how I use my phone. Even with heavy use I get a good day out of it, at least for what I need.
(If you have any problem in upgrading to latest android wear 5.1.1 , please go to this thread .)
I have noticed people with android wear 5.1.1 started to discuss battery. However your battery curves of "android wear" or "wear battery status" app are just not that detailed for trouble shooting. Besides, it is not reasonable you wait for one day for a curve to be generated —— your know everyday is different, may be you take an extra exercise today. Good news is there is a lollipop tool called "Battery Historian" for analytic purpose. This works for android wear lollipop too.
If I was not wrong, there are previously some issue with SWR50 (I just recalled, may not that related to this topic). What I met is
①The compass app (Also DeveloperOpition-Manufacturer-Compass-Yaw) will become uncalibrated after sometime, if you rotate your watch, the angles only stay in like 170°~220°
②I remember a Youtube review saying SWR50 rotate-wakeup is not as sensitive as LGR is.
③Some app (e.g. autowear) cause SWR50 dramatical battery fall and accelerometer not responding
Guess there is something special of SWR50. At least ① still in 5.1.1 in my case.
Go to github thread to download "Battery Historian".
I was still using Historian 1.0 with python when writing this, but just noticed it has upgraded to 2.0 and supports Go just several days ago.
to start:
1. enable log in your watch: "adb shell dumpsys batterystats --enable full-wake-history"
2. reset timeline if you need: "adb shell dumpsys batterystats --reset"
3. After some time
4. Get report: "adb bugreport > bugreport.txt"
5. Generate html:
Follow the instruction to use GO.
Or if you are using python(2.7.9), then the command is "Python.exe historian.py -a bugreport.txt > out.html"
Reading the html may be difficult for new ones (for me too).
To understand the html, I suggest
1. find out where the battery drops most from curve
2. Check hardware like screen gps wifi etc on/off state,
3. Check frequency and Lenght an activity wakeup (There is also a summary blow)
Most of time it is the background wake up that eats your battery.
Yesterday night I put watch (90%+) but when I wake up in the morning it dropped to (30%-). I suddenly realized it may be a good example for here.
AS you can see the screen is always off, besides the percentages sums up only around 30%.
And here is a detailed graph:
{
"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"
}
The result surprised me: it says "com.npi.wearbatterystats" waked up my watch a lot, but this app is "Wear Battery Stats".
I added a battery curve above the status but not ready to share the code (but you can see what is added in html code in my View attachment html.zip)
You are welcome to share your battery consumption with your folks and let us make our watches live longer every time. :cyclops:
Surprising to see wear battery stats causing the drain. I'll. Uninstal that and see how it goes
With battery historian you see easily know the state of your wifi and screen at any moment, and which activity waked up your screen etc.
My second record. it is 'wear battery stats' again, interesting though.
anees167 said:
Surprising to see wear battery stats causing the drain. I'll. Uninstal that and see how it goes
Click to expand...
Click to collapse
how would you do that?
Hello everyone,
I have noticed an absurd drop of the battery level when I'm using my device for usual applications such as Facebook, YouTube, etc...
When it's on 20% approx the battery reaches zero level in less than 10 minutes. This problem started when I have updated my device to the last firmware available (14.6.a.1.236)
I have re flashed the firmware 2 times via flashtool and the results are the same.
It could be an software or a hardware issue?
Thank you for your help :fingers-crossed:
{
"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"
}
Thank you very much!
My device has 13 months of use.
I use greenify in root mode, but don't have xposed.
I have used a calibration battery app and still have this problem.
May I use xposed in stock ROM without the risk of bricking my device?
3132 said:
Thank you very much!
My device has 13 months of use.
I use greenify in root mode, but don't have xposed.
I have used a calibration battery app and still have this problem.
May I use xposed in stock ROM without the risk of bricking my device?
Click to expand...
Click to collapse
you have the battery dead bug. search and you will find.
3132 said:
Hello everyone,
I have noticed an absurd drop of the battery level when I'm using my device for usual applications such as Facebook, YouTube, etc...
When it's on 20% approx the battery reaches zero level in less than 10 minutes. This problem started when I have updated my device to the last firmware available (14.6.a.1.236)
I have re flashed the firmware 2 times via flashtool and the results are the same.
It could be an software or a hardware issue?
Thank you for your help :fingers-crossed:
Click to expand...
Click to collapse
Chances are it's a hardware issue and replacing your battery could fix it:
http://forum.xda-developers.com/son...ttery-reporting-phone-dying-suddenly-t3095120
I had the issue where my battery would drop from >70% to 0% suddenly, and replacing my battery has fixed it completely.
Test disabling "Google Services", "Google Play" and "Get More" in accessibility settings. Also test disabling temporarly the Google Account "Search for threaths on the mobile" feature. I was having quite fast battery drain until I did this. It nearly takes twice as long time for each percent to go down. As for your sudden drop check if you got apps that could interfere. Apps that can modify the battery stats.
Btw I had same sudden drop of 5, 10 and even once 30% when screen was off. I thought it was the battery and it was like that for some months until I uninstalled official Facebook app. Now I dont know if the Facebook app was the reason or only reason but after that it has worked flawless for months and continues to.
I tried everything and the results are the same ?.
I think my battery is damaged. Right now my device is plugged to the charger. After 20 minutes of being connected, my device shows only 7%