Related
NEXT 2.1.8 placeholder: http://forum.xda-developers.com/showpost.php?p=51678768&postcount=2513
STOP! This kernel supports ONLY Samsung Jelly Bean 4.1.x, 4.2.2, CM 10.1.x, 10.2, and 11.0. It won't work on ICS, CM 9, CM 10.
FOR NOW I FORBID ANYONE ELSE REUSE THIS STILL IN DEVELOPMENT DUAL BOOT PROJECT FOR HIS/HER OWN GALAXY TAB 2 PROJECT!
STOP PRESS:
NEXT 2.x separated in two package: the kernel part as blackhawk-next-kernel-2.x-p31xx.zip and the proprietary binaries part as proprietary-vendor-samsung.zip for JB >= 4.2 and proprietary-vendor-samsung-4.1.x.zip for JB 4.1.x .
Flash the kernel part first and then directly the proprietary binaries part! Flash the appropriate proprietary part on both 1st and 2nd ROM!
Sources:
Kernel sources at http://github.com/kumajaya/android_kernel_samsung_espresso10/tree/cm-10.2-update
Features:
Samsung stock 4.1.x, 4.2.2 (since 1.8), CM 10.1.x and CM 10.2 (since 1.7) support with a single kernel image
For stock ROM: external SD card - internal media swapper script included
Samsung proprietary exFAT modules are loaded. CM 10.1 exFAT support files attached at post #2
For CM/CM based ROM: auto rotate screen default orientation depend on ro.sf.hwrotation value, camera orientation fix included
Dual-booting. You can have Samsung JB and CM 10.1 ROMs on a single device at the same time.
Nice looking AROMA based boot menu
Using CyanogenMod kernel source, updated to p3110 source for newer WLAN (Youtube HD bugfix on stock ROM), modem, sensors driver, and etc for both P31xx and P51xx target
CPU clock: 300MHz, 600MHz, 800MHz, 1.008GHz, 1.2GHz, 1.35GHz, 1.42GHz, 1.48GHz, and 1.52GHz, locked @ 1.008GHz on boot
GPU clock: 153.6MHz, 307.2MHz, 384MHz, and 512MHz, 307.2MHz as the default maximum clock
CPU voltage control. You can use Android Tuner/System Tuner/Trickster MOD to set CPU voltage
The ramdisk base on JB 4.1.2 (stock ROM) and JB 4.2.2 (CM 10.1)
Using newer PowerVR SGX 540 kernel modules and binaries blob
row, bfq, sio, and vr scheduler support
Governor bug fix. Replace Samsung's interactive governor with default OMAP4 3.0.31 interactive governor from omapzoom.org, plus pegasusq and lulzactive
NFS and CIFS/samba (not loaded by default) filesystem support
LZMA compressed initrd, to keep boot image smaller than 8MB
swap support. zram and cleancache with a working zcache driver, enabled by default
kernel config, insmod configs.ko and then you can access /proc/config.gz
external modem support, for PPP Widget (not loaded by default, P31xx need powered USB hub for external modem)
Some tweaks from gokhanmoral's siyahkernel for S3, passive entropy tweak applied
Remove a lot of debug message from touchscreen driver, display, mmc, modem, etc
linaro arm-linux-gnueabihf- cross compiler, compiler optimization applied
SuperSU v1.41 for stock ROM
Self compiled BusyBox v1.22.0-git in /sbin, config file based on CM's BusyBox bbconfig output. fstrim applet patch applied, android_reboot applet added (a quick but clean port from Android toolbox), swapon applet with priority option. For stock ROM: this version of Busybox will overwrite busybox binary in /system/bin or /system/xbin and save it as busybox.backup
Early boot scripts support (/system/etc/init.d, /data/local/userinit.sh, and /data/local/userinit.d)
Post boot script support (/system/etc/init.post_boot.sh)
For stock ROM: custom boot animation support (/data/local/bootanimation.zip or /system/media/bootanimation.zip if exists, Samsung boot animation as a fallback). If a bootanimation.zip found, the boot sound will be turned off as well as the shutdown animation.
Modified mount options
adb insecure, adb mode in charge state also insecure
Advanced TCP congestion support, westwood as the default congestion
No /system/etc/hosts patch, you can install AdAway from F-Droid
Known Problems:
Thanks To:
gokhanmoral, amarullz, Phil3759, Chainfire, cmenard, codeworkx, imoseyon, coolbho3k, Faux123, AuxLV, CodyF86, poppolo2001
This part will be expanded. Most of the patches I applied are coded by someone else. Please remind me if I forget to give credits to anybody...
Downloads:
PhilZ Touch 5.08.5: http://forum.xda-developers.com/showthread.php?t=2202667
Todo:
More features in NEXT tool
Special Thanks:
@trssho91, @Caldair, @fast96, @Jellydroidkin, @Android-Andi, @nakbaliNe, @Bhaskara Rao, @tsatomas
Downloads Record:
blackhawk-next-kernel-1.0-p31xx.zip: 316
blackhawk-next-kernel-1.1-p31xx.zip: 87
blackhawk-next-kernel-1.1-addon-nooc-p31xx.zip: 41
blackhawk-next-kernel-1.2-p31xx.zip: 503
blackhawk-next-kernel-1.2-addon-nooc-p31xx.zip: 160
blackhawk-next-kernel-1.3-p31xx.zip: 240
blackhawk-next-kernel-1.3-addon-nooc-p31xx.zip: 112
blackhawk-next-kernel-1.4-p31xx.zip: 583
blackhawk-next-kernel-1.4-nooc-p31xx.zip: 294
blackhawk-next-kernel-1.6-p31xx.zip: 380
blackhawk-next-kernel-1.6-nooc-p31xx.zip: 227
blackhawk-next-kernel-1.6.1-p31xx.zip: 180
blackhawk-next-kernel-1.6.1-nooc-p31xx.zip: 90
blackhawk-next-kernel-1.6.2-p31xx.zip: 151
blackhawk-next-kernel-1.6.2-nooc-p31xx.zip: 81
blackhawk-next-kernel-1.5-p31xx.zip: 600
blackhawk-next-kernel-1.5-nooc-p31xx.zip: 304
blackhawk-next-kernel-1.8.1-p31xx.zip: 222
blackhawk-next-kernel-1.8.1-nooc-p31xx.zip: 99
blackhawk-next-kernel-1.8.2-p31xx.zip: 577
blackhawk-next-kernel-1.8.2-nooc-p31xx.zip 321
XDA:DevDB Information
[KERNEL][SINGLE/DUAL][JB/KK][STOCK/CM]blackhawk's NEXT kernel, Kernel for the Samsung Galaxy Tab 2
Contributors
ketut.kumajaya, Android-Andi
Kernel Special Features: Dual boot stock and AOSP based ROM
Version Information
Status: Stable
Current Stable Version: 2.3
Created 2014-09-21
Last Updated 2014-10-11
NEXT 2.x separated in two package: the kernel part as blackhawk-next-kernel-2.x-p31xx.zip and the proprietary binaries part as proprietary-vendor-samsung.zip for JB >= 4.2 and proprietary-vendor-samsung-4.1.x.zip for JB 4.1.x .
Changelog:
21/04/2014 2.2:
Flash-Friendly File System (f2fs) support
Full github commits 8/4 - 20/4/2014: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-11.0
Update proprietary blobs, proprietary-vendor-samsung-update.zip
02/01/2014 2.1.5 -> 2.1.6:
CM 11.0 support
28/10/2013 2.1.4 -> 2.1.5:
Updated to upstream 3.0.101 kernel
Audit and SELinux enabled
Smartreflex completely disabled
GPU frequencies not exposed to STweaks bug fixed
Do not load exFAT modules on CM 10.2
Full changelog: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.2-update
27/10/2013 2.1.3 -> 2.1.4:
Ramdisk updated to sync with latest CM 10.2
20/10/2013 2.1.2 -> 2.1.3:
Update init script for PAC
Disable almost all kernel debugging support except KALLSYMS. Kernel failed to boot with CONFIG_KALLSYMS disabled
28/09/2013 2.1.1 -> 2.1.2:
Turn all CPUs online when governor gets changed, hotplug bug workaround
SIO and VR I/O scheduler
Initial STweaks support, big thanks @gokhanmoral. Download STweaks app from Play store to access almost all NEXT related settings (CPU governor, frequency, and voltages; GPU governor and frequency limit; surfaceflinger rotation; I/O scheduler; logger; CIFS, Xbox controller, and USB modem support; and dual boot related settings).
22/09/2013 2.1 -> 2.1.1:
Update overclock codes, remove gpu_oc interface: https://github.com/kumajaya/android...mmit/94ac45a10213de400c7bf3c01b5c5b052ae8ba18
sgxfreq: add sysfs interface to store frequency limit: https://github.com/kumajaya/android...mmit/738061b30d2278d3b51b341bc2597dad300f4e47
sgxfreq: limit frequency to default on boot: https://github.com/kumajaya/android...mmit/8a6933cf6565b5587db6a2a5ce7b1207807ab701
The latest Android Tuner app needed to control the modified OMAP GPU control interface but the dirty way by editing /etc/init.post_boot.sh always available
18/09/2013 2.0 -> 2.1:
Separated vendor blobs for JB 4.1.x and JB >= 4.2, @poppolo2001 fix applied
With CPU and GPU overclock, CPU under/over voltage, upstream kernel 3.0.96 by @CodyF86
Complete changelog: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.2-update
02/09/2013 1.8.3 -> 2.0:
Vendor blobs in separated flashable zip, taken from Samsung 4.2.2. Flash proprietary-vendor-samsung.zip directry after flashing NEXT kernel 2.0 on both 1st and 2nd ROM!
Ten seconds boot menu timeout. Boot to the latest booted ROM when timeout periode reached. Finally, my trick works :victory:
Using Samsung P3110 Update1 kernel source: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=p3110 . Patched to comply CM/AOSP need and NEXT dual boot, without SELinux and audit support, gcc linaro compiler. Kernel source: https://github.com/kumajaya/android_kernel_samsung_espresso10/tree/cm-10.2
Samsung open source exFAT kernel modules included, source: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=exfat
Without CPU or GPU overclock
Without extended CPU governor or I/O scheduler
Without swap or zram support
AROMA 2.70 beta 6 binary
13/08/2013 1.8.2 -> 1.8.3:
Samsung 4.2.2: The first attemp to reduce battery draining issue, zram service disabled! You can enable zram (not as a service) by issuing "setprop persist.service.zram 25" over Terminal Emulator or "adb shell". Reboot is required.
CM 10.2: Bluetooth tethering fix from upstream CM 10.2
07/08/2013 1.8.1 -> 1.8.2:
The third attemp to support Samsung 4.2.2 for all device configuration
Vendor blobs in separate flashable zip updated, please re-download it!
06/08/2013 1.8 -> 1.8.1:
The second attemp to support Samsung 4.2.2 for all device configuration
Vendor blobs in separate flashable zip. For all ROMs, on both 1st and 2nd ROM: Flash vendor-blobs-new-ducati-blackhawk.zip directry after flashing NEXT kernel!
Single channel sound output bug fix
05/08/2013 1.7 -> 1.8:
Initial Samsung 4.2.2 support
Updated to upstream Linux kernel 3.0.41 (incremental patch)
https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.1-blackhawk 1-2 Aug 2013
The first kernel utilizing the new ducati firmware, the first kernel preserved 815.8MB RAM! Don't forget to flash vendor-blobs-old-ducati-blackhawk-p31xx.zip if you switch to another kernel
01/08/2013 1.6.3 -> 1.7:
Initial CM 10.2 support. Do not flash blackhawk-next-cm-exfat-vold.zip! CM 10.2 already has an open source/reverse engineered exFAT filesystem support
zram switched to zsmalloc, zram optimized for Android disabled
XBox 360 USB controller with BigX LED support enabled (by @iks8 request). Modules not loaded by default, edit /system/etc/init.d/02modules to activate it.
23/07/2013 1.6.2 -> 1.6.3:
Add android_reboot applet to NEXT's busybox (a quick port from Android toolbox) to fix AROMA boot menu fail to boot into recovery/bootloader as reported by @kinung
I hate bug!
22/07/2013 1.6.1 -> 1.6.2:
Hotplug CPU governor working properly with cleancache enabled, zcache memory corruption problem fixed!
21/07/2013 1.6 -> 1.6.1:
Hotplug CPU governor kernel panic bug fix. This governor not working properly with cleancache enabled, cleancache disabled for now
Static linked busybox compiled from source, fstrim patch applied. Busybox config based on CM's busybox bbconfig output. Total 46 more than previous busybox applet, add priority option to swapon applet
zRAM swap per CPU core, same priority value. CM's /system/bin/compcache script updated to handle 2 zRAM devices. Reference: http://wiki.gentoo.org/wiki/Zram
Stock ROM persist.customboot.zram property changed to persist.service.zram, follow CM's standard
Stock ROM default zRAM size changed to 26% RAM size
Swappiness value changed to 90
18/07/2013 1.5 -> 1.6:
LZO compression updated to current upstream version, optimized for arm. Reference: http://git.kernel.org/cgit/linux/ke.../?id=b0af9cd9aab60ceb17d3ebabb9fdf4ff0a99cf50
zRam support optimized for Android, utilizing the new lzo library. Set 18% of RAM as zRam swap file. CM user can use CM's Settings - Performance options.
cleancache support with working Zcache driver, utilizing the new lzo library
entropy threshold tweaks, /dev/random linked to /dev/urandom
github 14-18/07/2013 commits: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.1-blackhawk
11/07/2013 1.4.1 -> 1.5:
Decrease CPU voltage for frequencies below 1.2GHz, increase CPU voltage for frequencies above 1.2GHz
Re-enable MMC_CAP_ERASE for I/O speed improvement, run "fstrim -v /data" and "fstrim -v /cache" manually to TRIM your filesystem or run LagFix (fstrim GUI, download it from Play)
Remove my old hack in cpufreq driver
Newer PowerVR SGX540 3D kernel module and vendor binaries, in sync to CM-10.1. For dual boot user, you must update both 1st and 2nd ROM to renew both ROM vendor binaries!
Change screen_off_max_freq from 1.008GHz to 800MHz, small changes in init scripts
SuperSU v1.41
16/06/2013 1.4 -> 1.4.1:
I/O speed improvement, 1.3 and 1.4 bugfix
SuperSU v1.34 - thanks Chainfire
nooc: Smartreflex class 3 re-enabled, voltage control disabled
small update to disable swap support by default for my "stock based ROM" included
04/06/2013 1.3 -> 1.4:
Selected kernel modules, scripts, and binaries integrated in boot.img, single flash for 1st and 2nd ROM
Kernel compression back to gzip, boot.img compression switched to lzma for better compression (I need more space)
Auto root (for stock)
Auto busybox (for stock)
Auto rotate (for both stock and CM) depend on ro.sf.hwrotation value, camera orientation fix included
External sdcard and internal media swapper script integrated in boot.img (for stock as 1st ROM)
Override init.d CPU governor setting on boot completed (technical reason/by design). Please use an app "on boot" or /etc/init.post_boot.sh to set CPU governor
init script reworked (again), simplified
Standalone nooc version, no longer as an addon for standard NEXT
Untested CRT off animation support
01/06/2013 1.2 -> 1.3:
Updated compiler to the latest linaro gcc 4.7
Better data integrity on both 1st and 2nd ROM
Ramdisk init scripts reworked, inline with the latest Samsung (Taiwan BRI 04/2013) and CM (29/05/2013 nightly)
Inline with P51xx port
Updated exFAT modules (don't know it's better or worse, it's closed source)
Default CPU clock still 1.008GHz, default GPU clock 307.2MHz
1.1 -> 1.2:
Potential bug in sdcard swapper script fixed. Yes, for stock ROM as 1st ROM this kernel still has a script to swap external sdcard - internal media.
SuperSU updated to the latest version (stock ROM).
1.0 -> 1.1:
exFAT filesystem support, stock ROM only for now. I will share separate flashable zip for CM 10.1, when it's ready (broken USB storage support). Please note Dual Boot FAQs #24!
CGROUPS, SLUB, and TRACING support back enabled for exFAT compatibility, Android logger disabled by default to compesated it. You can enable logger by editing /system/etc/init.d/02modules .
No boot menu in single ROM environment.
Change stock ROM init.d script starting point. Earlier than before, same as CM 10.1 now.
Non overclock addon for anyone who is experiencing overheats when using standard NEXT kernel.
Source change: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.1-blackhawk, May 24-26, 2013. A lot of undocumented change in ramdisk side.
exFAT support in CM 10.1
Download and flash blackhawk-next-cm-exfat-vold.zip over recovery
fsck.exfat, mkfs.exfat, vold binaries and all needed libraries taken from Samsung JB 4.2.2 included
USB storage support is broken, you need USB OTG Helper from http://forum.xda-developers.com/showthread.php?t=1588940 as 3rd party USB storage mounter
exfat binaries for exfat support in USB OTG Helper included. So, all USB OTG Helper features (FAT, Ext2/3/4, full NTFS, and exFAT support) enabled
To avoid Dual Boot FAQs #24 issue, flash blackhawk-next-cm-exfat-vold.zip and NEXT kernel of course directly after CM update. For CM 10.1 only!
Download Record:
proprietary-vendor-samsung.zip: 4481
proprietary-vendor-samsung-4.1.x.zip: 1478
Dual Boot FAQs
Dual Boot FAQs
Adapted from droidphile's "Dual Boot FAQs" with permission.
1. "Why would I wanna dual-boot?"
A. You don't have to.
Suppose you're more of an aosp rom fan. But misses the HDMI out, bluetooth hands-free and love sammy camera more. Do a minimal installation of sammy rom and boot into it when in need of these features and use aosp rom otherwise.
Or you are a sammy rom fan but love the responsiveness and pure android feel of aosp roms.
And while you can dual boot two sammy or two aosp roms, it doesn't make any sense.
2. "What if I don't need dual booting?"
A. No issues. Kernel won't force to setup 2 roms. You can single boot as before.
3. "Will dual booting change my bootloader or do any dangerous stuff like setting my phone on fire?"
A. NO. Changes are at kernel and ramfs level only. Some space in your internal sd card is used, and also the unused hidden partition mmcblk0p11 is used to store cache of second rom. Dual booting doesn't repartition the filesystem or perform anything scary.
4. "I want to setup dual booting."
A. There are four situations:-
1) Sammy rom now. Want to use aosp as secondary.
2) Sammy rom now. Want to use aosp as primary.
3) Aosp rom now. Want to use sammy as secondary.
4) Aosp rom now. Want to use sammy as primary.
Prerequisites for any setup is
a) Flash latest blackhawk's NEXT kernel
b) Flash new ducati vendor blobs (since 1.8.x)
c) Flash latest PhilZ Touch - blackhawk repack version - recovery
d) Atleast 90% battery left.
e) 2 GB free on internal SD.
f) Some spare time
1) Present sammy, setup aosp as secondary:-
i) Reboot into recovery
ii) Flash blackhawk's NEXT tool, create system.img for CM/CM based ROM and then close it
iii) Reboot into secondary recovery
iv) Flash aosp ROM as 2nd ROM
v) Flash blackhawk's NEXT kernel again
vi) Flash new ducati vendor blobs again (since 1.8.x)
2) Present sammy, setup aosp as primary:-
i) Reboot into recovery
ii) Nandroid backup your current sammy ROM
iii) Flash blackhawk's NEXT tool, create system.img for Samsung stock/stock based ROM and then close it
iv) Reboot into secondary recovery
v) Nandroid restore your sammy ROM as 2nd ROM
vi) Flash blackhawk's NEXT kernel again
vii) Flash new ducati vendor blobs again (since 1.8.x)
viii) Reboot into primary recovery
ix) Flash aosp ROM as 1st ROM
x) Flash blackhawk's NEXT kernel again
xi) Flash new ducati vendor blobs again (since 1.8.x)
3) Present aosp, setup sammy as secondary:-
Same as (1), instead of flashing aosp to second, flash sammy to second.
4) Present aosp, setup sammy as primary:-
Same as (2), instead of flashing aosp to first ROM, flash sammy.
NOTE:
-To dual boot Two Aosp or Two Sammy roms, just follow (1) or (2) (depending on which one of them you want as primary/secondary), just flash Sammy instead of aosp or aosp instead of sammy.
5. "What things should I be taking care off while dealing with dual booting?"
A. - Make sure where you are: in primary or secondary recovery.
6. "How to boot into primary rom?"
A. AROMA based boot menu will help you on every boot.
7. "How to boot into secondary rom?"
A. AROMA based boot menu will help you on every boot.
8. "Is kernel partition shared?"
A. Yes. Same kernel boots both roms.
9. "If I flash another kernel (that doesn't support db) do I lose dual booting?"
A. Yes
10. "I lost dualbooting after flashing another kernel. I didn't do anything to second rom files in sdcard/.secondrom. How can I get db back?"
A. Just flash the latest blackhawk's NEXT kernel, flash new ducati vendor blobs again (since 1.8.x)
11. "Will there be any performance degradation on the rom used as secondary compared to primary?"
A. NO
12. "Will my phone run slow overall because of db?"
A. NO
13. "How to flash a newer version of 1st rom?"
A. As usual, just flash it from primary recovery. Flash blackhawk's NEXT kernel again, flash new ducati vendor blobs again (since 1.8.x)
14. "How to flash newer version of 2nd rom?"
A. Just flash it from secondary recovery. Flash blackhawk's NEXT kernel again, flash new ducati vendor blobs again (since 1.8.x)
15. "Would upgrading 1st or second rom cause other rom to fail on boot?"
A. No. Partitions of other rom are not touched during upgrading.
16. "I miss the recovery I used before, so much.."
A. PhilZ Touch not bad at all.
17. "User apps of 1st rom are automatically available for second rom?"
A. NO. However, if you had backed them up using Titanium Backup or similar apps, just restore apps while on second rom.
18. "I wanna keep separate backup for apps in both the Roms, since I use one Rom for say entertainment and other productivity."
A. Setup different backup directory in Titanium Backup in 1st and 2nd rom.
19. "I don't see STweaks app in second rom."
A. This is blackhawk's NEXT dual boot solution for Galaxy Tab 2, a free implementation of gokhanmoral's Siyah dual boot.
20. "Do I need to anything special before flashing a newer blackhawk's NEXT kernel?"
A. NO. Just flash kernel in primary and secondary recovery. Yes, on both 1st and 2nd ROM. Just flash kernel in recovery - whichever you used to do. Kernel image is copied to the unified kernel partition (since 1.4 version). Flash new ducati vendor blobs (since 1.8.x) on both ROM may be required to ensure vendor blobs match to the kernel
21. "How can I run same STweaks settings of 1st Rom in 2nd Rom?"
A. This is blackhawk's NEXT dual boot solution for Galaxy Tab 2, a free implementation of gokhanmoral's Siyah dual boot.
22. "How do I remove everything related to DB and run single boot again?"
A. In primary recovery, flash blackhawk's NEXT tool and delete 2nd ROM system image. OR delete .secondrom directory in /data/media while on 1st Rom.
23. "If secondrom files are kept in /data/media, will wiping data in recovery erase second rom files?"
A. NO. /data/media is skipped in CWM recovery.
24. "I was using ExFat card on sammy rom without any issues. I have setup dual boot with aosp and now after booting into CM it says microSD card is corrupted."
A. Aosp roms doesn't support ExFat out of the box. The data was corrupted by aosp vold. Even if you boot back to Sammy rom, it still would be corrupted. To recover data, manually mount the card in recovery, copy contents to internal SD and reformat card to a Fat32.
Also try
chkdsk X: /f (where X is the drive letter of microsd), you may be able to copy data.
25. "I read somewhere that both rom data partition use the same space. Doesn't that mean my apps are shared across roms?"
A. NO. It just means they uses same partition. They're still different directories.
1st rom data = /data
2nd rom data = /data/media/.secondrom/data
26. "Will hitting "Boot into Secondary Recovery" in recovery boot menu change my recovery?"
A. NO. It just runs (not flash) an alternate recovery so that you can configure dualboot settings.
27. "How do I backup 1st Rom and 2nd Rom?"
A. To backup 1st Rom, do what you did to backup rom while you were single booting a while ago.
To backup 2nd Rom, use the secondary recovery.
28. "Is there an easier way for dual-boot?"
A. Yes, send your device to me.
29. "DB architecture?"
A. Like you know, every rom has a /data, /system, /cache partition and a kernel to boot.
For primary rom, it's
mmcblk0p10 = /data
mmcblk0p9 = /system
mmcblk0p7 = /cache
And these won't change whether you're single booting or dual booting.
For secondary rom, data and system is stored in internal sd, cache in hidden partition. Note that internal sd in our device is mounted to /data/media.
We have data as a directory, System as an image in data/media/.secondrom. Cache in mmcblk0p11 which is hidden partition and not used otherwise.
- When second rom is booting, second rom data is bind mounted to mmcblk0p10 as /data/
- data/media/.secondrom/system.img partition is mounted as /system.
- mmcblk0p11 is mounted as /cache.
More FAQs will be added and the list will be updated as DB is improved.
Dual Boot Exercises
Exercise I
An example current facts:
ROM: Samsung stock JB 4.1.2
Kernel: blackhawk single kernel
Recovery: PhilZ Touch prior version
Prerequisites step:
Update your kernel to blackhawk's NEXT kernel
Update your recovery to the latest PhilZ Touch - blackhawk repack version - recovery
Download CM latest nightly + GApps zip
~2GB free on internal storage
Dual boot step:
Reboot into recovery
Flash blackhawk's NEXT tool, create system.img for CM/CM based ROM and then close it
Reboot into secondary recovery, make sure you choose "Secondary Recovery"! Make sure you really choose "Secondary Recovery"!!
Flash CM
Flash GApps zip
Reflash blackhawk's NEXT kernel
Reboot into secondary ROM - CyanogenMod!
It's always better if you make a backup before performing all above steps. Do it at your own risk!
Exercise II
An example current facts:
ROM: CM 10.1 latest nightly
Kernel: blackhawk single kernel
Recovery: PhilZ Touch prior version
Have Samsung stock 4.1.2 nandroid backup
Prerequisites step:
Update your kernel to blackhawk's NEXT kernel
Update your recovery to the latest PhilZ Touch - blackhawk repack version - recovery
Nandroid backup your current CM 10.1 ROM
~2GB free on internal storage. I am not sure, depend on your backup data size
CM 10.1 as 2nd ROM:
Reboot into recovery
Flash blackhawk's NEXT tool, create system.img for CM/CM based ROM and then close it
Reboot into secondary recovery, make sure you choose "Secondary Recovery"! Make sure you really choose "Secondary Recovery"!!
Restore CM 10.1 nandroid backup
Format /cache, clean dalvik-cache
Reflash blackhawk's NEXT kernel
Reboot into secondary ROM - CyanogenMod!
Samsung 4.1.2 as 1st ROM:
Reboot into primary recovery, make sure you choose "Primary Recovery"! Make sure you really choose "Primary Recovery"!!
Restore Samsung stock 4.1.2 nandroid backup
Format /cache, clean dalvik-cache
Reflash blackhawk's NEXT kernel
Reboot into primary ROM - Samsung!
Do all above steps at your own risk!
Just opened a new thread for my masterpiece work on Galaxy Tab 2. Enjoy it and don't forget to press my Thanks button
PhilZ Touch attached in post #1 has a "red" on screen navigation bar in secondary recovery to distinguish between primary and secondary :laugh:
08/08/2013: Kernel for stock 4.2.2 Developtment Secret
If you want to build your own kernel for stock 4.2.2, this is the development secrets how to fix CPU frequency jumping to maximum available frequency, how to fix slow graphics issue, how utilize the new ducati firmware and increase the RAM space, how to fix hardware accelerated media problem and how to fix WiFi tethering issue.
Kernel source: http://github.com/kumajaya/android_kernel_samsung_espresso10/tree/cm-10.1-blackhawk
Samsung kernel update: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=p3110
Samsung exFAT source: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=exfat
How to fix CPU frequency jump to maximum available frequency (1.52GHz, overclock version) on boot
Rename /system/lib/hw/power.default.so to /system/lib/hw/power.default.so.bak, copy power.piranha.so from NEXT kernel 1.8.2 package to /system/lib/hw
How to fix slow graphics issue
This solution authored by @codeworkx 8 moths ago but disabled by default: https://github.com/kumajaya/android...mmit/0c6d1a53f1a51b588786b168a48e2566f8a49065 Enabling both FB_OMAP2_VSYNC_SEND_UEVENTS and FB_OMAP2_VSYNC_SYSFS solve this problem
How utilize the new ducati firmware and increase the RAM space
How to fix hardware accelerated media problem
How to fix WiFi tethering issue
If you use above information, proper credit must be given including a clear text about this solution.
21/09/2013: OMAP PowerVR 3D GPU Control
There some interface inside /sys/devices/platform/omap/pvrsrvkm.0/sgxfreq:
frequency interface to access the current GPU frequency (153600000/307200000/384000000)
frequency_list interface to access supported GPU frequencies (153600000 307200000 384000000)
frequency_limit interface to access the GPU maximum frequency limit (default: 307200000). Writeable mean this code inside the pvrsrvkm kernel module, the GPU maximum frequency controllable
governor interface to access the current GPU governor (userspace/on3demand/activeidle/onoff)
governor_list interface to access supported GPU governor (userspace on3demand activeidle onoff)
The upcoming version of Android Tuner (0.10.2) support OMAP GPU controls.
21/09/2013: NEXT 2.0.1
As I mentioned before, I still continued cm-10.2 branch kernel development. This branch is the source code of NEXT 2.0, I've added overclock support but limited at 1.2GHz CPU and 384MHz GPU. OMAP GPU controls support applied as gpu_oc interface replacement. Kernel attached here as blackhawk-next-kernel-2.0.1-p31xx.zip .
Changelog:
Rewriting overclock code: https://github.com/kumajaya/android...mmit/35e0c0455cb7ae4beb50375c5873b328a76a1087
Add sysfs interface to store GPU frequency limit: https://github.com/kumajaya/android...mmit/738061b30d2278d3b51b341bc2597dad300f4e47
Limit GPU frequency to default on boot: https://github.com/kumajaya/android...mmit/8a6933cf6565b5587db6a2a5ce7b1207807ab701
Xpad force feedback support disabled
WARNING: This kernel only for device that can handle 1.2GHz CPU and 384MHz GPU frequency.
ketut.kumajaya said:
Just opened a new thread for my masterpiece work on Galaxy Tab 2. Enjoy it and don't forget to press my Thanks button
Click to expand...
Click to collapse
Now Im very confuse. Which one to use? Im on CM10.1 4.2.2 Lastet update.. GT P3110..which kernel should I install? what is the different between KK and Philz Touch?
Fotonista said:
Now Im very confuse. Which one to use? Im on CM10.1 4.2.2 Lastet update.. GT P3110..which kernel should I install? what is the different between KK and Philz Touch?
Click to expand...
Click to collapse
There is no confusion at all...
Every file you need is in the first post: kernel, tool and Philz. Don't use anything else.
Read the examples. All information is in there...
I don't know about the differences between KK and Philz, but I don't care though... Philz is just great!
Many, many respects to ketut...
Big thanks for your efforts...
Sent from my GT-P3110 using xda app-developers app
Fotonista said:
Now Im very confuse. Which one to use? Im on CM10.1 4.2.2 Lastet update.. GT P3110..which kernel should I install? what is the different between KK and Philz Touch?
Click to expand...
Click to collapse
PhilZ Touch is a recovery image, NEXT kernel is a boot image, KK-Boot discontinued project.
Ketut @ awesome work with awesome guide.. U explained each n every step clearly for freshers.. N BTW do I need to update Blackhawk next kernel to 1.0..if yes, wiping cache n delvk is necessary before flashing? I am asking u cos I Dnt want to be in mess anymore.. I am happily enjoy dual boot environment.. Thanks again for all the effort..
Sent from my GT-P3100 using xda premium
god_creature said:
Ketut @ awesome work with awesome guide.. U explained each n every step clearly for freshers.. N BTW do I need to update Blackhawk next kernel to 1.0..if yes, wiping cache n delvk is necessary before flashing? I am asking u cos I Dnt want to be in mess anymore.. I am happily enjoy dual boot environment.. Thanks again for all the effort..
Sent from my GT-P3100 using xda premium
Click to expand...
Click to collapse
Yes. Fixed the problem when installed CM 10.1 directly as 2nd ROM. No wipe needed.
Please let me ask a question here.
I have already asked in Philz's thread but no answer till now.
Can Philz restore backups made within cwm?
I already have some backups from cwm times and if Philz could restore them that would save me a lot of time. Of course I could just try and see, but that information would be usefull to have before starting in advance.
Please, ketut, any information on that?
Sent from my GT-P3110 using xda app-developers app
dimfil said:
Please let me ask a question here.
I have already asked in Philz's thread but no answer till now.
Can Philz restore backups made within cwm?
I already have some backups from cwm times and if Philz could restore them that would save me a lot of time. Of course I could just try and see, but that information would be usefull to have before starting in advance.
Please, ketut, any information on that?
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
Compatible: http://forum.xda-developers.com/showthread.php?t=2201860
ketut.kumajaya said:
Compatible: http://forum.xda-developers.com/showthread.php?t=2201860
Click to expand...
Click to collapse
Great!
It's a lot of pages. I can't find it right away, but your answer is enough for me! So, they are compatible.
I will try and report if necessary.
Sent from my GT-P3110 using xda app-developers app
This great work Ketut, thanks for giving us easy way to dual boot. Keep up the good job.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ketut, congrats on your new achievement !
Just one quick question : Can you post all the features (other than dual-boot ability) of this blackhawk-next-kernel on first post ? Or the features are still the same with this :
ketut.kumajaya said:
This is [BOOT IMAGE][GT-P31XX] KK-Boot - Custom boot image for stock 4.1.1/4.1.2 ROM and [KERNEL][GT-P31XX][JB][4.2.2]CyanogenMod 10.1 unofficial kernel 3.0.31 combination, plus cm-10.1-blackhawk commit on github:
Remove Samsung debugging code in ext4 filesystem, inline with omapzoom
Initializing Android USB depending on the rom type, big thanks to gokhanmoral. This is the key of single kernel. Multiboot support not so far, you can reuse my kernel for multiboot (if you can)
Compiler optimizations
Kernel without CGROUPS support
Using SLQB memory allocator
Decrease MPU, IVA, and GPU voltage
Adapt and fix codeworkx's sysfs for controlling pivot mode. This is the key of landscape kernel
Stop the spam from audio driver
An exprimental config, remove a lot of debugging config from kernel: 775MB RAM
Stock JB 4.1.1/4.1.2 ROM: Using a slim version of busybox (from gokhanmoral's ramfs for siyahkernel-sgs3), bash and nano binary, sysrw and sysro script removed. GPU clock @ 384MHz + 2D GPU rendering, stock ROM really need an overclocked GPU.
CM/CM based ROM: As usual, change ro.sf.hwrotation value from 270 to 0 in /system/build.prop will transform your device to landscape mode, a workaround fix for boot animation graphic glitch. GPU clock @ 307MHz + 2D GPU rendering + 16bit transparency + disabled dithering + purging assets allowed
/system/etc/init.post_boot.sh is yours kernel tuning template. But remember, do not force your system too much until you are sure that your device is able to handle it.
Flash this using the latest CWM, CWM Touch, Philz Touch, or TWRP at your own risk!
Click to expand...
Click to collapse
Thank you
distan7 said:
Ketut, congrats on your new achievement !
Just one quick question : Can you post all the features (other than dual-boot ability) of this blackhawk-next-kernel on first post ? Or the features are still the same with this :
Thank you
Click to expand...
Click to collapse
Same kernel, different ramdisk. Thanks for your support :good:
STOP PRESS: Update PhilZ Touch to 5.03.7 http://forum.xda-developers.com/showpost.php?p=39935850&postcount=89!
Oh good news my brother I am happy
Envoyé depuis mon GT-N7100 avec Tapatalk
Couple questions to ketut Please try to answer me - noobie
1) I can flash this for single rom, yes? It should be better than previous version?
2) I can still turn Tab on, press volume down button to boot into CWM?
3) How to turn off the boot menu? (I think I don't need it)
Andrev01 said:
Couple questions to ketut Please try to answer me - noobie
1) I can flash this for single rom, yes? It should be better than previous version?
2) I can still turn Tab on, press volume down button to boot into CWM?
3) How to turn off the boot menu? (I think I don't need it)
Click to expand...
Click to collapse
1. Yes as covered by Dual Boot FAQs. No.
2. Yes.
3. Can not be, maybe the next version. Reboot to recovery and bootloader may be removed for security reasons.
{
"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"
}
Unofficial build of CyanogenMod 11 (Android 4.4) for the HTC Desire C (Golfu)
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KITKAT), which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Working:
Camera
WiFi
Bluetooth
Mobile network
Camcorder
Video playback
VPN
Screenshot
Recent apps switching
Audio (playback/input/routing/headphones/etc)
SD card
NFC
All sensors (accelerometer, proximity sensor, etc. work)
GPS
Everything else, as long as it isn't listed as a bug
Major bugs:
No major bugs
Credits (in no particular order):
The CyanogenMod team
LegaCyMod
Armv6
cute_prince
sachinthomas
Testers for prompt testing
And all those who helped directly or Indirectly
XDA:DevDB Information
CM-11 For Golfu, ROM for the HTC Desire C
Contributors
kirmaniarslan, h1gh1
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
ROM Firmware Required: Rooted
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: 5
Stable Release Date: 2015-05-05
Created 2014-10-16
Last Updated 2015-05-05
Not working
- FM radio.
- Apps that expect newer libOMXVidEnc will not work, Skype is one example. Viber and WhatsApp are working.
- do not use stock browser for serious browsing, although it is working, it has bugs with adreno libs. For 2-step authentication on Google, it will do.
Upstream issues
SDCard not showing unmount option
Trebuchet crashing when you enable CM Home or Google Search as panel
Cyanogenmod stock camera app shows 4.5mp instead of 5 mp - camera works properly with other third party apps and takes 5MP pictures.
Sources: - cm-11.0 branches in each repo:
Device
Kernel
Vendor
Thanks:
CyanogenMod team, legacyMod & KonstaT, HTC Pico development team, TeamHackLg & everyone who's been working on CM11.
Downloads:
CM11 RC5 (194.45 MB)
Android File Host | BasketBuild
MD5: 63ff9995dad6d2f6798f5b6b8b1a8c11
Optional GAPPS:
http://forum.xda-developers.com/showthread.php?t=2779598(thanks @kodirovshchik for suggestion)
How to install:
You must update recovery with this one - TWRP 2.8.6.0 or this one Philz Touch 6.59.0 - ClockWorkMod 6.0.5.1- these two have SELinux support. Philz and CWM do not have support for F2Fs!
Install the recovery trough fastboot
- fastboot flash recovery recovery.img
Reboot to recovery from fastboot
- make a backup of your current ROM to SDCard
- wipe -> do a factory reset
- wipe -> advanced wipe -> select only system and wipe
- install zips (rom and gapps)
- reboot to bootloader
if you are updating from previous CM11, you can dirty flash -> just wipe /system in Wipe -> Advanced Wipe, and install rom and gapps. No guarantees here.
Install boot image
fastboot flash boot boot.img
install boot.img that is inside the ROM that you downloaded
do not do fastboot erase cache
As of RC5, ROM now supports both EXT4 and F2FS in a same installation, and there is an easy way to switch back and forth between full EXT4 and F2FS setup, or any partition layout you would like (why would someone want this, I do not know, but the option is there).
Switching to F2FS from EXT4:
- You must install TWRP 2.8.6.0 with F2FS support.
- install RC5 and gapps (optionally), flash boot.img and restart. Check that the ROM is working properly. Activate advanced reboot in developer options. Reboot to recovery.
- backup - make a nandroid backup of system, data and cache.
- wipe, advanced wipe - select system - change or repair file system - choose F2FS. Repeat this for data and cache.
- settings -> Check use rm -rf instead of format.
- restore -> this will restore your data to existing partitions without format.
- settings -> Uncheck use rm -rf instead of format.
- reboot
You will boot to full F2FS ROM, with all your data and settings intact. Check it out in terminal with
mount | grep f2fs
How to build:
Up to date sources on github. (one patch for legacyMod frameworks_av is missing, will update device tree soon)
1. Follow instructions on initializing a build environment up to a point of downloading the source code.
2. Initialize CyanogenMod 11 repo.
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
3. Add local manifest that downloads HTC Desire C device config, properties and kernel source from my github and few CM replacement projects from legaCyMod github.
Code:
curl --create-dirs -L -o .repo/local_manifests/local_manifest.xml -O -L https://raw.githubusercontent.com/high1/android_local_manifest/cm-11.0/local_manifest.xml
4. Sync source code.
Code:
repo sync
5. Update prebuilts
Code:
cd path-to/cm11/vendor/cm/
./get-prebuilts
6. Apply patches
Code:
path-to/cm11/device/htc/golfu/patches./apply.sh
7. Compile.
Code:
cd path-to/cm11/
. build/envsetup.sh
brunch cm_golfu-userdebug -jx
(x is number of your processor cores -+1)
'repo sync' to pull merged changes from upstream.
'make clobber' to clean the build environment.
Repeat step 7 to make a new build.
FAQ:
Q: I can't find developer options and performance settings, why?
A: Settings -> About phone -> Click 'Build number' several times
Q: I don't have reboot options in power menu, why?
A: Settings -> Developer options -> Advanced reboot
Q: Is ART runtime working?
A: Yes it is. Beware, it is not compatible with xposed framework.
Q: How to make fastboot and adb work with Windows 8.1? (Device enumeration failed error)
A: First, make sure you have this update installed - http://www.microsoft.com/en-pk/download/details.aspx?id=43515 . Unzip http://goo.gl/CAXglZ and merge it to your registry. HTC drivers must be installed, compatible with Windows 8.1 here: http://forum.xda-developers.com/showthread.php?t=2714921
Q: USB tethering does not work?
A: Here is a guide: Android USB Tethering In Windows 8.1
Changelog
3.5.2015 changelog:
- one ROM for both file systems - made multiple file system patch work on CM11, and update fstab and updater-script for that,
- fixed black screen in call - updated touchscreen and proximity driver from cyanogen_htc_msm8960 3.4 kernel, and updated board definitions, so that the proximity sensor is now working properly
- switched back to legacy OMX - camera recording is working, and the latest Viber is working properly. Skype is crashing due to old OMX libraries, but does not render the phone useless.
- using adreno libraries from TeamHackLGE - just for testing
- updated libqc-opt.so from TeamHackLGE repo - seems that this fixes some schedulers get stuck on lowest frequency.
- addes sioplus scheduler to kernel.
10.4.2015 changelog:
- released two separate ROMs, ext4 and full f2fs
- f2fs ROM got hand update for updater-script and fstab
- fixed errors reported when installing the ROM - updater-script has hardcoded filesystem, and this was the cause
- fixed the camera regression
7.4.2015 changelog:
Device tree:
- switched to HtcLegacy display-caf, which fixes high idle battery drain
- updated OMX libraries from TeamHackLG msm7x27a vendor repo - this fixes Viber, Skype etc, but video recording is broken
- switched to QCOM power HAL
- bluetooth vendor library is now in /vendor
- switched to Cyanogenmod frameworks_av
- cleaned up patches (down to only three and one replaced repo - this is almost pure CM11)
- switched to TWRP 5.1 branch, and made it compile with CM11 tree
- switched to QACT for audio lib
- compiling nightly again, as CM11 is EOL, and I think no new milestones will happen
- forcing high-end graphics is not default anymore
- moved adreno libs in vendor tree to vendor folder, removed one unneeded fil
Kernel:
- updated touch and proximity drivers from 3.4 kernel
- headset profile from 3.4 kernel
- added lz4 compression to kernel
- Update zram and zsmalloc up-to 3.17 kernel changes (zsmalloc now used instead of xvmalloc)
- enabled lz4 compression for zram
- restored audit support
- further various updates to kernel
20.2.2015 changelog:
- fixed brightness bug by keeping original framebuffer stack
- fixed memory bug (0.00B shown)
- added f2fs support to kernel
- added intelliactive, adaptive and smartassH3 governors, and updated interactive. Enabled all governors in kernel.
- added zen scheduler. Updated BFQ scheduler to v7r7. Enabled all schedulers in kernel.
- updates to block stack, faster I/O
- ROM built pre deoxed - installation will be longer, first boot will be much shorter
- moved all the proprietaries to vendor tree
- added F2FS support to ROM and recovery
15.12. changelog:
- fixed Bluetooth regression
- added surface texture patch
- updated prebuilts
7.12. changelog:
source synced to CM11 M12
switched to pico kernel, ION build
ported ION changes to golfu board
new graphics libraries, latest that support our board
ported golfu panel driver to pico kernel
switched to kernel XZ compression
switched to display-caf - TeamHackLG with patch
removed a lot of legacy repos - only frameworks_av needs to be replaced now
using CM11 chromium webview - applications that call evaluateJavaScript work now
updated touchscreen drivers
simplified camera build
added Philz touch recovery to ROM build
12.11. changelog:
- new wireless driver, ported from samsung kernel
- kernel changes, needed for new driver - new wireless_ath stack, imported compat folder, Makefile tweaks - do not build ath.ko for golfu
- fixes wifi tether
- fixes soft reboot
9.11. changelog:
Remaining audio routing issues are fixed, libaudio updated so no need for patching.
Call recording works
Solved freezing issues (need confirmation)
decreased wake up delay, enabled slow blur, increased ui responsivness
some other tweaks for sleep mode, limiting number of runnig apps
monitoring net usage on proper interface
removed custom wifi, updated wireless definitions and switched to Cyanogenmod private lib for ath6kl
kernel makefile optimizations - proper flags for our device
-O2 optimizations - kernel fits to boot.image so it should also improve speed
24.10. changelog:
Synced with latest CM11 nightly
Fixed video - camera recording, youtube
Disabled haptic feedback by default
Enabled call recording
23.10. changelog:
Fixed Wifi
Kernel with overclocking - capped to 600 at start, overclockable to 900 - One kernel for All!!!
Fixed stock browser with legacyMod patches
legacyMod prebuilts
18.10. changelog:
Fixed camera rotation (excluded definitions for 3M golfu, sensor mount angle is 0, and fixed sensor driver file in kernel - thx to Sachin Thomas)
Fixed media_profiles.xml partially - you can start the video, but it crashes on recording start
Fixed nfc - firmware was missing
Enabled swap to zRAM KitKat style
Re-enabled HTC performance lock, but only during boot
(Fixes yet to be uploaded with next beta)
16.10. changelog:
Android 4.4.4
First public build
A lot of changes and cleanups to the ramdisk and boardconfig
Added SELinux support to kernel
Made a working, stable recovery, first with repacked zImage and then source built
ROM made bootable
Fixed adb
Fixed SDCard
Fixed Bluetooth
Fixed Audio
Fixed RIL
Partially working camera
Added TWRP to ROM build process instead of CWM
Disabled HTC performance lock and limited frequencies on first boot so that one image is usable for all and devices do not crash
Enabled KSM by default
This all would not be possible without help - I looked up alot to KonstaT that makes CyanogenMod for ZTE Blade III, and a lof of this post is taken from his way of posting. KirmaniArslan helped to solve quite a few quirks, and posted patches actively, and started the development - his device tree was made bootable.
I expect logcats from all who will do testing, and hopefully we can fix the remaining bugs and let this device have fully working Cyanogenmod (Omni, Pacman, AOKP hopefully later). Also, with the release, you have full permission to use the source to build other ROMs, only requirement is that if you find a fix, you do a pull request at Github.
Regards, and enjoy the ROM as much as you can.
kirmaniarslan said:
BETA 1 : https://mega.co.nz/#!mBZhHKaZ!jQ7_vJ...F9zzpyvNla5fgQ
Kernel for BETA 1 : https://mega.co.nz/#!KURjUALa!Rj-nlM...A0I7LIq5Xdj2YQ
Click to expand...
Click to collapse
Ok. Enter decryption key. =)
Reserved for testbuilds
kodirovshchik said:
Ok. Enter decryption key. =)
Click to expand...
Click to collapse
Links updated.
So. As for me.
Adb doesnt work at first boot, so i can't get logcat. All logs what i have - TWRP log.
Cyclic reboot. It works for 2-3 sec and reboots. ANd i cant even look at settings or enable debugging. 2sec and reboot. One thing i'm shure its not from overheating =(
upd:
ok... boot in safe mode gives me 2 extra seconds.. and... there is no developers menu. it is locked. and i cant unlock it.
upd2: nope. i definitely can't attach rom Log and Ksmg.
kodirovshchik said:
So. As for me.
Adb doesnt work at first boot, so i can't get logcat. All logs what i have - TWRP log.
Cyclic reboot. It works for 2-3 sec and reboots. ANd i cant even look at settings or enable debugging. 2sec and reboot. One thing i'm shure its not from overheating =(
upd:
ok... boot in safe mode gives me 2 extra seconds.. and... there is no developers menu. it is locked. and i cant unlock it.
Click to expand...
Click to collapse
Have you wiped everything properly ?
kirmaniarslan said:
Have you wiped everything properly ?
Click to expand...
Click to collapse
idk coz in the HOWTO there is only "do a factory reset". What is the proper way?
Upd: for me it looks like overclock problem =)
kodirovshchik said:
idk coz in the HOWTO there is only "do a factory reset". What is the proper way?
Upd: for me it looks like overclock problem =)
Click to expand...
Click to collapse
Try the boot.img inside the ROM then. But it should not behave like that. Wipe the system along with the factory reset.
I'm having problems with TWRP v 2.8.0.0 recovery. I was using clokwork before and after flashing my log gets spammed with couldn't mount emmc. Adding full log
Adding link to pastebin, because for some strange reason I got error in forum that file was invalid
http://pastebin.com/iRgFm13z
Sorted out this issue, but rom seems to be stuck on bootloop.
Added logcat
doweeez said:
I'm having problems with TWRP v 2.8.0.0 recovery. I was using clokwork before and after flashing my log gets spammed with couldn't mount emmc. Adding full log
Adding link to pastebin, because for some strange reason I got error in forum that file was invalid
http://pastebin.com/iRgFm13z
Sorted out this issue, but rom seems to be stuck on bootloop.
Added logcat
Click to expand...
Click to collapse
Could you try image packaged with the ROM? Seems that I must leave HTC Performance boot lock, as a lot of phones crash.
h1gh1 said:
Could you try image packaged with the ROM? Seems that I must leave HTC Performance boot lock, as a lot of phones crash.
Click to expand...
Click to collapse
Thanks. Got it booted
doweeez said:
Thanks. Got it booted
Click to expand...
Click to collapse
OK. Will post another test kernel image once I fix the boot performance lock.
h1gh1 said:
Try the boot.img inside the ROM then. But it should not behave like that. Wipe the system along with the factory reset.
Click to expand...
Click to collapse
Ok. For me "How to install" must looks like:
1. Install the recovery trough fastboot
2. Reboot to recovery from fastboot
3. install zip
4. reboot to bootloader
5. Install boot image
6. reboot
Mb is is caused by S-OFF, but I rly need to flash kernel only after flashing zip. Work with "normal" kernel.
Upd1: Does ART works? Cause it looks like it works.
Upd2: OMG ART rly works. Can't belive it =)
kodirovshchik said:
Ok. For me "How to install" must looks like:
1. Install the recovery trough fastboot
2. Reboot to recovery from fastboot
3. install zip
4. reboot to bootloader
5. Install boot image
6. reboot
Mb is is caused by S-OFF, but I rly need to flash kernel only after flashing zip. Work with "normal" kernel.
Click to expand...
Click to collapse
Flashing the ROM does not affect boot partition, because of S-OFF. Order of instalation (boot image first) should not affect booting. I enabled zRAM kitkat style in latest build, as you requested - we are compliant with Google recommendations for low RAM devices now. I forgot to say, yes but ART is working without any problems, as long as apps work with it.
h1gh1 said:
Flashing the ROM does not affect boot partition, because of S-OFF. Order of instalation (boot image first) should not affect booting. I enabled zRAM kitkat style in latest build, as you requested - we are compliant with Google recommendations for low RAM devices now. I forgot to say, yes but ART is working without any problems, as long as apps work with it.
Click to expand...
Click to collapse
ART it's rly cool surprise =) Nice =)
As for S-OFF, i rly think u cant make changes with boot if u phone is S-ON. When u swith it to S-OFF u can make changes from recovery. Any way i have no other explanation, why order is important for me. i'll try to test it =)
UPD: is there any trick in win8 for adb? cause for me adb works only from my linux laptop.
kodirovshchik said:
ART it's rly cool surprise =) Nice =)
As for S-OFF, i rly think u cant make changes with boot if u phone is S-ON. When u swith it to S-OFF u can make changes from recovery. Any way i have no other explanation, why order is important for me. i'll try to test it =)
UPD: is there any trick in win8 for adb? cause for me adb works only from my linux laptop.
Click to expand...
Click to collapse
Yes, there is. Import this in your registry - you must have a patch with workaround installed, http://www.microsoft.com/en-pk/download/details.aspx?id=43515
extract reg file from attached zip and merge it to your registry.
I'm having problems with USB mass storage. First time when I click to turn it on, it unmounts sd card, but I'm not able to access sd-card file on PC. Second time I click loading loops forever.
Have anyone encountered similar problems?
doweeez said:
I'm having problems with USB mass storage. First time when I click to turn it on, it unmounts sd card, but I'm not able to access sd-card file on PC. Second time I click loading loops forever.
Have anyone encountered similar problems?
Click to expand...
Click to collapse
It's ums file setting, looks like it. I chose MTP as default, as mass storage requires mounting, unmounting etc... Will be fixed in the next build. Thx.
h1gh1 said:
It's ums file setting, looks like it. I chose MTP as default, as mass storage requires mounting, unmounting etc... Will be fixed in the next build. Thx.
Click to expand...
Click to collapse
MTP seems to work. It detects as HTC EVO 4G LTE .
CyanogenMod 12.1 is a free, community built distribution of Android 5.1 (Lollipop) which greatly extends the capabilities of your phone.
{
"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"
}
ROM Features:
Based on latest CyanogenMod 12.1 sources
Compiled with SaberMod 4.9 and JustArchi's Optimizations V4.1 for maximum performance
Full F2FS support - no mount issues during ROM updates
SELinux set to 'permissive' by default
Android default UID and GID for internal storage
(No more write issues after formatting sdcard!)
Slim and fast user build
Kernel Features:
Based on latest CAF kernel sources (LA.AF.1.1.c1)
Compiled with ArchiToolchain 4.9 and several Cortex-A9 optimizations
Overclocking up to 1.62 GHz
Underclocking up to 162 MHz for maximum battery life
User-customizable CPU Voltage driver (thanks to faux123)
Intelliactive and IntelliMinMax CPU governors (thanks to faux123)
In-kernel Thermal Driver (thanks to franciscofranco)
SIO and FIOPS IO schedulers
F2FS (Flash-Friendly File System) support (Performance comparison vs EXT4)
FauxSound support for maximum audio gain control (thanks to faux123)
Latest TWRP recovery, including a Materialised TWRP theme by z31s1g
Be aware that improper usage of kernel features can cause serious damage to your device!
Only use the stuff above if you know what you're doing!
In agreement with the GPL, you can find the sources and defconfig used to compile this kernel right here.
Known Issues:
Please keep in mind that CM12.1 sources are still work in progress. As a result, some features may be broken or only partially working.
That's why I decided to only list device-specific issues below.
Below ~60% battery, the displayed battery level will reduce significantly on rebooting. This is a known issue with all AOSP based ROMs.
After switching to a new battery, I noticed this behavior is related to automatic battery calibration and directly affected by the health of your phone's battery.
Disclaimer:
By downloading and installing this ROM, you agree that I cannot be held responsible for any damage caused to your device while installing or using it. Please keep in mind that it's YOU who chose to do these modifications to your device!
Installation:
Make sure your bootloader is unlocked - if not, follow this guide: Link
First installation? Flash the boot.img from ROM zip via Flashtool (use Fastboot mode!)
Boot into TWRP recovery
Do a factory reset and wipe system partition
Flash latest ROM zip (check "Downloads" section)
Flash suitable GApps for CM12.1 or CM12
Flash latest SuperSU from here: Link
Reboot
Downloads:
Final CM12.1 version: Link (Last updated: Jan 08, 2016)
Final CM12 version: Link (Last updated: April 05, 2015)
CM default su binary: Link (Don't flash if you're using SuperSU!)
Uninstaller zip: Link (Restores default storage permissions)
Credits:
CyanogenMod Team for their active development on the CM12.1 sources.
updateing for helping me with lots of compilation issues and initial bugfixing.
JustArchi for his awesome optimizations!
Changelog:
- 20160108 (final build):
Latest CM12.1 changes
Fixed the lags in power save mode by slightly increasing the cpu clock
.Thanks to everyone for using and supporting my work! It's been a great time with you all!
- 20151115:
Latest CM12.1 changes
Optimized system for better RAM performance
Enabled CM Performance Profiles support
Reduced minimum screen brightness
Reverted Toast UI to AOSP default
- 20151010:
Latest CM12.1 changes
Reverted SONY lockscreen clock to AOSP default
Reverted softkeys to AOSP default
Removed Xperia fonts
- 20150929:
Latest CM12.1 changes
Added Xperia softkeys
Fixed missing TWRP boot splash screen
- 20150912:
Latest CM12.1 changes
- 20150824:
Latest CM12.1 changes
Recreated NeoKernel with latest CAF sources from here.
Updated ArchiDroid's Optimizations to V4.1
ROM is now built with SaberMod 4.9 toolchain!
Re-colored recoveryboot LEDs. Got sick of this ugly purple!
Replaced stock TWRP ui with latest Materialised Play theme from here. Credits to z31s1g for the great theme and ElArchibald for his help!
Recoveries present on FOTAkernel will be ignored from now on - fixes installation issues caused by broken CWM or outdated TWRP versions
Disabled Dex-Preoptimization to allow greater and easier customizability, as well as more free space on system partition
Fixed Xposed framework causing bootloops
Fixed GPS for some users (Got rid of QUIPC)
- 20150808:
Latest CM12.1 changes
- 20150726:
Latest CM12.1 changes
Added medium L2 clock rates to NeoKernel, should improve battery life
.NOTE: The device tree used to build this ROM is now fully open-source!
- 20150620:
Latest CM12.1 changes
Fixed delayed PIN screen on boot
Added SONY styled lockscreen clock from here. (Credits to idid idamrep!)
Included all stock Xperia fonts in the ROM
- 20150603:
Latest CM12.1 changes
Enabled Multiuser UI with 3 maximum users
Fixed Google Play Services repeatedly force closing
Updated TWRP sources to latest
- 20150516:
Latest CM12.1 changes
Minor fixes and optimizations in device source
- 20150424:
Latest CM12.1 changes
Update to Android 5.1.1
- 20150419:
Latest CM12.1 changes
Added unlimited call log mod from here
Fixed backup issues in TWRP (using updated sources now)
- 20150412:
Latest CM12.1 changes
Reverted updates in F2FS sources (should fix the random bootloops)
Fixed non-working sensors (added prebuilt sensors.msm8960.so)
- 20150405 (CM12.1 build):
Initial release of CM12.1 (Android 5.1)
Merged all kernel features and optimizations from CM12
Updated TWRP to 2.8.6.0
.NOTE: A full wipe is recommended, but not required!
- 20150405 (CM12 build):
Final CM12 build (Android 5.0)
Latest CM12 changes
Added SIO and FIOPS io schedulers
Added in-kernel Thermal Driver (thanks to franciscofranco)
Updated F2FS sources in kernel
Fixed the network disconnects when initiating a call
Reverted to TWRP 2.8.4.0 to fix some ui bugs
- 20150329:
Latest CM12 changes
Compiled with JustArchi's ArchiDroid Optimizations V4
Updated CAF kernel source
Additional kernel optimizations for Cortex-A9
Disabled debug flags in kernel
Switched to ArchiToolchain 4.9 for kernel
Switched to SaberMod 4.8 toolchain for ROM
Removed USB "Mass Storage" and "Charge only" modes
- 20150321:
Latest CM12 changes
- 20150314:
Latest CM12 changes
- 20150309:
Latest CM12 changes
(Introduces a bug: Clock in statusbar disappears on reboot. Hide/unhide statusbar clock in Settings as a workaround)
Removed FM Radio - Have a look at this one!
- 20150303:
Latest CM12 changes
Fixed the segmentation fault when trying to mount/remount
Most likely fixed the volume errors some people encountered
Reverted to AOSP LLVM compiler (QCOM one needs more work)
Minor bugfixes - FM Radio is still WIP for now
- 20150301:
Latest CM12 changes
Added FM Radio
Replaced AOSP LLVM compiler with Qualcomm one, optimized for krait cpus (thanks to MusterMaxMueller)
ROM is now built with Linaro 4.8 instead of SaberMod 4.8
Kernel is now built with Linaro 4.9 instead of SaberMod 4.10
Updated kernel source to latest CAF
Minor changes and improvements in device tree
- 20150222:
Latest CM12 changes
- 20150215:
Latest CM12 changes
FolderMount and "sd issue" fixed - ROM is now using android default uid for sdcard0
Added intellimm and intelliactive cpu governors (thanks to faux123)
Added ultra low CPU clocks to kernel (162 and 270 MHz)
F2FS (Flash-Friendly File System) support
Latest Faux Sound features
Graphite Loop Optimizations in kernel
O3 optimized GPU drivers
Updated TWRP to version 2.8.5.0
Some changes and cleanup in installer zip
.NOTE: From this version on, you will have to flash my neo-uninstall.zip before switching ROMs!
- 20150207:
Latest CM12 changes
- 20150201:
Latest CM12 changes
Removed CMUpdater
- 20150124:
Latest CM12 changes
- 20150118:
Latest CM12 changes
- 20150115:
Latest CM12 changes
Fixed the 3G issue that was present in version 20150112
Updated TWRP to version 2.8.4.0
- 20150112:
Latest CM12 changes
Merged official CM device repos
Added "Charge only" USB mode
Other minor fixes and improvements
- 20150104:
Latest CM12 changes
- 20141228:
Latest CM12 changes
New recovery splash screen, best looking with this Material TWRP theme
Fixed volume key not working when screen off
Optimized boot image size
Minor bugfixes and improvements
- 20141222:
Latest CM12 changes
Update to Android 5.0.2
Compiled the whole rom with O3 flags
Enabled Overclocking up to 1620 MHz in kernel
Added user-configurable undervolting interface
Updated kernel source
Enabled USB Mass Storage
- 20141216:
Latest CM12 changes
Notification LED fixed
Working TWRP recovery included (thanks to colonel_lp)
New lights hal (open source instead of proprietary one)
Switched to SaberMod toolchain
Added some kernel cflags, optimized for Cortex-A9 cpu architecture
- 20141208:
Initial release
If you like my work and want to support me, please hit that thanks button, give some positive feedback or consider a small donation for my efforts.
XDA:DevDB Information
CyanogenMod 12.1, ROM for the Sony Xperia V
Contributors
WhiteNeo
Source Code: https://github.com/WhiteNeo-?tab=repositories
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod 12.1
Version Information
Status: No Longer Updated
Created 2014-12-09
Last Updated 2016-01-08
Screenshots:
Video:
Here's another video by taaviu that gives you an impression of Android L.
FAQ:
How to update to latest build?
1. Reboot to recovery
2. Flash latest rom zip
3. Flash latest gapps linked in OP
4. Flash SuperSU
5. Wipe Cache & Dalvik Cache
6. Reboot
How to safely uninstall this rom?
1. If you were using F2FS, revert to EXT4 before uninstalling!
2. Reboot to recovery
3. Flash neo-uninstall.zip
4. Proceed with the installation steps of your new rom
Should you face storage issues with your new rom, run the following Terminal commands:
Code:
su
chmod 777 /mnt/media_rw/sdcard0
chown 2800:2800 /mnt/media_rw/sdcard0
chown -R 2800:2800 /mnt/media_rw/sdcard0
Troubleshooting:
I can't create folders in internal storage!
Follow the instructions on updating to latest build. While flashing, my rom will apply its required storage permissions automatically.
Alternatively, you may simply run the following Terminal commands:
Code:
su
chmod 777 /mnt/media_rw/sdcard0
chown 1023:1023 /mnt/media_rw/sdcard0
chown -R 1023:1023 /mnt/media_rw/sdcard0
Camera any Gallery won't save my photos!
Follow the instructions on updating to latest build. While flashing, my rom will apply its required storage permissions automatically.
Alternatively, you may simply run the following Terminal commands:
Code:
su
chmod 777 /mnt/media_rw/sdcard0
chown 1023:1023 /mnt/media_rw/sdcard0
chown -R 1023:1023 /mnt/media_rw/sdcard0
I can't move apps to sdcard!
Moving apps to internal storage is quite buggy and discouraged. I recommend repartitioning your device with the instructions below.
Advanced Modifications:
Switching to F2FS:
First of all, make sure you're running homebuild version 20150215 or later!
1. Copy all important files from internal storage to the external sdcard
2. Reboot to recovery
3. Do a full backup (make sure to select external sdcard as target location)
4. Disable MTP in "Mount" menu
5. Go to "Wipe" > "Advanced Wipe" menu
6. Check "System", then tap "FS Options" and "Change FS"
7. Select "F2FS", then swipe to apply the change
8. Repeat steps 5 and 6 for "Data" and "Cache" partitions, as well as internal storage
9. Navigate to TWRP Settings and check "Use rm -rf instead of formatting"
10. Restore your previous backup
12. Reboot to system
13. Restore your copied files from external sdcard
14. Reboot
Reverting to EXT4:
1. Copy all important files from internal storage to the external sdcard
2. Reboot to recovery
3. Do a full backup (make sure to select external sdcard as target location)
4. Disable MTP in "Mount" menu
5. Go to "Wipe" > "Advanced Wipe" menu
6. Check "System", then tap "FS Options" and "Change FS"
7. Select "EXT4", then swipe to apply the change
8. Repeat steps 5 and 6 for "Data" and "Cache" partitions, as well as internal storage
9. Navigate to TWRP Settings and check "Use rm -rf instead of formatting"
10. Restore your previous backup
12. Reboot to system
13. Restore your copied files from external sdcard
14. Reboot
Repartitioning your device:
Note:
Up to 14GB of free space on external sdcard might be required to perform the steps below! (Should be less if your internal storage isn't completely bloated )
The value XXXX used below has to be replaced with a calculated number and varies depending on your desired space. I recommend 5120, as it's a decent balance between general data storage (used for most apps) and space on internal storage for apps with bigger data (games). Refer to step 13 of this link if you want to calculate your own partition sizes.
1. Copy all important files from internal storage to the external sdcard with the following terminal command:
Code:
rsync -P -a /sdcard /ext_card/sdcard0/
2. Reboot to recovery
3. Do a full backup (make sure to select external sdcard as target location)
4. Navigate to "Mount" menu, disable MTP and unmount all partitions listed there
5. Navigate to "Advanced" > "Terminal Command" and type the following code:
Code:
parted /dev/block/mmcblk0 print
This command should display some text like this:
Code:
Model: MMC M8G2FB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 2228kB 2097kB TA
2 2228kB 3801kB 1573kB Boot
3 3801kB 5374kB 1573kB Boot2
4 6291kB 27.3MB 21.0MB Kernel
5 27.3MB 28.3MB 1049kB TZ
6 29.4MB 32.5MB 3146kB modemst1
7 33.6MB 36.7MB 3146kB modemst2
8 37.7MB 40.9MB 3146kB fsg
9 40.9MB 46.1MB 5243kB ramdump
10 46.1MB 54.5MB 8389kB ext4 apps_log
11 54.5MB 71.3MB 16.8MB FOTAKernel
12 71.3MB 1359MB 1288MB System
13 1359MB 1621MB 262MB Cache
14 1621MB 3769MB 2147MB Userdata
15 3769MB 7818MB 4050MB SDCard
We're going to remove Userdata and SDCard partitions, so check if these partitions also have the numbers 14 and 15 on your phone.
6. Type the following terminal commands to proceed with resizing the partitions:
Code:
parted /dev/block/mmcblk0 rm 14
parted /dev/block/mmcblk0 rm 15
parted /dev/block/mmcblk0 mkpartfs logical ext2 1621 [B]XXXX[/B]
parted /dev/block/mmcblk0 name 14 Userdata
parted /dev/block/mmcblk0 mkpartfs logical ext2 [B]XXXX[/B] 7818
parted /dev/block/mmcblk0 name 15 SDCard
7. Leave the terminal screen and go to "Wipe" > "Advanced Wipe" menu
8. Check "Data", then tap "FS Options" and "Change FS"
9. Select "EXT4" or "F2FS", then swipe to apply the change
10. Repeat steps 8 and 9 for internal storage (is named "sdcard" in this menu)
11. Restore your previous backup
12. Restore your backed-up files from external sdcard with the following terminal command:
Code:
cp -a /external_sd/sdcard0/* /sdcard/
13. Reboot
14. Enter the following terminal commands to fix storage permissions:
Code:
su
chmod 777 /mnt/media_rw/sdcard0
chown 1023:1023 /mnt/media_rw/sdcard0
chown -R 1023:1023 /mnt/media_rw/sdcard0
Finally I'll test soon
Aria.A97 said:
Finally I'll test soon
Click to expand...
Click to collapse
Thanks, make sure to give some feedback here.
Upload will be finished in around 15min.. Time to do a Titanium Backup.
WhiteNeo said:
Thanks, make sure to give some feedback here.
Upload will be finished in around 15min.. Time to do a Titanium Backup.
Click to expand...
Click to collapse
Yeah, of course Some minutes ago I saw it was uploaded, but only 72 MBs
Aria.A97 said:
Yeah, of course Some minutes ago I saw it was uploaded, but only 72 MBs
Click to expand...
Click to collapse
I know.. It seems like AFH had some problems with uploading.
By the way, rom is online.
With the whole "no working recovery included", does it mean that we cant flash one to FOTAkernel afterwards?
By the way, you are a freaking champion for releasing this ROM, and thanks for all the work you put into making our phones better
Swidilator said:
With the whole "no working recovery included", does it mean that we cant flash one to FOTAkernel afterwards?
By the way, you are a freaking champion for releasing this ROM, and thanks for all the work you put into making our phones better
Click to expand...
Click to collapse
Just doing what I can.
However, I gotta mention that I would never have come that far without @updateing.
Once more huge thanks for your help!
FOTA recovery should work, as the phone boots properly into recovery. You may give this a shot, I remember having seen a FOTA TWRP version by championswimmer in Cross Device Forum. :good:
The problem is that the recovery is not CWM anymore. CyanogenMod team is developing their own recovery at the moment. And that one doesn't work (yet)
Download complete. Gapps server was really slow. For me it took 13 minutes to download only Gapps. Now I'm doing a full nandroid backup.
Edit 1 : Booted. WiFi, Bluetooth and Cellular works fine. I'll report more soon
Edit 2 : Report after 40 minutes of use : Fully stable. Other stuff including camera and root access work completely fine. I just had 1 setting FC at first. This ROM is smooth enough (not as much as expected Lool)
These are all of bugs I found :
1. Setting - bluetooth menu - when searching, that circle animation has some problems
2. Setting - Wireless & networks - More - Cellular networks - Carrier settings makes "com.android.phone" FC. (Maybe it's carrier related )
3. The most important bug I've found (not for me, but it can be a disaster for some others ) is Notification/Battery LED does not work at all.
By the way, I have functional CM Recovery. I was able to boot into recovery by selecting reboot recovery power menu. CM Recovery appeared. Even touch is working fine but there is no backup/restore related option.There was just apply update from zip and reboot.
After all, really thanks for your work it's awesome, as always
WhiteNeo said:
Just doing what I can.
However, I gotta mention that I would never have come that far without @updateing.
Once more huge thanks for your help!
FOTA recovery should work, as the phone boots properly into recovery. You may give this a shot, I remember having seen a FOTA TWRP version by championswimmer in Cross Device Forum. :good:
The problem is that the recovery is not CWM anymore. CyanogenMod team is developing their own recovery at the moment. And that one doesn't work (yet)
Click to expand...
Click to collapse
Nice work . But can u make dis work on xperia T
Aria.A97 said:
Download complete. Gapps server was really slow. For me it took 13 minutes to download only Gapps. Now I'm doing a full nandroid backup.
Edit 1 : Booted. WiFi, Bluetooth and Cellular works fine. I'll report more soon
Edit 2 : Report after 40 minutes of use : Fully stable. Other stuff including camera and root access work completely fine. I just had 1 setting FC at first. This ROM is smooth enough (not as much as expected Lool)
These are all of bugs I found :
1. Setting - bluetooth menu - when searching, that circle animation has some problems
2. Setting - Wireless & networks - More - Cellular networks - Carrier settings makes "com.android.phone" FC. (Maybe it's carrier related )
3. The most important bug I've found (not for me, but it can be a disaster for some others ) is Notification/Battery LED does not work at all.
By the way, I have functional CM Recovery. I was able to boot into recovery by selecting reboot recovery power menu. CM Recovery appeared. Even touch is working fine but there is no backup/restore related option.There was just apply update from zip and reboot.
After all, really thanks for your work it's awesome, as always
Click to expand...
Click to collapse
Thanks for testing
I think the carrier settings fc and led stuff is device related. Will try to fix it in next build. :good:
Booting in recovery works fine, but flashing does not work.
I'm sure CM team will fix this soon.
Installed in the morning.
Had no crushes yet, no bugs in animation that I`ve seen. However, power consumption is dramatically high compared to stock 4.3 JB. Most time processor runs at 1.5ghz.
WhiteNeo said:
Thanks for testing
I think the carrier settings fc and led stuff is device related. Will try to fix it in next build. :good:
Booting in recovery works fine, but flashing does not work.
I'm sure CM team will fix this soon.
Click to expand...
Click to collapse
So the problem is caused by CM recovery?
Allen Hu said:
So the problem is caused by CM recovery?
Click to expand...
Click to collapse
Exactly. :good:
Hi
It's my first time to post something so I don't know if I'm doing it right
So
First of all thank you for the ROM and the great work keep it up :good:
Second I found some other bugs Dunno if it's apps releated or something in the ROM itself
1. Gestures keyboard doesn't work
2. Google Play services keep asking to update it "and it's up to date"
3. Tap and hold doesnt work "quick toggles" in notification centre. and is it CM feature ?
An other question
When A new release is out can I flash CM11 kernel to flash the new release since I flashed it using CWM I was on CM11
P.S I didnt wipe data or system wipe just backed up the old ROM and flashed this one didn't want to re-install all apps etc..
Very good looking rom. Flashing right now, got first bootloop....because i flashed cm12 kernel. That was my fault. Now im already setting my device up.
Looks like LTE aslo working.
Any good ideas how to make navibar smaller? Xposed wont work with 5.0 as i know.
Shady_BlackSn0w said:
Hi
It's my first time to post something so I don't know if I'm doing it right
So
First of all thank you for the ROM and the great work keep it up :good:
Second I found some other bugs Dunno if it's apps releated or something in the ROM itself
1. Gestures keyboard doesn't work
2. Google Play services keep asking to update it "and it's up to date"
3. Tap and hold doesnt work "quick toggles" in notification centre. and is it CM feature ?
An other question
When A new release is out can I flash CM11 kernel to flash the new release since I flashed it using CWM I was on CM11
P.S I didnt wipe data or system wipe just backed up the old ROM and flashed this one didn't want to re-install all apps etc..
Click to expand...
Click to collapse
Bugs 1 and 3 are related to CM sources. Number two is most likely caused by your dirty installation. (Which I don't recommend, by the way)
Thats the plan.. Until CM recovery works we gotta fastboot NeoKernel and flash the update from its included recovery. :good:
taaviu said:
Very good looking rom. Flashing right now, got first bootloop....because i flashed cm12 kernel. That was my fault. Now im already setting my device up.
Looks like LTE aslo working.
Any good ideas how to make navibar smaller? Xposed wont work with 5.0 as i know.
Click to expand...
Click to collapse
LTE is working? That's great news! :good:
Can anyone confirm this?
No idea how to resize the navbar, but I'm sure CM team will add a customnization option soon.
Temporary Fix for play service
Disable app notifications in settings
Again thank you @WhiteNeo :good:
WhiteNeo said:
LTE is working? That's great news! :good:
Can anyone confirm this?
Click to expand...
Click to collapse
I Confirm. LTE working.
Thank You for the excelient work :good:
[ROM][UNOFFICIAL][6.0.1][E6653/E6603] CyanogenMod 13 for the Sony Xperia Z5 [ALPHA]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CyanogenMod 13 for the Sony Xperia Z5 E6653 and E6603
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase
performance and reliability over stock Android for your device.
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be
used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps).
CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Before you start
This ROM is only for the E6653 and the E6603
Code:
*
* Your warranty may be voided !
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
Special Thanks
@CTXz for getting the ball rolling on CyanogenMod for Z5 series and stemming the lion's share to get this working
@oshmoun for providing fixes ASAP
@AndroPlus for providing a great kernel that works with many recoveries
@moonbutt74 for reminding me that smashing your device can provide a solution
@sub77 for teaching me how to work with QCOM (I was on exynos before)
@Joeisgood99 for providing a solid working TWRP-3.0.0.0 build until we had our own
@bazhip for providing a well working twrp 2.8.7.0 for restoring until we had our own
@alphatact1cs has a great overview on lots of topics for the Z5 device family
@auras76 for his great Custom ROM
@infected_ for his experience
Thanks to @mpro420 for help to get Viper4Android working !
Thanks to @jimRnor for Project DiVA SoundMod !
The Sonyxperiadev team for releasing their sources to the public
SonyAOSP team
SonyCM team
Sony Xperia (community) devs
And ofcourse the entire CyanogenMod team!
(Known) Issues
Video Recording
Bluetooth (keeps restarting) (might be fixed, needs feedback + testing)
Camera Colors (can be circumvented by using specific apps CameraNext Mod )
Camera Focus & Sharpness (driver issue, probably since it uses Xperia Z (original) drivers but different lenses ?)
Camera lowlight pictures (might improve with release of Sony's "Experimental AOSP Camera" for the Z5 series, porting of other Framework + Stock Cam app; partially needs DRM magic)
Camera Focus (even with VCM2 actuator changes focus is still kind of murky)
Fingerprint sensor (might work depending on build date of ROM)
Lag after booting up device (Will resolve: lock screen after boot and waiting a few seconds)
Long bootup times & less smoothness with "stock" (prebuilt) kernel
What can not be fixed, changed - aka WONTFIX - NOTOURPROBLEM
There might be potential speed issues with Class 10+ microSD cards not properly being "tuned", in that case switch to slower cards or RMA it which should hopefully solve it. There is a possibility to force slower speeds on cards but that is not really the optimal solution with ultra speed cards and needs further investigation. Samsung (EVO/EVO+) cards, Transcend cards and a few others UHS-I(+) and faster are affected.
What has been Fixed
Horizontal color lines and color glitches during bootup
Gapps
Sudden Lag after some time
NFC
Odd calling numbers
In-call mic
Sound on calls
Camera button
Microphone
Thermal regulation
Red flashy frames
RIL (SIM detection)
Dex pre-optimization
Camera
Sensors
Crash after locking device
microSD access
Flash light / Torch
Full brightness (should be fully working)
Gapps (permissions issues) [occurs occasionally and should be circumvented by full-wipe approach (incl. internal storage)
Hang/Loop during boot stage (should be circumvented by full-wipe approach (incl. internal storage)) (use Custom Kernel, under investigation)
High battery drain [~ 10%-20% per hour] when dirty-flashing system (fastboot -S 256M flash system system.img), make sure to have data backed up, then format /data ; OTA updates should be fine though [need feedback] ); causes are: dirty flashing, certain apps, ROM issues, etc.
Guides/Instructions
Unlocking Bootloader
Warning! The following procedure may void your warranty and will wipe EVERYTHING
Visit Sonys Official Bootloader Unlock guide (Details to all the risks you are taking are located on their site)
After Unlocking your bootloader you can proceed with the next steps
Steps on how to Fastboot, Flashmode, Recovery, Emergency/Force Poweroff
@alphatact1cs has a great overview on lots of topics for the Z5 device family
over at [GUIDE] Sony Xperia Z5 - UNLOCK / ROOT / TWEAKS - OS 5.1.1 / 6.0
There go to the [GUIDE] StockROM section , open it up and under #GENERAL you'll find everything you need to know.
Setting up fastboot and how to use it
For windows users
Please checkout this guide on how to use fastboot on windows
If you prefer to keep a low footprint instead of installing the whole Android SDK, take a look at its thread
[TOOL]Minimal ADB and Fastboot [8-28-15]
For Linux users
Installation
Debian based distros (Debian, Ubuntu etc.)
Open a terminal and enter the following :
Code:
sudo apt-get update && sudo apt-get install android-tools*
Confirm the installation by either hitting enter or typing y
Gentoo based Distros (Gentoo, Funtoo, Sabayon, Scientific Linux)
Once you're in a terminal, enter the following:
Code:
emerge dev-util/android-sdk-update-manager
Other distros (Arch, Fedora, Open Suse etc.)
Please find the apropriate packages to install android fastboot tools for your distro
How to use
Open a terminal in the location your .img file is located or cd into that directory like this:
Code:
cd <path to your directory that contains the .img files>
Replace <path to your directory that contains the .img files> with your actuall path
To boot temporarely into a .img (ex recovery) use the following command (replace <your.img> with your .img file) :
Code:
fastboot boot <yourfile>.img
To flash a kernel image enter the following (replace <your.img> with your .img file):
Code:
fastboot flash boot <your.img>
To flash a recovery image enter the following (replace <your.img> with your .img file):
Code:
fastboot flash recovery <your.img>
To exit fastboot enter :
Code:
fastboot reboot
How to install CM 13
Above all - do a Backup of ALL your data
When I write ALL I mean ALL (this includes the data on your micro SD card,
don't come whining to me if you lose your wedding photos/videos, kids' photos/videos or other important stuff !
For optimal experience I'd recommend my built custom kernel (quicker boot times, higher reliability, more tweakability)
General, in-depth instructions
Download one of the newer Z5 AndroPlusKernels v20+ by @AndroPlus from his official website (Scroll down and select Z5, then on AndroidFileHost search for Z5_AndroPlusKernel_Permissive_v2 (v20 - v23) and download it)
Extract the flashable zip-file e.g. Z5_AndroPlusKernel_Permissive_v23.zip
Download our TWRP 3.0.1-0 build for the Z5)
Download the appropriate gapps from below (Can be downloaded on your device)
Download the CM 13 Zip for the Z5 from below (Can be downloaded on your device)
Move the GAPPS zip and the CM 13 to your Z5 if you haven't downloaded them on your device
Power Off your Z5 and wait about 10-15 seconds to make sure it's off
To enter fastboot mode hold VOL UP and while holding VOL UP connect your device to your pc via cable
When the notification LED has turned blue you are in fastboot mode
On your PC flash the boot.img that has been extracted from the Z5_AndroPlusKernel_Permissive_v23.zip using fastboot (
Code:
fastboot flash boot boot.img
)
Now flash twrp-3.0.1-0-E6653-20160403.img by using fastboot (
Code:
fastboot flash recovery twrp-3.0.1-0-E6653-20160403.img
)
Once both of those images have been flashed you can reboot the device like so:
Code:
fastboot reboot
Quickly pull the usb cable from the computer (you can leave the other end in the phone's port)
When booting up wait for the notification light to turn yellow at the Sony logo
Once it has turned yellow, you will enter TWRP by pressing VOL UP (or VOL DOWN - up works more reliably)
If you've missed the step above, reboot your device and try the step above again
Alternatively you can force turn off the device via: Power Button + Volume Up , then turn it on again via Power Button
If TWRP asks you to enable read and write, swipe to continue
Go to settings and lower the max brightness to the minimum or one of the lower levels to preserve energy
In TWRP make a full backup to the microSD in case you want to revert back to stock.
After it has finished, in this case Reboot -> System.
Copy over the TWRP folder from the external microSD to your computer (reason: you might not have access to your external SD or have to reformat it
Thank Microsoft, Sony, etc. for that: "Stock" ROM uses texfat , AOSP, CM, etc. uses exfat, ext4, ntfs
The files on the microSD might get corrupted (filesystem problem) or the microSD going crazy (I already had both cases)
Now Power on your phone and follow the steps again to get into TWRP
Swipe to continue (?)
select Wipe > Advanced Wipe
Now ONLY tick Dalvik/ART cache, System, Cache and Data
WARNING! THE NEXT STEP WILL WIPE YOUR SYSTEM AND DATA, MEANING YOU WILL DELETE YOUR STOCK SONY SYSTEM AND ALL YOUR APPS
(You already DID a Backup of your files so nothing to worry about)
Once you've ticked the correct boxes, swipe to wipe
Once the wipe is complete, return to the main menu and select Install
Locate and select your CM 13 Zip
Select "Add more Zips" and add your GAPPS package and finally swipe to install
Once the installation succeeded you can select "Reboot System"
Wait for CM 13 to boot up (Can take several minutes)
Enjoy CM13
OPTIONAL: You can remove your TWRP backup that is located in the TWRP folder if you feel like you will no longer need it
How to ROOT
In CM 13, enable the developer options
Select Root access
Select Apps Only (Or Apps and ADB if you use ADB)
Done
How to disable the Thermal Manager
Before we start I want to set a few questions and warnings. Disabling the thermal manager will cause you device to run slightly hotter, do this at your own risk.
Let's start out with why you would want to disable the thermal manager. At this point it's not recommended to disable the thermal manager as it has been fixed. However some people still want the max performance out of their device. The average heat without the thermal manager will be roughly the same, if not less compared to the stock ROM with it's thermal manager enabled.
So why is the thermal manager even included if it the device runs mostly fine without it. As most of you already know, the Snapdragon 810 (MSM8994) has overheating problems. The first CM boot after flash is responsible for optimizing apps and android and can become extremely resource hungry at that point. Due to that, the device can heat tremendously! Not only can that cause a panic reboot but it can also damage your device in rare cases. To avoid that issue a thermal manager shrinks down process and slowers the boot animation (That's why the CM logo may lag at first boot).
Enough said, let's get going..
To disable the thermal manager you must do the following :
First enable root access (See "How to ROOT" guide)
Open the CM file manager
Go to settings > General Settings > Access Mode
Select root acess mode
Go back to the file manager
Swipe from left to right or press the menu button in the upper left corner
Select Root folder
Open the folder/directory called etc
Delete thermanger.xml
Reboot
Done
How return back to stock via TWRP backup
Reboot your device
Wait for the notification light to turn purple at the Sony logo
Once it has turned purple, you will enter TWRP by pressing VOL UP or VOL DOWN
If you've missed the step above reboot and try again
If TWRP will ask you to enable read and write, swipe to continue
In TWRP select restore and select your backup, then swipe to restore
Once the restore is done you can select "Reboot System"
If your device hangs at the Sony wave boot animation, force shut down and power your device up again.
Downloads
Latest recommended CyanogenMod release for the Sony Xperia Z5 E6653/E6603 :
6.0.1_13.0-20160626-UNOFFICIAL-sumire_r46_alternate
Latest recommended Kernel for the CM release for the Sony Xperia Z5 E6653/E6603 :
6.0.1_13.0-20160626-UNOFFICIAL-sumire_r46_alternate
All my releases can be found here on : Android File Host
TWRP for CM/AOSP-based ROMs:
[TWRP][E6653/E6603/E6633/E6683] 3.0.2 , for CM/AOSP ROMs
Gapps (Select ARM64 > 6.0) :
Open Gapps
[GAPPS][6.0/5.1/5.0][arm/arm64] Official Slim GApps ( recommended )
XPosed for Android:
[OFFICIAL] Xposed for Lollipop/Marshmallow (Installer in Thread)
XPosed Releases
SuperSU in SystemMode:
SuperSU in System-Mode [v2.65-STABLE] [v2.68-BETA] [v2.70-WIP/BETA-RC]
Sound MODs:
[Sound Mod ][Project DiVA][6.0 MM_Z5 series] KitaKami sound mod Prototype 01 (any effect ?)
A.R.I.S.E. Sound Systems - Auditory Research in Sound Enhancement - Exodus RC8.3 (works (RC8.3))
[SOUNDMOD][JB/KK/LP/MM]Project Yume Final, You are the Legend (needs testing)
[SUPER MOD][4.4+/6.0/N][ v7.5.2 ] XTREMEMusic™ THE SOUND THAT YOU'VE NEVER HEARD! (NOT working (7.4), needs testing of 7.5*
[Audio Mod] eXtremeBeats Aural Maximizer (needs testing)
[APP]Material ViPER4Android 2.4.0.1[Light/Dark][LP/MM]
mpro420 said:
1.)zip file install via twrp.
2.)reboot to system.
3.)enable v4a "write to sdcard" permission in setting/apps/viper4android/permission.
4.)open v4a and gain root permission.
5.)install driver for v4a.
6.)reboot system.
7.)[emoji39]
Click to expand...
Click to collapse
Questions and bug reporting
The following questions will be ignored
Inappropriate questions
Requests for other devices
Forced orders, EX. : "PLS FIX!!!!!!"
ETA's
Often repeated questions or requests usually by the same user
Requests that are out of CM's framework (Ex. Adding Sony Apps)
How to report a bug/issue
Explain exactly what happens
Mention a log if you can (Please use hastebin or any other paste site to keep the thread clean)
If you can't mention a log, explain as precise as possible when, why and where it occurs!
Source Code
All Source Code can be obtained from:
https://github.com/Sony-Kitakami
https://github.com/SonyAosp
https://github.com/sonyxperiadev
https://github.com/CyanogenMod
https://github.com/zachariasmaladroit/android_kernel_sony_msm8994_kitakami_r2
Kernel Source code can be obtained from : zachariasmaladroit/android_kernel_sony_msm8994_kitakami_r2
We gladly accept any developers that are willing to contribute to this project! Please PM @CTXz if you are interested in joining this project!
Build from Source
http://forum.xda-developers.com/xperia-z5/general/guide-build-cm13-source-z5-z5c-z5p-t3357040
Screen Shots (Z5 compact)
XDA:DevDB Information
CyanogenMod 13 for the Sony Xperia Z5 E6653 and E6603, ROM for the Sony Xperia Z5
Contributors
CTXz, Moonbutt74 , zacharias.maladroit , oshmoun , infected_
Source Code:
https://github.com/Sony-Kitakami
https://github.com/SonyAosp
https://github.com/sonyxperiadev
https://github.com/CyanogenMod
https://github.com/zachariasmaladroit/android_kernel_sony_msm8994_kitakami_r2
ROM OS Version: 6.0.x Marshmallow
ROM Firmware Required: 6.0 Recommended
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2016-04-11
Last Updated 2016-06-28
Changelog
Code:
2016/05/06
[LIST]
[*]Dual SIM support (ROM) [COLOR="Red"][B][WIP][/B][/COLOR]
[*]Dual SIM support (Kernel) [COLOR="Red"][B][WIP][/B][/COLOR]
[*]smoother brightness (automatic & manual), lower default and manual brightness
[*]weather provider support (CM)
[*]thermal manager improvements (CM)
[*]potential stability-fixes (CM)
[*]brightness dimming disabled (once temperature raises)
[*]VCM2 camera actuator (presumably working focus) == feature complete camera [LED torch still needs work]
[*]adb enabled from the start (diagnostics at this early ROM stage)
[*]upstream ROM + Kernel changes
[*]
[*] Sim-specific change: add DSDS (dual sim) detection script that starts second ril-daemon
[*]
[*] Custom Kernel changes:
[*] Intelliplug + Intellithermal by default [[B][COLOR="Red"]stability testing[/COLOR][/B]]
[*] added Quick Wakeup, PowerSuspend,
[*] added AdrenoIdler
[*] CPU and general Kernel optimized compiler flags
[*] re-enabled efficient WorkQueue [[B][COLOR="Red"]stability testing[/COLOR][/B]]
[*] re-enabled nop idle governor for CPUIDLE driver [[B][COLOR="Red"]stability testing[/COLOR][/B]]
[*]
[/LIST]
2016/04/19
- LiveDisplay (CM upstream) should work more reliably and should not cause instabilities and (boot)loops anymore
- torch should work now (ROM)
- changes, improvement to Bootup (Kernel side) - should make prebuilt kernel more reliable
2016/04/17 [suzuran]
- Fixed Brightness
- Fixed Torch
- Fixed Double Tap 2 Wake
- Added CPU core optimization
- Added USB gadget support
- Synced with the latest CM sources
-----------------------------------------------
* For devs
- Added Kitakami patcher to manifests
2016/04/15
- Full brightness range + maximum brightness (ROM + Kernel)
- KCAL support (Kernel)
- alucard, elementalX, zzmoove governors (Kernel)
- upstream sync (Kernel), perhaps better, more reliable WiFi
- more battery efficiency during video playback (Kernel), [needs testing, lags ?]
- adreno (GPU) governor, lower default frequency (Kernel), perhaps lower battery consumption, [needs testing, lags ?]
- vibrator intensity control (Kernel) [needs testing]
- some more battery efficiency tweaks (Kernel)
- NTFS, exFAT filesystem support (for microSD) (Kernel)
- tweaks and reliability improvements (Kernel)
- Driver wakelock control (Kernel)
- NEON/FPU compiler optimizations (Kernel)
- improved Hotplug reliability and stability (Kernel)
2016/04/12 [suzuran]
- Fixed sdcard recognition
- Updated binaries to v4
- Released CM build guide
- Synced with newest sources
2016/04/11
- CM 13 For the Z5 E6653 Released
2016/04/10
- CM 13 For the Z5 Premium E6853 Released
2016/04/05
- Fixed GApps
- Partially fixed Bluetooth
- Synced to latest CM sources
2016/03/27
- Fix thermal manager lag
- Fix NFC
- Updated kernel configs
- Added ffmpeg codecs support
- Synced with newest CM sources
-------------------------------------------
* For devs
- Cleaned up suzuran and satsuki tree
- > Moved common media configs to kitakami common tree
- > Moved acdb files to vendor tree
2016/03/24
- Fix In-call Mic
- Add support for the E5803
- Add option to boot into recovery (On purple LED at Sony logo press VOL UP or VOL DOWN to enter recovery)
- Update Thermal manager
- Merge latest AOSP kernel commits
- Sync to newest CM source
2016/03/22
- Fix microphone
- Add settings for camera button
- Add settings for volume rockers
- Fix sound on calls
2016/03/20 - RIP TonyStark, you were a great moderator and we'll all miss you.
- Added Thermal regulation to avoid overheating problems
- Fixed Red flashy frames
- Fixed RIL (SIM detection)
- Fixed Dex pre-optimization
- Fixed Camera
- Fixed Sensors
- Fixed Crash after locking device
2016/03/18 - CM 13 For the Z5 Compact E5823 Released
Reserved 02
Reserved 03
(and another one)
You know the drill:
the most important part is the phone functionality (well, it's a smartphone ),
please test that after you've done the initial set-up and tell, whether it works
Finally get there....
Great job man!
Hope there will be dual sim support asap.
Nice jobe, I'll wait for a more stable version to test it
keep up the good work
best regards.
Well done again to Sony Kitakami Developer Organization!
Sooooo much time and effort represented in those CM13 github projects. Total Respect.
Nuf said.
JerryLaiHMmmmmm said:
Finally get there....
Great job man!
Hope there will be dual sim support asap.
Click to expand...
Click to collapse
I've taken a look but haven't figured out yet on how to make it work,
if there are any developers out there with DSDS (dual sim) devices, interested on getting this working and read this - please take a look at it
Thanks !
korom42 said:
Nice jobe, I'll wait for a more stable version to test it
keep up the good work
best regards.
Click to expand...
Click to collapse
Okay
Thanks
Joeisgood99 said:
Well done again to Sony Kitakami Developer Organization!
Sooooo much time and effort represented in those CM13 github projects. Total Respect.
Nuf said.
Click to expand...
Click to collapse
Thanks ! <3
Will you be making a guide on building this rom from source? And of course, thank you for all your hard work we all greatly appreciate it.
Uclydde said:
Will you be making a guide on building this rom from source? And of course, thank you for all your hard work we all greatly appreciate it.
Click to expand...
Click to collapse
Very soon mate
Uclydde said:
Will you be making a guide on building this rom from source? And of course, thank you for all your hard work we all greatly appreciate it.
Click to expand...
Click to collapse
Build from Source
The guide on how to build your own Z5 ROM will be posted once we feel like this ROM is ready enough
Click to expand...
Click to collapse
Take a look at the source and the repos, the guides are out there ...
... you got a PM
CTXz said:
Very soon mate
Click to expand...
Click to collapse
beat me to it
zacharias.maladroit said:
[ROM][UNOFFICIAL][6.0.1][E6653/E6603] CyanogenMod 13 for the Sony Xperia Z5 [ALPHA]
if you loose your wedding photos/videos,
Click to expand...
Click to collapse
If it's "loose", put some glue on it!
lol
m3ta said:
If it's "loose", put some glue on it!
lol
Click to expand...
Click to collapse
lol - I get those mixed up quite a bit, sometimes due to typos, too
Status Update:
Uploaded new img files and a flashable zip-file for TWRP (haven't tried it out myself, currently evaluating Resurrection Remix)
Sorry for the inconvenience so far
Give it a try, if you dare
Okay, so I followed the steps for "General installation", and the rom is surprisingly smooth. The only issue I've noticed that isn't addressed in the original post is that vibration intensity is WAY higher than in the stock rom. Like it's actually pretty loud. I know it's a minor issue compared to some of the other things, but I'm just throwing that out there. I'll point out anything else I find.
Absolute legend! Thanks man. I'll get to testing once i get home off this drilling rig
Uclydde said:
Okay, so I followed the steps for "General installation", and the rom is surprisingly smooth. The only issue I've noticed that isn't addressed in the original post is that vibration intensity is WAY higher than in the stock rom. Like it's actually pretty loud. I know it's a minor issue compared to some of the other things, but I'm just throwing that out there. I'll point out anything else I find.
Click to expand...
Click to collapse
Thanks for testing
Actually it already was higher on AOSP, if recall correctly, but I'll ask the other devs if they noticed something out of the ordinary
Thanks
atanu89 said:
Absolute legend! Thanks man. I'll get to testing once i get home off this drilling rig
Click to expand...
Click to collapse
Thanks
Thanks for this great rom, the only problem i encounter is that my phone keeps stuck in first startup (cyanogenmod logo) and that keeps going i force my phone to switch off after 45 minutes, is there something i do wrong i followed the in depth guide
Sovjet-Command said:
Thanks for this great rom, the only problem i encounter is that my phone keeps stuck in first startup (cyanogenmod logo) and that keeps going i force my phone to switch off after 45 minutes, is there something i do wrong i followed the in depth guide
Click to expand...
Click to collapse
That partially is caused by the "stock" built kernel,
you can see whether is improved by flashing my custom kernel.
One observation (according to @moonbutt74 afaik) led to the conclusion that the upstream (from sonyxperiadev) setting of coherent_pool=8M doesn't match with Sony's ("Stock ROM") setting of coherent_pool=2M,
and does no good for startup time (and reliability ?).
Another factor (like in most AOSP-based ROMs, Kernels) is that the kernel was built with a less tuned toolchain (gcc),
can't directly explain though why does leads to exactly that behavior.
Tl;dr:
Give the custom kernel a try - the "stock" kernel should work but for some reason sometimes it does not
custom has exfat + ntfs support to make microSDs work reliably and other things
Thanks
Kernel v4.4
and
Android Open Source Project 8.0
Oreo
for
Samsung Galaxy Tab 10.1
(p4wifi / GT-P7510)
(p4 / GT-P7500)
(p4tmo / SGH-T859)
{
"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"
}
I have ported this device to Android Linux kernel v4.4. This is the official Android kernel for Oreo. This ROM requires a completely new kernel and recovery. Read everything before use.
Recovery - TWRP BigSys
TWRP BigSys will use a different partition layout in order to have a larger system partition size.
Flashing TWRP-Bigsys with odin/heimdall will overwrite the cache partition. Format the cache partition it in recovery after flashing with odin/heimdall.
Partition layout:
Code:
Before:
[ system (578MB) | cache (448MB) | data (16GB/32GB) | hidden / preload (300MB) ]
After:
[ system (1026MB) | data (16GB/32GB) | recovery extra (16MB) | cache (284MB) ]
TWRP BigSys is not compatible with any ROM before Oreo.
BigSys partitioning is based on BigPart for Motorola Xoom.
Kernel - Linux v4.4
This is based on the official Android common kernel. The drivers and platform specific parts ported from the original 3.1.10 kernel.
Working
Code:
Tegra 2 platform
Downstream video/avp
Dynamic voltage and frequency scaling
USB (ConfigFS)
- no host mode
Voltage Regulators / Battery / Charger
tps6586x
stmpe811
max17042
p4_battery
nct1008
Display Panel
cmc623
Touch Digitizer
mxt1386
Audio
wm8994
3.5mm jack
voodoo sound driver
Wifi
bcm4330
Bluetooth
bcm4330
GPS
bcm4751
Sensors
mpu3050: gyroscope
kxtf9: accelerometer
ak8975: compass
bh1721fvc: light sensor
Haptics
isa1200
Misc
Samsung misc partition. (Stores reboot mode and proprietary control bits)
Samsung LPM (off mode charging)
Will not work
Code:
3G/Cellular modem
xmm6260
tegra usb phy hsic
- No mainline kernel driver for this USB interface
Cameras / Flash
s5k5ccgx
s5k5bbgx
- Incompatible camera stack
HDMI
sii9234
Samsung 30-pin connector
keyboard dock, dongles, accessories
Functional differences
Code:
Enable force usb charging at kernel boot (rather than android init).
Add haptic vibration strength.
ROM - Android 8.0 Oreo
The ROM is AOSP based.
It is one ROM and recovery for p4wifi (GT-P7510), p4 (GT-P7500), and p4tmo (SGH-T859) since 3G/cellular will not work in the kernel. There is no difference between the two devices other than the cellular modem.
Customizations:
Advanced reboot menu
NEON emulation
Apollo music app
Working / Not working:
See the list under the kernel section.
First Install
Backup all data to a location off the device.
Install and boot into TWRP BigSys
Format system partition
- Wipe > Advanced Wipe > Check "System" > Swipe to Wipe
Reboot to TWRP BigSys
Install ROM
- (optional) Install GApps
- (optional) Install root
See post #2 on how to report problems
Updating
Install ROM
Downloads
ROM / Recovery
Browser - decatf-chromium
GApps - Open GApps
Known Issues
Known kernel 4.4 issues:
ak8975 compass orientation not reporting data
- test: CPU-z sensors tab shows no data
Wifi chip/firmware crash:
- Connection drops and will not reconnect.
- Low reproducabiliy.
- Bug is known to occur on all tested bcmdhd drivers except stock ICS and espresso10 bcmdhd driver.
- Workaround: Turn off wifi. Turn on wifi.
[*]Battery drain in power off:
- Device is not actually powering off.
- Low reproducabiliy.
- Possible causes:
- tps6586x regulator does not power off (due to i2c transfer errors).
- Hard lock up when CPU1 is offline and wifi sdio bus is on.
- host1x syncpt stuck. - test1:
- Proper power off: Press power button for 2 seconds to power on.
- Improper power off: Press power button for 8 seconds to power on. - test2: Reboot to recovery hangs after OS shutdown instead of rebooting to recover.
Other known issues:
Android OS stuck at boot logo:
- Cause 1: The HIDL HALs not starting properly
- Cause 2: System services die and loop forever
- Workaround: Reboot device
FAQ
Will X feature work?
- I have ported everything I can to the new kernel. Anything not mentioned is not going to work.
3G / Cellular?
- The Tegra USB driver in mainline kernel does not support the USB interface which connects the modem.
Camera?
- The camera devices are not working on the mainline kernel. The camera blob hasn't worked right since Lollipop anyways.
Can the old 3.1.10 kernel be used on Oreo?
- The old kernel is not working on Oreo.
Can the 4.4 kernel be used on previous ROMs?
- No.
Will this kernel work on Galaxy Tab 8.9?
- No.
How to return to stock partition layout.
Install a non-BigSys TWRP.
Format system and cache partition.
Reboot to TWRP
Change Log
Code:
20181011
- android-8.1.0_r48
- Linux 4.4.160
20180814
- android-8.1.0_r42
- Linux 4.4.147
20180416
- android-8.1.0_r19
- Linux 4.4.128
- Disable Android Go configuration
- Add back cache partition
- Fix a potential issue blocking wifi suspend
- Fix an issue with audio not working after suspend
- Fix bluetooth gpios
- Correct a voltage regulator configuration
20180316
- android-8.1.0_r16
- webview 65.0.3325.144
- Signature Spoofing
- Linux 4.4.121
- mainline mfd/m8994 driver
20180213
- Fix SOC (core) process ID 2 initialization
- Add BFQ iosched
20180206
- android-8.1.0_r10
- Linux 4.4.115
- webview 64.0.3282.123
20180110
- android-8.1.0_r6
- Linux 4.4.111
- Night Light feature
- Android Go configuration
- Fix DVFS issues
- Fix 3.5mm headphone plug issues
20171117
- android-8.0.0_r28
- Linux 4.4.98
- local_manifest changes:
device/samsung/p4-common
1095462 p4-common: init: set schedutil rate limit to 30000us
5153c33 Revert "p4-common: init: interactive governor"
0b90b12 Revert "power: enable interactive and interactive boost"
8489850 Revert "p4-common: set interactive governor permissions"
a95ade0 Revert "power: set interactive governor target loads"
d557892 configstore: set vsync phase offsets
881361f p4-common: disable samsung hwc fix
3f1308f p4-common: sched fifo on UI and RenderThreads
260c9e9 p4-common: overlay: change recents thumbnail svelte to limit cache
acfcdcd power: set interactive governor target loads
221576e p4-common: set interactive governor permissions
c8d553b power: enable interactive and interactive boost
ba7e0f6 p4-common: init: interactive governor
e6b1d5c Revert "p4-common: disable wifi direct"
3b2e521 Revert "hwc: move eglswapbuffers from blob into hwc wrapper"
5075a0b hwc: move eglswapbuffers from blob into hwc wrapper
frameworks/base
53cc0b0 hwui: don't use eglSwapBuffersWithDamageKHR
vendor/decatf
a4bef77 set_rt_prios.sh: Move mmc0/dhd_dpc priority into kernel
88a52a6 set_rt_prios.sh: lower wifi task priority and nice value
40db629 Add set_rt_prios.sh
20171109
- Fix CMC623F initialization
20171107
- Support more eMMC chips for BigSys
Acknowledgments
mainlane for donating a device after my original tablet broke.
digetx - downstream tegra video driver, Tegra USB ConfigFS, various work on Tegra devices in mainline.
BigPart developers for devising this method of partitioning.
Donate
Donate to me.
XDA:DevDB Information
Kernel 4.4 & Android 8.0 Oreo, ROM for the Samsung Galaxy Tab 10.1
Contributors
decatf
Source Code: https://github.com/decatf/
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Alpha
Created 2017-10-15
Last Updated 2018-10-11
Error reporting guide:
Saying "it doesn't work" will not get your problem solved. Save and upload the system logs from your device so that I can see what happening on your device.
How to save system logs from within Android:
Root the device.
Install SysLog.
Reboot the system.
Reproduce the problem.
Open Syslog app and save the Kernel Log and Main Log.
Send me the log files stored in /sdcard/Syslog.
Share the files on Google Drive or another similar service.
Then PM me a link to the files. Please describe exactly what the issue is.
The kernel log from the previous boot is stored in memory. If the device or kernel crashes then retrieve the previous kernel log from recovery.
How to retrieve the previous kernel log in recovery:
Advanced
File Manager
Navigate to /proc/last_kmsg
Copy File
Navigate to /sdcard/
Select Current Folder
Swipe to Confirm
Getting logs though ADB:
- Beginner’s Guide to the Android Debug Bridge
- (Basics of ADB) For Beginners
...
Add feature to new kernel
Would it be possible to add in the kernel the neccessary things for pelya usb keyboard. Google search for pelya usb keyboard and there is a github with all the code needed to be inserted into the kernel to make the usb keyboard work.
Hi,
this is the log, I'm not sure whether I've done everything correctly..
Can I flash this rom on over the existing 20171005 version? Thanks.
dookie23 said:
Can I flash this rom on over the existing 20171005 version? Thanks.
Click to expand...
Click to collapse
Yes. It is the same ROM. Only the kernel is different.
This not meant for regular use. It only posted in order to get kernel logs and feedback on the issues in the first post. I will not maintain this kernel for regular use.
@decatf
my panel seems to be the lsi one so I'm afraid my log is rather useless for you?!
hojnol said:
@decatf
my panel seems to be the lsi one so I'm afraid my log is rather useless for you?!
Click to expand...
Click to collapse
There are different CPU variants too. Hence point #2 and #3.
decatf said:
Yes. It is the same ROM. Only the kernel is different.
This not meant for regular use. It only posted in order to get kernel logs and feedback on the issues in the first post. I will not maintain this kernel for regular use.
Click to expand...
Click to collapse
Hi @decatf,
Thanks very much for doing this. Attached are the logs. The processor has no problem switching to different clock frequencies.
System was booting fine with 3.18 on my P4, please find the output of cmdline and clk_summary attached.
Kind regards, mistersixt.
I will try to test my tab on weekend
It has an issue rendering text, but nothing a reboot can't fix, aside that it's working fine.
I cann't upload files, so I'll send you a PM with syslogs.
Thanks for your time.
Rom works ok, Xposed bootloops, screen turns on and off.
I can OC CPU to 1,5GHz with no problem.
Updated first posted with Oreo ROM, kernel, and recovery.
Nobody sent any logs with the CMC623F panel so that remains untested.
Hi decatf. I tried testing the kernel when you first posted it but I couldn't get past boot loops. After restoring a nandroid back up, I follwed thw instructions for a clean install with the following esult:
Backup all data to a location off the device.
Install and boot into TWRP BigSys
Format system partition
- Wipe > Advanced Wipe > Check "System" > Swipe to Wipe
Reboot to TWRP BigSys
Install ROM
- (optional) Install GApps
- (optional) Install root
E1001: Failed to update system image.
Updater process ended with ERROR:7
Error installing zip file '/sdcard/aosp-8.0-p4wifi-20171106.zip'
tiberian41 said:
Hi decatf. I tried testing the kernel when you first posted it but I couldn't get past boot loops. After restoring a nandroid back up, I follwed thw instructions for a clean install with the following esult:
Backup all data to a location off the device.
Install and boot into TWRP BigSys
Format system partition
- Wipe > Advanced Wipe > Check "System" > Swipe to Wipe
Reboot to TWRP BigSys
Install ROM
- (optional) Install GApps
- (optional) Install root
E1001: Failed to update system image.
Updater process ended with ERROR:7
Error installing zip file '/sdcard/aosp-8.0-p4wifi-20171106.zip'
Click to expand...
Click to collapse
Get the recovery log:
- Advanced > Copy Log
decatf said:
Get the recovery log:
- Advanced > Copy Log
Click to expand...
Click to collapse
Many thanks decatf
tiberian41 said:
Many thanks decatf
Click to expand...
Click to collapse
Your device has a different eMMC chip and partition locations than my device. I had not expected this. The BigSys partitioning is only coded to work when it sees the expected partition layout to convert.
It only means that I need to write some code to handle whatever different eMMC chips there are. So you'll have to wait for now until that's done.
OK, cool. Thanks very much decatf. :good:
decatf said:
Your device has a different eMMC chip and partition locations than my device. I had not expected this. The BigSys partitioning is only coded to work when it sees the expected partition layout to convert.
It only means that I need to write some code to handle whatever different eMMC chips there are. So you'll have to wait for now until that's done.
Click to expand...
Click to collapse