Here is the initial release of my kernel. I'd like to have some other stuff fixed/working, but for now, this is it. I've made a lot of changes and I tried to list them all below, but I know there is stuff that I missed. Currently, the only issue that I know of is that the boot animation will be out of sync and may skip on boot. I have currently retained the stock boot animation, but custom boot animations are also possible if people would like them.
Also, while this kernel can work for recovery, I currently have not tested it, so recovery will remain what it is (ie. jt1134's CWM). I plan on testing recovery soon and releasing an updated Odin for it, as well as just having the kernel zip re-flash recovery.
Installation Instructions:
1. Download zip
2. Transfer to SDCard
3. Reboot into recovery, you'll need to have CWM if you don't already
4. Install zip from SDCard and select the zip you downloaded.
5. Reboot and enjoy
0807
Make logcat an option that can be turned on/off
-From root shell, run "logcat-enable" to turn logcat on, "logcat-disable" to turn it off
Make /preinstall partition swap space
Fix problem with rooting phone on boot
Fix fix_permissions in recovery
Update to recovery
0731
Fix mount USB storage in recovery
0730
Custom boot animation support
Updated recovery
0710
Voodoo Sound V10
Updated CWM Recovery
0602
Voodoo Sound fixed - Thanks supercurio
Removed OnDemand
Added FIFO and BFQ IO Schedulers
Added tun.ko and cifs.ko
0531
Initial release, built from source
Undervolted
Voodoo lagfix available - Thanks supercurio
Updated compiler flags
Linaro Toolchain for cross-compiling
Battery hack to allow for non-OEM Batteries - courtesy of SirGatez
init.d support
SDCard speed tweak (via init.d script)
Upstream EXT4 Patches
VFAT Patch
TCP and CFS Tweaks to help data/performance
V(R) IO Scheduler
Auto-root on boot
Maybe missing some other stuff, check Github for full changes
TODO (somewhat in order of importance):
Test CWM and flash recovery partition
Smooth out boot animation
Get an overclocking kernel out
NOTES:
If you are experiencing problems, I need detailed info to be able to fix it or help you out. Failure to provide detailed info will mean I'm just going to ignore your problem as user error. Details would be something such as which kernel you are flashing (filename) and steps to reproduce the issue. Also, if you used any other kernels that had the same problem or didn't have the problem.
DISCLAIMER
By downloading and using the kernels, this signifies that you have read this full post and the FAQ before reporting an issue. You also take all responsibility if your phone breaks or your warranty becomes void (which, if you're flashing this, it already is). I offer no guarantees as to anything working, though I try not to release broken stuff, it happens sometimes.
Legend
voodoo/novoodoo - voodoo has the lagfix, novoodoo doesn't (I hope this was obvious)
Frequently Asked Questions
How do I install this?
You flash this in CWM. If you need CWM, you can find it here
Can I use ROM Manager to flash this?
If you didn't use Odin to flash CWM, this will not work. Also, ROM Manager is not compatible with CWM when it fully replaces stock recovery.
Can I install this over another Voodoo Lagfix kernel?
Yes. Any kernel that use's supercurio's lagfix can be flashed over any other kernel that uses it.
How do I disable Voodoo Lagfix?
Create a file on the SDCard named disable-lagfix within the voodoo folder (/sdcard/voodoo/disable-lagfix). You can also use the option in the Voodoo Control app (from the market) or the option in CWM Recovery to disable the lagfix.
How do I know if it is installed?
Go to Settings > About Phone and the kernel version should read:
Code:
2.6.32.9
[email protected] #1
Will this work with xxx ROM?
This will work with any currently available ROM that is posted here.
Can I overclock with this kernel?
No. Currently overclocking is not supported. I do plan on looking into implementing this in a future version though.
Can I use SetCPU with this kernel?
You can use SetCPU with this, but do not use profiles. If you have problems and are using profiles, I'm not going to try to fix them as profiles do not work properly on any SGS phone that I've seen.
Does this kernel include xxx feature?
If it is not listed in the first post, probably not. To be sure, check the commits to the source on Github.
Can you add/implement xxx feature?
If you can link to what you want added/changed, I can look into doing so. If you just say something like "I want bigger quadz!" with no information about what you want or where to find it, I'll just disregard your request.
I am having xxx issue, can you fix it?
See the NOTES section above. Failure to provide any steps to reproduce your error, or a log of the issue as it is occurring will not get your problem fixed. I need the output from logcat and/or dmesg to be able to fix problems. Use the following to obtain a log (easiest with ADB).
Code:
adb shell dmesg > dmesg.txt
adb logcat > logcat.txt
Enter one of the commands and attempt to recreate your issue. Logcat will run constantly until you stop it (disconnect the phone, or ctrl+c). Dmesg will dump the current buffer and end. Try to get a logcat first as it will be easier to capture the error. PM me the files once you've collected them and I will look into it. DO NOT POST THEM IN THE FORUM. Logcat and dmesg may both contain identifying information (like your phone number or email address) so PMing them to me will prevent everyone from seeing this info. If you need help, ask or join IRC.
If you would like something added to the FAQ, please post it in the following format:
Code:
[PLAIN][b]Put the question here[/b]
Put the answer here[/PLAIN]
Flash in cwm.
Sent from my SCH-I510 using XDA Premium App
papi92 said:
Flash in cwm.
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
Yes, added installation instructions to OP
So if we already have voodoo lagfix installed based on other kernel do we try the non lagfix ver or is it ok to install the new file with lagfix included?
Sent from my SCH-I510 using XDA Premium App
Blanco954 said:
So if we already have voodoo lagfix installed based on other kernel do we try the non lagfix ver or is it ok to install the new file with lagfix included?
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
If you have lagfix enabled you just flash the voodoo kernel, or disable lagfix and flash non-voodoo kernel if you want RFS file system
Thanks Hopper. I will give this a try.
Sent from my SCH-I510 using XDA Premium App
Worked like a champ for me...thank you!
Sent from my SCH-I510 using Tapatalk
Do we disable the lagfix the same way as we do with jts?
Sent from my SCH-I510 using XDA Premium App
Flash, flashed!
Thanks again, imnuts!
confirming my noob status again:
I can just use CWM and install this right over your debloat and JT's kernel? OR, do I need to go back to non-voodoo ED1?
papi92 said:
Do we disable the lagfix the same way as we do with jts?
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
We currently have only one cwm which is jt's, so I don't quite understand what you mean.
froodyo said:
confirming my noob status again:
I can just use CWM and install this right over your debloat and JT's kernel? OR, do I need to go back to non-voodoo ED1?
Click to expand...
Click to collapse
If you currently have lag fix enabled, you can only flash the voodoo kernel. If you do not have lagfix enabled, you can flash either kernel.
You do not need to go back to ed1. Just flash the appropriate kernel.
hoppermi said:
If you currently have lag fix enabled, you can only flash the voodoo kernel. If you do not have lagfix enabled, you can flash either kernel.
You do not need to go back to ed1. Just flash the appropriate kernel.
Click to expand...
Click to collapse
Thank you very much.
papi92 said:
Do we disable the lagfix the same way as we do with jts?
Click to expand...
Click to collapse
Yes, lagfix is disabled the same way with any kernel that uses supercurio's Voodoo Lagfix.
froodyo said:
I can just use CWM and install this right over your debloat and JT's kernel? OR, do I need to go back to non-voodoo ED1?
Click to expand...
Click to collapse
Kernels are almost always independent of the ROM, so yes, you can install this regardless of what ROM you are running (Stock, debloated, something else). If/When we get a non-TouchWiz based ROM, this may change, but for now, you can use this with anything currently available.
hoppermi said:
If you currently have lag fix enabled, you can only flash the voodoo kernel. If you do not have lagfix enabled, you can flash either kernel.
Click to expand...
Click to collapse
I set up novoodoo to try and avoid issues, so if you were on voodoo and didn't disable, the novoodoo should still work, but why risk it if you don't have to?
So I flashed the voodoo kernel and now my charge keeps randomly freezing and rebooting
Manjews said:
So I flashed the voodoo kernel and now my charge keeps randomly freezing and rebooting
Click to expand...
Click to collapse
Are you doing any under clocking? I had this problem before the new kernel trying to under clock with the screen off.
hey i come from the fascinate and i love your work can't wait until you get voodoo sound working
i will be rooting a friends droid charge soon and then i will set him up with JT cwm voodoo and your kernel
glad to see some devs i already know working on the droid charge
khanfuze said:
Are you doing any under clocking? I had this problem before the new kernel trying to under clock with the screen off.
Click to expand...
Click to collapse
No but I think it might be set cpu related issue. I had the scaling set to on demand. I turned it off and so far it's running smooth with no issues.
Manjews said:
No but I think it might be set cpu related issue. I had the scaling set to on demand. I turned it off and so far it's running smooth with no issues.
Click to expand...
Click to collapse
Good to hear Samsung released broken cpu governors again
Related
This kernel is intended to be a simple rooted kernel, based off samsung stock, with only simple mods ... its feature are:
NEW!!! NOW HAS CWM 3.1.0.1 RFS/EXT/USB CWM REBOOT RECOVERY AND ROM MANAGER SUPPORT!
I do think this will be my last froyo kernel build... unless some bug comes up, that has to be fixed...
Kernel developers: feel free to rip my initramfs, for cwm 3.1.0.1 reboot recovery, it should work with all known builds, and may need just a little editing of the .rc files and sdx.sh in /sbin, to get your mods in place. The github is updated, and is ready for prime production!
Changes and features as of v1.05:
* CWM reboot recovery updated to 3.1.0.1 Purple edition, with customized recovery for the Epic4G
* Voodoo sound updated to v9, from supercurio
* busybox 1.18.0 removed, and cwm recovery busybox full 1.16.2 is replacing it, making the kernel even smaller
* thumbEE kernel support reverted, as my testing indicates that deep sleep is affected, draining battery faster
Changes and Features as of v1.04:
* ClockworkMod 3.0.2.5 Reboot Recovery, compatible with RFS and ext4
* fixed busybox DNS, thanks Rodderik!
* Added scripts for USB Mass Storage, mountums & umountums
* Voodoo Sound Driver v8 update, from supercurio
* RNDIS / wired USB tethering support built in from kernel
* THUMBEE built in from kernel for cortex a8 optimization, thanks Rodderik!
* build_kernel.sh modified to reflect EpicCM/nullghost script, but with some special revisions.
* rclean updated, to clean root files without any errors, in case would like to be used, before a stock kernel flash
* Root and busybox with minimal system mods
* designed to allow OTA update after flashing back the stock kernel, provided the user hasn't modified other necessary system files
* RFS and ext4 compatible
* REBOOT RECOVERY TO CWM 3.0.2.5 BOTH RFS AND EXT4, ROM MANAGER COMPATIBLE
* CIFS, TUN, & TMCPSS Clamping enabled from kernel
* market app malware patch, writing blank /system/bin/profile at boot
* mkasick sysfs keyboard patch, with my keytimer script
* voodoo sound 7 by supercurio, controlled by voodoo control app in android market
* additonal custom scripts in /sbin for cleaning root, busybox, and flash kernels and recoveries
This kernel was built to replace the traditional one click root method for my all in one root and recovery script.
Link:
DRockstar.Clean.Kernel.EC05.v1.05.zip
NEW!!! for flashing with Odin, we'll have to get used to this, in future, for rooting the phone by flashing a rooted kernel
You can use this odin flash to effectively root the phone:
Clean.Kernel.EC05.v1.05.tar.md5
Sources:
http://github.com/DRockstar/Clean-Kernel-EC05
Credits:
* kain203: donated the use of an 8 core linux vm for my use in compiling kernels and the cwm binary. This *greatly* increased my productivity, and allowed me to edit and compile everything for cwm and my kernel, *all* from my Epic 4G, believe it or not...
* noobnl & joeykrim- this kernel was originally inspired by noobnl Andromeda kernel for eclair, and uses the same joeykrim root and busybox method
* Rodderik, without his guidance, patience, and original working victory_03_defconfig, this kernel wouldn't have been possible. Some commits in sources taken from his sources.
* supercurio, for his voodoo sound, commits directly from his github source
* mkasick, for his sysfs keyboard patch
* nullghost and tanimn, for help getting github set up, and having easy to follow github sources
* koush, for ClockworkMod, and help in finally getting dualfs support, and direct input for cwm
* vocaltreat, for purple cwm icon
* skeeterslint and Rodderik, for helping me get packages installed, and ClockworkMod binary compiled
Sent from my SPH-D700 using Tapatalk
NICE!
Do you BONSAI?
Nice work man keep it up!
goodness, I went to vote this 5star and my machine hiccupped and rated it one star. your work here is awesome, keep it up
contradude said:
goodness, I went to vote this 5star and my machine hiccupped and rated it one star. your work here is awesome, keep it up
Click to expand...
Click to collapse
You can always go back, and revote the star rating...
Sent from my SPH-D700 using Tapatalk
Hey there, thanks for this, but I'm unable to update profile or prl. I get the unknown error. I am running ace rom v2. Any tips?
Sent from my SPH-D700 using XDA Premium App
lattiboy said:
Hey there, thanks for this, but I'm unable to update profile or prl. I get the unknown error. I am running ace rom v2. Any tips?
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
There was a fix for this in another thread. I don't think it's related to the kernel though cause I was able to update my profile and prl successfully.
EDIT: This is the thread I was referring to, may want to check it out:
http://forum.xda-developers.com/showthread.php?t=1041415
Good work man.
Sent From My Evo Killer!!
blazinazn said:
There was a fix for this in another thread. I don't think it's related to the kernel though cause I was able to update my profile and prl successfully.
EDIT: This is the thread I was referring to, may want to check it out:
http://forum.xda-developers.com/showthread.php?t=1041415
Click to expand...
Click to collapse
Thanks. I followed the instructions, but it now says "Internal Error". Hmmm.....
I wouldn't care, but to use my Airave correctly I'm supposed to update PRL and Profile.
lattiboy said:
Thanks. I followed the instructions, but it now says "Internal Error". Hmmm.....
I wouldn't care, but to use my Airave correctly I'm supposed to update PRL and Profile.
Click to expand...
Click to collapse
Strange, you may want try rebooting the phone and trying again. This issue should have been resolved but then again I always had problems updating the profile/prl even when it wasn't on Sprints side with my first epic. I got a replacement (refurb) and haven't had any issues since.
Why would someone rate this thread less than 5 stars? ...
Anyways great job dude you released some good stuff
Hey DRockstar,
good work on putting out a clean kernel. I havent had any time to look into the modem delta thing lately.
Since you compiled the kernel you must know if the USB driver is compiled into the kernel. I'm suspecting it is right? If so maybe flashing a new kernel can actually fix my USB problem.
LiberatorUSA said:
Hey DRockstar,
good work on putting out a clean kernel. I havent had any time to look into the modem delta thing lately.
Since you compiled the kernel you must know if the USB driver is compiled into the kernel. I'm suspecting it is right? If so maybe flashing a new kernel can actually fix my USB problem.
Click to expand...
Click to collapse
I didn't mess with the usb drivers, and no one has reported any problems connecting usb. You can feel free to see if this fixes your USB problem, but I doubt it will have any bearing on it, honestly.
Sent from my SPH-D700 using Tapatalk
Well I still don't understand how people with DK28 can have USB problems since they seem like independent systems. So if flashing DK28 screws up a USB config or something then flashing a new kernel might help. Its a long shot but worth a try.
Do you know if this one works with CM7 A4?
LiberatorUSA said:
Well I still don't understand how people with DK28 can have USB problems since they seem like independent systems. So if flashing DK28 screws up a USB config or something then flashing a new kernel might help. Its a long shot but worth a try.
Do you know if this one works with CM7 A4?
Click to expand...
Click to collapse
No, it won't.
I wish I could give this a try right now, but i don't have a computer to install clockwork on my phone. guess i'm waiting till quitting time.
just a side note the link in the OP has a typo
http://drockstar.devphone.org/EpicKernel/DRockstar.Clean.Kernel.EC05.v1.02.zip
Does anyone know, is there something like this I can flash, that will give me ext4 cwm3? Cant get to a computer right now.
Oops, wrong thread.
Sent from my SPH-D700 using Tapatalk
Can someone point me in the direction of a clockworkmod flash that doesn't also root. all the ones i have found seem to be expired links
Can't wait to try this. Thanks
@ masterface: Use the one posted by Dameon. Right click to open it. Open in new window. Then you should be able to download it like normal instead of getting blank page. Hope that helps
Sent from my SPH-D700 using XDA Premium App
I have a .zip file that will remove the voltage scheduler if you have any saved on boot. A lot of users are using gingerbread ROMs that uses CWM3 including myself, but unfortunately this program only works with earlier versions of CWM. So I'm looking for a newer zip file that will remove voltage settings or if someone is savvy enough to update the script or whatever it is you have to do, it would be greatly appreciated.. the zip file I'm looking to use can be found in my sig. (schedule remover) ... thanks
cwm3 doesnt have
Advanced options > wipe voltage settings?
all the cwm 2.5 that we've been using for froyo do.
but check this out for converting cwm 2.5 zips to 3.0
CWM 2.5.x.x conversion to 3.0.0.x
I actually thought I remembered seeing that in the advanced options when you said that... but i just booted into recovery and its not there. I appreciate the reply.. i look into that link you provided.. thank you
Ummm what kernel are you using?
Talon most definitely has it.
studacris said:
Ummm what kernel are you using?
Talon most definitely has it.
Click to expand...
Click to collapse
escapists kernel. But that makes sense. That must have been where I saw it when I was using Talon. Thanks for confirming
Curious if disabling lagfix on the droid charge is a common problem or if others are sucessful in doing this. Had a bag experience disabling lagfix in the past which borked my file system. Thinking of trying the ext conversion again. Anyone have any special methods to disable lagfix when switching roms that would be more sucessful than creating disable-lagfix file in voodoo folder? Thanks
flyinj54 said:
Curious if disabling lagfix on the droid charge is a common problem or if others are sucessful in doing this. Had a bag experience disabling lagfix in the past which borked my file system. Thinking of trying the ext conversion again. Anyone have any special methods to disable lagfix when switching roms that would be more sucessful than creating disable-lagfix file in voodoo folder? Thanks
Click to expand...
Click to collapse
use the voodoo control app to disable lagfix on next boot, that should work but I've never used it myself
flyinj54 said:
Curious if disabling lagfix on the droid charge is a common problem or if others are sucessful in doing this. Had a bag experience disabling lagfix in the past which borked my file system. Thinking of trying the ext conversion again. Anyone have any special methods to disable lagfix when switching roms that would be more sucessful than creating disable-lagfix file in voodoo folder? Thanks
Click to expand...
Click to collapse
All methods to disable lagfix create the disable-lagfix file which is checked by the init script to determine if lagfix is to be disabled.
There is the Voodoo control app that makes the creation of the file convenient and mostly noob proof.
However, the actual conversion is done exactly the same regardless of the method that the file is created.
There are a couple of issues with the actual conversion to be aware of.
The first is that the conversion of the cache partition always fails.
The second is that the data partition is formatted differently than Samsung's rfs format.(4k vs 16k clusters)
Bottom line is that you end up with a somewhat borked set of filesystems.
_____________________________
Rooted and Bloat frozen Stock EE4
V6 SuperCharger
Would the safest bet be when flashing let's say a stock ROM back on the phone to not disable the lagfix and flash the Pit file and let's say ee4 to have the file system converted back?
Sent from my SCH-I510 using Tapatalk
flyinj54 said:
Would the safest bet be when flashing let's say a stock ROM back on the phone to not disable the lagfix and flash the Pit file and let's say ee4 to have the file system converted back?
Sent from my SCH-I510 using Tapatalk
Click to expand...
Click to collapse
yeah EE4 with PIT is probably your safest bet
blazing through on my 4G Droid Charge
I see some developers recommended disabling lagfix before installing their package. This doesn't make much sense to be since disabling the lagfix borks your file system.
Try to help me in this scenario. Lets say i'm running gummycharge 2.0 with their included Imo Voodoo Kernel v2.3.2 which has converted my file system to ext4. Now I want to switch to the infinity rom. Can I just do my normal cwr of wiping data, cache, and davlik without changing the kernel from rom to rom? I guess my question is can I use one kernel to run on any rom I want to install or must the kernel be changed based on the rom? I see that the infinity rom has their own kernel but lets say I just want to run the kernel that came with gummy.
Ok so now I want to get back to stock because lets say I have a problem that needs warranty attention. Just Odin the pit and ee4 and my file system will be back to rfs without having to disable voodoo lagfix and bork my system correct?
Thanks for help trying to learn the most I can before switching back to ext4 with my prior bad experience.
flyinj54 said:
I see some developers recommended disabling lagfix before installing their package. This doesn't make much sense to be since disabling the lagfix borks your file system.
Try to help me in this scenario. Lets say i'm running gummycharge 2.0 with their included Imo Voodoo Kernel v2.3.2 which has converted my file system to ext4. Now I want to switch to the infinity rom. Can I just do my normal cwr of wiping data, cache, and davlik without changing the kernel from rom to rom? I guess my question is can I use one kernel to run on any rom I want to install or must the kernel be changed based on the rom? I see that the infinity rom has their own kernel but lets say I just want to run the kernel that came with gummy.
Ok so now I want to get back to stock because lets say I have a problem that needs warranty attention. Just Odin the pit and ee4 and my file system will be back to rfs without having to disable voodoo lagfix and bork my system correct?
Thanks for help trying to learn the most I can before switching back to ext4 with my prior bad experience.
Click to expand...
Click to collapse
yes you got it correct, for the most part roms can be flashed over one another and the kernel will simply stay the same or get updated if its newer... so yes your example of Gummy to Infinity will work, I've done it numerous times myself
second issue of using EE4 and PIT to get to stock for verizon is also correct, it is your safest and most fool proof bet even verizon won't be able to tell it was modded (some people say they can, or look at the sd card for clues but its debatable)
edit: also the kernels are build specific so only GB ones with GB roms and froyo with froyo roms etc.. don't flash a froyo rom over a GB one with a GB kernel running, I think you'd need to disable voodoo lagfix first for that
blazing through on my 4G Droid Charge
READ ME FIRST! This is beta. Some things may not work properly. If you find a problem, please either respond to this thread, or add a bug on the issue tracker on github. Thanks!
Introduction
This kernel is built from Samsung's T959VUVKJ6 Kernel source drop with some slight modifications.
There are plans for this kernel to have voodoo sound, bln, and optimizations in the future.
But for now, stability and code cleanliness are top priority.
The thread title will update as I do. I don't have any scheduled plans, so don't ask for ETAs.
Changes
My code is hosted on GitHub. You can find the latest changes there.
Btw... I actually tag my releases
Plans
I sorta did a little brain dump on what I'm thinking here.
Initramfs
We are now on a new version of CWM: v5.0.2.7
Old backups from previous nandroid's WILL NOT restore with this version, as the nandroid backup format changed.
Also, if you're updater-script and update-binary that are using amend instead of edify, please switch to edify. Amend is no longer supported.
New recovery fixes backup & restore, adds the ability to restart adbd and restart to download mode.
Current Support
AFAIKT, this kernel is basically just like stock, but adds ext4(and jbd2), tun, cifs, fuse, and si4709 modules.
Debug info was recently disabled, which should also speed things up a bit.
ChainDD's Free Superuser.apk and /system/xbin/su are automatically installed/updated if needed.
Same with RaverX3X's bootanimation binary.
Download
Subtly Modified Stock for T959V KJ6 v0.1.1-rc1+:
sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip
Flashing
Either flash from CWM or:
Install Heimdall
Extract the zImage from the CWM zip file
Change your directory to where the zImage is
Put your phone in download mode
Run the following:
Code:
heimdall flash --kernel zImage --recovery zImage
Credits
drhonk (cwm+voodoo initramfs)
krylon360
RaverX3X (moral support, testing, bootanimation binary)
SeafoodExpert(aka ericmpanda), FBis251, and zargeus (for testing)
pawitp (thanks again for your help earlier)
supercurio (for voodoo lagfix and everything else!)
ChainsDD (for Superuser.apk and su)
Benjamin Dobell (for Heimdall, my current favorite program)
Last, but not least...
Samsung (for the source, of course)
Release History
Beta 3.1 (an RC): sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip
Disable broken DMA Acceleration and Deep Idle.
Nothing else updated. Another kernel update will happen soon
Beta 3 (tagged in git): sms-T959V-KJ6-v0.1.0-unsigned-update.zip
Update CWM to v5.0.2.7
Fix backup & restore
More kernel cleanup
Beta 2d (no kernel update, just initramfs): sms-T959V-KJ6-v0.0.2d-unsigned-update.zip
Add bootanimation as a voodoo extension. This will install /system/bin/bootanimation just like su and Superuser.apk.
Updated to ChainsDD's Superuser.apk to build v3.0.7 (41). 'su' is still 3.0.3
Beta 2c (no kernel update, just initramfs): sms-T959V-KJ6-v0.0.2c-unsigned-update.zip
Basically reverted back to v0.0.2
Double checked that su and superuser are updated
Worked with Krylon360 and RaverX3X to finally get initramfs bootanimation working. Now the rom just needs the right /system/bin/bootanimation (and it needs to be executable! yea. I ran into that one... :sigh: )
Beta 2b (no kernel update, just initramfs): sms-T959V-KJ6-v0.0.2b-unsigned-update.zip
Removed 'disabled' from bootanimation service, as suggested by Krylon360
Updated Superuser.apk and su
Beta 2a (no kernel update, just initramfs): sms-T959V-KJ6-v0.0.2a-unsigned-update.zip
Removed 'disabled' from samsungani service, as suggested by Krylon360
Beta 2 (tagged in git): sms-T959V-KJ6-v0.0.2-unsigned-update.zip
More build clean-up
Disabled Debug Info and a few other debug options for performance
Made ext4 and tun as modules, now also packing cifs, fuse, and si4709
Initial Beta (tagged in git): sms-T959V-unsigned-update.zip
For more details, check out github... really. Everything I do, there is source for!
Changes to the kernel can be found here.
The bug tracker for the kernel is here.
awesome work! I am very excited to try this. Downloading now and will update as soon as I have a few minutes to spare.
jigglynuts said:
awesome work! I am very excited to try this. Downloading now and will update as soon as I have a few minutes to spare.
Click to expand...
Click to collapse
Great! I'm about to pass out... lol.
As the Title says/warns... this is beta2.
I am running this on my phone, as well as a few other people, and we haven't ran into any major issues... yet.
If you actually find a bug, please submit a new bug to the issue tracker on github.
:sleeps:
:happydance
Thanks for your work!
Mind I ask, i know rfs and ext4, but what is the mtd+yaffs 2 you mentioned adding?
Will ext4 voodoo conversions take place in the same manner as before?
Sent from my SGH-T959V using XDA App
Updated op with an update to remove disabled from samsungani in init.rc.
Thanks for the tip, Krylon360!
Finally a KJ6 kernel compiled form source! Thanks so much, will try it shortly!
Caligula36 said:
:happydance
Thanks for your work! Mind I ask, i know rfs and ext4, but what is the mtd+yaffs 2 you mentioned adding? Will ext4 voodoo conversions take place in the same manner as before?
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Basically, the internal storage on your phone is a flash device.
BML and FSR (aka XSR) acts as a software-based FTL (Flash Translation Layer).
This allows you to put filesystems like fat or ext4 on a flash device.
Hardware FTLs are everywhere. Look at your memory stick for instance. There is an FTL between the usb device controller and the nand flash chips that actually store the data. You can format your memory stick with ext4, btrfs, ntfs, whatever...
Samsung decided to go further down the rabbit hole with RFS, which is basically a modified version of FAT(32?) with ACLs and Journalling. IMO, silly.
BUT, fsr/rfs are proprietary modules and are built with a kernel that has a set of symbols exposed. If I disabled debugging (like I did) and something in one of those fsr/rfs modules depended on it, then the fsr/rfs modules wouldn't load (unless you trick it).
Moving to controlling the flash on the phone (in which the flash type on this phone isn't nand, but OneNAND-Flex) with MTD gets us away from the proprietary modules, but introduces a new problem. Can't use ext4 for /system, /data, and /cache anymore. Instead you have to use a flash filesystem, like yaffs2 (which is what the CM supported Samsung phones use). I would like to see a test on this phone with UBI/UBIFS though. I think that might have better performance then yaffs2 or jffs2 (but almost everything, including my grandma is faster then jffs2... seriously).
It's subtly modified stock, and I'm using the same initramfs (minus kernel modules, of course) that kj1 with voodoo lagfix had (now with boot animation support with the latest update). Lagfix and all should work just as it did before.
Ask, and ye shall receive... (or better, get a whole page about how flash works)
Just what I've been waiting for... I've missed CWM, but wanted to keep the kj6 kernel.
I'll push this later this morning as time permits and see how it goes.
Thanks!
How fast is boot with this?
I am using it with the simply simple rom right now, perfect combination!!!
Sent from my SGH-T959V using XDA App
Will it work with init.d scripts ? lockscreens and thundervolt...
itzik2sh said:
Will it work with init.d scripts ? lockscreens and thundervolt...
Click to expand...
Click to collapse
It's just a kernel it has init-d support and boot animation support.
lockscreens are framework dependant not kernel dependant.
Sent from my HTC Glacier using xda premium
I've been using this for a few hours now on top of Valhalla o/c'd to 1.3ghz and it's been running great so far. Good job man.
Sent from my SGH-T959V using xda premium
how long does it take to boot. Normal or voodoo kernel time.
airfluip1 said:
how long does it take to boot. Normal or voodoo kernel time.
Click to expand...
Click to collapse
Shaved 4-5 seconds off my boot, on Octane 2.x
Sent from my SGH-T959V using xda premium
Running great on icbinb kj6.
Many thanks for this.
Just flashed, no issues so far
Sent from my SGH-T959V using XDA App
Okay, user error... got it flashed with Heimdall after all... we'll see how she plays...
Working well with ICBINB Official KJ6. Nice work. Glad to see some developers are back in action with this phone.
Hello FB, will you help me.
I'm not sure which of these kernels is stable, except the v0.0.2d with CWM3.
From your post:
sms-T959V-KJ6-v0.1.1-rc2.zip
From bhundven post:
Subtly Modified Stock for T959V KJ6 v0.1.1-rc1+: sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip
sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip {same as #1 ? (above rc1+)}
sms-T959V-KJ6-v0.1.0-unsigned-update.zip
Besides the /system unmount issue, what is the advantage of CWM5 vs CWM3?
Thank you
Fb's latest kernel is the most stable kernel as off now.
i would say go for fb's kernel
fb modified or i should say upgraded bhudven kernel...
and it got team acid splash screen which is a very nice touch
bark777 said:
Hello FB, will you help me.
I'm not sure which of these kernels is stable, except the v0.0.2d with CWM3.
From your post:
sms-T959V-KJ6-v0.1.1-rc2.zip
From bhundven post:
Subtly Modified Stock for T959V KJ6 v0.1.1-rc1+: sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip
sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip {same as #1 ? (above rc1+)}
sms-T959V-KJ6-v0.1.0-unsigned-update.zip
Besides the /system unmount issue, what is the advantage of CWM5 vs CWM3?
Thank you
Click to expand...
Click to collapse
I got 66 hours with no reboots on RC2.
The main differences between CWM 3 and 5 are that CWM 5 doesn't have trouble making and restoring backups (made in CWM 5), the ability to have ADB in recovery and the option to reboot to download.
Additionally, it has most of the changes made after Dec 7, 2011:
https://github.com/teamacid/android_kernel_galaxys4g/commits/sgs4g-aosp
FBis251 said:
I got 66 hours with no reboots on RC2.
The main differences between CWM 3 and 5 are that CWM 5 doesn't have trouble making and restoring backups (made in CWM 5), the ability to have ADB in recovery and the option to reboot to download.
Additionally, it has most of the changes made after Dec 7, 2011:
Click to expand...
Click to collapse
Thank you JMW and FB.
Is this the normal message state?
CWM-based VooDoo LagFix Recovery v5.0.2.7
Voodoo lagfix is actually: disabled
......................next boot: enabled
Option:
/system lagfix conversion: yes
...................debug mode: no
I show this from a terminal session:
/system ext4 rw,
/cache ext4 rw
/data ext4 rw
I tried to disable VooDoo but it does not disable, do I need to start with VooDoo disabled from version 0.0.2d?
I went back to v0.0.2d and disabled VooDoo, then flashed v0.1.1 rc2. The conversion took place per the voice. But it still shows that it is disabled as above.
Bark, read the OP under Features
http://forum.xda-developers.com/showthread.php?t=1513287
The RC2 version of the kernel forces you onto ext4 (lagfix) since there's no real reason why you should stay on RFS (lagfix disabled).
Not sure why that was confusing to me, but I really appreciate your quick response. Thank you for straightening me out!
Whoops! I heard my phone rebooting as it sat on the table. I guess I'll go back to v0.0.2d.
I'm running stock GB with AS 14.1 and Tegrak UV/OC to 1.2.
I have been running this kernel without any problems whatsoever.
I would check your UV/OC values to see if that is causing the reboot.
FBis251 said:
The main differences between CWM 3 and 5 are that CWM 5 doesn't have trouble making and restoring backups (made in CWM 5), the ability to have ADB in recovery and the option to reboot to download.[/url]
Click to expand...
Click to collapse
jigglynuts said:
I have been running this kernel without any problems whatsoever.
I would check your UV/OC values to see if that is causing the reboot.
Click to expand...
Click to collapse
Hello JN,
I'm going to chose oc/uv over the latest version of this kernel. I checked my settings and they are as suggested. I guess if the v0.0.2d kernel can tolerate my OC/UV settings and not reboot then I would deem it a tad more stable.
Since I can use the CWM5 version at will, I will use it to do backups. But I will use the v0.0.2d version daily as the OC'ing does make this device snappier. I don't understand the "ADB in recovery" part of the explanation, got to do some reading.
Do you overclock your phone, I would be interested in the setting you use.
Thanks!
my phone rebooted once after flashing the latest kernel.
after half a month no problems yet
Sent from my SGH-T959V using xda premium
JuLes' MostWanted said:
my phone rebooted once after flashing the latest kernel.
after half a month no problems yet
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
Hello JMW,
That is interesting. I wonder if after some time the kernel adjusts something and then calls for a reboot.
I will go back and run the latest again and then give it some time based upon your input.
Thank you.
Common causes for phone to reboot is the voltage governor is too low or just something wrong with it
just for the record Bhudven and Fb nailed the values ;-)
JuLes' MostWanted said:
Common causes for phone to reboot is the voltage governor is too low or just something wrong with it
Click to expand...
Click to collapse
The voltage/cpuspeed 's have not changed between v0.0.2d and latest.
The thing is, I only know of a few people that have any problems and no one has given me or fb any kind of logs to prove there is a problem.
No logs, nothing to fix.
JuLes' MostWanted said:
just for the record Bhudven and Fb nailed the values ;-)
Click to expand...
Click to collapse
The values have always been nailed. The have not changed.
The only problems I have with this kernel is going from BML (fsr/rfs/ext4) to MTD then back to BML.
I try using heimdall and odin and the only way for me to revert back to bml is using the 'eraseall' command at the sbl prompt (which isn't easy to get to if you don't have the right tools or know what your doing) then one-click with bootloaders. Something wrong with the erase-block-size/page-size with mtd vs. bml. idk, still trying to figure that one out.
too bad i cannot provide logs.
as far as observe it always reboot once after i install the latest from fb....
note: before reboot, laggy
but all runs great after that reboot
i dunno why this happens but I think it a great thing
i just wanna make people aware of it.
damn this kernel diving must be mind boggling thats why I will stick to theme
bhundven said:
The voltage/cpuspeed 's have not changed between v0.0.2d and latest.
The thing is, I only know of a few people that have any problems and no one has given me or fb any kind of logs to prove there is a problem.
No logs, nothing to fix.
The values have always been nailed. The have not changed.
The only problems I have with this kernel is going from BML (fsr/rfs/ext4) to MTD then back to BML.
I try using heimdall and odin and the only way for me to revert back to bml is using the 'eraseall' command at the sbl prompt (which isn't easy to get to if you don't have the right tools or know what your doing) then one-click with bootloaders. Something wrong with the erase-block-size/page-size with mtd vs. bml. idk, still trying to figure that one out.
Click to expand...
Click to collapse
Thank you for your work, but can you please address why the kernels you released since you disabled Deep Idle and DMA Engines have random reboot issues. Many many people who have reverted back to the 2d kernel no longer have these issues.
I'm fairly sure it's because of init.d scripts messing with the CPU settings and other kernel settings.
I'm going to write a "stability" build of RC2 that just backs up your init.d on boot and wipes the directory. Bet you'll get rid of your reboots until you start messing with Tegrak and OC/UC/UV settings.
bhundven said:
No logs, nothing to fix.
Click to expand...
Click to collapse
I am so willing to submit logs, if I only knew how. I have read thousands of posts on this site and have learned a ton about my phone and how to upgrade it. But try as I may and I have tried, I cannot find a good reference document on collecting logs. I heard some people say I will run a logcat and I have downloaded log collector from the market.
I used to work in the field service arena and it was common that our customers would collect error data for us to use to find their problems, but they would always collect the wrong things until we gave them a list of what we needed and how to collect it. So I am sure that it is my noob searching that has made it difficult for me to throw a lasso around this issue, but if someone would direct me to a thread or give instructions I am sure it would help me and I think maybe some others too.
I would also like to thank the devs that replied in this thread. I'm sure there are better things to do then reply again to the reboot issues some are experiencing. I truly appreciate your time, offerings and effort.
Thx
FBis251 said:
I'm fairly sure it's because of init.d scripts messing with the CPU settings and other kernel settings.
Click to expand...
Click to collapse
I have no init scripts, no init.d directory, & do not oc/UV. I have the reboot issue. Bryan looked @ a logcat I took a while back but it held no clues. I'll see if I can find the time to install a kernel past 2d and troubleshoot.
Sent from my SGH-T959V using xda premium
Well if you DO wind up testing this, we needs these files:
hampsterblade said:
I'm currently looking through
/proc/last_kmsg
/data/tombstones/
/data/system/dropbox/
I just found something suspicious in system server wtf about the time the phone shut down
.
Here are the logs if anyone wants too look over.
Click to expand...
Click to collapse