Related
G3MOD TEAM
Founder
dharamg3
Kernel Developers
hillbeast , moikop , cool.darshak
Application Developers
dympy , andreapier
ROM/Theme Developers
Stylooo , RafayelG , aarrun
Kernel Features:
Non-OC Version: 83MHz - 667MHz
OC Version: 83MHz - 1200MHz
RootADB
Busybox 1.19
File System Support: rfs/ext2/ext3/ext4
Init.d Scripts
1% Battery Mod
OverClocking
UnderVolt
data2sd
BFQ I/O Scheduler
Voodoo v10
CWM Touch Recovery
Configurable CompCache
BootLogo
TinyRCU
MultiBoot
Kernel Hz: (Non-OC: 250, OC: 500)
tun.ko
100MHz CPU clock stepping
DMA Enabled in G3D
Dynamic OC
Hybrid kernel (supports every firmware for Galaxy 3)
Hybrid Data2SD
Multi Data
NTFS read-only support (but no auto mounting SD card yet)
BLN Support. (Thanks to marcellusbe)
JFS and HFS+ support
CWM Features:
1) Reboot
2) Extended Power Menu
1.1) Power Off
1.2) Reboot
1.3) Reboot Recovery
1.4) Download
3) Update.zip's
3.1) Update.zip from sdcard Root
3.2) Select .zip from sdcard
3.3) Toggle Signature Verification
3.4) Toggle Script Asserts
4) Multiboot
4.1) Switch ROM's
4.2) Backup ROM
4.3) Switch Kernel's
5) Data / Factory Reset
6) Wipe
6.1) Data / Factory Reset
6.2) Cache
6.3) Wipe dalvik cache
6.4) Wipe Battery Stats
7) Backup and Restore
7.1) Backup
7.2) Restore
7.3) Advanced Backup 7.3.1) Boot 7.3.2) System 7.3.3) Data 7.3.4) Cache 7.3.5) sd-ext
7.4) Advanced Restore 7.4.1) Boot 7.4.2) System 7.4.3) Data 7.4.4) Cache 7.4.5) sd-ext
8) Mounts And Storage
9) Advanced
Kernel Downloads:
http://code.google.com/p/g3modteam/downloads/list
Kernel Changelog:
v2.5 (15/05/2012
Supports CM7a8.1
Supports ICS (if colours are screwy, update OpenFIMG)
CWM5 with touch
General source code fixes
v2.4.1 (23/02/2012)]
CM7 A7 support!
Fixed filesystem covertion system.
Lagfree governor properly implemented.
Added BLN support.
Fixed wifi for CM7 (Thanks to Arakmar).
v2.3 (15/12/2011)
Hybrid initramfs: Added support for ICS-based roms.
Multiboot: Fixed dalvik-cache restoring.
Multiboot: Added support for backing up android_secure.
AOSP Proximity sensor support added.
Initramfs: Optimized init.rc files and added usb.rc file.
MAX8998 Driver: Removed led blinking support since it isn't being used anymore.
v2.2.2 (21/11/2011)
Went back to old BLN system, this seems to work fine.
New NON-OC Kernel Hz: 250.
Should have a better battery backup
v2.2.1 (16/11/2011)
JFS Utilities permission fixed.
BLN System fixed.
v2.2 (15/11/2011)
Support for new BLN system.
Optimized SIO Scheduler for flash devices.
Added JFS Utilities (forgotten in the previous release).
Dropped OC+ version support.
v2.1 (09/11/2011)
Lagfree Governor.
83Mhz steps for Non-OC and OC+ version
Lowmemorykiller.c tweak.
Reverted ondemand performance tweak.
Updated BFQ I/O Scheduler to v2.1r1.
Data2SD tweak: Improved IO Performance for non-Data2SD users and fixed *incompatibility* with Kyrillos's App2SD script.
Added Hybrid Data2SD internal System cache.
Compcache is now configurable.
Fixed battery drain problem.
BLN Support. (Thanks to marcellusbe)
Removed InteractiveX governor due to problems.
JFS and HFS+ support.
v2.0 (02/10/2011)
Hybrid kernel (supports every firmware for Galaxy 3 (except Eclair))
CM6.2 and CM7 Support (obviously but it must be said twice)
Adjusted battery driver (more accurate)
83MHz minimum on OC kernel
Hybrid Data2SD
Multi Data
Compcache toggleable
InteractiveX CPU frequency mode
SIO scheduler
MD5 hash disabled on nandroid
More stable at idle
Reduced power drain at idle
jhash3 removed as it increased power drain.
v1.9 (09/09/2011)
tun.ko included and enabled
100MHz CPU clock steppings: you can now set your speed to anything between 100 and 1400MHz in 100MHz step (100, 200, 300...)
CPU minimum frequency now 100MHz on Performance, Ultimate and Extreme
jhash3 for improved HSDPA/3G/EDGE speeds.
Multiboot improved for data backup and recovery
Added Reboot and Wipe Data/Dalvik Cache to main menu of CWM.
DMA enabled in G3D - Thanks marcellusbe
Added InDroid and CM7 to Multiboot
v1.8 [30/08/2011]
Reworked Battery Driver
Reworked CWM Recovery
Now 11 ROM's support in Multiboot
v1.7 [15/08/2011]
Multi Boot
Power off Option in CWM
Dynamic OC (ability to change the maximum freq)
Modify the max_blk_count value to prevent overflow.(sdcard related)
mmc: core: Fix dereferencing after NULL check (sdcard related)
Lower vfs_cache_pressure 100->25.
ARM: fix some sparse errors in generic ARM code
lib: Improve the performance of memcpy and memmove of the general version
lib: Introduce some memory copy macros and functions
ashmem: fix deadlock when system is low on memory
v1.6 [11/08/2011]
Batter Driver Back to Original - Only Change is added Compensation for Data On
Stable OC
UV Works for All Frequencies - Can be checked via dmesg
Removed SavagedZen and SmartAss for now.Giving Problems. Will come back in future versions.
SDCard Partitioning Problem Solved - Ext3 partitioning for mmcblk0p2 - Can be converted to Ext4 Using g3mod app.
Kernel Flashing via CWM Recovery Working
Kernel Hz: Lite:256 Performance:300 Ultimate:500 Extreme: 1000
Noop I/O Scheduler by default
Fixed Typo in Bootlogo
v1.5 [05/08/2011]
CompCache
BootLogo
TinyRCU
Battery Driver Reworked - Please test and give feedback
v1.4 - 31/7/2011
CWM Recovery In Kernel
Fixed CPU Freq Driver. SetCPU now shows properly.
UV working properly now.Can Be Checked in dmesg.
A 1300MHz freq Step in Extreme Version for those who want 1300MHz overclocking.
Changed Kernel Hz to 300 for Better Battery Backup.
v1.3.4 - 27/7/2011
Overclocking Stable (Less freezes) - To Test
BFQ I/O Scheduler - http://algo.ing.unimo.it/people/paolo/disk_sched/
Extreme Version Screen Off Bug Solved
No OC bus for any versions - (For those who want OC Bus, please use v1.3.0 for the moment. I will try to make OC bus in some better manner)
v1.3.3 - 25/7/2011
5 Touch Mod
Removed RAM Optimization Script
Overclocking Stable (Less freezes) - To Test
Solved Bug which showed wrong freq in SetCPU and PimpMyCPU
Solved Time In State for SetCPU
Extreme Version has OC Bus 200MHz
Frequently Asked Questions
For NOOBS
Q) How to flash the kernel
A) Just apply update.zip from Recovery or flash tar file using ODIN.
Q) Will i lose my data if i flash kernel?
A) No, you wont lose any data nor do you have to wipe data or cache.
Q) Does my battery need to be 100% to flash?
A) Not at all
Q)Flashed CM 6.2 Kernel on Froyo Rom and WIFI doesnt work?
A) There are two versions of Kernel. One is for Froyo Rom and other is for CyanogenMod Rom 6.2 (CM 6.2). if you are on Froyo rom and flash CM 6.2 then your wifi wont work and vice versa.
Q) 1400 Mhz (Extreme version) doesnt work for me
A) Not all Galaxy 3 suppport overclocking as high as 1400 Mhz. If it doesnt work then keep frequency lower or flash Ultimate, Performance or Lite version
Q) What does this data2sd in g3mod do?
A) data2sd is method by which all your /data partition goes to your sdcard thus giving you more space for downloading apps. Its suggested to use data2sd only if your sdcard class is higher than Class 6
Q) Internel Memory shows 0kb
A) Check if you have fs.data2sd at this location /sdcard/Android/data/g3mod/ If yes then delete it or else your sd card doesnt have sd-ext partition
Q) How can i go to recovery mode
A) Press MENU+VOLUME UP+VOLUME DOWN+POWER button and bingo!!!
Q) Should i use multi boot even if i am having 2 gb card class 2 ?
A) Sd card with any class can use multiboot
Q) Data Wipe Necessary When Switching Between CM and Froyo ?
A) Yes data wipe is necessary for switching roms between CM and Froyo. But we have given option to Backup data also in recovery.
Q) My APP is not working after Flashing KERNEL
A) Its not a kernel problem
Q) What is tun.ko?
A) It is basically used to setup Open VPN connections
Q) What is jhash3?
A) jhash3 improves the HSDPA/3G/EDGE speed
For Advanced users
Q1) Battery is draining fast?
A) After flashing the kernel please calibrate your battery or else let 3-4 full battery cycles pass.
Q2) Which profiles should i use?
A) Lets take example that you are using Ultimate kernel. Keep the governor ondemand (Like every good boyfriend fulfills all demands of his girlfriend ondemand governor does the same for your CPU ).
Make profiles:-
1) Time Profile - 12 am to 6.00 am Freq 100 Mhz to 400 Mhz Priority 100
2) Screen Off - Freq 100 Mhz to 600 Mhz Priority 95
Q3) What are advanced settings in the SetCPU mean?
A) Sampling rate is rate at which the frequency of your CPU changes. Up Threshold is limit at which CPU will change freq on load (Scales Up). Down Threshold (conservative only) is limit at which CPU will change freq on load (Scales Down). Powersave bias is used for saving the power of CPU, it will slow down the CPU and affect the performance also 200 in powersave bias mean 20%...250 means 25% and so on.
Q4) I want performance and also good battery what profiles should be i use?
A) Refer to Q2 for Profiles Set up and now go in Advanced tab and Keep Sampling Rate 10000 or 15000. Upper Threshold to 90 and Powersave bias to 200 (20%). Since we are using powersave bias, this will affect the performance as it slows down the CPU so to increase the performance we are lowering the Sampling rate thus we get perfect balance of Performance and good battery backup.
NOTE: ABOVE SETTINGS ARE JUST EXAMPLE..PLEASE PLAY AROUND AND CHOOSE SETTINGS WHICH SUITS YOU THE BEST
WATCH THIS NOOBS
Donations:
If you want to donate to the team as a whole, please divide the amount and donate separately to each member. Sorry for the trouble caused.
Thank You for considering to donate.
dharamg3 -
hillbeast -
moikop -
cool.darshak -
Steps for Multi boot:
1) Flash Kernel v1.7+
2) Go to CWM Recovery -> Multiboot -> Backup ROM.
3) Backup your Current ROM to ROM1 (It will backup the system.img at /sdcard/Android/data/g3mod/roms/romname_ROM )
4) Add the system.img of your 2nd ROM to /sdcard/Android/data/g3mod/roms/romname_ROM and similarly for different ROM's.
5) Use the CWM Recovery -> Multiboot -> Switch ROM option to switch between different ROM's.
6) If switching between Froyo ROM and CM6.2 RoM, you will need to wipe data and also change kernel's via update.zip method.
7) Use the data backup and restore option to prevent loss of data when switching between Froyo and CM6.2 ROM's.
Note: Ask the developer of the ROM's to provide you with the system.img for their ROM
How to use Hybrid Data2SD
1) Connect your phone via ADB
2) Go into adb shell
3) Type 'echo hybrid > /sdcard/Android/data/g3mod/fs.data2sd'
4) Create a text document in Notepad with a list of all the directories you wish to move. Example:
Code:
app
log
dalvik-cache
---LEAVE A BLANK LINE AT THE END---
5) Save the file and call it 'data2sd.dirs'
6) Do 'adb push data2sd.dirs /sdcard/Android/data/g3mod/'
7) Reboot your phone
8) Once your phone has booted, run 'adb shell cat /data2sd.log' to ensure it is running correctly.
How to enable Multi Data
1) Connect your phone via ADB
2) Go into adb shell
3) Type 'echo 0 > /sdcard/Android/data/g3mod/multiosdata'
4) Multi Data will automatically backup your data upon booting into a different OS.
Make sure to not wipe your SD-EXT partition. Doing so will erase the backups from other firmware. Only wipe it if you wish to erase data for everything.
You can also use Multi Data to quickly restore data if your phone has become corrupted. It will restore it back to the last multi-boot switching
1) Connect your phone via ADB
2) Go into adb shell
3) Type 'echo 0 > /sdext/lastos'
4) Reboot the phone
Directories for Multi boot:
//ROM Dir
__system("mkdir /sdcard/Android/data/g3mod/roms/CyanogenMod6_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/CyanogenMod7_ROM"); //Add CM7 Support
__system("mkdir /sdcard/Android/data/g3mod/roms/G3MOD_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/Kyrillos_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/Grigora_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/AOSP_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/DutchMods_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/Kyorarom_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/Indroid_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/rom1_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/rom2_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/rom3_ROM");
__system("mkdir /sdcard/Android/data/g3mod/roms/rom4_ROM");
//Data + sd-ext Backup Dir
__system("mkdir /sdcard/Android/data/g3mod/data/Froyo_DATA");
__system("mkdir /sdcard/Android/data/g3mod/data/CM6_DATA");
__system("mkdir /sdcard/Android/data/g3mod/data/CM7_DATA");
//Kernel dir
__system("mkdir /sdcard/Android/data/g3mod/kernel/Froyo");
__system("mkdir /sdcard/Android/data/g3mod/kernel/CM6");
__system("mkdir /sdcard/Android/data/g3mod/kernel/CM7");
How to configure compcache:
If you want to use default configuration (as up to now.. 62 MB aprox.), you don't have to do anything different as what you have been doing. But if you want to use a more/less memory, here are the steps:
Inside that /sdcard/Android/data/g3mod/compcache file, write ONLY the number of MegaBytes you want to use for compcache.
Reboot.
If compcache file is empty or contains a "0" inside, it will use default configuration.
How to: BLN
This is only "needed" if you have a i5801 | i5800L or any other Galaxy 3 model with back button lights and want BLN in it.
How to install:
First, download the lights.GT-I5800.so file from google code. Then execute this commands:
adb remount (or if this doesn't work: mount -o remount,rw /dev/stl6 /system)
adb rm /system/lib/hw/lights*
adb push [Location of this file] /system/lib/hw
After that, reboot and now you have BLN working
Steps for Changing the Max Freq(Dynamic OC):
There is an entry in /sys/devices/system/cpu/cpu0/cpufreq/plls_table where you can put your own value for APLL.
Before doing this, set "PERFORMANCE" governor on and min and max frequencies to the maximum.
Code:
// Do this in adb
echo "0 a[SIZE="5"][B][U]258[/U][/B][/SIZE]0[SIZE="5"][B][U]3[/U][/B][/SIZE]01 a14d0303 c07e13fc cf850240" > /sys/devices/system/cpu/cpu0/cpufreq/plls_table
You need to replace the 258(Hex Value) with your desired value.
Here 258 means
(2*16*16) + (5*16) + 8 = 600
and 3 means it is 600*2 = 1200
Therefore, a2580301 means 1200MHz.
This is a temporary method. For a permanent Method, add this line to a init.d script. Name the script to something like S10_Dyanmic_OC.
Help Others: If you calculate a Hex Value for a particular frequencies add it here:
https://docs.google.com/spreadsheet/viewform?formkey=dG5hdnpsWFdTNExiY2t3dy16VzBvaWc6MQ
You can view all the frequency Hex value's calculated by others over here:
https://docs.google.com/spreadsheet...G5hdnpsWFdTNExiY2t3dy16VzBvaWc&hl=en_US#gid=0
Kernel Related Media:
5 Touch Support:
BootLogo and Progess Bar
Multi Boot
g3mod_v1.3.4_LITE.tar (5.9 MB)
http://www.multiupload.com/3BIF9S2IES
g3mod_v1.3.4_LITE.zip (6.1 MB)
http://www.multiupload.com/9IJTKFIJDX
g3mod_v1.3.3_LITE.tar (5.9 MB)
http://www.multiupload.com/DDMMU0U9YB
g3mod_v1.3.3_LITE.zip (6 MB)
http://www.multiupload.com/DW1QZPDQOY
g3mod_v1.3.4_PERFORMANCE.tar (5.9 MB)
http://www.multiupload.com/H53ZTO5ULW
g3mod_v1.3.4_PERFORMANCE.zip (6.1 MB)
http://www.multiupload.com/WWFL3EXH0Y
g3mod_v1.3.3_PERFORMANCE.tar (5.9 MB)
http://www.multiupload.com/Y9CDMFVH61
g3mod_v1.3.3_PERFORMANCE.zip (6 MB)
http://www.multiupload.com/0MQQRR1KV8
g3mod_v1.3.4_ULITMATE.zip (6.1 MB)
http://www.multiupload.com/I4JCH7E5JE
g3mod_v1.3.4_ULTIMATE.tar (5.9 MB)
http://www.multiupload.com/TEQXRZMKPQ
g3mod_v1.3.3_ULITMATE.zip (6 MB)
http://www.multiupload.com/97DV0V4OQC
g3mod_v1.3.3_ULTIMATE.tar (5.9 MB)
http://www.multiupload.com/KV9SSVWWZ7
g3mod_v1.3.4_EXTREME.tar (5.9 MB)
http://www.multiupload.com/EGZKK89JTZ
g3mod_v1.3.2_LITE Odin
g3mod_v1.3.2_LITE CWM
g3mod_v1.3.1_LITE Odin
g3mod_v1.3.1_LITE CWM
g3mod_v1.3.0_LITE Odin
g3mod_v1.3.0_LITE CWM
g3mod_v1.3.2_PERFORMANCE Odin
g3mod_v1.3.2_PERFORMANCE CWM
g3mod_v1.3.1_PERFORMANCE Odin
g3mod_v1.3.1_PERFORMANCE CWM
g3mod_v1.3.0_PERFORMANCE Odin
g3mod_v1.3.0_PERFORMANCE CWM
g3mod_v1.3.2_ULTIMATE Odin
g3mod_v1.3.2_ULTIMATE.zip CWM
g3mod_v1.3.1_ULTIMATE Odin
g3mod_v1.3.1_ULTIMATE CWM
g3mod_v1.3.0_ULTIMATE Odin
g3mod_v1.3.0_ULTIMATE.zip CWM
g3mod_v1.3.2_EXTREME Odin
g3mod_v1.3.2_EXTREME CWM
g3mod_v1.3.1_EXTREME Odin
g3mod_v1.3.1_EXTREME CWM
g3mod_v1.3.0_EXTREME Odin
g3mod_v1.3.0_EXTREME CWM
Source For Developers:
https://github.com/dharamg3
Note:
We am learning how to develop kernels.
We willl add different features as and when we can implement them.
The main goal of this kernel will be to keep the phone stable and fast.
There will be nothing as alpha or beta releases.
We will give out the kernels directly, but if anything goes wrong and you have to reflash the ROM or kernel, please dont start shouting.
You may give us different ideas on what features to implement. We will try our best to implement all the features you want
Many of the features implemented in this kernel, are taken from marcellusbe's Fugumod Kernel, and we shall be ever thankful to marcellusbe for the fugumod kernel
Warning:
We are not responsible for any damage caused to your phone (softbrick or hardbrick)
Credits:
marcellusbe for all his help, awesome fugumod kernel
supercurio for voodoo v10
Paolo for BFQ I/O Scheduler
All developers for making this an awesome phone
Everyone who is helping is solving different issues with this kernel
Please let us know if we miss anyone ...oh we did already miss someone..thanks G3MOD TEAM too
What to the old thread?
Nm read that
Btw 6th post got some errors...
@Dharam, i have a question. In your v1.8 Kernel, We can change the partitions to any type we want, can't we? Because in Mumbozver's recovery, we could only use ext2/ext4/ext2.
kyrillos13 said:
@Dharam, i have a question. In your v1.8 Kernel, We can change the partitions to any type we want, can't we? Because in Mumbozver's recovery, we could only use ext2/ext4/ext2.
Click to expand...
Click to collapse
The kernel itself supports everything, but CWM only supports EXT2. I will look into either porting CWM4 or getting 2.5 to support more systems.
hillbeast said:
The kernel itself supports everything, but CWM only supports EXT2. I will look into either porting CWM4 or getting 2.5 to support more systems.
Click to expand...
Click to collapse
getting 2.5 to support other partitions will be a better idea...coz for CWM 4 you need complete CM7 source, and also most of the update.zip's on the g3 forums use amend...and CWM 4 supports only edify....
All the best to the future process
Sent from my GT-I5800 using XDA App
Right, I want to work on USB OTG but lack the cable, and the only way I can do it with what I have is if I destroy my only USB cable for my phone. So if someone wants me to do USB OTG, then buy me a cable and I'll do it
All the stuff is there to do it, I just need to get the phone to switch into host mode.
I think v1.9 is going to come sooner than expected...excellent work by the whole team...
Will this root my phone if I install this in Stock ROM?
[email protected] said:
Will this root my phone if I install this in Stock ROM?
Click to expand...
Click to collapse
it will give you ADB Root, but not the superoneclick root...
dharamg3 said:
it will give you ADB Root, but not the superoneclick root...
Click to expand...
Click to collapse
Ok thanks.....
I am a newbie at this...
But, which root did I get when I installed Kyrillos' ROM?
BCK - Bam Custom Kernel for i9003 / Galaxy SL
This Kernel is based on the Chinese GB source, released by Samsung on the 18th of November. Last changes to the source were made by Samsung on November 15th. If you still have questions after reading this post, look at the FAQs (including a list of requested features and known issues).
Kernel features:
No SOD
Bugfixes:
~ Sync bug fixed. Notifications for new mails and messages should arrive within one minute under all circumstances
~ Bluetooth problems fixed. Your phone now should play nice with bluetooth hosts, i.e. your car audio system
~ Micro stutters nearly completely gone thanks to lowered processor transition latency. It's smooooooooth
~ Home button double presses exterminated
Governors:
~ smartassV2 governor by erasmux (default)
~ interactive governor by Mike Chan
IO scheduler:
~ SIO IO scheduler by Miguel Boton (default)
~ BFQ IO scheduler by Paolo Valente and Fabio Checconi
~ deadline IO scheduler
Extended features:
~ ro.secure=0 (root acces through adb shell - to root the 'clean flavour' of BCK, please follow the instructions)
~ EXT4 support (to convert your file system, use amit.bagaria's ext4 add-on .apk) (Only in CF-Root .tar)
~ Support for init.d scripts (to use scripts, please follow the instructions) (Only in CF-Root .tar)
~ BLN support (to use BLN, please follow the instructions)
~ TUN support for VPN networks built-in (no module needed)
~ Increased SD-card read ahead of 768 kb for improved read speed
~ Available with universal CF-root ramdisk based on amit.bagaria's version, improved by loSconosciuto (Only in CF-Root .tar)
~ Available with universal CWM ramdisk (rooted) based on universal CF-root, but 'tweakless' (Only in CWM .tar)
Overclocking and Voltage:
~ Evolved sysfs interface for variable overclock or underclock (all operating points [OPPs] can be adjusted seperately)
~ Fifth OPP (1.2 GHz) available, device booting up at stock speed (1 GHz)
~ Total frequency control. The device will never run at higher speeds than defined by you, not even on WiFi.
~ sysfs interface for voltages (read only at the moment)
~ Slight undervolt (3%) on all OPPs
Flashing , settings and compatibility:
If you want to use BCK, please flash it on a clean stock ROM. If you want to go back to stock, repartition and reflash the full firmware with ODIN. This kernel will not work on CM or MIUI.
The CF-root and CWM versions (PDA_BCK_CF-root_universal_***.tar / PDA_BCK_CWM_universal_***.tar) can be flashed on any recent Gingerbread firmware. These versions are pre-rooted, which means they include Superuser.
The non-CF-root "clean" version (PDA_BCK_XXKPQ_***.tar / PDA_BCK_XXLE4_***.tar) will only work on XXKPQ / XXLE4. Do not flash this version on anything other ROM than the one indicated in the file name. This will break your WiFi. It's especially risky to flash the clean version of BCK after flashing any CF-root kernel before. Don't do it. This version does not include Superuser, but it is prepared to be rooted. Follow the instructions to do this.
After a kernel update, please wait for the device to boot up and reboot once. There is generally no need for cache cleaning or a full reset. To change the governor and IO scheduler, I use NoFrills CPU Control from the market. It's free and reliable.
I recommend to use the clean XXKPQ version. If you want / need to have root, try the CWM version. If you want the 'full package' with FuGu-Mod and more, use the CF-root. I recommend that you do not apply any further tweaks and use a stock ROM.
>>> Warning: Overclocking may damage your device. <<<
Overclocking instructions:
For overclocking, you will need a shell on your phone, or adb access. I use Android Terminal Emulator. Overclocking is currently limited to certain frequencies (see below) and all operationg points will be set with the stock voltage of the corresponding stock frequency. The frequencies you set have to be within the following ranges:
Code:
OPP1: 100 - 500 MHz, stock 300 MHz
OPP2: 501 - 700 MHz, stock 600 MHz
OPP3: 701 - 900 MHz, stock 800 MHz
OPP4: 901 - 1100 MHz, stock 1000 MHz
OPP5: 1101 - 1500 MHz, stock 1200 MHz, not used by default
Remember that your phone uses all operating points depending on the current load. Anything more than 10% higher than the highest stock frequency is likely to be unstable, but you are free to try it. To change the clocks, open Terminal Emulator (or type 'adb shell') and hack in
Code:
su
echo "1100" > /sys/power/overclock_opp4
as an example. The others are opp5, opp3, opp2 and opp1. That's it.
Settings will be lost at reboot, unless you add them to your init.d scripts. I do not recommend this, as this may cause boot loops if the settings are to high! Be advised that NoFrills CPU Control, SetCPU, or whatever app you use that may adjust clock settings interfers with this. You may wanna update their settings after this. I do not recommend using them to set anything at boot if you overclock any OPP, because they might save the wrong frequencies and crash or do worse.
Changelog:
beta 1:
Added cpufreq governors
beta 2:
Changed smartassV2 settings to fit i9003
Added EXT4 support
Smaller zImage due to .config changes
beta 3 (not released):
Experimented with overclocking (not working, yet)
beta 4:
Finetuned smartassV2 settings
Made smartassV2 governor default
Reverted: Smaller zImage due to .config changes
Switched to linaro 4.6.2 toolchain (also used for ICS)
Activated new, aggressive compiler optimizations (-O3)
Added deadline IO scheduler
Added BFQ IO scheduler (10% higher performance than CFQ in Antutu Database IO Benchmark. This does not mean, that the maximum read or write speed increase! It just means that the throughput under heavy load is higher.)
Made BFQ IO scheduler default
Updated all modules
beta 5:
Variable overclock. Loosely based on the modifications of the Nook Color sources by dalingrin and of course with help from amit.bagaria and DooMLoRD.
beta 6:
Variable overclock for all operating points
beta 7:
Switched to universal CF-Root by amit.bagaria (BCK now should run on every recent GB ROM)
Added correct version information in settings menu, credits to DooMLoRD
Fixed cpufreq stats to correctly reflect frequency changes
Increased SD-card read ahead to 768 KBytes. This results in higher SD-card read speeds.
Major simplifications in overclocking code. Works more robust, now.
Added sysfs interface to show voltages. See /sys/power/overclock_vdd_oppX
Changed all voltages to the mainline Linux kernel defaults. This results in a slight 3% undervolt for each OPP, which saves about 5% power and should have no impact on stability whatsoever. Below you will find an overview of the exact voltages.
Code:
stock BCK
OPP1: 1.0250 V 1.0000 V
OPP2: 1.2000 V 1.1625 V
OPP3: 1.3300 V 1.3000 V
OPP4: 1.3875 V 1.3500 V
OPP5: not def. 1.3800 V
beta 8:
OPP5 (1.2 GHz) now enabled in _1200 version of kernel. Thanks to knzo for pointing me to the right patch.
Fixed video recording bug when running at 1.2 GHz
Fixed power management issues at 1.2 GHz
Small changes to smartassV2 and interactiveX settings
beta 9:
Added simple IO ('SIO') scheduler
Only one kernel version now, which includes OPP5 (1.2 GHz) but boots up at 1 GHz. Be advised that your device may nevertheless be running at 1.2 GHz for five to ten seconds at boot because of software limitations.
Changes in PM to always respect cpufreq policy limits. From now on, the device will never run at higher speeds than defined by you, not even on WiFi. Based on an omapzoom.org patch.
Changes to OPP switching code. May lead to less 'hickups'. Based on an omapzoom.org patch.
Bugfix for framebuffer code. Based on an omapzoom.org patch.
Reduced IVA / DSP frequency when on OPP5 to be on the safe side.
beta 9fix:
Reverted: Changes to OPP switching code. May lead to less 'hickups'. (Patch caused random freezes using WiFi.)
Reverted: Bugfix for framebuffer code. (Patch showed no noticeable benefits.)
beta 10:
Fix for sync bug applied. If you still have problems, please report.
This version is identical to beta 10rc14. No need to flash again, if you already are on that version.
beta 11:
Updated universal CF-Root by amit.bagaria to version 9 (released 1st of February 2012), but NO touch recovery
Slight increase in OPP5 voltage (1.38 V -> 1.40 V), may prevent some reported reboots on 1.2GHz
Code:
stock BCK
OPP5: not def. 1.4000 V
Changes in overclocking code to play nice with your frequency settings. If you overclock OPP5 but have restricted freqs to 300 - 1000 MHz, it won't automatically activate OPP5 anymore. The same is true for the lowest OPP.
If you overclock OPP4 above 1000 MHz and have restricted freqs to 300 - 1000 MHz, it will update the upper boundary to the new frequency of OPP4 so it doesn't get deactivated.
beta 12:
Fixed bluetooth problem with car audio systems (Based on omapzoom patches [1], [2] and [3]). Might resolve other bluetooth issues, too.
Universal CF-Root: Fixed bootanimation. Thanks to loSconosciuto.
Universal CF-Root: Fixed install procedure. It will check the actual kernel version, now. Thanks to loSconosciuto.
Universal CF-Root: Fixed fix_permissions script to work on our device. Thanks to loSconosciuto.
Switched to user_defconfig, to avoid unnecessary debug lines in dmesg.
beta 13:
Updated sources to GT-I9003_SWA_GB_Opensource_Update1 from the 30th of March. This also enables TUN support by default. You do not need any modules for this - it works "out of the box" with any VPN client.
Universal CF-Root: Backup is not failing anymore when started from CWM. Thanks to loSconosciuto.
Universal CF-Root: Some small improvements to multiple scripts.
Home button double press issue fixed. There should be no more unwanted double selections in CWM and you can now reliably long press the home button to bring up the list of previously used apps. Idea and timer function taken from a patch by Tegrak.
Fixed priority class for CONTENT_PROVIDER not being set, which may have caused apps of this class to be ignored by the autokiller, resulting in less free RAM.
Lowered OMAP processor transition latency to the value recommended by TI. Subjectively, this brought huge improvements in terms of reducing micro stutters.
Lowered CFS scheduler latency and granularity to values very close to mainline kernel defaults. This could reduce lags in some critical situations, but it doesn't do wonders.
Switched to SIO as default IO scheduler.
beta 14:
Universal CF-Root: Replaced CWMManager and TweakManager with zipaligned files. Thanks to loSconosciuto.
Universal CF-Root: The TweakManager is not replaced on install if it didn't change to preserve it's settings. Thanks to loSconosciuto.
Universal CF-Root: Corrected problems because of too little free space in /system when converting to ext4 by permanently moving InfoAlarm.apk from /system/app to /data/app. Thanks to loSconosciuto.
Universal CF-Root: Fixed the non-working WiFi on XXLE4 and prevented future problems. Instead of patching the WiFi modules, they are now replaced. Thanks to loSconosciuto.
Universal CF-Root: Fixed some small mistakes in the CF-root install procedure.
Switched the compression of ramdisk and kernel from gzip to lzma. This makes the files much smaller and allows us to include more 'stuff'.
Changed smartassV2 settings to wake up at lower frequencies. Further, it is not locked at 300 MHz anymore when the screen is off. Tests showed that free scaling is more battery friendly.
Removed InteractiveX and OndemandX governors and added the Interactive governor by Mike Chan (Source: CyanogenMod Crespo kernel). Since free scaling proved to be more battery friendly, the screen off profiles in InteractiveX and OndemandX made them superfluous.
The device will not scale above 1 GHz for some seconds when booting anymore. It's now safe to use BCK even if your device can't handle 1.2 GHz. Based on a patch by dalingrin.
Changes in PM to respect cpufreq policy limits when playing or recording video. The device should respect your wishes under all circumstances, now
Fixed the SmartReflex voltage calibration of the OMAP SoC for OPP5. This could lower power consumption as soon as OPP5 (1.2 GHz) is activated for the first time.
Slight increase in the OPP5 nominal voltage (1.40 V -> 1.42 V) to allow for some adjustment by SmartReflex (now that it's working...), if necessary. The actual voltage when the device is running will not change for most users! Based on patches by dalingrin and Sanjeev Premi.
Code:
stock BCK
OPP5: not def. 1.4200 V
beta 14 fix:
Universal CF-Root: Fixed the non-ending row of force closes after flashing the Universal flavour of BCK. The clean XXKPQ version did not show these problems and didn't need a 'fix'.
beta 15:
Universal CF-Root: Modified some permissions to bring it closer to the stock ramdisk
Universal CWM: Created a CWM ramdisk based on CF-root, without most tweaks. You now have three BCK flavours to choose from
Updated to newest UPDATE2 sources by Samsung
Sync bug fix reworked to use new Samsung method from UPDATE2. This may lead to slightly lower standby battery consumption.
Fixed accidental front camera mirroring
Editing smartassV2 settings with busybox 1.20.x and newer no longer leads to reboots. Thanks to loSconosciuto for pointing me to the patch.
Fixed complete crash of WiFi driver when activating WiFi by adapting smartassv2 thresholds
Reverted to the original Google Android toolchain using gcc 4.4.3
Because of the toolchain-switch, the compiler optimizations are now back to -O2 instead of -O3
Credits:
Credits go to the mentioned developers of the cpufreq governors, ganeshbiyer, skin1980 and amit.bagaria for the CF-Root and skin1980 for his repack script. Many thanks to DooMLoRD, amit.bagaria, knzo and loSconosciuto for their help! BCK sources are available on GitHub.
Files:
Attached files:
ODIN-flashable PDA_BCK_XXKPQ_***.tar with stock Samsung ramdisk ('Clean flavour'). Only for XXKPQ ROMs.
ODIN-flashable PDA_BCK_XXLE4_***.tar with stock Samsung ramdisk ('Clean flavour'). Only for XXLE4 ROMs.
ODIN-flashable PDA_BCK_CF-root_universal_***.tar with CF-root ramdisk ('Universal CF-root flavour'). For all current Gingerbread ROMs.
ODIN-flashable PDA_BCK_CWM_universal_***.tar with CWM (rooted) ramdisk ('Universal CWM flavour'). For all current Gingerbread ROMs.
Other files (not attached):
Old releases and release candidates can be found on Dev-Host. Use these with caution!
MD5 sum:
Code:
PDA_BCK_XXKPQ_beta10.tar: 83013b2d54c52dddb72deec46b5471de
PDA_BCK_CF-root_universal_beta10.tar: e1e8bcc28c878095618413141b642ec1
PDA_BCK_XXKPQ_beta11.tar: 9eaa6d080f3409c4822e38602bad8efb
PDA_BCK_CF-root_universal_beta11.tar: 93437cf26699dfe595881941b13a6a83
PDA_BCK_XXKPQ_beta12.tar: d9849ae7d9587402aa6465081b4c65a1
PDA_BCK_CF-root_universal_beta12.tar: 2107dfbf33b2838e66007f4319bee14e
PDA_BCK_XXKPQ_beta13.tar: bff3112d3249e951a569148d79643744
PDA_BCK_CF-root_universal_beta13.tar: 1fab51d641a8914e11a81781683d7d7d
PDA_BCK_XXKPQ_beta14.tar: 08cd77964c3d8b54b4c97e59500a0b96
PDA_BCK_CF-root_universal_beta14fix.tar: 6a2cda17362f5a2e6aac7e78dbe94089
PDA_BCK_XXLE4_beta15.tar: 7159e6cd5f2b71bebffcb4d86201b6cf
PDA_BCK_CF-root_universal_beta15.tar: ecfa46b8aec239f1ac246df61dc63477
PDA_BCK_CWM_universal_beta15.tar: 765a5253b0313d41399ea86822cf5f80
Nice i'll try it out ! but m not on clean kpq :\ oh well its worth the shot for thse governors and can u please provide the link to the new source ?
phone boots but the boot animation keeps on repeating ! cf root problem !clean kpq did the trick m in !
Oh!very nice
shriomman said:
Nice i'll try it out ! but m not on clean kpq :\ oh well its worth the shot for thse governors and can u please provide the link to the new source ?
phone boots but the boot animation keeps on repeating ! cf root problem !clean kpq did the trick m in ! but how to root it now ? :\
edit- rooted with soc with psnuter had to instal busybox from stricson and all working just fine
Click to expand...
Click to collapse
Thanks bro for your feedback.
Sent from my GT-I9003 using Tapatalk
over clock to ? ghz?
leongwenjun said:
over clock to ? ghz?
Click to expand...
Click to collapse
it doesnt have oc ! it has special cpu governors which are efficient and fast
tough luck for me mate....
i compile a vanilla kernel which is ~200 kb larger than stock zImage and it doesnt even boot!
also,even i want to update to 2.6.35.14,,,,,,,,,,,,,,how u did it without source?
also(2)lz open an acc. on github!
@sakindia123: Take a look here, update your sources to the new version, and get the new toolchain they use (see readme in the sources).
i followed that link before......
ok i will try with new source
what will happen if we use this ? are there any good feautures ?
it has special cpu governors which are efficient and fast
Now just wait for some days guys. Doomlord, bam, sakindia will show u real power of our device.
This is great! Just one little question, you said this is for a chinese firmware, but you mention KPQ, so it can be put in XXKPQ or not? Anyway sorry for my noob question
vishal24387 said:
Now just wait for some days guys. Doomlord, bam, sakindia will show u real power of our device.
Click to expand...
Click to collapse
U forgot To mention "fuss" dude...
Sent from my GT-I9003 using XDA Premium App
Slynightdark said:
This is great! Just one little question, you said this is for a chinese firmware, but you mention KPQ, so it can be put in XXKPQ or not? Anyway sorry for my noob question
Click to expand...
Click to collapse
It is based on the Chinese source - this includes kernel and android system source. But the kernel is universal (not language specific), and I applied all necessary settings for XXKPQ. Therefore you can flash it on KPQ.
what does a kernel do??
it is the main driving force of a phone that i know.
does it make our phone fast??
how to flash it as i would like to give it a try right away!!
can i roll back to stock kernel after this??
sorry for thr noob question as im new to all this.
---------- Post added at 08:45 PM ---------- Previous post was at 08:40 PM ----------
also do we need to have CWM recovery for this????
or we can do it with the stock recovery menu??
i was just doing some testing and the kernel is stuck at "SAMSUNG" bootanimation after a FRESH FLASH...
any idea?
used on XXKPQ FW
I flash your kernel. From last 5hours no SOD ISSUE. I'm using smartass v2 let's see how will battery I will get from it.
Sent from my GT-I9003 using Tapatalk
Fresh flash of what PDA? Yours, mine, GitHub?
@manrock111: smartassv2 gives me slightly higher battery usage than stock. I want to tweak it, but have problems with my sources at the moment.
XDA_Bam said:
Fresh flash of what PDA? Yours, mine, GitHub?
@manrock111: smartassv2 gives me slightly higher battery usage than stock. I want to tweak it, but have problems with my sources at the moment.
Click to expand...
Click to collapse
sorry... did a fresh install of full XXKPQ FW and now its booting
ok now this is weird... suddenly all of my test kernels have started booting
Fusion Ultimate Kernel for all Sense-based 4.0.3 ROMs
Latest Version: v3.4 (9/1/12)
Disclaimer:
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. :P
* blah blah blah you get the point.
*/
As many of you probably already know, I had another 'Fusion' kernel for the S4 HTC One S. However, because I incorporated mdeejay's patches, the kernel did not play nice with the CPU and whatnot. I nuked my repo, imported the T-Mobile US kernel sources, and re-built the kernel from scratch. I wanted to start a new thread so people would not mix up this and the old kernel.
Click to expand...
Click to collapse
Post #1: Release, Features, and Downloads
Post #2: Changelog
Post #3: How to compile from source
Post #4: Frequently Asked Questions
Features
[*]CPU frequency control from 192Mhz 1.89Ghz
[*]your choice of stock or overclock options
[*]universal package
[*]zip package with modified init.qcom.post_boot.sh and thermald.conf
[*]voltage control (use System Tuner Lite/Pro)
[*]SmartassV2, Interactive, Conservative, LagFree, Lionheart, BrazilianWax, Intellidemand, InteractiveX, SavagedZen, and Smartass CPU governors added
[*]Simple IO (SIO) and V(R) scheduler added
[*]capacitive LED lights dimmed to 2mA
[*]improved media scanning times (increased readahead buffer)
[*]good multitasking
[*]enabled zRam (see FAQ for a detailed explanation of what it does)
[*]greatly improved I/O performance (disabled fsync() )
[*]XZ kernel compression
[*]overall good battery life and performance
[*]optimized and tweaked
[*]much more; check the changlog or my GitHub if you want to know the specifics
Click to expand...
Click to collapse
Downloads
Do NOT flash versions 3.0 and higher in recovery!! They are 7zips!!
I purposely made it a 7zip archive so people don't flash it. Instead, extract the appropriate zip from the package and then flash like before. You get options of whether you want overclock or stock clock. The zip will flash the correct files and modules according to your choice and then clean out conflicting init.d scripts for the best possible compatibility.
All Downloads are HERE
How to Install
For hboot 1.09 and below:
Just flash the zip in TWRP recovery. It will automatically flash the boot.img for you.
For hboot 1.13 and up:
you have two options
Option #1
Use TWRP's HTC Dumlock feature. It is a pretty neat workaround that allows you to flash boot.imgs in recovery even on a higher hboot.
Look here for instructions from TeamWin. If you are not comfortable with this method, then follow option #2 to manually flash in fastboot.
Option #2
In addition to flashing the zip, you will have to extract the boot.img from the package and flash it manually with fastboot. Blame HTC for the half-assed 'unlock bootloader' offering they give us. Hopefully we will get S-OFF soon...
Code:
adb reboot bootloader
fastboot flash boot boot.img
fastboot erase cache
fastboot reboot
Look here for a guide.
Sources
initramfs: https://github.com/klin1344/initramfs_ville
kernel: https://github.com/klin1344/kernel_ville_US
Enjoy
Changelog/Complete Feature List
Changelog
v1.0 (Initial Release 7/24/12)
re-wrote overclock code
completely re-based on the TMOUS source
init.d scripts support with Busybox run-parts
overclocked up to 1.89Ghz
added 192Mhz step
added SmartassV2 CPU governor (still finicky; needs more testing)
enabled Conservative and Interactive CPU governors
added SIO scheduler and enabled as default
increased readahead buffer
various tweaks for UI responsiveness
stable
v1.1 (7/27/12)
cleaned up CPU code (all frequency issues should be gone by now; check github for full details)
added LionHeart CPU governor
added LagFree CPU governor
reduced capacitive LED brightness to 2mA (looks better)
tuned Interactive CPU governor parameters
many optimizations; check github for more details if you want
v2.0 (7/29/12)
added voltage control capabilities (use SetCPU or similar app to UV)
cleaned up CPU code again to try to get frequencies to stick
v2.1 (7/31/12)
added V(R) IO scheduler
change to a zip package
modified init.qcom.post_boot.sh and thermald.conf
added modules in the zip so it shouldn't break WiFi on EU ROMs anymore
allowed undervolting minimum of 400mV
tweaked minfree and ADJ values for multitasking and performance; the used values were from the V6 OOM Calculator
Conservative CPU governor as default for battery life (use an app to change it if you want)
defaulted CPU frequencies to 192Mhz 1.5Ghz on boot
v2.2 (8/2/12)
enabled zRam
adjusted VM ratios
added NEON and Snapdragon optimizations
v3.0 (8/8/12)
fixed SmartassV2 for performance and battery life
available with overclock or stock CPU clock
enhanced compatibility with many ROMs
cleaned up post_boot script and many parameters now handled @ kernel
fixed CPU reverting to min 384Mhz
overall much, much cleaner implementation and settings will stay
v3.1 (8/16/12)
a universal package
disabled fsync() for I/O improvement
optimized Ondemand CPU governor settings
v3.2 (8/22/12)
lighter OOM and ADJ settings for better multitasking
v3.3 (8/29/12)
added BrazilianWax, Intellidemand, InteractiveX, SavagedZen, and Smartass (V1) governors
added tun.ko and cifs.ko
XZ kernel compression
optimized SmartassV2 CPU governor
v3.4 (9/1/12)
added wifi module to the zip
tun.ko and cifs.ko now built into kernel
tweaked deadline I/O scheduler for better performance
make kernel use AC charging mode for unknown chargers
various lowmemorykiller fixes
fixed and tweaked a few other things
Click to expand...
Click to collapse
For Developers
How to build this kernel from source:
This is assuming you already have your Linux environment setup and installed the required packages for compiling a kernel.
1. Clone my initramfs and kernel sources.
Code:
git clone git://github.com/klin1344/kernel_ville_US.git
git clone git://github.com/klin1344/initramfs_ville_4.0.3.git
2. Compress the ramdisk into a gzipped archive. First navigate to the initramfs_ville_4.0.3 directory, then:
Code:
find . | cpio -o -H newc | gzip > ../ramdisk.gz
3. Grab the toolchain from DoomLord's handy repo:
Code:
git clone git://github.com/DooMLoRD/android_prebuilt_toolchains.git toolchains
4. I have created an easy build script. Modify the top four lines to be applicable to your setup. Make sure CROSS_COMPILE is set to the directory of the toolchain we just downloaded earlier (there are two; not the Linaro one). And change INITRAMFS_DIR to the directory of the ramdisk.gz you created earlier.
5. Build. First navigate to the kernel_ville_US directory.
Code:
./build.sh ville_defconfig
for the stock option or
Code:
./build.sh ville_oc_defconfig
if you want the overclocked option.
The script will detect the number of cores of your CPU and automatically make with the optimal -j#.
6. If all goes well you should end up with a boot.img in the kernel_ville_US directory.
FAQ.... Please read this before posting questions!!!
FAQ
Frequently asked questions. Please read all of this first, and then if it doesn't answer your question, feel free to ask in the thread. I just don't want to have to keep answering Is this kernel SENSE based? or How do I jailbreak my HTC One S??? type of questions. Lol. :silly: Thank you.
Click to expand...
Click to collapse
What ROMs is this kernel compatible with?
As stated in the OP, this kernel is compatible with all S4 devices running a 4.0.3 Sense-based ROM. It is NOT compatible with the new 2.21 RUU, which is Android 4.0.4 based. We will have to wait until HTC releases the new kernel source because the differences are not only in the initramfs.
What is the best governor for me to use?
It really depends on what you're looking for. If you want performance, go with Lionheart or Ondemand. If you want battery life, go with Conservative. And if you are looking for a balance between battery life and performance, then use either SmartassV2, Interactive, or LagFree. These are just my opinions. Look here for a great reference of all the CPU governors. Test them out and decide which works best for you.
Which I/O scheduler is the best?
I personally use SIO, but you can test and decide which is the best for you. Read here to find the pros and cons of each one.
How do I overclock?
The kernel should default at 192Mhz 1.5Ghz CPU clocks. To overclock, use SetCPU, No-Frills CPU, System Tuner Lite/Pro, or any similar CPU control app. Some apps don't allow the settings to stick properly. I recommend using No-Frills or System Tuner.
How do I undervolt?
Right now, the only app that works for voltage control is System Tuner. Both the Lite and Pro versions allow you to change the voltages. Do not use SetCPU as it doesn't work.
Here is the voltage table I am currently using:
Code:
1890mhz: 1250 mV
1809mhz: 1225 mV
1728mhz: 1200 mV
1674mhz: 1175 mV
1512mhz: 1150 mV
1458mhz: 1137 mV
1404mhz: 1125 mV
1350mhz: 1125 mV
1296mhz: 1100 mV
1242mhz: 1100 mV
1188mhz: 1075 mV
1134mhz: 1075 mV
1080mhz: 1025 mV
1026mhz: 1000 mV
972mhz: 1000 mV
918mhz: 975 mV
864mhz: 975 mV
810mhz: 950 mV
756mhz: 950 mV
702mhz: 900 mV
648mhz: 900 mV
594mhz: 875 mV
540mhz: 850 mV
486mhz: 800 mV
384mhz: 725 mV
192mhz: 650 mV
Please just take these as a grain of salt; not all chips are created equal! Some devices can become an ass when it comes to undervolting, while others can starve the CPU to death and still run fine. Experiment little by little until you find your perfect voltages.
What is zRam and how does it work?
Originally Posted by faux123
ZRAM (aka CompCache aka RAMZSwap)
ZRAM is an updated version formally known as CompCache and RAMZSwap. It was originally designed for 2.6.38.xx kernels, I have backported to our 2.6.35.xx kernel. ZRAM allows real-time compression of memory objects in RAM thus reducing memory pressure for the Linux kernel and can keep more apps in memory longer (more apps in RAM == better performance, less fetching from slower MMC or SDCard). Compression, however, is not Free. Some CPU cycles are required to do the compress/decompression, so there's a slight penalty for it. The original CompCache / RAMZSwap required a user space binary to control its behavior which adds additional penalty to performance, but the new version ZRAM eliminated the need for a separate dedicated daemon, thus reducing the overhead and increased performance from the old CompCache by 20%. Therefore, with the newer implementation of ZRAM interface, the performance penalty is almost negligible.
Click to expand...
Click to collapse
WiFi doesn't work???
Flash the alternative modules package in the OP. It is for EU based ROMs as well as MIUI Sense-based. You only need to flash it once, unless you change or update your ROM.
Nice..Will do testing...
Hopefully it give the best battery life than stock
Thank you sir!
(S4) HTC 1s
Here is a zip to flash the kernel! Testing with Axiom S v1.8, will test battery with SmartassV2
nieves53 said:
Here is a zip to flash the kernel! Testing with Axiom S v1.8, will test battery with SmartassV2
Click to expand...
Click to collapse
Thanks. But unfortunately the reason I did not make it a zip is because that some of us who are on hboot 1.13 or higher can't flash boot.img's in TWRP recovery at all. The same goes for radios. I stupidly ran the 1.78 RUU, which update my hboot from 1.09 to 1.13. :crying:
klin1344 said:
Thanks. But unfortunately the reason I did not make it a zip is because that some of us who are on hboot 1.13 or higher can't flash boot.img's in TWRP recovery at all. The same goes for radios. I stupidly ran the 1.78 RUU, which update my hboot from 1.09 to 1.13. :crying:
Click to expand...
Click to collapse
Should have just flashed the radio
How do you like the new radio? I seem to be getting a lot better service and a more stable WiFi connection.
Liking the kernel so far
Sent from my HTC VLE_U using xda premium
Bug I found -
-While install apps it take awhile for it to install. (1mins or 2min). I just phone the sit until it finish install
-After reboot ...the kernel take awhile for it kick in. For example..If you have email it will take awhile to prompt on notication bar .
Is it possible you can post zips for download in the OP? Thanks. Will try tomorrow.
x1tyme said:
Bug I found -
-While install apps it take awhile for it to install. (1mins or 2min). I just phone the sit until it finish install
-After reboot ...the kernel take awhile for it kick in. For example..If you have email it will take awhile to prompt on notication bar .
Click to expand...
Click to collapse
Maybe try wiping data / factory reset? To be honest those sound more like rom issues rather than kernel related issues.
I cannot reproduce it.
Sent from my One S
klin1344 said:
Maybe try wiping data / factory reset? To be honest those sound more like rom issues rather than kernel related issues.
I cannot reproduce it.
Sent from my One S
Click to expand...
Click to collapse
My fault. I was lazy and flash the flashable zip on post #7 and create this error. Reflash rom and fastboot usb and works like a charms..:good:
If you need another guy to test a 4.0.4 Pre-Release...
(i'm under Trick 6.0)
plakers said:
If you need another guy to test a 4.0.4 Pre-Release...
(i'm under Trick 6.0)
Click to expand...
Click to collapse
+1 but the thing is a bit complicated because we need current modules because of better wifi signal.
I guess we'll just have to wait for the new kernel source from 2.21 base
just flashed it with axiom v1.8.0
everything seems to be working fine.. it's fast smooth stable
nice stuff, Klin
Trying this now in hopes my frequency changes stick after a reboot unlike stock :/
Sent from my HTC VLE_U using Tapatalk 2
Is it normal for CPU settings to not stick after a reboot?
I set 1.3ghz/384mhz max/min for both cores. I reboot and it defaults back to 1.5/192
Basically same issue with stock kernel.
Elloco305 said:
Trying this now in hopes my frequency changes stick after a reboot unlike stock :/
Sent from my HTC VLE_U using Tapatalk 2
Is it normal for CPU settings to not stick after a reboot?
I set 1.3ghz/384mhz max/min for both cores. I reboot and it defaults back to 1.5/192
Basically same issue with stock kernel.
Click to expand...
Click to collapse
Have anybody experience there screen blink? Or just Rom issue
Sent from my HTC VLE_U using Tapatalk 2
Elloco305 said:
Trying this now in hopes my frequency changes stick after a reboot unlike stock :/
Sent from my HTC VLE_U using Tapatalk 2
Is it normal for CPU settings to not stick after a reboot?
I set 1.3ghz/384mhz max/min for both cores. I reboot and it defaults back to 1.5/192
Basically same issue with stock kernel.
Click to expand...
Click to collapse
What app are you using? I use No-Frills CPU and it has the "apply on boot" option.
klin1344 said:
What app are you using? I use No-Frills CPU and it has the "apply on boot" option.
Click to expand...
Click to collapse
Setting don't stick after reboot. I'm using setcpu
Also, When I applied this kernel..my screen flick across the screen while exit app (es explorer)
NEXT 2.1.8 placeholder: http://forum.xda-developers.com/showpost.php?p=51678873&postcount=472
STOP! This kernel supports ONLY Samsung Jelly Bean 4.1.x, 4.2.2, CM 10.1.x, 10.2, and 11.0 ROMs. It won't work on ICS, CM 9, CM 10.
FOR NOW I FORBID ANYONE ELSE REUSE THIS STILL IN DEVELOPMENT DUAL BOOT PROJECT FOR HIS/HER OWN GALAXY TAB 2 PROJECT!
IMPORTANT NOTES:
NEXT 2.x separated in two package: the kernel part as blackhawk-next-kernel-2.x-p51xx.zip and the proprietary binaries part as proprietary-vendor-samsung.zip for JB >= 4.2 (stock 4.2.2, CM 10.2) and proprietary-vendor-samsung-4.1.x.zip for JB 4.1.x (stock 4.1.2, CM 10.1) . Flash the kernel and then directly flash the proprietary binaries!
Download both proprietary-vendor-samsung.zip and proprietary-vendor-samsung-4.1.x.zip from http://forum.xda-developers.com/showthread.php?t=2285366 post #2!
Sources:
Kernel sources at http://github.com/kumajaya/android_kernel_samsung_espresso10/tree/cm-10.1-blackhawk
Features:
Samsung stock 4.1.x, 4.2.2 (since 1.8.3), CM 10.1.x and CM 10.2 (since 1.8.3) support with a single kernel image
For stock ROM: external SD card - internal media swapper script included
Samsung proprietary exFAT modules are loaded. CM 10.1 exFAT support files attached at post #2
For CM/CM based ROM, P31xx only: auto rotate screen default orientation depend on ro.sf.hwrotation value, camera orientation fix included
Dual-booting. You can have Samsung JB and CM 10.1 ROMs on a single device at the same time.
Nice looking AROMA based boot menu
Using CyanogenMod kernel source, updated to p3110 source for newer WLAN (Youtube HD bugfix on stock ROM), modem, sensors driver, and etc for both P31xx and P51xx target
CPU clock: 300MHz, 600MHz, 800MHz, 1.008GHz, 1.2GHz, 1.35GHz, 1.42GHz, 1.48GHz, and 1.52GHz, locked @ 1.008GHz on boot
GPU clock: 153.6MHz, 307.2MHz, 384MHz, and 512MHz, 307.2MHz as the default maximum clock
CPU voltage control. You can use Android Tuner/System Tuner/Trickster MOD to set CPU voltage
The ramdisk base on JB 4.1.2 (stock ROM) and JB 4.2.2 (CM 10.1)
Using newer PowerVR SGX 540 kernel modules and binaries blob
row, bfq, sio, and vr scheduler support
Governor bug fix. Replace Samsung's interactive governor with default OMAP4 3.0.31 interactive governor from omapzoom.org, plus pegasusq and lulzactive
NFS and CIFS/samba (not loaded by default) filesystem support
LZMA compressed initrd, to keep boot image smaller than 8MB
swap support. zram and cleancache with a working zcache driver, enabled by default
kernel config, insmod configs.ko and then you can access /proc/config.gz
external modem support, for PPP Widget (not loaded by default, P31xx need powered USB hub for external modem)
Some tweaks from gokhanmoral's siyahkernel for S3, passive entropy tweak applied
Remove a lot of debug message from touchscreen driver, display, mmc, modem, etc
linaro arm-linux-gnueabihf- cross compiler, compiler optimization applied
SuperSU v1.41 for stock ROM
Self compiled BusyBox v1.22.0-git in /sbin, config file based on CM's BusyBox bbconfig output. fstrim applet patch applied, android_reboot applet added (a quick but clean port from Android toolbox), swapon applet with priority option. For stock ROM: this version of Busybox will overwrite busybox binary in /system/bin or /system/xbin and save it as busybox.backup
Early boot scripts support (/system/etc/init.d, /data/local/userinit.sh, and /data/local/userinit.d)
Post boot script support (/system/etc/init.post_boot.sh)
For stock ROM: custom boot animation support (/data/local/bootanimation.zip or /system/media/bootanimation.zip if exists, Samsung boot animation as a fallback). If a bootanimation.zip found, the boot sound will be turned off as well as the shutdown animation.
Modified mount options
adb insecure, adb mode in charge state also insecure
Advanced TCP congestion support, westwood as the default congestion
No /system/etc/hosts patch, you can install AdAway from F-Droid
Known Problems:
Thanks To:
gokhanmoral, amarullz, Phil3759, Chainfire, cmenard, codeworkx, imoseyon, coolbho3k, Faux123, AuxLV
brolee93 for latest P51xx Samsung stock boot image
This part will be expanded. Most of the patches I applied are coded by someone else. Please remind me if I forget to give credits to anybody...
Downloads:
PhilZ Touch blackhawk version attached, PhilZ Touch 5.08.5 attached at post #3
NEXT kernel beta release attached
NEXT tool: http://forum.xda-developers.com/showthread.php?t=2285366
exFAT support files for CM/CM based ROM: http://forum.xda-developers.com/showthread.php?t=2285366 post #2
Todo:
More features in NEXT tool
Special Thanks:
@behemot24, @shakatu, @ironmaskusa, @tetakpatak
XDA:DevDB Information
[KERNEL][SINGLE/DUAL][JB/KK][STOCK/CM]blackhawk's NEXT kernel, Kernel for the Samsung Galaxy Tab 2
Contributors
ketut.kumajaya, Android-Andi
Kernel Special Features: Dual boot stock and AOSP based ROM
Version Information
Status: Stable
Current Stable Version: 2.4
Created 2014-09-21
Last Updated 2014-10-29
NEXT 2.x separated in two package: the kernel part as blackhawk-next-kernel-2.x-p51xx.zip and the proprietary binaries part as proprietary-vendor-samsung.zip for JB >= 4.2 (stock 4.2.2, CM 10.2) and proprietary-vendor-samsung-4.1.x.zip for JB 4.1.x (stock 4.1.2, CM 10.1) . Flash the kernel and then directly flash the proprietary binaries!
Download both proprietary-vendor-samsung.zip and proprietary-vendor-samsung-4.1.x.zip from http://forum.xda-developers.com/showthread.php?t=2285366 post #2!
Changelog:
21/04/2014 2.2:
Flash-Friendly File System (f2fs) support
Full github commits 8/4 - 20/4/2014: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-11.0
Update proprietary blobs, proprietary-vendor-samsung-update.zip
28/10/2013 2.1.4 -> 2.1.5:
Updated to upstream 3.0.101 kernel
Audit and SELinux enabled
Smartreflex completely disabled
GPU frequencies not exposed to STweaks bug fixed
Do not load exFAT modules on CM 10.2
Full changelog: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.2-update
27/10/2013 2.1.3 -> 2.1.4:
Ramdisk updated to sync with latest CM 10.2
21/10/2013 1.8.3 -> 2.1.3:
Update init script for PAC
Disable almost all kernel debugging support except KALLSYMS. Kernel failed to boot with CONFIG_KALLSYMS disabled
Turn all CPUs online when governor gets changed, hotplug bug workaround
SIO and VR I/O scheduler
Initial STweaks support, big thanks @gokhanmoral. Download STweaks app from Play store to access almost all NEXT related settings (CPU governor, frequency, and voltages; GPU governor and frequency limit; surfaceflinger rotation; I/O scheduler; logger; CIFS, Xbox controller, and USB modem support; and dual boot related settings).
Update overclock codes, remove gpu_oc interface: https://github.com/kumajaya/android...mmit/94ac45a10213de400c7bf3c01b5c5b052ae8ba18
sgxfreq: add sysfs interface to store frequency limit: https://github.com/kumajaya/android...mmit/738061b30d2278d3b51b341bc2597dad300f4e47
sgxfreq: limit frequency to default on boot: https://github.com/kumajaya/android...mmit/8a6933cf6565b5587db6a2a5ce7b1207807ab701
The latest Android Tuner app needed to control the modified OMAP GPU control interface but the dirty way by editing /etc/init.post_boot.sh always available
Separated vendor blobs for JB 4.1.x and JB >= 4.2, @poppolo2001 fix applied
With CPU and GPU overclock, CPU under/over voltage, upstream kernel 3.0.96 by @CodyF86
Complete changelog: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.2-update
10/08/2013 1.6.3 -> 1.8.3:
Initial upcoming Samsung 4.2.2 support
Initial CM 10.2 support. Do not flash blackhawk-next-cm-exfat-vold.zip! CM 10.2 already has an open source/reverse engineered exFAT filesystem support
Vendor blobs in separate flashable zip. For all ROMs, on both 1st and 2nd ROM: Flash vendor-blobs-new-ducati-blackhawk.zip directly after flashing NEXT 1.8.3!
Updated to upstream Linux kernel 3.0.41 (incremental patch)
The first kernel utilizing the new ducati firmware, the first kernel preserved 804MB RAM! Don't forget to flash vendor-blobs-old-ducati-blackhawk.zip if you switch to another kernel
zram switched to zsmalloc, zram optimized for Android disabled
XBox 360 USB controller with BigX LED support enabled (by @iks8 request). Modules not loaded by default, edit /system/etc/init.d/02modules to activate it.
23/07/2013 1.6.2 -> 1.6.3:
Add android_reboot applet to NEXT's busybox (a quick port from Android toolbox) to fix AROMA boot menu fail to boot into recovery/bootloader as reported by @kinung
I hate bug!
22/07/2013 1.5 -> 1.6.2:
Hotplug CPU governor working properly with cleancache enabled, zcahe memory corruption problem fixed!
Static linked busybox compiled from source, fstrim patch applied. Busybox config based on CM's busybox bbconfig output. Total 46 new busybox applet, add priority option to swapon applet
zRAM swap per CPU core, same priority value. CM's /system/bin/compcache script updated to handle 2 zRAM devices. Reference: http://wiki.gentoo.org/wiki/Zram
Stock ROM default zRAM size 26% RAM size. Following CM's standard, user can set zRAM value for example to 30% by typing "setprop persist.service.zram 30" over Terminal Emulator or over "adb shell setprop persist.service.zram 30". CM user can use Settings application: Performance - Memory management - zRam.
Swappiness value changed to 90
LZO compression updated to current upstream version, optimized for arm. Reference: http://git.kernel.org/cgit/linux/ke.../?id=b0af9cd9aab60ceb17d3ebabb9fdf4ff0a99cf50
zRAM support optimized for Android, utilizing the new lzo library.
cleancache support with working zcache driver, utilizing the new lzo library
entropy threshold tweaks, /dev/random linked to /dev/urandom
github 14-22/07/2013 commits: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.1-blackhawk
12/07/2013 1.4.1 -> 1.5:
Decrease CPU voltage for frequencies below 1.2GHz, increase CPU voltage for frequencies above 1.2GHz
Re-enable MMC_CAP_ERASE for I/O speed improvement, run "fstrim -v /data" and "fstrim -v /cache" manually to TRIM your filesystem or run LagFix (fstrim GUI, download it from Play)
Remove my old hack in cpufreq driver
Newer PowerVR SGX540 3D kernel module and vendor binaries, in sync to CM-10.1. You must update both 1st and 2nd ROM to renew both ROM vendor binaries!
SuperSU v1.41
16/06/2013 1.4 -> 1.4.1:
I/O speed improvement, 1.3 and 1.4 bugfix
SuperSU v1.34 - thanks Chainfire
nooc: Smartreflex class 3 re-enabled, voltage control disabled
04/06/2013 1.3 -> 1.4:
Selected kernel modules, scripts, and binaries integrated in boot.img, single flash for 1st and 2nd ROM
Kernel compression back to gzip, boot.img compression switched to lzma for better compression (I need more space)
Auto root (for stock)
Auto busybox (for stock)
External sdcard and internal media swapper script integrated in boot.img (for stock as 1st ROM)
Override init.d CPU governor setting on boot completed (technical reason/by design). Please use an app "on boot" or /etc/init.post_boot.sh to set CPU governor
init script reworked (again), simplified
Standalone nooc version, no longer as an addon for standard NEXT
Untested CRT off animation support
NEXT users, please update your kernel to 1.3 version to avoid filesystem corruption risk on Samsung stock/stock based ROM! Please read Dual Boot FAQs how to update your kernel!
01/06/2013 beta -> 1.3:
Better data integrity on both 1st and 2nd ROM
Ramdisk init scripts reworked, inline with the latest Samsung (Taiwan BRI 04/2013) and CM (29/05/2013 nightly)
Inline with P31xx, that's way this port version directly jump to 1.3
Updated exFAT modules (don't know it's better or worse, it's closed source)
Default CPU clock still 1.008GHz, default GPU clock 307.2MHz. Non OC version as an addon
Both version tested on P3100 (remember, I have no access to P51xx device). Booted, upscale graphics, touchscreen not work, wrong orientation sensor, swapped volume button, got 1280x800 screenshots :laugh:
30/05/2013: Initial beta release.
Dual Boot FAQs
Adapted from droidphile's "Dual Boot FAQs" with permission.
1. "Why would I wanna dual-boot?"
A. You don't have to.
Suppose you're more of an aosp rom fan. But misses the HDMI out, bluetooth hands-free and love sammy camera more. Do a minimal installation of sammy rom and boot into it when in need of these features and use aosp rom otherwise.
Or you are a sammy rom fan but love the responsiveness and pure android feel of aosp roms.
And while you can dual boot two sammy or two aosp roms, it doesn't make any sense.
2. "What if I don't need dual booting?"
A. No issues. Kernel won't force to setup 2 roms. You can single boot as before.
3. "Will dual booting change my bootloader or do any dangerous stuff like setting my phone on fire?"
A. NO. Changes are at kernel and ramfs level only. Some space in your internal sd card is used, and also the unused hidden partition mmcblk0p11 is used to store cache of second rom. Dual booting doesn't repartition the filesystem or perform anything scary.
4. "I want to setup dual booting."
A. There are four situations:-
1) Sammy rom now. Want to use aosp as secondary.
2) Sammy rom now. Want to use aosp as primary.
3) Aosp rom now. Want to use sammy as secondary.
4) Aosp rom now. Want to use sammy as primary.
Prerequisites for any setup is
a) Flash latest blackhawk's NEXT kernel
b) Flash new ducati vendor blobs (since 1.8.x)
c) Flash latest PhilZ Touch - blackhawk repack version - recovery
d) Atleast 90% battery left.
e) 2 GB free on internal SD.
f) Some spare time
1) Present sammy, setup aosp as secondary:-
i) Reboot into recovery
ii) Flash blackhawk's NEXT tool, create system.img for CM/CM based ROM and then close it
iii) Reboot into secondary recovery
iv) Flash aosp ROM as 2nd ROM
v) Flash blackhawk's NEXT kernel again
vi) Flash new ducati vendor blobs again (since 1.8.x)
2) Present sammy, setup aosp as primary:-
i) Reboot into recovery
ii) Nandroid backup your current sammy ROM
iii) Flash blackhawk's NEXT tool, create system.img for Samsung stock/stock based ROM and then close it
iv) Reboot into secondary recovery
v) Nandroid restore your sammy ROM as 2nd ROM
vi) Flash blackhawk's NEXT kernel again
vii) Flash new ducati vendor blobs again (since 1.8.x)
viii) Reboot into primary recovery
ix) Flash aosp ROM as 1st ROM
x) Flash blackhawk's NEXT kernel again
xi) Flash new ducati vendor blobs again (since 1.8.x)
3) Present aosp, setup sammy as secondary:-
Same as (1), instead of flashing aosp to second, flash sammy to second.
4) Present aosp, setup sammy as primary:-
Same as (2), instead of flashing aosp to first ROM, flash sammy.
NOTE:
-To dual boot Two Aosp or Two Sammy roms, just follow (1) or (2) (depending on which one of them you want as primary/secondary), just flash Sammy instead of aosp or aosp instead of sammy.
5. "What things should I be taking care off while dealing with dual booting?"
A. - Make sure where you are: in primary or secondary recovery.
6. "How to boot into primary rom?"
A. AROMA based boot menu will help you on every boot.
7. "How to boot into secondary rom?"
A. AROMA based boot menu will help you on every boot.
8. "Is kernel partition shared?"
A. Yes. Same kernel boots both roms.
9. "If I flash another kernel (that doesn't support db) do I lose dual booting?"
A. Yes
10. "I lost dualbooting after flashing another kernel. I didn't do anything to second rom files in sdcard/.secondrom. How can I get db back?"
A. Just flash the latest blackhawk's NEXT kernel, flash new ducati vendor blobs again (since 1.8.x)
11. "Will there be any performance degradation on the rom used as secondary compared to primary?"
A. NO
12. "Will my phone run slow overall because of db?"
A. NO
13. "How to flash a newer version of 1st rom?"
A. As usual, just flash it from primary recovery. Flash blackhawk's NEXT kernel again, flash new ducati vendor blobs again (since 1.8.x)
14. "How to flash newer version of 2nd rom?"
A. Just flash it from secondary recovery. Flash blackhawk's NEXT kernel again, flash new ducati vendor blobs again (since 1.8.x)
15. "Would upgrading 1st or second rom cause other rom to fail on boot?"
A. No. Partitions of other rom are not touched during upgrading.
16. "I miss the recovery I used before, so much.."
A. PhilZ Touch not bad at all.
17. "User apps of 1st rom are automatically available for second rom?"
A. NO. However, if you had backed them up using Titanium Backup or similar apps, just restore apps while on second rom.
18. "I wanna keep separate backup for apps in both the Roms, since I use one Rom for say entertainment and other productivity."
A. Setup different backup directory in Titanium Backup in 1st and 2nd rom.
19. "I don't see STweaks app in second rom."
A. This is blackhawk's NEXT dual boot solution for Galaxy Tab 2, a free implementation of gokhanmoral's Siyah dual boot.
20. "Do I need to anything special before flashing a newer blackhawk's NEXT kernel?"
A. NO. Just flash kernel in primary and secondary recovery. Yes, on both 1st and 2nd ROM. Just flash kernel in recovery - whichever you used to do. Kernel image is copied to the unified kernel partition (since 1.4 version). Flash new ducati vendor blobs (since 1.8.x) on both ROM may be required to ensure vendor blobs match to the kernel
21. "How can I run same STweaks settings of 1st Rom in 2nd Rom?"
A. This is blackhawk's NEXT dual boot solution for Galaxy Tab 2, a free implementation of gokhanmoral's Siyah dual boot.
22. "How do I remove everything related to DB and run single boot again?"
A. In primary recovery, flash blackhawk's NEXT tool and delete 2nd ROM system image. OR delete .secondrom directory in /data/media while on 1st Rom.
23. "If secondrom files are kept in /data/media, will wiping data in recovery erase second rom files?"
A. NO. /data/media is skipped in CWM recovery.
24. "I was using ExFat card on sammy rom without any issues. I have setup dual boot with aosp and now after booting into CM it says microSD card is corrupted."
A. Aosp roms doesn't support ExFat out of the box. The data was corrupted by aosp vold. Even if you boot back to Sammy rom, it still would be corrupted. To recover data, manually mount the card in recovery, copy contents to internal SD and reformat card to a Fat32.
Also try
chkdsk X: /f (where X is the drive letter of microsd), you may be able to copy data.
25. "I read somewhere that both rom data partition use the same space. Doesn't that mean my apps are shared across roms?"
A. NO. It just means they uses same partition. They're still different directories.
1st rom data = /data
2nd rom data = /data/media/.secondrom/data
26. "Will hitting "Boot into Secondary Recovery" in recovery boot menu change my recovery?"
A. NO. It just runs (not flash) an alternate recovery so that you can configure dualboot settings.
27. "How do I backup 1st Rom and 2nd Rom?"
A. To backup 1st Rom, do what you did to backup rom while you were single booting a while ago.
To backup 2nd Rom, use the secondary recovery.
28. "Is there an easier way for dual-boot?"
A. Yes, send your device to me.
29. "DB architecture?"
A. Like you know, every rom has a /data, /system, /cache partition and a kernel to boot.
For primary rom, it's
mmcblk0p10 = /data
mmcblk0p9 = /system
mmcblk0p7 = /cache
And these won't change whether you're single booting or dual booting.
For secondary rom, data and system is stored in internal sd, cache in hidden partition. Note that internal sd in our device is mounted to /data/media.
We have data as a directory, System as an image in data/media/.secondrom. Cache in mmcblk0p11 which is hidden partition and not used otherwise.
- When second rom is booting, second rom data is bind mounted to mmcblk0p10 as /data/
- data/media/.secondrom/system.img partition is mounted as /system.
- mmcblk0p11 is mounted as /cache.
More FAQs will be added and the list will be updated as DB is improved.
Dual Boot Exercises
http://forum.xda-developers.com/showthread.php?t=2285366 post #4.
Was waiting for this :victory:
Sent from my GT-P5110 using XDA Premium HD app
Just opened a new thread for my masterpiece work on Galaxy Tab 2. Enjoy it and don't forget to press my Thanks button or better my DTM button
PhilZ Touch attached in post #1 has a "red" on screen navigation bar in secondary recovery to distinguish between primary and secondary :laugh:
So this kernel boots 1 ROM over internal storage and second over SD card?
Sent from my GT-P5110 using XDA Premium HD app
Marionette said:
So this kernel boots 1 ROM over internal storage and second over SD card?
Sent from my GT-P5110 using XDA Premium HD app
Click to expand...
Click to collapse
Dual Boot FAQs #29.
Ohhh good news i go to test thanks you rock
With 0.6 i can oc 1.35.
But now i have freez or reboot or black screen
brolee93 said:
Ohhh good news i go to test thanks you rock
With 0.6 i can oc 1.35.
But now i have freez or reboot or black screen
Click to expand...
Click to collapse
Please try increase the CPU voltage by 25mV. In this version, CPU voltage 50mV lower than the previous values. You can use Android Tuner or /system/etc/init.post_boot.sh .
KK, you are a genius! This is working splendidly, I have cyanogen as my primary and blaster as my secondary and they are both workihg smooth for me so far... I have them both running currently at 1200 mhz and seem to be doing fine.. you have really made my day!
Sent from my GT-P5113 using Tapatalk HD
Running smoothly for Zap Blaster.
ironmaskusa said:
KK, you are a genius! This is working splendidly, I have cyanogen as my primary and blaster as my secondary and they are both workihg smooth for me so far... I have them both running currently at 1200 mhz and seem to be doing fine.. you have really made my day!
Sent from my GT-P5113 using Tapatalk HD
Click to expand...
Click to collapse
I actually watched your HDMI problem. It's one of the reasons this dual boot solution was born. Glad I could help you, thanks for your support :good:
shakatu said:
Running smoothly for Zap Blaster.
Click to expand...
Click to collapse
Really? And all your init.d scripts removed by NEXT
That's okay cuz I have No Frills set up for my CPU settings. Of course my public release is still running kkboot 1.6.
After looking at your install script IDK if I would include this in my ROM if/when you allow people to. I'll let them make up their own mind.
Sent from my GT-P5113 using XDA Premium HD app
shakatu said:
That's okay cuz I have No Frills set up for my CPU settings. Of course my public release is still running kkboot 1.6.
After looking at your install script IDK if I would include this in my ROM if/when you allow people to. I'll let them make up their own mind.
Sent from my GT-P5113 using XDA Premium HD app
Click to expand...
Click to collapse
Personally, I found that Zap Blaster works well my device (p5113) because of the IR and such.. plus at the time it was overclockable and my HDMI output worked well with it. So, I decided to use it for awhile.. but I could not resist CM because it runs so smooth and I love how clean and reliable it has always been on me for this device as well as other devices I have owned.
Again, I am very happy about this DUAL boot option and I don't think I will change my setup for a time to come... My tablet is perfect now, in my opinion. Thanks again, KK.
The tablet behaviour between this kernel and the samsung original kernel is completely different! Ketut, if samsung would give a crap about their customers, they should buy this kernel from you and push it on all the galaxy tab 2... but that's not going to happen, so actually only the xda members have the chance to see their tablet working as it should, thanks to your work. Lucky us
behemot24 said:
The tablet behaviour between this kernel and the samsung original kernel is completely different! Ketut, if samsung would give a crap about their customers, they should buy this kernel from you and push it on all the galaxy tab 2... but that's not going to happen, so actually only the xda members have the chance to see their tablet working as it should, thanks to your work. Lucky us
Click to expand...
Click to collapse
For free A lot of clicks to install NEXT package but why people missed to click my Thanks button
EDIT:
This kernel version will directly jump to 1.3 in order to sync with P31xx version. Still inspecting line by line using diff tool to make sure already in sync
When i install this kernel on ZapBlaster the Video Player and Camera stops working
Sent from my GT-P5113 using xda premium
rap3rman said:
When i install this kernel on ZapBlaster the Video Player and Camera stops working
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
Two apps I never use on my tablet, so I haven't tested them...
ketut.kumajaya said:
Please try increase the CPU voltage by 25mV. In this version, CPU voltage 50mV lower than the previous values. You can use Android Tuner or /system/etc/init.post_boot.sh .
Click to expand...
Click to collapse
yeah ok i see this .
can you add Stweaks support ?
This post can be updated anytime.
For korean support and for those who can translate Korean, visit my blog:
http://kykint.tistory.com/
Download TWRP Recovery v2.8.7.0 for G906SKL
/* Requirements */
* Galaxy S5 broadband LTE-A (SM-G906S, G906K, G906L)
* Samsung stock firmware or Dokdo-projct
- Kitkat: ANK1
- Lollipop: BOG2 for G906K, BOH1 for G906S/L
* Custom recovery (Philz, TWRP, etc)
/* Note before using */
* Backup important data before installing
* Upon installation, every warranty inclusing KNOX becomes void
* I, kykint, am not responsible for any inconvenience or problems that occur while using this kernel
* Only one hotplug driver should be on (mpdecision, intelli_plug, alucard_hotplug, lazyplug)
Lazyplug is currently not supported on kernel customizing applications. Wait until their developers update.
* Dokdo-Project version of lolliwiz is highly experimental. Don't complain about battery drain.
It also does not support uninstaller yet.
/* About new installer */
Since Release 9, the installer will automatically extract your device's ramdisk, merge it with lolliwiz kernel, and then install it.
Upon installation, if a backup folder (/system/lolliwiz-bak) is found, it will automatically restore it first and then continue installation.
It will backup original boot.img and sensors library to the backup folder (/system/lolliwiz-bak) while installing.
There might be some problems regarding this new installer, so please keep the following instructions in mind.
* When installing another variant's ROM, do not install lolliwiz right after flashing ROM.
Install the stock kernel of your variant, and then install lolliwiz.
* Those who have been using R8 or older version of lolliwiz must flash stock kernel first before installing R9 or later.
* Do not install stock kernel when lolliwiz is installed on your device.
Only install stock kernel when uninstaller fails to remove lolliwiz and restore to stock kernel.
/* Kernel features */
Built with custom compiled krait-optimized UBERTC 5.2.1
Various compile optimization flags
Various improvements backported from Linux mainline
CPU Governors: franco interactive & conservative, intelliactive, and a lot more
I/O Schedulers: CFQ, ROW, DEADLINE, SIO, FIOPS
Custom hotplug drivers: intelli_plug, alucard_hotplug, lazyplug
CPU Voltage control
Adreno_idler GPU governor addon
Simple_ondemand is not crashing anymore
Display gamma control
Dynamic FSync Control
SELinux set as permissive by default
FauxSound ported for wcd9330 (LP only)
Support for kernel mode NEON
Optimized Kernel Samepage Merging
Quickwakeup driver by Motorola
Random driver ported from latest Linux mainline
Adaptive LowMemoryKiller
Full support for F2FS
Power-efficient Workqueue
Unaligned access support for lib
Init.d script support
Various minor fixes and improvements
/* Changelogs */
Refer to the 3rd post
/* Kernel customization */
Recommended applications: Kernel Adiutor, TricksterMod
/* Downloads */
Lolliwiz & stock kernels
Previous versions of lolliwiz
LW-G906-Dokdo-R*.zip : for Dokdo-Project users
LW-G906-R*_F2FS.zip : for F2FS users
/* F2FS Conversion Manual */
Refer to the 2nd post.
/* Chatters */
Release 9 and 10 are mostly bug fix releases, so there isn't much difference.
Kitkat support has been put off to R11, and if a bug is found again and R11 happens to be released early, it will be put off to later release again.
Still, I'm considering EOL of kitkat version as it is becoming harder to support the old Linux version.
/* Contacts */
You can contact me through telegram @maplezeon, but I won't listen to complaints.
On weekdays I'm mostly at school, from 7am to 10pm, so there's no much time for chats.
/* Source */
http://pc.cd/U2YrtalK
/* Special thanks to */
세이님, 티라미슈님, hsk님, arter97님, JustArchi, Christopher83, faux123,
franciscofrancoeng.stk, flar2, imoseyon, friedrich420, Google, Samsung
and every single one of you guys, for using my kernel
XDA:DevDB Information
Lolliwiz Kernel for SM-G906, Kernel for the Samsung Galaxy S 5
Contributors
kykint
Source Code: http://pc.cd/U2YrtalK
Kernel Special Features:
Version Information
Status: Stable
Created 2015-04-28
Last Updated 2015-09-11
Changelogs
Release 10 - Sep 7
Reverted GCC 5+ compatibility improvement patches
=> Hopefully fixed some applications disappearing
Unaligned access enabled explicitly for lib
Release 9 - Sep 6
Brand new installer
=> Now support all three variants (S/K/L), boot.img and sensors library are backed up in /system/lolliwiz-bak
Add uninstaller
Fixed proximity sensor not working
=> Caused by Merge of G906K Kernel source, solved by installing sensors library from OG2 firmware
Applied patches regarding media driver
Updated lz4 source and enable unaligned access
NVIDIA's power savings patch
Westwood as default TCP congestion control method
Optimized intelli_plug
New hotplug driver: Lazyplug by arter97
=> Currently not supported on kernel setting applications, wait for updates
Some GCC 5+ compatibility improvements
Release 8 - Sep 1
Added experimental support for Dokdo-Project
(Compatible with all three variables and every version of Dokdo-Project)
KK support dropped at the moment
LP: Common: Merged G906K OG2 kernel source
LP: kt: Merged OG2 ramdisk
LP: skt,lgu: Merged OH2 ramdisk
LP: kt: fixed a typo in ramdisk
Linux 3.10.70
Full F2FS support + source updated to the latest
Power-efficient workqueue
Random driver backported from Linux 4.2+
Another new hotplug driver - Alucard hotplug
Custom built UBERTC with Krait optimizations
New build optimization flags
Fixed min cpu frequency changing on its own
Dynamic fsync disabled by default
built-in support for NTFS
Other miscellaneous fixes and updates
Release 7 - Jun 28
LP: Imported patches from upstream (1,000+ patches)
LP: Linux 3.10.59
KK: Imported patches from upstream (300+ patches)
KK: Linux 3.10.6
Compile optimization flags from arter97's kernel, big thanks to @arter97
Added adreno_idler addon for adreno-msm-tz GPU governor
Removed Simple GPU Algorithm
Switched to UBER Toolchain, GCC 5.1
Added motorola's quickwakeup driver
Added patches to reduce wakelock
Backported random driver from Linux 4.0.6
Optimized KSM
Added adaptive_lmk
Various small fixes & improvements
Release 6 - May 30
Added support for KitKat
Fixed wrong boot.img arguments
Fixed Sweep2Sleep not working on some variants
Removed SEANDROID warning on boot logo
Added advanced TCP congestion methods
Disabled crc check for better performance
Merged BOE1 changes
Ramdisk compressed with LZ4
Other small tweaks & fixes
Release 5 - Apr 20
Removed smartassV2 CPU Governor
Added mythx_plug CPU Governor
Added support for kernel NEON mode
Removed Franco's Sound Control
Ported FauxSound for work with wcd9330
Applied patches for gpu and video driver
Imported latest interactive & conservative governor from franco's shamu kernel
Added support for KSM on/off
Enabled tuning option for Cortex-A15
Some minor fixes from faux123
F2FS Conversion manual
/* F2FS Conversion Manual */
(for LP and Dokdo-Project only, no KK support)
(Not tested on Dokdo-Project)
I will not add any additional explanations about F2FS, since this is a very risky task and recommended only for experts,
and since not knowing about F2FS means that you're not one of them.
Cautions
1. Conversion process of /data partition and filesystem will wipe away every single data in your device,
so every data in internal sdcard should be backed up on your PC.
2. Flashing /cache partition image when the device has already been converted to F2FS will format /cache partition to EXT4,
so manual conversion process of /cache partition to F2FS must be done again.
3. The /cache partition image mentioned above is included in stock firmware package, so be careful when installing stock firmware
4. Inside stock firmware is included a stock kernel which only supports EXT4, so again, be careful when installing stock firmware
5. /data and /cache partition must be set to the same filesystem, both EXT4, or both F2FS
6. I personally recommend that every process be done using my TWRP recovery, which will be posted in a seperate thread later.
7. The F2FS version of kernel zip has a '_F2FS' tag at the end of its filename, while EXT4 has nothing.
Be careful, Dokdo-Project version supports both EXT4 and F2FS, so they're not seperated,
and when converting to F2FS on Dokdo-Project, you can skip kernel switching(reinstalling) process.
How to change filesystem on TWRP
Wipe > Advanced Wipe > (Select a partition) > Repair or Change File System > Change FIle System > (choose between EXT4 and F2FS) > Swipe to Change
* It takes a great amount of time when changing to EXT4, up to several minutes.
How to check current filesystem on TWRP
Wipe > Advanced Wipe > (Select a partition) > Repair or Change File System
and you'll see your current filesystem on the upper part of the screen.
Converting to F2FS
0. For stability, flash uninstaller first if you already have lolliwiz installed.
1. Install F2FS version of Lolliwiz. (_F2FS.zip)
2. Change the filesystem of /data and /cache partition to F2FS.
3. Reboot into recovery mode again.
Back to EXT4
0. For stability, flash uninstaller first if you already have lolliwiz installed.
1. Install EXT4 version of Lolliwiz.
2. Change the filesystem of /data and /cache partition to EXT4.
3. Reboot into recovery mode again.
Installing stock firmware on F2FS
1. Reboot into download mode and install stock firmware with odin as usual.
2. When the installation finishes, it'll automatically reboot into recovery mode and flash CSC package.
Wait until androboy disappears and the device reboots again.
3. Reboot into download mode again.
4. Install my TWRP.
5. Reboot into recovery right after installing.
6. Install F2FS version of lolliwiz.
7. Format /cache partition to F2FS
8. Run factory reset if needed. This is an option.
9. Reboot.
If the device won't boot even if you carefully followed all of the above instructions, repeat the process again.
Thanks
Thanks I was on the Korean forums yesterday trying to translate lol.
I noticed there's a test for b5. Giving it a try.
One issue I seem to have on b4 and 5 test is that no matter what kernel tuning app I use if I turn off mpdecision and intelliplug on, after a reboot mpdecision always comes back on.
Audioboxer said:
I noticed there's a test for b5. Giving it a try.
One issue I seem to have on b4 and 5 test is that no matter what kernel tuning app I use if I turn off mpdecision and intelliplug on, after a reboot mpdecision always comes back on.
Click to expand...
Click to collapse
Kernel settings are set to defaults on each reboot and the default setting on hotplug is mpdecision on, intelli_plug off. That's why every kernel app has the ability to restore previous settings after reboot. Try enableing them, kernel adiutor works fine for me
kykint said:
Kernel settings are set to defaults on each reboot and the default setting on hotplug is mpdecision on, intelli_plug off. That's why every kernel app has the ability to restore previous settings after reboot. Try enableing them, kernel adiutor works fine for me
Click to expand...
Click to collapse
Thanks, but I told it to save settings. It's weird as all the settings were saved, including intelliplug on, but mpdecision was turned on as well. I'll uninstall it and start again!
Do you have a donation link btw?
Edit: Here is what I mean
{
"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"
}
Edit2: Strange, I reflashed the kernel and it is now working!
Audioboxer said:
Thanks, but I told it to save settings. It's weird as all the settings were saved, including intelliplug on, but mpdecision was turned on as well. I'll uninstall it and start again!
Do you have a donation link btw?
Edit: Here is what I mean
Edit2: Strange, I reflashed the kernel and it is now working!
Click to expand...
Click to collapse
Nice to hear it's working well now.
I don't get donations, maybe you could donate to the REAL developers out there, they're always working hard for us XD
Very interesting!
I'm reading the Asian forums since a week and I have found that this kernel is well used.
How can I flash back stock kernel if something happens? And where can I find stock kernels??
If they are unavailable, I'd like to make my own Odin tar.md5 files for flashing stock kernel.
Can I follow the script/batch procedure (found here on Xda) that produces the tar.md5 flashable files?
Tnx!!
Sent from my Samsung Galaxy S3 GT-i9300 using Tapatalk 4
Thanks
PIRATA! said:
Very interesting!
I'm reading the Asian forums since a week and I have found that this kernel is well used.
How can I flash back stock kernel if something happens? And where can I find stock kernels??
If they are unavailable, I'd like to make my own Odin tar.md5 files for flashing stock kernel.
Can I follow the script/batch procedure (found here on Xda) that produces the tar.md5 flashable files?
Tnx!!
Sent from my Samsung Galaxy S3 GT-i9300 using Tapatalk 4
Click to expand...
Click to collapse
No worries, I'll upload stock kernels for recovery/odin as soon as I get back home
kykint said:
No worries, I'll upload stock kernels for recovery/odin as soon as I get back home
Click to expand...
Click to collapse
Can you do it also for KitKat if you have then?
Tnx.
Sent from my Samsung Galaxy S3 GT-i9300 using Tapatalk 4
Sharing battery based profile still in testing
Hi everyone ,
i would like to share my battery based profile.
I used Trickstermod kernel app taken from bbs dot sonyue dot com
( The kernel app is under attachment)
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
1. Install the app.
2. Open the app, at top left a list will open, Choose the General
3. Change the following
I/O Control:
Read Ahead Buffer Size 1024
Schedular fiops
CPU Frequency Control
Frequency Lock ON
Min 300000 (choose the lowest scroll to the top first)
Max 1574400
CPU Governor Control
Governor Conservativex
------------------------------------------------------------------------------------------------------------------------------------------
4. Now Choose Specific
Mp-Decision OFF
Intelli-Plug ON
Dynamic FSYNC ON
GPU Governor Powersave
GPU Max Frequency 240
Intelli-Thermal Control ..........> Intelli-Thermal ON
MPU Voltages
( I undervolted from Snapdragon 805 thread in xda)
< 300MHz 700
< 345MHz 710
< 422MHz 720
< 499MHz 730
< 576MHz 740
< 652MHz 750
< 729MHz 760
< 806MHz 770
< 883MHz 780
< 960MHz 820
< 1036MHz 830
< 1113MHz 840
< 1190MHz 850
< 1267MHz 860
< 1344MHz 870
< 1420MHz 880
< 1497MHz 890
< 1574MHz 900
< 1651MHz 910
< 1728MHz 920
< 1804MHz 930
< 1881MHz 940
< 1958MHz 950
< 2035MHz 960
< 2112MHz 975
< 2188MHz 990
< 2265MHz 1005
< 2342MHz 1020
< 2419MHz 1035
< 2457MHz 1040
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
Or You can download the profile in attachment and do the following:
1. Download the profile and extract it.
2. Go to your phone storage and look for a folder name tm_profiles
3. Paste it there.
4. Open the trickstermod app.
5. press at the top left and choose Tool.
6. You will find Global Profile. press restore and choose my profile Battery Test V2 pvs11 .
----------------------------------------------------------------------------------------------------------------------------------------------------------------
I hope you will test it guys and my aim is just battery light user no gaming.
Please feedback its just test if you more knowledge share as i already contacted the OP permission to open a profile thread.
@kykint
Undervolting source
http://forum.xda-developers.com/htc-one-m8/general/guide-snapdragon-801-clocking-voltage-t2807173
kardinal969 said:
Hi everyone ,
i would like to share my battery based profile.
I used Trickstermod kernel app taken from bbs dot sonyue dot com
( The kernel app is under attachment)
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
1. Install the app.
2. Open the app, at top left a list will open, Choose the General
3. Change the following
I/O Control:
Read Ahead Buffer Size 1024
Schedular fiops
CPU Frequency Control
Frequency Lock ON
Min 300000 (choose the lowest scroll to the top first)
Max 1574400
CPU Governor Control
Governor Conservativex
------------------------------------------------------------------------------------------------------------------------------------------
4. Now Choose Specific
Mp-Decision OFF
Intelli-Plug ON
Dynamic FSYNC ON
GPU Governor Powersave
GPU Max Frequency 240
Intelli-Thermal Control ..........> Intelli-Thermal ON
MPU Voltages
( I undervolted from Snapdragon 805 thread in xda)
< 300MHz 700
< 345MHz 710
< 422MHz 720
< 499MHz 730
< 576MHz 740
< 652MHz 750
< 729MHz 760
< 806MHz 770
< 883MHz 780
< 960MHz 820
< 1036MHz 830
< 1113MHz 840
< 1190MHz 850
< 1267MHz 860
< 1344MHz 870
< 1420MHz 880
< 1497MHz 890
< 1574MHz 900
< 1651MHz 910
< 1728MHz 920
< 1804MHz 930
< 1881MHz 940
< 1958MHz 950
< 2035MHz 960
< 2112MHz 975
< 2188MHz 990
< 2265MHz 1005
< 2342MHz 1020
< 2419MHz 1035
< 2457MHz 1040
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
Or You can download the profile in attachment and do the following:
1. Download the profile and extract it.
2. Go to your phone storage and look for a folder name tm_profiles
3. Paste it there.
4. Open the trickstermod app.
5. press at the top left and choose Tool.
6. You will find Global Profile. press restore and choose my profile Battery Test V2 pvs11 .
----------------------------------------------------------------------------------------------------------------------------------------------------------------
I hope you will test it guys and my aim is just battery light user no gaming.
Please feedback its just test if you more knowledge share as i already contacted the OP permission to open a profile thread.
@kykint
Undervolting source
http://forum.xda-developers.com/htc-one-m8/general/guide-snapdragon-801-clocking-voltage-t2807173
Click to expand...
Click to collapse
Good!
I'm following the Asian forum where I've found this kernel and related config app, from which I've read that there's a modified version of the app....And for this please give me some infos.
I'm also searching for some interesting custom rom as I see there are some, like the KingWolf one or the Milan one.
Any help on using this kernel with some roms?
Tnx!
Sent from my Samsung Galaxy S3 GT-i9300 using Tapatalk 4
PIRATA! said:
Can you do it also for KitKat if you have then?
Tnx.
Sent from my Samsung Galaxy S3 GT-i9300 using Tapatalk 4
Click to expand...
Click to collapse
I uploaded lollipop stock kernels for both recovery and odin. I'll upload for kitkat as well when I get the latest kitkat firmware.
Sorry, this might be a dumb question, but I'd rather ask it then brick my only smart-phone:
I'm currently on miscom's ROM (see here: http://forum.xda-developers.com/galaxy-s5/development/galaxy-s5-g906-custom-rom-t2848569)
Also using Philz recovery
How do I get to the Lolliwiz Kernel safely? Can I keep my apps, settings and so on?
Again, sorry. This is my first android phone (but certainly not the last one!) and I'm pretty clueless... But getting the miscom kernel on it was pretty easy with a bit of reading...
mcbrite said:
Sorry, this might be a dumb question, but I'd rather ask it then brick my only smart-phone:
I'm currently on miscom's ROM (see here: http://forum.xda-developers.com/galaxy-s5/development/galaxy-s5-g906-custom-rom-t2848569)
Also using Philz recovery
How do I get to the Lolliwiz Kernel safely? Can I keep my apps, settings and so on?
Again, sorry. This is my first android phone (but certainly not the last one!) and I'm pretty clueless... But getting the miscom kernel on it was pretty easy with a bit of reading...
Click to expand...
Click to collapse
Make a backup of whole apps with TitaniumBackup first, then backup system, data, boot in philz recovery(run custom backup) and flash stock lollipop through odin. miscom's rom is 4.4.2 as I know of, and my kernel supports 5.0.1 only at the moment.
If your phone bootloops after flashing lollipop, factory reset through philz and restore apps from TitaniumBackup, or flash back stock kitkat firmware and then restore system, data, boot in recovery.
Note that flashing stock firmware will blow away your recovery and you should manually install it again with odin. Also, factory reset through philz will preserve your internal sdcard but stock recovery WILL NOT.
kykint said:
Make a backup of whole apps with TitaniumBackup first, then backup system, data, boot in philz recovery(run custom backup) and flash stock lollipop through odin. miscom's rom is 4.4.2 as I know of, and my kernel supports 5.0.1 only at the moment.
If your phone bootloops after flashing lollipop, factory reset through philz and restore apps from TitaniumBackup, or flash back stock kitkat firmware and then restore system, data, boot in recovery.
Note that flashing stock firmware will blow away your recovery and you should manually install it again with odin. Also, factory reset through philz will preserve your internal sdcard but stock recovery WILL NOT.
Click to expand...
Click to collapse
Wait a minute!!! I though that factory reset in Philz recovery for G906 was not working and doing that would brick the phone!!!!!
I've read this in the info thread on the S5 G906 here on XDA!!!
Look under here in the Known issues:
prodigiez said:
.........
CWM
Unofficial PhilZ recovery is also available as below
Credit to hsk for unofficial CWM
updated : adb fix for cwm
Source: http://www.matcl.com/?m=bbs&bid=appDB&where=subject|tag&keyword=hsk&uid=231166
PhilZ Touch official thread http://forum.xda-developers.com/showthread.php?t=2201860
Download unofficial philz cwm here
This document is unofficial (Unofficial) ported version.
There may be bugs, so please use at your own risk.
Before flashing this, you must understand the contents of this post after you decide whether to apply please.
G906S/K/L = Tested working.
Flashing guide
Flash philz cwm with Odin as AP/PDA
Uncheck Auto Reboot and Start flashing.
Once completed , disconnect the USB cable and enter recovery manually by pressing the combination key.
Recovery time and date synchronization
PhilZ Settings - GUI Preferences - Time Setup - Change date and time - Qualcomm Time Daemon and (x) check - Yes Load Time Daemon
PhilZ Settings - GUI Preferences - Time Setup - Time Zone ( your preferred timezone )
Date / time will be synchronized with the system.
Reboot device.
Known issues:
KNOX Warranty 0x1
.
Wipe Data / Factory Reset from Clean to Install a New ROM feature is not working and might brick your device. Do not use this feature. If you brick your device , you may download the stock firmware from sammobile and flash it with ODIN.
CWM does not work with adb. CWM now works with ADB
CWM does not work with aromafm.
Credit to : XDA , PhilZ , hsk , bluecloud ,dougiebee and whoever involve. Tks
.......
Click to expand...
Click to collapse
Sent from my Samsung Galaxy S3 GT-i9300 using Tapatalk 4
Great.... Bricked it.... Gonna need you guys' help again....
Did it like instructed... After flashing stuck lollipop, stuck on the second boot logo ("olleh o" for me).
Since recovery went back to stock, tried a factory reset and cache delete from the stock recovery... no help....
UPDATE: HOLD THE HELP!!! Unbricked it! On Stock Lollipop now... Working on it... Will get back to you....