Database Develop

[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.

[ROM] [2013-05-14] CM10 "Look Ma! No Hands!" Edition

Hiya !
As a result of all the r&d in Metallica's thread, i'm starting this new one to focus mainly on testing if by having cm10 run on the new bootloader, the call bug is somehow affected/resolved.
So let's do that
For whoever may want to compile the rom, all the patches and instructions are here and on the next few pages. Let's keep that thread for raw development and this one for testing
This rom is 99% pure cm material and, aside the patches i applied to make it boot on the new bootloader and some little things like PDroid... for now...
Do not, and i repeat, do not flash any official cm10 or cm10.1 release when on the new booloader. It will just fail miserably
So, here goes...
Updated howto to simplify the process by using the cwm flashable recovery
If you come from any ICS with unlocked bootloader (Topogigi, Carburano, etc...):
1) grab the recovery zip and the cm10 zip attached to this post
2) enable debug in developer options (if you haven't already of course)
3) connect the usb cable to your box
4) copy the two zips in your external sd card
5) reboot to recovery by holding power and volume down
5) wipe data/cache, then go to mounts and format system (just to be safe)
6) flash the recovery zip file you previously slapped in the external sd card
7) reboot recovery from the advanced menu
8) flash the cm10 zip as usual
If you come from a GB Bootloader (cm7/9/10 - stock gb):
1) get the AIO Toolkit and read the instructions on that thread !!!
2) in the AIO toolkit select to flash my recovery
3) download the latest cm10 zip attached to this post
4) copy the zip to your external sd card
5) boot to recovery holding down POWER and VOL- together
6) flash the cm10 zip as usual
If you update from a previous version of this rom
1) download the new version to your external (or internal) sdcard
2) reboot to recovery
3) wipe cache/dalvik (no data wiping necessary at all)
4) flash the rom
5) reboot and enjoy
A nandroid backup of your previous rom is vigorously suggested
A big thanks to RC and the CM team for cm10 and cm10.1 is mandatory
Special thanks go to Tonyp, Metallica, Harsh, Wkpark, Imperticus, and all the people (surely i forgot someone, don't hate me) that spent time and effort in brainstorming to make this possible in the r&d thread
Second post: kernel, addons and experimental mods
Third post: recovery and rom changelogs
CM10 Downloads
2013-05-14 -> cm-10-20130514-UNOFFICIAL-p990 (Look Ma! No Hands!)
2013-02-08 -> cm-10-20130208-UNOFFICIAL-p990 (Here Come The Drums)
2013-01-06 -> cm-10-20130106-UNOFFICIAL-p990 (Lights Fest)
2012-12-28 -> cm-10-20121228-UNOFFICIAL-p990 (Penguins Galore)
2012-12-26 -> cm-10-20121226-UNOFFICIAL-p990 (After Christmas)
2012-12-24 -> cm-10-20121224-UNOFFICIAL-p990 (Merry Christmas)
2012-12-20 -> cm-10-20121220-UNOFFICIAL-p990 (Initial Release)
Touch Recovery 6.0.2.5
Get it from this post and read the changelog there. Thanks to Tonyp.
-

Pengus Kernel
Development of this kernel has been discontinued and resumed as Kowalski Kernel in this thread !​
Change Log
Code:
2013/01/13
- Fixed wifi issues when tethering
- Reverted a patch related to sdcard access
- Set default i/o readahead to 256 kbytes
- Added a temp wake / unwake lock to suspend/resume for bcm4329
- Revert to 32M of carveout reduction
- Force wifi pm_fast mode when screen on
- Revert to 07/01 values for kernel flags
2013/01/11
- Disabled auto hotplug during screen-on operations
* Both CPUs will be always active
- Enabled auto hotplug only during suspend
* On screen off the 2nd core will go to sleep
- Small changes in the kernel cflags
2013-01-10
- Fixed auto_hotplug code that was causing freezes
- Fixed the auto_hotplug parameters for good
- Configuration optimizations (lots of them)
- Fixed a couple bugs in the wifi pm system
- Set default i/o readahead to 1024 kbytes
- Implemented Proportional Rate Reduction for TCP
- Applied a few patches to speedup access to the sd
- Modified cflags to speedup the fpu a bit
2013-01-07
- Fixed notification lights... again.
* They work perfectly when selecting "always on" mode.
* Blinking requires some more love in the kernel. Works perfectly when on charger.
- Fixed wifi power consumption when in active use.
2013-01-06
- Carveout reduced to 120M. 32M more ram for free.
- Fixed notification lights. They blink correctly now.
- Fixed wifi:
* Will keep the connection in background and allow the phone to enter deep sleep.
* Preconfigured to use PM_FAST in suspend and PM_OFF during normal operation.
* Added sysfs interface for wifi power management (/sys/modules/wireless/parameters/max_pm).
* "echo 1 > /sys/modules/wireless/parameters/max_pm" will enable PM_MAX suspend mode.
- Fixed bluetooth:
* Allows the phone to enter deep sleep without disconnecting the clients.
* Headset commands will not work when the phone is in deep sleep.
* Just turn on the screen and they will work fine until there is rf traffic (music, voice, etc).
* Added 60 seconds grace time before deep sleep kicks in.
- Backported ROW I/O scheduler from Qualcomm (from kernel 3.2). Set as default.
- Backported Dynamic Interactive governor (from kernel 3.2). Set as default.
- Backported Auto Hotplug (from kernel 3.4) and removed Tegra Hotplug.
* Kernel will disable the second core when not needed.
* Second core is always off when in sleep mode.
- Backported multiple SMP patches (from kernel 3.4).
- Updated Interactive governor with patches from the Aurora Project.
- Enabled support for BoostPulse on the Interactive governor.
- Added support for NTFS and HFS+ filesystems.
- Added support for NFS 3/4.
- Added support for multiple tcp congestion algorithms.
- Changed the default tcp congestion algorithm to Westwood.
- Removed all debug options. Kernel is compiled in release mode now.
2012-12-30
- Fixed bluetooth disconnecting when screen off. Note: When bt is on, the phone won't go into deep sleep.
- Fixed wireless hotspot. When hotspot is active, wifi will not go to sleep so tethering will work fine.
- Merged marsgod audio/media fixes from his github.
- Merged a ton of fixes from nvidia and broadcom.
- Reduced carveout to 128M so, well, you get 24M of additional ram for free.
- Some more fixes to the wifi module, so it drains even less battery in deep sleep.
- Removed the conservative governor when in sleep, possible cause of BSODs.
- Set deadline as default i/o scheduler and tweaked a bit the parameters.
Before installing these kernels, just two things
1) This is only for the new bootloader. Don't install it on the old one or your phone won't boot.
2) Wipe dalvik and cache in cwm before flashing a kernel. No data wipe is necessary.
For kernels >= 2013-01-06
- Make sure that in Settings -> Performance -> Processor it's set as default the DynInteractive governor, and that in Settings -> Performance -> I/O Scheduler the default is ROW. For both tick the "set on boot" option and reboot. The DynInteractive seems to behave perfectly in terms of frequency ramping so far and keeps the system running mostly on low clock speeds, unless really needed (games, heavy browsing, etc).
- To enable the wifi conservative mode, via adb/terminal, type "su" and then "echo 1 > /sys/module/wireless/parameters/max_pm". This setting will not stick across reboots, but will take effect as soon as you turn off your screen.
- They will work only on roms with a date >= 2012-12-28
---> 2013-01-13 ---> pengus-kernel-20130113 + Wifi-Conservative-20130113 (only for this kernel)
---> 2013-01-11 ---> pengus-kernel-20130111 + Wifi-Conservative-20130111 (only for this kernel)
---> 2013-01-10 ---> pengus-kernel-20130110 + Wifi-Conservative-20130110 (only for this kernel)
---> 2013-01-07 ---> pengus-kernel-20130107 + Wifi-Conservative-20130107 (only for this kernel)
---> 2013-01-06 ---> pengus-kernel-20130106-v2 + WifiModule-Fix-20130107 (only for this kernel)
---> 2012-12-20 ---> cm10-kernel-20121230
Warning, dragons ahead !
1) Enable Swap on the unused SWP partition (/dev/block/mmcblk0p4) - Thanks to wfd for the idea
This will grant you 370mb of swap space.
On heavy duty this will maybe slow down marginally your phone, but trying is for free and that partition is 100% wasted otherwise
Download the SwapEnabler.zip attached to this post and flash it in cwm. Done
2) Fix Nitz time on V30A and SU660 basebands
So your timezone is totally crazy ? Just add "telephony.test.ignore.nitz=true" to /system/build.prop and reboot. This will fix it.
Don't know how to mount/remount edit files on android system ? Learn from above or... flash NitzDisabler.zip attached to this post from cwm
3) Swap External/Internal sdcards - Thanks to Imperticus
Check out this post and download the file attached to it. Just flash it in cwm and your sdcards will be swapped
4) DPI Changer - Thanks to Tonyp
Check out this post and read it carefully
5) Working GTalk Audio/Video !!! - Thanks to wfd
Say thanks to wfd on this post
6) Interesting post on how to get a perfect GPS fix - Thanks to tetsuo55
You can find the post here and don't forget to thank him !
7) Working FaceLock for CM10 roms ! - Thanks to flopower1996
Here's the post where you can thank him and download the apk: http://forum.xda-developers.com/showpost.php?p=37795310&postcount=3044
.

CM10 for the Unlocked ICS Bootloader Changelog
Code:
2013/05/14
- Fixed two major RIL bugs
- Call Forwarding Options
- In-Call Mute
- Merged all upstream CM changes up to today
- Optimized the thumbnails handling
- Optimized the media scanner process
- Added the option to center the clock on the menu bar
- Added hardware key targets
- Torch
- Screenshot
- Quick Memo
- Power Menu
- Toggle Last App
- Long press menu key on lockscreen -> Torch
- Added Quick Memo app
- Ships with Smart Launcher and Nova Launcher
- Comes with a pre-release 122pre Kowalski Kernel
- Zen I/O scheduler
- A load of subtle performance and power saving fixes
- Fix for USB/AC reporting
- Removed all default live wallpapers, videos, wallpapers, etc
2013/02/08
General mods
- Nitx fix by TonyP - After flashing reboot again to make it work
- Updated wpa supplicant 8
- Updated dhcp daemon
- Trickster Mod preinstalled
- Kowalski Manager preinstalled
- PDroid Apk preinstalled
- Holo Launcher as default launcher
- Trebuchet removed
- Added iwconfig/iwlist
- Added alsa_amixer / alsa_ctl / alsa_aplay
- Removed VideoEditor apk
- Added libjpeg-turbo from Linaro Android
- Optimized CFLAGS for C and C++ parts
- Enabled Purging of Assets in performance -> memory menu
- Kowalski Kernel 011p4
Cherry-Picks from CM Gerrit
- FM Radio: Add support for FM Radio in Android
- SMS Usage Monitor: Prevent recurring usage Alerts
- Added cooler weather icons (thanks wfd)
- Fix for custom button and keyboad light values
- extend PreferenceActivity for title text on a single pane mode
- add criticalBatteryShutdownLevel; fix plugged/charging status
- bluetooth: prevent Android restart with buggy devices
- Allow purging of asset bitmaps
- Stop supplicant and dhcp before start
- audioflinger: Fix to release wakelock after closeoutput
- libstagefright:Buffer size needs to be set on Native Window
- Fix for NULL pointer deference when Audio Record fails
- Fix for audio playing on speaker when headset is removed
- surfaceflinger: Add all display connections to connection list.
- Mms: Take into account image rotation.
- MMS app: fix crash when MMSC setting is NULL
- Camera: Allow setting "profile-video-size" before recording starts
- Messaging: Add the ability to mark a message as read from the notification
- Add option to enable/disable Electron Beam Animation
- libsuspend: Correctly handle errors initializing autosuspend, to avoid exceptions later on
- Decode DHCP netmask option correctly
- Fixed an unused param warning
- libnetutils: Fix up the dhcp request arguments
- dhcp_utils: Add -f dhcpcd.conf processing
- vold: Add support for EXT filesystem on sdcard
2013/01/06 - CM10 Lights Fest Edition
- Merged 20130106 CM official sources
- Integrated the latest 20130106 kernel from op
2012/12/28 - CM10 Penguins Galore Edition
- Merged 20121228 CM official sources
- Moar love for the wifi chip (conservative pm by default)
- Fully blinking notification lights (thanks Tonyp for the fix)
2012/12/26 - CM10 After Christmas Edition
- Merged 20121226 CM10 official sources
- Loads of wifi-related fixes (deep sleep, power management, etc)
- Fixed battery animation when phone is off and connected to charger
- Fixed phone doesn't boot when connected to charger
- Added an install step that installs the lgdrm files
2012/12/24 - CM10 Merry Christmas Edition
- Merged 20121224 CM10 official sources
- Added PDroid support ! You asked for it, you got it ;)
- Added an install step that checks if the internal sd is readable/mountable. If not, it formats it automagically
- Removed CMUpdater.apk (thanks Tonyp for the idea)
2012/12/20 - CM10 for the new bootloader initial release
- Merged 20121220 CM10 official sources
- Fixed code to allow booting on the new bootloader
PDroid support thanks to pastime1971 for his patches in this thread and download the PDroid.apk from here
Custom CWM Changelog
Code:
2012/12/30 - Inverted the sdcards order in backup menu. Updated to 2.0.2.6.
2012/12/23 - Updated to version 6.0.2.5
2012/12/22 - Fixed home key not working in recovery
2012/12/21 - Enabled usb mass storage
2012/12/20 - Initial 6.0.1.9 release with fixed partition layout and product info
If you want to see what i did in code, you can find a detailed explanation here: http://forum.xda-developers.com/showpost.php?p=35736099&postcount=175
This recovery works perfectly fine also to flash Carburano's DJ X, civato's ICS with aroma installer and the upcoming cm10.1 (for new layout) from Imperticus. Tested personally going back and forth between my cm10 and the ones listed and all went smooth.

Whola..
I m gonna try this...
.
One question, recovery is modified, so it can use to flash other roms like topogigi or we need to change revovey again for those roms ?

RohanAJoshi said:
Whola..
I m gonna try this...
.
One question, recovery is modified, so it can use to flash other roms like topogigi or we need to change revovey again for those roms ?
Click to expand...
Click to collapse
Better if you revert to the one that came with the rom originally. It's in the nvflash pack.
The recovery is not really modified at code level, only how it presents the phone to the updater script so that cm10 installer doesn't complain.
I'm working to adapt the zip to the ics recovery, but it's taking a while... in the meantime this recovery is the only one guaranteed to work correctly for this cm10 version
Edit: updated OP. Tested with carburano's and civato's ics roms and they both flash correctly with this recovery

Cool. Will try this. Thanks pengus!
Sent from my LG-P990 using xda app-developers app

Sorry, but is cm10 or cm10.1 rom?

Can we flash moded 4.1.2 - > 4.2 Gapps to this?
Sent from my LG-P990 using xda premium

Is it possible to go from LG Official V30a to this? if yes, how please as i dont have the Boot Recovery mode on it after smartflashing Official V30a, please guide me...

kamiar said:
Is it possible to go from LG Official V30a to this? if yes, how please as i dont have the Boot Recovery mode on it after smartflashing Official V30a, please guide me...
Click to expand...
Click to collapse
Are U blind or just too layzy:
"
If you come from a GB Bootloader (cm7/9/10 - stock gb):
1) place the cm10 zip attached to this post in the external sdcard of your phone.
2) grab one of the ICS roms out there (Django Manouche X, TG P990 ICS V30A, or whatever you prefer based on V28 or V30).
3) replace the recovery.img file in the folder of the rom you downloaded with the one attached in this post.
4) nvflash the rom you chose following the instructions on the relative pages and let the phone boot fully (so it formats your internal sdcard correctly).
5) after first boot, shutdown the phone.
6) turn on the phone and boot it to recovery by holding power and volume down.
7) flash the zip file you previously slapped in the external sd card.
"
This should work for U

someone has already tried it? Some news regarding the call bug?

kamiar said:
Is it possible to go from LG Official V30a to this? if yes, how please as i dont have the Boot Recovery mode on it after smartflashing Official V30a, please guide me...
Click to expand...
Click to collapse
I think you need to unlock the bootloader first then root then install the appropriate CWM for the new bootloader. Then follow the instruction in OP for those already in new bootloader.

with the ADB/terminal command, do we typr it all in one go ?

If new CM10 out (or CM10.1) can we flash it instant or need to make something change before flash other rom?

Oh noo are you serious this rom is out? I think I have to take a day off because this rom will answer one BIG question! Damn nice work, thanks a lot for all the efforts.

You Need to change your phone partition layout.
k101d said:
If new CM10 out (or CM10.1) can we flash it instant or need to make something change before flash other rom?
Click to expand...
Click to collapse
You cant flash cm10 directly on Ics patition layout, as cm10 still works on old GB layout, so u need to go back to nv flash GB or use nvflash toolkit. :angel:

hellraiser said:
You cant flash cm10 directly on Ics patition layout, as cm10 still works on old GB layout, so u need to go back to nv flash GB or use nvflash toolkit. :angel:
Click to expand...
Click to collapse
OK get idea I check the updater-script both origainal CM10 and the new mod for this ICS partition layout and found mounting point different SO I think if I want to flash anyrom into this ICS partiotion layout I will try to edit updater-script.

call bug resolved?

anjo88 said:
call bug resolved?
Click to expand...
Click to collapse
Most important thing of this rom is we can enjoy the pink LG logo while booting CM10. Less important is the call bug, hopefully it's fixed too=)
Well, that's what this is all about isn't it?:laugh: Can't really say, but we all hope! Just installed, CM10 is damnnn SMOOTHH compared to 30A

x_justin said:
Most important thing of this rom is we can enjoy the pink LG logo while booting CM10. Less important is the call bug, hopefully it's fixed too=)
Well, that's what this is all about isn't it?:laugh: Can't really say, but we all hope! Just installed, CM10 is damnnn SMOOTHH compared to 30A
Click to expand...
Click to collapse
Yea it is faaasssttt I will today make a bunch of calls just to be sure

[KERNEL][SINGLE/DUAL BOOT][JB/KK][STOCK/CM]blackhawk's NEXT kernel 2.4

NEXT 2.1.8 placeholder: http://forum.xda-developers.com/showpost.php?p=51678768&postcount=2513
STOP! This kernel supports ONLY Samsung Jelly Bean 4.1.x, 4.2.2, CM 10.1.x, 10.2, and 11.0. It won't work on ICS, CM 9, CM 10.
FOR NOW I FORBID ANYONE ELSE REUSE THIS STILL IN DEVELOPMENT DUAL BOOT PROJECT FOR HIS/HER OWN GALAXY TAB 2 PROJECT!
STOP PRESS:
NEXT 2.x separated in two package: the kernel part as blackhawk-next-kernel-2.x-p31xx.zip and the proprietary binaries part as proprietary-vendor-samsung.zip for JB >= 4.2 and proprietary-vendor-samsung-4.1.x.zip for JB 4.1.x .
Flash the kernel part first and then directly the proprietary binaries part! Flash the appropriate proprietary part on both 1st and 2nd ROM!
Sources:
Kernel sources at http://github.com/kumajaya/android_kernel_samsung_espresso10/tree/cm-10.2-update
Features:
Samsung stock 4.1.x, 4.2.2 (since 1.8), CM 10.1.x and CM 10.2 (since 1.7) support with a single kernel image
For stock ROM: external SD card - internal media swapper script included
Samsung proprietary exFAT modules are loaded. CM 10.1 exFAT support files attached at post #2
For CM/CM based ROM: auto rotate screen default orientation depend on ro.sf.hwrotation value, camera orientation fix included
Dual-booting. You can have Samsung JB and CM 10.1 ROMs on a single device at the same time.
Nice looking AROMA based boot menu
Using CyanogenMod kernel source, updated to p3110 source for newer WLAN (Youtube HD bugfix on stock ROM), modem, sensors driver, and etc for both P31xx and P51xx target
CPU clock: 300MHz, 600MHz, 800MHz, 1.008GHz, 1.2GHz, 1.35GHz, 1.42GHz, 1.48GHz, and 1.52GHz, locked @ 1.008GHz on boot
GPU clock: 153.6MHz, 307.2MHz, 384MHz, and 512MHz, 307.2MHz as the default maximum clock
CPU voltage control. You can use Android Tuner/System Tuner/Trickster MOD to set CPU voltage
The ramdisk base on JB 4.1.2 (stock ROM) and JB 4.2.2 (CM 10.1)
Using newer PowerVR SGX 540 kernel modules and binaries blob
row, bfq, sio, and vr scheduler support
Governor bug fix. Replace Samsung's interactive governor with default OMAP4 3.0.31 interactive governor from omapzoom.org, plus pegasusq and lulzactive
NFS and CIFS/samba (not loaded by default) filesystem support
LZMA compressed initrd, to keep boot image smaller than 8MB
swap support. zram and cleancache with a working zcache driver, enabled by default
kernel config, insmod configs.ko and then you can access /proc/config.gz
external modem support, for PPP Widget (not loaded by default, P31xx need powered USB hub for external modem)
Some tweaks from gokhanmoral's siyahkernel for S3, passive entropy tweak applied
Remove a lot of debug message from touchscreen driver, display, mmc, modem, etc
linaro arm-linux-gnueabihf- cross compiler, compiler optimization applied
SuperSU v1.41 for stock ROM
Self compiled BusyBox v1.22.0-git in /sbin, config file based on CM's BusyBox bbconfig output. fstrim applet patch applied, android_reboot applet added (a quick but clean port from Android toolbox), swapon applet with priority option. For stock ROM: this version of Busybox will overwrite busybox binary in /system/bin or /system/xbin and save it as busybox.backup
Early boot scripts support (/system/etc/init.d, /data/local/userinit.sh, and /data/local/userinit.d)
Post boot script support (/system/etc/init.post_boot.sh)
For stock ROM: custom boot animation support (/data/local/bootanimation.zip or /system/media/bootanimation.zip if exists, Samsung boot animation as a fallback). If a bootanimation.zip found, the boot sound will be turned off as well as the shutdown animation.
Modified mount options
adb insecure, adb mode in charge state also insecure
Advanced TCP congestion support, westwood as the default congestion
No /system/etc/hosts patch, you can install AdAway from F-Droid
Known Problems:
Thanks To:
gokhanmoral, amarullz, Phil3759, Chainfire, cmenard, codeworkx, imoseyon, coolbho3k, Faux123, AuxLV, CodyF86, poppolo2001
This part will be expanded. Most of the patches I applied are coded by someone else. Please remind me if I forget to give credits to anybody...
Downloads:
PhilZ Touch 5.08.5: http://forum.xda-developers.com/showthread.php?t=2202667
Todo:
More features in NEXT tool
Special Thanks:
@trssho91, @Caldair, @fast96, @Jellydroidkin, @Android-Andi, @nakbaliNe, @Bhaskara Rao, @tsatomas
Downloads Record:
blackhawk-next-kernel-1.0-p31xx.zip: 316
blackhawk-next-kernel-1.1-p31xx.zip: 87
blackhawk-next-kernel-1.1-addon-nooc-p31xx.zip: 41
blackhawk-next-kernel-1.2-p31xx.zip: 503
blackhawk-next-kernel-1.2-addon-nooc-p31xx.zip: 160
blackhawk-next-kernel-1.3-p31xx.zip: 240
blackhawk-next-kernel-1.3-addon-nooc-p31xx.zip: 112
blackhawk-next-kernel-1.4-p31xx.zip: 583
blackhawk-next-kernel-1.4-nooc-p31xx.zip: 294
blackhawk-next-kernel-1.6-p31xx.zip: 380
blackhawk-next-kernel-1.6-nooc-p31xx.zip: 227
blackhawk-next-kernel-1.6.1-p31xx.zip: 180
blackhawk-next-kernel-1.6.1-nooc-p31xx.zip: 90
blackhawk-next-kernel-1.6.2-p31xx.zip: 151
blackhawk-next-kernel-1.6.2-nooc-p31xx.zip: 81
blackhawk-next-kernel-1.5-p31xx.zip: 600
blackhawk-next-kernel-1.5-nooc-p31xx.zip: 304
blackhawk-next-kernel-1.8.1-p31xx.zip: 222
blackhawk-next-kernel-1.8.1-nooc-p31xx.zip: 99
blackhawk-next-kernel-1.8.2-p31xx.zip: 577
blackhawk-next-kernel-1.8.2-nooc-p31xx.zip 321
XDA:DevDB Information
[KERNEL][SINGLE/DUAL][JB/KK][STOCK/CM]blackhawk's NEXT kernel, Kernel for the Samsung Galaxy Tab 2
Contributors
ketut.kumajaya, Android-Andi
Kernel Special Features: Dual boot stock and AOSP based ROM
Version Information
Status: Stable
Current Stable Version: 2.3
Created 2014-09-21
Last Updated 2014-10-11

NEXT 2.x separated in two package: the kernel part as blackhawk-next-kernel-2.x-p31xx.zip and the proprietary binaries part as proprietary-vendor-samsung.zip for JB >= 4.2 and proprietary-vendor-samsung-4.1.x.zip for JB 4.1.x .
Changelog:
21/04/2014 2.2:
Flash-Friendly File System (f2fs) support
Full github commits 8/4 - 20/4/2014: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-11.0
Update proprietary blobs, proprietary-vendor-samsung-update.zip
02/01/2014 2.1.5 -> 2.1.6:
CM 11.0 support
28/10/2013 2.1.4 -> 2.1.5:
Updated to upstream 3.0.101 kernel
Audit and SELinux enabled
Smartreflex completely disabled
GPU frequencies not exposed to STweaks bug fixed
Do not load exFAT modules on CM 10.2
Full changelog: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.2-update
27/10/2013 2.1.3 -> 2.1.4:
Ramdisk updated to sync with latest CM 10.2
20/10/2013 2.1.2 -> 2.1.3:
Update init script for PAC
Disable almost all kernel debugging support except KALLSYMS. Kernel failed to boot with CONFIG_KALLSYMS disabled
28/09/2013 2.1.1 -> 2.1.2:
Turn all CPUs online when governor gets changed, hotplug bug workaround
SIO and VR I/O scheduler
Initial STweaks support, big thanks @gokhanmoral. Download STweaks app from Play store to access almost all NEXT related settings (CPU governor, frequency, and voltages; GPU governor and frequency limit; surfaceflinger rotation; I/O scheduler; logger; CIFS, Xbox controller, and USB modem support; and dual boot related settings).
22/09/2013 2.1 -> 2.1.1:
Update overclock codes, remove gpu_oc interface: https://github.com/kumajaya/android...mmit/94ac45a10213de400c7bf3c01b5c5b052ae8ba18
sgxfreq: add sysfs interface to store frequency limit: https://github.com/kumajaya/android...mmit/738061b30d2278d3b51b341bc2597dad300f4e47
sgxfreq: limit frequency to default on boot: https://github.com/kumajaya/android...mmit/8a6933cf6565b5587db6a2a5ce7b1207807ab701
The latest Android Tuner app needed to control the modified OMAP GPU control interface but the dirty way by editing /etc/init.post_boot.sh always available
18/09/2013 2.0 -> 2.1:
Separated vendor blobs for JB 4.1.x and JB >= 4.2, @poppolo2001 fix applied
With CPU and GPU overclock, CPU under/over voltage, upstream kernel 3.0.96 by @CodyF86
Complete changelog: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.2-update
02/09/2013 1.8.3 -> 2.0:
Vendor blobs in separated flashable zip, taken from Samsung 4.2.2. Flash proprietary-vendor-samsung.zip directry after flashing NEXT kernel 2.0 on both 1st and 2nd ROM!
Ten seconds boot menu timeout. Boot to the latest booted ROM when timeout periode reached. Finally, my trick works :victory:
Using Samsung P3110 Update1 kernel source: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=p3110 . Patched to comply CM/AOSP need and NEXT dual boot, without SELinux and audit support, gcc linaro compiler. Kernel source: https://github.com/kumajaya/android_kernel_samsung_espresso10/tree/cm-10.2
Samsung open source exFAT kernel modules included, source: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=exfat
Without CPU or GPU overclock
Without extended CPU governor or I/O scheduler
Without swap or zram support
AROMA 2.70 beta 6 binary
13/08/2013 1.8.2 -> 1.8.3:
Samsung 4.2.2: The first attemp to reduce battery draining issue, zram service disabled! You can enable zram (not as a service) by issuing "setprop persist.service.zram 25" over Terminal Emulator or "adb shell". Reboot is required.
CM 10.2: Bluetooth tethering fix from upstream CM 10.2
07/08/2013 1.8.1 -> 1.8.2:
The third attemp to support Samsung 4.2.2 for all device configuration
Vendor blobs in separate flashable zip updated, please re-download it!
06/08/2013 1.8 -> 1.8.1:
The second attemp to support Samsung 4.2.2 for all device configuration
Vendor blobs in separate flashable zip. For all ROMs, on both 1st and 2nd ROM: Flash vendor-blobs-new-ducati-blackhawk.zip directry after flashing NEXT kernel!
Single channel sound output bug fix
05/08/2013 1.7 -> 1.8:
Initial Samsung 4.2.2 support
Updated to upstream Linux kernel 3.0.41 (incremental patch)
https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.1-blackhawk 1-2 Aug 2013
The first kernel utilizing the new ducati firmware, the first kernel preserved 815.8MB RAM! Don't forget to flash vendor-blobs-old-ducati-blackhawk-p31xx.zip if you switch to another kernel
01/08/2013 1.6.3 -> 1.7:
Initial CM 10.2 support. Do not flash blackhawk-next-cm-exfat-vold.zip! CM 10.2 already has an open source/reverse engineered exFAT filesystem support
zram switched to zsmalloc, zram optimized for Android disabled
XBox 360 USB controller with BigX LED support enabled (by @iks8 request). Modules not loaded by default, edit /system/etc/init.d/02modules to activate it.
23/07/2013 1.6.2 -> 1.6.3:
Add android_reboot applet to NEXT's busybox (a quick port from Android toolbox) to fix AROMA boot menu fail to boot into recovery/bootloader as reported by @kinung
I hate bug!
22/07/2013 1.6.1 -> 1.6.2:
Hotplug CPU governor working properly with cleancache enabled, zcache memory corruption problem fixed!
21/07/2013 1.6 -> 1.6.1:
Hotplug CPU governor kernel panic bug fix. This governor not working properly with cleancache enabled, cleancache disabled for now
Static linked busybox compiled from source, fstrim patch applied. Busybox config based on CM's busybox bbconfig output. Total 46 more than previous busybox applet, add priority option to swapon applet
zRAM swap per CPU core, same priority value. CM's /system/bin/compcache script updated to handle 2 zRAM devices. Reference: http://wiki.gentoo.org/wiki/Zram
Stock ROM persist.customboot.zram property changed to persist.service.zram, follow CM's standard
Stock ROM default zRAM size changed to 26% RAM size
Swappiness value changed to 90
18/07/2013 1.5 -> 1.6:
LZO compression updated to current upstream version, optimized for arm. Reference: http://git.kernel.org/cgit/linux/ke.../?id=b0af9cd9aab60ceb17d3ebabb9fdf4ff0a99cf50
zRam support optimized for Android, utilizing the new lzo library. Set 18% of RAM as zRam swap file. CM user can use CM's Settings - Performance options.
cleancache support with working Zcache driver, utilizing the new lzo library
entropy threshold tweaks, /dev/random linked to /dev/urandom
github 14-18/07/2013 commits: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.1-blackhawk
11/07/2013 1.4.1 -> 1.5:
Decrease CPU voltage for frequencies below 1.2GHz, increase CPU voltage for frequencies above 1.2GHz
Re-enable MMC_CAP_ERASE for I/O speed improvement, run "fstrim -v /data" and "fstrim -v /cache" manually to TRIM your filesystem or run LagFix (fstrim GUI, download it from Play)
Remove my old hack in cpufreq driver
Newer PowerVR SGX540 3D kernel module and vendor binaries, in sync to CM-10.1. For dual boot user, you must update both 1st and 2nd ROM to renew both ROM vendor binaries!
Change screen_off_max_freq from 1.008GHz to 800MHz, small changes in init scripts
SuperSU v1.41
16/06/2013 1.4 -> 1.4.1:
I/O speed improvement, 1.3 and 1.4 bugfix
SuperSU v1.34 - thanks Chainfire
nooc: Smartreflex class 3 re-enabled, voltage control disabled
small update to disable swap support by default for my "stock based ROM" included
04/06/2013 1.3 -> 1.4:
Selected kernel modules, scripts, and binaries integrated in boot.img, single flash for 1st and 2nd ROM
Kernel compression back to gzip, boot.img compression switched to lzma for better compression (I need more space)
Auto root (for stock)
Auto busybox (for stock)
Auto rotate (for both stock and CM) depend on ro.sf.hwrotation value, camera orientation fix included
External sdcard and internal media swapper script integrated in boot.img (for stock as 1st ROM)
Override init.d CPU governor setting on boot completed (technical reason/by design). Please use an app "on boot" or /etc/init.post_boot.sh to set CPU governor
init script reworked (again), simplified
Standalone nooc version, no longer as an addon for standard NEXT
Untested CRT off animation support
01/06/2013 1.2 -> 1.3:
Updated compiler to the latest linaro gcc 4.7
Better data integrity on both 1st and 2nd ROM
Ramdisk init scripts reworked, inline with the latest Samsung (Taiwan BRI 04/2013) and CM (29/05/2013 nightly)
Inline with P51xx port
Updated exFAT modules (don't know it's better or worse, it's closed source)
Default CPU clock still 1.008GHz, default GPU clock 307.2MHz
1.1 -> 1.2:
Potential bug in sdcard swapper script fixed. Yes, for stock ROM as 1st ROM this kernel still has a script to swap external sdcard - internal media.
SuperSU updated to the latest version (stock ROM).
1.0 -> 1.1:
exFAT filesystem support, stock ROM only for now. I will share separate flashable zip for CM 10.1, when it's ready (broken USB storage support). Please note Dual Boot FAQs #24!
CGROUPS, SLUB, and TRACING support back enabled for exFAT compatibility, Android logger disabled by default to compesated it. You can enable logger by editing /system/etc/init.d/02modules .
No boot menu in single ROM environment.
Change stock ROM init.d script starting point. Earlier than before, same as CM 10.1 now.
Non overclock addon for anyone who is experiencing overheats when using standard NEXT kernel.
Source change: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.1-blackhawk, May 24-26, 2013. A lot of undocumented change in ramdisk side.
exFAT support in CM 10.1
Download and flash blackhawk-next-cm-exfat-vold.zip over recovery
fsck.exfat, mkfs.exfat, vold binaries and all needed libraries taken from Samsung JB 4.2.2 included
USB storage support is broken, you need USB OTG Helper from http://forum.xda-developers.com/showthread.php?t=1588940 as 3rd party USB storage mounter
exfat binaries for exfat support in USB OTG Helper included. So, all USB OTG Helper features (FAT, Ext2/3/4, full NTFS, and exFAT support) enabled
To avoid Dual Boot FAQs #24 issue, flash blackhawk-next-cm-exfat-vold.zip and NEXT kernel of course directly after CM update. For CM 10.1 only!
Download Record:
proprietary-vendor-samsung.zip: 4481
proprietary-vendor-samsung-4.1.x.zip: 1478

Dual Boot FAQs
Dual Boot FAQs
Adapted from droidphile's "Dual Boot FAQs" with permission.
1. "Why would I wanna dual-boot?"
A. You don't have to.
Suppose you're more of an aosp rom fan. But misses the HDMI out, bluetooth hands-free and love sammy camera more. Do a minimal installation of sammy rom and boot into it when in need of these features and use aosp rom otherwise.
Or you are a sammy rom fan but love the responsiveness and pure android feel of aosp roms.
And while you can dual boot two sammy or two aosp roms, it doesn't make any sense.
2. "What if I don't need dual booting?"
A. No issues. Kernel won't force to setup 2 roms. You can single boot as before.
3. "Will dual booting change my bootloader or do any dangerous stuff like setting my phone on fire?"
A. NO. Changes are at kernel and ramfs level only. Some space in your internal sd card is used, and also the unused hidden partition mmcblk0p11 is used to store cache of second rom. Dual booting doesn't repartition the filesystem or perform anything scary.
4. "I want to setup dual booting."
A. There are four situations:-
1) Sammy rom now. Want to use aosp as secondary.
2) Sammy rom now. Want to use aosp as primary.
3) Aosp rom now. Want to use sammy as secondary.
4) Aosp rom now. Want to use sammy as primary.
Prerequisites for any setup is
a) Flash latest blackhawk's NEXT kernel
b) Flash new ducati vendor blobs (since 1.8.x)
c) Flash latest PhilZ Touch - blackhawk repack version - recovery
d) Atleast 90% battery left.
e) 2 GB free on internal SD.
f) Some spare time
1) Present sammy, setup aosp as secondary:-
i) Reboot into recovery
ii) Flash blackhawk's NEXT tool, create system.img for CM/CM based ROM and then close it
iii) Reboot into secondary recovery
iv) Flash aosp ROM as 2nd ROM
v) Flash blackhawk's NEXT kernel again
vi) Flash new ducati vendor blobs again (since 1.8.x)
2) Present sammy, setup aosp as primary:-
i) Reboot into recovery
ii) Nandroid backup your current sammy ROM
iii) Flash blackhawk's NEXT tool, create system.img for Samsung stock/stock based ROM and then close it
iv) Reboot into secondary recovery
v) Nandroid restore your sammy ROM as 2nd ROM
vi) Flash blackhawk's NEXT kernel again
vii) Flash new ducati vendor blobs again (since 1.8.x)
viii) Reboot into primary recovery
ix) Flash aosp ROM as 1st ROM
x) Flash blackhawk's NEXT kernel again
xi) Flash new ducati vendor blobs again (since 1.8.x)
3) Present aosp, setup sammy as secondary:-
Same as (1), instead of flashing aosp to second, flash sammy to second.
4) Present aosp, setup sammy as primary:-
Same as (2), instead of flashing aosp to first ROM, flash sammy.
NOTE:
-To dual boot Two Aosp or Two Sammy roms, just follow (1) or (2) (depending on which one of them you want as primary/secondary), just flash Sammy instead of aosp or aosp instead of sammy.
5. "What things should I be taking care off while dealing with dual booting?"
A. - Make sure where you are: in primary or secondary recovery.
6. "How to boot into primary rom?"
A. AROMA based boot menu will help you on every boot.
7. "How to boot into secondary rom?"
A. AROMA based boot menu will help you on every boot.
8. "Is kernel partition shared?"
A. Yes. Same kernel boots both roms.
9. "If I flash another kernel (that doesn't support db) do I lose dual booting?"
A. Yes
10. "I lost dualbooting after flashing another kernel. I didn't do anything to second rom files in sdcard/.secondrom. How can I get db back?"
A. Just flash the latest blackhawk's NEXT kernel, flash new ducati vendor blobs again (since 1.8.x)
11. "Will there be any performance degradation on the rom used as secondary compared to primary?"
A. NO
12. "Will my phone run slow overall because of db?"
A. NO
13. "How to flash a newer version of 1st rom?"
A. As usual, just flash it from primary recovery. Flash blackhawk's NEXT kernel again, flash new ducati vendor blobs again (since 1.8.x)
14. "How to flash newer version of 2nd rom?"
A. Just flash it from secondary recovery. Flash blackhawk's NEXT kernel again, flash new ducati vendor blobs again (since 1.8.x)
15. "Would upgrading 1st or second rom cause other rom to fail on boot?"
A. No. Partitions of other rom are not touched during upgrading.
16. "I miss the recovery I used before, so much.."
A. PhilZ Touch not bad at all.
17. "User apps of 1st rom are automatically available for second rom?"
A. NO. However, if you had backed them up using Titanium Backup or similar apps, just restore apps while on second rom.
18. "I wanna keep separate backup for apps in both the Roms, since I use one Rom for say entertainment and other productivity."
A. Setup different backup directory in Titanium Backup in 1st and 2nd rom.
19. "I don't see STweaks app in second rom."
A. This is blackhawk's NEXT dual boot solution for Galaxy Tab 2, a free implementation of gokhanmoral's Siyah dual boot.
20. "Do I need to anything special before flashing a newer blackhawk's NEXT kernel?"
A. NO. Just flash kernel in primary and secondary recovery. Yes, on both 1st and 2nd ROM. Just flash kernel in recovery - whichever you used to do. Kernel image is copied to the unified kernel partition (since 1.4 version). Flash new ducati vendor blobs (since 1.8.x) on both ROM may be required to ensure vendor blobs match to the kernel
21. "How can I run same STweaks settings of 1st Rom in 2nd Rom?"
A. This is blackhawk's NEXT dual boot solution for Galaxy Tab 2, a free implementation of gokhanmoral's Siyah dual boot.
22. "How do I remove everything related to DB and run single boot again?"
A. In primary recovery, flash blackhawk's NEXT tool and delete 2nd ROM system image. OR delete .secondrom directory in /data/media while on 1st Rom.
23. "If secondrom files are kept in /data/media, will wiping data in recovery erase second rom files?"
A. NO. /data/media is skipped in CWM recovery.
24. "I was using ExFat card on sammy rom without any issues. I have setup dual boot with aosp and now after booting into CM it says microSD card is corrupted."
A. Aosp roms doesn't support ExFat out of the box. The data was corrupted by aosp vold. Even if you boot back to Sammy rom, it still would be corrupted. To recover data, manually mount the card in recovery, copy contents to internal SD and reformat card to a Fat32.
Also try
chkdsk X: /f (where X is the drive letter of microsd), you may be able to copy data.
25. "I read somewhere that both rom data partition use the same space. Doesn't that mean my apps are shared across roms?"
A. NO. It just means they uses same partition. They're still different directories.
1st rom data = /data
2nd rom data = /data/media/.secondrom/data
26. "Will hitting "Boot into Secondary Recovery" in recovery boot menu change my recovery?"
A. NO. It just runs (not flash) an alternate recovery so that you can configure dualboot settings.
27. "How do I backup 1st Rom and 2nd Rom?"
A. To backup 1st Rom, do what you did to backup rom while you were single booting a while ago.
To backup 2nd Rom, use the secondary recovery.
28. "Is there an easier way for dual-boot?"
A. Yes, send your device to me.
29. "DB architecture?"
A. Like you know, every rom has a /data, /system, /cache partition and a kernel to boot.
For primary rom, it's
mmcblk0p10 = /data
mmcblk0p9 = /system
mmcblk0p7 = /cache
And these won't change whether you're single booting or dual booting.
For secondary rom, data and system is stored in internal sd, cache in hidden partition. Note that internal sd in our device is mounted to /data/media.
We have data as a directory, System as an image in data/media/.secondrom. Cache in mmcblk0p11 which is hidden partition and not used otherwise.
- When second rom is booting, second rom data is bind mounted to mmcblk0p10 as /data/
- data/media/.secondrom/system.img partition is mounted as /system.
- mmcblk0p11 is mounted as /cache.
More FAQs will be added and the list will be updated as DB is improved.

Dual Boot Exercises
Exercise I
An example current facts:
ROM: Samsung stock JB 4.1.2
Kernel: blackhawk single kernel
Recovery: PhilZ Touch prior version
Prerequisites step:
Update your kernel to blackhawk's NEXT kernel
Update your recovery to the latest PhilZ Touch - blackhawk repack version - recovery
Download CM latest nightly + GApps zip
~2GB free on internal storage
Dual boot step:
Reboot into recovery
Flash blackhawk's NEXT tool, create system.img for CM/CM based ROM and then close it
Reboot into secondary recovery, make sure you choose "Secondary Recovery"! Make sure you really choose "Secondary Recovery"!!
Flash CM
Flash GApps zip
Reflash blackhawk's NEXT kernel
Reboot into secondary ROM - CyanogenMod!
It's always better if you make a backup before performing all above steps. Do it at your own risk!
Exercise II
An example current facts:
ROM: CM 10.1 latest nightly
Kernel: blackhawk single kernel
Recovery: PhilZ Touch prior version
Have Samsung stock 4.1.2 nandroid backup
Prerequisites step:
Update your kernel to blackhawk's NEXT kernel
Update your recovery to the latest PhilZ Touch - blackhawk repack version - recovery
Nandroid backup your current CM 10.1 ROM
~2GB free on internal storage. I am not sure, depend on your backup data size
CM 10.1 as 2nd ROM:
Reboot into recovery
Flash blackhawk's NEXT tool, create system.img for CM/CM based ROM and then close it
Reboot into secondary recovery, make sure you choose "Secondary Recovery"! Make sure you really choose "Secondary Recovery"!!
Restore CM 10.1 nandroid backup
Format /cache, clean dalvik-cache
Reflash blackhawk's NEXT kernel
Reboot into secondary ROM - CyanogenMod!
Samsung 4.1.2 as 1st ROM:
Reboot into primary recovery, make sure you choose "Primary Recovery"! Make sure you really choose "Primary Recovery"!!
Restore Samsung stock 4.1.2 nandroid backup
Format /cache, clean dalvik-cache
Reflash blackhawk's NEXT kernel
Reboot into primary ROM - Samsung!
Do all above steps at your own risk!

Just opened a new thread for my masterpiece work on Galaxy Tab 2. Enjoy it and don't forget to press my Thanks button
PhilZ Touch attached in post #1 has a "red" on screen navigation bar in secondary recovery to distinguish between primary and secondary :laugh:
08/08/2013: Kernel for stock 4.2.2 Developtment Secret
If you want to build your own kernel for stock 4.2.2, this is the development secrets how to fix CPU frequency jumping to maximum available frequency, how to fix slow graphics issue, how utilize the new ducati firmware and increase the RAM space, how to fix hardware accelerated media problem and how to fix WiFi tethering issue.
Kernel source: http://github.com/kumajaya/android_kernel_samsung_espresso10/tree/cm-10.1-blackhawk
Samsung kernel update: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=p3110
Samsung exFAT source: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=exfat
How to fix CPU frequency jump to maximum available frequency (1.52GHz, overclock version) on boot
Rename /system/lib/hw/power.default.so to /system/lib/hw/power.default.so.bak, copy power.piranha.so from NEXT kernel 1.8.2 package to /system/lib/hw
How to fix slow graphics issue
This solution authored by @codeworkx 8 moths ago but disabled by default: https://github.com/kumajaya/android...mmit/0c6d1a53f1a51b588786b168a48e2566f8a49065 Enabling both FB_OMAP2_VSYNC_SEND_UEVENTS and FB_OMAP2_VSYNC_SYSFS solve this problem
How utilize the new ducati firmware and increase the RAM space
How to fix hardware accelerated media problem
How to fix WiFi tethering issue
If you use above information, proper credit must be given including a clear text about this solution.
21/09/2013: OMAP PowerVR 3D GPU Control
There some interface inside /sys/devices/platform/omap/pvrsrvkm.0/sgxfreq:
frequency interface to access the current GPU frequency (153600000/307200000/384000000)
frequency_list interface to access supported GPU frequencies (153600000 307200000 384000000)
frequency_limit interface to access the GPU maximum frequency limit (default: 307200000). Writeable mean this code inside the pvrsrvkm kernel module, the GPU maximum frequency controllable
governor interface to access the current GPU governor (userspace/on3demand/activeidle/onoff)
governor_list interface to access supported GPU governor (userspace on3demand activeidle onoff)
The upcoming version of Android Tuner (0.10.2) support OMAP GPU controls.
21/09/2013: NEXT 2.0.1
As I mentioned before, I still continued cm-10.2 branch kernel development. This branch is the source code of NEXT 2.0, I've added overclock support but limited at 1.2GHz CPU and 384MHz GPU. OMAP GPU controls support applied as gpu_oc interface replacement. Kernel attached here as blackhawk-next-kernel-2.0.1-p31xx.zip .
Changelog:
Rewriting overclock code: https://github.com/kumajaya/android...mmit/35e0c0455cb7ae4beb50375c5873b328a76a1087
Add sysfs interface to store GPU frequency limit: https://github.com/kumajaya/android...mmit/738061b30d2278d3b51b341bc2597dad300f4e47
Limit GPU frequency to default on boot: https://github.com/kumajaya/android...mmit/8a6933cf6565b5587db6a2a5ce7b1207807ab701
Xpad force feedback support disabled
WARNING: This kernel only for device that can handle 1.2GHz CPU and 384MHz GPU frequency.

ketut.kumajaya said:
Just opened a new thread for my masterpiece work on Galaxy Tab 2. Enjoy it and don't forget to press my Thanks button
Click to expand...
Click to collapse
Now Im very confuse. Which one to use? Im on CM10.1 4.2.2 Lastet update.. GT P3110..which kernel should I install? what is the different between KK and Philz Touch?

Fotonista said:
Now Im very confuse. Which one to use? Im on CM10.1 4.2.2 Lastet update.. GT P3110..which kernel should I install? what is the different between KK and Philz Touch?
Click to expand...
Click to collapse
There is no confusion at all...
Every file you need is in the first post: kernel, tool and Philz. Don't use anything else.
Read the examples. All information is in there...
I don't know about the differences between KK and Philz, but I don't care though... Philz is just great!
Many, many respects to ketut...
Big thanks for your efforts...
Sent from my GT-P3110 using xda app-developers app

Fotonista said:
Now Im very confuse. Which one to use? Im on CM10.1 4.2.2 Lastet update.. GT P3110..which kernel should I install? what is the different between KK and Philz Touch?
Click to expand...
Click to collapse
PhilZ Touch is a recovery image, NEXT kernel is a boot image, KK-Boot discontinued project.

Ketut @ awesome work with awesome guide.. U explained each n every step clearly for freshers.. N BTW do I need to update Blackhawk next kernel to 1.0..if yes, wiping cache n delvk is necessary before flashing? I am asking u cos I Dnt want to be in mess anymore.. I am happily enjoy dual boot environment.. Thanks again for all the effort..
Sent from my GT-P3100 using xda premium

god_creature said:
Ketut @ awesome work with awesome guide.. U explained each n every step clearly for freshers.. N BTW do I need to update Blackhawk next kernel to 1.0..if yes, wiping cache n delvk is necessary before flashing? I am asking u cos I Dnt want to be in mess anymore.. I am happily enjoy dual boot environment.. Thanks again for all the effort..
Sent from my GT-P3100 using xda premium
Click to expand...
Click to collapse
Yes. Fixed the problem when installed CM 10.1 directly as 2nd ROM. No wipe needed.

Please let me ask a question here.
I have already asked in Philz's thread but no answer till now.
Can Philz restore backups made within cwm?
I already have some backups from cwm times and if Philz could restore them that would save me a lot of time. Of course I could just try and see, but that information would be usefull to have before starting in advance.
Please, ketut, any information on that?
Sent from my GT-P3110 using xda app-developers app

dimfil said:
Please let me ask a question here.
I have already asked in Philz's thread but no answer till now.
Can Philz restore backups made within cwm?
I already have some backups from cwm times and if Philz could restore them that would save me a lot of time. Of course I could just try and see, but that information would be usefull to have before starting in advance.
Please, ketut, any information on that?
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
Compatible: http://forum.xda-developers.com/showthread.php?t=2201860

ketut.kumajaya said:
Compatible: http://forum.xda-developers.com/showthread.php?t=2201860
Click to expand...
Click to collapse
Great!
It's a lot of pages. I can't find it right away, but your answer is enough for me! So, they are compatible.
I will try and report if necessary.
Sent from my GT-P3110 using xda app-developers app

This great work Ketut, thanks for giving us easy way to dual boot. Keep up the good job.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ketut, congrats on your new achievement !
Just one quick question : Can you post all the features (other than dual-boot ability) of this blackhawk-next-kernel on first post ? Or the features are still the same with this :
ketut.kumajaya said:
This is [BOOT IMAGE][GT-P31XX] KK-Boot - Custom boot image for stock 4.1.1/4.1.2 ROM and [KERNEL][GT-P31XX][JB][4.2.2]CyanogenMod 10.1 unofficial kernel 3.0.31 combination, plus cm-10.1-blackhawk commit on github:
Remove Samsung debugging code in ext4 filesystem, inline with omapzoom
Initializing Android USB depending on the rom type, big thanks to gokhanmoral. This is the key of single kernel. Multiboot support not so far, you can reuse my kernel for multiboot (if you can)
Compiler optimizations
Kernel without CGROUPS support
Using SLQB memory allocator
Decrease MPU, IVA, and GPU voltage
Adapt and fix codeworkx's sysfs for controlling pivot mode. This is the key of landscape kernel
Stop the spam from audio driver
An exprimental config, remove a lot of debugging config from kernel: 775MB RAM
Stock JB 4.1.1/4.1.2 ROM: Using a slim version of busybox (from gokhanmoral's ramfs for siyahkernel-sgs3), bash and nano binary, sysrw and sysro script removed. GPU clock @ 384MHz + 2D GPU rendering, stock ROM really need an overclocked GPU.
CM/CM based ROM: As usual, change ro.sf.hwrotation value from 270 to 0 in /system/build.prop will transform your device to landscape mode, a workaround fix for boot animation graphic glitch. GPU clock @ 307MHz + 2D GPU rendering + 16bit transparency + disabled dithering + purging assets allowed
/system/etc/init.post_boot.sh is yours kernel tuning template. But remember, do not force your system too much until you are sure that your device is able to handle it.
Flash this using the latest CWM, CWM Touch, Philz Touch, or TWRP at your own risk!
Click to expand...
Click to collapse
Thank you

distan7 said:
Ketut, congrats on your new achievement !
Just one quick question : Can you post all the features (other than dual-boot ability) of this blackhawk-next-kernel on first post ? Or the features are still the same with this :
Thank you
Click to expand...
Click to collapse
Same kernel, different ramdisk. Thanks for your support :good:

STOP PRESS: Update PhilZ Touch to 5.03.7 http://forum.xda-developers.com/showpost.php?p=39935850&postcount=89!

Oh good news my brother I am happy
Envoyé depuis mon GT-N7100 avec Tapatalk

Couple questions to ketut Please try to answer me - noobie
1) I can flash this for single rom, yes? It should be better than previous version?
2) I can still turn Tab on, press volume down button to boot into CWM?
3) How to turn off the boot menu? (I think I don't need it)

Andrev01 said:
Couple questions to ketut Please try to answer me - noobie
1) I can flash this for single rom, yes? It should be better than previous version?
2) I can still turn Tab on, press volume down button to boot into CWM?
3) How to turn off the boot menu? (I think I don't need it)
Click to expand...
Click to collapse
1. Yes as covered by Dual Boot FAQs. No.
2. Yes.
3. Can not be, maybe the next version. Reboot to recovery and bootloader may be removed for security reasons.

[ROM][UNOFFICIAL][6.0.1][E6653/E6603] CyanogenMod 13 for the Sony Xperia Z5 [ALPHA]

[ROM][UNOFFICIAL][6.0.1][E6653/E6603] CyanogenMod 13 for the Sony Xperia Z5 [ALPHA]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CyanogenMod 13 for the Sony Xperia Z5 E6653 and E6603​
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase
performance and reliability over stock Android for your device.
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be
used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps).
CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Before you start
This ROM is only for the E6653 and the E6603
Code:
*
* Your warranty may be voided !
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
Special Thanks
@CTXz for getting the ball rolling on CyanogenMod for Z5 series and stemming the lion's share to get this working
@oshmoun for providing fixes ASAP
@AndroPlus for providing a great kernel that works with many recoveries
@moonbutt74 for reminding me that smashing your device can provide a solution
@sub77 for teaching me how to work with QCOM (I was on exynos before)
@Joeisgood99 for providing a solid working TWRP-3.0.0.0 build until we had our own
@bazhip for providing a well working twrp 2.8.7.0 for restoring until we had our own
@alphatact1cs has a great overview on lots of topics for the Z5 device family
@auras76 for his great Custom ROM
@infected_ for his experience
Thanks to @mpro420 for help to get Viper4Android working !
Thanks to @jimRnor for Project DiVA SoundMod !
The Sonyxperiadev team for releasing their sources to the public
SonyAOSP team
SonyCM team
Sony Xperia (community) devs
And ofcourse the entire CyanogenMod team!
(Known) Issues
Video Recording
Bluetooth (keeps restarting) (might be fixed, needs feedback + testing)
Camera Colors (can be circumvented by using specific apps CameraNext Mod )
Camera Focus & Sharpness (driver issue, probably since it uses Xperia Z (original) drivers but different lenses ?)
Camera lowlight pictures (might improve with release of Sony's "Experimental AOSP Camera" for the Z5 series, porting of other Framework + Stock Cam app; partially needs DRM magic)
Camera Focus (even with VCM2 actuator changes focus is still kind of murky)
Fingerprint sensor (might work depending on build date of ROM)
Lag after booting up device (Will resolve: lock screen after boot and waiting a few seconds)
Long bootup times & less smoothness with "stock" (prebuilt) kernel
What can not be fixed, changed - aka WONTFIX - NOTOURPROBLEM
There might be potential speed issues with Class 10+ microSD cards not properly being "tuned", in that case switch to slower cards or RMA it which should hopefully solve it. There is a possibility to force slower speeds on cards but that is not really the optimal solution with ultra speed cards and needs further investigation. Samsung (EVO/EVO+) cards, Transcend cards and a few others UHS-I(+) and faster are affected.
What has been Fixed
Horizontal color lines and color glitches during bootup
Gapps
Sudden Lag after some time
NFC
Odd calling numbers
In-call mic
Sound on calls
Camera button
Microphone
Thermal regulation
Red flashy frames
RIL (SIM detection)
Dex pre-optimization
Camera
Sensors
Crash after locking device
microSD access
Flash light / Torch
Full brightness (should be fully working)
Gapps (permissions issues) [occurs occasionally and should be circumvented by full-wipe approach (incl. internal storage)
Hang/Loop during boot stage (should be circumvented by full-wipe approach (incl. internal storage)) (use Custom Kernel, under investigation)
High battery drain [~ 10%-20% per hour] when dirty-flashing system (fastboot -S 256M flash system system.img), make sure to have data backed up, then format /data ; OTA updates should be fine though [need feedback] ); causes are: dirty flashing, certain apps, ROM issues, etc.
Guides/Instructions
Unlocking Bootloader
Warning! The following procedure may void your warranty and will wipe EVERYTHING
Visit Sonys Official Bootloader Unlock guide (Details to all the risks you are taking are located on their site)
After Unlocking your bootloader you can proceed with the next steps
Steps on how to Fastboot, Flashmode, Recovery, Emergency/Force Poweroff
@alphatact1cs has a great overview on lots of topics for the Z5 device family
over at [GUIDE] Sony Xperia Z5 - UNLOCK / ROOT / TWEAKS - OS 5.1.1 / 6.0
There go to the [GUIDE] StockROM section , open it up and under #GENERAL you'll find everything you need to know.
Setting up fastboot and how to use it
For windows users
Please checkout this guide on how to use fastboot on windows
If you prefer to keep a low footprint instead of installing the whole Android SDK, take a look at its thread
[TOOL]Minimal ADB and Fastboot [8-28-15]
For Linux users
Installation
Debian based distros (Debian, Ubuntu etc.)
Open a terminal and enter the following :
Code:
sudo apt-get update && sudo apt-get install android-tools*
Confirm the installation by either hitting enter or typing y
Gentoo based Distros (Gentoo, Funtoo, Sabayon, Scientific Linux)
Once you're in a terminal, enter the following:
Code:
emerge dev-util/android-sdk-update-manager
Other distros (Arch, Fedora, Open Suse etc.)
Please find the apropriate packages to install android fastboot tools for your distro
How to use
Open a terminal in the location your .img file is located or cd into that directory like this:
Code:
cd <path to your directory that contains the .img files>
Replace <path to your directory that contains the .img files> with your actuall path
To boot temporarely into a .img (ex recovery) use the following command (replace <your.img> with your .img file) :
Code:
fastboot boot <yourfile>.img
To flash a kernel image enter the following (replace <your.img> with your .img file):
Code:
fastboot flash boot <your.img>
To flash a recovery image enter the following (replace <your.img> with your .img file):
Code:
fastboot flash recovery <your.img>
To exit fastboot enter :
Code:
fastboot reboot
How to install CM 13
Above all - do a Backup of ALL your data
When I write ALL I mean ALL (this includes the data on your micro SD card,
don't come whining to me if you lose your wedding photos/videos, kids' photos/videos or other important stuff !
For optimal experience I'd recommend my built custom kernel (quicker boot times, higher reliability, more tweakability)
General, in-depth instructions
Download one of the newer Z5 AndroPlusKernels v20+ by @AndroPlus from his official website (Scroll down and select Z5, then on AndroidFileHost search for Z5_AndroPlusKernel_Permissive_v2 (v20 - v23) and download it)
Extract the flashable zip-file e.g. Z5_AndroPlusKernel_Permissive_v23.zip
Download our TWRP 3.0.1-0 build for the Z5)
Download the appropriate gapps from below (Can be downloaded on your device)
Download the CM 13 Zip for the Z5 from below (Can be downloaded on your device)
Move the GAPPS zip and the CM 13 to your Z5 if you haven't downloaded them on your device
Power Off your Z5 and wait about 10-15 seconds to make sure it's off
To enter fastboot mode hold VOL UP and while holding VOL UP connect your device to your pc via cable
When the notification LED has turned blue you are in fastboot mode
On your PC flash the boot.img that has been extracted from the Z5_AndroPlusKernel_Permissive_v23.zip using fastboot (
Code:
fastboot flash boot boot.img
)
Now flash twrp-3.0.1-0-E6653-20160403.img by using fastboot (
Code:
fastboot flash recovery twrp-3.0.1-0-E6653-20160403.img
)
Once both of those images have been flashed you can reboot the device like so:
Code:
fastboot reboot
Quickly pull the usb cable from the computer (you can leave the other end in the phone's port)
When booting up wait for the notification light to turn yellow at the Sony logo
Once it has turned yellow, you will enter TWRP by pressing VOL UP (or VOL DOWN - up works more reliably)
If you've missed the step above, reboot your device and try the step above again
Alternatively you can force turn off the device via: Power Button + Volume Up , then turn it on again via Power Button
If TWRP asks you to enable read and write, swipe to continue
Go to settings and lower the max brightness to the minimum or one of the lower levels to preserve energy
In TWRP make a full backup to the microSD in case you want to revert back to stock.
After it has finished, in this case Reboot -> System.
Copy over the TWRP folder from the external microSD to your computer (reason: you might not have access to your external SD or have to reformat it
Thank Microsoft, Sony, etc. for that: "Stock" ROM uses texfat , AOSP, CM, etc. uses exfat, ext4, ntfs
The files on the microSD might get corrupted (filesystem problem) or the microSD going crazy (I already had both cases)
Now Power on your phone and follow the steps again to get into TWRP
Swipe to continue (?)
select Wipe > Advanced Wipe
Now ONLY tick Dalvik/ART cache, System, Cache and Data
WARNING! THE NEXT STEP WILL WIPE YOUR SYSTEM AND DATA, MEANING YOU WILL DELETE YOUR STOCK SONY SYSTEM AND ALL YOUR APPS
(You already DID a Backup of your files so nothing to worry about)
Once you've ticked the correct boxes, swipe to wipe
Once the wipe is complete, return to the main menu and select Install
Locate and select your CM 13 Zip
Select "Add more Zips" and add your GAPPS package and finally swipe to install
Once the installation succeeded you can select "Reboot System"
Wait for CM 13 to boot up (Can take several minutes)
Enjoy CM13
OPTIONAL: You can remove your TWRP backup that is located in the TWRP folder if you feel like you will no longer need it
How to ROOT
In CM 13, enable the developer options
Select Root access
Select Apps Only (Or Apps and ADB if you use ADB)
Done
How to disable the Thermal Manager
Before we start I want to set a few questions and warnings. Disabling the thermal manager will cause you device to run slightly hotter, do this at your own risk.
Let's start out with why you would want to disable the thermal manager. At this point it's not recommended to disable the thermal manager as it has been fixed. However some people still want the max performance out of their device. The average heat without the thermal manager will be roughly the same, if not less compared to the stock ROM with it's thermal manager enabled.
So why is the thermal manager even included if it the device runs mostly fine without it. As most of you already know, the Snapdragon 810 (MSM8994) has overheating problems. The first CM boot after flash is responsible for optimizing apps and android and can become extremely resource hungry at that point. Due to that, the device can heat tremendously! Not only can that cause a panic reboot but it can also damage your device in rare cases. To avoid that issue a thermal manager shrinks down process and slowers the boot animation (That's why the CM logo may lag at first boot).
Enough said, let's get going..
To disable the thermal manager you must do the following :
First enable root access (See "How to ROOT" guide)
Open the CM file manager
Go to settings > General Settings > Access Mode
Select root acess mode
Go back to the file manager
Swipe from left to right or press the menu button in the upper left corner
Select Root folder
Open the folder/directory called etc
Delete thermanger.xml
Reboot
Done
How return back to stock via TWRP backup
Reboot your device
Wait for the notification light to turn purple at the Sony logo
Once it has turned purple, you will enter TWRP by pressing VOL UP or VOL DOWN
If you've missed the step above reboot and try again
If TWRP will ask you to enable read and write, swipe to continue
In TWRP select restore and select your backup, then swipe to restore
Once the restore is done you can select "Reboot System"
If your device hangs at the Sony wave boot animation, force shut down and power your device up again.
Downloads
Latest recommended CyanogenMod release for the Sony Xperia Z5 E6653/E6603 :
6.0.1_13.0-20160626-UNOFFICIAL-sumire_r46_alternate
Latest recommended Kernel for the CM release for the Sony Xperia Z5 E6653/E6603 :
6.0.1_13.0-20160626-UNOFFICIAL-sumire_r46_alternate
All my releases can be found here on : Android File Host
TWRP for CM/AOSP-based ROMs:
[TWRP][E6653/E6603/E6633/E6683] 3.0.2 , for CM/AOSP ROMs
Gapps (Select ARM64 > 6.0) :
Open Gapps
[GAPPS][6.0/5.1/5.0][arm/arm64] Official Slim GApps ( recommended )
XPosed for Android:
[OFFICIAL] Xposed for Lollipop/Marshmallow (Installer in Thread)
XPosed Releases
SuperSU in SystemMode:
SuperSU in System-Mode [v2.65-STABLE] [v2.68-BETA] [v2.70-WIP/BETA-RC]
Sound MODs:
[Sound Mod ][Project DiVA][6.0 MM_Z5 series] KitaKami sound mod Prototype 01 (any effect ?)
A.R.I.S.E. Sound Systems - Auditory Research in Sound Enhancement - Exodus RC8.3 (works (RC8.3))
[SOUNDMOD][JB/KK/LP/MM]Project Yume Final, You are the Legend (needs testing)
[SUPER MOD][4.4+/6.0/N][ v7.5.2 ] XTREMEMusic™ THE SOUND THAT YOU'VE NEVER HEARD! (NOT working (7.4), needs testing of 7.5*
[Audio Mod] eXtremeBeats Aural Maximizer (needs testing)
[APP]Material ViPER4Android 2.4.0.1[Light/Dark][LP/MM]
mpro420 said:
1.)zip file install via twrp.
2.)reboot to system.
3.)enable v4a "write to sdcard" permission in setting/apps/viper4android/permission.
4.)open v4a and gain root permission.
5.)install driver for v4a.
6.)reboot system.
7.)[emoji39]
Click to expand...
Click to collapse
Questions and bug reporting
The following questions will be ignored
Inappropriate questions
Requests for other devices
Forced orders, EX. : "PLS FIX!!!!!!"
ETA's
Often repeated questions or requests usually by the same user
Requests that are out of CM's framework (Ex. Adding Sony Apps)
How to report a bug/issue
Explain exactly what happens
Mention a log if you can (Please use hastebin or any other paste site to keep the thread clean)
If you can't mention a log, explain as precise as possible when, why and where it occurs!
Source Code
All Source Code can be obtained from:
https://github.com/Sony-Kitakami
https://github.com/SonyAosp
https://github.com/sonyxperiadev
https://github.com/CyanogenMod
https://github.com/zachariasmaladroit/android_kernel_sony_msm8994_kitakami_r2
Kernel Source code can be obtained from : zachariasmaladroit/android_kernel_sony_msm8994_kitakami_r2
We gladly accept any developers that are willing to contribute to this project! Please PM @CTXz if you are interested in joining this project!
Build from Source
http://forum.xda-developers.com/xperia-z5/general/guide-build-cm13-source-z5-z5c-z5p-t3357040
Screen Shots (Z5 compact)
XDA:DevDB Information
CyanogenMod 13 for the Sony Xperia Z5 E6653 and E6603, ROM for the Sony Xperia Z5
Contributors
CTXz, Moonbutt74 , zacharias.maladroit , oshmoun , infected_
Source Code:
https://github.com/Sony-Kitakami
https://github.com/SonyAosp
https://github.com/sonyxperiadev
https://github.com/CyanogenMod
https://github.com/zachariasmaladroit/android_kernel_sony_msm8994_kitakami_r2
ROM OS Version: 6.0.x Marshmallow
ROM Firmware Required: 6.0 Recommended
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2016-04-11
Last Updated 2016-06-28

Changelog
Code:
2016/05/06
[LIST]
[*]Dual SIM support (ROM) [COLOR="Red"][B][WIP][/B][/COLOR]
[*]Dual SIM support (Kernel) [COLOR="Red"][B][WIP][/B][/COLOR]
[*]smoother brightness (automatic & manual), lower default and manual brightness
[*]weather provider support (CM)
[*]thermal manager improvements (CM)
[*]potential stability-fixes (CM)
[*]brightness dimming disabled (once temperature raises)
[*]VCM2 camera actuator (presumably working focus) == feature complete camera [LED torch still needs work]
[*]adb enabled from the start (diagnostics at this early ROM stage)
[*]upstream ROM + Kernel changes
[*]
[*] Sim-specific change: add DSDS (dual sim) detection script that starts second ril-daemon
[*]
[*] Custom Kernel changes:
[*] Intelliplug + Intellithermal by default [[B][COLOR="Red"]stability testing[/COLOR][/B]]
[*] added Quick Wakeup, PowerSuspend,
[*] added AdrenoIdler
[*] CPU and general Kernel optimized compiler flags
[*] re-enabled efficient WorkQueue [[B][COLOR="Red"]stability testing[/COLOR][/B]]
[*] re-enabled nop idle governor for CPUIDLE driver [[B][COLOR="Red"]stability testing[/COLOR][/B]]
[*]
[/LIST]
2016/04/19
- LiveDisplay (CM upstream) should work more reliably and should not cause instabilities and (boot)loops anymore
- torch should work now (ROM)
- changes, improvement to Bootup (Kernel side) - should make prebuilt kernel more reliable
2016/04/17 [suzuran]
- Fixed Brightness
- Fixed Torch
- Fixed Double Tap 2 Wake
- Added CPU core optimization
- Added USB gadget support
- Synced with the latest CM sources
-----------------------------------------------
* For devs
- Added Kitakami patcher to manifests
2016/04/15
- Full brightness range + maximum brightness (ROM + Kernel)
- KCAL support (Kernel)
- alucard, elementalX, zzmoove governors (Kernel)
- upstream sync (Kernel), perhaps better, more reliable WiFi
- more battery efficiency during video playback (Kernel), [needs testing, lags ?]
- adreno (GPU) governor, lower default frequency (Kernel), perhaps lower battery consumption, [needs testing, lags ?]
- vibrator intensity control (Kernel) [needs testing]
- some more battery efficiency tweaks (Kernel)
- NTFS, exFAT filesystem support (for microSD) (Kernel)
- tweaks and reliability improvements (Kernel)
- Driver wakelock control (Kernel)
- NEON/FPU compiler optimizations (Kernel)
- improved Hotplug reliability and stability (Kernel)
2016/04/12 [suzuran]
- Fixed sdcard recognition
- Updated binaries to v4
- Released CM build guide
- Synced with newest sources
2016/04/11
- CM 13 For the Z5 E6653 Released
2016/04/10
- CM 13 For the Z5 Premium E6853 Released
2016/04/05
- Fixed GApps
- Partially fixed Bluetooth
- Synced to latest CM sources
2016/03/27
- Fix thermal manager lag
- Fix NFC
- Updated kernel configs
- Added ffmpeg codecs support
- Synced with newest CM sources
-------------------------------------------
* For devs
- Cleaned up suzuran and satsuki tree
- > Moved common media configs to kitakami common tree
- > Moved acdb files to vendor tree
2016/03/24
- Fix In-call Mic
- Add support for the E5803
- Add option to boot into recovery (On purple LED at Sony logo press VOL UP or VOL DOWN to enter recovery)
- Update Thermal manager
- Merge latest AOSP kernel commits
- Sync to newest CM source
2016/03/22
- Fix microphone
- Add settings for camera button
- Add settings for volume rockers
- Fix sound on calls
2016/03/20 - RIP TonyStark, you were a great moderator and we'll all miss you.
- Added Thermal regulation to avoid overheating problems
- Fixed Red flashy frames
- Fixed RIL (SIM detection)
- Fixed Dex pre-optimization
- Fixed Camera
- Fixed Sensors
- Fixed Crash after locking device
2016/03/18 - CM 13 For the Z5 Compact E5823 Released

Reserved 02

Reserved 03
(and another one)

You know the drill:
the most important part is the phone functionality (well, it's a smartphone ),
please test that after you've done the initial set-up and tell, whether it works

Finally get there....
Great job man!
Hope there will be dual sim support asap.

Nice jobe, I'll wait for a more stable version to test it
keep up the good work
best regards.

Well done again to Sony Kitakami Developer Organization!
Sooooo much time and effort represented in those CM13 github projects. Total Respect.
Nuf said.

JerryLaiHMmmmmm said:
Finally get there....
Great job man!
Hope there will be dual sim support asap.
Click to expand...
Click to collapse
I've taken a look but haven't figured out yet on how to make it work,
if there are any developers out there with DSDS (dual sim) devices, interested on getting this working and read this - please take a look at it
Thanks !
korom42 said:
Nice jobe, I'll wait for a more stable version to test it
keep up the good work
best regards.
Click to expand...
Click to collapse
Okay
Thanks
Joeisgood99 said:
Well done again to Sony Kitakami Developer Organization!
Sooooo much time and effort represented in those CM13 github projects. Total Respect.
Nuf said.
Click to expand...
Click to collapse
Thanks ! <3

Will you be making a guide on building this rom from source? And of course, thank you for all your hard work we all greatly appreciate it.

Uclydde said:
Will you be making a guide on building this rom from source? And of course, thank you for all your hard work we all greatly appreciate it.
Click to expand...
Click to collapse
Very soon mate

Uclydde said:
Will you be making a guide on building this rom from source? And of course, thank you for all your hard work we all greatly appreciate it.
Click to expand...
Click to collapse
Build from Source
The guide on how to build your own Z5 ROM will be posted once we feel like this ROM is ready enough
Click to expand...
Click to collapse
Take a look at the source and the repos, the guides are out there ...
... you got a PM
CTXz said:
Very soon mate
Click to expand...
Click to collapse
beat me to it

zacharias.maladroit said:
[ROM][UNOFFICIAL][6.0.1][E6653/E6603] CyanogenMod 13 for the Sony Xperia Z5 [ALPHA]
if you loose your wedding photos/videos,
Click to expand...
Click to collapse
If it's "loose", put some glue on it!
lol

m3ta said:
If it's "loose", put some glue on it!
lol
Click to expand...
Click to collapse
lol - I get those mixed up quite a bit, sometimes due to typos, too

Status Update:
Uploaded new img files and a flashable zip-file for TWRP (haven't tried it out myself, currently evaluating Resurrection Remix)
Sorry for the inconvenience so far
Give it a try, if you dare

Okay, so I followed the steps for "General installation", and the rom is surprisingly smooth. The only issue I've noticed that isn't addressed in the original post is that vibration intensity is WAY higher than in the stock rom. Like it's actually pretty loud. I know it's a minor issue compared to some of the other things, but I'm just throwing that out there. I'll point out anything else I find.

Absolute legend! Thanks man. I'll get to testing once i get home off this drilling rig

Uclydde said:
Okay, so I followed the steps for "General installation", and the rom is surprisingly smooth. The only issue I've noticed that isn't addressed in the original post is that vibration intensity is WAY higher than in the stock rom. Like it's actually pretty loud. I know it's a minor issue compared to some of the other things, but I'm just throwing that out there. I'll point out anything else I find.
Click to expand...
Click to collapse
Thanks for testing
Actually it already was higher on AOSP, if recall correctly, but I'll ask the other devs if they noticed something out of the ordinary
Thanks
atanu89 said:
Absolute legend! Thanks man. I'll get to testing once i get home off this drilling rig
Click to expand...
Click to collapse
Thanks

Thanks for this great rom, the only problem i encounter is that my phone keeps stuck in first startup (cyanogenmod logo) and that keeps going i force my phone to switch off after 45 minutes, is there something i do wrong i followed the in depth guide

Sovjet-Command said:
Thanks for this great rom, the only problem i encounter is that my phone keeps stuck in first startup (cyanogenmod logo) and that keeps going i force my phone to switch off after 45 minutes, is there something i do wrong i followed the in depth guide
Click to expand...
Click to collapse
That partially is caused by the "stock" built kernel,
you can see whether is improved by flashing my custom kernel.
One observation (according to @moonbutt74 afaik) led to the conclusion that the upstream (from sonyxperiadev) setting of coherent_pool=8M doesn't match with Sony's ("Stock ROM") setting of coherent_pool=2M,
and does no good for startup time (and reliability ?).
Another factor (like in most AOSP-based ROMs, Kernels) is that the kernel was built with a less tuned toolchain (gcc),
can't directly explain though why does leads to exactly that behavior.
Tl;dr:
Give the custom kernel a try - the "stock" kernel should work but for some reason sometimes it does not
custom has exfat + ntfs support to make microSDs work reliably and other things
Thanks

[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.