Related
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
Seems like whenever I install a custom kernel that is OC 'd, any launcher force closes after sleep... any ideas?
cuban88 said:
Seems like whenever I install a custom kernel that is OC 'd, any launcher force closes after sleep... any ideas?
Click to expand...
Click to collapse
Never seen this myself. I run at 1.4GHz and have tried all of the custom launchers with none of them doing this. Also, can report the same for my wife's phone.
Yea it lags a lot.. then says wait or force close .. could it be a set CPU setting? ?
cuban88 said:
Yea it lags a lot.. then says wait or force close .. could it be a set CPU setting? ?
Click to expand...
Click to collapse
Hmm...What is your CPU set at? I have seen this when I boot occasionally but never when waking from sleep.
Netarchy / 1300-800 on demand.
Screen off 1000-800 on demand.
Anything under 800 makes it worse..
Clean flash every time. Wipe>Rom > Kernel
cuban88 said:
Netarchy / 1300-800 on demand.
Screen off 1000-800 on demand.
Anything under 800 makes it worse..
Clean flash every time. Wipe>Rom > Kernel
Click to expand...
Click to collapse
Have you tried not using any profiles? I run 1400/100 with Netarchy's 1.2.4 CFS and the ondemand governor (lately I've been trying conservative just to see what kind of life I get out of that but I'll probably wind up using ondemand again). Also, which launcher are you using?
ADW.
I have not tried to run 100-1400 w/o profiles .. I will try this for 24 hours or so and leave feedback for anyone else out there with this issue ..
Are you saying that battery life is 12+ without profiles?
I have been using CM nightlys with netarchy 1.4 kernel at 1300-800 on demand and profile set to 1000-800 on demand (with the force close problems) and have been averaging 8-10 hours heavy use and 12-14 moderately .. how about yourself?
(I just got a random force close for ADW as I type.... I'm starting to think I should uninstall it and reinstall)
cuban88 said:
ADW.
I have not tried to run 100-1400 w/o profiles .. I will try this for 24 hours or so and leave feedback for anyone else out there with this issue ..
Are you saying that battery life is 12+ without profiles?
I have been using CM nightlys with netarchy 1.4 kernel at 1300-800 on demand and profile set to 1000-800 on demand (with the force close problems) and have been averaging 8-10 hours heavy use and 12-14 moderately .. how about yourself?
(I just got a random force close for ADW as I type.... I'm starting to think I should uninstall it and reinstall)
Click to expand...
Click to collapse
Personally, I've never been a fan of ADW always or ADW ex...always been a LPP man to be honest. I get between 14-16 hours of moderately heavy use (a few texts, a lot of XDA browsing, Engadget reading, and email, a few phonecalls, and almost always on WiFi and sometimes a few flashes as well). I have been on RC1 since it was released also.
Waw that's good .. I will try 100-1400 w/o profiles and get back to you and post results
I'm getting the same issue with the stock launcher running Modaco R11 and Netarchy 1.2.4 & today on 1.2.5.
I'm running profiles:
Screen off 400 powersave
Battery 1300/100 ondemand
I'll run no profiles 1300/100 on demand for 24 hrs and report back if issue is still present.
I always get past one day. No profiles, OC.
You should try http://www.appbrain.com/app/screen-filter/com.haxor if you want some more battery life. Works very well Only complaint is that when you have it on and theres sunlight reflecting on the screen its going to be difficult to see whats happening on the screen, but you can always toggle it off via notification bar.
So far so good without profiles being set.. moderate use(email, maps, phone calls). I'm going on 4 hours and I'm at 87% without any force closes ..
Within 4 hrs, plenty of stock launcher FC's for me running previously posted setup (no profiles)
Sent from my Nexus S using XDA App
cadguy said:
Within 4 hrs, plenty of stock launcher FC's for me running previously posted setup (no profiles)
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
If you're getting force closes of the stock launcher then something else is causing it to force close. A lot of people seem to be having issues with MoDaCo, my wife included. Might try a different ROM. I'm actually starting to really like stock 2.3.3 or GingerCollab.
zephiK said:
I always get past one day. No profiles, OC.
You should try http://www.appbrain.com/app/screen-filter/com.haxor if you want some more battery life. Works very well Only complaint is that when you have it on and theres sunlight reflecting on the screen its going to be difficult to see whats happening on the screen, but you can always toggle it off via notification bar.
Click to expand...
Click to collapse
This is off topic. There are settings is cm7 to do the same thing as this app. I use it along with the auto brightness to never need to manually change anything. It's under cm settings*display*automatic backlight*light levels.
Update
No problems with either ADW/Launcher Pro.
It has been 10 hours; automatic backlight, internet, email, phone calls. I'd call this moderate use (no games, lots of work relates online searches and maps use). Battery life is currently at 65%.
What I did....
Wiped>Flashed CM nightly#7 / GAPPS>reboot/setup>recovery> flashed Netarchy 1.4> reboot
Not one FC. Thanks Kenvan19 for the no profile suggestion. I was used to using profiles on my N1, guess it isn't needed on NS!
cuban88 said:
No problems with either ADW/Launcher Pro.
It has been 10 hours; automatic backlight, internet, email, phone calls. I'd call this moderate use (no games, lots of work relates online searches and maps use). Battery life is currently at 65%.
What I did....
Wiped>Flashed CM nightly#7 / GAPPS>reboot/setup>recovery> flashed Netarchy 1.4> reboot
Not one FC. Thanks Kenvan19 for the no profile suggestion. I was used to using profiles on my N1, guess it isn't needed on NS!
Click to expand...
Click to collapse
No problem man! Glad you got it figured out
So my brothers and I all experience this on our Sensations since beginning to use ARHD in late November.
Ranging anywhere from once a day to once a week, we will get this issue where our phone goes into a lock state, but will not exit. It doesn't matter what battery level the phone is at. The phone is quite clearly on, but the screen won't wake, no buttons will respond. The only solution is to remove the battery and reboot.
Anyone run into this as well?
Does it seem to happen at a certain time? After opening a certain app?
Does sound odd though.
The only certainty I can say is that it happens when no applications are open and the screen goes into lock mode. It also happens regardless of the launcher being used (I use FX, my brother uses HTC Rosie, the other uses Go).
gotpriest said:
So my brothers and I all experience this on our Sensations since beginning to use ARHD in late November.
Ranging anywhere from once a day to once a week, we will get this issue where our phone goes into a lock state, but will not exit. It doesn't matter what battery level the phone is at. The phone is quite clearly on, but the screen won't wake, no buttons will respond. The only solution is to remove the battery and reboot.
Anyone run into this as well?
Click to expand...
Click to collapse
+1 I have this issue too...I lowered my overclock and it's been working fine since
Sent From My HTC Sensation 4G
I assume that is performed through SetCPU? Or Daemon.
In Daemon, there's only four options, Sleep and Wake Max, Sleep and Wake Min - how did you fix yours?
Anyone offer a tip on this?
I don't have SetCPU on my phone (looks like it was replaced?)
Don't want to bork my phone, just wondering how to dial down the overclock slightly to prevent this hard crash.
Thanks
ARHD has Daemon Tools I think, with this you can reduce your overclock.
However my suggestion would be to increase the Maximum sleep CPU speed. [Sleep Max]
I can't remember but I think be default it is at ~440MHz, increase it by around 600MHz and see if that fixes the problem. If so you can reduce it gradually to save battery, stopping if the problem redevelops.
Thankee very much!
I have a similar issue with ARHD 3.6.11, but it happens only if I use the camera app. It may or may not be immediately on taking pictures, but seems to happen only when camera app is in memory. I have not changed any undervolting or overclocking settings.
Any ideas?
tk_xda said:
I have a similar issue with ARHD 3.6.11, but it happens only if I use the camera app. It may or may not be immediately on taking pictures, but seems to happen only when camera app is in memory. I have not changed any undervolting or overclocking settings.
Any ideas?
Click to expand...
Click to collapse
If it happens when you press the power button to turn the screen off while you are using the camera app, it is a known problem (of faux's kernel, that comes out of the box for ARHD).
To solve you have to flash Bricked kernel. Or stay on faux and live with that.
Grandelama said:
If it happens when you press the power button to turn the screen off while you are using the camera app, it is a known problem (of faux's kernel, that comes out of the box for ARHD).
To solve you have to flash Bricked kernel. Or stay on faux and live with that.
Click to expand...
Click to collapse
Does this particular known issue apply if the screen turns off on its own due to inactivity time? What about if camera app is in background?
Does faux kernal need a camera fix similar to the one for bricked?
guys...my phone sometimes freezes on the lockscreen....and I have to pull out the battery...the problem is that this happens with all roms, sense or not based....
what's going on?!
You may get more help if you provide a little more info, ie:
-Are you using a specific 3rd party launcher with roms?
-Are you using a custom kernel, and if so what are your settings?
-Have you tried running in safe mode to rule out 3rd party apps?
-Did this problem begin after anything in particular you can think of?
-etc....
Maybe too low CPU values?
Undervolt can cause this as well.
It happened to me while using APEX on ARHD.
But indeed more info is needed.
this started a week ago...with miui official/faux kernel and now with aokp b38/tamcore kernel....I know tamcore kernel is undervolted, and don't know nothing about faux's one...
I use nova launcher, setcpu is set at 384/1188 and I have a profile screen-off at 192/432...
uh, forgot, I use SIO scheduler...I set it with no frills and uninstalled it after, to have just one cpu control app (setcpu)...
this morning my alarm didn't ring! then I had to pull out the battery because it was freezed...luckily I woke up by myself this morning XD
I recommend to use a higher off-screen value (384 MHz) as a first try. See how it reacts and also use an app to check the current voltage (like system tuner / st pro).
If this does not helps then start isolating apps.
I have NOOP sched and 384-432 Off-screen and had no issues far, but I remember that with 192 Mhz a while ago the screen did not wake up a few times (on ARHD 6.3.x).
I updated to b39, nothing now....if it freezes i'll try setting a higher minfreq...
thank you all! thx+1
Hi All,
A few weeks ago I installed Cyanogenmod 10.1 20130630 nightly on my Everest Xoom and have been very happy with the Jellybean features and performance.
The one problem I have had though is heavy battery drain. Before on ICS stock I would charge the Xoom and get around a week standby with light use between charges (I only use the Xoom no more than 20minutes a day really). Since installing Cyanogenmod, I cant get more than 2 days standby. I have set WiFi during sleep to never and I have tried charging it fully then not touching it besides a screen unlock for test purposes every day and cant get more than 2 days. Any suggestions how I can get more standby time, or a different ROM more suited to my occasional use?
Thanks!
glenb83 said:
Hi All,
A few weeks ago I installed Cyanogenmod 10.1 20130630 nightly on my Everest Xoom and have been very happy with the Jellybean features and performance.
The one problem I have had though is heavy battery drain. Before on ICS stock I would charge the Xoom and get around a week standby with light use between charges (I only use the Xoom no more than 20minutes a day really). Since installing Cyanogenmod, I cant get more than 2 days standby. I have set WiFi during sleep to never and I have tried charging it fully then not touching it besides a screen unlock for test purposes every day and cant get more than 2 days. Any suggestions how I can get more standby time, or a different ROM more suited to my occasional use?
Thanks!
Click to expand...
Click to collapse
Have you checked your Battery Settings (In Settings) to see if it is a rogue app(s)? If it is, you can either uninstall that app or use Greenify (http)://forum.xda-developers.com/showthread.php?t=2155737 to hibernate it and prevent it from wasting even more battery life. If you can't find anything abnormal in Battery Settings, install Wakelock Detector (http)://forum.xda-developers.com/showthread.php?t=2179651 and check the app the next day. Anything draining the most battery life in standby should be on the top of the list. You can then uninstall that app or Greenify it as I mentioned before. Tip: If you install Greenify, check in the settings if auto-hibernation is turned on and if it isn't turn it on. In the widgets drawer there is a Greenify widget that you can tap to hibernate now if it is on your homescreen, if you want to hibernate apps immediately.
You can also intall SetCpu (http)://forum.xda-developers.com/showthread.php?t=505419 to save battery life. Go to the profiles tab, tap add profile, change the profile to Power Off, Max to 456000, Min to 216000, and change the scaling to powersave or conservative if you don't have powersave.