Database Develop

Remove Ram Hack

Hi,
Do you know if there any way to remove ram hack?
As far as i understood the ram hack is in the image file boot.img.
So I tried to remove it flashing the boot with original htc boot.img, but it did not worked.
Thanks for your futures answers.
Bye
Herc. 8)

get the right version rom update and extract the boot.img from the zip.
then
flash_image boot /path.to/filename.img
Or you could restore the backup I know you made before flashing the intial ram hack

Hi,
I think there is a misunderstanding.I'm using a dwang 1.13 and I would like to remove the RAM Hack
Bye
Herc. 8)

I looked thru Dwang's change log for his ROM and do not see that he implemented a RAM hack to his boot image. This would lead me to believe that you are running one of Wes Garner's modded ROMs from Dwang.
If that is the case, you can just update from the 1.13 to the current Dwang rom, which won't have the RAM hack. Or, you could find a copy of the 1.13 Dwang ROM and flash that. And just like @vixsandlee said, just extract the boot.img from that rom and flash that.
Or as a diffferent approach, you could restore your nandroid backup from before the RAM hack was added.
If I have misunderstood your situation, please let me know and we can work towards as resolution.

Hi,
I guessed you well understood what I want to do but according to Dwang post I think the Ram Hack is present:
[ROM][32B/Dream][Dec23][Dwang][Donut][Speed and Stability][v1.17.1]
This ROM is completely 1.6 stock (framework, apps, etc) with the exception of the following enhancements:
1. Compcache enabled by default (no backing swap, just straight compcache)
2. Memory hack which gives you 107.5 megs of linux system memory
3. ROM works with both mt3g (32b) and g1 (dream).
4. Root enabled
5. Market should be fully working
6. Busybox
7. Loccy's enhanced Browser v1.5 with MT
8. Netfilter and iptables modules added to the kernel. Wifi tethering works with both "aNetShare" and "android-wifi-tether" apps.
9. Launcher with 5 screens
10. Apps2SD for G1/Dream users ext2/ext3 fs only [may need to format /system/sd (/dev/block/mmcblk0p2) partition if getting black screen]
11. Work Email App (Exchange Support)
12. Userinit.sh support in /sdcard directory
13. All built-in apps optimized with zipalign and optipng
14. Wired usb tethering support. Download this app to enable http://code.google.com/p/android-wired-tether/
15. Deadline IO Scheduler
Caveats:
* Because of the RAM Hack, 3d games will run slow!
* Does not support ext4 partition
Click to expand...
Click to collapse
So If know which boot image to use without this ram hack I'm your man
Bye
Herc.8)

Hercule,
That feature set is for V1.17, you said you were on 1.13. I can't tell where the RAM Hack was added (in the beginning or added later).
I think a PM to @Dwang asking if he has a regular CFS boot image for his rom available. Or if he can tell you if there is a certain build where the RAM hack was added.

Hi Qman,
I can tell you this feature was already implemented in 1.13.
I"ll follow your advice and ask Dwang about the original boot.img
Cheers
Herc.

[ROM]Onyx R4.2 - Froyo - No TouchWiz - Team Whiskey - *11/18/10*

Onyx is simply a TouchWiz Free version of Obsidian. The changelog is listed there, in addition to those changes the following have been made.
Will make flashable nonwiping updates available until all the bugs are worked out and cleared. Once they are the newer and stable revision will be posted with complete skinning in two seperate versions. Please make requests for feature changes and things you would like removed.
4.2
- Added inharent support for Backlight Notification compatible kernels (BLN)
- Optimized Build Prop with ROM Identification Added
- Streamlined Frameworks
- Numerous Corrected Images
- Return of TouchWiz MMS w/ Blurry mms Fix
- Integrated WirelessADB
- Additional I/O scheduler, VM management, kernel scheduler, and minfree edits via sombionixInit script
- Integrated Flashing with Universal Lag Fix system. (Source by sztupy @ XDA, Ported by Krylon360 @ TeamWhiskey)
Team Whiskey Universal LagFix Kernel Features
- All lagfixes and tweaks activated directly within clockwork advanced menu
- MULTIPLE lagfix options, new and old
- Integrated TW logo
- 3e recovery built into kernel
- No longer required to disable lagfixes before flashing
- Enable/disable back light notifications
- Option to switch to 2e recovery
- Option to install Superuser
- Enable/disable I/O scheduler tweaks
- Enable/disable VM management tweaks
- Enable/disable kernel scheduler tweaks
- Enable/disable misc. tweaks
- Reboot into download mode
How To Utilize Universal LagFix Kernel:
1. Flash ROM as you normally would via clockwork recovery
2. Let device boot and then reboot back into clockwork recovery
3. Once in recovery, you will now see 2 new options at the bottom
4. Within the new menus, you will find options to enable/disable certain features and an assortment of lagfixes
5. Enabling/disabling features and tweaks are fairly self explanatory, so have fun with those.
6. Lagfixes are also fairly simple, however, if you are not extremely familiar with them, I suggest sticking to what you know such as the OCLF or voodoo options
7. Once you select the lagfix you want, you will see that your current configuration is updated. You must then go back and select reboot.
8. It will kick you back into clockwork very quickly and give you options before converting your partitions to your selected lagfix. I suggest you pick the first one which creates a backup and restore of your system.
9. Your device will now convert your partition, reboot your phone, and you're done!
Known Issues:
PLEASE READ PLEASE READ PLEASE READ PLEASE READ
- Currently, there is a VERY small percentage of users who have reported that their internal sd partition has been wiped. This is happening to roughly 1/20 people who flash 4.2 with the universal lag fix. If this happens, you will have to odin back to JFD and then upgrade back to 4.2 or any version of your choice. The kernel works very well, however, this is the first time this source and recovery modding has been ported to the Vibrant. None of my dev team has had this happen to any of us so we unfortunately cannot reproduce the problem and pinpoint the problem. We are thinking its hardware related at the moment. Please flash this at your own risk. If it does work for you, you'll love it, trust me! If you're one of the unfortunate ones that gets your internal wiped, well, I apologize, but you've been warned. I suggest ONLY experienced users download the rom with the ULF included. All others should download 4.2 w/stock kernel. THIS IS A KERNEL RELATED ISSUE, NOT ROM RELATED!
Update:
For those VERY VERY few unfortunate people who get their internal sdcard partition wiped, we have confirmation that using odin, going back to JFD, then back to Obsidian/Onyx 4.2 works fine. Everyone that has done this has had no further issues regarding the wipe issue.
3.1
-Even MORE framework edits
-tamed dragons
-now prints money
3.0
-Additional Framework Edits
-Beginning of a complete graphical overhaul
-Reskinned DialerTab Functions
2.2
-Fixes Mounting
2.1
-Corrected several improper strings
-Repaired twframework and framework
-removed power menu
R2.1 fixes a few issues, random dropping into airplane mode, crash when using the power button, repeat mms notifications, and more.
2.0
-TouchWiz Disabled and removed
-Standard LauncherPro installation w/ Fusion Skinning
-Reskinned to include Onyx button bar and status bar
All the other changes that were listed in R1 in beta were combined with Obsidian to make one big pile of awesome.
Reverting back to previous iteration, it was running clean and bugfree. Does not have the same stability previous Rev did. Took those peices and reintegrated into R2+
Removed some edits, much more stable now. I KNOW How you hate flashing updates, I promise I will try to make this the last major flashing update for a very long time. Its stable and perfect as far as I can see other than the known mounting issue. Enjoy!
Additional Option Flashes:
If you REALLY like the samsung apps I removed flash this - http://teamwhiskey.com/bin/onyx/FlashPa ... gExtra.zip
If you REALLY liked the WiFi calling and need it back, even if it slows your phone down, constantly, even in the background - http://teamwhiskey.com/bin/onyx/FlashPa ... alling.zip
OCLF/Voodoo Displaced, not removed.
To enable your new box of awesome, you will first need to reboot back into recovery. You will notice this is slightly different from your standard recovery. I will keep this as brief as I can and to the point. You can do any combination you want of lagfix, from simple bind to overkill mode and replace the entire FS to JFS + EXT2 Binds. This is totally at your discretion.
Personally, I enabled EVERYTHING and activated the most OVERKILL mode I could, because I like things over the top lol.
Its fast, wicked fast, its like fast took meth and kicked not so fast in the face in a single springboard motion to be faster.
Reboot to Recovery
Go to the Advanced menu below CWM
Set tweaks and options as you want to, I turned on Backlight Notifications and all the tweaks personally
After that, go to the LAGFIX section and shop for your weapon of choice, pick whichever you want. (Understand that converting data is a dragon in disguise, like a shoplifter in a cage inside an ATM that he COULD BREAK FREE from. Use at your own discretion.)
Reboot
Allow it to convert, could take a long time. Get a snack. Watch Hulu.
Once it boots, its done, reboot after about 15 or 20 for good measure and extra flavor.
Restore your data, dont restore EVERYTHING from Titanium Backup if youre coming from an Eclair build, single select restore your apps and their data. Otherwise Titanium Backup tries to make you some Froyeclair in a blender.
Backlight notifications are awesome, use them.
IF YOU ARE A BATTERY MONGER AND HATE IF YOUR BATTERY DOESNT LAST FOURTYSEVENTYTEEN Hours. Flash the stock kernel, otherwise you will get an average of 10-14 hours with this kernel.
Download:
Onyx 4.2 w/stock kernel
ULF Removed for Stability Issues in flashing
If you are one of the ones that had serious issues with ULF properly flashing we are very sorry that you are having those issues. We have pulled the ULF kernel due to its inconsistant flashing and are moving forwards with a few different concepts. If you are still having issues with this kernel and going back to normal please visit Sombionix or Viralblack in the TeamWhiskey IRC channel.
NEW internal/external mounting fix - after flashing, reboot phone and computer
Download Rom Extras:
Rom Extras

Thank you, this Rom rocks!!!!
Question: The USB debug mode enables itself everything the phone reboots. Is it supposed to be this way?
Thanks again for a awesome rom

Wait 10-14 hours of battery with this kernel? i know the features are awesome but that seems pretty bad. is that 10-14 hours with normal use or just chilling? cause moderate to heavy use and 12 hours doesnt seem so bad.

Awesome rom. Love it as usual.
I was one of the unfortune that got their SD wiped, but I made a bakup.
I flashed froyo via Odin, then reflashed Onyx v4. Works like awesome sause.

Not sure what caused this, Onyx or the overkill JS lagfix, but when I mount my internal/external sd card, the external shows up as a cdrom drive. The internal one is fine.

Can you please make a version with stock kernel
Sent from my SGH-T959 using XDA App

theres a version for stock on the TW website. It was there when i downloaded this at 803 am EST
whats up with this new stuff? i selected the very bottom option in the tweaks for the JS overkill? is this JFS thing the new hotness? i dunno which to pick. i want this thing to be as epicly cracked out as i can make it. can you doo voodoo WITH this new thing or is it one or the other?
right now im sitting at 1406 quadrant and all i did was select that option

aeok18109 said:
theres a version for stock on the TW website. It was there when i downloaded this at 803 am EST
Click to expand...
Click to collapse
Correct, their website shows:
"SECOND FLASHABLE STOCK KERNEL, use if you dont want to risk dragons."

aeok18109 said:
theres a version for stock on the TW website. It was there when i downloaded this at 803 am EST
whats up with this new stuff? i selected the very bottom option in the tweaks for the JS overkill? is this JFS thing the new hotness? i dunno which to pick. i want this thing to be as epicly cracked out as i can make it. can you doo voodoo WITH this new thing or is it one or the other?
right now im sitting at 1406 quadrant and all i did was select that option
Click to expand...
Click to collapse
W/ voodoo it's either one or the other.
JFS = Journaled File System or JFS is a 64-bit journaling filesystem created by IBM.
RFS = Remote file sharing - essentially this is what Samsung originally went with and it's slow.
Viralblack said:
OCLF/Voodoo Displaced, not removed.
To enable your new box of awesome, you will first need to reboot back into recovery. You will notice this is slightly different from your standard recovery. I will keep this as brief as I can and to the point. You can do any combination you want of lagfix, from simple bind to overkill mode and replace the entire FS to JFS + EXT2 Binds. This is totally at your discretion.
Personally, I enabled EVERYTHING and activated the most OVERKILL mode I could, because I like things over the top lol.
Its fast, wicked fast, its like fast took meth and kicked not so fast in the face in a single springboard motion to be faster.
Click to expand...
Click to collapse
Quadrant scores aren't everything, if it feels fast, looks fast. It's fast.

oh yea i know. i personally could give a rats dong about Quadrant scores. This thing is pretty fast. i just posted it for reference. you know SOMEONE is gonna ask lol

Awesome, this is legit, had It since yesterday!
Sent from the speed demon

Okay, I was running the Macnut ROM (Eugene's ROM) and, having tried Onyx from the first beta, I decided to go back. I installed from CWM with no issues (no Internal SD wipe, etc.), let it sit for a bit then went into recovery to do the ULF. I didn't know what to choose but, I ain't afraid o' no ****in' dragons so, I chose the bottom most option for the works. After letting it sit for about 15 mins again and a Titanium restore of my apps, this thing screams. After a fresh reboot, I got 1852 on Quadrant and there is absolutely no lag on this thing. NONE. The only slight beef I have with this rom is that I miss the completely black Swype keyboard.

Stock Kernel
I am aware of the stock kernel on the TW forum, but it says both the R4 zip and the Stock Kernel zip need to be flashed "at the SAME TIME"
How do I flash two *.zip files at the "same time"?
Thanks.

1. How do you use the WirelessADB??
2. What is Backlight Notifications?

miikey_ said:
I am aware of the stock kernel on the TW forum, but it says both the R4 zip and the Stock Kernel zip need to be flashed "at the SAME TIME"
How do I flash two *.zip files at the "same time"?
Thanks.
Click to expand...
Click to collapse
it means flash the R4 zip in CWM, then flash the stock kernel in CWM WITHOUT REBOOTING IN BETWEEN.
fearless1964 said:
1. How do you use the WirelessADB??
2. What is Backlight Notifications?
Click to expand...
Click to collapse
it makes the 4 android keys at the bottom light up when you have notifications... awesome for those of us who came from phones like the Nexus One that had a notification LED and miss it like woah

miikey_ said:
I am aware of the stock kernel on the TW forum, but it says both the R4 zip and the Stock Kernel zip need to be flashed "at the SAME TIME"
How do I flash two *.zip files at the "same time"?
Thanks.
Click to expand...
Click to collapse
flash one, then flash the kernel right after before rebooting into the rom for the first time. My issue is the stock kernel dl link is dead =\

miikey_ said:
I am aware of the stock kernel on the TW forum, but it says both the R4 zip and the Stock Kernel zip need to be flashed "at the SAME TIME"
How do I flash two *.zip files at the "same time"?
Thanks.
Click to expand...
Click to collapse
flash the R4 zip then flash the stock kernel without booting the device in between

rsfaze said:
flash one, then flash the kernel right after before rebooting into the rom for the first time. My issue is the stock kernel dl link is dead =\
Click to expand...
Click to collapse
Here it is. One stock Kernel, enjoy.

how do u use WirelessADB???

fearless1964 said:
how do u use WirelessADB???
Click to expand...
Click to collapse
ADB functions without a wire (USB cable)

[KERNEL] Nexus S Trinity Max 1.1/Vmax 1.2 Kernel - 2/10/2011

Trinity Max is a Kernel for Nexus S running conservative core voltages at each OC level.
Trinity Vmax only differs in extended voltages at each OC level.
I recommend Max, Vmax is if you want to see if you can squeeze out just that last ounce of clock speed and are comfortable with the higher core coltages.
Perfectly fine to use setcpu including screen off profiles below 800MHz. Thanks to coolbho3k's patch that fixes the policies during suspend/sleep and restores the previous on resume.
This is for.Android 2.3.2.or below.
What you get:
Safe Boot to 1.0GHz.
OC Levels of 1.2GHz, 1.3GHz, 1.4GHz, 1.5GHz, 1.6GHz
1000HZ
Voodoo-Sound (Thanks Supercurio)
Low-Freq Sleep Fix (Thanks Coolbho3k)
Build optimizations
Build system tweaks
Ext4 mount fix (aka. Turbo Boost)
Click to expand...
Click to collapse
Trinity-Max-CM7-1.1
Trinity-Max-Bionix-1.1
Trinity-Max-StockRom-1.1
Vmax:
Safe Boot to 1.0GHz.
OC Levels of 1.2GHz, 1.3GHz, 1.4GHz, 1.5GHz, 1.6GHz
Higher Voltages than the Max series Kernels
1000HZ
Voodoo-Sound (Thanks Supercurio)
Low-Freq Sleep Fix (Thanks Coolbho3k)
Build optimizations
Build system tweaks
Ext4 mount fix (aka. Turbo Boost)
Click to expand...
Click to collapse
Trinity-Vmax-CM7-1.2
Trinity-Vmax-cm7-v1.1
Trinity-Vmax-bionix-v1.1
Stock:
Stock Frequencies and Voltages
BFS (Thanks Con Kolivas)
1000HZ
Voodoo-Sound (Thanks Supercurio)
Low-Freq Sleep Fix (Thanks Coolbho3k)
Build optimizations
Build system tweaks
Click to expand...
Click to collapse
Kernel for Stock Roms
Kernel for cm7
Kernel for Bionix NS
Experimental UV Big Bore kernel available: Trinity-UV-108BB-Experimental
------------------------------------------------------------------
BT Trouble? Not in this house!
method of assurance: (lost track who said it first, it's in this thread, thanks)
- switch wifi OFF, switch BT OFF
- update kernel
- FIRST: on reboot switch BT ON
- THEN switch WiFi ON

Can we get an Update.zip ?
and maybe for MoDaCo?
i know youve been waiting for these questions ^^

RinTinTigger said:
Can we get an Update.zip ?
and maybe for MoDaCo?
i know youve been waiting for these questions ^^
Click to expand...
Click to collapse
Yes, you can, later.
Copy/paste on modaco? i could. always forget that nice place for some reason.

Thanks for creating flash zip later.
And i ment a working kernel for the MoDaCo custom rom r3 ^^

RinTinTigger said:
Thanks for creating flash zip later.
And i ment a working kernel for the MoDaCo custom rom r3 ^^
Click to expand...
Click to collapse
What does it need in init.rc to work?
If it does nothing special, it would work anyways, and if it does special stuff, link me to the initrd they use and i can build one with that.
I Will push the modified source to github once i am done, then they can take care of that if i don't before then.

Cool!
Any chance you could post your patches?

here is boot.img. i put the .ko in /system/modules in the ramdisk folder and compiled but still error for wifi. im sure i did it wrong. anyways, its a bootable/flashable img. my phone boots off it.
Code:
fastboot boot oc.img

k0mpresd said:
here is boot.img. i put the .ko in /system/modules in the ramdisk folder and compiled but still error for wifi. im sure i did it wrong. anyways, its a bootable/flashable img. my phone boots off it.
Code:
fastboot boot oc.img
Click to expand...
Click to collapse
Also contains the ext4 optimizations? /hope
I feel the need, the need for speed!
EDIT: And is this only for the stock kernel, or will it work on CM7?

yes, has ext4 mod.

Not booting on MoDaCo r3 :/

So basically just push the .ko and boot the zImage in fastboot?
What is the purpose of the line that's being added to the build.prop?

mortzz said:
So basically just push the .ko and boot the zImage in fastboot?
What is the purpose of the line that's being added to the build.prop?
Click to expand...
Click to collapse
That's all it is.
You can run neocore without it and if you don't hit 65fps, it's still needed.
On the vibrant it still limits the results even if kernel is capable of more.
Why 68? It's what quadrant reports for refresh, and no need to go above that.

k0mpresd said:
here is boot.img. i put the .ko in /system/modules in the ramdisk folder and compiled but still error for wifi. im sure i did it wrong. anyways, its a bootable/flashable img. my phone boots off it.
Code:
fastboot boot oc.img
Click to expand...
Click to collapse
Put the module into system/modules/ inside the update.zip's skeleton
copying SYSTEM, I can modify it to do that if needed.
Now I wonder if mkbootimg actually likes me or not. I wasted so much time on mkbootimg in the beginning, I'm simply staying clear of it right now..
haha, now I get it, not a update.zip
you'd have to modify init.rc to copy it over, which I might add to reduce the number of steps needed
Btw, I'll add /data mount options next time, I tried them after I built this.
Quadrant advanced shows a nice difference obviously, I'll include it in the way shown on the ext4 thread.
Torn between tweaking this more and first flashing somb's alpha rom and trying this with it.

Mine locks up whenever I run Neocore. I guess my phone isn't stable

success!
here is bootable boot.img that will install correct bcm4329.ko and build.prop.
test:
Code:
fastboot boot oc_final.img
or flash:
Code:
fastboot flash boot oc_final.img
edit: whoops, typo.

mortzz said:
Mine locks up whenever I run Neocore. I guess my phone isn't stable
Click to expand...
Click to collapse
Neocore was always my problem child with froyo kernel, I was overjoyed running multiple runs without issues.
This is only a first version, we can push voltages later. And make this available for more phones.

DebauchedSloth said:
Cool!
Any chance you could post your patches?
Click to expand...
Click to collapse
I said I'll push it to github when I'm done.
Right now I just need feedback to get a better idea about reliability.

morfic said:
Neocore was always my problem child with froyo kernel, I was overjoyed running multiple runs without issues.
This is only a first version, we can push voltages later. And make this available for more phones.
Click to expand...
Click to collapse
Yeah, it locks up in nenamark and playing 3D heavy games too.
Awesome, thanks! I'd be disappointed if my phone couldn't take a mild overclock.

this should be a one-click install to install your zimage with correct files.
download, extract, run overclock.bat. only for windows.

k0mpresd said:
success!
here is bootable boot.img that will install correct bcm4329.ko and build.prop.
test:
Code:
fastboot boot oc_final.img
or flash:
Code:
fastboot flash boot oc_final.img
edit: whoops, typo.
Click to expand...
Click to collapse
This only for stock rom? CM7?

[Q] CM7 Kernel building question

Okay here it goes:
I'm planning on building my own kernel from the lge-sniper-kernel. Basically, what I want to add is just InteractiveX as the default governor for better battery life. I read a lot on the topic and I'm well able to build and inject the kernel. My plans are based on this guide by knzo (dated 4th November 2011): h++p://forum.xda-developers.com/showthread.php?t=1332776
The question now is: Is the lge-sniper-kernel source still compatible with the latest releases of CM7? I'm worried it is not anymore, because the Huexxx-v4 kernel and NOVA kernel are based on the sniper sources and became not compatible with CM7 anymore at some point.
Oh yes and: If I mess up the kernel build and flash it, can I still access S/W download mode or is the phone bricked beyond recovery?

boype said:
Okay here it goes:
I'm planning on building my own kernel from the lge-sniper-kernel. Basically, what I want to add is just InteractiveX as the default governor for better battery life. I read a lot on the topic and I'm well able to build and inject the kernel. My plans are based on this guide by knzo (dated 4th November 2011): h++p://forum.xda-developers.com/showthread.php?t=1332776
The question now is: Is the lge-sniper-kernel source still compatible with the latest releases of CM7? I'm worried it is not anymore, because the Huexxx-v4 kernel and NOVA kernel are based on the sniper sources and became not compatible with CM7 anymore at some point.
Oh yes and: If I mess up the kernel build and flash it, can I still access S/W download mode or is the phone bricked beyond recovery?
Click to expand...
Click to collapse
The CM7 has the lge-sniper-kernel. The NOVA kernel and Huexxx-v4 kernel wasn't updated. Huexxx updated his kernel to 4.1, he just update with the latest commits, and then it worked.
The part of you messing up, I think if you do a nandroid you can easily restore everything. Since when you update to the latest nightly for an example, the kernel is substitute for the default one, I think you wont have any problem. Just flash over a nightly or the RC version and you will be ok, I think.
I'm not a dev and I don't did this test, it just my assumption.

Sniper is the cm7 kernel so its supposed to work on cm, but huexxx kernel 4.1 is also compiled from source and has interactivex governor, and your phone will still access download if you do something wrong.
FDN

Yeah, you can use Huexxx kernel. This kernel has InteractiveX and other things...

dcop7 said:
Yeah, you can use Huexxx kernel. This kernel has InteractiveX and other things...
Click to expand...
Click to collapse
I can't use Huexxx-4.1 with a non-default governor: Whenever I choose InteractiveX (or any other non-default kernel) and set it to load on boot, the phone is incredibly laggy and slow after reboot. This is why I want to build the kernel myself with interactiveX as default, hoping it won't be laggy.

boype said:
I can't use Huexxx-4.1 with a non-default governor: Whenever I choose InteractiveX (or any other non-default kernel) and set it to load on boot, the phone is incredibly laggy and slow after reboot. This is why I want to build the kernel myself with interactiveX as default, hoping it won't be laggy.
Click to expand...
Click to collapse
It is laggy only in the first minutes. And I think with an init.d script you can make interactiveX default governor, but I don't know if it will be laggy also
---------- Post added at 10:08 AM ---------- Previous post was at 10:05 AM ----------
I think if you use this command you will be able to change the governor:
echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
In your case, it will be something like this:
echo interactiveX > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Create a blank file with this name: "77governor" or something and put this lines
#!/system/bin/sh
echo interactivex > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor​
Copy that file to system/etc/init.d and then reboot. Check if in this way it will be laggy
But do a nandroid first! I didn't test this!!

@dcop7
Not work with init.d script
You must use ROM Toolbox app (or similar), there is an option to make script at boot in scripter menu

slurpdroid said:
@dcop7
Not work with init.d script
You must use ROM Toolbox app (or similar), there is an option to make script at boot in scripter menu
Click to expand...
Click to collapse
Thanks, I didn't know that.
I only used init.d scripts to change other values...

I need to report back here, hoping anyone of you (previously very helpful) guys has a solution to another problem that came up: After injecting my kernel, the phone just gets stuck at the initial LG boot logo (the buttons do not even start flashing). I am able to run S/W update mode to recover though.
I followed knzo's indicated guide to build my own kernel (h++p://forum.xda-developers.com/showthread.php?t=1332776):
1) I installed all needed linux packages
2) cloned the lge-sniper-kernel from github
3) made the '.config' via the command 'make ARCH=arm cyanogenmod_hub_defconfig'
4) built the /arch/arm/boot/zImage successfully with the command 'make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- -j2'. No *.ko files were generated.
5) copied the zImage to aprold's kernel injector zip file from h++p://forum.xda-developers.com/showthread.php?t=1350679
6) flashed the zip via CWM (after doing wipe cache and wipe dalvik).
On a sidenote: I did not even alter anything within the kernel-source, since I first wanted to check out whether I am able to build and flash a kernel in the first place.
Did I do anything wrong or did I forget something? Thanks for your help in advance.

Sorry for doublepost. I solved my problem by using another toolchain.

[M.O.D. KERNEL Q 1.5] MIUI 11 Mi9/ 9T Pro 835mhz GPU DynFsync LZ4 WLblock *FOD Fix*

[M.O.D. KERNEL Q]
*** NOTE: a dev has posted on TG the FOD fix for beta/ MIUI 12 forked from my code, download there! I asked for GitHub source to comply with XDA and will post once I have it and provide a link to the file link "Mi9/Mi9T Pro Optimization and Overclocking" Telegram has it now: https://t.me/joinchat/NNTe_E9G4ZcZKXCUrajFYQ ***
MIUI 11 Mi9/ 9T Pro MOD 1.5
MOD-Q 1.5 is for stable MIUI 11 variants for Mi9 only - Xiaomi.eu 11.0.5 stable is what it was built for, runs best on, just use it. The Mi9T Pro version supports MIUI 11 variants plus many AOSP builds. If you use an official MIUI 11 Xiaomi version you will get a warning message "Contact device manufacturer." You can ignore that, it means nothing. But I highly suggest using Xiaomi.eu 11.0.5, or another MIUI 11 variant like MiRoom or some use Revolution OS.
***DO NOT USE ANY PERFORMANCE (CPU/GPU/ETC) MAGISK MODULES WITH THIS FOR BEST PERFORMANCE!!! IT INSTALLS IT'S OWN OPTIMIZED MAGISK MODULE AUTOMATICALLY***
FP scanner will only work up to 11.0.5. Xiaomi keeps changing the code and not releasing it to made Dev builds not work. There were "patches" that worked until a few weeks back, but Xiaomi has yet again changed their FP scanner code. So I will not update the FP code, do not ask, it is a complete waste of time. Sorry, but Xiaomi.eu 11.0.5 and MOD 1.5 work very very well together.
Features:
835mhz GPU, Adreno Boost, Dynamic Fsync, Boeffla WL blocker (better battery idle), F2FS optimizations, LZ4 ZRAM. EXFAT USB/SDCard support added. Sultan Boost + PapaSmurf's Op7Pro tweaks, Dynamic Overclocking + Underclocking with frequency boost for smooth, fast, clean performance and fluid scaling. Many thanks to PapaSmurf who greatly influenced this kernel; portions are ported from his Op7 Pro Repo.
Mi9T Pro version also reported to work on AOSP ROMs using the original FOD implementation (Derpfest, MSM, CRDroid, Havoc, LOS).
Just use the Magisk Module it installs for you automatically when you flash the zip from TWRP, likely the best results will be obtained. SmartPack can be installed to choose between profiles under Performance Tweaks - battery / balanced / performance / gaming, although the default installed Magisk module is highly recommended by itself for optimal performance and good battery drain.
Github source has been added for MOD 1.5 here. Please read the Readme that's why it's there.
https://github.com/mrslezak/MODQ1.5
Releases are available here: Download them for your device and follow the instructions there. If you already have TWRP and Magisk, it will be easy. Just read please it will answer your questions.
https://github.com/mrslezak/MODQ1.5/releases/tag/MOD1.5
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[M.O.D. KERNEL PIE] Mi9 Android9 GPU830mhz F2FS data/cache Dynamic Fsync LZ4 WLblocker V2 [STABLE]
MOD Pie notes:
***New features added! Dynamic Fsync replaces the Fsync toggle (credits to author Paul Reioux aka Faux123 <[email protected]>), and Boeffla Wakelock blocker 1.1.0 (credits to author: andip71 <[email protected]>) has been added. The GPU830mhz runs on a higher regulator now so even 3DMark runs without issue, this is as stable as it gets. A battery saving Magisk Module has been added for longer life and scored 422.5K still on AnTuTu! It will throttle and hotplug (idle) cores as needed to save battery ***
Super tweaked kernel for the Mi 9. Best AnTuTu Benchmark 432K thus far, expect 420K-430K in daily operation with good battery life. This will vary based on the ROM selected. Stock AnTuTu is 370K. So you can run your phone faster than any production 855+ at the moment. This kernel is setup on purpose to allow anything from stock to maximum performance, you can set parameters as you like in a kernel manager.
GitHub Source: https://github.com/mrslezak/MODKernel-V2-Cepheus
Releases are available here:
https://github.com/mrslezak/MODKernel-V2-Cepheus/releases/tag/V2
TG Name: MattoftheDead
M.O.D. Kernel (MattoftheDead). This kernel is STABLE, everything works, it runs on any MIUI based ROM (MIUI Global Dev, MIUI China Dev, MiGlobe, Xiaomi.eu, AOSP, etc.). ***If you install this kernel and don't follow the tweak instructions, it runs exactly like stock. There is now a Magisk module that will run with the optimal settings to make this easy! *** So read up. You can apply any tweaks you'd like. These include:
GPU 830mhz overclock - stable and smooth. The GPU will throttle down when not being used to a lower mhz. The Magisk Module will enable the max 830mhz clock for you. Or you can go without if you have a dialcode supported GPU MaxFreq OC mode *#*#8106#*#*
ZRAM LZ4 data encryption enabled - fastest encryption method, smaller ZRAM sizes (512mb is good) work very well [2GB is the stock ZRAM default, LZO is the default kernel compression which is slow]. ZRAM is in-memory swap so it is ultra fast. This allows you to have more free RAM for apps to run.
F2FS data and cache partition support - full ICE AES 256bit encryption. Note only @mauronofrio TWRP 3.3.1-39 + supports F2FS partition mounting so you MUST use this TWRP recovery!!!
F2FS has been tested on MIUI Global Dev 9.6.27 and Xiaomi.eu 9.7.22, 9.8.1, MiGlobe, RevOS, AOSP, Havoc thus far (more added daily) and read/write speeds and app access are definitely fast. Support was enabled by working directly with @mauronofrio on XDA (thanks Mauro) so we originated F2FS support for Mi9 - there are also F2FS kernel tweaks that help the speed in the kernel.
BOEFFLA Wakelock Blocker 1.1.0 - blocks wakelocks and allows you to change what gets blocked that is waking up your phone and preventing deep sleep. There are defaults blocked already in this build that are known to be blockable safely. If you want to add more, use SmartPack Kernel manager under Wakelocks. It will also show you what apps are causing them and the frequency so you can disable the ones that are not needed.
If you want to join in the discussion and see updates in realtime, World MI9 & Mi9T Pro Optimization and Overclocking is a TG group which has many things related to MOD and any other kernels, mods for the phone, Magisk Modules, all types of things for the devices.
Step 1: [KERNEL REQUIRED FILES]
Go to the releases page posted earlier and download everything.
Step 2: [ROM SELECTION]
If you already have a Pie MIUI based DEV ROM installed, you can continue to use it. Global Dev 9.6.27 is recommended. But this supports up to Xiaomi.eu 9.8.1. If you want to use a new MIUI based ROM, download it and setup the device (between these ranges of releases - some like MiRoom, some like stock, some like Xiaomi.eu). If you are clean flashing everything, don't bother restoring all the apps - they will be deleted when you switch to F2FS. Just set it up so you can login and get to the default menu with the default apps displayed. Either way, you will have to setup the device as a new phone. So back up all your user data (photos, downloads, etc), apps, etc. using Google Drive, Xiaomi Cloud, Titanium Backup Pro, or any other app that backs up apps and settings. It's often easiest to put them on your PC since you will be plugged into it during this install process with your USB cable.
Step 3: [MAURO TWRP INSTALLATION FOR F2FS SUPPORT]:
Boot Mi9 holding Power + Volume Down
Hook up to your phone to the PC with the charging cable
Open a command prompt. Go to your Minimal ADB and Fastboot folder.
Type: fastboot devices
And hopefully you see your device ID pop up. If not you don't have the right driver, the cable is bad, or something else is wrong. Search Google.
Next flash Mauro TWRP:
fastboot flash recovery twrp-3.3.1-41-cepheus-mauronofrio.img (or use his latest from the link at the bottom of this thread)
Hopefully you see it flash to the device in a few seconds successfully and it's ready to go.
Booting to TWRP:
Turn off your phone. Now hold down power + volume up. Once the boot Logo appears, let go of the power button but keep holding volume up. TWRP should boot. If not, try again. I usually have to remove the phone case. Now enter your password and proceed to the next section. If it asks you if you want to keep the system read only SAY NO! You will be modifying system components, keep it writable to avoid installation issues.
Step 4: [FLASHING THE M.O.D. KERNEL]
Check the releases page posted above. Just unzip the file there and flash via TWRP as an image to boot. It's patched with Magisk already.
Step 5: [CONVERT EXT4 TO F2FS}:
Converting EXT4 data and cache partitions to F2FS:
Check the releases page posted above for fstab_patch_F2FS_MI9_Cache_NoBarrier.zip required to enable F2FS. You MUST flash this in TWRP or your OS will NOT be able to boot an F2FS data partition!!!! This file has been kanged all over the internet, it was created here. Feel free to use it, everyone already is.
***Note flashing TWRP / Install / fstab_patch_F2FS_MI9_Cache_NoBarrier.zip MUST be repeated any time you change ROMs or you won't have access to your data!!! So back this up!!!!***
Boot back into TWRP. You will need to go to Wipe, Advanced Wipe, Click Data, Repair or Change File System, Change File System, and click F2FS. Swipe to change. It will format and you'll have nothing on your data partition. Next format cache. Go to Wipe, Advanced Wipe, Click Cache, Repair or Change File System, Change File System, now click F2FS. Swipe to change. Again it will format and be wiped.
Step 6: [SETTING UP YOUR "NEW" PHONE]:
Next, reboot to System. The device should boot up and welcome you to your "new" device. It has no data apps so it has to be new. You will have to login to your Xiaomi account if it is associated with the device. Then you can choose to restore from a Google Backup and next from Xiaomi Cloud. You can do either one to get your apps back. I would suggest Xiaomi Cloud after Google completes all its downloads - it will place icons in the right places and install your root apps if you had them. And after setting up your apps, now boot back to TWRP and make a Backup. Now for this Nandroid backup you should backup data, boot, dtbo, and vendor partitions (vendor has the fstab.qcom file that allows your F2FS supported partition to boot now). Even if you save to your internal device initially, be sure to put it on a PC for safe keeping. Then If you accidentally wipe your partition later, you can skip importing, get to the main screen after minimal setup completes, enable file transfer from the connected PC, and then copy the Nandroid backup to your Internal Memory. Boot into TWRP and restore the backup and you're back in business.
Step 7: [INSTALLING MAGISK MANAGER AND KERNEL MANAGER]:
So now you install the MagiskManager-v7.3.2.apk to enable all root functions. If you want Google Pay and anything else setup posts are here in the Mi9 forum that show you how. Generally hide all banking apps, trading apps, Google Pay, GMS, etc. And I suggest installing GMS doze for better battery life and the Mi9 Auto Brightness fix.
In addition, to have the MOD kernel setup for the best performance, go into Magisk Manager, Modules, and flash the (Magisk)MOD-Battery-Saver+_v2.zip from the releases page. It will auto set all the parameters the kernel features, and does a great job with extending battery life at the same time.
This is the best setup for performance. Pictures are included below.
If you would like to change the settings, you need a kernel manager. So next you can install the Smart Pack APK SmartPack_Kernel_Manager_v8.7.apk to enable or disable all the tweaks you desire.
Pictures are attached below to show the TWRP screens for flashing and F2FS partition conversion. Also the settings of best performance using Smart Pack kernel manager are here. If you want to change any of the best settings after flashing the Magisk Module, do it in the kernel manager of your choice and set on boot - where to change those options is in the pictures below for SmartPack.
Enjoy!
Mauro TWRP
https://forum.xda-developers.com/Mi-9/development/recovery-unofficial-twrp-xiaomi-mi-9-t3905825
SmartPack Kernel Manger
https://forum.xda-developers.com/android/apps-games/app-smartpack-kernel-manager-t3854717
FK Kernel Manager CPU Profile
https://play.google.com/store/apps/details?id=com.franco.kernel&hl=en_US
Magisk
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Minimal ADB and Fastboot
https://forum.xda-developers.com/showthread.php?t=2317790
And one last thing. I have been working with some of the most well known devs out there on XDA on Telegram, Private Messaging, and other channels to get this kernel where it is - but I have no XDA presence. I've helped hundreds of people on Telegram setup their systems or diagnose their issues. If you find this post useful, helpful, innovative, or install my kernel and like it, please click the Thanks button to acknowledge the work that I've done to get the Mi9 to this point. It would be greatly appreciated to get some thank yous for all the hours I've put into this development work for the Mi9, and provides some motivation to keep improving. Other kernels are on the way as well for more Xiaomi / Redmi devices if I feel some love from the community. Much appreciated!
Thanks goes out to @smeroni68 and @mauronofrio for helping fix the fstab.qcom zip that cost several hours of pain yesterday for users and I on Telegram that did not have the Vendor partition mounted when flashing the old fstab.zip file - it will flash now mounted or not from TWRP. And thanks to @ilia1985 for providing a Magisk Module template for the kernel manager settings, now OC setup doesn't even need a kernel manager!
***DISCLAIMER - APPLYING ANY ROOT MODS IS ALWAYS AT YOUR OWN RISK! I AM NOT RESPONSIBLE FOR BRICKED DEVICES, DAMAGE OR OTHER THAT MAY OTHERWISE OCCUR. THIS HAS BEEN TESTED EXTENSIVELY BUT USE AT YOUR OWN RISK***

First.. that's the first time.
Huge thanks to the dev for their contribution!

Awesome work!
What does "miui based rom" mean?
Is Havoc OS miui based?

Troomak said:
Awesome work!
What does "miui based rom" mean?
Is Havoc OS miui based?
Click to expand...
Click to collapse
Nah, it's aosp

Looks like it's base on last one version of android9 MIUI DEV 9.8.1 to modify its kernel, doesn't it ?
So it's not base on linux kernel 4.14.139 to develop ?
Kris

Kris Chen said:
Looks like it's base on last one version of android9 MIUI DEV 9.8.1 to modify its kernel, doesn't it ?
So it's not base on linux kernel 4.14.139 to develop ?
Kris
Click to expand...
Click to collapse
4.14.83 per the hardware device settings. Q is already upstreamed to the latest Linux and CAF so just waiting on a source release so kernels can be made. No need to spend time upstreaming unless another dev wants to (I'm in contact with the other kernel dev here on XDA we're working together now, he may upstream). He upstreamed his to 4.14.139 and will pull my source repo soon to fix bugs in his build so he may just upstream this kernel or fix bugs in his kernel in the process. Collaboration is a good thing. I've been waiting for assistance for a long time and it's good to team up with others devs. We don't get paid we do this as a hobby.

Thanks !
Can I use Ex kernel manager to tune kernel parameters ?
In another one - Will there CPU/GPU frequency table exist to choose which one of frequency combination I want to use base on condition of phone usage - Gaming, multimedia application, and general usage !
mslezak said:
4.14.83 per the hardware device settings. Q is already upstreamed to the latest Linux and CAF so just waiting on a source release so kernels can be made. No need to spend time upstreaming unless another dev wants to (I'm in contact with the other kernel dev here on XDA we're working together now, he may upstream).
Click to expand...
Click to collapse

Kris Chen said:
Thanks !
Can I use Ex kernel manager to tune kernel parameters ?
In another one - Will there CPU/GPU frequency table exist to choose which one of frequency combination I want to use base on condition of phone usage - Gaming, multimedia application, and general usage !
Click to expand...
Click to collapse
Yes EX Kernel Manager is a good one to use. You will have to experiment with if it can lock in frequencies. Follow the guide for CPU settings they are optimal. You could by app adjust if needed and if it is supported by EX. Some support per app some don't. I think SmartPack does. The issue is that the 830gpu clock is an additional clock. The others are all stock clocks. This is for maximum battery life and compatibility. The highest 830GPU is only fully settable via dial code *#*#8106#*#* at this time - try in your ROM to see if it is supported. In some KM you can set max and min to 830mhz and it will lock in the frequency (FK) although this was only tested for 1 day on an unstable build (too hot thermals). More tests are needed, feel free to try and post what you observe.

hiperglyde said:
Nah, it's aosp
Click to expand...
Click to collapse
Many AOSP builds are still on Xiaomi underlying code. The test would be to install the TWRP mentioned and take a backup of boot and dtbo partitions. Stay on EXT4. Then flash the restore TWRP provided and see if it boots. I user has already made it to the logo screen on AOSP using this method. He is using an unencrypted partition though. If you are on an encrypted partition the likelihood of it working is higher. The TWRP is bootable from fastboot as well so you will be able to access recovery. Advise you save the backup to removeable media / computer before flashing. Report back your results please.

Hey There.
I am trying to mount the fsqtab.qcom an do not get how to do it on my Mi9 using these directions?
The fstab.qcom included MUST be placed in /vendor/etc/ OR YOUR PHONE WILL NOT BE ABLE TO MOUNT THE DATA PARTITION!!!! So your next step is to copy the fstab.qcom via a root browser or from Minimal ADB and Fastboot. Boot to Recovery (hold power + volume up, release power button when the boot logo appears), then run from a terminal: adb push fstab.qcom /vendor/etc/fstab.qcom
How do you do whats listed above 'precisely'?
I can make everything else work. I just cannot seem to get this file inserted in Vendor?
Can you help please
(my profile says senior member but I am really not )

Great work!! Thanks for the kernel.
Any chance Kcal will be possible?

Finaly installed it on aosp extended.Thanks for developer

Bryceicle1971 said:
Hey There.
I am trying to mount the fsqtab.qcom an do not get how to do it on my Mi9 using these directions?
The fstab.qcom included MUST be placed in /vendor/etc/ OR YOUR PHONE WILL NOT BE ABLE TO MOUNT THE DATA PARTITION!!!! So your next step is to copy the fstab.qcom via a root browser or from Minimal ADB and Fastboot. Boot to Recovery (hold power + volume up, release power button when the boot logo appears), then run from a terminal: adb push fstab.qcom /vendor/etc/fstab.qcom
How do you do whats listed above 'precisely'?
I can make everything else work. I just cannot seem to get this file inserted in Vendor?
Can you help please
(my profile says senior member but I am really not )
Click to expand...
Click to collapse
Did you turn on the option ADB sideload in twrp? Under advanced?

*justintime* said:
Did you turn on the option ADB sideload in twrp? Under advanced?
Click to expand...
Click to collapse
I just installed it via root browser

Two ways you can do:
1.To use root explorer copy fstab.qcm under /vendor/etc ...
2.Enter TWRP and mount vendor parition, then copy fstab.qcm under /vendor/etc ...
Kris
QUOTE=Bryceicle1971;80122399]Hey There.
I am trying to mount the fsqtab.qcom an do not get how to do it on my Mi9 using these directions?
The fstab.qcom included MUST be placed in /vendor/etc/ OR YOUR PHONE WILL NOT BE ABLE TO MOUNT THE DATA PARTITION!!!! So your next step is to copy the fstab.qcom via a root browser or from Minimal ADB and Fastboot. Boot to Recovery (hold power + volume up, release power button when the boot logo appears), then run from a terminal: adb push fstab.qcom /vendor/etc/fstab.qcom
How do you do whats listed above 'precisely'?
I can make everything else work. I just cannot seem to get this file inserted in Vendor?
Can you help please
(my profile says senior member but I am really not )[/QUOTE]

*justintime* said:
Did you turn on the option ADB sideload in twrp? Under advanced?
Click to expand...
Click to collapse
No. Does that allow the terminal to find the file in your USB?
I've been leaving the extracted files in my c-type USB plugged into the cell
---------- Post added at 10:30 AM ---------- Previous post was at 10:26 AM ----------
Kris Chen said:
Two ways you can do:
1.To use root explorer copy fstab.qcm under /vendor/etc ...
2.Enter TWRP and mount vendor parition, then copy fstab.qcm under /vendor/etc ...
Kris
QUOTE=Bryceicle1971;80122399]Hey There.
I am trying to mount the fsqtab.qcom an do not get how to do it on my Mi9 using these directions?
The fstab.qcom included MUST be placed in /vendor/etc/ OR YOUR PHONE WILL NOT BE ABLE TO MOUNT THE DATA PARTITION!!!! So your next step is to copy the fstab.qcom via a root browser or from Minimal ADB and Fastboot. Boot to Recovery (hold power + volume up, release power button when the boot logo appears), then run from a terminal: adb push fstab.qcom /vendor/etc/fstab.qcom
How do you do whats listed above 'precisely'?
I can make everything else work. I just cannot seem to get this file inserted in Vendor?
Can you help please
(my profile says senior member but I am really not )
Click to expand...
Click to collapse
[/QUOTE]
Thanks. I'll try your an other suggestions

*justintime* said:
Did you turn on the option ADB sideload in twrp? Under advanced?
Click to expand...
Click to collapse
Have tried to turn on ADB side load an it keeps failing after a long wait? What am i missing?
---------- Post added at 12:07 PM ---------- Previous post was at 12:00 PM ----------
mslezak said:
[M.O.D. KERNEL] Mi 9 Android 9 Pie GPU830mhz F2FS data/cache Fsync LZ4 ZRAM [STABLE]
MOD-KERNEL-TOOLS.zip -> kernel and all software to use the features of the kernel: https://mega.nz/#!TopRnIDK!6GbL_8QPToK0oLCSDnJ_d9EUnZ9AflDgf-9pu6JCiKo
GitHub Source: https://github.com/mrslezak/Xiaomi_Kernel_OpenSource branch: cepheus-p-oss
Telegram Group: https://t.me/joinchat/NNTe_E9G4ZcZKXCUrajFYQ
Telegram Name: @MattOftheDead
M.O.D. Kernel (MattoftheDead). This is a kernel project that has been going on for months now behind the scenes. It is STABLE, everything works, it runs on any MIUI based ROM (MIUI Global Dev, MIUI China Dev, MiGlobe, Xiaomi.eu, etc.). Android 9 (Pie) only as Android 10 has not been released and Xiaomi decided to change the kernel components (boot.img and dtbo.img will flash to Q, but no WIFI, no calls, and colors are "off."). If you install it and don't follow the tweak instructions, it runs exactly like stock. You can apply any tweaks you'd like. These include:
GPU 830mhz overclock - stable and smooth - most MIUI Dev based ROMs can enable via dialing *#*#8106#*#* - enable MaxFreq GPU Mode - you can test before installing. The GPU will throttle down when not being used to a lower mhz.
FSync toggle (enable/disable) - disable gives higher speed at the risk of data corruption if a system crash occurs. Note I've used this 4 months with no issues, if you use stable software you are less likely to run into problems. Eventually dynamic Fsync will be added if I ever have time or help (writes to disk when screen is off, safer than just disabling).
ZRAM LZ4 data encryption enabled - fastest encryption method, smaller ZRAM sizes (512mb is good) work very well [2GB is the ZRAM default, LZO is the default kernel compression which is slow]
F2FS data and cache partition support - support with full ICE AES 256bit encryption. Note only @mauronofrio TWRP 3.3.1-39 + supports F2FS partition mounting so you MUST use this recovery!!!
F2FS has been tested on MIUI Global Dev 9.6.27 and Xiaomi.eu 9.7.22 thus far and read/write speeds and app access are definitely fast. Support was enabled by working directly with @mauronofrio on XDA (thanks Mauro) so we originated F2FS support for Mi9 - there are also F2FS kernel tweaks that help the speed.
Now if you want to install this kernel, you can right away and use it on EXT4 (default for all Xiaomi ROMs). To use with F2FS you will need to adb push a modified fstab.qcom file to /vendor/etc/fstab.qcom. Or you can use a root browser and just copy it over if you are currently rooted. It will boot either EXT4 or F2FS with encryption with the same fstab.qcom file. And then you will enter the danger zone once it is time to enable F2FS! You will have to backup all your apps. This means MiCloud (for root apps this is good, saves APKs and settings), Google backup (the backup frequency seems random to me, although if a backup is recent you'll get all your PlayStore apps back), Titanium Backup Pro ($ PAID, you can't use the free version as the internal data will be wiped when the partition is formatted), or search for another backup solution online. Nandroid backups won't work after conversion either as they include the partition format (EXT4, F2FS, etc.) so don't bother. More on this later in the thread.
To save everyone time and space (I don't have a good way to upload files), join my Telegram channel. Read the instructions and you will be up and running in no time. They are outlined in great detail there along with tons of other discussions around optimizations and benchmarks. However, I will attempt to summarize installation on XDA as best as I can. Telegram Link: https://t.me/joinchat/NNTe_E9G4ZcZKXCUrajFYQ -> XDA MI9 Optimization and Overclocking
I have also provided a Mega.nz zip file with a bunch of tools you can use to get up and running. It comes with the modified kernel (boot.img GPU830_F2FS_Fsync_CRC_LZ4_boot.img and dtbo.img GPU830_F2FS_Fsync_CRC_LZ4_dtbo.img), the modified fstab.qcom file for encrypted F2FS support, the Mauronofrio TWRP version required twrp-3.3.1-39-cepheus-mauronofrio.img, Magisk-v19.4.zip Canary, MagiskManager-v7.3.2.apk, SmartPack Kernel Manager com.smartpack.kernelmanager-v8.7-20190815-release.apk to set tweaks along with a file SmartPack_init.d.txt that can be copied and pasted directly into SmartPack (in the menu, Init.d, enable Init.d, add new, copy and paste the text in, save it, and everything will be setup optimally) - NOTE init.d does not work on all ROMs (even with it enabled on boot in the software), so you may need to click on the profile under Init.d manually to execute after boot. A Franco Kernel Manager CPU Profile is included Maxfreq-CPUs-FK_Kernel_Manager_Profile if you use FK since it won't let you set CPU frequencies in the software (included just for people who have FK or prefer it over SmartPack - it won't setup ZRAM to LZ4 or 512mb for you, or toggle FSync, so you will have to manually do it if you use FK). Also the latest Windows Minimal ADB and Fastboot minimal_adb_fastboot_v1.4.3_setup.exe is included, although you probably already have it since you have a bootloader unlocked phone
Now some very basic steps to the more complicated, much you should already know since you clicked on a custom kernel post!!!!
Flashing Mauro TWRP:
Boot Mi9 holding Power + Volume Down
Hook up to your phone to the PC with the charging cable
Open a command prompt. Go to your Minimal ADB and Fastboot folder.
Type: fastboot devices
And hopefully you see your device ID pop up. If not you don't have the right driver, the cable is bad, or something else is wrong. Search Goggle.
Next flash Mauro TWRP:
fastboot flash recovery twrp-3.3.1-39-cepheus-mauronofrio.img
Hopefully you see it flash to the device in a few seconds sucessfully and it's ready to go.
Booting to TWRP:
Turn off your phone. Now hold down power + volume up. Once the boot Logo appears, let go of the power button but keep holding volume up. TWRP should boot. If not, try again. I usually have to remove the phone case.
Flashing boot.img, dtbo.img, and Magisk19.4.zip:
You can do this manually or from a TWRP backup. In the MOD-KERNEL-TOOLS zip file, you can unzip [TWRP-Restore-Backup] MODKernel-Magisk19.4 to internal storage or OTA SD card / USB drive, click Restore, and restore boot and dtbo. Then it is already patched with Magisk 19.4 (you have root access). Then reboot. Now for the more manual method. You can select Install. Then select Flash Image. Select GPU830_F2FS_Fsync_CRC_LZ4_boot.img and flash to the boot partition. After flashing, go back in TWRP and flash GPU830_F2FS_Fsync_CRC_LZ4_dtbo.img to the dtbo partition. Now go back in TWRP again and click on Flash Zip. Select Magisk19.4.zip and flash. After this completes, reboot.
Setting up F2FS data and cache partitions:
The process to setup F2FS is to first download a compatible ROM if you don't already have one installed (MIUI based, Android 9 (Pie), this includes MIUI Dev, Xiaomi.eu, MiGlobe, Revolution OS, etc.) ENSURE ANDROID 9 PIE: 9.8.1 variants are usually the last Android Pie build. After downloading, you can install it as a new phone after following the guide below so don't bother setting anything up other than a Xiaomi account login if prompted; don't restore apps yet either. You can setup with defaults now and not import apps. You should make it to the home screen though. All apps will be deleted after formatting.
You will be setting up a new phone and will have to login to all your apps over again. So to reiterate, MAKE COPIES OF ALL YOUR PROGRAMS BEFORE DOING THIS! Xiaomi Cloud, Google Backup, Titanium Backup, etc. - use something not on your phone, NOT a Nandroid backup! NOT in internal storage! (it will be wiped)!
The fstab.qcom included MUST be placed in /vendor/etc/ OR YOUR PHONE WILL NOT BE ABLE TO MOUNT THE DATA PARTITION!!!! So your next step is to copy the fstab.qcom via a root browser or from Minimal ADB and Fastboot. Boot to Recovery (hold power + volume up, release power button when the boot logo appears), then run from a terminal: adb push fstab.qcom /vendor/etc/fstab.qcom
Now in TWRP, you will need to go to Wipe, Advanced Wipe, Click Data, Repair or Change File System, Change File System, now click F2FS. Swipe to change. It will format and you'll have nothing on your data partition. Next format cache. Go to Wipe, Advanced Wipe, Click Cache, Repair or Change File System, Change File System, now click F2FS. Swipe to change. Again it will format and be wiped.
Next, reboot to System. The device should boot up and welcome you to your "new" device. You will have to login to your Xiaomi account if it is associated with the device. Then you can choose to restore from a Google Backup and next from Xiaomi Cloud. You can do either one to get your apps back. I would suggest Xiaomi Cloud after Google completes all its downloads - it will place icons in the right places and install your root apps if you had them. If you accidentally wipe your partition later (as I just did while making this tutorial, ouch), you can skip importing, get to the main screen, enable file transfer from the connected PC, then copy the Nandroid backup you absolutely should make and transfer to a PC right after setting all your apps up (logging in etc.). Now for this Nandroid backup you should backup data, boot, dtbo, and vendor partitions (don't forget that fstab.qcom we put here!). Even if you save to your internal device initially, be sure you later put it on a PC for safe keeping. I am just now copying back my TWRP directory to restore my phone this moment as I type...
Pictures are attached below to show the TWRP screens. Also the settings for the best performance using Smart Pack kernel manager included in the ZIP file download (will add after I restore). And a picture of the dial code + GPU Max Freq screen where you turn on the 830mhz GPU clock. Enjoy!
Links to XDA files included in the MOD-KERNEL-TOOLS.zip:
Mauro TWRP
https://forum.xda-developers.com/Mi-9/development/recovery-unofficial-twrp-xiaomi-mi-9-t3905825
SmartPack Kernel Manger
https://forum.xda-developers.com/android/apps-games/app-smartpack-kernel-manager-t3854717
FK Kernel Manager CPU Profile
https://play.google.com/store/apps/details?id=com.franco.kernel&hl=en_US
Magisk
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Minimal ADB and Fastboot
https://forum.xda-developers.com/showthread.php?t=2317790
Click to expand...
Click to collapse
No system no boot an a bootloop. This enhancement is a bit complex an I'm kind of confused?

Bryceicle1971 said:
Have tried to turn on ADB side load an it keeps failing after a long wait? What am i missing?
---------- Post added at 12:07 PM ---------- Previous post was at 12:00 PM ----------
No system no boot an a bootloop. This enhancement is a bit complex an I'm kind of confused?
Click to expand...
Click to collapse
Witch rom are you using?
Inviato dal mio MI 9 utilizzando Tapatalk

smeroni68 said:
Witch rom are you using?
Inviato dal mio MI 9 utilizzando Tapatalk
Click to expand...
Click to collapse
Xiaomi.eu for Mi9 9.7.22 v10-9

Bryceicle1971 said:
Have tried to turn on ADB side load an it keeps failing after a long wait? What am i missing?
---------- Post added at 12:07 PM ---------- Previous post was at 12:00 PM ----------
No system no boot an a bootloop. This enhancement is a bit complex an I'm kind of confused?
Click to expand...
Click to collapse
You copied fstab.qcom to /vendor/etc/? Boot into recovery, attached to your PC. Then from a command prompt in Minimal ADB and Fastboot,copy fstab.qcom there. Then type: adb devices. It should show a device ID. Then type adb push fstab.qcom /vendor/etc/. It should say succeeded. Then reboot. This only makes a difference if you are on F2FS.
If you aren't booting to system go ahead and try the TWRP recovery version - unzip and flash that package to boot and dtbo from TWRP Restore. It's already patched with Magisk 19.4 and several people are on it that had issues flashing the files separately.