Related
Im wondering if anybody can attest to the stability and reliability as well as safety concerns with running a galaxy s phonew at 1200 mhz. I see a lot oflash kernels boasting this overclock. Thanks in advance
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Flash and find out. If it doesn't freeze, your good. Some phones can't handle the oc. There's really no grey area, it will either be stable, or it won't. 1.2 is the standard, and is probably the safest. I'm at 1.48 and stable.
Sent from my SGH-T959 using XDA Premium App
I'm mainly concerned for overheating as I've cooked a couple pc processors
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Use setCPU and set up a temperature profile. I have mine set so when the phone hits 120 F, the processor scales down to stock clock speed and cools off.
Dan_Brutal said:
Flash and find out. If it doesn't freeze, your good. Some phones can't handle the oc. There's really no grey area, it will either be stable, or it won't. 1.2 is the standard, and is probably the safest. I'm at 1.48 and stable.
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
What kernel your using?
Sent from my GT-I9000 using XDA App
Bullet[EDT]
U will not have any heat issues unless ur charging ur phone. When u charge a galaxy s phone ur gets very warm including in stock speeds
Definitely. The Infuse 4G has the same hummingbird chip overclocked to 1.2 ghz by default, so it should run with no issues. I can doing 1.3 ghz with no problem. Can't hit 1.4 though.
Sucks since my last phone could handle 1.6 ghz (through a custom 1.6 ghz DOW kernel, thanks Morific!).
It is safe but you lose battery life so that didn't work for me but it is safe and no overheating issues
Dunno what Kernel i used but it was by Morific, and was discontinued for being unstable, but my phone has been able to go up to 1.4, they tried a 1.6 but was far too unstable or something.
xriderx66 said:
Dunno what Kernel i used but it was by Morific, and was discontinued for being unstable, but my phone has been able to go up to 1.4, they tried a 1.6 but was far too unstable or something.
Click to expand...
Click to collapse
I think the Manhattan project messes with the environmental properties of the phone or something.
Sent from my SGH-T959 using XDA Premium App
Dan_Brutal said:
I think the Manhattan project messes with the environmental properties of the phone or something.
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
Yes, the Manhattan project was a dud since it never really overclocked the device. In fact it only slowed it down.
But I requested a 1.6 ghz version of the DOW kernel from Morific, just for fun. Surprisingly it worked well with my old device.
advanttage said:
Im wondering if anybody can attest to the stability and reliability as well as safety concerns with running a galaxy s phonew at 1200 mhz. I see a lot oflash kernels boasting this overclock. Thanks in advance
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
That depends on the phone a lot. I know lots of people who use 1200 but I did with Overstock and Tigers Blood and my phone would freeze. Also use set cpu for the same side to keep an eye on temp.
Sent from my GT-I9000 using XDA Premium App
I've had no problems oc'in, but it really does depend on your chip. Been running mine at 1420 for a week, super stable never gone above 29c under load. IMO, just have to give it a shot and see how stable it is for you.
I'm using Bullet and have been getting great battery life even with it fully OC'd. About 20-25 hrs with moderate use.
CrazyCharlie said:
I'm using Bullet and have been getting great battery life even with it fully OC'd. About 20-25 hrs with moderate use.
Click to expand...
Click to collapse
+1... im using Bullet with it tapped out and get pretty good battery life.
Can I get a link to Bullet? I've never seen it.
Can't not allowed to post the link to bullet....EDT's Site.
CrazyCharlie said:
I'm using Bullet and have been getting great battery life even with it fully OC'd. About 20-25 hrs with moderate use.
Click to expand...
Click to collapse
With what rom??
Overclocked mine to 1.48 and been running stable for a few weeks now...
Sent from my GT-I9000 using XDA Premium App
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
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
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.
My nexus 7 keeps under clicking itself to 1.5GHz from anything.
I have stock rooted with Trinity kernel 4.2 using tkt to over clock anyone have any tips
Sent from my Nexus 7 using xda app-developers app
maxjivi05 said:
My nexus 7 keeps under clicking itself to 1.5GHz from anything.
I have stock rooted with Trinity kernel 4.2 using tkt to over clock anyone have any tips
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
It's called 'saving power'.
As long as it doesn't lag and clocks itself up to maximum when required, there's nothing to worry about.
Or you can get some CPU clock app and set it on maximum performance. But don't be surprised if you can boil eggs on it then and the battery dies in 2 hrs :good:
issak42 said:
It's called 'saving power'.
As long as it doesn't lag and clocks itself up to maximum when required, there's nothing to worry about.
Or you can get some CPU clock app and set it on maximum performance. But don't be surprised if you can boil eggs on it then and the battery dies in 2 hrs :good:
Click to expand...
Click to collapse
I ran my N7 at 1.7 (using Trinity) without any heating problems. Battery life was acceptable.
Sent from my Nexus 7 using xda premium
Found out it was power Hal script I ran fixed now!
--
NVM removed it now it Underclocks to normal 1.3 GHz from any Freq!!! Why....
Sent from my Nexus 7 using xda app-developers app
maxjivi05 said:
Found out it was power Hal script I ran fixed now!
--
NVM removed it now it Underclocks to normal 1.3 GHz from any Freq!!! Why....
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
clear the data for tkt and reboot. if you are using tkt, you dont need a powerhal script, since tkt runs it automatically after opening it.
Does Tegra 3 really need overclocked? Having used Tegra 2 I can say that could definitely use a little bump but so far T3 is keeping up with me and I can see a big difference between T2 and T3. Makes me wonder what T4 Wayne has in store.
edge929 said:
Does Tegra 3 really need overclocked? Having used Tegra 2 I can say that could definitely use a little bump but so far T3 is keeping up with me and I can see a big difference between T2 and T3. Makes me wonder what T4 Wayne has in store.
Click to expand...
Click to collapse
does it need it.. probably not. do we want to overclock anyways.. yes! btw, its underclocked by default(its rated to 1.5ghz). i use it at 1150mhz as a daily btw.