Develop Bugs

Stock O/C Kernel 1.7Ghz and CM/MIUI/GB O/C Kernel 1.8Ghz UPDATED 01/09 - Grankin01

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

[KERNEL] [GPL] [4.3] FuguMod kernel (3.0.101) (open, stable, reliable and secure)

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

[MOD] Trickster MOD [2012-07-09]

Introducing Trickster MOD, bringing Trickster experience to virtually every ROM out there.
Users using Trickster ROM 1.2.1 or newer can use this MOD to update
This CWM zip include the binaries and scripts I used for optimization in Trickster ROM. What it can do/set:
- Zipalign and sqlite DB optimization at boot
- Some android properties tweaks with mobile network speed tweak
- Screen state optimization for kernel task scheduler and virtual memory management (ch33kybutt)
- Set I/O scheduler, read ahead buffer, CPU scaling governor, min and max CPU speed
Following features are dependent on kernel features:
- Color (applied by default), contrast and gamma tweaks
- Generic hotplug
- CPU Temp limit
- Minimal SmartReflex voltage of Core, IVA, and MPU domains
- Nominal SmartReflex voltage for Core, IVA, and MPU domains
- Regulator voltages
- GLaDOS live OC of Core, GPU and MPU
- WIFI mode for screen off (power saving or full speed)
- Vibrator strength
- Headset volume boost
- High performance sound
- Force fast charge
- Battery live extender
- Touch wake and touch wake duration
- fsync control
Download
Trickster MOD 20120709
Control App​
Changelogs
Requirements:
- CWM
- Someone who understands instructions below​
Installation/Update instructions:
- Reboot to CWM recovery
- Do a nandroid if you're scared (recommended in case you have problem)
- Install zip from sdcard
- Reboot the phone
- If you see /sdcard/trickster directory with configuration files inside then this mod installed successfully​
Usage:
By default Trickster color, some android property regarding UI smoothness and mobile data speed tweaks and screen state optimization are applied. If you want to change additional settings then either use the app or :
- Go to /sdcard/trickster directory, you'll see at most four following configuration files, depending on kernel features:
. color.conf: color related tweak
. general.conf: generic tweaks like zipalign, sqlite, and screenstate optimization
. kern_general.conf: generic kernel tweaks like CPU speed, governor, IO scheduler and readahead buffer
. kern_specific.conf: specific kernel features like sound control, WIFI power, fast charge...​ - Edit any above file to change the settings you want using app like ES Explorer, Root Explorer..., instructions included inside
- Settings are automatically applied when user saves any of these files
- Some changes require restarting your phone
- To check log to see if it works use "logcat|grep Trickster" from adb/terminal​
Reinstall boot service, Reset settings, Removal instructions:
- If you install a new kernel that includes ramdisk (boot.img format like franco or leanKernel), you can either reinstall Trickster MOD, run "tricks install" from adb root shell or terminal, or apply this CWM zip from recovery.
- You can delete a configuration file, files, or entire /sdcard/trickster directory to reset to default settings for a file, files or all configuration respectively
- If you mess up and can't boot, say aggressive OC/UV , use this CWM zip to reset
- If you want to uninstall, use this CWM zip​
Credits:
- Google
- Our great kernel devs
- chainfire for SuperSU and su
- stericson for busybox
- ch33kybutt's for his brilliant idea on screen state optimizations
- Beta testers for your dedication in testing this
- nexus.prime for his unintallation script
- phone_user for init.d CWM zip
- Anyone I learnt from
Disclaimer: This is provided with NO GUARANTY whatsoever. Use your common sense.
Beta test: If you want to test my stuffs, including other things beside this. Contact me through PM.

First
Thanks for this! Downloading now
Sent from my Galaxy Nexus using XDA

tanner4137 said:
First
Thanks for this! Downloading now
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
DERP!

Looks great! @OP, I remember your contributions in Franco's thread. Will any of these modifications conflict with his setup?
Cheers,

mazubo said:
Looks great! @OP, I remember your contributions in Franco's thread. Will any of these modifications conflict with his setup?
Cheers,
Click to expand...
Click to collapse
No, it won't. This is supposed to be a unification for all the stuffs that one can unite on the GNex. I will try to create an app to do this along side of improving this script in the future.
TBH with the recent CM episode I felt this is needed even more, screw them all. My script or app won't include things that won't work with CM like what they did, I assure you.

bigeyes0x0 said:
No, it won't. This is supposed to be a unification for all the stuffs that one can unite on the GNex. I will try to create an app to do this along side of improving this script in the future.
TBH with the recent CM episode I felt this is needed even more, screw them all. My script or app won't include things that won't work with CM like what they did, I assure you.
Click to expand...
Click to collapse
Awesome, thank you! I'm currently running paranoid android which is cm9 base.
I'll report back!

bigeyes0x0 said:
...
This is supposed to be a unification for all the stuffs that one can unite on the GNex. I will try to create an app to do this along side of improving this script in the future.
...
Click to expand...
Click to collapse
Cooool!
---------- Post added at 02:39 PM ---------- Previous post was at 02:14 PM ----------
Hi bigeyes0x0
Air kernel V1.3 changed many things
http://forum.xda-developers.com/showpost.php?p=26318191&postcount=3

Woooow, Thank you !!

nexus.prime said:
Hi bigeyes0x0
Air kernel V1.3 changed many things
http://forum.xda-developers.com/showpost.php?p=26318191&postcount=3
Click to expand...
Click to collapse
It's fine, the mod is already written in a way that it can handle update like this with ease. If there's actually a new sysfs that isn't exist anywhere else, I will add it if I deem it necessary. If that were not the case I would be in for maintenance hell for every kernel of every dev's update .
r_data said:
Woooow, Thank you !!
Click to expand...
Click to collapse
You're welcome. I actually wanted to get into kernel dev before but it seems like destiny is a ***** and I am stuck with these, as I am not going able to find enough time to care for my ROM, this mod, the app that I wanted to create and a kernel to add to these. Ranting aside, I'm fine with how things are .

Where is trickster.conf?
Don't understand, I installed the zip, but no trickster.conf appeared in /sdcard...

Ok, probably a dumb question,
But can these literally be used on ANY rom?
Or at least any ICS rom?
For example, would this be useful on a moto atrix running ICS? (CM9 based)
There a few ICS roms for the atrix floating around and I just wanna know if I should share this thread with some of the devs over there?
I do have a G-nex that ive been able to play with over the last couple days, and its sweet! If I flash this mod, are there any noticeable changes right off the bat, or just after imputing a command through terminal?
Thanks, and nice job

sperug said:
Don't understand, I installed the zip, but no trickster.conf appeared in /sdcard...
Click to expand...
Click to collapse
Your ROM does not have init.d function, I think
forum.xda-developers.com/showpost.php?p=21232559&postcount=2
Sent from my Galaxy Nexus

Will this work without a custom rom, 4.04 boot unlocked with root and custom kernel?
Sent from my BlackBerry 9700 using Tapatalk

ATRIXXIRTA said:
Ok, probably a dumb question,
But can these literally be used on ANY rom?
Or at least any ICS rom?
For example, would this be useful on a moto atrix running ICS? (CM9 based)
There a few ICS roms for the atrix floating around and I just wanna know if I should share this thread with some of the devs over there?
I do have a G-nex that ive been able to play with over the last couple days, and its sweet! If I flash this mod, are there any noticeable changes right off the bat, or just after imputing a command through terminal?
Thanks, and nice job
Click to expand...
Click to collapse
Theoretically, it should work anywhere with an ARMv7 CPU and Android 2.3 or higher but this has been tested only on GNex varieties by me and my testers. Still as I wrote this for GNex kernels, this script of course can't change kernel features that this script does not have. Basically I think it should work but with limited functionality, to be sure just nandroid first before applying it. Still I do not support this in anyway so don't come crying to me later if anything happens and I won't answer question regarding this script and other devices further. I do believe it has some values for any device out there, but it needs ppl with some knowledge to tweak it.
EVERED78 said:
Will this work without a custom rom, 4.04 boot unlocked with root and custom kernel?
Sent from my BlackBerry 9700 using Tapatalk
Click to expand...
Click to collapse
Yeah, it should.
nexus.prime said:
Your ROM does not have init.d function, I think
forum.xda-developers.com/showpost.php?p=21232559&postcount=2
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Thanks for this, I will add this info in the first post.

any pics?

There's no pic for this, it's for tweaking and enhance ROM usability, battery life and performance.

ds4 said:
any pics?
Click to expand...
Click to collapse
Rotflmao. Apparently some people have alot to learn.
Sent from my i9250 (GSM) Galaxy Nexus

Anyone tried it on AOKP b37? Any noticeable improvement?

eRajesh said:
Anyone tried it on AOKP b37? Any noticeable improvement?
Click to expand...
Click to collapse
Don't work for me... Lost navbar and notification bar..
Sent from my Galaxy Nexus using XDA

Works lovely on Liquid 1.4
Sent from my i9250 (GSM) Galaxy Nexus

[Base 1.80][Root][SCRIPT] 08/07 Butterfly V12/Ghostpepper Inspired Interactive Values

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.

4/19/2017 [] 7.1.1 UPDATE [] HTC 10 (msm 8996) [] CPU, VM, RAM, IO "Tune"

ORIGINAL THREAD HERE: https://forum.xda-developers.com/axon-7/development/2-15-2017-axon-7-msm-8996-cpu-vm-ram-t3557392
This mod was originally created for the Axon 7, but due to several requests, I've modified a version for the HTC 10, please see below, and post questions or comments in the original thread above. Please state you are a HTC 10 user if you have feedback in that thread, to consolidate user feedback and speed up response time.
Custom tuning for a device is always a necessity. "Canned" settings will get you by, but they are certainly never optimized for a specific device. In fact, Linux typically takes a general approach to find harmonic balance in default settings that will, for the most part, work in an acceptable manner for just about any device. There are a lot of resources available on this device, so we should utilize it in a manner appropriate to squeeze out as much battery life and performance as possible without sacrificing much of those outputs, don't you think? This is going to fix that for you.
Here is what is required of you before you begin:
1. Must be rooted
2. Must have the HTC 10 OR a device running the Snapdragon 820, as this modification is not so much device specific, but hardware specific. The important aspect being the snapdragon 820 and the RAM disk size.
3. Must have write protection disabled. If the HTC 10 requires write protection to be disabled, see the code and instruction below:
Using adb shell:
Code:
adb reboot disemmcwp
Using Linux terminal (from your phone, for example):
Code:
reboot disemmcwp
Let's begin.
Getting right to it, here's what I've done:
- modified parameters of the interactive governor, and quite extensively at that (search some of my threads if you want a little bit of a breakdown of the general approach I take)
- reconfigured input_boost parameters
- reconfigured vm parameters (again, the device has a lot of RAM resource, this will utilize it and give you a far better user experience. Basically, I've adjusted dirty_ratio, dirty_background_ratio, swappiness, and other parameters of the virtual machine.)
- disabled zRAM for 6 GB variants (RAM compression, again, not needed on this device really, this mod will save you CPU cycles and power) this will not apply to HTC 10 users, you will still have zRAM enabled.
- remapped minfree parameters for LMK (low memory killer) again only for 6 GB variants
- Tuned CFQ scheduler for flash storage devices
- Tuned "core_ctl" module (needs kernel support, I recommend freeza's latest version of BeastMode. For those wondering, yes, you can still use this mod with the stock kernel. It won't break anything.) again this will only apply to devices that support core_ctl at the kernel.
In a nutshell, that's what we're looking at here. I can guarantee you this will have a significantly positive impact on your device. Turbo time, homies.
How to install????
Easy. First, the file we are replacing is found in /system/etc... it is the "init.qcom.post_boot.sh" file - this file is basically shell scripts, which are applied at boot via this particular shell file.
All you have to do is download the file to your device, open up a file explorer (must have root capability), navigate to the /system/etc folder with said file explorer, mount your /system as RW (read write), delete your stock "init.qcom.post_boot.sh" file, and replace it with mine.
After you've successfully done this, change the new file's permissions to rw-r--r-- (0644), and then reboot!
Or, if you are brave, you can do it manually via a terminal app and get your fingers wet... if you choose to do that, see below:
Make sure the file is located on the root of your internal sdcard in /sdcard, open your terminal app (again, must have root) and type the following commands, hitting enter after each one (be careful to pay attention to the spacing).
Code:
su
Code:
cd /
Code:
mount -o remount,rw /system
Code:
cd /system/etc
Code:
rm init.qcom.post_boot.sh
Code:
cd /sdcard
Code:
mv init.qcom.post_boot.sh /system/etc
Code:
chmod 0644 /system/etc/init.qcom.post_boot.sh
I don't want credit, don't need you to give or offer donations, this is purely for the community in the spirit of Linux ideology. All I ask is for you to hit the thanks button :good:
That's pretty much it, guys. Enjoy!
DOWNLOAD

warBeard_actual said:
ORIGINAL THREAD HERE: https://forum.xda-developers.com/axon-7/development/2-15-2017-axon-7-msm-8996-cpu-vm-ram-t3557392
Hello everyone, I would like to provide this mod to the HTC 10. If somebody could grab me the STOCK file: init.qcom.post_boot.sh found in /system/etc I will modify it for you guys and post it here with instructions on how to install.
It will provide you a good boost in battery life without sacrificing performance.
Thanks!
Click to expand...
Click to collapse
Thanksss :angel:

I little bit more tuning can't be wrong I guess. Here you go. Just uploaded the respective file needed to do the trick.

5m4r7ph0n36uru said:
I little bit more tuning can't be wrong I guess. Here you go. Just uploaded the respective file needed to do the trick.
Click to expand...
Click to collapse
I'll have this done tomorrow night. Thanks for getting me the file

Hey guys, file is up, with instruction on how to install.
There were actually a lot of typos in the stock file from HTC
I cleaned up the file from redundancy, fixed a few things while adding my modifications to the file. For those wondering, YES the file is supposed to much smaller as a lot of unneeded code was removed that was specific for other SoC's.
Enjoy, feedback is welcome, but I can guarantee your experience will be postive results.

Phone booted, will be testing over the next few days

warBeard_actual said:
Hey guys, file is up, with instruction on how to install.
There were actually a lot of typos in the stock file from HTC
I cleaned up the file from redundancy, fixed a few things while adding my modifications to the file. For those wondering, YES the file is supposed to much smaller as a lot of unneeded code was removed that was specific for other SoC's.
Enjoy, feedback is welcome, but I can guarantee your experience will be postive results.
Click to expand...
Click to collapse
"The file we are replacing is found in /system/etc... it is the "init.qcom.post_boot.sh" file - this file is basically shell scripts, which are applied at boot via this particular shell file" - I could not find this file in /system/etc... Does the type of rom that I'm running matter. currently running ResurrectionRemix 5.8.3 (7.1.2) w/ tabp0le kernel

5m4r7ph0n36uru said:
I little bit more tuning can't be wrong I guess. Here you go. Just uploaded the respective file needed to do the trick.
Click to expand...
Click to collapse
Aloha,
Just to be clear.. So if I download this zip and flash through TWRP I will be on 7.1? I'm currently on stock with Majestic.
Mahalo
Sent from my HTC 10 using XDA-Developers Legacy app

devilman30 said:
Aloha,
Just to be clear.. So if I download this zip and flash through TWRP I will be on 7.1? I'm currently on stock with Majestic.
Mahalo
Sent from my HTC 10 using XDA-Developers Legacy app
Click to expand...
Click to collapse
No
Read the OP

Mike Grace said:
"The file we are replacing is found in /system/etc... it is the "init.qcom.post_boot.sh" file - this file is basically shell scripts, which are applied at boot via this particular shell file" - I could not find this file in /system/etc... Does the type of rom that I'm running matter. currently running ResurrectionRemix 5.8.3 (7.1.2) w/ tabp0le kernel
Click to expand...
Click to collapse
Well, I should have probably told you that CM-based ROMs don't have this file. Lol.
If you are an experienced user, you can add this to init.d

Using this without any problems, on top of ex kernel modifications and using PNP tweak v23. Do all of these play nicely together?
Sent from my HTC 10 using XDA-Developers Legacy app

warBeard_actual said:
Well, I should have probably told you that CM-based ROMs don't have this file. Lol.
If you are an experienced user, you can add this to init.d
Click to expand...
Click to collapse
I'm not an "experienced user" per-say but basically we take your edited init.qcom.post_boot.sh file and move into init.d (I'm on LOS ROM) folder and re-name and set permissions correctly?
I have re-named to 01init.qcom.post_boot
I'll upload a screenshot shortly to show what I have done.
Also, will it matter the kernel and write protection?
I'm assuming that I don't need to bother with it since I was able to move and edit this file?

MrRob0t said:
I'm not an "experienced user" per-say but basically we take your edited init.qcom.post_boot.sh file and move into init.d (I'm on LOS ROM) folder and re-name and set permissions correctly?
I have re-named to 01init.qcom.post_boot
I'll upload a screenshot shortly to show what I have done.
Also, will it matter the kernel and write protection?
I'm assuming that I don't need to bother with it since I was able to move and edit this file?
Click to expand...
Click to collapse
Yep, should be good. Make sure you leave your original stock file in /system/etc however... and line out any conflicting code in that stock file.
init.d loads during boot, as opposed to post boot, so any conflicting code with be overwritten after the .sh file executes (around the time you start seeing your lock screen)

warBeard_actual said:
Yep, should be good. Make sure you leave your original stock file in /system/etc however... and line out any conflicting code in that stock file.
init.d loads during boot, as opposed to post boot, so any conflicting code with be overwritten after the .sh file executes (around the time you start seeing your lock screen)
Click to expand...
Click to collapse
Original stock file. Does that mean the file that you edited or do i need to put the original file that was not edited. Using los based rom so original doesn't exist. Thank you

Mike Grace said:
Original stock file. Does that mean the file that you edited or do i need to put the original file that was not edited. Using los based rom so original doesn't exist. Thank you
Click to expand...
Click to collapse
Using LOS, you're good to go, as the file doesn't exist in /system/etc
Toss it in /system/etc/init.d and remove the .sh extension, good to go.

Delete