yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] networkdood:
Are they placed in init.d automatically?
[Captivate Android Development] mtcarey:
Yes, the CWM package installer puts them there.
[Captivate Android Development] momulah:
Voodoo sound support? App says kernel not supported...kj3 fasty
[Captivate Android Development] Jsmokey:
You have to have voodoo control plus to get voodoo sound. We need source to compile it in the kernel directly so for now that's the only way to get voodoo sound in captivate gb roms/kernels.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] momulah:
Using voodoo plus I am. Still says it!kj3
[Captivate Android Development] boog:
That command is what builds cyanogen for the captivate, and it set's the "environment" (as I hear it called). I have flashed the resulting rom to my phone when I was playing with cyanogen.

"Make clean" will also clear everything and compile over after you make changes to source files.

I just do all of my development on my netbook, I never shut it down (well, very seldom), I either just let it sleep or hibernate, and I keep my terminal open all the time lol.

I have been gathering parts to put together another machine for development. I was given a 24" iMac that has a bad video card that would be great for development, and linux. Just need either a video card for it, or a motherboard and ram to transfer the cpu and hdd. Sucks being a poor boy!
[Captivate Android Development] droiduzr2:
How do I enable the backlight notification?

I am running FASTY III 1.3 with this Corn KJ3 kernel.

It took me 2 minutes to go from the old Kh2 (whatever fasty came with before) to flash to this using CWM.

I did notice after the flash by battery meter said 62% but I had 42% before the upgrade:D

I will reset the battery status next charge.
[Captivate Android Development] Jsmokey:
Thats strange if you're using the paid voodoo plus control app. Its worked for everyone else I've talked to about it. I've been trying everything to somehow get voodoo sound built into my kernel and no luck so far.

You could try kyuta's samurai kernel and see if that gets voodoo working right. The only real option though till source comes is voodoo plus.

@ notification post

We also need source to get for bln to work right, if that's what you mean.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] mtcarey:
Sorry... no Voodoo sound or color without the kernel source, which has not been released.
[Captivate Android Development] mtcarey:
Ouch... development on a netbook! I think those iMacs use nVidia graphics cards... you can get one pretty cheap from Newegg.
[Captivate Android Development] mtcarey:
Unfortunately, BLN isn't working. Apparently we need the kernel source for that. I've noticed that my battery percentage is almost always screwy after flashing any kernel. Just a few minutes on a charger usually seems to reset it to something more accurate.
[Captivate Android Development] Secretcow:
The kernel is awesome!!!

Mtcarey thank you so much!! I flashed this over stock Android 2.3.5 kj3 with gingerbread bootloader and added jwue11's ram script and a few of my tweaks.. I get 2400 in quadrant with no overclocking :D :D. The battery life is soo good too. Idle gets me 1% of battery life drained per hour.
[Captivate Android Development] mtcarey:
You're welcome! Pretty amazing difference.
[Captivate Android Development] Soy_Filipo:
Does this kernel have CWM?

Sent from my Galaxy Captivate, not that you care, just saying...
[Captivate Android Development] Jsmokey:
Yes it does.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] mtcarey:
New CWM 5 almost ready!

Just putting the finishing touches on a new custom version of CWM Recovery 5. I've added built-in lagfixing from within recovery (no voodoo), and finally gotten nandroid backup and restore fully working. Lots of other goodies include installing root, enabling / disabling init.d scripts, sysctl, logcat, start-up and shutdown sounds, custom init.rc tweaks, and lots more. The goal is to make it as simple as possible to drop it into any kernel and have all the goodies. I've gotten carried away with adding things, so I'm going to pull the plug in the next day or so and include it in a new version of the Corn Kernel. Stay tuned....
[Captivate Android Development] Kyuta Syuko:
That recovery's making me jealous. Or maybe just green with envy :D
[Captivate Android Development] mtcarey:
Don't be too envious... it's been a long, tedious process. :eek: Code, re-compile, re-pack, re-flash, re-boot, re-(expletive deleted) and so on....
[Captivate Android Development] Kyuta Syuko:
But it's paying off in the end right?
[Captivate Android Development] boog:
I have to ask, what is the fix for nandroid? And does it work on both rfs and ext4?

Good work! I wish my coding skills were higher than "Hello World!"
[Captivate Android Development] getinlost:
Nudge! Bump! Hello? Dup Dup Dup, is this thing on? It's been a "couple" days and I am jonesin' to flash something!
[Captivate Android Development] Jsmokey:
I second this, what Is the fix for nandroid I was just getting started on it today and even a point to where things are going wrong would be a huge time saver.

@getinlost If you have a hankering to flash something you can try my kernel, red nebula, or kyuta's samurai kernel.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] mtcarey:
There were several problems in Nandroid... primarily, when it does (did) a restore it was calling "format_device" in extendedcommands.c, which knows how to format yaffs, fat and ext4 (kind of), but not rfs. That's where it was dying. I made several changes to it, including substituting my own formatting routines, and skipping re-formatting altogether if not needed. CwM does not know rfs at all!
[Captivate Android Development] mtcarey:
It's coming! I got sidetracked with something else, but now doing final testing. Maybe tomorrow....
[Captivate Android Development] Jsmokey:
Ok that'll definitely cut down in the time I spend running through code trying to find problems. Thanks for the information.

Oh and I just wanted to say my last post wasn't meant to put your kernel down in any way just was giving him some options since he was wanting to flash something. I'm very appreciative of you're work on it as it was a big help with mine in the old thread.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] mtcarey:
No offence taken! It's not like there's money in this or anything.... It's part of the "fun" to try different things.
[Captivate Android Development] Kyuta Syuko:
Well that kinda explains why boog was able to restore a nandroid backup with ext4 but not rfs, but doesn't explain why it's not consistent. Maybe because of the "kind of" support it has for ext4? boog was saying he'd be able to restore the back up the first time but then would have to convert to rfs then back to ext4 to be able to do it again.
[Captivate Android Development] mtcarey:
As I recall, when restoring to rfs, Nandroid would simply erase the target with "rm -rf" first since it considers rfs an "unknown" file system. With ext4, it would "erase" by doing a re-format... however, the re-format function for ext4 (when it was already ext4) left the partition unmounted at which point the restore operation would die since it didn't check that the target was mounted! Nandroid had many problems... I made dozens of changes.
[Captivate Android Development] Jsmokey:
Sounds like I'm going to have a real fun week ahead trying to sort this all out..... Thanks for all the info though this is definitely going to save me a ton of time and headaches trying to fix it.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] boog:
I have been using everything I have been doing as a learning experience. So, do you have your changes (or anything) on git? or possibly zip up the files you changed for nandroid, so I could look at the differences, I would love to learn where the issues were since I can't find them myself.

Were all or most of the changes in nandroid.c? I'm guessing there were probably more.
[Captivate Android Development] Jsmokey:
In an earlier post he said there was problems with extendedcommands.c also and probably a few others.

I'm going to pull it into eclipse tonight, just got cdt plug in working in it, and see what all I can find that doesn't seem right, maybe compare it with an older version to see what changed since eclipse has a pretty awesome comparison feature.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] mtcarey:
Not on git yet. I'd like to make sure all the kinks are worked-out before posting the source. I've made hundreds of changes and enhancements, and not just to nandroid. For instance, I just finished making the text color externally configurable. Trivial, but still....
[Captivate Android Development] Kyuta Syuko:
Trivial but a feature I think would be nice to have for recovery even if it isn't used much. Recovery I mean.
[Captivate Android Development] Jsmokey:
I think that's a pretty awesome feature actually, I can't count how many times I've booted into recovery in a new kernel and couldn't stand the color of it and I tend to use recovery alot testing new themes, tweaks, and on and on.

So for people like me and probably you, kyuta, boog and most devs its something that is a very welcome addition to cwm.

Also mtcarey, I was wondering is it sztupy's universal lag fix you're working on incorporating? I was just curious cause I was actually working on building his into my cwm project.

edit: just really started going through all the code for nandroid mtcarey and I can see why you disappeared for a while on us there. This thing is completely borked. I don't know what I was thinking getting myself into this....;p Oh well I really needed to brush up on my c skills anyways and I think after this I'll be quite familiar with it again. Now I just wish I wouldn't have dropped C for so long.

edit again: The more I look through this the more I can't figure out what the hell they were thinking when they wrote the code for nandroid. It makes no f'in sense why would you go ahead and 'format' something in your code when you know its unknown/unsupported by the binaries you're using to do it, why not just leave it alone!?!?! That just seems like something that should stand out as a major no-no to do. Also I see what you meant when you said it kind of supports ext 4 from what I see so far, with my very rusty understanding of C, it seems like it just kind of randomly takes a shot in the dark at formatting/restoring to ext4 and hopes for the best. :S

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] mtcarey:
I started with sztupy's ULK, but very little of the original remains. Other than the name "lagfixutils.c" I can't think of anything that remains unchanged. As far as the nandroid code goes, yes it is a mess. In fact all of CwM is pretty messed up... lots of duplication and patched-on changes. It's definitely showing it's age and could probably use a complete re-write. I haven't written anything in straight C for almost 20 years, so it's been a good refresher. Fun with pointers!
[Captivate Android Development] TRusselo:
date in title is wrong.... today is only the 8th not 12th
[Captivate Android Development] droiduzr2:
Hey,

I flashed the new kernel and my phone sits on the colorful bootup screen.

I used the CWM file. Voodo lagfix was turned off as I was trying the Red Nebula kernel yesterday.

I was using your previous kernel that installed and worked fine.

It said this one installed properly.

I did pull the battery after waiting 15 minutes but got stuck in the same reboot loop with the colorful boot screen.

How do I fix this?

thanks

---------- Post added at 05:59 PM ---------- Previous post was at 05:18 PM ----------

I also tried to use the Odin file...no go

I used Odin to go back to previous Corn Kernel (I think lagfix is off). I did not hear the voice as it converted. I flashed with Odin and it came up right away after reboot.

It seems something is not working right with the new kernel.
[Captivate Android Development] space_eyes:
Yeah I got the same thing, booted back up into cwm, tried reflashing but there's no dir's, E:\ all gone :(, will try odin back to other kernal see if i don't have to completely wipe. If doesn't work I will start fresh to see if new kernal will work from that...

EDIT:

I was installing via CWM and it rebooted by itself...
[Captivate Android Development] mtcarey:
What does the "colorful boot screen" look like? This doesn't have one! I'll flash Red Nebula and then this again to figure out what's wrong. I already have an idea.
[Captivate Android Development] Jsmokey:
I think he may be talking about the galaxy s animation. Only thing I can think of unless the rom he uses has a different one included with it. If you can figure out the problem I'd be glad to know, I flash to corn and samurai occasionally to do some comparison testing but the version I have of corn is the one right after you got su fixed and I haven't had any issues going back and forth between them.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] space_eyes:
was the reg boot screen, magical color pieces... The crt black out worked, the press the side key again and voila more magical color pieces.
[Captivate Android Development] solinar:
Same thing here.

I ended up flashing samurai kernel with odin and got things back to normal.
[Captivate Android Development] Jsmokey:
Flashed samurai from corn kernel or my red nebula kernel? Just trying to figure out where the issue is cause I haven't had any reports like this in my kernel's thread.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] space_eyes:
started from fresh install, rooted, then install fasty kj3 1.2, corn 3.07, rfs, everythings boots ok great, let sit for a while, then booted to CWM, installed new corn, phone reboots by itself (not sure if in middle of install or not? supposed to reboot?, doesn't usually). Then get wonderful boot logo, never leaves that screen, can still boot to new CWM, but no go from there...

EDIT:

**** happens.
[Captivate Android Development] mtcarey:
Looking into it... figures that there are problems when everything worked fine for me! :confused:
[Captivate Android Development] jsbac:
Same thing here -- stays at my boot animation screen (PC POST boot animation). What's strange is after awhile the screen will timeout (as others reported) and I can hit the power button to make the screen come on -- BUT, I can hear the notifications when I receive emails so it's partially working..

I am using Fasty kj2 V1.2 flashing over Corn Kernel 3.07 via CWM.

I was able to flash back to CK 3.07 with no problems.

jsbac
[Captivate Android Development] zas0006:
just thought I would say that I flashed via sgs kernel flasher and I am up and running with no issues. very snappy, great cwm options, all and all a very good kernel.
[Captivate Android Development] mtcarey:
Glad to hear it's working for someone!
[Captivate Android Development] Jsmokey:
For everyone trying this and getting boot anim loops once you're able to press the unlock button, slide to unlock like normal then turn the phone so it'd be in landscape mode and I bet you get a half screen with boot anim and half showing your homescreen. This is the exact same thing my kernel was doing when I was working on getting boot anims working. The system isn't sending a kill signal to the boot animation service is my guess.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] mtcarey:
It makes sense that it's something screwy with the boot animation... I just flashed this over 3 different kernels with no problems. I did just add a check for any broken "sanim.zip" links which might cause a problem. I also found a nasty typo in the routine converting the /data partition from ext4 back to rfs, which is now fixed. Download links will be re-enabled momentarily!
[Captivate Android Development] Jsmokey:
I don't know if you saw it but there's a line kyuta told me to put at the end of init.rc that will stop the boot animation when the system has finished loading all the way. That should fix it if it still happens after the changes you made.

My first tester for my kj3 version didn't have any problems with boot anim loops before I added the line to stop them but most everyone else did, its so weird how things work on a handful of devices and the rest all get the same issues. That's all part of development and debugging though.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] mtcarey:
I'll look into that. Funny, the boot animation stuff is unchanged from the previous version, and I had no complaints about that one.
[Captivate Android Development] prbassplayer:
Yup Boot anim gets stuck =/.
[Captivate Android Development] msprag13:
Tried to insert dropbox links but I am a low post newbie so I can't post links.

I'm not a troll XDA.
[Captivate Android Development] mtcarey:
If you click on my login name to the left you can send me a message or email.
[Captivate Android Development] jbabbler:
Just a quick FYI... Gave it a quick test with Fasty III V1 and got bootloop. BL splash---> Kernel ATT Splash---- Reboot. I ran the kernel cleaning script and removed and removed the old Voodoo folder on my SD from an old install of Apex. I am running I9000 BLs if that matters. I Odin Flashed orignial Book K1 and am working fine. Didn't lose anything. . I just downloaded the kernel a few mins ago so I assume it was the newest one. I can try again if you want me to try something else. I'm stoked about getting this working. Thanks for taking this on.
[Captivate Android Development] Kyuta Syuko:
Well looks like yet another I897 firmware was just leaked. Guess I'll drop the KI2 project and start working with KJ1.

Either way I gotta wait for my slow arse laptop...

*edit*

I wish there was a bit more documentation on how to build Voodoo from source...
[Captivate Android Development] cyberbandit1998:
Yes the kernel is bad stuck at Att no cwm had to use Odin to get phone usable
[Captivate Android Development] mtcarey:
I just now made a few changes and installed on Fasty III V1... works great now. Re-download and give it a shot (if you're brave).

P.S. Quadrant gave me 2216 with ext4 on Fasty.
[Captivate Android Development] jbabbler:
Very well done (fasty III v1. I'm typing this on out right now. Lagfix is enabled and every aspect of the rom is smooth. I'll keep dining out and report back. Thank you for this.
[Captivate Android Development] Geezer000:
How long did it take to convert.....i'm at 15min now. Trying it on FUSION VII beta 12. Just have black screen after ATT boot screen. No bootloops or anything, just going no where
[Captivate Android Development] mtcarey:
If you hear periodic "chirping" sounds it is converting. The ATT boot screen should be visible throughout the process. If you have a black screen make sure your battery didn't die... plug it into a charger.
[Captivate Android Development] Geezer000:
No sounds.....it just rebooted on me after 15min. Got back in to CWM and am disabling it and see if it will boot first and then convert with voodoo control app.

---------- Post added at 07:36 PM ---------- Previous post was at 07:23 PM ----------

No go with disabling it. Still bootlooping. Will have to try to reflash...
[Captivate Android Development] msprag13:
Tested on pinnacle 1.3 and so far seems fine. Jumped quad score from 1300 to 1900. Conversion took about 5 minutes tops.

Did my log files help at all.
[Captivate Android Development] jbabbler:
Mine took about 5 mins. I heard the Voo doo voice just like the I9000 Roms only really fast. Never tried Quadrant before now so i don't know good from bad but it said 2086.
[Captivate Android Development] mtcarey:
They helped in that they told me what NOT to look at. It turned-out I had two broken symlinks that needed repairing.
[Captivate Android Development] mtcarey:
I got the Alsa audio player binary ("aplay") from an I9000 kernel. Doesn't quite agree with the Captivate. I'll try to work on that, but at least it's some audible feedback.
[Captivate Android Development] Geezer000:
Tried with the ODIN and still nothing. I'm going to have to return to stock now because my cappy won't go past the ATT screen when trying a non-voodoo kernel. Hopefully it works.
[Captivate Android Development] jbabbler:
I personally couldn't care less what it sounds like.you only hear it once :)
[Captivate Android Development] msprag13:
Quad 2489 with tegrak at 1.3

And I can cook my breakfast eggs on my phone so it's a double win
[Captivate Android Development] Geezer000:
How did you guys get back up and running after a bad flash were it didn't work....
[Captivate Android Development] msprag13:
Bad flash

I just reflashed boogs base kh3 kernel via odin.

are you on i897 loaders or i9000?
[Captivate Android Development] Geezer000:
I'm on i897 and the boog base didn't work.

---------- Post added at 08:23 PM ---------- Previous post was at 08:18 PM ----------

reflashed pinnacle 1.2 and it works fine. I guess it has issues with FUSION
[Captivate Android Development] xpakage:
There is still problems. I am on Serenity and it is not working. Just black screen and goes back to the boot animation after a power button press.
[Captivate Android Development] Jsmokey:
Yep the animation is definitely not getting a signal to stop playing from the system. Like I said if you turn the phone so its in landscape and unlock like you normally would you'll get like a split screen of animation and homescreen because the system is actually running both but boot anim only can display an image about half as wide as the screen in landscape orientation.

I swear these boot anims have it out for all us kernel devs.

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
[Captivate Android Development] mtcarey:
Ok - animation problem fixed. My bad - I left out a line from init.rc when I cut and pasted from the previous version. Very strange that it didn't cause me any problems, though.
[Captivate Android Development] prbassplayer:
Nice rework on CWM. Going to give this Kernel a go. Thanks for all your hard work!
[Captivate Android Development] Squeaner:
The new version works great! Keep up the good work. Had the boot animation issue with 4.02.
[Captivate Android Development] Kyuta Syuko:
So everything in your recovery's working? If so mind if I drop it into my kernel as well? Credits to you of course.
[Captivate Android Development] xpakage:
4.03 is working :D
[Captivate Android Development] boog:
I was just thinking the same thing! mtcarey will be the cwm hero! :D
[Captivate Android Development] mtcarey:
Feel free to use it, though you might want to wait a day or so to make sure there are no other issues.
[Captivate Android Development] getinlost:
Ver. 403 working. I just converted to ext4. Waiting for full boot and now going to try going back to rfs.

Edit: Converted back to rfs fine. I like the battery stats while the process is going.
[Captivate Android Development] mtcarey:
Yeah, I added the battery level... thought it might be useful!
[Captivate Android Development] Jsmokey:
Man you really went nuts on cwm and everything this time around mt, nice work, almost makes me want to abandon my work on cwm....

Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.