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.
To overclock. Which one iis better?
SENT FROM MY DINC2 RUNNING CM7 overclocked to 1.6ghz
Ok. I don't know if it was the kernel or what but f4 phantom bricked my touchpad. The screen was blue and I couldn't restart it. It scared me so bad. But it just now began working again and the first thing I did was remove f4.
SENT FROM MY DINC2 RUNNING CM7 overclocked to 1.6ghz
Haven't had issues with F4, actually runs both cores full time which is an advantage compared to Warthog. I've never gotten F15 to work correctly.
Running f15 at 1.8 no issues at all..
Matt V said:
Haven't had issues with F4, actually runs both cores full time which is an advantage compared to Warthog. I've never gotten F15 to work correctly.
Click to expand...
Click to collapse
isn't that going to eat up your battery?
Not really because it's on demand. At idle both cores run at 400MHz.
Matt V said:
Not really because it's on demand. At idle both cores run at 400MHz.
Click to expand...
Click to collapse
Then what does the Warthog kernel do?
Wearespacepeople said:
Then what does the Warthog kernel do?
Click to expand...
Click to collapse
Warthog idles core 1 at 292 or so and cuts off core 2 until needed. I originally used F15c Eagle to OC and recently switched to Wathog to try it out. Both Oc'd to 1.728Ghz. I have never gotten either of them to activate core 2, even with polling set to 1 sec.
JohnnyChuttz said:
Warthog idles core 1 at 292 or so and cuts off core 2 until needed. I originally used F15c Eagle to OC and recently switched to Wathog to try it out. Both Oc'd to 1.728Ghz. I have never gotten either of them to activate core 2, even with polling set to 1 sec.
Click to expand...
Click to collapse
Warthog activates core 2 when necessary I believe, I've seen it jump to 1.7ghz
JohnnyChuttz said:
Warthog idles core 1 at 292 or so and cuts off core 2 until needed. I originally used F15c Eagle to OC and recently switched to Wathog to try it out. Both Oc'd to 1.728Ghz. I have never gotten either of them to activate core 2, even with polling set to 1 sec.
Click to expand...
Click to collapse
polling frequency is not too important. just have to do something like watch a hd video. then go back and check. the number will be back down again. but what u have to do is to click on the graph, and u'll see it peaks to 1.7 when needed.
i've used f15c, and it froze a few times. been using Warthog for a day now, so far no freeze.
havent tried F4 yet. i'm happy with the performance and stability now, so i might not change it unless there's a big difference.
Use f15c ... it works awesome , if you dont see the second core do anything is because the second core is not being used! you can test it openning lets say 3 youtube videos at the same time then go to govnah and you will see second core working! after you install the kernel if second core says n/a just unnistall the kernel reboot and try phantom after you install restar again.. I guess using phantom running both cores at the same time will drecrease battery a little bit.
had problems getting f15 to oc above 1.5, would give me errors if I tried to up it. Switched to warthog and my TP has been 100%. I'm very happy with it. I have not tried F4.
bug splat said:
had problems getting f15 to oc above 1.5, would give me errors if I tried to up it. Switched to warthog and my TP has been 100%. I'm very happy with it. I have not tried F4.
Click to expand...
Click to collapse
I tried f4 but I believe since both cores run at full speed all the time battery will decrease faster not sure how much faster , I have tried movies, games, 4 youtube videos at the same time some of multitasking and with 1.7 is more than enough everything runs perfect with f15 .. I would say you are covered with warthog
Here's a test showing that F4 performs the best out of any of the kernels.
http://forums.precentral.net/hp-tou...k-benchmarking-kernel-fastest-comparison.html
bafare said:
I tried f4 but I believe since both cores run at full speed all the time battery will decrease faster not sure how much faster , I have tried movies, games, 4 youtube videos at the same time some of multitasking and with 1.7 is more than enough everything runs perfect with f15 .. I would say you are covered with warthog
Click to expand...
Click to collapse
The only way both cores are at full speed all the time is if you set the governor to performance. I believe it defaults to on demand so it should only only use higher frequencies when necessary.
I prefer F4 Phantom at the moment.
used F4 at 1.8 for few hours now and it works smooth. Difference between F15c and F4 is quite noticeable .
I have updated from uberkernel to f4 @ 1.72 , seems very stable.
Battery life on the f4 kernal is amazing even with performance mode on. I can get about a day and a half with consistant usage (I mainly use it as a pdf viewer for my textbooks, sprinkled in with heavy web usage here and there when I zone out). I can only imagine the battery life with eagle and warthog if I stuck with it longer... 6000mAh battery ftw.
Sent from my T-Mobile myTouch 3G Slide using XDA Premium App
I agree, the battery life, screen, and processor, are the strong features of this tablet. Even with webOS it's a nice, handy tablet.
Is there any particular reason the second core always drops down to 216mhz? This happens with any custom kernel I run, currently running moray with electra kernel at 1.5Ghz using pimp my cpy to OC.
ggrammer said:
Is there any particular reason the second core always drops down to 216mhz? This happens with any custom kernel I run, currently running moray with electra kernel at 1.5Ghz using pimp my cpy to OC.
Click to expand...
Click to collapse
when it's needed, it goes to the required frequency...
sounds reasonable but I will notice some lag and stuttering while I am using the xoom, i will open os monitor and the second core is sitting at 216, i move it manually to 1.5Ghz and the tablet is more responsive...
Edit
Sorry I should have been more specific about the situation. When I say the 2nd core drops to 216 I mean the max frequency drops to 216 so the 2nd core does not clock up any higher unless I manually intervene.
same on my xoom with tiamat 2.2.2 and setcpu. i have two profles , screen off with 216-456mhz and other with 216-1200mhz. only the first score is over clocked after switched on, the second stucks at 216-456mhz. i contacted the developer of setcpu someting around 2 weeks a go, but no solution till now.
okay i see wat u mean...i just checked and i'm getting the same results... it sits on the min freq, all laggy, then when i manually set the frequency, it's super responsive like it shud.... i'm over-clocking to 1.6 btw
burgi400 said:
same on my xoom with tiamat 2.2.2 and setcpu. i have two profles , screen off with 216-456mhz and other with 216-1200mhz. only the first score is over clocked after switched on, the second stucks at 216-456mhz. i contacted the developer of setcpu someting around 2 weeks a go, but no solution till now.
Click to expand...
Click to collapse
I don't think that it strictly a SetCPU problem. I also have an Advent Vega and have used SetCPU to overclock it. Had almost the same problem, except both cores were stuck at 216Mhz.
Tried multiple overclocking apps and have had the same problem with all of them. Device fine until it goes into sleep mode, CPU stuck at 216Mhz when brought out of sleep. Even setting the minimum setting to 456Mhz still resulted in the CPU being stuck at 216Mhz on wakeup.
so i guess the big question is whether it is the kernels (I've tried a few) or in the way these apps OC a dualcore processor...It makes me wonder about the OC apps though, they were all built for single core originally and in each of them you only set 1 max and 1 min speed. OS monitor is the only app that displays both cores, at least that I have used, but it doesn't set an OC value at boot. Maybe if one of the smart devs on here could comment maybe even just to shed some light on this
Is there no solution to this issue yet?
Is it a tegra fault/problem?
Is it a Kernel issue?
Would flashing back to a stock kernel fix it? (if that is even possible...)
Hi all.
Im using SebsstianFM 1.5 GHz kernel on my sensation . It becomes warm and heats my fingers, so I can't resolve is this an issue. I thought before that htc sensation has the same chipset in both xe and non-xe series. Hasn't it?
Perhaps Im unlucky one with the specific cpu or some heating is normal?
Thanks a lot in adv
Every processor is different, some can handle higher clockrates than others. Try underclocking it.
Thanks, I do.
But I'm sad a bit when informed about new Sebastian 1.7 GHz kernel. As for me 1.3 is the far frontier..
garryveda said:
Thanks, I do.
But I'm sad a bit when informed about new Sebastian 1.7 GHz kernel. As for me 1.3 is the far frontier..
Click to expand...
Click to collapse
try it without charger for a while, the chips are made for 1512MHz
it can get hot for me when running on 1512 but only with charger
For me 1.5 GHz was OK, only got "hot" when I played 3D games like CS and FIFA, but I Find the 1.35 GHz a bit friendlier for the battery (and at the clock the phone very rarely gets hot).
No prob here with Sebastian's V1.30.1 @1.5ghz yet again all chips handle every frequency in a different manner
Sent from my HTC Sensation Z710e using Tapatalk
How hot is hot? Am using using bricked 1.6 for aosp and I o/c to 1.9 Ghz to run benchmarks. After 10 minutes set at performance my battery hit 80° lol. Good benchmark scores tho.
Daily I use 1.56 Ghz and all is fine, wish I could o/c to 2ghz tho, just for the sound of it
sent from my Sensation XE
I didn't realize installing Sebastian's kernel would overclock me to 1.7GHz. My Senny is cooking over here. Anyone know where I can find the stock kernel? Or should I just slow it with SetCpu?
NVM...found it!
As for mine one it is really hot. Phone got 50 degrees within five using minuites while 1.5 GHz running. Though it is quite cold when used usual way like the calling, messaging etc. But anytime I load it with real tasks like playing 3d games, shoting videos it becomes hot and not suitable to use.
So 1.3 is my top...
Overheating for me is usually because of the app. Poorly built apps can cause overheating. My phone overheats even with the stock HTC 1.2GHz kernel when playing certain games.
Use SetCPU as a govenor to set the processor automaticly back to 1,2 Ghz when overheating.
I guess my processor is one of the luckier ones, I'm getting 1.72GHz under volted with no problems At the end of the day the Sensation was 'designed' to run at 1.22GHz so anything above is a bonus
You should be glad your phone doesnt blow up...as far as i see it, 1.7 ghz speed is so much closer to the netbook laptop processor speeds we get these days. these netbooks come with built-in exhaust fans to avoid heating up of the processor.
The sensation does not have such hardware builting, so its better not to overclock it too much or you might end up with a burnt up phone.
ARHD rom has a stock kernel , U can try it :d
Situation has chanched since I got updated with ARHD 6.5.3. For now I'm using 1.6 SebastianFm kernel with no prob.
Phone is comfortable with its temperature even when hard tasks running.
I don't know whether the new ROM is brilliant or the weather becomes more warm causing not to feel device heating with my fingers.
The fact is that issue has gone and I'm happy