Database Info

[KERNEL][GPL]Clean Kernel EC05 v1.05 CWM 3.1.0.1 REBOOT RECOVERY & ROM MANAGER!!!

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

[KERNEL][FROYO][8-07-11] PeanutButta Jelly Time

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

[Kernel] Dragon-G2x v1.1.1 (OTA/Weapon) [9/2/2011]

First off, big thanks to Faux123. This is based on his repo with a few tweaks of my own. I'll be adding more as we go on. And of course, he's welcome to pull any patches he likes from my github.
Changes:
Added zram compressed swap support. I'll attach a script to turn it on and one to see what its status is. It's not like the older ramzswap that requires a special tool, everything is done through sysfs now. Very nice.
Added zcache compressed cache. This is a bigger win IMO, it compresses any compressible data in the cache. This means you can keep much more data in cache, which means you have to read it in from slow flash much less often.
Tweaked the low memory killer to take swap space into account, but only some of it.... This prevents swap thrashing while the system tries to kill processes and free up ram/swap. I also suggest using something like AutoKiller to set the levels to the best performance for your workload. We all run different apps and such, and that can affect how these things work for each user. There is no setup that is going to be perfect for 100% of users. Speaking of AutoKiller, I have found the advanced tweaks to help a fair bit as well. Don't use the memory management one, it overides your settings for things like swappyness. And the IO Scheduler doesn't do anything as we aren't using cfq. Unless you turn on cfq...
On Swap and compression:
While badly configured swap can slow things down, it's far more complex than people think. It also frees up RAM that's not being used frequently for apps that are. So your system can more efficiently use the resources it has. While compression does use some CPU time, our dual core 1Ghz+ CPUs can compress/decompress REALLY fast. Far faster than reading from the flash storage. In theory, this can affect battery life, though I haven't seen any significant issues from it.
Q: But we have 512M, that's a LOT!
A: Well, kind of... Not all of it is accessible to the kernel for running apps. 128M for the GPU, some for the cameras, wifi, etc... In the end, a little less than 400M is available. Then you have to add in system overhead from the kernel itself, Android's OS processes, etc.. That is quite limiting, IMO, so using it more efficiently is important to me.
Q: I don't like compression/swap.
A: Then don't run this kernel.
Download (OTA) v1.1: http://goo.gl/2dCK8
Scripts: http://goo.gl/M4SzG
Code:
OTA Changelog:
v1.1.1:
* Fixed Haptic Vibration
* Fixed some config settings
v1.1:
* Updates from faux123 to fix LG crap code
* Increase voltages and enable 1.5GHz
v1.0.3:
* Added low memory killer changes back in.
* Fixed Haptic Vibration
v1.0.2:
* Correct mis-applied zcache patch.

Does this kernel rebuild cache every boot like faux 1.3?
Sent from my MeGaBoT Transformer!

Haptic feedback doesn't work. Faux had the same problem in one of his earlier kernels bbut he fixed it .
Sent from my LG-P999 using XDA App

KingDavid63 said:
Does this kernel rebuild cache every boot like faux 1.3?
Sent from my MeGaBoT Transformer!
Click to expand...
Click to collapse
Yes. I've poked around, but haven't figured out why. It's certainly nothing I'm intentionally doing. I tried using the same initrd from the Weapon stock kernel, no joy. That's about the only thing the kernel should be able to change that would make a difference.

C-4Nati said:
Haptic feedback doesn't work. Faux had the same problem in one of his earlier kernels bbut he fixed it .
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
I'll test it again, but I know it was working at one point.
EDIT: Argh.. yeah, config got messed up. Compiling now.
OK. 1.1.1 is up, tested on my phone with working vibrate.

Data missing
Hey ttabbal, maybe you can help me a little bit with the issue im having with cyanogenmod based roms,
I've been trying to know a bit more bout RILs and ended up learning that it resides at the kernel. My objetive of learning about it is because no matter I do i cant have data conection on any CM7 based ROM but I DO have data on any Froyo / Gingerbread OTA rom, even tryed to change basebands, change sim card, push the apps related to the telephony from GB OTA to Cyanogen and replace Ril Libs also. Nothing had worked. And this is where you can help me a little: while using your kernel I have the exact same issue! No data whatsoever! No matter what ROM I use, in the other hand using Faux's kernel i got no issue, and bec you based yours in his work im sure you know what exactly changed between them and enlight me or make me understang what can I possibly do to fix my issue.
Thanks!
BTW I live in Guatemala CA, using a data plan from CLARO (America Movil) carrier
Look here at the Wikipedia Link to look at the baseband Im using.

albertorodast2007 said:
Hey ttabbal, maybe you can help me a little bit with the issue im having with cyanogenmod based roms,
I've been trying to know a bit more bout RILs and ended up learning that it resides at the kernel. My objetive of learning about it is because no matter I do i cant have data conection on any CM7 based ROM but I DO have data on any Froyo / Gingerbread OTA rom, even tryed to change basebands, change sim card, push the apps related to the telephony from GB OTA to Cyanogen and replace Ril Libs also. Nothing had worked. And this is where you can help me a little: while using your kernel I have the exact same issue! No data whatsoever! No matter what ROM I use, in the other hand using Faux's kernel i got no issue, and bec you based yours in his work im sure you know what exactly changed between them and enlight me or make me understang what can I possibly do to fix my issue.
Thanks!
BTW I live in Guatemala CA, using a data plan from CLARO (America Movil) carrier
Look here at the Wikipedia Link to look at the baseband Im using.
Click to expand...
Click to collapse
I'm happy to share any information I can. Your issue is interesting as I can't think of any changes that should affect the radio. Most of the radio code isn't in the kernel. It's handled by a daemon called rild. We could try reverting some patches. The first thing to try would be to test all the older versions of the kernel. I'll get links posted for you when I get to a computer. If one of those work, we can look at the differences between them to try and narrow it down.

albertorodast2007 said:
Hey ttabbal, maybe you can help me a little bit with the issue im having with cyanogenmod based roms,
I've been trying to know a bit more bout RILs and ended up learning that it resides at the kernel. My objetive of learning about it is because no matter I do i cant have data conection on any CM7 based ROM but I DO have data on any Froyo / Gingerbread OTA rom, even tryed to change basebands, change sim card, push the apps related to the telephony from GB OTA to Cyanogen and replace Ril Libs also. Nothing had worked. And this is where you can help me a little: while using your kernel I have the exact same issue! No data whatsoever! No matter what ROM I use, in the other hand using Faux's kernel i got no issue, and bec you based yours in his work im sure you know what exactly changed between them and enlight me or make me understang what can I possibly do to fix my issue.
Thanks!
BTW I live in Guatemala CA, using a data plan from CLARO (America Movil) carrier
Look here at the Wikipedia Link to look at the baseband Im using.
Click to expand...
Click to collapse
I'm not so sure the kernel is going to affect your issue much. As ttabbal said it lies in the RILD binary. CM7/Miui has known issues with no data connectivity though it seems to happen pretty random. Have you tried doing a hard reboot? (hold power + vol up approximately 10 seconds) On occasion I have the same issue with no data signal (though cell is just fine). Usually a hard reboot (or two) solves the problem though.

Whitehawkx said:
I'm not so sure the kernel is going to affect your issue much. As ttabbal said it lies in the RILD binary. CM7/Miui has known issues with no data connectivity though it seems to happen pretty random. Have you tried doing a hard reboot? (hold power + vol up approximately 10 seconds) On occasion I have the same issue with no data signal (though cell is just fine). Usually a hard reboot (or two) solves the problem though.
Click to expand...
Click to collapse
Yup, its someting else, i even managed to solve the APN dissapearing issue in other way: install market enabler, change SIM code to anything and ther revert back to defualt an it will show u again your APNs just like if you hard rebooted.
I even tried copying rild (/system/bin) from OTA GB rom to a CM7 rom and flash, and nothing, and why using your rom and faux's kernel i got data and if using ttabbal's one i have none? has to do something with the kernel! but thanks for ur posts anyways I know ur busy guys

albertorodast2007 said:
Yup, its someting else, i even managed to solve the APN dissapearing issue in other way: install market enabler, change SIM code to anything and ther revert back to defualt an it will show u again your APNs just like if you hard rebooted.
I even tried copying rild (/system/bin) from OTA GB rom to a CM7 rom and flash, and nothing, and why using your rom and faux's kernel i got data and if using ttabbal's one i have none? has to do something with the kernel! but thanks for ur posts anyways I know ur busy guys
Click to expand...
Click to collapse
Your description sounds like the known cm7 apn bug to me. Installing a kernel usually triggers the bug for me as it involves soft reboots. With dragon, do the data workarounds work? Exactly what ROM are you running?

I think im not leaving things clear, my above post was what I did to fix apn dissapearing when i flashed cm7... and even if i hard rebooted (or used the market enabler trick) and apns where restored still couldnt get data to work...
Im usign whitehawk's rom now, but if i pair it with your kernel, the issue i have is not that apn dissapear (like they did in cm7, bec of the known issue) but that I cant get data to connect.
Sent from my LG-P999 using XDA App

albertorodast2007 said:
I think im not leaving things clear, my above post was what I did to fix apn dissapearing when i flashed cm7... and even if i hard rebooted (or used the market enabler trick) and apns where restored still couldnt get data to work...
Im usign whitehawk's rom now, but if i pair it with your kernel, the issue i have is not that apn dissapear (like they did in cm7, bec of the known issue) but that I cant get data to connect.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
OK, just making sure. Here are the older versions of the kernel. Try them out and see if any resolve the data issue you are seeing.
1.1: http://goo.gl/e913p
1.0.3: http://goo.gl/7QY0a
1.0.2: http://goo.gl/O6PDb
1.0.1: http://goo.gl/OWkG8
1.0: http://goo.gl/gLeFz
I honestly don't expect them to, but if the only change is the kernel, it seems like it could be related. Could you also attach a file with logs when it's trying to connect? Perhaps also with a log when booting from Faux's kernel when it works right?
adb logcat > log.txt
adb logcat -b radio > radio.txt
I might be able to see something in there...
Just to make sure we're on the same page, by Whitehawkx's rom you mean Weapon 2.4? I just noticed your sig says 2.3... I don't see sigs when I'm on my phone, so I missed that before. Have you tried updating to 2.4? It might help... it might not...

ttabbal said:
OK, just making sure. Here are the older versions of the kernel. Try them out and see if any resolve the data issue you are seeing.
1.1: http://goo.gl/e913p
1.0.3: http://goo.gl/7QY0a
1.0.2: http://goo.gl/O6PDb
1.0.1: http://goo.gl/OWkG8
1.0: http://goo.gl/gLeFz
I honestly don't expect them to, but if the only change is the kernel, it seems like it could be related. Could you also attach a file with logs when it's trying to connect? Perhaps also with a log when booting from Faux's kernel when it works right?
adb logcat > log.txt
adb logcat -b radio > radio.txt
I might be able to see something in there...
Just to make sure we're on the same page, by Whitehawkx's rom you mean Weapon 2.4? I just noticed your sig says 2.3... I don't see sigs when I'm on my phone, so I missed that before. Have you tried updating to 2.4? It might help... it might not...
Click to expand...
Click to collapse
hahahaha noob mistake... yeah im on 2.4 just updated my sig, thanks for pointing me that, thanks man! gonna use adb to get u some usefull logcats...
BTW i've seen some interesting updates on the nightly changelog for the p999, gonna try flashing latest nightly and see if something has changed....

Logs
Ok some logs from faux's and yours latest kernels, gonna start trying previous kernels from your links, muchas gracias!
BDW: flashed nightly #124 and still no data for me, i guess its bec im using it outside the states and/or its a SIM unlocked device..

just checking ttabal... did you ever figure out the cache rebuild on every boot thing?

How to use a script?

ILUHA_89 said:
How to use a script?
Click to expand...
Click to collapse
Script Manager from Market its free, or search any other script app...

Crashes on OTA
Used for half a day and had two lock ups using GB OTA. G2X would not come out of stand by. I will retry at a later time. It was nice to be able to use annyconnect vpn.

I cannot get the zswap stats script to run properly...it says syntax error (expecting ")") or some ****...what I'm I not understanding with this

Been running the kernel for about a day, both scripts running with script manager, no freezes or issues yet. Been trying to cause problems like I've had with other kernels, and i'm not getting them.

[KERNEL][UVKJ6][BETA3.1] Subtly Modified Stock with CWM5 + Voodoo Lagfix [1/14/2012]

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.

[RFC] universal recovery [2012/09/16]

Hello Galaxy S users,
Specifically, in this forum, it's Galaxy S 4G.
I know you've been watching T.V., and know (maybe... well here in E-merica) a little about universal health care... well I have something totally unrelated to talk with you about. [word this sentence with Steven Colbert's voice]
Universal Recovery.
As it stands, our bootloaders know nothing about the silly recovery partition on our devices.
And on stock roms, it is a total waste of good space we could put to any other partition (mostly data).
When this topic first reared it's ugly head, I thought to myself about just incorporating the unused space to data. But no! I have seen the light. And it is good!
There are a few different recoveries out there that are mostly a preference thing.
Stock Android Recovery (think the "3e" thing...) (totally friggin stock. No modifications)
ClockworkMod Recovery (cwm)
ClockworkMod Touch Recovery (cwm-touch)
TeamWin Recovery Project (twrp)
manual partition magic (that really only devs know about... [Bryan Jedi waves his hand in your face] forget I said anything here.)
... to name a few. Granted I will not support/help you on the first or last versions of recovery mentioned above.
I would like to use the recovery partition to unify the storage of the recoveries.
As we have seen with the radio partition... On stock, it is a bml partition without rfs. The modem.bin is written (redbend_ua) directly to the bml12 partition and read back by /system/bin/rild
On (Gingerbread(mtd)/CM7/ICS(mtd)/CM9) MTD based roms, the radio partition is a yaffs2 formated partition in which modem.bin's are simply copied to. A symlink (/dev/block/bml12) to allow rild to work correclty... (well and a nasty hack on SGS4G to pad the modem.bin with zeros, because the rild reads more then the size of the modem.bin but less then the size of bml12)
Lets say we format the recovery partition as yaffs2 (or either vfat or ext4 on bml roms), and store ramdisk-recovery-<version>-<fstype>-<recovery-type>.img files there.
Examples:
ramdisk-recovery-gb-bml-cwm.img
ramdisk-recovery-ics-mtd-twrp.img
Then create a cwm update.zip that allows you to switch your recovery based on what is in the /recovery partition.
The title of this post is [RFC]... This is a Request For Comments.
As an amendment to this RFC, I would also like to have universal updater.sh and updater-script files to be created so that one could say, flash:
stock bml gb (cwm) -> ics mtd (cwm-touch)
ics mtd (twrp) -> stock bml gb (twrp)
ics mtd (cwm) -> gb mtd (cwm-touch)
gb mtd (twrp) -> stock bml gb (cwm-touch)
gb mtd (cwm-touch) -> ics mtd (cwm)
...without ever needing to go to download mode to run a oneclick or odin.
This thread should eventually turn into a development thread containing the results of this discussion.
...
A little while back, I started a poll.
The results of the poll, and comments lead me to believe that users are more interested in obtaining root and having the latest version then anything else.
All of these recovery methods should provide root access to install which ever rom you want (rooted or not rooted) and whatever recovery you want to use.
Goals (no particular order):
Run an updater.zip OR run an android app to change the current version of recovery.
Unify the updater.sh and updater-scripts for our roms, so you guaranty that you can flash from any rom to any rom (unless it has not been updated to use this new standard)
Do something with the lost 6-7M of unused space currently known as 'recovery'.
Let me know what you think. I already have a WIP, but it only supports cwm (at the time of this writing. cwm-touch and twrp coming soon...).
I am working on minimal environments (android manifests) to build each specific recovery nightly so that these will always stay up to date with what is in our repositories.
Being an RFC thread, please provide some helpful feedback.
ALSO, I leave this open to other Galaxy S phones as well!
You too have a device with this stupid recovery partition.
If all Galaxy S phones used the same codebase for updater.sh and updater-scripts and for setting the currently used recovery, it would be a win for everyone.
OK, Technical section:
--------------------------------------------------------------------------------------
On the latests CM10, a patch was applied by pawitp a little while back to allow a simpler packing of ramdisk and recovery.
Because of this, you can basically repack the initramfs with a different recovery.
If we changed our stock bml gb kernel, cm7 (and other mtd based kernels) to use a similar recovery method, we could unify the way we change between recoveries.
--------------------------------------------------------------------------------------
...Comments go here VVVVVVVVVVV

As we were discussing on #teamacid, I think I can help with figuring out the mtd -> bml portion of this since most of my previous work has been with installer scripts and the recovery environment.
Bryan was telling me that it should just be a matter of flashing the bml zImage and to reboot and continue the install.
I definitely think that storing the recovery.img files in /recovery would be a great solution. It'll keep the kernel/boot.img files leaner and allow us to update the recovery without messing with the kernel.

FBis251 said:
As we were discussing on #teamacid, I think I can help with figuring out the mtd -> bml portion of this since most of my previous work has been with installer scripts and the recovery environment.
Bryan was telling me that it should just be a matter of flashing the bml zImage and to reboot and continue the install.
I definitely think that storing the recovery.img files in /recovery would be a great solution. It'll keep the kernel/boot.img files leaner and allow us to update the recovery without messing with the kernel.
Click to expand...
Click to collapse
Essentially, yes. There are two "universal"s here.
Universal recovery selection
Universal updater.sh and updater-script usage
And, yes, kind of... the reservoir may also be apart of the big problem here.
There is much experimentation and discovery to happen before anything really results from this thread.

I definitely support the movement. What can I do to speed up the process or help with this development?
Sent from my SGH-T959V using Tapatalk 2

I'm interested in the implications this could have to the S devices with a flash counter.
Sent from my SGH-T959V using xda premium

GreyDark said:
I'm interested in the implications this could have to the S devices with a flash counter.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
I know that the sgs4g has a flash counter, but it never increments.
I think it was something they were thinking about, but never got working for the release.

VillaCastana321 said:
I definitely support the movement. What can I do to speed up the process or help with this development?
Sent from my SGH-T959V using Tapatalk 2
Click to expand...
Click to collapse
I just need to finish my WIP and let other devs at it so they can make changes to it.
The WIP is driven by what is in the OP of this thread. It is not written very well and not very detailed.
I hope that changes over time with feedback.

Having botched my share of kernel/recovery flashes, this would be very interesting if I could always access something that would let me flash a known-good kernel/recovery from microSD when I next mess up.
Admittedly, I could stop flashing unknown kernel/recovery when I'm not within reach of Heimdall, but...

So the SII can use triangle away for the flash counter while with the SIII it's still usable yet not recommended from what I saw. By using dd to get the recovery in, the SIII dodges the counter again, (first time by using Odin to get root) but there can always be people who might even do that wrong. I don't know about the other S devices, but if there was an easy way to get root and a custom recovery, definitely a plus for average users.
Sent from my SGH-T959V using xda premium

I think its a very good idea. It makes perfect sense, I don't see a downside and see its possible. It would be great actually
Sent from my SGH-T959V using xda app-developers app

This sounds awesome... would b willing to test.....
sent from my t959w running RemICS, Voodoo sound, Rom Toolbox pro.

Fun starts in a month or so.
Wait... For... it.

bhundven said:
Fun starts in a month or so.
Wait... For... it.
Click to expand...
Click to collapse
Patiently waiting... teeth clenched....staring at my screen,watching for that post up..... LOL
sent from my t959w running RemICS-UX, Voodoo sound, Rom Toolbox pro

abonides said:
Patiently waiting... teeth clenched....staring at my screen,watching for that post up..... LOL
sent from my t959w running RemICS-UX, Voodoo sound, Rom Toolbox pro
Click to expand...
Click to collapse
So you are told to wait about a month, and you are spazing after six days? Wow, really patient.

Cooptx said:
So you are told to wait about a month, and you are spazing after six days? Wow, really patient.
Click to expand...
Click to collapse
I think he was joking

pisherthefisher said:
I think he was joking
Click to expand...
Click to collapse
I hope so
SMH
Sent from [CONTET DELETED]

love the idea <3

Sorry,my sick twisted humour cannot b appreciated via text.
sent from my t959w running RemICS-UX, Voodoo sound