yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] \/icious:
Anybody run quadrant yet? Im not running this unless its hitting 2000+

JK wer iz ma trout!

People are having minor issues LP. Has anyone tried ADW?
[Captivate Android Development] vunuts:
No, not on crack. I have all my teeth, thank you very much, but I did all that was stated in the OP and when it rebooted, it booted into a blank home screen. So maybe it was just my phone or maybe I just ****ed something up. Sorry for sharing my experience and undermining you oh holy greatness DG.
[Captivate Android Development] topshelf95:
Works great, flashed NP just like op says. Overall quite responsive but I've noticed some lag issues opening and closing things. Also very odd but my screen brightness keeps adjusting up and down when I'm using pretty much anything. Its even doing it as I type this. :D Gonna try adw for a bit see how that goes. Will report back. Keep up the good work DG!

PS I reverted back to stock and did a master clear to start over fresh before trying this out.
[Captivate Android Development] amwbt:
Does One Click Lag Fix have to be removed before applying this? That might be some of these guys problems.
[Captivate Android Development] Clienterror:
Same thing happend to me. I just started from a fresh recog beta7 and it worked great.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] PuffinNugz:
I keep getting Bitmap errors when trying to install and can do nothing beyond except reflash to stock.

Any ideas?
[Captivate Android Development] geokhentix:
Are there any plans to intergrate EXT4 support in the near future? EXT4 owns EXT2 so hard. :(
[Captivate Android Development] DOAlaboratories:
I can't wait for this.

Plus then, if we get bored enough, we can use OCLF on top of it like the i9000 guys did with voodoo ;)

Sent from my Cappy using mental telepathy, *****ezz.
[Captivate Android Development] Chief Beefalo:
Yea i wanna echo this... Not sure if these guys are disabling OCLF, uninstalling ext2 tools, and removing OCLF before they update.

I had no problems putting this on Cog b7 - LP.
[Captivate Android Development] SnakeHaveYou:
Can i use this Kernel with Shep211's Stock ROM without HSUPA? Now i'm using xcaliburinhand's Reoriented Kernel..
[Captivate Android Development] PuffinNugz:
I've not used OCLF since beta 3 or 4.
[Captivate Android Development] johnyhoffman:
Same thing happened here. Followed instructions in OP up until point where you reboot into recovery to apply the update.zip. When it rebooted gave the missing bitmap errors that quoted poster is getting. Tried pulling battery and rebooting 5 times. No luck. Only functional button in the recovery screen is the menu button and all that does is turn the screen off and on. Didn't find any solutions so am starting from stock. Will update on how things go.

This all happened using a clean install of CDEbeta3. No lagfix of any kind. Not a big deal since I just wanted to mess with it and get an idea of any actual speed increases. CDEbeta3 is pretty darn snappy on its own though.
[Captivate Android Development] DOAlaboratories:
Sent from my Cappy using mental telepathy, *****ezz.
[Captivate Android Development] geokhentix:
In recovery, your phone is adb-ready. All you have to do is type

adb reboot (in the tools folder of the SDK folder of course...)

and it'll boot up normally without recovery.
[Captivate Android Development] johnyhoffman:
Ah, didn't know that. Will give it a shot if I get back to that point and get stuck again.
[Captivate Android Development] smokestack76:
I know it gets old man but you have to watch your wording. Alot of n00bs here look up to you and follow you to earths end lol.
[Captivate Android Development] PuffinNugz:
Finally worked. Really did nothing differently this time. Re-dl'ed the kernal and Z4 package.

1. Went to stock JF6

2. Rooted

3. ODINed COG B6 (7 was giving me too many issues)

4. transferred z4zip to sdcard

5. installed RM, flashed CW

6. Flashed new kernal

7. RM to Reboot to Recovery

8. Install from SDcard.

Did all those steps 3x in a row. Finally worked.
[Captivate Android Development] amwbt:
Mine doesn't seem as fast as OCLF when reinstalling my apps. Is this normal? Anyone else notice? Or maybe it didn't work?
[Captivate Android Development] shaolin95:
Anyone using this with Shep211 10-15 ROM (non hsupa)?

Thanks!
[Captivate Android Development] Grif7:
What is cw?
[Captivate Android Development] PuffinNugz:
Clockworkmod recovery in Rom manager.
[Captivate Android Development] ice3186:
internet issues

Anyone else having internet issues, i cant connect to the internet after i run this!
[Captivate Android Development] johnyhoffman:
Ok. So adb definitely does not work when at the recovery screen I am stuck at. I know my way around adb and usb devices enough to know that the phone is not recognizable as a usb device when in this recovery screen. I am going to give this one more go here then maybe just say forget it. Just wanted to tinker with this, but not worth much more of my time. Will post exactly what is happening when I get done here.
[Captivate Android Development] msm903:
adb worked fine for me at recovery mode.
[Captivate Android Development] shoefly:
Just curious, but do you have usb debugging enabled? Try booting into the recovery without the usb plugged in and give it a couple of seconds
[Captivate Android Development] shoefly:
Change step 7 to flash rom from sd card from within rom manager gui instead of reboot into recovery and I think you'll find it went slot smoother ;-)
[Captivate Android Development] PuffinNugz:
actually, i did that the first two times. it worked when I did it how i posted.
[Captivate Android Development] Bowsa2511:
Doesn't voodoo v5 have a new method without using a recompiled kernel?

http://github.com/project-voodoo/lagfix

http://xdaforums.com/showpost.php?p=8690978&postcount=1
[Captivate Android Development] DJNgoma:
I'll be testing this now whilst trying a new ROM till CogYo Beta 8(or possibly 9) comes out. So it will be Shep211's JPM\JI6 ROM + z4mod for now :D. **Cross Fingers**
[Captivate Android Development] warri:
My launcher pro works fine
[Captivate Android Development] johnyhoffman:
I finally succeeded in getting the lagfix to run. I basically did as previous posters have done and kept trying the same thing over and over. Took 3 times for me as well ... weird. Adb is still not working in recovery for me. It works as it should at all times, but does not work at the recovery screen. Once again, weird. Thanks for the input and pointers though.

Now after playing with this mod for awhile it definitely does not have the feel that voodoo does with Eclair. Hope someone gets that going on our Captivates soon. Out of all the lagfixes/magic tricks, it's the only fix that has given me real world/use results that I could see.

Dropped w/ my Samsung Captivate using TapaTalk Pro
[Captivate Android Development] bts0uth:
Tip for anyone that can't get ADB to work, when your stuck on the recovery screen and the power button doesn't select anything do this:

1 -Unplug usb cable if it's connected

2 - Pull out battery

3 - Put it back in and leave phone off

4 - Plug in the USB cable and the battery image should appear to show its charging.

5 - Hold down the power button and it will start normally and not go into recovery mode.

6 - You can now use rom manager to get into clockwork

ADB kept saying device not found so I tried this and it went straight to the galaxy s screen and not recovery.
[Captivate Android Development] kangi26:
If you post quadrant scores I will hunt you down and slap you with a very large trout!![/QUOTE]

(Just thought it needed to be posted again. We don't want any trout slinging going on around here:D)
[Captivate Android Development] Pinepig:
Isn't it strange how they work on different phones. I've done all three ( Aosp, cog7 and the jpm/ji6 ) roms and have backups of all three in RM. The cog 7 even without the lagfix was obviously the fastest one on mine, decent battery life too. The AOSP ond JPM seem about the same speed ( quick but obvious lag ) and the AOSP rom is a battery hog ( and most folks say it's great ).

I guess it just shows that there is no one perfect rom, thanks to the devs for putting out so many different options. If one doesn't work for you well, just try one of the others and see how it works, hell they can can all be made to apear any way you want ( all three of mine look basically the same after I set them up the way I like them ).

I am looking forward to trying the cyan 6.1 when they get it running.
[Captivate Android Development] SnakeHaveYou:
(Just thought it needed to be posted again. We don't want any trout slinging going on around here:D)[/QUOTE]

You must stick this on every page of this!
[Captivate Android Development] tazman171:
At least you're using trout and not carp! ;)
[Captivate Android Development] tazman171:
Because I started a new page I shall re-iterate the declaration from DG. :cool:
[Captivate Android Development] bubbinator91:
Okay so the .zip that converts it back to RFS doesn't work. It doesn't show any errors during the update process (it just goes really fast), but the log file does. The phone isn't bricked, but the lagfix is still applied. Here is the code in the log file:

+ export PATH=/:/system/xbin:/system/sbin:/sbin:/system/sbin:/system/bin:/system/xbin
+ busybox cat
+ busybox date
###############################################################################
#
# Starting z4mod 'rfs' convert on /data (/dev/block/mmcblk0p2)
# Tue Oct 19 01:33:20 GMT 2010
#
###############################################################################
+ [ ! -f /z4mod ]
+ partition=data
+ devblock=mmcblk0p2
+ filesystem=rfs
+ [ rfs == ext ]
+ [ rfs == rfs ]
+ format_cmd=fat.format
+ [ fat.format == ]
+ busybox which fat.format
+ [ ]
+ halt
+ umount /data
umount: can't umount /data: Invalid argument
+ exit 1

Basically, I wanna un-apply it in order to properly flash back to stock with odin. Is it safe to do that even with the lagfix still applied?
[Captivate Android Development] johnyhoffman:
Ok restarted my phone 5 times just for kicks. Let it sit for about 5 minutes in between reboots. This thing is definitely snapping through apps faster than any other time I have been on a Froyo rom. Can't wait to see what happens once the cache on stuff builds up and starts to really fly. May not need to wait for that voodoo afterall.

Dropped w/ my Samsung Captivate using TapaTalk Pro
[Captivate Android Development] xfernand:
I'm still testing ASOP beta 3. I think I'll wait for the baked COG version.... or at least a couple of days to see what else the ASOP version comes up with....
[Captivate Android Development] Crizthakidd:
whats better to flash right now cogbeta7, the asop one or this lmao ugh decisions decisions
[Captivate Android Development] MikeyMike01:
You can mix and match kernels with ROMs.

This kernel will work with both AOSP, and Cognition Beta7.

As an aside, do yourself and enormous favor and set up ClockworkMod BEFORE you flash the kernel. That means boot into it once using ROM Manager.
[Captivate Android Development] alexmullins:
How did yall get passed recovery after installing the new kernel in odin? Ive tried the suggestion of pulling the battery and plugging in the cord so that the battery charging screen shows up and pressing power but that just puts me back into recovery.

EDIT: nevermind. I forgot to setup ClockworkMod before i flashed the kernel as suggested above. Doing that fixed it and boot up.
[Captivate Android Development] NeoXerO:
okay, so how do I know that this properly installed?

I can't really see THAT much of a speed difference so I want to be sure I did it right.
[Captivate Android Development] Dani897:
Yeah some people are little over enthusiastic. If you flashed the kernel and ran the .zip and it took a long time it probably worked. I'm not sure of a good way to test it though. Other than, dare I say it ....

...quadrant standard..

Just to verify there is a speed increase in the file system, you may be surprised at how not fast this is rated in quadrant, its not like the one click.

Remember quadrant score are irrelevant comparing different phones, or even the same phone with different mods.
[Captivate Android Development] cruiserbax:
What do I need to modify to make the ext2 update convert ALL of the partitions instead of just /data? or is /data where the main OS/apps reside?
[Captivate Android Development] shoefly:
in a terminal emulator from the market put this " mount | busybox grep ext2 "
[Captivate Android Development] aqtrans:
Heh, just do what ^^ said.
[Captivate Android Development] Dani897:
Yeah I need to familiarize myself with linux commands.
[Captivate Android Development] magnumrt562:
My market vanished after i ran this via RomManager...

DG the quadrant was only 1536... :eek: My daughter was watching Blue's Clues all day so getting smacked with a trout is an improvement...

IMHO, the performance was the same...

Im sticking with: Cog 2.2 BETA 6, JG8 Modem, and NO LAGFIX!!!!!!!!!!!!
[Captivate Android Development] chrisharmful:
Well, it installed without any problems for me so that's a good thing. Seems snappier, almost like voodoo on the older Cognitions. Just one snag though, think it's affecting my GPS, seems like it took longer to get a lock, willl test it further tomorrow. Otherwise, happy with it so far.
[Captivate Android Development] MikeyMike01:
If you're dumping this based on a 1500 quadrant score, you're crazy.
[Captivate Android Development] bts0uth:
Is this what it should say if its working?

export PATH=/data/local/bin:$PATH

$ $mount | busybox grep ext2

/dev/block/mmcblk0p2 /data ext2 rw,nosuid,nodev,noatime,nodiratime,errors=continue 0 0

$

Posted from my Captivate
[Captivate Android Development] in_nujerz:
Can we please have this kernel as an update.zip place?
[Captivate Android Development] MikeyMike01:
That's what mine says.
[Captivate Android Development] WickedStyx:
If you're using apps that cause it to lag like a mofo even with OCLF (eg Touchdown, Feedr, BeyondPod, etc) the difference will be incredibly obvious. If not, well be happy :)
[Captivate Android Development] MikeyMike01:
I wonder what would happen if you did the OCLF on top of this...
[Captivate Android Development] WickedStyx:
I read elsewhere that /system is already mounted in recovery so this is not easy. /data is where all the apps you install reside and I think the cache as well. /system is where the OS and core services and apps (like twlauncher, phone app, contacts app, etc.) reside
[Captivate Android Development] aqtrans:
Looks like all that needs to be modified to format the other partitions as ext2 is the "updater-script". The z4mod program the script runs takes the "partition" and "devblock" to be formatted as an argument, and right now it's "data" and "mmcblk0p2".

Here goes nothing... :p
[Captivate Android Development] eclypse3demons:
This did not work after I plugged the usb cord in, it went to the battery screen then immediately booted into recovery mode, the top of the screen is the blue recovery options below that in red is:

E:Missing bitmap icon_installing

(Code -7)

E:Missing bitmap icoc_error

(Code -7)

Then in yellow below that:

#Manual Mode#

--Appling Muti-CSC...

Installing Muti-CSC

Thats it just sits at that screen every reboot, no options work from the top, and adb commands do not work... =( any ideas? Does it take a really long time from the above message regarding Installing Muti-CSC or is it not doing anything right now I cannot do anything with the phone to recover....

*****Update*****

Ok after much trial and error I determined it was not getting past the point above.

Figured the following.

1. Start Odin (I am using I897UCJI6-OCD-REV02-Low-designgears.exe)

2. Remove the Battery, sim, and ext sd card.

3. Reinsert the battery

4. Hold both Vol up and Vol down only (Not power button)

5. Plug in USB - Hold till you get the droid and shovel pic for download mode - then Odin should detect it.

From there I just flashed back the build that was working previously....

So here is my question do I even need the new Kernel? with my flash and can just do the mod portion of it with the ext2.zip??

"phew" was freaking out =)
[Captivate Android Development] justflorin:
Probably a stupid question considering how many times I have a flashed my phone, I need to know the right response regardless, flashing the kernel over 2.2b6 will force me to re setup my phone or not? I've got a few programs that if I reflash the will reset and I've worked too much to do that for now, thanks
[Captivate Android Development] MikeyMike01:
Of course you need the kernel.
[Captivate Android Development] eclypse3demons:
Just checking I am not a programmer I know what the kernel and I of course know what this thread is about and how it works, just was curious if I was already running 2.2 if it was not already in there =)

Right here <====== Noob :D
[Captivate Android Development] shoefly:
Yes your on ext2(z4mod)
[Captivate Android Development] PuffinNugz:
That's what was happening to me. But third or fourth time was the charm.

My steps...
[Captivate Android Development] Chief Beefalo:
All your settings/programs will stay intact.

Good luck
[Captivate Android Development] eclypse3demons:
Ok some questions cause I was not able to get this going I reproduced the same issue 3 times.

4. transferred z4zip to sdcard (did you rename the zip file? or just put it in as is)

5. installed RM, flashed CW (did that)

6. Flashed new kernal (did that)

7. RM to Reboot to Recovery (I did not do this I did install from SD at this spot which brings me back to below question)

8. Install from SDcard. (see question on #4 above)

I think I am missing something with the process.

-D
[Captivate Android Development] Chief Beefalo:
It doesn't have to be renamed... it can be named anything.

It looks like your steps are correct... so when you reboot into recovery after flashing with odin, and you try and install from sdcard what happens?
[Captivate Android Development] eclypse3demons:
E:Missing bitmap icon_installing

(Code -7)

E:Missing bitmap icoc_error

(Code -7)

Then in yellow below that:

#Manual Mode#

--Appling Muti-CSC...

Installing Muti-CSC

These are the steps I took

1> had to recover my working install of 2.2 so I put the phone in download mode then using following rom.

I897UCJI6-OCD-REV02-Low-designgears.exe

2> Rooted the phone by putting in debug mode and using SuperOneClickv1.5.1-shortfuse.

3> Install Busybox, ClockworkMod, then flash Clockwork recovery.

4> Put USB data in storage mode and copied z4mod.ext2.update.zip to the root of the SD card.

5> Reboot phone and put it back into download mode, and installed Kernel.tar to PDA via ODin.

6> On reboot I used CM and put phone into recovery mode, then I get the problems, I also tried installing from SD from that program and also got the same problem.

CM reboots and I get the recovery menu and the below text and the system does not go anywhere. Then it requires me to complete step #1 again..

E:Missing bitmap icon_installing

(Code -7)

E:Missing bitmap icoc_error

(Code -7)

Then in yellow below that:

#Manual Mode#

--Appling Muti-CSC...

Installing Muti-CSC (stops here and hangs)

I am not sure if it has to do with how I am transferring z4mod.ext2.update.zip to the SD card and permissions or if there is still a previous update.zip still sitting in the root of the SD.

I am just not sure what I am doing wrong.

Above that is the blue recovery menu none of it is useable..

^after rebooting into recovery I do not get any option to install from SD card just the text above your quote. I cannot do anything.

-D
[Captivate Android Development] crupp:
Is this a permanent fix? or can this be backed out if someone wanted to do that?
[Captivate Android Development] Chief Beefalo:
have you tried flashing clockwork mod recover before flashing with odin? Sometimes CWM doesn't reboot into recovery the first time you try and run it. So before you go through odin, or maybe even after, go to CWM and "Flash Clockwork Recovery", then select "Reboot into Recovery". If you get into recovery without problems, reboot, open CWM and select "Install Rom from SD card" select the z4mod, and let it reboot.

You may have already done this whole process, but i just wanted to make sure that you had rebooted into CWM recovery once befroe you started this trying to install.

In the OP, he included an updated.zip for un-doing the mod.
[Captivate Android Development] crupp:
Sorry, missed that. thanks
[Captivate Android Development] crupp:
Does anyone have a zip of the Kernel. No access to multi at work. Thanks
[Captivate Android Development] silversleeper:
I had this same issue when attempting to get into recovery mode. It seemed to get into the stock recovery mode, but I couldn't select any of the options to get my phone into Clockwork. I ended up flashing the kernel again, then booting up the phone and running Rom Manager. From there instead of choosing Reboot into Recovery, I selected Install ROM from SD Card.

That actually got the update running properly. It took quite some time though, I almost thought it froze about 2/3 the way through. I don't think I'm out of the water just yet though, because after the reboot (after the update.zip ran) it booted to the AT&T splash screen followed by the Galaxy S animation. Then I got left with a blank screen, but still active as the bottom button LEDS are lit.
[Captivate Android Development] eclypse3demons:
Ok so are you saying before I flash the kernel to flash CM recovery, then do reboot into recovery to see if it works first, then go back and flash the kernel with Odin, then go back to to CM and install from SD....

And thanks for your time its appreciated..
[Captivate Android Development] Chief Beefalo:
Yes.... Flash clockwork mod and reboot into clockwork recovery just to make sure recovery through cwm is working before trying to install. If you didn't do this, it is likely the source of your problem.
[Captivate Android Development] eclypse3demons:
Ok so I did the following

Installed froyo 2.2

Installed Busybox, Clockwork Mod, Rooted phone. Rebooting after all.

Flashed ClockWork Mod recovery, then selected Reboot into recovery mode.

Phone rebooted into recovery mode (3e) no problems, all menus were available. rebooted the phone from the menu back into OS.

Installed the new Kernel.tar via Odin. Rebooted.

Ran Install from SD card from CM, Phone rebooted, and still the same problem

Phone sitting at

E:Missing bitmap icon_installing

(Code -7)

E:Missing bitmap icoc_error

(Code -7)

Then in yellow below that:

#Manual Mode#

--Appling Muti-CSC...

Installing Muti-CSC (stops here and hangs)

ugh...
[Captivate Android Development] Chief Beefalo:
hmmmm... very strange.

I don't know what this error is. I didn't have this happen flashing from Cognition Beta 7. You could try Flashing Cog (i would encourage it strictly because it is awesome) and going going from there, but otherwise, i am not going to be much help. Also, i think DG has said that he will be integrating z4mod into Cognition Beta 8, so you could just wait for that in the next day or 2.

Sorry for your trouble.
[Captivate Android Development] eclypse3demons:
So do you think I am doing the proper steps them it may just be some fluke issue with my build?
[Captivate Android Development] Chief Beefalo:
It looks like you are doing the steps correctly to me.
[Captivate Android Development] geokhentix:
The stock recovery in this kernel is a bit borked, as DG said in the OP. As many people have said in the previous pages, you can't select reinstall packages with the kernel. If you're getting stuck boot-looping into recovery, let it sit on recovery, plug in usb, and adb reboot. That'll boot the phone back to normal.

For the rest of you reading this who are skeptical and thinking about trying, do not use Install from SD Card. Instead, use Reboot into Recovery and let it do it's thing. Once you're in clockwork, install it via SD Card from there. This will prevent the bootlooping.
[Captivate Android Development] shoefly:
Redownload the kernel or goto the original z4mod thread find my post with my kernel and try again