Related
Hey guys,
N00b here.
I've read the n00b guide and also searched around in the forum. I did find a thread similar to mine however I couldn't really get any useful info out of it and maybe since then new tools are available to help me track my problem, so I post my question.
So... on to it...
My Nexus S is suddenly having high keep-awake times. About phone tells me a battery usage of 32% android system, followed by 21% Display. Android system has a keep awake time of 3h 51m and a CPU total of 7m 52s. All this over the course of 19 hours. I don't have a screenshot with me but it's clear that the phone is awake a lot when the screen is off.
Automatic updates are off.
Some days ago everything was fine. My google acount is only synching contacts and calendar and even that is turned off when I'm not at home. Even so, I saw a high usage of the keep-awake bar even when the screen was off.
I've installed some weather widgets and battery info widgets and the update cycles of weather applications are around 45 mins so I wouldn't see a reason for such a high period of keep-awake cycles.
Anyway, each phone is a phone, is there an application that can tell you what is keeping the phone awake ? I have installed Watchdog lite but it doesn't show anything abnormal. I've installed Spare Parts Plus but it can't show me the battery usage history because apparently stock 2.3.4 Gingerbread doesn't support it.
So now I'm stick with trying to disabled notifications on one app, remove its widget and see if it helps. If it doesn't.. go to the next. This is quite tedious work really.
Still the battery life is ok I guess... 50% after 19 hours however I haven't played around with it much but I would be happier to have a low keep-awake cycle for the Android System like I had some days ago.. makes me feel like everything is fine
Thanks for any hints guys!
Having the same issue as well.. I have my widgets and such to only check every 4-6 hours, but the awake time in the battery stats is nearly on all the time.
Keep awake time is 4 hours and 22 min, out of 12 hours of battery. I'm left with 42 % battery with only 1 hr 15 min on screen time (texts and such, no games).
Hmmm a memory drain of 60% in 1 hour is quite a bit heavy. I would suggest you to download Watchdog lite from the app store and use it's real time CPU analyzer to try and see what's consuming the most.
Once I had weatherbug going rogue. But then it showed up in the battery usage list with a high CPU usage and clicking on the item I could see a high awake time so I uninstalled it.
At the moment I've removed some of my widgets and so far it seems to be OK. However tonight I had some weird awake times again. I uninstalled Battery Info widget from the phone and I'll see if it all goes well tonight. Then I'll start to activate the other widgets I had deactivated before to see what happens.
Also I downloaded aCatLog from the app store. Pretty interesting tool... you can see what's going on in the logs. I see a few Java exceptions every now and then.. never a good sign as they might not be handled properly by the application code that threw them. I see evernote synch problems, a data traffic counter throwing exceptions and K-9 to have problems with idle connection reset by peer. And I often see the garbage collector working. But I assume all this is normal. Switching to the event log it's too much information to absorve. Nevertheless I haven't seen in any of those logs an explicit request or grant of a system wake lock.
mindwalkr said:
My Nexus S is suddenly having high keep-awake times.
Click to expand...
Click to collapse
Did you recently enable Latitude, by any chance?
Try top -m 5 -n 1 in terminal
fallenguru said:
Did you recently enable Latitude, by any chance?
Click to expand...
Click to collapse
No Latitude enabled
snandlal said:
Try top -m 5 -n 1 in terminal
Click to expand...
Click to collapse
Do I need to download Terminal Emulator from the market to do this ? Or do I need to download the Android SDK and connect to the device via USB ? I need to check out to do this, never done it before and this is my first android phone.. only a week old
Again this morning my awake time was on for quite a bit (I guess 1 hour). I got an extract of the main log...
Some things are curious, the following occurs more or less each half hour. I am signed out of gtalk why was the service trying to keep alive ?
06-08 06:10:03.656 W/GTalkService( 189): [GTalkConnection.18] doConnect: caught XMPPError connecting to mtalk.google.com:5228.: (502)
06-08 06:10:03.656 W/GTalkService( 189): -- caused by: java.net.SocketTimeoutException: Connection timed out
06-08 06:10:03.660 D/GTalkService( 189): [GTalkConnection.18] connectionClosed: connId=0, error=CONNECTION FAILED
This is also giving me trouble, I might uninstall my Traffic Counter app
06-08 06:42:30.710 W/System.err( 4015): java.io.FileNotFoundException: /data/data/com.carl.trafficcounter/app_pref_bytes_last/0_0_bytes_last (No such file or directory)
Evernote seems to have some issues as well sometimes
06-08 06:44:36.371 I/com.evernote.android.edam.TAndroidHttpClient( 5320): 25: Response received in: 126718ms
06-08 06:44:36.398 E/com.evernote.client.SyncService( 5320): Sync failed
06-08 06:44:36.398 E/com.evernote.client.SyncService( 5320): org.apache.thrift.transport.TTransportException: java.net.UnknownHostException: www.evernote.com
And that's all I could see. Everything else seems to be garbage collection WiFi activities and what not..
It seems that I've narrowed down Go Weather as what's making my Android System stay awake. I couldn't see anything really useful on logcat about this but empiric observations seem to confirm it.
If I remove the Go Weather widget and turn off it's background updates (hourly), then restart the phone... I see the Android System incrementing some 3-4 mins keep awake time per hour. If I set the widget again and turn on Go Weather's background updates, after an hour the Android System keep awake time goes up like 15-20 mins or so. If at this point I remove the Go Weather widget and turn off it's background updates, the Android System keep awake will still go up at the same rate as if the Widget was there. If I restart the phone without the widget, then the Android System keep awake seems to increase back to regular 3-4 mins per hour.
The funny thing is that according to Permission Dog, Go Weather doesn't even use the WAKE permission so I would rule it out as what was keeping Android System awake.
Android System was driving me crazy too. I figured out that when my WiFi was enabled, it would continually keep the phone awake when the screen was off. So I just toggle the wifi off when I'm not using it, and android system behaves now.
I'm curious as to what changed though, because when I was using stock 2.3.4 and CM7.0.3 I would leave wifi on all day, and android system didn't cause any battery issues.
* sorry for my English.
Okay guys, I know many of us Android fanboys are obsessed of Dozing and Greenifying and Napping or whatever that keeps their phone deepsleep. I used to be one of them, but now I'm too old and following those guides from Amplify, Tasker, Greenify etc. or whatever it is, has turned out to be too complicated and ridiculous for me. A few days ago I took some time to investigate about doze and decided to mess up with the phone once more.
At first, I made my own doze settings as below:
randomseasons said:
Hi all, after hours and hours of reading (English is not my native language) and testing, I think I have set up a pretty good settings for Doze.
I'm not saying that other profiles are bad, but the matter is that some profiles were set up very early while all of us hadn't understood Doze thoroughly yet
Before we start, let's talk about what I'm aiming for. Basically, doze profiles are aiming for "decrease the time it takes for the phone to sleep, and increase the duration between awake checkups". But is that what we should look forward to? For me, it's reasonable to have my phone sleep soon, however I won't want my phone dead all the time, so I'm heading to "After I leave my phone, wait a short enough time then sleep, but don't let the phone sleep for too long, instead wake it soon enough while decrease the duration of the wakeups. Then after I leave it for a long enough time which really means I'm not using my phone, multiply the time between wakeups."
This way compared to other profiles, for daily use my phone stays more ready (shorter sleeping periods), but it also works less (shorter awake duration), and when I don't use my phone, it will actually catch up with the long sleeping states soon (higher multiply factor).
Here are my settings with that motto in mind:
*** all the parameters are in seconds ***
A) ------------------------------------------
Inactive Timeout - inactive_to: 180
Sensing Timeout - sensing_to: 0
Locating Timeout - locating_to: 0
Location Accuracy - location_accuracy: 50
- This one is easy. I want my phone to sleep right away after 3 minutes of being inactive (screen off), ignoring any motion. You can change the inactive timeout to whatever number that suits you. As we set the location timeout to 0, the Location Accuracy doesn't matter anymore, however I increase it to 50 although just because... I can do it , it's a safe number.
------------------------------------------------
B)-----------------------------------------------
Motion Inactive Timeout - motion_inactive_to: 60
- This number means if the phone checks and finds any motion, it will wait 60 seconds to check for any SIGNIFICANT (strong motion, different from light motion as in the sensing period) motion again. As we don't check for any motion in the beginning, this parameter is useless, however I still set it at 60 seconds, imagine for some particular reason the doze does check for motion (again, this won't happen if the app works as it's supposed to), then I don't want my phone to stay as long as 600 seconds (the default) value, and I don't want my phone to checks too often either, hence I want it to check again after one minute.
Idle After Inactive Timeout - idle_after_inactive_to: 0
- I want my phone to sleep right away after the inactive timeout elapses, I don't want it to wait to check for significant motion, so zero for this.
----------------------------------------------
C) -----------------------------------------------
Idle Pending Timeout - idle_pending_to: 15 seconds.
Max Idle Pending Timeout - max_idle_pending_to: 120 seconds.
Idle Pending Factor - idle_pending_factor: 2.
- This means: when the phone first wakes up (the criteria of when it will happen is in part D below), it will be kept awake for 15 seconds. The second times it will wake up, it will multiply by 2, which is 30 seconds, and so on. The maximum duration of wakeup is 120 seconds.
For me, I want to wake my phone soon enough (see in part D) and decrease the time of the phone being awake. I think 15 seconds for the first time is long enough. You can change it as you want, though :silly:
-----------------------------------------------
D) -----------------------------------------------
Idle Timeout - idle_to: 1200s (default is 3600)
Max Idle Timeout - max_idle_to: 21600s
Idle Factor - idle_factor: 2.
- After 1200s (20 mins), my phone will wake and check for 15 seconds (see part C), then the next time it wakes, it will need 40 minutes before waking up. The maximum time is basically as long as we want so 21600s is okay.
- I'm thinking to change this part to 900s or 720s and idle factor 3, which means that the phone will wake up sooner, at <=15 minutes mark, but after that, the sleeping duration will increase 3 times faster.
------------------------------------------
E) -----------------------------------------------
Min Time to Alarm - min_time_to_alarm: 3600.
This is the minimum time we will allow until the next upcoming alarm for us to actually go in to idle mode.
I don't get what this sentence says, my English sometimes sucks, but I guess it means if the next alarm is within the set number then the phone won't try to go into idle mode. I leave it default.
Max Temp App Whitelist Duration - max_temp_app_whitelist_duration: 20s
Max amount of time to temporarily whitelist an app when it receives a high tickle.
- Set this number whatever you feel like, for me I think 20s is enough.
MMS Temp App Whitelist Duration - mms_temp_app_whitelist_duration: 0
Amount of time we would like to whitelist an app that is receiving an MMS.
- Set this number whatever you feel like, I live in Vietnam, I don't ever use MMS at all so 0 for it.
SMS Temp App Whitelist Duration - sms_temp_app_whitelist_duration: 15s
Amount of time we would like to whitelist an app that is receiving an SMS.
- Set this number whatever you feel like, for me I think 15s is enough.
----------------------------------------------------------------------
BRIEF TEST:
1. Turned the screen off, sent an email to myself within 3 minutes (inactive timeout duration), the phone notified right away, no delay, 7 tries, worked every time.
2. Turned the screen off, waited at least 3 minutes, sent an email to myself, the phone didn't notify right away. If I turned the screen on, of course the email came right away. Out of 8 tries, 6 times the phone notified me between 15min - 20min mark, which followed closely to my rule. 2 times it notified me between 5 - 10 minutes. I think it was because some app woke my phone unexpectedly.
After 2 days, the observation showed me that my Doze Setting has been working decently, I'm quite satisfied. I will keep testing though :silly::victory:
Sorry for my bad English.
Edited: English and grammar.
Click to expand...
Click to collapse
As some guy pointed out, some settings don't act in the way I thought they do, anyway I was having a fantastic result with these settings. My phone was deepsleeping often enough, it woke up after every short time, but each time was short, exactly my purpose.
Then a few days ago, I installed Greenify with xposed, and as it turned out, it's working TOO GOOD. , no matter how many apps I run, Facebook, Messenger, Maps, 8tracks, internet-based apps, clouds etc... (I only Greenify very few of of them), the phone changes its state to idle too strictly and too perfectly and I want it to be. For example, my current doze records were like:
8:00 - turned off my phone
8:04 - 8:19: doze // 14 mins
8:19 - 8:20: awake // 20s
8:20 - 9:00: doze // 40 mins
9:00 - 9:01: doze // 1 mins.
9:01 - 13:00: doze / 4 hours.
etc...
If you have read my doze configs, you can see that my phone now nearly perfect as my settings, I set it to doze after 3 minutes, then after 15 mins wake up 15 secs, then doze for 45 minutes.... etc... without any big difference. The weird thing is that music apps still works perfectly for me. :angel:
Now with Zenfone 2, my phone only drains 3% through the night, with all wifi gps 3G on, and I can still receive notifications ! Zenfone 2 users please come and praise me lol
It's been a long time since I last visited xda so I don't know if anybody has tried this, it would be a shame if I'm sharing what everyone already knew, but if not I guess this post would be very useful for many people.
Cheers, for a better and more simpler Android world ! :silly:
randomseasons said:
* sorry for my English.
Okay guys, I know many of us Android fanboys are obsessed of Dozing and Greenifying and Napping or whatever that keeps their phone deepsleep. I used to be one of them, but now I'm too old and following those guides from Amplify, Tasker, Greenify etc. or whatever it is, has turned out to be too complicated and ridiculous for me. A few days ago I took some time to investigate about doze and decided to mess up with the phone once more.
At first, I made my own doze settings as below:
As some guy pointed out, some settings don't act in the way I thought they do, anyway I was having a fantastic result with these settings. My phone was deepsleeping often enough, it woke up after every short time, but each time was short, exactly my purpose.
Then a few days ago, I installed Greenify with xposed, and as it turned out, it's working TOO GOOD. , no matter how many apps I run, Facebook, Messenger, Maps, 8tracks, internet-based apps, clouds etc... (I only Greenify very few of of them), the phone changes its state to idle too strictly and too perfectly and I want it to be. For example, my current doze records were like:
8:00 - turned off my phone
8:04 - 8:19: doze // 14 mins
8:19 - 8:20: awake // 20s
8:20 - 9:00: doze // 40 mins
9:00 - 9:01: doze // 1 mins.
9:01 - 13:00: doze / 4 hours.
etc...
If you have read my doze configs, you can see that my phone now nearly perfect as my settings, I set it to doze after 3 minutes, then after 15 mins wake up 15 secs, then doze for 45 minutes.... etc... without any big difference. The weird thing is that music apps still works perfectly for me. :angel:
Now with Zenfone 2, my phone only drains 3% through the night, with all wifi gps 3G on, and I can still receive notifications ! Zenfone 2 users please come and praise me lol
It's been a long time since I last visited xda so I don't know if anybody has tried this, it would be a shame if I'm sharing what everyone already knew, but if not I guess this post would be very useful for many people.
Cheers, for a better and more simpler Android world ! :silly:
Click to expand...
Click to collapse
Do you you Aggressive Doze and Disable Motion Sensing at all? Naptime has these settings and I'm not sure whether to put them on or not!
Hi guys,
I'm using the S3 a lot for tracking my running and that's going pretty good. Really good actually. Satellites are locked super fast, in 4 or 5 seconds and tracking is accurate.
Today I tried the cycling activity. Unfortunately it does not track kms. Time and heart rate are logged but no distance.
I tried multiple times, satellite is locked, the program is running, time is ticking.
Does anybody have any experience, do I forget to do something?
Nobody tried cycling mode?
Not intentionally, a couple of times driving the S3 has decided I am cycling and offers encouragement.
If you start it manually I recall it has ALL the distance details, including a summary map. I don't think you get that if it senses a ride and starts automatically.
Sent from my SAMSUNG-SM-G935A using Tapatalk
Well, I started it as an activity, so manually.
I'll do it again in a bit, see what happens.
With auto detecting it doesn't seem to use the GPS, like running is detected fine but no track logging.
Update : 1 just cycled 200 meters and it tracked 170. First 30 locking the satellites.
So... Why it didn't do anything yesterday, trying a bunch of times, booting in between, beats me. Maybe it's today's health update?
I'm having the same problem, walking tracks distance covered, but Cycling doesn't. Calories and time were tracked, but not distance. Really disappointing.
I use my Gear S3 to track my cycling activity all the time.
I go to the S Health app on the watch, set activity type to cycling then set a "target" based on how far I plan to cycle.
Whilst in the setup part of the watch app there are selectable options for "location" (make sure you are selecting this or it won't track where you are, which may be why you're not getting distance?)
I also select "auto pause" to pause tracking if I stop cycling. I then scroll up to the top and hit Go.
After a 3 second countdown it starts tracking my ride.
If I stop cycling briefly (at red traffic lights etc) the watch automatically pauses tracking. When I start riding again it automatically starts tracking again.
At the end of the ride I simply choose finish on the watch and confirm I wan't to finish.
It then syncs all manner of information with my phones S Health app including:
A map of the ride showing my route
Total distance (which is always with a few metres of my Cateye bike computer)
Total duration (e.g. the total time from starting the watch to hitting finish, including time the watch paused due to me being stationary)
Workout duration (the time I was actually moving)
Average & maximum speed
Average pace & maximum pace
Lowest & highest elevation
Total ascent & decent
Average & maximum heart rate
Workout calories & total calories
Weather
There is also a Selectable option to show the whole ride on a graph broken down by up to 2 options from speed/heart rate/elevation
When I used to rely on the Gear S3 workout detection to pickup my cycling, the information available at the end was very limited.
It works brilliantly when I set it manually before my ride (and only takes a few seconds too)
Do you have your phone with you while you cycle?
As I understand when your watch is connected to phone it uses phone for location.
I had a same problem and after I turned location on phone Off and than back to On problem disappeared.
Not sure if this is your problem but it is worth a try
Since I got my Gear S3 last year I use it when I go hiking to track my workout. My chosen workout type is set to default to Hiking and all I usually did was tap on the green start arrow at the start of my hike and it would track it and auto-pause when I stopped for a rest. At teh end of teh hike I then had to select to end the recording. This was working fine but for past 3 weeks when ever I try it I find that it only recorded the first part of a hike (say 30- 50 mins) and then stopped. I'm assuming it's giving up when I pause for a rest but cannot be sure. It's most frustrating as it used to work well but now I can't trust it at all. Any suggestions?
MapMy Run also auto-pauses and will not resume tracking
Update: My problem as described above with SHealth has continued. Yesterday I downloaded and installed the new MapMyRun app for the Gear S3 as just released by Under Armour. Today I went on a hike in the mountains for 3 hours or so and decided to try out MapMy Run. I set it for hiking mode, started it up, and for first couple of hours it was working great. It looked really good (nice clear sharp display with lots of information) and I was well pleased with it, until it just stopped tracking after around 2 hours 20 mins. The display just stopped at the same time and distance travelled etc and stopped updating.
I tried pressing the Back button and the voice announcement offered to Pause tracking. As I did NOT want to pause tracking I clicked the Back button again, and it said it had resumed, but it stuck at same time and distance for the rest of my hike. So it seems that my problem as reported above with SHealth is somehow affecting all exercise tracking on my S3. It appears that at some point it just auto-pauses itself and will not resume again. This is very frustrating as tracking my hikes and other workouts was one of the main reasons why I bought this smartwatch but it is now just totally unreliable for this. Soooo frustrating!
If anyone can suggest any fixes I should try I'd really appreciate it.
guitareth said:
Update: My problem as described above with SHealth has continued. Yesterday I downloaded and installed the new MapMyRun app for the Gear S3 as just released by Under Armour. Today I went on a hike in the mountains for 3 hours or so and decided to try out MapMy Run. I set it for hiking mode, started it up, and for first couple of hours it was working great. It looked really good (nice clear sharp display with lots of information) and I was well pleased with it, until it just stopped tracking after around 2 hours 20 mins. The display just stopped at the same time and distance travelled etc and stopped updating.
I tried pressing the Back button and the voice announcement offered to Pause tracking. As I did NOT want to pause tracking I clicked the Back button again, and it said it had resumed, but it stuck at same time and distance for the rest of my hike. So it seems that my problem as reported above with SHealth is somehow affecting all exercise tracking on my S3. It appears that at some point it just auto-pauses itself and will not resume again. This is very frustrating as tracking my hikes and other workouts was one of the main reasons why I bought this smartwatch but it is now just totally unreliable for this. Soooo frustrating!
If anyone can suggest any fixes I should try I'd really appreciate it.
Click to expand...
Click to collapse
Just to update on my own issues with MapMy Run app on the S3 locking up part way through a workout. Since installing latest version 1.1.3 of MapMy Run I tested the app on a 6 hours + hike on Friday and it worked great without locking up at all. It automatically paused and resumed whenever I stopped for a rest. I will test it again this coming Friday before being overly confident, but so far so good!
A few days ago when I was doing absolutely nothing all day, I got about 12 minutes somehow on the 30 minute "moderate to high intensity" fitness ring but i've no idea how as every day otherwise, including today, it stays at 0.
I just went for a 45 minute run, keeping my heart rate in the aerobic and anaerobic zones - on the Huawei Health app on the phone (which oddly displays a slightly different number of steps) the ring is completed and says 41 minutes. On my watch.... still 0.
The app is connected to the watch, which is listed under "Me -> My Devices"
Any idea what's going on?
Restarted the watch, no difference.
Did a "clear data" on the app on the watch. Now the green ring works but the blue one (steps) doesn't (it stopped at 292 for some reason) - meanwhile on the phone, which has clearly synced with the watch as it has my exercise record from my 5 mile walk, it says I've done 10000 steps but 0 minutes.
Guess I'll just ignore the rings then if they're buggy, which is a shame as they're a nice feature. Alternatively might look into selling this thing and going for a Galaxy watch.