The delay between pressing the power or home key, and the screen coming on is a little frustrating. I will be rooting my sgs2 this weekend but was wondering, after I root and install setcpu, and change the frequency, will the lock screen lag disappear? I've read that the current delay is due to the way the cpu is currently clocked? Can anybody help? Thanks
Sent from my GT-I9100 using XDA Premium App
Just tested this, yep setting the cpu speed higher does make it faster
Sent from my GT-I9100 using XDA App
Excellent. Thanks for your response. I can't wait to get that root goodness on this amazing phone.
Sent from my GT-I9100 using XDA Premium App
It's a little weird that I have to overclock a dual core 1.2 GHZ phone so that it can be instantly unlocked. The delay is pretty big when unlocking especially...
Aldonski said:
It's a little weird that I have to overclock a dual core 1.2 GHZ phone so that it can be instantly unlocked. The delay is pretty big when unlocking especially...
Click to expand...
Click to collapse
Because after being idle for sometime, the SGS2 will downclock to 200MHz (lowest). Use setCPU to increase the lowest possible clockspeed seems 200MHz so abit slow for waking up.
The underclock is a pain because it lags the turning on slightly...but it saves battery life, so I my eyes, it's a winner
mine is instantly here when pressing home or power button...
i am rooted and the overclock kernel is patched but set to default 200-1200MHz
Sent from my overclocked GT-I9100 using XDA Premium App
khein said:
Because after being idle for sometime, the SGS2 will downclock to 200MHz (lowest). Use setCPU to increase the lowest possible clockspeed seems 200MHz so abit slow for waking up.
Click to expand...
Click to collapse
Bought Setcpu, set min to 500 ...still lags on unlock. Set min to 800 ...same problem..
I applied this this and suddenly noticed that the delay is gone, the screen comes on immediately. It is also noticeably quicker to unlock. I'm guessing that the delay is caused by the animation effect Samsung used for screen on/off and that changing it to the stock android approach (Immediate on and crt off) that it now appears snappier. It's not a perfect solution but I'm sure a dev could take a look and see if they could remove the wake up lag while keeping the stock battery/screen off animation if people wanted.
hello guys....
have tried softlocker free, it seems
just that it works, I'm testing, but I check battery power ... sorry for my English
xxxilef said:
hello guys....
have tried softlocker free, it seems
just that it works, I'm testing, but I check battery power ... sorry for my English
Click to expand...
Click to collapse
With softlocker is instant but drain double or more battery in standby...so it isn't a solution for me:-(
Sent from my GT-I9100 using XDA Premium App
beppez82 said:
With softlocker is instant but drain double or more battery in standby...so it isn't a solution for me:-(
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
Have you confirmed this at all? Because when i test it, the battery seems to be more or less the same.
Its true that softlocker keeps the phone alive, but it is still downclocking somehow. Im not sure how it works, but the battery is still decent.
Wanted to test this, but cant read detailed battery drain from the Samsung driver.
Hollow.Droid said:
I applied this this and suddenly noticed that the delay is gone, the screen comes on immediately. It is also noticeably quicker to unlock. I'm guessing that the delay is caused by the animation effect Samsung used for screen on/off and that changing it to the stock android approach (Immediate on and crt off) that it now appears snappier. It's not a perfect solution but I'm sure a dev could take a look and see if they could remove the wake up lag while keeping the stock battery/screen off animation if people wanted.
Click to expand...
Click to collapse
I use this framework and still have the lag.
zxz0O0 said:
I use this framework and still have the lag.
Click to expand...
Click to collapse
+1 here btw with softlocker from market help a lot but drain much battery in idle
Sent from my GT-I9100 using XDA Premium App
i tried using widgetlocker (v1.2.4) and the delay is gone. now my screen powers on in an instant even when not connected to a charger, even if the screen has been off for more than 15minutes.
my rom is Lite'ning Rom v6.1 (if this info helps...)
Update: i reflashed lite'ning rom after trying other roms. but the lag came back. i don't know what i did before to fix it. i can only remember that with all my apps installed with lite'ning rom and using it for 2 days, i just installed widgetlocker and the lag was gone. But now i can't restore it
Related
Am I doing something wrong? No matter what I do. I cannot get setcpu to cap at 1200Ghz, it always resets to 1300Ghz. No matter what rom I use it wont stay set. It always resets
Sent from my MB860 using xda premium
Do you have the "set at boot" box checked off?
If so, under Settings > CyanogenMod Settings > Performance do you have the CPU set at 1200 and have set at boot checked off?
DK
I hope someone corrects me if I'm wrong, but I believe there may be a bug with SetCPU. You can try CPU Tuner or that other app which does the same thing to confirm.
In any event, you may be able to circumvent it by setting up a profile. Just an idea. Let us know how it goes!
Maybe a bad version of setcpu or oc kernel. I haven't had any issues but I'm on HomeBase and have setcpu limits on screen off 216/456 and battery <50 1000. Been working superb I must say.
I use CPU Master and haven't had any issues at all.
Sent from CM7 Pre-Beta 4 on Atrix 4G.
No problems with setCPU. Just check off "apply at boot"
Hmm,i have the same issue with stock 2.3.4, setCpu and both faux or kholks kernel,very weird, i will try profiles, later today.
Same here, I have mentioned it many times and actuallly thought I was the only one.
Sent from my Tab using a pigeon.
Ok, i just tried the profiles and still to no avail. Very weird and rather annoying
I've also mentioned this a few times and have since moved back to 0.1.7
Try wiping setCPU's data from the manage applications menu.
Nope, same thing happens. The interesting thing is that if I cap it at 800 MHz, it tops up at that. Any step higher and the cap doesn't work.
Sent from my MB860 using Tapatalk
drdino said:
Nope, same thing happens. The interesting thing is that if I cap it at 800 MHz, it tops up at that. Any step higher and the cap doesn't work.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Very odd. You could also try wiping cache and dalvik if you haven't already.
Have you had this issue with any other ROMs?
I am more or less having the same issue. The annoying thing is that sometimes it would work but sooner or later, after a reboot, or changing the settings, it would go off again.
One thing that seeme to help is to set both slides to the min setting then just move one slide at a time, one click at a time and wait a few seconds between changes, till you get the settings you want... did not always work but it did more often then not.
I am going to try cpu master see if that does work for me.
Yeah it's weird. Whether it sticks or not seems totally random.
Hi, I'm on stock 2.3.4 and tried using CPU Tuner, it seems the kernel still won't act accordingly to the max cap I set.
Just like when I use SetCPU, even with the slider set max to 1000 and "Set on boot" ticked, it still jumps to 1300 sometimes.
So the problem could be with kernel, but I don't really know
bapaogoreng said:
Hi, I'm on stock 2.3.4 and tried using CPU Tuner, it seems the kernel still won't act accordingly to the max cap I set.
Just like when I use SetCPU, even with the slider set max to 1000 and "Set on boot" ticked, it still jumps to 1300 sometimes.
So the problem could be with kernel, but I don't really know
Click to expand...
Click to collapse
That's what I figure. I've tried everything.
Sent from my Atrix using XDA Premium
amwbt said:
That's what I figure. I've tried everything.
Sent from my Atrix using XDA Premium
Click to expand...
Click to collapse
Here's the good news:
http://forum.xda-developers.com/showthread.php?p=17575166#post17575166
drdino said:
Nope, same thing happens. The interesting thing is that if I cap it at 800 MHz, it tops up at that. Any step higher and the cap doesn't work.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Had the same problem with my atrix when I had one, prevented me from using any oc kernel.
Sent from my GT-I9100 using xda premium
bapaogoreng said:
Here's the good news:
http://forum.xda-developers.com/showthread.php?p=17575166#post17575166
Click to expand...
Click to collapse
Very good info. Thanks for posting! Greatly appreciated.
Sent from my SGH-I897 using xda premium
I am running faux's newest kernel on my att atrix, Allen build 4. I've noticed that upon cold reboot, the frequency scales correctly. after a while however, the phone stays at the max frequency. I've tried stopping running archives that I thought might be causing this, hit it doesn't help. Is it the kernel?
Sent from my MB860 using xda premium
You have a misbehaving process
turl1 said:
You have a misbehaving process
Click to expand...
Click to collapse
That's what I thought originally, but after killing all the apps that were running, it still stayed at the frequency.
I have a hypothesis, and i'm going to test it in a second. I think that when I plug my phone into my laptop dock, it for some reason locks the frequency at max.
EDIT: It's the webtop mode. If I plug the phone into my laptop dock, and open the laptop, the frequency is locked at maximum frequency. I'm going to flash the stock kernel again, and see what happens next.
EDIT2: So it's definitely faux's newest kernel. It might just be me, but it definitely is locking to max frequency. Stock does not have this problem.
Sent from my MB860 using xda premium
paravorheim said:
That's what I thought originally, but after killing all the apps that were running, it still stayed at the frequency.
I have a hypothesis, and i'm going to test it in a second. I think that when I plug my phone into my laptop dock, it for some reason locks the frequency at max.
EDIT: It's the webtop mode. If I plug the phone into my laptop dock, and open the laptop, the frequency is locked at maximum frequency. I'm going to flash the stock kernel again, and see what happens next.
EDIT2: So it's definitely faux's newest kernel. It might just be me, but it definitely is locking to max frequency. Stock does not have this problem.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
I have seen the same behaviour. Just got my HD Dock yesterday. When I pulled it out it was warm/hot. I thought it was just the clock/screen using power or whatever. Then I opened SetCPU while in the dock and it showed a constant 1000Mhz. When I unplug it still shows that frequency. Too bad
use the auto detect button again#
Sent from my MB860 using xda premium
ltdanno360 said:
use the auto detect button again#
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Thanks, I'll try it out in the morning, and report back.
Sent from my MB860 using xda premium
I think this is a known issue with faux's new kernel. When you place the phone into a laptop dock it clocks the CPU at max until a reset. I guess the same thing happens with any dock
Sent from my MB860 using xda premium
i have recently made a decision to delete the set cpu and install cpu masters from the market ,i think so for after 24 hours i think it does make a difference um
i notice lower temps even after an hour of useing the webtop or just an average temp overall i am useing the faux 2.0 kernal 1.3 oc but its set at 1.2
my profiles are screen off 456 max-216-min
the rest are 1200max 216-min
Sent from my MB860 using xda premium
I don't have a dock but I just installed _unknown's hdmi/webtop mod while running faux's enhanced stock 0.2.0. Noticed my phone was really hot after trying it out, even with the screen off and noticed a constant 1000 max. in setCPU.
Cleared my cache & dalvik, reinstalled kernel, jugg's battery fix, cleared my battery stats, rebooted into recovery (figured it wouldn't hurt since it defaulted to that option), then fixed permissions and restarted. Everything seems to be back to normal.
Will see what happens when I run the webtop again and report back later. Currently CPU is showing 36C and battery is at 32C. Are these acceptable temps?
After calibrating, draining and recharging and wiping stats a thousand times, this is what I get:
https://lh5.googleusercontent.com/-...9zLfSiSGJ_Q/s512/screenshot-1321359229108.png
Wtf is that crap?
Sent from my PocketDock
Rouge app, or bad battery
Sent from AT&T SGS2
Viamonte said:
After calibrating, draining and recharging and wiping stats a thousand times, this is what I get:
https://lh5.googleusercontent.com/-...9zLfSiSGJ_Q/s512/screenshot-1321359229108.png
Wtf is that crap?
Sent from my PocketDock
Click to expand...
Click to collapse
2 hours of screen time there, that seems about normal to me. I'm lucky if I squeeze out 3 hours of screen time throughout the day.
Sent from my MB860 using Tapatalk
It depends entirely on what you are doing. 2 hours of screen time (even in ideal conditions) will most likely get through half of your battery.
What screen brightness settings do you use?
What were you doing with the "screen on"? (i.e. gaming, video etc).
What kernel do you use? Try the Faux 1.0 Ghz kernel (if not already) and consider undervolting.
I imagine with the combo of Faux's stock kernel, undervolting and perhaps reducing screen brightness will see 5ish hours of screen time.
It was on around 85% brightness due to being under direct sunlight.
My kernel is faux's 1.45 for CM
Over 80% of the time the clock was around 200, 400MHZ as stated by SetCPU, and both those clocks are undervolted by 50.
I was browsing the whole time.
Viamonte said:
It was on around 85% brightness due to being under direct sunlight.
My kernel is faux's 1.45 for CM
Over 80% of the time the clock was around 200, 400MHZ as stated by SetCPU, and both those clocks are undervolted by 50.
I was browsing the whole time.
Click to expand...
Click to collapse
Wow no wonder. Roaming for 2 hours with brightness nearly on full will definitely drain your battery.v Plus the 1.45 Ghz kernel overclocks the RAM and GPU also. You might want to get an anti glare screen-protector and flash the 1.3 Ghz kernel and use wifi.
I'm on the nightlie 18
Sent from my MB860 using xda premium
rog1121 said:
Wow no wonder. Roaming for 2 hours with brightness nearly on full will definitely drain your battery.v Plus the 1.45 Ghz kernel overclocks the RAM and GPU also. You might want to get an anti glare screen-protector and flash the 1.3 Ghz kernel and use wifi.
Click to expand...
Click to collapse
Umm... wifi wasn't an option back there, and I don't use screen protectors. BUT I didn't know that bit of fact from faux's kernel, I'll put in the 1.3
BTW, Green power pro does help a ****load on keeping battery alive.
ps: anyway to control RAM and GPU clocks the way we do with SetCPU with the... well... cpu?
msd24200 said:
I'm on the nightlie 18
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Why don't u go to a stable version and see if the battery drain continues there also ? You can always create backups to restore right ..
Sent from my MB860 using Tapatalk
Welcome to cm7. I'm lucky to get 10 hours light usage with faux 1ghz kernel undervolted with a screen off profile of 216-216mhz.
Sent from my MB860 using XDA Premium App
jimmer411 said:
Welcome to cm7. I'm lucky to get 10 hours light usage with faux 1ghz kernel undervolted with a screen off profile of 216-216mhz.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Have you tried installing better battery stats and CPU spy to see if you have a rogue app? You should be getting significantly better battery life. How is your cell signal?
Sent from my GT-P7310 using Tapatalk
anupash said:
Why don't u go to a stable version and see if the battery drain continues there also ? You can always create backups to restore right ..
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Lol it is stable and my battery life is great
Sent from my MB860 using xda premium
I don't believe setcpu functions correctly for dual core devices, I remember reading, albeit a while ago, setcpu only effects 1 core, leaving the second untamed.
Please correct me if I'm wrong. Stock cm kernel has plenty of ass behind it, no ones playing bf3 on their handsets....yet...
Sent from my MB860 using xda premium
In all actuality, android isn't optimized for dual core devices either. ICS will be.
Sent from my MB860 using xda premium
termleech said:
Have you tried installing better battery stats and CPU spy to see if you have a rogue app? You should be getting significantly better battery life. How is your cell signal?
Sent from my GT-P7310 using Tapatalk
Click to expand...
Click to collapse
Watchdog shows the suspend process and android media process taking up about 30% usage constantly. Signal is strong when I'm at work, constant 4-5 bars H+
Even after a full wipe and clean install of CM7 those same processes throw up alerts immediately, I will get al alert for the suspend process every few mins.
Background data off, no email syncing or anything. I'm lucky to get 3 hours screen on time or pandora streaming. I bought a new Motorola battery about a month ago and I don't use GPS or wifi.
Running stock, aura or homebase and the drain is gone... they aren't any good IMO tho.
For now I'm carrying a spare charger everywhere I go till the nexus prime is released.
Sent from my MB860 using XDA Premium App
JaronBang said:
In all actuality, android isn't optimized for dual core devices either. ICS will be.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
ICS is still android lol
I know what you meant though. Just saying
I'm gonna change that fugly homescreen wallpaper cause I think it looks like crap.
http://www.google.com/search?q=gala...isch&tbs=simg:CAESEgm_1ROHEuoqj2yEwgptZq7y50Q
I'm going to see how far I can overclock my specific device stably
danielsf said:
I'm going to see how far I can overclock my specific device stably
Click to expand...
Click to collapse
overclock that monster CPU? For which reason if it's just Blazing fast and no lagg at all ? Just to consume more battery?
the first thing i will do is using browser and see how beautifull is surfing web with this incredible device
No reason not to make it faster i say. Not needing something is no reason not to.
Sent from my LG-P920 using xda premium
hefonthefjords said:
No reason not to make it faster i say. Not needing something is no reason not to.
Sent from my LG-P920 using xda premium
Click to expand...
Click to collapse
Battery life.
ale0crysis said:
overclock that monster CPU? For which reason if it's just Blazing fast and no lagg at all ? Just to consume more battery?
the first thing i will do is using browser and see how beautifull is surfing web with this incredible device
Click to expand...
Click to collapse
Firstly, it's mainly just out of curiosity, I just want to see how far me device can go. Also, take my SGS2 for example, stock 1.2ghz, at the end of the day when I put it in to charge at about 9pm, I am left with about 20%+ battery. In my opinion that is useless battery life, as it is not enough to get through the next day, so it is just being wasted. So to overclock to 1.4 or 1.5ghz on my s2 to increase speed and battery life isn't an issue at all, why shouldn't I gain the extra speed? Same will hopefully apply to the SGS3
I can easily get to 1.6ghz at 1375mV and it's rock stable, but I do notice a battery drain when that high. It's all about personal balance between performance, heat generated by OC'ing and battery, for me 1.5ghz is the sweet spot for all three. Also I do heavily under-volt both cpu & gpu. My GPU isn't overclocked as their isn't a game that taxes it at stock, but it's nice knowing I can OC the GPU perfectly stably & safely to 400mhz from 267mhz and get a sizable performance boost, if I ever need it in the future.
turn it on?
Sent from my iPhone using Tapatalk
Take it out of the box!
Do a little dance!
watch it
Try to smash it and see how hard it takes to break, and then buy another one
Post here
ROOT it . (If available)
Sent from my SAMSUNG-SGH-I717 using XDA
Make a phone call to see if it works.
No honestly... it's also a phone...
Do a drop test
Sent from my GT-I9100 using xda premium
Hold it on my hand for 10minutes and then get it rooted.
Sent from my Incredible S using XDA
Arsaw said:
Hold it on my hand for 10minutes and then get it rooted.
Sent from my Incredible S using XDA
Click to expand...
Click to collapse
+1
Skickat från min GT-I9000 via Tapatalk 2
Erahgon said:
Make a phone call to see if it works.
No honestly... it's also a phone...
Click to expand...
Click to collapse
Its a what now???
Sent from my GT-I9000 using XDA
Make love to it
Say 'Hi Galaxy'
Hi All,
Want to share with you, experimented the XXLT5 on GTN7000. Superb ROM....so far no issues....you name it, it works fine. Note the downloaded file is above 1GB...seems this has all the fixes required. You can root it as well....if any issues found on this stock rom do let me know....will be interested to catch the bug.
Link for download...http://www.hotfile.com/dl/213299077/83496c8/N7000XXLT5_N7000OXXLT2_XEH.zip.html
Link for root : http://d-h.st/GiO
Installation...as usual....Odin...so have a latest pack..open, select the PDA and good to go.
the hotspot works?
aftabbabar said:
the hotspot works?
Click to expand...
Click to collapse
Yes...works fine.
I'm running N7000XXLT4 as my build -- is this simply an improved update that just hasn't hit my German unit yet?
And what's better in this LT5 from LT5 posted on may 7th? http://forum.xda-developers.com/showthread.php?t=2267748 Why we need another thread?
...from SG NOTE N7000 with Tapatalk 2
Murshad007 said:
I upgraded ota from Gb to Ics. And i do a factory reset before. Then on ics i didnd factory due to brick bug. And ota update to JB UAE version. My cpu is always 15-35 % on idle and above 60% with any applictation like Google+ or Hangout..
I did wipe cache and factory reset in recovery.
Now i flashed LT5 And wipe and factory before and after. But still the same?
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Do you have a cracked screen? My CPU idled quite high when my screen was cracked.... Did you also experience the above problems with CyanogenMod?
Screen not cracked, outer body have some cracks. Phone is running smooth in gb and Ics
Sent from my GT-N7000 using xda app-developers app
hotweiss said:
Do you have a cracked screen? My CPU idled quite high when my screen was cracked.... Did you also experience the above problems with CyanogenMod?
Click to expand...
Click to collapse
Cm10.1 nighties 29 06 2013 same issue.. Although phone not hanged up.. But CPU usage around 35-65% without any heavy usage
Sent from my GT-N7000 using xda app-developers app
Murshad007 said:
Cm10.1 nighties 29 06 2013 same issue.. Although phone not hanged up.. But CPU usage around 35-65% without any heavy usage
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Something must be wrong with the phone if you have such a high CPU usage after a fresh install. Send it in for servicing.
hotweiss said:
Something must be wrong with the phone if you have such a high CPU usage after a fresh install. Send it in for servicing.
Click to expand...
Click to collapse
first, whats your upgrade procedure, try without restoring stuff and let os settle in. restoring app+data usually causes this with me.
Also what app do you use for measuring cpu usage. That may be off for some reason. Also note cpu utilization v. s. governor. Example on demand scales up frequency when e. g. uses 80%, so it will seem high, but in regard to frequency it is not. Due to battery savings lower frequencies are used, until 80% frequency is reached before going to a higher frequency, thus for same task higher utilization of that frequency it may not be a bad indication is what I am saying.
Now a rom usually needs some time to synch, perform breakin tasks, scan all media etc, try to see through settings, development options then cpu utilization what is utilizing cpu. Maybe app has gone bad, rogue, or maybe its expected.
M using CPU Z, thanx for utilization info
Sent from my GT-N7000 using xda app-developers app
Murshad007 said:
M using CPU Z, thanx for utilization info
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
your welcome, you can check also cooltool, that has a nice overlay you can position anywhere. You can configure and show e.g. frequency, cpu utilization, temp(battery I think), pretty fun.
Sent from my GT-N7000 using Tapatalk 2