yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] shadow65781:
Yes i havedone everything that you guys have suggested thanks for your responses i do apreciate your assistance
[Captivate Android Development] Atheistnofaith:
Awesome!

Hey everyone I have applied the patch, 'over' the stock kernel without any problems. The device access time speed up greatly, I have bechmarked the device before applying the patch and after. Using Quadrant Standard, after the patch the device out benchmarks the Nexus One(froyo 2.2) and even the standard Galaxy S class phones stored in there online database. Wow guys great job on the dev, keep up the great work!
[Captivate Android Development] jslee1020:
Ok... so the only thing that I can gather is wrong is the external SD card. I'm using a class 4 16gb sandisk microsdhc... and I formatted on the PC to fat32. Has anyone tried with other formats? (extfat?)

Have you tried w/o external SD installed?? Does the internal SD show up quicker/without problems?

I tried with USB debugging on... but performance is similar.
[Captivate Android Development] atinm:
Yes, I almost always run with the external SD off while I'm developing because I am rebooting, reflashing etc so much. It is faster without external SD of course, but that is because all my music sits on that so media scanning takes a little time even though it is much less than without the EXT4 lagfix. I wouldn't be able to do anything if I couldn't mount the cards as I have to install the update.zip on the root of the SD card and I also frequently install things into system/framework (stock lock screen) which requires me to first write there and then adb shell into the phone to copy to where I really want it.

I guess basically I haven't run into any problems with SD cards. Could it be a permissions thing like other people have seen sometimes when they've done all kinds of flashes beforehand? Maybe go back to RFS, run Rom manager and fix permissions?
[Captivate Android Development] jslee1020:
will give permission fix a try... thanks
[Captivate Android Development] shaolin95:
Hi All!

I got SRE 1.3 with lag fix 4 and was hoping to try this one.

From the SL4A sctips that SRE has there is one to remove the fix so do you think I can just use that removefix script then install yours?
[Captivate Android Development] atinm:
I don't remember all what SRE 1.3.1 did, but I know some things will definitely break if you just install this on top. SRE 2 is out, or almost out and that has the EXT4 voodoo lagfix so you could just go to that.

-Atin
[Captivate Android Development] shaolin95:
ah ok, good thing you replied so fast as I was ready to so LOL

I was trying to avoid doing the whole enchilada of flashin back to stock, copying everything back etc...guess there is no escaping that then :-)

Thanks!

PS Is this compatible with the OC kernel (1.2Ghz) ? Just found out it is not so now I must decided if I want my current lag fix with the extra 200mhz for now until the OC is compatible with voodoo or if Voodoo fix is THAT good that it outweights the benefits of 1.2Ghz and my current lag fix....any opinion guys?
[Captivate Android Development] jslee1020:
I was on SRE131c + ext2 lag fix and then switched to voodoo. And I have to tell you... real life difference is there! You will definitely feel the difference even with no OC. I'm on stock... rooted... voodoo kernel... and its faaaast:D ... plus none of the bugs people are experiencing with SRE
[Captivate Android Development] ranova:
Overclocking is such a gimmick with newly released phones like ours, especially the 200mhz bump.

I can see people overclocking their Droid 1's and G1's, as it does provide a necessary speed increase. But with the latest androids, overclocking is just a way to flaunt your epeen with no significant speed increase.
[Captivate Android Development] shaolin95:
Sure mate but you realize that is just YOUR opinion and that is the same silly excuse people that are afraid of overclocking use with any CPU, I got a i7 920 and some coworkers feel is stupid to OC, same thing goes for video cards so, dont think that just because YOU feel that way, that is LAW. :rolleyes:
[Captivate Android Development] atinm:
I haven't put in overclocking because of all the issues that people have been running into. Unhelpful is working on putting voodoo into his OC kernel, so you'll have that once he is done. I was less concerned about his OC work than I was about power (UV) stuff - that made my own phone very unstable and I don't want to mess with it and doubt I will be putting that out at all. And yes, the speed difference pre and post EXT4 conversion is so significant, the overclocking doesn't seem to gain me much over that. I'd rather have the EXT4 than the OC due to the significant real life difference I get. Having both might be cool and hopefully Unhelpful will get that out sometime so that designgears can pull in the Unhelpful kernel into one of his Cognition builds (I think he plans on releasing a few versions).

-Atin
[Captivate Android Development] shaolin95:
I am on my way to installing this one now and I agree about the UV stuff, that seems to create too many issues so I only care about the OC part. :-)

I will report my experience after I test this today.

Thanks for the great work! :D
[Captivate Android Development] dmuntean:
Does this kernel support mobileAP?
[Captivate Android Development] atinm:
This is just the kernel, the enabling of capabilities like mobileAP is left to others. I think designgears' Cognition has included that with my EXT4 lagfix kernel in his ROM.
[Captivate Android Development] ranova:
it was obviously an opinion... you need to chill out :rolleyes:
[Captivate Android Development] shaolin95:
how about if you chillout before stating that someone that does something you dont, does it for epenis?;)
[Captivate Android Development] atinm:
Guys, relax . . .
[Captivate Android Development] shaolin95:
I did the SRE2 with your lag fix and it does feel very snappy...I did some raw loading tests for some games yesterday...will verify if there is a difference in loading time and report back. (I left the results from yesterday at home).

Thanks!
[Captivate Android Development] RobertDeBord:
tun.ko

Does this include tun.ko for Captivate that'll allow me to use Cisco VPNs? Just want to verify since I can't get it to work yet and want to make sure that's there before I spend a ton of time trying to get this thing to work :)

According to the changelog page "Added tun.ko module for Cisco VPN" so I'm hoping (assuming?) this is in this version.

Thanks!

[EDIT] One last question: If I've applied this but currently have 'disable-lagfix' in my voodoo folder because of some problems I ran into last night, do you know if tun.ko is in place or do I need to enable the lagfix before it works? My assumption is it'll work but just wanted to double check. Thanks again!
[Captivate Android Development] bts0uth:
I applied all 3 .zips in the first post and everything is working great other than I can't download anything from the market. They say starting download and never start. I've tried rebooting and it doesn't help. First time I've had this issue. B7 downloaded apps just fine
[Captivate Android Development] iamamp3pimp:
i did it with a file folder
[Captivate Android Development] gunnyman:
easy way to get the disable-lagfix file

open adb

adb shell

# touch /sdcard/voodoo/disable-lagfix

That's all there is to it.
[Captivate Android Development] tazman171:
Installed it, went in great. Only thing I got was and "external Sd card can't mount" error. I shutdown, popped the card out and back in and rebooted. Every thing is fine.

Been wanting this since I had it with SRE 1.3 with ext4, but I had some serious issues with that. So thank you for releasing this, the Cappy is so much more responsive now, especially in games, it rocks. :cool:
[Captivate Android Development] SPE926:
The only thing that i have noticed since applying the fix is that I can no longer link contacts, I have tried to link numbers on my phone to facebook profiles and it used to work fine, now it says that the contact is linked but doesn't actually do it. any one else have this problem? I searched and read most of the thread but didn't see anything.
[Captivate Android Development] S300M:
should i do this or wait for froyo, just got my captivate today
[Captivate Android Development] atinm:
Did you come from stock or did you install other things? Nothing in the kernel should be doing anything with Market.
[Captivate Android Development] atinm:
Is there anything else you did besides install this? All this is doing is replace the filesystem - nothing else should be affected and is basically transparent to anything above the operating system.
[Captivate Android Development] atinm:
It does include tun.ko and it'll be in place regardless of the disable-lagfix presence.
[Captivate Android Development] SPE926:
nope, only other thing that it had on it was unleash the beast but it had been on it for a little while before i did the fix. I suppose it may just be a quirk with my phone, maybe I'll odin back to stock and restart....
[Captivate Android Development] atinm:
You don't actually need to apply the 3 .zips - just the latest if you are coming from stock or at least are new to the EXT4 lagfix (voodoo). The previous versions are for historical purposes and you only actually need v1.5a specifically if you happened to install one of the previous versions (1.1, 1.2, 1.4, 1.5). Otherwise you just need the latest.
[Captivate Android Development] posthold:
I flashed back to stock without disabling the lag fix. How do I remove the ext4 partition?
[Captivate Android Development] rajendra82:
1. Reinstall voodoo kernel

2. Let it boot and allow data to be ext4 properly

3. Create the disable-lagfix file and reboot to get rid of ext4

4. Flash to stock with Odin
[Captivate Android Development] tjsooley:
is this kernal based off 2.6.29?

2.6.29 only supports 256 megs of ram

we cant see the full 512 till we get a newer kernal.
[Captivate Android Development] atinm:
Yes - I am using what samsung has exposed for the captivate.
[Captivate Android Development] rajendra82:
Samsung has chosen to reserve a bunch of RAM for the radio and ramdisk, even people running Froyo are not seeing any more free memory. We will need additional hacking to free up what they have restricted us from.
[Captivate Android Development] tmusall:
ext4 mount options

Can someone post the output of this command:

$ mount

I would like to know if /data is mounted with noatime and nodiratime options. Installed congnition rom last night and noticed that these options are missing. Would like to know if this is an oversight or done for a particular reason. To me it has always be standard practice to use noatime and dirnoatime especially on file systems mounter on flash memory. Thanks.
[Captivate Android Development] rajendra82:
I have voodoo, and no cognition. Output below:

rootfs / rootfs ro 0 0
proc /proc proc rw 0 0
sys /sys sysfs rw 0 0
/dev/block/mmcblk0p4 /data ext4 rw,barrier=1,data=ordered 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,noatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0102,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block//vold/179:8 /sdcard/sd vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[Captivate Android Development] atinm:
It *should* be noatime and nodiratime. I am calling mount with them on. Not sure why the output doesn't show it though. If you create a file called enable-debug in the /sdcard/Voodoo directory, you will see the logs of the init under the /sdcard/Voodoo/init* files and you'll see I call "mount -t ext4 -o noatime,nodiratime /dev/block/mmcblk0p4 /data" when mounting /data.

mount -o remount,rw,noatime,nodiratime /data

seems to fix it

$ mount
rootfs on / type rootfs (ro)
proc on /proc type proc (rw)
sys on /sys type sysfs (rw)
/dev/block/mmcblk0p4 on /data type ext4 (rw,noatime,nodiratime,barrier=1,data=ordered)
tmpfs on /dev type tmpfs (rw,mode=755)
devpts on /dev/pts type devpts (rw,mode=600)
/dev/block/stl6 on /mnt/.lfs type j4fs (rw)
tmpfs on /sqlite_stmt_journals type tmpfs (rw,size=4096k)
none on /dev/cpuctl type cgroup (rw,cpu)
/dev/block/stl9 on /system type rfs (rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8)
/dev/block/stl10 on /dbdata type rfs (rw,nosuid,nodev,noatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8)
/dev/block/stl11 on /cache type rfs (rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8)
/dev/block/stl3 on /efs type rfs (rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8)
/dev/block//vold/179:1 on /sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0102,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block//vold/179:9 on /sdcard/sd type vfat (rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
[Captivate Android Development] atinm:
Good catch - thanks. You have found a bug - I am remounting /data and it loses the noatime and nodiratime. The bug will degrade performance right now - will fix it later today as soon as I get home.
[Captivate Android Development] rajendra82:
You mean voodoo is about to get even faster. Oh my gosh. :eek:
[Captivate Android Development] tmusall:
Good to hear. I'll be sure to look for your update tonight.
[Captivate Android Development] atinm:
Just uploaded captivate-voodoo_lagfix_3.0_v1.8.zip that fixes the noatime, nodiratime performance issue you found.

Thanks,

-Atin
[Captivate Android Development] rajendra82:
Woohoo, 1.8 baybee.

Quadrant about the same was 1700 before 1711 now. Output of mount does show noatime and nodiratime enabled.
[Captivate Android Development] bfara83:
If I have 1.6 version installed, do I just install 1.8 overtop using the update.zip method or does this lagfix need to be disabled before installing?
[Captivate Android Development] Pmac25:
Is 1.8 the same as what is posted on the project voodoo web site?
[Captivate Android Development] atinm:
No, that is 1.7 - supercurio hasn't update yet.
[Captivate Android Development] atinm:
You should just be able to install over.
[Captivate Android Development] atinm:
Part of the improvement just comes from fewer writes because there are no times recorded just for accessing.
[Captivate Android Development] rajendra82:
Just update. Data will stay put. You only need to disable when flashing on an ext4 unaware kernel, or when booting into clockwork mod recovery.
[Captivate Android Development] Circazero:
Im running JH7.

if i flash SRE 1.3.1c (because it gets rid of all the crapware and enables sideloading) Would it be okay to flash Voodoo 1.8 right after I flash SRE?
[Captivate Android Development] supercurio:
Okay, v1.8 is now online on project-voodoo.org too ;)
[Captivate Android Development] xtremekilla09:
First of all, let me thank you guys - atnim and supercurio plus our countless members. This kind of support is awesome.

Second, I just wanted to know if there was any plans on getting the color fix ported over to captivate?

Lately, I have been noticing the screen too much and I can clearly see the blue tint and lack of sharpness and it is driving me nuts. Don't get me wrong, this is the best screen in my eyes as I just made the jump from Touch Pro screen to Super AMOLED...lol. After seeing those screen shots on http://project-voodoo.org/color, I just feel that this color fix will make my phone complete.

I really dont want to change my LCD density because it makes all the apps look weird and out of shape.

Once again Thank You, seriously!

EDIT: Sorry, Just read that it is still unfinished so....never mind.
[Captivate Android Development] Smallsmx3:
Which version does cognition have. Im assuming i can just disable lagfix and install 1.8 over it without any odin or flashing
[Captivate Android Development] msm903:
Cognition has v1.8 as of 9/21/2010
[Captivate Android Development] Smallsmx3:
i had the origianal cognition installed. so whatever voodoo was there is what i had. I just left the voodoo enabled. flashed over 1.8. I didnt get the lady robot voice. everything booted up. I also had hsupa enabled which is now gone. Im assuming that it worked? It was fairly quick boot though.
[Captivate Android Development] cfili:
Can't download from market

The installation went fine (1.8) but now downloads from the market place fail. Anything I should look for or change? Thanks.

EDIT: Maybe it is the market place being flaky and has nothing to do with voodoo. Downloaded eventually worked.
[Captivate Android Development] [DT]:
OK, it appears I'm deck for the AT&T update (just postponed it for an hour). I'm running the Voodoo Fix (from ~2 weeks ago, not sure which version).

Any ideas if this update changes the kernel? If it does, wouldn't that leave the ext4 filesystem orphaned since the new kernel wouldn't be able to see it?

I'm *thinking* the safest thing to do is to uninstall, then update from AT&T - I'm not sure if it could be reinstalled (v1.8), I guess that depends on exactly what's coming down from AT&T.

I hate to remove Voodoo, the phone has been _perfect_ performance-wise with this (fixes one of my major beefs).

Anybody with any thoughts on this?
[Captivate Android Development] rajendra82:
Your results indicate that the update worked. HSUPA = i900 rotation fixed kernel, No HSUPA = voodoo. Voice prompt = File system conversion from RFS to ext4 or back, no voice prompt = file system remains the format, only kernel flashed over.
[Captivate Android Development] rajendra82:
Catch the update and post the file up here, and we can examine it and tell you. Most likely there is no kernel in the 12 MB update. Safest would be to disable voodoo, flash OTA update, reinstall voodoo, and reenable.
[Captivate Android Development] Smallsmx3:
So your telling me i cant have voodoo and hsupa.? Im pretty sure i had both.
[Captivate Android Development] [DT]:
Yeah, since the Voodoo reverses pretty easily, I'll probably do that.

Does the update queue up onto the phone first? Where should I look (I'm rooted and have plenty of filesystem utils).
[Captivate Android Development] crupp:
what if I dont hear the voice when un installing. Is it uninstalled? How can I verify
[Captivate Android Development] rajendra82:
I meant to say that the the voodoo lagfix beta4 captivate kernel by atinm, and installed a default in SRE 2 does not support HSUPA. The i9000 Eclair kernel with rotation fix by xcaliburinhand, that overwrites atinm's kernel when you install the optional HSUPA package, also supports the voodoo lag fix, but currently has issues with bluetooth. You can have the lagfix and HSUPA, but not with a kernel based on Captivate sources.
[Captivate Android Development] [DT]:
Let it run and it will eventually reboot. It takes a good 10+ minutes - you'll get the initial voice cue, then 10+ minutes later another, then a few minutes later your phone will reboot.

FYI, if you're removing for the AT&T update, I'm not having any luck, getting the failed message at 50% and a reboot.
[Captivate Android Development] [DT]:
You know, the Voodoo fix is so outstanding, that I'm willing [for the time being] to forget about the AT&T update - especially given the GPS still sounds like it's slightly sketchy - and just go back to Voodoo.
[Captivate Android Development] Justinph5:
This is what I did. Tried it with voodoo disabled. Got to 50% in less than 1 second, then failed. Restarted, so I just enabled voodoo again and will be happy with it.

My GPS only takes a while to get an initial lock anyways, one it's locked, its perfectly fine.
[Captivate Android Development] [DT]:
Awesome, yeah, I just did the same. The voodoo 1.8 installed really quick - hell, I actually even used the method to return my kernel to pre-voodoo (which worked fine) to update via AT&T (which again, like you, failed at 50%). I'm done hassling with AT&T.

The voodoo fix actually seemed to apply, but I got almost no startup delay and no audio cues, hopefully it applied OK. So far the phone doesn't seem quite as snappy as it did with my previous voodoo update.
[Captivate Android Development] sblees:
I just downloaded the att update, should I disable voodoo before I install the update? Or does it matter? (assuming it doesn't fail at 50%)

Thanks
[Captivate Android Development] jhsperc:
You will not be able to apply the update.

I tried with adb and the stock kernel recovery and it fails.

Might as well forget about updating till someone gets an update.zip going.
[Captivate Android Development] sblees:
Well, if I was going to try, do I have to disable the voodoo lag fix? I don't have any hope that it will actually work, but on the off chance I need to know if I install the update can I leave voodoo installed. (I'm running v1.6)

Thanks
[Captivate Android Development] jhsperc:
If you were going to try, yes. You would have to disable any lag fixes, and being that this lag fix changes your kernel you have to revert that back as well.

If the update worked successfully you would then be able to reapply the voodoo fix.

You should also remove root as well before you try and apply the update, I would also backup everything with Titanium Backup then factory reset - then install the update. Just to make sure you don't brick your phone on accident.

But, being that it won't work anyway just be happy that you don't get any ill side effects like what's been reported elsewhere on the forums.
[Captivate Android Development] sblees:
Ok I think I'll just skip the update, after I downloaded it, it gave me the option to postpone so I choose to postpone for 4hrs... does anyone know how I delete the update from my phone?

EDIT: nevermind... I let the update fail and that got rid of it.

Thanks
[Captivate Android Development] [DT]:
Has anyone removed an earlier version, like 1.6, and then installed a new 1.8? When I installed 1.6, I got the voice and it took like several minutes to complete, when I installed 1.8 it was almost instant.

So to outline what I did:

Installed 1.6 and the phone ran amazing, the f/s conversion/install/etc., took about 5-10 minutes.

Used the phone for a few weeks with outstanding performance, until this recent AT&T update

Removed the ext4 by dropping a 'disable-lagfix' folder in the voodoo directory (it took about 10 minutes to convert the f/s back, got all the audio cues ("converting filesystem..."), etc.

Muddled around with AT&T updates (never got past 50%)

Ran the 'redbend_ua' command via ADB (~spooky~ method :) )

Tried AT&T updates again with the stock kernel (same failure at 50%)

Downloaded Voodoo 1.8, copied to sdcard root as update.zip

Reboot into recovery, ran it

Got the big blue text about updating (and the script execution)

OK ... this is where it gets a little odd ...

The 1.8 didn't do any audio cues, and rebooted/finished (seemingly error free) in like 30-45 seconds. The phone is running perfectly fine. It doesn't seem as "unlaggy" as it did with the 1.6, leaving me to believe that maybe the f/s was +not+ converted.

Is there any way to confirm the filesystem has been converted?

My kernel appears to be showing the proper version: atin@thor #Voodoo_lagfix_3.0_v1.8
[Captivate Android Development] supercurio:
Hey xtremekilla09 :)

Yes, color will be ported to Captivate ;)
[Captivate Android Development] jhernand1102:
Did you remove the disable lagfix file in the voodoo folder?