yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] designgears:
I hate you wArri atinm, I just got Voodoo into my custom kernel...

Ok, well, guess this is no longer being worked on, I feel better now..
[Captivate Android Development] Chief Beefalo:
oh snap!

Flashing time again. mmmmmmm

THANKS!!
[Captivate Android Development] atinm:
I'm working on CyanogenMod6 for our phones and this happened to by on the way there because I was futzing in recovery so I put it out as ppl seemed to be asking for Voodoo support in Froyo. If it doesn't work for you, don't worry - the performance difference between stock RFS and Voodoo on Froyo isn't as significant as it was with Eclair (the 'Q' number is near 1400 rather than above 1700 - I guess still somewhat better than stock).

-Atin
[Captivate Android Development] designgears:
haha, he posted this right as I finished up my Kernel, was about to update to beta9... heh
[Captivate Android Development] mcx6:
Thanks again you warri and atimn for all your hard work and help, will be applying this to my setup.
[Captivate Android Development] atinm:
It's cause I'll do it a whole different way next time. But don't let me stop you from working on the kernel, the more ppl who take up the slack the better so I can focus on what I need to work on (CyanogenMod!).
[Captivate Android Development] airbillion:
Are you still going to post beta 9? I can't wait to try it!
[Captivate Android Development] designgears:
yup, just doing some final testing
[Captivate Android Development] rob989_69:
AHHHH Thanks a million. I've been waiting for this since Froyo hit. Looking forward to B9 DG. Thanks for all the hard work guys!!
[Captivate Android Development] Bowsa2511:
You can work on the colorfix, and I believe you had the bootanimation.zip incorporated into your kernel?
[Captivate Android Development] Kaik541:
colorfix can't be done without sources and this kernel will have aosp bootanimation.zip support soon as well.
[Captivate Android Development] Kaik541:
and speak of the devil, anyone wanting AOSP boot animation support, use this kernel here:

http://github.com/downloads/atinm/captivate_multistage_initramfs/cwm-ext4-v1.14.zip

same as above, flash in CWM, place any WVGA bootanimation.zip in either /system/media or /data/local
[Captivate Android Development] Bowsa2511:
That's right.. can't wait for our froyo source :)

Is that a ext4/lagfix + bootanimation kernel only?

Is it 2.2, and does it have recovery 2e?
[Captivate Android Development] nammyczc:
Does that mean we can use custom boot animations now?
[Captivate Android Development] atinm:
All of the above. But CWM recovery is default, you can boot into 2e if you want from that. I prefer CWM recovery as my default, so that's how it is.
[Captivate Android Development] Bowsa2511:
With bootanimation support.. I assume unsigned .zips are supported?
[Captivate Android Development] DOAlaboratories:
It seems to hate clockwork... it won't install no matter whick way I flash it in clockwork

sent with mental telepathy

(CDE ROM + OCLF +z4mod)
[Captivate Android Development] Kaik541:
these two things are unrelated, bootanimation.zip goes on your phone, unsigned zips are run from recovery. this kernel as clockwork as the default recovery.

works fine for me, but you can also try renaming it to update.zip and trying that way... the only way to tell if it's working is with a custom boot animation or verifying the output of build.txt in the root of the phone
[Captivate Android Development] DOAlaboratories:
no dice that way either.all the update-script text comes up, says it's done flashing the kernel, and then reboots, but the name of the kernel doesn't change. plus when i tried as update.zip it stuck at the boot screen and i had to flash an older kernel to get it to boot.
[Captivate Android Development] loserskater:
It worked for me using stock recovery but not clockwork. I already had a boot animation waiting, so the reason there wasn't a boot animation is probably because you didn't have one in /system/media. Or it was converting to ext4. Try it again and wait a couple minutes.
[Captivate Android Development] Delwyn:
DOAlaboratories,

Did you find another way to get Voodoo working with CDE AOSP? I'm just asking since that's the setup you have on your sig. I tried several times to apply this Voodoo to CDE AOSP and no dice. Thanks for any input you have.
[Captivate Android Development] DOAlaboratories:
Yeah, I used the reorient kernel. There are problems with the hsupa though.

sent with mental telepathy

(CDE ROM + OCLF +z4mod)
[Captivate Android Development] Delwyn:
Awesome! Thanks for your help!
[Captivate Android Development] kannonball2290:
can someone help with the custom bootanimation.zip? i downloaded a wvga boot animation and put it in system/media after i flashed the kernel with clockwork and i got nothin just stock.. any ideas?
[Captivate Android Development] RKight:
Same here. I tried installing this via both Clockwork and as an update.zip via 2e recovery. I have tried putting bootanimation.zip in both /system/media and /data/local but I just get the stock boot animation every time.
[Captivate Android Development] Demented71:
I've given up for the time being on the bootanimation thing. I downloaded one, and it works fine, but when I put one of my own, it shows the AT&T screen then goes black until it reaches the homescreen.

I actually have another, more important issue. My Widget Locker comes up pretty quick, but when I slide to unlock it, it's a black screen. When I hit the power button, I have the lockscreen again, and same thing happens when I slide to unlock it. It seems it takes forever for Launcher Pro to get going or something. Could that be because the kernel is launching TWLauncher first, and then finally Launcher Pro?

I'm gonna delete TwLauncher via TiBu, and see if that speeds up Launcher Pro.

Other than that annoyance, this kernel is pretty sweet. Will definitely hold me over until I see what DG has cooking...;)
[Captivate Android Development] opcow:
I'm not getting Voodoo when I install this in my Cog 8.1 rom. Not even sure if my kernel has changed--says 2.6.32.9 jetaek.lee@sep-11 #1.

(sep-11 #1 wtf I've installed the al qaeda kernel!)

Anyway, 'mount | grep ext' show nothing and there was no Voodoo folder created on my sdcard (not sure if it creates it or if I have to).
[Captivate Android Development] Demented71:
Yeah I'm pretty sure I heard the robot chick say "Conversion Successful", but I don't have a voodoo folder either. I'm about to flash Cog beta9, so I asked there as well on how to disable the lagfix if I need to. I always flash to stock then format anyways, so I'm not even sure if it matters. Guess I'll find out in a little bit...heh
[Captivate Android Development] atinm:
To disable lagfix - you'll need to create /sdcard/Voodoo and put disable-lagfix in there. This is a mixed release because it was part of something else I am doing and wasn't really going to follow the Voodoo method and added the Voodoo/disable-lagfix checking at the last minute.

Again, if this doesn't work for you, don't worry about it. The performance difference isn't significant compared to stock on Froyo unlike with Eclair.

-Atin
[Captivate Android Development] warri:
I believe Atinm removed the Build.txt file creation in the latest.

But if for some reason it doesnt flash for you, try again, Boot into recovery and flash from there, then reboot.
[Captivate Android Development] loserskater:
Can't wait for that day to come!
[Captivate Android Development] warri:
Boot animations work perfectly ;)
[Captivate Android Development] atinm:
I use the stock CWM recovery I install with this kernel as my Nandroid Backup and Restore application rather than doing it via ROM Manager. It allows me to backup/restore while still in lagfix mode so there is never a reason (for me) to convert back to RFS mode. I also added a "Reboot into 2e Recovery" as well as a "Reboot into Download" for people who want to use 2e recovery (you would need to convert back if you are going to be installing 2e specific stuff). The "Reboot into Download" just puts you in Download mode without having to go through the 3 button contortions . . .

-Atin
[Captivate Android Development] abacon15:
So whats the verdict on this? Is it plain awesome? Is it buggy? Does it kill the battery?
[Captivate Android Development] NiXXeD:
Working good for me.
[Captivate Android Development] NiXXeD:
Had version 1.14 on my phone, and my friend wanted this as well so I gave him the 1.15, doesn't appear to install voodoo.

I didn't hear voices while booting, and it booted quite fast.

Also checked from terminal emu, mount and /data is still rfs.
[Captivate Android Development] schtuka:
Thanks, I will try .14 first.

Hmmm, flashed it as an update.zip. Got to see android bootanimation, but no voice converting to ext4. It is captivate kernel I had reoriented w/e-recovery before. Booted fast. System is still RFS......

I can open CWM recovery, which means it applied it, but no voodoo. I'll give a try to .15

I am dumbass. I forgot disable-lagfix from Tayutama's Rom I just came from.
[Captivate Android Development] NiXXeD:
Ok after some playing in #cognition we got it to work. I tried both as 2e recovery update.zip and in CWM and neither would work. We found the logs looked ok, everything ran, but didn't actually write the zImage. Kaik said it sometimes runs too fast/early before it's done unpacking?

Anyway we ran /sbin/bmlwrite /tmp/zImage /dev/block/bml7 from CWM recovery after I installed the zip and it worked just fine. Weird.
[Captivate Android Development] rajendra82:
Based on your post I tried to patch in 1.14 from ROM manager, and on my first boot no conversion from RFS->ext4. So I rebooted into recovery and got stock 2e recovery, so obviously it had not taken. So while there, I decided to launch a CWM session, and reapplied 1.14. On the next reboot I got the voodoo voice about converting data partitions now, which is where it 's at. Looks like that's what needs to be done. I am going to try 1.15 using that method too.
[Captivate Android Development] DJNgoma:
I see there is 1.16... What are the changes?
[Captivate Android Development] rajendra82:
Man for an unsupported kernel, this is surely getting updated a lot :)
[Captivate Android Development] DJNgoma:
Yep, how I love the Captivate community. Just so many updates :p.
[Captivate Android Development] schtuka:
Sooooo, I had my fun with this kernel, made nandroid of my Froyo now with voodoo and want to come back to I9000 Tayutamas rom which is with voodoo fix too. Can I just restore I9000 voodoo rom over this voodooed kernel? Or should I go the usual; disable-lagfix in voodoo folder?

Thanks.
[Captivate Android Development] onesun43:
I can't get the kernel to take with either CWM or 2e recovery. I don't have bmlwrite because I'm on CDE4. I tried the same method using redbend_ua per the last line of the updater-script. It does the exact same thing as just applying the zip with CWM, big-text-blue-screen-flash but no new kernel. Here's my output from redbend_ua. Any suggestions?

~ # /sbin/redbend_ua restore /tmp/zImage /dev/block/bml7
/sbin/redbend_ua restore /tmp/zImage /dev/block/bml7
RedBend Update Agent 6,1,14,1

FOTA : Make Block Device Nodes
UA/(MakeBMLNodes): mknod path=/dev/block/bml4, dev_no=35076
UA/(MakeBMLNodes): mknod path=/dev/block/bml5, dev_no=35077
UA/(MakeBMLNodes): mknod path=/dev/block/bml7, dev_no=35079
UA/(MakeBMLNodes): mknod path=/dev/block/bml8, dev_no=35080
UA/(MakeBMLNodes): mknod path=/dev/block/bml11, dev_no=35083
lcd_init(498): start!
lcd_init(507): fb0 open success
lcd_init(514): width = 480, height = 800
UA/ check_existence: /data/fota/delta.Sbl
UA/(update_all): Check Delta : path_idx(0), part_idx(0), file_path((null)), cnt(0)
UA/ check_existence: /data/fota/delta.zImage
UA/(update_all): Check Delta : path_idx(0), part_idx(1), file_path((null)), cnt(0)
UA/ check_existence: /data/fota/delta.modem
UA/(update_all): Check Delta : path_idx(0), part_idx(2), file_path((null)), cnt(0)
UA/ check_existence: /data/fota/delta.platform
UA/(update_all): Check Delta : path_idx(0), part_idx(3), file_path((null)), cnt(0)
UA/ check_existence: /sdcard/Android/data/temp.fota.delta/delta.Sbl
UA/(update_all): Check Delta : path_idx(1), part_idx(0), file_path((null)), cnt(0)
UA/ check_existence: /sdcard/Android/data/temp.fota.delta/delta.zImage
UA/(update_all): Check Delta : path_idx(1), part_idx(1), file_path((null)), cnt(0)
UA/ check_existence: /sdcard/Android/data/temp.fota.delta/delta.modem
UA/(update_all): Check Delta : path_idx(1), part_idx(2), file_path((null)), cnt(0)
UA/ check_existence: /sdcard/Android/data/temp.fota.delta/delta.platform
UA/(update_all): Check Delta : path_idx(1), part_idx(3), file_path((null)), cnt(0)

fail!
Open /data/fota/fota.status
fsync after write: 0
reboot returned
~ #

*EDIT: I tried redbend_ua with the 1.14 version and it worked. It's weird that the 1.14 zip comes with bmlwrite and the 1.17 zip comes with redbend_ua. bmlwrite doesn't seem to work with either version, and redbend_ua only works with 1.14. I too would like to see a changelog.
[Captivate Android Development] bubbinator91:
Damn already at 1.17. Is there a changelog somewhere?
[Captivate Android Development] aqtrans:
Just to report my experiences, I first flashed this kernel a day or two before this topic was posted, flashed v1.0, (I monitor wes and atinm's githubs to keep an eye on the CM6 progress :p), and it has been working great until today.

I shut down my phone earlier, and from then on it would not boot any further than the AT&T World Phone screen. Was able to obtain a logcat, it seemed to be stalling because /data wasn't mounted. I thought all my data was gone, but after booting into recovery and reapplying the 1.14 update, it booted up fine, with my data intact :) Quite a weird occurrence, but with such an easy "fix", I'm not complaining.

On another note: It seems like all versions prior to 1.14 were removed from his download page, anyone know why?
[Captivate Android Development] Kaik541:
guys, the "unsupported" part of this doesn't mean development has stopped or stalled, it means do not expect things like changelogs or walkthroughs. me and warri can help you troubleshoot, but installing this is done so at your own risk with no promises it will work.

1.16 and 1.17 contain redbend as a way to flash, but it is broken, the kernel is identical to the one available in 1.15.

The one everyone should be using is 1.15. If you are flashing and cannot get it to work, here is what you do. (again, this only applies with 1.15):

1) boot into clockwork mod recovery

2) install the zip from sd card

3) DO NOT RESTART

4) connect the phone through USB, "adb shell" to gain access (if you do not know how to do this, please do not try to use this kernel)

5) write into the shell "/sbin/bmlwrite /tmp/zImage /dev/block/bml7" **this can only be done in recovery after running the zip but before rebooting**

6) reboot

after performing the above, the kernel should work. the kernel does not create a "Voodoo" folder on your SD card, simply add it and the disable-lagfix file to disable. this kernel also does not change the information in "about phone" so it will still read jteak.lee sep-11 #2 (or whatever it is) of the stock kernel.
[Captivate Android Development] opcow:
I've looked on github, but I don't see anything but the 1.14 build. Where are the later builds people are referring to?
[Captivate Android Development] xfernand:
So here is the strange part. I successfully install v1.15 but never got to hear the voodoo conversion message and I keep trying time & time again including the method above. As I'm about to give up I place the "disable-lagfix" in the voodoo directory, reboot and I get the message of conversion back to RFS so I had voodoo all along!!. This means I have the updated recovery as well where I can backup with voodoo on? I also get the new bootanimation. I would be great if someone can confirm.

Thanks.

Edit: I still see only ClockworkMod Recovery v2.5.1.0 when I boot into recovery.
[Captivate Android Development] warri:
Your supposed to see CWM v2.5.1.0 .. thats the version Atinm has baked into this kernel.

Thats correct, if you have the boot animation your flash was successful.. you can replace that with any WVGA bootanimation.zip to /system/media and /data/local
[Captivate Android Development] xfernand:
Thanks! works great. Spent 2 hours resolving a non-issue. :D Most of my concern was with doing a proper nandroid.

For anyone that may have doubts on the Voodoo backup, just do 1 with Voodoo and 1 w/o. The files size should nearly identical, meaning all your data made it in...

Great work guys... Thanks.
[Captivate Android Development] rajendra82:
So should this new 1.18 be flashed or not?
[Captivate Android Development] Kaik541:
like has already been said, everything you flash i at your own risk and you will not be receiving changelogs or explanations of new zips
[Captivate Android Development] atinm:
I just put up versions for Kaik to test - and I frequently delete older versions if I find them buggy. 1.18 is actually a better version of CWM (the previous one was backing up your external sd card too). But 1.18 still has trouble flashing the kernel for some people and as this is recovery related, and I am working in recovery - I tend to update this too if I fix something in recovery.
[Captivate Android Development] rajendra82:
Hey atinm, I appreciate your great work. My comment was not directed at you specifically but at an earlier post by the OP that said we should all be only using 1.15 despite the availability of 1.16, and 1.17 subsequently. Since the OP seemed to have more knowledge about the differences in version numbers, and what they were for. I was wanting his opinion on whether the new version was recommended for flashing by us (similar to 1.15), or meant a private release for the testers (similar to 1.16 and 1.17).
[Captivate Android Development] Kaik541:
1.14 will (for now) stay up as the "stable" version... anything after that can be considered experimental. if a new version comes out that is "confirmed stable" (relatively), the older ones will be removed. Basically stick with the lowest numbered version available on the github, atinm will remove the lower version if a newer one becomes "stable."
[Captivate Android Development] id10terrordfw:
That's good to know about the external SD, as I have a nearly full 32GB micro SD in there...
[Captivate Android Development] irtehun:
I cant seem to get either version of this to work. for some reason it will not write the kernel.
[Captivate Android Development] opcow:
Did you see this post? I followed those instructions when installing 1.14 on Cognition b9 and it worked.
[Captivate Android Development] killeen1980:
How do i know if i flash the kernel correctly?????

Hi guys, i just flash this kernel using rom manager. I can't find the voodoo folder in my system file, the phone seem faster but i'm not sure if i flashed it correctly.

How do you know if you flash it right???? The kernel version is " 2.6.32.9 jetaek.lee@sep-11 #1 " can some one point me in the right direction. :confused:
[Captivate Android Development] uiskibum:
i'm pretty sure all of this has been answered in some for or another in this thread, and its not even that long.

The kernel install method does NOT create the Voodoo folder, you'll need to do that yourself if you want to disable. Did you hear the "voodoo voices" after you flashed it? Yes=successful No=not successful

atinm did not update the build.prop to reflect using his kernel, so what you see is "stock", if you have adb execute the following

adb shell
mount | grep ext4

if you see any entries listed it worked, if not it did not wwork
[Captivate Android Development] rajendra82:
For those of you still using this, version 1.19 based on injecting a multistage initramfs into the JJ4 kernel is up. The lack of a multi-stage voodoo kernel was holding me back from JJ4 until now, and 1.19 seems works well together with the new leak so far.
[Captivate Android Development] droid330:
just flashed this-works fine on my captivate so far-added a cool boot animation also,but i had a new bootup sound and lost it during flashing...will figure out how to get it back:confused:
[Captivate Android Development] Kaik541:
this kernel does not support "PowerOn.wav"
[Captivate Android Development] droid330:
thanx for repling-spent a couple of hours trying to get my startup sound back until i came back here to read the latest posts....
[Captivate Android Development] leezrd:
thanx for teaching me how to change boot animation running cogn. 2 v. 3b6
[Streak 5 Q&A, Help & Troubleshooting] leadguy68:
I was successful at getting it to 2.1 from 2.2.

However, i had issues getting it to the O2 1.6 rom, i ended up using clockwork and the .zip rom of 1.6 and it flashed successfully. However, upon boot i was stuck at the dell screen.

After this i tried all recovery images to get back to 2.1 or a workiing 1.6 install with no avail.

Now im stuck with out being able to do anything but flash recovery images, but cant install a update file because it isnt recognizing my SD card after removing it for some reason.... i tried multiple cards with no luck either.
[Streak 5 Q&A, Help & Troubleshooting] leadguy68:
Oh and to be clear, I am currently on the Build 4399 (rooted, intended for O2 devices) rom with the corresponding clockwork recovery installed. Can not access my SD card now tho.
[Streak 5 Q&A, Help & Troubleshooting] dkwelton:
This just happened to me! Toto modaco and download stock recovery Tom and flash it with fastboot and then you will be able to do why you want
[Streak 5 Q&A, Help & Troubleshooting] leadguy68:
Yeah i was able to use fastboot to flash someones nandroid backup of 2.1 and get it to finally boot.

I however am stuck back at 2.1 and cant flash 1.6 with out the same thing happening. I have SD card access once again tho.
[Streak 5 Q&A, Help & Troubleshooting] spences10:
You need the modded stock recovery

http://www.megaupload.com/?d=8LDVERY4

I used this to downgrade before a warranty repair, worked for me :)
[Streak 5 Q&A, Help & Troubleshooting] jmr144k:
Which 1.6 build is this used for, O2 1.6 or US 1.6 6601 build?
[Streak 5 Q&A, Help & Troubleshooting] Turbozilla:
This recovery image is to used to get you from O2 2.1 build 8105 to O2 1.6 build 4399. It worked for me after several days trying various guides and suggestions on other threads and sites.

I used this recovery image to Flash ROM Streak_104_4399_21.pkg which can be found on other threads.

-Christopher
[Streak 5 Q&A, Help & Troubleshooting] kanjimaster:
That modded recovery bricked my streak I'm tryin to get back to 1.6 everytime i run this recovery after downgrading to 2.1 from steves 2.2, I have tried several recoveries and nothing seems to work so stuck on 2.1 atm.

(oh btw I used QDL streakfash to unbrick I dunno if that helps anything.)
[Streak 5 Q&A, Help & Troubleshooting] vijay555:
It may not be relevant, but I had huge instability with my ROMs for a while, random hard resets, force closes, ROMs not taking properly etc, failed flashes even with 1.6 etc.

Turned out I had one of the bad batches of Streaks with a bad internal MicroSD card. I sent it back to Dell, they replaced the card, and all was well again. Perfect stability etc.

You can confirm this on the diagnostics menu.

V
[Droid Eris Themes and Apps] jerryrp:
I found a good app that helps out with GPS while using Cardio Trainer running app.

In the past it always seems that my GPS logging was never consistent and always throwing me off route thus creating some extra mileage to my runs.

It's in the market called "Tracker Booster"

I ran two days and same route and was only off by approx 50 feet.

Used on my Droid Eris running 2.1 Tainted VanV14 one day and Tazz Froyo v14 2.2 on the next day and came up with similar results.

You could prob use this app with any application that uses the phone's GPS.
[EVO 4G Accessories] Blitzpwnage:
WELL HERE YOU GUYS GO!

Still not sure if this will play out as it says but I am hoping that it does!

Also Best Buy took the Otterbox Defender down from their site. As to why I am in the dark as much as you guys! :confused:

Still 11/15 at least we have a small chance and a glimmer of hope! :D