I found that I was having an issue with most of the new kernels and after much research I found that it was due to the HAVS being very aggressive from stock to make the kernel better at battery preservation.
To fix this you need to build a script and dump it on your phone so it loads every boot. This was hard to find all the info in one place so I figured I would put it all together here.
Ok here we go, first grab the file you need from your phone doing a cut and paste of the following commands
adb shell
cat /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs
Copy and paste this out into a text editor
Then adjust the script voltages such as I did in the following example
#!/system/bin/sh
echo "19200 975 1000" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs
echo "128000 1000 1025" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs
echo "245000 1000 1025" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs
echo "384000 1000 1025" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs
echo "422400 1000 1050" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs
echo "460800 1000 1050" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs
echo "499200 1000 1050" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs
echo "537600 1025 1075" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs
echo "576000 1050 1100" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs
echo "614400 1050 1125" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs
echo "652800 1100 1150" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs
echo "691200 1100 1175" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs
Just change the numbers in the right to match what voltage you need to use to keep your phone from rebooting.
Now we need to get the file on the phone but we need permissions so run
adb remount
once you do that you need to push the script back to the phone using the adb push command
adb push c:\filename /etc/init.d/filename
This will put the file there but you need to chanage the permissions so that it can run on each boot.
adb shell
chmod 755 /etc/init.d/filename
once this is done you can reboot again to dump the values or you can do the following command.
./etc/init.d/filename
That should do it
YOu can do to check
cat /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels_havs
The above values were just ones I was playing around with my phone seems to have issues at the bottom of the range so I bumped those up a bit and it seemed to work fine!
Let me know if you need any help with this as it was a pain finding all the info and putting it all together.
Props to ziggy at http://www.ziggy471.com/2011/01/21/beta-kernel-21-jan-11/
as he was the one where I got most of the info.
like which kernels and what versions would this apply too?
I have had to do it to the SZ and Tiamat kernels, but this is only if you phone is boot looping with the stock and you believe its due to voltage. I was having a problem with ever rom and kernel that was using HAVS with my phone and this was the only way I could get it to boot and stabilize.
Again its not for everybody and I would assume that you can make you phone not boot, but you could also use this to drop the voltage to save more battery but you might make it so you phone boot loops and you would be stuck going to back to a nandroid or stock kernel again.
Seagrizzly said:
I have had to do it to the SZ and Tiamat kernels, but this is only if you phone is boot looping with the stock and you believe its due to voltage. I was having a problem with ever rom and kernel that was using HAVS with my phone and this was the only way I could get it to boot and stabilize.
Again its not for everybody and I would assume that you can make you phone not boot, but you could also use this to drop the voltage to save more battery but you might make it so you phone boot loops and you would be stuck going to back to a nandroid or stock kernel again.
Click to expand...
Click to collapse
im running the nosbc savage-zen with no issues.
fixxxer2008 said:
im running the nosbc savage-zen with no issues.
Click to expand...
Click to collapse
I also have the same issues with OP. Any kernel that has HAVS will put my phone on a constant bootloop (savage zen with or without sbc) or either get it to load fine (Tiamat), but will then lock after a few seconds and reboot.
fixxxer2008 said:
im running the nosbc savage-zen with no issues.
Click to expand...
Click to collapse
Same.. no issues here with that kernel.
thanks! great post.
i wrote a script figured i'd upload it here.
this is savaged-zen 1.0.1 stock voltage -50
it can be edited with whatever voltages you want, but make sure you save it as plain text.
just push this following the instructions in the OP but remove the .txt file extension.
Hey cool and thanks for the script, to repeat for those saying things work fine for them. That is awesome but some of us were having an issue running any of the HAVS kernels at all and thus why I had to do this fix to get my phone stable and using the new kernels, by the way I have had awesome battery life with my changes after about 12 hours only down to 79% using the tiamat 3.3.3 kernel as a base with my changes, I would only have to assume that if you could run the kernel with HAVS stock it would only be better so props goes out to the dev for that.
This is the only SBC Rom that doesn't reboot for me SBC-htc-15. I forget what Rom I was using with it but I'm using CM7 RC4 now. I'm not really sure how to do what is suggested so is there another option that might be easier?
thanks
It's so strange how we all have the same phone, yet some are very picky with HAVS and lower voltages and some are completely fine with it.
Gonna try it because my battery on CM7 has been...6 hours?
Android 17 said:
It's so strange how we all have the same phone, yet some are very picky with HAVS and lower voltages and some are completely fine with it.
Click to expand...
Click to collapse
Not really, no two cores are the exact same. The way they design them calls for them to be within an acceptable range only.
Definitely already seeing a massive improvement in battery efficiency, thanks.
Related
Ok so I Overclocked/undervolted via Milestone Overclock - no problems, however it got me thinking, all we are doing with this app is changing the maximum frequency and the maximum vsel.
I was looking for some extra oomph but also wanted to maximise battery life. My current set up is a 900mhz/46vsel maximum, but what about the other available frequencies - 600/300mhz - we ain't touching the vsel on these - are we getting the most out of this??
I did a bit of delving around so firstly I found the following when performing a cat /proc/overclock/mpu_opps with my overclock in place:
mpu_opps[3] rate=900000000 opp_id=3 vsel=46
mpu_opps[2] rate=600000000 opp_id=2 vsel=48
mpu_opps[1] rate=300000000 opp_id=1 vsel=33
So this is showing that the vsel for 600mhz is actually higher than 900mhz - not very economical! so how can we change this, well delving around various forums i got the jist of how to change this so here's a tutorial
IMPORTANT READ THIS!!! Disclaimer: I will not be held responsible for any damage to your phone, your PC or indeed your life from following this guide. The steps in this guide worked for me. Doing this kind of thing could affect your warranty and all that so have a long hard think about it before you go ahead. If anything goes wrong and your phone freezes or reboots spontaneously, remove the sdcard and boot the phone which will disable the overclock module and enable you to reverse whatever you did! As always I would always recommend a backup using Clockworkmod recovery. This is hacking and bad things can happen so be prepared. This is only tested on a stock/rooted 2.21 UK Generic/2.34 Deblur ROM with no apps removed - I have no idea if this works on other ROMs like JBoogie's (stock roms should be ok), because I don't know what changes/tweaks the Dev has done - If you try it and find it does/doesn't work then report back, but I can't offer any support for that
1) Create a setscaling.sh (I have attached mine as a base) script, this is what mine looks like. You can change frequencies/vsels, but it MUST stay in the format below.
echo 46 > /proc/overclock/max_vsel
echo 900000 > /proc/overclock/max_rate
echo 1 300000000 28 > /proc/overclock/mpu_opps
echo 2 600000000 38 > /proc/overclock/mpu_opps
echo 3 900000000 46 > /proc/overclock/mpu_opps
echo 0 900000 > /proc/overclock/freq_table
echo 1 600000 > /proc/overclock/freq_table
echo 2 300000 > /proc/overclock/freq_table
Lines 1/2 are your custom vsel/freq as loaded into Milestone Overclock
Lines 3/4/5 are your freq's and the custom vsels you want to use at those freq's (you can see they are much less than what they were originally!)
Lines 6/7/8 are your frequency table
I can't stress enough you must keep the format the same, and make sure you use the corect number of. It is possible to for example add an extra step/Frequency in - I haven't tested this so just be careful. Also bear in mind if you lower the vsels too much then you will cause the phone to fall over. However if you do get this just pull the SD card an it will boot the phone with the overclock module disabled
when you have set your setscaling.sh up you then need to do the following.
copy it to your sdcard, then via adb (you can also use root explorer)
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/setscaling.sh /system/xbin/setscaling.sh
chmod 755 /system/xbin/setscaling.sh
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
Then to after this to execute via adb you can just type:
setscaling.sh
Seriously though guys get root explorer as that will enable you to edit you setscaling.sh on the fly as you do your testing (finding optimum vsel), once edited you can then execute it by simply clicking on the file.
Once you have got your setscaling.sh just the way you want it, you can then get it to initialise automatically after boot - this had me stumpted for a while as the script was executing before the overclock module had loaded hence the settings weren't taking effect and I was having to start it manually. I'm more windows orientated and this actually turned out to be a really easy fix.
the key is another script called install-recovery.sh (again I have attached this to the post) and it contains the following info
#!/system/bin/sh
sleep 80
setscaling.sh
So what this does is it waits 80 secs before executing setscaling.sh - which gives the system more than enough time to boot up and load the overclock module. Intall this as per below after plaing on sdcard:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/install-recovery.sh /system/etc/install-recovery.sh
chmod 755 /system/etc/install-recovery.sh
reboot
Once rebooted do a cat /proc/overclock/mpu_opps and check your setscaling.sh has applied ok (i.e it is displaying your custom vsels)
Jobs a good un - enjoy!
##If you are reporting problems with it not working please post the exact steps of what you have done, otherwise I won't be able to assist##
Reserved...............
I've searched for an hour how to use Motorola Overclock. I've put the kernelmodule.tar.gz on the sdcard...
But i don't understand how to load it. Or where to place it...
The wiki on the googlecode page leaves me without a clue.
vanloque said:
I've searched for an hour how to use Motorola Overclock. I've put the kernelmodule.tar.gz on the sdcard...
But i don't understand how to load it. Or where to place it...
The wiki on the googlecode page leaves me without a clue.
Click to expand...
Click to collapse
mate just download milestone overclock from the market!
Higgsy said:
mate just download milestone overclock from the market!
Click to expand...
Click to collapse
That's what i did... And then i can't do anything in the app...
Oh Hey, i did forget to Re-Root after FrozenEclairing!
vanloque said:
That's what i did... And then i can't do anything in the app...
Click to expand...
Click to collapse
Do you have root?
after you apply this how do you tell if its worked?
edit: wow im retarded ignore this post -.-
A one right here
thanks, needed this for my overclock
I use gscript lite, and this info is perfet A 1
thanks for the idea and this should work with just adb; no need to download the scripts...
Code:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
echo "#!/system/bin/sh
echo 46 > /proc/overclock/max_vsel
echo 900000 > /proc/overclock/max_rate
echo 1 300000000 28 > /proc/overclock/mpu_opps
echo 2 600000000 38 > /proc/overclock/mpu_opps
echo 3 900000000 46 > /proc/overclock/mpu_opps
echo 0 900000 > /proc/overclock/freq_table
echo 1 600000 > /proc/overclock/freq_table
echo 2 300000 > /proc/overclock/freq_table" > /system/xbin/setscaling.sh
chmod 755 /system/xbin/setscaling.sh
setscaling.sh
echo "#!/system/bin/sh
sleep 80
/system/xbin/setscaling.sh" > /system/etc/install-recovery.sh
chmod 755 /system/etc/install-recovery.sh
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
really glad others are using this and liking it, everyone who is using milestone overclock should be using it!
Hey Higgsy,
i installed your scripts through Root Explorer (incl. executing + rebooting), but checking the mpu_opps file still gives me standard frequencies. You got an idea for this?
Greets, Jack
basshamster said:
Hey Higgsy,
i installed your scripts through Root Explorer (incl. executing + rebooting), but checking the mpu_opps file still gives me standard frequencies. You got an idea for this?
Greets, Jack
Click to expand...
Click to collapse
is the milestone overlock installed and module loaded?
Custom setting in milestone overclock set to 900mhz/46vsel?
Did you set the permissions? (ie the chmod bit).
- Milestone Overclock installed and loaded (incl. startup-load)
- i use different settings 1000/50 (300/30, 600/40 -> in setscaling-script), but 1000/50 is also set in custom settings so it seems equal to me
- permissions of both scripts are "rwxr-xr-x"
hmmm....
little edit: mpu_opps gives me 300/33, 600/48, 1000/50 so it#s not completely standard
basshamster said:
- Milestone Overclock installed and loaded (incl. startup-load)
- i use different settings 1000/50 (300/30, 600/40 -> in setscaling-script), but 1000/50 is also set in custom settings so it seems equal to me
- permissions of both scripts are "rwxr-xr-x"
hmmm....
little edit: mpu_opps gives me 300/33, 600/48, 1000/50 so it#s not completely standard
Click to expand...
Click to collapse
yeah it is standard apart from the max overclock you set in Milestone Overclock.
Please attach your exact setscaling.sh so I can take a look at it.
Thx for helping!
basshamster said:
Thx for helping!
Click to expand...
Click to collapse
hmm looked ok on the face of it, however when I recreated the file it was 355bytes as opposed to yours that was 353bytes
anyway, i think I might know the problem, in root explorer, open setscaling.sh in text editor - look at the end of each line - is there a little box? If there is the delete them - save and then execute.
Your permissions were ok
This is working ok on my phone now
Unfortunately still not working ... don't know what's the problem. Maybe someone else joins us with another solution. Thx for your help anyway!
I posted on the google forum bugreport.
When i click LOAD that reboots the phone and when i relaunch the app the clocks are still empty, so i click load again and it reboots again... Etc.
so after searching the forums i found:
1) faux clock
2) system tuner
3) init.d scripts
with (2) vdd values dont persist & revert to stock after a while for some unknown reason.
with (3) the vdd table doesnt change at all, except when the same commands in script are entered through adb.
i havent tried (1). i've had the most success with (3), but having to do it through adb every reboot is a bother. how are you guys doing it?
kaof said:
so after searching the forums i found:
1) faux clock
2) system tuner
3) init.d scripts
with (2) vdd values dont persist & revert to stock after a while for some unknown reason.
with (3) the vdd table doesnt change at all, except when the same commands in script are entered through adb.
i havent tried (1). i've had the most success with (3), but having to do it through adb every reboot is a bother. how are you guys doing it?
Click to expand...
Click to collapse
I'm using FauxClock 0.8.0 and resetting if it reboots.
I like the fact that it resets the UV on a boot, so that if I've UV'd too low it resets to be usable on a boot.
gol_n_dal said:
I'm using FauxClock 0.8.0 and resetting if it reboots.
I like the fact that it resets the UV on a boot, so that if I've UV'd too low it resets to be usable on a boot.
Click to expand...
Click to collapse
I think fauxclock 0.8 is your best option. 0.75 has some compatibility problem so do not use it.
If you want to use a scrip. I would put the corresponding code in the /etc/init.post_boot.sh
Code:
echo "-50000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
Reboot and then check the vdd table.
If init.post_boot.sh does not exist, do the following in the terminal emulator
Code:
touch /system/etc/init.post_boot.sh
chmod a+x /system/etc/init.post_boot.sh
vi /system/etc/init.post_boot.sh
After successfully creating the init.post_boot.sh, then write this in it:
Code:
#!/system/bin/sh
<YOUR COMMANDS GO HERE>
gol_n_dal said:
I'm using FauxClock 0.8.0 and resetting if it reboots.
I like the fact that it resets the UV on a boot, so that if I've UV'd too low it resets to be usable on a boot.
Click to expand...
Click to collapse
Scripts make a cleaner mod, try it someday!
You can UV individual frequencies, and after you get it right it's just set-it-and-forget-it.
yungyeh said:
I think fauxclock 0.8 is your best option. 0.75 has some compatibility problem so do not use it.
If you want to use a scrip. I would put the corresponding code in the /etc/init.post_boot.sh
Code:
echo "-50000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
Reboot and then check the vdd table.
If init.post_boot.sh does not exist, do the following in the terminal emulator
Code:
touch /system/etc/init.post_boot.sh
chmod a+x /system/etc/init.post_boot.sh
vi /system/etc/init.post_boot.sh
After successfully creating the init.post_boot.sh, then write this in it:
Code:
#!/system/bin/sh
<YOUR COMMANDS GO HERE>
Click to expand...
Click to collapse
Lesson learnt - UV scripts in system/etc/init.d don't work, but editing init.post_boot.sh does!
Works like a charm, thanks so much!
kaof said:
Lesson learnt - UV scripts in system/etc/init.d don't work, but editing init.post_boot.sh does!
Works like a charm, thanks so much!
Click to expand...
Click to collapse
Have to make sure that the init.d scripts have the right permissions for them to work ^_^
Kohr-Ah said:
Have to make sure that the init.d scripts have the right permissions for them to work ^_^
Click to expand...
Click to collapse
What are the right permissions?
I tried
Code:
adb shell
chmod 777 system/etc/init.d/scriptName
and it didn't work!
Any experience overclocking the Xoom 2 ?
And whats the best way/app to do it?
Not that the device is slow... but I have a lot of 1080p movies with enormous bitrates that I want to watch that bring my xoom2 to its knees.
I will root the device soon... havn't done that yet. Is there something I have to look for when I overclock ? I dont want to destroy it of course...
Is the processor even good for overclocking ?
Help would be much appreciated.
No one has overclocked yet. Someone at one point a while back mentioned insertable kernel modules he made for the processor in the Xyboard/Xoom 2 but I can't find his post anymore...
Hm ok. Sounds a little bit too complicated for my taste... I was hoping for an easy software solution. Only tried 2-3 apps none of them works...
but its really not a big deal... just found out that most of the movies I wanted to watch work fine as long as I dont try to play them over wifi and they are more or less H.264 Baseline Profile... all is fine.
But I bet in the future overclocking will be useful.
Take a look at http://code.google.com/p/opptimizer/
You will need to root your device, use these modules, and setcpu.
sidmoraes said:
Take a look at http://code.google.com/p/opptimizer/
You will need to root your device, use these modules, and setcpu.
Click to expand...
Click to collapse
Giving that a try now, thanks That was most likely the same guy who mentioned it previously.
You do not need to overclock to watch hd movies. I was having issues with hd not being able to play. I just downloaded the best video player app from market with hd performance codex & played my movies great!
Sent from my GT-I9100 using Tapatalk
Elysian893 said:
Giving that a try now, thanks That was most likely the same guy who mentioned it previously.
Click to expand...
Click to collapse
Did you had success with that? Can you post how to overclock the device if it worked for you?
Thanks!
I haven't had any luck. When I change the frequencies (manually, none of his scripting works) it just bogs down completely, even though SetCPU shows it running at 1.5ghz... Can barely do anything but shut it down and restart it...
I have overclocked my device at 1.36 and is stable but i hadn't any luck in higher frequencies
Sent from my XOOM 2 ME using Tapatalk
Could you post a little step by step tutorial about how you did it?
I tried to put these opptimizer files in the system directory but I get an error message all the time... :/
I have root but wasn't able to get it to work. Help would be appreciated.
escapist69 said:
Could you post a little step by step tutorial about how you did it?
I tried to put these opptimizer files in the system directory but I get an error message all the time... :/
I have root but wasn't able to get it to work. Help would be appreciated.
Click to expand...
Click to collapse
i will post a small tutorial in few hours or tommorow when i will have a little spare time ...
I am not responsible if anything happend to your device. Don't blame me for frying your Tablet
Go to http://code.google.com/p/opptimizer/ to get the modules, for more information and support the developer ....
quick download link http://code.google.com/p/opptimizer/downloads/detail?name=mo_simp_1.5_xyboard-signed.zip&can=2&q=
Unzip the modules
Put them in your /sdcard directory (or anywhere you want)
You need to root your device and download terminal emulator from play store
In terminal emulator:
su (grant root access to terminal )
mount -o rw,remount /system
<<<< copy modules>>>>
cp /sdcard/symsearch.ko /system/lib/modules/
cp /sdcard/overclock.ko /system/lib/modules/
<<<<install loadable kernel module>>>>
insmod /system/lib/modules/symsearch.ko
insmod /system/lib/modules/overclock.ko
mount -o ro,remount /system
<<<<Modules are now installed- you only have to do this one time>>>>
To overclock the cpu in terminal (you don't need to do that. You can download shell script and run it)
echo 5 1350000000 1390000 > /proc/overclock/mpu_opps
1350000000 is for frequency and 1390000 for Voltage
Motorola VSEL Values:
63 = 1400000 this the maximum value
62 = 1390000
61 = 1380000
60 = 1370000
59 = 1360000
58 = 1350000
Every device can oveclock and be stable in deferent values . Mine is not stable over 1.36. Try and post your resault
To overclock the gpu in terminal
echo 384000000 > /proc/overclock/gpu_opps
valid values for GPU Frequency 256000000, 307200000, 384000000
Every time you reboot the device Overclock settings are lost ...
Download this shell script and put it in /sdcard/ directory: http://dl.dropbox.com/u/152184/oc.sh
In terminal emulator, you can run the script every time you want to overclock the device:
sh /sdcard/oc.sh
You can edit the script with other values to find the best for your device
Thanks man! I will try this soon and report back how it went... THX a lot!
I will put this in the first post from me so people who are interested can find it quickly.
With the last updated, i think gpu is clocked to 3,84 so you don't seem to be able to overclock gpu with those modules...
Sent from my XOOM 2 ME using Tapatalk
Did anyone try this? I am really interested to see what is the frequency limit you have with your xooms
Sent from my XOOM 2 ME using Tapatalk
I think there is a conflict with vm heap size . If i change dalvik.vm.heapgrowthlimit value and try to overclock it, my tablet reboots !!!
mdcykkk9 said:
I am not responsible if anything happend to your device. Don't blame me for frying your Tablet
Go to http://code.google.com/p/opptimizer/ to get the modules, for more information and support the developer ....
quick download link http://code.google.com/p/opptimizer/downloads/detail?name=mo_simp_1.5_xyboard-signed.zip&can=2&q=
Unzip the modules
Put them in your /sdcard directory (or anywhere you want)
You need to root your device and download terminal emulator from play store
In terminal emulator:
su (grant root access to terminal )
mount -o rw,remount /system
>
cp /sdcard/symsearch.ko /system/lib/modules/
cp /sdcard/overclock.ko /system/lib/modules/
insmod /system/lib/modules/symsearch.ko
insmod /system/lib/modules/overclock.ko
mount -o ro,remount /system
To overclock the cpu in terminal (you don't need to do that. You can download shell script and run it)
echo 5 1350000000 1390000 > /proc/overclock/mpu_opps
1350000000 is for frequency and 1390000 for Voltage
Motorola VSEL Values:
63 = 1400000 this the maximum value
62 = 1390000
61 = 1380000
60 = 1370000
59 = 1360000
58 = 1350000
Every device can oveclock and be stable in deferent values . Mine is not stable over 1.36. Try and post your resault
To overclock the gpu in terminal
echo 384000000 > /proc/overclock/gpu_opps
valid values for GPU Frequency 256000000, 307200000, 384000000
Every time you reboot the device Overclock settings are lost ...
Download this shell script and put it in /sdcard/ directory: http://dl.dropbox.com/u/152184/oc.sh
In terminal emulator, you can run the script every time you want to overclock the device:
sh /sdcard/oc.sh
You can edit the script with other values to find the best for your device
Click to expand...
Click to collapse
Hallo!
Thanks for your guide.
I'm following it in a Xoom2 , european Ics , rooted, but i'm stucked in insmod commands.
I get:
insmod: init_module '/system/lib/modules/symsearch.ko' failed (Exec format error)
How can I manage it?
I downloaded the mo_simp_1.5_xyboard-signed.zip file
I haven't tried it on ics yet, i will try it in few hours and i will report back... Are you sure you copy modules correct?
mdcykkk9 said:
I haven't tried it on ics yet, i will try it in few hours and i will report back... Are you sure you copy modules correct?
Click to expand...
Click to collapse
I think yes.
In dmesg i read a ' different magic number error' on the module file.
Let me know your result
Inviato dal mio GT-N7000 con Tapatalk 2
spidertop said:
I think yes.
In dmesg i read a ' different magic number error' on the module file.
Let me know your result
Inviato dal mio GT-N7000 con Tapatalk 2
Click to expand...
Click to collapse
You can't insmod modules on kernel 3+ (ics kernel) i think. i will search around to see if there are is any way to overclock the tablet,
So I applied the voodoo color settings from this thread here: http://forum.xda-developers.com/showthread.php?t=1401759
But they don't stick after reboot. Can anyone tell me how I can get them to stay when I reboot my Nexus?
You can always make an init.d script if your ROM supports it
Here's an example of how it should look, you can change the values to whatever you like
#! /sys/bin/sh
echo 2863311680 >/sys/class/misc/voodoo_color/red_multiplier
echo 3336681600 >/sys/class/misc/voodoo_color/green_multiplier
echo 3925507840 >/sys/class/misc/voodoo_color/blue_multiplier
echo -33 >/sys/class/misc/voodoo_color/blue_v1_offset
echo -26 >/sys/class/misc/voodoo_color/red_v1_offset
echo -30 >/sys/class/misc/voodoo_color/green_v1_offset
Or you can use an app called ROM Toolbox and use the "Scripter" to run this at boot
Sent from my Nexus S 4G using Tapatalk 2
Thanks! It's working great! However, I do notice that it sometimes makes my phone reboot on bootup about two times before it applies. But better than trying to remember my screen's values in Voodoo.
Update: I removed the ds files and corrected the powersaver script...
First of all... I would like to give credits to all the owner of this tweaks... This tweaks are not mine... I just compiled them
This tweak never fixes battery drain, it can or may improve your battery life
Let me first advice you that this mod worked for me, and would not fully guarantee that it would also work for you.. I'm using CM9 Alpha 4 with xxkpu as based...
With this mod... Battery life has increased by 25%... I can use the phone for browsing (connected with WiFi) and little gaming for 12 hours of semi-continuous use, it means that I lock the phone from time to time and resume my browsing (background apps still connects to the internet when sleeping) or gaming...
This is a Sysctl tweak with optimized Conservative mod... I have also attached the same tweak but with current Gingerbread system tweaks (I am currently using this, no problems so far)
Use Conservative governor as default after flashing this mod
Downloads:
see attachments
Other Tweaks to Improve Battery Life
I've been reading a lot lately... And here's what I've found out...
Disable Surface Dithering (This just fixed my overheating problem, and games runs more smoothly now)
Always use Conservative Governor
Disabling fast dormancy may improve our battery life (untested but I'm currently using this) To disable fast dormancy, just add this to you build.prop:
ro.ril.fast.dormancy.rule=0
Click to expand...
Click to collapse
Reloaded ICS
By the way, I also included Reloaded ICS... I tested it on our device and works very well... Reloaded ICS allows you to perform additional tweaking of the status bar and many more... Full details here
All credits goes to rob43
I've also attached the latest working version of Reloaded ICS...
To undo this Mod, Just delete this files:
/system/etc/init.d/10sysctl
/system/etc/init.d/01confpowersaver
/system/etc/init.d/95tweaks
/system/etc/sysctl.conf
Click to expand...
Click to collapse
Please post you feedbacks and suggestions
Thanks! Will try
Cheers
Sent from my GT-i9003 powered by Stable and Smooth CyanogenMod 9!
landono5 said:
First of all... I would like to give credits to all the owner of this tweaks... This tweaks are not mine... I just compiled them
This tweak never fixes battery drain, it can or may improve your battery life
Let me first advice you that this mod worked for me, and would not fully guarantee that it would also work for you.. I'm using CM9 Alpha 4 with xxkpu as based...
With this mod... Battery life has increased by 25%... I can use the phone for browsing (connected with WiFi) and little gaming for 12 hours of semi-continuous use, it means that I lock the phone from time to time and resume my browsing (background apps still connects to the internet when sleeping) or gaming...
This is a Sysctl tweak with optimized Conservative mod... I have also attached the same tweak but with current Gingerbread system tweaks (I am currently using this, no problems so far)
Use Conservative governor as default after flashing this mod
Downloads:
see attachments
Other Tweaks to Improve Battery Life
I've been reading a lot lately... And here's what I've found out...
Disable Surface Dithering (This just fixed my overheating problem, and games runs more smoothly now)
Always use Conservative Governor
Disabling fast dormancy may improve our battery life (untested but I'm currently using this) To disable fast dormancy, just add this to you build.prop:
Reloaded ICS
By the way, I also included Reloaded ICS... I tested it on our device and works very well... Reloaded ICS allows you to perform additional tweaking of the status bar and many more... Full details here
All credits goes to rob43
I've also attached the latest working version of Reloaded ICS...
Please post you feedbacks and suggestions
Click to expand...
Click to collapse
can use in MIUI???
How to get back to original settting
After all these tweaks if I had to get back to original configuration ?
How to do that.?
I just gave a quick look, nothing more.
01confpowersave has an error.
Right after
Code:
#scheduler cfq
there should be an "if". Or you add an if (I don't know what) or you remove fi; from here:
Code:
for i in $(ls -1 /sys/block/stl*) $(ls -1 /sys/block/mmc*)
do
echo "cfq" > $i/queue/scheduler
done
[COLOR="RED"]fi;[/COLOR]
EDIT: I think 95tweaks makes the boot slow because it wipes the dalvik-cache on every boot (and weirdly it creates a database of the zipaligned files, but it doesn't use it) (and FYI some of the tweaks there are already avaible in CWM Tweaks). The last part of the script is useless (read the last part of this: http://forum.xda-developers.com/showthread.php?t=1587553)
And please Mac OS X users, don't include .DS_Store and ._.SD_Store in your zips.
loSconosciuto said:
I just gave a quick look, nothing more.
01confpowersave has an error.
Right after
Code:
#scheduler cfq
there should be an "if". Or you add an if (I don't know what) or you remove fi; from here:
Code:
for i in $(ls -1 /sys/block/stl*) $(ls -1 /sys/block/mmc*)
do
echo "cfq" > $i/queue/scheduler
done
[COLOR="RED"]fi;[/COLOR]
I think 95tweaks makes the boot slow because it wipes the dalvik-cache on every boot (and weirdly it creates a database of the zipaligned files, but it doesn't use it) (and FYI some of the tweaks there are already avaible in CWM Tweaks). The last part of the script is useless (read the last part of this: http://forum.xda-developers.com/showthread.php?t=1587553)
And please Mac OS X users, don't include .DS_Store and ._.SD_Store in your zips.
Click to expand...
Click to collapse
Soo should I flash it?
Cheers
Sent from my GT-i9003 powered by Stable and Smooth CyanogenMod 9!
shail139 said:
After all these tweaks if I had to get back to original configuration ?
How to do that.?
Click to expand...
Click to collapse
You need to remove
Code:
/system/etc/01confpowersaver
/system/etc/95tweaks
/system/etc/init.d/10sysctl
/system/etc/sysctl.conf
while it's a little bit more problematic for "update-reloaded-1.9b4-cm9-050712.zip" because it replaces the original SystemUI.apk.
bscraze said:
Soo should I flash it?
Click to expand...
Click to collapse
Well, 'conservative' is not tweaked because of the 'if' problem, but there's no problem in flashing it, you still have all the sysctl.conf tweaks. Probably it's better to wait a flashable zip without all the Mac trash files, or manually remove them from the zip.
EDIT:
and I was wrong regarding the slow boot, I didn't read the script well enough.
I'll try to fix these... These mods aren't mine actually.. Thank you for your support...
I was wondering how the Mac files got there, I'm even using Windows...
Edit:
Got it, the mac files are from the original zips...
And the Fi; line should remain there... Well, according to the dev I've talked to, that is a needed command, I have really no idea what it does... But I'll guarantee that it works... Governors changed on boot...
The Fi is for stopping an if command...
if
<command>
else
<command>
fi
landono5 said:
And the Fi; line should remain there... Well, according to the dev I've talked to, that is a needed command, I have really no idea what it does... But I'll guarantee that it works... Governors changed on boot...
The Fi is for stopping an if command...
if
<command>
else
<command>
fi
Click to expand...
Click to collapse
Yes, I know, but, where is the if?
Code:
#!/system/bin/sh
#cpu
echo "300000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo "1000000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "conservative" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
#scheduler cfq
for i in $(ls -1 /sys/block/stl*) $(ls -1 /sys/block/mmc*)
do
echo "cfq" > $i/queue/scheduler
done
fi;
#Conservative settings for saver mode.
echo "95" > /sys/devices/system/cpu/cpufreq/conservative/up_threshold
echo "120000" > /sys/devices/system/cpu/cpufreq/conservative/sampling_rate
echo "1" > /sys/devices/system/cpu/cpufreq/conservative/sampling_down_factor
echo "40" > /sys/devices/system/cpu/cpufreq/conservative/down_threshold
echo "10" > /sys/devices/system/cpu/cpufreq/conservative/freq_step
Edit:
And yes, you are right, the governor is changed. The problem is that scripts are not compiled, so errors come at runtime and the execution stops when an error is found.
The error is after the line that changes the governor. As I said, the problem is that conservative is not tweaked (the part after the fi).
Blue and not transparent status bar looks horrible, how to do it to look like before?
rascal0pl said:
Blue and not transparent status bar looks horrible, how to do it to look like before?
Click to expand...
Click to collapse
You can turn off Themes in Color Setting
loSconosciuto said:
Yes, I know, but, where is the if?
Code:
#!/system/bin/sh
#cpu
echo "300000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo "1000000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "conservative" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
#scheduler cfq
for i in $(ls -1 /sys/block/stl*) $(ls -1 /sys/block/mmc*)
do
echo "cfq" > $i/queue/scheduler
done
fi;
#Conservative settings for saver mode.
echo "95" > /sys/devices/system/cpu/cpufreq/conservative/up_threshold
echo "120000" > /sys/devices/system/cpu/cpufreq/conservative/sampling_rate
echo "1" > /sys/devices/system/cpu/cpufreq/conservative/sampling_down_factor
echo "40" > /sys/devices/system/cpu/cpufreq/conservative/down_threshold
echo "10" > /sys/devices/system/cpu/cpufreq/conservative/freq_step
Edit:
And yes, you are right, the governor is changed. The problem is that scripts are not compiled, so errors come at runtime and the execution stops when an error is found.
The error is after the line that changes the governor. As I said, the problem is that conservative is not tweaked (the part after the fi).
Click to expand...
Click to collapse
I'm really confused... I know very little regarding android yet... What should I change regarding the script so that it will run smoothly...
Isn't this .zip can be flash straight away in cwm then is work just by that? I mean we don't have to adjust anything after flash it
Sent from my GT-I9003 using XDA
Just flash the zip and it'll be fine...
landono5 said:
I'm really confused... I know very little regarding android yet... What should I change regarding the script so that it will run smoothly...
Click to expand...
Click to collapse
It's Linux. Just change the file to:
Code:
#!/system/bin/sh
#cpu
echo "300000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo "1000000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "conservative" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
#scheduler cfq
for i in $(ls -1 /sys/block/stl*) $(ls -1 /sys/block/mmc*)
do
echo "cfq" > $i/queue/scheduler
done
# fi;
#Conservative settings for saver mode.
echo "95" > /sys/devices/system/cpu/cpufreq/conservative/up_threshold
echo "120000" > /sys/devices/system/cpu/cpufreq/conservative/sampling_rate
echo "1" > /sys/devices/system/cpu/cpufreq/conservative/sampling_down_factor
echo "40" > /sys/devices/system/cpu/cpufreq/conservative/down_threshold
echo "10" > /sys/devices/system/cpu/cpufreq/conservative/freq_step
and you'll be done. Don't know what that fi was for, anyway, we want to reduce power drain and then the tricks have to be applied for that.
It will work on any galaxy devices ? Just a question
nooooooooooo, don't do it
he ported it for our device
Did anyone test this ?
I m using Remics rom, so can i flash this script...
Sent from my GT-I9003 using xda premium
vijaypalmanit said:
I m using Remics rom, so can i flash this script...
Sent from my GT-I9003 using xda premium
Click to expand...
Click to collapse
+1 and which Zip we have to flash? Which update? In tapatalk i can see this...