EDIT: According to garyd9, this is an Exynos issue and cannot be fixed. I believe him that this is an Exynos issue because it supports what I've seen, and he's a smart guy. I'm still holding out hope that there is some possible resolution in the future. Why else are we here if not to find ways to make our phones better, right? However, because of the nature of this issue, it's not going to be resolved by app settings, disabling apps, etc. If you don't see the lag yourself, it's because your phone isn't in deep sleep when you try to wake it.
Original Post:
Alright guys, some of you have probably noticed that this phone suffers from the wake lag that others (all Samsung?) have also suffered from.
Symptom: When you press the power or home button it takes 1-2 seconds before the screen turns on.
This DOES NOT happen when the phone is plugged in, likely because the problem is a delay getting the phone out of deep sleep. Deep sleep does not occur while the phone is plugged in.
Culprit: Anybody know? My wife's AT&T GS2 has this same problem and has with every ROM/Kernel combo I've tried (AOSP, AOKP). My Skyrocket has the issue on some of the more recent versions of Sky Jelly Bean, which I believe Sean said was a Kernel problem.
Fixes that don't work: This morning I tried the most popular suggestions:
Turn off Lock Screen Popup note
Lock Screen Ripple Effect
S-Voice home key
S-Voice Auto-start speaker
S-Voice wake up command
NONE OF THESE WORK!
So, let's band together and solve this thing. Do some tests and find something that works. Preferably, a solution that takes as little modding as possible.
Is this something that can only be solved by a customer kernel? If so, let's see if a dev is up to the task!
EDIT TO ADD: This seems to be an issue on all variations of this device. I'm searching their forums for an answer, but don't see one yet. I decided to post this here to get more eyeballs on the problem
More info from Entropy512:
Entropy512 said:
To be more detailed: It seems to be specific to how Samsung wires up the modem interfaces of Exynos devices. On Exynos4 devices, they're always hung off of HSIC (a variant of USB) buses. Since HSIC is based on USB, it has the same slow suspend/resume of USB. Almost all Exynos3 devices hung the modem off of a serial port if I recall correctly, and these devices could suspend/resume much faster. If you look at a resume sequence, there are huge time gaps, and after the first 200-300 msec, almost all resume activity is modem stuff.
The only solution, unless someone figures out a way to make the HSIC resume faster (I'm not messing with it, I have enough trouble getting it not to drop the bus randomly!!!!!!!), is to inhibit deep sleep with a wakelock - but this will be bad for battery life.
Click to expand...
Click to collapse
Jrockttu said:
Alright guys, some of you have probably noticed that this phone suffers from the wake lag that others (all Samsung?) have also suffered from.
Symptom: When you press the power or home button it takes 1-2 seconds before the screen turns on.
This DOES NOT happen when the phone is plugged in, likely because the problem is a delay getting the phone out of deep sleep. Deep sleep does not occur while the phone is plugged in.
Culprit: Anybody know? My wife's AT&T GS2 has this same problem and has with every ROM/Kernel combo I've tried (AOSP, AOKP). My Skyrocket has the issue on some of the more recent versions of Sky Jelly Bean, which I believe Sean said was a Kernel problem.
Fixes that don't work: This morning I tried the most popular suggestions:
Turn off Lock Screen Popup note
Lock Screen Ripple Effect
S-Voice home key
S-Voice Auto-start speaker
S-Voice wake up command
NONE OF THESE WORK!
So, let's band together and solve this thing. Do some tests and find something that works. Preferably, a solution that takes as little modding as possible.
Is this something that can only be solved by a customer kernel? If so, let's see if a dev is up to the task!
Click to expand...
Click to collapse
I'm not feeling major sleep lag on att , Sprints on the other hand was pretty bad with 2-3 sec delay
Simple soft locker from market... doesnt seem to effect battery. Try it out works great
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
u921333 said:
Simple soft locker from market... doesnt seem to effect battery. Try it out works great
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
The app creates a partial wakelock, so it will affect battery. A wakelock will keep the phone from going into deep sleep, which is what extends Android phone battery life. With such a large battery, it won't be as noticeable on this phone, but it still has substantial negative effects.
sling said:
I'm not feeling major sleep lag on att , Sprints on the other hand was pretty bad with 2-3 sec delay
Click to expand...
Click to collapse
I'm getting about 2 second lag on both mine and my wife's AT&T N2s. Mine is rooted, hers is not.
Jrockttu said:
Alright guys, some of you have probably noticed that this phone suffers from the wake lag that others (all Samsung?) have also suffered from.
Symptom: When you press the power or home button it takes 1-2 seconds before the screen turns on.
This DOES NOT happen when the phone is plugged in, likely because the problem is a delay getting the phone out of deep sleep. Deep sleep does not occur while the phone is plugged in.
Culprit: Anybody know? My wife's AT&T GS2 has this same problem and has with every ROM/Kernel combo I've tried (AOSP, AOKP). My Skyrocket has the issue on some of the more recent versions of Sky Jelly Bean, which I believe Sean said was a Kernel problem.
Fixes that don't work: This morning I tried the most popular suggestions:
Turn off Lock Screen Popup note
Lock Screen Ripple Effect
S-Voice home key
S-Voice Auto-start speaker
S-Voice wake up command
NONE OF THESE WORK!
So, let's band together and solve this thing. Do some tests and find something that works. Preferably, a solution that takes as little modding as possible.
Is this something that can only be solved by a customer kernel? If so, let's see if a dev is up to the task!
EDIT TO ADD: This seems to be an issue on all variations of this device. I'm searching their forums for an answer, but don't see one yet. I decided to post this here to get more eyeballs on the problem.
Click to expand...
Click to collapse
I have everything that you have listed except Turn off screen popup mode & I have no lag at all.
It's a side effect of the exynos SOC. You can't "fix" it. It just takes about 800ms to wake from deep sleep.
garyd9 said:
It's a side effect of the exynos SOC. You can't "fix" it. It just takes about 800ms to wake from deep sleep.
Click to expand...
Click to collapse
800ms???? No way can I wait that long lol jk
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
garyd9 said:
It's a side effect of the exynos SOC. You can't "fix" it. It just takes about 800ms to wake from deep sleep.
Click to expand...
Click to collapse
Bummer.
Jrockttu said:
The app creates a partial wakelock, so it will affect battery. A wakelock will keep the phone from going into deep sleep, which is what extends Android phone battery life. With such a large battery, it won't be as noticeable on this phone, but it still has substantial negative effects.
Click to expand...
Click to collapse
I have used it on my galaxy s2 and my international galaxy s3 without seeing any negative battery issues. Now granted it has to have some effect but even with the not so great life on s2 wasnt noticeable. Try it out and see if it works for you. I was skeptical at first.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
It is in fact S-Voice.. completely remove it from the Note and you will remove the lag.. this has been an issue with virtually every device with S-Voice... I bet there will be a bebloated ROM come along in the next day or 2 and itll fix it.
Sent from my SAMSUNG-SGH-I317 using xda premium
I dont but I do know my galaxy s3 had it even when I was on aokp.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
daddymatt said:
It is in fact S-Voice.. completely remove it from the Note and you will remove the lag.. this has been an issue with virtually every device with S-Voice... I bet there will be a bebloated ROM come along in the next day or 2 and itll fix it.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
Like the poster above this says, my wife's Galaxy S2 has the lag on AOKP and AOSP based roms that do not have S-Voice. As much as I don't want to believe it, Gary is likely right that it's an exynos issue. I was just hoping that it could be solved through a kernel.
Tested it for ****s and giggles, definitely not S-Voice. I disabled it and restarted phone. Let it settle about a minute from start up, opened BetterBatteryStats to CPU state screen and looked at the "deep sleep" state. Turned screen off for a few seconds, lagged, checked deep sleep state to make sure it had increased (ensuring it was recovering from deep sleep). This is the simple method to test any of these supposed fixes that people say will solve the laggy wake.
Anybody that says their phone doesn't lag when they wake up the screen is likely because they're looking at it while they're charging it, they're playing music, they have an active notification, or they're turning it off and back on really quick. All of these prevent the phone from deep sleeping. Deep sleep is what causes the issue.
I had lag on my Note I whenever it would deep sleep on any Rom. This only happened when I had Wi-Fi off when sleeping. When I turned Wi-Fi on all the time lag was gone. Not a clean battery friendly fix but the lag was driving me crazier than charging the battery a little sooner.
Sent from my GT-N7000 using Tapatalk 2
I have the att version and I was just wondering...the same thing...I am willing..to try anything...I mean it sucks just waiting a little bit. I was just waiting for a new rom
daddymatt said:
It is in fact S-Voice.. completely remove it from the Note and you will remove the lag.. this has been an issue with virtually every device with S-Voice... I bet there will be a bebloated ROM come along in the next day or 2 and itll fix it.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
I would have to say this is true. I've seen people do this in videos and it seems to work. They say its the wake looking and checking to see if you held the button or double clicked it that will solves this problem. Are there any other settings that control the home button settings like how you show recent apps or s-voice?
http://www.youtube.com/watch?v=UHMIxBUclh0&feature=plcp
truth77 said:
I would have to say this is true. I've seen people do this in videos and it seems to work. They say its the wake looking and checking to see if you held the button or double clicked it that will solves this problem. Are there any other settings that control the home button settings like how you show recent apps or s-voice?
Click to expand...
Click to collapse
The only thing disabling S-Voice does is make your Home key work faster once the phone is already on because it's not waiting to see if you're double tapping it. S-Voice has no impact on the wake issue.
Mj23foreva said:
http://www.youtube.com/watch?v=UHMIxBUclh0&feature=plcp
Click to expand...
Click to collapse
That's the first thing I watched this morning when investigating this issue. If you notice, his "fix" doesn't seem to work that well for him. Try it yourself, it won't work. That's why I put it in the OP that these don't work.
No lag here and the phone's been in use/running for 24 hours now.
Related
Hey guys,
This has been bothering me for a while now, but on occasion, my phone just stops sleeping. I attached a screen shot to show what I mean.
It happened on stock, so I've tried a couple other kernels, but they have the same problem.
Any suggestions?
Sent from my SPH-D710 using xda premium
trifthen said:
Hey guys,
This has been bothering me for a while now, but on occasion, my phone just stops sleeping. I attached a screen shot to show what I mean.
It happened on stock, so I've tried a couple other kernels, but they have the same problem.
Any suggestions?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Yes, probably you're experiencing the "AndroidOS" runaway issue. This is a nebulous and currently unresolvable issue, probably related to some Samsung/Sprint driver issue(s) causing feedback loops between the events/0 and suspend processes. It seems to be fixed temporarily by a reboot, or just randomly. It may or may not be associated with excessive battery usage.
I used to get those solid awakes, but then I froze a lot of apps and it went away.
I didn't do it systematically to figure out which was the cause.
As an aside, if you have an older version of FlightView, then that could definitely cause the issue. That isn't a stock app, but is somewhat popular and had a bug keeping the phone awake *even though it wasn't configured to do anything*.
Kn0wBuddy said:
Yes, probably you're experiencing the "AndroidOS" runaway issue.
Click to expand...
Click to collapse
Ironically, my AndroidOS has always been high (almost always higher than display), but it would always sleep just fine, and my battery-life was pretty good. But every time this happens, my AndroidOS is actually lower than usual.
So I've temporarily disabled Juice Defender (just in case it was interrupting something and confusing it into holding a wake lock) and removed the Facebook widget (Better Battery Stats had that listed as 50% of the wakeup events, which is just ridiculous).
I set a custom reference point so I can watch it for a while and see if anything weird pops up. It seems to be happening more often in the last week or so, and the only thing I did back then was remove Watchdog, because I haven't gotten any alerts for about a month.
I have noticed that usually when it gets stuck in an awake state for a long time, it also coincidentally has a stealth LOS, and rebooting will magically cause texts and voicemails to appear. Let's hope the December radio update fixes that problem.
- Has anybody been experiencing 3G/HSPA+ signal issues whilst on CM10-M2 or the CM10 10/14 nightly?
I completely lost my signal until I had a friend call my phone. And then it came back, but it was very slow. (The indicator was grey) This seems to happen often.
- Also, do profiles work?
I have a School profile (default lockscreen with a pattern) and a Home profile (insecure lockscreen) It seems like switching in between these does nothing since I have to still unlock the device with a pattern when I use the Home profile.
- Home button issues?
This just might be my phone, but my homebutton has not been waking my device sometimes. I have to push it extra hard for it to register.
khoikn said:
- Has anybody been experiencing 3G/HSPA+ signal issues whilst on CM10-M2 or the CM10 10/14 nightly?
I completely lost my signal until I had a friend call my phone. And then it came back, but it was very slow. (The indicator was grey) This seems to happen often.
- Also, do profiles work?
I have a School profile (default lockscreen with a pattern) and a Home profile (insecure lockscreen) It seems like switching in between these does nothing since I have to still unlock the device with a pattern when I use the Home profile.
- Home button issues?
This just might be my phone, but my homebutton has not been waking my device sometimes. I have to push it extra hard for it to register.
Click to expand...
Click to collapse
Grey bars means you aren't connected to Google Services, I haven't had any issues with signal.
The home button is a known issue. Mine does most of the time but sometimes it takes two presses.
Sent from my SGH-T999
joshnichols189 said:
Grey bars means you aren't connected to Google Services, I haven't had any issues with signal.
The home button is a known issue. Mine does most of the time but sometimes it takes two presses.
Sent from my SGH-T999
Click to expand...
Click to collapse
It could just possibly be a bad connection within the hallways (cell signal has been known to falter in there.) But even using my phone outside seems to yield a weak signal.
Okay, I thought that my home button was broken, thanks for clearing that up!
Using capacitive buttons would be some much more durable..
So, after much hassle (I managed to brick my phone) I finally managed to fix my data speeds.
Switched back to stock TW ICS.
Data speed aren't 12mbps, but at least fast enough for me to actually use my data.
Which is strange, but heck, I can finally use my phone again.
Just have to wait for the OTA Jellybean update then...
khoikn said:
So, after much hassle (I managed to brick my phone) I finally managed to fix my data speeds.
Switched back to stock TW ICS.
Data speed aren't 12mbps, but at least fast enough for me to actually use my data.
Which is strange, but heck, I can finally use my phone again.
Just have to wait for the OTA Jellybean update then...
Click to expand...
Click to collapse
That's strange.. why don't you try a touchwiz jellybean ROM?
Sent from my SGH-T999
joshnichols189 said:
That's strange.. why don't you try a touchwiz jellybean ROM?
Sent from my SGH-T999
Click to expand...
Click to collapse
FrostyJB was the first ROM that I ever installed on my GSIII.
And I hated it....
That experience just wasn't as fast as I would like and the battery life was terrible.
I'm open to suggestions for other TW-based JB ROMS though if anyone has any.
Edit:
Even stock ICS TW doesn't suit me. Battery life is terrible (Not used at all today, screen's been on for 30 minutes = 79% battery.) and the OS itself feels groggy and slowed.
CM10 feels like the only ROM that I could really use.
For your home button, have you disabled svoice? Double press home and if svoice opens go into settings and uncheck double press home to open.
For profiles, not too sure as I've never really used them, but have you looked into apps like Tasker?
How long ago did you try the jb roms? Both Frosty and XquiziT have come a long way and according to almost everyone are great daily drivers.
For data speeds, have you tried all the different modems? My thread is now stickied in Development. Check post 3 for some build.prop tweaks that may help as well.
As for battery life, it sounds like you're just not using the correct settings if that's your goal. Turn off any features when you're not using them. Especially auto sync. If you have a poor signal this can decimate your battery. (Which may be the main cause anyway, to which id have to say to try the different modems.) I generally get great battery. Often 3-4 hours screen on and can go 20-30 hours on a charge.
Hope some of this helps.
Sent from my SGH-T999 using xda app-developers app
**Edit: I got ninja-posted **
I agree on stock firmware being sluggish. It's just terrible. I personally chose to get away from TouchWiz altoghether. I don't hate the way it looks, I just like AOSP more. I've been using CM10 for over two months now.
Well, as it's been said, the home button issue has been around for a while now. Don't press it hard, just press a few times.
I don't use profiles myself. I get the feeling that the profile settings just don't encompass security settings. I would expect that to be for ringtones/volumes etc. But maybe Tasker can do this for you (PIN or slide, depending on location)? Tasker is very cool, and even more powerful. Even if it can't do this for you, it's still worth every penny (imo).
As far as your data connection, if data stops working, try cycling it off and on. It should re-establish the connection. Have you tried different modems?
DocHoliday77 said:
For your home button, have you disabled svoice? Double press home and if svoice opens go into settings and uncheck double press home to open.
For profiles, not too sure as I've never really used them, but have you looked into apps like Tasker?
How long ago did you try the jb roms? Both Frosty and XquiziT have come a long way and according to almost everyone are great daily drivers.
For data speeds, have you tried all the different modems? My thread is now stickied in Development. Check post 3 for some build.prop tweaks that may help as well.
As for battery life, it sounds like you're just not using the correct settings if that's your goal. Turn off any features when you're not using them. Especially auto sync. If you have a poor signal this can decimate your battery. (Which may be the main cause anyway, to which id have to say to try the different modems.) I generally get great battery. Often 3-4 hours screen on and can go 20-30 hours on a charge.
Hope some of this helps.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I have S-Voice disabled, yes. Plus, the whole issue of the home button doesn't really bother me anymore. Simply reaching my hand up to push the powerbutton is easier now that I have switched cases.
I tried FrostyJB at the end of September.
The build.prop tweaks seem too far out of my league, but thank you so much for the modem idea!
I can remember installing the UVLI8 once upon a time and getting insane results. Will definitely give it a shot. The Jellybean modems work on JB 4.1.2 right?
My battery usage has always been the bare minimum. Literally no toggles are on (GPS, WiFi, Sync, etc) and that's my status. I've been noticing that "Cell Standby" has been the primary culprit for battery drain.
Hey guys, I was getting terrible battery life when the phone is idle. I looked into it to see what was going on. First off, I am on the stock rooted deodex'd ROM that scrosler posted. The biggest problem was an app I installed called Light Flow Lite, it controls your LED. It had over 6 hours of wakelock today. Removed it, not worth it at all.
The second thing I found that was interesting was after that, the phone STILL wasn't hitting deep sleep. I poked around in BetterBatteryStats and didn't find anything in there that would explain that. I then ran a "top" (in terminal or adb shell, type top -m 5 -t). Everything looked normal, nothing crazy. But I turned the screen off and let it run for a few seconds. I got a massive spike in CPU (anywhere from 15-35%) for system_server with the thread "WindowManagerPo" (which is likely short for WindowManagerPolicy).
I did some searching and it turns out that there is a bug with auto rotation that causes this. Essentially, the sensors don't stop looking for orientation change when the screen is off. I found reports of this in the Nexus S forums, GS3 forums, etc. This leads me to believe it is a Samsung kernel issue, since that's the least common denominator when it comes to the phones that had this issue. If you don't use auto rotation, you probably aren't encountering this issue (but keep reading for some good info below!) But I use auto rotation, how can I fix this?
Download an app called Auto Rotate Auto Lock. This app will turn off auto rotation when your screen turns off and enable it back when you turn the screen back on. This looks like this should really help to combat this bug and it handy for people like me who like auto rotation but don't want to have battery life suffer from something as stupid as this. I have verified that my phone now does enter Deep Sleep easily, and it hadn't hit that all day!
I also recommend an app called CPU Spy Plus (XDA thread). This app shows some very valuable information about your processor. You never want to see "Deep Sleep" under Unused CPU States as this means your phone isn't sleeping and is wasting battery!
It would also be good to download BetterBatteryStats (XDA Thread). This will help you nail down battery drain that you won't see in the stock Battery graph found in Settings. Things or importance are Partial Wakelocks and Alarms.
Monitoring these apps can really help you to increase your battery life on your phone. If anyone else is having bad battery life when idle, please try this out. I'm sure this will help you Feel free to ask questions, I will try to answer them as best as I can!
I have autorotation turned on but not the face orientation sensing. I haven't noticed a significant battery loss, at 19 hours with 10 left according to battery spy, but I'll give this a try and see if it increases it any.
i'll give it a shot. i was wondering how at work it would drain 2-4% an hour but at home with a crappy signal i'd only lose 6% all night.
at work it's in my pocket and at home it's stationary.
madsquabbles said:
i'll give it a shot. i was wondering how at work it would drain 2-4% an hour but at home with a crappy signal i'd only lose 6% all night.
at work it's in my pocket and at home it's stationary.
Click to expand...
Click to collapse
I have noticed Google Talk drains batteries when your signed in. By default your phone will sign in. If you don't use TALK, sign-out of the app and you will see increased battery life. Your wont ping the internet as much which saves batteries.
Thanks viperboy I took your suggestion and so far it seems to be helping.
I haven't tried that app yet, however I have definitely noticed an improvement in battery life by disabling auto rotation. Thanks for the info.
THIS NOTE 2 IS SENT FROM A GALAXY WHERE SAMSUNG SPRINTS TO THE TOP, AND JELLY BEANS EAT APPLES!!!!
after a bit of troubleshooting i found that battery monitor widget pro was the cause of my drain. after removing it i went from 2 to 3% an hour to 3% overnight. this really sucks as i love the info bmw colleects. this is the only device i have that suffers drain from the app.
Thanks for the info. I have been losing % 15 battery every night while I'm asleep and was wondering why
...from a Galaxy Note II
-viperboy- said:
Hey guys, I was getting terrible battery life when the phone is idle. I looked into it to see what was going on. First off, I am on the stock rooted deodex'd ROM that scrosler posted. The biggest problem was an app I installed called Light Flow Lite, it controls your LED. It had over 6 hours of wakelock today. Removed it, not worth it at all.
The second thing I found that was interesting was after that, the phone STILL wasn't hitting deep sleep. I poked around in BetterBatteryStats and didn't find anything in there that would explain that. I then ran a "top" (in terminal or adb shell, type top -m 5 -t). Everything looked normal, nothing crazy. But I turned the screen off and let it run for a few seconds. I got a massive spike in CPU (anywhere from 15-35%) for system_server with the thread "WindowManagerPo" (which is likely short for WindowManagerPolicy).
I did some searching and it turns out that there is a bug with auto rotation that causes this. Essentially, the sensors don't stop looking for orientation change when the screen is off. I found reports of this in the Nexus S forums, GS3 forums, etc. This leads me to believe it is a Samsung kernel issue, since that's the least common denominator when it comes to the phones that had this issue. If you don't use auto rotation, you probably aren't encountering this issue (but keep reading for some good info below!) But I use auto rotation, how can I fix this?
Download an app called Auto Rotate Auto Lock. This app will turn off auto rotation when your screen turns off and enable it back when you turn the screen back on. This looks like this should really help to combat this bug and it handy for people like me who like auto rotation but don't want to have battery life suffer from something as stupid as this. I have verified that my phone now does enter Deep Sleep easily, and it hadn't hit that all day!
I also recommend an app called CPU Spy Plus (XDA thread). This app shows some very valuable information about your processor. You never want to see "Deep Sleep" under Unused CPU States as this means your phone isn't sleeping and is wasting battery!
It would also be good to download BetterBatteryStats (XDA Thread). This will help you nail down battery drain that you won't see in the stock Battery graph found in Settings. Things or importance are Partial Wakelocks and Alarms.
Monitoring these apps can really help you to increase your battery life on your phone. If anyone else is having bad battery life when idle, please try this out. I'm sure this will help you Feel free to ask questions, I will try to answer them as best as I can!
Click to expand...
Click to collapse
Thanks for the suggestions. I have heard so much about the great battery life, but that has not been my experience. I had a Note 1 and I had no problems. With Note 2, the battery drains to about 1/4 after about 7 hours with limited use. I have turned off auto rotation, lowered the screen brightness, changed auto check settings for email, and don't see much difference. In addition, it seems a shame that I should have to figure out ways to use fewer functions to make battery last for phone calls, since I never had to do that before. Any ideas?
Thank you for this info. I consistently get a full days charge of of my phone but was pretty clueless when it came to what was draining my battery. I've used the rotation lock app and will report my results to see if I get even more remaining battery each day.
Sent from my SPH-L900 using xda app-developers app
Thanks for the helpful advice Viperboy! I've definitely been having wake lock issues with my phone. Hopefully these apps will help me eliminate the problems.
kat3k said:
Thanks for the suggestions. I have heard so much about the great battery life, but that has not been my experience. I had a Note 1 and I had no problems. With Note 2, the battery drains to about 1/4 after about 7 hours with limited use. I have turned off auto rotation, lowered the screen brightness, changed auto check settings for email, and don't see much difference. In addition, it seems a shame that I should have to figure out ways to use fewer functions to make battery last for phone calls, since I never had to do that before. Any ideas?
Click to expand...
Click to collapse
As viperboy mentioned, BetterBatteryStats is your friend. It really will help you figure out why your phone isn't sleeping like it should. It definitely takes some time to monitor and figure out what the readings mean to help point you to the apps or settings that're affecting your battery, but well worth it. I also like having a better understanding of how things work on my phone.
i did a double check on battery monitor widget pro and it started draining my phone again. as soon as i uninstalled it everything was fine again. this is with both cleanrom and blazer. i'll just wait til official support comes and try it again.
-viperboy- said:
Hey guys, I was getting terrible battery life when the phone is idle. I looked into it to see what was going on. First off, I am on the stock rooted deodex'd ROM that scrosler posted. The biggest problem was an app I installed called Light Flow Lite, it controls your LED. It had over 6 hours of wakelock today. Removed it, not worth it at all.
The second thing I found that was interesting was after that, the phone STILL wasn't hitting deep sleep. I poked around in BetterBatteryStats and didn't find anything in there that would explain that. I then ran a "top" (in terminal or adb shell, type top -m 5 -t). Everything looked normal, nothing crazy. But I turned the screen off and let it run for a few seconds. I got a massive spike in CPU (anywhere from 15-35%) for system_server with the thread "WindowManagerPo" (which is likely short for WindowManagerPolicy).
I did some searching and it turns out that there is a bug with auto rotation that causes this. Essentially, the sensors don't stop looking for orientation change when the screen is off. I found reports of this in the Nexus S forums, GS3 forums, etc. This leads me to believe it is a Samsung kernel issue, since that's the least common denominator when it comes to the phones that had this issue. If you don't use auto rotation, you probably aren't encountering this issue (but keep reading for some good info below!) But I use auto rotation, how can I fix this?
Download an app called Auto Rotate Auto Lock. This app will turn off auto rotation when your screen turns off and enable it back when you turn the screen back on. This looks like this should really help to combat this bug and it handy for people like me who like auto rotation but don't want to have battery life suffer from something as stupid as this. I have verified that my phone now does enter Deep Sleep easily, and it hadn't hit that all day!
I also recommend an app called CPU Spy Plus (XDA thread). This app shows some very valuable information about your processor. You never want to see "Deep Sleep" under Unused CPU States as this means your phone isn't sleeping and is wasting battery!
It would also be good to download BetterBatteryStats (XDA Thread). This will help you nail down battery drain that you won't see in the stock Battery graph found in Settings. Things or importance are Partial Wakelocks and Alarms.
Monitoring these apps can really help you to increase your battery life on your phone. If anyone else is having bad battery life when idle, please try this out. I'm sure this will help you Feel free to ask questions, I will try to answer them as best as I can!
Click to expand...
Click to collapse
Have you tried the Perseus kernel? I hear the battery life is improved with it. So may be it doesn't have the rotate issue.
I've been using cpu sleeper and I easily get about 30 hours. Looks like the new apk fixed quad core. So when the phone is off it only uses one core and shuts down the other three and lights them back up when you need them.
Sent from my SPH-L900 using xda premium
ZenInsight said:
Have you tried the Perseus kernel? I hear the battery life is improved with it. So may be it doesn't have the rotate issue.
Click to expand...
Click to collapse
I'm on it now, but I haven't looked to see if it fixed the auto rotation bug yet,
rudyrude432 said:
I've been using cpu sleeper and I easily get about 30 hours. Looks like the new apk fixed quad core. So when the phone is off it only uses one core and shuts down the other three and lights them back up when you need them.
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
That app is unnecessary. Pegasusq governor already does that by default. Goes to 1 core and 200mhz when screen off, at least that's how my Note 10.1 was. I assume it is the same here since the International GS3, GN 10.1, and GNII basically share the same kernel with a few minor differences.
I think I may try the perseus kernel today to see if it improves battery.. I haven't heard it does.. I just been seeing people do that benchmark stuff with it
-TeaM VeNuM Like A Boss
Interesting... I have a script that reports on CPU freq and, when plugged into USB (maybe the wall charger too, didn't check), it appears that the kernel runs cpu0 and cpu3 all the time, even when screen off. With the phone unplugged, it went to using only cpu0 but didn't cap the freq. It was spending a good amount of time at the higher frequencies even though I had nothing running.
MiguelHogue said:
I think I may try the perseus kernel today to see if it improves battery.. I haven't heard it does.. I just been seeing people do that benchmark stuff with it
-TeaM VeNuM Like A Boss
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1959898&page=5
Post #42
I installed the app to turn the rotation off when the screen is off so far everything good but when I get a call this goes crazy because the screen goes while in call. I know this because I have an smartwatch which it has a notification app and every message that the phone has my watch vibrates with that message and I had a call few minutes ago my watch started vibrating non stop until I hang up.
Sent from my SPH-L900 using Tapatalk 2
My note 2 always takes around 1-2 seconds to wake up every time with wake up button. I found its quite annoying compared to my old i4. Does anyone have the same problem. Any fix?
I have the same problem.
sometimes it is instant, but sometimes it takes a sec.
Try turning off S-Voice activation on the home button and also 'Pop up Note on Lockscreen' in the lock screen settings.
Try turning off the lock screen ripple effect also.
Normal
That is normal behavior and I believe is part of the android platform (so the note2 is not to blame). When you lock your android phone, it goes into "deep sleep" (unless you have an app running in the background which is preventing it from doing so). Deep sleep is basically a phase where the cpu clock speed gets very low to save battery. When you wake your phone it takes about a full 1-1.5 seconds to wake it from that phase.
If you're not getting that 1-1.5sec delay, that means your phone wasn't in the deep sleep phase when you woke it up.
I'd say ~1 sec delay when waking your device up is a good trade-off for a better standby battery performance.
interfreak said:
Try turning off S-Voice activation on the home button and also 'Pop up Note on Lockscreen' in the lock screen settings.
Try turning off the lock screen ripple effect also.
Click to expand...
Click to collapse
I already turned off all above. I cant get to ripple effect because i use vpn and it forced me to use pattern lock. Thanks anyway
MohJee said:
That is normal behavior and I believe is part of the android platform (so the note2 is not to blame).
Click to expand...
Click to collapse
No. This is not normal behavior. The Nexus 3 does not have this lag despite running the latest OS (same as the Note 2). It's ****ing annoying.....
It is a good sign, it means that the phone was in deep sleep state.
It is basically the quad core thing..takes time to go from deep sleep to rev up.the cores
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
interfreak said:
Try turning off S-Voice activation on the home button and also 'Pop up Note on Lockscreen' in the lock screen settings.
Try turning off the lock screen ripple effect also.
Click to expand...
Click to collapse
thanks for the tip, did them all, and it is much faster now.
"edit"
I think it is a deep sleep issue after waiting a while
MohJee said:
That is normal behavior and I believe is part of the android platform (so the note2 is not to blame). When you lock your android phone, it goes into "deep sleep" (unless you have an app running in the background which is preventing it from doing so). Deep sleep is basically a phase where the cpu clock speed gets very low to save battery. When you wake your phone it takes about a full 1-1.5 seconds to wake it from that phase.
If you're not getting that 1-1.5sec delay, that means your phone wasn't in the deep sleep phase when you woke it up.
I'd say ~1 sec delay when waking your device up is a good trade-off for a better standby battery performance.
Click to expand...
Click to collapse
What you have said is basically CRAP. It has nothing to do with deep sleep and everything to do with the chipset that Samsung uses in most of their recent phones. The Nexus is a notable exception. It has NO WAKUP LAG. If this was an Android thing, as you have incorrectly stated, the Nexus would have wakeup lag and so would HTC phones. They don't.
If you have no idea what you are talking about, please don't post your own theories, which in this case are totally WRONG.
appro77 said:
What you have said is basically CRAP. It has nothing to do with deep sleep and everything to do with the chipset that Samsung uses in most of their recent phones. The Nexus is a notable exception. It has NO WAKUP LAG. If this was an Android thing, as you have incorrectly stated, the Nexus would have wakeup lag and so would HTC phones. They don't.
If you have no idea what you are talking about, please don't post your own theories, which in this case are totally WRONG.
Click to expand...
Click to collapse
@ appro77 - thanks for your input, (I always like it when a theory is proved wrong by demonstrating proof of the apposing theory.) while I agree with you I can only hope your constructive input will inspire a solution.
MohJee said:
That is normal behavior and I believe is part of the android platform (so the note2 is not to blame). When you lock your android phone, it goes into "deep sleep" (unless you have an app running in the background which is preventing it from doing so). Deep sleep is basically a phase where the cpu clock speed gets very low to save battery. When you wake your phone it takes about a full 1-1.5 seconds to wake it from that phase.
If you're not getting that 1-1.5sec delay, that means your phone wasn't in the deep sleep phase when you woke it up.
I'd say ~1 sec delay when waking your device up is a good trade-off for a better standby battery performance.
Click to expand...
Click to collapse
That's absolutely incorrect to blame Android as the culprit. This is the only Android device I've had that has such considerable wake-up lag.
appro77 said:
What you have said is basically CRAP. It has nothing to do with deep sleep and everything to do with the chipset that Samsung uses in most of their recent phones. The Nexus is a notable exception. It has NO WAKUP LAG. If this was an Android thing, as you have incorrectly stated, the Nexus would have wakeup lag and so would HTC phones. They don't.
If you have no idea what you are talking about, please don't post your own theories, which in this case are totally WRONG.
Click to expand...
Click to collapse
Im not sure if thats crap, but i also heard kinda things all the time from many CM devs, when i was using note N7000, Milestone3 and LG O2X, those CM devs said same thing like wakeup lag cause by deep sleep, if device wake up instantly, it means the battery is draining.....
But the lag is like 1 second, not 2 seconds, so if my note2 can wake up around 1 second, i can accept it and count the "wake up lag" theory is true, if this is a false theory, please correct me with the true one.
It's normal behaviour for a stock rom.
It's certainly fixable with source built roms
Affects to battery and 'deep sleep' are debatable.
S3 has identical behaviour
If it bothers you, take your head out of your rectum.
Sent from my GT-N7105 using xda app-developers app
Hi I am on the at&t version but we have it as well but it kinda a exnous processor thing every one that I had with that processor does it. I install soft locker on the market completely gets rid of it and dont show any real adverse battery effects. Just my two cents .
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
because of google play???
moved to new threat
So I searched around in this forum but I can't find an answer. My Note 2 (AT&T obv) takes almost a full second to wake after pressing the unlock button. It's been like this through 2 roms and was the same way on my stock rom. Literally I press the button and it takes a good 1/2 to a full second to wake up to the lock screen. Am I the only person having this issue? I tried removing my SD card and it slightly lowered the wake time but it's still significant. I went from my Inspire 4G to this and even with the perseus kernel and both on cleanROM and Jedix6 or whatever it's called the problem persists and the phone doesn't seem as snappy as my OC'd Inspire. I mean the inspire had little to no lag at all after pressing the button to see the lock screen but it seems odd to have to wait as long as I do on a newer, faster phone. Maybe I'm just being nit picky... Any ideas?
Bliznade said:
So I searched around in this forum but I can't find an answer. My Note 2 (AT&T obv) takes almost a full second to wake after pressing the unlock button. It's been like this through 2 roms and was the same way on my stock rom. Literally I press the button and it takes a good 1/2 to a full second to wake up to the lock screen. Am I the only person having this issue? I tried removing my SD card and it slightly lowered the wake time but it's still significant. I went from my Inspire 4G to this and even with the perseus kernel and both on cleanROM and Jedix6 or whatever it's called the problem persists and the phone doesn't seem as snappy as my OC'd Inspire. I mean the inspire had little to no lag at all after pressing the button to see the lock screen but it seems odd to have to wait as long as I do on a newer, faster phone. Maybe I'm just being nit picky... Any ideas?
Click to expand...
Click to collapse
Ive noticed it as well. Got used to it and it don't bother me anymore but a solution would be nice
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
http://forum.xda-developers.com/showthread.php?p=33492447
Sent from my SAMSUNG-SGH-I317 using xda premium
have you tried to increase your minimum deep sleep cpu frequency from 200mhz to maybe 350mhz or so?
a shot in the dark would be reducing the animation scale in developer settings but this is only if it's considered an animation when you turn on the phone
battery life is amazing on this phone and if you agree and want to try it. There is a app called soft locker on the market that will fix the delay. I dont notice that much of a drain on the battery even though I know it has to have some. Basically the CPU in samsung phones go into a very deep sleep and that helps battery but if you use the above app it creates wakelocks that keep it from deep sleep and fixes the issue.
This can make battery life less but like I said I have used it for over a month and still get over a day out of my phone and I usually have 4 hours or more screen on time and still end day with 25%-50% battery left.
http://forum.xda-developers.com/showpost.php?p=35617276&postcount=2096
Apen83 in the Jedi ROM thread says to do this:
"Settings > developer options > window animations off / transition off / animator duration off"
Looks like its working for them.
If it works for you, hit the link and thank his post.
This doesn't help as it's not an animation.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
It's a characteristic of Exynos processors. It sucks, but what can ya do?
I'm using asylum rom and kernel and see nowhere near the delay that stock had. It's almost instant on for me
Its probably the pegasusq governor, but that's what you have to go with to be able to hotplug CPU cores. This is the price you pay for battery life.
You did not search well enough. There is no solution, and nothing you can do about it other than the aforementioned Soft Locker, which will negatively impact your battery life.
More info here: http://forum.xda-developers.com/showthread.php?t=1983697&highlight=wake+lag
It sucks, but I guess it's a sacrifice I have to live with on an otherwise awesome device.