Has anyone damaged there s2 from undergoing?
Is there a possibility that you can damage your phone from undervolting?
Sent from my GT-I9100 using Tapatalk 2
davegermiquet said:
Has anyone damaged there s2 from undergoing?
Is there a possibility that you can damage your phone from undervolting?
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
It's a good experiment but the processor may be pushed into an usafe operating area where some people may find theirs can't cope. If it was safe the manufacturers would be doing it as standard. Don't do it if you need it to be 100% reliable. As an experiment it's very interesting and may give some worthwhile gains.
It's not going to be laggy but if you can stand a reduction in performance then slowing the clock speed is a safer way to save battery, rather than reduced voltage.
---------- Post added at 09:55 AM ---------- Previous post was at 09:44 AM ----------
Overclock and overvolt terms are very common on computer PC. However, this will increase power usage and generate more heat. Not so good to try it on smartphone. So the other ways ~ underclock and undervolt should be better on smartphone like Samsung Galaxy S II, right? Yes, to improve battery life. Underclock may not be so efficient in performance / walt ratio. But undervolt surely will improve battery life while maintain the overall performance speed.
For example, by underclock from 1.2 GHz to 1 GHz, speed performance drops 16.67% but voltage usage drops 6% only from 1250 mV to 1175 mV. Therefore, it is better to just undervolt only and keep the highest speed stage. Let’s say by reducing voltage from 1250 mV to 1150 mV at 1.2 GHz speed stage, you will get 8% voltage usage reduction while maintaining 1.2 GHz speed.
How to undervolt Samsung Galaxy S2?
1.Install custom kernel that support undervolt.
2.Install SetCPU.
3.At Voltages tab, select the desire value for each speed stages.
4.Note – try to reduce 25 mV each time.
5.Click Apply then.
6.Run Stress test ~ Stress CPU to test stability (located at Info tab).
7.That’s all.
Note – Only check ‘Set on Boot’ when you are confident that the undervolted values won’t hang and stable all the time.
Each phone has its own CPU chipset. Other people’s SetCPU voltages settings may not work for you. Therefore, you need to try lot of the settings until you get the lowest voltages and stable for daily use.
Yes. But is there potential that it will damage the phone permanently? Can it wreck the cpu?
Sent from my GT-I9100 using Tapatalk 2
Very unlikely. You are far more likely to damage your phone/reduce the life of the CPU by overvolting/overclocking (logical).
Most damage is caused by users not bothering to read and follow instructions/stickies etc exactly.
Can't see electronically how UV would cause any damage to semiconductor components or electrical circuits. Maybe software issues caused by freezing or forced reboot or battery pull though.
Sent from my GT-I9100 using xda premium
Main "potential danger" issue with UV, aside from poor stability and pointless "gains", is the CPU may write bad data to memory (volatile OR non-volatile) causing corruption. This can be recovered, generally, but not if it writes rubbish to the low level "boot" areas.
just dont set the voltage tweaks on boot so if you settings goes wrong
your phone restart and its back to stock voltages
than you can try new settings
i have UV mine from the kernel test thread values and its smooth and battery life is improved
Related
What's the purpose of overclocking and undervolting. What's the reason for the undervolting?
Sent from my ADR6400L using XDA App
It reduces CPU temperature and the amount of battery needed. It is especially useful when you overclock your CPU as both benefits are seen then.
Undervolting typically increases instability, unless it is also in conjunction with underclocking.
If you overclock, you might add voltage to keep the processor running higher than its rated speed. Similarly, if you drop the clock cycles, you may be able to drop voltage and run a cooler, more power-friendly processor.
I am currently underclocking to 768MHz on stock voltage.
Is that why with the speedtweak on 1.92 with the under volting makes the phone lock up.
Sent from my HTC ThunderBolt using XDA App
Likely. The only time I experienced frequent locks was when I was undervolted extremely. If you're running an overclocked and undervolted simultaneously you increase the odds that the cpu won't have enough juice to run properly.
Virtually every device will tolerate speedtweak's extreme undervolt/overclock to 1.41GHz with complete stability. Most will also remain stable running within stock voltage up to 1.222GHz. I've never been a fan of running with a hard cap on speed. Adjusting governor settings makes more sense. I'm also thinking underclocking and using HTC stock voltage scaling is a waste since the CPU will definitely remain more stable at more extreme undervolting at those speeds. Some kernels will run well with a minimum voltage of 650.
1st : My understands
So I'm completely new on the undevolting science and don't know if I understood everything correctly... For me, undevolting the cpu means : reduce power consumption for the same speed, so we can minimize the battery drain and have the same performance at high frequencies. Am I right?
I also understood that if we UV too much, the phone will be buggy/freeze. Is there any other risk I should be aware?
2nd : My statements
I start to UV my phone tonight and now I'm quite surprised to see how low I can go : I'm running at 1200MHz / 600mV (instead of the stock 1275mV) and the phone is solid stable (I don't know if I can go slower though, I was a bit scared and decided to post this message before continuing). So how do I check setcpu applied the settings correctly? To check system stability I use setcpu's stress test for about 2mins (the short test between two settings), then about 10mins (the big test for the final seting) and finally my feelings using my phone as a daily usage. Am I doing it right?
What are the common values at the UV exercise?
3rd : Some wtf in my head
If our phones can handle a so low value (compared to the stock one), why is it so high by default? I understand that, for stability and because every device is different, sammsung could not use the lowest value, but even some 100mV could improve the battery life of the phone, and since not everybody is tweaking his phone as us, it would have made an even greater phone OTB...
PS : my configuration
Phone/Pda/CSC : XXKG5
Kernel : ninphetamine 2.0.5
Yes, lower voltage is better but not all chips will take it. With undevolting the main risk is random instability or reboots, if you get a reboot just scale your uv back by 25mv and see what happens.
As far as why the voltages are what they are, for a chip as young as the one in the sgs2 there is a lot of variance in the chip, not all will be as "good" as others, so samsung bin (select) them to hit the clock they do at the voltage they do at a certain yield (aka not to many chips unable to hit the needed specs).
Maybe in the future the stock voltage will be lower, but for the time being we can tweak and see if we got a gold sample (better than standard) chip.
Also as far as your uv settings, you are not at 600 or something mv, the kernel has a hard lower limit of 800mv, even if it slows something below that in setcpu, the minimum the kernel will give the cpu is 800mv.
Sent from my GT-I9100 using XDA Premium App
Thank you very much for your quick reply ! And sory for being late too ^^
I indeed re-read more carefully Ninpo's thread and saw his kernel can UV from 800mV to 1500mV. Btw I think because 600mV was under the limit, stock setting was applied.
So after a day of testing, I can say my phone handle 200MHz / 825mV, 500MHz / 850mV, 800MHZ / 950mV, 1GHz / 1075mV and 1,2GHz / 1150mV with no problem at all And now, my battery will last forever
skuizy said:
Thank you very much for your quick reply ! And sory for being late too ^^
I indeed re-read more carefully Ninpo's thread and saw his kernel can UV from 800mV to 1500mV. Btw I think because 600mV was under the limit, stock setting was applied.
So after a day of testing, I can say my phone handle 200MHz / 825mV, 500MHz / 850mV, 800MHZ / 950mV, 1GHz / 1075mV and 1,2GHz / 1150mV with no problem at all And now, my battery will last forever
Click to expand...
Click to collapse
To make it last forever you want to set it to 0mV
Just don't set 200mhz to low or your phone may suffer from the sleep of death where it won't wake up.
Sent from my GT-I9100 using XDA Premium App
veyka said:
To make it last forever you want to set it to 0mV
Click to expand...
Click to collapse
Haha, if I could do it !!!
Thanks for the advice, if it doesn't wake up, I'll put the 200MHz voltage a bit higher
What are the best settings to have you phone's CPU speed set at? I'm looking for both good performance and good battery. Also I am using the default overclocker, what is the best one? Thank you guys for your time.
Sent from my LG-VM670 using XDA Premium App
I use SMARTASS as my CPU speed governor and I set my CPU to 480-748 MHz, seems pretty stable for me.
Sent from my LG-VM670 using xda premium
thaunknownartist said:
What are the best settings to have you phone's CPU speed set at? I'm looking for both good performance and good battery. Also I am using the default overclocker, what is the best one? Thank you guys for your time.
Sent from my LG-VM670 using XDA Premium App
Click to expand...
Click to collapse
Overclocking values differ from phone to phone. Test it out with different values and use the one which is stable for you.
This was just discussed in the IHO technical-discussion thread, as a matter of fact.
My phone is stable for most stuff at 806 MHz, but sometimes the camera will cause a freeze/reboot. So I run at a 786 MHz max. Your phone will be different; this has to do with minute physical differences between individual chips.
The thing to keep in mind when overclocking is that the processor in our phone (unlike those of many other phones) does not make use of dynamic voltage scaling. There are only two voltage levels: a lower one if the phone is running at or below (or is it just below? correct me if I'm wrong, guys) 480 MHz, and a higher one if the phone is running above. So below 480 MHz, the system will give the processor a certain amount of voltage (period), and above, the processor will get a certain higher amount of voltage (period).
Because of that, the tests that have been done indicate that 806 MHz is the sweet spot for battery efficiency when the phone is in use--and the closer you get to 806, the better. Thus, I've had the following settings for quite some time:
786 MHz min
786 MHz max
Performance governor
which has treated me pretty well. On a day of light to moderate use, I'd end up with 65-75% battery left (occasionally more like 80%), depending on cell signal where I am et al. And it gives me probably the best performance I'm gonna get out of this phone.
However, I very recently decided to change the minimum to below that 480 MHz threshold and see what a lower voltage when idling would do for my battery life. My current settings are:
320 MHz min (may change to 480)
786 MHz max
Smart*** governor
There is actually a noticeable performance decrease when I first wake the phone up, so I may switch governors as well. In any case, I've had those settings for only one full day now, but for that one day the battery life was noticeably better. I'll post an update when I've had a few more days to test.
As always, it's difficult to quantify battery life in a reliable/rigorous manner (much less a universally applicable one), so YMMV.
First of all, I am totally new to this forum.(I mean as an registered user)
Before that I always had the thing from the forum what I needed.
Now here is my question,
If i overclock the processor speed of my android device to a higher position, isn't it gonna take more battery power than usual?
Phone model: Xperia Live With Walkman
Boot loader: unlocked
Root Access: Rooted
Kernel: Rage 3.2
ROM: Real ICS r6
overclocking is going to drain your battery obviously.
overclocking drains more battery but gives better performance,too much over clocking makes phone heat & even hardware issues
saqib nazm said:
overclocking drains more battery but gives better performance,too much over clocking makes phone heat & even hardware issues
Click to expand...
Click to collapse
My phn's original capacity is 1 Ghz
How much overclocking can keep my battery level fair and also give smoother performance without causing me any hardware issue?
Btw, Thx for the ans.:good:
Saimoon said:
My phn's original capacity is 1 Ghz
How much overclocking can keep my battery level fair and also give smoother performance without causing me any hardware issue?
Btw, Thx for the ans.:good:
Click to expand...
Click to collapse
Power consumption = Voltage x Voltage x cpufreq x some constant for your device. If you OC (raise the cpufreq) you will have more power consumption and more heat generation because most of the power is dissipated as heat and the heat is what damages your cpu. It is probably impossible to kill your cpu in one go, because your device should shut off when it begins to over heat (this will look like a random reboot). But you will slowly degrade the over all performance of your cpu and eventually you get to a point where you see a lot of random reboots. So if you decide to OC you probably want to also undervolt as well. This is because power consumption (and heat) scale with the square of the applied voltage. One rule of thumb is that your maximum cpufreq is actually determined by the voltage. For example, my cpu is rated to be stable at 1 GHZ and 1200 mV, so when I OC and UV, I scale the cpufreq as high as I can go, as long as the voltage is not greater than 1200 mV, for me this is 1.5 GHz.
Also remember that your cpu governor will have a big effect on your power consumption and it is probably doing a good job keeping the cpu running in the low range of the cpufreq table, so you are unlikely to see big effects of OC or UV on real life battery consumption.
every chipset is different, even though the brand and model is the same. noone can guarantee you any safe value to overclock.
Thanks Giving!
Thanks Everybody for helping me out!
I am applying 1.402 GHz :laugh:
Overclocking is not the only thing you have to think of in order to improve your phone's overall performance. The most important issue for me is choosing the right kernel and applying the right governor + I/O scheduler. From my experience with Mini (i have tried ALL available kernels and most of ROMs) I can surely say that now with my phone (ICS .587, custom ROM + kernel) overclocked to 1.5 GHz battery with minimal use (20 mins calls, 40 mins WiFi per day) lasts at least 60 hours. When I bought my phone (GB, no OC, all stock) battery was struggling to stay alive for 24 hours with the same minimal use. Conclusion: first pick the right kernel and ROM, then OC.
What is the difference between undervolting and underclocking? What does each do to battery life, performance, etc.
Also, what are the best, stable undervolting and underclocking value for the Rezound? I'm running Neo's Tron rom
gleggie said:
What is the difference between undervolting and underclocking? What does each do to battery life, performance, etc.
Also, what are the best, stable undervolting and underclocking value for the Rezound? I'm running Neo's Tron rom
Click to expand...
Click to collapse
Undervolting is lowering the amount of power the processor draws at a certain frequency. Let's say, for example, a processor uses 1025mV at 1.18GHz normally. If you lower the voltage to 975mV for that frequency (using System Tuner or something similar) that's undervolting. If you lower the voltage too much the device will be unstable and reboot.
Underclocking is lowering the top speed of a processor. On our Rezound, the maximum speed of our processor is 1.5GHz stock. If you lower the maximum speed to 1.18GHz that's underclocking. Obviously lowering the maximum speed of the processor will decrease the performance of the device somewhat, depending on how much you lower it and what you're doing. Just getting on Twitter and XDA you might not notice the difference in speed, but during gaming it'll become more prevalent.
There isn't an established "best" amount to undervolt by, as each device is different. One device might be able to undervolt by 50mV with no problems, while another might not be able to handle any undervolting at all. If you're using the latest version of TRON ROM you should already be on Snuzzo's FunkyBean kernel, which has been undervolted by 50mV at every frequency.
Undervolting is also a subjective thing. Some people choose to go with 1.18GHz, while others may choose something higher than that, like 1.35GHz. It all depends on how you use your device and how you want it to perform. I suggest trying out something around 1.24GHz and seeing if it's alright with you. If it's too laggy just raise the speed bit by bit until you're satisfied with it.
I'm sorry for the long winded reply, but I wanted to make sure I covered everything.
Sent from my ADR6425LVW using XDA Premium.
SteveG12543 said:
Undervolting is lowering the amount of power the processor draws at a certain frequency. Let's say, for example, a processor uses 1025mV at 1.18GHz normally. If you lower the voltage to 975mV for that frequency (using System Tuner or something similar) that's undervolting. If you lower the voltage too much the device will be unstable and reboot.
Underclocking is lowering the top speed of a processor. On our Rezound, the maximum speed of our processor is 1.5GHz stock. If you lower the maximum speed to 1.18GHz that's underclocking. Obviously lowering the maximum speed of the processor will decrease the performance of the device somewhat, depending on how much you lower it and what you're doing. Just getting on Twitter and XDA you might not notice the difference in speed, but during gaming it'll become more prevalent.
There isn't an established "best" amount to undervolt by, as each device is different. One device might be able to undervolt by 50mV with no problems, while another might not be able to handle any undervolting at all. If you're using the latest version of TRON ROM you should already be on Snuzzo's FunkyBean kernel, which has been undervolted by 50mV at every frequency.
Undervolting is also a subjective thing. Some people choose to go with 1.18GHz, while others may choose something higher than that, like 1.35GHz. It all depends on how you use your device and how you want it to perform. I suggest trying out something around 1.24GHz and seeing if it's alright with you. If it's too laggy just raise the speed bit by bit until you're satisfied with it.
I'm sorry for the long winded reply, but I wanted to make sure I covered everything.
Sent from my ADR6425LVW using XDA Premium.
Click to expand...
Click to collapse
Thanks for the thorough response!