[KERNEL][SINGLE/DUAL BOOT][KK]CM / CM Based / Stock 4.1 - Galaxy S III Mini Android Development

NEXT Kernel 1.0.0:
STOP! This kernel supports Custom KitKat Roms (e.g. OmniROM, SlimKat, CM 11.0), Custom JB 4.3.x Roms (e.g. CM 10.2) and Stock / Stockbased Roms!
It won't work on any AOSP Android 4.1.x or 4.2.x Custom Roms for now!
FOR NOW I FORBID ANYONE ELSE REUSE THIS STILL IN DEVELOPMENT DUAL BOOT PROJECT FOR HIS/HER OWN GALAXY S3 MINI PROJECT!
Sources:
https://github.com/andi34/android_kernel_samsung_golden
Dual-Boot Solution by @ketut.kumajaya, well known from Samsung Galaxy Tab 2 and Samsung Galaxy Tab 3 8.0
I/O Scheduler : noop | deadline | cfq | sio | sioplus | row | zen
Governor : Abyssplug | Ondemand | Interactive | Powersave | Performance | SmartassV2 | Sakuractive
based on latest Samsung OSRC for Samsung Golden (JB_Update2)
Linux kernel 3.0.101 version
Compiled with GCC 4.7
Open source Samsung exFAT included (v. 1.2.7)
Static BusyBox v1.21.1 in /sbin, android_reboot applet added (a quick but clean port from Android toolbox), swapon applet with priority option. Thanks to @ketut.kumajaya
"magic busybox" for Stock (based) 4.1 Roms: Ramdisk Busybox will overwrite busybox binary in
/system/bin or /system/xbin and save it as busybox.backup
Auto root on Stock (based) 4.1, but please download SuperSU from Google Play to update
Early boot scripts support
(/system/etc/init.d, /data/local/userinit.sh, and /data/local/userinit.d)
symlink /system/etc/wifi/bcmdhd_sta.bin_b2 to /system/etc/wifi/bcmdhd_sta.bin
to fix broken Wifi on Stock(based) Roms
SElinux Support
Known Problems:
Bootmenu
- Reboot into Recovery from main Bootmenu does not work
- Reboot into Bootloader from main Bootmenu only reboots normal
StockRom
- USB connection not working, charging works
- Wifi-Tethering not working on Stock / Stockbased Rom
Known fully working Roms
SlimKat by Android-Andi
OmniROM by golden-guy
VanirAOSP by Unjustified Dev
enox Stockbased Rom
Stock Light
Virginity v14
Selfcompiled CM 10.2.1 (based on CM 10.2.1 Stable Source)
Novafusion CM 11 & PAC (ext4 formatted!)
Novafusion CM 10.2 & PAC
Thanks To:
ketut.kumajaya - without you this would never be possible <3
gokhanmoral, Chainfire
@LuuchoRocha
@cocafe
OliverG96
DerTeufel1980
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...
I am still learning each day, i learnd most stuff from our great Developer Ketut P. Kumajaya
- i think HE deserves a Beer instead donating to me ATM. If you like you can spend Ketut a beer using PayPal
Screenshots
{
"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"
}
XDA:DevDB Information
[golden] NEXT kernel, Kernel for the Samsung Galaxy S III Mini
Contributors
Android-Andi, ketut.kumajaya
Kernel Special Features:
Version Information
Status: Beta
Created 2014-08-12
Last Updated 2014-10-11

Downloads
All files attached
- NEXT Tool 0.2 to create a 2nd System Partition (system.img) - also included inside PhilZ Touch Blackhawk Recovery
- PhilZ Touch Blackhawk Recovery for Dual-Boot-Support
- NEXT Kernel
Since NEXT Kernel 1.5.4: download latest NEXT Kernel here
Older files for history still here attached!
Changelog
Code:
[U]11.10.2014[/U]
1.5.6 -> 1.6.0
- Utilized blkid further
- Autogenerated fstab adapted from NEXT Kernel for Samsung Galaxy Tab 3
- Initial F2FS Support (experimental)
[U]19.09.2014[/U]
Update dual boot tool 0.3
- Create 1.5 GB dynamic growth sparse image
- Ext4 formatting fix
- Free space calculation fix
1.5.5 -> 1.5.6
- fixes a warning in dmesg (sysfs: cannot create duplicate filename '/devices/virtual/switch/usb_audio')
[U]17.09.2014[/U]
1.5.4 -> 1.5.5
- get rid of DVFS limit without breaking Stock 4.1 or Android 4.3 / Android 4.4
thanks [user=5562153]@LuuchoRocha[/user] and [user=4832589]@cocafe[/user]
[U]16.09.2014[/U]
1.5.3 -> 1.5.4
- Android 4.3: added PAC Support
- Nintendo Wii Remote support (experimental, untested)
- cpufreq: turn all CPUs online when governor gets changed
[U]04.09.2014[/U]
1.5.1 -> 1.5.3
- "magic busybox" for Stock (based) 4.1 Roms: Ramdisk Busybox will overwrite busybox binary in
/system/bin or /system/xbin and save it as busybox.backup
- Auto root on Stock (based) 4.1, but please download SuperSU from Google Play to update
- Early boot scripts support
(/system/etc/init.d, /data/local/userinit.sh, and /data/local/userinit.d)
- symlink /system/etc/wifi/bcmdhd_sta.bin_b2 to /system/etc/wifi/bcmdhd_sta.bin
to fix broken Wifi on Stock(based) Roms
[u]01.09.2014[/u]
1.5.0 -> 1.5.1
fix broken Dual-Boot (because missing "tmp" folder inside ramdisk? also some file permissions fixed inside ramdisk)
1.4.0 -> 1.5.0
Upstream Kernel Changes to 3.0.101 - thanks a lot to @Fred6681 for fixing some know Problems after Upstream!
Build Xpad module (not tested if it is working)
Enabled DVFS Limit to make the Kernel boot on Stock and AOSP Roms
New Charger-Animation - thanks a lot to @daywalk3r666
[u]25.08.2014[/u]
1.3.1 -> 1.4.0
Initial CM 10.2 support
[u]22.08.2014[/u]
1.3.0 -> 1.3.1
Fix 800mhz bug, thanks to @Fred6681
1.2.0 -> 1.3.0
Updated Android 4.4 ramdisk: this will fix broken Wifi on Novafusion Roms / Roms based on Novafusion source
Build exFat as module
[u]20.08.2014[/u]
1.1.0 -> 1.2.0
Added Stock / Stock based 4.1 Support
More i/o scheduler: Added sioplus | row | zen
Compiled using GCC 4.7 again for better compatibility
Update LZO compression
arm/vfp: Makefile optimization
and some more....
1.0.5 -> 1.1.0
Fixed bootmenu flickering / blackscreen :) now the bootmenu is 100% visible
(Reboot-Recovery option from bootmenu not working, ends in kernel-panic,
reboot bootloader not working, it will normal reboot)
partially restore initial cm11 ramdisk
cleanup cm11 ramdisk
[U]19.08.2014[/U]
1.0.4 -> 1.0.5
Update permissions inside init.samsunggolden.rc,
set SELinux to permissive for now,
lzma compressed ramdisk
1.0.3 -> 1.0.4
Use Linaro 4.8 Toolchain
[U]18.08.2014[/U]
1.0.2 -> 1.0.3
Use Linaro 4.7-2013-04 Toolchain
[U]12.08.2014[/U]
1.0.1 -> 1.0.2
- fix an Superuser issue, added back init.superuser.rc
1.0.0 -> 1.0.1:
- fix "com.android.phone" crashed on Vanir Rom
1.0.0:
- initial release
How-To
Flash PhilZ Touch Blackhawk Recovery
Reboot into PhilZ Touch Blackhawk
Flash NEXT Kernel
Advanced Functions -> Run Aroma Dual Boot Tool
Create a 2nd System.img (choose 1 GB)
Reboot your recovery
Choose the 2nd Bootoption (it is flickering, black screen, just press the volume down key one time and press the power button).
Now the navigation buttons inside PhilZ Touch are RED
Flash a 2nd Rom (i tested my own SlimKat and @golden-guys OmniROM because they don't use F2FS)
Flash NEXT Kernel again
Reboot
Now you will see a Bootmenu (flicckering & blackscreen), you will see it short if you press the volume key,
first option = boot 1st Rom, second option = boot 2nd Rom
USE ON YOUR OWN RISK! MAKE A BACKUP BEFORE TRYING!

Reserved
Dual Boot FAQs
Adapted from @ketut.kumajaya s Dual-Boot FAQ,
original adapted from droidphile's "Dual Boot FAQs".
1. "Why would I wanna dual-boot?"
A. You don't have to.
You need one testing system and don't want to break your daylie Rom.
You can not decide between different Roms - use both
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 mmcblk0p24 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:-
Prerequisites for any setup is
a) Flash latest blackhawk's NEXT kernel.
b) Flash latest Extended PhilZ Touch recovery: http://forum.xda-developers.com/showpost.php?p=54772218&postcount=2
c) Atleast 90% battery left.
d) 3 GB free on internal SD.
e) Some spare time
1) Present AOSP, setup AOSP as secondary:-
i) Reboot into recovery
ii) Select "Run Aroma Dual Boot Tool" in Advaced Menu, create system.img for CM/CM based ROM and then close it
iii) Reboot into secondary recovery (red on screen navigation buttons)
iv) Flash AOSP ROM as 2nd ROM
v) Flash blackhawk's NEXT kernel again
2) Present AOSP, setup aosp as primary:-
i) Reboot into recovery
ii) Nandroid backup your current sammy ROM
iii) Select "Run Aroma Dual Boot Tool" in Advaced Menu, create a 2nd system.img and then close it
iv) Reboot into secondary recovery (red on screen navigation buttons)
v) Nandroid restore your AOSP ROM as 2nd ROM
vi) Flash blackhawk's NEXT kernel again
vii) Reboot into primary recovery
viii) Flash AOSP ROM as 1st ROM
ix) Flash blackhawk's NEXT kernel again
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
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
14. "How to flash newer version of 2nd rom?"
A. Just flash it from secondary recovery. Flash blackhawk's NEXT kernel again
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. "Do I need to anything special before flashing a newer blackhawk's NEXT kernel?"
A. NO. Just flash kernel in recovery - whichever you used to do. Kernel image is copied to the unified kernel partition
20. "How do I remove everything related to DB and run single boot again?"
A. In primary recovery, flash blackhawk's NEXT tool or "Run Aroma Dual Boot Tool" in Advaced Menu from PhilZ Touch Blackhawk and delete 2nd ROM system image. OR delete .secondrom directory in /data/media while on 1st Rom.
21. "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.
22. "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
23. "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.
24. "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.
25. "Is there an easier way for dual-boot?"
A. Yes, send your device to me.
26. "DB architecture?"
A. Like you know, every rom has a /data, /system, /cache partition and a kernel to boot.
For primary rom, it's
mmcblk0p25 = /data
mmcblk0p22 = /system
mmcblk0p23 = /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 mmcblk0p24 which is hidden partition and not used otherwise.
- When second rom is booting, second rom data is bind mounted to mmcblk0p25 as /data/
- data/media/.secondrom/system.img partition is mounted as /system.
- dev/block/mmcblk0p24 is mounted as /cache.
How to get important Logs
tonyp said:
The three most important log types are:
logcat: the logoutput of the Android system
radio logcat: the log outpur ot your System / BB / RIL communication
kernel log (kmsg / dmesg): the kernel messages
Additionally there's the last_kmsg which is a dump of the kernel log until the last shutdown.
Normal Logcat:
Code:
adb logcat -v time -d > logcat.log
Radio Logcat:
Code:
adb logcat -b radio -v time -d > logcat_radio.log
Note: Cyanogenmod (based) ROMs require the following setting to export kernel logs via adb:
Settings - Developer Options - Root access - choose: "Apps and ADB"
Kernel Log:
Code:
adb shell su -c dmesg > dmesg.log
Last_kmsg:
Code:
adb shell su -c "cat /proc/last_kmsg" > last_kmsg.log
Click to expand...
Click to collapse
More FAQs will be added and the list will be updated as DB is improved.

Wow!
another milestone in the S3 Mini history!
Keep it up bro :good:

Incredible!!
This will bring my two favorite ROMs on one device!! Unbelievable Till now, I thought it is possible only with linux lubuntu and ROM, like on my tab...
Thank you!
m.

This is amazing! Can we use roms like debloated stock with your roms?
Sent from my GT-I8190/Novafusion CM11

Don't you read the OP?!? Not for stock ROMs! And 4.4.x only!
m.

meduza2 said:
Don't you read the OP?!? Not for stock ROMs! And 4.4.x only!
m.
Click to expand...
Click to collapse
Ah missed that part! Thanks for pointing out.
Sent from my GT-I8190/Novafusion CM11

No worries
m.

heithered said:
This is amazing! Can we use roms like debloated stock with your roms?
Sent from my GT-I8190/Novafusion CM11
Click to expand...
Click to collapse
Will try to add Stock 4.1.2 support sometimes later.
Send from OnePlus One using Tapatalk

Android-Andi said:
Will try to add Stock 4.1.2 support sometimes later.
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
Hey, this is a big deal. It is still awesome with or without stock support! Thanks for your awesome work!
Sent from my GT-I8190/Novafusion CM11

Well, just to leave an "Amazing work" as always:good:

great work.....dual boot with slimkat and omnirom works perfect.with vanir "com.android.phone" crashed

Top Job and faster as Nova!!!!

especially for you
@Android-Andi,
because of the world first dual boot for our s3mini, we created extra an info banner for you
Please have a look: Weltpremiere bei hubo.in
meduza, bodo_1, daywalksr666, kingg

Wow, you did it! That's so cool! Thanks a lot for this! ?

Simply awesome

It is incredible what AA made for our device.
But what is the sense of this mod?
I can use only one ROM at the same time.
Or am I wrong?
I am happy for explanations
The only idea i have:
First ROM for daily use
Second ROM for testing and replacing with different ROMs...
m.

moonryder said:
It is incredible what AA made for our device.
But what is the sense of this mod?
I can use only one ROM at the same time.
Or am I wrong?
I am happy for explanations
m.
Click to expand...
Click to collapse
you can load two roms to your phone.
at start up,you can choose either of 2 roms.
may be from recovery mode I think.
this is all what I know. hope I helped.
waiting for correction if I was wrong.
thanks and great work and much appreciation to Android Andi bro

@moonryder,
you could quickly boot one of your favorite ROMs or use the second boot partition for test ROMs....
m.

Related

[KERNEL] APOLO [i9100][SAMMY & AOSP]

Branch 4.x only for Sammy ROMS 4.1.2 (CWM and TWRP)
Branch 5.x only for AOSP 4.2.2 (CWM & TWRP)
Branch 6.x only for AOSP 4.3.x (TWRP)
Branch 7.x only for AOSP 4.4.x (TWRP)
Branch 8.x only for AOSP 5..x (TWRP)
DEVELOPMENT STOPPED . APOLO WON'T WORK IN LATEST LP ROMS . MORE INFO
Apolo Configurator -> will be available in Google Play THIS
Apolo 8.0 Beta9
Beta 9
-initramfs updates
-zRam disabled
Beta 8:
- initramfs updated
- TWRP 2.8.5.0
Beta 7/7b:
- zRam enabled
- initramfs updated
Beta6:
- App2SD Fixed
- Wifi Toggle issues fixed
- Network issues fixed
Beta5:
- CM wifi issue fixed
- same initramfs for cm and omni (same kernel for all roms)
- charging animation fixed
- zzmoove updated to 1.0beta5
Beta4:
- Recovery TWRP updated to 2.8.5.0
- Updated initramfs to latest CM & OMNI
Beta3:
- Recovery TWRP updated to 2.8.3.0
- Governor zzmoove updated to 1.0 Beta4
- Fuse bug fix by @zeitferne (thanks to @Lanchon too)
- Charging Animation fixed (thanks to @Lysergic Acid)
Download Link
MIRROR
Apolo 7.3 (final version for kitkat)
- Governor zzmoove updated 1.0 Beta5 (thanks ZaneZam)
- TWRP Recovery 2.8.6.0 ("Reboot Bootloader" button fixed)
- SPEEDUP KEYRESUME (Faster wake up at power button and incoming call)
- Fixed fuse bug (thanks to @Lanchon)
Apolo 4.15b for SAMMY JB ROMS (Removed vibration interface compared with 4.15)
- Governor zzmoove updated to 1.0 beta 4
- Speedup keyresume (faster wake up)
- Governor Neox has come back (not included in beta )
- FPBug fix by @zeitferne & @Lanchon)
Download links in the usual section in this OP​Changelog old Versions in Post #2
Features:
This kernel is mainly based in hardcore work (thank you to Hardcore :victory: for his great contributions). I have added undervolting (kind of phenomenal) and some additional features.
- CWM and TWRP recovery in Samsung. In AOSP I will use only TWRP in the future.
- No logs, no extra debugging
- install su, supersu in samsung. Support init.d and cifs
- Ondemand Tweaked by Hardcore
- Added some governors (specially tweaked slp and zzmoove)
- Scheduler changing enabled
- BLN enable (Since Apolo 4.5 BLNWW too)
- CRT-OFF enable
- Effective Underclock (max frequency limited)
- UV Interface for ARM (you can change voltages in ARM with external aplications)
- Kernel Includes frandom for using with CrossBreeder (I really recomend it, Thx idcrisis)
- No Overclock and no different CPU-GPU steps from stock (please don't ask me more about that, I won't add it)
Update Supersu (only sammy kernel, AOSP doesn't have supersu)
Choose normal update (not the other with CWM/TWRP). In case you chose the wrong option, you'll have a bootloop. Read the bootloop section in this OP to recover your system.
Undervolting
UV cannot damage your mobile phone, but it can make your device unsteady. It is important that you choose the right version for your mobile.
There are some Apolo versions depending on the UV used:
- Light (stock voltages)
- Regular (-50mV in ARM, internals)
- Extreme (3 versions, you can try to see what versión is better for your battery life): in JB system chooses among the different steps available inside the kernel (in internal and ARM), so depending what step is chosen, final voltages applied are different.
Regular and extreme has -50mv UV in GPU (others UV like bus, memory, video controller too). Light has stock voltages in GPU
I recommend you try regular version first. If there are no problems in two days (reboots or frozen screens) you can try extreme V0.
System changes voltages in some devices (new in JB). Android chooses among voltages included in kernel (8 steps in every frequency). I recommend not to change them in extrem versions.
More information and Voltages values:
Depending on the device, system changes voltages (in JB), choosing among voltages defined in the kernel source. It seems, system tries to choose the ideal ones for every device (taking into consideration internal and ARM voltages).
For each frequency, there are 8 posible voltages in the code (I call them steps). In ICS, system always chose 4th step for every frequency, but in JB it doesn't sometimes.
It happends with ARM voltages (you can see them in the configurator) and with internal voltages, so there are many possibilities
You can see ARM and Internal voltages in this pdf (it is in Spanish but I think you can understand it) :
VOLTAGES
So, it is not strange that configurator shows different values in two different devices with the same Apolo version. It simple, system has chosen different voltages steps. I recommend you don't pay too much attention to this, it is not important, indeed system try to be stable choosing different values.
Tips
- TWRP and CWM Backups are not compatibles between them, so you need the suitable version to restore your backups.
- I recommend OBackup. Great application for making backups in Android itself (it supports TWRP and CWM).
- Not always less voltages means better battery life, it depends on your device. The only way is testing every version and please start with Regular or Light version
- Deep Sleep problems sometimes is caused by undervolting. If your system doesn't enter in deep sleep and it is not because of any application , install regular or light version.
- It is not the same, lower ARM voltages with an external APP (for example Apolo Configurator) and change Apolo version (V2,V1,V0 or regular) because there are more voltajes involved (not only ARM)
- If you want to turn off the leds always (when you touch tactile buttons), you have to use Apolo Configurator, otherwise (if you use only Samsung settings) your leds will turn on when you turn on the screen.
- If your system doesn't boot due to wrong Voltages, flash this in recovery : download zip
- Acess to internal sd in TWRP recovery :
(Up a level )
then go to
"emmc"
that's your internal sd
- Recommended wipe Cache and Dalvik after changing any kernel (it is not mandatory but it is a good custom)
- To increase sound volume use mods like Viper or appications like Alsa Mixer or Vodoo louder in play store
Enable logs in TWRP and v7 : Create a file in "/data" named ".enable_logs" and reboot.
¿In kit kat, should I use CM version or Omni version?
Just see if your ROM has superuser included (I mean if you can gain root just enabling it in developer options). In that case you should use CM version. If your ROM needs supersu to manage the root, install omni version.
Bugs
- Battery Animation doesn't work when phoes is off
There is a workaround. Thanks to @It_ler : http://forum.xda-developers.com/showpost.php?p=43244090&postcount=1250
- S2W doesn't work after rebooting.
It's because this S2W bug: "When the phone is booting, if the screen is off in the exactly moment the script is changing the S2W setting, the screen will not respond any longer and you have to reboot."
To avoid it, increase the screen timeout. Another solution is to keep the screen on, while the phone is starting until android had started completely and you can be sure that the script has been applied (more than a minute because the script has 60 seconds of delay).
- If BLN y/o WIFI doesn't work in kit kat ROMS (maybe it can help in other bases too)
If test button works in Apolo Configurator check if in your Android Settings- Display there's something related to notifications led or Notifications light
or review
Rom settings (name depends on the ROM) - Active display must be disabled, otherwise BLN won´t work
If BLN test or wifi doesn't work, try this:
- Remove Apolo folder in /system (if folder exists)
- Go to Recovery
- Wipe Cache
- Flash Apolo
- Wipe cache again
- Reboot
- Avast doesn't work with Apolo, if you can't live without it, use other kernel, sorry
- Bootloops: it doesn't happend very often but it can happend in JB if there is something corrupt in partitions. Posible solutions:
1) Try to enter to recovery. Press vol up, Home button and Power button at the same time until the device enters into recovery (system can restart 2 or 3 times, but don't release buttons). Then wipe cache and dalvik and reboot.
2a) if 1) didn't work, enter into download mode and flash light TWRP version if you had CWM. Wipe cache and Dalvik and reinstall CWM if you wish.
2b) if TWRP didn't work or you had TWRP version already, flash last PhilZ kernel (thx to Phil3759), enter into Philz recovery and wipe cache and Dalvik. Then reinstall Apolo.
3) if nothing worked, try to reinstall your ROM without wipe data and wipe cache and Dalvik
4) wipe data (you will loose all your application and configurations)
5) reinstall with odin stock ROM WITH repartition (pit file). Then install Apolo and reinstall your custom ROM.​
- Sometimes when you reboot your device, your battery seems to drop a lot (it is not real).
To recover your old battery percentage, plug in your device and reboot into recovery. Check your battery level in the recovery, if it is correct, reboot (solved).
If it is not, reboot into recovery again (in CWM advanced - reboot into recovery, in TWRP reboot - recovery). It should be solved.
This issue never happens if you reboot your device while is charging, so I recommend you plug in your device before rebooting (if you can do it)
If you can't plug in your device, don't reboot if you can avoid it
- AOSP: Recommended installation procedure for 4.3 ROMS (stuck in the second boot) Read post 3
- AOSP: Restoring backups changing ROM base (stuck in the second reboot), Read post 3
Download Kernel
Mirror
Installation (you can install Apolo through CWM or TWRP recovery, it doesn't matter)
- Use a kernel cleaning script before installing (for instance Gs2KernelWipe thanks to hawkerpaul, but you can use other)
- .zip : install in custom recovery
- .tar : install in PC with odin (windows) or heimdall (linux)
Apolo Configurator (Available in Google Play again HERE)
I've developed a multilanguage application (Spanish, English, Italian, Catalan, Gallego, Russian and Turkish).You can change governor and scheduler, set ARM undervolting, configure BLN, BLNWW and S2W and set brightness curve:
I extremely recommend you read the Apolo Configurator Manual : Apolo Configurator Manual
My recommendation about scheduler/governor (it's only my opinion, maybe yours can be different)
- You can find 3 defined profiles in Apolo Configurator (performance, balanced and battery saving) based in noop/slp. I have changed parameters to achive the profile goals.
- Another good combination is noop/zzmoove
THANKS
- Hardcore for his fabulous kernel speedmod
- Thx to great :goodhil3759 (he helped me to build the CWM recovery and let me use his recovery in the new Apolo versions) Please, visit his great job here
- Thx to jeboo for his great kernel and for let me use his TWRP recovery :good:
- Thx gokhanmoral , great master. Most advanced features come from him
- Thx dorimanx for his great kernel and sources
- fenomeno83 for his idea and help when I started
- Thx mialwe for his great "smoove" governor (base of zzmoove) and ZaneZam for keeping it alive with the zzmoove.
- Chainfire for CF-Root, CWM Manager, etc, etc
- Thx sk8erwitskil, myfluxi, Talustus for recovery sources
- Thx to Devil_1210 for his help building the ICS kernel
- Thx to my betas for their help and ideas and much more: Broquen, Garrapatero123, Palleiro, Doomper, partisano, 666roi666 , Gordon320, nrg86
- Many thanks to @daga69 for giving me a S2 and keep this kernel alive
- Thanks to @rrgrrg for the Configurator icon.
(for sure I forgot more people, I hope they forgive me)
Donors: :laugh:
Axel 11, manuelmagix, K-a-M-u-Z-u, elbanzai,Zytrel, bkraptor,Shadowrun1,rogers11,LarsX,Andreas75k,espirito-livre, dsp26, gumsle, karpfenhai,
Andreas75k (Yes again ), metalgearhathaway
Thanksssss a lot ¡¡ :highfive::victory::good:
If you see something that you cannot understand or it is not correct (my English is far away from perfect ) please let me know
If you want to translate the Apolo Configurator to other lenguages, please tell me
Thanks to @lejarton, @Maxximo88, @stelistcristi,@Gordon320, @nrg86, @Palleiro, @Partisano, @Broquen and @nhmanasfor their translations
Enjoy ¡¡
Apolo source code
CHANGELOG OLD VERSIONS
Apolo 7.1 (for kitkat ROMS, 4.4.x)
- Recovery TWRP updated to 2.7.1.0
- Mali drivers updated
- zzmoove updated to 0.9beta3 (thanks to ZaneZam)
- rebuilt cypress (maybe helps with BLN errors in some devices)
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo 7.0b for kit kat, 6.3 for 4.3.x ROMS (TWRP recoverys) and Apolo 4.14 for stock ROMS (CWM & TWRP recoverys)
Changelog All bases (7.0b & 4.14 & 6.3):
- New zzmoove 0.8 (thx ZaneZam Link )
For kitkat (Apolo 7.0b & 6.3 TWRP):
- Fixed second core bug that affected some governors
- Pac-Rom support
- TWRP updated to 2.7.0.0 (it doesn't work fine in stock roms 4.1.2 (bootloops issue), so if you want to go back to sammy roms from kitkat, install first 4.14 and reboot in recovery and install from Apolo 4.14 recovery)
Remember that 6.3 comes with new mali drivers. If you see your screen off when you start your system, you must flash this through recovery.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo 4.13 (SAMMY) & 6.2b (AOSP 4.3.1)
Both (SAMMY and AOSP):
- Linux updated to 3.0.101
- Updated row scheduler
- Added bfq scheduler
- Removed MDNIE Sharpness by Hardcore (no mor problems with mdnie scenarios)
- Initramfs improved
6.2b ONLY:
- GPU an Screen drivers updated (r3p2+s3cfb)
- Wifi drivers updated to 1.61.58
WARNING: 6.2b version only with mali r3p2+s3cfb.
If your ROM is mali v2 (old drivers) you have to update some libs (otherwise, black screen). You can do it with this zip (flash in recovery):
https://copy.com/reo37Z4KqLVhU1S2
The zip will change some libs in ROM, so if you want to go back, you'll have to flash the ROM again without wipes
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo beta kitkat (Android 4.4 CM and OMNI-SlimKat)
- Beta 3 ONLY for OMNI ROMs: Solves the issue installing some application in latest nightlies
- Beta 2/2b for CM ROMs:
Only with mali v3. Works with new CM bases (4.4.2) .Thanks Karpfenhai for your help testing it
- Fixed battery settings
- CWM stock recovery (restores fine)
- Last changes (like 6.2)
If you suffer issues with the battery indicator, please change to beta2 or beta2b (depending on what kernel had the issue)
- For Omni ROMS there is a beta2 (same changelog) with TWRP recovery
For SLIMKAT 4.4.2 ROMs you should use Apolo beta2b for CM.
If you use omni version in CM ROMS (don't recommended because you will loose root) don't forget to download supersu and update binary BEFORE flashing Apolo kernel (otherwise you'll have a bootloop).Thanks to @Shahan_mik3 and @EricCartmanez for the information.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo Beta 3 FOR CM KITKAT (4.4.2) ROMS
- Solves the issue in (FC in phone) in latests nightlies
- Fix the bug moving big files to external sd (CREDITS TO GUSTAVO)
It was a lot of work, headaches, and semibricksssss so ENJOY IT¡¡
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo versions 4.12, 5.1, 6.1
For all bases:
- Reverted the stupid android_secure change I did in last kernel
- Added new governor Neox
- Added MyFluxi sound interface (to control it you'll need to use the new Apolo configurator 5.0)
- Fixed mdnie in the camera with mdnie sharpness disabled
Only For 5.1:
- Fixed vibration control
Only For 6.1:
- Added support for framework-2.jar
- Fixed com.android.phone FC in latest releases
---------------------------------------------------------------------------------------------------------------------------------------------
Apolo 5.0 & 6.0 (AOSP ROMS)
5.0 (AOSP ROMS 4.2.2):
- TWRP version fixed (bluetooth) and updated to 2.6.3
6.0 (AOSP ROMS 4.3 and 4.3.1):
- Initramfs improved
- Fixed booting for latest Pacman ROMS (4.3.1)
- TWRP version fixed (bluetooth) and updated to 2.6.3
- Vibration Control enabled
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------Apolo 4.11 (Sammy only)
- zzmoove updated to 0.7d
- Backup and restore Android_secure fixed
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo 5.0 & 6.0 (AOSPs Version)
- Base: smdk4412 by cyanogenmod
- Same tweaks as Apolo JB 4.x
- zzmoove updated to 0.7d
- Backup and Restore of Android_secure solved (thx dorimanx)
- Fully compatible with Apolo Configurator
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo 4.10 (Sammy ROMS)
- Added brightness curve interface (credits to gokhanmoral) It will be necessary to use new Apolo Configurator 4.0 to configure the brightness curve (available in Google Play).
- Exfat support in kernel and recoverys (CWM and TWRP)
- TWRP recovery updated to 2.6.1 (thx to the TWRP team)
- zzmoove updated to version 0.7c.(thx ZaneZam)
- su and supersu updated (thx chainfire)
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo JB 4.9
- Slightly change in brightness levels (automatic brightness higher than 4.8)
- Wifi drivers updated (latest S4) thx dorimanx
- Pegasusq , sampling time set to 50000, instead 100000 (improvement listening music with bluetooth)
- Try to solve issue of charging animation with phone off (will see if it works)
- zzmoove updated to 0.6 and tweaked thx ZaneZam
- sio scheduler updated
- su, supersu updated
- Revert USB charging values to 450 mA by default (safety measure). Added charging interface, so since Apolo configurator 3.8b you will be able to change it.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo JB 4.8
- Bilingual CWM recovery(Spanish-English). Default: English (you can change language in Extras Apolo)
- Fixed toggle ctr-off in CWM recovery
- Default backup format set to tar in CWM
- Updated TWRP recovery to version 2.5 (Thx Jeboo for sources). Added Preload support.
- Two new minimum brightness levels in manual mode (lower than stock)
- Fixed init.d. Now kernel considers all scripts in /system/etc/init.d
- Fixed BLN test in Configurator
- Current for USB charging to 650 mA (same as wall charger)
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo JB 4.7
- New Wifi Drivers from S4 (Thx dorimanx and codeworks)
- Added I/O Scheduler row (Thx Jeboo)
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo JB 4.6
- Revert Linaro toolchain compiler to GCC 4.6.3
- New governor interactivex (thx dorimanx)
- New governor zzmoove tweaked by pedestre (I recommend this governor, it's great)
- Fixed bug flashing from recovery updates with Assert instruction (for instance modem zips)
- Updated su and supersu
- Fix Touchscreen Choppy using MXT224E chip(thx kgp700)
- New Apolo Configurator 3.2 (useful for activating and scheduling BLN and BLNWW, selecting governors and schedulers and much more ...). You can find it free in Google Play
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo JB 4.5
- New interface with BLNWW, leds timeout and brightness and Slide to Wake (All the credits for gokhanmoral)
- New governor Intellidemand (thx dorimanx)
- New Apolo Configurator 3.0 (useful for activating BLN and BLNWW and much more ...). You can find it in Google Play free
INSTALLATION PROCEDURE FOR 4.3 / WIPING DATA ( if you are going to wipe data, skip 4,5 and 6)
In 4.4 is not necessary if you are using beta2,beta2b or beta3 (Omni or CM)
I don't know what the problem is (update: the problem is recovery) but if you follow this procedure (fresh install) you won't have any problem. If you install the rom right with Apolo, you may be stuck in the second reboot ?¿?¿
1- Install CM recovery (it is better install ROM with CM recovery). You can download it here
2- Advanced - Reboot in recovery (you will reboot in CM recovery , it is no a touch recovery, sorry)
3- Wipe data (and format system if you are going to install a new ROM)
4- Install ROM
5- Install gapps
6- Wipe data again
7- Boot system
7- Do the initial guided setup (wifi, gmail, etc) and install a couple of your apps
8- Reboot (it takes to boot a little longer than usual, even a couple of minutes)
9- After a successful second reboot, you can change the kernel to Apolo and you won't have any issue. It will always boot normally.
RESTORE ROMS IN AOSP ROMS (moving from 4.3 to 4.4 or from 4.4 to 4.3)
This issue only happends (AFAIK) when you change your base restoring the backup, for instance if you are in 4.4 and restoring a 4.3.1 backup. In my experience if you are in the same base, it works right.
You won't have any issue restoring roms in firs reboot, but you may be suffered the same issue (stuck in samsung logo) in second reboot, after restoring your backup. You can do your backups with Apolo, the issue is restoring, but I recommend you do your backups with OBackup App, because you don't need to reboot in recovery (you can do it in Android without rebooting)
If you want to restore your backups successfully I recommend you first change the kernel to CM kernel and then restore your backup:
SAFE PROCEDURE TO RESTORE BACKUPS
1- Reboot in recovery
2- Install CM recovery download
3- Advanced- Reboot in recovery
4- In CM recovery : Restore your backup
5- Reboot and everything will be fine
And more
Greetings!!!
YES! Finally Apolo by Pedestre here!!!
WELCOME :victory:
Kernel rocks
And CWM in english now?
Ooooh goood
I follow your kernel on an Italian forum, and it's quite popular.. just because your kernel is waaaaay good :thumbup:
Welcome to Xda mate! I hope a lot of people will enjoy your work
WarcoLLapsE said:
YES! Finally Apolo by Pedestre here!!!
WELCOME :victory:
Kernel rocks
And CWM in english now?
Click to expand...
Click to collapse
Thanks ¡¡
No plans , too much work translating and maintaining two CWM recoverys, but I wouldn't mind to include any English CWM recovery if somebody let me use it (as I did with TWRP from Jeboo)
finally on xda!!
Thank you for having implemented the zzmoove:thumbup:
my results with this amazing kernel .....
only wifi - no games/no 3G/no BLN/no Slide2wake, Tapatalk, internet browser, youtube + 2h to music on headphones....
Spoiler
{
"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"
}
Spoiler
Phone: SGS2
Inviato da: Tapatalk 2
Rom: NeatROM 4.7 LITE XWLSS
Kernel:Apolo 4.6 v0 ←testing-
Modem: XXMS2
Battery: Stock 1650mAh
SD Ext. : 32Gb class 10
Inviato dal mio supermuletto :tank:
Thank you very much for your work Pedestre. Glad to see you here too. Good Luck. Regards
Enviado desde mi GT-I9100 usando Tapatalk 2
vitalianoleone said:
finally on xda!!
Click to expand...
Click to collapse
+1
Just added this kernel thread to my kernels-to-test list of my kernel test thread.
Hope that latest light version will run stable on my phone, as I had some FCs and SODs on previous regular version.
Thanks pedestre! Great kernel and best person. :thumbup:
It_ler said:
+1
Just added this kernel thread to my kernels-to-test list of my kernel test thread.
Hope that latest light version will run stable on my phone, as I had some FCs and SODs on previous regular version.
Click to expand...
Click to collapse
FCs and SODs are tipical undervolting issues. Light version has stock voltages, I hope you don't have any problem
Your mobile must be delicate with undervolting; most devices don't experience any issue with regular version.
Thanks for added Apolo to your kernel list. Great job testing ¡¡
My results
Spoiler
Phone: SGS2
Inviato da: Tapatalk 2
Rom: NeatROM 4.7 LITE XWLSS
Kernel: Apolo 4.6 v0 ←testing-
Modem: XXMS2
Battery: Stock 1650mAh
SD Ext. : 32Gb class 10
Inviato dal mio supermuletto :tank:
Thanks !!
Let's try 4.6
Nice to see you here pedestre, tnx a lot for your work!
What a tremendous job man!! Works great with AllianceROM!! Thx
Welcome master. Great job. Best kernel ever.
Yeah! Finally on xda! I'm sure that philz will let you use his recovery!
Inviato dal mio GT-I9100 con Tapatalk 2
Glad to see you around here
I will help you as much as I can

ROM★★★TF201 KitKat 4.4.4-CROMBi-kk-R1-Oct 1★★★

{
"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"
}
YOU MUST BE ON THE HAIRYBEAN 2.31 JB 4.2.1 BOOTLOADER VERSION 10.6.1.27.1 AND TWRP 2.6.3.1+ OR CWM 6.0.4.6+ BEFORE FLASHING THIS ROM. SEE UPGRADE INSTRUCTIONS BELOW IF YOU ARE UNSURE
You must do a full wipe in recovery if coming from another ROM base. Do not do a full wipe from the bootloader. Don't forget to do a Nandroid Backup first and give the ROM 10 mins to stabilise!
Features and Tweaks
This ROM is based from CM11 AOSP sources
Based off cm-4.4-20140901-crombikk4.4.2-tf300t source by lj50036
Full Aroma Installer for main rom including choice of 3 kernels and ROM2SD and DATA2sd support
CM11 kernel built from CM11 source by lj50036
Remixed _thatv8 kernel with CM11 ramdisk - repacked by sbdags
Remixed Grimlock kernel with CM11 ramdisk - repacked by sbdags - experimental
DPI Size: 160 (TF300 recommended stock fonts), 148 (Small fonts), 132 (Tiny fonts)
Launchers: Trebuchet, Google Experience Launcher, Apex , Nova
Boot Animations: CM Circle of Fire, CM Color Circle, Nexus Phase Beam, Cyanogen Stock
Gapps (updated by sbdags to Google latest apks and libs) flashed from separate package
Misc Apps: ESFile Explorer, Adobe Flash, AdAway, Titanium Backup, DropBox, Keyboard Manager
Tweaks: File system and performance optimised, Init.d support!, Zip Align, Force GPU Rendering, Browser2RAM
Continued Best Support of any ROM!
Warning - experimental tweaks
[*]Option to enable / disable data journaling on /data during install - CAN CAN CAUSE DATA LOSS IF SUDDEN SHUTDOWN OR CRASH
[*]Option to enable / disable fsync during install - CAN CAN CAUSE DATA LOSS IF SUDDEN SHUTDOWN OR CRASH
Change Log
cm-11.0-20140901-crombi-kk-RC2-tf300t Kitkat 4.4.4rc2 source by lj50036
Change Log
20140906 changes
- Rebuilt from latest CM11 4.4.4rc2 Kitkat - CROMBi-kk source - maintained by lj50036!
- Merged rom from 2 sources to introduce universal installer for 4 devices
- Updated device ID for TF201 which should fix wifi issues
- Updated options with TF700 and ME301, kernels + Device IDs!
- Dynamic fsync properly enabled on Grimlock kernel when fsync disabled selected in installer
- Made Google Calendar install by default as too many apps rely on it
- Updated Google Chrome to version 36.0.1985.135
- Updated Google Maps to version 8.3.1
- Updated Google Search to version 3.6.14
- Updated YouTube to version 5.9.0.13
- Updated ESFileExplorer to version 3.2.0
- Removed DropBox as bloatware (30MB!) - still available on the Play Store
- Removed Google Plus as bloatware (33MB!) - still available on the Play Store
- Removed alternate stock browser as no longer required
- Set default options to sbdags recommended for best performance
20140811 changes
- ROM is now Release Candidate 2! RC1 cleared private testing.
- ROM Version is CROMBi-kk_RC2 KitKat-4.4.4rc2-CM11-DEODEX
- Added my Intergalactic Ultra Touch (TM) settings to ROM Super snappy now
- Updated the Grimlock CM11 kernel to version 2 - thanks hardslog
- Changed the dalvik vm optimisation to reduce heap closer to stock as I think Garbage Collection wasn't happening frequently enough and when it did it took too long
- WiFi scan interval reset to 180
- Changed Zip Align script to a more recent version and added SQL Lite tweaks
- Can't see benefit of B2R script so default is off now
- Browsers now have their own section in installer
- Dolphin Browser with Adobe Flash both moved to system apps
- Tidied up gapps package from PA Gapps
- Updated Google Music to version 5.6.1617P
- Updated Google Maps to version 8.2.0
- Updated Google Hangouts to version 2.1.317
- Updated Google Chrome to version 36.0.1985.131
- Updated Google Core Services to version 5.0.89
- Updated Apex Launcher to Version 2.5.0
- Updated ESFileExplorer to version 3.1.9.1
- Updated GravityBox to 3.2.5
- Removed phab7 from xposed modules (no longer works on 4.4.x)
- Removed betterbean theme
- Added Android-L theme and Light / Dark variants
- Rebuilt from CM11 4.4.4 Kitkat - CROMBi-kk source - maintained by lj50036!
- Fixed the settings - staus crashing
- Fixed the screen not shutting off when closing the lid when docked - thanks psudeke!
- Lowered GPU values for TF201 users which should stop tearing and glitches
- Doubled the fling values for extra screen responsiveness
- Updated permissions to 4.4.4 CM11 set in updater script
- Repacked latest CM11 kernel with init10 functionality for ROM2SD/DATA2Sd and F2FS support
- Added latest Grimlock CM11 kernel v1.0 for the TF300 - thanks Hardslog
- Added Google Chrome as an option to install to /system/app
- Added option to remove the Stock Browser from /system/app
- Added Viper4Android Music FX as an option to replace CM DSP Manager
- Rom has SuperUser enabled by default now
- More virtual machine dalvik tweaks to speed things up
- Updated Apex Launcher to version 2.4.1
- Updated YouTube to version 5.7.41
- Updated Google Maps to version 8.1.1
- Updated Google Plus to version 4.4.3.69327528
- Updated Google Search to version 3.5.16
- Updated Google Music to version 5.6.1609P
- Updated Google Hangouts to version 2.1.311
- Updated Google Core Services to version 5.0.84
- Updated DropBox to version 2.4.2
- Updated Apex Launcher to version 2.4.0
- Updated Nova Launcher to version 3.0.1
- Updated Gravity Box to version 3.2.4
- Updated ESFileExplorer to version 3.1.8
- Beta - Tweaked Touchscreen sensitvity to the max for a very responsive experience
20140512 changes
- Rebased off latest CM11 source
- Kernel installer algorithm cleaned up to allow rom2sd, data2sd and f2fs selection management
- Compiled static busybox for /system/boot which fixes preinit issues for data2sd and rom2sd - thanks _that for your help
- Fixed f2fs on internal and external not working with data2sd (bug in fstab and installer)
- More fixes to f2fs installer routines and preinit scripts - added combinations of ext4 and f2fs
- Fixed _that wifi and bluetooth module compatibilty problems with _that kernel
- Changed the init mount point for f2fs to use the discard option on internal data only
- Cleaned up installer script
- ROM2SD and DATA2SD now working with normal CROMBi-kk on internal!
- Updated grimlock kernel to 2.4 for both TF300 and TF201 - thanks hardslog
- Updated ME301 compatibility packs included OC from hardslog
- Updated 2 new animations (red and blue) from psudeke
- Updated Google Calendar to version 201404014
- Updated Google Core Services to latest version
- Updated Google Plus to version 4.3.1.63038142
- Updated Google TTS to version 3.0.11
- Updated Hangouts to version 2.1.0
- Updated ESFileExplorer to version 3.1.3
- Updated DropBox to version 2.4.1
- Updated Dolphin Browser to verison 10.3.1
- Updated Google Maps to version 8.0.0
- Updated Google Search / Now to version 3.4.16.1149292
- Updated YouTube to version 5.6.36
- Updated Apex Launcher to version 2.3.3
- Updated Titanium Backup to version 6.1.5.5
- Updated Xposed Framework to version 2.5.1
- Updated Gravity Box to version 3.1.0
- Updated Google Music to version 5.5.15110.1148372
- Added inverted blue CM Theme as it's rather pretty
20140318 changes
- Fixed CM11 kernel not installing correctly from Aroma
- Removed TeleServices.apk to stop fc on boot in com.android.phone
20140317 changes
- Rebuilt from new base from lj50036 - Includes dock fixes (java) from CM11 source
- Fixed com.android.phone force close issues
- Fixed Grimlock kernel installing incorrect modules
- Fixed _thatv8 kernel with updated init and init.cardhu.cpu.rc for better cpu mode support - thanks ebildude123
- Fixed installer so hopefully users won't have an issue with addon.d scripts
- Fixed the CM11 backup and restore scripts not running as ro.cm.version was missing CM11
- Fixed : ROM2SD now correctly maps internal partitions to /datai, /systemi and /storage/sdcardi
-----ROM2SD still only works with a 4.2 JB ROM on internal
- Fixed : DATA2SD now offered again - currently uses _that v8 kernel
- Terminal Emulator lib file only installed when option is chosen in installer
- Added NTFS and extFAT support to stock based kernels
- Added Dolphin Browser and JetPack with FlashPlayer in installer as this is the only way to use flash in KitKat right now
- Updated Stock Browser Icon to Asus 4.3 version
- Updated Nova Launcher to version 2.3
20140315 changes
- Rebuilt from new base from lj50036 - Includes dock fixes (java) from CM11 source
- Repacked _thatv8 kernel with updated init and init.cardhu.cpu.rc for better cpu mode support
- Repacked Hunds 3.4.5 kernel with LetMeKnow's Extreme Tweaks
- Fixed installer so hopefully users won't have an issue with addon.d scripts
- Fixed the CM11 backup and restore scripts not running as ro.cm.version was missing CM11
- Fixed : ROM2SD now correctly maps internal partitions to /datai, /systemi and /storage/sdcardi
-----ROM2SD still only works with a 4.2 JB ROM on internal
- Fixed : DATA2SD now offered again - currently uses _that v8 kernel
- Terminal Emulator lib file only installed when option is chosen in installer
- Added NTFS and extFAT support to stock based kernels
- Added Dolphin Browser and JetPack with FlashPlayer in installer as this is the only way to use flash in KitKat right now
- Updated Stock Browser Icon to Asus 4.3 version
- Updated Nova Launcher to version 2.3
- 20140315 GApps Package updated. See post 2 for changelog
20140314 changes
- Updated Adobe Flash version to hacked version to test with 4.4
- Updated Adaway to version 2.8.1
- Updated Terminal Emulator to version 1.0.58
- Build.prop edit to increase scroll sensitivity
ro.min.fling_velocity=30000
ro.max.fling_velocity=60000
20140312 changes
GApps Package updated. See post 2 for changelog
20140309 changes
- lj50036 has rebased the Rom from CM11 source. No more CMB reliance
- Repacked all 3 kernels so up to date with CM11 changes
- Added Cyanogen Stock Bootanimation as option
- Inverted calendar removed and replaced with stock Google one
- Split GPU rendering into 2 parts - Need to test differences:
Part 1 forces GPU Rendering for 2D operations in the build.prop
Part 2 forces software rendering to be disabled thus the GPU must be used
- Cleaned up updater-script as not using CM Backup / Restore functionality for now
- Added tweaked Browser.apk back in as well as media codecs and lib file for Terminal Emulator
20140308 changes
- Fixed Aroma script error meaning 95CleanTweaks not being given correct permissions to run as init.d
- Reset CPU profiles in the ramdisk so they mirror the ones we are used to from CROMi-X in terms of speed and fps limits
- That's kernel OCs to 1.8GHz with balanced at 1.5GHz and power saving at 1GHz
- lj50036's kernel OCs to 1.7GHz with balance at 1.5GHz and power saving at 1GHz
- Hunds's kernel OCs to 1.8GHz with balanced at 1.6GHz and power saving at 1.4GHz
- Attempted to fix issue with some users not being able to install to ROM2SD - but still broken if CROMBi-kk is on internal
- Updated media codecs from another CM11 build. Hopefully it'll fix dice and other video content
- Recompiled Browser.apk with speed tweaks as they got lost in a recent build
- If ROM2SD is chosen in installer then TWRP stays in ROM2SD mode until a reboot
- Gapps can be flashed to ROM2SD without needing the rom2sd1.zip if flashed straight after the rom installer
- Updated ES FIle Explorer to version 3.1.0.3
20140306 changes
- Updated GravityBox to version 2.9.8
- Final tidy up of ROM and scripts for release
20140305 changes
- Fixed the ROM2SD booting issues - thanks _that!
- New extract ramdisk script to solve the above
- Repacked the 2 CM11 kernels with thatv9 init binary which fixes empty last_kmsg issues
- Remixed Hunds 3.4.5 OC kernel with CM11 ramdisk - experimental not sure it works well
- Updated Titanium Backup to version 6.1.5.4
20140304 changes
- Added ROM2SD and DATA2SD scripting to installer
- Updated the stock CM11 kernel to include pre-init scripting - enables Data2sd & Rom2sd
- Updated Apex Launcher to version 2.30
- Removed CM11 _that kernel for now as wifi non functional due to missing modules during compilation
- Added script to upgrade build.prop from CROMBi-X to CROMBi-kk
20140303 changes
- Fixed Xposed not installing properly
- Added Asus _that kernel repacked with CM11 ramdisk and preinit compatibility
- Fixed missing modules from lj50036 & _that kernel
- Fixed Nexus Flow Bootanimation finishing too early
- Added phab7 as a test
- ROM name changed to CROMBi-kk
20140302 changes
- Built Aroma Script for main ROM installer
- Added new thatv8 kernel for CM11
- Updated dropbox to version 2.3.12.10
- Updated Terminal Emulator to version 1.0.57
20140301 changes
- Added Browser to RAM script
- Repacked Browser.apk with debug options on by default for speed - see labs options
- Added CleanTweaks init.d script from CROMi-X 5.4 as a test (need to analyse what is compatible)
- Build.Prop tweaks from CROMiX
Click to expand...
Click to collapse
Click to expand...
Click to collapse
The Team
@sbdags - Creative Mastermind (From CROMi-X)
@lj50036 - Source Guy (From CMB ROMS)
@hardslog - The Canadian (From Grimlock ROMS)
Credits
Google, wow is all I can say!
CyanogenMod we wouldn't be doing this if if weren't for them (even if they are for profit now hah).
CMB for the basis of our Gapps package!
nycbjr (CMB ROMS team leader) Thx for all the time teaching me the way (lj50036)!!!!
_that For all the great advice!!!!!
To Do
Add Aroma to Gapps Package
Add Asus Apps as separate install
More Kernels and Tweaks
XDA:DevDB Information
CROMBi-kk, a ROM for the Asus Transformer TF201, ROM for the Asus Eee Pad Transformer Prime
Contributors
lj50036, sbdags , hardslog, _that
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.1.x
ROM Firmware Required: V 10.6.1.27.1
Based On: CyanogenMod 11 AOSP
Version Information
Status: Beta
Current Beta Version: 20140906
Beta Release Date: 2014-03-18
Created 2014-06-05
Last Updated 2014-10-11
Reserved
UPGRADE INSTRUCTIONS
REFER TO POST #4 FOR UPGRADE INSTRUCTIONS​FLASHING THE ROM FROM RECOVERY
Steps
1. Download the ROM below and save to your internal or external SD Card. Do not unzip the file.
CROMBi-kk ROM DOWNLOAD
Note: The first boot after install will take 10 mins whilst everything is built. Some people might think it is looping but it is not
CROMBi-kk Current Release Full Mirror 1
CROMBi-kk Current Release Full Mirror 2
CROMBi-kk Current Release Full Mirror 3
ASUS APPS DOWNLOAD - Flash from Recovery : Compiled by kansasboy001
Asus Battery Widget, Asus Calculator, Asus Calendar, Asus Clock, Asus Dayscene Live Wallpaper, Asus Dictionary, Asus Email, Asus Gallery, Asus Keyboard, Asus Photo Story, Asus Sound Recorder, Asus Tasks, My Frame, My Water I & II, Asus Supernote Pro, Weather & Time Widget, Asus Framework, Asus Settings, Asus Audio (V4A), Asus Contacts, Asus File Manager(Root Browser), Asus Camera, Asus Browser
[THREAD][APPS] [ASUS Apps][ CROMBi-kk & ZOMBi-kk]
GOOGLE APPS (GAPPS) DOWNLOAD - NO LONGER NEEDED!
GAPPS NOW INCLUDED AS OPTIONS IN MAIN ROM ZIP
Change Log
crombi_kkgapps_20140315
Updated YouTube to version 5.5.27
Updated Google Maps to version 7.7.0
Updated Google Search and Libs to version 3.3.11
crombi_kkgapps_20140312
Updated Google Calendarsync adapter to latest version
Fixed the issue of GApps not flashing if not done directly after ROM
crombi_kkgapps_20140309
Updated Google Bookmarksync adapter to latest version
crombi_kkgapps_20140308
If Gapps is flashed after CROMBi-kk it should now in ROM2SD mode - no ROM2SD1.zip required
Updated Google TTS to version 3.0.10.1047791
crombi_kkgapps_20140306
Removed calendarprovider.apk from gapps as conflicted with calendar app in rom
crombi_kkgapps_20140301
Updated updater-script
Updated Google Plus to version 4.3.0.62241793
Updated Google Core Services and lib files to latest version
Updated Google Experience Launcher to version 1.0.9
crombi_kkgapps_20140223
Updated Gmail2 to version 4.7.2
Updated Hangouts and lib files to version 2.0.303
Updated Google Maps to version 7.6.1
Updated YouTube to version 5.3.32
Updated Google Now and lib files to version 3.2.17.1009776arm
Updated Play Store to version 4.5.10
Removed Google Calendar as a version is already provided in rom
ROM2SD INSTRUCTIONS PLEASE READ!
ROM2SD only works if you have CROMi-X, miniC flashed on internal. Just choose ROM2SD in the installer of CROMBi-kk to flash it to ROM2SD and the installer will do the rest.
ROM2SD USERS PLEASE CLICK HERE
- Install CROMBi-kk and choose ROM2SD install
- Flash ROM2SD1.zip No longer required
- Flash GAPPS Package No longer required
- Flash Wifi ROM2SD Patch No longer required
2. Boot to recovery – Either choose Boot to Recovery from the Power Menu if available on your current ROM or from the tablet power off hold the [volume down] button and press the [power] button. Once your see the flashing RCK icon, press [volume up] to select. If another icon is flashing use [volume down] to move between icons.
3. Using your recovery make a Nandroid Backup of your current setup
4. Select install and navigate to where you saved your ROM zip file.
5. Choose the CROMBi-kk zip file and follow the on screen prompts to customize your installation.
6. Choose the wifi patch and flash..
7. Reboot and enjoy.
SDCARD SETUP PLEASE CLICK HERE
Using GParted to setup a micro SD for ROM2SD support
First and foremost - DO NOT USE MINI TOOL!
Formatting a micro sd card for ROM2SD
We will be using a GParted Live boot USB and a FAST good quality micro sd like a Sandisk or Samsung Class 10 - SDHC/SDXC UHS-1 card with read speed of at least 20MB/S. If you have a cheap chinese eBay card don't bother - they are not good enough.
You will also need a USB Stick with at least 1GB size. Note this process formats the USB disk so don't keep any important files on it. It will also wipe your micro sd so make sure you are prepared.
1. Go to the link below and download the GParted Live CD/USB/HD/PXE Bootable Image and save it somewhere you remember
http://gparted.sourceforge.net/download.php
2. Download Linux Live USB Creator and install it
http://www.linuxliveusb.com/
3. Fire up LiLi USB Creator:
a. Choose your USB key - I,e, the drive letter for your USB (not sd card)
b. Choose your GParted iso image for the source
c. Choose the check box to Format Key in FAT32 and hide files
d. Click the lightning bolt to create
4. Now you have a bootable disk you need to boot from it. You may need to alter you BIOS Settings on your PC to boot from a USB Stick but mine did it without messing.
5. Insert your micro SD card into an SD Card adapter and insert into PC
6. Boot into GParted
7. Choose Gparted Live <Enter>
8. Don’t touch keymap <Enter>
9. Languge <Enter>
10. Start Gparted Automatically
11. Change device to your micro sd )it will default to you hard disk - hda– mine is /dev/sdc
12. Delete all existing partitions
For a 64GB card: (resize as needed but /system doesn't need to be bigger than 1GB)
13. Create new, always select primary: do this 3 times.
14. FAT 32 : Size 16GB – this will be /dev/sdc1 in gparted and will be your sdcard for storage in Android
15. EXT4 : Size 42GB – this will be /dev/sdc2 in gparted and will be your /data partition in Android
16. EXT4 : Size 1GB – this will be /dev/sdc3 in gparted and will be your /system partition in Android
Apply, wait until it finishes and then reboot. Remember to remove the usb stick
*Images stolen from elsewhere as I couldn’t get it to save mine
Now you are ready to install ROM2SD. Note if you want to use DATA2SD then only do 2 partitions 1x FAT32 and 1x larger EXT4
Then reinstall CROMBi-kk but this time choose the ROM2SD option
HUGE THX
@spudsmac
@miduku
@robbie888
@lightiv
@Bigred007
@Waldo_
@emfanitek
@rlanza1054
@Unidave199
@Lock-N-Load
@Fear Knot
@lvrijn
@mitsublw
@scouzers
@zdebel
@jhr5474
@Eddie Hicks
@smchadwell
@dladz
@eRPeeX
@LocusofZen
Thx everyone that have donated, if you do not see your user name here and have donated, shoot me an PM and I will add you....
Thx Josh
Take a look
UPGRADE INSTRUCTIONS, STEP BY STEP​
This may help
Starting from a stock bootloader V 10.4.2.18
What you will need
Woking fastboot & adb / SDcard optional
TWRP for a 201 = twrp_tf201t.blob
@ne0zone75 TWRP for the 300 = ne0zone75_tf300t.blob
HairyBean BL & TWRP: This is effectively turn your 201 into a 300 <---- which is a flashable zip inside the zip that you downloasd
All 3 of the above file are in a zip in the Download section @ the top of every page of the thread ...... THIS ZIP IS NOT FLASHABLE...Your must unzip it to get to the real files !!! The name of this zip is 'upgrade_tf201_to_tf300t.zip'
CROMBI 201 ROM zip
A fully charged tablet
All the above files in the same directory as your fastboot.exe (if using windows) In your home folder on linux....
The process
Lets start with the TWRP recovery for the 201, let flash it with fastboot...
Power your tablet off and with the [ VOL DOWN & POWER ] buttons boot the tablet into the bootloader
Once there [ VOL DOWN ] untill the green box is on the USB ICON then [ VOL UP ] to select fastboot
Let make sure your PC can see your tablet with this command.
Code:
fastboot devices
Code:
fastboot -i 0x0b05 flash recovery twrp_tf201t.blob
Then
Code:
fastboot -i 0x0b05 reboot-bootloader
[ VOL UP ] ON RCK to enter recovery
Once in TWRP check to see if adb is working...
Code:
adb devices
Ok now that we know that is working let go ahead and push the HairyBean BL onto the tablet
Code:
adb push HairyBean_Bootloader_TWRP2.5.zip /sdcard
Now under the install tab in TWRP fine the folder and flash it....
reboot once it has fishined..If ask to install SuperUser say NO..........
LET THE BLUE BAR FILL !!!!!!!!! Once it has finished it will reboot into Hairybean TWRP....
Once booted into recovery, run this command to boot into fastboot
Code:
adb reboot-bootloader
You will see that the USB icon is missing now, this is good... If you still see the USB icon DON'T go to the next step
Now lets flash @ne0zone75 TWRP recovery
Code:
fastboot -i 0x0b05 flash recovery ne0zone75_tf300t.blob
Once that has finished let reboot into bootloader
Code:
fastboot -i 0x0b05 reboot-bootloader
Now enter recovery....
Make sure its verison 2.7.1.0
Go to Wipe////Format Data////Type yes
This can take up to 90 mins to format
DO NOT INTERRUPT THE FORMAT !!!!!!!
Now lets push CROMBI-KK onto your tab
Code:
adb push cm-11.0-2014xxxx-crombi-kk-tf201t.zip /sdcard
Find it under the install tab and flash it..
REBOOT into android, first boot can take up to 15 minutes
Kernel Sources
All Kernels included in this ROM package are unofficial, as they are complied from source, thay may not match the source that they were forked from. I will be linking the kernel source code as per the GNU GPL License.
Unofficial @hardslog Grimlock Kernel Source CLICK ME@-V1.0.0
Unofficial CM-11.0 Kernel Source CLICK ME@-V1.0.0
Unofficial @_that Kernel Source CLICK ME @-V1.0.0
Official @hardslog Grimlock Kernel Source CLICK ME
Official CM-11.0 Kernel Source CLICK ME
Official @_that's Kernel Source CLICK ME @-V11
Hi Josh its a good idea letting other TF201 users know about this rom, it might also be good to mention and to link to the bootloader/twrp downgrade file as well.
Sent from my Transformer Prime TF201 using XDA Premium HD app
The dumb questions up front!
So, I'm already on Hairybean 2.31 so I'm already unlocked so I would already meet the requirement you have up front: "YOU MUST BE ON THE HAIRYBEAN 2.31 JB 4.2.1 BOOTLOADER"
So I should be able to just flash the zip file I downloaded from step 2 of the instructions to update my TWRP and then flash the ROM, correct?
ratman6161 said:
So, I'm already on Hairybean 2.31 so I'm already unlocked so I would already meet the requirement you have up front: "YOU MUST BE ON THE HAIRYBEAN 2.31 JB 4.2.1 BOOTLOADER"
So I should be able to just flash the zip file I downloaded from step 2 of the instructions to update my TWRP and then flash the ROM, correct?
Click to expand...
Click to collapse
yes, but do a full wipe before flashing the rom
Sent from my Transformer Prime TF201 using XDA Premium HD app
This is awesome dude, can't wait to give it a try.
Check out my website for encouragement....
www.projectintercession.blogspot.com
boldnuts said:
yes, but do a full wipe before flashing the rom
Sent from my Transformer Prime TF201 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks, I'll be trying this out tonight. Also I appreciate you doing a TF201 specific posting. I've been looking at the stuff over on the TF300 forum and it was looking like it should work, but its sure nice to have it here.
I will just post a testimonial here for newcomers. I have been using this ROM as a daily driver ever since it was released a few months ago. I have to admit that it is speedy and lovely. The F2FS feature in the new version of the ROM gave me that much more RAM and I don't feel the degrade I once did with the tablet on other ROMs on the forum. Gaming, movies, browsing, it does it all with good speed.
lj50036 said:
You never Know
Click to expand...
Click to collapse
To ALL doubters this Rom is the JAM ! and lj50036 is the go2MAN ! If you want a TF300 , but have a TF201 this is the ROM that you NEED to install ....
NOW !
feyerbrand said:
I will just post a testimonial here for newcomers. I have been using this ROM as a daily driver ever since it was released a few months ago. I have to admit that it is speedy and lovely. The F2FS feature in the new version of the ROM gave me that much more RAM and I don't feel the degrade I once did with the tablet on other ROMs on the forum. Gaming, movies, browsing, it does it all with good speed.
Click to expand...
Click to collapse
You originally turned me on to the TF300 thread many months ago and I been there ever since. Thanks for this.
I have to concur, these guys have really improved upon all the latest Droid releases and kept me from wanting to sell this (now a) dinosaur of a tablet. Good ****.
:good:
Excellent job @lj50036. :good: I'm gonna try this soon.
Thanks...
Best Regards
Initial Impressions
Just installed the ROM last night. Coming from Hairy Bean 2.31 it was extremely easy to install. Just had to flash the .zip for the updated TWRP and then Flash the ROM. It should be almost as easy for those not on Hairy Bean as you would just have one more step which is to flash the HB boot loader. But overall I found the procedure to be incredibly easy and low risk.
Once installed the ROM works great. Seems nice and fast and smooth though I have not had a chance to use it extensively yet. One minor nit I noticed is that in the CPU settings the maximum CPU speed seems to default to 1800 MHZ and I think most Primes will not like that. I know mine wouldn't like anything over 1700 so I would recommend changing that before checking the "apply at start up" box.
After doing the initial install and letting my apps download from Google Play I decided to take the plunge and turn on ART. This really works well on my Motorola Droid Maxx phone so I figured I'd try it. It was a no go (though not really a bug because there are warnings all over it about being experimental). The system got stuck in a boot loop where I would get the boot animation and it would sit there for a long time...before spontaneously restarting and repeating. The back of the tablet (I'm assuming where the CPU must be felt decidedly warm to the touch. Anyway, this isn't a huge deal since I kind of didn't expect ART to work on this device. If anyone else has it working I'd like to hear about it.
ratman6161 said:
Just installed the ROM last night. Coming from Hairy Bean 2.31 it was extremely easy to install. Just had to flash the .zip for the updated TWRP and then Flash the ROM. It should be almost as easy for those not on Hairy Bean as you would just have one more step which is to flash the HB boot loader. But overall I found the procedure to be incredibly easy and low risk.
Once installed the ROM works great. Seems nice and fast and smooth though I have not had a chance to use it extensively yet. One minor nit I noticed is that in the CPU settings the maximum CPU speed seems to default to 1800 MHZ and I think most Primes will not like that. I know mine wouldn't like anything over 1700 so I would recommend changing that before checking the "apply at start up" box.
After doing the initial install and letting my apps download from Google Play I decided to take the plunge and turn on ART. This really works well on my Motorola Droid Maxx phone so I figured I'd try it. It was a no go (though not really a bug because there are warnings all over it about being experimental). The system got stuck in a boot loop where I would get the boot animation and it would sit there for a long time...before spontaneously restarting and repeating. The back of the tablet (I'm assuming where the CPU must be felt decidedly warm to the touch. Anyway, this isn't a huge deal since I kind of didn't expect ART to work on this device. If anyone else has it working I'd like to hear about it.
Click to expand...
Click to collapse
Thx for your feelback mate....:good:
The reboot after enabling ART can take 10 -15 mins....
Take a logcat of the boot and you will see lots of things happening....
If you see the same thing happening over and over then yes thats a biootloop
Can anyone else confirm ART not booting up ??
THx Josh
lj50036 said:
Thx for your feelback mate....:good:
The reboot after enabling ART can take 10 -15 mins....
Take a logcat of the boot and you will see lots of things happening....
If you see the same thing happening over and over then yes thats a biootloop
Can anyone else confirm ART not booting up ??
THx Josh
Click to expand...
Click to collapse
art is working ok on my prime, I am using the f2fs file system though, so different kernel and keeping the overclock to 1600
Sent from my Transformer Prime TF201 using XDA Premium HD app
boldnuts said:
art is working ok on my prime, I am using the f2fs file system though, so different kernel and keeping the overclock to 1600
Sent from my Transformer Prime TF201 using XDA Premium HD app
Click to expand...
Click to collapse
So I'm still downloading the needed files, but is the f2fs option apart of the initial setup process? I've done some reading on it and would like to give it a try. Also had anyone tried the ROM to sdcard option yet? Thanks
Check out my website for encouragement....
www.projectintercession.blogspot.com
LOOK
Pictures are worth a thousand words...
andrewjt19 said:
So I'm still downloading the needed files, but is the f2fs option apart of the initial setup process? I've done some reading on it and would like to give it a try. Also had anyone tried the ROM to sdcard option yet? Thanks
Check out my website for encouragement....
www.projectintercession.blogspot.com
Click to expand...
Click to collapse
for f2fs you have to flash the correct version of twrp, then format your data partition as f2fs, then reinstall the rom
http://forum.xda-developers.com/showthread.php?t=2625580
Sent from my Transformer Prime TF201 using XDA Premium HD app
---------- Post added at 04:51 PM ---------- Previous post was at 04:51 PM ----------
lj50036 said:
Pictures are worth a thousand words...
Click to expand...
Click to collapse
cant wait!
Sent from my Transformer Prime TF201 using XDA Premium HD app

[KERNEL][AOSP 4.4.4/5.x|CAF][UNIFIED ghost | moto_msm8960dt][TDHK 09/20/2015]

TDH Kernel for the Moto X Unified (CAF)
The kernel is that which manages the phone at a fundamental level. To learn more, see the "Index of Documentation for People Interested in Writing and/or Understanding the Linux Kernel."
How I Support This Work:
Donations always work
Thanks buttons also work wonders. Don't forget to hit the Thanks button for those whose work benefits you.
If I don't respond to a question, there is a very high likelihood the answer already exists in this thread -- use search as I rarely forget what's already covered.
Working Features:
AOSP
Best battery life (kernel installs init.d script to setup SmartMax governor)
Governors: SmartMax, Intelliactive, interactive, ondemand, userspace, powersave, performance (more coming if relevant -- 'marketing checkmarks' -- a.k.a. useless but stuck in just for feature count -- won't get into this kernel)
Optional IOSched: Noop, Deadline, CFQ, BFQ, FIOPS, SIO (more coming if relevant -- same comment applies as for Governors)
Optional GPU Governors= Performance, Ondemand, Simple, Interactive
User voltage control
Kexec support
Initial Kexec support
ExFAT support
KSM optimizations
Enhanced NEON support
Reduce kswapd schedule enhancement
EXT4 file system speed ehancements
Many stability and optimizations upgrades.
In progress / futures (not stable yet) ...
Overclocking/underclocking options (in progress ... sigh , coming soon)...
Optional GPU overclocking
Doubletap2wake
Logo2wake
Pocket detection
Logo2menu.
Credits go to many, but most particularly:
Linus Torvalds (for Linux itself)
Flar2
Faux123
ThickLizard
TBaldin
A lot of other kernel devs whose code I read regularly to learn
All the Moto X Community
Instructions:
READ THE DISCLAIMER.
Download the kernel
Reboot into Recovery
Nandroid backup
Flash the kernel
Enjoy
Things to Know:
The flash uses standard 'by-name' partitions, so should install correctly on most AOSP based ROMs
The flash supports the CM11 standard /data/local/userinit.d init script (99-tdhk)
That script will delay one minute after boot and force the SmartMax governor on all cores
FIOS is the default IO scheduler
No need for Trickster or Performance Settings if you want those defaults (which you should)
KERNEL SOURCE
Enjoy.
XDA:DevDB Information
TDHK, Kernel for the Moto X
Contributors
tdhite, skiwong20
Source Code: https://github.com/tdhite/android_kernel_motorola_msm8960dt-common
Kernel Special Features: Governors, schedulers, sleep/wake options, battery tweaks, performance tweaks.
Version Information
Status: Stable
Current Stable Version: KitKit: 12/21/2014;
Stable Release Date: 2015-09-20
Created 2014-07-19
Last Updated 2015-09-20
Disclaimer
*** Legal Disclaimer -- READ ALL OF THE FOLLOWING ***
If you use any of the software provided by this thread, or convey such software to
someone else, you and all subsequent conveyees are bound by the following:
# LEGAL DISCLAIMERS AND ASSUMPTION OF THE RISK BY THE USER OF THIS PROGRAM
# Assumption of the Risk of Use
# YOU ASSUME, AND AGREE TO ASSUME, ALL THE RISK OF HARM BY USING THIS
# PROGRAM. THIS PROGRAM MAY VOID YOUR WARRANTY WITH A THIRD PARTY,
# IT MAY IMPROPERLY OPERATE AND DAMAGE YOUR DEVICE, IT MAY CAUSE ANY
# MYRIAD OF HARMFUL OUTCOMES REGARDING YOUR DEVICE OR THE USE OF THE DEVICE
# ON WHICH IT GETS INSTALLED. YOU ACKNOWLEDGE THAT YOU ARE AWARE OF THOSE
# RISKS, UNDERSTAND THOSE RISKS, AND VOLUNTARILY AND INTELLIGENTLY ELECT
# TO ENGAGE THOSE RISKS BY USING THE PROGRAM.
#Disclaimer of Warranty.
# THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE
# LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
# OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND,
# EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
# WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
# THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH
# YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME ALL LIABILITY AND
# AGREE THAT IN NO EVENT WILL YOU SEEK ANY FORM OF RECOMPENSE, WHETHER LEGAL OR
# EQUITABLE, INCLUDING BUT NOT LIMITED TO NECESSARY SERVICING, REPAIR,
# CORRECTION OR OTHERWISE.
#Limitation of Liability.
# IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL
# ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE
# PROGRAM, PERMITTED OR NOT, BE LIABLE TO YOU FOR LEGAL DAMAGES OR EQUITABLE
# RELIEF, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES
# ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT
# LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED
# BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
# PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
# POSSIBILITY OF SUCH DAMAGES.
Downloads
KERNELS (Current):
Download: TDHK-Ghost Lollipop 09-20-2015
This kernel is for LolliPop AOSP ROMs
Change Logs
Use the latest TWRP or latest CWM/PhilZ Recovery to flash as the installer uses 'by-name partitioning';
This kernel should work for any 'ghost' AOSP Lollipop ROM -- of course read the DISCLAIMER post.
Download: TDHK-Ghost KitKat 12-21-2014
This kernel is for KitKat AOSP ROMs *after* the unified 'ghost' ROM model;
Change Logs
Use the latest TWRP (suggest 2.8.0.1 or greater) or latest CWM/PhilZ Recovery to flash as the installer uses the new by-name partitioning;
This kernel should work for any 'ghost' AOSP rom -- of course read the DISCLAIMER post.
Download: TDHK-MotoX 08-31-2014
This kernel is for ROMs *before* the unified 'ghost' model;
Change Logs
Use the latest TWRP (suggest 2.8.0.1) or latest CWM/PhilZ Recovery to flash as the installer uses the new by-name partitioning;
This kernel should work for any 'msm8960dt' AOSP rom -- of course read the DISCLAIMER post.
IMPORTANT:
If you wipe Dalvik Cache, let the phone boot completely once, then reboot again (long story, but AOSP roms set a property on Android that triggers your selected 'performance' settings (e.g., performance, balanced, whatever), when you clear Dalvik that property set trigger runs rather late and the init.d script delay setup by this kernel to force smartmax onto the CPU cores might already have happened, so you end up with the old governors (ick!). Reboot and all should be fine.
Another option is to open a terminal window and 'su' to root privileges, then type "set prop sys.perf.profile 99". No need to reboot if you do this.
OLD Releases:
Download: TDHK-Ghost Lollipop 09-17-2015
This kernel is for LolliPop AOSP ROMs
Change Logs
Use the latest TWRP or latest CWM/PhilZ Recovery to flash as the installer uses 'by-name partitioning';
This kernel should work for any 'ghost' AOSP Lollipop ROM -- of course read the DISCLAIMER post.
B]Download: TDHK-Ghost Lollipop 08-07-2015[/B]
This kernel is for LolliPop AOSP ROMs
Change Logs
Use the latest TWRP or latest CWM/PhilZ Recovery to flash as the installer uses 'by-name partitioning';
This kernel should work for any 'ghost' AOSP Lollipop ROM -- of course read the DISCLAIMER post.
Download: TDHK-Ghost Lollipop 07-20-2015
This kernel is for LolliPop AOSP ROMs
Change Logs
Use the latest TWRP or latest CWM/PhilZ Recovery to flash as the installer uses 'by-name partitioning';
This kernel should work for any 'ghost' AOSP Lollipop ROM -- of course read the DISCLAIMER post.
Download: TDHK-Ghost Lollipop 06-28-2015
This kernel is for LolliPop AOSP ROMs
Change Logs
Use the latest TWRP (suggest 2.8.6.0) or latest CWM/PhilZ Recovery to flash as the installer uses 'by-name partitioning';
This kernel should work for any 'ghost' AOSP Lollipop ROM -- of course read the DISCLAIMER post.
Download: TDHK-Ghost Lollipop 05-24-2015
This kernel is for LolliPop AOSP ROMs
Change Logs
Use the latest TWRP (suggest 2.8.6.0) or latest CWM/PhilZ Recovery to flash as the installer uses 'by-name partitioning';
This kernel should work for any 'ghost' AOSP Lollipop ROM -- of course read the DISCLAIMER post.
Download: TDHK-Ghost Lollipop 04-06-2015
This kernel is for LolliPop AOSP ROMs
Change Logs
Use the latest TWRP (suggest 2.8.6.0) or latest CWM/PhilZ Recovery to flash as the installer uses 'by-name partitioning';
This kernel should work for any 'ghost' AOSP rom -- of course read the DISCLAIMER post.
Download: TDHK-Ghost Lollipop 01-11-2015
This kernel is for LolliPop AOSP ROMs
Change Logs
Use the latest TWRP (suggest 2.8.3.0) or latest CWM/PhilZ Recovery to flash as the installer uses 'by-name partitioning';
This kernel should work for any 'ghost' AOSP rom -- of course read the DISCLAIMER post.
Download: TDHK-Ghost Lollipop 12-21-2014
This kernel is for LolliPop AOSP ROMs *after* the unified 'ghost' ROM model;
Change Logs
Use the latest TWRP (suggest 2.8.0.1 or greater) or latest CWM/PhilZ Recovery to flash as the installer uses the new by-name partitioning;
This kernel should work for any 'ghost' AOSP rom -- of course read the DISCLAIMER post.
Download: TDHK-Ghost 10-26-2014
This kernel is for ROMs *after* the unified 'ghost' ROM model;
Change Logs
Use the latest TWRP (suggest 2.8.0.1 or greater) or latest CWM/PhilZ Recovery to flash as the installer uses the new by-name partitioning;
This kernel should work for any 'ghost' AOSP rom -- of course read the DISCLAIMER post.
Download: TDHK-Ghost 10-16-2014
This kernel is for ROMs *after* the unified 'ghost' ROM model;
Change Logs
Use the latest TWRP (2.7.1.1 or greater) or latest CWM/PhilZ Recovery to flash as the installer uses the new by-name partitioning;
This kernel should work for any 'ghost' AOSP rom -- of course read the DISCLAIMER post.
Download: TDHK-Ghost 10-05-2014
This kernel is for ROMs *after* the unified 'ghost' ROM model;
Change Logs
Use the latest TWRP (2.7.1.1 or greater) or latest CWM/PhilZ Recovery to flash as the installer uses the new by-name partitioning;
This kernel should work for any 'ghost' AOSP rom -- of course read the DISCLAIMER post.
Download: TDHK-Ghost 09-20-2014
This kernel is for ROMs *after* the unified 'ghost' ROM model;
Change Logs
This kernel should work for any 'ghost' AOSP rom -- of course read the DISCLAIMER post.
KERNEL (Enhanced -- no longer needed as integrated into standard kernel):
Download: TDHK-MotoX 08-10-2014
KERNEL):
Download: TDHK-MotoX 07-28-2014
Change Logs
Use the latest TWRP (2.7.1.1 or greater) or latest CWM/PhilZ Recovery to flash as the installer uses the new by-name partitioning;
This kernel should work for any AOSP rom -- of course read the DISCLAIMER post.
IMPORTANT!!!
If you wipe Dalvik Cache, let the phone boot completely once, then reboot again (long story, but AOSP roms set a property on Android that triggers your selected 'performance' settings (e.g., performance, balanced, whatever), when you clear Dalvik that property set trigger runs rather late and the init.d script delay setup by this kernel to force smartmax onto the CPU cores might already have happened, so you end up with the old governors (ick!). Reboot and all should be fine.
Another option is to open a terminal window and 'su' to root privileges, then type "set prop sys.perf.profile 99". No need to reboot if you do this.
Custom Kernel 07/17/2014
Use the latest TWRP (2.7.1.1 or greater) or latest CWM/PhilZ Recovery to flash as the installer uses the new by-name partitioning;
[*]SmartMax Tweaks (better battery credit: Rad Ryan);
[*]Startup (/data/local/userinit.d/99-tdhk) handling to force SmartMax governor on all cores;
[*]Rebased onto CM-11 MSM8960 Kernel Sources as of 07/17/2014;
[*]Make Nandroid backup;
[*]Flash in recovery after flashing ROM;
Change Logs
TDHK-Ghost Lollipop 09-20-2015
Maintenance release -- synced with CM12.x sources as of the date of the build.
Use this if you download a Lollipop 'ghost' ROM (e.g. CM 12.x ) .
TDHK-Ghost KItKat 12-21-2014
Synced with CM11 sources as of the date of the build.
Use this if you download a KitKat 'ghost' ROM.
TDHK-MotoX 08-31-2014
Fixes intermittent data drops for very latest ROM versions, as well is failures to load WiFi on the same.
Contains all updates to base kernel, CM11 and prior 'enhanced' version -- all as of date of build.
Use this if you download a msm8960dt based ROM.
Prior Releases
TDHK-Ghost Lollipop 09-17-2015
Maintenance release -- synced with CM12.x sources as of the date of the build.
Use this if you download a Lollipop 'ghost' ROM (e.g. CM 12.x ) .
TDHK-Ghost Lollipop 08-07-2015
Maintenance release -- synced with CM12.x sources as of the date of the build.
Use this if you download a Lollipop 'ghost' ROM (e.g. CM 12.x ) .
TDHK-Ghost Lollipop 07-20-2015
Fix multi-core governor (not)stickiness when cores go offline.
Synced with CM12.x sources as of the date of the build.
Use this if you download a Lollipop 'ghost' ROM (e.g. CM 12.x ) .
TDHK-Ghost Lollipop 06-28-2015
Maintenance release.
Synced with CM12.x sources as of the date of the build.
Use this if you download a Lollipop 'ghost' ROM (e.g. CM 12.x ) .
TDHK-Ghost Lollipop 05-24-2015
Maintenance release.
Synced with CM12.x sources as of the date of the build.
Disabled quickdraw (which was the brunt of CM12.x updates).
Use this if you download a Lollipop 'ghost' ROM (e.g. CM 12.x ) .
TDHK-Ghost Lollipop 04-06-2015
Maintenance release.
Synced with CM12 sources as of the date of the build.
Use this if you download a Lollipop 'ghost' ROM (e.g. CM 12.0 ) .
TDHK-Ghost Lollipop 01-11-2015
Intelliactive governor
Initial Kexec support
ExFAT support
KSM optimizations
Enhanced NEON support
Reduce kswapd schedule enhancement
EXT4 file system speed ehancents
Many stability and optimizations regarding buffer overruns and similar
Synced with CM12 sources as of the date of the build -- includes fix for NFC.
Use this if you download a Lollipop 'ghost' ROM (e.g. CM 12.0) .
TDHK-Ghost Lollipop 12-21-2014
Synced with CM12 sources as of the date of the build -- includes fix for NFC.
TDHK-Ghost 10-26-2014
Synced with CM11 sources as of the date of the build -- includes fix for NFC.
Use this if you download a 'ghost' ROM (e.g., pac_ghost-nightly-(date_goes_here)).
TDHK-Ghost 10-16-2014
Synced with CM11 sources as of the date of the build to pick up WiFi enhancements.
Use this if you download a 'ghost' ROM (e.g., pac_ghost-nightly-(date_goes_here)).
TDHK-Ghost 10-05-2014
Added user level CPU Voltage Control.
Use this if you download a 'ghost' ROM (e.g., pac_ghost-nightly-(date_goes_here)).
TDHK-Ghost 09-20-2014
Based on Ghost unified sources (should work on effectively any AOSP based ROM);
Contains all updates to base kernel, CM11 and prior 'enhanced' versions -- all as of date of build.
Use this if you download a 'ghost' ROM (e.g., pac_ghost-nightly-(date_goes_here)).
TDHK-MotoX 08-10-2014
Contains all that is in the Stable version.
Enhancements include upstream commits bringing the kernel up to 3.4.101.
Additional thanks to @dhacker29 for much of the upstream commits -- they're just not in CM yet, maybe one day ...
TDHK-MotoX 07-28-2014
Fixed SmartMax governor bug that caused screen to stay off after some reboots.
Changed bootup and governor setting model to support Android property model (sets up /init.target.rc to import /init.tdhk.rc, the latter of which triggers to set smartmax whenever the Android property "ro.perf.profile" is set to "99".
Yay! AOSP kernel..
Booted up great!
XT 1058 running leonardoafa unofficial carbon rom!
Thanks. Downloading to test on XT1053.
Flashed great. XT1058 on Dirty Unicorns
Can i install it on stock 4.4.2? Or just 4.4.4?
Sorry, dude. Not looking backwards, I doubt less than 4.4.4 will work but you can always flash any try.
Do me a favor and turn on the CPU options in the developer's options. See that the smartmax governor is on all cores.
Want to be sure the init.d script is properly executing on that ROM (DU).
Wi-Fi and Signal lost after installing on XT1053 (Stock 4.4.3)
Im just making sure, this only works on AOSP roms and not stock, right?
Kittiesoncrack said:
Im just making sure, this only works on AOSP roms and not stock, right?
Click to expand...
Click to collapse
Yip, that's right.
kenosis said:
Wi-Fi and Signal lost after installing on XT1053 (Stock 4.4.3)
Click to expand...
Click to collapse
4.4.4, not 4.4.3. Maybe one day I'll look at building backwards to others, but while stabilizing some new features, it's 4.4.4 or up.
Works great on the Droid Maxx!! Thanks man... Much needed!
What 4.4.4 rom is everyone using?
tdhite said:
Yip, that's right.
4.4.4, not 4.4.3. Maybe one day I'll look at building backwards to others, but while stabilizing some new features, it's 4.4.4 or up.
Click to expand...
Click to collapse
Thanks. Hope to see it for 4.4.3.
tdhite said:
Do me a favor and turn on the CPU options in the developer's options. See that the smartmax governor is on all cores.
Want to be sure the init.d script is properly executing on that ROM (DU).
Click to expand...
Click to collapse
{
"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"
}
Remember to quote so I'll get the notifications
@tdhite, can you provide the sources...
Sent from my GT-I9082 using Tapatalk
awesome job tdhite. thanks for your time on this project, so happy to see a CAF kernel available. ?
##W4TCH0UT## said:
@tdhite, can you provide the sources...
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
kernel source add to OP
Sent from my AOSP on Flo using XDA Free mobile app
skiwong20 said:
awesome job tdhite. thanks for your time on this project, so happy to see a CAF kernel available. ?
https://github.com/tdhite/android_kernel_motorola_msm8960dt-common
i will tell him later to add to op
Sent from my AOSP on Flo using XDA Free mobile app
Click to expand...
Click to collapse
It's not the source. It doesn't include the commits of features he has mentioned in the op. So he hasn't uploaded the kernel source.
Sent from my GT-I9082 using Tapatalk

[ROM][GT-P52XX][UNOFFICIAL][6.0.1] CyanogenMod 13.0

Unofficial CyanogenMod 13.0 for Samsung Galaxy Tab 3 10.1​
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.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, ...
* You flash this at your own risks
*/
About CM
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. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Important information
You need a recent TWRP version to flash this ROM.
Installation
First time installing, coming from another ROM or upgrading from alpha < 4
Copy ROM to SDCard
Copy Houdini to SDCard
Copy GApps to SDCard
Boot into recovery
Backup EFS partition
Wipe -> Advanced Wipe -> Dalvik Cache + System + Cache + Data
Install ROM
Install Houdini
Install GApps
Reboot
First start takes a long time
Upgrading from earlier version of CyanogenMod 13.0 (alpha >= 4)
Copy ROM to SDCard
Boot into recovery
Install ROM
Reboot
[OPTIONAL] Converting filesystem to F2FS (thanks @michiil)
The ROM has F2FS support. You may want to use it instead of the default (EXT4).
This will delete ALL files/data from your tab.
What you will need: A working PC and a working USB cable.
Install the most recent Recovery
Download the most recent Recovery from the second post. Flash the zip file in recovery. Back in the main menu press Reboot > Recovery
Format Data and Cache to F2FS
Wipe > choose Cache > repair or change file system > change file system > F2FS > Swipe to Confirm
Go back and repeat the same steps with Data. I got some error messages when formatting Data but they don't seem to be a problem.
Back in the main menu press Reboot > Recovery
Install Rom + Houdini + Gapps
Connect your tab to your PC and copy the zip files on the tab.
Flash the files, reboot and enjoy :good:
How to get back to EXT4
You will again loose all files/data on the tab.
Just repeat Step 2 but use EXT4 instead of F2FS.
What's working
RIL (audio calls, data, sms, mms)
2D/3D acceleration
HW video encoding/decoding
Screen cast (Miracast/Wifi Display)
MHL/HDMI
Sound
InfraRed
Camera
Wifi
Bluetooth
GPS
Sensors
SDCard, USB OTG
Tethering (USB, Bluetooth, Wifi)
Software DRM (Level 3, see below)
Known to be working
Google Movies
Amazon Prime Video
Molotov TV
myCANAL
Canalplay Kids
Known *not* to be working
6play
Features
Automatic brightness
Change Color profile
Change mDNIe scenario
Enable/disable mDNIe negative mode
Multiuser
Enable/disable capacitive keys
Change capacitive keys width
Buttons backlight on screen touch or key touch only
Smart cover lock/unlock
F2FS and exFAT support
Houdini (allows to install arm only apps on this x86 device)
Updated ZRAM support with LZ4 compression for maximum memory and speed
Updated Xbox Controller driver
Updated interactive CPU governor
Available CPU governors: powersave, interactive, performance, ondemand
Available I/O schedulers: noop, deadline, cfq, bfq (v7r8), fiops
Available battery modes (CM power profiles): power save, balanced, performance
What's not working
Chromecast screencasting (other functions work)
Hardware DRM (Level 1)
SELinux (permissive)
You tell me
How to root
Go to 'Settings/About tablet'
Tap 7 times on 'Build number'
Go back
Go to 'Developer options'
Tap on 'Root access'
Select 'Apps only' ('Apps and ADB' if you plan to use it in adb shell)
How to help
When something is not working correctly, in addition to common informations, I may ask you to provide logs. There are different kind of logs and it's not always easy to get all of them. For this, you can use SysLog (available on F-Droid or Google Play).
Fixed in version 2.1.0 There is currently a bug in the app. Download it from AndroidFileHost. Use this patch if you want to compile it yourself:
Make sure to root device before using this app.
To get the logs:
Start SysLog
Click on 'TAKE LOG'
Once log is taken, SysLog will try to share the resulting file, just cancel
Send me the file /sdcard/SysLog/[YYYY-MM-DD_HH.mm]/[YYYY-MM-DD_HH.mm].zip
If you left 'Scrub potentially personal information from the logs' checked, you should be safe.
Sources
Kernel
Common: https://github.com/santos10-dev/android_kernel_samsung_santos10/tree/cm-13.0
Device trees
Common: https://github.com/santos10-dev/android_device_samsung_santos10-common/tree/cm-13.0
Galaxy Tab 3 10.1 3G: https://github.com/santos10-dev/android_device_samsung_santos103g/tree/cm-13.0
Galaxy Tab 3 10.1 Wifi: https://github.com/santos10-dev/android_device_samsung_santos10wifi/tree/cm-13.0
Galaxy Tab 3 10.1 LTE: https://github.com/santos10-dev/android_device_samsung_santos10lte/tree/cm-13.0
Local manifest
https://github.com/santos10-dev/android_device_samsung_santos10-common/wiki/Local-manifest-CM-13.0
Credits
Angel_666 , moonbutt74 and Restl3ss for starting the work on this device
Android-Andi for his device tree
crpalmer for his work on Intel support
Deltadroid for his GApps package
All testers of the "signup" thread
CyanogenMod and Google for Android
XDA
AndroidFileHost
XDA:DevDB Information
CyanogenMod 13.0 for GT-P52XX, ROM for the Samsung Galaxy Tab 3 10.1
Contributors
nels83
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2016-03-21
Last Updated 2017-04-11
Downloads
ROM
ROM - Beta 2 (20161210)
Galaxy Tab 3 10.1 3G : santos103g (MD5)
Galaxy Tab 3 10.1 Wifi : santos10wifi (MD5)
Galaxy Tab 3 10.1 LTE : santos10lte (MD5)
You can find old versions on AndroidFileHost. Version code is in file description.
Houdini 6.0.0_x.47745
Houdini for Android 6.0
GApps
See Open Gapps, select Platform x86 and Android 6.0.
Other
Flash player (11.1.112.60)
Flash player for x86
Note: not much used nowadays but useful if you want to play flash games.
Changes
Changelog
Beta 2 (20161210)
- Fixed audio calls
- Switched to dlmalloc
Old changes
Beta 1 (20161204)
- Fixed freezes
- Fixed AGPS
- Cleaned up sensors hal
- Use opensource audio hal
- Added FIOPS io scheduler
Alpha 7 (20161121)
- CM update (android 6.0.1_r74)
- Added software DRM support (Level 3)
- Fixed touchscreen lags (maybe not all lags, thanks to @Alphita and @KNGPN Q w Q)
- Fixed lock screen rotation (thanks to @tinko975)
- Fixed Google SetupWizard loop when no network is available (CM)
Alpha 6 (20161018)
- CM update
- Updated kernel memory management (and removed samsung specific code)
- Updated kernel android drivers
- Fixed button lights always on when disabled
- Fixed rotation (small) bug
- Fixed deep sleep issues
- Fixed many reboot issues
- Enabled CABC
Alpha 5 (20160822)
- Updated to stable/cm-13.0-ZNH5Y branch
- Enabled Doze mode (thanks to @vin_)
- Enabled 180deg rotation by default
- Enabled swap volume keys on rotation by default
- Added MHL/HDMI support
- Added houdini Intel patches for better compatibility
- Added USB charger port support
- Fixed fast/slow charging reports
- Fixed buttons backlight on key touch only
- All kernel modules are now builtin
- Various tweaks
Alpha 4 (20160731)
- Switched back to stable/cm-13.0-ZNH0E branch
Alpha 3 (20160727)
- CM update
- Fixed Flash Player
- Fixed /dev/last_kmsg
- Fixed cpuset
- Tweaked power management
- Implemented CM power profiles (battery modes)
- Added color profile setting (in LiveDisplay)
- Added Advanced Settings (mDNIe scenario, large/small capacitive keys, buttons light on screen/button touch)
- Added stock charger images
Alpha 2 (20160430)
- Based on stable/cm-13.0-ZNH2K branch
- First try at RIL (3G and LTE)
- Fixed Wifi tethering (thanks @deadfun)
- Enabled and tweaked cpusets (fixes SMP "bug")
- Updated and tweaked cpufreq interactive
- Updated xpad driver (thanks @X-Coder)
- Updated kernel config (merged android recommended settings)
- Added bfq io scheduler
- Enabled deadline scheduler
- Enabled powersave cpufreq scaling governor
Alpha 1 (20160321)
- First release
- Based on stable/cm-13.0-ZNH0E branch
Thanka @nels83 i was waiting for this since morning ?
why does RIL not working? its the most important thing for me
Awesome it works
How to Upgrade from CM12?
Spegeli said:
How to Upgrade from CM12?
Click to expand...
Click to collapse
Download TWRP, opengapps, houdini and the rom (corresponding to your device)
Backup all your data (pictures, music etc.) and apps (preferably with apps like titanium backup) to your PC
put the zips from above onto your sd card (if you don't have one, use the internal storage)
boot into recovery of your tab
wipe /system, /cache, /data, dalvik cache and (if you don't have important data like the zips on there) the internal storage
flash the files in the following order:
TWRP (then restart your device into recovery)
ROM
Houdini
Gapps
if you want to do it: reformat /cache and /data now with f2fs
reboot into system
connect your device to the pc again and get your backed up files and apps
reinstall apps through the play store and if you want to: get their data back with Titanium Backup
Done.
EDIT:
it's nice that CM13 is out and that Houdini is working
though I'm going to wait for RIL support before I update
How complicated is it to fix/How long will it take (min)? (if you can say that)
Dj_Fex said:
Download TWRP, opengapps, houdini and the rom (corresponding to your device)
Backup all your data (pictures, music etc.) and apps (preferably with apps like titanium backup) to your PC
put the zips from above onto your sd card (if you don't have one, use the internal storage)
boot into recovery of your tab
wipe /system, /cache, /data, dalvik cache and (if you don't have important data like the zips on there) the internal storage
flash the files in the following order:
TWRP (then restart your device into recovery)
ROM
Houdini
Gapps
if you want to do it: reformat /cache and /data now with f2fs
reboot into system
connect your device to the pc again and get your backed up files and apps
reinstall apps through the play store and if you want to: get their data back with Titanium Backup
Done.
EDIT:
it's nice that CM13 is out and that Houdini is working
though I'm going to wait for RIL support before I update
How complicated is it to fix/How long will it take (min)? (if you can say that)
Click to expand...
Click to collapse
Not possible to Upgrade without loosing all Apps (and there Settings)?
sorry, I won't guarantuee you that anything is working if you leave the data partition and don't format it
even though it might be nice to keep the data
it's safer to backup your the data and apps that you need and then start fresh
and usually it's not even that much of a hassle (you just need to get used to it)
Nels says at the top:
if you come from an earlier version of cm13 then it's possible
but if you come from another rom (cm12) you need to wipe data
@nels83 I just noticed, your changelog link still points to the cm 12 branch (only a copy&paste issue of course so no big deal)
@nels83 Just upgraded from cm12,1 beta 2. This ROM works fine. Thanks
pvt-koffiejunk said:
@nels83 Just upgraded from cm12,1 beta 2. This ROM works fine. Thanks
Click to expand...
Click to collapse
do you fresh install the rom?or just dirty flash it and its work fine?
Anyone know how to make this rom black ?
Rom is buttery smooth, I am having issues with chrome being slow but that also happened on cm 12.1
Lionerx said:
do you fresh install the rom?or just dirty flash it and its work fine?
Click to expand...
Click to collapse
Just dirty. Figured I could always flash again and do the right way.
Strange I don't see option for downloading of GApps 6 86x at open GApps
Mrkijo said:
Strange I don't see option for downloading of GApps 6 86x at open GApps
Click to expand...
Click to collapse
maybe is temporarly down.. it worked for months.. with aosp rom too..
i download it yesterday.
edit:
here are links from few days before..
https://github.com/opengapps/x86/releases/tag/20160320
..
@nels83 just a quick info: if I use your P5210 device tree in my CM 13.0 source, can I build it from scratch? I'd like to experiment with that.
tinko975 said:
maybe is temporarly down.. it worked for months.. with aosp rom too..
i download it yesterday.
edit:
here are links from few days before..
https://github.com/opengapps/x86/releases/tag/20160320
..
Click to expand...
Click to collapse
Thanks, you were right, it was temporary and now it is on again ?
After 20 Hours of Testing, the Rom works good except:
- Kaspersky Internet Security crashed when starting a analysis
- Camera crashed when switching to Focus Effects or Video
The rest seems working fine so far.

[KERNEL] [ROOT] [SM-N920*] Exynos 7420 | SkyHigh Kernel

[KERNEL] [ROOT] [SM-N920*] Exynos 7420 | SkyHigh Kernel [ v6.8.0-EOL ] | Synapse | Aroma | F2FS | UBERTC 6.2.1 20161012
The BEST & FULLY FEATURED EXYNOS 7420 KERNEL IS REBORN . . . . .
** I will NEVER support KOREAN (S/K/L) variant. Get over it and flash ARTER kernel instead !! **
Many select patches for better security, performance and efficiency (not all listed). THERE IS "NO NEED" to tweak anything -- Just FLASH it !! But, if you desire, can further tweak many settings and available features with Synapse to suit your own habits and device capability. That is for you to find out
SUPPORTED DEVICES:
SM-N920C
SM-N920CD
SM-N920G
SM-N920I
SM-N9200_HK
SM-N9208_SEA​
RAMDISK BASE:
N920C : N920CXXU3BPJ7
N9200_HK : N9200ZHS3BPI3
N9208_SEA : N9208XXU3BPJ4​
FEATURES:
Modified from the LATEST device specific official Samsung source(s): Samsung OSRC
AUTO-ROOT SYSTEM-LESS SR3-SuperSU-v2.78 (on flash)
KNOX WARRANTY VOID: 1
SELinux PERMISSIVE (default) or ENFORCING
DEEP SLEEP FIX
UX ROM (BOOT support only)
AROMA Installer (set your own defaults)
Auto-Install busybox v1.24.1-Dorimanx & Sqlite3 to /system/xbin (on flash)
Compiled with UBERTC 6.2.1 20161012 + Graphite optimizations
Linux 3.10.104
init.d script support (drop in script & set permissions to 755 or 777 and reboot)
adb insecure
stock dt.img
Secure storage = false (should prevent WIFI settings & passwords wiping on reboots)
Reduced logging
F2FS experimental support (Much faster I/O - write speeds).
exFAT FS support
NTFS R/W support with app
CIFS support (not tested)
ISO 9660 CDROM & UDF FS support
Frandom
mount all partitions NOATIME (better performance & efficiency)
mount EXT4 /data & /cache partitions LAZYTIME (better performance & efficiency)
A53 LITTLE cores increased boot frequency (faster boot)
LZO ramdisk de/compression algorithm (faster boot)
CLEANCACHE & ZCACHE
Microsoft X-BOX gamepad controller module (updated)
Slub tweaked
Invisible CPUSETs (better efficiency)
A tonne of select patches for features, better performance & efficiency
Synapse app support for many kernel configurations + much much more !!
SYNAPSE FEATURES:
Too many too list . . . Have a look through Synapse yourself. If you don't know, then read and research or leave it DEFAULT !!
About
A57 CPU frequency scaling
A57 voltage control
A53 CPU frequency scaling
A53 voltage control
CPU governor
A57 governor tunables
A53 governor tunables
Multicore
CPU stats
Boost
GPU frequency scaling
GPU voltage control
Thermal
BUS
IO
Memory
Advanced
Power Suspend
Doze
Wakelocks
Audio
Battery
LED
Screen
Network
Security
FS (file system)
CortexBrain
Crontab
USB mode
Modules
Backup & Restore profiles + EFS (auto on boot to /sdcard/SkyHigh/EFS)
Logs
Reboot
Info
CREDITS:
My family !!
Chainfire - root & SuperSU app
AndreiLux - years of support for Exynos development and his various kernel features + Synapse app and UCI code
halaszk88 - patches and some Synapse code I adapted to many of my kernels
dorimanx - BusyBox and various ramdisk tweaks/ideas
apb_axel - I adapted and used many of the Synapse controls to suit my kernels
arter97 - various source fixes/patches
ktoonsez - ktoonservative hotplug governor
YashdSaraf - BusyBox-Cleaner script
Android File Host
Linus Torvalds & Linux Foundation
Google & Samsung OSRC
and many others!
All those in my select private group that have provided constructive feedback, help, and support.
IF I'VE FORGOTTEN ANYONE, PLEASE DON'T BE SHY AND SPEAK UP, THANKS
XDA:DevDB Information
SkyHigh Kernel for N920* devices, Kernel for the Samsung Galaxy Note 5
Contributors
UpInTheAir
Source Code: https://www.androidfilehost.com/?w=files&flid=88214
Kernel Special Features: Aroma - Synapse ++ almost everything !!
Version Information
Status: Stable
Current Stable Version: 6.8.0-EOL
Stable Release Date: 2016-11-19
Created 2016-07-30
Last Updated 2016-11-19
License - requirements - installation - download - source
DON'T POST LAME QUESTIONS THAT YOU CAN FIND THE ANSWER TO BY A LITTLE SEARCHING.
I AM NOT GOOGLE & NEVER PRETEND TO KNOW EVERYTHING, SO A LITTLE HELP FROM YOURSELF WILL GO A LONG WAY. . .
THANKS & ENJOY !!
** LICENSE & DISCLAIMER **
/*
© Copyright (c) 2015-2016 UpInTheAir <[email protected]>
All rights reserved. The alterations from OEM, associated script files and coding packed within this ramdisk & installation package (the "Software"), may not be reproduced, displayed, modified or distributed without the express prior written permission of the copyright holder. For permission, contact [email protected].
The above copyright notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF , FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
*/
In plain language
DO NOT STEAL MY SH*T !!
UpInTheAir is NOT responsible, the person you see in the mirror is !!
REQUIREMENTS:
Supported variant only !!
​** I will NEVER support KOREAN (S/K/L) variant. Get over it and flash ARTER kernel instead !! **
Touch Wiz Android M 6.0.1 ROM or UX leaked firmware (boot support only)
Appropriate custom recovery (i.e..TWRP for your variant)
INSTALLATION & UPDATE:
If you have Synapse installed = = you must clear Synapse app data before flash !!
Device Settings: Enable Developer Options > OEM UNLOCK is ENABLED
Boot into custom recovery (volume UP + home + power)
DO NOTHING but flash SkyHigh kernel.zip (ALWAYS flash again AFTER any custom ROM installation, system or data wipe)
After flash == DO NOTHING but REBOOT IMMEDIATELY from TWRP or you will have to re-flash !!
CONVERT EXT4 TO F2FS FS:
If not already, install the latest TWRP for your device variant (ie. 3.0.2-2). This must support F2FS.
Boot into TWRP.
Insert USB-OTG
** ALL DATA WILL BE WIPED FROM INTERNAL STORAGE (restored later)
Backup (copy) all important files (incl. your NANDROID) off device (ie. from internal storage > USB STORAGE). This can take a while. Advanced > File Manager > .....
Home > Backup > Select Storage > USB Storage > OK > "Swipe to Backup" (Only need DATA, but recommend to backup all partitions).
Install > Select Storage > USB Storage > OK.
Select f2fs.zip > "Swipe to confirm flash" (This will WIPE ALL DATA !! & convert DATA & CACHE to F2FS. System is not supported by kernel).
Check the box to remember setting and “Swipe to allow Modifications”.
If you do not have Step #8, then Data was not converted to F2FS.
Mounts > unchecked both Cache & Data. Repeat Step #7 & 8.
Restore > Select Storage > USB Storage > OK > Select TWRP Backup folder > DATA ONLY !! > "Swipe to Restore" (ignore warning about EXT4).
Home > Install > Select Skyhigh_kernel.zip > "Swipe to confirm Flash".
Home > Mount > USB STORAGE > uncheck/unmount (then remove USB-OTG).
Home > Reboot > SYSTEM.
Wait ~2-5 mins for boot.
Once booted, let stabilize for ~5 mins.
You can check Data & Cache F2FS FS status in either /proc/mounts or Synapse app (FS section).
Use a root type explorer (su permission) & navigate to /sdcard, and delete the "0" folder.
Move (copy) your backed up files from Step #4 to internal storage (/sdcard). This can take a while. Maybe one folder at a time is better?
ISSUES ?
If using TWRP MTP mode, deleting some folders/files may crash TWRP and cause corruption. Instead, use a root type file explorer to delete from device.
If you need to wipe data, then use the ext4 or f2fs.zip, otherwise this is not possible with this TWRP !!
Not tested any method with customized ROMs. The ROM installer script may re-format partitions back to EXT4 or not mount correctly causing TWRP crash or corruption. I can only suggest to Flash ROM with EXT4 FS > make a NANDROID on USB-OTG and then follow the F2FS steps above.
CONVERT F2FS TO EXT4 FS:
The Same steps as above, but use the ext4.zip !!
OPTIONAL SYNAPSE INSTALLATION:
After boot:
Wait at least 120 secs to stabilize
Install Synapse app from Google Play and rate it ☆☆☆☆☆ !!
Open Synapse
Tap "Understood"
So changes stick every time you start Synapse == Make any change & 'apply'.
Recommend: Disable KNOX with Synapse
DOWNLOADS:
** I will NEVER support KOREAN (S/K/L) variant. Get over it and flash ARTER kernel instead !! **
Mod Edit: Link removed.
BUGS:
Aroma Installer: 10% of installation will encounter Aroma installer "freeze". It's only the display that freeze, the script still execute in the background. Just wait a minute, then press slightly to the top right 'home' key / top left of the 'back' key . . .
UX BETA firmware - blue light filter
UX BETA firmware - torch light (some ROMs)
HD voice ? - Speakerphone: other party cannot hear voice
SOURCE - ALL SkyHigh VARIANT:
Available upon request.
v6.6.1 AFH
v6.8.0 uploaded soon. . . . .
.
FAQ & HELP
TROUBLESHOOTING GUIDE:
I might not have your device variant and or able to reproduce your "issue".
Please provide as much information as possible.
Without resetting your device to a stable unmodified baseline, any potential troubleshooting or logs could be meaningless.
So please follow the guidelines set out below. Users can't "read minds".
Without providing important information, we are unable to help YOU.
Search thread, XDA and Google before posting
Provide as much information as possible.
- Device model
- Firmware version
- ROM name / version
- Kernel version
- Modem version
- Bootloader version
- Synapse settings (try default)
- Installed tweaks and apps etc (Xposed ?)
- The exact steps you've taken to try resolve the issue yourself.​
Exact steps to reproduce the issue. Provide screenshots if able.
Does it work with older / other versions etc
Reset your device to a stable baseline (ie. stock) with only custom TWRP recovery and kernel (FULL WIPE: system, cache, dalvik-ART)
Possible logs
FAQ & HELP:
CAN I BUILD A KERNEL FOR YOUR __XX DEVICE ?
Sorry. I don't have the spare time for any more variant support.
Additionally, I do not build for any device that I can not compile using SAME source, personally test method or debug. Some device variants can compile with same source.
** I will NEVER support KOREAN (S/K/L) variant. Get over it and flash ARTER kernel instead !! **
CAN I INCLUDE SkyHigh KERNEL IN MY ROM
NO == My ramdisk modifications are COPYRIGHT (refer LICENSE in Post #2), and distribution without MY (UpInTheAir) prior written consent is not only in a breach of that license, but also XDA Rule #12)
Although I do appreciate your contribution, if you could please do not include my kernel in any ROM package etc. This policy goes for anyone.
Having my kernel distributed outside my development thread just removes a lot of credit and more importantly, constructive user feedback that could be helpful to my development or user issue.
ALWAYS on DISPLAY (AoD)
I have spent some time to attempt port S7 display drivers to our kernel, but haven't had success as yet with too many errors.
TBH, it's a lot of work for something I'm not really interested in or would use. . . so I don't wish to spend any more of my own time on it, sorry. If someone else does it, GREAT
DO I "NEED" SYNAPSE
THERE IS NO "NEED" !!
It is "recommended", which is OPTIONAL, and not "needed".
It is for ADVANCED or adventurous users who wish more control of their device or use various features I've added.
Using any other optional tweaking or control app may conflict & many features and options won't be available.
WHY WAIT 120 SECS
The kernel and Synapse scripts need time to boot up properly and allow SU permission.
There are scripts / code that have a deliberate delay and must run after Synapse. These are not user optional.
Synapse has a stability check on boot. You may get "synapse boot cancelled".
Thermal throttling will be trying to limit many things, let the device settle
OTHER PARTY CAN NOT HEAR VOICE ON SPEAKER PHONE
It could be a conflict in the system/etc/mixer_*.xml. I don't know for sure, but if I exclude the sound mod, then this "fixes" the problem.
As I cannot reproduce the issue (and the majority), then the audio mod stays.
Unfortunately, making it optional would require to build kernels without and create much more work for many device I don't actually use.
Either live with it, or use another kernel. Sorry.
"NO UCI SUPPORT"
It's a ROM busybox compatibility issue !!
Re-flash kernel as per Installation Instructions. (kernel install zip flashes proven busybox binary to /system/xbin)
BACKUP / RESTORE ISSUES
It's a ROM busybox or sqlite3 compatibility issue !!
Re-flash kernel as per Installation Instructions. (kernel install zip flashes proven busybox binary to /system/xbin)
BACKUP & RESTORE
DO NOT restore profiles from different kernel version
Refer to THIS post for "how-to" screen-shots
Refer to THIS post for a "how-to" video
LOADABLE MODULES AREN'T WORKING
Check your /system/lib/modules directory. Are any ____.ko present?
Did you flash a ROM or wipe the system partition at any point? Doing this will remove them !
Re-flash the kernel will install the modules.
If modules aren't installed after flash, then re-flash and manually mount system in recovery first.
You can check running modules in terminal with:
​lsmod
KTOONSERVATIVE GOVERNOR
Some info from the author HERE
DT2W & COLOUR CONTROL
No, I cannot make it work properly with single source for all supported variants
CPU POWER CONSUMPTION
The Samsung Exynos 7420 Deep Dive - Inside A Modern 14nm SoC (by ANANDTECH - Andrei)
F2FS SUPPORT
It's not needed. You wouldn't see any difference or measure much, if anything. Not worth the potential trade-off. This is not eMMC anymore
Storage Benchmarks
STUCK ON SAMSUNG BOOT LOGO AFTER FLASH
Ensure you flashed the correct kernel for your device model
Ensure your download is not corrupted. Check MD5 hash or re-download
Your current base firmware (ROM, boot-loader version etc.) may be incompatible - UPDATE to latest with Odin and try again.
CM SUPPORT
Read THIS
BATTERY TIPS (require updating !! )
Try some (or combination) of the CPU MULTICORE features in Synapse:
HMP profile = Default (values are battery orientated)
Power Aware Scheduling (slight performance cost) = Enabled
HMP LITTLE Packing (slight performance cost) = Enabled
PEWQ (power-efficient workqueue) (slight performance cost) = Enabled
Set A57 & A53 Interactive governor profile = Battery
Set Input-Booster for key/touchkey profile = Battery
Multi-tasking: enable UKSM & "low" or "quiet" profile (slight performance/battery cost)
PERFORMANCE TIPS (requires updating !! )
Set A57 & A53 Interactive governor profile = Performance
Set A57 & A53 Interactive governor = Turbo Mode (battery cost)
Set HMP threshold profiles = Stock or Performance
Once in a while:
Optimize Databases
FSTrim​
RANDOM REBOOT
Don't UV or UC CPU or GPU
Use SkyHigh defaults
Use a stock UNMODIFIED ROM for your device variant
No tweaks, Xposed or other CPU control apps installed
Follow the TROUBLESHOOTING GUIDE
ASV_GROUP (ALL DEVICES ARE NOT CREATED EQUAL)
THIS is an example from my Exynos5420 source. Similar idea for Exynos4
DOWNLOAD LINK NOT WORKING
I want to keep this project all in one place - ☆☆ NO MIRRORS ☆☆
Please try again in a few minutes
POOR CPU/GPU BENCHMARK or GRAPHICS PERFORMANCE
Disable any CPU MULTICORE options in Synapse
Disable any Battery profiles in Synapse. Set to default or Performance.
Allow the device to cool. Repetitive testing will heat the device hardware and invoke thermal throttling and lead to decreased benchmark.
HIGH CPU/GPU OC == excessive heat == thermal throttling == reduced clock frequency == DECREASE PERFORMANCE
DYNAMIC MANAGEMENT OF DIRTY PAGE WRITEBACKS
by Christopher83
This feature allows to have two different intervals for dirty page writebacks and to dynamically manage them when the system has been resumed (it's active) or when has been suspended.
Three new procfs parameters are exposed inside /proc/sys/vm path:
dynamic_dirty_writeback is the activation status of this feature, set 1 to enable it, set 0 to disable it and use the standard behaviour
dirty_writeback_active_centisecs is the interval for the dirty page writebacks when the system is active (screen on)
dirty_writeback_suspend_centisecs is the interval for the dirty page writebacks when the system is suspended (screen off)
This feature is in part inspired on Francisco Franco's PATCH
TCP/IP NETWORK SECURITY
Thanks to zeppelinrox & V6SuperCharger
Hardening the TCP/IP stack to SYN attack
Bump up tw_buckets in case we get DoS'd
Ignore pings
Don't cache connection metrics from previous connection
Don't pass traffic between networks or act as a router
Enable spoofing protection (turn on reverse packet filtering)
Don't accept source routing
Don't accept redirects
Further reading:
http://www.cyberciti.biz/faq/linux-kernel-etcsysctl-conf-security-hardening
http://www.symantec.com/connect/articles/hardening-tcpip-stack-syn-attacks
CHROMECAST - STREAMING PROBLEMS
Lock screen MUST be enabled (simple screen lock swipe) I don't know why but it breaks the chromecast app's ability to resume smoothly if switched off
Synapse > Network > DTIM (both screen ON & OFF) = 1
Synapse > Network > WIFI Power Mode (screen OFF) = FAST
@UpInTheAir needed to create these threads to compile them for Synapse. He contacted me to close these as soon as he made them until he is ready with the finished product. Have patience.
Also I would like to apologize to UITA as the last ban may have been due to a system glitch where the signature was restored upon return, so was unjust. I have seen these glitches before and better communication might have prevented the error. We will do better going forward!
Edit: Opened
Reserved
Nice to see you back UITA.
Welcome back UITA ?
SM-N930F cihazımdan gönderildi
Welcome officially back
SkyHigh KERNEL REBORN - v5.6 released !!
SkyHigh KERNEL REBORN - v5.6 released !!
Hi fellow members.
Please find my latest release for SkyHigh kernel. There are many many changes, both visually (more / improved features) and a upgraded engine (better performance & efficiency) since I last publicly released. Far too many to talk about. . . .
Please note that although I have taken as much care in building and testing by my friends and I, the kernel may still not perform as hoped for you. Could be due to various factors including (but limited to):
hardware quality
firmware installed (incompatibility)
user habit (how you use the device)
apps & mods installed, customization's (conflicts)
user kernel settings (read them carefully - if in doubt == defaults)
As noted in Post #3, I may not have your device variant and not be always able to help either. In the end, sometimes SkyHigh is just not meant for you . . . .
If you have issues = = READ & FOLLOW ALL Posts #1-3
READ & FOLLOW THE INSTALLATION INSTALLATIONS EXACTLY (or else device will not boot)
Also please note (as per OP) the support for UX based ROMS is still in beta. I have personally tested very briefly, and also some of my friends (not all variant)
Enjoy
UITA
.
Proud to be one of the first ten guys downloading your kernel. Hahaha
*reborn kernel
Woo Hoo!
N920C variant doesn't have .zip file extension at the end of the file. FYI, thanks.
Edit: Didn't boot on N7 Port.
iko11 said:
N920C variant doesn't have .zip file extension at the end of the file. FYI, thanks.
Edit: Didn't boot on N7 Port.
Click to expand...
Click to collapse
Don't know why AFH is truncating the .zip extension . . . never used to. I'll see what's up, trying to get this source uploaded
EDIT: re-uploading all three kernels. zip extension sorted
iko11 said:
N920C variant doesn't have .zip file extension at the end of the file. FYI, thanks.
Edit: Didn't boot on N7 Port.
Click to expand...
Click to collapse
+1 cant flash even if i zip the file...sorry
N920c/64g/infinity Ux beta a2 / arise sound +doubly/xposed greenify+amplify+powernap
www.ndroid.io
---------- Post added at 01:07 PM ---------- Previous post was at 12:42 PM ----------
ziped work great...flashed succes....on ux beta a2 infinity rom...will test now
N920c/64g/infinity Ux beta a2 / arise sound +doubly/xposed greenify+amplify+powernap
www.ndroid.io
Welcome back, UITA.
Thanks for the update, finished downloading and will give it a try.
Sent from my SM-N930F using Tapatalk
carlitobahsoun said:
+1 cant flash even if i zip the file...sorry
N920c/64g/infinity Ux beta a2 / arise sound +doubly/xposed greenify+amplify+powernap
www.ndroid.io
---------- Post added at 01:07 PM ---------- Previous post was at 12:42 PM ----------
ziped work great...flashed succes....on ux beta a2 infinity rom...will test now
N920c/64g/infinity Ux beta a2 / arise sound +doubly/xposed greenify+amplify+powernap
www.ndroid.io
Click to expand...
Click to collapse
Tested RR4 UX
I've re-uploaded with zip extension
hi
my device n920cd
my rom CRISSCROSS v-2.3
The kernel's all good
Thank you very much
UpInTheAir said:
Don't know why AFH is truncating the .zip extension . . . never used to. I'll see what's up, trying to get this source uploaded
EDIT: re-uploading all three kernels. zip extension sorted
Click to expand...
Click to collapse
I don't know if it's a bug, On the first attempt I tried to boot on Enforcing but didn't boot, at the Samsung logo it vibrated consequtively, bzz, bzz .... bzz, bzz like. But Permissive works fine. I am fully operational besides Blue Filter not working.
iko11 said:
I don't know if it's a bug, On the first attempt I tried to boot on Enforcing but didn't boot, at the Samsung logo it vibrated consequtively, bzz, bzz .... bzz, bzz like. But Permissive works fine. I am fully operational besides Blue Filter not working.
Click to expand...
Click to collapse
Might be to do with UX or your ROM. I only test that on 100% stock ROM and worked fine at the time.
The blue light filter bug for UX is known and has already been reported / added to the "BUG REPORT" tab. (View in website mode on PC).
Please be aware that I extensively test only on stable stock firmware. Not beta leaks etc. So some UX bugs may or may not get fixed. I personally use stock.
{
"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"
}
NTFS
Hi UITA, thanks for coming back. Could you please tell me which apps need to be used in order to use NTFS formatted external hard drives.
Thank you.

Categories

Resources