Related
G3MOD TEAM
Founder
dharamg3
Kernel Developers
hillbeast , moikop , cool.darshak
Application Developers
dympy , andreapier
ROM/Theme Developers
Stylooo , RafayelG , aarrun
Kernel Features:
Non-OC Version: 83MHz - 667MHz
OC Version: 83MHz - 1200MHz
RootADB
Busybox 1.19
File System Support: rfs/ext2/ext3/ext4
Init.d Scripts
1% Battery Mod
OverClocking
UnderVolt
data2sd
BFQ I/O Scheduler
Voodoo v10
CWM Touch Recovery
Configurable CompCache
BootLogo
TinyRCU
MultiBoot
Kernel Hz: (Non-OC: 250, OC: 500)
tun.ko
100MHz CPU clock stepping
DMA Enabled in G3D
Dynamic OC
Hybrid kernel (supports every firmware for Galaxy 3)
Hybrid Data2SD
Multi Data
NTFS read-only support (but no auto mounting SD card yet)
BLN Support. (Thanks to marcellusbe)
JFS and HFS+ support
CWM Features:
1) Reboot
2) Extended Power Menu
1.1) Power Off
1.2) Reboot
1.3) Reboot Recovery
1.4) Download
3) Update.zip's
3.1) Update.zip from sdcard Root
3.2) Select .zip from sdcard
3.3) Toggle Signature Verification
3.4) Toggle Script Asserts
4) Multiboot
4.1) Switch ROM's
4.2) Backup ROM
4.3) Switch Kernel's
5) Data / Factory Reset
6) Wipe
6.1) Data / Factory Reset
6.2) Cache
6.3) Wipe dalvik cache
6.4) Wipe Battery Stats
7) Backup and Restore
7.1) Backup
7.2) Restore
7.3) Advanced Backup 7.3.1) Boot 7.3.2) System 7.3.3) Data 7.3.4) Cache 7.3.5) sd-ext
7.4) Advanced Restore 7.4.1) Boot 7.4.2) System 7.4.3) Data 7.4.4) Cache 7.4.5) sd-ext
8) Mounts And Storage
9) Advanced
Kernel Downloads:
http://code.google.com/p/g3modteam/downloads/list
Kernel Changelog:
v2.5 (15/05/2012
Supports CM7a8.1
Supports ICS (if colours are screwy, update OpenFIMG)
CWM5 with touch
General source code fixes
v2.4.1 (23/02/2012)]
CM7 A7 support!
Fixed filesystem covertion system.
Lagfree governor properly implemented.
Added BLN support.
Fixed wifi for CM7 (Thanks to Arakmar).
v2.3 (15/12/2011)
Hybrid initramfs: Added support for ICS-based roms.
Multiboot: Fixed dalvik-cache restoring.
Multiboot: Added support for backing up android_secure.
AOSP Proximity sensor support added.
Initramfs: Optimized init.rc files and added usb.rc file.
MAX8998 Driver: Removed led blinking support since it isn't being used anymore.
v2.2.2 (21/11/2011)
Went back to old BLN system, this seems to work fine.
New NON-OC Kernel Hz: 250.
Should have a better battery backup
v2.2.1 (16/11/2011)
JFS Utilities permission fixed.
BLN System fixed.
v2.2 (15/11/2011)
Support for new BLN system.
Optimized SIO Scheduler for flash devices.
Added JFS Utilities (forgotten in the previous release).
Dropped OC+ version support.
v2.1 (09/11/2011)
Lagfree Governor.
83Mhz steps for Non-OC and OC+ version
Lowmemorykiller.c tweak.
Reverted ondemand performance tweak.
Updated BFQ I/O Scheduler to v2.1r1.
Data2SD tweak: Improved IO Performance for non-Data2SD users and fixed *incompatibility* with Kyrillos's App2SD script.
Added Hybrid Data2SD internal System cache.
Compcache is now configurable.
Fixed battery drain problem.
BLN Support. (Thanks to marcellusbe)
Removed InteractiveX governor due to problems.
JFS and HFS+ support.
v2.0 (02/10/2011)
Hybrid kernel (supports every firmware for Galaxy 3 (except Eclair))
CM6.2 and CM7 Support (obviously but it must be said twice)
Adjusted battery driver (more accurate)
83MHz minimum on OC kernel
Hybrid Data2SD
Multi Data
Compcache toggleable
InteractiveX CPU frequency mode
SIO scheduler
MD5 hash disabled on nandroid
More stable at idle
Reduced power drain at idle
jhash3 removed as it increased power drain.
v1.9 (09/09/2011)
tun.ko included and enabled
100MHz CPU clock steppings: you can now set your speed to anything between 100 and 1400MHz in 100MHz step (100, 200, 300...)
CPU minimum frequency now 100MHz on Performance, Ultimate and Extreme
jhash3 for improved HSDPA/3G/EDGE speeds.
Multiboot improved for data backup and recovery
Added Reboot and Wipe Data/Dalvik Cache to main menu of CWM.
DMA enabled in G3D - Thanks marcellusbe
Added InDroid and CM7 to Multiboot
v1.8 [30/08/2011]
Reworked Battery Driver
Reworked CWM Recovery
Now 11 ROM's support in Multiboot
v1.7 [15/08/2011]
Multi Boot
Power off Option in CWM
Dynamic OC (ability to change the maximum freq)
Modify the max_blk_count value to prevent overflow.(sdcard related)
mmc: core: Fix dereferencing after NULL check (sdcard related)
Lower vfs_cache_pressure 100->25.
ARM: fix some sparse errors in generic ARM code
lib: Improve the performance of memcpy and memmove of the general version
lib: Introduce some memory copy macros and functions
ashmem: fix deadlock when system is low on memory
v1.6 [11/08/2011]
Batter Driver Back to Original - Only Change is added Compensation for Data On
Stable OC
UV Works for All Frequencies - Can be checked via dmesg
Removed SavagedZen and SmartAss for now.Giving Problems. Will come back in future versions.
SDCard Partitioning Problem Solved - Ext3 partitioning for mmcblk0p2 - Can be converted to Ext4 Using g3mod app.
Kernel Flashing via CWM Recovery Working
Kernel Hz: Lite:256 Performance:300 Ultimate:500 Extreme: 1000
Noop I/O Scheduler by default
Fixed Typo in Bootlogo
v1.5 [05/08/2011]
CompCache
BootLogo
TinyRCU
Battery Driver Reworked - Please test and give feedback
v1.4 - 31/7/2011
CWM Recovery In Kernel
Fixed CPU Freq Driver. SetCPU now shows properly.
UV working properly now.Can Be Checked in dmesg.
A 1300MHz freq Step in Extreme Version for those who want 1300MHz overclocking.
Changed Kernel Hz to 300 for Better Battery Backup.
v1.3.4 - 27/7/2011
Overclocking Stable (Less freezes) - To Test
BFQ I/O Scheduler - http://algo.ing.unimo.it/people/paolo/disk_sched/
Extreme Version Screen Off Bug Solved
No OC bus for any versions - (For those who want OC Bus, please use v1.3.0 for the moment. I will try to make OC bus in some better manner)
v1.3.3 - 25/7/2011
5 Touch Mod
Removed RAM Optimization Script
Overclocking Stable (Less freezes) - To Test
Solved Bug which showed wrong freq in SetCPU and PimpMyCPU
Solved Time In State for SetCPU
Extreme Version has OC Bus 200MHz
Frequently Asked Questions
For NOOBS
Q) How to flash the kernel
A) Just apply update.zip from Recovery or flash tar file using ODIN.
Q) Will i lose my data if i flash kernel?
A) No, you wont lose any data nor do you have to wipe data or cache.
Q) Does my battery need to be 100% to flash?
A) Not at all
Q)Flashed CM 6.2 Kernel on Froyo Rom and WIFI doesnt work?
A) There are two versions of Kernel. One is for Froyo Rom and other is for CyanogenMod Rom 6.2 (CM 6.2). if you are on Froyo rom and flash CM 6.2 then your wifi wont work and vice versa.
Q) 1400 Mhz (Extreme version) doesnt work for me
A) Not all Galaxy 3 suppport overclocking as high as 1400 Mhz. If it doesnt work then keep frequency lower or flash Ultimate, Performance or Lite version
Q) What does this data2sd in g3mod do?
A) data2sd is method by which all your /data partition goes to your sdcard thus giving you more space for downloading apps. Its suggested to use data2sd only if your sdcard class is higher than Class 6
Q) Internel Memory shows 0kb
A) Check if you have fs.data2sd at this location /sdcard/Android/data/g3mod/ If yes then delete it or else your sd card doesnt have sd-ext partition
Q) How can i go to recovery mode
A) Press MENU+VOLUME UP+VOLUME DOWN+POWER button and bingo!!!
Q) Should i use multi boot even if i am having 2 gb card class 2 ?
A) Sd card with any class can use multiboot
Q) Data Wipe Necessary When Switching Between CM and Froyo ?
A) Yes data wipe is necessary for switching roms between CM and Froyo. But we have given option to Backup data also in recovery.
Q) My APP is not working after Flashing KERNEL
A) Its not a kernel problem
Q) What is tun.ko?
A) It is basically used to setup Open VPN connections
Q) What is jhash3?
A) jhash3 improves the HSDPA/3G/EDGE speed
For Advanced users
Q1) Battery is draining fast?
A) After flashing the kernel please calibrate your battery or else let 3-4 full battery cycles pass.
Q2) Which profiles should i use?
A) Lets take example that you are using Ultimate kernel. Keep the governor ondemand (Like every good boyfriend fulfills all demands of his girlfriend ondemand governor does the same for your CPU ).
Make profiles:-
1) Time Profile - 12 am to 6.00 am Freq 100 Mhz to 400 Mhz Priority 100
2) Screen Off - Freq 100 Mhz to 600 Mhz Priority 95
Q3) What are advanced settings in the SetCPU mean?
A) Sampling rate is rate at which the frequency of your CPU changes. Up Threshold is limit at which CPU will change freq on load (Scales Up). Down Threshold (conservative only) is limit at which CPU will change freq on load (Scales Down). Powersave bias is used for saving the power of CPU, it will slow down the CPU and affect the performance also 200 in powersave bias mean 20%...250 means 25% and so on.
Q4) I want performance and also good battery what profiles should be i use?
A) Refer to Q2 for Profiles Set up and now go in Advanced tab and Keep Sampling Rate 10000 or 15000. Upper Threshold to 90 and Powersave bias to 200 (20%). Since we are using powersave bias, this will affect the performance as it slows down the CPU so to increase the performance we are lowering the Sampling rate thus we get perfect balance of Performance and good battery backup.
NOTE: ABOVE SETTINGS ARE JUST EXAMPLE..PLEASE PLAY AROUND AND CHOOSE SETTINGS WHICH SUITS YOU THE BEST
WATCH THIS NOOBS
Donations:
If you want to donate to the team as a whole, please divide the amount and donate separately to each member. Sorry for the trouble caused.
Thank You for considering to donate.
dharamg3 -
hillbeast -
moikop -
cool.darshak -
Steps for Multi boot:
1) Flash Kernel v1.7+
2) Go to CWM Recovery -> Multiboot -> Backup ROM.
3) Backup your Current ROM to ROM1 (It will backup the system.img at /sdcard/Android/data/g3mod/roms/romname_ROM )
4) Add the system.img of your 2nd ROM to /sdcard/Android/data/g3mod/roms/romname_ROM and similarly for different ROM's.
5) Use the CWM Recovery -> Multiboot -> Switch ROM option to switch between different ROM's.
6) If switching between Froyo ROM and CM6.2 RoM, you will need to wipe data and also change kernel's via update.zip method.
7) Use the data backup and restore option to prevent loss of data when switching between Froyo and CM6.2 ROM's.
Note: Ask the developer of the ROM's to provide you with the system.img for their ROM
How to use Hybrid Data2SD
1) Connect your phone via ADB
2) Go into adb shell
3) Type 'echo hybrid > /sdcard/Android/data/g3mod/fs.data2sd'
4) Create a text document in Notepad with a list of all the directories you wish to move. Example:
Code:
app
log
dalvik-cache
---LEAVE A BLANK LINE AT THE END---
5) Save the file and call it 'data2sd.dirs'
6) Do 'adb push data2sd.dirs /sdcard/Android/data/g3mod/'
7) Reboot your phone
8) Once your phone has booted, run 'adb shell cat /data2sd.log' to ensure it is running correctly.
How to enable Multi Data
1) Connect your phone via ADB
2) Go into adb shell
3) Type 'echo 0 > /sdcard/Android/data/g3mod/multiosdata'
4) Multi Data will automatically backup your data upon booting into a different OS.
Make sure to not wipe your SD-EXT partition. Doing so will erase the backups from other firmware. Only wipe it if you wish to erase data for everything.
You can also use Multi Data to quickly restore data if your phone has become corrupted. It will restore it back to the last multi-boot switching
1) Connect your phone via ADB
2) Go into adb shell
3) Type 'echo 0 > /sdext/lastos'
4) Reboot the phone
Directories for Multi boot:
//ROM Dir
__system("mkdir /sdcard/Android/data/g3mod/roms/CyanogenMod6_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/CyanogenMod7_ROM"); //Add CM7 Support
__system("mkdir /sdcard/Android/data/g3mod/roms/G3MOD_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/Kyrillos_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/Grigora_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/AOSP_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/DutchMods_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/Kyorarom_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/Indroid_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/rom1_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/rom2_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/rom3_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/rom4_ROM");
//Data + sd-ext Backup Dir
__system("mkdir /sdcard/Android/data/g3mod/data/Froyo_DATA");
__system("mkdir /sdcard/Android/data/g3mod/data/CM6_DATA");
__system("mkdir /sdcard/Android/data/g3mod/data/CM7_DATA");
//Kernel dir
__system("mkdir /sdcard/Android/data/g3mod/kernel/Froyo");
__system("mkdir /sdcard/Android/data/g3mod/kernel/CM6");
__system("mkdir /sdcard/Android/data/g3mod/kernel/CM7");
How to configure compcache:
If you want to use default configuration (as up to now.. 62 MB aprox.), you don't have to do anything different as what you have been doing. But if you want to use a more/less memory, here are the steps:
Inside that /sdcard/Android/data/g3mod/compcache file, write ONLY the number of MegaBytes you want to use for compcache.
Reboot.
If compcache file is empty or contains a "0" inside, it will use default configuration.
How to: BLN
This is only "needed" if you have a i5801 | i5800L or any other Galaxy 3 model with back button lights and want BLN in it.
How to install:
First, download the lights.GT-I5800.so file from google code. Then execute this commands:
adb remount (or if this doesn't work: mount -o remount,rw /dev/stl6 /system)
adb rm /system/lib/hw/lights*
adb push [Location of this file] /system/lib/hw
After that, reboot and now you have BLN working
Steps for Changing the Max Freq(Dynamic OC):
There is an entry in /sys/devices/system/cpu/cpu0/cpufreq/plls_table where you can put your own value for APLL.
Before doing this, set "PERFORMANCE" governor on and min and max frequencies to the maximum.
Code:
// Do this in adb
echo "0 a[SIZE="5"][B][U]258[/U][/B][/SIZE]0[SIZE="5"][B][U]3[/U][/B][/SIZE]01 a14d0303 c07e13fc cf850240" > /sys/devices/system/cpu/cpu0/cpufreq/plls_table
You need to replace the 258(Hex Value) with your desired value.
Here 258 means
(2*16*16) + (5*16) + 8 = 600
and 3 means it is 600*2 = 1200
Therefore, a2580301 means 1200MHz.
This is a temporary method. For a permanent Method, add this line to a init.d script. Name the script to something like S10_Dyanmic_OC.
Help Others: If you calculate a Hex Value for a particular frequencies add it here:
https://docs.google.com/spreadsheet/viewform?formkey=dG5hdnpsWFdTNExiY2t3dy16VzBvaWc6MQ
You can view all the frequency Hex value's calculated by others over here:
https://docs.google.com/spreadsheet...G5hdnpsWFdTNExiY2t3dy16VzBvaWc&hl=en_US#gid=0
Kernel Related Media:
5 Touch Support:
BootLogo and Progess Bar
Multi Boot
g3mod_v1.3.4_LITE.tar (5.9 MB)
http://www.multiupload.com/3BIF9S2IES
g3mod_v1.3.4_LITE.zip (6.1 MB)
http://www.multiupload.com/9IJTKFIJDX
g3mod_v1.3.3_LITE.tar (5.9 MB)
http://www.multiupload.com/DDMMU0U9YB
g3mod_v1.3.3_LITE.zip (6 MB)
http://www.multiupload.com/DW1QZPDQOY
g3mod_v1.3.4_PERFORMANCE.tar (5.9 MB)
http://www.multiupload.com/H53ZTO5ULW
g3mod_v1.3.4_PERFORMANCE.zip (6.1 MB)
http://www.multiupload.com/WWFL3EXH0Y
g3mod_v1.3.3_PERFORMANCE.tar (5.9 MB)
http://www.multiupload.com/Y9CDMFVH61
g3mod_v1.3.3_PERFORMANCE.zip (6 MB)
http://www.multiupload.com/0MQQRR1KV8
g3mod_v1.3.4_ULITMATE.zip (6.1 MB)
http://www.multiupload.com/I4JCH7E5JE
g3mod_v1.3.4_ULTIMATE.tar (5.9 MB)
http://www.multiupload.com/TEQXRZMKPQ
g3mod_v1.3.3_ULITMATE.zip (6 MB)
http://www.multiupload.com/97DV0V4OQC
g3mod_v1.3.3_ULTIMATE.tar (5.9 MB)
http://www.multiupload.com/KV9SSVWWZ7
g3mod_v1.3.4_EXTREME.tar (5.9 MB)
http://www.multiupload.com/EGZKK89JTZ
g3mod_v1.3.2_LITE Odin
g3mod_v1.3.2_LITE CWM
g3mod_v1.3.1_LITE Odin
g3mod_v1.3.1_LITE CWM
g3mod_v1.3.0_LITE Odin
g3mod_v1.3.0_LITE CWM
g3mod_v1.3.2_PERFORMANCE Odin
g3mod_v1.3.2_PERFORMANCE CWM
g3mod_v1.3.1_PERFORMANCE Odin
g3mod_v1.3.1_PERFORMANCE CWM
g3mod_v1.3.0_PERFORMANCE Odin
g3mod_v1.3.0_PERFORMANCE CWM
g3mod_v1.3.2_ULTIMATE Odin
g3mod_v1.3.2_ULTIMATE.zip CWM
g3mod_v1.3.1_ULTIMATE Odin
g3mod_v1.3.1_ULTIMATE CWM
g3mod_v1.3.0_ULTIMATE Odin
g3mod_v1.3.0_ULTIMATE.zip CWM
g3mod_v1.3.2_EXTREME Odin
g3mod_v1.3.2_EXTREME CWM
g3mod_v1.3.1_EXTREME Odin
g3mod_v1.3.1_EXTREME CWM
g3mod_v1.3.0_EXTREME Odin
g3mod_v1.3.0_EXTREME CWM
Source For Developers:
https://github.com/dharamg3
Note:
We am learning how to develop kernels.
We willl add different features as and when we can implement them.
The main goal of this kernel will be to keep the phone stable and fast.
There will be nothing as alpha or beta releases.
We will give out the kernels directly, but if anything goes wrong and you have to reflash the ROM or kernel, please dont start shouting.
You may give us different ideas on what features to implement. We will try our best to implement all the features you want
Many of the features implemented in this kernel, are taken from marcellusbe's Fugumod Kernel, and we shall be ever thankful to marcellusbe for the fugumod kernel
Warning:
We are not responsible for any damage caused to your phone (softbrick or hardbrick)
Credits:
marcellusbe for all his help, awesome fugumod kernel
supercurio for voodoo v10
Paolo for BFQ I/O Scheduler
All developers for making this an awesome phone
Everyone who is helping is solving different issues with this kernel
Please let us know if we miss anyone ...oh we did already miss someone..thanks G3MOD TEAM too
What to the old thread?
Nm read that
Btw 6th post got some errors...
@Dharam, i have a question. In your v1.8 Kernel, We can change the partitions to any type we want, can't we? Because in Mumbozver's recovery, we could only use ext2/ext4/ext2.
kyrillos13 said:
@Dharam, i have a question. In your v1.8 Kernel, We can change the partitions to any type we want, can't we? Because in Mumbozver's recovery, we could only use ext2/ext4/ext2.
Click to expand...
Click to collapse
The kernel itself supports everything, but CWM only supports EXT2. I will look into either porting CWM4 or getting 2.5 to support more systems.
hillbeast said:
The kernel itself supports everything, but CWM only supports EXT2. I will look into either porting CWM4 or getting 2.5 to support more systems.
Click to expand...
Click to collapse
getting 2.5 to support other partitions will be a better idea...coz for CWM 4 you need complete CM7 source, and also most of the update.zip's on the g3 forums use amend...and CWM 4 supports only edify....
All the best to the future process
Sent from my GT-I5800 using XDA App
Right, I want to work on USB OTG but lack the cable, and the only way I can do it with what I have is if I destroy my only USB cable for my phone. So if someone wants me to do USB OTG, then buy me a cable and I'll do it
All the stuff is there to do it, I just need to get the phone to switch into host mode.
I think v1.9 is going to come sooner than expected...excellent work by the whole team...
Will this root my phone if I install this in Stock ROM?
[email protected] said:
Will this root my phone if I install this in Stock ROM?
Click to expand...
Click to collapse
it will give you ADB Root, but not the superoneclick root...
dharamg3 said:
it will give you ADB Root, but not the superoneclick root...
Click to expand...
Click to collapse
Ok thanks.....
I am a newbie at this...
But, which root did I get when I installed Kyrillos' ROM?
NEXT 2.1.8 placeholder: http://forum.xda-developers.com/showpost.php?p=51678873&postcount=472
STOP! This kernel supports ONLY Samsung Jelly Bean 4.1.x, 4.2.2, CM 10.1.x, 10.2, and 11.0 ROMs. It won't work on ICS, CM 9, CM 10.
FOR NOW I FORBID ANYONE ELSE REUSE THIS STILL IN DEVELOPMENT DUAL BOOT PROJECT FOR HIS/HER OWN GALAXY TAB 2 PROJECT!
IMPORTANT NOTES:
NEXT 2.x separated in two package: the kernel part as blackhawk-next-kernel-2.x-p51xx.zip and the proprietary binaries part as proprietary-vendor-samsung.zip for JB >= 4.2 (stock 4.2.2, CM 10.2) and proprietary-vendor-samsung-4.1.x.zip for JB 4.1.x (stock 4.1.2, CM 10.1) . Flash the kernel and then directly flash the proprietary binaries!
Download both proprietary-vendor-samsung.zip and proprietary-vendor-samsung-4.1.x.zip from http://forum.xda-developers.com/showthread.php?t=2285366 post #2!
Sources:
Kernel sources at http://github.com/kumajaya/android_kernel_samsung_espresso10/tree/cm-10.1-blackhawk
Features:
Samsung stock 4.1.x, 4.2.2 (since 1.8.3), CM 10.1.x and CM 10.2 (since 1.8.3) support with a single kernel image
For stock ROM: external SD card - internal media swapper script included
Samsung proprietary exFAT modules are loaded. CM 10.1 exFAT support files attached at post #2
For CM/CM based ROM, P31xx only: auto rotate screen default orientation depend on ro.sf.hwrotation value, camera orientation fix included
Dual-booting. You can have Samsung JB and CM 10.1 ROMs on a single device at the same time.
Nice looking AROMA based boot menu
Using CyanogenMod kernel source, updated to p3110 source for newer WLAN (Youtube HD bugfix on stock ROM), modem, sensors driver, and etc for both P31xx and P51xx target
CPU clock: 300MHz, 600MHz, 800MHz, 1.008GHz, 1.2GHz, 1.35GHz, 1.42GHz, 1.48GHz, and 1.52GHz, locked @ 1.008GHz on boot
GPU clock: 153.6MHz, 307.2MHz, 384MHz, and 512MHz, 307.2MHz as the default maximum clock
CPU voltage control. You can use Android Tuner/System Tuner/Trickster MOD to set CPU voltage
The ramdisk base on JB 4.1.2 (stock ROM) and JB 4.2.2 (CM 10.1)
Using newer PowerVR SGX 540 kernel modules and binaries blob
row, bfq, sio, and vr scheduler support
Governor bug fix. Replace Samsung's interactive governor with default OMAP4 3.0.31 interactive governor from omapzoom.org, plus pegasusq and lulzactive
NFS and CIFS/samba (not loaded by default) filesystem support
LZMA compressed initrd, to keep boot image smaller than 8MB
swap support. zram and cleancache with a working zcache driver, enabled by default
kernel config, insmod configs.ko and then you can access /proc/config.gz
external modem support, for PPP Widget (not loaded by default, P31xx need powered USB hub for external modem)
Some tweaks from gokhanmoral's siyahkernel for S3, passive entropy tweak applied
Remove a lot of debug message from touchscreen driver, display, mmc, modem, etc
linaro arm-linux-gnueabihf- cross compiler, compiler optimization applied
SuperSU v1.41 for stock ROM
Self compiled BusyBox v1.22.0-git in /sbin, config file based on CM's BusyBox bbconfig output. fstrim applet patch applied, android_reboot applet added (a quick but clean port from Android toolbox), swapon applet with priority option. For stock ROM: this version of Busybox will overwrite busybox binary in /system/bin or /system/xbin and save it as busybox.backup
Early boot scripts support (/system/etc/init.d, /data/local/userinit.sh, and /data/local/userinit.d)
Post boot script support (/system/etc/init.post_boot.sh)
For stock ROM: custom boot animation support (/data/local/bootanimation.zip or /system/media/bootanimation.zip if exists, Samsung boot animation as a fallback). If a bootanimation.zip found, the boot sound will be turned off as well as the shutdown animation.
Modified mount options
adb insecure, adb mode in charge state also insecure
Advanced TCP congestion support, westwood as the default congestion
No /system/etc/hosts patch, you can install AdAway from F-Droid
Known Problems:
Thanks To:
gokhanmoral, amarullz, Phil3759, Chainfire, cmenard, codeworkx, imoseyon, coolbho3k, Faux123, AuxLV
brolee93 for latest P51xx Samsung stock boot image
This part will be expanded. Most of the patches I applied are coded by someone else. Please remind me if I forget to give credits to anybody...
Downloads:
PhilZ Touch blackhawk version attached, PhilZ Touch 5.08.5 attached at post #3
NEXT kernel beta release attached
NEXT tool: http://forum.xda-developers.com/showthread.php?t=2285366
exFAT support files for CM/CM based ROM: http://forum.xda-developers.com/showthread.php?t=2285366 post #2
Todo:
More features in NEXT tool
Special Thanks:
@behemot24, @shakatu, @ironmaskusa, @tetakpatak
XDA:DevDB Information
[KERNEL][SINGLE/DUAL][JB/KK][STOCK/CM]blackhawk's NEXT kernel, Kernel for the Samsung Galaxy Tab 2
Contributors
ketut.kumajaya, Android-Andi
Kernel Special Features: Dual boot stock and AOSP based ROM
Version Information
Status: Stable
Current Stable Version: 2.4
Created 2014-09-21
Last Updated 2014-10-29
NEXT 2.x separated in two package: the kernel part as blackhawk-next-kernel-2.x-p51xx.zip and the proprietary binaries part as proprietary-vendor-samsung.zip for JB >= 4.2 (stock 4.2.2, CM 10.2) and proprietary-vendor-samsung-4.1.x.zip for JB 4.1.x (stock 4.1.2, CM 10.1) . Flash the kernel and then directly flash the proprietary binaries!
Download both proprietary-vendor-samsung.zip and proprietary-vendor-samsung-4.1.x.zip from http://forum.xda-developers.com/showthread.php?t=2285366 post #2!
Changelog:
21/04/2014 2.2:
Flash-Friendly File System (f2fs) support
Full github commits 8/4 - 20/4/2014: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-11.0
Update proprietary blobs, proprietary-vendor-samsung-update.zip
28/10/2013 2.1.4 -> 2.1.5:
Updated to upstream 3.0.101 kernel
Audit and SELinux enabled
Smartreflex completely disabled
GPU frequencies not exposed to STweaks bug fixed
Do not load exFAT modules on CM 10.2
Full changelog: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.2-update
27/10/2013 2.1.3 -> 2.1.4:
Ramdisk updated to sync with latest CM 10.2
21/10/2013 1.8.3 -> 2.1.3:
Update init script for PAC
Disable almost all kernel debugging support except KALLSYMS. Kernel failed to boot with CONFIG_KALLSYMS disabled
Turn all CPUs online when governor gets changed, hotplug bug workaround
SIO and VR I/O scheduler
Initial STweaks support, big thanks @gokhanmoral. Download STweaks app from Play store to access almost all NEXT related settings (CPU governor, frequency, and voltages; GPU governor and frequency limit; surfaceflinger rotation; I/O scheduler; logger; CIFS, Xbox controller, and USB modem support; and dual boot related settings).
Update overclock codes, remove gpu_oc interface: https://github.com/kumajaya/android...mmit/94ac45a10213de400c7bf3c01b5c5b052ae8ba18
sgxfreq: add sysfs interface to store frequency limit: https://github.com/kumajaya/android...mmit/738061b30d2278d3b51b341bc2597dad300f4e47
sgxfreq: limit frequency to default on boot: https://github.com/kumajaya/android...mmit/8a6933cf6565b5587db6a2a5ce7b1207807ab701
The latest Android Tuner app needed to control the modified OMAP GPU control interface but the dirty way by editing /etc/init.post_boot.sh always available
Separated vendor blobs for JB 4.1.x and JB >= 4.2, @poppolo2001 fix applied
With CPU and GPU overclock, CPU under/over voltage, upstream kernel 3.0.96 by @CodyF86
Complete changelog: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.2-update
10/08/2013 1.6.3 -> 1.8.3:
Initial upcoming Samsung 4.2.2 support
Initial CM 10.2 support. Do not flash blackhawk-next-cm-exfat-vold.zip! CM 10.2 already has an open source/reverse engineered exFAT filesystem support
Vendor blobs in separate flashable zip. For all ROMs, on both 1st and 2nd ROM: Flash vendor-blobs-new-ducati-blackhawk.zip directly after flashing NEXT 1.8.3!
Updated to upstream Linux kernel 3.0.41 (incremental patch)
The first kernel utilizing the new ducati firmware, the first kernel preserved 804MB RAM! Don't forget to flash vendor-blobs-old-ducati-blackhawk.zip if you switch to another kernel
zram switched to zsmalloc, zram optimized for Android disabled
XBox 360 USB controller with BigX LED support enabled (by @iks8 request). Modules not loaded by default, edit /system/etc/init.d/02modules to activate it.
23/07/2013 1.6.2 -> 1.6.3:
Add android_reboot applet to NEXT's busybox (a quick port from Android toolbox) to fix AROMA boot menu fail to boot into recovery/bootloader as reported by @kinung
I hate bug!
22/07/2013 1.5 -> 1.6.2:
Hotplug CPU governor working properly with cleancache enabled, zcahe memory corruption problem fixed!
Static linked busybox compiled from source, fstrim patch applied. Busybox config based on CM's busybox bbconfig output. Total 46 new busybox applet, add priority option to swapon applet
zRAM swap per CPU core, same priority value. CM's /system/bin/compcache script updated to handle 2 zRAM devices. Reference: http://wiki.gentoo.org/wiki/Zram
Stock ROM default zRAM size 26% RAM size. Following CM's standard, user can set zRAM value for example to 30% by typing "setprop persist.service.zram 30" over Terminal Emulator or over "adb shell setprop persist.service.zram 30". CM user can use Settings application: Performance - Memory management - zRam.
Swappiness value changed to 90
LZO compression updated to current upstream version, optimized for arm. Reference: http://git.kernel.org/cgit/linux/ke.../?id=b0af9cd9aab60ceb17d3ebabb9fdf4ff0a99cf50
zRAM support optimized for Android, utilizing the new lzo library.
cleancache support with working zcache driver, utilizing the new lzo library
entropy threshold tweaks, /dev/random linked to /dev/urandom
github 14-22/07/2013 commits: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.1-blackhawk
12/07/2013 1.4.1 -> 1.5:
Decrease CPU voltage for frequencies below 1.2GHz, increase CPU voltage for frequencies above 1.2GHz
Re-enable MMC_CAP_ERASE for I/O speed improvement, run "fstrim -v /data" and "fstrim -v /cache" manually to TRIM your filesystem or run LagFix (fstrim GUI, download it from Play)
Remove my old hack in cpufreq driver
Newer PowerVR SGX540 3D kernel module and vendor binaries, in sync to CM-10.1. You must update both 1st and 2nd ROM to renew both ROM vendor binaries!
SuperSU v1.41
16/06/2013 1.4 -> 1.4.1:
I/O speed improvement, 1.3 and 1.4 bugfix
SuperSU v1.34 - thanks Chainfire
nooc: Smartreflex class 3 re-enabled, voltage control disabled
04/06/2013 1.3 -> 1.4:
Selected kernel modules, scripts, and binaries integrated in boot.img, single flash for 1st and 2nd ROM
Kernel compression back to gzip, boot.img compression switched to lzma for better compression (I need more space)
Auto root (for stock)
Auto busybox (for stock)
External sdcard and internal media swapper script integrated in boot.img (for stock as 1st ROM)
Override init.d CPU governor setting on boot completed (technical reason/by design). Please use an app "on boot" or /etc/init.post_boot.sh to set CPU governor
init script reworked (again), simplified
Standalone nooc version, no longer as an addon for standard NEXT
Untested CRT off animation support
NEXT users, please update your kernel to 1.3 version to avoid filesystem corruption risk on Samsung stock/stock based ROM! Please read Dual Boot FAQs how to update your kernel!
01/06/2013 beta -> 1.3:
Better data integrity on both 1st and 2nd ROM
Ramdisk init scripts reworked, inline with the latest Samsung (Taiwan BRI 04/2013) and CM (29/05/2013 nightly)
Inline with P31xx, that's way this port version directly jump to 1.3
Updated exFAT modules (don't know it's better or worse, it's closed source)
Default CPU clock still 1.008GHz, default GPU clock 307.2MHz. Non OC version as an addon
Both version tested on P3100 (remember, I have no access to P51xx device). Booted, upscale graphics, touchscreen not work, wrong orientation sensor, swapped volume button, got 1280x800 screenshots :laugh:
30/05/2013: Initial beta release.
Dual Boot FAQs
Adapted from droidphile's "Dual Boot FAQs" with permission.
1. "Why would I wanna dual-boot?"
A. You don't have to.
Suppose you're more of an aosp rom fan. But misses the HDMI out, bluetooth hands-free and love sammy camera more. Do a minimal installation of sammy rom and boot into it when in need of these features and use aosp rom otherwise.
Or you are a sammy rom fan but love the responsiveness and pure android feel of aosp roms.
And while you can dual boot two sammy or two aosp roms, it doesn't make any sense.
2. "What if I don't need dual booting?"
A. No issues. Kernel won't force to setup 2 roms. You can single boot as before.
3. "Will dual booting change my bootloader or do any dangerous stuff like setting my phone on fire?"
A. NO. Changes are at kernel and ramfs level only. Some space in your internal sd card is used, and also the unused hidden partition mmcblk0p11 is used to store cache of second rom. Dual booting doesn't repartition the filesystem or perform anything scary.
4. "I want to setup dual booting."
A. There are four situations:-
1) Sammy rom now. Want to use aosp as secondary.
2) Sammy rom now. Want to use aosp as primary.
3) Aosp rom now. Want to use sammy as secondary.
4) Aosp rom now. Want to use sammy as primary.
Prerequisites for any setup is
a) Flash latest blackhawk's NEXT kernel
b) Flash new ducati vendor blobs (since 1.8.x)
c) Flash latest PhilZ Touch - blackhawk repack version - recovery
d) Atleast 90% battery left.
e) 2 GB free on internal SD.
f) Some spare time
1) Present sammy, setup aosp as secondary:-
i) Reboot into recovery
ii) Flash blackhawk's NEXT tool, create system.img for CM/CM based ROM and then close it
iii) Reboot into secondary recovery
iv) Flash aosp ROM as 2nd ROM
v) Flash blackhawk's NEXT kernel again
vi) Flash new ducati vendor blobs again (since 1.8.x)
2) Present sammy, setup aosp as primary:-
i) Reboot into recovery
ii) Nandroid backup your current sammy ROM
iii) Flash blackhawk's NEXT tool, create system.img for Samsung stock/stock based ROM and then close it
iv) Reboot into secondary recovery
v) Nandroid restore your sammy ROM as 2nd ROM
vi) Flash blackhawk's NEXT kernel again
vii) Flash new ducati vendor blobs again (since 1.8.x)
viii) Reboot into primary recovery
ix) Flash aosp ROM as 1st ROM
x) Flash blackhawk's NEXT kernel again
xi) Flash new ducati vendor blobs again (since 1.8.x)
3) Present aosp, setup sammy as secondary:-
Same as (1), instead of flashing aosp to second, flash sammy to second.
4) Present aosp, setup sammy as primary:-
Same as (2), instead of flashing aosp to first ROM, flash sammy.
NOTE:
-To dual boot Two Aosp or Two Sammy roms, just follow (1) or (2) (depending on which one of them you want as primary/secondary), just flash Sammy instead of aosp or aosp instead of sammy.
5. "What things should I be taking care off while dealing with dual booting?"
A. - Make sure where you are: in primary or secondary recovery.
6. "How to boot into primary rom?"
A. AROMA based boot menu will help you on every boot.
7. "How to boot into secondary rom?"
A. AROMA based boot menu will help you on every boot.
8. "Is kernel partition shared?"
A. Yes. Same kernel boots both roms.
9. "If I flash another kernel (that doesn't support db) do I lose dual booting?"
A. Yes
10. "I lost dualbooting after flashing another kernel. I didn't do anything to second rom files in sdcard/.secondrom. How can I get db back?"
A. Just flash the latest blackhawk's NEXT kernel, flash new ducati vendor blobs again (since 1.8.x)
11. "Will there be any performance degradation on the rom used as secondary compared to primary?"
A. NO
12. "Will my phone run slow overall because of db?"
A. NO
13. "How to flash a newer version of 1st rom?"
A. As usual, just flash it from primary recovery. Flash blackhawk's NEXT kernel again, flash new ducati vendor blobs again (since 1.8.x)
14. "How to flash newer version of 2nd rom?"
A. Just flash it from secondary recovery. Flash blackhawk's NEXT kernel again, flash new ducati vendor blobs again (since 1.8.x)
15. "Would upgrading 1st or second rom cause other rom to fail on boot?"
A. No. Partitions of other rom are not touched during upgrading.
16. "I miss the recovery I used before, so much.."
A. PhilZ Touch not bad at all.
17. "User apps of 1st rom are automatically available for second rom?"
A. NO. However, if you had backed them up using Titanium Backup or similar apps, just restore apps while on second rom.
18. "I wanna keep separate backup for apps in both the Roms, since I use one Rom for say entertainment and other productivity."
A. Setup different backup directory in Titanium Backup in 1st and 2nd rom.
19. "I don't see STweaks app in second rom."
A. This is blackhawk's NEXT dual boot solution for Galaxy Tab 2, a free implementation of gokhanmoral's Siyah dual boot.
20. "Do I need to anything special before flashing a newer blackhawk's NEXT kernel?"
A. NO. Just flash kernel in primary and secondary recovery. Yes, on both 1st and 2nd ROM. Just flash kernel in recovery - whichever you used to do. Kernel image is copied to the unified kernel partition (since 1.4 version). Flash new ducati vendor blobs (since 1.8.x) on both ROM may be required to ensure vendor blobs match to the kernel
21. "How can I run same STweaks settings of 1st Rom in 2nd Rom?"
A. This is blackhawk's NEXT dual boot solution for Galaxy Tab 2, a free implementation of gokhanmoral's Siyah dual boot.
22. "How do I remove everything related to DB and run single boot again?"
A. In primary recovery, flash blackhawk's NEXT tool and delete 2nd ROM system image. OR delete .secondrom directory in /data/media while on 1st Rom.
23. "If secondrom files are kept in /data/media, will wiping data in recovery erase second rom files?"
A. NO. /data/media is skipped in CWM recovery.
24. "I was using ExFat card on sammy rom without any issues. I have setup dual boot with aosp and now after booting into CM it says microSD card is corrupted."
A. Aosp roms doesn't support ExFat out of the box. The data was corrupted by aosp vold. Even if you boot back to Sammy rom, it still would be corrupted. To recover data, manually mount the card in recovery, copy contents to internal SD and reformat card to a Fat32.
Also try
chkdsk X: /f (where X is the drive letter of microsd), you may be able to copy data.
25. "I read somewhere that both rom data partition use the same space. Doesn't that mean my apps are shared across roms?"
A. NO. It just means they uses same partition. They're still different directories.
1st rom data = /data
2nd rom data = /data/media/.secondrom/data
26. "Will hitting "Boot into Secondary Recovery" in recovery boot menu change my recovery?"
A. NO. It just runs (not flash) an alternate recovery so that you can configure dualboot settings.
27. "How do I backup 1st Rom and 2nd Rom?"
A. To backup 1st Rom, do what you did to backup rom while you were single booting a while ago.
To backup 2nd Rom, use the secondary recovery.
28. "Is there an easier way for dual-boot?"
A. Yes, send your device to me.
29. "DB architecture?"
A. Like you know, every rom has a /data, /system, /cache partition and a kernel to boot.
For primary rom, it's
mmcblk0p10 = /data
mmcblk0p9 = /system
mmcblk0p7 = /cache
And these won't change whether you're single booting or dual booting.
For secondary rom, data and system is stored in internal sd, cache in hidden partition. Note that internal sd in our device is mounted to /data/media.
We have data as a directory, System as an image in data/media/.secondrom. Cache in mmcblk0p11 which is hidden partition and not used otherwise.
- When second rom is booting, second rom data is bind mounted to mmcblk0p10 as /data/
- data/media/.secondrom/system.img partition is mounted as /system.
- mmcblk0p11 is mounted as /cache.
More FAQs will be added and the list will be updated as DB is improved.
Dual Boot Exercises
http://forum.xda-developers.com/showthread.php?t=2285366 post #4.
Was waiting for this :victory:
Sent from my GT-P5110 using XDA Premium HD app
Just opened a new thread for my masterpiece work on Galaxy Tab 2. Enjoy it and don't forget to press my Thanks button or better my DTM button
PhilZ Touch attached in post #1 has a "red" on screen navigation bar in secondary recovery to distinguish between primary and secondary :laugh:
So this kernel boots 1 ROM over internal storage and second over SD card?
Sent from my GT-P5110 using XDA Premium HD app
Marionette said:
So this kernel boots 1 ROM over internal storage and second over SD card?
Sent from my GT-P5110 using XDA Premium HD app
Click to expand...
Click to collapse
Dual Boot FAQs #29.
Ohhh good news i go to test thanks you rock
With 0.6 i can oc 1.35.
But now i have freez or reboot or black screen
brolee93 said:
Ohhh good news i go to test thanks you rock
With 0.6 i can oc 1.35.
But now i have freez or reboot or black screen
Click to expand...
Click to collapse
Please try increase the CPU voltage by 25mV. In this version, CPU voltage 50mV lower than the previous values. You can use Android Tuner or /system/etc/init.post_boot.sh .
KK, you are a genius! This is working splendidly, I have cyanogen as my primary and blaster as my secondary and they are both workihg smooth for me so far... I have them both running currently at 1200 mhz and seem to be doing fine.. you have really made my day!
Sent from my GT-P5113 using Tapatalk HD
Running smoothly for Zap Blaster.
ironmaskusa said:
KK, you are a genius! This is working splendidly, I have cyanogen as my primary and blaster as my secondary and they are both workihg smooth for me so far... I have them both running currently at 1200 mhz and seem to be doing fine.. you have really made my day!
Sent from my GT-P5113 using Tapatalk HD
Click to expand...
Click to collapse
I actually watched your HDMI problem. It's one of the reasons this dual boot solution was born. Glad I could help you, thanks for your support :good:
shakatu said:
Running smoothly for Zap Blaster.
Click to expand...
Click to collapse
Really? And all your init.d scripts removed by NEXT
That's okay cuz I have No Frills set up for my CPU settings. Of course my public release is still running kkboot 1.6.
After looking at your install script IDK if I would include this in my ROM if/when you allow people to. I'll let them make up their own mind.
Sent from my GT-P5113 using XDA Premium HD app
shakatu said:
That's okay cuz I have No Frills set up for my CPU settings. Of course my public release is still running kkboot 1.6.
After looking at your install script IDK if I would include this in my ROM if/when you allow people to. I'll let them make up their own mind.
Sent from my GT-P5113 using XDA Premium HD app
Click to expand...
Click to collapse
Personally, I found that Zap Blaster works well my device (p5113) because of the IR and such.. plus at the time it was overclockable and my HDMI output worked well with it. So, I decided to use it for awhile.. but I could not resist CM because it runs so smooth and I love how clean and reliable it has always been on me for this device as well as other devices I have owned.
Again, I am very happy about this DUAL boot option and I don't think I will change my setup for a time to come... My tablet is perfect now, in my opinion. Thanks again, KK.
The tablet behaviour between this kernel and the samsung original kernel is completely different! Ketut, if samsung would give a crap about their customers, they should buy this kernel from you and push it on all the galaxy tab 2... but that's not going to happen, so actually only the xda members have the chance to see their tablet working as it should, thanks to your work. Lucky us
behemot24 said:
The tablet behaviour between this kernel and the samsung original kernel is completely different! Ketut, if samsung would give a crap about their customers, they should buy this kernel from you and push it on all the galaxy tab 2... but that's not going to happen, so actually only the xda members have the chance to see their tablet working as it should, thanks to your work. Lucky us
Click to expand...
Click to collapse
For free A lot of clicks to install NEXT package but why people missed to click my Thanks button
EDIT:
This kernel version will directly jump to 1.3 in order to sync with P31xx version. Still inspecting line by line using diff tool to make sure already in sync
When i install this kernel on ZapBlaster the Video Player and Camera stops working
Sent from my GT-P5113 using xda premium
rap3rman said:
When i install this kernel on ZapBlaster the Video Player and Camera stops working
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
Two apps I never use on my tablet, so I haven't tested them...
ketut.kumajaya said:
Please try increase the CPU voltage by 25mV. In this version, CPU voltage 50mV lower than the previous values. You can use Android Tuner or /system/etc/init.post_boot.sh .
Click to expand...
Click to collapse
yeah ok i see this .
can you add Stweaks support ?
[ROM]★★[JB 4.2.1][CROMi-X 5.4][DATA2SD/ROM2SD | ODEX/DEODEX 10.6.1.27.5][FEB 22]★★
TF700 USERS: YOU MUST BE ON THE ASUS STOCK JB 4.2.1 BOOTLOADER VERSION 10.6.1.14.x AND TWRP 2.5.0.0+ BEFORE FLASHING THIS ROM. SEE UPGRADE INSTRUCTIONS BELOW IF YOU ARE UNSURE
If you have a different ASUS tablet, please look at this thread to see if there is a compatible version of this ROM.
I recommend you do a full wipe if coming from another ROM. Choose Wipe – Factory in TWRP. Do not do a full wipe from the bootloader.
You can restore data from Titanium Backups but please do not restore system data or apps from a previous version or another ROM if you want a nice clean smooth upgrade experience.
Don't forget to do a Nandroid Backup first and give the ROM 10 mins to stabilise!
{
"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"
}
ABOUT
• CROMi-X is a stock based ROM designed from scratch from the ASUS Stock 10.6.1.27.1 & 10.6.1.14.10 Jelly Bean 4.2.1 WW releases and 10.6.1.x bootloader. It has its roots in the original CleanROM by scrosler
• CROMi-X is targeted to towards the user that wants a ROM with the ability to pick and choose the options they want!
• CROMi-X is tuned for performance and built for stability!
• CROMi-X is true to stock in looks!
• CROMi-X can be provisioned for US and non US – World Wide (WW) editions during the install process
• CROMi-X Source on github : here
• Thanks to scrosler, elesbb, pjc21, _that, flumpster, timberwolf671, LetMeKnow, Robgee789, elfaure, That’s OK & Thibor69 for their invaluable help in making this possible!
All the testers. Thank you so much for your patience and testing! :highfive:
Additional thanks to all the File Hosters: @johnlgalt and @workdowg :good:
• A huge thanks to @nomad10002, @Mackis, @mikmock, @RagingHarry, @sgkla, @okantomi and @jtrosky for donating too much money to my CROMI projects! :good:
FEATURES
• BOTH 4.1 and 4.2 GUIs are available - use settings - launchers to switch
• ODEX/DEODEX version available.
• Aroma Installer with the following options:
• Locale: US or WW
• DPI Size: 213 (TF700 recommended small fonts), 240 (Stock fonts), 224 (Medium fonts) & 200 (Small fonts), 180 (Tiny fonts) & 160 (Specsavers fonts)
• Kernels: _that / stock modded kernel variant based from ASUS Stock 10.6.1.14.8 & sbdags ASUS Stock Modded 10.6.1.27.5 Kernel, plus Hund's Kernel
• Launchers: Asus Stock, Apex , Nova, ADW
• Boot Animations: CROMi-X Asus Bios, CROMi-X Blue Fire, CROMI-X Yellow Spinner, CROMi-X Fire and Water, Asus Stock, Nexus Google
• Google Apps : Multi DPI Play Store, News & Weather Genie, Gmail, Maps, Talk, YouTube, Google Now and Voice Search, Google Music, Street View for Maps, Document Viewer, Gallery, Picasa
• Asus Apps: File Manager, App Back Up, App Locker, My Cloud, My Net, SuperNote, Video Editor, Web Storage, My Frame, My Dictionary, Splashtop, My BitCast, My Library (Asus Reader – only works on 160 DPI), Screen Saver, Asus Live Wallpapers (Asus Day Scene, My water & My Water II),Parental Control
• Apps Removed: Google Plus, Kindle, Chrome, Press Reader, Vibe, Zinio, CM Client, DM Client (calling home apps), DRM Content Provider
• Misc Apps: ESFile Explorer, Adobe Flash, AdAway, Titanium Backup, DropBox, DSP Manager, Rebooter, LMT Pie Control, Keyboard Manager
• File system and performance tweaks!
• Init.d support!
• Zip align on boot!
• Advanced Power Menu
• Auto Brightness reconditioned (Brighter at lower light levels for IPS+)
• 4.1 or 4.2 GUI Switcher enabled via Settings…Launchers….
• Browser performance tweaks (Extra menu with OpenGL Rendering, Light Touch and CPU Upload Path enabled)
• Browser2RAM init.d scripts (Default Browser, Firefox, Naked Browser and Chrome version)
• Scroll Caching Disabled for smoother in app scrolling
• Fsync Disabled option for extreme speed!
• Data2SD/ROM2SD implemented via _that’s or Hund's kernel
• Over-Clock, Under-Volt and Over-Volt scripts via _that's or Hund's kernel
• Cache2SD implemented via Meldrak's scripts. Full Thread HERE
• Continued Best Support of any ROM!
ISSUES
None that I am aware of
CHANGE LOG
22/02/2014 CROMi-X v5.4 Full ROM
o Removed CROMi-Control app. After discussions with elesbb he will redevelop as an xposed module
o Reverted Framework (framework.jar, services.jar, systemui.apk, transformer.apk) to pre-cromi-control versions
o Modded systemui.apk and transformer.apk to allow sd card and dock notifications to be removed as an option in installer
o Rebuilt Stock Launcher Lite version - 3 Screens ONLY, New Beach Wallpaper, 4.2 Gui gets 9x6 workspace and draw icons, removed google bar and page indicator
o Fixed framework-res.apk wallpaper inconsistencies. Tree definitely gone now and beach wallpaper formatted correctly
o Added installer option to switch balanced and performance profiles. If you choose balanced you actually get performance. Device boots to performance
o Changed entropy settings to stop kernel rebuilding entropy_avail - result should be less lag
o Updated _that's OC kernel to version 8
o Updated Hunds' kernel to version 3.4.5
o Updated LetMeKnow's ET to Hunds' 3.4.5 kernel
o Updated Google Core Services and libs to latest version
o Updated Titanium Backup to version 6.1.5.3
o Updated Google Maps to version 7.6.1
o Updated Google Music to version 5.4.1409N
o Updated Google Now to version 3.2.17
o Updated Superuser and binary to latest version 1.93
o Updated ES File Explorer to version 3.1.0.2
o Updated Asus Web Storage to version 2.1.3.7556
o Updated Google Mail to version 4.7.2
o Fixed issue of ET installation locked into 213 DPI
o Fixed search options missing - Reinstated QuickSearch from Asus
o Minor build.prop fix to remove duplicate entry
o Fixed build.prop for TF300T US users as it was showing the wrong version
18/01/2014 CROMi-X v5.3 Full ROM
o Recompiled framework-res.apk with TF701T default wallpaper. Goodbye Asus Tree
o Fixed Google Keyboard not defaulting on clean install when Asus keyboard is not installed
o Fixed the minutes of lag after installing apps from the play store - it's seconds now - but much better now
o Fixed older version of hunds app in deodex version
o Fixed older version of GPU UV in odex version
o Fixed missing battery widget on odex version
o Extracted libs from Google Keyboard so it can go back to /system/app
o Extracted libs from Google Search so velvet.apk can go back to system/app
o Updated and Extracted libs from Google Framework Services so GmsCore.apk can go back to system/app
o Changes to 50CleanTWeaks script for vm tweaks - should do much better with lag. See below url for explanations
https://www.kernel.org/doc/Documentation/sysctl/vm.txt
Removed the following kernel tweaks - probably better leaving them default for now:
echo "0" > /proc/sys/vm/panic_on_oom
echo "0" > /proc/sys/vm/laptop_mode
/system/xbin/sysctl -w vm.drop_caches=3
Changed
/system/xbin/sysctl -w vm.dirty_ratio=90 from 22
/system/xbin/sysctl -w vm.dirty_background_ratio=70 from 4
/system/xbin/sysctl -w vm.min_free_kbytes=5572 from 4096
/system/xbin/sysctl -w vm.vfs_cache_pressure=10 from 50
/system/xbin/sysctl -w vm.dirty_expire_centisecs=200 from 3000
/system/xbin/sysctl -w vm.dirty_writeback_centisecs=500
o Re-added optimized remounts on boot on /data /cache and /system
o Updated the 3D processing fps limits from LetMeKnow in CPU2.sh and CPU3.sh
logi "setprop persist.tegra.NV_FPSLIMIT 1"
setprop persist.tegra.NV_FPSLIMIT 1
logi "setprop persist.sys.NV_FPSLIMIT 90"
setprop persist.sys.NV_FPSLIMIT 90
o Build.prop edits:
Removed:
wifi.supplicant_scan_interval=180
persist.android.strictmode=0
ro.vold.umsdirtyratio=20
ro.ril.disable.power.collapse=0
com.qc.hardware=true
debug.enabletr=true
debug.sf.hw=true
net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
windowsmgr.support_rotation_270=true
o Updated Extreme Tweaks version to 1.6. Thanks LetMeKnow.
o Updated ES FIle Explorer to version 3.0.9.1
o Updated YouTube to version 5.3.32
o Updated Google Text to Speech to latest version
o Updated Gravity Box to version 2.9.2
o Fixed Xposed not loading after a clean install - modules still need to be toggled off/on and a single reboot per module
o Removed lagfix. Since I stopped using it I have not had any data corruption. It's on the play store if you want it
05/01/2014 CROMi-X v5.2.4 Full ROM
o Fixed Adobe Flash Player so works with Amazon Prime. Now loaded to /data for compatibility
o Updated Hosts file for adblocking option
o Updated ES File Explorer to version 3.0.9.0
o Updated Titanium Backup to version 6.1.5.2
o Updated You Tube to version 5.3.28
o Updated SuperUser and binary to version 1.86
o Updated DropBox to version 2.3.12
o Updated Google Play Store to version 4.5.10 for non TF700 users
o Updated Gravity Box to version 2.8.5
o Updated Hunds kernel to version 3.4.4 beta
o Updated latest Lucius Tweaks for non ET versions. Thanks lucius.zen
changed scheduler to SIO for Hunds based kernels and tcp congestion control to lp
changed OV table values for CPU and GPU
o Tweaked vm settings in init.d scripts to see if it eliminates some lag
/system/xbin/sysctl -w vm.dirty_ratio=22
/system/xbin/sysctl -w vm.dirty_background_ratio=4
/system/xbin/sysctl -w vm.dirty_expire_centisecs=3000
/system/xbin/sysctl -w vm.dirty_writeback_centisecs=500
o Moved UserDictionaryProvider back to /system/app to fix Thumb Keyboard issues - thanks meldrak
o Updated libAppDataSearch.so and libgames_rtmp_jni.so in /system/lib to stop google play service redownloading. Thanks meldrak
o Fixed Stock Browser with better compiled version - helps search bar consistency. Thanks meldrak
o Replaced QuickSearch functionality with better version. Thanks meldrak
o Recompiled the AsusReader.apk with Alice in Wonderland epub removed. Still creates a 0 byte stub
o Updated cache2sd scripts to version 1.5. Thanks meldrak. Thread is here http://forum.xda-developers.com/showthread.php?t=2258050
o Added Keyboard Dock remapping option to installer - LOCK key = DELETE and SEARCH key = LEFT ALT
Older Versions:
16/12/2013 CROMi-X v5.2.3 Full ROM
o Updated CROMi-Control to fix the reboot issues. Thanks elesbb
o Updated Hunds TF700T kernel to version 3.4.3
o Updated LetMeKnow's ET to Hunds 3.4.2 v1.5
o Moved the XT9 user databases to the Asus Keyboard installer
o Updated read ahead values for stock based kernels to 4096KB for internal and 6144KB for external SD
o Removed redundant sysctl entries in 50CleanTweaks (Both normal and ET). Thanks lucius.zen
o Set midrange_freq = 760000, max_normal_freq = 1300000, timer_rate = 20000 and min_sample_time = 40000 in 50CleanTweaks. Thanks lucius.zen
o Changed the default hunds hotplug interface settings to 2 4 6. LMK's ET is still set to 0 0 0
o Zipaligned all apks in the ROM
o Updated Google Music to version 5.3.1316M
o Updated Google Keyboard to version 2.0.19133.927933a
o Updated Google Maps to version 7.5.0
o Updated Google Calendar to version 201308023
o Updated Google Mail to version 4.6
o Updated multi-dpi playstore to version 4.5.10
o Updated ESFileExplorer to version 3.0.7.0
o Updated Keyboard Manager to version 2.11
o Updated Xposed Installer to version 2.4.1
o Updated Xposed GravityBox to version 2.8.1
o Updated SuperUser to version 1.85
o Fixed ThumbKeyboard issues - thanks meldrak
05/12/2013 CROMi-X v5.2.2 Full ROM
o Updated thatv6 kernel to thatv7 test for sdcard fixes and tcp congestion control
o Updated TF700 Hunds Kernel to version 3.4.2 Beta
o Updated LetMeKnow's TF700 ET to version 1.3 and best bits from 1.4
o Updated 50CleanTweaks Init.d script (thanks LMK and lucius.zen):
/system/xbin/sysctl -w fs.file-max=131072
/system/xbin/sysctl -w fs.inotify.max_queued_events=32768
/sys/devices/system/cpu/cpufreq/interactive/go_maxspeed_load=85
/sys/devices/system/cpu/cpufreq/interactive/max_boost=1800000
/sys/devices/system/cpu/cpufreq/interactive/midrange_freq=900000
/sys/devices/system/cpu/cpufreq/interactive/midrange_go_maxspeed_load=65
o Set swapiness back to 0
o Set read ahead KB to 4096KB
o Dropped GPU UV by 15mV - 45mV in 91GPUUV init.d script
o Dropped CPU OV by 10mV - 40mV in 89OV init.d script
o Updated file system tuning tweaks in installer (should fix kernel forced reboots to reoptimize)
o Changed TCP congestion algorithm to westwood for all versions (should help wifi performance)
o Updated Google Keyboard to version 2.0.19123.914326a
o Updated YouTube to version 5.3.24
o Updated Titaninum Backup to version 6.1.4.3
o Updated dropbox to version 2.3.11.4
o Updated SuperUser app and binary to version 1.80
o Updated Google Services to latest version
o Updated Android Terminal to version 1.0.54
17/11/2013 CROMi-X v5.2a Full ROM
o Fixed rebooting issue when flashing _thatv4 kernel (v5.2a)
o Fixed the missing Settings Status which was causing force closes
o Fixed WiFi slowing down after sleep issues - thanks LMK
o Fixed missing keyboard permissions
o Fixed Android is Upgrading message on every boot for ODEX version
o Fixed missing busy box symlinks
o Fixed ROM2SD installer script - installs the correct pre-init script to internal /system/boot
o Updated and resized the Stock Bootanimation to the new TF700T JB4.3 Asus Stock
o Updated _thatv5 kernel to newer _thatv6 rebased to 10.6.1.14.10 and 4.3 compatibility
o Updated CleanTweaks interactive governor control to go max a little earlier
o Updated Google Play Services to latest version
o Upated SuperUser and SU binary to version 1.69
o Added Android Terminal Emulator to ROM as option
o Moved libereader.so to Asus Reader option
o Moved FaceLock to be an option in the installer
10/11/2013 CROMi-X v5.1.2 Full ROM
o Fixed build.prop files to have correct version for all devices
o Fixed issues re-optimizing dalvik cache on reboot for ODEX users
o Added Rom2SD compatibility to ROM. Thanks to _that. You must use Gparted to create Fat32, EXT4 and EXT4 partitions and be on your fast microsd
o Added miniCROMi-X Launcher - debloated Asus Launcher (all wallpapers removed and one TF701T added)
o Updated LetMeKnow's ET to version 1.1
o Updated EXT 4 tuning options to safer data journaling enabled versions in the installer
o Updated fix from LMK for slow wifi performance for all editions
o Updated CleanTweaks fs.file-max=65536 as recommended setting for 1GB RAM
o Updated CleanTweaks interactive governor control to be a bit more battery friendly
o Updated the egl.cfg file for the GPU Rendering : Disable Software Rendering option
o Updated Hunds App to version 2.4
o Updated Google Boot Animation to larger size
o Updated Google Play Services to version 4.0.31
o Updated Google Keyboard to version 2.0.18933.905102a
o Updated Google Calendar to version 201306302
o Updated Google Maps to version 7.4.0
o Updated Google Music to version 5.2.1301L
o Updated Titanium Backup to version 6.1.3
o Updated ES File Explorer to version 3.0.6.0
o Updated AdAway to version 2.8
o Updated AdBlocking Hosts file to http://winhelp2002.mvps.org November version
o Updated GravityBox for Xposed to version 2.6.9
o Moved Google Keyboard and Libraries to be an option
o Moved Google Live Wallpapers to be an option
o Moved Asus Email, Exchange and Widget to be an option
o Moved Asus Keyboard and Libraries to be an option
o Moved Asus Taskmanager to be an option
o Moved Asus Battery Widget to be an option
o Removed mms.apk and phone.apk as not required
o Removed the TF701T Weather Widget and App - will offer as a separate download
o Removed ES File explorer classic theme - you can download this from the store
o Removed GoLauncher HD - hasn't been updated in a year and who uses it really?
o Updated ME301T audio and camera modules from 10.6.1.31 for MemoPad 10 users
28/10/2013 CROMi-X v5.1.1 Full ROM
o Updated missing auto brightness profiles from Deodex version
o Updated auto brightness profiles for Prime to match Infinity ones
o Changed Rom Build Name as breaks TWRP backup naming convention
o Updated CROMi-Control to version with fixed Res Changer - thanks elesbb
o Updated Google Play Store to version 4.3.11 for non TF700 users
o Fixed PlayStore reverting to older version for TF700 users and updated to Multi-DPI version 4.4.21
o Moved updated Google Play Services to /system/app - solves issues of update on new install
o Updated GravityBox Xposed Module to version 2.6.5
o Updated YouTube to version 5.2.27
o Updated Google Music to version 5.2.1233L
o Updated Google Maps to version 7.3.0
o Updated Asus Reader to TF701T version
o Recompiled Asus Apps with TF701T equivalent App Icons
(Browser, Email, Calculator, Download Manager, File Manager, Contacts, Settings, Sound Recorder, Calendar, Gallery, Camera)
o Removed GMSCore.apk (Google+) as redundant in /system/app
o CROMi-X Bios bootanimation speed improvements
o Switched the data2sd card layout to hunds method as a bit more logical than _thats - one consistant approach now
o Rom now wipes cache on every install - option in installer is now only for dalvik cache
Extracted TF701T Wallpapers - available in a separate download in post 2 - just extract to microsd and use gallery to set as wallpaper
13/10/2013 CROMi-X v5.1 Full ROM
o Rebased from Asus Stock 10.6.1.27.5 so updated to version 5.1
o Re-Odexed as new framework base & recompiled Asus Browser with speed tweaks
o Updated CROMi Control to version 1.0.2. Thanks elesbb
o Updated the Asus Weather app to the one from the new TF701T Tegra 4 rom as a trial
o Updated Hunds App to version 2.3
o Updated TF700 Hunds Kernel to version 3.4.1
o Updated LetMeKnow's Extreme Tweaks v1.0 with Hunds 3.4 kernel
o Updated Xposed Installer to version 2.3.1
o Updated Xposed Module GravityBox to version 2.6.1
o Updated Titanium Backup to version 6.1.1
o Updated cache2sd to v1.4. Thanks meldrak. Don't run this if you are already using data2sd
o Fixed missing incorrect symlinks for Hulu Plus fix - thanks flumpster
o Fixed SD-EXT shows correct size in installer now if you have an EXT partition on the sd card
o Fixed BlueTooth name - no longer Nexus 4 by default
o Removed Rebooter app as could be causing data corruption with fsync disabled
ChangeLog from Asus:
1. Improve system stability
2. Update Polaris Office to v4.0.5030, to fix Spanish IME issue with keyboard dock
3. Support HDMI 1080P output when play Full HD video clip
4. Fixed the issue that sometime the Weather widget will fail to update weather data
Click to expand...
Click to collapse
UPGRADE INSTRUCTIONS
Start by choosing the scenario below which reflects how your tablet is currently configured.
Scenario One
Factory Stock Android Operating System & Bootloader (Asus 10.6.1.x)
Steps
1. If you haven’t yet, unlock and root your TF700 by following these instructions.
2. Install the latest version of Team Win Recovery Project (TWRP) - TWRP XDA Thread
Download and install the Scott's TF700T Recovery Install Tool. Once downloaded, extract the files on your Windows PC, connect your tablet to the computer and run the Recovery Install Tool.bat file.
3. Skip Scenario Two and Jump to the Installing CROMi-X section.
Scenario Two
Custom recovery such as TWRP or Clockworkmod installed with a Custom ROM package
Steps
1. Update your bootloader to the latest one for your device by flashing from your existing custom recovery and then choose reboot from the menu.
Please don't flash these at the same time as a ROM package as the latter will cancel the bootloader/TWRP flash.
TF700 World Wide WW SKU Users:
10.6.1.14.10 WW Bootloader and TWRP 2.6.1.0 DOWNLOAD 1
10.6.1.14.10 WW Bootloader and TWRP 2.6.1.0 DOWNLOAD 2
10.6.1.14.10 WW Bootloader and TWRP 2.6.1.0 DOWNLOAD 3
md5: ef765b8aec5f28cdea3d0c1381ee573f
TF700 North American US SKU Users:
10.6.1.14.10 US Bootloader and TWRP 2.6.1.0 DOWNLOAD 1
10.6.1.14.10 US Bootloader and TWRP 2.6.1.0 DOWNLOAD 2
10.6.1.14.10 US Bootloader and TWRP 2.6.1.0 DOWNLOAD 3
md5: 3032bebe982920208eea4c4893ab01cd
TF700 Taiwanese TW SKU Users:
10.6.1.14.10 TW Bootloader and TWRP 2.6.1.0 DOWNLOAD 1
10.6.1.14.10 TW Bootloader and TWRP 2.6.1.0 DOWNLOAD 2
10.6.1.14.10 TW Bootloader and TWRP 2.6.1.0 DOWNLOAD 3
md5: 2555a7b2071ba89a2d64c25ac31b5cbb
TF700 Japanese JP SKU Users:
10.6.1.14.10 JP Bootloader and TWRP 2.6.1.0 DOWNLOAD 1
10.6.1.14.10 JP Bootloader and TWRP 2.6.1.0 DOWNLOAD 2
10.6.1.14.10 JP Bootloader and TWRP 2.6.1.0 DOWNLOAD 3
md5: 9e2b696fab3c3d1b96374290195d9da2
IT WILL TAKE ABOUT 1 MINUTE TO MOVE THE BLUE BAR TO FULL. DON'T PANIC AND DON'T INTERRUPT IT!
After the blue bar fills your device will reboot back into your normal ROM but you will be on the new bootloader and have TWRP installed
2. Next Step, please go to the Installing CROMi-X section.
Scenario Three
I'm upgrading from CROMi-X 4.x.
Steps
1. Congratulations. Jump directly to the Installing CROMi-X section.
INSTALLING CROMi-X
If you followed the appropriate steps for your scenario above, you now have a compatible bootloader installed and a custom recovery such as TWRP.
Steps
1. Download the appropriate ROM package below and save to your internal or external SD Card. Do not unzip the file. Join the debate about which manner of packaging files is better (ODEX or DEODEX) or just use DEODEX since it allows for a bit more customization possibilities. ODEX may boot slightly faster but then again, it may only boot slightly faster the first time. Google ODEX vs DEODEX if you really want to understand.
DEODEX VERSION DOWNLOAD
CROMi-Xenogenesis 5.4 DEODEX Full Mirror 1
CROMi-Xenogenesis 5.4 DEODEX Full Mirror 2
CROMi-Xenogenesis 5.4 DEODEX Full Mirror 3
MD5 Sum: ead2750ffb5110ae022e971811a08151
ODEX VERSION DOWNLOAD
CROMi-Xenogenesis 5.4 ODEX Full Mirror 1
CROMi-Xenogenesis 5.4 ODEX Full Mirror 2
CROMi-Xenogenesis 5.4 ODEX Full Mirror 3
MD5 Sum: 69451bc3bb546238520d9412b9c574ff
Browser Key on Keyboard fix DOWNLOAD
Click here!
If you want to back up a ROM2SD installation or flash a different ROM onto your micro SD then please see instructions here. Thanks _that!
ROM2SD Thread
2. Boot to recovery – Either choose Boot to Recovery from the Power Menu - Restart in CROMi-X or from a 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 Back up of your current setup
4. Select install and navigate to where you saved your ROM zip file.
5. Choose the CROMi-Xenogensis zip file and follow the on screen prompts to customize your installation.
6. Reboot and enjoy.
About Fsync
Explanation by _that:
About the Experimental Features
During the install some features are listed as EXPERIMENTAL. I have left them as an option so you can play and enjoy debugging Please let me know if you used the experimental features like Extreme Tweaks, Cache2SD, Overvolting, Undervolting. if you want a stable smooth experience flash _that's kernel, with fsync disabled and one of the normal WW or US editions.
If you are a speed freak and don't mind the odd bug go for hunds with experimental tweaks, software rendering disabled and GPU OC, CPU OV and GPU UV.
Cache2SD is very experimental and may cause other issues so I'll leave that one up to you
Please hit Thanks and Rate the thread 5 Stars
Care to support the development of this and future ROMS? Please click the Donate to Me button on the left side of the screen under my user name
Add Ons
CROMi-X Add Ons
Kernel & Tweaks Installer - DOWNLOAD
Kernel & Tweaks Installer v5.2 - Updated Jan 06, 2014
For those who want to switch Kernels quickly, enable data2sd, rom2sd, cache2sd, change DPI, change res, disable / enable fsync and other tweaks
Note for Data2SD and Rom2SD you must have the correct ext partitions on your external sd card. See instructions here
Kernels:
TF700T : ASUS 10.6.1.27.5 Stock Kernel by sbdags
TF700T : _that 10.6.1.14.8 Modded Stock Kernel v4 Data2SD Compatible, Row Scheduler, UV, CIFS, ISO9660 and Fsync Control. By _that
TF700T : _that 10.6.1.14.10 Over Clocked Modded Stock Kernel v7 Rom2SD, Data2SD Compatible, Row Scheduler, UV, CIFS, ISO9660 and Fsync Control. By _that
You will have 3 options for Kernel CPU Speeds, all with GPU at 650MHz:
1518 - Power Save 1GHz, Balanced 1.5GHz, Performance 1.8GHz
1315 - Power Save 1GHz, Balanced 1.3GHz, Performance 1.5GHz
1318 - Power Save 1GHz, Balanced 1.3GHz, Performance 1.8GHz
TF700T : Hunds 10.6.1.14.10 Modded Kernel v3.4.4 BETA - Rom2SD, Data2SD Compatible, Overclocked, UV, Multi Scheduler, Fsync Control, Tweak App by Hundsbuah
TF700T : Max 10.6.1.14.8 Linaro Kernel Reloaded v4 RC3 BETA - Overclocked with dynamic Fsync Control by maxrdlf95
TF300T/G/TF201/ME301 : ASUS 10.6.1.27.5 Stock Kernel By sbdags
TF300T/G/TF201/ME301 : _that 10.6.1.14.8 Modded Stock Kernel v4 Rom2SD, Data2SD Compatible, Row Scheduler, UV, CIFS, ISO9660 and Fsync Control. By _that
TF300T/G/TF201/ME301 : _that 10.6.1.14.10 Over Clocked Modded Stock Kernel v7 Rom2SD, Data2SD Compatible, Row Scheduler, UV, CIFS, ISO9660 and Fsync Control. By _that
TF300T : Hunds 10.6.1.8.4 Modded Kernel v11 - Data2SD Compatible, Overclocked, UV, Multi Scheduler, Fsync Control, Tweak App by Hundsbuah
TF201 : Hunds 10.6.1.8.4 Modded Kernel v3.3.2 - Data2SD Compatible, Overclocked, UV, Multi Scheduler, Fsync Control, Tweak App by Hundsbuah
TF300T/G/TF201/ME301 : Max 10.6.1.14.8 Linaro Kernel Reloaded v4 RC2 BETA - Overclocked with dynamic Fsync Control by maxrdlf95
TF201 : Max 10.6.1.14.8 Linaro Kernel Reloaded v4 RC3 BETA - Overclocked with dynamic Fsync Control by maxrdlf95
Tweaks:
Data2sd enabling / disabling (only works with _that's and hunds kernels)
DPI Change
Resolution Change (TF700 Only : 1920 x 1200 or 1280 x 800)
Fsync Disabled / Enabled
GPU rendering or CPU software rendering
CPU Over-Volt by 50mV
CPU Under-Volt by 50mV
GPU Under-Volt (hunds only)
Cache2SD (Experimental)
DOWNLOAD Kernel Installer v5.2 Mirror 1
DOWNLOAD Kernel Installer v5.2 Mirror 2
MD5: ae34db3e891f5b96c82a5f124ddf6dc8
==================================================================================================
Various Kernel Benchmarks
Right benchmarks with various kernel options:
All were taken on CROMi-X 5.1 Odex with default options at 240dpi unless otherwise stated (fsync off / on). I've used quadrant as most people understand the results - I know it's not the best and I did 3 tests each time and took the 3rd result.
Stock - fsync on - 5672
_that v4 - fsync off - 5981
_that v4 - fsync on + data2sd - 5745
_thatv5 - fsync on - 6267
_that v5 - fsync off - 6414
_that v5 - fsync on + data2sd - 6143
Hunds + ET - fsync on - 6684
Hunds + ET - fsync off - 7245
Hunds + ET - fsync on + data2sd - 6725
Hunds - fsync off - 6805
Hunds - fsync on +data2sd - 6597
So data2sd doesn't really offer that much if you keep fsync on. It does feel faster when loading large games and files. The issue is it is a bit more unstable and easier to corrupt the data partition if you have fsync off. Same risk with normal data I suppose but less likely to corrupt due to less sponteneous reboots.
Is data2sd worth it? Only if you want to use your tablet whilst downloading large files or play store updates or you are prone to corruption with fsync off. Otherwise you can achieve at least the same speed with fsync off although with a risk to corrupt your data partition eventually.
==================================================================================================
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 CROMi-X but this time choose the ROM2SD option (currently option 3 on the kernel page)
==================================================================================================
miniCROMi-X ROM - Lite version of CROMi-X with ROM2SD support
Now has it's own thread here
==================================================================================================
CROMi-X Compatible Themes
pjc21’s Color Theme Mod
dan_joegibbsfan's DarkHorse Millennium Theme
Warhead_KAI's FlatDesignL Theme
==================================================================================================
TF701T Wallpapers
Extracted straight from the Asus Stock Rom and resized for our device. Extract to microsd and set wallpaper using gallery app
Download Mirror 1
Download Mirror 2
Download Mirror 3
Cromi Control v1.0.2 Changelog 10-6-13:
CROMI CONTROL:
- Better kill option
- Cromi control remembers settings on launch
ROM FEATURES:
- Dock browser button any browser
- No safe media warning
****HOW TO UPDATE****
1. Download and place on sd card of choice.
2. Reboot to recovery
3. Flash update zip
4. Wipe caches (cache/dalvik cache)
5. Fix permissions
6. Reboot, click thanks enjoy and give me more feature requests options
DOWNLOAD
Yeeeeeeee! So stoked. Thanks man, for all the work you continue to do for us.
Sent from my DROID RAZR using Tapatalk 4
Good job as usual sbdags!!
Thanks
elesbb said:
reserverd for CROMI Control updaets and features
Click to expand...
Click to collapse
Would it be possible to add a touch sensitivity setting into CROMI Control?
---
Awesome work gents! I can't wait to flash!!
Awesome work ! Thanks in advance to you all! Starting download and testing
sgkla said:
Would it be possible to add a touch sensitivity setting into CROMI Control?
---
Awesome work gents! I can't wait to flash!!
Click to expand...
Click to collapse
You could go to your build.prop and change it from there if you want... However, if we can access from the cromi control, it would be a lot better..
18G921858U986341Y - great work again...and again...and again... Thank you.
Many thanks to paulsaz, MicAlter, tijsva, gts9999 and jaredmorgs who have all donated towards CROMi-X 5.0 in the last few days! Thank you so much guys! It means a lot and it's great to have your support. :good::good::good:
My first flash attempt failed. I downloaded from a different mirror and everything went fine. Upon reboot I had a persistent nova launcher fail. I was going to uninstall then reinstall nova launcher but it is installed is a system app. This probably a conflict the two versions of nova launcher. I'm going to reflash and opt out of nova launcher.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
I have been waiting patiently for this awesome development! Thank you sbdags!
Sent from my SPH-D710 using Tapatalk 2
Reflashed without nova. Installed from store. No issues with that anymore.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Perfect!!
Enviado desde mi Nexus 4 usando Tapatalk 2
Guys curiosity question. Is there a plan for Asus to provide a 4.3 android release? If not could this be an interesting and possible upgrade provided in CromiX 6 for ex?
Will test this new version!
Envoyé depuis mon ASUS Transformer Pad TF700T en utilisant Tapatalk 4
duckredbeard said:
Reflashed without nova. Installed from store. No issues with that anymore.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
I did include the latest version of nova. How do they manage the pro version? Is it an additional file or a new apk? If the latter that might have caused the issue?
XabiX666 said:
Guys curiosity question. Is there a plan for Asus to provide a 4.3 android release? If not could this be an interesting and possible upgrade provided in CromiX 6 for ex?
Will test this new version!
Envoyé depuis mon ASUS Transformer Pad TF700T en utilisant Tapatalk 4
Click to expand...
Click to collapse
They plan to release but who knows when? Maybe after the new infinity pad comes out in Sep/Oct?
For data2sd is it working directly from the installer, or there is a need to follow also the data2sd thread and partioning of the SD card.
Do we lose anything on the card itself by trying this option?
Merci
Envoyé depuis mon ASUS Transformer Pad TF700T en utilisant Tapatalk 4
---------- Post added at 01:04 AM ---------- Previous post was at 01:00 AM ----------
I did include the latest version of nova. How do they manage the pro version? Is it an additional file or a new apk? If the latter that might have caused the issue?
What is the advantage to take the app within the installer vs installing it from the store. Is it to have the pro version without paying for it? Otherwise it seems better to go through the store to avoid conflicts right?
Envoyé depuis mon ASUS Transformer Pad TF700T en utilisant Tapatalk 4
XabiX666 said:
For data2sd is it working directly from the installer, or there is a need to follow also the data2sd thread and partioning of the SD card.
Do we lose anything on the card itself by trying this option?
Merci
Envoyé depuis mon ASUS Transformer Pad TF700T en utilisant Tapatalk 4
Click to expand...
Click to collapse
You need to follow the data2sd thread instructions to partition the card in gparted. You will lose all your current data although it is still there technically as now the tab sees an empty data partition so you will have to set up from scratch again.
I will have to try this ROM loved the cromi Roms of the past but moved on to the 4.3 Roms as of lately
Sent from my SGH-I337M using XDA Premium HD app
[ROM]●●[TF700T][miniCROMi-X 2.0.1][JB 4.2.1 | OC | OV | DEODEX 10.6.1.27.5][FEB 14]●●
miniCROMi-X ROM - Lite version of CROMi-X with ROM2SD support
{
"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"
}
Changelog
miniCROMi-X v2.0.1 - Released 14/02/2014
o Fixed installer script not waiting for /system to become available before attempting to mount
o Updated Super User to version 1.93
o Updated Google Core Services to latest version
miniCROMi-X v2.0 - Released 30/01/2014
o Updated Framework-res to version that doesn't need cromi-control installed.
o Recompiled framework-res.apk with TF701T default wallpaper. Goodbye Asus Tree
o Reverted services.jar and framework.jar to pre cromi-control versions
o Removed cromi-control
o Modded SystemUI.apk and Transformer.apk to remove sd card and dock notifications
o Updated LMK's Extreme Tweaks to version 1.6
o Updated LMK's init.cardhu.rc for ROM2SD compatibilty for better kernel integration
o Modified MiniC Launcher to 3 screens, new default wallpaper, 9x6 icons on 4.2 and removed screen indicators
o Updated Superuser and binary to latest version 1.91
o Moved Flash Player to /data/app
o Updated Google Play services and keyboard to latest versions
o Fixed Google Keyboard not defaulting on clean install when Asus keyboard is not installed
o Updated Hosts file
o Zip Aligned all system apks
o Changed Bootanimation to TF701T Stock
Click to expand...
Click to collapse
Old Versions:
Code:
[B]miniCROMi-X v1.3 - Released 01/12/2013[/B]
o Updated LetMeKnow's tweaks to v1.3
o Updated SuperUser and Binary to version 1.80
o Updated Google Play Services to latest version
o Updated Google Keyboard to latest version
o Updated Normal install so it doesn't install ROM2SD compatibility anymore
[B]miniCROMi-X v1.2a - Released 15/11/2013[/B]
o Fixed missing popup search bar when holding on text in v1.2a
o Applied LetMeKnow's power saving build.prop edit to assist fixing WiFi slowing down
o Fixed the missing Settings Status which was cauing force closes
o Removed facelock app, lib and face detection models from ROM
o Removed blocklayoutdriver.ko as not used
o Removed libereader.so as no Asus Reader app included
o Fixed keyboard permissions
o Updated SuperUser and SU binary to version 1.69
Created Patch for Asus Keyboard which fixes dock layout for non-US models
B]miniCROMi-X v1.1 - Released 10/11/2013[/B]
o Name changed to miniCROMi-X or miniC for short ;)
o Calendar sync adapter added to allow Google Calendar to sync properly
o Updated Google Play Services to version 4.0.31
o Updated Google Keyboard to version 2.0.18933.905102a
o Removed GoogleBackupTransport.apk, GoogleFeedback.apk
o Added Keyboard.apk back in for Dock compatibility
[B]CROMini-X v1.0 - Released 04/11/2013[/B]
o Name changed to CROMini-X
o Aroma-less - normal installer - no options - 2 versions - normal and rom2sd
o Massively debloated ROM. Half the size of CROMi-X. Most Google and Asus Apps removed - should have 500MB free RAM on boot
o ROM2SD compatible. You need 2 Ext4 partitions on your MicroSD for it to work. Thanks to _that
o CROMi-X Extreme tweaks and CROMI-CONTROL app installed by default
o Applied LMK's ET 1.1, hotplug interface set to 0,0,0. Quadrant on perf should be around 7000 and stable
o Updated Hunds app to version 2.4
o Added newer implementation of BusyBox that has better compatibility from trickster mod site
o Removed email widget and task manager widget
o Removed all wallpapers from Launcher apart form TF701T default - now only 5mb :)
o Resized Google Boot Animation
o You can install most add on apps from the store and use titanium backup to move to /system if you wish :) Or just install CROMi-X ;)
Credits to _that & Hundsbuah for the kernel and LetMeKnow for the kernel tweaks and elesbb for CROMi-Control
Remember you must have a fast microSD card formatted with a fat32, ext4 for /data and ext4 for /system in GPARTED for Rom2sd.
1. You need a fast microsd card - preferably at least a 16GB Class 10 - UHS-1 card like a sandisk or Samsung with a read speed of over 20MB/s
2. You need to use Linux or how I did it a GParted ISO on a Bootable USB Stick on a PC
3. In GParted set up your micro sd with 3 partitions all primary (no logical) in this order FAT32, EXT4, EXT4
They will be used as SDCARD, /data, /system in that order so I recommend the following sizes for a 16GB sdcard; 4GB for SDCard, 11GB for /data and 1GB for system or thereabouts.
If you used a 32GB or 64GB card then increase the SDCard and /data partitions as you see fit (I went with 16GB, 47GB and 1GB on my 64GB card)
4. The ROM now flashes the correct preinit script files to your normal system setup so as long as you have a _that or hunds based kernel it will detect your ROM2SD automatically
5. Install the ROM2SD version and let it finish. Let it reboot.
6. You should be presented with a clean install setup wizard when it boots if it has worked. If it hasn't worked you will be back at your previous CROMi-X/miniC installation launcher.
7. Job done - set up your ROM2SD however you like - it can't interfere with your normal setup
8. You will notice 2 folders on root - datai and sdcardi - these allow you to see your internal /datai and sdcardi partitions if you wish to copy files over
9. As long as the SDCard is inserted you will boot to ROM2SD, remove it (not whilst in android unless you want to crash) and on that boot you will switch back to your normal miniC or CROMi-X if you installed that to SD.
DOWNLOADS
miniC Normal Download
miniCROMi-X DEODEX v2.0.1_Signed.zip - 230 MB - Mirror 1
miniCROMi-X DEODEX v2.0.1_Signed.zip - 230 MB - Mirror 2
md5: 2362a85541f1ac6adc448397b26e1bf2
miniC Rom2SD Download
miniCROMi-X DEODEX v2.0.1_ROM2SD_Signed.zip - 230 MB - Mirror 1
miniCROMi-X DEODEX v2.0.1_ROM2SD_Signed.zip - 230 MB - Mirror 2
md5: 957a38f97109a2243756b473db3f924e
For those of you missing the dock layouts for your language please flash this patch. It will install the necessary files so you can set the dock language in the Asus Keyboard which dictates what the dock should use
Download Asus Keyboard Patch
md5: bee82d0e73ac0d5b2185417fa416e0a9
Use this patch if you want to remove the google keyboard.
Download Google Keyboard Removal Patch
md5: efcc6216af60feb7cba8dfab72daeac8
If you want to backup and restore to your ROM2SD setup flash the following file first in TWRP as it shifts TWRP to see the microsd as internal. Flash it again to return back to internal. All credits to _that for that
ROM2SD1.zip - 144 KB - Mirror 1
md5: 7b699136d59ea3d5538570ccaf422acf
XDA:DevDB Information
miniCROMi-X, a ROM for the Asus Transformer TF700
Contributors
sbdags, LetMeKnow, hundsbuah elesbb, pjc21, _that, flumpster
ROM OS Version: 4.2.x Jelly Bean
ROM Kernel: Linux 3.1.x
ROM Firmware Required: Bootloader 10.6.1.x version compatible
Based On: Asus Source
Version Information
Status: Stable
Current Stable Version: 2.0.1
Stable Release Date: 2014-01-30
Previous Version: 2.0
Previous Release Date: 2013-01-30
Created 2013-11-10
Last Updated 2014-02-14
miniC Addons
miniCROMi-X Add Ons
Kernel & Tweaks Installer - DOWNLOAD
Kernel & Tweaks Installer v5.2 - Updated Jan 06, 2014
For those who want to switch Kernels quickly, enable data2sd, rom2sd, cache2sd, change DPI, change res, disable / enable fsync and other tweaks
Note for Data2SD and Rom2SD you must have the correct ext partitions on your external sd card. See instructions here
Kernels:
TF700T : ASUS 10.6.1.27.5 Stock Kernel by sbdags
TF700T : _that 10.6.1.14.8 Modded Stock Kernel v4 Data2SD Compatible, Row Scheduler, UV, CIFS, ISO9660 and Fsync Control. By _that
TF700T : _that 10.6.1.14.10 Over Clocked Modded Stock Kernel v7 Rom2SD, Data2SD Compatible, Row Scheduler, UV, CIFS, ISO9660 and Fsync Control. By _that
You will have 3 options for Kernel CPU Speeds, all with GPU at 650MHz:
1518 - Power Save 1GHz, Balanced 1.5GHz, Performance 1.8GHz
1315 - Power Save 1GHz, Balanced 1.3GHz, Performance 1.5GHz
1318 - Power Save 1GHz, Balanced 1.3GHz, Performance 1.8GHz
TF700T : Hunds 10.6.1.14.10 Modded Kernel v3.4.4 BETA - Rom2SD, Data2SD Compatible, Overclocked, UV, Multi Scheduler, Fsync Control, Tweak App by Hundsbuah
TF700T : Max 10.6.1.14.8 Linaro Kernel Reloaded v4 RC3 BETA - Overclocked with dynamic Fsync Control by maxrdlf95
TF300T/G/TF201/ME301 : ASUS 10.6.1.27.5 Stock Kernel By sbdags
TF300T/G/TF201/ME301 : _that 10.6.1.14.8 Modded Stock Kernel v4 Rom2SD, Data2SD Compatible, Row Scheduler, UV, CIFS, ISO9660 and Fsync Control. By _that
TF300T/G/TF201/ME301 : _that 10.6.1.14.10 Over Clocked Modded Stock Kernel v7 Rom2SD, Data2SD Compatible, Row Scheduler, UV, CIFS, ISO9660 and Fsync Control. By _that
TF300T : Hunds 10.6.1.8.4 Modded Kernel v11 - Data2SD Compatible, Overclocked, UV, Multi Scheduler, Fsync Control, Tweak App by Hundsbuah
TF201 : Hunds 10.6.1.8.4 Modded Kernel v3.3.2 - Data2SD Compatible, Overclocked, UV, Multi Scheduler, Fsync Control, Tweak App by Hundsbuah
TF300T/G/TF201/ME301 : Max 10.6.1.14.8 Linaro Kernel Reloaded v4 RC2 BETA - Overclocked with dynamic Fsync Control by maxrdlf95
TF201 : Max 10.6.1.14.8 Linaro Kernel Reloaded v4 RC3 BETA - Overclocked with dynamic Fsync Control by maxrdlf95
Tweaks:
Data2sd enabling / disabling (only works with _that's and hunds kernels)
DPI Change
Resolution Change (TF700 Only : 1920 x 1200 or 1280 x 800)
Fsync Disabled / Enabled
GPU rendering or CPU software rendering
CPU Over-Volt by 50mV
CPU Under-Volt by 50mV
GPU Under-Volt (hunds only)
Cache2SD (Experimental)
DOWNLOAD Kernel Installer v5.2 Mirror 1
DOWNLOAD Kernel Installer v5.2 Mirror 2
MD5: ae34db3e891f5b96c82a5f124ddf6dc8
==================================================================================================
Various Kernel Benchmarks
Right benchmarks with various kernel options:
All were taken on CROMi-X 5.1 Odex with default options at 240dpi unless otherwise stated (fsync off / on). I've used quadrant as most people understand the results - I know it's not the best and I did 3 tests each time and took the 3rd result.
Stock - fsync on - 5672
_that v4 - fsync off - 5981
_that v4 - fsync on + data2sd - 5745
_thatv5 - fsync on - 6267
_that v5 - fsync off - 6414
_that v5 - fsync on + data2sd - 6143
Hunds + ET - fsync on - 6684
Hunds + ET - fsync off - 7245
Hunds + ET - fsync on + data2sd - 6725
Hunds - fsync off - 6805
Hunds - fsync on +data2sd - 6597
So data2sd doesn't really offer that much if you keep fsync on. It does feel faster when loading large games and files. The issue is it is a bit more unstable and easier to corrupt the data partition if you have fsync off. Same risk with normal data I suppose but less likely to corrupt due to less sponteneous reboots.
Is data2sd worth it? Only if you want to use your tablet whilst downloading large files or play store updates or you are prone to corruption with fsync off. Otherwise you can achieve at least the same speed with fsync off although with a risk to corrupt your data partition eventually.
Uh,uh! First one! :cyclops:
Let's set an example: Transaction ID #7FL985280X445515J
Thanks Darren!
berndblb said:
Uh,uh! First one! :cyclops:
Let's set an example: Transaction ID #7FL985280X445515J
Thanks Darren!
Click to expand...
Click to collapse
Bernd! Many thanks for the first donation of miniCROMi-X.
sbdags said:
Bernd! Many thanks for the first donation of miniCROMi-X.
Click to expand...
Click to collapse
You're more than welcome!
But could I trouble you for more detailed instructions for thick headed noobs like me on the ROM2SD installation?
I'm good until point 5), but then....
How's the hell do you install mini-X to the microSD?
I understand that once installed on a microSD with the correct partitions the kernel (??) will auto-detect it and boot into the rom installed on the card.
But how do you install? Boot into TWRP with miniCROMi-X on the fat32 partition of the card and just install from there?
I have to admit, it's late and I'm lazy. Just got finished with a clean install of 5.1.2 (which btw is super smooooth so far) and would hate to flash over that if I'm wrong.
berndblb said:
You're more than welcome!
But could I trouble you for more detailed instructions for thick headed noobs like me on the ROM2SD installation?
I'm good until point 5), but then....
How's the hell do you install mini-X to the microSD?
I understand that once installed on a microSD with the correct partitions the kernel (??) will auto-detect it and boot into the rom installed on the card.
But how do you install? Boot into TWRP with miniCROMi-X on the fat32 partition of the card and just install from there?
I have to admit, it's late and I'm lazy. Just got finished with a clean install of 5.1.2 (which btw is super smooooth so far) and would hate to flash over that if I'm wrong.
Click to expand...
Click to collapse
I'm going to get a full guide written mate on how to get the parted iso create a bootable usb and then use it Give me a few days
Also we have an alternative method for ROM2SD from _that that may make it even easier to install
I just tried to install, minicromi -and after twrp installed it, it didn't go into setup... just said reboot. At that point it would simply stick in a boot loop. Tried to reinstall boot loader and will retry. Really want to put all on my new SD card to speed this baby up
Sent from my VS980 4G using Tapatalk
success!
Update: I can avoid the reboots if I pop out my SD card. So. Just installed mini, now will go back to twrp and pop in SD card (partitioned), and try to install rom2sd
Sent from my VS980 4G using Tap a talk
Keep in mind im a beginner!
Few words of advise:
1) I ended up using new cromi 5.1.2
2) you must install twice!!! first without the sd card (i had mine in and it caused problems)- and choose option to set up rom2sd
3) start device- then reboot again into twrp bootloader- and reinstall rom but choose rom2sd now---(now insert sd card!)
first time it crashed after rom2sd- but second time (switched to hunds) and boom...its a miracle...device is awesome!!!
side note- i DID use the micro explorer windows partition tool many said "doesnt work well"- had windows 8 device- worked like a charm.
worth the late night figuring this out.
sdbags- how can i donate! you are the man
Jeffruby said:
Few words of advise:
1) I ended up using new cromi 5.1.2
2) you must install twice!!! first without the sd card (i had mine in and it caused problems)- and choose option to set up rom2sd
3) start device- then reboot again into twrp bootloader- and reinstall rom but choose rom2sd now---(now insert sd card!)
first time it crashed after rom2sd- but second time (switched to hunds) and boom...its a miracle...device is awesome!!!
side note- i DID use the micro explorer windows partition tool many said "doesnt work well"- had windows 8 device- worked like a charm.
worth the late night figuring this out.
Click to expand...
Click to collapse
I've been having a somewhat similar problem. I now tried your version, but I still end up with it upgrading the 87 apps, then it forever stalls at Android is upgrading... with the subtext Starting apps. I've installed it like 10 times, this last 2 times using your method (_that's OC then Hunds), no difference no matter what I try :crying:
It works fine without the card and the Rom2SD compatible option install. During second round Installed 5.1.2 both from internal memory with popping in the card midway, as you wrote and also from the card itself, left in, obviously.
When you make the partitions on the microSD card, do you give it a label or flag. I do neither. I'm at my wit's end... and wife's starting to get pissed off that I'm spending all day on this - again!
Adso3000 said:
I've been having a somewhat similar problem. I now tried your version, but I still end up with it upgrading the 87 apps, then it forever stalls at Android is upgrading... with the subtext Starting apps. I've installed it like 10 times, this last 2 times using your method (_that's OC then Hunds), no difference no matter what I try :crying:
It works fine without the card and the Rom2SD compatible option install. During second round Installed 5.1.2 both from internal memory with popping in the card midway, as you wrote and also from the card itself, left in, obviously.
When you make the partitions on the microSD card, do you give it a label or flag. I do neither. I'm at my wit's end... and wife's starting to get pissed off that I'm spending all day on this - again!
Click to expand...
Click to collapse
I don't understand what problems you guys are having, I have installed this 20 times plus and it works fine every time.
I gave my partitions labels - not sure if it matters.
So you have fat32, ext4 and ext4
You install the rom and you have two choices:
1. You install it without the ROM2SD compatibility and without ROM2SD as you only care about internal. (If you install it with ROM2SD compatibility it is going to try and boot from the SD card but you currently have nothing installed so it will never work - this will force you to have to boot with the card out)
2. You install the ROM2SD (this automatically forces compatibility to internal as well - maybe this is the confusion?). As long as the card is in it will boot to ROM2Sd but only as long as you have CROM-X or miniCROMi-X on internal.....
The only time you need to choose ROM2SD compatibility is when you already have a working rom on sd and you are upgrading internal.
Does that make sense?
So what you meant was:
1) Install it first the good old fashioned way choosing normal mode and let it boot and finish setup.
2) Then do the exact same thing again, only this time with the install Rom2SD option instead of the “normal” option.
Is that correct?
4. You must have already installed CROMi-X with ROM2SD compatibility selected from the installer and have it working - dirty or clean will work.
5. Install the ROM2SD version and let it finish. Let it reboot.
That part 4 sounds like my point 1 but with the compatibility option instead which you say don't work, hence the confusion.
I install two different boot animations so I can see where it's booting from. My point 1 is done and all good. Then I did point 2 and just like before it starts just fine, but then ends up stuck at the “Android is upgrading... Starting app.” screen and it never finishes. Last night I just did that too and this morning it was dead and out of battery (started with a full charge).
I'm dying to know what labels you gave your 3 partitions respectively. Since you didn't mention flags, I'm guessing you didn't flag one as boot for instance. This would be a really quick to change and see it that is where the dog lies burried.
Thanks for your quick reply btw. Mine a bit late as I just had to try out your suggestions.
Adso3000 said:
So what you meant was:
1) Install it first the good old fashioned way choosing normal mode and let it boot and finish setup.
2) Then do the exact same thing again, only this time with the install Rom2SD option instead of the “normal” option.
Is that correct?
4. You must have already installed CROMi-X with ROM2SD compatibility selected from the installer and have it working - dirty or clean will work.
5. Install the ROM2SD version and let it finish. Let it reboot.
That part 4 sounds like my point 1 but with the compatibility option instead which you say don't work, hence the confusion.
I install two different boot animations so I can see where it's booting from. My point 1 is done and all good. Then I did point 2 and just like before it starts just fine, but then ends up stuck at the “Android is upgrading... Starting app.” screen and it never finishes. Last night I just did that too and this morning it was dead and out of battery (started with a full charge).
I'm dying to know what labels you gave your 3 partitions respectively. Since you didn't mention flags, I'm guessing you didn't flag one as boot for instance. This would be a really quick to change and see it that is where the dog lies burried.
Thanks for your quick reply btw. Mine a bit late as I just had to try out your suggestions.
Click to expand...
Click to collapse
Yes 1 and 2 are how I normally flash it. In fact I just did it again tonight and it worked fine.
4 and 5 (what happened to 3? ) will also work.
I'll think about the installer next time to make it a bit more obvious.
You don't need to flag anything - only primary partitions. Don't need to set boot flag.
I labelled mine like this:
FAT32 : STORAGE
EXT4 : SD-EXT
EXT4 : SYSTEM
But you could label them whatever you want.....
Stuck @ "Apps upgrading..." SOLVED!
sbdags said:
Yes 1 and 2 are how I normally flash it. In fact I just did it again tonight and it worked fine.
4 and 5 (what happened to 3? ) will also work.
I'll think about the installer next time to make it a bit more obvious.
You don't need to flag anything - only primary partitions. Don't need to set boot flag.
I labelled mine like this:
FAT32 : STORAGE
EXT4 : SD-EXT
EXT4 : SYSTEM
But you could label them whatever you want.....
Click to expand...
Click to collapse
Not too sure about that just label them whatever part though.
Originally (yesterday) I had it named it Partion 1, Partition 2 and Partition 3. Then today I removed the labels entirely and it still acted funny. Just now I popped in the card, ran GParted and noticed the 3rd partition was given the label SYSTEM during the previous non-functional installation, but the first 2 still had no label. My problem was the apps loading. I noticed the installation seemed longer and don't remember it saying: Optimizing SD-EXT or something to that effect, "installing Dropbox, installling Titanium" etc at the end of all that quickly passing text when I ran the Rom2SD install previously, but I'm so tired right now it might be something I'm just imagining.
All I can say now is that just the fact that I named them exactly like you named yours it now works brilliantly :highfive: and that "apps starting" part took a only a few seconds. It seems the installation, in my case at least, can't figure out that it needs to install the apps to 2nd partition without the label SD-EXT or more likely given the timing of failure, it just fails to load them from said partition.
To anyone reading this, just name your partitions like sbdags does, just to be on the safe side and you're likely naming them anyway, or if not, then it is 1 minute well spent.
I've wiped, installed, booted, setup, etc. on the wrong side of 20 times since yesterday morning and I'm almost in disbelief that it's actually working all of a sudden :victory: and so late that it's now bedtime and I'll have to wait till tomorrow to take the damn thing flyin'
Thanks dude
It's all the good people at xda like yourself that I think of and mention to friends and family as a shining example of hope for the future for the human race when experiencing or hearing about all the ****ty sides of human behaviour from crime to corrupt politicians, terrorists, bigots and just general lack of helpfulness and a willing spirit. It brings me a sense of hope :angel: I've grown quite cynical over the years, but xda is one of the things that keep me from becoming like the old dude in the animated movie Up. :silly:
When Asus (or Samsung etc.) lets you fall, it's comforting to know there's almost always someone here at xda to catch you before you hit the ground.
Good luck and good night fellow Gadgeteers!
I finished just in time to cuddle a bit with the missus before she falls asleep to try to make up for all the time I've been knee-deep in **** with my head stuck between the screen and the keyboard during any free-time in the last two days. :silly:
Adso3000 said:
Not too sure about that just label them whatever part though.
Originally (yesterday) I had it named it Partion 1, Partition 2 and Partition 3. Then today I removed the labels entirely and it still acted funny. Just now I popped in the card, ran GParted and noticed the 3rd partition was given the label SYSTEM during the previous non-functional installation, but the first 2 still had no label. My problem was the apps loading. I noticed the installation seemed longer and don't remember it saying: Optimizing SD-EXT or something to that effect, "installing Dropbox, installling Titanium" etc at the end of all that quickly passing text when I ran the Rom2SD install previously, but I'm so tired right now it might be something I'm just imagining.
All I can say now is that just the fact that I named them exactly like you named yours it now works brilliantly :highfive: and that "apps starting" part took a only a few seconds. It seems the installation, in my case at least, can't figure out that it needs to install the apps to 2nd partition without the label SD-EXT or more likely given the timing of failure, it just fails to load them from said partition.
To anyone reading this, just name your partitions like sbdags does, just to be on the safe side and you're likely naming them anyway, or if not, then it is 1 minute well spent.
I've wiped, installed, booted, setup, etc. on the wrong side of 20 times since yesterday morning and I'm almost in disbelief that it's actually working all of a sudden :victory: and so late that it's now bedtime and I'll have to wait till tomorrow to take the damn thing flyin'
Thanks dude
It's all the good people at xda like yourself that I think of and mention to friends and family as a shining example of hope for the future for the human race when experiencing or hearing about all the ****ty sides of human behaviour from crime to corrupt politicians, terrorists, bigots and just general lack of helpfulness and a willing spirit. It brings me a sense of hope :angel: I've grown quite cynical over the years, but xda is one of the things that keep me from becoming like the old dude in the animated movie Up. :silly:
When Asus (or Samsung etc.) lets you fall, it's comforting to know there's almost always someone here at xda to catch you before you hit the ground.
Good luck and good night fellow Gadgeteers!
I finished just in time to cuddle a bit with the missus before she falls asleep to try to make up for all the time I've been knee-deep in **** with my head stuck between the screen and the keyboard during any free-time in the last two days. :silly:
Click to expand...
Click to collapse
Wow thanks for the kind words! :good: Hmmm.... not sure why labelling them works - I just called them whatever popped into my head......
sbdags said:
not sure why labelling them works - I just called them whatever popped into my head......
Click to expand...
Click to collapse
I didn't label my partitions at all and it worked...
For those of you missing the dock layouts for your language please flash this patch. It will install the necessary files so you can set the dock language in the Asus Keyboard which dictates what the dock should use
Download Asus Keyboard Patch
md5: bee82d0e73ac0d5b2185417fa416e0a9
Use this patch if you want to remove the google keyboard.
Download Google Keyboard Removal Patch
md5: f9a5ad7acbd47b737db2c54e849ee6b8
Seems to be working fine and smooth. Not sure if Browser2Ram is already implemented as standard?
How much screentime is people getting? Seems like the battery drain is bigger, but I have to give more charge cycles before I jump to conclusions.
Great work!
Ali I Hagen said:
Seems to be working fine and smooth. Not sure if Browser2Ram is already implemented as standard?
How much screentime is people getting? Seems like the battery drain is bigger, but I have to give more charge cycles before I jump to conclusions.
Great work!
Click to expand...
Click to collapse
Yes b2r is implemented by default as are hunds kernel with extreme tweaks. This is why your battery life isn't great. This ROM is designed for the speed demons. It comes over clocked and over volted.
Search not working
Hi
I installed the rom yesterday and it's running great thanks! I am having one issue which I would like to be able to fix. When I select text by a long press on the screen the options show up to copy or search web but when I select search web it says Search Via - No apps can perform this action. Is there a app I can add that is missing to fix this?
Thanks
R.
rnormore said:
Hi
I installed the rom yesterday and it's running great thanks! I am having one issue which I would like to be able to fix. When I select text by a long press on the screen the options show up to copy or search web but when I select search web it says Search Via - No apps can perform this action. Is there a app I can add that is missing to fix this?
Thanks
R.
Click to expand...
Click to collapse
I'll have a look.
YOUR ONE STOP THREAD FOR ALL S4 I9505 ROM'S & TWEAKSTHE ULTIMATE BATTERY PROLONGING TWEAKS - MADE BY @SHADE5THE OP ALWAYS HAS LATEST UPDATES - THANKS TO @_BON_BON
Logo will be added back soon
LATEST ROM's & ESSENTIALS FOR I9505
1) AOSP 6.0 Marshmallow ROM by the JCD Team 14-03-2016
Optimized
2) Optimised CM 13 ROM built by the JDCTeam 25-05-2016
3) Resurrection ROM v5.6.8 built by @TJSteveMX 02-05-2016
4) Official TWRP Recovery v3.0.2-0 by the TeamWin 05-04-2016
5) GApp's of your choice (select ARM) (Updated daily!)
6) Dynamic Busybox Installer and updater script, by @_Bon_Bon
LATEST TWEAKS DOWNLOAD LINKS
1) Unofficial CM12.1 Alucard Kernel & sTweaks (flashable) 20-01-2016
All features may not work! This isn't officially supported on any other ROM than the OptimizedCM12.1!
2) Bon_Bon's "build.prop" tweaks 14-6-2015
3) Shade5's sTweaks Undervolt settings 14-6-2015
4) AntaresOne's Camera Crash Fix 19-6-2015
5) TrueStereo Mod by @FPSUsername (Also check his signature for a good balanced Alucard profile!)
6) XPOSED for Lollipop & Marshmallow (Official) by @Rovo89
LIST OF ALL GUIDES
1) How to make Any Rom Awesom-er RE-REVAMPED by @_Bon_Bon
2) S4 i9505 Undervolting Guide by @Shade5
3) AMOLED & Hardware tweaks Guide -by @Shade5
4) Camera tweaks guide - by @Shade5
5) Compilation of mods and useful scripts by @_Bon_Bon
6) sTweaks Kernel tweaking for everyday performance - by @Shade5
7) The_Thing I9505 PlugIn by @_Bon_Bon
8) Alucard's Kernel setting's by @Shade5
9) How to update your modem/bootloader by @_Bon_Bon
XDA:DevDB Information
S4 Awesome(er) SuperTweaks, Tool/Utility for the Samsung Galaxy S 4
Contributors
Shade5, _Bon_Bon
Version Information
Status: Stable
Created 2015-07-16
Last Updated 2016-06-01
This GUIDE is aimed at users who want to REDUCE HEATING/TEMPERATURE & get LONGER BATTERY LIFE on all versions of the RR ROM
(It wont affect your AnTuTu scores much & you will be able to use your phone for hours without your battery, phone or fingers burning up)
NOTE: My tweaks are related to HARDWARE (CPU, GPU, IO & Screen) & not the software's power consumption
PRINCIPLE OF TWEAKS: : [1] Undervolting the CPU - to draw less power & run cooler
All the below steps will only take about 5 minutes to complete (& another 5 minutes if you need to install the Kernel)
STEP 1 - Flash ALUCARD's Kernel V3.4.108 (if you haven't already done so) from here (Thank's to @_Bon_Bon for the latest Kernel & permission to use his work)
Boot into recovery & flash the Zip (just like you flashed your ROM) - you will not lose any data at all
__________________________________________________
STEP 2 (AUTO MODE)
If you wish to get ALL my Kernel Tweaks in ONE STEP simply download this file OR download the default.zip (you need to unzip it) attachment
Save it to the root of your INTERNAL MEMORY (see screenshot on where it should be - you may already have a file with the same name there - please delete it)
Now open sTweaks -> select the BACKUP OR RESTORE tab -> Press RESTORE NOW
Wait 30 seconds.....
Now REBOOT -> open STWEAKS -> CPU Voltage - click Check the CPU Voltage are same as below (to be sure the settings are active) :good:
ALTERNATIVELY:....... (Manual mode - so you are involved in what is happening )
Open the sTweaks app -> CPU Voltage Control & put ON the CPU VOLTAGE MAIN SWITCH
Now set voltages as below:
NOTE: (these are for a PVS2 & above chipset found in over 90% of i9505's)
IF you face any freezing+lines on screen (it is because of others tweaks/settings - please stick to just using my Kernel settings)
IF freezing still persists it means you have a PVS1 or PVS0 chip - simply add +25mV to each setting if that's the case
378 kHz 750000 uV
486 kHz 750000 uV
594 kHz 750000 uV
702 kHz 775000 uV
810 kHz 812500 uV
918 kHz 825000 uV
1026 kHz 850000 uV
1134 kHz 875000 uV
1242 kHz 887500 uV
1350 kHz 912500 uV
1458 kHz 950000 uV
1566 kHz 975000 uV
1674 kHz 1012500 uV
1782 kHz 1062500 uV
1890 kHz 1100000 uV
Now go to the GPU tab in sTweaks & put on the " GPU VOLTAGE MAIN SWITCH"
Set GPU voltages as below
Level 1 895000 uV
Level 2 1000000 uV
Level 3 1100000 uV
Now Click on the CPU page & ensure ENABLE ON BOOT (Load all settings on Boot) & below it press LOAD ALL
REBOOT -> open STWEAKS -> CPU Voltage - click Check CPU Voltage (to be sure your above voltage settings are active) :good:
DONE !
I've overworked my phone for >100 hours & done over 55 full CPU/GPU stress tests with multiple CPU & benchmark tools to give you these STABLE final results.
With Games + Downloads + Benchmarking + Other apps + CPU Monitoring was running the CPU reached just 62C (see it in the screenshot attached)
I also took 2 back-to-back comparative benchmarks using AnTuTu & got 27,000 (an overall drop of just 6% from the initial 29,000)
RAM performance increases (cooler & more efficient) while Runtime & 3D performance loses out a little but this won't affect you unless you are into hardcore gaming/too much multi-tasking (if so then please do not reduce the GPU voltages)
Do share your results & experience - Happy tweaking folks! :highfive: & don't forget to hit that THANKS:good: button
This guide is aimed at users who want to get LONGER BATTERY LIFE on all versions of the RR ROM
(It wont affect your AnTuTu scores & you will be able to use your phone for hours without your battery burning up)
NOTE: This only tweaks the HARDWARE (CPU, Screen, Vibrator) & not the software's power consumption
PRINCIPLE OF TWEAKS:
1) Exploiting the AMOLED screen - to display more black (pixels off) thus increase battery life
2) Adjusting simple accessible settings - to improve performance/battery
All the below steps will only take about 5 minutes to complete from you SETTINGS MENU
_____________________________________________
MOBILE NETWORKS -> Preferred 3G/2G (unless you really want 4G)
MORE -> NFC (Off)
CONFIGURATIONS -> MISCELLANEOUS -> Widgets/CLOCK widget Setting(increase update freq) , Vibrator Intensity (40%)
CONFIGURATIONS -> BUTTONS -> Navigation Bar Buttons (OFF if using Hardware keys)
CONFIGURATIONS-> HARDWARE KEYS (Enable if BUTTONS is OFF) -> Backlight (Enable for 1 second)
THEMES -> Install "Nicholas' Blacked Out" theme & Also "Pitch Black" wallpaper (from PLAY STORE)
DISPLAY -> Adaptive Brightness (ON) , Sleep (15s or 30s) , Daydream (OFF) , Ambient Display (ON)
SOUND & NOTIFICATION -> Other Sounds -> Touch Sounds (OFF), Vibrate on touch (OFF), Vibrate (OFF)
DEVELOPER OPTIONS -> Window Animation Scale (1 or OFF), Transition Animation Scale (1 or OFF), Animator duration scale (1 or OFF)
SUPER SU# -> Settings -> Enable Su during boot (ON)
DONE !!! :good::good:
Screenshot's attached!
Don't forget to hit THANKS if I helped. :good::fingers-crossed:
p.s : This also works on other ROM's where you have similar settings that you can toggle/edit
.
How to make Any Rom Awesome-er
RE-REVAMPED
INDEX:
1. Before ROM Install
2. After ROM Install
3. Recommended and useful Apps
4. Themes and personalization
All the download links can be found from the thread OP
A SAFE Odin version can be downloaded from this thread
Thanks to the developer!
1. Before ROM Install
Updating your Modem and Bootloader
I’ve already made a guide on how, why and where to download your Modem and bootloader files, so go check it out here
I’ve also made an up-to date thread with links to latest modems and bootloaders, here
Installing / Upgrading your recovery
Download and flash Official TWRP recovery 3.0.0
All TWRP recovery downloads for the JFLTEXX
Code:
[B] Features: [/B]
- It has touch screen support, for added convenience
- Works with all ROM installers
- Can be used to flash .zip and .img files
- Has added support for F2FS filesystems
- Has a beautiful UI
- It’s still being updated!
[B] How to install: [/B]
[B] If you already have TWRP v2.8.4 or higher installed: [/B]
1. Download and Unzip the TWRP-XXX-F2FS.tar.md5
2. Take out the recovery.img file and place it somewhere inside your phone
3. Boot into TWRP recovery
4. Go to Install -> Find and click the ‘Images...’ button
5. Browse to the image that you downloaded and select it
6. Choose recovery and swipe to flash
7. Done!
[B] If you have stock / other recovery installed: [/B]
1. Download Odin from the link above
2. Unzip the file you downloaded and open Odin3.exe
3. Power off your device completely
4. Turn on your device by pressing volume-up and the power buttons
5. Attach the device to your computer via a USB cable
6. Make sure Odin detects your device and click the AP button
7. Browse to and select the tar file that you downloaded and start the flash
8. Done!
Then boot into recovery if not already there
Converting / formatting filesystems to F2FS
Formatting filesystems as F2FS is suggested, if your ROM / Kernel supports it
This is done to improve speed and storage lifespan.
Code:
Filesystems that | Which
you can convert | Method
------------------------------------------------------
/cache | Format
/data | Format / Restore
/sdcard | Format
/system | Restore
/preload | Format
-------------------------------------------------------
EXT4 on /system is actually faster than F2FS, because it's a read only partition.
So, if you don't mess around with /system on a regular basis, converting it is not necessary.
Code:
[B] Converting filesystems through formatting: [/B]
1. Go to Wipe -> Advanced Wipe
2. Click the checkbox for the desired partition
3. Click Repair or Change File System
4. Now you can see the current filesystem format, if it’s already F2FS, can skip to step 6
5. Click ‘Change File System’ -> choose F2FS and swipe to change
6. Done!
[B] Converting filesystems through restoring a backup: [/B]
1. Go to Backup and choose the partition(s) you want to convert and back them up
2. Go to Wipe -> Advanced Wipe
3. Click the checkbox for the desired partition
4. Click Repair or Change File System
5. Now you can see the current filesystem format, if it’s already F2FS, can skip to step 10
6. Click ‘Change File System’ -> choose F2FS and swipe to change
7. Go to Settings and check: ”Use rm -rf instead of formatting”
8. Go to Restore and select the backup you made earlier
9. Restore the partition you converted to F2FS from that backup
10. Repeat above steps for all partitions you desire to convert / backed-up
11. Done!
Flash-able tweaks and mods
If you haven’t flashed your ROM and GAPPs yet, now is the time to do so
If the ROM doesn’t have a suggested GAPPs, choose Open GAPPs from the OP
List of MODs and tweaks you can Install:
Code:
1. [URL="http://forum.xda-developers.com/galaxy-s4/unified-development/mod-true-stereo-t3110740"]TrueStereo Mod[/URL], by @FPSUsername
2. [URL="http://forum.xda-developers.com/android/software-hacking/mod-thething-v0-2-3-t3169439"]The_Thing Mod[/URL], by me :P
3. Unofficial Alucard Kernel for CM12.1, by the JDCTeam and Alucard (Look in the OP)
4. [URL="http://forum.xda-developers.com/showthread.php?t=3034811"]XPOSED[/URL], by [user=4419114]@rovo89[/user] (Most ROM developers won’t support problems that you might encounter after installing XPOSED
5. [URL="http://forum.xda-developers.com/showpost.php?p=61892852&postcount=6"]Fstrim 3.0[/URL], from my compilation of MODs and useful scripts
6. [URL="http://forum.xda-developers.com/showpost.php?p=61892852&postcount=6"]SwaPa swap space Enabler / Disabler[/URL], from my compilation of MODs and useful scripts
7. [URL="http://forum.xda-developers.com/android/software-hacking/busybox-bonbon-s-busybox-t3253400"]Busybox builds[/URL], by me :P
8. [URL="http://forum.xda-developers.com/showthread.php?t=1916098"]MOAB, Adware, Malware, Spyware and Bloatware blocker[/URL], by @BSDgeek_Jake
Links for all of these can be also found in the OP
1. After ROM Install
Kernel and System tweaks
This section assumes that you have Alucard kernel installed, but some of the guides can be applied to systems without Alucards kernel.
You can get Official Alucard kernel from here
List of GUIDEs and Tweaks:
Code:
1. [URL="http://forum.xda-developers.com/showpost.php?p=61891946&postcount=2"]Undervolting guide[/URL], by [user=2062281]@Shade5[/user]
Through this guide, you can get some extra juice out of your phones
battery, without losing on performance too much
2. [URL="http://forum.xda-developers.com/showpost.php?p=61891964&postcount=3"]AMOLED & Hardware tweaks guide[/URL], by [user=2062281]@Shade5[/user]
A guide every S4 owner should follow, you can improve your battery life
by hours, without losing on performance [B] AT ALL [/B]
3. [URL="http://forum.xda-developers.com/showpost.php?p=61892305&postcount=5"]Camera tweaks guide[/URL], by [user=2062281]@Shade5[/user]
Do you have camera problems? No more! You can significantly decrease the
amount of frustration you have with you camera, by following this simple set of TIPs!
4. [URL="http://forum.xda-developers.com/showpost.php?p=61937937&postcount=24"]sTweaks Kernel tweaking for everyday performance[/URL], by [user=2062281]@Shade5[/user]
Tweaking the Android kernel is essential for achieving a better battery
life and performance. By following this guide, you can improve both easily!
5. [URL="http://forum.xda-developers.com/showpost.php?p=62285460&postcount=116"]Alucard's Kernel setting's[/URL], by [user=2062281]@Shade5[/user]
Oh you thought we were done tweaking the kernel? Here’s another guide on
tweaking the Android kernel, to squeeze to last little droplets of power out of your phone!
6. [URL="https://mega.nz/#!uotDxCTT!2y_-OPMbffdGBpX9V_P8TJKrbcpV9U8I09icCuvX4fQ"]_Bon_Bon’s build.prop tweaks[/URL] :P
Copy the text from this file and add them to the end of your /system/build.prop file, using a file manager. After you’re done, wipe /data/dalvik-cache and reboot your device.
([B][COLOR="Red"] ATTENTION This tweak is deprecated! Also: [/COLOR] If you flashed my The_Thing MOD, or have applied some other tweaks including build.prop, don’t use this file! [/B])
Additional tweaks
Some other small tweaks and tricks that aren’t that effective or aren’t suitable for the average user
You have been warned, some of the following TIPs aren’t suitable for everyone! So try them at your own risk!
Code:
1. Reducing resolution
Now, this boosts graphics performance A LOT, but can cause instability
You need a resolution changer app, I’d recommend NOMone Resolution
Changer from the Play Store
You have two choices, two thirds of the original resolution or three fourths
of the original resolution
(These two are the ones I chose, you can try out your own ones at your own risk)
Original
[ATTACH]3407082._xfImport[/ATTACH]
2/3
[ATTACH]3407084._xfImport[/ATTACH]
Width = 720, Height = 1280, LCD Density = 360 / 330
Gives more performance, difference is hard to see
[B] (Some games and apps might not be supported with this resolution, like Dead Trigger 2) [/B]
In addition, if you think that the icons are too large, you can go back and change LCD Density to 330
3/4
[ATTACH]3407083._xfImport[/ATTACH]
Width = 810, Height = 1440, LCD Density = 360
Gives performance, difference is impossible to see
3. Recommended and useful apps
sEFix, Entropy Tweaker
It’s a handy little app that changes Entropy generation threshold. Increasing Entropy generation threshold can reduce slowdowns while using apps that rely on randomly generated numbers.
Code:
1. Download the app from the Play Store, [URL="https://play.google.com/store/apps/details?id=com.zdvdev.sef"]here[/URL]
2. Open the app and move the slider, so the threshold shows 1024
3. Done!
Greenify, App Hibernator
Now then, we’ve all heard about the battery and performance boosting app, known as Greenify
It needs no introduction and no explanation, just go check out its XDA thread and enjoy your new found power!
Amplify, WakeLock stopper
Using this app you can prevent and customize what Wakelocks are allowed to happen and how often. It’s a handy app and worth your time, so go check out its website!
Power Nap For XPOSED
Yet another Wakelock blocker. This app lets you choose what applications that are allowed to cause Wakelocks and it blocks all others. Go check out its XDA thread!
4. Themes and personalization
This is why Android, for me anyways, it’s the best OS for your phone out there.
Customizations! Themes! Boot Animations! Endless possibilities!
So I challenge you, to tell us your favourite themes and layouts and leave links from where to find them! Some of them will be given a place in this guide!
3mel said:
as requested, my favourite theme MATERIAL GLASS by Pitched Apps
most themes I try have one tiny aspect like toggle colours and notifications tray that bug me. this theme I like on every screen, nice clean dark and simple...
compatible with layers manager RRO and CM 12.1 theme manager
http://play.google.com/store/apps/details?id=com.pitchedapps.material.glass.free
Click to expand...
Click to collapse
And that’s all, hope I helped! :3
Thanks to:
@AntaresOne
@alucard_24
@rovo89
@Shade5
@waylaidwanderer
@oasisfeng
@3mel
CAMERA HACKS & MODS
If you face a Camera bug on any Lollipop ROM where hardware interface crashes after shooting some photos/videos & it says "UNABLE/IMPOSSIBLE TO CONNECT TO CAMERA".
just reboot into recovery & flash this file
Your camera will NEVER crash again!!!! Credits to @AntaresOne
Samsung's Camera drivers are closed-source (locked) so custom ROM developers are not able to extract the full potential of the hardware (eg HDR & manual camera settings such as focal length etc.)
No Camera app can fix that issue - however I would recommend you use any of these Camera applications:
1)"OpenCamera" from Play store
2) Google Camera (preinstalled) for normal & panorama shots.
3) CM12 modded CameraNext v22 from this link
"CM Camera" is nice but again due to driver limitations it's features get limited & also Panorama sometimes crashes!
MODS/ZIPS
Here you'll find all my handy little mods and explanations what they do
I do accept request, just don't ask me to build an AI ;D
These mods require the latest busybox and init.d support!
Busybox
Don't have Busybox, or you don't like your current build? Then try mine!
It comes in 3 different builds to be used in different situations and is definitely worth your time
Now also includes a dynamic installer script! It can be used to install and update the build, so you only have to download the installer once!
SwaPa
Using this script the user can create a swap space into cache, from 50mb to 150mb.
Most users don't need it, as it's only useful if you're doing some serious multitasking or benchmarking.
When android runs out of physical memory (that rarely happens on our phone) it normally starts to kill any inactive background processes, but first gives them a chance to persist their progress (Caching or writing it down to /data) With swap, android moves the process to a swap file and retrieves it when it's needed again, so it acts like a slower version of RAM.
It also has the ability to remove all swap spaces, including Zram.
Zram is bad on a phone with a lot of physical ram (like ours) so it can be disabled. You can read more about it here.
Fstrim 3.0
When android deletes files it just writes 0 to the block where it was. This means that when android wants to rewrite to that block, it first has to completely empty it and this decreases performance. And someone could potentially recover the data that was on that block, possibly stealing personal information. So this script every 5 hours "trims" (clears blocks considered empty) /data, /system, /preload and /cache, prolonging your phones storage lifetime and improving performance. And it creates a log file to /data so you can see how much was "trimmed" You can read more about it here.
New feature! Cache dumping! Android caches apps for faster start-up and usage, but on some ROMs/Kernels this can cause lag after few days, or even few hours! Now this script dumps the cached ram for an instant speed boost!
Reserved
WAKELOCK hacks coming soon....
Tagging below users to come follow us here
@_Bon_Bon @droidblitz
@fra9090
@henry1550
@peppect91
@nickmax1
@Corduroysack
@HorkayZolee
@Sincerity1993
@mmatic10
| Under construction |
Thanks
Shade5 said:
THE OP IS OWNED & OPERATED BY TWEAK GURU _BON_BON
Below posts will be updated by Shade5
LATEST RR ROM FOR I9505
Here build by @akhilnarang
Created 2015-07-16
Last Updated 2015-07-16
Click to expand...
Click to collapse
Many thanks for doing this, makes things much easier to find and keep up to date now, a great help.
Sorry... misclicked
Will my s4 charge faster if i set the charging to 1900mA in the kernel?
Because i have a 4port usb charging port with an output of 3amps i believe.
Sent from my Resurrection-Remix \m/ I9505 \m/
droidblitz said:
Will my s4 charge faster if i set the charging to 1900mA in the kernel?
Because i have a 4port usb charging port with an output of 3amps i believe.
Sent from my Resurrection-Remix \m/ I9505 \m/
Click to expand...
Click to collapse
@droidblitz you must keep the sTweaks settings for AC Charging at 1900mA in the Kernel & USB at 460mA
Only if you have a charger 1.9A charger only will it charge super-fast to full capacity - BUT it will also heat up the circuits & it's not advisable to use the phone at such times.
P.S - I don't have the original charger (nor do I have the original battery) so I use a 1A charger to fill the battery & it does the job in a few hours (around 4-5 hrs I guess) and it doesnt heat the battery or circuits much (which means my battery will last me much much longer)
Shade5 said:
@droidblitz you must keep the sTweaks settings for AC Charging at 1900mA in the Kernel & USB at 460mA
Only if you have a charger 1.9A charger only will it charge super-fast to full capacity - BUT it will also heat up the circuits & it's not advisable to use the phone at such times.
P.S - I don't have the original charger (nor do I have the original battery) so I use a 1A charger to fill the battery & it does the job in a few hours (around 4-5 hrs I guess) and it doesnt heat the battery or circuits much (which means my battery will last me much much longer)
Click to expand...
Click to collapse
Ohh i thought it was not really working.
Gonna try it with 1900mA besides im putting my phone on top of a laptop cooler when its charging. To keep it cool while playing.
Sent from my Resurrection-Remix \m/ I9505 \m/
Excellent move making your own thread, it will be a lot easier to find stuff now @bon_bon @Shade5
Thanks @Corduroysack . Hope this makes a lot of people happy... Another guide will be posted by me today
I'm away for the weekend so will check back on Sunday night ?
Alucard kernel works on GPE ?
fra9090 said:
Alucard kernel works on GPE ?
Click to expand...
Click to collapse
No, it's for cm12.1 :/
Hope I helped :3
After I flash the Alucard Kernel, I go to STweaks to load the profile but it says no kernel support?
I had that, but if I went back to it after 30 seconds or so it showed all the settings. Check SELinux is set to permissive as well.