Related
WARNING KNOW WHAT YOU ARE DOING BEFORE ATTEMPTING THIS, IF YOU DON'T UNDERSTAND WHAT IS BEING TALKED ABOUT HERE YOUR BEST TO LEAVE IT ALONE
This is a Vibrant kernel/recovery image that includes EXT2/3/4 support as well as init.d support for user scripts. Everything works as expected Wifi/GPS/BT etc
This eliminates the race condition as the scripts in init.d run before the default Android services.
You can add any user scripts you want by adding them to the /system/etc/init.d folder e.g "05userscript" They are parsed by order 00 then 01 then 02 etc
BEFORE FLASHING THE KERNEL You must flash the init.d update to add the needed folder and files to boot with this kernel. That is because the completion script sets a prop value telling the default Android services to run. If that prop isn't set you will be sitting at the Vibrant screen forever.
The new init.d updates remove any other versions of busybox and install the correct version and symlinks to take care or the issues people have been having with multiple BB installs. There is a version that has no data to SD script for those that want to run other lag fix's. And then there is one with the data to SD script.
Default CPU frequencies and Overclocked versions available.
OCv4
Clock Drift fixed
Fix scaling bug, performance level was set past end of table on sleep
Scaling enhancement, selectable clock source for GPU
GPU clocked at 222MHz for all speeds except 100MHz, where it matches CPU clock
more up/down threshold changes
Wake Lag improvements
Switched back to "CFQ" for perf reasons over deadline and no-op
BB symlinks removed from ramdisk (to avoid conflict with mods that make their own links to BB)
OCv3
NO MORE WAKE LAG!!!!
Reverted back to OC on boot
up/down threshold adjustments again
rebuilt with crosstool-ng 1.8.0 gcc 4.3.4
OCv2
Extra steps are back. [100/200/400/600/800/1000/1200] YOU MUST use setCPU to up it to 1.2Ghz it is set at 1Ghz default for stability reasons,this CPU is very sensitive to voltage/freq changes. Should be more stable overall then prev build. (Thanks Unhelpful)
up/down threshold adjustments
SCv9
No More WAKE LAG!!
Uncommented FM Radio module in init.rc
SCv8
Conservative/Deadline
SCv7
Ondemand/Deadline are default now in
SCv6
ADB issue resolved.
Busybox issues resolved. Can now update through stericson's BB utility from the market.
OC version available with extra 600mhz and 1200mhz step added (you still have 800, 1000 etc) Linpacks in the 10.0's (Thanks to ivanmmj for the help)
SCv5
Volume rocker fixed
cleaned up RAMDISK
reverted to stock recovery (rev1 had clockwork as the recovery but was having a few issues)
added symlinks for busybox applets
Fully compatible with Clockwork (backups/restore from ROM manager) (no more annoying reboot before Clockwork starts)
INSTRUCTIONS
Note:The new init.d updates install BusyBox for you and create the symlinks. They also remove any other prior version before doing so
1.Choose one of the init.d updates that suites you.
A.
Data and Dalvik init.d-busybox with data to SD update.zip
MD5:0317ae432d2db15e51fd0da2c4d53857
B.
Data and Dalvik init.d-busybox without any lagfix scripts update.zip
MD5:9e720b587188676e7fff2f144433bd23
2.Reboot into recovery and flash this. Once booted check your system/etc dir for the init.d folder and scripts inside before moving forward. If they are there we move on.
3.Download the kernel/recovery image
OCv4 1.2 No Wake Lag/No Time drift
Update.zip (flash through clockwork recovery)
www.justanotherdev.slackdev.com/Kernel-Vibrant-OCv4.zip
MD5:33487d4bec50d123d0bb10843d141723
ODIN Image
www.justanotherdev.slackdev.com/kernel-vibrant-OCv4.tar
MD5:5aae7e5ab08227e1fd4c931c24f678ac
OCv3 1.2 No Wake Lag
kernel-vibrant-OCv3-NG.tar
MD5:1e2ddb9bd9fe4adb0ccc73fa818c63be
OCv2 1.2Ghz with extra steps back in. More aggressive up/down thresholds
kernel-vibrant-oc-ng.tar
BETA OC 1.2Ghz (no added steps for now)
kernel-vibext4-oc1.tar.md5
MD5:d1e26f769406c5d368492855c7b5059e
SCv9 No Wake Lag
kernel-vibrant-SCv9-NG.tar
MD5:0614a8205087a84fe34bbe2c653183a9
SCv8
kernel-vibext4-8.tar.md5
MD5:e9c2a45d89d994c485b8af8e1b1a923c
SCv7
kernel-vibext4-7.tar.md5
MD5:cedbad0273a2dd2a1b2d0a4ed3e89fce
4.Reboot into download mode and use ODIN to flash the kernel. Use the CSC field with no PIT file. This will flash the kernel/recovery
NOTE:You can find ODIN in my other thread here
If you have an EXT2/3/4 partition I used tabbals script (to tired and will be re-writing this shortly) for the mean time to bind your data to the EXT partition or otherwise known as the "EXT hack" for those that want those wondering. If you do not want this script you can remove the 07a2sd script from the init.d folder before flashing the kernel.
Now you can add any user scripts you like to the init.d folder and we dont need to use the "playlogos" hack anymore. This is a work in progress and more tweaks/features will be integrated and updated as they are tested and made available in this thread. I had to give you guys something to mess around with. And a proper way to run user scripts.
Thanks to Unhelpful, supercurio, cyanogen, scepterr, wes garner, Eugene_373 and everyone that helps out in the XDA community!
Sources:
Kernel: T959 source from opensource.samsung.com
Voodoo-fix http://github.com/project-voodoo
OC patch posted below
Enjoy!
Need to revert to the stock kernel??
www.justanotherdev.slackdev.com/kernel-vibrant-stock.tar.md5.tar
MD5:9f89f8c5a6c785ff967806a4ca70906f
Beautiful! now if only we can find a way to flash the kernel from recovery without needing odin.....
anomalous3 said:
Beautiful! now if only we can find a way to flash the kernel from recovery without needing odin.....
Click to expand...
Click to collapse
Agreed. Feel free to use this kernel/recovery in your ROMS just give credit and I'll be more than happy
Also more to come folks just sit tight. This is my hobby and I have to take care of some real life issue ATM...cough ...the woman...cough.
amazing job! thanks for helping calm down the xda addicts. how well does the userinit and apps2sd play with kernel, can we use those files or will they have to modified to work with your kernel?
frank707 said:
amazing job! thanks for helping calm down the xda addicts. how well does the userinit and apps2sd play with kernel, can we use those files or will they have to modified to work with your kernel?
Click to expand...
Click to collapse
Any scripts will work fine just as before. The main difference is that we dont need the "playlogo" hack that was used previously which runs a script called userinit from /system/bin/ now all user scripts will go in /system/etc/init.d/
Now we have this folder (init.d) to store all are user scripts in and gives us the option to choose which runs first according to how they are labeled. Just have a peek inside the init.d folder to see what I'm talking about. Init.d is pretty common on Linux boxes just not Android
Also to be clear this should clear up race conditions as any user scripts in init.d will run before the default Android services.
FYI tabbals scripts is renamed "/system/etc/init.d/07a2sd" (which I should have names d2sd but whatever lol) in this build. Same script so yes the scripts will work just fine
frank707 said:
amazing job! thanks for helping calm down the xda addicts. how well does the userinit and apps2sd play with kernel, can we use those files or will they have to modified to work with your kernel?
Click to expand...
Click to collapse
one of the main purposes of the kernel is to give us a linux-standard place for people to add startup scripts, and to make data2sd possible without trouble, including ext4 which combines most of the speed of ext2 with the stability of ext3.
anomalous3 said:
one of the main purposes of the kernel is to give us a linux-standard place for people to add startup scripts, and to make data2sd possible without trouble, including ext4 which combines most of the speed of ext2 with the stability of ext3.
Click to expand...
Click to collapse
Exactly.
Have fun I'm off to bed for now. I've been running this for 2 days without issues. Please let me know if you find any bugs. WiFi BT and everything else should be working just like the stock kernel I also haven't had one kernel panic yet.
justanothercrowd said:
FYI tabbals scripts is renamed "/system/etc/init.d/07a2sd" in this build. Same script so yes the scripts will work just fine
Click to expand...
Click to collapse
can't wait till take takes off. So is tabbal's script already setup to run automatically as long as i have my ext partition setup?
Im definately +1 for getting rid of odin, Jac do you use github at all ?
frank707 said:
can't wait till take takes off. So is tabbal's script already setup to run automatically as long as i have my ext partition setup?
Click to expand...
Click to collapse
This is correct yes.
bbuchacher said:
Im definately +1 for getting rid of odin, Jac do you use github at all ?
Click to expand...
Click to collapse
I use git/mercurial but not github. I will be creating an account their to share code as people have been requesting it
bbuchacher said:
Im definately +1 for getting rid of odin, Jac do you use github at all ?
Click to expand...
Click to collapse
good to see some Super D/E/F power using this phone. Would I be correct in thinking the main problem with packing the kernel into a boot.img would be the offsets, or do you think we're dealing with something a bit more serious?
Would I have to wipe if I flashed this kernal? Or can this be flashed on top of what I have now and not lose anything?
Goog1e Phone said:
Would I have to wipe if I flashed this kernal? Or can this be flashed on top of what I have now and not lose anything?
Click to expand...
Click to collapse
No Wipe is needed. Make sure you flash the update first though it is a REQUIRMENT for it to boot with this kernel.
justanothercrowd said:
No Wipe is needed. Make sure you flash the update first though it is a REQUIRMENT for it to boot with this kernel.
Click to expand...
Click to collapse
attempted to flash the first zip but init.d folder wasn't created. Wouldn't flash through stock recovery, attempted to flash through cw, will try again and update
The follow error occurs on flash
Code:
E:Can't chown/mod system/etc/init.d/02a2sd
(No such file or directory)
E:Failture at line 7:
set_perm 0 1000 0755 SYSTEM:etc/init.d/02a2sd
Installation aborted.
problem is in script, just edited it, about to try to flash
no dice, no install
davbran said:
no dice, no install
Click to expand...
Click to collapse
EDIT: realized my FTP client wasnt uploading in binary mode which caused some issues.
Re-download the files they have been hashed and double checked.
Enjoy!
I was trying to upgrade to CM6 from CM5 and was facing lot of issues so I followed below process and got it worked. I thought of sharing it with everybody as lot of person are having issues.
I know most of the information is available on XDA but not on a single place.
I have made a separate thread because A2sd and SWAP are not supported by CM6 officially.
This is not an official method of installing CM6, this is how I got it worked and you can use it for reference.
1) Preperation: You need to get the below mention files, Please get these files from below mentioned thread:
a) CM6 and Gaaps
b) CustomMTD Patch - You only need FR-recovery and FR-boot latest version.
c) Script for a2sd and swap - get the latest script.
d) Fastboot - Fastboot should be setup and working, If you are on Linux go here
e) SD Card Partition - If you are not sure how to partition the sd card. If you want to use a2sd and swap, please partition your sd-card.Store all files on root of sd-card.
2) Connect the phone to PC, do not mount the phone.
3) Wipe the phone:
a) Boot into recovery(reboot while holding home and power). Wipe everything.
b) Boot in fastboot mode. (reboot while holding back and power)
Enter the command in terminal or command prompt on the PC
fastboot erase system -w c) reboot into recovery.
4) Install the custom MTD. (If you already have custom MTD then this step is not required.)
a) Flash customMTD fr-recovery file.
b) Reboot into recovery.
5) Install CM6 Gapps and boot loader.
a) Flash CM6
b) Flash Gapps
c) Flash Boot Loader fr-boot file
d) reboot phone
6) Once phone is booted and you are on the home screen, go to
CyanogenMod Settings > Application Settings > Install location - Set Install location as Internal, make sure allow application moving is not checked.
CyanogenMod Settings > Performance Settings - make sure that Compcache, JIT, dithering is not checked. If something is checked please uncheck it.
Lock home in memory can be checked, but some guys has reported that it drains a lot of battery.
Reboot the phone.
7) Go to terminal type below code
su
sh /sdcard/fr-patch140.txt a2sd
It will ask if you want to install a2sd, type Y and press enter. Once APKManager is installed, type quit to exit.
Reboot the phone.
8) If you are not using a2sd and want to setup swap, please enter the below command in the terminal otherwise continue to step 9.
su
sh /sdcard/fr-patch140.txt sdext
reboot the phone.
9) Go to terminal type below code
su
sh /sdcard/fr-patch140.txt swap
It will ask for swappiness, I use 60 there, but its your own preference. After that it will ask you if you want to use swap-file, press n and enter.
After this enter below to terminal
FreeIf you get swap setup it will show in front of swap in terminal, if the result show zero swap then reboot and do the step 9 again.
Now you have a CM6 with apps2sd and swap. All the newly installed apps will automatically go to ext.
If you don't like 3d gallery and want it to replace it with old gallery..This has been provided by ZilverZurfarn on CM6 thread.
Extract Gallery.apk from a older CM update (like 5.0.8) somewhere (c:\temp in the example below)
Using adb:
adb remount
adb shell rm /system/app/Gallery3D.apk
adb push c:\temp\Gallery.apk /system/app/Gallery.apk
Also there are some apps which I don't prefer, as I don't use android native keyboard, Android browser, POP email, amazon MP3 etc. So I have created a script for my use which has been shared and it can be run from the terminal..
download remove-app-v1.0.txt and store it to root of your sd card. than enter below commands in terminal
su
sh /sdcard/remove-app-v1.0.txt
currently this script will remove below mention apps based on user input.
Amazon MP3, Live Wallpaper picker, CM Wallpapers, POP Email, Android Native Browser, Android Native Onscreen Keyboard, Genie Widget...
Note: - Before removing browser and keyboard please make sure you have a replacement for them.
I do not take any credit for work, its just a reference for installing CM6. Thanks to Cyanogen and team, Firerat, Lbcoder for producing these amazing roms and methods.....
Please provide your feedback and suggestion for the guide.
If you like my guide and want to Donate
Can I have swap without app2sd?
I skipped the app2sd part, but the swap wouldn't work.
it didn't ask me about the swap file.
It ended with:
use
/system/bin/swappy on # to turn swap on
supa2001 said:
Can I have swap without app2sd?
I skipped the app2sd part, but the swap wouldn't work.
it didn't ask me about the swap file.
It ended with:
use
/system/bin/swappy on # to turn swap on
Click to expand...
Click to collapse
Yes, swap can be there without A2sd..
Do you have Fr-Patch139.txt script or any other version...could you please reboot and so the step 8 again
I did it many times
Do I need to create some files like userinit ?
Thanks for replying.
supa2001 said:
I did it many times
Do I need to create some files like userinit ?
Thanks for replying.
Click to expand...
Click to collapse
Try below command:
sh /sdcard/fr-patch139.txt sdext
reboot the phone
sh /sdcard/fr-patch139.txt swap
If this doesn't work, could you please pass on the message you are getting from the script.
G1sanju said:
Try below command:
sh /sdcard/fr-patch139.txt sdext
reboot the phone
sh /sdcard/fr-patch139.txt swap
If this doesn't work, could you please pass on the message you are getting from the script.
Click to expand...
Click to collapse
It works now. Thanks.
What does sdext do ?
When I ran sdext, it said "danger detected" though, is it still safe?
Same thing appeared when I did swap.
G1sanju said:
I was trying to upgrade to CM6 from CM5 and was facing lot of issues so I followed below process and got it worked. I thought of sharing it with everybody as lot of person are having issues.
I know most of the information is available on XDA but not on a single place.
I have made a separate thread because A2sd and SWAP are not supported by CM6 officially.
This is not an official method of installing CM6, this is how I got it worked and you can use it for reference.
1) Preperation: You need to get the below mention files, Please get these files from below mentioned thread:
a) CM6 and Gaaps
b) CustomMTD Patch - You only need FR-recovery and FR-boot latest version.
c) Script for a2sd and swap - get the latest script.
d) Fastboot - Fastboot should be setup and working, If you are on Linux go here
d) SD Card Partition - If you are not sure how to partition the sd card. If you want to use a2sd and swap, please partition your sd-card.Store all files on root of sd-card.
2) Connect the phone to PC, do not mount the phone.
3) Wipe the phone:
a) Boot into recovery(reboot while holding home and power). Wipe everything.
b) Boot in fastboot mode. (reboot while holding back and power)
Enter the command in terminal or command prompt on the PC
fastboot erase system -w c) reboot into recovery.
4) Install the custom MTD. (If you already have custom MTD then this step is not required.)
a) Flash customMTD fr-recovery file.
b) Reboot into recovery.
5) Install CM6 Gapps and boot loader.
a) Flash CM6
b) Flash Gapps
c) Flash Boot Loader fr-boot file
d) reboot phone
6) Once phone is booted and you are on the home screen, go to
CyanogenMod Settings > Application Settings > Install location - Set Install location as Internal, make sure allow application moving is not checked.
CyanogenMod Settings > Performance Settings - make sure that Compcache, JIT, dithering is not checked. If something is checked please uncheck it.
Lock home in memory can be checked, but some guys has reported that it drains a lot of battery.
Reboot the phone.
7) Go to terminal type below code
su
sh /sdcard/fr-patch139.txt a2sd
It will ask if you want to install a2sd, type Y and press enter. Once APKManager is installed, type quit to exit.
Reboot the phone.
8) Go to terminal type below code
su
sh /sdcard/fr-patch139.txt swap
It will ask for swappiness, I use 60 there, but its your own preference. After that it will ask you if you want to use swap-file, press n and enter.
After this enter below to terminal
FreeIf you get swap setup it will show in front of swap in terminal, if the result show zero swap then reboot and do the step 8 again.
Now you have a CM6 with apps2sd and swap. All the newly installed apps will automatically go to ext.
If you don't like 3d gallery and want it to replace it with old gallery..This has been provided by ZilverZurfarn on CM6 thread.
Extract Gallery.apk from a older CM update (like 5.0.8) somewhere (c:\temp in the example below)
Using adb:
adb remount
adb shell rm /system/app/Gallery3D.apk
adb push c:\temp\Gallery.apk /system/app/Gallery.apkI do not take any credit for work, its just a reference for installing CM6. Thanks to Cyanogen and team, Firerat for producing these amazing roms and methods.....
Please provide your feedback and suggestion for the guide.
Click to expand...
Click to collapse
Thanks mate this will really help me to put my apps on SDcard..as past days m really trying to get my phone memory safe...
supa2001 said:
It works now. Thanks.
What does sdext do ?
When I ran sdext, it said "danger detected" though, is it still safe?
Same thing appeared when I did swap.
Click to expand...
Click to collapse
"danger detected" message is for SPL, It checks for the SPL first and you have danger spl installed.
By default CM6 does not mount ext partition as it does not support a2sd right now. sdext creates a mount point for ext partition. a2sd internally does that but as you are not using a2sd this was not done.
vermaekansh said:
Thanks mate this will really help me to put my apps on SDcard..as past days m really trying to get my phone memory safe...
Click to expand...
Click to collapse
Thanks, If you use this guide then please provide your feedback and suggestion towards it.
Sorry, but is there a script to disable swap? I am gonna do some test to see what works best.
Thanks.
supa2001 said:
Sorry, but is there a script to disable swap? I am gonna do some test to see what works best.
Thanks.
Click to expand...
Click to collapse
In the terminal
sh /sdcard/fr-patch139.txt rev swap
this will turn the swap off.
Watch out...newbie in the room
Okay, you are going to love this.... I'm sorry if this is too long but I hope you can help a newbie trying to learn this stuff!
I am REALLY new to all this, and did a Root and Rom Update as the Unlockr.com videos taught me, to get CM6. And then also added the gapps file because I read a thread that that was needed to get gmail and the market on my phone. Once rebooted, everything worked ok but slow. Then I noticed that my gmail wasn't syncing, and then it started to force close. So I did a wipe and loaded CM5 because I saw on a thread that that was faster for the G1. With all of this, after reading your thread and suggestion, I am wondering...
1. Is CM6 slow for you?
2. Should I have loaded gapps? IS that how to get gmail and should it sync automatically? If not, is there a way to make it?
3. Should I stick with CM5 or try CM6 following these suggestions??
And big ones.... I wish there was a website somewhere with definitions to all the terms and apps used. Lol.. I Google all of them but don't always find anything that actually describes what they are.
Swap and app2sd were mentioned on the video instructions for loading a new ROM but do they automatically come in the ROM zip files? Because in the video they didn't load them separately. They partition the card "for" them, but don't show installing them. Obviously I assume App2sd is a program to store your apps on your sd card. Is this something that I SHOULD install? Is swap something I should install?
And what is a CustomMTD Patch? Annnnnnd, what is fastboot??
I know this is a lot of questions... I decided to ask them all here because they pertain to this thread because I'm wondering if I should do this...
Thanks for any and all answers!
I would assume that you have a G1, and my answer is based on that assumption. If you have different phone let me know.
1. Is CM6 slow for you?
If I don't use a2sd and swap, answer is yes. I install lot of apps, with cutomMTD it works fine in starts but slows down after some time. With a2sd and swap it is worth a try.
2. Should I have loaded gapps? IS that how to get gmail and should it sync automatically? If not, is there a way to make it?
CM roms does not distribute google apps with the rom as its not legal. So if you want gapps then yes that file has to be flashed. CM6 can be run without gapps, but you won't get gmail, market etc..once you have gmail it should sync automatically.
3. Should I stick with CM5 or try CM6 following these suggestions??
CM5 is quite stable rom and runs fine. Choice is yours...CM6 is in initial stages, but is good too...I go with CM5 for my daily driver as a2sd is not officially supported. It will be there in CM6.1....
And what is a CustomMTD Patch? Annnnnnd, what is fastboot??
G1 was build with a low memory and the way internal memory has been partition todays rom can't fit into it. That's why dangerSPL, but there is a risk involved in installing dangerSPL. If you don't follow the instruction you can brick your phone. CustomMTD is a safe method. This increase the size of data partition so you can install more apps internally. link for that thread is in first post.
a2sd is a way to store apps on sdcard, sdcard needs to be partitioned to support that..step 1 - e in my guide. That's a manual way of doing it. If you have AmanRA recovery then it will have a menu option for that. Most of the rom supports it automatically, so if you have sd card partition then rom will automatically do that.
CM6 does not support a2sd so it has to done in different way. CM5 supports it but in settings - application - a2sd has to be checked on to move your apps to sdcard.
Swap is kind of extra memory to help running the applications. if you run multiple application together then you need swap on CM5 and CM6.
G1sanju said:
CM5 is quite stable rom and runs fine. Choice is yours...CM6 is in initial stages, but is good too...I go with CM5 for my daily driver as a2sd is not officially supported. It will be there in CM6.1....
Click to expand...
Click to collapse
So when CM6.1 is comming out for G1..do you have nay idea about HCTCLAY's ROM over CM6
vermaekansh said:
So when CM6.1 is comming out for G1..do you have nay idea about HCTCLAY's ROM over CM6
Click to expand...
Click to collapse
Nope I don't follow htcclay but it is based on CM so should be updated
Sent from my HTC Dream using XDA App
G1sanju said:
Nope I don't follow htcclay but it is based on CM so should be updated
Sent from my HTC Dream using XDA App
Click to expand...
Click to collapse
No hard feeling for CM but for me htcclay's ROM's are more stable than CM's.....any release date for CM6.1 for G1?
vermaekansh said:
No hard feeling for CM but for me htcclay's ROM's are more stable than CM's.....any release date for CM6.1 for G1?
Click to expand...
Click to collapse
Roms are personal preferences, I also tried lot of roms before settling on CM... and for CM there are no eta it will be released when it's done...
Sent from my HTC Dream using XDA App
WOW!
THANK YOU!!! You are awesome for going through all of those!
Yes, it is a G1.
Are there any features in CM6 that aren't in CM5, or is it faster than CM5 with the ap2sd & swap?
I believe I partitioned the sd card when I loaded the CM6 ROM.
So I'd like to try the CM6 with the ap2sd, swap and the CustomMTD. I do have the AmanRA recovery, but not sure about how to select the ap2sd.
Any chance you would tell me how to get the ap2sd, swap and CustomMTD on the phone if I have already Flashed CM6 on there?
Thanks again, regardless. The info you gave me helped me learn a little more. I'm still a bit confused about what fastboot is though. But I will just keep at it and keep learning!
Are there any features in CM6 that aren't in CM5, or is it faster than CM5 with the ap2sd & swap?
CM6 is based on froyo, latest version of android...its good and yes speed is comparable. Also CM has added new stuff in it, like fully customizable power bar and other stuff...Full changelog is there in CM6 thread.
I believe I partitioned the sd card when I loaded the CM6 ROM.
So I'd like to try the CM6 with the ap2sd, swap and the CustomMTD. I do have the AmanRA recovery, but not sure about how to select the ap2sd.
For CM6 a2sd is through script, instruction is in first post. I have included customMTD also there. So if you follow the guide, you will be having customMTD, a2sd and swap...swap require an partition on your sdcard, if you don't have that partition then it will ask for swap file.
Any chance you would tell me how to get the ap2sd, swap and CustomMTD on the phone if I have already Flashed CM6 on there?
you can wipe and start over again, first post should be good for you.
Thanks again, regardless. The info you gave me helped me learn a little more. I'm still a bit confused about what fastboot is though. But I will just keep at it and keep learning!
Oh I forgot about the fastboot, fastboot and adb are tool, which give an option to control, flash and do other thing on the phone from PC. The link for setup guide is in first post.
Thanks again!!
Man! You are great! Thanks again for all your help! Now let's see if I can manage to follow your thread and not brick my phone! Lol
Until next time....
Onyx is simply a TouchWiz Free version of Obsidian. The changelog is listed there, in addition to those changes the following have been made.
Will make flashable nonwiping updates available until all the bugs are worked out and cleared. Once they are the newer and stable revision will be posted with complete skinning in two seperate versions. Please make requests for feature changes and things you would like removed.
4.2
- Added inharent support for Backlight Notification compatible kernels (BLN)
- Optimized Build Prop with ROM Identification Added
- Streamlined Frameworks
- Numerous Corrected Images
- Return of TouchWiz MMS w/ Blurry mms Fix
- Integrated WirelessADB
- Additional I/O scheduler, VM management, kernel scheduler, and minfree edits via sombionixInit script
- Integrated Flashing with Universal Lag Fix system. (Source by sztupy @ XDA, Ported by Krylon360 @ TeamWhiskey)
Team Whiskey Universal LagFix Kernel Features
- All lagfixes and tweaks activated directly within clockwork advanced menu
- MULTIPLE lagfix options, new and old
- Integrated TW logo
- 3e recovery built into kernel
- No longer required to disable lagfixes before flashing
- Enable/disable back light notifications
- Option to switch to 2e recovery
- Option to install Superuser
- Enable/disable I/O scheduler tweaks
- Enable/disable VM management tweaks
- Enable/disable kernel scheduler tweaks
- Enable/disable misc. tweaks
- Reboot into download mode
How To Utilize Universal LagFix Kernel:
1. Flash ROM as you normally would via clockwork recovery
2. Let device boot and then reboot back into clockwork recovery
3. Once in recovery, you will now see 2 new options at the bottom
4. Within the new menus, you will find options to enable/disable certain features and an assortment of lagfixes
5. Enabling/disabling features and tweaks are fairly self explanatory, so have fun with those.
6. Lagfixes are also fairly simple, however, if you are not extremely familiar with them, I suggest sticking to what you know such as the OCLF or voodoo options
7. Once you select the lagfix you want, you will see that your current configuration is updated. You must then go back and select reboot.
8. It will kick you back into clockwork very quickly and give you options before converting your partitions to your selected lagfix. I suggest you pick the first one which creates a backup and restore of your system.
9. Your device will now convert your partition, reboot your phone, and you're done!
Known Issues:
PLEASE READ PLEASE READ PLEASE READ PLEASE READ
- Currently, there is a VERY small percentage of users who have reported that their internal sd partition has been wiped. This is happening to roughly 1/20 people who flash 4.2 with the universal lag fix. If this happens, you will have to odin back to JFD and then upgrade back to 4.2 or any version of your choice. The kernel works very well, however, this is the first time this source and recovery modding has been ported to the Vibrant. None of my dev team has had this happen to any of us so we unfortunately cannot reproduce the problem and pinpoint the problem. We are thinking its hardware related at the moment. Please flash this at your own risk. If it does work for you, you'll love it, trust me! If you're one of the unfortunate ones that gets your internal wiped, well, I apologize, but you've been warned. I suggest ONLY experienced users download the rom with the ULF included. All others should download 4.2 w/stock kernel. THIS IS A KERNEL RELATED ISSUE, NOT ROM RELATED!
Update:
For those VERY VERY few unfortunate people who get their internal sdcard partition wiped, we have confirmation that using odin, going back to JFD, then back to Obsidian/Onyx 4.2 works fine. Everyone that has done this has had no further issues regarding the wipe issue.
3.1
-Even MORE framework edits
-tamed dragons
-now prints money
3.0
-Additional Framework Edits
-Beginning of a complete graphical overhaul
-Reskinned DialerTab Functions
2.2
-Fixes Mounting
2.1
-Corrected several improper strings
-Repaired twframework and framework
-removed power menu
R2.1 fixes a few issues, random dropping into airplane mode, crash when using the power button, repeat mms notifications, and more.
2.0
-TouchWiz Disabled and removed
-Standard LauncherPro installation w/ Fusion Skinning
-Reskinned to include Onyx button bar and status bar
All the other changes that were listed in R1 in beta were combined with Obsidian to make one big pile of awesome.
Reverting back to previous iteration, it was running clean and bugfree. Does not have the same stability previous Rev did. Took those peices and reintegrated into R2+
Removed some edits, much more stable now. I KNOW How you hate flashing updates, I promise I will try to make this the last major flashing update for a very long time. Its stable and perfect as far as I can see other than the known mounting issue. Enjoy!
Additional Option Flashes:
If you REALLY like the samsung apps I removed flash this - http://teamwhiskey.com/bin/onyx/FlashPa ... gExtra.zip
If you REALLY liked the WiFi calling and need it back, even if it slows your phone down, constantly, even in the background - http://teamwhiskey.com/bin/onyx/FlashPa ... alling.zip
OCLF/Voodoo Displaced, not removed.
To enable your new box of awesome, you will first need to reboot back into recovery. You will notice this is slightly different from your standard recovery. I will keep this as brief as I can and to the point. You can do any combination you want of lagfix, from simple bind to overkill mode and replace the entire FS to JFS + EXT2 Binds. This is totally at your discretion.
Personally, I enabled EVERYTHING and activated the most OVERKILL mode I could, because I like things over the top lol.
Its fast, wicked fast, its like fast took meth and kicked not so fast in the face in a single springboard motion to be faster.
Reboot to Recovery
Go to the Advanced menu below CWM
Set tweaks and options as you want to, I turned on Backlight Notifications and all the tweaks personally
After that, go to the LAGFIX section and shop for your weapon of choice, pick whichever you want. (Understand that converting data is a dragon in disguise, like a shoplifter in a cage inside an ATM that he COULD BREAK FREE from. Use at your own discretion.)
Reboot
Allow it to convert, could take a long time. Get a snack. Watch Hulu.
Once it boots, its done, reboot after about 15 or 20 for good measure and extra flavor.
Restore your data, dont restore EVERYTHING from Titanium Backup if youre coming from an Eclair build, single select restore your apps and their data. Otherwise Titanium Backup tries to make you some Froyeclair in a blender.
Backlight notifications are awesome, use them.
IF YOU ARE A BATTERY MONGER AND HATE IF YOUR BATTERY DOESNT LAST FOURTYSEVENTYTEEN Hours. Flash the stock kernel, otherwise you will get an average of 10-14 hours with this kernel.
Download:
Onyx 4.2 w/stock kernel
ULF Removed for Stability Issues in flashing
If you are one of the ones that had serious issues with ULF properly flashing we are very sorry that you are having those issues. We have pulled the ULF kernel due to its inconsistant flashing and are moving forwards with a few different concepts. If you are still having issues with this kernel and going back to normal please visit Sombionix or Viralblack in the TeamWhiskey IRC channel.
NEW internal/external mounting fix - after flashing, reboot phone and computer
Download Rom Extras:
Rom Extras
Thank you, this Rom rocks!!!!
Question: The USB debug mode enables itself everything the phone reboots. Is it supposed to be this way?
Thanks again for a awesome rom
Wait 10-14 hours of battery with this kernel? i know the features are awesome but that seems pretty bad. is that 10-14 hours with normal use or just chilling? cause moderate to heavy use and 12 hours doesnt seem so bad.
Awesome rom. Love it as usual.
I was one of the unfortune that got their SD wiped, but I made a bakup.
I flashed froyo via Odin, then reflashed Onyx v4. Works like awesome sause.
Not sure what caused this, Onyx or the overkill JS lagfix, but when I mount my internal/external sd card, the external shows up as a cdrom drive. The internal one is fine.
Can you please make a version with stock kernel
Sent from my SGH-T959 using XDA App
theres a version for stock on the TW website. It was there when i downloaded this at 803 am EST
whats up with this new stuff? i selected the very bottom option in the tweaks for the JS overkill? is this JFS thing the new hotness? i dunno which to pick. i want this thing to be as epicly cracked out as i can make it. can you doo voodoo WITH this new thing or is it one or the other?
right now im sitting at 1406 quadrant and all i did was select that option
aeok18109 said:
theres a version for stock on the TW website. It was there when i downloaded this at 803 am EST
Click to expand...
Click to collapse
Correct, their website shows:
"SECOND FLASHABLE STOCK KERNEL, use if you dont want to risk dragons."
aeok18109 said:
theres a version for stock on the TW website. It was there when i downloaded this at 803 am EST
whats up with this new stuff? i selected the very bottom option in the tweaks for the JS overkill? is this JFS thing the new hotness? i dunno which to pick. i want this thing to be as epicly cracked out as i can make it. can you doo voodoo WITH this new thing or is it one or the other?
right now im sitting at 1406 quadrant and all i did was select that option
Click to expand...
Click to collapse
W/ voodoo it's either one or the other.
JFS = Journaled File System or JFS is a 64-bit journaling filesystem created by IBM.
RFS = Remote file sharing - essentially this is what Samsung originally went with and it's slow.
Viralblack said:
OCLF/Voodoo Displaced, not removed.
To enable your new box of awesome, you will first need to reboot back into recovery. You will notice this is slightly different from your standard recovery. I will keep this as brief as I can and to the point. You can do any combination you want of lagfix, from simple bind to overkill mode and replace the entire FS to JFS + EXT2 Binds. This is totally at your discretion.
Personally, I enabled EVERYTHING and activated the most OVERKILL mode I could, because I like things over the top lol.
Its fast, wicked fast, its like fast took meth and kicked not so fast in the face in a single springboard motion to be faster.
Click to expand...
Click to collapse
Quadrant scores aren't everything, if it feels fast, looks fast. It's fast.
oh yea i know. i personally could give a rats dong about Quadrant scores. This thing is pretty fast. i just posted it for reference. you know SOMEONE is gonna ask lol
Awesome, this is legit, had It since yesterday!
Sent from the speed demon
Okay, I was running the Macnut ROM (Eugene's ROM) and, having tried Onyx from the first beta, I decided to go back. I installed from CWM with no issues (no Internal SD wipe, etc.), let it sit for a bit then went into recovery to do the ULF. I didn't know what to choose but, I ain't afraid o' no ****in' dragons so, I chose the bottom most option for the works. After letting it sit for about 15 mins again and a Titanium restore of my apps, this thing screams. After a fresh reboot, I got 1852 on Quadrant and there is absolutely no lag on this thing. NONE. The only slight beef I have with this rom is that I miss the completely black Swype keyboard.
Stock Kernel
I am aware of the stock kernel on the TW forum, but it says both the R4 zip and the Stock Kernel zip need to be flashed "at the SAME TIME"
How do I flash two *.zip files at the "same time"?
Thanks.
1. How do you use the WirelessADB??
2. What is Backlight Notifications?
miikey_ said:
I am aware of the stock kernel on the TW forum, but it says both the R4 zip and the Stock Kernel zip need to be flashed "at the SAME TIME"
How do I flash two *.zip files at the "same time"?
Thanks.
Click to expand...
Click to collapse
it means flash the R4 zip in CWM, then flash the stock kernel in CWM WITHOUT REBOOTING IN BETWEEN.
fearless1964 said:
1. How do you use the WirelessADB??
2. What is Backlight Notifications?
Click to expand...
Click to collapse
it makes the 4 android keys at the bottom light up when you have notifications... awesome for those of us who came from phones like the Nexus One that had a notification LED and miss it like woah
miikey_ said:
I am aware of the stock kernel on the TW forum, but it says both the R4 zip and the Stock Kernel zip need to be flashed "at the SAME TIME"
How do I flash two *.zip files at the "same time"?
Thanks.
Click to expand...
Click to collapse
flash one, then flash the kernel right after before rebooting into the rom for the first time. My issue is the stock kernel dl link is dead =\
miikey_ said:
I am aware of the stock kernel on the TW forum, but it says both the R4 zip and the Stock Kernel zip need to be flashed "at the SAME TIME"
How do I flash two *.zip files at the "same time"?
Thanks.
Click to expand...
Click to collapse
flash the R4 zip then flash the stock kernel without booting the device in between
rsfaze said:
flash one, then flash the kernel right after before rebooting into the rom for the first time. My issue is the stock kernel dl link is dead =\
Click to expand...
Click to collapse
Here it is. One stock Kernel, enjoy.
how do u use WirelessADB???
fearless1964 said:
how do u use WirelessADB???
Click to expand...
Click to collapse
ADB functions without a wire (USB cable)
Hi guys I decided to flash a new rom minicm7 and flash its latest kernel naa 13.
A couple of problems:
MY rom is minicm7 with naa latest version 13.
1.when I open the menu to access all my applications the scrolling feels laggy and if I were to scroll in settings file manager or anything else it's smooth any reason why?
2.Secondly which kernel suits you better for this rom (minicm7): Alfs? or NAa?
(I don't want comments like 'see for yourself' this question is based on your OWN invaluable experience)
3. for alfs 8acm7 i'm considering on seeing if it will workout for my device or not (minicm7). Before I do that:
Do I also need to flash chargemon on top of that? and does the flashing of chargemon straight after you flash any version of alfs kernel (except for the ones that already have it attached) apply to any rom regardless as well?
If so which chargemon do I flash? the v2 with the 17k downloads? (sorry im derping out)
4.Do I also need to flash anything else for naa just like how there was an extra file to flash for alfs?
5. I also installed tweaks 3 tweaks such as adre boost, odex, and e15 optimizer. Will these tweaks vanish if I flash a new rom + kernel?
6. Do you keep ANYTHING if you flash a new rom or kernel?
7. Do you lose anything of any sort if you flash a kernel?
8. How do you guys get such high scores in benchmark tests?
I have the same thing as a lot of people do but they seem to get 200 or even 300 higher. Could it because my sd card is filled with anime and music leaving only 5 - 6 gigs / 16gigs ?
I usually went by the rule of flashing 2.1.1.0 and rerooting my device and doing everything again just to stay safe
I don't know if these questions might be derp or not but I don't care please answer by putting a number first I really need answers.
Thank you once again
From my experience and opinion: (Please correct me if I'm wrong...)
1. IDK... BTW Is your MiniCM7 2.2.1 or Nightlies? Have your tried rebooting once or twice? Because mine was smooth...
2. nAa because it is more stable. They also said that the performance is faster with Alfs but I don't like FPS caps problem (Higher chance to get screen cut otherwise laggy scrolling visually)...
3. IDK... I haven't tested it...
4. No...
5. Most likely because you'll need to full wipe before installing a ROM (not kernel)...
6. Anything unless it requires to full wipe...
7. Yes... I think it overwrites some system apps and even some user apps and user data might be corrupted... (maybe when doing cross flashing of ROMs)
8. Overclock (The most effective and dangerous way), Supercharger (I think AutoKiller Memory Optimizer is the same), Swap (different partition), Adrenalines, Odex and et cetera...
Lily48 said:
From my experience and opinion: (Please correct me if I'm wrong...)
1. IDK... BTW Is your MiniCM7 2.2.1 or Nightlies? Have your tried rebooting once or twice? Because mine was smooth...
2. nAa because it is more stable. They also said that the performance is faster with Alfs but I don't like FPS caps problem (Higher chance to get screen cut otherwise laggy scrolling visually)...
3. IDK... I haven't tested it...
4. No...
5. Most likely because you'll need to full wipe before installing a ROM (not kernel)...
6. Anything unless it requires to full wipe...
7. Yes... I think it overwrites some system apps and even some user apps and user data might be corrupted... (maybe when doing cross flashing of ROMs)
8. Overclock (The most effective and dangerous way), Supercharger (I think AutoKiller Memory Optimizer is the same), Swap (different partition), Adrenalines, Odex and et cetera...
Click to expand...
Click to collapse
Hi there thanks a lot for your help and I am using minicm 2.2.1. And how do you swap different partion?
Ftwisawesome said:
Hi there thanks a lot for your help and I am using minicm 2.2.1. And how do you swap different partion?
Click to expand...
Click to collapse
You can use the recovery for creating SWAP but with Ext though...
[Ext is another partition for user apps and it's advantage is that you can use the apps on the partition while the sd is mounted on PC]
1. Back up everything on SD because it will be formatted...
2. Enter Recovery -> advanced -> Partition SD Card
3. Choose you Ext size -> Choose 128M Swap size... they said 256M is not recommended...
4. Reboot -> Terminal -> su (if required) -> free -> DONE!
If you want to use Ext, you may install Link2SD -> Choose Ext4 -> Reboot -> Launch Link2SD -> Start linking... DONE!... (Warning: sometimes it breaks app when the annoying error comes (I forgot))... I think you can also use the CyanogenMOD -> Performance -> A2SD (ext) but IDK how to use it...
See also Tips & Tricks To Increase Our Phone's Speed
Wow thanks!
So do I need to do this before I swap?
because when I dled swapper and swapped I ran free it was working fine but I felt no ingame improvment in anyway.
SO all I have to do is the above then swap and im good to go?
Ftwisawesome said:
Wow thanks!
So do I need to do this before I swap?
because when I dled swapper and swapped I ran free it was working fine but I felt no ingame improvment in anyway.
SO all I have to do is the above then swap and im good to go?
Click to expand...
Click to collapse
Swap is already done after partitioning... it's ready after reboot... the terminal is only used to check if it is mounted...
Only the Ext needs setup...
PS: I tried GingerDX and all Dalvik-Cache files went to the Ext without any setup ... Swapper makes mounting SD to PC very SLOW... SWAP Partition doesn't work with MiniCM9 3.0.2 but working on IScreamDX v004...
Ftwisawesome, learn to use the search function, most answers to your questions can be found when you show a little initiative.
NEXT 2.1.8 placeholder: http://forum.xda-developers.com/showpost.php?p=51678768&postcount=2513
STOP! This kernel supports ONLY Samsung Jelly Bean 4.1.x, 4.2.2, CM 10.1.x, 10.2, and 11.0. It won't work on ICS, CM 9, CM 10.
FOR NOW I FORBID ANYONE ELSE REUSE THIS STILL IN DEVELOPMENT DUAL BOOT PROJECT FOR HIS/HER OWN GALAXY TAB 2 PROJECT!
STOP PRESS:
NEXT 2.x separated in two package: the kernel part as blackhawk-next-kernel-2.x-p31xx.zip and the proprietary binaries part as proprietary-vendor-samsung.zip for JB >= 4.2 and proprietary-vendor-samsung-4.1.x.zip for JB 4.1.x .
Flash the kernel part first and then directly the proprietary binaries part! Flash the appropriate proprietary part on both 1st and 2nd ROM!
Sources:
Kernel sources at http://github.com/kumajaya/android_kernel_samsung_espresso10/tree/cm-10.2-update
Features:
Samsung stock 4.1.x, 4.2.2 (since 1.8), CM 10.1.x and CM 10.2 (since 1.7) support with a single kernel image
For stock ROM: external SD card - internal media swapper script included
Samsung proprietary exFAT modules are loaded. CM 10.1 exFAT support files attached at post #2
For CM/CM based ROM: auto rotate screen default orientation depend on ro.sf.hwrotation value, camera orientation fix included
Dual-booting. You can have Samsung JB and CM 10.1 ROMs on a single device at the same time.
Nice looking AROMA based boot menu
Using CyanogenMod kernel source, updated to p3110 source for newer WLAN (Youtube HD bugfix on stock ROM), modem, sensors driver, and etc for both P31xx and P51xx target
CPU clock: 300MHz, 600MHz, 800MHz, 1.008GHz, 1.2GHz, 1.35GHz, 1.42GHz, 1.48GHz, and 1.52GHz, locked @ 1.008GHz on boot
GPU clock: 153.6MHz, 307.2MHz, 384MHz, and 512MHz, 307.2MHz as the default maximum clock
CPU voltage control. You can use Android Tuner/System Tuner/Trickster MOD to set CPU voltage
The ramdisk base on JB 4.1.2 (stock ROM) and JB 4.2.2 (CM 10.1)
Using newer PowerVR SGX 540 kernel modules and binaries blob
row, bfq, sio, and vr scheduler support
Governor bug fix. Replace Samsung's interactive governor with default OMAP4 3.0.31 interactive governor from omapzoom.org, plus pegasusq and lulzactive
NFS and CIFS/samba (not loaded by default) filesystem support
LZMA compressed initrd, to keep boot image smaller than 8MB
swap support. zram and cleancache with a working zcache driver, enabled by default
kernel config, insmod configs.ko and then you can access /proc/config.gz
external modem support, for PPP Widget (not loaded by default, P31xx need powered USB hub for external modem)
Some tweaks from gokhanmoral's siyahkernel for S3, passive entropy tweak applied
Remove a lot of debug message from touchscreen driver, display, mmc, modem, etc
linaro arm-linux-gnueabihf- cross compiler, compiler optimization applied
SuperSU v1.41 for stock ROM
Self compiled BusyBox v1.22.0-git in /sbin, config file based on CM's BusyBox bbconfig output. fstrim applet patch applied, android_reboot applet added (a quick but clean port from Android toolbox), swapon applet with priority option. For stock ROM: this version of Busybox will overwrite busybox binary in /system/bin or /system/xbin and save it as busybox.backup
Early boot scripts support (/system/etc/init.d, /data/local/userinit.sh, and /data/local/userinit.d)
Post boot script support (/system/etc/init.post_boot.sh)
For stock ROM: custom boot animation support (/data/local/bootanimation.zip or /system/media/bootanimation.zip if exists, Samsung boot animation as a fallback). If a bootanimation.zip found, the boot sound will be turned off as well as the shutdown animation.
Modified mount options
adb insecure, adb mode in charge state also insecure
Advanced TCP congestion support, westwood as the default congestion
No /system/etc/hosts patch, you can install AdAway from F-Droid
Known Problems:
Thanks To:
gokhanmoral, amarullz, Phil3759, Chainfire, cmenard, codeworkx, imoseyon, coolbho3k, Faux123, AuxLV, CodyF86, poppolo2001
This part will be expanded. Most of the patches I applied are coded by someone else. Please remind me if I forget to give credits to anybody...
Downloads:
PhilZ Touch 5.08.5: http://forum.xda-developers.com/showthread.php?t=2202667
Todo:
More features in NEXT tool
Special Thanks:
@trssho91, @Caldair, @fast96, @Jellydroidkin, @Android-Andi, @nakbaliNe, @Bhaskara Rao, @tsatomas
Downloads Record:
blackhawk-next-kernel-1.0-p31xx.zip: 316
blackhawk-next-kernel-1.1-p31xx.zip: 87
blackhawk-next-kernel-1.1-addon-nooc-p31xx.zip: 41
blackhawk-next-kernel-1.2-p31xx.zip: 503
blackhawk-next-kernel-1.2-addon-nooc-p31xx.zip: 160
blackhawk-next-kernel-1.3-p31xx.zip: 240
blackhawk-next-kernel-1.3-addon-nooc-p31xx.zip: 112
blackhawk-next-kernel-1.4-p31xx.zip: 583
blackhawk-next-kernel-1.4-nooc-p31xx.zip: 294
blackhawk-next-kernel-1.6-p31xx.zip: 380
blackhawk-next-kernel-1.6-nooc-p31xx.zip: 227
blackhawk-next-kernel-1.6.1-p31xx.zip: 180
blackhawk-next-kernel-1.6.1-nooc-p31xx.zip: 90
blackhawk-next-kernel-1.6.2-p31xx.zip: 151
blackhawk-next-kernel-1.6.2-nooc-p31xx.zip: 81
blackhawk-next-kernel-1.5-p31xx.zip: 600
blackhawk-next-kernel-1.5-nooc-p31xx.zip: 304
blackhawk-next-kernel-1.8.1-p31xx.zip: 222
blackhawk-next-kernel-1.8.1-nooc-p31xx.zip: 99
blackhawk-next-kernel-1.8.2-p31xx.zip: 577
blackhawk-next-kernel-1.8.2-nooc-p31xx.zip 321
XDA:DevDB Information
[KERNEL][SINGLE/DUAL][JB/KK][STOCK/CM]blackhawk's NEXT kernel, Kernel for the Samsung Galaxy Tab 2
Contributors
ketut.kumajaya, Android-Andi
Kernel Special Features: Dual boot stock and AOSP based ROM
Version Information
Status: Stable
Current Stable Version: 2.3
Created 2014-09-21
Last Updated 2014-10-11
NEXT 2.x separated in two package: the kernel part as blackhawk-next-kernel-2.x-p31xx.zip and the proprietary binaries part as proprietary-vendor-samsung.zip for JB >= 4.2 and proprietary-vendor-samsung-4.1.x.zip for JB 4.1.x .
Changelog:
21/04/2014 2.2:
Flash-Friendly File System (f2fs) support
Full github commits 8/4 - 20/4/2014: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-11.0
Update proprietary blobs, proprietary-vendor-samsung-update.zip
02/01/2014 2.1.5 -> 2.1.6:
CM 11.0 support
28/10/2013 2.1.4 -> 2.1.5:
Updated to upstream 3.0.101 kernel
Audit and SELinux enabled
Smartreflex completely disabled
GPU frequencies not exposed to STweaks bug fixed
Do not load exFAT modules on CM 10.2
Full changelog: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.2-update
27/10/2013 2.1.3 -> 2.1.4:
Ramdisk updated to sync with latest CM 10.2
20/10/2013 2.1.2 -> 2.1.3:
Update init script for PAC
Disable almost all kernel debugging support except KALLSYMS. Kernel failed to boot with CONFIG_KALLSYMS disabled
28/09/2013 2.1.1 -> 2.1.2:
Turn all CPUs online when governor gets changed, hotplug bug workaround
SIO and VR I/O scheduler
Initial STweaks support, big thanks @gokhanmoral. Download STweaks app from Play store to access almost all NEXT related settings (CPU governor, frequency, and voltages; GPU governor and frequency limit; surfaceflinger rotation; I/O scheduler; logger; CIFS, Xbox controller, and USB modem support; and dual boot related settings).
22/09/2013 2.1 -> 2.1.1:
Update overclock codes, remove gpu_oc interface: https://github.com/kumajaya/android...mmit/94ac45a10213de400c7bf3c01b5c5b052ae8ba18
sgxfreq: add sysfs interface to store frequency limit: https://github.com/kumajaya/android...mmit/738061b30d2278d3b51b341bc2597dad300f4e47
sgxfreq: limit frequency to default on boot: https://github.com/kumajaya/android...mmit/8a6933cf6565b5587db6a2a5ce7b1207807ab701
The latest Android Tuner app needed to control the modified OMAP GPU control interface but the dirty way by editing /etc/init.post_boot.sh always available
18/09/2013 2.0 -> 2.1:
Separated vendor blobs for JB 4.1.x and JB >= 4.2, @poppolo2001 fix applied
With CPU and GPU overclock, CPU under/over voltage, upstream kernel 3.0.96 by @CodyF86
Complete changelog: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.2-update
02/09/2013 1.8.3 -> 2.0:
Vendor blobs in separated flashable zip, taken from Samsung 4.2.2. Flash proprietary-vendor-samsung.zip directry after flashing NEXT kernel 2.0 on both 1st and 2nd ROM!
Ten seconds boot menu timeout. Boot to the latest booted ROM when timeout periode reached. Finally, my trick works :victory:
Using Samsung P3110 Update1 kernel source: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=p3110 . Patched to comply CM/AOSP need and NEXT dual boot, without SELinux and audit support, gcc linaro compiler. Kernel source: https://github.com/kumajaya/android_kernel_samsung_espresso10/tree/cm-10.2
Samsung open source exFAT kernel modules included, source: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=exfat
Without CPU or GPU overclock
Without extended CPU governor or I/O scheduler
Without swap or zram support
AROMA 2.70 beta 6 binary
13/08/2013 1.8.2 -> 1.8.3:
Samsung 4.2.2: The first attemp to reduce battery draining issue, zram service disabled! You can enable zram (not as a service) by issuing "setprop persist.service.zram 25" over Terminal Emulator or "adb shell". Reboot is required.
CM 10.2: Bluetooth tethering fix from upstream CM 10.2
07/08/2013 1.8.1 -> 1.8.2:
The third attemp to support Samsung 4.2.2 for all device configuration
Vendor blobs in separate flashable zip updated, please re-download it!
06/08/2013 1.8 -> 1.8.1:
The second attemp to support Samsung 4.2.2 for all device configuration
Vendor blobs in separate flashable zip. For all ROMs, on both 1st and 2nd ROM: Flash vendor-blobs-new-ducati-blackhawk.zip directry after flashing NEXT kernel!
Single channel sound output bug fix
05/08/2013 1.7 -> 1.8:
Initial Samsung 4.2.2 support
Updated to upstream Linux kernel 3.0.41 (incremental patch)
https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.1-blackhawk 1-2 Aug 2013
The first kernel utilizing the new ducati firmware, the first kernel preserved 815.8MB RAM! Don't forget to flash vendor-blobs-old-ducati-blackhawk-p31xx.zip if you switch to another kernel
01/08/2013 1.6.3 -> 1.7:
Initial CM 10.2 support. Do not flash blackhawk-next-cm-exfat-vold.zip! CM 10.2 already has an open source/reverse engineered exFAT filesystem support
zram switched to zsmalloc, zram optimized for Android disabled
XBox 360 USB controller with BigX LED support enabled (by @iks8 request). Modules not loaded by default, edit /system/etc/init.d/02modules to activate it.
23/07/2013 1.6.2 -> 1.6.3:
Add android_reboot applet to NEXT's busybox (a quick port from Android toolbox) to fix AROMA boot menu fail to boot into recovery/bootloader as reported by @kinung
I hate bug!
22/07/2013 1.6.1 -> 1.6.2:
Hotplug CPU governor working properly with cleancache enabled, zcache memory corruption problem fixed!
21/07/2013 1.6 -> 1.6.1:
Hotplug CPU governor kernel panic bug fix. This governor not working properly with cleancache enabled, cleancache disabled for now
Static linked busybox compiled from source, fstrim patch applied. Busybox config based on CM's busybox bbconfig output. Total 46 more than previous busybox applet, add priority option to swapon applet
zRAM swap per CPU core, same priority value. CM's /system/bin/compcache script updated to handle 2 zRAM devices. Reference: http://wiki.gentoo.org/wiki/Zram
Stock ROM persist.customboot.zram property changed to persist.service.zram, follow CM's standard
Stock ROM default zRAM size changed to 26% RAM size
Swappiness value changed to 90
18/07/2013 1.5 -> 1.6:
LZO compression updated to current upstream version, optimized for arm. Reference: http://git.kernel.org/cgit/linux/ke.../?id=b0af9cd9aab60ceb17d3ebabb9fdf4ff0a99cf50
zRam support optimized for Android, utilizing the new lzo library. Set 18% of RAM as zRam swap file. CM user can use CM's Settings - Performance options.
cleancache support with working Zcache driver, utilizing the new lzo library
entropy threshold tweaks, /dev/random linked to /dev/urandom
github 14-18/07/2013 commits: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.1-blackhawk
11/07/2013 1.4.1 -> 1.5:
Decrease CPU voltage for frequencies below 1.2GHz, increase CPU voltage for frequencies above 1.2GHz
Re-enable MMC_CAP_ERASE for I/O speed improvement, run "fstrim -v /data" and "fstrim -v /cache" manually to TRIM your filesystem or run LagFix (fstrim GUI, download it from Play)
Remove my old hack in cpufreq driver
Newer PowerVR SGX540 3D kernel module and vendor binaries, in sync to CM-10.1. For dual boot user, you must update both 1st and 2nd ROM to renew both ROM vendor binaries!
Change screen_off_max_freq from 1.008GHz to 800MHz, small changes in init scripts
SuperSU v1.41
16/06/2013 1.4 -> 1.4.1:
I/O speed improvement, 1.3 and 1.4 bugfix
SuperSU v1.34 - thanks Chainfire
nooc: Smartreflex class 3 re-enabled, voltage control disabled
small update to disable swap support by default for my "stock based ROM" included
04/06/2013 1.3 -> 1.4:
Selected kernel modules, scripts, and binaries integrated in boot.img, single flash for 1st and 2nd ROM
Kernel compression back to gzip, boot.img compression switched to lzma for better compression (I need more space)
Auto root (for stock)
Auto busybox (for stock)
Auto rotate (for both stock and CM) depend on ro.sf.hwrotation value, camera orientation fix included
External sdcard and internal media swapper script integrated in boot.img (for stock as 1st ROM)
Override init.d CPU governor setting on boot completed (technical reason/by design). Please use an app "on boot" or /etc/init.post_boot.sh to set CPU governor
init script reworked (again), simplified
Standalone nooc version, no longer as an addon for standard NEXT
Untested CRT off animation support
01/06/2013 1.2 -> 1.3:
Updated compiler to the latest linaro gcc 4.7
Better data integrity on both 1st and 2nd ROM
Ramdisk init scripts reworked, inline with the latest Samsung (Taiwan BRI 04/2013) and CM (29/05/2013 nightly)
Inline with P51xx port
Updated exFAT modules (don't know it's better or worse, it's closed source)
Default CPU clock still 1.008GHz, default GPU clock 307.2MHz
1.1 -> 1.2:
Potential bug in sdcard swapper script fixed. Yes, for stock ROM as 1st ROM this kernel still has a script to swap external sdcard - internal media.
SuperSU updated to the latest version (stock ROM).
1.0 -> 1.1:
exFAT filesystem support, stock ROM only for now. I will share separate flashable zip for CM 10.1, when it's ready (broken USB storage support). Please note Dual Boot FAQs #24!
CGROUPS, SLUB, and TRACING support back enabled for exFAT compatibility, Android logger disabled by default to compesated it. You can enable logger by editing /system/etc/init.d/02modules .
No boot menu in single ROM environment.
Change stock ROM init.d script starting point. Earlier than before, same as CM 10.1 now.
Non overclock addon for anyone who is experiencing overheats when using standard NEXT kernel.
Source change: https://github.com/kumajaya/android_kernel_samsung_espresso10/commits/cm-10.1-blackhawk, May 24-26, 2013. A lot of undocumented change in ramdisk side.
exFAT support in CM 10.1
Download and flash blackhawk-next-cm-exfat-vold.zip over recovery
fsck.exfat, mkfs.exfat, vold binaries and all needed libraries taken from Samsung JB 4.2.2 included
USB storage support is broken, you need USB OTG Helper from http://forum.xda-developers.com/showthread.php?t=1588940 as 3rd party USB storage mounter
exfat binaries for exfat support in USB OTG Helper included. So, all USB OTG Helper features (FAT, Ext2/3/4, full NTFS, and exFAT support) enabled
To avoid Dual Boot FAQs #24 issue, flash blackhawk-next-cm-exfat-vold.zip and NEXT kernel of course directly after CM update. For CM 10.1 only!
Download Record:
proprietary-vendor-samsung.zip: 4481
proprietary-vendor-samsung-4.1.x.zip: 1478
Dual Boot FAQs
Dual Boot FAQs
Adapted from droidphile's "Dual Boot FAQs" with permission.
1. "Why would I wanna dual-boot?"
A. You don't have to.
Suppose you're more of an aosp rom fan. But misses the HDMI out, bluetooth hands-free and love sammy camera more. Do a minimal installation of sammy rom and boot into it when in need of these features and use aosp rom otherwise.
Or you are a sammy rom fan but love the responsiveness and pure android feel of aosp roms.
And while you can dual boot two sammy or two aosp roms, it doesn't make any sense.
2. "What if I don't need dual booting?"
A. No issues. Kernel won't force to setup 2 roms. You can single boot as before.
3. "Will dual booting change my bootloader or do any dangerous stuff like setting my phone on fire?"
A. NO. Changes are at kernel and ramfs level only. Some space in your internal sd card is used, and also the unused hidden partition mmcblk0p11 is used to store cache of second rom. Dual booting doesn't repartition the filesystem or perform anything scary.
4. "I want to setup dual booting."
A. There are four situations:-
1) Sammy rom now. Want to use aosp as secondary.
2) Sammy rom now. Want to use aosp as primary.
3) Aosp rom now. Want to use sammy as secondary.
4) Aosp rom now. Want to use sammy as primary.
Prerequisites for any setup is
a) Flash latest blackhawk's NEXT kernel
b) Flash new ducati vendor blobs (since 1.8.x)
c) Flash latest PhilZ Touch - blackhawk repack version - recovery
d) Atleast 90% battery left.
e) 2 GB free on internal SD.
f) Some spare time
1) Present sammy, setup aosp as secondary:-
i) Reboot into recovery
ii) Flash blackhawk's NEXT tool, create system.img for CM/CM based ROM and then close it
iii) Reboot into secondary recovery
iv) Flash aosp ROM as 2nd ROM
v) Flash blackhawk's NEXT kernel again
vi) Flash new ducati vendor blobs again (since 1.8.x)
2) Present sammy, setup aosp as primary:-
i) Reboot into recovery
ii) Nandroid backup your current sammy ROM
iii) Flash blackhawk's NEXT tool, create system.img for Samsung stock/stock based ROM and then close it
iv) Reboot into secondary recovery
v) Nandroid restore your sammy ROM as 2nd ROM
vi) Flash blackhawk's NEXT kernel again
vii) Flash new ducati vendor blobs again (since 1.8.x)
viii) Reboot into primary recovery
ix) Flash aosp ROM as 1st ROM
x) Flash blackhawk's NEXT kernel again
xi) Flash new ducati vendor blobs again (since 1.8.x)
3) Present aosp, setup sammy as secondary:-
Same as (1), instead of flashing aosp to second, flash sammy to second.
4) Present aosp, setup sammy as primary:-
Same as (2), instead of flashing aosp to first ROM, flash sammy.
NOTE:
-To dual boot Two Aosp or Two Sammy roms, just follow (1) or (2) (depending on which one of them you want as primary/secondary), just flash Sammy instead of aosp or aosp instead of sammy.
5. "What things should I be taking care off while dealing with dual booting?"
A. - Make sure where you are: in primary or secondary recovery.
6. "How to boot into primary rom?"
A. AROMA based boot menu will help you on every boot.
7. "How to boot into secondary rom?"
A. AROMA based boot menu will help you on every boot.
8. "Is kernel partition shared?"
A. Yes. Same kernel boots both roms.
9. "If I flash another kernel (that doesn't support db) do I lose dual booting?"
A. Yes
10. "I lost dualbooting after flashing another kernel. I didn't do anything to second rom files in sdcard/.secondrom. How can I get db back?"
A. Just flash the latest blackhawk's NEXT kernel, flash new ducati vendor blobs again (since 1.8.x)
11. "Will there be any performance degradation on the rom used as secondary compared to primary?"
A. NO
12. "Will my phone run slow overall because of db?"
A. NO
13. "How to flash a newer version of 1st rom?"
A. As usual, just flash it from primary recovery. Flash blackhawk's NEXT kernel again, flash new ducati vendor blobs again (since 1.8.x)
14. "How to flash newer version of 2nd rom?"
A. Just flash it from secondary recovery. Flash blackhawk's NEXT kernel again, flash new ducati vendor blobs again (since 1.8.x)
15. "Would upgrading 1st or second rom cause other rom to fail on boot?"
A. No. Partitions of other rom are not touched during upgrading.
16. "I miss the recovery I used before, so much.."
A. PhilZ Touch not bad at all.
17. "User apps of 1st rom are automatically available for second rom?"
A. NO. However, if you had backed them up using Titanium Backup or similar apps, just restore apps while on second rom.
18. "I wanna keep separate backup for apps in both the Roms, since I use one Rom for say entertainment and other productivity."
A. Setup different backup directory in Titanium Backup in 1st and 2nd rom.
19. "I don't see STweaks app in second rom."
A. This is blackhawk's NEXT dual boot solution for Galaxy Tab 2, a free implementation of gokhanmoral's Siyah dual boot.
20. "Do I need to anything special before flashing a newer blackhawk's NEXT kernel?"
A. NO. Just flash kernel in primary and secondary recovery. Yes, on both 1st and 2nd ROM. Just flash kernel in recovery - whichever you used to do. Kernel image is copied to the unified kernel partition (since 1.4 version). Flash new ducati vendor blobs (since 1.8.x) on both ROM may be required to ensure vendor blobs match to the kernel
21. "How can I run same STweaks settings of 1st Rom in 2nd Rom?"
A. This is blackhawk's NEXT dual boot solution for Galaxy Tab 2, a free implementation of gokhanmoral's Siyah dual boot.
22. "How do I remove everything related to DB and run single boot again?"
A. In primary recovery, flash blackhawk's NEXT tool and delete 2nd ROM system image. OR delete .secondrom directory in /data/media while on 1st Rom.
23. "If secondrom files are kept in /data/media, will wiping data in recovery erase second rom files?"
A. NO. /data/media is skipped in CWM recovery.
24. "I was using ExFat card on sammy rom without any issues. I have setup dual boot with aosp and now after booting into CM it says microSD card is corrupted."
A. Aosp roms doesn't support ExFat out of the box. The data was corrupted by aosp vold. Even if you boot back to Sammy rom, it still would be corrupted. To recover data, manually mount the card in recovery, copy contents to internal SD and reformat card to a Fat32.
Also try
chkdsk X: /f (where X is the drive letter of microsd), you may be able to copy data.
25. "I read somewhere that both rom data partition use the same space. Doesn't that mean my apps are shared across roms?"
A. NO. It just means they uses same partition. They're still different directories.
1st rom data = /data
2nd rom data = /data/media/.secondrom/data
26. "Will hitting "Boot into Secondary Recovery" in recovery boot menu change my recovery?"
A. NO. It just runs (not flash) an alternate recovery so that you can configure dualboot settings.
27. "How do I backup 1st Rom and 2nd Rom?"
A. To backup 1st Rom, do what you did to backup rom while you were single booting a while ago.
To backup 2nd Rom, use the secondary recovery.
28. "Is there an easier way for dual-boot?"
A. Yes, send your device to me.
29. "DB architecture?"
A. Like you know, every rom has a /data, /system, /cache partition and a kernel to boot.
For primary rom, it's
mmcblk0p10 = /data
mmcblk0p9 = /system
mmcblk0p7 = /cache
And these won't change whether you're single booting or dual booting.
For secondary rom, data and system is stored in internal sd, cache in hidden partition. Note that internal sd in our device is mounted to /data/media.
We have data as a directory, System as an image in data/media/.secondrom. Cache in mmcblk0p11 which is hidden partition and not used otherwise.
- When second rom is booting, second rom data is bind mounted to mmcblk0p10 as /data/
- data/media/.secondrom/system.img partition is mounted as /system.
- mmcblk0p11 is mounted as /cache.
More FAQs will be added and the list will be updated as DB is improved.
Dual Boot Exercises
Exercise I
An example current facts:
ROM: Samsung stock JB 4.1.2
Kernel: blackhawk single kernel
Recovery: PhilZ Touch prior version
Prerequisites step:
Update your kernel to blackhawk's NEXT kernel
Update your recovery to the latest PhilZ Touch - blackhawk repack version - recovery
Download CM latest nightly + GApps zip
~2GB free on internal storage
Dual boot step:
Reboot into recovery
Flash blackhawk's NEXT tool, create system.img for CM/CM based ROM and then close it
Reboot into secondary recovery, make sure you choose "Secondary Recovery"! Make sure you really choose "Secondary Recovery"!!
Flash CM
Flash GApps zip
Reflash blackhawk's NEXT kernel
Reboot into secondary ROM - CyanogenMod!
It's always better if you make a backup before performing all above steps. Do it at your own risk!
Exercise II
An example current facts:
ROM: CM 10.1 latest nightly
Kernel: blackhawk single kernel
Recovery: PhilZ Touch prior version
Have Samsung stock 4.1.2 nandroid backup
Prerequisites step:
Update your kernel to blackhawk's NEXT kernel
Update your recovery to the latest PhilZ Touch - blackhawk repack version - recovery
Nandroid backup your current CM 10.1 ROM
~2GB free on internal storage. I am not sure, depend on your backup data size
CM 10.1 as 2nd ROM:
Reboot into recovery
Flash blackhawk's NEXT tool, create system.img for CM/CM based ROM and then close it
Reboot into secondary recovery, make sure you choose "Secondary Recovery"! Make sure you really choose "Secondary Recovery"!!
Restore CM 10.1 nandroid backup
Format /cache, clean dalvik-cache
Reflash blackhawk's NEXT kernel
Reboot into secondary ROM - CyanogenMod!
Samsung 4.1.2 as 1st ROM:
Reboot into primary recovery, make sure you choose "Primary Recovery"! Make sure you really choose "Primary Recovery"!!
Restore Samsung stock 4.1.2 nandroid backup
Format /cache, clean dalvik-cache
Reflash blackhawk's NEXT kernel
Reboot into primary ROM - Samsung!
Do all above steps at your own risk!
Just opened a new thread for my masterpiece work on Galaxy Tab 2. Enjoy it and don't forget to press my Thanks button
PhilZ Touch attached in post #1 has a "red" on screen navigation bar in secondary recovery to distinguish between primary and secondary :laugh:
08/08/2013: Kernel for stock 4.2.2 Developtment Secret
If you want to build your own kernel for stock 4.2.2, this is the development secrets how to fix CPU frequency jumping to maximum available frequency, how to fix slow graphics issue, how utilize the new ducati firmware and increase the RAM space, how to fix hardware accelerated media problem and how to fix WiFi tethering issue.
Kernel source: http://github.com/kumajaya/android_kernel_samsung_espresso10/tree/cm-10.1-blackhawk
Samsung kernel update: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=p3110
Samsung exFAT source: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=exfat
How to fix CPU frequency jump to maximum available frequency (1.52GHz, overclock version) on boot
Rename /system/lib/hw/power.default.so to /system/lib/hw/power.default.so.bak, copy power.piranha.so from NEXT kernel 1.8.2 package to /system/lib/hw
How to fix slow graphics issue
This solution authored by @codeworkx 8 moths ago but disabled by default: https://github.com/kumajaya/android...mmit/0c6d1a53f1a51b588786b168a48e2566f8a49065 Enabling both FB_OMAP2_VSYNC_SEND_UEVENTS and FB_OMAP2_VSYNC_SYSFS solve this problem
How utilize the new ducati firmware and increase the RAM space
How to fix hardware accelerated media problem
How to fix WiFi tethering issue
If you use above information, proper credit must be given including a clear text about this solution.
21/09/2013: OMAP PowerVR 3D GPU Control
There some interface inside /sys/devices/platform/omap/pvrsrvkm.0/sgxfreq:
frequency interface to access the current GPU frequency (153600000/307200000/384000000)
frequency_list interface to access supported GPU frequencies (153600000 307200000 384000000)
frequency_limit interface to access the GPU maximum frequency limit (default: 307200000). Writeable mean this code inside the pvrsrvkm kernel module, the GPU maximum frequency controllable
governor interface to access the current GPU governor (userspace/on3demand/activeidle/onoff)
governor_list interface to access supported GPU governor (userspace on3demand activeidle onoff)
The upcoming version of Android Tuner (0.10.2) support OMAP GPU controls.
21/09/2013: NEXT 2.0.1
As I mentioned before, I still continued cm-10.2 branch kernel development. This branch is the source code of NEXT 2.0, I've added overclock support but limited at 1.2GHz CPU and 384MHz GPU. OMAP GPU controls support applied as gpu_oc interface replacement. Kernel attached here as blackhawk-next-kernel-2.0.1-p31xx.zip .
Changelog:
Rewriting overclock code: https://github.com/kumajaya/android...mmit/35e0c0455cb7ae4beb50375c5873b328a76a1087
Add sysfs interface to store GPU frequency limit: https://github.com/kumajaya/android...mmit/738061b30d2278d3b51b341bc2597dad300f4e47
Limit GPU frequency to default on boot: https://github.com/kumajaya/android...mmit/8a6933cf6565b5587db6a2a5ce7b1207807ab701
Xpad force feedback support disabled
WARNING: This kernel only for device that can handle 1.2GHz CPU and 384MHz GPU frequency.
ketut.kumajaya said:
Just opened a new thread for my masterpiece work on Galaxy Tab 2. Enjoy it and don't forget to press my Thanks button
Click to expand...
Click to collapse
Now Im very confuse. Which one to use? Im on CM10.1 4.2.2 Lastet update.. GT P3110..which kernel should I install? what is the different between KK and Philz Touch?
Fotonista said:
Now Im very confuse. Which one to use? Im on CM10.1 4.2.2 Lastet update.. GT P3110..which kernel should I install? what is the different between KK and Philz Touch?
Click to expand...
Click to collapse
There is no confusion at all...
Every file you need is in the first post: kernel, tool and Philz. Don't use anything else.
Read the examples. All information is in there...
I don't know about the differences between KK and Philz, but I don't care though... Philz is just great!
Many, many respects to ketut...
Big thanks for your efforts...
Sent from my GT-P3110 using xda app-developers app
Fotonista said:
Now Im very confuse. Which one to use? Im on CM10.1 4.2.2 Lastet update.. GT P3110..which kernel should I install? what is the different between KK and Philz Touch?
Click to expand...
Click to collapse
PhilZ Touch is a recovery image, NEXT kernel is a boot image, KK-Boot discontinued project.
Ketut @ awesome work with awesome guide.. U explained each n every step clearly for freshers.. N BTW do I need to update Blackhawk next kernel to 1.0..if yes, wiping cache n delvk is necessary before flashing? I am asking u cos I Dnt want to be in mess anymore.. I am happily enjoy dual boot environment.. Thanks again for all the effort..
Sent from my GT-P3100 using xda premium
god_creature said:
Ketut @ awesome work with awesome guide.. U explained each n every step clearly for freshers.. N BTW do I need to update Blackhawk next kernel to 1.0..if yes, wiping cache n delvk is necessary before flashing? I am asking u cos I Dnt want to be in mess anymore.. I am happily enjoy dual boot environment.. Thanks again for all the effort..
Sent from my GT-P3100 using xda premium
Click to expand...
Click to collapse
Yes. Fixed the problem when installed CM 10.1 directly as 2nd ROM. No wipe needed.
Please let me ask a question here.
I have already asked in Philz's thread but no answer till now.
Can Philz restore backups made within cwm?
I already have some backups from cwm times and if Philz could restore them that would save me a lot of time. Of course I could just try and see, but that information would be usefull to have before starting in advance.
Please, ketut, any information on that?
Sent from my GT-P3110 using xda app-developers app
dimfil said:
Please let me ask a question here.
I have already asked in Philz's thread but no answer till now.
Can Philz restore backups made within cwm?
I already have some backups from cwm times and if Philz could restore them that would save me a lot of time. Of course I could just try and see, but that information would be usefull to have before starting in advance.
Please, ketut, any information on that?
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
Compatible: http://forum.xda-developers.com/showthread.php?t=2201860
ketut.kumajaya said:
Compatible: http://forum.xda-developers.com/showthread.php?t=2201860
Click to expand...
Click to collapse
Great!
It's a lot of pages. I can't find it right away, but your answer is enough for me! So, they are compatible.
I will try and report if necessary.
Sent from my GT-P3110 using xda app-developers app
This great work Ketut, thanks for giving us easy way to dual boot. Keep up the good job.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ketut, congrats on your new achievement !
Just one quick question : Can you post all the features (other than dual-boot ability) of this blackhawk-next-kernel on first post ? Or the features are still the same with this :
ketut.kumajaya said:
This is [BOOT IMAGE][GT-P31XX] KK-Boot - Custom boot image for stock 4.1.1/4.1.2 ROM and [KERNEL][GT-P31XX][JB][4.2.2]CyanogenMod 10.1 unofficial kernel 3.0.31 combination, plus cm-10.1-blackhawk commit on github:
Remove Samsung debugging code in ext4 filesystem, inline with omapzoom
Initializing Android USB depending on the rom type, big thanks to gokhanmoral. This is the key of single kernel. Multiboot support not so far, you can reuse my kernel for multiboot (if you can)
Compiler optimizations
Kernel without CGROUPS support
Using SLQB memory allocator
Decrease MPU, IVA, and GPU voltage
Adapt and fix codeworkx's sysfs for controlling pivot mode. This is the key of landscape kernel
Stop the spam from audio driver
An exprimental config, remove a lot of debugging config from kernel: 775MB RAM
Stock JB 4.1.1/4.1.2 ROM: Using a slim version of busybox (from gokhanmoral's ramfs for siyahkernel-sgs3), bash and nano binary, sysrw and sysro script removed. GPU clock @ 384MHz + 2D GPU rendering, stock ROM really need an overclocked GPU.
CM/CM based ROM: As usual, change ro.sf.hwrotation value from 270 to 0 in /system/build.prop will transform your device to landscape mode, a workaround fix for boot animation graphic glitch. GPU clock @ 307MHz + 2D GPU rendering + 16bit transparency + disabled dithering + purging assets allowed
/system/etc/init.post_boot.sh is yours kernel tuning template. But remember, do not force your system too much until you are sure that your device is able to handle it.
Flash this using the latest CWM, CWM Touch, Philz Touch, or TWRP at your own risk!
Click to expand...
Click to collapse
Thank you
distan7 said:
Ketut, congrats on your new achievement !
Just one quick question : Can you post all the features (other than dual-boot ability) of this blackhawk-next-kernel on first post ? Or the features are still the same with this :
Thank you
Click to expand...
Click to collapse
Same kernel, different ramdisk. Thanks for your support :good:
STOP PRESS: Update PhilZ Touch to 5.03.7 http://forum.xda-developers.com/showpost.php?p=39935850&postcount=89!
Oh good news my brother I am happy
Envoyé depuis mon GT-N7100 avec Tapatalk
Couple questions to ketut Please try to answer me - noobie
1) I can flash this for single rom, yes? It should be better than previous version?
2) I can still turn Tab on, press volume down button to boot into CWM?
3) How to turn off the boot menu? (I think I don't need it)
Andrev01 said:
Couple questions to ketut Please try to answer me - noobie
1) I can flash this for single rom, yes? It should be better than previous version?
2) I can still turn Tab on, press volume down button to boot into CWM?
3) How to turn off the boot menu? (I think I don't need it)
Click to expand...
Click to collapse
1. Yes as covered by Dual Boot FAQs. No.
2. Yes.
3. Can not be, maybe the next version. Reboot to recovery and bootloader may be removed for security reasons.