Related
OK. My wife phone is really crazy draining battery like it's crack. Soo would like to know anyone using this. What's your set up. Should I do load on bootup etc? Scaling set to? When screen off so forth. She's on SC 2.9.2 with jt kernel lastest one. Thx for the help guys.
Sent from my ADR6400L using XDA Premium App
Interactive. Ondemand. Conservative. Performance. Pretty much self explanatory right? Does anyone have a nice guide for fascinate? Maybe. I set up 400mhz on sleep and.it would power on after putting on lock.
Sent from my ADR6400L using XDA Premium App
I'm not having battery issues and I'm running just the 2.2 leak with JT's 327-2 kernel. Just set CPU to conservative and maybe drop it down to 800 mhz. I spent the majority of my day today talking on my phone and playing cordy and I was at 50%.
You can give this a shot it could just be giving weird info on the battery level. while the phone is on, charge the battery to 100% full. Turn off phone plug it in and charge to 100% again. Boot phone into CWR and clear the battery stats. Start phone like normal.
Hope that helps.
Install spare parts and use the Battery History feature and check for a wakelock. Thats the prime reason why a phone will drain like crazy.
To check for a wake lock Spare Parts> Battery History >And look to see how long it's running. If it's a really high % and the screen has been off you have a wake lock.
To find out what's causing the wakelock click "other usage" and choose "partial wake usage".
If it's Android system it's probably the GPS doing it. So turn off the GPS unless you're using it.
Cool ill check those out.
Sent from my ADR6400L using XDA Premium App
So setcpu useless then? Or does it even make a little difference with the battery? On sleep at least?
Sent from my ADR6400L using XDA Premium App
I find the phone to do a good job of managing itself but I also haven't played with setcpu alot. A sleep profile probably wouldn't hurt things... but someone else is probably better suited to answering your question.
The only thing I'm using it for now is for a temperature profile to act as a failsafe if the phone/battery start gettting too hot.
bobloblaw1 said:
I find the phone to do a good job of managing itself but I also haven't played with setcpu alot. A sleep profile probably wouldn't hurt things... but someone else is probably better suited to answering your question.
The only thing I'm using it for now is for a temperature profile to act as a failsafe if the phone/battery start gettting too hot.
Click to expand...
Click to collapse
Thx for the info. I'm running into screen freeze with setting up sleep profile... Grrrrr.
Sent from my ADR6400L using XDA Premium App
dadsterflip said:
Thx for the info. I'm running into screen freeze with setting up sleep profile... Grrrrr.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Just speed up the minimum mhz for the profile. I believe 400 would be okay, try it.
Dread This Day said:
Just speed up the minimum mhz for the profile. I believe 400 would be okay, try it.
Click to expand...
Click to collapse
No luck..... Freezes
Sent from my ADR6400L using XDA Premium App
Freezes only on conservative. But ondemand works great
Sent from my ADR6400L using XDA Premium App
dadsterflip said:
So setcpu useless then? Or does it even make a little difference with the battery? On sleep at least?
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
SetCPU may help with battery life however you are better off with JuiceDefender in my opinion. This will automatically turn off items not needed when phone screen is off.
If battery draining is your real problem, this thread may also help:
http://forum.xda-developers.com/showthread.php?t=987529
Set CPU isn't really fully compatible with the fascinate. The author says use a certain profile but it doesn't help much. When i used set CPU, my phone would go to sleep endlessly and I wasn't able to turn the screen on. This is because there was a bug causing it to go down to 19.2Mhz even though I set it at around 400. I had to pull the battery to solve this.
I have found that running Setcpu freezes mine up anytime it goes into sleep mode not matter what speed it is set at. The only way I was able to fix this was by removing the app, reflashing the kernel, and reinstalling it.
Have you tried to charge to 100% with the phone off, boot into recovery, and clear the battery stats? Run the battery to death before charging and you will have improved battery life.
Ill try to do all those advices guys. Thx for the info.
Sent from my ADR6400L using XDA Premium App
SuperFan86 said:
Run the battery to death before charging and you will have improved battery life.
Click to expand...
Click to collapse
Do NOT run the battery to "death". This actually is bad for the battery. Every time you do this you will kill cells that will never come back giving you less life per charge of the battery.
Suicide Shift said:
Do NOT run the battery to "death". This actually is bad for the battery. Every time you do this you will kill cells that will never come back giving you less life per charge of the battery.
Click to expand...
Click to collapse
You are right.
I meant run it super low, it may even display 0. This allows for better calibration of the battery.
Zacisblack said:
Set CPU isn't really fully compatible with the fascinate. The author says use a certain profile but it doesn't help much. When i used set CPU, my phone would go to sleep endlessly and I wasn't able to turn the screen on. This is because there was a bug causing it to go down to 19.2Mhz even though I set it at around 400. I had to pull the battery to solve this.
Click to expand...
Click to collapse
The profiles definitely do not work on the SF. The app doesn't really get along well with any of the Galaxy S phones. I run mine at 800 max, 100 min and on conservative. It brings it down to around 100 mhz when sleeping, and back up to 400 or 800 when using it. Don't enable any profiles, as it will cause your phone to freeze when the screen goes off.
There are two things you can use SetCPU to change/edit that I have found won't cause problems. You can change the min/max clock speed the phone will run at and you can change the cpu governor. I had issues with Set on Boot enabled, though Profiles are the biggest issue. The info tab is also useful for looking at information about the kernel and system.
I am new to the roms/kernals just got on it this month or so but i am using community rom 1.3 nd OTB 1.3 kernal and my battery is HORIBLE!! it will go down 10% with no wifi nd no data in like ten minutes. Can someone please help me set up my voltage control or tell me what is going on and why my battery is so bad? Thanks
ballerfree said:
I am new to the roms/kernals just got on it this month or so but i am using community rom 1.3 nd OTB 1.3 kernal and my battery is HORIBLE!! it will go down 10% with no wifi nd no data in like ten minutes. Can someone please help me set up my voltage control or tell me what is going on and why my battery is so bad? Thanks
Click to expand...
Click to collapse
Try Battery Calibration.
Charge your phone to 100% "on" > turn your phone "off" and charge up to 100% > Turn "on" and charger again to 100% > Go into Recovery > Advanced > Wipe Bstats.
If it doesn't work, let me know.
1% a min, that has to be a calibration issue. deff try what the second post said first.
ok so i just did what you told me and it is still dropping bad. i just finished it like 10 mins ago and its aready 96% with no data no wifi still idk what to do andymore.
you have to let it go through several calibrations. Charge to 100% and let it die, and recharge to 100%. go through this process several times and you will see improvement.
Ok ima try to keep doing it for the next day or two
Sent from my SCH-I500 using XDA App
When addressing the massive battery drain of Froyo ROMS, the battery stats wipe / calibrate is weak and pathetic. It only works as a placebo for people who don't have a scientific approach to battery drain.
Froyo ROMS on Fascinate have all kinds of battery issues. Some people notice them, some don't. Do the following and it may help:
1) toggle airplane mode each boot
2) enter / exit maps each boot
3) disable location services
4) set wifi sleep plcy. to screen off
5) disable auto rotation
Iphone 4: excellent battery life out of the box. No hacks. No forum trolling. What a novel idea!
Froyo on Fascinate is half baked and was tossed over the fence like a dog turd.
Scrappy1 said:
When addressing the massive battery drain of Froyo ROMS, the battery stats wipe / calibrate is weak and pathetic. It only works as a placebo for people who don't have a scientific approach to battery drain.
Froyo ROMS on Fascinate have all kinds of battery issues. Some people notice them, some don't. Do the following and it may help:
1) toggle airplane mode each boot
2) enter / exit maps each boot
3) disable location services
4) set wifi sleep plcy. to screen off
5) disable auto rotation
Iphone 4: excellent battery life out of the box. No hacks. No forum trolling. What a novel idea!
Froyo on Fascinate is half baked and was tossed over the fence like a dog turd.
Click to expand...
Click to collapse
I don't think 1% an min can be attributed to any run away process or any normal or abnormal use. I may be wrong but I don't think that kind of drain rate is possible without an actual short in the hardware. I would love to hear the devs chime in on the calibration issue as my only knowledge of it is just repeating what I've read.
Oh and unplugging your phone and finding that your down to 95% is normal. Your phone won't hold the 100% charge to prevent damage from over charge. When charging it will hit 100% then stop until out drops to around 95% them start back up again.
So don't count what it "drops" in the first few secs after unplugging.
Iv been doing this for two weeks nd it still is horrible on battery.....idk what to do nemore
Sent from my SCH-I500 using XDA App
ballerfree said:
Iv been doing this for two weeks nd it still is horrible on battery.....idk what to do nemore
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Why don't you try a different kernel? Maybe the PB&J variety?
So, I went to sleep at full charge, took it off the charger to see how my drain was....I woke up 6 hours later and it was at 64%. I took a look at partial wake locks and it looks as follows (I can't upload .png from my phone)
RILJ (Dialer) 205s count 2178
juicedefender 3019s count 1570
Alarm manager 1543s count 1320
Google services event log also has a pretty high count. I ran the "battery fix" and all that jazz,recalibrated my battery,not sure why drain is so terrible?
Could someone please help me out?
I am running cm7 with faux 0.2.0 1.3 kernel. I have it undervolted and profiles so it never goes above 1ghz unless on ac charger. (456 when screen is off)
Sent from my MB860 using XDA App
I'm not sure how much it helps you with your issue, but for me JuiceDefender works very well. I would otherwise have a multitude of data sync apps such as Gmail running, and this limits it while periodically enabling sync.
Start tweaking what apps are using data and the battery life will be better.
I have had a problem the same where I am not so sure juicedefender is helping because I tend to set my phone on the desk when I do homework and the screen comes on after I put into sleep mode and then no more that 5 seconds later it turns on at about 25% screen brightness then jumps to 100% them dims to 25% then goes off, all in a matter of between 10-20seconds. I loom at the battery use area in settings and standby is at least 40% & display is right under and idle is next. my settings that I think may be causing this are the mobile data where the autosync is set at enable (in juice defender) & I tried ping but it does the same thing. I just want to know why the screen comes on ever 5 seconds. I don't know how to contact the developer to try and resolve my problem. I am actually on a thunderbolt but that shouldn't matter. I just wanted to reinforce that "i'm not sure juice defender is working as I get about the same battery life".
Xoom Xoom
I get double the life out of the same roms. I'll try a rom for a day then run juice defender and get a day and a half. Depends on how you have defender setup. The only thing I don't like it doing is disabling my wifi as It sometimes won't reconnect back unless I manually do it. I think setcpu is a joke though. I had it set for 216/456 at screen off and it was running at 1200 for 1/2 the time it was supposed to be asleep. Then whne I opened it up...(Battery less than 50% stay below 1000) and the screen booted up 1300. So to me it's an extra service I don't need.
JD has always given me more battery life on any rom that I have tried.. I recently got rid of it and am trying out GreenPower. so far GP seems to work a bit better than JD. I get a bit more life out of my batter than JD gave me.. try green power out if JD is not cutting it for you.. GP seems a bit lighter as well.. so, could be overall why get more battery life out of it..
Zug
Juice Defender seemed to do little to nothing for my phone. I got rid of it and my battery life remained the same. I can't say the same for everyone else but what works for you might not work for the next guy.
All I'm simply saying is give it a shot and test it out religiously before you make a decision to use it or not.
Works for me another good thing to do if you use set CPU underclock the hell out of it when the screen is off not using it so why not
Sent from my MB860 using XDA App
My setCPU profiles are as follows:
CPU > 62.0c 456/216 (Priority 100)
Screen off 456/216 (96)
In Call 456/216 (75)
Charging AC 1300/216 (74)
Battery < 20% 608/216 (59)
Battery < 10% 456/216 (54)
Phone is otherwise capped at 1ghz
I have JD configured to run my syncs once every 15 minutes for 1 minute. It is also disabling mobile data while the screen is off and wifi when inactive for 1 minute.
Not sure what else I should do here? Should I re-flash CM7 with the battery @ 100%?
kisnerct said:
My setCPU profiles are as follows:
CPU > 62.0c 456/216 (Priority 100)
Screen off 456/216 (96)
In Call 456/216 (75)
Charging AC 1300/216 (74)
Battery < 20% 608/216 (59)
Battery < 10% 456/216 (54)
Phone is otherwise capped at 1ghz
I have JD configured to run my syncs once every 15 minutes for 1 minute. It is also disabling mobile data while the screen is off and wifi when inactive for 1 minute.
Not sure what else I should do here? Should I re-flash CM7 with the battery @ 100%?
Click to expand...
Click to collapse
Install the battery calibration app and see if your charge at 100% shows 4000mV+, if it doesn't, that means your calibration is off and you need to search for juggernaut's battery thread and follow the instructions on that to fix your calibration.
Kraize said:
Install the battery calibration app and see if your charge at 100% shows 4000mV+, if it doesn't, that means your calibration is off and you need to search for juggernaut's battery thread and follow the instructions on that to fix your calibration.
Click to expand...
Click to collapse
It shows me at 4196mV at 99%,( unable to get past that)
Sent from my MB860 using XDA App
Barely saw any gain using JD...only used it on my Dell Streak though. The atrix will go 2 days if I need it to so I don't see any need for JD.
I m using JD for nearly 2 years now and I have to say that it DEFINITLY improves battery-life - just by letting it switch off your 3G when you don´t need it you save a lot of juice.
When I still used my Captivate as my DD, JD helped alot. With all the firmware leaks I was reflashing my phone all the time and constantly testing different kernels/roms/apps for battery life.
On my Atrix, it hasn't seemed to help nearly as much. Not sure why... SetCPU with faux's OC/UV kernel has boosted battery significantly though.
I got lots of wakelocks using it. For me it's better to turn off data manually.
Sent from my MB860 using XDA App
DavidNL said:
I got lots of wakelocks using it. For me it's better to turn off data manually.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
+ 1, it instantly topped the wakelocks. I thought I'd give it a go & bought the full version; un-installed 6 hours later. Maybe it works well on cm7? I'm on Nottach's Dark Side.
Back to good ol' green power.
Vangelis13 said:
+ 1, it instantly topped the wakelocks. I thought I'd give it a go & bought the full version; un-installed 6 hours later. Maybe it works well on cm7? I'm on Nottach's Dark Side.
Back to good ol' green power.
Click to expand...
Click to collapse
Switched to green power
and now I get at least 12 more hours versus juice defender...crazy!
Sent from my MB860 using XDA App
Interesting. I'll have to try green power. JD said my battery multiplier was 2.10x when I used it. It could just be making that up though. I got 28 hours of life from the atrix and still had 40% battery left (moderate usage: frequent texting and periodic data+wifi usage, I think a 20-30 minute phone call too)
I swtiched to green power. Didn't notice much of a difference in battery life, but Gp is certainly a lot easier to use.
How can I make my battery last longer? I am using set cpu and various profiles to give me the best optimization I can, however my phone barely makes it 10 hours with light use *1hr web browsing, avid txting, light music listening via music on phone ~ 1 hr as well.* I'm not faulting the phone. I just want to know what can be done to get the most out of the stock battery as I see people getting results twice as good as mine and just done get what I'm doing wrong here.
Thanks for the help in advanced.
I have the exact same problem as you. Are you using unnamed with Enthropy's experience kernal as well? I'm about to flash cm7 to see if I can get better results.
Sent from my SAMSUNG-SGH-I777 using xda premium
xAnimal5 said:
I have the exact same problem as you. Are you using unnamed with Enthropy's experience kernal as well? I'm about to flash cm7 to see if I can get better results.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
I used cm7 for a while now using UnNamed and cm gave marginally better battey life but
Just use the dang phone . You dont need to do anything special for great battery life. Try a factory reset if theres a problem though. Im rooted on cog beta 4 getting amazing battery life. I talked my mom imto getting this phone over the new iphone and hers is completely stock and she knows nothing and doesnt close any apps and gets the same amazing battery life as i do.
Reset and use it. If you cant get through a day of heavy use the phone is defective.
Sent from my SAMSUNG-SGH-I777 using xda premium
roadrash7 said:
If you cant get through a day of heavy use the phone is defective.
Click to expand...
Click to collapse
+1....or you have wakelocks. Find BetterBatteryStats and CPUSpy. BetterBatteryStats will tell you if something is preventing the device from going into deep sleep. I like to use "wakelocks since unplugged." CPUSpy will tell you the amount of time your device spends in each frequency, including deep sleep. For this, you'll need to reset the timers each time you unplug the phone.
Its add easy as flashing cm.... I went 15 hours and still had 60% left. with OC. Nothing else special (aka no juice defender our set CPU). The only trick is deleting everything in the dcim folder (known medias bug ) you'll see 1% battery loss per hour, with fb and GV sync
Sent from my SGH-I777 using XDA App
Simba501 said:
+1....or you have wakelocks. Find BetterBatteryStats and CPUSpy. BetterBatteryStats will tell you if something is preventing the device from going into deep sleep. I like to use "wakelocks since unplugged." CPUSpy will tell you the amount of time your device spends in each frequency, including deep sleep. For this, you'll need to reset the timers each time you unplug the phone.
Click to expand...
Click to collapse
BBS sometimes misses wakelocks, for even more info, grab the contents of /proc/wakelocks and post them here.
my solution: keep a charger with you anywhere you go
I have a car charger, home charger and work charger (as do most people)
Thanks for all the replies. I'm sure there's go to be a work around for this
Not sure about a workaround. From everything I've seen, the max battery life is around six hours when the screen is on. Basically, if your screen has been on for 4-5 hours, it's time for a recharge.
Sent from my Galaxy S II using Tapatalk
arctia said:
Not sure about a workaround. From everything I've seen, the max battery life is around six hours when the screen is on. Basically, if your screen has been on for 4-5 hours, it's time for a recharge.
Sent from my Galaxy S II using Tapatalk
Click to expand...
Click to collapse
Well based on all I've read it seems like the battery is a mixed bag depending on the OC profiles, roms and kernels being used with the device.
Is it true that setting a screen off profile in set cpu will cause the device to not be able to enter a deep sleep mode and thus will kill the battery faster?
Sent from my SAMSUNG-SGH-I777 using xda premium
Alucardis666 said:
Well based on all I've read it seems like the battery is a mixed bag depending on the OC profiles, roms and kernels being used with the device.
Is it true that setting a screen off profile in set cpu will cause the device to not be able to enter a deep sleep mode and thus will kill the battery faster?
Click to expand...
Click to collapse
Not true. It is true, however, that on stock kernels and ones without the "sleep of death" fix, setting a screen off profile with a clock limit lower than 800 MHz can cause "sleep of death" issues. Right now I think only my kernel and the Cyanogenmod kernel have the SoD fix.
Entropy512 said:
Not true. It is true, however, that on stock kernels and ones without the "sleep of death" fix, setting a screen off profile with a clock limit lower than 800 MHz can cause "sleep of death" issues. Right now I think only my kernel and the Cyanogenmod kernel have the SoD fix.
Click to expand...
Click to collapse
Thanks for clearing that up
I'll post here as I don't have enough posts for the development forum yet.
I'm running Entropy's 16th exp kernal, and Cog4 and I noticed my battery draining far too fast, CPUSpy then showed that the phone simply isn't entering deep sleep. I had previously been undervolting with Voltage Control but I uninstalled the program just to be safe, still not deep sleeping. I also uninstalled Widgetlocker, and I don't think I have any apps that would cause infinite wakelock. What are some possible causes of this issue? Just so I have an idea where I should be changing things.
UPDATE: Reflashing the kernal fixed the problem for a while but then I reinstalled voltage control and now I seem to have it again. Uninstalling and reflashing again however, did not fix the problem. I am utterly confused
On another subject, has anyone actually noticed better battery life after undervolting?
Freaking SWEET! My battery lasted 33 hours and 13 minutes! I've only owned the phone for 3 days now and this is off of teh very 1st FULL charge! Usage was between light & moderate. Data sync on, Wifi On, GPS OFF, BT OFF, FB Data Sync OFF, Capacitative buttons set to light up only in the dark & NO haptic touchback...mmm, can't remember what else I tweaked at the moment but I think that's fantastic battery life! I'm upgrading from a G1 that couldn't last more than 17 hours when it was on standby ONLY with maybe 2 phonecalls and less than 20 text messages. I usually only averaged 6-8 hours and with SIMILAR usage in the last couple of days, I've been able to get 33+ HOURS? ^_^ <-- I'm very, very happy so far! This is on a stock root - NO custom ROM for me at the moment...I'm actually digging TouchWiz 4.0 which I thought I was going to hate when I played with the previous version of TW on the T-Mo Vibrant. (yes, my G1 was running CM 7.1 and battery life still sucked and I went through 2 different aftermarket batteries w/o any luck!)
Don't know what the voodoo in the programming is with this bad boy, but I think Sammy did a nice job this time!
The best thing you can do is having "Autostart" to prevent App to start automatically. I saved 25-30% on my SGS 1 and the same on my SGS 2 (i777). My son on the I9000 SGS 2 saved also 30%.
poker_rick said:
The best thing you can do is having "Autostart" to prevent App to start automatically. I saved 25-30% on my SGS 1 and the same on my SGS 2 (i777). My son on the I9000 SGS 2 saved also 30%.
Click to expand...
Click to collapse
Thanks for the tip
selfassembled said:
I'll post here as I don't have enough posts for the development forum yet.
I'm running Entropy's 16th exp kernal, and Cog4 and I noticed my battery draining far too fast, CPUSpy then showed that the phone simply isn't entering deep sleep. I had previously been undervolting with Voltage Control but I uninstalled the program just to be safe, still not deep sleeping. I also uninstalled Widgetlocker, and I don't think I have any apps that would cause infinite wakelock. What are some possible causes of this issue? Just so I have an idea where I should be changing things.
UPDATE: Reflashing the kernal fixed the problem for a while but then I reinstalled voltage control and now I seem to have it again. Uninstalling and reflashing again however, did not fix the problem. I am utterly confused
On another subject, has anyone actually noticed better battery life after undervolting?
Click to expand...
Click to collapse
Check for wakelocks in BetterBatteryStats, and if that doesn't find anything, do the following in an Android Terminal Emulator shell:
Code:
cat /proc/wakelocks > /sdcard/wakelocks.txt
or better, using ADB (Google it and if you're on Windows, Droid Explorer)
Code:
adb shell cat /proc/wakelocks > wakelocks.txt
Then post wakelocks.txt here
All the apps,camera n everything works on that rom? ??? I installed cm7 bt now stock it cuz some apps and camera app didn't work.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
I have recently realized that my phone had a lag/delay when turning of the screen to the lockscreen. When I press the power button, it would take about 1-1.5 seconds after I press the button for the screen to actually turn on. This does not happen while charging for me, only on battery. After screen on, the UI runs fine. This also never happened to me when I was on Gingerbread roms.
I am currently running Serendipity 9.2 with Cherrypicker kernal because I like the UI, but I still get the screen-on lag
I have tried ShoStock 2, Foxhound, AOKP, Serendipity 9, Mystic and ShirShirRomICS
and comboed those with all of the different kernals: Siyah, Fluxxi, Cherrypicker and NEAK. All this to no avail
I was wondering if this is only happening to me, because it slightly annoys me that I need to wait, since it makes the phone feel like its not as speedy as it should be.
If somebody can help me solve this I will be SOO GRATEFUL!
Thank you so much!
I forget which thread but entropy said screen delay is about that long now. Its a Samsung thing that can't be worked around
Sent from my SGH-I777 using Tapatalk 2
awww, Hopefully entropy will find a way
Maybe its because its not based on the Official i777 one?
but was it just me or did GB roms not have the delay?
Takes mine an avg of .5 seconds. Sometimes it's almost instant, other times it's near 1 second, but the avg would be close to .5 - I wonder if that will change the longer I've got this phone?
Clay
Sent from my SGH-I777 using XDA
Mine turns on basically instantly
Sent from my SGH-I777 using Tapatalk 2
Nick281051 said:
Mine turns on basically instantly
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
What rom and kernal are you using?
george.z.he said:
What rom and kernal are you using?
Click to expand...
Click to collapse
Fluxii 6/2 and Task's aokp 6/3
Sent from my SGH-I777 using Tapatalk 2
george.z.he said:
awww, Hopefully entropy will find a way
Maybe its because its not based on the Official i777 one?
but was it just me or did GB roms not have the delay?
Click to expand...
Click to collapse
GB had about .5 sec delay. Ics is close to 1 sec
Sent from my SGH-I777 using Tapatalk 2
Mine used to do the same. After a new aokp build 36 Install the lag went away- maybe a coincidence?
Sent from my SGH-I777 using XDA
Try upping your lowest frequency step if you have your min set to 100/200mhz on your governor, change it to 500mhz and see if it stops happening. (Works for me, only happens on certain I/O schedulers and governors however.)
Sent from my SGH-I777 using xda premium
cepsbow said:
Try upping your lowest frequency step if you have your min set to 100/200mhz on your governor, change it to 500mhz and see if it stops happening. (Works for me, only happens on certain I/O schedulers and governors however.)
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Which I/O scheduler and governed do u use?
Sent from my SGH-I777 using xda premium
On demand and noop were the most stable for me. However it varies by device, not all sgs2 are created equal. I would suggest trying a few and see which runs most stable for your phone as the kernels governors vary (I was experiencing this issue with siyah and Neak on various aokp builds (35-37). Conservative/noop & vr with Neak and powersaver & performance / cfq & vr for both on siyah)
Currently on stock aokp 6-3 with tasks kernel, he truly overhauled the kernel, works better than any alternate kernel I've run so far with no issues on any oc/uc/uv settings.
Sent from my SGH-I777 using xda premium
If I recall correctly from the discussion many months ago (I think it was in Entropy's DD kernel thread for GB) there is basically a .65 second delay from power button press to screen on when waking from deep sleep on the SGS2 - and this is a hardware limitation, not software.
When you are seeing quicker screen wakes it is because the device was not in deep sleep at the time of the press of the power button. In the case of waking from a non-deep-sleep condition, probably the lowest idle clock speed or current clock speed (set by whatever background process has the phone awake) will be the controlling factor in how fast the screen wakes up.
I could be completely wrong here...someone please correct me if so...
dandrumheller said:
If I recall correctly from the discussion many months ago (I think it was in Entropy's DD kernel thread for GB) there is basically a .65 second delay from power button press to screen on when waking from deep sleep on the SGS2 - and this is a hardware limitation, not software.
When you are seeing quicker screen wakes it is because the device was not in deep sleep at the time of the press of the power button. In the case of waking from a non-deep-sleep condition, probably the lowest idle clock speed or current clock speed (set by whatever background process has the phone awake) will be the controlling factor in how fast the screen wakes up.
I could be completely wrong here...someone please correct me if so...
Click to expand...
Click to collapse
Then is it possible to turn off deep sleep? And does it drain a lot of battery if it is not in deep sleep?
I realized when playing music or when the BLN notification is on it wakes instantly.
george.z.he said:
Then is it possible to turn off deep sleep? And does it drain a lot of battery if it is not in deep sleep?
I realized when playing music or when the BLN notification is on it wakes instantly.
Click to expand...
Click to collapse
Yes it is possible to turn off deep sleep. There is an app in the market called "wakelocker" or something similar. You can find references to it in the very early ICS ROMs for the i777, as it was used to avoid the random screen-ons we were having. It can be set up to hold a permanent wakelock.
However, you should expect to drain between 5 and 10% battery per hour idle if you are wakelocked all the time. In other words, your battery life will completely tank if you do this. Most people around here do anything and everything they possibly can to prevent wakelocks, as this is the best way to improve device-idle battery life. As someone mentioned in the AOKP thread, screen on delay is a sign of good sleepiness (or something like that - I'm paraphrasing cause I don't want to bother to go look)... If I were you, I'd leave it be...
My SGS2 has a 5-6 seconds delay before waking up from deep sleep. I noticed that after I take the phone away from my ear after a call the screen takes very long to turn back on, as if the proximity sensor is sleeping away.
This is definitely not because of my last firmware update because it simply didn't happen after I installed it. It was just impressively fast. This new behavior started about 3-4 weeks ago, I can't figure out right now whether I installed something that could produce such behavior.
Build number: IML74K.XWLP7
Kernel version: 3.0.15-I9100XWLP7-CL340913 [email protected] #3 (rooted)
Baseband: I9100XXLPS
LE: I have the european version.
pcamlin said:
Mine used to do the same. After a new aokp build 36 Install the lag went away- maybe a coincidence?
Sent from my SGH-I777 using XDA
Click to expand...
Click to collapse
Yeah,mine as well and have no idea if it's a coincidence,seems like an old radio will get back to work after some beats...
Yeah as said above, it is a hardware thing combined with the state of the processor. The reason some people's turn on very rapidly is because their processor is already doing something, aka not sleeping. You should have at minimum probably a half second to maximum 2 second delay from pressing the button to your screen coming on. Otherwise your battery would be terrible.
Sent from my new and improved SGH-I777 with AOKP!
dogfax said:
Yeah as said above, it is a hardware thing combined with the state of the processor. The reason some people's turn on very rapidly is because their processor is already doing something, aka not sleeping. You should have at minimum probably a half second to maximum 2 second delay from pressing the button to your screen coming on. Otherwise your battery would be terrible.
Click to expand...
Click to collapse
How does HTC do it then? My wife's stock Inspire wakes literally instantly, and its idle battery drain is even better than my S2 running AOKP/Fluxi. This is proof to me that Samsung could be designing things a little better...
mattdm said:
How does HTC do it then? My wife's stock Inspire wakes literally instantly, and its idle battery drain is even better than my S2 running AOKP/Fluxi. This is proof to me that Samsung could be designing things a little better...
Click to expand...
Click to collapse
I was just thinking the other day why did I get rid of my Inspire...
Oh yeah... cuz I have a thing for phones