When the phone screen is off, (not the phone) do you guys seem to press the power button to wake the phone up and it doesn't work, the home, menu, back, and search touch buttons light up but the screen remains on sleep and when I try the lock patter it does vibrate as if the screen was on, and when I press the power button again the screen lights up for an instant and shuts down and you can see it unlocked!. This has happen on every G2 I have had.
T-Mobile G2 1.42 GHZ
Do you have a set CPU profile that's really low for screen off? That seems to be a issue for some people
Sent from my 'SilverBullet' HTCDesireZ running CM7
deliriousDroid said:
Do you have a set CPU profile that's really low for screen off? That seems to be a issue for some people
Sent from my 'SilverBullet' HTCDesireZ running CM7
Click to expand...
Click to collapse
Nop, I have it running @ 1.42ghz all the time, no low profiles
T-Mobile G2 1.42 GHZ
try underclocking a bit and problem solved or removing the screen on CRT animation
i love the animation so much that i havent overclock more than 1.3ghz cause the issue starts above that
Which rom are you using?
Sent from my HTC Vision using XDA App
LGS1231 said:
Which rom are you using?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Stock rom
T-Mobile G2 1.42 GHZ
androidfeen809 said:
Stock rom
T-Mobile G2 1.42 GHZ
Click to expand...
Click to collapse
I thought 806MHz was the Max for stock
Sent from my 'SilverBullet' HTCDesireZ running CM7
deliriousDroid said:
I thought 806MHz was the Max for stock
Sent from my 'SilverBullet' HTCDesireZ running CM7
Click to expand...
Click to collapse
806 MHz is the max for the stock ROM, but if you're rooted with a custom kernel you can up it to the max the kernel allows. However I don't understand why anyone would keep their phone running at max speed with absolutely no throttling... it's a pretty big waste of battery and kernel capability
Related
removed.
Yes it does, it doesn't need to run on ghz speed to wake up fast.
Sent from my HTC HD2 using XDA App
JoonatanO said:
Yes it does, it doesn't need to run on ghz speed to wake up fast.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
If it doesn't need to run on ghz speed to wake up fast then why does it stay on?
-----------------------------------------------------------------------
Actually setcpu will stay on or shut off depending on the settings.....
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
Went to use my tablet this morning and it was stuck on the lockscreen, it was completely un- responsive. I rebooted it by holding the power and volume down. It worked ... But only having this tablet for under a week, should i take it back , and is this a hardware issue? I'm running 3.1 on it, should I Exchange it? Or is there a fix?
Sent from my Inspire 4G using XDA Premium App
robertmoore208 said:
Went to use my tablet this morning and it was stuck on the lockscreen, it was completely un- responsive. I rebooted it by holding the power and volume down. It worked ... But only having this tablet for under a week, should i take it back , and is this a hardware issue? I'm running 3.1 on it, should I Exchange it? Or is there a fix?
Sent from my Inspire 4G using XDA Premium App
Click to expand...
Click to collapse
Sounds like a rogue app.
Hmmm.... Could be? I'm an avid ROM flasher when it comes to my phone, my tablet I'm pretty much noob. I'll check that.. I was also thinking maybe the set cpu was too high?
Sent from my Inspire 4G using XDA Premium App
robertmoore208 said:
Hmmm.... Could be? I'm an avid ROM flasher when it comes to my phone, my tablet I'm pretty much noob. I'll check that.. I was also thinking maybe the set cpu was too high?
Sent from my Inspire 4G using XDA Premium App
Click to expand...
Click to collapse
What is your CPU set at?
I am running richardtrip's kernel, Max set to 1504, min set to 216 and all is fast and stable.
I'm running the honey villain ROM, 1000 max 216 min..
Sent from my Inspire 4G using XDA Premium App
robertmoore208 said:
I'm running the honey villain ROM, 1000 max 216 min..
Sent from my Inspire 4G using XDA Premium App
Click to expand...
Click to collapse
That's not over clocked - afaik, that's stock clock speed.
robertmoore208 said:
I'm running the honey villain ROM, 1000 max 216 min..
Sent from my Inspire 4G using XDA Premium App
Click to expand...
Click to collapse
im running the same but at over 1600. something doesnt sound copasetic.
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 was comparing the screen on my Vibrant with the screen on my Nexus S, and I was noticing how yellow the Nexus S screen is. Anyway to fix this with a kernel? I am running the stock ota.
Sent from my Nexus S
Smokexz said:
I was comparing the screen on my Vibrant with the screen on my Nexus S, and I was noticing how yellow the Nexus S screen is. Anyway to fix this with a kernel? I am running the stock ota.
Sent from my Nexus S
Click to expand...
Click to collapse
fixed! the Trinity TEI6S kernel http://goo.gl/QAuKi
im running this on a stock/rooted 4.0.3 rom, and it runs great. the Trinity kernels have their own color. more white. less dirty yellow. its undervolted/underclocked with an overclocked bus/gpu of 220mhz. its friendly to the battery yet very quick.
I was upset last 3 days cause the yellow color of my nexus s screen( absolutely worst than my vibrant ). With new kernel, i now can enjoy my Super Amoled screen again. Thanks. However, i still have the green screen flicker issue. Hope it can be fixed in future update.
Trinity does not work on all phones. Mine for example:/
Sent from my Galaxy Nexus Sep using Tapatalk
Shark_On_Land said:
Trinity does not work on all phones. Mine for example:/
Sent from my Galaxy Nexus Sep using Tapatalk
Click to expand...
Click to collapse
Just use any kernel that has voodoo color
I'm using glados
Sent from my Nexus S using xda premium
Shark_On_Land said:
Trinity does not work on all phones. Mine for example:/
Sent from my Galaxy Nexus Sep using Tapatalk
Click to expand...
Click to collapse
Mine either
Sent from my Nexus S 4G using xda premium
demo23019 said:
Just use any kernel that has voodoo color
I'm using glados
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Just wondering what settings you're using in Voodoo to correct the yellow color?
I have GLaDOS v2.4 and I'm running the Voodoo color profile and left everything else alone. However, in white areas, there still seems to be a yellowish tint.
Flash kernel that support vodoo..then discuss here..
http://forum.xda-developers.com/showthread.php?t=1401759
simms22 said:
fixed! the Trinity TEI6S kernel http://goo.gl/QAuKi
im running this on a stock/rooted 4.0.3 rom, and it runs great. the Trinity kernels have their own color. more white. less dirty yellow. its undervolted/underclocked with an overclocked bus/gpu of 220mhz. its friendly to the battery yet very quick.
Click to expand...
Click to collapse
Installed it, it gave me a green screen and Voodoo control does not work.... so I will try Glados kernel. By the way I also tried the Trinity kernel on the thread, but when I installed that it didn't even let my phone start up.
Sent from my Nexus S
I bounce between GLaDOS and Matr1x and voodoo.
I prefer how glados operates with my phone and sph33r ics rom, but the random reboots are an annoyance.
Matr1x doesn't cause my phone to reboot, plus it features SmartassV2, but BLD and 100mhz min don't work for me Wish there was one perfect kernel for ics, like FrancoFrancisco was for gingerbread.
Braneless said:
I bounce between GLaDOS and Matr1x and voodoo.
I prefer how glados operates with my phone and sph33r ics rom, but the random reboots are an annoyance.
Matr1x doesn't cause my phone to reboot, plus it features SmartassV2, but BLD and 100mhz min don't work for me Wish there was one perfect kernel for ics, like FrancoFrancisco was for gingerbread.
Click to expand...
Click to collapse
Yeah I just got a random reboot, what's this Matr1x you speak of? Is it good? BLN?
Sent from my Nexus S
Smokexz said:
Yeah I just got a random reboot, what's this Matr1x you speak of? Is it good? BLN?
Sent from my Nexus S
Click to expand...
Click to collapse
Matr1x v13.0 ics kernel by Mathkid95. It runs very quickly, smoothly, and no reboots whatsoever.
It features bln, bld, SmartassV2, it's undervolted, but does not include deep idle in these latest releases.
Try it!
Ive disabled deep idle by default due to wake problems
100mhz min works for me with setcpu
I will look into bld
Sent from my Nexus S using XDA App
mathkid95 said:
Ive disabled deep idle by default due to wake problems
100mhz min works for me with setcpu
I will look into bld
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Runs great, bln works fine and no random reboots! Thanks! By the way is there to get rid of the flash after locking the screen? It's very annoying.
Sent from my Nexus S