FuguMod kernel is now available for the Galaxy Nexus.
It has been reported to work both on GSM and CDMA versions. But I can only test it on GSM version myself.
You can download them at:
http://fugumod.org/galaxy_nexus/
Source and changelog can be found here:
https://github.com/renaudallard/gnexus_kernel
IRC channel:
irc.freenode.net #fugumod
To install, just download the appropriate version for your ROM (4.0.x) and flash it with fastboot (RAW version: fastboot flash boot kernel-$VERSION.img) or flash it with CWM (CWM/zip version).
Please note that not all versions exist in CWM format.
4.0.2 version is based on official google initramfs + init.d support (is now in deprecated state, no future updates will be brought)
4.0.3 version is based on the initramfs of AOSP + init.d support. it is compatible with 4.0.4
4.0.4 version is based on the initramfs of AOSP + init.d support. it is compatible with 4.0.3
4.1.x version is based on the initramfs of AOSP + init.d support.
4.2.x version is based on the initramfs of stock kernel
4.3 version is based on the initramfs of stock kernel (use that one for CM, not reco)
4.3-reco version is based on the initramfs of stock kernel, even with install-recovery.sh enabled (so supersu can work, but if you don't have supersu, don't use it)
for experimental versions, do not flash if you are not ready for big troubles, they may not even boot, burn your phone and eat your cat.
Features:
- stackprotector
- various security enhancements
- RCU boost
- Automatic process grouping
- TUN (compiled in kernel)
- latest 3.0 linux kernel
- newer wifi driver
- gamma/color hack
- CM9 compatibility
- PaX (from r333)
- grsec (from r624)
- TouchWake from Ezekeel (from r778)
Versions
Kernels are based on the below version scheme
kernel_FuguMod_20120111_r20-4.0.3.img
20120111 is the date it has been packaged
r20 is the release number
4.0.3 is the ROM it is compatible with
Color offsets
In CM9, just use the built in function.
For other ROMs, the settings offsets are in
/sys/class/misc/samoled_color/
For example green_v1_offset
Just edit the three green red and blue color settings. Default value is 60.
It can be done on the console with a command like this: echo 55> /sys/class/misc/samoled_color/green_v1_offset
Stable vs Testing
There are sometimes kernels in testing folder. These may be very stable or may not boot at all. Be sure to have an USB cable and fastboot under the hand if you try one of these. That said, in general, if they stay into testing folder for more than 15 min, they should at least boot and work more or less. I tend to remove non booting kernels from testing folder in less than 10 min (depending a little bit on the speed testers take them), and so if you see them one hour later, you should assume they are safe enough to flash.
So, in general Stable is the safest bet, but Testing may be the best. I, myself, generally run testing one.
Deprecated folder
In general, unless you really know what you are doing, you should avoid flashing those, they are mainly there for historical reasons.
Radio drops and blueish/faded screens
Please ensure you are running the correct firmware for bootloader and baseband, like in the matrix in bottom of that page: http://source.android.com/source/building-devices.html
For those where problems persist after flashing recommended versions, try "echo 0 > /sys/kernel/debug/smartreflex/sr_core/autocomp"
OTG unmounting internal SD
Please see http://forum.xda-developers.com/showpost.php?p=24040652&postcount=174
Mirrors
bootloaders: http://fugumod.org/bootloaders-gn/
basebands: http://fugumod.org/modem/galaxy_nexus/
Check for vulnerabilities
http://www.xray.io
Compatibility with hackish style apps
All apps which require direct memory write, access to symbols or memory offsets or modules will NOT work. And, no, don't ask they won't be supported in the future.
Security
If you want good security when your phone is stolen, in addition to encryption, don't forget to turn debugging off. Also, use enpasschanger to change your encryption password, any short PIN encryption can be cracked in a few minutes easily (for example, using my script at http://pastebin.com/Mdu06RZN)
Redistribution
As per GPL, you are authorized to redistribute this kernel with any of your custom ROMs provided you give out the source code like I do. You can link to my github in your distribution site.
However, if you modify the kernel yourself, whatever the modification is (compiling it yourself with a different compiler is a modification), you are not authorized to name it FuguMod, although you can credit me and tell the base comes from FuguMod but you cannot call the kernel itself FuguMod.
Touchwake
to enable it "echo 1 > /sys/devices/virtual/misc/touchwake/enabled"
to make it always on: "echo 1 > /sys/devices/virtual/misc/touchwake/always"
Beware, touchwake is known to sometimes produce screen locks
PGM
See "Compatibility with hackish style apps". Use touchwake instead.
Lost root
Use supersu instead of superuser from chainsDD (superuser from koush seems to work fine too). Change the setting in SuperSU to ignore CM root setting if you are running CM.
Updater app
https://play.google.com/store/apps/details?id=my.zin.rashidi.android.fugumod
root on 4.3
Currently only reco version has support for root access with supersu. Keep in mind that su access is now (as of 4.3) provided by a daemon, which may drain your battery or worse. Please think about your uses for root to see what is better fit for you.
W00t fugumod on the nexus!!
Will try it, thanks for dropping this here.
I'm totally happy
Finally! A kernel we can rely on Thanks alot mate, looking forward to further developments on this. I remember FuguMod fondly on the SGSII
Nitroz said:
Finally! A kernel we can rely on Thanks alot mate, looking forward to further developments on this. I remember FuguMod fondly on the SGSII
Click to expand...
Click to collapse
You probably mean SGS1.
I'm not entirely sure how accurate setcpu is at reading frequencies, but it seems to be stuck at 700mhz after a reboot. Moving the sliders a bit allows the cpu to use the entire range of 350-1200mhz as intended. I'm on AOKP milestone 2 if it matters and using r26.
Haven't yet tried this, but maybe min frequency when booting is set to 700mhz?
when you open setcpu, is the min slider at 350mhz?
What governor are you using? Not sure it matters though, but it might so.
maybe try using cpuspy to read the usage. Also, there may be something in your init.rd limiting the frequencies
Sent from a Nexus
Yes, min and max are set at 350/1200 on the sliders, but the green text says it's at 700/1200. Governor is the default interactive. Right now, I'm only using setcpu as a tool to view my frequencies as everything is "under observation" as I've only had this phone for a week. I did a reboot last night before going to bed. When I woke up 6 hours later, batt was down to 92%. Which is a quite fast considering I only had 5 hours of sleep. That's when I noticed that frequency was pegged at 700mhz the whole time. I tried opening other apps that should ramp up the speed, but as far as I can tell, it was still at 700.
Now, as I said, I'm only using setcpu to check my frequencies so "set at boot" isn't applied. When I apply "set at boot," min/max is at 350/1200 after a reboot and CPU scales up and down properly. So does this mean the default setting of the kernel is 700/1200? The thing is, even with max at 1200. I can't seem to make it scale up to 1200.
EDIT:
nikademus said:
maybe try using cpuspy to read the usage. Also, there may be something in your init.rd limiting the frequencies
Sent from a Nexus
Click to expand...
Click to collapse
I don't seem to have an init.rd file anywhere. I did a search using root explorer.
Edit 2:
CPUSpy says I'm only using 700 and DeepSleep even after running Asphalt 6. This is after a reboot without setting anything at boot with setcpu.
j.go said:
Yes, min and max are set at 350/1200 on the sliders, but the green text says it's at 700/1200. Governor is the default interactive. Right now, I'm only using setcpu as a tool to view my frequencies as everything is "under observation" as I've only had this phone for a week. I did a reboot last night before going to bed. When I woke up 6 hours later, batt was down to 92%. Which is a quite fast considering I only had 5 hours of sleep. That's when I noticed that frequency was pegged at 700mhz the whole time. I tried opening other apps that should ramp up the speed, but as far as I can tell, it was still at 700.
Now, as I said, I'm only using setcpu to check my frequencies so "set at boot" isn't applied. When I apply "set at boot," min/max is at 350/1200 after a reboot and CPU scales up and down properly. So does this mean the default setting of the kernel is 700/1200? The thing is, even with max at 1200. I can't seem to make it scale up to 1200.
EDIT:
I don't seem to have an init.rd file anywhere. I did a search using root explorer.
Edit 2:
CPUSpy says I'm only using 700 and DeepSleep even after running Asphalt 6. This is after a reboot without setting anything at boot with setcpu.
Click to expand...
Click to collapse
OK, 4.0.3 init.rc I have been given is the one from Francisco Franco and it limits the minimum frequency to 700mhz. This will be solved in next build, in a few minutes. Although you should be able to go over 700Mhz
nikademus said:
OK, 4.0.3 init.rc I have been given is the one from Francisco Franco and it limits the minimum frequency to 700mhz. This will be solved in next build, in a few minutes. Although you should be able to go over 700Mhz
Click to expand...
Click to collapse
Ah, well that's good to hear. Maybe the conditions needed to raise the frequency are not being met. Not that I know anything about kernels...
j.go said:
Ah, well that's good to hear. Maybe the conditions needed to raise the frequency are not being met. Not that I know anything about kernels...
Click to expand...
Click to collapse
Try the latest version, I removed all Francisco tweaks.
nikademus said:
Try the latest version, I removed all Francisco tweaks.
Click to expand...
Click to collapse
All right, I'll give it a spin tonight and post how it goes. Thanks!
I think I will be upgrading my phone to 4.0.3. This would mean I would not support 4.0.2 as I would not be able to test it properly. Are there users here who need the 4.0.2 version?
great
R37 für 4.0.3 runs flawless.
I use CM9 kang by fitsnugly.
R40 also flawless on fitsnugglys CM9 kang
r41 is out, probably last release for today
I flashed the latest KANG from today and the 122211 gapps with R41.
Works like a charm so far
aosp kang built today, flashed R43 just now. booted fine first try, wifi/bluetooth are fine, data call as well, rebooted, set scheduler/gov to deadline/ondemand, min/max freq to 1.2ghz, score on antutu maxing out around 5200, 5300. with my modified stock, i hit 6200+ in those conditions.
switch back to cfq/interactive, sd write speed goes up a bit to 10.4mb/s (deadline was just under 9.4mb/s), cpu integer 1304, float 1099, pushes score up a bit but still not reaching 5400 (this is with all tests selected, 2d/3d, database..). tweaked lowmemorykiller, antutu score jumps to 5600+.
but benchmarks mean almost nothing, i know. overall it's pretty smooth, fast on bootup, ocasional "lag" here and there (but that may be Mr. Android's fault).
will report more as the kernel settles in.
thanks nikademus.
edit: just re-installed gta. it seems i have no in-game sounds at all? it's fine until it gets to the main menu though. anybody else seeing this? happening on stock kernel too, wth..
edit2: jumping on r44.
flashed R44 on the latest fitsnugly kang. all is well. as expected, as only unused modules have been removed
Related
Thanks to Leshak , AndSecTest, mimocan, Unhelpful, xan, Supercurio and husq510 for the help.
This project started based on information found here:
http://forum.xda-developers.com/showthread.php?t=740514
But is has soon revolved into more fixes, patches and hacks. Thanks to all the developers involved and do buy them beers so they can continue to work on the fixes.
I've tested it to work on my phone but i cannot guarantee it will work on yours or if it will damage your phone so use it at your own risk. See known issues below if the problems have been resolved
Primary Features
- ext2/3/4
- Support I/O Scheduling for CFQ (stock), Noop, Deadline and Anticipatory
- Overclock and Undervolt support
- Overclocking for better performance. If you do not want to OC, use SetCPU to set Max at 1Ghz and enable checkbox Set on boot
- User defined Undervolt to save battery especially at lower frequencies. Use Xan's app for easy GUI control - here
- Also use Xan's app to change IO scheduling
- Rooted ADB shell for Android commander compatibility
Requirement
- i9000
- For Eclair 2.1 Only (Will not work on Froyo firmware)
My setup for cross compile without wakeup lag
- Use ct-ng crosstool
- Copy config file from arm-unknown-linux-gnueabi
Download
See attachment
Stock Kernels for reverting
Stock JM3 v3 kernel
Stock JM2 kernel
Stock XWJM5 kernel
Instructions:
- Extract the tar file from .7z
- Load tar file in PDA using ODIN and flash
- Do not check repartition and do not use pit file
- Use SetCPU to adjust frequencies
Reporting Problems
Please provide information below to help me understand:
kernel version: (eg oc120uv2-ctng)
UVLF setting (if kernel supports): (eg 50)
UVHF setting (if kernel supports): (eg 25)
descriptions:
Known Issues
- ondemand setting is unstable (need more verifications)
TO DO LIST
- BFS scheduling
- kernel modules (submit request)
Changelog
oc120_voodoo_b4.2
- enable CWM support even with voodoo ext4. Caveats: CWM will unmount /data after nandroid backup, you will not be able to remount /data in ext4 until you reboot back to recovery. Also, restore does not work when trying to restore /data.
- fixed check for debug_mode (it used to create logs in /sdcard/Voodoo/logs regardless if you enable*debug in /sdcard/Voodoo/)
oc120_voodoo_b4.1
- BLN patch v4 from neldar (http://forum.xda-developers.com/showthread.php?t=772672)
- All credit goes to author
- Signed update.zip format so rename file to update.zip and copy to /sdcard
- use recovery to flash
oc120_voodoo_b4
- updated to voodoo b4 (http://project-voodoo.org) - please read Documentation/FAQ, if you have previous installed Voodoo Beta1, please uninstall before upgrading
- Excludes color patch for later release
- All lagfix credit included in this build goes to Supercurio, please buy him a beer or two so he can continue on working on the project
oc120_voodoo_b3.1
- fixed init.d not working
oc120_voodoo_b3
- remove performance governor from startup cos i9000 dont need that
- added init.d support
oc120_voodoo_b2
- Use stock GPU ~200mhz table
- Voodoo2 lagfix (http://project-voodoo.org) - please read Documentation/FAQ, if you have previous installed Voodoo Beta1, please uninstall before upgrading
- Excludes color patch for later release
- All lagfix credit included in this build goes to Supercurio, please buy him a beer or two so he can continue on working on the project
oc120uv2
- Unhelpful patch for GPU table (http://github.com/Unhelpful/linux-galaxy/commit/5a729d3e2189159a20b00e0c331f0b112490e075)
- Interactive governor (http://github.com/Unhelpful/linux-galaxy/commit/aea72a98a2f261901d6f28f2d1deae3921d35948)
- user configurable UV settings (default value = 0 for UVLF and UVHF) for conservative governor only
- /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVLF_mV (for 100-800mhz)
- /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVHF_mV (above 800mhz)
- for example # echo 50 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVLF_mV (will UV by 50mV for 100-800mhz)
- for example # echo 50 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVHF_mV (will UV by 50mV for 1-1.2ghz)
- Setting increment of 25 (eg 25,50,75,100). Anything out range may hang
- Anything above 100 will be set to 100 (but I doubt you can get 100mV without crashing)
- After setting, do ur benchmarks and if everything is stable, you can add the command above into your init script depending which lagfix you have, add into your script.
Thanks!
Some questions:
1) the first thread about oc mentioned 1.2ghz, was this unstable for you?
2) Is this over-volted, under-volted, or no changes in voltage?
3) I'm guessing if I update to this kernal, I will loose any features of other kernals, like the lag-fix kernal?
I hope you can persuade the other devs to include this in their roms.
It this just for the unbranded SGS or does it work for TMO vibrant too?
Novek said:
It this just for the unbranded SGS or does it work for TMO vibrant too?
Click to expand...
Click to collapse
the kernel is just for the international version
it is just a test, i hv not test the limit yet.. this is a new phone so want to take it easy
i kept the voltage stock so just overclock a little and if its stable, will do more . More testing and reading is needed before i touch on the voltage.
it does not include mimocan's mod, i will work on it next release
Not Work
Hi GS S user,
not work in XXJP3 rooted Firmware!
Flash, Boot and go in Recovery menu!
Sir-ay said:
Hi GS S user,
not work in XXJP3 rooted Firmware!
Flash, Boot and go in Recovery menu!
Click to expand...
Click to collapse
XXJP3 is froyo.. android 2.2
he clearly states it works in eclair... android 2.1
Nice job cant wait to see how high the new hummingbird cpu can go. The galaxy s 2 has same cpu and is running at 2 ghz (if the leaked info is correct). I hope we can push it up to 2ghz with out to much voltage/heat increase.
[[ Cold ]] said:
XXJP3 is froyo.. android 2.2
he clearly states it works in eclair... android 2.1
Click to expand...
Click to collapse
upps
I will OC!!!!!!!!!!
Do you notice the postive effects of the overclock in any way? What does it do with benchmarks? Also do you test for (temperature) stability with some games as well, as they use the graphics card a lot which is on the same chip. Even when not overclocked the SGS can get prettty warm.
Installs nicely, oc ok to, but dont see that much increase in linpack.
Nice work tho.
Any chance to have ext 4 support in next update?
Thanks :
updated to v2
raspdeep said:
updated to v2
Click to expand...
Click to collapse
you're fast, lol. Thanks.
INeedYourHelp said:
your fast, lol. Thanks.
Click to expand...
Click to collapse
update before i go to bed
Guys, how do I use SetCpu?
Was 1.2ghz unstable?
Sent from my SGH-T959 using XDA App
interested in this... Allthough the phone does seem to get hot during heavy use, it doesn't get 'too' hot.
I have seen about 47 degrees celcius max read from battery temp (which seems to be cpu temp on our phones as my battery was stone cold)
Hi any possibility get v1 without mimocan.
Got samset including it nd sgs wnt boot cause of mimocan included.
thanks
I am using JM2. Does this make my phone any faster? Does it maked it lag free?
After tested this oc.. i am bit unsure: i get no performance increase... Is it confirmed that its functional?
First is an O/C kernel that I built from the HTC source. This kernel is stable and with the right profiles setup in setCPU has given me very good battery life. I'm giving coolbho3000 credit here as his post in the G2 forums is what helped me to do this. I am also acknowledging gr8gorilla who helped me several times through this process. Second is a kernel built from the latest CM kernel zource from zinx. It has proven to be very stable (after tweaking the voltages).
Now for the boring part ... If you choose to flash this you do it at your own risk. I am in no way, shape, or form responsible if you flash this and your phone turns into a paperweight. Once again, flash this at your own risk.
There, now that that is out of the way we can get on to the good stuff.
Make sure you choose the right kernel. The stock kernel will break your CM install if you flash it.
Kernels for Stock and Stock based roms
Kernel 2.6.32.21grankin010OC0v0.05
http://t1mgmaps.com/file.php?id=24
Md5Sum: 72c3430177eeefc6ff4b2c658efa0949
Features:
adb root enabled by default
system set r/w at boot (no need to remount)
voltages tweaked
cacheflush hack from zodttd integrated
noatime for better FS performance
Kernel 2.6.32.21grankin01-OC-v0.04
http://t1mgmaps.com/file.php?id=20
Md5Sum: a8668bdb2c1c7ca6ef0d9fbdafbe6969
Features(+v0.03):
Same features as v03 but with different voltages
Kernel 2.6.32.21grankin-OC-v0.03
http://t1mgmaps.com/file.php?id=19
Md5Sum: a82111399a9a4d570def14dce563a073
Features(+v0.01):
Voltages tweaked - Hopefully this one is more stable for you guys.
Kernel 2.6.32.21grankin01-OC-v0.02
http://www.mediafire.com/?o216o3b6jea13f9
Md5Sum: 2fdcde29532339743f0c41daae32db7f
Features(+v0.01):
O/C'd to 1.8Ghz with several intermediate clock speeds
Voltages for 1.7Ghz have been turned up a little bit to address stability concerns
Kernel 2.6.32.21grankin01-OC-v0.01
http://www.mediafire.com/?bqbdgb38m15n789
Md5Sum: af73907d0f9d8fbc1b5dcc41ea6b9552
Features:
Ext4 support (if you want to play with it)
O/C'd to 1.7Ghz with several intermediate clock speeds
ADB has root privileges automatically
System is set R/W on boot (no need to mount anymore)
HTC Perflock is disabled (pre-requisite for over-clocking)
CPU Governors:
Performance
Conservative
OnDemand
UserSpace
PowerSave
Kernels for CyanogenMod and MIUI
Do not use these with CM7-GB. They will not boot properly.
Kernel_grankin01-CM-OC-v0.10
http://t1mgmaps.com/file.php?id=26
Md5Sum: 6c4f5b18ca5509cc83cf5eac0667b3e0
Features:
Same as v09 but video works
Kernel_grankin01-CM-OC-v0.09
http://t1mgmaps.com/file.php?id=25
Md5Sum: 63bcc734bf33cb30eb0dd335f807bf10
Features(+v0.08):
Wifi is fixed in this release
Kernel 2.6.32.27grankin01-CM-OC-v0.08
http://www.mediafire.com/?4hs3ix1b8rdmz36
Md5Sum: 7822eb4dcf547d712c455c72c83d4118
Features:
Noatime for better FS performance
Cacheflush hack by zodttd is integrated
Voltages have been tweaked (again )
Inludes all the standard features also
Kernel 2.6.32.27grankin01-CM-OC-v0.07
http://t1mgmaps.com/file.php?id=18
Md5Sum: 9273d9405e6bdb76f754c96916e36262
Features(+0.06):
System Permanent R/W Fix (edited code in v06 and left that out ... oops)
Video is fixed
Voltages changed (hopefully for better battery life)
Kernel 2.6.32.27grankin01-CM-OC-v0.06
http://t1mgmaps.com/file.php?id=17
Md5Sum: 55f04250126b6763db2f180b2829e4ac
Features(+0.05):
Newest Bluetooth fixes
Newest Video fixes - broken/missing code
System Permanent R/W - Broken (edited code and left that out ... oops)
Kernel 2.6.32.27grankin01-CM-OC-v0.05
http://t1mgmaps.com/file.php?id=16
Md5Sum: 026e5717311fa42da073ac8a9fc442d5
Features(+0.03):
Bluetooth fix
Charge issue fix
Kernel 2.6.32.27grankin01-CM-OC-v0.03
http://www.mediafire.com/?3g6yv8g9ypsu953
Md5Sum: 0424f5565387f86818c1e67ff636443e
Features(+v0.02):
New version of kernel includes fix for video
Kernel 2.6.32.27grankin01-CM-OC-v0.02
http://www.mediafire.com/?jsux5wtj7mgcvzo
Md5Sum: 8c243df7f53143a6a3be5292073f052b
Features:
Ext4 support (if you want to play with it)
O/C'd to 1.8Ghz with several intermediate clock speeds
ADB has root privileges automatically
System is set R/W on boot (no need to mount anymore)FIXED
HTC Perflock is disabled (pre-requisite for over-clocking)
CPU Governors:
Performance
Conservative
OnDemand
UserSpace
PowerSave
Interactive
CM7-Gingerbread Kernels
Do not use these with CM6-Froyo! They have different ramdisks and wifi options built in.
These kernels have no issue with video. If you are having trouble with youtube and such update your GB rom to one of the newest. There was a memory leak in the source for the rom itself that zinx has fixed. Thirty to Forty-Five minutes of straight youtube action and I had no problem at all.
Kernel_2.6.32.27grankin01-CM-GB-OC-v0.09
http://t1mgmaps.com/file.php?id=29
Md5Sum: 7565340ac31ff7560d45ab42e043acc0
Features(+v0.08):
Changed voltages a tad
I get great battery life with light to moderate usage on this kernel
Kernel 2.6.32.27grankin01-CM-OC-v0.08-GB
http://t1mgmaps.com/file.php?id=22
Md5Sum: b7b5fde8db99a01d827c3b7fc81a387e
Features:
Noatime for better FS performance
Cacheflush hack by zodttd is integrated
Ext4 support (if you want to play with it)
O/C'd to 1.8Ghz with several intermediate clock speeds
ADB has root privileges automatically
System is set R/W on boot (no need to mount anymore)
HTC Perflock is disabled (pre-requisite for over-clocking)
CPU Governors:
Performance
Conservative
OnDemand
UserSpace
PowerSave
Interactive
I have packaged this into an update.zip format that you can flash through your custom recovery. Simply choose to install a zip from the sdcard and pick the update package to install it. It will install the wifi driver at the same time so you don't need to worry about that. Everything works with this kernel so far for me if you have any problems please post them and I'll see what I can do to fix them.
Remember that you hardware is not the same as your neighbor's so while he may be able to max the settings out and run stable your device may need to be set to a lower clock speed to run stable.
Source code for both kernels has been added to github. If you want to play around with them download source from here: https://github.com/grankin01
Happy Modding/Devving!
wow, thank you sir
I was just about to start testing kernels with Zinx's CM6 anyway. Looks like yours is first.
hmmm... could not run update.zip through clockworkmod. I was looking to extract the files and push them manually, however, I don't see a zImage file to push.
No luck with the miui rom. Cant get past the splash screen.
Sent from my HTC Glacier using XDA App
monnietron said:
No luck with the miui rom. Cant get past the splash screen.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Yeah, its based off of CM. I'm working on one built fromthe CM source right now.
Christopher3712 said:
I was just about to start testing kernels with Zinx's CM6 anyway. Looks like yours is first.
hmmm... could not run update.zip through clockworkmod. I was looking to extract the files and push them manually, however, I don't see a zImage file to push.
Click to expand...
Click to collapse
There isn't a zimage. I wrapped it all up in its own boot.img and then packaged it in the update.zip with the wifi module.
Does this break the nightly CM ROM? I know gorilla's kernel does.
I appreciate your work!
TmobileDash12 said:
Does this break the nightly CM ROM? I know gorilla's kernel does.
I appreciate your work!
Click to expand...
Click to collapse
Yes, it breaks it horribly. I'm working on it now.
grankin01 said:
Here is an O/C kernel that I built from the HTC source. This kernel is stable and with the right profiles setup in setCPU has given me very good battery life. I'm giving coolbho3000 credit here as his post in the G2 forums is what helped me to do this. I am also acknowledging gr8gorilla who helped me several times through this process.
Click to expand...
Click to collapse
Thanks for this grankin01. Great work to you and the others involved.
So no miui or cm6 on this kernel correct I just dont wanna break anything.
Sent from my icey cold glacier 4g freezing every phone in its path.
jriv said:
So no miui or cm6 on this kernel correct I just dont wanna break anything.
Sent from my icey cold glacier 4g freezing every phone in its path.
Click to expand...
Click to collapse
Not yet. It will work with the rom that you have installed right now though.
hey guys. im a noob to android. every other phone i have had has been winmo. i wanted to try this oc kernel because it seems easier to install than the gorilla one. however i ran into a problem when installing. i have a stock rom 2.2.1, perm rooted s=off, using clockwork recovery. i backed up my rom and flashed via rom manager. it then began to send me into a boot loop never getting past the first screen. just kept turning off and rebooting. soooooo i rebooted directly into clockwork and tried to do it from there and the same thing happened. so i restored my recovery and now everything is back to normal. can anyone point me in the right direction? i did notice that in clockwork it gave me two options to flash the kernel or to flash an update from the sd card. should i have flashed the update zip instead of the kernel or flash both.. sorry im a partial noob. i know how to use adb a lil and the emulator, this is the first thing i flashed on my phone and nearly had a heart attack from thinking i was bricked! any help is appreciated
Do you already have setCPU installed? Not everyone's phone will be able to reach the maximum speed without bootlooping or locking up. Just the nature of the beast. Try setting your speed down in setCPU (if you already have it installed) and turn set at boot off and then flashing and rebooting. Then you can test the speeds one by one to know what is working for you.
Edit: New kernel for CM and MIUI is nearly ready. 1.8Ghz with over 3200 on quadrant!!!
grankin01 said:
Not yet. It will work with the rom that you have installed right now though.
Click to expand...
Click to collapse
Oh I'm running miui now just haven't changed my sig lol
Sent from my icey cold glacier 4g freezing every phone in its path.
Can't wait for your kernel for CM! I wanna see my phone unleash its true power! Lol thanks dude.
Sent from my HTC Glacier using XDA App
grankin01 said:
Do you already have setCPU installed? Not everyone's phone will be able to reach the maximum speed without bootlooping or locking up. Just the nature of the beast. Try setting your speed down in setCPU (if you already have it installed) and turn set at boot off and then flashing and rebooting. Then you can test the speeds one by one to know what is working for you.
Edit: New kernel for CM and MIUI is nearly ready. 1.8Ghz with over 3200 on quadrant!!!
Click to expand...
Click to collapse
thanks.... stupid me... duuhhh.... i have setcpu installed already and it is set at "set on boot".... thanks for the help man... will give it a go and let you know how that works out!
Edit: turning off set on boot in setcpu didnt work. still boot looped. i will try uninstalling setcpu, then flashing, then reinstalling. i dont get it though because my highest on setcpu is the stock 1024.... hmm maybe its the profiles i have set up... either way, gonna give it another go in a few. im gonna get this working today if its the last thing i do. so thankful for backups to restore lol
grankin01 said:
Do you already have setCPU installed? Not everyone's phone will be able to reach the maximum speed without bootlooping or locking up. Just the nature of the beast. Try setting your speed down in setCPU (if you already have it installed) and turn set at boot off and then flashing and rebooting. Then you can test the speeds one by one to know what is working for you.
Edit: New kernel for CM and MIUI is nearly ready. 1.8Ghz with over 3200 on quadrant!!!
Click to expand...
Click to collapse
That's...retarded. I can't wait to see how that handles. lol! Are you incorporating U/V's on the lower frequencies as well?
UV / OC?
Is this a UV / OC kernel? Thanks for the help.
Christopher3712 said:
That's...retarded. I can't wait to see how that handles. lol! Are you incorporating U/V's on the lower frequencies as well?
Click to expand...
Click to collapse
Yes, and O/V's in the higher frequecies for stability. This one was picky.
InvisibleHero said:
Is this a UV / OC kernel? Thanks for the help.
Click to expand...
Click to collapse
Only in the lower frequencies. The higher frequencies weren't stable running lower voltages.
Thanks OP. When you say the lower ranges, at which MHz did you not UV? Just curious. I am thinking of not OC'ing more than 1.4MHz and didnt know if I would get the UV benefit.
*EDIT* Meant GHz
Presenting, my HD2 NAND Android kernel!
Summary
To provide, stable, fast and up to date kernels for our HD2s running either DFT or CWM nand android
Features
- 1190, 1190 Undervolt auto scaling versions available. listed is kernel MAX speed, it will scale to anything less depending on demand and ROM installed. Default max seepd is 998 without the use of an overclocking app
- Faster IO tweak taken from hastarins kernel tree
- Latest YAFFS driver
- Always built from latest source tree
- Very responsive kernel configuration
- Battery efficient
- Supports EXT 2 / 3 / 4, depending our your chosen ROM
- RMNET / PPP both supported, depending on your chosen ROM
- Bluetooth, WiFi, LED notifications all working correctly
- Smartass (default), Interactive and all standard CPU governors supported
- CIFS supported
- MAX defualt speed is 998, use setCPU or similar to overclock if you so wish
- cLK supported
- Automatic Extended Battery Support
Choosing your kernel
1190Mhz
This should work perfectly on nearly every HD2. It offers good speed at a slight cost to battery life. It will, depending on how your chosen ROM implements it, scale anywhere between 245-1190 Mhz depending on load
1190Mhz Undervolt
Same performance as 1190Mhz above, but with lower CPU voltage settings. It will work perfectly on most phones, but not all. If you experience FCs or random reboots then chose one of the aforementioned versions. This kernel offers significant battery life improvements if it works for you.
About the source and GPL compliance
The kernel is built direct from main GIT. You can access the commit logs and sources here on gitorious
The changes and modifications as mentioned in the changelog, and my build .config are all in my separate patch file, which you can download here
Download
All the kernels are supplied on one zip package. Contained within the package are the 2 kernel zImages and the associated modules. Chefs and advanced users will know what to do with these.
Download v11 (files only) --> http://htcfanboys.com/CleanEx/Kernel/DISTRIBUTION KERNELv11.zip
Download CWM ZIPs FOR NON TYPHOON ROMS (*series A*)
http://forum.xda-developers.com/showpost.php?p=11968195&postcount=408
Download CWM ZIPs FOR TYPHOON ROMS / ROMS SHIPPED WITH TYTUNG v6 (*series B*)
these include the wpa_supplicant fix for Wifi / bootlooping
http://forum.xda-developers.com/showpost.php?p=11974837&postcount=471
(the RAM named ones are for typhoon ram build)
Flash under cwm.
Wipe Cache and Dalvik Cache.
~~~~IMPORTANT~~~~
If you are not sure you need the WiFi patch, flash the *series A* kernel. If you find your phone bootlooping / wifi crashing, flash the *series B* kernels
As a backup, the wifi patch remains attached to this post
Changelogs
v11
- Pulled new updates from GIT
- Automatic Extended Battery support
- cLK patches and support built in
- some cleanups
- config changes, more responsive (quadrant wont improve thats IO bound)
v10
- Bug fixes, WiFi should work for everyone without the patch
- Imported the i2c, gsensor, GPU decoupling driver patches to new build tree
- Removed all debugging from kernel (99.9% people dont need it)
- Some build config changes, little more responsive
v9
- Fixed WiFi driver for non GB builds
- Fixed default CPU speed @ 998 max
- Fixed crashes / bootloops / random reboots
v8
- Switch to main branch, import speed mods from previous version
- Fix WiFi for GB / non-GB builds
- config changes for better response times
v7
- Switched to tytungs branch
- Swapped tytungs GB only WiFi driver for main one from primary GIT
- Added CIFS support
- Removed 998 / 1536 speeds
- 1190 Normal is not undervolted and will work for everyone
- 1190 uv is undervolted and might not work for everyone
- Reverted to SLAB, should fix bootlooping
- Other minor config changes
v6
-First public release
Disclaimer
I am not responsible for any damage, loss of data or earnings resulting from the use of my kernels. Users who wish to use an overclock kernel do so on the understanding that running any device outside its normal operating parameters may have damaging consequences
Credits:
Cotulla, Bepe, Hastarin, Tytung, Rafpigna, Markinus and all other kernel source contributors as mentioned on the GIT Commit logs.
Fadzy, JoPlayer, Dave and Jan-Willem for their never ending support, friendship, help and good laughs.
First! This is in a kleandroid 2.55?
yes....and no
its just been recompiled, and i added pure 998mhz for people who have phones that cant take the faster speeds!
Awesome! This is the best kernel, have been using it for like three days and it gives me the best battery life and performance. I loved it. I'll pack this one into cwm zip when I get home and flash it.
Edit: how much does battery life actually improve with the uv one? Now I'm torn between the uv and oc to 1.5ghz. Battery or performance?
Sent from my HD2 running Android on NAND
Can anyone test this on sergio's coredroid 1.4 and post results? I would but dont have my computer for a couple days.
g.lewarne
Please add 998Mhz kernel to next update CleanDroid!
Derek0228 said:
Awesome! This is the best kernel, have been using it for like three days and it gives me the best battery life and performance. I loved it. I'll pack this one into cwm zip when I get home and flash it.
Edit: how much does battery life actually improve with the uv one? Now I'm torn between the uv and oc to 1.5ghz. Battery or performance?
Sent from my HD2 running Android on NAND
Click to expand...
Click to collapse
you might get maybe possible 15% more battery time out of the UV kernel. in ideal circumstances in a perfect world of course
CWM
How to use that? :-(
Any zip to use on cwr?
felipemadox said:
How to use that? :-(
Any zip to use on cwr?
Click to expand...
Click to collapse
Not yet, it is still underway.
I made some cwm zips, before going to sleep. I wasn't able to test them because it's late, but they should work. If g.lewarne wants to post them in the OP, i have no problem. Inside the zip, after you download, there are 4 more zips, one for 998, 1190, 1536(this one doesn't work for me) and 1190 UV. Just flash the one you like and enjoy!
http://www.multiupload.com/DPR3F7TW7J
http://www.mediafire.com/?sqg55hze9evgchb
If you find this useful donate me a click on my thanks button.
Thanks derek.
g.lewarne said:
Thanks derek.
Click to expand...
Click to collapse
Once tested, please update, i will test a rom on it.
raviluke said:
Once tested, please update, i will test a rom on it.
Click to expand...
Click to collapse
I can't test anything now as im off to bed . Its 2am and I did a 14 hour day. Yawn!
report
Derek0228 said:
I made some cwm zips, before going to sleep. I wasn't able to test them because it's late, but they should work. If g.lewarne wants to post them in the OP, i have no problem. Inside the zip, after you download, there are 4 more zips, one for 998, 1190, 1536 and 1190 UV. Just flash the one you like and enjoy!
Please give feedback, again I say, they should work but haven't tested them. I've made all his previous kernel versions cwm zip, and flashed them successfully.
http://www.multiupload.com/DPR3F7TW7J
http://www.mediafire.com/?sqg55hze9evgchb
Click to expand...
Click to collapse
Thank you!
1190Mhz Undervolt its working here.
1536 does not work for ne! Causes random reboot on boot. If you want to test it, do so, but i'm pretty sure it's a problem with the kernel, not with the zip, because the one g.lewarne uses on his rom had 1536 and caused random reboots too, cant be a coincidence . Also, youre welcome!
I flashed the 1190 to test, now off to flash the UV one!
Sent from my HD2 running Android on NAND
raviluke said:
Once tested, please update, i will test a rom on it.
Click to expand...
Click to collapse
It works, but not the 1536 one, or at least not for me.
Sent from my HD2 running Android on NAND
Might I just point out that in real world situations the 1190 kernels are just as fast. 1536 is really just a gimmick but some people want it so there you to. Myself, I run my own personal 1305
Sorry for spamming this thread, but I must ask, is uv dangerous? If so, what are some steps I have to follow to prevent my phone from getting fu'd? Like for example,i know that for the 1536, we shouldn't have it always o/c'd to the 1.5ghz.
Sent from my HD2 running Android on NAND
Derek0228 said:
Sorry for spamming this thread, but I must ask, is uv dangerous? If so, what are some steps I have to follow to prevent my phone from getting fu'd? Like for example,i know that for the 1536, we shouldn't have it always o/c'd to the 1.5ghz.
Sent from my HD2 running Android on NAND
Click to expand...
Click to collapse
Uv Isn't dangerous in the same way, the only problem is possible crash, cpu is safe
Derek0228 said:
I made some cwm zips, before going to sleep. I wasn't able to test them because it's late, but they should work. If g.lewarne wants to post them in the OP, i have no problem. Inside the zip, after you download, there are 4 more zips, one for 998, 1190, 1536(this one doesn't work for me) and 1190 UV. Just flash the one you like and enjoy!
http://www.multiupload.com/DPR3F7TW7J
http://www.mediafire.com/?sqg55hze9evgchb
If you find this useful donate me a click on my thanks button.
Click to expand...
Click to collapse
Installed the UV Kernel on Coredroid v1.4 TMOUS ver its getting stuck at GO GO GO
This is a (lightly) modified, based on stock, kernel for the 1st gen Asus Zenwatch; repacked from the stock boot.img (by replacing zImage).
See the changelog below for changes from stock and between versions.
NOTE: This kernel is only for the MEC23S (Android Wear 1.4) build, and is still experimental. I have not tested this on the newest build (and it's likely not compatible), but I'll probably do a final build for the latest version as a sendoff.
To download the kernel, go to the Downloads tab at the top of the OP, and download the file (version)-ondemand.img.
I can provide a mirror if the DevDB download doesn't work for some people.
I'm not entirely sure what else I can test/add to this kernel (without needing root, since it's not flawless on this watch), so if anyone has some suggestions, I can try adding those things to the kernel, so for now, new builds will come as there are new features to add.
If you want to try out this kernel, I recommend that you try just booting it through fastboot first:
Code:
fastboot boot (version)-ondemand.img
If something goes wrong, I am also including the stock kernel (boot_original.img in the downloads tab).
If you decide that you want to flash the kernel, you need to unlock your bootloader first (it will wipe all your data, so backup first), then run this command:
Code:
fastboot flash boot (version)-ondemand.img
To check if the custom kernel actually loaded, run an ADB shell, and type:
Code:
uname -a
The kernel version number should have "(version)-ondemand" right after it.
Notes:
For now, I am mainly planning to test out features that I can add or modify on the kernel without compromising stability or battery life, and I will also be testing each build on my own Zenwatch.
If there is enough interest, I can try and add custom CPU governors or set a different included one as default, but since there's no way to change the governor without root, I'll need to upload separate kernel images for each new default governor.
Vibration intensity is pretty easy to increase, so if 3100 mV still feels a bit weak, I can try bumping it up a bit more, like to 3150 or 3200 mV (I don't want to risk raising it too much and damage hardware).
Building the kernel doesn't take too long, so if there are any bugs or features to be added, I can compile and upload a new kernel pretty quickly.
XDA:DevDB Information
Custom ZW Kernel, Kernel for the Asus ZenWatch
Contributors
itechnoguy
Source Code: https://github.com/iTechnoguy/zwkernel
Kernel Special Features:
Version Information
Status: Testing
Current Beta Version: v2
Beta Release Date: 2016-04-10
Created 2016-03-30
Last Updated 2016-04-10
Changelog:
v2 - 04-10-2016
Changes:
I/O Scheduler no-op added (and made default; stock kernel default was CFQ)
Compiled with Linaro GCC 4.9
Note: So far, ondemand is one of the only CPU governors other than performance that don't cause the Zenwatch to bootloop (including 3rd party governors), so for now, ondemand will remain the default (a couple of other governors, like interactive remain compiled in, but bootloop when made default)
v1 - 03-29-2016
Changes from stock kernel:
Uses the ondemand governor by default (instead of performance)
Slightly increased vibration strength (measured in mV; increased from 3000 to 3100 mV)
To-Do/Look into:
Implementing CPU (and IO schedulers?) governors without having to create a separate kernel image for each governor, meaning needing systemless root to avoid needing to reflash the system partition before an OTA
Possibly add init.d support so that scripts can change the governor on boot (without needing an app, which would probably be hard to use on the ZW's small screen)
Kernel-level support for disabling the default low-bit ambient mode (since build.prop edits don't work)
If you have the opportunity when you are looking around in there see if there is anything in the kernel that forces low bit ambient. I have tried changing the build.prop to turn it off as you would on other devices and it has not been successful.
hecksagon said:
If you have the opportunity when you are looking around in there see if there is anything in the kernel that forces low bit ambient. I have tried changing the build.prop to turn it off as you would on other devices and it has not been successful.
Click to expand...
Click to collapse
I'll look into it, but from what it looks like so far, it seems that low bit ambient mode isn't a kernel-level feature. I'll keep digging around though, and see if there is something within the kernel that controls it.
Maybe ability to disable 2 cores to increase battery life?
Sent from my SM-G925F using Tapatalk
macia10 said:
Maybe ability to disable 2 cores to increase battery life?
Click to expand...
Click to collapse
I can implement that; it's more of a ramdisk edit (as seen in tiny4579's discontinued kernel for this same watch).
I guess there's also the parameter CONFIG_NR_CPUS to set the max number of CPU cores (like setting maxcpus in the ramdisk), but on a kernel level. I'll take a look and test it out.
I've been testing a couple of builds with reduced cores, and I've been running into issues. Any dual core setup I've tried so far (either by limiting the CPUs within the kernel or just the ramdisk) seems to be unstable, causing the watch to reboot within a couple of minutes of finishing boot. I guess the ramdisk editing worked on a previous kernel/build of Android Wear, but it's causing some sort of instability on Marshmallow now.
I also tested with tri-core builds, but none of those even made it past the boot logo.
I have flashed the kernel and will run it for a few days to see if there is any battery improvment. As far as CPU goes maybe using a hotplugging governor is the way to go? Not sure if there are any modern ones out there but I recall back in the day before hotplugging was done with a stand alone module.
hecksagon said:
I have flashed the kernel and will run it for a few days to see if there is any battery improvment. As far as CPU goes maybe using a hotplugging governor is the way to go? Not sure if there are any modern ones out there but I recall back in the day before hotplugging was done with a stand alone module.
Click to expand...
Click to collapse
I've been watching the CPU usage using AIDA64, and it seems like most of the cores are inactive most of the time, so I think the kernel might already be using Qualcomm's built in hotplug driver.
I might have to add in a separate hotplugging governor, which shouldn't be too much of a problem, since the default CPU governors were just performance, ondemand, userspace, and conservative (interactive is also available, which I may make default next if a hotplug governor doesn't work well).
In terms of battery life, I noticed that ondemand does help increase idle/screen-off battery time, but screen-on time seems to be about the same as when using performance.
get about an extra day with ambient off and tap to wake. I'm at the end of day 2 with ~30% left.
I recall back when we had root that previous versions of the official software ran only single core on performance governor. I think the CPU was limited to like 800 or 1000 MHz too.
Yeah, the default max clock speed is set to roughly 787 MHz, and the minimum (in this kernel version) was at 300 MHz.
I think I may make the next build with interactive instead of ondemand, to see if interactive offers any better battery life, since hotplug governors basically refuse to compile with a newer kernel. I'm also considering making the new default minimum clock speed to 250 MHz (or lower, if it doesn't get unstable).
New build is up (v2), available on the DevDB Downloads tab (full name: v2-ondemand.img). See the second post for changes.
I just realized that my watch updated to Android Wear build MWD48B by itself, which also brings a new kernel (Asus posted the new sources a few days ago). I don't know if there's still interest in a modified kernel, but I can try building a new kernel with the updated sources (which may take a bit since I don't have access to my normal build system).
itechnoguy said:
I just realized that my watch updated to Android Wear build MWD48B by itself, which also brings a new kernel (Asus posted the new sources a few days ago). I don't know if there's still interest in a modified kernel, but I can try building a new kernel with the updated sources (which may take a bit since I don't have access to my normal build system).
Click to expand...
Click to collapse
col you have latest build already.
Partners watch has not recieved the update... But she has twrp and the OPs Kernel flashed so may be thats the reason..
Could someone confirm if going back to stock recovery on kernel will allow the update and proved instructions and downloads to restore them
lohtse said:
col you have latest build already.
Partners watch has not recieved the update... But she has twrp and the OPs Kernel flashed so may be thats the reason..
Could someone confirm if going back to stock recovery on kernel will allow the update and proved instructions and downloads to restore them
Click to expand...
Click to collapse
You'll have to restore the stock recovery to install the OTA update (I made a backup of the stock recovery from the last update here: https://drive.google.com/open?id=0B6eYQrCg9u-bUTA2d3dRdEZBbXM).
In terms of having the custom kernel flashed, I don't think that affects the update, because my Zenwatch stealth updated without me noticing (even though I had the kernel flashed), since I had the stock recovery installed, not TWRP.
I would love continued effort on a kernel but it doesn't look like this device has much life left here at XDA. If you don't personally believe you will benefit from your effort, don't make it for others.
hecksagon said:
I would love continued effort on a kernel but it doesn't look like this device has much life left here at XDA. If you don't personally believe you will benefit from your effort, don't make it for others.
Click to expand...
Click to collapse
I am considering doing one final kernel for this watch (no ETA, because I've been really busy lately), since it's very likely that Wear 1.5 will be the final update, so the kernel won't need updating past that (if it's stable, of course). It might not see much use, but it'll still be here for people that continue to use this watch past its official support life.
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.