EDIT: This app has been suspended, it serves no purpose anymore.
Last edited:
[APP] Myrt Undervolt GUI
- Thread starter TrymHansen
- Start date
-
- Tags
- themes and apps
HEEELP: "I saved the undervolt-values to the startup script without testing properly first. Now it keeps rebooting. Is there anything I can do?"
Yes. The phone cannot be damaged by undervolting, but your data might. First thing you should do is to stop the reboots by pressing and holding "Power" and "Volume Down" to enter CWM.
You will need to have ADB installed on your computer. (The following instructions are for Windows-users.)
Select "Mounts and Storage" in CWM and select "Mount /system"
o In a shell, type:
If you're using a Topogigi ROM:
If you're using anything else:
Now edit the file c:\volt_scheduler or c:\S_volt_scheduler in a PROPER editor like Notepad2 or Notepad++. DO NOT use the regular Notepad. You'll see a line with some numbers enclosed in quotation marks. Replace those numbers with zeroes. Save it.
Then type (Topogigi)
or for other roms:
If you're lucky, your phone will boot properly. If it still boot-loops, you've had some sort of corruption and need to wipe. If it still loops you've had corruption on the system partition, a full re-install (or backup-restore) is the last option.
Yes. The phone cannot be damaged by undervolting, but your data might. First thing you should do is to stop the reboots by pressing and holding "Power" and "Volume Down" to enter CWM.
You will need to have ADB installed on your computer. (The following instructions are for Windows-users.)
Select "Mounts and Storage" in CWM and select "Mount /system"
o In a shell, type:
If you're using a Topogigi ROM:
Code:
adb pull /system/xbin/volt_scheduler c:\
Code:
adb pull /system/etc/init.d/S_volt_scheduler c:\Then type (Topogigi)
Code:
adb push c:\volt_scheduler /system/xbin/volt_scheduler
del c:\volt_scheduler
adb shell chmod 755 /system/xbin/volt_scheduler
adb rebootor for other roms:
Code:
adb push c:\S_volt_scheduler /system/etc/init.d/S_volt_scheduler
del c:\S_volt_scheduler
adb shell chmod 755 /system/etc/init.d/S_volt_scheduler
adb rebootIf you're lucky, your phone will boot properly. If it still boot-loops, you've had some sort of corruption and need to wipe. If it still loops you've had corruption on the system partition, a full re-install (or backup-restore) is the last option.
Last edited:
greaatt... sadly this afternoon i already edit the script manually 
wait for some hours, and i can use this wonderful tool!
nevermind, just download & let's play with this.. (editing script every testing is kinda annoying.. )
Thanks! I use your clock adjustment tools too
wait for some hours, and i can use this wonderful tool!
nevermind, just download & let's play with this.. (editing script every testing is kinda annoying..
)Thanks! I use your clock adjustment tools too
You're very welcome.greaatt... sadly this afternoon i already edit the script manually
wait for some hours, and i can use this wonderful tool!
nevermind, just download & let's play with this.. (editing script every testing is kinda annoying..
Thanks! I use your clock adjustment tools too
thanks for ure great effort.
can you specify the UV settings that will not damage the phone?
p.s. i really like unlock silly values option
Thanks.
edit: can i use -50Mv
I wish it were that easy. Every phone is different. Mine seems to be completely stable at -75 across the board, and at 800Mhz I can run it at the lowest voltage possible, 770mV. Which is why I run everything at -50 ;-) (I learned a long time ago that balancing on the edge sooner or later makes you fall off.)
Other people have reported that their max stable undervolt is -25mV. There's no single recipe for everybody.
The correct way to test it is to set both min and max-frequencies to the same (for both awake and sleep-modes), then decrease voltage by one step, then run the toughest apps you can think of for at least 15 minutes each. If nothing weird happens, write down the numbers, decrease one step again, etc. etc. until you have found the breaking point for that particular frequency.
Then, and this is important, you need to make sure the phone is able to wake from sleep with those same values. For this you need to set sleep-mode to the normal frequencies again.
If everything works out with that, rinse and repeat with the next frequency. After you're done, you should have a nice set of numbers - increase them all by 25mV. That's your lowest stable voltage for each frequency.
Thanks!Awesome apps Trym! I downloaded this and the OC one. Left some stars on the market too.
10chars.
I guess I can easily do that from the app. Currently looking into how to best determine if a system has working init.d support.I UV by 50mv and then saved the profile with pimp my CPU and applied at boot since I use init.d
I wonder how much more battery I can squeeze more now
Sent from my LG-P990 using XDA App
EDIT: Done.
Last edited:
I don't have any more plans for it at the moment, it does what it was designed to do. Open for suggestions though. I did add support for startup-scripts on ROMs with init.d. (I modify PimpMyCpus script, if it's there, to avoid conflicting scripts. If not I create it.)
Last edited:
Long story short: Some ROMs didn't apply the settings at boot due to non-functioning init.d. So I made some changes to better discover which ROMs support it. So, in theory, if the button isn't there, you're running a ROM which it doesn't work on anyway.
This is all very new to me, If I mistakenly remove the button on ROMs where you have working init.d, please report back here with the details of the ROM. (Update to the latest version of the app first.)
I tested it on GR4 cooked with stock kernel (no working init.d support, even when you replace the kernel), GR4 cooked with custom kernel (working init.d), Fr19 (Working init.d), Topogigi (which it was originally designed for - always working) etc.
CM7 has init.d support, but refuses to set the undervolt-values both live and and boot (VorkKernel), I'm looking into that.
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
72thanks for ure great effort.
can you specify the UV settings that will not damage the phone?
p.s. i really like unlock silly values option
Thanks.
edit: can i use -50Mv
I wish it were that easy. Every phone is different. Mine seems to be completely stable at -75 across the board, and at 800Mhz I can run it at the lowest voltage possible, 770mV. Which is why I run everything at -50 ;-) (I learned a long time ago that balancing on the edge sooner or later makes you fall off.)
Other people have reported that their max stable undervolt is -25mV. There's no single recipe for everybody.
The correct way to test it is to set both min and max-frequencies to the same (for both awake and sleep-modes), then decrease voltage by one step, then run the toughest apps you can think of for at least 15 minutes each. If nothing weird happens, write down the numbers, decrease one step again, etc. etc. until you have found the breaking point for that particular frequency.
Then, and this is important, you need to make sure the phone is able to wake from sleep with those same values. For this you need to set sleep-mode to the normal frequencies again.
If everything works out with that, rinse and repeat with the next frequency. After you're done, you should have a nice set of numbers - increase them all by 25mV. That's your lowest stable voltage for each frequency.1
I don't have any more plans for it at the moment, it does what it was designed to do. Open for suggestions though. I did add support for startup-scripts on ROMs with init.d. (I modify PimpMyCpus script, if it's there, to avoid conflicting scripts. If not I create it.)1Just a heads up that it now works on VorkKernel (CM7) as well, from appversion 0.6.5.
