Android 2.3.7 - Cyanogen Mod 7.2.0 RC2 – Huawei U8120 - update 30
Based on Tas0s, Anryl CM7 Rom, CM7 Gingerman by Tilal6991, U8160 official rom by Psyke83 and kallt_kaffe U8100 rom .
Thanks for their work.
Kernel:2.6.29 (by Anryl)
Jit enabled
Ext3 support
OC 748mhz
Kernel:2.6.32-9 (based on Psyke83 u8160 sources)
Sources download
Jit enabled
Ext4 support
OC 748mhz
Android : 2.3.7 / CM7.2.0
Sources Download
Working:
RIL
Audio
Bluetooth
Data
Wi-Fi
Wi-Fi Hotspot
Camera
Accelerometer
Lights
Sensors
USB mounting
OC up to 748mhz
Extras:
Compcache support
Zipalign scripts
app2sd in ext4
ext4 support
Huawei launcher2
mms support
ip-call support
Bugs/Not working/TODO:
Missing FM (no sources available. Same for U8100, U8110, C8500, C8600, U8150, M860 and several others)
I am not responsible for any damage to your phone
Install Notes:
FIRST MAKE NAND BACKUP IN RECOVERY pwr+vlUp+dial
1-Install Rom Manager from Market and enter
2-Flash ClockworkMod Recovery 5.0.2.3 for Huawei U8120 (file in download area)
3-Install Rom from Sd Card
4-Choose the Rom and wipe everything before install
For SD mount to work format sd in recovery
Use Htc_IME keyboard for or any other with calibration - Link http://www.mediafire.com/?mudeautgj4dgye0
if you get a bootloop after switching wifi on remove the battery and it goes ok
For Updating Rom
Rename file to update.zip. put on the root of sdcard. enter recovery and select install update from sdcard
Google Apps for CM7
Latest Version - gapps-gb-20110828
http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip
Update1
Fixed GPS
Fixed AGPS
Fixed layout in usb mass storage screen & dialer
Fixed Framework
YouTube fixed
Update 2
Camera fixed
Update 3
Video recording with video illusion app
Update 4
Video recording with camera fixed
Removed format Data and System script for updating rom
initlogo changed to gingerman V5 rom
Update 5
Update 4 performance issues fixed
No need to install update 3 before 5
Update 6
Reduced framework-res for lag problem
Fixed lag after disable app
Update 7
Removed unused files from framework-res.apk
Fixed bug when connecting to Skype
Update 8
Fixed Bootloop issues after install (since update3)
Fixed layout in Screen Unlocker and Mass Storage Mount
Changed CM7 Memory Killer values to save more RAM
Update 9
Fixed CRT Animation issues
Fixed Mic Headset issue
Changed Memory Killer values to Ascend rom boot.img values
Removed unused files from previous rom testings
Update 10
Updated to recent CM7.1.0/Gingerbread 2.3.5 sources
Fixed Mic Headset issue
Update 11
Added Calibration Support (Thanks to Tas0s and Anryl)
Update 12
Updated kernel to 2.6.32-9 (based on Huawei u8160)
Added EXT4 support
OC to 614mhz
Fixed internal A2SD
Battery drain issues fixed
Fixed screen on/off animations
Update 13
Added WiFi Hotspot
default OC 600mhz
SD card 2 PC now mounts readable CDROM drive (use Qtadb to acess sdcard)
Update 14
Fixed Cyanogen CPU OC Settings (thanks to Tas0s)
Added cifs.ko module and network support
Tweaked kernel and corrected some camera settings
fixed inconsistencies in rpcrouter code (thanks to Tas0s)
Update 15
Updated cm7.1 sources
Update 16
Updated cm7.2 RC0 sources
Fixed lag after apps are closed
Fixed Barcode Scanner and Google Googles issues
Fix SD-Card mount in PC
Update 17
Fixed Wifi response
Fixed Wifi Hotstap
Fixed USB Hotstap
Updated to latest cm7.2 RC0 sources
Update 18
Updated kernel with several fixes and updates
(used xz compression, merged CM7 android driver, merged huawei_battery from 2.6.35 huawei kernel, undervolt wifi slot and several other fixes and upgrades)
Fixed several battery drain issues
updated Qualcomm GPS sources
updated RIL from u8160
Updated to latest cm7.2.0 RC0 sources
Update 19
Updated u8120 kernel
Updated to audio sources from psyke83 rom
Updated to latest cm7.2.0 RC0 sources
Update 20
reverted Touchscreen driver in Kernel to see if it fixes touch for U8100 and U8110
Updated libaudio: fix headset & headset mic routing issues during calls (Thanks to Psyke83)
Updated to latest cm7.2.0 RC0 sources
Update 20a
reverted Touchscreen patches in Kernel to see if it fixes touch for U8100 and U8110
Update 21
Updated kernel sources to 2.6.32.9 CodeAurora froyo_almond branch by Psyke83
Updated to latest cm7.2.0 RC0 sources
Update 22 (06-03-2012)
Updated kernel sources to 2.6.32.9 CodeAurora froyo_almond branch with black screen issues fixed thanks to Psyke83
Updated to latest cm7.2.0 RC0 sources (almost RC1)
Added HuaweiLauncher2.apk and some other Huawei APKs from the official M865 Gingerbread 2.3.3 Rom
Update 22b (07-03-2012)
Updated kernel sources to 2.6.32.9 huawei 2.6.32.9-perf from Psyke83 fix the black screen issue
Updated to latest cm7.2.0 RC0 sources (almost RC1)
Update 23 (12-03-2012)
Updated kernel sources to 2.6.32.9 CodeAurora froyo_almond branch with wifi sleep causing black screen fixed (better battery performance then the Huawei 2.6.32.9-perf kernel)
Updated to latest cm7.2.0 RC0 sources (almost RC1)
fixed CM7 Battery stats
Update 24 (23-03-2012)
Updated kernel 2.6.32.9 CodeAurora froyo_almond branch
Fixed MAC adress (added softmac file to system/wifi)
Added Zipalign script
Added scripts for mounting system, data and data-ext in ext4
Added zram module instead of ramzswap
Updated to latest cm7.2.0 RC1 sources
Update 25 (28-03-2012)
Updated kernel 2.6.32.9 CodeAurora froyo_almond branch
Fixed issues causing battery drain in update 24
Added poweron boot sound (R2D2) (to disable bootsound see below)
Updated camera libs from latest Froyo rom for U8180
Updated to latest cm7.2.0 RC1 sources
removed data2ext from script
Updated rom link to 25a
removed data2ext from script in 25a because of issues reported by users
fixed wifi low-power issues of update 24 and 25
Update 26 (16-04-2012)
Updated kernel 2.6.32.9 CodeAurora
added Cleancache, Zcache to kernel and several other updates and patches.
improved touchscreen calibration values
improved Rom and battery, performance
Updated camera libs from latest Froyo rom for m860
Added GooManager for future Rom updates
Updated to latest cm7.2.0 RC1 sources
Update 27 (22-04-2012)
Updated kernel 2.6.32.9 CodeAurora
added config based on JoeyJiao kernel config with improvement on battery.
used gralloc compiled from cyanogen open-source instead of proprietary one.
Fixed green glitches in Rotation animation
Added Miui theme
Updated to latest cm7.2.0 RC1 sources
Update 28 (08-05-2012)
Updated kernel 2.6.32.9 CodeAurora
Fixed several typos in Huawei kernel sources.
Enabled KSM (Kernel SamePage Mapping) support.
Turned on setting for Flash, forgot to add it in previous rom.
used libmm-omxcore and libomxcore compiled from cyanogen open-source instead of proprietary ones.
Better 2d performance (before, at 691mhz OC, Antutu Benchmark gave me 184 max score in 2d, now is 350)
Turned Rotation animation on by default
Fixed battery drain issues caused by camera after app is closed (finally)
Updated to latest cm7.2.0 RC1 sources
A format and wipe is sugested
Update 29 (30-06-2012)
Updated kernel 2.6.32.9 CodeAurora
Fixed low audio issues.
Added U8120Parts based on Psyke83 rom. A big thanks to him.
Updated to latest cm7.2.0 sources
Update 30 (09-01-2013)
Added boot sound menu to U8120Parts based on Psyke83 rom.
Cleaned several add-ons in rom
Updated to latest cm7.2.0 sources
Huawei bootanimation
http://www.mediafire.com/?xlrueekewbd3f44
Replace the file with RootExplorer in system/media and set the same permissions. Reboot
How to disable Boot Sound
Method 1- open RootExplorer app, and browse to system/ and open with text editor the build.prop file. scroll to # ADDITIONAL_BUILD_PROPERTIES and look for persist.sys.nobootsound=1 and replace 1 with 0. Save and close.
Method 2- open RootExplorer in system/media/ and delete poweron.ogg file.
How to change MAC adress
Method 1- open Terminal Emulator app, type "su" to enter superuser mode, then type this line of code:
echo 1a:2b:3c:4d:5e:6f > /system/wifi/softmac (write your own mac-adress found inside the phone in the battery case)
Method 2- open RootExplorer in system/wifi/ and open softmac file with text editor and write your own the mac-adress, save and close.
U8120 CWM recovery 5.0.2.3
http://www.mediafire.com/?g0w5k73hdoqrgso
Batch file for installing CWM recovery to phone by HofiX-CZ
Instructions in file
http://www.mediafire.com/?cobhtvqd0o0p996
Download Link: Update 11
Format data is necessary if using other rom
CM7.1.0 with kernel 2.6.29 - I suggest a format system and data in recovery, mounts and storage, before installing
http://www.mediafire.com/?v6sabh378piibuu
Download Link: Update 22b
CM7.2.0 RC0 with Kernel 2.6.32-9-perf from Huawei
http://www.mediafire.com/?dkouo40d8btcgm6
Download Link: Update 23
CM7.2.0 RC0 with Kernel 2.6.32-9-perf from Codeaurora
http://www.mediafire.com/?tzab5yx55f9t8rt
Download Link: Update 25a
CM7.2.0 RC1 with Kernel 2.6.32-9-perf from Codeaurora
http://www.mediafire.com/?ip4v7p3xf8azkgy
Boot.img update for Update 25a with Kernel 2.6.32-9-perf from Huawei
Just install as any rom, after update 25 or 25a is installed.
http://www.mediafire.com/?dvc8kg4g28n2x2i
Download Link: Update 26
CM7.2.0 RC1 with Kernel 2.6.32-9-perf from Codeaurora
http://tinyw.in/pd8b
Download Link: Update 27
CM7.2.0 RC1 with Kernel 2.6.32-9-perf from Codeaurora
http://tinyw.in/DD5T
Download Link: Update 28
CM7.2.0 RC1 with Kernel 2.6.32-9-perf from Codeaurora
I suggest a format boot, system, data and cache in recovery=» mounts and storage, before installing
http://tinyw.in/p3se
Download Link: Update 29
CM7.2.0 RC1 with Kernel 2.6.32-9-perf from Codeaurora
http://tinyw.in/xbR7
Download Link: Update 30
CM7.2.0 RC1 with Kernel 2.6.32-9-perf from Codeaurora
http://tinyw.in/9cIf
Other U8120/U8100/U8110 Rom's (from Ainster)
All Huawei U8100/U8110/U8120 ROM's in one place
system/app/CertInstaller.apk
E:Verification failed
Installation aborted
help please!!!!!!!!!!
rodry21 said:
system/app/CertInstaller.apk
E:Verification failed
Installation aborted
help please!!!!!!!!!!
Click to expand...
Click to collapse
Install recovery HUAWEI ASCEND -from rommanager ,boot, wipe everything and install zip from sdcard
works fine but lack optimazacion 3D gaming with this rom games are slow but everything else works perfectly thanks for the rom
great rom, but i cant copy my files to SD,usb, its open like CD ROM, but impossible to add files..
mih_88 said:
great rom, but i cant copy my files to SD,usb, its open like CD ROM, but impossible to add files..
Click to expand...
Click to collapse
Is your sd formated with ext2 or 3?
Awesome ROM, installed without a problem. Its a bit sluggish, could be just my phone.
joilaroi said:
Is your sd formated with ext2 or 3?
Click to expand...
Click to collapse
with fat.
joilaroi said:
Is your sd formated with ext2 or 3?
Click to expand...
Click to collapse
Now formatted to FAT, without succes..
mih_88 said:
Now formatted to FAT, without succes..
Click to expand...
Click to collapse
Thats strange. i have formated sd with fat32 on first partition and with ext3 on second and link2sd works, as well as usb mounting.
Have you tried to remove the windows driver and let it install again?
NO WORKING Fpse,Gensoid,Snesoid,Games in 3D slow performance
waiting for next release
joilaroi said:
Thats strange. i have formated sd with fat32 on first partition and with ext3 on second and link2sd works, as well as usb mounting.
Have you tried to remove the windows driver and let it install again?
Click to expand...
Click to collapse
And you can copy\delete files from SD? Are you shure? I see my SD, all files and folders, but edit them impossible..
But at tahahawa 1.3.5 its mount perfect without problems and removing drivers with etc.2,3, fat 32..
what about the FM ?
If people having problems with mounting. Backup everything, then let Clockwork recovery to format your SD and do a full wipe on everything, then re-flash the rom.
I try this rom today
My first opinion: it's good! But due to many little bugs i still on tahahawa's froyo rom :]
But if the fm radio, camera, calibration and the opengl renderer will workt perfectly, it'll be a good rom
Thanks!
Sent from my U8120 using XDA Premium App
try taking calibration from anryl's rom
rwmanos said:
try taking calibration from anryl's rom
Click to expand...
Click to collapse
unfortunately CM7 as no calibration support
I'm not able to access the status bar due to bad calibration on my 8120. The only possibility is to put it to the lower side of the screen in the tablet tweaks of the cyanogenmod menu.
Is there a way to access the statusbar from the upper side?
I can't find the native tethering menu of gingerbread, is it disabled? Tethering via barnacle app works.
Performance seems to be a bit low. I set the overclock already to 710MHz.
Otherwise this is a nice ROM, I will test it for the next couple of days.
eckerse said:
I'm not able to access the status bar due to bad calibration on my 8120. The only possibility is to put it to the lower side of the screen in the tablet tweaks of the cyanogenmod menu.
Is there a way to access the statusbar from the upper side?
I can't find the native tethering menu of gingerbread, is it disabled? Tethering via barnacle app works.
Performance seems to be a bit low. I set the overclock already to 710MHz.
Otherwise this is a nice ROM, I will test it for the next couple of days.
Click to expand...
Click to collapse
Go to adwlauncher/general settings/swipe down - set it to open close notifications.
Update 2
http://www.mediafire.com/?sywbmjp3zaeah8j
Video fixed. for video recording use Video Illusion from Market
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 ?