Hello and Good Day to All!,
note: I can no longer maintain this as I have already sold my Charm Unit ..., attached below is the source code used on this development
This is a guide on how to overclock your Motorola Charm. [tested on T-Mobile Motorola Charm MB502]
Disclaimer: I am not responsible of bricking/frying your phone!, use this at your own risk
It is confirmed that some users of the Charm Overclock have bricked theirs using this app
Prerequisites:
● Phone should be rooted
● You have a copy of a "proper/valid" sbf file of your Motorola Charm unit in case anything goes wrong.
Ask people in the link provided for directions on how to obtain your proper sbf file: http://modmymobile.com/forums/633-motorola-charm-general/557900-charm-firmwares-superthread.html
Method #1
Install my Charm Overclock App and use it like that of the Milestone Overclock App
[note: apk found just below this very post]
Method #2 (by ryukoz)
1. open /system/build.prop in text editor
2. find ro.product.model=MB502, change MB502 to MB511
3. use milestone overclock
Method #3
Things needed (some maybe optional):
● Your Motorola Charm phone
● PC
● USB Data Cable for your Phone/PC
● MicroSD Card Reader
Prerequisites:
● All pertaining drivers should be installed in your PC (i.e. Moto USB Drivers..., etc.)
The Steps:
1. From your PC, Download 'Milestone Overclock' apk from: http://code.google.com/p/milestone-overclock/downloads/list (I've used version 148)
2. Extract this Milestone Overclock apk to a clean folder and locate the file 'overclock_flipout_21.ko' in: ..res\raw\ directory
3. Copy the module overclock_flipout_21.ko into the root of your SDCard
4. Install the Milestone Overclock App to your phone (either thru Market or with the one you downloaded)
5. Install also SetCPU
6. From a terminal emulator on your phone or thru adb, run these commands (should be root user)
7. # su
8. # cd /sdcard
9. # grep omap2_clk_init_cpufreq_table /proc/kallsyms
● you should see an output like: c004e498 T omap2_clk_init_cpufreq_table
● take note of the red colored eight digit hex number
10. and then we load the Overclocking Module with the code below (replace the RED number with your actual address you found on your device):
11. # insmod overclock_flipout_21.ko omap2_clk_init_cpufreq_table_addr=0xc004e498
12. run dmesg and see if you have something similar below:
● [ 9361.096099] overclock: found mpu_opps_addr at 0xc050c888
13. Open the Milestone Overclock app (the module should be loaded by default as we already loaded it manually)
14. Slide the slider to the far right and press the 'menu' button and choose 'settings'
15. In the 'Custom rate (KHz)', put in the value you like, say: '1000000' (this is 1GHz)
16. In the 'Custom vsel', put in the value you like say: '60'
17. Leave the other settings and press 'Ok'
18. Lastly, Press the 'Apply' button ^_^
Don't forget to set 'SetCPU' as well
I would like to thank "Milestone Overclock" and "SetCPU" ^_^
also..., to the XDA Personnels: Please Open a Motorola Charm Sub Forum ^_^
Frequency and vsel Table (and maybe others to note)
Currently tested and somewhat stable:
● device=mb502, frequency=1GHz, vsel=60 (stable), user=dabiano
● device=mb502, frequency=1GHz, vsel=58 (stable), user=therkr
● device=mb502, frequency=1.1GHz, vsel=63 (stable? [still testing]), user=elliot.newnham
● device=mb502, frequency=720MHz, vsel=46 (stable? [still testing]), user=ryukoz
Default Frequency Table!? (via cat /proc/overclock/mpu_opps)
● 720MHz @ 62vsel
● 550MHz @ 56vsel
● 500MHz @ 50vsel
● 250MHz @ 39vsel
● 125MHz @ 32vsel
My Customized Frequency Table!
● 1GHz @ 60vsel
● 800MHz @ 50vsel
● 600MHz @ 40vsel
● 400MHz @ 30vsel
● 200MHz @ 20vsel
other values are welcome! ^_^, we need other combinations
Questions and Answers
General Q and A
Q. Which overclock settings is stable?
A. I have used 1GHz and 60vsel and its stable (still currently testing)
Q. Do we have a 'stable' Frequency and vsel table?
A. not at the moment, I would like people to contribute by experimenting on different values and post here stable combinations and well post it
Q. Does this drain the battery much more quicker if I overclock my Motorola Charm?
A. YES! ^_^
Q. How come Milestone Overclock does not support Motorola Charm?
A. Kindly ask them to include it as we are using their Flipout module
==================================================
==================================================
Charm Overclock App Q and A
Q. Why does the "Autoload on boot" won't work?
A. Now it works by modifying /system/bin/mot_boot_mode (I don't know other alternatives to make it set during boot/startup)
Q. Your Application sucks.
Q. Can we include this "fill-in-the-blanks" feature?
A. I'm welcome to such improvements [if I have the time]
Great Job!
Firstly, I'd like to thank you for doing something with the Motorola Charm. I felt for some time that everyone had stopped work and there would be no more developer goodies except the root and mostly usless recovery (without ROMs).
But thanks to you now at least i can increase the speed of my device!!
I also wanted to ask what does it mean to set "custom vsel"? Is it voltage selection?
If yes, then how do I see the ORIGINAL voltage of my charm?
SetCPU tells me original clock speed is 720MHz, but nothing about original voltage?
What can happen if I put low vsel value and high clock speed?
Thanks!
I tried following your steps but got stuck on step 9.
Terminal Emulator says:
Code:
grep: proc/kallsyms: No such file or directory
Where did I go wrong?
UPDATE
fixed!
I just started terminal emulator again and wrote command in step 9 and it worked(without su).
I think "cd /sdcard" had caused the problem the first time.
Please do answer my questions.
Sent from my MB502 using XDA App
Hi Guys , Have followed everything and went on well till step 12 . But still Milestone Overclock app says mb502 is not supported add in project site.
Any idea??????
udayshankarv said:
Hi Guys , Have followed everything and went on well till step 12 . But still Milestone Overclock app says mb502 is not supported add in project site.
Any idea??????
Click to expand...
Click to collapse
You should have overclock_flipout_21.ko in sdcard and have milesone overclock and setCPU installed. Also, note the ID of your device.
Here's my method:
Reboot device.
DO NOT open milestone overclock/setCPU now.
Go to terminal:
$ su
# cd /sdcard
# insmod overclock_flipout_21.ko omap2_clk_init_cpufreq_table_addr=0x********
Where ******** is your device specific ID
Then open milestone overclock and you'll see the module automatically loaded. Now you can follow the steps mentioned by dabiano.
TIP:
Keep the "vsel" value to 55 instead of 60 as mentioned in first post. It's still stable and save battery!
Hope this helps.
Sent from my MB502 using XDA App
Hello I am new to the forum .... I want to thank you for the job ... I did everything explained and was successful but I have a concern, I reset the phone settings and clears the start .... no way you run save the settings of 1000mhz?
YoYoX said:
Hello I am new to the forum .... I want to thank you for the job ... I did everything explained and was successful but I have a concern, I reset the phone settings and clears the start .... no way you run save the settings of 1000mhz?
Click to expand...
Click to collapse
Actually, the milestone overclock app should automatically do the module loading part but Moto Charm (MB502) is not recognised so we have to manually do it every reboot.
I believe someone more experinced can create a script for doing that as well.
Let's see.
thanks so be it ... wait
Q. I also wanted to ask what does it mean to set "custom vsel"?, Is it voltage selection?
A. I'm still not sure what is the meaning of it! ^_^, but its sure close to the said 'voltage' something... ^_^
Q. If yes, then how do I see the ORIGINAL voltage of my charm?
A. I'm still not sure how can we see the actual vsel for the default 720MHz, but I'm also wondering the same way, I'll ask some other people around how to query this one.
Q. SetCPU tells me original clock speed is 720MHz, but nothing about original voltage?
A. ..., no comment!? ^_^
Q. What can happen if I put low vsel value and high clock speed?
A. possible processor frying!? ^_^, just be careful on setting frequency and vsel on any device as there is a limit on it. (just followed it from Milestone/Motoroi vsel settings)
I tried following your steps but got stuck on step 9.
Terminal Emulator says:
Code:
grep: proc/kallsyms: No such file or directory
Where did I go wrong?
UPDATE
fixed!
I just started terminal emulator again and wrote command in step 9 and it worked(without su).
I think "cd /sdcard" had caused the problem the first time.
Please do answer my questions.
Click to expand...
Click to collapse
1. error on typing it?
2. be mindful when issuing 'su' as when su is invoked, it will have a different env, path, etc..., that's why I first issued 'su' then changing directory.
(ex. if you make 'cd /sdcard' first then issue 'su', then there will be a big chance that the path will not be '/sdcard' anymore)
udayshankarv said:
Hi Guys , Have followed everything and went on well till step 12 . But still Milestone Overclock app says mb502 is not supported add in project site.
Any idea??????
Click to expand...
Click to collapse
actually..., the overclocking module (.ko) supports our device but the Milestone Overclock UI does not.
and I also placed it in the QandA section on post #3
dabiano said:
actually..., the overclocking module (.ko) supports our device but the Milestone Overclock UI does not.
and I also placed it in the QandA section on post #3
Click to expand...
Click to collapse
How do we get them to enable support in tue UI? Is there a request page where everyone can go and post?
...
therkr said:
How do we get them to enable support in tue UI? Is there a request page where everyone can go and post?
Click to expand...
Click to collapse
actually yes..., you can go to the Milestone Overclock website and file a issue report and there is actually 1 already but none of the devs there started to make it happen
here is the issue report on Milestone Overclock for Motorola Charm: http://code.google.com/p/milestone-overclock/issues/detail?id=101
I would gladly make a 'simple customized' Charm Overclock UI but I'm still learning Android
Thanks guys! works great
$ su
# cd /sdcard
# insmod overclock_flipout_21.ko omap2_clk_init_cpufreq_table_addr=0x********
Where ******** is your device specific ID
Click to expand...
Click to collapse
works best for my phone btw.
elliot.newnham said:
Thanks guys! works great
works best for my phone btw.
Click to expand...
Click to collapse
it's on step #9, read carefully the guide ^_^
Code:
9. # grep omap2_clk_init_cpufreq_table /proc/kallsyms
this will output something like: c004e498 T omap2_clk_init_cpufreq_table
this red colored stuff is your device memory location and 'DO NOT COPY THE ADDRESS THAT IS PLACED HERE this is just a sample address' and instead copy what is displayed on your device when you issued it via terminal or in adb.
...
updated some frequency table posted on the 2nd post of this thread
Hello! I have a question, I alredy overclocked my Charm, worked perfectly, but when I reset de phone I get un-overclocked, and I have to do everything again, any idea what to do? Or I shall do everything again and again?
Thanks!
Sent from my MB502 using XDA App
...
iventura said:
Hello! I have a question, I alredy overclocked my Charm, worked perfectly, but when I reset de phone I get un-overclocked, and I have to do everything again, any idea what to do? Or I shall do everything again and again?
Thanks!
Sent from my MB502 using XDA App
Click to expand...
Click to collapse
Hi! ^_^
unfortunately, I don't know how to make it permanent as of now as the Milestone Overclock UI does not permit it
bad news is that you really need to do these on reboots
good news is that I'm trying to make a UI of it and make it persistent [painless configuration ] (or until Milestone Overclock does this first)
I'm still a newbie on Android stuff and I'm struggling making one
That's great, but now I noticed another trouble -.-
I overclocked it again, and using setCPU I setted min freq to 1000 Mhz and the mobile reset itself Just to see if it is stable because I didnt do it before so I tryed.
I think I must leave min freq in 250 Mhz
Sent from my MB502 using XDA App
Related
Beta testing of a new kernel that allows over clocking up to 660mhz. I have no time to do a lot of testing. So far MCR rom 3.2 is stable and fast with it. So I am calling for testers. The kernels are using ramzswap.
Download
Note: It will not work on 2.x rom as it is a 2.6.27 kernel.
This is great news. I would try it, but I have a CDMA Hero.
I think this also works for 2.1 ROM; I'm using Vanillain 1.0 and I went from 145 CPU benchmark to 154...
how to apply?
and does setcpu support this setting yet?
thanks for the work
1) Download the SetCPU in the link
2) Drag the SetCPU file into your SD card
3) Open and install using any file manager (I use Astro)
4) Download the setcpu.txt file into your SD card (not into a folder)
5) Open SetCPU and press Menu > Device Selection > Scroll all the way down to "Custom Frequency Config" (last on the list)
6) Then set up the frequency as you desire
is this based on teknologist's kernel? this shall be included in MCR once stable enough.
Is root needed?
Yes you need root for this to work, and just on a side notice using the overclock widget seems to work to.
worked on my hero i guess.. but how stupid m i, i tried edit the txt file and push into my nexus and try the settings... damm.. f*ck, it did not work at all... damm...
doesn't do anything for me according to linpack. Same amount of Mflops/s
edit: and screen went black and never got out of it.... :S
660 MHz ?? Bye bye batery...
Myriad Group is developing a new virtual machine for android that increases 3x the speed of the system running aplications, with the same hardware, and a optimized use of the batery and will allow richer grafics... The name of the project is Dalvik turbo and it will be show on the Mobile World Congress of Barcelona...
You can read it here: www(dot)mobileburn.com/news.jsp?Id=8684
I hope we can use it to our Hero's ...
Dalvik Turbo looks extremely promising. If 3x performance can actually be achieved, then we have to ask Google... what were you thinking with Dalvik's original design?
Please, read this:
http://android.modaco.com/index.php?s=&showtopic=302182&view=findpost&p=1185063
What do these numbers mean?
Sergio PC said:
Seems to be working fine, you can tell in various instances such as scrolling in menus etc...
Lox_Dev you the man! thanks.
Click to expand...
Click to collapse
BogoMips is not the clock!
It's the efficiency of running a bootonly calibration loop.
This doesn't mean that Lox_Dev work isn't a great thing, though.
so in a nutshell, whith this mod does hero run faster or not?
ermacwins said:
so in a nutshell, whith this mod does hero run faster or not?
Click to expand...
Click to collapse
I don't think so.
Just because your car shows 200mph in the speedometer doesn't mean it can go that fast.
Really, read here: http://android.modaco.com/index.php?s=&showtopic=302182&view=findpost&p=1185063
Uqbar said:
BogoMips is not the clock!
It's the efficiency of running a bootonly calibration loop.
This doesn't mean that Lox_Dev work isn't a great thing, though.
Click to expand...
Click to collapse
Alright i understand ill edit that post to find some explanations.
Thanks man.
Hello I'm flash that kernel and after reboob i see circle showing droid logo => htc =>droid and that replay again and again some clue ?
After a backup I usually wipe everything out before installing a new rom.
Try this.
EZ-DZ GODSPEED OVERCLOCKING kernel Update ver 03 for the HTC Desire Z
WHAT'S THIS ??
- This is a flashable Update.zip containing the stock HTC Desire Z with HTC Sense Kernel 2.6.32.21-gd2764ed.
- NOTICE this is kernel-specific. This overclocking update won't work if you have a different kernel (T-Mobile firmware, some asian versions, etc). This is intended for the current stock european generic Desire Z, the Bell-NAM Desire Z, and any custom ROM based on this Kernel version.
- It will overclock your phone's CPU to 1017 MHz, 1206 MHz or 1420 MHz Godspeed.
- The stock Kernel has not been modified. Instead of that, the Overclocking module is automatically loaded on boot.
- It also includes embedded root priviledges, disabled security, the latest Busybox (Nov 2010) and Superuser, so your root will stay even if you ever have to factory reset.
- Flashing one of this Kernel Update zips will NOT erase your personal info and configurations; it will not wipe your phone because only the kernel will be updated.
HOW TO FLASH ??
- I assume you are an experienced user, if not, please refer to the "EASY rooting/flashing TUTORIAL and FAQs for dummies" thread, read the FAQ, and them come back.
TIP: Hey, please remember: it's always clever to make a NANDroid backup before flashing anything.
- I have prepared 3 sets: a conservative 1 GHz overclocking update, an intermediate 1.2 GHz option and a more aggressive 1.4 GHz version. Pick your Downlaod from this post's footer, and copy it to your phone's SD card.
- Flash it via ClockworkMod: Open ROM Manager, tap "Install ROM from SD card", scroll to select your EZ Godspeed update zip, tap OK. Phone will reboot with the updated kernel.
TIP: DON'T check "Wipe Data and Cache" unless you wanna delete all your personal info, installed apps and configurations.
- Enjoy your new godspeed EZ overclocked DZ
WANT TO FINE TUNE OR TRY OTHER SPEEDS ??
- I strongly recommend getting SetCPU from the Market. It will let you control your max/min CPU speeds, fine tune, and many advanced options, but be aware SetCPU can't override the max speed specified by the Godspeed kernel update you choose.
- To change the max overclocking speed, You can flash from any Godspeed update to another as many times as you wish, because the only diference between each is the overclocking module autoload script 03gtrabOC, which specifies the oc-dz.ko overclocking module max value (check post 5 if you want to learn how it works or how to make your own update zips).
HOW TO DISABLE / UNINSTALL ??
Do you really wanna go back ?? OK then, manually uninstalling is EZ-DZ too:
1.- Delete the file /system/etc/init.d/03gtrabOC and reboot. The overclocking module won't be auto-loaded anymore; you're back to 806MHz.
2.- Delete /system/lib/modules/oc-dz.ko (the overclocking module). This is optional since the module won't be loaded without the script.
Everything else in this Update zips is stock (the Kernel, radio module bcm4329.ko, etc) except for a couple of ramdisk optimizations (embedded root and enabled busybox run parts capabilities) and the latest Busybox and Superuser apps (which you already had).
OR you can simply restore your NANDroid backup and forget you ever flashed this OC thing.
ACKNOWLEDGEMENTS:
THANKS to tkirton (update script guru and patient teacher), coolbho3000 (original overclocking module for the HTC Vision), stridger (recompiled module for the Desire Z), dsixda (learned a lot by reading the scripts from his kitchen) and many others.
If I owe acknowledgements please let me know and I will update this post.
DOWNLOADS:
- For 1.4 GHz overclocking download EZDZ_Godspeed_update03.zip
MD5 checksum: b28261f48b2fe437075d64bf4cd727c5
- For 1.0 GHz overclocking download EZDZ_Godspeed1GHz_update03.zip
MD5 checksum: 7e1ac82406bcf818ed33d4e886bba99c
- For 1.2 GHz overclocking download EZDZ_Godspeed1.2_update03.zip
MD5 checksum: dfc699802cae2744b22ce32f10380df6
Good work
Awesome work!
Is there a way to set speed at 1Ghz? I am using SetCPU. Slider gives me only 245, 368, 768 and 1420MHz speed. Any ideas?
Oh! And is there easy way defuse this nice kernel? Root and S-Off I already had.
Still waiting for this f$*kin' phone in France, need it !
In setCPU, impossible to set speed at stock Mhz ? (806Mhz, correct ?)
As always, feel free to modify/edit/tweak/improve etc anything I share
How are the max frequencies/clockspeeds set ??
The overclocking script file /system/etc/init.d/03gtrabOC loads the overclocking module oc-dz.ko at boot, and sets its max speed.
The last line in the script sets the maximum overclocking value:
The only change between all versions is the final number at "pll2_l_val=x" (the MHz value multiplier is 19.2). Examples:
For stock 806.4 MHz
pll2_l_val=42
For 1017.6 MHz
pll2_l_val=53
For 1209 Mhz
pll2_l_val=63
For 1420 Mhz
pll2_l_val=74
How to delete the script 03gtrabOC to stop auto-loading the overclocking module ??
Using ADB commands from a PC:
adb remount (remounts r/w for that session if phone has unsecured kernel, like this one)
adb shell rm /system/etc/init.d/03gtrabOC
How is the overclocking module auto-loaded ??
The stock boot.img was unpacked, and inside ramdisk, bootcomplete.rc was edited to include a line which enables Busybox run parts at boot, then, with Notepad++ a line was added to the updater-script of the Update zip which gives running atributes to any script dropped into /system/etc/init.d. There's where the module-loading script 03gtrabOC was placed.
Was else was included or modified ??
- The overclocking module compiled by stridger was added to /system/lib/modules/
- Superuser APK was added to /system/app/ just in case it's missing or wrong.
- Su and the latest version of Busybox were added to /system/xbin/
- A full set of Busybox symlinks was added to the Update zip updater-script with Notepad++
- Inside the boot.img's ramdisk, defaul.prop was edited to ro.secure=0 (unsecured Kernel, "root")
- The Kernel itself was not touched, to avoid conflicts / problems (anyway the source is still not available).
How were these Update zips packed and signed ??
Using Daneshm90's Update zip tool.
How was the boot.img unpacked and repacked ??
Using scripts from dsixda's kitchen on Cygwin, a Unix emulator for Windows.
Thanks AGAIN mate. Is 1.4 GHz safe choice for everyday usage?
I'll try play with values, I just want that 1GHz too.
EDIT: And I want that 1.4 GHz value too. lol
03gtrabOC has only one value, is that some kind divider? I am sorry but I can not figure those tables out.
This works great. I assume that this now sticks between reboots?
ludow said:
03gtrabOC has only one value, is that some kind divider? I am sorry but I can not figure those tables out.
Click to expand...
Click to collapse
Updated post 1 (new 1GHz version) and post 5 (how to manually change overclocking speed / multiplier value)
sonofabit said:
This works great. I assume that this now sticks between reboots?
Click to expand...
Click to collapse
Yes it should
gtrab, quick question. As this update has root built in do i have to root my device first or can i simply install clockwork and apply this update?
huetson2 said:
gtrab, quick question. As this update has root built in do i have to root my device first or can i simply install clockwork and apply this update?
Click to expand...
Click to collapse
yes of course you need root and S-OFF to flahs this or anything non-official
check the easy tutorial FAQ linked on the post, you'll become a flashing master in 8 minutes
Is 1.4GHz the fastest we can go on the Z / without a custom kernel?
Seeing as the G2 can go up to 1.9GHz.
gtrab said:
yes of course you need root and S-OFF to flahs this or anything non-official
check the easy tutorial FAQ linked on the post, you'll become a flashing master in 8 minutes
Click to expand...
Click to collapse
been a while since flashing an htc (magic), been flashing a galaxy s for the last 6 months.
Have read the tutorial now thanks and all is clear again
DanWilson said:
Is 1.4GHz the fastest we can go on the Z / without a custom kernel?
Seeing as the G2 can go up to 1.9GHz.
Click to expand...
Click to collapse
I'm on 1.4Ghz, that's enough for me, but other users dare to go up and up. Check the other overclocking threads in this forum to see what other users are reporting.
This update zip won't change the voltage, just the speed, so we will have to find out
huetson2 said:
been a while since flashing an htc (magic), been flashing a galaxy s for the last 6 months.
Have read the tutorial now thanks and all is clear again
Click to expand...
Click to collapse
you're welcome
gtrab said:
I'm on 1.4Ghz, that's enough for me, but other users dare to go up and up. Check the other overclocking threads in this forum to see what other users are reporting.
This update zip won't change the voltage, just the speed, so we will have to find out
Click to expand...
Click to collapse
Come Christmas (well, a couple days after) my Z shall be pimped. -ish.
And I'll try an overclock of epic proportions. For five minutes, or until I crap myself. Which ever is first
this works well! Tnx man! finaly a way to overclock that stays after reboot!
all nice and stable @ 1.42GHZ
Great work! Might be a good idea to add a file with stock kernel and bcm4329.ko for the people who already flashed with a oc kernel.
JCreations said:
Great work! Might be a good idea to add a file with stock kernel and bcm4329.ko for the people who already flashed with a oc kernel.
Click to expand...
Click to collapse
The stock kernel and bcm4329.ko are already included
Just delete system/etc/init.d/03gtrabOC and you are back to stock
It stangely doesn't work for me.
I already have root and s-off. But when I apply the update my DZ freezes on boot-up.
I'm doing a nandroid recovery now. Hope it wil boot-up again.
gtrab said:
The stock kernel and bcm4329.ko are already included
Just delete system/etc/init.d/03gtrabOC and you are back to stock
Click to expand...
Click to collapse
hey gtrab i have kernel version 2.6.32.21-gd2764ed
will this still work on my desire z?
maus010 said:
It stangely doesn't work for me.
I already have root and s-off. But when I apply the update my DZ freezes on boot-up.
I'm doing a nandroid recovery now. Hope it wil boot-up again.
Click to expand...
Click to collapse
1.- Maybe you have a different ROM, o this is not "stock" for you
2.- Maybe yoou have a corrupt download. Did you check the MD5 checksums ??
Discontinued for now.
-------------------------------------
Okey just did some reorganisation to get this post a little bit cleaner.
I just deleted the unneeded versions, but I have a backup of them, so if you really want to have one of the older versions send me a pm and which one you want, else just stick to my recommendations below.
Most important question first:
Which Version should you take?
Siyah Kernel 2.6.6i and newer: init.d Gen 2.6.6i SE
Siyah Kernel 2.6.2 to 2.6.6: init.d Gen 2.6.2
Siyah Kernel 2.6_S99 to 2.6.1: init.d Gen 2.6
Siyah Kernel 2.5.* (all Versions, also GT): init.d Gen 2.5 SE
Siyah Kernel 2.4.2 to 2.4.*: init.d Gen 2.4.2 SE
Siyah Kernel 2.4.1 and older: init.d Gen 2.2 Beta 16 SE
What does SE and RRW stand for?
SE is for "Second Edition" and should be preferred, but you are free to take the version you like.
RRW is for "Remount Read/Write" and will remount "/system" with rw permissions, use this version if ADB Push fails to push the bootscript to the phone.
If you want to use push, pull or activate function you have to enable USB Debugging Mode else ADB can't recognize the device.
(Can be found under Menu > Settings > Applications > Developement > USB Debugging)
Please tell me if there are any issues with any function.
Known issues:
The function for deep sleep levels is not implemented correctly in the following 4 versions:
-init.d Gen 2.6
-init.d Gen 2.6 RRW
-init.d Gen 2.6.2
-init.d Gen 2.6.2 RRW
Fixed since 2.6.6i!
Thanks to gokhanmoral for the best kernel ever and helping me via pm!
Thanks to droidphile for this epic manual!
http://forum.xda-developers.com/showthread.php?t=1369817
Read it first for a better understanding of the values.
Screenshots (v 2.6.2):
Thanks to D5PiX for free image hosting
Changelog:
2.6.6i SE:
added ignore nice load to ondemand
fixed import function
fixed lazy governor
2.6.6.i:
deep sleep levels fixed
added suspend_freq to ondemand (since ondemandx was merged with it)
updated all values to the new ones from Siyah Kernel 2.6.7
2.6.2:
3 step gpu settings added
lulzactive v2 settings added
2.6:
Excluded charging currents (not needed)
Added a handfull of new options:
- deepsleep cpu and bus level
- second core sample settings (rate 2nd core on, off, screen off)
- smooth scaling parameters
- added AFTR settings
2.5 SE:
Added lulzactive samplerate settings
2.5:
Added touchscreen threshold
2.4.2 SE
Added delay function (the script will delay for a choosen amount of seconds before execution)
Added governordepending settings (sampling rate, up/downscale thresholds etc)
Added function to pull bootscript from phone to hard disk
2.4.2:
Updated to new default values.
Excluded "insmod/non insmod/legacy"-modes, insmodding will be included as needed by 2.4.2 Kernel
2.2 Beta 16 SE:
Exchanged "2.2 Beta 16 mode" with "always insmod mode"
2.2 Beta 16:
Improved including options
Added Siyah 2.2 Beta 16 referring insmod-settings
Added possibility to activate bootscript without restarting the phone
Added possibility to import settings from existing bootscript
Beta 2.2:
Included 2nd core thresholds for screen on and screen off
Included 2nd core loadbalancing (sched_mc)
Included displaysettings (min backlight and max gamma)
Change permission after pushing script to phone
Beta 2.1:
Possibility to include only selected tabs to the created script
Beta 2:
Added ADB to the package
Possibility to push script directly to phone via ADB
Beta:
CPU frequencies and voltages
Minimum/Maximum frequency used by governor
Governor
GPU frequencies and voltages
IO scheduler
Static busspeeds
Charging currents
Possibility to create and save script on harddisk
Beta 2 out now!
Will push your generated script directly to your plugged phone via ADB, just unzip, choose options, press ADB on Save tab and done.
Sources didnt change that much, will provide them later or after implementing the new siyah kernel functions.
Anything that you want me to implement first?
Any issues or errors while using it?
goose2600 said:
Runnig executable open a window where you can choose your preferred settings.
Then the program will generate the script and you have to copy it to device by hand
Click to expand...
Click to collapse
KcDaRookie said:
as goose said ATM you have to copy it by hand to /system/etc/init.d
but I will try to implement adb autopush so that you only have to click a button while the phones connected
Click to expand...
Click to collapse
Getting an old man, but always trying to learn more....
Can you give me (US) more explaination on the basic way to use it ?
CPU OK, GPU don't, IO Scheduler don't, BUS don't, CHARGING OK
Maybe if you could provide a text with your init. Gen
Sorry to be such a newbee...
GREAT JOB !
Kindly yours
Nice one
bvannier said:
getting an old man, but always trying to learn more....
Can you give me (us) more explaination on the basic way to use it ?
Cpu ok, gpu don't, io scheduler don't, bus don't, charging ok
maybe if you could provide a text with your init. Gen
sorry to be such a newbee...
Great job !
Kindly yours
Click to expand...
Click to collapse
think you !
The script generated works fine. ADB push too.
There is just a little mistake, the argument for busfreq_static si "disbled" by default instead of "disabled". But if you enable it then you disable it, it's well written "disabled".
I just add some lines in the script in order to modify the hotplug thresholds and it's perfect !
Thank you
Thank you Reno_kun, will change that asap!
altough the default kernel value is disabled so echoing disbled shouldn't have any effect ^^
will implement hotplugging treshold and brightness settings in next update, i hope i'll have time tomorrow ^^
edit: fixed that and did some rearranging.
Better and better
Incredible work, THINK YOU
Kindly yours
any chance to make phone app from this?
KcDaRookie said:
Thank you Reno_kun, will change that asap!
altough the default kernel value is disabled so echoing disbled shouldn't have any effect ^^
will implement hotplugging treshold and brightness settings in next update, i hope i'll have time tomorrow ^^
edit: fixed that and did some rearranging.
Click to expand...
Click to collapse
I've got an other problem
At boot, the script in init.d is not applied. I need to change permissions from rw-rw-rw- to rwxrw-rw- in order it is used.
What are usual permissions for a script in init.d ?
Thank you for your work KcDaRookie
@bvannier: thank you very much
@lokotus: you are free to use to sources to make an phone app from this, I don't have the knowledge that is needed for this, also i think using SetCPU, nofrills, voltage control or gokhanmorals tool for his kernel once it's released is much more efficient because the changes will take effect on the fly.
with this script you have to reboot at least once...
hmm.. I getting a great idea.. I think I will implement that the new values will directly be echoed via adb to the phone, so that they will immediately take place..
I tested a bit and this isn't impossible, thank you for this idea
Reno_kun said:
I've got an other problem
At boot, the script in init.d is not applied. I need to change permissions from rw-rw-rw- to rwxrw-rw- in order it is used.
What are usual permissions for a script in init.d ?
Thank you for your work KcDaRookie
Click to expand...
Click to collapse
I have mines set to 777 (rwxrwxrwx) but I think 766 (rwxrw-rw-) should be enough
I see if I can change permission via adb directly after push ^^
Thanks for that comment =)
Thank you guy !
I tried several time and I always had 666, it's may be due to the ROM ? Which one do you use ?
You should post some pict in the OP for showing that your soft is very easy to use
Reno_kun said:
Thank you guy !
I tried several time and I always had 666, it's may be due to the ROM ? Which one do you use ?
You should post some pict in the OP for showing that your soft is very easy to use
Click to expand...
Click to collapse
Am still on Stock ROM ^^
Will add pictures as soon as Beta 2.2 is uploaded.
There we go, new version with sources released.
It should set the permissions to 766 and also kill the adb-deamon after pushing the script to the phone.
Just tested and all work fine !
Thank you a lot !
If you have time, could you add an "import" feature in order to use a script already saved ?
@OP: awesome job dude
@Reno_kun: I'll think about it, but I think this will take some more time, will put it on the to do list ^^
@TecQuality: your welcome =)
KcDaRookie said:
@Reno_kun: I'll think about it, but I think this will take some more time, will put it on the to do list ^^
@TecQuality: your welcome =)
Click to expand...
Click to collapse
So with this tool we dont need voltage control anymore right?
Anyways, the intructions are: enable the debug mode, plug the device, generate a script and select the push command correct? We need to start the adb server?
Directly from my SGS II using xda premium
@TecQuality: No, you don't have to start the server manually, the adb push command starts the adb-deamon/adb server automatically but won't stop the deamon afterwards therefor I stop the server after pushing the bootscript and setting the permissions.
So you just start the tool, plug your phone to the pc in usb-debug mode, choose your configs and press ADB Push, after that restart your phone and the bootscript should apply at systemstart.
Installation Instructions:
Here's a step by step instruction to install this kernel:
[normal mode]
1. download the above file (via phone directly or to a PC)
2. copy the downloaded zip file to /sdcard/download/
3. extract boot.img from the zip file to a location of your choice ON YOUR PC
4. open up a command window (Windows) or shell terminal (Linux/Mac)
5. connect USB cable to the phone
6. type "adb reboot bootloader"
[fastboot mode]
7. type "fastboot flash boot boot.img"
8. Once fastboot flash is completed, disconnect the USB cable
9. Select hboot using volume buttons on the phone
[recovery mode]
10. Select recovery
11. go to /sdcard/download and select the downloaded zip file and let it run its script.
12. Once the script is done, select "reboot system now"
Note: After FLASHING, the first reboot may take longer than usual, please be patient... After the first reboot, it may lag during initial load (let everything finish loading). Once everything is loaded and phone is ready for use, reboot the phone a 2nd time and the lag will be gone and everything should be silky smooth...
****************** KitKat KERNEL (Android Version 4.4.x) ******************
Change Log => http://faux.romhost.me/endeavoru/kk44/changelog.txt
(Mainline Edition: All Variants => 1.40 Quad)
The File ==> One-X Kernel Mainline <==
OLD OLD DEPRECATED KERNELS BELOW
****************** Ice Cream Sandwich KERNEL (Android Version 4.0.x) ******************
(Mainline Edition: All Variants => 1.40 Quad)
The File ==> One-X Kernel Mainline <==
(Ultimate Edition: Variant based CPU overclocking: Variant 3 => 1.60 Quad, Variant 2 => 1.55 Quad, Variant 1 => 1.50 Quad)
The File ==> One-X Kernel Ultimate <==
************** ABSOLUTELY NO SUPPORT FOR THIS VERSION AT ALL, DON'T EVEN BOTHER TO POST **************
(Ultimate Edition: Variant FREE CPU overclocking: Variant 3 => 1.60 Quad, Variant 2/1/0 => 1.55 Quad)
The File ==> One-X Kernel Variant Free <==
[ Advanced Users: ]
How to find tegra3 CPU variant information with my kernels:
use terminal or file explorer of your choice with root access and read/open this following file below:
Code:
/sys/kernel/debug/t3_variant
cpu_process_id <== is the variant info range from 0~3
[ Optional: ]
[ For Kernel Devlopers ONLY: ]
NEWS BULLETIN:
One-X kernel 012 is out based on latest CM release!
Please don't hesitate to talk among yourselves and help each other out... The XDA community is what inspired me to hack kernels for everyone since everyone here is nice and helpful to each other... Keep helping each other.... Famous proverb: It's better to give than to receive...
Standard Disclaimer: Not responsible for bricking your phone, voiding your warranty, or any other pain or suffering you may feel as result of using this kernel!!!
My github Complying with GPL
https://github.com/faux123/android_kernel_htc_endeavoru
Follow me on
:
If you find this Kernel useful, feel free to hit the [Like] button below
History:
Change Log
DUE TO MY EXTREMELY BUSY SCHEDULE BOTH @ WORK AND @ HOME, I WILL ONLY MAKE MAJOR ANNOUNCEMENTS ONCE PER WEEK
Open Beta may not be stable and may cause issues with your phone!
By loading open beta you have agreed to:
1. To report all random reboots with associated /proc/last_kmsg
2. To provide feedback on errors or bugs with detail phone information such as ROM, kernel version, and apps
3. Participate in Forum discussions for the beta software with others without FLAMING each other or post useless information such as:
a} Phone doesn't boot (without providing any additional information, ROM versions etc)
b} phone is too hot (without providing any additional information, ie OC freq, UV etc)
The Open Beta system is designed to have the community help each other and the developers. This way, all potential bugs are flushed out so the final released version will be stable and error free. The more actively you participate in Beta Testing the better the final product will be (you are really helping yourself to create a better community software).
If you do NOT agree with the statements above, DO NOT load my Open Beta software.
Kernel 012 Open Beta 1 is out! (BETAs ARE ALWAYS ULTIMATE + Variant Free unless I stated otherwise)
ICS ==> http://faux.androidro.ms/endeavoru/beta/endeavoru-Faux123-012b1.zip
[ build 1 ]
Add Low Power (LP) core overdrive
(What is LP overdrive? LP core is capable of running up to 620 MHz @ 1.3 volts, so I simply unlocked the LP core to allow it to operate @ max freq. The overdrive also adjust the G cluster / LP core cross over point. The stock version was @ 475MHz LP / 370 MHz G-cluster, I moved the cross over point to 620MHz LP / 513 MHz G-cluster).
What does all this mean? It means LP core is now able to handle more load up to 620MHz single core before switching over to the more power hunger G-Clusters. This should theoretically save more battery life (since LP core is designed to very power frugal in Hardware). When you check the CPU stats with CPUSpy, you will see the cross over points 513MHz and 620 MHz to have high usage time. <== THIS is normal because the stats counts BOTH the LP time and the G-Cluster time so it appears to have more time than other frequencies.
reserved 3
SWEET FAUX IS HERE TOO!
Flashing now
Woot. First post . Thanks faux !
Sent from my HTC One X using XDA
Edit: beat me to first
Great to see you here
Welcome. Heard many good stuff about your work and very glad that you are here. Rated your thread 5 stars and thanked you as well Hope you get your phone soon
Thanks, looking forward to trying this out, will flash later tonight with a fresh ARHD 5.1.1
Nice to see you here mate. have you a changelog for us?
Holy Crap! it's faux! woo. I guess you got your hands on a 1X?
MarcoHD said:
Nice to see you here mate. have you a changelog for us?
Click to expand...
Click to collapse
http://rootzwiki.com/topic/25336-kernelone-x-sense-40-001-beta-may-11/
Hi faux,
As developer do you think that the flicker issue (on some devices) can be solved from the software side? I'm asking this becasue I'm still waiting for the fix from someone and don't want to send the device back to the shop if it will be possible to fix this via software.
Many thanks in advance!
hiazn said:
Holy Crap! it's faux! woo. I guess you got your hands on a 1X?
Click to expand...
Click to collapse
Nope... still don't have 1.. read the first line on my OP...
H377 said:
Hi faux,
As developer do you think that the flicker issue can be solved from the software side? I'm asking this becasue I'm still waiting for the fix from someone and don't want to send the device back to the shop if it will be possible to fix this via software.
Many thanks in advance!
Click to expand...
Click to collapse
Don't have the phone. so I don't know what flicker issues...
So can we set lower voltages with this kernel by using the app systemtuner?
Sent from my HTC One X using XDA
faux123 said:
Don't have the phone. so I don't know what flicker issues...
Click to expand...
Click to collapse
On some devices at some brightness levels, mostly on gray images the screen behaves not as expected. It starts to flicker but only on the grey part of image. (for me at least).
It's like installing an OS on PC with a generic display driver, like if the refresh rates were not correct.
Here are some benchmarks screen shots:
Hi faux!
Can the kernel be flashed right onto ARHD 5.1.1 or does it have to be adapted to ARHD?
Greetings
Edit: Tried it myself and it works on ARHD 5.1.1
Antutu Benchmark is : 10121
Quadrant BM is: 4366
Unfortunately, I have to admit that my Antutu scrore was around 11000 with Bricked Kernel,
but whatever
faux123 said:
Don't have the phone. so I don't know what flicker issues...
Click to expand...
Click to collapse
No flicker issues here....
Sent from my HTC One X using xda premium
Hey Guys,
I thought while waiting for the first custom kernels that maybe i should have a look at the interactive values and try to tweak them based on this way:
http://forum.xda-developers.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557
So i took a script from @Alcolawl and modified it to work with our device. Many thanks for his scripts.
I adjusted the values to our snapdragon 820 as the original scripts are for the nexus 6p which runs with a snapdragon 810. (octa on the 810 vs quad-core on the 820)
I´d highly recommend to try these values as it gave me a significant boost in battery life. here is a screenshot:
https://drive.google.com/file/d/0BxbxiBXaZVu-N1lsRTMyZ2hsY1k/view?usp=sharing
https://drive.google.com/file/d/0BxbxiBXaZVu-N1MzamRvM2FVZlk/view?usp=sharing
BIG UPDATE: with base 1.80 i´m not able to trick the touch/Input boost from htc´s pnpmgr with a chmod command like i did before. so all versions since Butterfly v11 will disable pnpmgr completely.
that means if you Play high end games and your device overheats like crazy please Report back. i had no Problem until now.
also there are now 2 versions. the oc one is for overclocked cpus with elementalx. without oc is for the default clock speeds.
here are explanations on what the 2 different stragies do:
Butterfly - A culmination of all strategies, provides smoothest performance of all currently published settings, though battery savings are a little more modest. Excellent for light and moderate users; heavy/marathon users might want to check out a different setting profile as it gets battery intense with heavy usage.
GhostPepper - Uses a quantized, frequency-aligned parametric curve to influence low core clock rates while providing extremely smooth transitions from each clock rate and exceptional battery life. Good for light to medium usage and multitasking.
So basically there will be two ways of applying this mod.
First one is via scripts. this allows to set parameters outside of the interactive governor controls like cpu boost, editing of pnpmgr, min/max frequencies etc. so basically there´s more control.
Second one is via EX Kernel Manager. I will upload the profiles and you can apply them directly into the app. This will however only affect the tunables of the interactive governor. Touchboost has to be set manually for the profile to work exactly as intended.
when the phrase "elex" is in the zips name it is for use with ex kernel manager app (loading profile in governor options screen.
so to try the script method follow these steps. (and before do a nandroid as always)
1. download the attched file.
2. unzip the file, choose the correct script (oc if you have overclocked)
3. with a root explorer or terminal copy the file to system/su.d
4. set the correct permissions (rwxr-xr-x)
now you may either choose to change the settings temporary (step 5A) until the next reboot or permanently upon each reboot (step 5B)
5A. rename the file to 50ghostpeppertenv3.sh
use any script manager and run the script from this location (system/su.d)
alternatively use any terminal emulator app with the following commands
su
cd system/su.d
sh 50ghostpeppertenv3.sh
Be advised that the script takes in its current state 60 seconds to be applied. So the changes need a minute to be applied.
now check if the script has applied
- to do this go to sys/devices/system/cpu/cpu0/cpufreq/interactive/target_loads
- if it looks like this: "25 480000:35 652800:45 844800:60 960000:75 1113600:85 1228800:90 1401600:95 1593600:100" the script was applied successfully
- the values changed with each update. what´s important to check is just the generel layout
5B. (-if you did the temporary approach beforehand remove the .sh)
- it should look like 50ghostpeppertenv3 (make sure there are now spaces at the end)
reboot and check if the script has applied
- to do this go to sys/devices/system/cpu/cpu0/cpufreq/interactive/target_loads
- if it looks like this : "25 480000:35 652800:45 844800:60 960000:75 1113600:85 1228800:90 1401600:95 1593600:100" the script was applied successfully.
-- the values changed with each update. what´s important to check is just the generel layout
Important!!!
if you run permissive and run into no signal issue due to this look here
if you should run into a no signal issue where your baseband shows as unknown under software status ( currently on custom roms eg leedroid) you have to put a script to system/su.d that sets selinux to permissive. attached is such a script.
unzip it. copy it to system/su.d
set the same permissions as the ghostpepper script and your good to go.
running in terminal the command "getenforce" should return permissive.
Second method via Elemental App:
1. Download the desired profile from the attachments
2.Extract the Profiles from the zip
3. Choose the Overclocked(oc) version if you overclocked
4.Copy the file to sdcard/ElementalX/gov_profiles
5. Open the app and apply the values
let me know if it brings a little battery boost for you. you may also let me know if you face performance issues.
Thank you and have fun testing it.
Changelog:
Ghostpepper:
v1: Initial Release
v2: Tweaking The Script so the values will get applied properly on all roms
adding a permissive script in case of getting enforced
v3: Removed touchboost so the profile may unleash its full potential <<--- results in overall slower device.
v4: Added back short input boost
v4withtb: Added back original touch boost from htc
v8: New try on getting the interface smooth and disabling touchboost (minimal stutter remains)
v8withtb: same as v8 touchboost is still active
v9: only one version with touchboost now. tweaked target loads (lower freqs are used more), short input boost
there are now two files inside the zip.
v10: try to further improve frequency usage, less aggressive scaling
v11: fix in case Little cores might get stuck at highest clock
Butterfly
v4: Initial Release
v4withtb: Initial Release with original touch boost from htc (extremely smooth)
v6withtb: tuned the values and kept touchboost from pnpmgr, kernel touch boost is disabled, extremely smooth for me
v7: less aggressive scaling, performance should be really good while reducing less power than v6
v9: basically scaling is tuned to respect the crossover effieciency point from big and little cluster
v11: updated to work on base 1.80
- disable pnpmgr completely because the chmod trick for disabling pnpmgr´s touchboost is no longer working
- enable msm_thermal and core_control
v12: tweak some values to work better with the new base
v13: hotfix as i made a mistake in the previous version
credits:
thanks to @Alcolawl for the script template
also thanks to @soniCron for the original thread
reserved
Thanks for this - about to try it out now.
Question, though - Instead of using init.d, which requires a modified ramdisk, why not just use su.d, which only requires SuperSU?
EDIT: It doesn't seem to be loading when using su.d either.
Thanks. I'm using it now. Will let you know if there are any performance problems.
Can you also make a script that makes the phone smoother?
Captain_Throwback said:
Thanks for this - about to try it out now.
Question, though - Instead of using init.d, which requires a modified ramdisk, why not just use su.d, which only requires SuperSU?
EDIT: It doesn't seem to be loading when using su.d either.
Click to expand...
Click to collapse
Yeah it's strange. When flar will Releases his kernel, init.d will be hopefully working.
Seems like we have to apply it manually for now. When exkm gets updated we can switch profiles there so maybe we should just find good values now.
gusoldier said:
Thanks. I'm using it now. Will let you know if there are any performance problems.
Can you also make a script that makes the phone smoother?
Click to expand...
Click to collapse
Did you face a performance loss with these values? For me it's already pretty smooth.
But sure I may trim it more performance oriented yes.
Freak07 said:
Did you face a performance loss with these values? For me it's already pretty smooth.
But sure I may trim it more performance oriented yes.
Click to expand...
Click to collapse
Compared to stock I feel no performance loss, as smooth as stock. What I actually meant was a new script for buttery smooth nexus like experience.
Btw I will also check how hot it will get. On stock the phone gets sometimes hot watching youtube etc. Hopefully it'll better with this script
gusoldier said:
Compared to stock I feel no performance loss, as smooth as stock. What I actually meant was a new script for buttery smooth nexus like experience.
Btw I will also check how hot it will get. On stock the phone gets sometimes hot watching youtube etc. Hopefully it'll better with this script
Click to expand...
Click to collapse
yeah. I can try this later. But compared to my nexus 6 and my pixel c the 10 is about as smooth.
Freak07 said:
Yeah it's strange. When flar will Releases his kernel, init.d will be hopefully working.
Seems like we have to apply it manually for now. When exkm gets updated we can switch profiles there so maybe we should just find good values now.
Click to expand...
Click to collapse
Got it working with su.d. Just needed to add some sleep at the beginning of the script, otherwise it runs too early and the parameters can't be set .
P.S. You didn't answer my question about why you're not using su.d instead of init.d?
Captain_Throwback said:
Got it working with su.d. Just needed to add some sleep at the beginning of the script, otherwise it runs too early and the parameters can't be set .
Click to expand...
Click to collapse
Can you post it? I will add it to op thank you captain!
Edit: didn't think about it I'm not that knowledgeable.
Or is it just like "sleep 30"?
Edit2: it is indeed. thank you again.
Freak07 said:
Can you post it? I will add it to op thank you captain!
Edit: didn't think about it I'm not that knowledgeable.
Click to expand...
Click to collapse
Sure, right now I'm just trying to find the minimum sleep value that works, and once I do, I'll post it.
RE: su.d, see the 2nd paragraph here: http://su.chainfire.eu/#selinux-policies-supolicy
An additional advantage besides the ones listed there is that in a systemless root setup, su.d doesn't require modifying system at all, which is important for being able to take OTA updates in the future. On this device, I try to touch system as little as possible (if at all), so it might be a better alternative, and doesn't require a custom ramdisk.
Captain_Throwback said:
Sure, right now I'm just trying to find the minimum sleep value that works, and once I do, I'll post it.
RE: su.d, see the 2nd paragraph here: http://su.chainfire.eu/#selinux-policies-supolicy
An additional advantage besides the ones listed there is that in a systemless root setup, su.d doesn't require modifying system at all, which is important for being able to take OTA updates in the future. On this device, I try to touch system as little as possible (if at all), so it might be a better alternative, and doesn't require a custom ramdisk.
Click to expand...
Click to collapse
yeah you´re right. thanks for the reference and the hint. i knew about it but didn´t remember i could use this see my edited last post. with sleep 30 it´s working for me. i updated the op.
besides, do you had any luck in finding your pvs bin? i´m extremely intersted in this. i only found my voltage table so far. maybe you may post yours too. i opened a thread here:
http://forum.xda-developers.com/htc-10/how-to/post-voltage-table-chip-t3383494
if we had a way to check our pvs bin it would be even more helpful.
Freak07 said:
yeah you�´re right. thanks for the reference and the hint. i knew about it but didn�´t remember i could use this see my edited last post. with sleep 30 it�´s working for me. i updated the op.
besides, do you had any luck in finding your pvs bin? i�´m extremely intersted in this. i only found my voltage table so far. maybe you may post yours too. i opened a thread here:
http://forum.xda-developers.com/htc-10/how-to/post-voltage-table-chip-t3383494
if we had a way to check our pvs bin it would be even more helpful.
Click to expand...
Click to collapse
sleep 30 didn't work for me, as I have another script running before this one. It's probably safer to go with sleep 60 to make sure it loads for everyone (sleep 45 did work for me too, but 30 was too short - figured it's better to allow more time). Just a suggestion, or you could just tell people that if it doesn't load for them to increase the sleep value. Up to you, really.
EDIT: And I don't know anything about a pvs bin
Captain_Throwback said:
sleep 30 didn't work for me, as I have another script running before this one. It's probably safer to go with sleep 60 to make sure it loads for everyone (sleep 45 did work for me too, but 30 was too short - figured it's better to allow more time). Just a suggestion, or you could just tell people that if it doesn't load for them to increase the sleep value. Up to you, really.
EDIT: And I don't know anything about a pvs bin
Click to expand...
Click to collapse
Okay i'll edit it to 60.
This is what I'm talking about. Every Chip has a pvs bin. The higher the bin the lower the voltage for a certain cpu frequency.
And every bin has its own voltage table.
http://forum.xda-developers.com/htc-one-m8/general/guide-snapdragon-801-clocking-voltage-t2807173
Hey @Freak07,
Wondering if you can help.. Can't seem to get this working?? Please see attachment. I've set permissions and used terminal to get it working but no dice?
Edit: Nevermind.... I can't follow simple instructions to unzip a file (I was renaming the zip rather than unzipping and renaming that to .sh).... #Special
Edit 2: Went straight for option 5b (so it should have worked on reboot). When I rebooted I lost the radio and have had to clean flash my ROM? I was on Leedroid's Rom when it happened.
rav101 said:
Hey @Freak07,
Wondering if you can help.. Can't seem to get this working?? Please see attachment. I've set permissions and used terminal to get it working but no dice?
Edit: Nevermind.... I can't follow simple instructions to unzip a file (I was renaming the zip rather than unzipping and renaming that to .sh).... #Special
Edit 2: Went straight for option 5b (so it should have worked on reboot). When I rebooted I lost the radio and have had to clean flash my ROM? I was on Leedroid's Rom when it happened.
Click to expand...
Click to collapse
Which Kernel were you on?
This morning i had the same issue when flashing tbalden Kernel using leedroid and my Script.
Freak07 said:
Which Kernel were you on?
This morning i had the same issue when flashing tbalden Kernel using leedroid and my Script.
Click to expand...
Click to collapse
Hey buddy,
I was on the kernel built into Leedroid.
Hope that helps.
rav101 said:
Hey buddy,
I was on the kernel built into Leedroid.
Hope that helps.
Click to expand...
Click to collapse
How did you recover? Full Wipe?
Delete
Freak07 said:
How did you recover? Full Wipe?
Click to expand...
Click to collapse
Yeah, I tried a dirty wipe but that didn't work so had to do a full wipe.