{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
YOU MUST BE ON THE HAIRYBEAN 2.31 JB 4.2.1 BOOTLOADER VERSION 10.6.1.27.1 AND TWRP 2.6.3.1+ OR CWM 6.0.4.6+ BEFORE FLASHING THIS ROM. SEE UPGRADE INSTRUCTIONS BELOW IF YOU ARE UNSURE
You must do a full wipe in recovery if coming from another ROM base. Do not do a full wipe from the bootloader. Don't forget to do a Nandroid Backup first and give the ROM 10 mins to stabilise!
Features and Tweaks
This ROM is based from CM11 AOSP sources
Based off cm-4.4-20140901-crombikk4.4.2-tf300t source by lj50036
Full Aroma Installer for main rom including choice of 3 kernels and ROM2SD and DATA2sd support
CM11 kernel built from CM11 source by lj50036
Remixed _thatv8 kernel with CM11 ramdisk - repacked by sbdags
Remixed Grimlock kernel with CM11 ramdisk - repacked by sbdags - experimental
DPI Size: 160 (TF300 recommended stock fonts), 148 (Small fonts), 132 (Tiny fonts)
Launchers: Trebuchet, Google Experience Launcher, Apex , Nova
Boot Animations: CM Circle of Fire, CM Color Circle, Nexus Phase Beam, Cyanogen Stock
Gapps (updated by sbdags to Google latest apks and libs) flashed from separate package
Misc Apps: ESFile Explorer, Adobe Flash, AdAway, Titanium Backup, DropBox, Keyboard Manager
Tweaks: File system and performance optimised, Init.d support!, Zip Align, Force GPU Rendering, Browser2RAM
Continued Best Support of any ROM!
Warning - experimental tweaks
[*]Option to enable / disable data journaling on /data during install - CAN CAN CAUSE DATA LOSS IF SUDDEN SHUTDOWN OR CRASH
[*]Option to enable / disable fsync during install - CAN CAN CAUSE DATA LOSS IF SUDDEN SHUTDOWN OR CRASH
Change Log
cm-11.0-20140901-crombi-kk-RC2-tf300t Kitkat 4.4.4rc2 source by lj50036
Change Log
20140906 changes
- Rebuilt from latest CM11 4.4.4rc2 Kitkat - CROMBi-kk source - maintained by lj50036!
- Merged rom from 2 sources to introduce universal installer for 4 devices
- Updated device ID for TF201 which should fix wifi issues
- Updated options with TF700 and ME301, kernels + Device IDs!
- Dynamic fsync properly enabled on Grimlock kernel when fsync disabled selected in installer
- Made Google Calendar install by default as too many apps rely on it
- Updated Google Chrome to version 36.0.1985.135
- Updated Google Maps to version 8.3.1
- Updated Google Search to version 3.6.14
- Updated YouTube to version 5.9.0.13
- Updated ESFileExplorer to version 3.2.0
- Removed DropBox as bloatware (30MB!) - still available on the Play Store
- Removed Google Plus as bloatware (33MB!) - still available on the Play Store
- Removed alternate stock browser as no longer required
- Set default options to sbdags recommended for best performance
20140811 changes
- ROM is now Release Candidate 2! RC1 cleared private testing.
- ROM Version is CROMBi-kk_RC2 KitKat-4.4.4rc2-CM11-DEODEX
- Added my Intergalactic Ultra Touch (TM) settings to ROM Super snappy now
- Updated the Grimlock CM11 kernel to version 2 - thanks hardslog
- Changed the dalvik vm optimisation to reduce heap closer to stock as I think Garbage Collection wasn't happening frequently enough and when it did it took too long
- WiFi scan interval reset to 180
- Changed Zip Align script to a more recent version and added SQL Lite tweaks
- Can't see benefit of B2R script so default is off now
- Browsers now have their own section in installer
- Dolphin Browser with Adobe Flash both moved to system apps
- Tidied up gapps package from PA Gapps
- Updated Google Music to version 5.6.1617P
- Updated Google Maps to version 8.2.0
- Updated Google Hangouts to version 2.1.317
- Updated Google Chrome to version 36.0.1985.131
- Updated Google Core Services to version 5.0.89
- Updated Apex Launcher to Version 2.5.0
- Updated ESFileExplorer to version 3.1.9.1
- Updated GravityBox to 3.2.5
- Removed phab7 from xposed modules (no longer works on 4.4.x)
- Removed betterbean theme
- Added Android-L theme and Light / Dark variants
- Rebuilt from CM11 4.4.4 Kitkat - CROMBi-kk source - maintained by lj50036!
- Fixed the settings - staus crashing
- Fixed the screen not shutting off when closing the lid when docked - thanks psudeke!
- Lowered GPU values for TF201 users which should stop tearing and glitches
- Doubled the fling values for extra screen responsiveness
- Updated permissions to 4.4.4 CM11 set in updater script
- Repacked latest CM11 kernel with init10 functionality for ROM2SD/DATA2Sd and F2FS support
- Added latest Grimlock CM11 kernel v1.0 for the TF300 - thanks Hardslog
- Added Google Chrome as an option to install to /system/app
- Added option to remove the Stock Browser from /system/app
- Added Viper4Android Music FX as an option to replace CM DSP Manager
- Rom has SuperUser enabled by default now
- More virtual machine dalvik tweaks to speed things up
- Updated Apex Launcher to version 2.4.1
- Updated YouTube to version 5.7.41
- Updated Google Maps to version 8.1.1
- Updated Google Plus to version 4.4.3.69327528
- Updated Google Search to version 3.5.16
- Updated Google Music to version 5.6.1609P
- Updated Google Hangouts to version 2.1.311
- Updated Google Core Services to version 5.0.84
- Updated DropBox to version 2.4.2
- Updated Apex Launcher to version 2.4.0
- Updated Nova Launcher to version 3.0.1
- Updated Gravity Box to version 3.2.4
- Updated ESFileExplorer to version 3.1.8
- Beta - Tweaked Touchscreen sensitvity to the max for a very responsive experience
20140512 changes
- Rebased off latest CM11 source
- Kernel installer algorithm cleaned up to allow rom2sd, data2sd and f2fs selection management
- Compiled static busybox for /system/boot which fixes preinit issues for data2sd and rom2sd - thanks _that for your help
- Fixed f2fs on internal and external not working with data2sd (bug in fstab and installer)
- More fixes to f2fs installer routines and preinit scripts - added combinations of ext4 and f2fs
- Fixed _that wifi and bluetooth module compatibilty problems with _that kernel
- Changed the init mount point for f2fs to use the discard option on internal data only
- Cleaned up installer script
- ROM2SD and DATA2SD now working with normal CROMBi-kk on internal!
- Updated grimlock kernel to 2.4 for both TF300 and TF201 - thanks hardslog
- Updated ME301 compatibility packs included OC from hardslog
- Updated 2 new animations (red and blue) from psudeke
- Updated Google Calendar to version 201404014
- Updated Google Core Services to latest version
- Updated Google Plus to version 4.3.1.63038142
- Updated Google TTS to version 3.0.11
- Updated Hangouts to version 2.1.0
- Updated ESFileExplorer to version 3.1.3
- Updated DropBox to version 2.4.1
- Updated Dolphin Browser to verison 10.3.1
- Updated Google Maps to version 8.0.0
- Updated Google Search / Now to version 3.4.16.1149292
- Updated YouTube to version 5.6.36
- Updated Apex Launcher to version 2.3.3
- Updated Titanium Backup to version 6.1.5.5
- Updated Xposed Framework to version 2.5.1
- Updated Gravity Box to version 3.1.0
- Updated Google Music to version 5.5.15110.1148372
- Added inverted blue CM Theme as it's rather pretty
20140318 changes
- Fixed CM11 kernel not installing correctly from Aroma
- Removed TeleServices.apk to stop fc on boot in com.android.phone
20140317 changes
- Rebuilt from new base from lj50036 - Includes dock fixes (java) from CM11 source
- Fixed com.android.phone force close issues
- Fixed Grimlock kernel installing incorrect modules
- Fixed _thatv8 kernel with updated init and init.cardhu.cpu.rc for better cpu mode support - thanks ebildude123
- Fixed installer so hopefully users won't have an issue with addon.d scripts
- Fixed the CM11 backup and restore scripts not running as ro.cm.version was missing CM11
- Fixed : ROM2SD now correctly maps internal partitions to /datai, /systemi and /storage/sdcardi
-----ROM2SD still only works with a 4.2 JB ROM on internal
- Fixed : DATA2SD now offered again - currently uses _that v8 kernel
- Terminal Emulator lib file only installed when option is chosen in installer
- Added NTFS and extFAT support to stock based kernels
- Added Dolphin Browser and JetPack with FlashPlayer in installer as this is the only way to use flash in KitKat right now
- Updated Stock Browser Icon to Asus 4.3 version
- Updated Nova Launcher to version 2.3
20140315 changes
- Rebuilt from new base from lj50036 - Includes dock fixes (java) from CM11 source
- Repacked _thatv8 kernel with updated init and init.cardhu.cpu.rc for better cpu mode support
- Repacked Hunds 3.4.5 kernel with LetMeKnow's Extreme Tweaks
- Fixed installer so hopefully users won't have an issue with addon.d scripts
- Fixed the CM11 backup and restore scripts not running as ro.cm.version was missing CM11
- Fixed : ROM2SD now correctly maps internal partitions to /datai, /systemi and /storage/sdcardi
-----ROM2SD still only works with a 4.2 JB ROM on internal
- Fixed : DATA2SD now offered again - currently uses _that v8 kernel
- Terminal Emulator lib file only installed when option is chosen in installer
- Added NTFS and extFAT support to stock based kernels
- Added Dolphin Browser and JetPack with FlashPlayer in installer as this is the only way to use flash in KitKat right now
- Updated Stock Browser Icon to Asus 4.3 version
- Updated Nova Launcher to version 2.3
- 20140315 GApps Package updated. See post 2 for changelog
20140314 changes
- Updated Adobe Flash version to hacked version to test with 4.4
- Updated Adaway to version 2.8.1
- Updated Terminal Emulator to version 1.0.58
- Build.prop edit to increase scroll sensitivity
ro.min.fling_velocity=30000
ro.max.fling_velocity=60000
20140312 changes
GApps Package updated. See post 2 for changelog
20140309 changes
- lj50036 has rebased the Rom from CM11 source. No more CMB reliance
- Repacked all 3 kernels so up to date with CM11 changes
- Added Cyanogen Stock Bootanimation as option
- Inverted calendar removed and replaced with stock Google one
- Split GPU rendering into 2 parts - Need to test differences:
Part 1 forces GPU Rendering for 2D operations in the build.prop
Part 2 forces software rendering to be disabled thus the GPU must be used
- Cleaned up updater-script as not using CM Backup / Restore functionality for now
- Added tweaked Browser.apk back in as well as media codecs and lib file for Terminal Emulator
20140308 changes
- Fixed Aroma script error meaning 95CleanTweaks not being given correct permissions to run as init.d
- Reset CPU profiles in the ramdisk so they mirror the ones we are used to from CROMi-X in terms of speed and fps limits
- That's kernel OCs to 1.8GHz with balanced at 1.5GHz and power saving at 1GHz
- lj50036's kernel OCs to 1.7GHz with balance at 1.5GHz and power saving at 1GHz
- Hunds's kernel OCs to 1.8GHz with balanced at 1.6GHz and power saving at 1.4GHz
- Attempted to fix issue with some users not being able to install to ROM2SD - but still broken if CROMBi-kk is on internal
- Updated media codecs from another CM11 build. Hopefully it'll fix dice and other video content
- Recompiled Browser.apk with speed tweaks as they got lost in a recent build
- If ROM2SD is chosen in installer then TWRP stays in ROM2SD mode until a reboot
- Gapps can be flashed to ROM2SD without needing the rom2sd1.zip if flashed straight after the rom installer
- Updated ES FIle Explorer to version 3.1.0.3
20140306 changes
- Updated GravityBox to version 2.9.8
- Final tidy up of ROM and scripts for release
20140305 changes
- Fixed the ROM2SD booting issues - thanks _that!
- New extract ramdisk script to solve the above
- Repacked the 2 CM11 kernels with thatv9 init binary which fixes empty last_kmsg issues
- Remixed Hunds 3.4.5 OC kernel with CM11 ramdisk - experimental not sure it works well
- Updated Titanium Backup to version 6.1.5.4
20140304 changes
- Added ROM2SD and DATA2SD scripting to installer
- Updated the stock CM11 kernel to include pre-init scripting - enables Data2sd & Rom2sd
- Updated Apex Launcher to version 2.30
- Removed CM11 _that kernel for now as wifi non functional due to missing modules during compilation
- Added script to upgrade build.prop from CROMBi-X to CROMBi-kk
20140303 changes
- Fixed Xposed not installing properly
- Added Asus _that kernel repacked with CM11 ramdisk and preinit compatibility
- Fixed missing modules from lj50036 & _that kernel
- Fixed Nexus Flow Bootanimation finishing too early
- Added phab7 as a test
- ROM name changed to CROMBi-kk
20140302 changes
- Built Aroma Script for main ROM installer
- Added new thatv8 kernel for CM11
- Updated dropbox to version 2.3.12.10
- Updated Terminal Emulator to version 1.0.57
20140301 changes
- Added Browser to RAM script
- Repacked Browser.apk with debug options on by default for speed - see labs options
- Added CleanTweaks init.d script from CROMi-X 5.4 as a test (need to analyse what is compatible)
- Build.Prop tweaks from CROMiX
Click to expand...
Click to collapse
Click to expand...
Click to collapse
The Team
@sbdags - Creative Mastermind (From CROMi-X)
@lj50036 - Source Guy (From CMB ROMS)
@hardslog - The Canadian (From Grimlock ROMS)
Credits
Google, wow is all I can say!
CyanogenMod we wouldn't be doing this if if weren't for them (even if they are for profit now hah).
CMB for the basis of our Gapps package!
nycbjr (CMB ROMS team leader) Thx for all the time teaching me the way (lj50036)!!!!
_that For all the great advice!!!!!
To Do
Add Aroma to Gapps Package
Add Asus Apps as separate install
More Kernels and Tweaks
XDA:DevDB Information
CROMBi-kk, a ROM for the Asus Transformer TF201, ROM for the Asus Eee Pad Transformer Prime
Contributors
lj50036, sbdags , hardslog, _that
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.1.x
ROM Firmware Required: V 10.6.1.27.1
Based On: CyanogenMod 11 AOSP
Version Information
Status: Beta
Current Beta Version: 20140906
Beta Release Date: 2014-03-18
Created 2014-06-05
Last Updated 2014-10-11
Reserved
UPGRADE INSTRUCTIONS
REFER TO POST #4 FOR UPGRADE INSTRUCTIONSFLASHING THE ROM FROM RECOVERY
Steps
1. Download the ROM below and save to your internal or external SD Card. Do not unzip the file.
CROMBi-kk ROM DOWNLOAD
Note: The first boot after install will take 10 mins whilst everything is built. Some people might think it is looping but it is not
CROMBi-kk Current Release Full Mirror 1
CROMBi-kk Current Release Full Mirror 2
CROMBi-kk Current Release Full Mirror 3
ASUS APPS DOWNLOAD - Flash from Recovery : Compiled by kansasboy001
Asus Battery Widget, Asus Calculator, Asus Calendar, Asus Clock, Asus Dayscene Live Wallpaper, Asus Dictionary, Asus Email, Asus Gallery, Asus Keyboard, Asus Photo Story, Asus Sound Recorder, Asus Tasks, My Frame, My Water I & II, Asus Supernote Pro, Weather & Time Widget, Asus Framework, Asus Settings, Asus Audio (V4A), Asus Contacts, Asus File Manager(Root Browser), Asus Camera, Asus Browser
[THREAD][APPS] [ASUS Apps][ CROMBi-kk & ZOMBi-kk]
GOOGLE APPS (GAPPS) DOWNLOAD - NO LONGER NEEDED!
GAPPS NOW INCLUDED AS OPTIONS IN MAIN ROM ZIP
Change Log
crombi_kkgapps_20140315
Updated YouTube to version 5.5.27
Updated Google Maps to version 7.7.0
Updated Google Search and Libs to version 3.3.11
crombi_kkgapps_20140312
Updated Google Calendarsync adapter to latest version
Fixed the issue of GApps not flashing if not done directly after ROM
crombi_kkgapps_20140309
Updated Google Bookmarksync adapter to latest version
crombi_kkgapps_20140308
If Gapps is flashed after CROMBi-kk it should now in ROM2SD mode - no ROM2SD1.zip required
Updated Google TTS to version 3.0.10.1047791
crombi_kkgapps_20140306
Removed calendarprovider.apk from gapps as conflicted with calendar app in rom
crombi_kkgapps_20140301
Updated updater-script
Updated Google Plus to version 4.3.0.62241793
Updated Google Core Services and lib files to latest version
Updated Google Experience Launcher to version 1.0.9
crombi_kkgapps_20140223
Updated Gmail2 to version 4.7.2
Updated Hangouts and lib files to version 2.0.303
Updated Google Maps to version 7.6.1
Updated YouTube to version 5.3.32
Updated Google Now and lib files to version 3.2.17.1009776arm
Updated Play Store to version 4.5.10
Removed Google Calendar as a version is already provided in rom
ROM2SD INSTRUCTIONS PLEASE READ!
ROM2SD only works if you have CROMi-X, miniC flashed on internal. Just choose ROM2SD in the installer of CROMBi-kk to flash it to ROM2SD and the installer will do the rest.
ROM2SD USERS PLEASE CLICK HERE
- Install CROMBi-kk and choose ROM2SD install
- Flash ROM2SD1.zip No longer required
- Flash GAPPS Package No longer required
- Flash Wifi ROM2SD Patch No longer required
2. Boot to recovery – Either choose Boot to Recovery from the Power Menu if available on your current ROM or from the tablet power off hold the [volume down] button and press the [power] button. Once your see the flashing RCK icon, press [volume up] to select. If another icon is flashing use [volume down] to move between icons.
3. Using your recovery make a Nandroid Backup of your current setup
4. Select install and navigate to where you saved your ROM zip file.
5. Choose the CROMBi-kk zip file and follow the on screen prompts to customize your installation.
6. Choose the wifi patch and flash..
7. Reboot and enjoy.
SDCARD SETUP PLEASE CLICK HERE
Using GParted to setup a micro SD for ROM2SD support
First and foremost - DO NOT USE MINI TOOL!
Formatting a micro sd card for ROM2SD
We will be using a GParted Live boot USB and a FAST good quality micro sd like a Sandisk or Samsung Class 10 - SDHC/SDXC UHS-1 card with read speed of at least 20MB/S. If you have a cheap chinese eBay card don't bother - they are not good enough.
You will also need a USB Stick with at least 1GB size. Note this process formats the USB disk so don't keep any important files on it. It will also wipe your micro sd so make sure you are prepared.
1. Go to the link below and download the GParted Live CD/USB/HD/PXE Bootable Image and save it somewhere you remember
http://gparted.sourceforge.net/download.php
2. Download Linux Live USB Creator and install it
http://www.linuxliveusb.com/
3. Fire up LiLi USB Creator:
a. Choose your USB key - I,e, the drive letter for your USB (not sd card)
b. Choose your GParted iso image for the source
c. Choose the check box to Format Key in FAT32 and hide files
d. Click the lightning bolt to create
4. Now you have a bootable disk you need to boot from it. You may need to alter you BIOS Settings on your PC to boot from a USB Stick but mine did it without messing.
5. Insert your micro SD card into an SD Card adapter and insert into PC
6. Boot into GParted
7. Choose Gparted Live <Enter>
8. Don’t touch keymap <Enter>
9. Languge <Enter>
10. Start Gparted Automatically
11. Change device to your micro sd )it will default to you hard disk - hda– mine is /dev/sdc
12. Delete all existing partitions
For a 64GB card: (resize as needed but /system doesn't need to be bigger than 1GB)
13. Create new, always select primary: do this 3 times.
14. FAT 32 : Size 16GB – this will be /dev/sdc1 in gparted and will be your sdcard for storage in Android
15. EXT4 : Size 42GB – this will be /dev/sdc2 in gparted and will be your /data partition in Android
16. EXT4 : Size 1GB – this will be /dev/sdc3 in gparted and will be your /system partition in Android
Apply, wait until it finishes and then reboot. Remember to remove the usb stick
*Images stolen from elsewhere as I couldn’t get it to save mine
Now you are ready to install ROM2SD. Note if you want to use DATA2SD then only do 2 partitions 1x FAT32 and 1x larger EXT4
Then reinstall CROMBi-kk but this time choose the ROM2SD option
HUGE THX
@spudsmac
@miduku
@robbie888
@lightiv
@Bigred007
@Waldo_
@emfanitek
@rlanza1054
@Unidave199
@Lock-N-Load
@Fear Knot
@lvrijn
@mitsublw
@scouzers
@zdebel
@jhr5474
@Eddie Hicks
@smchadwell
@dladz
@eRPeeX
@LocusofZen
Thx everyone that have donated, if you do not see your user name here and have donated, shoot me an PM and I will add you....
Thx Josh
Take a look
UPGRADE INSTRUCTIONS, STEP BY STEP
This may help
Starting from a stock bootloader V 10.4.2.18
What you will need
Woking fastboot & adb / SDcard optional
TWRP for a 201 = twrp_tf201t.blob
@ne0zone75 TWRP for the 300 = ne0zone75_tf300t.blob
HairyBean BL & TWRP: This is effectively turn your 201 into a 300 <---- which is a flashable zip inside the zip that you downloasd
All 3 of the above file are in a zip in the Download section @ the top of every page of the thread ...... THIS ZIP IS NOT FLASHABLE...Your must unzip it to get to the real files !!! The name of this zip is 'upgrade_tf201_to_tf300t.zip'
CROMBI 201 ROM zip
A fully charged tablet
All the above files in the same directory as your fastboot.exe (if using windows) In your home folder on linux....
The process
Lets start with the TWRP recovery for the 201, let flash it with fastboot...
Power your tablet off and with the [ VOL DOWN & POWER ] buttons boot the tablet into the bootloader
Once there [ VOL DOWN ] untill the green box is on the USB ICON then [ VOL UP ] to select fastboot
Let make sure your PC can see your tablet with this command.
Code:
fastboot devices
Code:
fastboot -i 0x0b05 flash recovery twrp_tf201t.blob
Then
Code:
fastboot -i 0x0b05 reboot-bootloader
[ VOL UP ] ON RCK to enter recovery
Once in TWRP check to see if adb is working...
Code:
adb devices
Ok now that we know that is working let go ahead and push the HairyBean BL onto the tablet
Code:
adb push HairyBean_Bootloader_TWRP2.5.zip /sdcard
Now under the install tab in TWRP fine the folder and flash it....
reboot once it has fishined..If ask to install SuperUser say NO..........
LET THE BLUE BAR FILL !!!!!!!!! Once it has finished it will reboot into Hairybean TWRP....
Once booted into recovery, run this command to boot into fastboot
Code:
adb reboot-bootloader
You will see that the USB icon is missing now, this is good... If you still see the USB icon DON'T go to the next step
Now lets flash @ne0zone75 TWRP recovery
Code:
fastboot -i 0x0b05 flash recovery ne0zone75_tf300t.blob
Once that has finished let reboot into bootloader
Code:
fastboot -i 0x0b05 reboot-bootloader
Now enter recovery....
Make sure its verison 2.7.1.0
Go to Wipe////Format Data////Type yes
This can take up to 90 mins to format
DO NOT INTERRUPT THE FORMAT !!!!!!!
Now lets push CROMBI-KK onto your tab
Code:
adb push cm-11.0-2014xxxx-crombi-kk-tf201t.zip /sdcard
Find it under the install tab and flash it..
REBOOT into android, first boot can take up to 15 minutes
Kernel Sources
All Kernels included in this ROM package are unofficial, as they are complied from source, thay may not match the source that they were forked from. I will be linking the kernel source code as per the GNU GPL License.
Unofficial @hardslog Grimlock Kernel Source CLICK ME@-V1.0.0
Unofficial CM-11.0 Kernel Source CLICK ME@-V1.0.0
Unofficial @_that Kernel Source CLICK ME @-V1.0.0
Official @hardslog Grimlock Kernel Source CLICK ME
Official CM-11.0 Kernel Source CLICK ME
Official @_that's Kernel Source CLICK ME @-V11
Hi Josh its a good idea letting other TF201 users know about this rom, it might also be good to mention and to link to the bootloader/twrp downgrade file as well.
Sent from my Transformer Prime TF201 using XDA Premium HD app
The dumb questions up front!
So, I'm already on Hairybean 2.31 so I'm already unlocked so I would already meet the requirement you have up front: "YOU MUST BE ON THE HAIRYBEAN 2.31 JB 4.2.1 BOOTLOADER"
So I should be able to just flash the zip file I downloaded from step 2 of the instructions to update my TWRP and then flash the ROM, correct?
ratman6161 said:
So, I'm already on Hairybean 2.31 so I'm already unlocked so I would already meet the requirement you have up front: "YOU MUST BE ON THE HAIRYBEAN 2.31 JB 4.2.1 BOOTLOADER"
So I should be able to just flash the zip file I downloaded from step 2 of the instructions to update my TWRP and then flash the ROM, correct?
Click to expand...
Click to collapse
yes, but do a full wipe before flashing the rom
Sent from my Transformer Prime TF201 using XDA Premium HD app
This is awesome dude, can't wait to give it a try.
Check out my website for encouragement....
www.projectintercession.blogspot.com
boldnuts said:
yes, but do a full wipe before flashing the rom
Sent from my Transformer Prime TF201 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks, I'll be trying this out tonight. Also I appreciate you doing a TF201 specific posting. I've been looking at the stuff over on the TF300 forum and it was looking like it should work, but its sure nice to have it here.
I will just post a testimonial here for newcomers. I have been using this ROM as a daily driver ever since it was released a few months ago. I have to admit that it is speedy and lovely. The F2FS feature in the new version of the ROM gave me that much more RAM and I don't feel the degrade I once did with the tablet on other ROMs on the forum. Gaming, movies, browsing, it does it all with good speed.
lj50036 said:
You never Know
Click to expand...
Click to collapse
To ALL doubters this Rom is the JAM ! and lj50036 is the go2MAN ! If you want a TF300 , but have a TF201 this is the ROM that you NEED to install ....
NOW !
feyerbrand said:
I will just post a testimonial here for newcomers. I have been using this ROM as a daily driver ever since it was released a few months ago. I have to admit that it is speedy and lovely. The F2FS feature in the new version of the ROM gave me that much more RAM and I don't feel the degrade I once did with the tablet on other ROMs on the forum. Gaming, movies, browsing, it does it all with good speed.
Click to expand...
Click to collapse
You originally turned me on to the TF300 thread many months ago and I been there ever since. Thanks for this.
I have to concur, these guys have really improved upon all the latest Droid releases and kept me from wanting to sell this (now a) dinosaur of a tablet. Good ****.
:good:
Excellent job @lj50036. :good: I'm gonna try this soon.
Thanks...
Best Regards
Initial Impressions
Just installed the ROM last night. Coming from Hairy Bean 2.31 it was extremely easy to install. Just had to flash the .zip for the updated TWRP and then Flash the ROM. It should be almost as easy for those not on Hairy Bean as you would just have one more step which is to flash the HB boot loader. But overall I found the procedure to be incredibly easy and low risk.
Once installed the ROM works great. Seems nice and fast and smooth though I have not had a chance to use it extensively yet. One minor nit I noticed is that in the CPU settings the maximum CPU speed seems to default to 1800 MHZ and I think most Primes will not like that. I know mine wouldn't like anything over 1700 so I would recommend changing that before checking the "apply at start up" box.
After doing the initial install and letting my apps download from Google Play I decided to take the plunge and turn on ART. This really works well on my Motorola Droid Maxx phone so I figured I'd try it. It was a no go (though not really a bug because there are warnings all over it about being experimental). The system got stuck in a boot loop where I would get the boot animation and it would sit there for a long time...before spontaneously restarting and repeating. The back of the tablet (I'm assuming where the CPU must be felt decidedly warm to the touch. Anyway, this isn't a huge deal since I kind of didn't expect ART to work on this device. If anyone else has it working I'd like to hear about it.
ratman6161 said:
Just installed the ROM last night. Coming from Hairy Bean 2.31 it was extremely easy to install. Just had to flash the .zip for the updated TWRP and then Flash the ROM. It should be almost as easy for those not on Hairy Bean as you would just have one more step which is to flash the HB boot loader. But overall I found the procedure to be incredibly easy and low risk.
Once installed the ROM works great. Seems nice and fast and smooth though I have not had a chance to use it extensively yet. One minor nit I noticed is that in the CPU settings the maximum CPU speed seems to default to 1800 MHZ and I think most Primes will not like that. I know mine wouldn't like anything over 1700 so I would recommend changing that before checking the "apply at start up" box.
After doing the initial install and letting my apps download from Google Play I decided to take the plunge and turn on ART. This really works well on my Motorola Droid Maxx phone so I figured I'd try it. It was a no go (though not really a bug because there are warnings all over it about being experimental). The system got stuck in a boot loop where I would get the boot animation and it would sit there for a long time...before spontaneously restarting and repeating. The back of the tablet (I'm assuming where the CPU must be felt decidedly warm to the touch. Anyway, this isn't a huge deal since I kind of didn't expect ART to work on this device. If anyone else has it working I'd like to hear about it.
Click to expand...
Click to collapse
Thx for your feelback mate....:good:
The reboot after enabling ART can take 10 -15 mins....
Take a logcat of the boot and you will see lots of things happening....
If you see the same thing happening over and over then yes thats a biootloop
Can anyone else confirm ART not booting up ??
THx Josh
lj50036 said:
Thx for your feelback mate....:good:
The reboot after enabling ART can take 10 -15 mins....
Take a logcat of the boot and you will see lots of things happening....
If you see the same thing happening over and over then yes thats a biootloop
Can anyone else confirm ART not booting up ??
THx Josh
Click to expand...
Click to collapse
art is working ok on my prime, I am using the f2fs file system though, so different kernel and keeping the overclock to 1600
Sent from my Transformer Prime TF201 using XDA Premium HD app
boldnuts said:
art is working ok on my prime, I am using the f2fs file system though, so different kernel and keeping the overclock to 1600
Sent from my Transformer Prime TF201 using XDA Premium HD app
Click to expand...
Click to collapse
So I'm still downloading the needed files, but is the f2fs option apart of the initial setup process? I've done some reading on it and would like to give it a try. Also had anyone tried the ROM to sdcard option yet? Thanks
Check out my website for encouragement....
www.projectintercession.blogspot.com
LOOK
Pictures are worth a thousand words...
andrewjt19 said:
So I'm still downloading the needed files, but is the f2fs option apart of the initial setup process? I've done some reading on it and would like to give it a try. Also had anyone tried the ROM to sdcard option yet? Thanks
Check out my website for encouragement....
www.projectintercession.blogspot.com
Click to expand...
Click to collapse
for f2fs you have to flash the correct version of twrp, then format your data partition as f2fs, then reinstall the rom
http://forum.xda-developers.com/showthread.php?t=2625580
Sent from my Transformer Prime TF201 using XDA Premium HD app
---------- Post added at 04:51 PM ---------- Previous post was at 04:51 PM ----------
lj50036 said:
Pictures are worth a thousand words...
Click to expand...
Click to collapse
cant wait!
Sent from my Transformer Prime TF201 using XDA Premium HD app
Related
Branch 4.x only for Sammy ROMS 4.1.2 (CWM and TWRP)
Branch 5.x only for AOSP 4.2.2 (CWM & TWRP)
Branch 6.x only for AOSP 4.3.x (TWRP)
Branch 7.x only for AOSP 4.4.x (TWRP)
Branch 8.x only for AOSP 5..x (TWRP)
DEVELOPMENT STOPPED . APOLO WON'T WORK IN LATEST LP ROMS . MORE INFO
Apolo Configurator -> will be available in Google Play THIS
Apolo 8.0 Beta9
Beta 9
-initramfs updates
-zRam disabled
Beta 8:
- initramfs updated
- TWRP 2.8.5.0
Beta 7/7b:
- zRam enabled
- initramfs updated
Beta6:
- App2SD Fixed
- Wifi Toggle issues fixed
- Network issues fixed
Beta5:
- CM wifi issue fixed
- same initramfs for cm and omni (same kernel for all roms)
- charging animation fixed
- zzmoove updated to 1.0beta5
Beta4:
- Recovery TWRP updated to 2.8.5.0
- Updated initramfs to latest CM & OMNI
Beta3:
- Recovery TWRP updated to 2.8.3.0
- Governor zzmoove updated to 1.0 Beta4
- Fuse bug fix by @zeitferne (thanks to @Lanchon too)
- Charging Animation fixed (thanks to @Lysergic Acid)
Download Link
MIRROR
Apolo 7.3 (final version for kitkat)
- Governor zzmoove updated 1.0 Beta5 (thanks ZaneZam)
- TWRP Recovery 2.8.6.0 ("Reboot Bootloader" button fixed)
- SPEEDUP KEYRESUME (Faster wake up at power button and incoming call)
- Fixed fuse bug (thanks to @Lanchon)
Apolo 4.15b for SAMMY JB ROMS (Removed vibration interface compared with 4.15)
- Governor zzmoove updated to 1.0 beta 4
- Speedup keyresume (faster wake up)
- Governor Neox has come back (not included in beta )
- FPBug fix by @zeitferne & @Lanchon)
Download links in the usual section in this OPChangelog old Versions in Post #2
Features:
This kernel is mainly based in hardcore work (thank you to Hardcore :victory: for his great contributions). I have added undervolting (kind of phenomenal) and some additional features.
- CWM and TWRP recovery in Samsung. In AOSP I will use only TWRP in the future.
- No logs, no extra debugging
- install su, supersu in samsung. Support init.d and cifs
- Ondemand Tweaked by Hardcore
- Added some governors (specially tweaked slp and zzmoove)
- Scheduler changing enabled
- BLN enable (Since Apolo 4.5 BLNWW too)
- CRT-OFF enable
- Effective Underclock (max frequency limited)
- UV Interface for ARM (you can change voltages in ARM with external aplications)
- Kernel Includes frandom for using with CrossBreeder (I really recomend it, Thx idcrisis)
- No Overclock and no different CPU-GPU steps from stock (please don't ask me more about that, I won't add it)
Update Supersu (only sammy kernel, AOSP doesn't have supersu)
Choose normal update (not the other with CWM/TWRP). In case you chose the wrong option, you'll have a bootloop. Read the bootloop section in this OP to recover your system.
Undervolting
UV cannot damage your mobile phone, but it can make your device unsteady. It is important that you choose the right version for your mobile.
There are some Apolo versions depending on the UV used:
- Light (stock voltages)
- Regular (-50mV in ARM, internals)
- Extreme (3 versions, you can try to see what versión is better for your battery life): in JB system chooses among the different steps available inside the kernel (in internal and ARM), so depending what step is chosen, final voltages applied are different.
Regular and extreme has -50mv UV in GPU (others UV like bus, memory, video controller too). Light has stock voltages in GPU
I recommend you try regular version first. If there are no problems in two days (reboots or frozen screens) you can try extreme V0.
System changes voltages in some devices (new in JB). Android chooses among voltages included in kernel (8 steps in every frequency). I recommend not to change them in extrem versions.
More information and Voltages values:
Depending on the device, system changes voltages (in JB), choosing among voltages defined in the kernel source. It seems, system tries to choose the ideal ones for every device (taking into consideration internal and ARM voltages).
For each frequency, there are 8 posible voltages in the code (I call them steps). In ICS, system always chose 4th step for every frequency, but in JB it doesn't sometimes.
It happends with ARM voltages (you can see them in the configurator) and with internal voltages, so there are many possibilities
You can see ARM and Internal voltages in this pdf (it is in Spanish but I think you can understand it) :
VOLTAGES
So, it is not strange that configurator shows different values in two different devices with the same Apolo version. It simple, system has chosen different voltages steps. I recommend you don't pay too much attention to this, it is not important, indeed system try to be stable choosing different values.
Tips
- TWRP and CWM Backups are not compatibles between them, so you need the suitable version to restore your backups.
- I recommend OBackup. Great application for making backups in Android itself (it supports TWRP and CWM).
- Not always less voltages means better battery life, it depends on your device. The only way is testing every version and please start with Regular or Light version
- Deep Sleep problems sometimes is caused by undervolting. If your system doesn't enter in deep sleep and it is not because of any application , install regular or light version.
- It is not the same, lower ARM voltages with an external APP (for example Apolo Configurator) and change Apolo version (V2,V1,V0 or regular) because there are more voltajes involved (not only ARM)
- If you want to turn off the leds always (when you touch tactile buttons), you have to use Apolo Configurator, otherwise (if you use only Samsung settings) your leds will turn on when you turn on the screen.
- If your system doesn't boot due to wrong Voltages, flash this in recovery : download zip
- Acess to internal sd in TWRP recovery :
(Up a level )
then go to
"emmc"
that's your internal sd
- Recommended wipe Cache and Dalvik after changing any kernel (it is not mandatory but it is a good custom)
- To increase sound volume use mods like Viper or appications like Alsa Mixer or Vodoo louder in play store
Enable logs in TWRP and v7 : Create a file in "/data" named ".enable_logs" and reboot.
¿In kit kat, should I use CM version or Omni version?
Just see if your ROM has superuser included (I mean if you can gain root just enabling it in developer options). In that case you should use CM version. If your ROM needs supersu to manage the root, install omni version.
Bugs
- Battery Animation doesn't work when phoes is off
There is a workaround. Thanks to @It_ler : http://forum.xda-developers.com/showpost.php?p=43244090&postcount=1250
- S2W doesn't work after rebooting.
It's because this S2W bug: "When the phone is booting, if the screen is off in the exactly moment the script is changing the S2W setting, the screen will not respond any longer and you have to reboot."
To avoid it, increase the screen timeout. Another solution is to keep the screen on, while the phone is starting until android had started completely and you can be sure that the script has been applied (more than a minute because the script has 60 seconds of delay).
- If BLN y/o WIFI doesn't work in kit kat ROMS (maybe it can help in other bases too)
If test button works in Apolo Configurator check if in your Android Settings- Display there's something related to notifications led or Notifications light
or review
Rom settings (name depends on the ROM) - Active display must be disabled, otherwise BLN won´t work
If BLN test or wifi doesn't work, try this:
- Remove Apolo folder in /system (if folder exists)
- Go to Recovery
- Wipe Cache
- Flash Apolo
- Wipe cache again
- Reboot
- Avast doesn't work with Apolo, if you can't live without it, use other kernel, sorry
- Bootloops: it doesn't happend very often but it can happend in JB if there is something corrupt in partitions. Posible solutions:
1) Try to enter to recovery. Press vol up, Home button and Power button at the same time until the device enters into recovery (system can restart 2 or 3 times, but don't release buttons). Then wipe cache and dalvik and reboot.
2a) if 1) didn't work, enter into download mode and flash light TWRP version if you had CWM. Wipe cache and Dalvik and reinstall CWM if you wish.
2b) if TWRP didn't work or you had TWRP version already, flash last PhilZ kernel (thx to Phil3759), enter into Philz recovery and wipe cache and Dalvik. Then reinstall Apolo.
3) if nothing worked, try to reinstall your ROM without wipe data and wipe cache and Dalvik
4) wipe data (you will loose all your application and configurations)
5) reinstall with odin stock ROM WITH repartition (pit file). Then install Apolo and reinstall your custom ROM.
- Sometimes when you reboot your device, your battery seems to drop a lot (it is not real).
To recover your old battery percentage, plug in your device and reboot into recovery. Check your battery level in the recovery, if it is correct, reboot (solved).
If it is not, reboot into recovery again (in CWM advanced - reboot into recovery, in TWRP reboot - recovery). It should be solved.
This issue never happens if you reboot your device while is charging, so I recommend you plug in your device before rebooting (if you can do it)
If you can't plug in your device, don't reboot if you can avoid it
- AOSP: Recommended installation procedure for 4.3 ROMS (stuck in the second boot) Read post 3
- AOSP: Restoring backups changing ROM base (stuck in the second reboot), Read post 3
Download Kernel
Mirror
Installation (you can install Apolo through CWM or TWRP recovery, it doesn't matter)
- Use a kernel cleaning script before installing (for instance Gs2KernelWipe thanks to hawkerpaul, but you can use other)
- .zip : install in custom recovery
- .tar : install in PC with odin (windows) or heimdall (linux)
Apolo Configurator (Available in Google Play again HERE)
I've developed a multilanguage application (Spanish, English, Italian, Catalan, Gallego, Russian and Turkish).You can change governor and scheduler, set ARM undervolting, configure BLN, BLNWW and S2W and set brightness curve:
I extremely recommend you read the Apolo Configurator Manual : Apolo Configurator Manual
My recommendation about scheduler/governor (it's only my opinion, maybe yours can be different)
- You can find 3 defined profiles in Apolo Configurator (performance, balanced and battery saving) based in noop/slp. I have changed parameters to achive the profile goals.
- Another good combination is noop/zzmoove
THANKS
- Hardcore for his fabulous kernel speedmod
- Thx to great :goodhil3759 (he helped me to build the CWM recovery and let me use his recovery in the new Apolo versions) Please, visit his great job here
- Thx to jeboo for his great kernel and for let me use his TWRP recovery :good:
- Thx gokhanmoral , great master. Most advanced features come from him
- Thx dorimanx for his great kernel and sources
- fenomeno83 for his idea and help when I started
- Thx mialwe for his great "smoove" governor (base of zzmoove) and ZaneZam for keeping it alive with the zzmoove.
- Chainfire for CF-Root, CWM Manager, etc, etc
- Thx sk8erwitskil, myfluxi, Talustus for recovery sources
- Thx to Devil_1210 for his help building the ICS kernel
- Thx to my betas for their help and ideas and much more: Broquen, Garrapatero123, Palleiro, Doomper, partisano, 666roi666 , Gordon320, nrg86
- Many thanks to @daga69 for giving me a S2 and keep this kernel alive
- Thanks to @rrgrrg for the Configurator icon.
(for sure I forgot more people, I hope they forgive me)
Donors: :laugh:
Axel 11, manuelmagix, K-a-M-u-Z-u, elbanzai,Zytrel, bkraptor,Shadowrun1,rogers11,LarsX,Andreas75k,espirito-livre, dsp26, gumsle, karpfenhai,
Andreas75k (Yes again ), metalgearhathaway
Thanksssss a lot ¡¡ :highfive::victory::good:
If you see something that you cannot understand or it is not correct (my English is far away from perfect ) please let me know
If you want to translate the Apolo Configurator to other lenguages, please tell me
Thanks to @lejarton, @Maxximo88, @stelistcristi,@Gordon320, @nrg86, @Palleiro, @Partisano, @Broquen and @nhmanasfor their translations
Enjoy ¡¡
Apolo source code
CHANGELOG OLD VERSIONS
Apolo 7.1 (for kitkat ROMS, 4.4.x)
- Recovery TWRP updated to 2.7.1.0
- Mali drivers updated
- zzmoove updated to 0.9beta3 (thanks to ZaneZam)
- rebuilt cypress (maybe helps with BLN errors in some devices)
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo 7.0b for kit kat, 6.3 for 4.3.x ROMS (TWRP recoverys) and Apolo 4.14 for stock ROMS (CWM & TWRP recoverys)
Changelog All bases (7.0b & 4.14 & 6.3):
- New zzmoove 0.8 (thx ZaneZam Link )
For kitkat (Apolo 7.0b & 6.3 TWRP):
- Fixed second core bug that affected some governors
- Pac-Rom support
- TWRP updated to 2.7.0.0 (it doesn't work fine in stock roms 4.1.2 (bootloops issue), so if you want to go back to sammy roms from kitkat, install first 4.14 and reboot in recovery and install from Apolo 4.14 recovery)
Remember that 6.3 comes with new mali drivers. If you see your screen off when you start your system, you must flash this through recovery.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo 4.13 (SAMMY) & 6.2b (AOSP 4.3.1)
Both (SAMMY and AOSP):
- Linux updated to 3.0.101
- Updated row scheduler
- Added bfq scheduler
- Removed MDNIE Sharpness by Hardcore (no mor problems with mdnie scenarios)
- Initramfs improved
6.2b ONLY:
- GPU an Screen drivers updated (r3p2+s3cfb)
- Wifi drivers updated to 1.61.58
WARNING: 6.2b version only with mali r3p2+s3cfb.
If your ROM is mali v2 (old drivers) you have to update some libs (otherwise, black screen). You can do it with this zip (flash in recovery):
https://copy.com/reo37Z4KqLVhU1S2
The zip will change some libs in ROM, so if you want to go back, you'll have to flash the ROM again without wipes
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo beta kitkat (Android 4.4 CM and OMNI-SlimKat)
- Beta 3 ONLY for OMNI ROMs: Solves the issue installing some application in latest nightlies
- Beta 2/2b for CM ROMs:
Only with mali v3. Works with new CM bases (4.4.2) .Thanks Karpfenhai for your help testing it
- Fixed battery settings
- CWM stock recovery (restores fine)
- Last changes (like 6.2)
If you suffer issues with the battery indicator, please change to beta2 or beta2b (depending on what kernel had the issue)
- For Omni ROMS there is a beta2 (same changelog) with TWRP recovery
For SLIMKAT 4.4.2 ROMs you should use Apolo beta2b for CM.
If you use omni version in CM ROMS (don't recommended because you will loose root) don't forget to download supersu and update binary BEFORE flashing Apolo kernel (otherwise you'll have a bootloop).Thanks to @Shahan_mik3 and @EricCartmanez for the information.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo Beta 3 FOR CM KITKAT (4.4.2) ROMS
- Solves the issue in (FC in phone) in latests nightlies
- Fix the bug moving big files to external sd (CREDITS TO GUSTAVO)
It was a lot of work, headaches, and semibricksssss so ENJOY IT¡¡
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo versions 4.12, 5.1, 6.1
For all bases:
- Reverted the stupid android_secure change I did in last kernel
- Added new governor Neox
- Added MyFluxi sound interface (to control it you'll need to use the new Apolo configurator 5.0)
- Fixed mdnie in the camera with mdnie sharpness disabled
Only For 5.1:
- Fixed vibration control
Only For 6.1:
- Added support for framework-2.jar
- Fixed com.android.phone FC in latest releases
---------------------------------------------------------------------------------------------------------------------------------------------
Apolo 5.0 & 6.0 (AOSP ROMS)
5.0 (AOSP ROMS 4.2.2):
- TWRP version fixed (bluetooth) and updated to 2.6.3
6.0 (AOSP ROMS 4.3 and 4.3.1):
- Initramfs improved
- Fixed booting for latest Pacman ROMS (4.3.1)
- TWRP version fixed (bluetooth) and updated to 2.6.3
- Vibration Control enabled
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------Apolo 4.11 (Sammy only)
- zzmoove updated to 0.7d
- Backup and restore Android_secure fixed
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo 5.0 & 6.0 (AOSPs Version)
- Base: smdk4412 by cyanogenmod
- Same tweaks as Apolo JB 4.x
- zzmoove updated to 0.7d
- Backup and Restore of Android_secure solved (thx dorimanx)
- Fully compatible with Apolo Configurator
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo 4.10 (Sammy ROMS)
- Added brightness curve interface (credits to gokhanmoral) It will be necessary to use new Apolo Configurator 4.0 to configure the brightness curve (available in Google Play).
- Exfat support in kernel and recoverys (CWM and TWRP)
- TWRP recovery updated to 2.6.1 (thx to the TWRP team)
- zzmoove updated to version 0.7c.(thx ZaneZam)
- su and supersu updated (thx chainfire)
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo JB 4.9
- Slightly change in brightness levels (automatic brightness higher than 4.8)
- Wifi drivers updated (latest S4) thx dorimanx
- Pegasusq , sampling time set to 50000, instead 100000 (improvement listening music with bluetooth)
- Try to solve issue of charging animation with phone off (will see if it works)
- zzmoove updated to 0.6 and tweaked thx ZaneZam
- sio scheduler updated
- su, supersu updated
- Revert USB charging values to 450 mA by default (safety measure). Added charging interface, so since Apolo configurator 3.8b you will be able to change it.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo JB 4.8
- Bilingual CWM recovery(Spanish-English). Default: English (you can change language in Extras Apolo)
- Fixed toggle ctr-off in CWM recovery
- Default backup format set to tar in CWM
- Updated TWRP recovery to version 2.5 (Thx Jeboo for sources). Added Preload support.
- Two new minimum brightness levels in manual mode (lower than stock)
- Fixed init.d. Now kernel considers all scripts in /system/etc/init.d
- Fixed BLN test in Configurator
- Current for USB charging to 650 mA (same as wall charger)
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo JB 4.7
- New Wifi Drivers from S4 (Thx dorimanx and codeworks)
- Added I/O Scheduler row (Thx Jeboo)
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo JB 4.6
- Revert Linaro toolchain compiler to GCC 4.6.3
- New governor interactivex (thx dorimanx)
- New governor zzmoove tweaked by pedestre (I recommend this governor, it's great)
- Fixed bug flashing from recovery updates with Assert instruction (for instance modem zips)
- Updated su and supersu
- Fix Touchscreen Choppy using MXT224E chip(thx kgp700)
- New Apolo Configurator 3.2 (useful for activating and scheduling BLN and BLNWW, selecting governors and schedulers and much more ...). You can find it free in Google Play
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apolo JB 4.5
- New interface with BLNWW, leds timeout and brightness and Slide to Wake (All the credits for gokhanmoral)
- New governor Intellidemand (thx dorimanx)
- New Apolo Configurator 3.0 (useful for activating BLN and BLNWW and much more ...). You can find it in Google Play free
INSTALLATION PROCEDURE FOR 4.3 / WIPING DATA ( if you are going to wipe data, skip 4,5 and 6)
In 4.4 is not necessary if you are using beta2,beta2b or beta3 (Omni or CM)
I don't know what the problem is (update: the problem is recovery) but if you follow this procedure (fresh install) you won't have any problem. If you install the rom right with Apolo, you may be stuck in the second reboot ?¿?¿
1- Install CM recovery (it is better install ROM with CM recovery). You can download it here
2- Advanced - Reboot in recovery (you will reboot in CM recovery , it is no a touch recovery, sorry)
3- Wipe data (and format system if you are going to install a new ROM)
4- Install ROM
5- Install gapps
6- Wipe data again
7- Boot system
7- Do the initial guided setup (wifi, gmail, etc) and install a couple of your apps
8- Reboot (it takes to boot a little longer than usual, even a couple of minutes)
9- After a successful second reboot, you can change the kernel to Apolo and you won't have any issue. It will always boot normally.
RESTORE ROMS IN AOSP ROMS (moving from 4.3 to 4.4 or from 4.4 to 4.3)
This issue only happends (AFAIK) when you change your base restoring the backup, for instance if you are in 4.4 and restoring a 4.3.1 backup. In my experience if you are in the same base, it works right.
You won't have any issue restoring roms in firs reboot, but you may be suffered the same issue (stuck in samsung logo) in second reboot, after restoring your backup. You can do your backups with Apolo, the issue is restoring, but I recommend you do your backups with OBackup App, because you don't need to reboot in recovery (you can do it in Android without rebooting)
If you want to restore your backups successfully I recommend you first change the kernel to CM kernel and then restore your backup:
SAFE PROCEDURE TO RESTORE BACKUPS
1- Reboot in recovery
2- Install CM recovery download
3- Advanced- Reboot in recovery
4- In CM recovery : Restore your backup
5- Reboot and everything will be fine
And more
Greetings!!!
YES! Finally Apolo by Pedestre here!!!
WELCOME :victory:
Kernel rocks
And CWM in english now?
Ooooh goood
I follow your kernel on an Italian forum, and it's quite popular.. just because your kernel is waaaaay good :thumbup:
Welcome to Xda mate! I hope a lot of people will enjoy your work
WarcoLLapsE said:
YES! Finally Apolo by Pedestre here!!!
WELCOME :victory:
Kernel rocks
And CWM in english now?
Click to expand...
Click to collapse
Thanks ¡¡
No plans , too much work translating and maintaining two CWM recoverys, but I wouldn't mind to include any English CWM recovery if somebody let me use it (as I did with TWRP from Jeboo)
finally on xda!!
Thank you for having implemented the zzmoove:thumbup:
my results with this amazing kernel .....
only wifi - no games/no 3G/no BLN/no Slide2wake, Tapatalk, internet browser, youtube + 2h to music on headphones....
Spoiler
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Spoiler
Phone: SGS2
Inviato da: Tapatalk 2
Rom: NeatROM 4.7 LITE XWLSS
Kernel:Apolo 4.6 v0 ←testing-
Modem: XXMS2
Battery: Stock 1650mAh
SD Ext. : 32Gb class 10
Inviato dal mio supermuletto :tank:
Thank you very much for your work Pedestre. Glad to see you here too. Good Luck. Regards
Enviado desde mi GT-I9100 usando Tapatalk 2
vitalianoleone said:
finally on xda!!
Click to expand...
Click to collapse
+1
Just added this kernel thread to my kernels-to-test list of my kernel test thread.
Hope that latest light version will run stable on my phone, as I had some FCs and SODs on previous regular version.
Thanks pedestre! Great kernel and best person. :thumbup:
It_ler said:
+1
Just added this kernel thread to my kernels-to-test list of my kernel test thread.
Hope that latest light version will run stable on my phone, as I had some FCs and SODs on previous regular version.
Click to expand...
Click to collapse
FCs and SODs are tipical undervolting issues. Light version has stock voltages, I hope you don't have any problem
Your mobile must be delicate with undervolting; most devices don't experience any issue with regular version.
Thanks for added Apolo to your kernel list. Great job testing ¡¡
My results
Spoiler
Phone: SGS2
Inviato da: Tapatalk 2
Rom: NeatROM 4.7 LITE XWLSS
Kernel: Apolo 4.6 v0 ←testing-
Modem: XXMS2
Battery: Stock 1650mAh
SD Ext. : 32Gb class 10
Inviato dal mio supermuletto :tank:
Thanks !!
Let's try 4.6
Nice to see you here pedestre, tnx a lot for your work!
What a tremendous job man!! Works great with AllianceROM!! Thx
Welcome master. Great job. Best kernel ever.
Yeah! Finally on xda! I'm sure that philz will let you use his recovery!
Inviato dal mio GT-I9100 con Tapatalk 2
Glad to see you around here
I will help you as much as I can
NEXT Kernel 1.0.0:
STOP! This kernel supports Custom KitKat Roms (e.g. OmniROM, SlimKat, CM 11.0), Custom JB 4.3.x Roms (e.g. CM 10.2) and Stock / Stockbased Roms!
It won't work on any AOSP Android 4.1.x or 4.2.x Custom Roms for now!
FOR NOW I FORBID ANYONE ELSE REUSE THIS STILL IN DEVELOPMENT DUAL BOOT PROJECT FOR HIS/HER OWN GALAXY S3 MINI PROJECT!
Sources:
https://github.com/andi34/android_kernel_samsung_golden
Dual-Boot Solution by @ketut.kumajaya, well known from Samsung Galaxy Tab 2 and Samsung Galaxy Tab 3 8.0
I/O Scheduler : noop | deadline | cfq | sio | sioplus | row | zen
Governor : Abyssplug | Ondemand | Interactive | Powersave | Performance | SmartassV2 | Sakuractive
based on latest Samsung OSRC for Samsung Golden (JB_Update2)
Linux kernel 3.0.101 version
Compiled with GCC 4.7
Open source Samsung exFAT included (v. 1.2.7)
Static BusyBox v1.21.1 in /sbin, android_reboot applet added (a quick but clean port from Android toolbox), swapon applet with priority option. Thanks to @ketut.kumajaya
"magic busybox" for Stock (based) 4.1 Roms: Ramdisk Busybox will overwrite busybox binary in
/system/bin or /system/xbin and save it as busybox.backup
Auto root on Stock (based) 4.1, but please download SuperSU from Google Play to update
Early boot scripts support
(/system/etc/init.d, /data/local/userinit.sh, and /data/local/userinit.d)
symlink /system/etc/wifi/bcmdhd_sta.bin_b2 to /system/etc/wifi/bcmdhd_sta.bin
to fix broken Wifi on Stock(based) Roms
SElinux Support
Known Problems:
Bootmenu
- Reboot into Recovery from main Bootmenu does not work
- Reboot into Bootloader from main Bootmenu only reboots normal
StockRom
- USB connection not working, charging works
- Wifi-Tethering not working on Stock / Stockbased Rom
Known fully working Roms
SlimKat by Android-Andi
OmniROM by golden-guy
VanirAOSP by Unjustified Dev
enox Stockbased Rom
Stock Light
Virginity v14
Selfcompiled CM 10.2.1 (based on CM 10.2.1 Stable Source)
Novafusion CM 11 & PAC (ext4 formatted!)
Novafusion CM 10.2 & PAC
Thanks To:
ketut.kumajaya - without you this would never be possible <3
gokhanmoral, Chainfire
@LuuchoRocha
@cocafe
OliverG96
DerTeufel1980
This part will be expanded. Most of the patches I applied are coded by someone else. Please remind me if I forget to give credits to anybody...
I am still learning each day, i learnd most stuff from our great Developer Ketut P. Kumajaya
- i think HE deserves a Beer instead donating to me ATM. If you like you can spend Ketut a beer using PayPal
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
XDA:DevDB Information
[golden] NEXT kernel, Kernel for the Samsung Galaxy S III Mini
Contributors
Android-Andi, ketut.kumajaya
Kernel Special Features:
Version Information
Status: Beta
Created 2014-08-12
Last Updated 2014-10-11
Downloads
All files attached
- NEXT Tool 0.2 to create a 2nd System Partition (system.img) - also included inside PhilZ Touch Blackhawk Recovery
- PhilZ Touch Blackhawk Recovery for Dual-Boot-Support
- NEXT Kernel
Since NEXT Kernel 1.5.4: download latest NEXT Kernel here
Older files for history still here attached!
Changelog
Code:
[U]11.10.2014[/U]
1.5.6 -> 1.6.0
- Utilized blkid further
- Autogenerated fstab adapted from NEXT Kernel for Samsung Galaxy Tab 3
- Initial F2FS Support (experimental)
[U]19.09.2014[/U]
Update dual boot tool 0.3
- Create 1.5 GB dynamic growth sparse image
- Ext4 formatting fix
- Free space calculation fix
1.5.5 -> 1.5.6
- fixes a warning in dmesg (sysfs: cannot create duplicate filename '/devices/virtual/switch/usb_audio')
[U]17.09.2014[/U]
1.5.4 -> 1.5.5
- get rid of DVFS limit without breaking Stock 4.1 or Android 4.3 / Android 4.4
thanks [user=5562153]@LuuchoRocha[/user] and [user=4832589]@cocafe[/user]
[U]16.09.2014[/U]
1.5.3 -> 1.5.4
- Android 4.3: added PAC Support
- Nintendo Wii Remote support (experimental, untested)
- cpufreq: turn all CPUs online when governor gets changed
[U]04.09.2014[/U]
1.5.1 -> 1.5.3
- "magic busybox" for Stock (based) 4.1 Roms: Ramdisk Busybox will overwrite busybox binary in
/system/bin or /system/xbin and save it as busybox.backup
- Auto root on Stock (based) 4.1, but please download SuperSU from Google Play to update
- Early boot scripts support
(/system/etc/init.d, /data/local/userinit.sh, and /data/local/userinit.d)
- symlink /system/etc/wifi/bcmdhd_sta.bin_b2 to /system/etc/wifi/bcmdhd_sta.bin
to fix broken Wifi on Stock(based) Roms
[u]01.09.2014[/u]
1.5.0 -> 1.5.1
fix broken Dual-Boot (because missing "tmp" folder inside ramdisk? also some file permissions fixed inside ramdisk)
1.4.0 -> 1.5.0
Upstream Kernel Changes to 3.0.101 - thanks a lot to @Fred6681 for fixing some know Problems after Upstream!
Build Xpad module (not tested if it is working)
Enabled DVFS Limit to make the Kernel boot on Stock and AOSP Roms
New Charger-Animation - thanks a lot to @daywalk3r666
[u]25.08.2014[/u]
1.3.1 -> 1.4.0
Initial CM 10.2 support
[u]22.08.2014[/u]
1.3.0 -> 1.3.1
Fix 800mhz bug, thanks to @Fred6681
1.2.0 -> 1.3.0
Updated Android 4.4 ramdisk: this will fix broken Wifi on Novafusion Roms / Roms based on Novafusion source
Build exFat as module
[u]20.08.2014[/u]
1.1.0 -> 1.2.0
Added Stock / Stock based 4.1 Support
More i/o scheduler: Added sioplus | row | zen
Compiled using GCC 4.7 again for better compatibility
Update LZO compression
arm/vfp: Makefile optimization
and some more....
1.0.5 -> 1.1.0
Fixed bootmenu flickering / blackscreen :) now the bootmenu is 100% visible
(Reboot-Recovery option from bootmenu not working, ends in kernel-panic,
reboot bootloader not working, it will normal reboot)
partially restore initial cm11 ramdisk
cleanup cm11 ramdisk
[U]19.08.2014[/U]
1.0.4 -> 1.0.5
Update permissions inside init.samsunggolden.rc,
set SELinux to permissive for now,
lzma compressed ramdisk
1.0.3 -> 1.0.4
Use Linaro 4.8 Toolchain
[U]18.08.2014[/U]
1.0.2 -> 1.0.3
Use Linaro 4.7-2013-04 Toolchain
[U]12.08.2014[/U]
1.0.1 -> 1.0.2
- fix an Superuser issue, added back init.superuser.rc
1.0.0 -> 1.0.1:
- fix "com.android.phone" crashed on Vanir Rom
1.0.0:
- initial release
How-To
Flash PhilZ Touch Blackhawk Recovery
Reboot into PhilZ Touch Blackhawk
Flash NEXT Kernel
Advanced Functions -> Run Aroma Dual Boot Tool
Create a 2nd System.img (choose 1 GB)
Reboot your recovery
Choose the 2nd Bootoption (it is flickering, black screen, just press the volume down key one time and press the power button).
Now the navigation buttons inside PhilZ Touch are RED
Flash a 2nd Rom (i tested my own SlimKat and @golden-guys OmniROM because they don't use F2FS)
Flash NEXT Kernel again
Reboot
Now you will see a Bootmenu (flicckering & blackscreen), you will see it short if you press the volume key,
first option = boot 1st Rom, second option = boot 2nd Rom
USE ON YOUR OWN RISK! MAKE A BACKUP BEFORE TRYING!
Reserved
Dual Boot FAQs
Adapted from @ketut.kumajaya s Dual-Boot FAQ,
original adapted from droidphile's "Dual Boot FAQs".
1. "Why would I wanna dual-boot?"
A. You don't have to.
You need one testing system and don't want to break your daylie Rom.
You can not decide between different Roms - use both
2. "What if I don't need dual booting?"
A. No issues. Kernel won't force to setup 2 roms. You can single boot as before.
3. "Will dual booting change my bootloader or do any dangerous stuff like setting my phone on fire?"
A. NO. Changes are at kernel and ramfs level only. Some space in your internal sd card is used, and also the unused hidden partition mmcblk0p24 is used to store cache of second rom. Dual booting doesn't repartition the filesystem or perform anything scary.
4. "I want to setup dual booting."
A. There are four situations:-
Prerequisites for any setup is
a) Flash latest blackhawk's NEXT kernel.
b) Flash latest Extended PhilZ Touch recovery: http://forum.xda-developers.com/showpost.php?p=54772218&postcount=2
c) Atleast 90% battery left.
d) 3 GB free on internal SD.
e) Some spare time
1) Present AOSP, setup AOSP as secondary:-
i) Reboot into recovery
ii) Select "Run Aroma Dual Boot Tool" in Advaced Menu, create system.img for CM/CM based ROM and then close it
iii) Reboot into secondary recovery (red on screen navigation buttons)
iv) Flash AOSP ROM as 2nd ROM
v) Flash blackhawk's NEXT kernel again
2) Present AOSP, setup aosp as primary:-
i) Reboot into recovery
ii) Nandroid backup your current sammy ROM
iii) Select "Run Aroma Dual Boot Tool" in Advaced Menu, create a 2nd system.img and then close it
iv) Reboot into secondary recovery (red on screen navigation buttons)
v) Nandroid restore your AOSP ROM as 2nd ROM
vi) Flash blackhawk's NEXT kernel again
vii) Reboot into primary recovery
viii) Flash AOSP ROM as 1st ROM
ix) Flash blackhawk's NEXT kernel again
5. "What things should I be taking care off while dealing with dual booting?"
A. - Make sure where you are: in primary or secondary recovery.
6. "How to boot into primary rom?"
A. AROMA based boot menu will help you on every boot.
7. "How to boot into secondary rom?"
A. AROMA based boot menu will help you on every boot.
8. "Is kernel partition shared?"
A. Yes. Same kernel boots both roms.
9. "If I flash another kernel (that doesn't support db) do I lose dual booting?"
A. Yes
10. "I lost dualbooting after flashing another kernel. I didn't do anything to second rom files in sdcard/.secondrom. How can I get db back?"
A. Just flash the latest blackhawk's NEXT kernel
11. "Will there be any performance degradation on the rom used as secondary compared to primary?"
A. NO
12. "Will my phone run slow overall because of db?"
A. NO
13. "How to flash a newer version of 1st rom?"
A. As usual, just flash it from primary recovery. Flash blackhawk's NEXT kernel again
14. "How to flash newer version of 2nd rom?"
A. Just flash it from secondary recovery. Flash blackhawk's NEXT kernel again
15. "Would upgrading 1st or second rom cause other rom to fail on boot?"
A. No. Partitions of other rom are not touched during upgrading.
16. "I miss the recovery I used before, so much.."
A. PhilZ Touch not bad at all.
17. "User apps of 1st rom are automatically available for second rom?"
A. NO. However, if you had backed them up using Titanium Backup or similar apps, just restore apps while on second rom.
18. "I wanna keep separate backup for apps in both the Roms, since I use one Rom for say entertainment and other productivity."
A. Setup different backup directory in Titanium Backup in 1st and 2nd rom.
19. "Do I need to anything special before flashing a newer blackhawk's NEXT kernel?"
A. NO. Just flash kernel in recovery - whichever you used to do. Kernel image is copied to the unified kernel partition
20. "How do I remove everything related to DB and run single boot again?"
A. In primary recovery, flash blackhawk's NEXT tool or "Run Aroma Dual Boot Tool" in Advaced Menu from PhilZ Touch Blackhawk and delete 2nd ROM system image. OR delete .secondrom directory in /data/media while on 1st Rom.
21. "If secondrom files are kept in /data/media, will wiping data in recovery erase second rom files?"
A. NO. /data/media is skipped in CWM recovery.
22. "I read somewhere that both rom data partition use the same space. Doesn't that mean my apps are shared across roms?"
A. NO. It just means they uses same partition. They're still different directories.
1st rom data = /data
2nd rom data = /data/media/.secondrom/data
23. "Will hitting "Boot into Secondary Recovery" in recovery boot menu change my recovery?"
A. NO. It just runs (not flash) an alternate recovery so that you can configure dualboot settings.
24. "How do I backup 1st Rom and 2nd Rom?"
A. To backup 1st Rom, do what you did to backup rom while you were single booting a while ago.
To backup 2nd Rom, use the secondary recovery.
25. "Is there an easier way for dual-boot?"
A. Yes, send your device to me.
26. "DB architecture?"
A. Like you know, every rom has a /data, /system, /cache partition and a kernel to boot.
For primary rom, it's
mmcblk0p25 = /data
mmcblk0p22 = /system
mmcblk0p23 = /cache
And these won't change whether you're single booting or dual booting.
For secondary rom, data and system is stored in internal sd, cache in hidden partition.
Note that internal sd in our device is mounted to /data/media.
We have data as a directory, System as an image in data/media/.secondrom.
Cache in mmcblk0p24 which is hidden partition and not used otherwise.
- When second rom is booting, second rom data is bind mounted to mmcblk0p25 as /data/
- data/media/.secondrom/system.img partition is mounted as /system.
- dev/block/mmcblk0p24 is mounted as /cache.
How to get important Logs
tonyp said:
The three most important log types are:
logcat: the logoutput of the Android system
radio logcat: the log outpur ot your System / BB / RIL communication
kernel log (kmsg / dmesg): the kernel messages
Additionally there's the last_kmsg which is a dump of the kernel log until the last shutdown.
Normal Logcat:
Code:
adb logcat -v time -d > logcat.log
Radio Logcat:
Code:
adb logcat -b radio -v time -d > logcat_radio.log
Note: Cyanogenmod (based) ROMs require the following setting to export kernel logs via adb:
Settings - Developer Options - Root access - choose: "Apps and ADB"
Kernel Log:
Code:
adb shell su -c dmesg > dmesg.log
Last_kmsg:
Code:
adb shell su -c "cat /proc/last_kmsg" > last_kmsg.log
Click to expand...
Click to collapse
More FAQs will be added and the list will be updated as DB is improved.
Wow!
another milestone in the S3 Mini history!
Keep it up bro :good:
Incredible!!
This will bring my two favorite ROMs on one device!! Unbelievable Till now, I thought it is possible only with linux lubuntu and ROM, like on my tab...
Thank you!
m.
This is amazing! Can we use roms like debloated stock with your roms?
Sent from my GT-I8190/Novafusion CM11
Don't you read the OP?!? Not for stock ROMs! And 4.4.x only!
m.
meduza2 said:
Don't you read the OP?!? Not for stock ROMs! And 4.4.x only!
m.
Click to expand...
Click to collapse
Ah missed that part! Thanks for pointing out.
Sent from my GT-I8190/Novafusion CM11
No worries
m.
heithered said:
This is amazing! Can we use roms like debloated stock with your roms?
Sent from my GT-I8190/Novafusion CM11
Click to expand...
Click to collapse
Will try to add Stock 4.1.2 support sometimes later.
Send from OnePlus One using Tapatalk
Android-Andi said:
Will try to add Stock 4.1.2 support sometimes later.
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
Hey, this is a big deal. It is still awesome with or without stock support! Thanks for your awesome work!
Sent from my GT-I8190/Novafusion CM11
Well, just to leave an "Amazing work" as always:good:
great work.....dual boot with slimkat and omnirom works perfect.with vanir "com.android.phone" crashed
Top Job and faster as Nova!!!!
especially for you
@Android-Andi,
because of the world first dual boot for our s3mini, we created extra an info banner for you
Please have a look: Weltpremiere bei hubo.in
meduza, bodo_1, daywalksr666, kingg
Wow, you did it! That's so cool! Thanks a lot for this! ?
Simply awesome
It is incredible what AA made for our device.
But what is the sense of this mod?
I can use only one ROM at the same time.
Or am I wrong?
I am happy for explanations
The only idea i have:
First ROM for daily use
Second ROM for testing and replacing with different ROMs...
m.
moonryder said:
It is incredible what AA made for our device.
But what is the sense of this mod?
I can use only one ROM at the same time.
Or am I wrong?
I am happy for explanations
m.
Click to expand...
Click to collapse
you can load two roms to your phone.
at start up,you can choose either of 2 roms.
may be from recovery mode I think.
this is all what I know. hope I helped.
waiting for correction if I was wrong.
thanks and great work and much appreciation to Android Andi bro
@moonryder,
you could quickly boot one of your favorite ROMs or use the second boot partition for test ROMs....
m.
The Prehistory of UltimateROM
About a month ago I decided to set out to improve the performance of my phone with a more optimized build. I had already begun building OmniROM 5.1.1 with a some set of optimizations based on the work of OptiPop Team, and shortly after some the major issues on Marshmallow on our devices were resolved, this idea to create an ultimatively optimized AOSP-based ROM has born.
Why Should You Use UltimateROM? What makes it different?!
Honestly, I don't necessarily care, how many users or downloads my ROM has. Most importantly, and what I do care about is people liking and enjoying their phone; if you try UltimateROM and you like it, great! I'm glad you enjoy it. If you don't, maybe leave some feedback on how I can improve it, and go try something else in the meantime. If you'd like to know, what I've done that makes this ROM unique, here is a list:
Highly optimized. similar to Linaro(and in many ways, better than), build, resulting in a smoother Android
Compeletely developed in the open, everything I do is right on my GitHub for anybody to use and improve upon.
A unique kernel which attempts to balance features, stability, and of course, performance
Almost the sources, excluding apps, the SystemUI and some more, are based on CyanogenMod ones, which means there are more fixes and support for our legacy devices (even though CyanogenMod itself doesn't really support any devices like our, anyway google doesn't even do that minimal support as CM Team does)
Disabled SELinux. Looking backward on how many issues SELinux was causing and still causing for people that use it on MM, it seems to me a ridiculuos how google promotes and implements it everywhere, without any proof of improving anything rather than making worse.
Current Information
Everything I do with UltimateROM I always test personally on my phone, but anyway...
Code:
#include <disclaimer.h>
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modifications, and
* if you point your finger at me for messing up your device, I will
* laugh at you.
*/
Please also note that currently I don't test installation with the Gapps. So far installation is only tested as dualboot ROM - though, the uploaded build is an usual one, - please let me know if the uploaded build has issues with booting, even though normally this should not happen.
What's working:
RIL (phone/SMS/3G)
Video (playback & recording)
Audio (playback & recording)
Wi-fi
Bluetooth
Camera (Front and rear)
2D/3D HW Acceleration
USB, MTP, ADB
all native tethers (Wifi/BT/USB)
external storage
What's not
Formatting SDcard as adoptable storage will screw it up (don't format / encrypt)
MTP bug with doubled folders in sdcard root folder
ROM features:
Dark Marshmallow Theme
long volume press to skip track
PA Pie control
SlimRecents / improved AOSP recents
Re-added task manager
Navigation Bar
System UI tuner
expanded desktop
storages are swapped by default
extended reboot menu
customizable button backlight settings
Viper4Android FX
superuser embedded
Download
UltimateROM
Installation
Before installation, make sure that you have enough free space on partition /system. AT LEAST 540 Mb is required for this build if installing WITHOUT any Gapps. If you don't have enough space, follow repartition manual. (at your own responsibility for any kind of possible damage. Be sure to measure twice and cut once!). There is a CWM ReParted zip that was tested by @Culateralligator.
wipe cache
make sure you're using TWRP 2.8.6.0. All the below is only tested on this recovery. Philz is not supported by this ROM and not planned to in the near future. Note that TWRP from the linked topic requires preinstalled chrono kernel.
install ROM first
install latest chrono kernel
install gapps (optional), if you do so, make sure you are not running of space on /system ( about GApps )
Sources:
https://github.com/UltimateROM/android_manifest
Thank Yous
SergeyL - many-many thanks for an initial set of patches, device tree and TWRP 3.0.0.0! Also thanks for helping me implementing some features to this ROM.
JDCTeam, BenzoROM - thanks for great cherry-picks!
MWisBest - this project was heavily inspired by his FML (Fork My Life) ROM
OptiPop - an initial set of optimizations that the currently used by me is based upon
@Meticulus - thanks for his great contributions on our devices!
@AGONTUK - thanks for an initial Marshmallow bring up!
@nieltg - Sources for Galaxy Ace 2 device
@golden-guy - thanks for great cherry-picks !
@TeamCanjica - vendor and hardware sources
@Unjustified Dev - Audio fixes
Google
CyanogenMod
AOKP
SlimROMs
EuphoriaOS
OmniROM
AOSPA
Viper4AndRroid Team
And many other devs, I could forget (please write me if I did so).
Special Thanks
@shaqman89 - for providing the build server
@S.AMU - for providing FTP server
XDA:DevDB Information
UltimateROM, ROM for the Samsung Galaxy Ace II
Contributors
ChronoMonochrome, SergeyL, JDCTeam, OptiPop Team, BenzoROM, OmniROM, AOKP, CyanogenMod, SlimRoms, AOSPA, Temasek.
Source Code: https://github.com/UltimateROM
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Stock 4.1.2 ROM or up + kitkat-compatible recovery
Based On: AOSP, CyanogenMod
Version Information
Status: Stable
Created 2016-03-20
Last Updated 2018-08-20
Changelogs
Changelog
20.08.2018 - build #13
sources update
switch to opensource sensors
switch more device libs to open source base
unified codina / janice build
02.12.2017 - build #12
fixed native moving apps to SDcard
APP2SD and similar apps now should work correctly *
fixed second incoming call not to crash rild (not tested, needs confirmation), thanks to @SergeyL
small RIL fixes
NOTE: installation method was updated. Flash latest chrono kernel build after this ROM install.
02.04.2017 - build #11
kernel updated to r5.0
sdcard mount fixes
integrated an unofficial build of the Xposed framework
ported the utility mtools *
* for repairing the broken sdcard label you can move the file /system/bin/mtools to /system/xbin folder, then type in the terminal emulator mlabel/i]. It will show the current sdcard label and will prompt to type the new one.
27.02.2017 - build #10
updated sources to 6.0.1_r78
added an initial support of the PowerHAL *
ported some changes from Resurrection Remix 7.1.1 build (thanks to SergeyL for patches)
updated kernel to r5.x.x (mostly updates from google android-3.4 kernel)
changed recovery to TWRP 3.x.x
unstable MySQL optimizations are reverted
changed buttons backlight mode - backlight is only enabled when buttons are pressed
experimental change scheduling policy of the surfaceflinger to FIFO
maybe, something yet
* at the moment there's no support of changing the PowerHAL profiles from the Settings, however, you can change profile in a file /system/etc/init.d/999powerhal
Proceed installation of this build only with data wipe.
20.09.2016 - build #9
Fully switched to an opensource RIL! Many thanks to Meticulus for finding the working RIL sources and fixing it, also I'd like to thank millosr and mickybart from Nozomi (Xperia S) forum for fixing the crash when performing a call and providing patches for debugging the proprietary libril!
More libs now are built from source - credit goes to Meticulus
Added sdcardfs support (requires at least build r4.8 of Chrono Kernel)
Added home key press to accept the incoming call and power key press to end the active call features from CyanogenMod - thanks to SergeyL for helping with finding those patches
Changed LowMemoryKiller tunables to the more aggressive + increased zram size to 400Mb - multitasking should be (hopefully) better
Changed Dynamic governor tunables to be more aggressive
Various minor fixes that improves the stability of ROM
We've also finally got rid of all shim (i.e. interposed) libraries that were needed in order for some features (camera, GPS etc) to work
30.05.2016 - build #8
updated wifi autoconnection fix (fixed the battery stats)
fixed SystemUI FC when switching USB mode via status bar notification
fixed GSM / WCDMA preferred / WCDMA Only switching
fixed soft reboot when switching 2G/3G with an enabled mobile data
added Pie Control from Paranoid Android
added SlimRecents
updated AOSP recents implementation ("clear all" button doesn't properly work, so don't enable it or use SlimRecents)
added task manager
allowed disabling of brighness slider disabling
revert AOSP camera to 5.1.1 (fixed the photo cropping issue)
added FAT images mounting via UMS support (use
sys.config.opt_sd0device=full_path_to_the_image.img build.prop setting to override the device mounted as Sdcard0 or sys.config.opt_sd1device for Sdcard1)
26.05.2016 - build #7
Work around wifi autoconnection issue
Fixed video encoding issue by some apps (instagram video upload etc) - thanks to Meticulus for the original patch
Added LockClock back
Added option to show the weather in the status bar
Various small improvements, tweaks etc.
23.05.2016 - build #6
More ROM modules compiled with GCC instead of Clang (GCC supports more optimizations)
Almost ROM modules compiled with Link Time Optimizations
Enabled graphite optimizations for more ROM modules
Added autovectorization optimization on per-modular base
More modules built in ARM mode
Allowed disabling of FC notification
Added time-context custom header images feature
Added customization of the carrier label
Added SystemUI tuner
Added display autorotation setting
19.05.2016 - build #5
updated kernel to r4.4.1
added and enabled by default UMS (USB Mass Storage) mode
re-added some default AOSP optimizations
added navigation bar
added battery level icon customization setting
added long back press to kill app feature
remove 3 secs delay in Superuser before to give the app permissions
added feature of disabling mediascaner at boot
added Sqilte performance improvements
disabled an unnecessary debug
another fixes / improvements
fixed graphical glitches in some apps caused by new UMP lib
resized bootanication (thanks Lemu @ 4pda.ru)
fixed init.d scripts
added aggresive Dynamic governor settings
13.05.2016 - build #4
cleaned up the default google optimizations, removed unnecessary flags
disabled forcible ARM mode optimization - until I revisit this again
added performance settings from OmniROM
added CM Filemanager
added a few more opensource code to libUMP, replacing calls to old library
fxed up an inadeqate CPU time consumption caused by logd process
6.05.2016 - build #3
updated sources to 6.0.1_r30
kernel update to r4.3.1
switched to GCC 5.3 toolchain by UBER
enabled graphite, fast math, loop nest, unsafe loop and some more optimizations
entire build is compiled in ARM mode
switched to opensource RIL libraries (based on CyanogenMod repos)
UMP (Unified Memory Provider) library now is mostly opensource - based upon CM sources
Attempt to fix storage permission issues in some apps such as browser - not tested
fixup for RIL java code - thanks to @SergeyL
disabled scrolling cache
SQLite code optimizations
Reduced various delays
many other fixes and improvements - thanks to SergeyL for patches
20.03.2016 - build #2
fixed APN editor crash
added removed fonts back
removed Gallery, Calendar and PrintSpooler
Viper4Android driver post-install (no need to install manually anymore)
Fixed busybox related issues
20.03.2016 - build #1
initial release
Miscellaneous
reserved
Take some time to try this ROM, and now there are some issues
1.there are lost 4 opentype fonts (compared with Sergeyl's CM13)(JP,KR,SC,TC-Regular),so Simplified Chinese display likes XXX
2.V4A needs to works with busybox, lol...
But ROM works smooth
fim5646 said:
Take some time to try this ROM, and now there are some issues
1.there are lost 4 opentype fonts (compared with Sergeyl's CM13)(JP,KR,SC,TC-Regular),so Simplified Chinese display likes XXX
Click to expand...
Click to collapse
These are removed, because of overly sized ROM. Are these fonts only that support these languages? If so, I'll of course re-add them. I was comparing this ROM to my OmniROM and haven't found these fonts, so I thought they can be safely removed.
2.V4A needs to works with busybox, lol...
Click to expand...
Click to collapse
I guess, it's common 6.0.x problem, as busybox has got partially replaced by toolbox and toybox from AOSP, thus making some apps confused.
ChronoMonochrome said:
These are removed, because of overly sized ROM. Are these fonts only that support these languages? If so, I'll of course re-add them. I was comparing this ROM to my OmniROM and haven't found these fonts, so I thought they can be safely removed.
Click to expand...
Click to collapse
Yeah,these 4 fonts only support Janpanese,Korean,Simplified Chinese and Traditional Chinese,(lastest outdated AOSP 6.0 has same problem...）Maybe OmniROM has different font files
ChronoMonochrome said:
I guess, it's common 6.0.x problem, as busybox has got partially replaced by toolbox and toybox from AOSP, thus making some apps confused.
Click to expand...
Click to collapse
Yeah....
Is there any way to fix sdcard problem?
And thanks for this awesome rom.
Fake2Dead said:
Is there any way to fix sdcard problem?
Click to expand...
Click to collapse
What problem exactly?
What GApps should we install, these modified by SergeyL? open_gapps-arm-6.0-pico-20160204.zip
https://yadi.sk/d/HX0CiHNnoGiC5
Culateralligator said:
What GApps should we install, these modified by SergeyL? open_gapps-arm-6.0-pico-20160204.zip
https://yadi.sk/d/HX0CiHNnoGiC5
Click to expand...
Click to collapse
GApps aren't personally tested by me, but I guess, you'll need those provided by SergeyL else keyboard will crash.
ChronoMonochrome said:
What problem exactly?
Click to expand...
Click to collapse
phone says sandisk sd card is corrupted. I tried to format from phone but it didn't work. Also i can't use my camera without external sdcard. And why extsdcard is sdcard0
"Sorry for my english if a have a fault"
Fake2Dead said:
phone says sandisk sd card is corrupted. I tried to format from phone but it didn't work. Also i can't use my camera without external sdcard. And why extsdcard is sdcard0
"Sorry for my english if a have a fault"
Click to expand...
Click to collapse
Did you format your sdcard as adoptable(internal) storage? This is something you actually shouldn't do and it's explicitly mentioned in the issues list as it doesn't work properly on our devices. SDcard should normally work without formatting (in case of M - which also performs encrypting of it), thanks to @SergeyL work. Now you have to format sdcard from Windows / *nix / whatever other OS; if even this won't help, we'll probably need a volunteer to test it. Personally for me sdcard works, but you may want to try SergeyL's CM13 to see if it's working there.
WiFi is unstable, lost connection from time to time, Web Browser is crashing. And any of gapps do not work - do not fit in system. Yes, i readed first post, i have orginally partitioned internal card and do not want touch it. SergeyL's CM13 work with smallest gapps
ChronoMonochrome said:
Did you format your sdcard as adoptable(internal) storage? This is something you actually shouldn't do and it's explicitly mentioned in the issues list as it doesn't work properly on our devices. SDcard should normally work without formatting (in case of M - which also performs encrypting of it), thanks to @SergeyL work. Now you have to format sdcard from Windows / *nix / whatever other OS; if even this won't help, we'll probably need a volunteer to test it. Personally for me sdcard works, but you may want to try SergeyL's CM13 to see if it's working there.
Click to expand...
Click to collapse
Thank you so much for help. I tried to format from windows(exfat) and it worked!
Edit: Don't try to format sdcard as fat32 it didn't worked on me
Pastorious said:
WiFi is unstable, lost connection from time to time, Web Browser is crashing. And any of gapps do not work - do not fit in system. Yes, i readed first post, i have orginally partitioned internal card and do not want touch it. SergeyL's CM13 work with smallest gapps
Click to expand...
Click to collapse
I can confirm Web Browser is unstable.
I haven't those WiFi problems yet, but I'm testing for little time.
What do you mean with smallest GApps?
I've tried no repartition + SergeyL GApps and I get ERROR CODE 70 -not enough system space-.
Culateralligator said:
I
What do you mean with smallest GApps?
Click to expand...
Click to collapse
I found somewhere gapps ~45MB, still too big for install, i have no idea how install Play shop
New build is 20.03.2016(#2) UP!
Changelog
fixed APN editor crash
added removed fonts back
removed Gallery, Calendar and PrintSpooler to free up some space
Viper4Android driver post-install (no need to install manually anymore)
Fixed busybox related issues
Might fix GApps not being fitted on /system issue in the future, but I'll need a volunteer to test the new partition scheme. If anyone knows how to modify CWM repartition scheme zip and create a new one with ~700-750Mb on /system, it would be even much great, because right now I have absolutely no time for this.
Enjoy!
Something weird... I've connected phone to PC 5-6 times.
Last 2 times appears sdcard1 with 1,09GB (real internal sd).
However, I have access to files of real external sd. But when I try to paste a file, it says I have no space for it.
Succesfully installed gapps removed printspooler webbrowser gallery calendar clock and 1 more thing and i found 48 mb gapps
Culateralligator said:
Something weird... I've connected phone to PC 5-6 times.
Last 2 times appears sdcard1 with 1,09GB (real internal sd).
However, I have access to files of real external sd. But when I try to paste a file, it says I have no space for it.
Click to expand...
Click to collapse
Indeed, it seems that I have misapplied one fix to the vold binary. Does this issue also appear on CM13?
P.s. it's possible that vold from CM13 will also work, because UltimateROM use same sources as CM. Can anyone try replacing /system/bin/vold and check if it helps?
Unofficial CyanogenMod 13.0 for Samsung Galaxy Tab 3 10.1
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, ...
* You flash this at your own risks
*/
About CM
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Important information
You need a recent TWRP version to flash this ROM.
Installation
First time installing, coming from another ROM or upgrading from alpha < 4
Copy ROM to SDCard
Copy Houdini to SDCard
Copy GApps to SDCard
Boot into recovery
Backup EFS partition
Wipe -> Advanced Wipe -> Dalvik Cache + System + Cache + Data
Install ROM
Install Houdini
Install GApps
Reboot
First start takes a long time
Upgrading from earlier version of CyanogenMod 13.0 (alpha >= 4)
Copy ROM to SDCard
Boot into recovery
Install ROM
Reboot
[OPTIONAL] Converting filesystem to F2FS (thanks @michiil)
The ROM has F2FS support. You may want to use it instead of the default (EXT4).
This will delete ALL files/data from your tab.
What you will need: A working PC and a working USB cable.
Install the most recent Recovery
Download the most recent Recovery from the second post. Flash the zip file in recovery. Back in the main menu press Reboot > Recovery
Format Data and Cache to F2FS
Wipe > choose Cache > repair or change file system > change file system > F2FS > Swipe to Confirm
Go back and repeat the same steps with Data. I got some error messages when formatting Data but they don't seem to be a problem.
Back in the main menu press Reboot > Recovery
Install Rom + Houdini + Gapps
Connect your tab to your PC and copy the zip files on the tab.
Flash the files, reboot and enjoy :good:
How to get back to EXT4
You will again loose all files/data on the tab.
Just repeat Step 2 but use EXT4 instead of F2FS.
What's working
RIL (audio calls, data, sms, mms)
2D/3D acceleration
HW video encoding/decoding
Screen cast (Miracast/Wifi Display)
MHL/HDMI
Sound
InfraRed
Camera
Wifi
Bluetooth
GPS
Sensors
SDCard, USB OTG
Tethering (USB, Bluetooth, Wifi)
Software DRM (Level 3, see below)
Known to be working
Google Movies
Amazon Prime Video
Molotov TV
myCANAL
Canalplay Kids
Known *not* to be working
6play
Features
Automatic brightness
Change Color profile
Change mDNIe scenario
Enable/disable mDNIe negative mode
Multiuser
Enable/disable capacitive keys
Change capacitive keys width
Buttons backlight on screen touch or key touch only
Smart cover lock/unlock
F2FS and exFAT support
Houdini (allows to install arm only apps on this x86 device)
Updated ZRAM support with LZ4 compression for maximum memory and speed
Updated Xbox Controller driver
Updated interactive CPU governor
Available CPU governors: powersave, interactive, performance, ondemand
Available I/O schedulers: noop, deadline, cfq, bfq (v7r8), fiops
Available battery modes (CM power profiles): power save, balanced, performance
What's not working
Chromecast screencasting (other functions work)
Hardware DRM (Level 1)
SELinux (permissive)
You tell me
How to root
Go to 'Settings/About tablet'
Tap 7 times on 'Build number'
Go back
Go to 'Developer options'
Tap on 'Root access'
Select 'Apps only' ('Apps and ADB' if you plan to use it in adb shell)
How to help
When something is not working correctly, in addition to common informations, I may ask you to provide logs. There are different kind of logs and it's not always easy to get all of them. For this, you can use SysLog (available on F-Droid or Google Play).
Fixed in version 2.1.0 There is currently a bug in the app. Download it from AndroidFileHost. Use this patch if you want to compile it yourself:
Make sure to root device before using this app.
To get the logs:
Start SysLog
Click on 'TAKE LOG'
Once log is taken, SysLog will try to share the resulting file, just cancel
Send me the file /sdcard/SysLog/[YYYY-MM-DD_HH.mm]/[YYYY-MM-DD_HH.mm].zip
If you left 'Scrub potentially personal information from the logs' checked, you should be safe.
Sources
Kernel
Common: https://github.com/santos10-dev/android_kernel_samsung_santos10/tree/cm-13.0
Device trees
Common: https://github.com/santos10-dev/android_device_samsung_santos10-common/tree/cm-13.0
Galaxy Tab 3 10.1 3G: https://github.com/santos10-dev/android_device_samsung_santos103g/tree/cm-13.0
Galaxy Tab 3 10.1 Wifi: https://github.com/santos10-dev/android_device_samsung_santos10wifi/tree/cm-13.0
Galaxy Tab 3 10.1 LTE: https://github.com/santos10-dev/android_device_samsung_santos10lte/tree/cm-13.0
Local manifest
https://github.com/santos10-dev/android_device_samsung_santos10-common/wiki/Local-manifest-CM-13.0
Credits
Angel_666 , moonbutt74 and Restl3ss for starting the work on this device
Android-Andi for his device tree
crpalmer for his work on Intel support
Deltadroid for his GApps package
All testers of the "signup" thread
CyanogenMod and Google for Android
XDA
AndroidFileHost
XDA:DevDB Information
CyanogenMod 13.0 for GT-P52XX, ROM for the Samsung Galaxy Tab 3 10.1
Contributors
nels83
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2016-03-21
Last Updated 2017-04-11
Downloads
ROM
ROM - Beta 2 (20161210)
Galaxy Tab 3 10.1 3G : santos103g (MD5)
Galaxy Tab 3 10.1 Wifi : santos10wifi (MD5)
Galaxy Tab 3 10.1 LTE : santos10lte (MD5)
You can find old versions on AndroidFileHost. Version code is in file description.
Houdini 6.0.0_x.47745
Houdini for Android 6.0
GApps
See Open Gapps, select Platform x86 and Android 6.0.
Other
Flash player (11.1.112.60)
Flash player for x86
Note: not much used nowadays but useful if you want to play flash games.
Changes
Changelog
Beta 2 (20161210)
- Fixed audio calls
- Switched to dlmalloc
Old changes
Beta 1 (20161204)
- Fixed freezes
- Fixed AGPS
- Cleaned up sensors hal
- Use opensource audio hal
- Added FIOPS io scheduler
Alpha 7 (20161121)
- CM update (android 6.0.1_r74)
- Added software DRM support (Level 3)
- Fixed touchscreen lags (maybe not all lags, thanks to @Alphita and @KNGPN Q w Q)
- Fixed lock screen rotation (thanks to @tinko975)
- Fixed Google SetupWizard loop when no network is available (CM)
Alpha 6 (20161018)
- CM update
- Updated kernel memory management (and removed samsung specific code)
- Updated kernel android drivers
- Fixed button lights always on when disabled
- Fixed rotation (small) bug
- Fixed deep sleep issues
- Fixed many reboot issues
- Enabled CABC
Alpha 5 (20160822)
- Updated to stable/cm-13.0-ZNH5Y branch
- Enabled Doze mode (thanks to @vin_)
- Enabled 180deg rotation by default
- Enabled swap volume keys on rotation by default
- Added MHL/HDMI support
- Added houdini Intel patches for better compatibility
- Added USB charger port support
- Fixed fast/slow charging reports
- Fixed buttons backlight on key touch only
- All kernel modules are now builtin
- Various tweaks
Alpha 4 (20160731)
- Switched back to stable/cm-13.0-ZNH0E branch
Alpha 3 (20160727)
- CM update
- Fixed Flash Player
- Fixed /dev/last_kmsg
- Fixed cpuset
- Tweaked power management
- Implemented CM power profiles (battery modes)
- Added color profile setting (in LiveDisplay)
- Added Advanced Settings (mDNIe scenario, large/small capacitive keys, buttons light on screen/button touch)
- Added stock charger images
Alpha 2 (20160430)
- Based on stable/cm-13.0-ZNH2K branch
- First try at RIL (3G and LTE)
- Fixed Wifi tethering (thanks @deadfun)
- Enabled and tweaked cpusets (fixes SMP "bug")
- Updated and tweaked cpufreq interactive
- Updated xpad driver (thanks @X-Coder)
- Updated kernel config (merged android recommended settings)
- Added bfq io scheduler
- Enabled deadline scheduler
- Enabled powersave cpufreq scaling governor
Alpha 1 (20160321)
- First release
- Based on stable/cm-13.0-ZNH0E branch
Thanka @nels83 i was waiting for this since morning ?
why does RIL not working? its the most important thing for me
Awesome it works
How to Upgrade from CM12?
Spegeli said:
How to Upgrade from CM12?
Click to expand...
Click to collapse
Download TWRP, opengapps, houdini and the rom (corresponding to your device)
Backup all your data (pictures, music etc.) and apps (preferably with apps like titanium backup) to your PC
put the zips from above onto your sd card (if you don't have one, use the internal storage)
boot into recovery of your tab
wipe /system, /cache, /data, dalvik cache and (if you don't have important data like the zips on there) the internal storage
flash the files in the following order:
TWRP (then restart your device into recovery)
ROM
Houdini
Gapps
if you want to do it: reformat /cache and /data now with f2fs
reboot into system
connect your device to the pc again and get your backed up files and apps
reinstall apps through the play store and if you want to: get their data back with Titanium Backup
Done.
EDIT:
it's nice that CM13 is out and that Houdini is working
though I'm going to wait for RIL support before I update
How complicated is it to fix/How long will it take (min)? (if you can say that)
Dj_Fex said:
Download TWRP, opengapps, houdini and the rom (corresponding to your device)
Backup all your data (pictures, music etc.) and apps (preferably with apps like titanium backup) to your PC
put the zips from above onto your sd card (if you don't have one, use the internal storage)
boot into recovery of your tab
wipe /system, /cache, /data, dalvik cache and (if you don't have important data like the zips on there) the internal storage
flash the files in the following order:
TWRP (then restart your device into recovery)
ROM
Houdini
Gapps
if you want to do it: reformat /cache and /data now with f2fs
reboot into system
connect your device to the pc again and get your backed up files and apps
reinstall apps through the play store and if you want to: get their data back with Titanium Backup
Done.
EDIT:
it's nice that CM13 is out and that Houdini is working
though I'm going to wait for RIL support before I update
How complicated is it to fix/How long will it take (min)? (if you can say that)
Click to expand...
Click to collapse
Not possible to Upgrade without loosing all Apps (and there Settings)?
sorry, I won't guarantuee you that anything is working if you leave the data partition and don't format it
even though it might be nice to keep the data
it's safer to backup your the data and apps that you need and then start fresh
and usually it's not even that much of a hassle (you just need to get used to it)
Nels says at the top:
if you come from an earlier version of cm13 then it's possible
but if you come from another rom (cm12) you need to wipe data
@nels83 I just noticed, your changelog link still points to the cm 12 branch (only a copy&paste issue of course so no big deal)
@nels83 Just upgraded from cm12,1 beta 2. This ROM works fine. Thanks
pvt-koffiejunk said:
@nels83 Just upgraded from cm12,1 beta 2. This ROM works fine. Thanks
Click to expand...
Click to collapse
do you fresh install the rom?or just dirty flash it and its work fine?
Anyone know how to make this rom black ?
Rom is buttery smooth, I am having issues with chrome being slow but that also happened on cm 12.1
Lionerx said:
do you fresh install the rom?or just dirty flash it and its work fine?
Click to expand...
Click to collapse
Just dirty. Figured I could always flash again and do the right way.
Strange I don't see option for downloading of GApps 6 86x at open GApps
Mrkijo said:
Strange I don't see option for downloading of GApps 6 86x at open GApps
Click to expand...
Click to collapse
maybe is temporarly down.. it worked for months.. with aosp rom too..
i download it yesterday.
edit:
here are links from few days before..
https://github.com/opengapps/x86/releases/tag/20160320
..
@nels83 just a quick info: if I use your P5210 device tree in my CM 13.0 source, can I build it from scratch? I'd like to experiment with that.
tinko975 said:
maybe is temporarly down.. it worked for months.. with aosp rom too..
i download it yesterday.
edit:
here are links from few days before..
https://github.com/opengapps/x86/releases/tag/20160320
..
Click to expand...
Click to collapse
Thanks, you were right, it was temporary and now it is on again ?
After 20 Hours of Testing, the Rom works good except:
- Kaspersky Internet Security crashed when starting a analysis
- Camera crashed when switching to Focus Effects or Video
The rest seems working fine so far.
Hi guys,
I've been building an extra lean CM13 ROM for hammerheadcaf with a few added features. A lot of CM packages have been stripped down, only the bare minimum is built to provide a fast and stable ROM. That gives you much more freedom as you can install exactly what you really want from the Playstore. You can install most of the missing packages manually, they are available in a flashable zip on the server (see second post).
Key features
ROM comes with TrueSight v3.0 builtin (with a few of my own tweaks)
Up to date MOB30Y vendor from Myfluxi's and Kylon's repo
Option to choose between dialer and voice assist in lockscreen
Option to hide next alarm from expanded status bar and lockscreen
Clock font and size customizable
Hide bluetooth icon when disconnected
Disable immersive messages
HeadsUp timeout and blacklist/whitelist
Longpress power button while screen off to trigger flashlight
Battery saver options
Keyboard options
SSID in status bar
Network traffic in status bar
Volume steps
Navigation bar size
Seconds in status bar
SuperSU builtin
AdAway and Xposed builtin (in developer options)
Synapse builtin
OpenDelta builtin for delta updates
ViPER4Android builtin (and working in Enforcing)
Optimizations
Every effort has been made to optimize the ROM the most :
ROM built with SABERMOD GCC 5.4 and DRAGONTC 4.0 (O3, Graphite, Strict aliasing, Polly, OpenMP, Pthread, LTO/ThinLTO, Krait tunings and lots of extra optimization flags)
KERNEL built with SABERMOD GCC 7.0 (O3, Graphite, OpenMP and lots of extra optimization flags)
Java built with OpenJDK 8
Removed some useless debugging
Installation
You will need latest radio (2.0.50.2.29) and latest bootloader (HHZ20h)
Latest TWRP recovery 3.0.2-0 for hammerheadcaf is highly recommended (and mandatory for delta updates)
If coming from any other ROM
Backup first... always backup first
Wipe system, data, cache and dalvik cache
Install ROM
Install GAPPS (opengapps are recommended)
Enjoy !
If coming from a previous build of mine
Backup (you know it)
Dirty flash
Enjoy! (if anything goes wrong, clean flash)
Xposed app is preinstalled and available in the developer options menu. BUT, you will have to install the Xposed framework in recovery if you want it. Afterward, it will survive dirty flashes, so you only need to flash it once. Please, be smart and only install required Xposed packages. Installing too many packages can cause weird behavior and I won't be responsible for it.
Download
To download the whole ROM
AndroidFileHost
To download delta updates
Go to Settings/About phone/System updates and use the OpenDelta app to automatically download delta updates.
Delta Updates
(Information to be confirmed later)
Here are a few explanations on how to use delta updates. First, you will need to keep the first full build you downloaded on your sdcard (any full build that have NIGHTLY in the filename will do). I recommend that you keep it on the root of your sdcard until you flash a new build with the OpenDelta app. After that, the OpenDelta app will automatically place a new flashable zip inside the OpenDelta folder that will be used for the next delta updates. At that point you can delete the build on the root of your sdcard, but you will need to keep the (latest) file in the OpenDelta folder at all times to keep the delta updates working.
You will also notice a folder named FlashAfterUpdate in the OpenDelta folder. As its name suggests, any flashable zip files that you put in this folder will be flashed automatically after the update. I recommend that you put all your extra flashable zips there, cause if you use the app to auto-flash the latest build, it will reboot automatically after updating, which means you won't have the opportunity to manually flash other zips.
Support
Please consider a donation if you like my work !!!
I hope you enjoy it !!!
Thanks and credit
CyanogenMod
@myfluxi
@lol4topnz
@kylon
@xanaxdroid
@frap129
@DVDandroid
@theapuv
All the good devs who contributed to the features I added
Extra Packages
On the server you will find a file named ExtraPackages_date.zip which contains a few apps that are not available out of the box in my builds (see list). You won't have to flash it every update, since there is a survival script. I suggest you open the zip and remove the files you don't need. As such, there are 2 browsers (Browser and Gello) and 2 cameras (Camera2 and Snap).
Here is what's included:
- Browser
- Gello
- Calendar
- Camera
- Snap
- Eleven
- Gallery
- Messaging
AudioFX
Those who prefer using AudioFX instead of ViPER4Android can now download a flashable zip named V4AtoAudioFX_date.zip that I uploaded on the server. It will uninstall V4A and install AudioFX. You won't have to flash it every update, since there is a survival script.
Changelog
08/21
- Upstream updates from CM
- Removed option to have 4 or 5 columns in QS
- Added option to have seconds in status bar
- Replaced Kernel Adiutor Mod with Synapse
- Added OpenDelta (in Settings/About phone/System updates)
- ROM built with GCC 5.4 SABERMOD
Older changelogs
08/13
- Upstream updates from CM
- Added option to have 3, 4 or 5 columns in QS
- Replaced Synapse with Kernel Adiutor Mod
08/06
- Updated to 6.0.1_r61
- August security patch
- Updated TrueSight kernel to v3.0
- Latest blobs from Myfluxi and Kylon (MOB30Y)
- Upstream updates from CM
- Updated Xposed Installer from DVDandroid
- ROM built with GCC 6.1 SABERMOD
07/27
- Upstream updates from CM
- Built with latest DragonTC 4.0
07/21
- Updated TrueSight kernel to v2.8
- Upstream updates from CM
- Updated Xposed Installer (DVDandroid version)
- Used Google Webview (in hope of fixing Google Play Services battery drain)
07/10
- Updated to 6.0.1_r52
- July security patch
- Latest blobs from Kylon (MOB30P)
- Updated TrueSight kernel to v2.7
- Added option to resize the navigation bar (in buttons settings)
- Added blurred lockscreen (in lock screen settings)
- Upstream updates from CM
- Updated SuperSU and AdAway
- ROM built with GCC 5.4 SABERMOD
- Removed DragonTC for now (fixes OK Google recognition)
06/27
- Updated TrueSight kernel to v2.6
- Upstream updates from CM
- Updated XposedInstaller (DVDandroid version)
- Used CM Webview (might need a clean install)
- Built with latest DragonTC 3.9
06/16
- Updated TrueSight kernel to v2.5 (fix for data connection problem)
- Tweaked some default kernel settings
- Upstream updates from CM
- Removed optimizations for some packages (fix for OK Google hotword not working)
06/09
- Updated to 6.0.1_r46
- June security patch
- Latest blobs from Kylon (MOB30M)
- Updated TrueSight kernel to v2.4
- Upstream updates from CM
- ROM built with GCC 5.3 SABERMOD
- Built with latest DragonTC 3.9
06/01
- Updated TrueSight kernel to v2.3
- Updated UKM to v3.9.3
- Updated XposedInstaller (DVDandroid version)
- Updated SuperSU to v2.74
- Updated Webview
- Upstream updates from CM
- ROM built with GCC 6.1 Linaro
05/27
- Added SSID in status bar
- Added Network traffic in status bar
- Added Volume steps
- Upstream updates from CM
- Updated TrueSight kernel to v2.2 (with temporary audio fix)
- Built with latest DragonTC 3.9
05/20
- Updated to latest CM upstream
- Updated TrueSight kernel to v2.1
- Updated Webview
- Removed double tap to sleep on lockscreen (broken since CM LiveLockScreen)
05/12
- SuperSU 2.72
- Upstream updates from CM
05/09
- Replaced KernelAdiutor with Synapse
- UKM preinstalled and fully working
- Fixed the clock size not sticking after reboot
05/06
- Updated to 6.0.1_r43
- May security patch
- Latest blobs from Kylon (MOB30H)
- Xposed Installer from dvdandroid
- Font and size of clock is now customizable
- Built with latest DragonTC 3.9
Looks promising and right up my alley! Will test and report back!! Thanks!
Edit: which gapps do you recommend? I have been using openapps, however with cm the compatibility seems to be lacking. So I switched to slimgapps, however, they have no launcher nor keyboard with them. I can find apks for the launcher and key board, but I don't think you can install them without a launcher correct?
Well this looks good. Just one question have you removed CM Theme Engine? Not that I'm complaining, just wanted to know.
Theme engine is still in.
See second post for info on how to manually install launcher and keyboard
Seems nice, do you use JustArchi's optimizations? And can i uninstall V4A easily enough because i want to use customized one?
And opengapps do work since 25.4, just remember to not use old builds you possibly have lying around.
V4LT5U said:
Seems nice, do you use JustArchi's optimizations? And can i uninstall V4A easily enough because i want to use customized one?
And opengapps do work since 25.4, just remember to not use old builds you possibly have lying around.
Click to expand...
Click to collapse
Well I use a lot more optimization than JustArchi's. But to answer the question, I have an equivalent form of the O3 optimization JustArchi has. About V4A, if you want to use a custom apk, you can easily replace the one provided with the one you like. If it contains other mods, than it might not work as easily. I don't recommend flashing any V4A package on top of the ROM, but if you link me to file I can take a look if there is a way to make it work.
Dark_Eyes_ said:
Well I use a lot more optimization than JustArchi's. But to answer the question, I have an equivalent form of the O3 optimization JustArchi has. About V4A, if you want to use a custom apk, you can easily replace the one provided with the one you like. If it contains other mods, than it might not work as easily. I don't recommend flashing any V4A package on top of the ROM, but if you link me to file I can take a look if there is a way to make it work.
Click to expand...
Click to collapse
I plan using this http://forum.xda-developers.com/android/software/viperaudio-viperatmos-3-8-sq-driver-t3289075 ViperAtmos 4.8 sony beats edition, still not sure if i use that specific one, there are million different versions
I tried following your instructions to put the apks in the sys/app folder but I do not have such folder. I think I am missing something? I tried putting them in the data folder however did not get installed during initial boot. If you could let me know that would be awesome!
New build is up!!!
I changed my mind and added back Trebuchet (CM launcher) and the keyboard, so you won't have to mess around when you first flash the ROM (or a new build for that matter).
I won't release new builds everyday, expect them once or twice a week.
acat550 said:
I tried following your instructions to put the apks in the sys/app folder but I do not have such folder. I think I am missing something? I tried putting them in the data folder however did not get installed during initial boot. If you could let me know that would be awesome!
Click to expand...
Click to collapse
Just for the sake of answering your question (that might be useful later), you have to mount the system partition before you can access it. Then you will see what is inside that partition. It is litterally impossible that you don't have a system/app folder, all prebuilt apps go there (and in system/priv-app).
I appreciate the quick answer! I think I will just go with the new build though lol! Been looking for a ROM that is stripped down and optimized to the fence! I have been running truesight as well so the duo is perfect!
Once a week is more than enough! I'll move to this rom when i have time. One thing you could do is aroma installer, thats a whole new thing to learn but if you feel like bored or want to try something new, it would be very useful. One thing i can think of now is adding and removing apps. You could use something like Cataclysm as reference
EDIT: Do you have the TrueSight UKM thing included? Thats one more thing to add if not.
One more question, lol. Does the adb work? The cm 13 build that i currently have crashes when i turn adb on. Not sure if TrueSight causes this or what. If you havent tried it, be aware that if it does crash for you too, you probably cant turn it off anymore. That happened to me, the phone was very slow when it was in lockscreen after boot and when i tried to unlock it, it just rebooted. So take backup if you think you want to try it
V4LT5U said:
Once a week is more than enough! I'll move to this rom when i have time. One thing you could do is aroma installer, thats a whole new thing to learn but if you feel like bored or want to try something new, it would be very useful. One thing i can think of now is adding and removing apps. You could use something like Cataclysm as reference
EDIT: Do you have the TrueSight UKM thing included? Thats one more thing to add if not.
One more question, lol. Does the adb work? The cm 13 build that i currently have crashes when i turn adb on. Not sure if TrueSight causes this or what. If you havent tried it, be aware that if it does crash for you too, you probably cant turn it off anymore. That happened to me, the phone was very slow when it was in lockscreen after boot and when i tried to unlock it, it just rebooted. So take backup if you think you want to try it
Click to expand...
Click to collapse
Nope UKM is not installed. At first I had Synapse prebuilt and UKM preinstalled (before releasing), but I had too many problems with it. It never applied my settings on reboot, plus half the time it crashed when restoring my profile. Too much trouble, and I don't use the extra settings that are not available in kernel adiutor. So, if you want it you will have to install both the app and UKM.
I just enabled adb without any problems. It also works when connected to the computer.
Dark_Eyes_ said:
Nope UKM is not installed. At first I had Synapse prebuilt and UKM preinstalled (before releasing), but I had too many problems with it. It never applied my settings on reboot, plus half the time it crashed when restoring my profile. Too much trouble, and I don't use the extra settings that are not available in kernel adiutor. So, if you want it you will have to install both the app and UKM.
I just enabled adb without any problems. It also works when connected to the computer.
Click to expand...
Click to collapse
Thanks for all the answers and hard work! :good:
It seems with the new build, that notification pulldown is broken. I have tried both open gapps and slim gapps, both to no avail. Any others with this problem?
HELP
Help Devs !! Why I can't dropdown the statusbar ?? Even I can't see quicksettings at all...this is bug ?
---------- Post added at 04:47 AM ---------- Previous post was at 04:47 AM ----------
acat550 said:
It seems with the new build, that notification pulldown is broken. I have tried both open gapps and slim gapps, both to no avail. Any others with this problem?
Click to expand...
Click to collapse
Same problem with me !!! Any solution ?? (
Junnie said:
Help Devs !! Why I can't dropdown the statusbar ?? Even I can't see quicksettings at all...this is bug ?
---------- Post added at 04:47 AM ---------- Previous post was at 04:47 AM ----------
Same problem with me !!! Any solution ?? (
Click to expand...
Click to collapse
That's most likely the cm and opengapps bug. Use an old gapps package for now.
Dark_Eyes_ said:
That's most likely the cm and opengapps bug. Use an old gapps package for now.
Click to expand...
Click to collapse
Gapps suggestion please???
Junnie said:
Gapps suggestion please???
Click to expand...
Click to collapse
Try banks gapps. Maybe slimgapps too, but someone bf reported it not working...