Hi, I'm a Vega owner but we don't have kernel source and given that the Gtab is pretty similar hardware I like to ask a question of you:
Does AlarmManager work while your device is sleeping?
The Android AlarmManager is used by most services but the most obvious and observable is the clock alarm. On any android phone I've used, if the device is sleeping then the AlarmManager will wake it up to perform the task at hand (E.G. switch on the screen and play an alarm, grab some RSS, pull tweets, etc) but from what I've seen the Vega goes straight into a kind of suspend where _nothing_ happens until you press the power button at which point the alarm fires even if it's well overdue. I'm wondering if this is correctable once we get kernel source.
So does having an alarm fire wake up your GTab device? If not are the any custom kernels that have fixed this for you?
Moved to general
SilentMobius said:
Hi, I'm a Vega owner but we don't have kernel source and given that the Gtab is pretty similar hardware I like to ask a question of you:
Does AlarmManager work while your device is sleeping?
The Android AlarmManager is used by most services but the most obvious and observable is the clock alarm. On any android phone I've used, if the device is sleeping then the AlarmManager will wake it up to perform the task at hand (E.G. switch on the screen and play an alarm, grab some RSS, pull tweets, etc) but from what I've seen the Vega goes straight into a kind of suspend where _nothing_ happens until you press the power button at which point the alarm fires even if it's well overdue. I'm wondering if this is correctable once we get kernel source.
So does having an alarm fire wake up your GTab device? If not are the any custom kernels that have fixed this for you?
Click to expand...
Click to collapse
I haven't really noticed in particular, but I can tell you that the G Tablet does plenty of resume/re-suspending when it's suspended, switching between L0/L1/L2 suspend modes, and so on. You can see all that activity from the dmesg output after an extended suspend. I've never tried the clock alarm, so not sure specifically if that can interrupt suspend state, but I wouldn't be shocked.
There is a ton of stuff in the Tegra2 kernel code regarding suspend/resume, so it's definitely possible that when you get the source code for the Vega kernel you can polish up the way it handles suspend/resume. We've had good luck merging up more recent changes from NVidia's mainline to fix some of the original kernel bugs regarding suspend/resume behavior (specifically low voltage states sticking the CPU at low clock speed after prolonged suspend).
Thanks rcgabriel, my worry is that people are currently blaming the lack of wifi during sleep on the failure of things like twitter/rss/etc not updating while the screen is off when in actual fact the AlarmManager events aren't even waking up the unit at all.
Could someone with a Gtab perhaps test if the alarm wakes up their device while it's asleep when they have a spare moment?
SilentMobius said:
Thanks rcgabriel, my worry is that people are currently blaming the lack of wifi during sleep on the failure of things like twitter/rss/etc not updating while the screen is off when in actual fact the AlarmManager events aren't even waking up the unit at all.
Could someone with a Gtab perhaps test if the alarm wakes up their device while it's asleep when they have a spare moment?
Click to expand...
Click to collapse
Hi,
I didn't know you could even do that (no Android phone here) .
My Gtab is stock TNT 3452, and I:
- Set an alarm for 11:25AM (it was 11:21AM)
- Pressed power
- Selected Sleep
- Screen went black
- At 11:25AM, the tablet started buzzing - Screen came on with the time and two buttons, Snooze and Dismiss.
Pretty cool!
I haven't tried the above just letting the tablet go to sleep on its own though.
Also, I can set the alarm to sound, but how do you do those other things like checking RSS, etc.? Is that dependent on an app to do that?
Jim
I have tried Juice Defender to accomplish this. Juice allows me to set the interval at which the tablet should wake, turn on the wifi, allow things like email to be polled then return to sleep. So far I cannot say if it is working or not working.
Before Juice my phone would buzz to say I had email at say 3 am, but the Gtab wouldnt get it until I woke it up hours later. My assumption was that the wifi was turned off when the tablet entered sleep and didnt turn on until I pushed the power button.
Well, after fixing my wifi at home I can say that Juice will allow email polling after the tablet has gone to sleep. this morning when I woke my tab up there were a three emails that arrived at 3 to 5 am in the inbox.
bboyle said:
I have tried Juice Defender to accomplish this. Juice allows me to set the interval at which the tablet should wake, turn on the wifi, allow things like email to be polled then return to sleep. So far I cannot say if it is working or not working.
Before Juice my phone would buzz to say I had email at say 3 am, but the Gtab wouldnt get it until I woke it up hours later. My assumption was that the wifi was turned off when the tablet entered sleep and didnt turn on until I pushed the power button.
Well, after fixing my wifi at home I can say that Juice will allow email polling after the tablet has gone to sleep. this morning when I woke my tab up there were a three emails that arrived at 3 to 5 am in the inbox.
Click to expand...
Click to collapse
i have juice defender but it seems it still cannot prevent wifi going to sleep even though i trigger on certain application and data transmission
Greetings,
I have set my Gear S2 to auto check my pulse every 10 Minutes. But sometimes it doesnt check for my pulse for 2 - 3 hours...
Is it dependent on something like if I move or something? Or is it a bug in the firmware?
Greetings
Robin
I know that if the watch doesn't get a good read on your pulse (too much movement, not sitting on wrist right, etc) it won't record the heart rate. At night while sleeping, I'll get pretty consistent readings for an hour or two, and then there will be like a 6hr gap. And on numerous occasions, I'll feel the watch vibrate slightly with no notifications or anything going off. I assume it's just error ed out on the read, and will try again later (or at the next scheduled interval)
* 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, I have an interesting issue with sleep tracking. S3 starts sleep tracking automatically. However after I wake up I usually sit down on the couch to have my cup of coffee and read news for an hour or so. I have noticed that my S3 detects this time as sleep and reports about it Is anybody having same experience? I know, this is not a big issue however...
r.
romualdp said:
Hi, I have an interesting issue with sleep tracking. S3 starts sleep tracking automatically. However after I wake up I usually sit down on the couch to have my cup of coffee and read news for an hour or so. I have noticed that my S3 detects this time as sleep and reports about it Is anybody having same experience? I know, this is not a big issue however...
r.
Click to expand...
Click to collapse
I had sort of the opposite experience. It apparently started automatically, but stopped when I got up at 5am for a, um, waste elimination event. I was back in bed within a minute or two, but didn't go right back to sleep. While I was laying there my watch displayed a notification with the number of hours slept (signaling the end of the sleep period, I guess).
This was my first night with the watch, though. Wondering if it needs to learn my patterns?
EDIT: So ... I have to modify my observations a bit. The number I got for sleep time was from the notification that appeared on the watch. When I went into the S Health app on my phone, though, it showed the correct duration, including periods of light vs. motionless sleeping. I've attached screen shots with each of the sleep periods highlighted.
So i just got my phone and set up my timer to wake me up for work. I don't like using an alarm because due to not having a set bed time(I work nights).
Before I went to bed I finished charging the phone to 100% and set the time for 8hr and 30 minutes and to not disturb. When the timer went off I looked at the phone was at 57%. I looked at the battery usage and it showed the clock had used over 25% of the battery.
I've never noticed this being a problem with other phones till this one. Is this normal?
I'm guessing the timer is preventing the phone from going into dose / sleep mode, or keeps waking it up regularly while it counts down
You can hold the home button to activate Google assistant and just say something like "Set an alarm for 7 hours", assistant will say "Done" and your alarm will go off in 7 hours
Try clearing it's data. Start over.
Also possible battery usage is being misreported as another app may be responsible. I've seen this happen occasionally.
Lsantana954 said:
So i just got my phone and set up my timer to wake me up for work. I don't like using an alarm because due to not having a set bed time(I work nights).
Before I went to bed I finished charging the phone to 100% and set the time for 8hr and 30 minutes and to not disturb. When the timer went off I looked at the phone was at 57%. I looked at the battery usage and it showed the clock had used over 25% of the battery.
I've never noticed this being a problem with other phones till this one. Is this normal?
Click to expand...
Click to collapse
Wait....you set a Timer or an Alarm? I don't think a timer would allow the phone to sleep but I wouldn't expect it to use that much batter power. Was it background or foreground usage?
I set a timer. If I read it correctly it was active usage