Related
hey guys, just wondering will using a lower vsel damage my cpu and/or battery?
i have previously beein using milestone overclock on 1ghz and 60 vsel and am adding setvsel into the mix, also any ideas on starter settings? thanks
also could someone just give me a heads up on what vsel actually IS
I don't believe there are any studies that show effects of long term use of lowering the voltage, which is what you are doing with vsel in order to save battery juice...or you could increase the voltage but that defeats the purpose and also heats up the battery which leads to shorter life span. Many use it without reporting any damage to battery or cpu, I believe it's safe (however, if you are overheating you might fry the battery or cpu, so you'll need to moniter and play with settings to get the desired effect without any overheating issues).
With regards to setvsel, there are reported issues from users with different roms...from what I've read (and you can do your own research to see if this is what you are seeing...this is the conclusion that I've come to by reading a lot of threads), it is better to use milestone to overclock and setcpu to lower the vsel.
With that being said, I've used them all and like setvsel so keep going back to it...but I've been having some issues lately so I've removed setvsel to see if that is what is causing some problems (too early to tell).
Oh, and as for settings...pop on the overclocking/undervolting thread in the development section to see a lot of different settings and remember that what works for one user might not work for you...you'll have to experiment a bit to find your ideal setting.
oh okay i think i might go back to my old settings with milestone overclock and setcpu and just lower the vsel! i was under the impression for some reason that lowering the vsel would heat the battery. Thanks!
I'm no expert to be honest, I'm more of a research kinda person. From what I've researched, undervolting can help keep temps down, and may particularly help when you overclock (as overclocking is stressing the cpu to go beyond it's normal operating design hence it may heat up...supplying it with less power, or voltage, is what helps keep the temps down.
Of course, this is given you find the optimal setting for your phone, and as it seems from reading through these forums, many users have experienced completely different results using the same settings (i.e., one user will have a stable setting without any problems while another user on the same rom using the same settings will have crashes and/or issues like overheating). Doesn't seem right, but it is what it is
yeah ive read through most of that stuff too, i went down to 1ghz at 51 vsel, seeming stable, but i decided to go with 54 anyway
1.1 GHz @ Stock vsel for over a month without any issues...I hope it lasts.
Sent from my MB525 using XDA App
Hi,
I've also read a lot regarding the underclocking 'dangers' but couldn't find anything to prove that there is such an issue. I think that it is an urban myth spread everywhere by people asking if there is a danger with low vsel [but that are never getting a positive answer on it].
The only thing I found using setvSel is that I had to first install Milestone Overclock and load its module prior to start setvsel. There is a way around it, but requires you to copy files in the system folders and change their permissions. I find that my way is much easier.
As far as over-heating goes, it's an overclocking thing; not underclocking.
My Defy is set at 900Mhz and really, I don't see the point of going much higher: everything runs smooth and lag free already.
vsel: 21/300; 32/600; 43/900 - 90% up_threshold
Been like that for about a month now and never experienced any problem at all.
The underclocking is great for saving battery; no exact numbers to give here but it feels like my battery now last 2 times longer. I can easily get 4 days between charges with low/moderate usage and would get to 6+ days "IF" I could stay away from games and having the screen ON for long sessions of browsing/video watching.
I tried SetCpu before but I didn't like the interface; the simplicity of SetvSel is really nice.
i use setcpu for scaling and profiles, and run 18/300, 36/600, 50/1000 stable and smooth as
Undervolting is not a bad thing at all. It means less Watts consumed for running (Watts = Voltage x Amperage), less of your battery consumed.
Ussually companies test a large batch of components and how they react on different voltages and freqvencies, and then they decide for a voltage that works with all components and that is safe for all cases. Eg. when they have different CPU speeds and thus different options for CPU's this is one way to decide which one work at 3GHz and which one at 2.7 GHz (the other one is demand for components).
Phisically you will not have any problems and you can't damage your phone by undervolting, so no problem here, only possible software problems if you go too low.
Advantages :
+ Lower processor temperature
+ Lower phone temperature
+ Longer battery time
+ Longer components life
Disadvantages
- Stability issues (freeze, artefacts, slowness)
maxi2mc said:
Disadvantages
- Stability issues (freeze, artefacts, slowness)
Click to expand...
Click to collapse
You know, I was recording a video and when playing back noticed that there were squiggly lines that went through the video a couple of times (in a two minute clip). This was the first time I saw this...and have recently lowered vsel by 2 on vsel3...could that be the artifacts that you are mentioning?
I just figured it perhaps I was too bouncy with the phone while recording making it glitch...but now that I see this post I'm thinking maybe I undervolted too much...what do you think?
My settings: 54/1000 44/700 28/300
I know what people mean by same settings don't work for every phone even if it's the exact same model. My Defy won't underclock as much as others. I'm using SetVesel, and I've been able to drop 5 points from each, and that's about it before it reboots itself. I only tested undervolting, but I mainly overclock to get as much speed as I can, and give it enough juice to run super fast. I'm current running [email protected], [email protected], [email protected] Threshold at 75%. The highest the temp ever got was 112F, and that was after playing a game for about an hour. Usually it stays below 90F for normal use. I get around 17-20 hours out of it with screen on time at about 3 hours @ 50% brightness. I've been running these settings about a month, and have not had any issues.
If you put something like 100vsel will the phone accept and then burn? Is there any protection? Does anyone know what's the highest acceptable vsel?
Just for curiosity...
im pretty sure 80 is the highest you should EVER use and that'll significantly increase the chances of your phone burning out. @bobbyphoenix you should be able to lower your vsels a fair bit or your really unlucky! i run a lower vsel for 1ghz than u do for 700mhz smooth and stable
stewi21 said:
im pretty sure 80 is the highest you should EVER use and that'll significantly increase the chances of your phone burning out. @bobbyphoenix you should be able to lower your vsels a fair bit or your really unlucky! i run a lower vsel for 1ghz than u do for 700mhz smooth and stable
Click to expand...
Click to collapse
CM7, rather non-technical person here. I seem to have a very happy phone at setvsel settings of [email protected], [email protected], [email protected], 86%. Been running this for the month or so since I rooted and the phone feels like it was made for this config. I've never seen the temp above ~32c. My 2¢.
r800at, Rooted, Bootloader Unlocked
Stock Kernel, Stock 2.3.3 Rom
Looked around, all the threads were from last year.
So I just got setCPU, and I was wondering the best settings for my play.
Does anyone want to post their setCPU profiles for me?
(heres my setCPU settings as of now;
Battery <10% 368Max | 122Min
Battery <30% 768Max | 122Min
Screen Off 245Max | 122Min
Charging 1024Max| 768Min
-- All ondemand scale -- )
EDIT: Scratch that, task killers are bad for android.
Overclocking naturally will run the battery down faster right? As well as I need a custom kernel for that? Does anyone have any testimonial for overclocking? I think the device runs fine right now, no slowdowns in my playstation games, even psxperia ones.
Overclocking does two things to phones: Burns through power faster than Richard Simmons burns through fat.
And increases the phone and battery heat, which in turn shortens it's life span.
Also different phones overclock differently, even the same models. I see all the time people saying their Play can hit 2Ghz, if I set mine that high, my phone crashes.
I actually have a question for you, don't mean to hijack. You have your speeds set to lower maxes at 30% and 10% battery, how do your playstation games run at those speeds? Slowdowns?
Also, I once heard that underclocking too much will make the phone crash, any problems with your screen off ever crashing?
My phone still gets calls/messages while the phone screen is off. I see no problems with my current setup, Im still trying to get more though, the phone lost 5% in 6hours of standby, then 5% in like 20 texts over an hour.
Obviously at <30% im not going to be playing games unless im home battery testing. I'd assume playstation pocket games would be out of the picture at that point, maybe just some gameboid or less resourceful games.
It just feels like this phone has a bad battery life for what it should be able to do. Played resident evil for 40 minutes and lost like 20%.
Well on FPSE playing FF7, I only lose about 13-15% an hour.
And i tried FPSE at 768mHz, only lose about 10FPS in intensive areas, but still playable.
I've been using a psxperia rom. So maybe the playstation pocket app takes more resources.
That and I have battery tweaks, and juice defender working as well.
I just have setCPU, been thinking of using a different rom/kernel just for better efficiency.
im now using a custom rom with the overclock kernel... i set my phone to "1.4ghz" with AnTuTu... its working great now... no more fps lags on the games i play... and no crashes... im just curious about one thing? will it break the phone in any way? its not heating up or anything atm... i mean i have experienced phone heat on my sensation xe... that phone gets really hot STOCK....
i dont want to break my play... i really like it compared to other phones in the market right now(the only one with gamepads)... its my first time ocing a phone btw...
If its not noticably hot (the battery too) constantly then your fine, just bare in mind try not to push it past 1.6ghz i found my phone didnt last very long at that speed.
The only thing with oc its that it shortens the life of your cpu obviously depending on how much you oc it....and it drains more battery but its not that big of a deal
Defy39 said:
If its not noticably hot (the battery too) constantly then your fine, just bare in mind try not to push it past 1.6ghz i found my phone didnt last very long at that speed.
Click to expand...
Click to collapse
what do you mean by it didnt last very long? did it break the phone?
Basically, my phone is overclocked to 2.0 GHz with smartass scaling with max 800MHz interactive scaling when screen turned off. It works great! Lasts 2~3 days without gaming (5 to 7 days with airplane mode on) and 4~8 hours of hardcore gaming with full charge (6~12 with airplane mode on). I recommend using an extended battery (I haven't, yet) if you are doing so. And it also involves luck. Even if it is the same model, color, etc. some CPUs are more capable than others.
still testing my phone under 1.4ghz seems stable...
DanielEGVi said:
Basically, my phone is overclocked to 2.0 GHz with smartass scaling with max 800MHz interactive scaling when screen turned off. It works great! Lasts 2~3 days without gaming (5 to 7 days with airplane mode on) and 4~8 hours of hardcore gaming with full charge (6~12 with airplane mode on). I recommend using an extended battery (I haven't, yet) if you are doing so. And it also involves luck. Even if it is the same model, color, etc. some CPUs are more capable than others.
Click to expand...
Click to collapse
is it normal for the phone to be abit hotter than when it was running stock???
btw how does smartass compare to ondemand?? smartass tends to get lower benchmark scores than on demand
seagheart89 said:
is it normal for the phone to be abit hotter than when it was running stock???
btw how does smartass compare to ondemand?? smartass tends to get lower benchmark scores than on demand
Click to expand...
Click to collapse
Yes ofc its normal - as each CPU/GPU creates heat based on the load it takes....
So the higher u OC the hotter it gets - thats why in former days OC was quite dangerous
In todays times cpu normaly 1st get unstable, and then has a safety function to shutdown if it gets too hot. (no warrenty that its the same for all chips)
smartass doesnt switch frequencies at once like on demand (e.g. instant from 200mhz to 1000mhz) but it tries to predict the needed power somehow so the whole switching is done in more steps... (as far as I remember)
So yes its performace is a bit below the on demand - but should not be that noticable - but it will also save your battery.
Gello guys,
(I'm on MooDed ICS 1.0.2)
I wanted to know what kernel(s) is (are) the best to overclock the Arc and to what frequency can I go with the phone stable? I'm actually on InFamous Kernel ( http://forum.xda-developers.com/showthread.php?t=1843532 ) But I'm not overclock. I was before on DooM Kernel and overclock to 1.2 gh/z.
Thanks a lot! (And sorry for my bad English, I do my best)
It all depends on your phone. Even though there all made the same, some of the processors can not handle the same amount of OC as other do. The way to test which runs most stable is to slowly up the frequency every hour or so, and test it to see if it's stable.
If your phone starts to random reboot, then it's probably best that you choose the lower frequency to what you are using when it reboots.
I'm using inFamous Kernel too, its overclocked to 1.5.
1.4 should be theoretically safe as that the speed that the Arc S runs at with the same processor
EDIT: I don't recommend passing 1.5 on the Arc as it will very quickly burn out the processor. (Even at 1.5, it's running 50% more than what it was originally designed for).
Overclocking will also reduce your battery life. So it's swings and roundabouts depending on if you want performance or battery life.
Hope I helped
Over cloking is realy affect to battery life and all so the head will get increase,
am always usting 1.2Hz.i think it is enough to have a smoooth run for a xperia smart phone while saving the battery and reducing the risk
Ok thanks guys! I'll try all I can. I'm now overclocked to 1.2 ghz and battery life is good for me, because I recharge it all night. At 1.4 ghz, it's stable normally but the CPU is hot (very hot) and I don't want to burn it. But is it normal? Because Arc S is on this frequency and isn't normally so hot
So Thanks one more time!
Yeah, don't worry about it getting warm. If it gets really hot, then I'd recommend to stop using it for a while. Simply to let it cool down.
Mine can get to the point when it feels it's going to melt the plastic on the back yet it still works perfectly, so yeah i'd say its normal. There's also a ton of older threads about how much peoples arc's heat up when it's being used.
The reason why the processor gets so hot is because there is very little heat sink because of how thin the arc is.
Obviously the more you overclock the hotter the processor will get. The hotter the processor gets, the more quickly the CPU will burn out. If you don't like to replace your phone every few years, don't overclock it to the limit.
You should OC stable at 1.2 - 1.4 GHZ
Ah ok thanks.. I like to change it every year / 2 years. And now I'll try Puissant phone like GS3 and others.
I've overclocked it to 1.6 and it's stable (fast..) and hot. But I'll follow your advices. Thanks a lot!
dont overclock over 1.4Ghz if you have arc and you can always undervolt to save some battery juice
arpith.fbi said:
dont overclock over 1.4Ghz if you have arc and you can always undervolt to save some battery juice
Click to expand...
Click to collapse
Ok, but I didn't find thé option to undervolt where is it?
Thanks
U need apps for undervolting such as setxperia, voltage control, etc.. Reduce the voltage and test it for few mins then again lower the value until ur phone auto restarts. Tats the threshold value
Sent from SE Xperia arc s using tapatalk 2
Is it possible to undervolt it if it's overclocked?
Thanks
TheJurassien said:
Is it possible to undervolt it if it's overclocked?
Thanks
Click to expand...
Click to collapse
yea obv..undervolting means supplying less voltage to the cpu at specific frequency. it doesnt matter at wat frequency the phone is running
It might work fine well above 1.4 depending on the quality of the CPU you have in your device. I am fortunate enough to be able to overclock an xperia arc to 1.8 GHz and have been running at this clock for 6 months. Even gaming at lengthy time with charger plugged in works fine.
I do not game every day and just listening to music, talking on the phone, texting, reading a webpage or watching a video will not run the CPU at full speed all the time. Battery live if also fine for my usage 1-3 days. I prefer a snappy and responsive phone.
Running at very high clock speeds is at your own risc, the cpu chip design should be able to handle the high temperatures. I have allways overclocked my phones and have not yet been able to kill any of them, maybe I have just been lucky. There could be a poor soldering that breaks when it heats up, only push it to the limits if you can afford paying for a new phone
1,6 GHz on XArc by Sirkay = epic speed.
Sent from my CM9'd Galaxy Tab 2 10.1
So I tried to underclock my One X to around 640 MHz and it was running VERY smoothly and stable with only 2 cores active. I was using the ViperX 2.2.1 ROM and the Kernel was the no OC NCX 0.99a. The battery life wasn't bad, but has anyone tried underclocking to 1 GHz or lower? If so, how is the battery life and what kernel and ROM did you use?
With SetCPU you can change the max. CPU, but why should you? When the phone doesn't need much processor power, it just scales down by itself.
So, it already has the best underclocker there is.
Mayby you could try undervolting to save even more battery, but that means the CPU can be somewhat less steady.
im trying to get my head around UVing / UCing my HOX. is there any guide around? im trying to search through the forum but still no luck.
ricopoetra said:
im trying to get my head around UVing / UCing my HOX. is there any guide around? im trying to search through the forum but still no luck.
Click to expand...
Click to collapse
underclocking means the CPU runs slower so should use less battery but slower CPU speeds also means to takes longer to preform tasks which could use more battery, check on google most places say its not worth it as that battery saved is tiny and not worth the drop in CPU performance.
undervolting however lowers the voltage that CPU uses while working this does save power and also lowers heat (less voltage less heat) but if you lower it to much then the CPU becomes unstable due to lack of power and well crashes and restarts the phone in most cases.
to get the best out of undervolting you need to lock the max CPU speed to each step (CPU speed, 300mhz, 600mhz and so on) and slower the voltage and then run a bench mark (like antutu) and see if its stable, if it is you lower the voltage again and repeat until it crashes at which point you have found the lowest voltage that the clock speed can handle so you jump up a voltage then more on to the next speed.
it takes along time but that would get you the best undervolt your phone and hardware could handle.
or you can just use the global to lower the voltage for every speed, this is much faster and much less time consuming but you don't get the most out of it.
for this you basically drop the voltage then use your phone for different things; browsing, games, benchmark and see if it crashes if not lower again till it does then go back up a step.
thanks for explaining. I'm getting some of the points that I missed Awhile ago. I guess I'm going to try the longer way of doing it.
Sent from my White HOX JB PA 2.10