Related
Hi. My question us what CPU speed can I use before the desire s takes damage? Thanks
Sent from my HTC Desire S using XDA Premium App
Would not go over 1200mhz for general use but in the end it comes down to heat and chip quality. Some chips will run faster and produce less heat then others, you'll have to test yours! Don't over volt even if it is possible?
That's about all I can give you on the matter.
Sent from my HTC Desire S using XDA App
um... just a quick question... why do You need more power? I mean what for??
n64 and psx emulators - full speed, gameloft's dungeon hunter 2 and rainbow six - smooth as my wifes ass, all the flash movies on web or divx offline - no problem, general use - as good as gingerbread can deliver.
I was thinking about which dual core beast shall I buy and ended up with this pocketable and powerful beauty.
... back to the topic - I wouldn't overclock it over 1.5 ghz, even then only for demanding tasks. battery life would decrease as well and I wouldn't trade that for a bit more fps.
Okay. Thank you guys
Sent from my HTC Desire S using XDA Premium App
bronx said:
um... just a quick question... why do You need more power? I mean what for??
n64 and psx emulators - full speed, gameloft's dungeon hunter 2 and rainbow six - smooth as my wifes ass, all the flash movies on web or divx offline - no problem, general use - as good as gingerbread can deliver.
I was thinking about which dual core beast shall I buy and ended up with this pocketable and powerful beauty.
... back to the topic - I wouldn't overclock it over 1.5 ghz, even then only for demanding tasks. battery life would decrease as well and I wouldn't trade that for a bit more fps.
Click to expand...
Click to collapse
Good response, I bought a Desire S recently too and feared the "single core" 1 GHz CPU wouldn't be much faster than my Legend clocked at 768 MHz, after all it is only 232 MHz difference. Couldn't have been more wrong. The phone is a beast.
1.2 ghz is a good speed if you wanna overclock (& also this speed is more than enough)
1.4-1.5 ghz is the limit, anything more than that is very unstable and can cause damage to your cpu
Hey guys. I have a Desire HD. Although they're different phones, i'm sure the internals are almost exactly the same, bar few differences. As such, the cpu should also be the same. I tried out different cpu speeds. I kept my phone at 1.72ghz for a couple of weeks. The phone got pretty hot when using Wifi and such, but didn't get too hot. I'd say the safe point is 1.5ghz but at the stock voltage. Works for me, should work for you guys too I can get 1.7ghz at 1325mv, which is good enough for me I didn't get random crashes etc. My persona highest on this phone was around 2.1 ghz, which was insanely high, the phone was super fast, but got hot blazing hot and the phone started flashing orange led lights and then shut down for like 10 minutes straight. I thought it was gone but...nope, was lucky thank god LOL
Always be careful. If you have insurance, then go ahead and by all means clock the hell out of it if you don't mind a decrease in battery life. But if you have no insurance, and bought it sim-free...i'd suggest 1.3ghz...better be safe than sorry, wouldn't you agree?
the phone started flashing orange led lights and then shut down for like 10 minutes straight. I thought it was gone but...nope, was lucky thank god LOL
Click to expand...
Click to collapse
Haha, bet that was a ball-shrinking moment. Made me laugh reading it.
But seriously, considering the potential damage & the native performance of the DS you wouldn't want to go crazy really.
Sent from my HTC Desire S
Hi!
I succesfully overclocked my DS to 1,5GHz(first to 1,3GHz, than to 1,4GHz), and it's fully stable with stock voltages. I use virtuous unity 1.29.0, and tweaked the built in OC daemon. Tested with stability test v1.5, and no problems after 30 minutes. Temperature is around 40 C(plugged in, charging, and running stability test).
What do you think, can I use it for 24/7? The temperatures are not high, and the phone is rock stable, so is it safe?
Thanks for answer.
ffodi said:
Hi!
I succesfully overclocked my DS to 1,5GHz(first to 1,3GHz, than to 1,4GHz), and it's fully stable with stock voltages. I use virtuous unity 1.29.0, and tweaked the built in OC daemon. Tested with stability test v1.5, and no problems after 30 minutes. Temperature is around 40 C(plugged in, charging, and running stability test).
What do you think, can I use it for 24/7? The temperatures are not high, and the phone is rock stable, so is it safe?
Thanks for answer.
Click to expand...
Click to collapse
why do you need to run it on 1.5ghz? it is very fast at 1.2ghz
& also 1.5ghz will consume more battery & if you put some load on the cpu like a little gaming or a lot of browsing it can get heated up
overclocking more than necessary isnt good as there can be hidden damage to the chip(even if the processor doesn't get heated up)
read post #3 here
so always go easy on the overclocking
kartkk said:
why do you need to run it on 1.5ghz? it is very fast at 1.2ghz
& also 1.5ghz will consume more battery & if you put some load on the cpu like a little gaming or a lot of browsing it can get heated up
overclocking more than necessary isnt good as there can be hidden damage to the chip(even if the processor doesn't get heated up)
read post #3 here
so always go easy on the overclocking
Click to expand...
Click to collapse
Thanks for the answer! I overclocked it to 1,5GHz becouse I like it if everything is fast as lightning.
I know it can consume more battery, but it's not a problem for me.
I've read that post, it's useful thanks, but i think if everything is on stock voltage it cant hurt the cpu. I overclock my desktop rig also since ~15 years, and never had problems with that. I know that it's not the same, but I hope there will be no problems with that.
Hey guys,
Ive been using SetCPU since it was fixed for the sensation. I am curious about what others have observed as far as battery life and performance goes.
I am running 1.8Ghz with a cpu voltage of 1.265V (1265000uV).
My battery doesnt last all that long despite all the profiles I have in place. I guess thats expected when you overclock by that much, huh? Is it worth it though?
Im sure more of you out there have experience to share. Im not talking Quadrant and benchmark scores, Im talking REAL use!
I am beginning to feel that dropping the frequency down may be in order since I cannot find anything that needs 1.8Ghz to work on this phone. Plus, less frequency means less required voltage. That would mean more battery!
Anyone care to chime in with their overclock frequency + voltage and experience?
Matt
I'm also interested in getting some input from other users, without having to clog up the respective overclocking threads in the Development section.
Yesterday after work, I set up the 1.5Ghz Undervolted option using utking's tool (http://forum.xda-developers.com/showthread.php?t=1168707). I didn't see too much need to push my CPU too hard, and a stable UV always piques my interest.
I created a couple of basic SetCPU profiles (screen off, battery below 20%, temperature < 50C), and scaling on demand up to 1512Mhz, my phone took about another 7-8 hours of moderately heavy use (Navigation, Maps, Yelp, photos, etc.) before it was on its last legs.
Bear in mind that I've been using the Anker 1900mAh battery. But even after the OC-UV that I set up, this was at least as good of battery usage as before without any SetCPU or overclocking, and actually seemed to be a little bit better to be honest.
I just dropped down to 1.6Ghz @ 1.26V...
I couldn't keep my phone from freezing with anything less than 1.26V @ 1.6Ghz. We will see how this goes for a few days and compare to my previous 1.8Ghz @ 1.265V.
So far, speed seems to be FASTER than 1.8Ghz. My Quadrant score (only being used here for comparison reasons) was 2700 right off the bat, whereas 1.8Ghz would peak around 2700-2800 after several tries.
The carousel works much better! I can swipe through quickly and have it scroll with zero lag. I can also fast swipe and watch is spin nicely!
Google Earth and Maps is about the same as 1.8Ghz.
Before, at 1.8Ghz, I could probably get 16 hours out of my phone with VERY LIGHT use. (A few 2min phone calls, check mail throughout the day, check the web a little). I am charging the phone up and will report back later.
Matt
I went down from 1.62 UV to 1.5 UV,because I could not see any difference in general use nad in benchmarks(except Quadrant) and battery consumption is much bigger with 1.62 with exact same profiles on setCpu.I think that this is best compromise between speed and battery life and as far as I know this is native clock speed of 8260 Snapdragon.
mrg02d said:
I just dropped down to 1.6Ghz @ 1.26V...
I couldn't keep my phone from freezing with anything less than 1.26V @ 1.6Ghz. We will see how this goes for a few days and compare to my previous 1.8Ghz @ 1.265V.
So far, speed seems to be FASTER than 1.8Ghz. My Quadrant score (only being used here for comparison reasons) was 2700 right off the bat, whereas 1.8Ghz would peak around 2700-2800 after several tries.
The carousel works much better! I can swipe through quickly and have it scroll with zero lag. I can also fast swipe and watch is spin nicely!
Google Earth and Maps is about the same as 1.8Ghz.
Before, at 1.8Ghz, I could probably get 16 hours out of my phone with VERY LIGHT use. (A few 2min phone calls, check mail throughout the day, check the web a little). I am charging the phone up and will report back later.
Matt
Click to expand...
Click to collapse
How simple is it to temp-root and overclock? I am really only interested in overclocking to speed up Sense, and you said it performs better with a speed boost.
Sent from my HTC Sensation 4G using XDA Premium App
Very,very easy,just read this tread :http://forum.xda-developers.com/showthread.php?t=1168707
I have mine undervolted at VDD_1175000 and 1500MHz. I like it very much...makes a big difference in quadarant score, but not sure in reality how much faster. Battery life is fine (when the phone is on). Have not experiened FC's
I have modified eugenes batch file to push my kernel file and preferred speed after perma-temp-root and now is all in one click...
So here is a little update:
Its been about 8 hours since full charge and I am at 55% battery left.
1.6Ghz @ 1.26V, On Demand.
Ive been checking email, making a few calls, and surfing the net with both wifi and GPRS (was out of the network, away from 4G). I also played Angry birds for a little bit and showed off Google Maps and Earth to my Mom.
Now that Im back home, ive turned back on 4G...
Ive noticed a slight amount of hesitation while opening and closing things, but nothing bad.
I havent had any profiles kick in yet, but they will soon with the battery getting low. I will resist charging the phone and see if I make it through the night, using it as I need it. I will report tomorrow.
Matt
I must be doing something wrong.
I am rooted and running LeeDriods 1.2 Rom. When I launch setcpu the only options i have are 1000 mghz? WTF am i doing wrong?
i think at LeeDroid 1.2 you must not use setcpu but Demon control?
BigBoppa said:
i think at LeeDroid 1.2 you must not use setcpu but Demon control?
Click to expand...
Click to collapse
Hmmm, okay. I saw where set cpu was updated for the sensation in the latest release but it doesn't seem to support overclocking with this rom.
Shame that as i was about to get that rom and flash it onto my phone, glad i came in here now
Running Leedroid 1.0
Kernel @ 1.7ghz max, i have it set to 1.5ghz and 192mhz
Runs hot when i play finger racing or reckless racing or modern combat 2 or something intensive, but besides the heat, it drains just like it normally would to be honest, maybe a little quicker, definite speed increase in overall user experience, without an OC the rom just flops, better than stock but just crap, OC is needed.
I have an overclocked Samsung Epic and it the improvement in speed in everyday use is significant. Because the processor voltage is set lower than stock there is no sacrifice in battery life. With the Asus Transformer do you get a definite and significant benefit from overclocking? I am not talking about test bench scores but real world noticeable responsiveness. When I skim through the forums it is difficult for me to tell? Some people swear by sticking with stock. I would appreciate others perspectives.
Thanks
The improvements from overclocking vary on the application.
Home screen switching is choppy regardless of overclocking simply because the launcher lacks optimization. Browser performance is improved a little bit, but mainly remains unchanged as well. Games run noticeably smoother, especially Fpse. Task switching gets a small boost, as some applications will be able to load faster.
If you're a big gamer, overclocking is definitely worth it. For everything else, it won't make much of a difference.
I haven't played too many games (mostly Stardunk and Stupid Zombies) on my TF, but I haven't noticed any issues with them. I have also played high profile 720p video with absolutely no stuttering or artefacts.
In other words, I haven't felt the need to overclock yet. But if you are doing heavy gaming and/or video processing of some kind, it might be worthwhile.
For me, there's hardly any need to OC. It all depends on what you wanna do. To many people who play a lot of games on their TF, they report increases in performance (especially with emulators) but on other things I never really noticed any difference. I'm currently underclocking my TF, and have been for about a week, with no noticable stutters or performance issues and have great battery life.
And it's not really an "effort" to flash a new kernel... the hardest thing is waiting for your device to boot up again...
I have a transformer, galaxy tab 10.1, and a xoom. I've used just about every kernel that can be overclocked for each one of them, and to be honest I haven't really seen any improvements from them. I don't really play many games on my tablets though, so maybe there really is some benefit in that area.
Galaxy's screen
How do you rate the screen of the Galaxy Tab 10.1? Is it as good as the Super AmoLED (+)'s from Samsung mobiles?
droidx1978z4 said:
I have a transformer, galaxy tab 10.1, and a xoom. I've used just about every kernel that can be overclocked for each one of them, and to be honest I haven't really seen any improvements from them. I don't really play many games on my tablets though, so maybe there really is some benefit in that area.
Click to expand...
Click to collapse
This seems so counter-intuitive to me. If you overclock a PC CPU there is a very direct correlation with performance. There are always limiting factors such HD acess, etc., but there is a definite and noticeable difference across applications. What is even more surprising is that we are talking about very large % increases vs what people can do in the PC world. People are overclocking these CPUs by 50% plus...You would think you would see a very noticeable improvement but that doesn't seem to be the case.
My main interest is in browser performance. For example, XDA forum pages load extremely slow in all browsers I have tried (stock, Opera, Dolfin) with 5-6s to refresh vs instant on desktop browser. Also flash video tends to freeze and stutter some times. My internet connection is over 20Mb/s down and 5Mb/s up. I was hoping that I would find overclocking safe and provide a noticeable improvement.
earlyberd said:
The improvements from overclocking vary on the application.
Home screen switching is choppy regardless of overclocking simply because the launcher lacks optimization. Browser performance is improved a little bit, but mainly remains unchanged as well. Games run noticeably smoother, especially Fpse. Task switching gets a small boost, as some applications will be able to load faster.
If you're a big gamer, overclocking is definitely worth it. For everything else, it won't make much of a difference.
Click to expand...
Click to collapse
So for web page loading you haven't noticed much of a difference? How about flash video?
Thanks.
Overclocking can be a bit like collecting .. 'string' , because it is mostly done for the sake of itself, kind of like the many Ham Radio fans who talk about their "rigs", etc etc.
Yeah, of course if you can get, like in the old old days, a celeron 300 that overclocks to 450, and is dead stable, it was noticeable, and if you had a droid 1, which overclocked (many did) with ease from 500 to 1000+ , then it was again, noticeable, just not a staggeringly 2 times increase, because there are too many other factors.
The number of bus errors, and retries and slowness of the original bus speeds, and other components makes for a not-quite-as-expected by the numbers 'increase'. I would still mess with it, but not for the obvious reasons. I like under-volting more, and over-clocking only the slightest bit where nothing ever crashes or FCs. The moment you overclock, you really shouldn't be asking questions about 'Why does blah blah netflix crash?' because it crashes because you overclocked, and nothing else matters until you stick a kernel back at stock in there.
The other thing I love about alternate kernels is that you've got control of what modules you either compile in or compile and load as .ko files. cifs, tun, ntfs, whatever, it is all very useful, so there are lots of good and not-as-good things about it.
One thing I hate is when a dev insists on creating a kernel that has a 'default' speed greater than stock so that you've instantly got an ordeal if you've got one of the many gizmos that will not overclock to his default (like 1.6 to pick a number out of a hat).. Just make them all start at default, then allow us , the users, to setup overclocking via testing with setcpu or some such thing. Much easier than basically bricking things right off.
I sometimes look at those guys that overclock 'seriously' (by 3-4 times) using a container of liquid nitrogen that lasts for ~5 minutes and it is all for bragging rights, setting records , etc and think they're insane, but that is also part of it. Some are happy if they can just post here that they got 9,000 mF on some test despite not being able to do anything else reliably.
hachamacha said:
Overclocking can be a bit like collecting .. 'string' , because it is mostly done for the sake of itself, kind of like the many Ham Radio fans who talk about their "rigs", etc etc.
Yeah, of course if you can get, like in the old old days, a celeron 300 that overclocks to 450, and is dead stable, it was noticeable, and if you had a droid 1, which overclocked (many did) with ease from 500 to 1000+ , then it was again, noticeable, just not a staggeringly 2 times increase, because there are too many other factors.
The number of bus errors, and retries and slowness of the original bus speeds, and other components makes for a not-quite-as-expected by the numbers 'increase'. I would still mess with it, but not for the obvious reasons. I like under-volting more, and over-clocking only the slightest bit where nothing ever crashes or FCs. The moment you overclock, you really shouldn't be asking questions about 'Why does blah blah netflix crash?' because it crashes because you overclocked, and nothing else matters until you stick a kernel back at stock in there.
The other thing I love about alternate kernels is that you've got control of what modules you either compile in or compile and load as .ko files. cifs, tun, ntfs, whatever, it is all very useful, so there are lots of good and not-as-good things about it.
One thing I hate is when a dev insists on creating a kernel that has a 'default' speed greater than stock so that you've instantly got an ordeal if you've got one of the many gizmos that will not overclock to his default (like 1.6 to pick a number out of a hat).. Just make them all start at default, then allow us , the users, to setup overclocking via testing with setcpu or some such thing. Much easier than basically bricking things right off.
I sometimes look at those guys that overclock 'seriously' (by 3-4 times) using a container of liquid nitrogen that lasts for ~5 minutes and it is all for bragging rights, setting records , etc and think they're insane, but that is also part of it. Some are happy if they can just post here that they got 9,000 mF on some test despite not being able to do anything else reliably.
Click to expand...
Click to collapse
Great post!
+1
Very philosophical ! ;-)
I guess what I am getting at is if you overclock to 1.2Ghz-1.3Ghz on the Transformer can you have a stable system that shows an appreciable improvement in responsiveness? Moving from hypothetical to actual...have you done this? Any specific kernel?
The engineer in me is looking for a definitive answer. ;-)
Thanks.
sstea said:
Very philosophical ! ;-)
I guess what I am getting at is if you overclock to 1.2Ghz-1.3Ghz on the Transformer can you have a stable system that shows an appreciable improvement in responsiveness? Moving from hypothetical to actual...have you done this? Any specific kernel?
The engineer in me is looking for a definitive answer. ;-)
Thanks.
Click to expand...
Click to collapse
Yeah, I've done this, just not on the TF yet. I'm working on a kernel right now that doesn't have OC built-in and activated at boot, so that we can use setcpu to screw around with it and find that 'sweet spot' that works for us, also under-over-volting. What I'd really like is to build in all the modules I like, setup over/under-clocking-volting and have it boot at 1 G. I mean, a dual-core 1G is nothing to sneeze at, and then try to ramp it up without screwing with over-volting immediately. I never like other peoples ROMs or Kernels because they have made their own crazy judgement calls. I like my own crazy judgement calls
Here's what I've noticed: When you have 'up-to-date' technology , as we do, in the TF, then overclocking that is totally stable makes a difference and it is noticeable. For me it's the FC's that kill the deal, but this chip and box appear to have plenty of headroom so I'm guessing that 1.2, 1.3, 1.4 are all good possibilities.
Example: My HTC Incredible phone has been overclocked to 1.1 from 1.0G for ~a year or so, and it doesn't FC, and it is faster, noticeably than at 1. It's only a 10% increase and yet it feels much quicker, so go figure. Those things are also subjective, so grain of salt... Example2: A stock droid1 is one I took to a double overclock, 550 to 1000, and yes it was faster at some things, but the underlying infrastructure didn't really support the faster CPU so I really never noticed a 100% increase that matched the clock speed. I left it that way for a year without any damages and it still boots up fine at 1 G.
In another post I started, I was asking what keys were required to boot 'safe mode' which exists in android OSs, and if I knew that, I'd try one of the OC'd kernels right now. IF not, I don't feel like unbricking again.
If you're interested, here's a good link for building your own: (generic android, not TF really:
http://www.droidforums.net/forum/rescue-squad-guides/31452-how-compile-your-own-kernel.html
Thanks for the response. With such a large community of Transformer users I am hoping to find a solid, conservative kernel that I can overclock with. Creating one myself is beyond my current technical capabilities.
I see a lot of overclocked kernel editions, and I am wonder could someone explane me, except extensive battery draining, instabillity and overheating of device, what is and is there any crucial positive point of overclocked kernels ?
Overclocked kernels are simply kernels whose speed limit had been raised above the stock speed.
That increases perrormans dramatically as is visible by different benchmarks utilities.
You are correct to assume that higher clock would require some extra voltage and that the phone will get hotter. But it is not always noticeable and is mostly depentant on the configuration.
The cpu clock is not always at the highest possible. Different governors define what speed should the cpu be at any time. If there's a lot of work the cpuspeed would increase and if it idles a lot it would decrease.
I love 3 oc kernels, Sebastian's, bricked and faux. They all have different philosophies but all are excelent, do not overheat and save gather.compared to stock though they allow higher cpu freqs.
I suggest you create a nandroid backup and try some of.there kernels. Give it atleast two days.before you make up your mind about it, and try another if you wish, till you find the one that is right for you.
Sent from my HTC Sensation using xda premium
I agree. I never see the point of over clocking. I always limit my processor to 1.18 or even 1.13 and never have any problems with overheating or poor battery life!
I used overclock kernels for a long time on my gs2. Its nearly the same like with a desktop CPU. Every CPU had it's own work range, many CPUs a
are even able to work with higher frequency but lower voltage than standard. This causes in higher speed with lower power consumption!
all you need is a kernel which allows individual voltage settings for each speed which you can set with setcpu.
BUT my opinion is that even the gs2 with 1,2 GHz dual core was faster than any Android app had needed, so the gs3 at all!
ATM I've setted the max frequency in setcpu to 600 mhz and I can't see any lags or missing speed...
So I guess many people are more looking for benchmarking than real practical advantage..
but undervolting is a real great thing for power hungry smartphones!
Gesendet von meinem GT-I9300 mit Tapatalk 2
You all right guys. That is why I asked myself that question because there is hard to find modded kernels with default speeds and all new goodies, because I have noticed even I "limit" overclocked kernel in my Hypersensation CM7 Cyanogen Settings, it happens that some kernels from time to time speeds up to overclocked value, even in settings they were limited, and that impact widespread device causes instabillity ( and corrensponding unpleasent situations of forced battery pulling).
Last good kernel what I find for my CM7 ( I don't like ICS) is Bricked_XE-1.6.beta7 and with this release of CM7 it seems that kernel edition further development stops.It runs on 1526 Mhz and I allways wonder why shouldn't it run "out of the box" on default speed...
Does anyone have suggestion link, (because I couldn't find it )for any CM7 modded kernel with all new goodies, but running on default Sensation XE Mhz speed ?
i have been using overclocked Kernels for a while now and rarely have any problems, the phone is quick, very quick and the battery drain is really not that different and that is running it at 1.72 with both cores permanently on
tin2404 said:
[...] because I have noticed even I "limit" overclocked kernel in my Hypersensation CM7 Cyanogen Settings, it happens that some kernels from time to time speeds up to overclocked value
Click to expand...
Click to collapse
This really should not happen. The maximum frequency for a governor is set through /sys pseudo-fs and (assuming the governor is not buggy) strictly followed. Maybe you have some leftover scripts somewhere messing with /sys?
tin2404 said:
( and corrensponding unpleasent situations of forced battery pulling).
Click to expand...
Click to collapse
And this should -- like already pointed out -- only be the case under heavy load. Normally, a sensible governor will only set frequencies necessary to satisfy the current load.
Hi XDA Community. I use Trinity Kernel by Morfic and i was wondering if it is okay to have an Overclocked Nexus 5 and use the phone at a regular basis like a normal stock clock Nexus. I don't want My phone to just randomly explode because of overclocking it. One of the features the kernel has as said at his/her XDA thread is "Up to 2726MHz (higher clocks will vary from device to device)". Is that frequency trustworthy when just using the phone normally or is that a benchmark frequency?
MaLing15 said:
Hi XDA Community. I use Trinity Kernel by Morfic and i was wondering if it is okay to have an Overclocked Nexus 5 and use the phone at a regular basis like a normal stock clock Nexus. I don't want My phone to just randomly explode because of overclocking it. One of the features the kernel has as said at his/her XDA thread is "Up to 2726MHz (higher clocks will vary from device to device)". Is that frequency trustworthy when just using the phone normally or is that a benchmark frequency?
Click to expand...
Click to collapse
Don't overclock that high. 2419MHz at most. Overclocking too high will cause more heat and throttle earlier, only useful for a short benchmark such as HWBot Prime or Quadrant (Antutu takes longer and will overheat by the time it finishes). Trinity also supports up to 3014MHz, OP hasn't been updated.
MaLing15 said:
Hi XDA Community. I use Trinity Kernel by Morfic and i was wondering if it is okay to have an Overclocked Nexus 5 and use the phone at a regular basis like a normal stock clock Nexus. I don't want My phone to just randomly explode because of overclocking it. One of the features the kernel has as said at his/her XDA thread is "Up to 2726MHz (higher clocks will vary from device to device)". Is that frequency trustworthy when just using the phone normally or is that a benchmark frequency?
Click to expand...
Click to collapse
You don't want to push the phone too much I think the Nexus 5 runs at 2.3 GHz. 2.7 MAY not be too bad but honestly, the phone runs pretty smooth as is. What benefits are you looking for from overclocking?
Thanks guys for sharing your knowledge. You know.. To get the MOST out of the Phone while at the same time being Safe.
if you really wanted, the phone won't explode if you run it at 3015mhz either. the worst that will happen is that your phone won't be able to run that high, and will freeze and reboot.
and don't listen to all.. run your phone how YOU like. yes, it'll cause a little(not much) more heat, and will throttle a little earlier, but that's why people like me disable throttle, so that's a non issue. I run my phone at high CPU speeds all the time, and use 2880mhz high/300mhz low quite often. just because I feel like it, no other reason.
oh, I run trinity as well, and do all of Trinity's testing
MaLing15 said:
Thanks guys for sharing your knowledge. You know.. To get the MOST out of the Phone while at the same time being Safe.
Click to expand...
Click to collapse
It's just what @jsgraphicart said. You're not really getting more out of your phone by overclocking. It's not going to run smoother, and most games don't lag anyway so they probably won't run better. I think most people just do it for benchmarks or just to check if it can run on a certain clockspeed.
Also what @simms22 said. You can do it if you want to, but simply because you want to because as far as I know there aren't really any benefits.
Back in my Palm Pre days, we used to overclock that thing to 1GHz. The default setting was 500MHz. I think it was even pushed to 1.2GHz. And it ran fine. But back then, you could tell the difference between a little lag at 500MHz and smoothness at 1GHz. With this phone and how Android has gotten smoother with every update, it's kind of hard to see any difference when overclocking. It will be smooth regardless.
oh, benefits, not really. a little more speed, yes. bit I would never call it a benefit, unless the speed difference was drastic, and its not.
As mentioned, overclocking the CPU can actually turn out to run slower because of aggressive thermal throttling. You could disable or extend the thermal throttling, but 2.3Ghz is already plenty fast for today's mobile software so you won't notice any difference in day to day usage.
bblzd said:
As mentioned, overclocking the CPU can actually turn out to run slower because of aggressive thermal throttling. You could disable or extend the thermal throttling, but 2.3Ghz is already plenty fast for today's mobile software so you won't notice any difference in day to day usage.
Click to expand...
Click to collapse
Even if you run your phone at 2880MHz/3014MHz/whatever with thermal throttle off, you can't really do anything too intensive as it'll hit 105C and shutoff lol
Lethargy said:
Even if you run your phone at 2880MHz/3014MHz/whatever with thermal throttle off, you can't really do anything too intensive as it'll hit 105C and shutoff lol
Click to expand...
Click to collapse
actually, no, youre wrong. when you run your phone at 2880/300 or 3014/300, you phone will hardly scale up that high, sometimes it will. you wont see any real difference between those high cpu speeds and running it at 2265/300. and battery will be similar. the difference will be if you run it at 2880/2880 or 3014/3014. now i run my phone at 2880/300 very often, and you know i disable thermal throttle. yet, i see no difference in temperatures, except if im doing something thats very cpu intensive.
simms22 said:
actually, no, youre wrong. when you run your phone at 2880/300 or 3014/300, you phone will hardly scale up that high, sometimes it will. you wont see any real difference between those high cpu speeds and running it at 2265/300. and battery will be similar. the difference will be if you run it at 2880/2880 or 3014/3014. now i run my phone at 2880/300 very often, and you know i disable thermal throttle. yet, i see no difference in temperatures, except if im doing something thats very cpu intensive.
Click to expand...
Click to collapse
Ah true. But still, a bit easier to hit it if doing something intensive Not to mention it may be a little unstable on some devices
Lethargy said:
Ah true. But still, a bit easier to hit it if doing something intensive Not to mention it may be a little unstable on some devices
Click to expand...
Click to collapse
on some devices??? on most devices! anyways, stability is overrated
LOL...no explosions on XDA allowed!