Related
Dirrk's Kernel Official Release
These are my kernels from samsungs crappy source! I am not responsible for you guys breaking your phone, which will happen if you do not FOLLOW THE DIRECTIONS. again FOLLOW THE DIRECTIONS.
Thanks to jt1134 for fixing voodoo, skeeterslint for helping me on the kernel builds and koush for clockwork and his ramdisk.
A lot of credit goes out to everyone in #samsung-fascinate on irc.freenode.net, they all helped contribute to jt1134s and my success and anyone who helped tests our 40+ versions before release.
If you want my source its all on github.
www.github.com/Dirrk
All of these kernels have the voodoo fix which is using ext4 for your /data partition. If you complain about your quadrant scores being lower you deserve a smack. Also sgtmack has confirmed that you can just install over jts if you choose to do so or any of my other versions.
SV = Standard Voltage and LV = Lower Voltage
Version D01 & D012 no animations
LV-1000
LV-1100
LV-1200
SV-1100
SV-1200
D02 with Animations
SV1100
SV1200
LV1000
LV1100
LV1200
LV1250
D01 & D02 Downloads
I just got the source for 2.2 and will be working on it asap.
These are clockwork installs. To be safe I would remove voodoo if you are using any of the older version already. To remove voodoo open your /sdcard/voodoo folder and make a new directory named disable_lagfix and restart your phone.
Enjoy
cool o mondo whats the dif between standard and low? and the highest is 1.2ghz right? do i need set cpu to make it work?
questions....
1. if we already have the latest 0.2 Voodoo Ext4 lagfix installed will this affect it?
2. do we need SetCPU?, i assume we do since this is a kernel not an app and i know we wouldn't be flashing an overclocking utility with no controllable GUI
If you don't use Setcpu, it will default to 800. So you can run it without, but it will be slower.
I did the remove_voodoo file thing to disable the first voodoo, then flashed this one. It worked great.
My phone doesn't like the 1200 lv kernel. I can run slower at lv, not 1.2. Every phone is different. If the lv kernel crashes, just flash the stock voltage one.
what scaling should we choose?
i installed SetCPU, chose autodetect
at first it showed 800Mhz max and 100Mhz min, after a few seconds it showed 1200max and 100min
"Conservative" is the default scaling, should we leave it that way?
jamesnmandy said:
what scaling should we choose?
i installed SetCPU, chose autodetect
at first it showed 800Mhz max and 100Mhz min, after a few seconds it showed 1200max and 100min
"Conservative" is the default scaling, should we leave it that way?
Click to expand...
Click to collapse
Conservative is the way to go...others have been known to cause issues.
so if lv doesnt work do we have to unistall it to flash sv?
No, I've been flashing over them with no problems. As long as the new kernel has voodoo, you can flash over the old one.
ok, something isn't right
already had voodoo 0.2 lagfix installed, fyi
before (with 0.2 voodoo lagfix already installed)
Linpack 8.128 MFLOPS
Quadrant 1646
after installing D01 1200LV:
Linpack 7.946 MFLOPS
Quadrant 1726
so i was like why is it slower on Linpack? rebooted
went into SetCPU, shows 1200max 100min, Set on Boot has never been checked and still isn't. conservative scaling still selected
i never had to re-do the autodetect, it went straight for 1200max 100min at boot without me doing anything
and now im getting 6.4's in Linpack......rebooted ran it, got 6.4, said meh, flaked out...ran again....6.4.....ran Quadrant, got 1481....
how exactly do we uninstall this?
Dirrk, can you share/quantify the actual voltage differences between standard and low. I'll assume standard is the max 1300mV??
jamesnmandy said:
ok, something isn't right
already had voodoo 0.2 lagfix installed, fyi
before (with 0.2 voodoo lagfix already installed)
Linpack 8.128 MFLOPS
Quadrant 1646
after installing D01 1200LV:
Linpack 7.946 MFLOPS
Quadrant 1726
so i was like why is it slower on Linpack? rebooted
...
how exactly do we uninstall this?
Click to expand...
Click to collapse
Just a suggestion: Before you uninstall, try wiping data/cache. When I was flashing all the earlier jt and Dirrk kernels, it always seemed to help with the quadrants.
I know it's not SUPPOSED to affect any of that stuff, but after a few flashes, my phone would start to act funny, and that cleared it up 100% of the time.
Good luck!
-Z
I just did the 1200 standard voltage and it is working beautifully
Seems like the downloads are the same as the ones without voodoo. Am i missing something? I dowloaded dirrk_sv1200.zip and the files in it are the same as the one before the voodoo fix.
Sent from my SCH-I500 using XDA App
doing the 1200 sv d01 dropped my quadrant score from 1805 to 1494. probably going to go back to the voodoo .02 lagfix.
johnnyv5 said:
Seems like the downloads are the same as the ones without voodoo. Am i missing something? I dowloaded dirrk_sv1200.zip and the files in it are the same as the one before the voodoo fix.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
You got to do the d01 ones.
I'm being directed to Google docs when I click the link am I missing something ?
magicriggs said:
I'm being directed to Google docs when I click the link am I missing something ?
Click to expand...
Click to collapse
That's correct. Log in and then refresh. You will see the list.
1750 quadrant/7.99 mflops on LV 1200
LV seems stable through a few rounds of benchmarks
Does LV not go up to 1200 that often or is that just me?
Q: If I install one of these kernel's would re-flashing/reverting back to the stock kernel be an easy task (just some Odin work)? Or would it be more involved?
Edit: I see that you can flash these kernel's on top of each other. I'm just wondering if you can flash the stock kernel on top of these as well or if that would cause problems. Thanks!
Hey guys, I'm currently running CM6, and when I tried to upgrade to CM7, from the version with overclocking and undervolting added, my fone always reboot and lag continously, unusable until i restore using factory reset.It never happened with any previous version of CM7. A couple day back, I tried the overclocking tweak for CM6, and the same thing happens. I have to restore using Xrecovery. Does anyone knows what the problem is ? I really want overclocking function
stable overclocking is 768 or less.... this much i knw some dev will help you
You did say that you used the overclocking patch , but did not tell did you use SetCPU with set on boot option ? Also what is ur max and min settings in setcpu ?
Anyways , not sure if you will now be able to go inside setcpu , since ur phone is restarting.
On mini pro , for me 780+ Mhz caused reboot. And if you have setcpu set to set it on each boot , then u will end up in infinite loop. For me it happened , but luckily if you do not touch ur phone (touch screen touch ;-) ) after a reboot , it wont reboot (atleast for me).;
So after a reboot :
1. connect phone to PC
2. use adb to uninstall the setcpu
3. reboot again.
This time you should not be having trouble as your phone should behave normally.
Again install setCPU (if you are interested still !!) and set the max to anything below 760Mhz.
What should we do if there is the reboot loop but setcpu is already uninstalled? Or if its installed but overclock is not set on boot?
Hey thanks for the help, but I can't do anything at all with the phone after the patch, with or without setcpu. It booted up, on lockscreen, lag for 30sec and continous reboot then -.-''
Sent from my U20i using XDA Premium App
will make much more sense letting people know what you have done. Just the normal OC module should not have ur phone rebooting.
Does the phone reboot if you do not touch it but just keep it connected to PC ? please answer or else its very hard to try and figure out an answer.
if you feel its causing an issue , then u got to figure out a way to disable that module.
The module gets loaded as x8oc.ko.
In CM6 - v4 , this is not there by default but will appear in hw_config.sh if you have patched it.
So u got to get /system/etc/hw_config.sh and comment out the line insmod for x8oc.ko and anything associate with it .
Did fresh install of v4 after factory reset, resulted in no overclock options and completely stable. Installed oc zip from cm6 oc thread which resulted in infinite reboots even when attached to pc, was not able to touch any settings. Reflashed v4 without factory reset and am back to no overclock and completely stable. Setcpu was not installed, recently installed on fresh v4, no options beyond 600mhz.
yep ..if u did a fresh install of v4 , it means the overclock is not functional as the module is not loaded in it.
Changelog for v4 says overclocked and undervolted, but never mind that. Installing oclock.zip as per instructions in that thread results in infinite reboot, does not stay up long enough to use adb shell or access setcpu. The fresh install of v4 does have overclock options in cyanogenmod settings, but values cannot be edited.
Are you implying that v4 will not support the oclock.zip or simply replying only to first sentence of explanation?
Any help is appreciated.
ok . so let me explain ( i know its quite hard on both ways ) . The overclock module (x80c.ko) is NOT loaded by the default V4 version. So if the module is not loaded Cyanogen setting will only show you the max (600 Mhz i thnk) and min (122 Mhz - I think). I did not find that module to be loaded in any of the init* scripts or in hw_config.sh. But the module is present with the build in the modules folder (but not active as its not loaded with insmod).
So if you just coming just after applying V4 - with no other patch. Then you do not have active overlocking module - hence overclocking wont work with SetCPU. Cyanogen does NOT provide you a scope to change the frequencies - you need setCPU - (you can change the max thru command line after enabling the module).
Now if you have patched the same with the oc patch , you have the module active (insmod works) , but another line of it in the hw_config.sh (patched one) does not become effective for me (some people reported it worked for them though).
The constant reboot which i faced was because i (with the help of SetCPU) had set very high frequency (causing the system to become unstable).
So inorder to fix it , you can do the following:
1. Full wipe through xrecovery
2. Apply V4 again.
3. Change hw_config.sh to add the insmod command to load x8oc.ko module.
4. Reinstall setcpu and see if you can set the max/min to safe values (say around 719 Mhz max and min as 300 or 400 Mhz).
5. If you see the system to be stable , well and good.
If by above , setCPU does not detect max/min (max should be 825 Mhz) , then you need to add the echo x27 > /proc/x8oc to hw_config just after the insmod line of x8oc.ko. (you will see some threads where sleep 2 or sleep 4 is also asked to be put in , but for unknown reason it did not work for me).
Whew!! that was long . But thats the way it worked for me.
For me when the reboots were happening , i had my phone connected to PC , but i was not touching the phone at all (if i touch , it used to reboot - but adb shell was working if i do not touch it).
If any further clarificaiton required , i would be glad to assist.
But before puting in a query , please try and give as much information was to what you did after which the reboots started (not just saying that i did the OC patch - cos for me just the OC patch never resulted into the reboots).
Thank you for that awesome explanation and sorry for the lack of relevant information earlier in the thread.
Should be able to do as you have suggested when I get home and will report back, either way your explanation has made it all clear and I can see where I have missed important steps. Many thanks.
Edit: edited hw config.sh, inserted insmod, sleep and echo lines. Stable ay 729, reboots at 748. Thanks again
good to know it worked !
same problem with my minni.... reboot again and again
Check your baseband, it must be xxx15 or it won't work because of different kernel
Nah got everything rite, basband and kernel, just when I apply the OC tweak, the fone would boot up, but freeze at lockscreen. IT DOES BOOT UP, BUT STUCK AT LOCKSCREEN !!! So bloody annoying, then stuck on bootloop until restore /system using xrecovery
Sent from my U20i using XDA Premium App
Don't apply the oversclock tweak from xrecovery, instead try editing hw_config.sh to have:
# x8 overclock
insmod /system/lib/modules/x8oc.ko
sleep 2
echo x27 > /proc/x8oc
I believe i had the same issue until i did this, then it was stable.
my mini max cpu is only 691 mhz or else the reboots and its laggy as hell. LIKE all your work every wear
have your lovely MDDI on to it help alot but still scrolling lag. maybe fresh install via seus?
wrong thread
i'm running virtuous unity ROM on my htc inspire 4g. i'm trying to underclock my phone to save battery. i read info on this from this webpage on xda:
http://forum.xda-developers.com/showpost.php?p=14529333&postcount=5
in the 'wake governor' file, its originally set to 'ondemand'. i'd like to edit it to save battery, but not to kill too much smooth performance. below are the options given. can you please rank the the following in terms of performance and battery life? and which is the best for my needs?
- SavagedZen
- Scary
- smartass
- interactive
- conservative
- userspace
- ondemand
- performance
.
There's now smartass v2, has all the benefits of smartass(no set cpu required, v. quick swiych of freq. after screen on/boot) but also v. stable. It's built in to my custom kernel (xperi arc) but google it
sinkster
sinkster said:
There's now smartass v2, has all the benefits of smartass(no set cpu required, v. quick swiych of freq. after screen on/boot) but also v. stable. It's built in to my custom kernel (xperi arc) but google it
sinkster
Click to expand...
Click to collapse
hi, sinkster.. thanks for the reply. but i really dont know what these terms mean. can you tell me what ranking they have on a scale from 1 to 10 in terms of battery life and also in terms of perfomance?
this is importsnt for me to decide what to set my phone at. especially when i want to save battery but at the same time, not sacrifice performance. thanks.
trapzz said:
hi, sinkster.. thanks for the reply. but i really dont know what these terms mean. can you tell me what ranking they have on a scale from 1 to 10 in terms of battery life and also in terms of perfomance?
this is importsnt for me to decide what to set my phone at. especially when i want to save battery but at the same time, not sacrifice performance. thanks.
Click to expand...
Click to collapse
The rom your running has its own custom kernel, which still only has the original smartass governor, which the thread you posted a link to talks about the flaws of it and came up with their own solution to bypass those flaws. There is a newer version of the smartass governor that fixes those flaws, so you dont have to manually edit the files that the thread is talking about doing, like your trying to do. In order to get the new version of the smartass governor, the developer of the kernel that your rom's dev. is using has to update it (i would recommend searching the forum for the original thread of the kernel). Or you could find another kernel that will work with your current rom but is also updated that includes the new smartass governor. As for the differences of the profiles, Smartass seems to be the most complex but best option for saving alot of battery while not affecting performance of the phone. It saves battery while the screen is off, and when the phone doesnt need to use its cpu fully. It basically learns and throttles between the cpu frequencies you have set based on phone usage while always using the bare minimum frequency while the screen is off and when no applications are being used and a higher/highest frequency you have set for when your using applications so they still run smooth. I would recommend getting Setcpu, it will detect what frequencies your phone is capable of and will allow you to set the smartass governor and the min/max frequencies for it to throttle between. I would also search your Rom's thread and the Kernel's thread(if there is one) to see what the min/max frequency people are having pleasant experiences with.
Synergies14 said:
The rom your running has its own custom kernel, which still only has the original smartass governor, which the thread you posted a link to talks about the flaws of it and came up with their own solution to bypass those flaws. There is a newer version of the smartass governor that fixes those flaws, so you dont have to manually edit the files that the thread is talking about doing, like your trying to do. In order to get the new version of the smartass governor, the developer of the kernel that your rom's dev. is using has to update it (i would recommend searching the forum for the original thread of the kernel). Or you could find another kernel that will work with your current rom but is also updated that includes the new smartass governor. As for the differences of the profiles, Smartass seems to be the most complex but best option for saving alot of battery while not affecting performance of the phone. It saves battery while the screen is off, and when the phone doesnt need to use its cpu fully. It basically learns and throttles between the cpu frequencies you have set based on phone usage while always using the bare minimum frequency while the screen is off and when no applications are being used and a higher/highest frequency you have set for when your using applications so they still run smooth. I would recommend getting Setcpu, it will detect what frequencies your phone is capable of and will allow you to set the smartass governor and the min/max frequencies for it to throttle between. I would also search your Rom's thread and the Kernel's thread(if there is one) to see what the min/max frequency people are having pleasant experiences with.
Click to expand...
Click to collapse
hi, Synergies14.. i truly do appreciate your in depth info. i got 3 questions:
1) you suggested i use 'smartass' as the best option to save battery life. but dont you think that this option sounds like a battery draining option?
2) you suggest i use smartass as the best option for increasing battery life. i set 'smartass' as the option for wake governor. should i also apply it to sleep governor? the sleep governor is currently set to conservative. let me know.
3) can you explain rank each of the 8 terms in terms of battery life and perfomance?
thank you. i appreciate it.
trapzz said:
hi, Synergies14.. i truly do appreciate your in depth info. i got 3 questions:
1) you suggested i use 'smartass' as the best option to save battery life. but dont you think that this option sounds like a battery draining option?
2) you suggest i use smartass as the best option for increasing battery life. i set 'smartass' as the option for wake governor. should i also apply it to sleep governor? the sleep governor is currently set to conservative. let me know.
3) can you explain rank each of the 8 terms in terms of battery life and perfomance?
thank you. i appreciate it.
Click to expand...
Click to collapse
Trapzz, my apologies for not responding to your post back on the 17th. As to question 1, the answer is no. The smartass governor throttles your cpu frequency based on the min/max frequencies you have set in Setcpu for when the screen is off, even if the screen is on and your not using any performance hog apps. The smartass governor is alot better at throttling between the frequencies than any of the other governors. For example, while your screen is off, it will have the cpu using the minimum frequency, even if the screen is on and your looking at text messages, it will only raise the frequency untill the text messages load and then it will scale back down after its done loading. Other governors keep the frequency raised the whole time your in your text messages, even after its loaded, untill you exit it and turn the screen off.
As for question 2, you shouldnt have any profiles set while using the smartass governor, as how the smartass governor works, you dont need any profiles set. Smartass takes care of it all on its own.
As for question 3, im not exactly sure how to rank each governor based on performance/battery life besides other than conservative is used for battery life, and performance is for performance and not saving battery. But with how smartass works, its auto scales the frequencies automatically. Its the best for saving battery, but its also best for performance as it scales to the highest frequency you have set and keeps it there for as long as your app needs it.
Hope i helped answer what you were asking! If you need anything else or any other questions feel free to reply or shoot me a personal message.
Sent from my Mik'd Supersonic OG Evo using xda premium
Synergies14 said:
Trapzz, my apologies for not responding to your post back on the 17th.
As for question 2, you shouldnt have any profiles set while using the smartass governor, as how the smartass governor works, you dont need any profiles set. Smartass takes care of it all on its own.
Click to expand...
Click to collapse
hi, Synergies14.. thanks for getting back to me.. no need to apologize, but thanks anyway.
you said that i shouldnt set any profile while using the smartass governor. i'm a bit confused. what exactly do you mean? do you mean that i shouldnt enter any values for the 3 wake and sleep states?
and do you also mean that i shouldnt set 'smartass' for sleep governor?
trapzz said:
hi, Synergies14.. thanks for getting back to me.. no need to apologize, but thanks anyway.
you said that i shouldnt set any profile while using the smartass governor. i'm a bit confused. what exactly do you mean? do you mean that i shouldnt enter any values for the 3 wake and sleep states?
and do you also mean that i shouldnt set 'smartass' for sleep governor?
Click to expand...
Click to collapse
You are running Setcpu, correct?
Sent from my PC36100 using xda premium
My apologies, it seems that your not, your actually manually editing files for it. I dont have access to a computer right now but i will soon and i will help you futher.
Sent from my PC36100 using xda premium
---------- Post added at 10:27 PM ---------- Previous post was at 09:33 PM ----------
trapzz said:
hi, Synergies14.. thanks for getting back to me.. no need to apologize, but thanks anyway.
you said that i shouldnt set any profile while using the smartass governor. i'm a bit confused. what exactly do you mean? do you mean that i shouldnt enter any values for the 3 wake and sleep states?
and do you also mean that i shouldnt set 'smartass' for sleep governor?
Click to expand...
Click to collapse
Alright, i apologize, i got a bit confused myself there. Judging from your Rom and what the Devs of it say, DO NOT install setcpu like i have mentioned. You will need to install a terminal app. You can go to the market and search for the app "Android Terminal Emulator" and install it. Then in the terminal app, type in "cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors" (without the quotation marks) and that will give you a list of available governors to use. Tell me the list of governors it gives you. Then type in "cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies". That will tell you the available Min/Max frequencies that your phone will allow. Tell me the list of frequencies that it gives you. Then i shall help you from there after providing that info to me.
A better option would be to undervolt by 25mv a time if ur kernel supports it
Synergies14 said:
You will need to install a terminal app. You can go to the market and search for the app "Android Terminal Emulator" and install it. Then in the terminal app, type in "cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors" (without the quotation marks) and that will give you a list of available governors to use. Tell me the list of governors it gives you. Then type in "cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies". That will tell you the available Min/Max frequencies that your phone will allow. Tell me the list of frequencies that it gives you. Then i shall help you from there after providing that info to me.
Click to expand...
Click to collapse
hi synergies.. below are the available governors and frequencies on my phone:
governors:
SavagedZen
Scary
smartass
interactive
conservative
userspace
ondemand
performance
freqs:
245760 368640 768000 1024000 825600 844800 864000 883200 902400 921600 940800 960000 979200 998400 1017600 1036800 1056000 1075200 1094400 1113600 1132800 1152000 1171200 1190400 1209600 1228800 1248000 1267200 1286400 1305600 1324800 1344000 1363200 1382400 1401600 1420800 1440000 1459200 1478400 1497600 1516800 1536000 1555200 1574400 1593600 1612800 1632000 1651200 1670400 1689600 1708800
Actually can you update your Rom first? if you haven't updated it, there is an update for it that came out a few days ago, before we do anything i want to make sure you have the latest piece of the software.(updating might actually help with the call vibration issue your having too). If you update it, tell me if you have a custom kernel installed or if you leave it with the stock kernel that the rom uses. The type of kernel you use will affect your available frequencies and also if everything is outdated. After you update your Rom, look to see if there is a program on there called "Daemon Controller". If not, then follow this link http://bit.ly/oDeBtV and install the .apk on your phone. This is the new graphical UI for changing and managing your virtuous_oc so you dont have to manually edit the files yourself.
Synergies14 said:
Actually can you update your Rom first? if you haven't updated it, there is an update for it that came out a few days ago, before we do anything i want to make sure you have the latest piece of the software.(updating might actually help with the call vibration issue your having too). If you update it, tell me if you have a custom kernel installed or if you leave it with the stock kernel that the rom uses. The type of kernel you use will affect your available frequencies and also if everything is outdated. After you update your Rom, look to see if there is a program on there called "Daemon Controller". If not, then follow this link http://bit.ly/oDeBtV and install the .apk on your phone. This is the new graphical UI for changing and managing your virtuous_oc so you dont have to manually edit the files yourself.
Click to expand...
Click to collapse
hi synergies. the problem with the update to my rom (virtuous unity), is that its got some issues. but i'll install it. and hopefully i wont experience the same issues.
one other important thing.. how do i do a EXT4 wipe?
.
trapzz said:
hi synergies. the problem with the update to my rom (virtuous unity), is that its got some issues. but i'll install it. and hopefully i wont experience the same issues.
one other important thing.. how do i do a EXT4 wipe?
.
Click to expand...
Click to collapse
I recommend doing a full nand backup before upgrading so that way if you do run into any issues that you dont like, you can just restore from that nand backup. What Recovery are you using?
Synergies14 said:
I recommend doing a full nand backup before upgrading so that way if you do run into any issues that you dont like, you can just restore from that nand backup. What Recovery are you using?
Click to expand...
Click to collapse
hi synergies.. i'm backing up through booting into recovery.
trapzz said:
hi synergies.. i'm backing up through booting into recovery.
Click to expand...
Click to collapse
Thats good. I need to know what recovery your using so i can help you with doing a ext4 wipe.
Synergies14 said:
Thats good. I need to know what recovery your using so i can help you with doing a ext4 wipe.
Click to expand...
Click to collapse
hi synergies.. i dont understand your question. the recovery i use is the one rooted users use... i boot into recovery and choose backup and restore and then backup my phone.
trapzz said:
hi synergies.. i dont understand your question. the recovery i use is the one rooted users use... i boot into recovery and choose backup and restore and then backup my phone.
Click to expand...
Click to collapse
There are different types of recovery that have different names, when u boot into your recovery it should tell you the name and version of the recovery your using
Sent from my Blazed out OG Evo using xda premium app.
Synergies14 said:
There are different types of recovery that have different names, when u boot into your recovery it should tell you the name and version of the recovery your using
Click to expand...
Click to collapse
hi, synergies. i got clockworkmod revovery v3.0.2.5.
trapzz said:
hi, synergies. i got clockworkmod revovery v3.0.2.5.
Click to expand...
Click to collapse
Alright, when you boot into recovery, as always, make a nand backup (as you've said you have already). When you wipe, please note that everything will be erased from your phone including all apps and settings, EVERYTHING. Also as a precaution, ALWAYS go into your contacts in your phone and select to export them to your SDcard. Then connect your phone to your computer and copy EVERYTHING thats on your sdcard to your computer (easily make a folder on your desktop, then select everything on your sdcard, copy it and paste it into the folder). This is so that all your contacts and all your pics/videos and your nand backup are backed up on your computer just incase the wiping process does completely wipe your sdcard (i highly doubt your sdcard will be erased, but its always good practice to take extreme caution as accidents do happen). Then copy the new Rom's zip file onto your sdcard.
*Once you have done all this, boot back into your recovery.
*From the main menu, select "wipe data/factory reset".
*Once that is done, select "wipe cache partition".
*Once that is done, select "mounts and storage".
*In that menu, select "format system".
*Once that is done, select "format data".
*Once that is done, select "format cache".
*Then, judging that you have ext4, i assume your sdcard is partitioned and has the ext on it, if you do, then select "format sd-ext".
*Then go back to the main menu.
*Select "advanced".
*Select "wipe dalvik cache".
*Return to the main menu. Now to install the rom!
*Select "install zip from sdcard".
*Select "choose zip from sdcard".
*A list will appear of the files on your sdcard, select the rom's zip from the list.
*It will ask to confirm installing the zip, go ahead and confirm.
*Once it is done installing, you should be back at the main menu, if not, navigate back to the main menu.
*Select "reboot system now" and you should now reboot into the new ROM. If you have any issues during this process with any of the steps let me know!
also, to get your contacts back into your phone, judging that your sdcard wasnt erased, go into your contacts and select to import from sdcard and you should be good to go!.
I installed Setcpu everything was working great till I lowered the the minimum Frequency to around 700MHZ & I checked the "Set On Boot". It started to reboot the phone continuously I went back unchecked the "Set on Boot" which helped but when I go back in Setcpu it would reboot again.
I tried setting the frequency to the max & it would freeze & reboot quicker. I tried putting the Setcpu safemode in the root of the sd card but it didnt do anything.
I uninstalled SetCpu & updated the RUU on my Rezound it solved the reboots & it seemed everything was running as normal until when the phone was auto-syncing the phone froze for about 10-seconds then everything was back to normal. I heard about flashing the .zip file but I don't know how & I'm not installing Setcpu again to find out.
I'm wondering if the freeze had anything to do with the SetCpu. Everything is deleted once you update the RUU so I don't believe there should be any left over files from the SetCPU. I'm not sure if there on my sd card I was thinking of formatting the SD.
It would never freeze like that before I installed the new update but I never did have Setcpu installed once I got the phone. So I'm wondering if this problem lies with the Setcpu or the new RUU update for the Rezound which is 2.01.605.11?
Probably SetCPU, if you tweak the setting too much (or putting it in awkward settings) it can create errors.
Might have to do with which kernel you are running. Some kernels, such as dsb, play better with certain cpu apps. dsb likes Antutu CPU Master.
Hmm could be something on the user side like kernel or perhaps if you installed a bad downloaded stock rom because I have have been using setcpu since day one with no errors on stock kernel on any rom. If you had a kernel installed prior it may still be installed which allows the cpu to ramp up to unstable speeds such as >1512 mhz.
Even if you were to try set an OC kernel to stable speeds, it will always ramp up to highest speeds, even higher than set. All in all, I would recommend to reflash stock kernel and made sure to flash boot.img which is most important. Hope this helps!
feralicious said:
Might have to do with which kernel you are running. Some kernels, such as dsb, play better with certain cpu apps. dsb likes Antutu CPU Master.
Click to expand...
Click to collapse
eh, dsb hasn't given me problems with SetCPU.
Weird
I only use setCPU, I have all the other ones too just about but they are all uninstalled because they usually just don't work as well, I use incredicontrol for undervolting, and that's it. Dsbs works with incredicontrol too... The kernel could be the issue and not the app but who knows
I'm trying to undervolt the CPU to squeeze as much battery life out of my phone as possible. I've been playing around with the Awesome Sauce and Enoch kernels, both of which should support user controlled undervolting. I'm running Viper4G and was able to flash both kernels no problem...the kernel info in Settings reflects the appropriate kernel after flashing. My problem though, is that I haven't been able to undervolt with either of them using any of the usual apps (SetCPU, Voltage Control, No Frills, System Tuner).
With SetCPU, I can modify the voltages and I see my custom voltages in the "Saved" section, but the "Current" voltages are still stock. This persists through reboot...my custom voltages are still saved, but they never become the current voltages.
With Voltage Control, the voltages just display as "Not Detected: 0mv".
With No Frills, I don't even see a voltage menu.
With System Tuner, I can modify the voltages but I get a popup saying "Voltages will not be saved after reboot. Check boot settings." If I go in and change it to apply the CPU settings on boot, I still get the same message. Same with applying in the init script.
So something obviously isn't right here. For both kernels, I've tried flashing the entire boot.img via fastboot as well as just the kernel via recovery with the same results. Since the one constant here is Viper4G, I'm wondering if the OC Daemon is preventing any changes from being made. I've checked the Viper Control script and it does say that the daemon is not running, so I'm not sure. Has anyone else been able to change voltage with either of these kernels? If so, what ROM are you on and which app did you use?
Thanks in advance...
premo15 said:
I'm trying to undervolt the CPU to squeeze as much battery life out of my phone as possible. I've been playing around with the Awesome Sauce and Enoch kernels, both of which should support user controlled undervolting. I'm running Viper4G and was able to flash both kernels no problem...the kernel info in Settings reflects the appropriate kernel after flashing. My problem though, is that I haven't been able to undervolt with either of them using any of the usual apps (SetCPU, Voltage Control, No Frills, System Tuner).
With SetCPU, I can modify the voltages and I see my custom voltages in the "Saved" section, but the "Current" voltages are still stock. This persists through reboot...my custom voltages are still saved, but they never become the current voltages.
With Voltage Control, the voltages just display as "Not Detected: 0mv".
With No Frills, I don't even see a voltage menu.
With System Tuner, I can modify the voltages but I get a popup saying "Voltages will not be saved after reboot. Check boot settings." If I go in and change it to apply the CPU settings on boot, I still get the same message. Same with applying in the init script.
So something obviously isn't right here. For both kernels, I've tried flashing the entire boot.img via fastboot as well as just the kernel via recovery with the same results. Since the one constant here is Viper4G, I'm wondering if the OC Daemon is preventing any changes from being made. I've checked the Viper Control script and it does say that the daemon is not running, so I'm not sure. Has anyone else been able to change voltage with either of these kernels? If so, what ROM are you on and which app did you use?
Thanks in advance...
Click to expand...
Click to collapse
Smw6180 posted somewhere on viper thread how to disable oc daemon. You should do a search on that thread. You are correct about system tuner, you need to undervolt every time you reboot the phone.
Sent from my lair.