yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] ttabbal:
OK. I have it working and verified now. If you have already applied one of the prior hacks, DO NOT INSTALL THIS. It will probably erase all your data and dalvik-cache in that case. I'm to tired to fix it right now. :D

I came from a fresh stock Odin flash. Here's the steps.

1) Root. Duh. :)

2) Install Busybox installer from the market, run it, and install the latest busybox.

3) Install ROM Manager from the market, run it, install the recovery, select Vibrant (or Captivate/I9000 if you're brave), and tell it it can run as root. Select reboot to recovery. Here it will reboot twice and such, see the Clockwork thread if you have questions. Don't do anything here, just reboot back to Android. This is just to get Clockwork all set up properly.

4) Once you're back into the Android system. Load ROM Manager, select flash ROM, and select this ZIP file.

It will ask if you're sure, if you say yes, it will reboot into recovery and run this. It will take a while on "Copying files", that's OK. It will auto-reboot when complete. Your phone should come back up exactly how it was, but faster. :D

I re-installed all my apps with Titanium while typing this. So far, everything is running fine. Quadrant gives me 1435, but I haven't removed any bloatware and I did just re-install all my apps. I've found the score to vary somewhat depending on what the phone is doing. I'm on ext3 as well, which might lower the score a bit, but I don't notice any difference just using the phone from ext2 which is what I was on before.

My highest score (about 2000) came on ext2, with bloatware removed, and my apps pretty quiet in the background. Not really all that realistic. Ext2 is dangerous as the system won't unmount it nicely, so it might get corrupted. Cyanogen posted on the G1 forum a long time ago about it, read that if you want more detail. I'll bet if I did the test without installing all my crap and killing the bloat, I'd get a really high score. :D
[Vibrant Android Development] anomalous3:
Hmm, deodexed build works fine except for the dialer and contacts, don't have time tonight to investigate.
[Vibrant Android Development] The_Chrome_Coyote:
If I revert "method 1" can I apply this without wiping?

sent from my Samsung Vibrant
[Vibrant Android Development] kopykatkiller:
Why not try yourself? For someone claiming to want to dev for this phone you seem a little to scared to try anything yourself.....just saying.
[Vibrant Android Development] aenima4six2:
Yeah, this typically results in a fail. Either get a G1 and partition with RA recovery or get another card reader and try again when it arrives.
[Vibrant Android Development] ttabbal:
Or dismount the external card from settings and use fdisk in adb shell/terminal. It's there if you have busybox. Not "easy", but doable. The best, error-proof way is with a real card reader on a computer with Paragon or GPartd. GPartd has the added benefit of being able to format the ext3 partition, the phone lacks the program required to convert from ext2 to ext3 without adding stuff to system. Maybe I'll create a ZIP for that too. I dunno. :)

I mean, really, SD card readers are what, $5 now? The Vibrant even came with a microSD to regular SD adapter, so you don't even need a slightly more rare microSD reader. :D
[Vibrant Android Development] rhcp011235:
Why? Because i dont flash random things to my phone looking to brick it. I like to ask before i do something that someone else has done.

Simple answer. If you look at all the others who jumped on the wagon who jumped to flash. wound up with a paper weight.
[Vibrant Android Development] ttabbal:
You could do that, I'm not sure why you would, but sure. The issue is that the script expects your data to actually live on /data. If you've applied this fix, /data/data and /data/dalvik-cache are empty directories used for bind mounts or are symlinks using the other method. The script then deletes the directories on /sd-ext and creates new ones to make sure you don't have old stuff in the way. This would kill all the data you put there before, then it copies the empty directories from /data over /sd-ext and you end up with a wiped phone. That is likely not the desired result. :D
[Vibrant Android Development] tissimo:
Fwiw, I haven't removed any bloatware on my phone and I get 1800-1900. I'm on a ext 2 partition though, do it might effect the speed a decent amount.. I used the old method though.

Sent from my SGS Vibrant
[Vibrant Android Development] ttabbal:
Indeed. I think those leaked ROMs gave Odin an undeserved bad rep around the Vibrant forums. The stock TMO ROM works perfectly with Odin and I've only ever had one problem. Something stuck at the beginning. No blue bar, so I rebooted with a battery pull and got the phone/computer screen. The directions the others gave got me back into download mode and the flash applied fine. If you aren't flashing the wrong stuff to your phone, you don't have those problems and this thing is about as brick-proof as you can ask for.

I don't see asking about stuff as a bad thing, some of us paid for our phones after all. :D

I'm planning to unzip the adb push/pull fix and see if I can make it integrate with the dc2sd ZIP I posted earlier. I'll probably keep it separate as not everyone uses adb as much as I do. :)
[Vibrant Android Development] ttabbal:
There seems to be a fair bit of variability in the scores, even between runs on my phone with no config changes. Background apps will make a difference, and ext3 is slower than ext2. It shows up in benchmarks, but you really don't notice it on the phone itself. What you will notice though, is a corrupted filesystem should your ext2 partition decide to die because the phone rebooted without dismounting it. It's not something that will happen easily, but in the wrong circumstances it can and does happen. Go get the e2fsprogs compiled for ARM, Cyanogen posted a ZIP in the G1 foums, and run e2fsck from recovery. I had some errors, nothing serious, but enough to convince me that I care about what I can see running apps, not so much about some synthetic benchmark.

Note that in that post Cyanogen is asking all ROM devs to stop using ext2 in favor of ext3 due to these problems. Something to consider. :)

Here's the post. I wanted to download the file to this computer. http://xdaforums.com/showthread.php?t=520582
[Vibrant Android Development] ttabbal:
OK. I wanted it for my phone, so here's e2fsprogs compiled by Cyanogen. You can use "tune2fs -j /dev/block/mmcblk1p2" in RECOVERY to convert ext2 to ext3 and use e2fsck and such as well. Note that when booted, the partition is mounted so these tools won't work. You must do it from clockwork recovery and "adb shell" as clockwork enables root in shell.

If "adb shell" gives you a device not found, remove the USB cable from the computer, not the phone, wait a few seconds, plug it back in, and wait a few more seconds. It should work now. Remember to "su" before using filesystem commands.

If you use ROM manager to flash this, you will reboot after flashing. If you want to use the tools right away, boot to recovery mode and apply the ZIP using the menus on the phone. Then you can adb shell right there.

All I did was put Cyanogen's files into a ZIP, but they do work on my phone.
[Vibrant Android Development] rhcp011235:
Nice. Great work, and thanks for the comment.
[Vibrant Android Development] davbran:
what sucks, is I have a card reader on my monitor, but even with the adapter it never sees my card.
[Vibrant Android Development] AustinKnight45:
So which ext is faster I've got ext3 and its doing like 1400 is ext 2 faster ?
[Vibrant Android Development] aenima4six2:
Anyone care to make an "undo" version of the script (move all apps back to Internal Storage)? Not that I would ever want to leave it this way, but it will make testing faster..

Also.. I haven't played around with ROM Manager with this patch. If you Nandroid with the patch, with all apps on external EXT partition, will a restore dump the apps back to the proper external EXT partition ?
[Vibrant Android Development] Maverick777:
This probably because the memory card reader cannot read SDHC cards. I had the same problem with my Dell 2405.

I actually use my DSLR or camcorder to read my SDHC cards.
[Vibrant Android Development] ttabbal:
I've got one in the works, it's just not tested enough for releasing yet.

Nandroid won't work with this unless Clockwork is also backing up and restoring the ext partition like Amon-RA did with the nandroid+ext option for G1/MT3G devices. Recovery doesn't know about this stuff, it's only active at boot. That's why there's an update.zip for wiping dalvik, there's not another way to do it without using adb shell in recovery, or a card reader and a Linux box. :)

I should probably make a data wiper as well, just in case.
[Vibrant Android Development] ttabbal:
See my post a little back. Ext2 is faster, but less safe. The SD failing to mount could leave you in a boot loop or similar, so I don't recommend it. The benchmarks are faster, but real-life doesn't show a significant difference. I run ext3 on my personal phone. You have to decide if it's worth it to you for benchmark bragging rights. I've hit 2000 with ext2, but I don't care enough about that to use it for daily use.
[Vibrant Android Development] DocRambone:
Maybe an foolish idea: modaco have a lag fix that moves app data to internal nand. Would it be a benefit to move the dalvik cache to nand and keep app data on ext?
[Vibrant Android Development] ttabbal:
Here's the revert zip. I just ran it on my phone, it's running fine. Loading apps and data just fine. I can tell it's slower, but it's not so bad. :)

Again, tested with Clockwork. I don't know or care if the stock recovery works with it. It should, but whatever. :D

Quadrant is now 916. In line with what we would expect it to be with the internal used for data and cache. Now I have to flash back.. whhheeeeeeeeeee... :)
[Vibrant Android Development] davbran:
You know, that's an interesting idea actually, because we were having issues with scores till we cleared the dalvik cache so. I wonder if that's the only thing really holding things up?
[Vibrant Android Development] ttabbal:
I doubt it would be significantly different to have dalvik on NAND vs. SD. Feel free to try it, there should be enough space available for it on /dbdata. I used the modaco version before I did this one. It works fine, it's just very space limited and I'd rather wear down my SD card than the internal NAND. Dalvik wouldn't cause significant wear though, so give it a go and report back. :) We're still learning how this phone does things. Maybe your idea will work better than the ones we have tried so far.

NAND is also space limited. About 130MB free with the base ROM installed. Again, probably OK for dalvik, just something to be aware of.
[Vibrant Android Development] bestwebs:
Hi,

I always used gparted to format my sd card on my G1 from recovery.

Is there a way to use gparted on the vibrant?

Thanks

:)
[Vibrant Android Development] ttabbal:
Issues with dalvik should have only come from earlier userinit.sh based versions not getting the files copied over before Android comes up on this stupid fast phone. The files would get corrupted and cause FCs and such. It shouldn't change scores. At least I THINK it shouldn't.... I could be wrong. :)

The new way with ZIPs uses recovery mode to copy the files. So it can take a while. Running the revert was SLOW. :) There's no race condition to worry about in recovery, so the files can get copied and the filesystems dismounted without worrying about the OS coming up and wanting those files.

Dalvik on my phone is about 44MB... So it will fit....
[Vibrant Android Development] davbran:
I liked your last solution, but sadly after making the change the market would force close on me everytime I tried to open it. I am not sure what was going on with it.
[Vibrant Android Development] ttabbal:
I don't think Clockwork has the USB-MS mode that I always used in Amon-RA from the G1. If you have the G1, use the partition creator in RA-Recovery. It will work fine. Swap to 0, ext to whatever size you want, FAT for the rest. Then use it to convert ext2 to ext3. Should be good to go after that.

I used gpartd, but I always did it with a card reader. :)
[Vibrant Android Development] davbran:
Anytime I trused to use USB storage in Clockwork it would blue screen my windows, that was on my N1 and MT3G
[Vibrant Android Development] ttabbal:
Odd, I haven't had any trouble with Market. I've tested it with every version of my scripts as it's more finicky that most apps. Have you tried using e2fsck (I have a ZIP for that in a prior post) from recovery? You could have a corrupted ext partition.

Heh.. "Vibrant, there's a ZIP for that." :D
[Vibrant Android Development] junkdruggler:
I also used gparted on my g1 but there is no recovery console in the vibrant... The g1 had a keyboard... you would still need a comp w adb to type the scripts...

I asked koush about this a while ago.. I never got a response, but I was asking for the g1.. I don't think it would be possible for a phone without a hard keyboard...
[Vibrant Android Development] DocRambone:
I tried it but me dalvik cache was way to big to fit (deoxed rom)...
[Vibrant Android Development] skater4690:
Well it seems the extra size was too big I reparted my SD card to 1gb extra and everything works great. 3gb was too much I guess lol
[Vibrant Android Development] AustinKnight45:
Ya I thought I saw somewhere in here that ext2 wasn't stable plus I haven't used ext 2 since the G1, I'm good on the benchmark no need for over kill and possibility of looping my phone thx for the info.
[Vibrant Android Development] ttabbal:
There seems to be an issue, but I haven't been able to nail it down. Going back and forth a few times shouldn't cause an issue, but it does seem to. I added a sync call to the script to try to ensure that the data is flushed to disk, but it's still messing up some app data. It's intermittent and seems more common with lots of apps installed. Restoring with Titanium fixes the problem, but that's just overwriting the bad data with known good data. Not sure what's up. If someone has thoughts, I'd be interested to hear them.

I'm concerned that people with lots of apps might get some data issues. Backups people, backups. It seems that it might be best to recommend new users start from a wipe. Use Titanium to backup and restore your apps and data. That seems to be the most reliable way to do it right now.

Outside of this, I haven't had any issues with the current scripts. I'll keep thinking about it, maybe there's something I missed.
[Vibrant Android Development] rhcp011235:
So, I fixed the FC issue. now i have a new one :) When i try to install a app from market it says im out of space? Any ideas?
[Vibrant Android Development] FastKatt:
Did you have the nand fix in place before? If so, are you sure everything is moved rp the ext partition?
[Vibrant Android Development] skater4690:
How big is your ext file size? I had the same problem my ext size was too big can't be bigger than 2gb
[Vibrant Android Development] justanothercrowd:
It is a little concerning that you are asking people for MONEY so you won't have to TEST (I mean thats basically the heart of Developing anything...TESTING IT :) ) anything on your phone. Why doesn't everyone get a spare phone to test on and we all ask for donations and we will just leave our phones alone.

It appears to me that your not (and I mean this in the nicest way possible) capable of deving either because you don't actually know enough yet or you are too scared to try something on your "personal" phone. (The being scared usually is because someone doesn't fully understand what the scripts etc are doing and thus can't determine if they are a risk)

All the development I've done for the G1/MT3G and the Vibrant has been tested on my personal phones. I do ask for donations but thats because I have produced development work. I would never ASK for money because I'm not familiar enough with my actions to safely develop on a platform I already own.

Again not trying to be a **** but everyone Dev's on their phones...unless you have a huge project like CM going theres no justification to buy you a Dev phone. Just my 2 cents sorry if it seems harsh.

Also most likely the folks using EXT2 are getting corruption just like we did with the G1. Even seen it on EXT3.

The solution was to add some calls to init.rc that call startup and shutdown scripts that safely mount fsck and unmount the EXT partitions on boot and shutdown as well as having the scripts run before the default init starts. This is currently being worked on as we speak.

I have a few small bugs to be worked out in my custom kernel and we will have everything I described above which will lead to less corruption and more functional phone.
[Vibrant Android Development] anomalous3:
wow, the ROM kitchen has come a looooong way. The brute force method it uses to deodex stuff is SO much easier and faster than figuring out dependencies the old fashioned way. Looks like I might have this working soonish :D

(haven't used it since the old days and my searches for resolving my deodex FCs brought me to the ROM kitchen page, saw it had deodexing capabilities and decided to give it a shot. Kind of cheating but why do it the hard way when you can do it the easy way).
[Vibrant Android Development] davbran:
When I had the market force close on me it was right after a titanium backup, I haven't had time to try it all again, this being my only phone right now, I have to keep the line free.
[Vibrant Android Development] davbran:
Does the xda app crash a lot for you guys?
[Vibrant Android Development] bestwebs:
Hi,

Looking forward to your improvements.

So far no crashes have occurred.

:)
[Vibrant Android Development] junkdruggler:
Where is that kitchen that deodexes?
[Vibrant Android Development] justanothercrowd:
I assume he is using this

http://xdaforums.com/showthread.php?t=633246
[Vibrant Android Development] junkdruggler:
Thank you
[Vibrant Android Development] CharonIDRONES:
@justanothercrowd

Great to see some quality developers behind the SGS. I predict (well, hope really) that with the demise of the Nexus One on T Mobile that those on the carrier will be looking to the SGS and getting a bigger dev community behind it. And whenever CM6 get's finished . . . #blamewes

Really though, thank you for all the quality work (coming from a G1), I am not a usual poster (don't need to, I know how to search ha) but really I am hoping that the community will be able to push this phone as much as they have pushed the Dream (though that won't be necessary for quite awhile haha)
[Vibrant Android Development] rhcp011235:
So,

It seems EXT2 I get 1900+ quad. For some reason on ext3 it just seems to bootloop during the media scan.

But, I took the advice of the person here to keep my space under 2G and it seems to work fine now.

As for the comment made by the person before: I prefer to ask people before doing and fooling around with things. Why spent hours to fool around if someone knows. If you want to donate do so. If you dont. Dont. Again, Im not holding a gun to your head.

I did most of my dev on the G1/G2 with extreamod for 2.2. I just got my vibrant. And, Im doing things very slowly.
[Vibrant Android Development] junkdruggler:
To develop is to make something new... What new did you bring to the community? Not meaning to fuel the fire... Just never heard anything from you and I still frequent the g1 forums...
[Vibrant Android Development] AustinKnight45:
Ive been running it for two days on ext 3 and haven't had one fc all my apps load up fast all seems good.

Sent From Tha 1 Tha Only... Vibrant
[Vibrant Android Development] davbran:
Yeah the XDA app force closed on send no matter what I was using, so I am not sure that it was effecting me.
[Vibrant Android Development] youneek:
I now get a strange stutter in my messaging. Everything else is quicker. Ext2 had some problems so I upgraded to ext3. I only get 1100 but the phone is very snappy.

Sent from my Vibrant
[Vibrant Android Development] anomalous3:
deodexing works except for the touchwiz calendar. Fortunately, I think it's rather useless and it can be replaced with the google apps calendar. Also, quadrant scores remain ~1900, but the deodexing destroyed my linpack scores for some reason. The plot thickens.
[Vibrant Android Development] mcbooth:
Could someone please help me get this working on a i9000?

I've pushed the 3 files to system/bin and set permission 0755

I have an external SD with fat32 as first partition, ext3 as second

On boot i get a black screen then home screen - no boot animation at all. It's clear the script isn't working, but where and why?

Assistance appreciated.. You guys are way ahead of the i9000 forums. Wish they were combined!!

Im trying it on 2.2 rom JP3

If i try the script manually i get 'Device or resource busy'. I have the latest busybox installed.
[Vibrant Android Development] bestwebs:
Hi,

Check the size of your ext.

Should be less than 2 gb.

Also the zip is supposed to be flashed from recovery.

Rename to update.zip

Sounds like the files that you pushed are corrupted or have wrong permissions set.

:)
[Vibrant Android Development] ttabbal:
The XDA app is based on Tapatalk, which isn't a very well programmed app. It doesn't take much to crash it. FWIW, I was getting the crash on posting before I did anything with the phone and it's working fine as of last night. Fawk if I know, I didn't change anything about the phone. I tried wiping it's data, reinstalling the app, nothing helped it. I wonder if XDA updated the plugin it uses?
[Vibrant Android Development] aenima4six2:
Awesome, thanks you sir!

This will take care of Dalvik as well as all apps correct? Also, I thought I read someone got a lil speed boost from using the dalvik wipe script after applying the A2SD patch. Why would that be?

Last but not least, would a "zip align" script benefit at all once the de-odex rom is release?
[Vibrant Android Development] ttabbal:
Can you ADB shell? Unzip the archive on a computer, then open the script in a text editor and copy/paste the commands in the shell, one at a time. Do this from Clockwork recovery, so you can get root. The scripts run as root by default, so you will need to "su" first. Let me know when a command returns error text and what it tells you. If the enable.sh works fine, then try /system/bin/dc2sd.sh and see if one of those commands isn't working. I don't have an i9000, so I'll have to rely on you to help me find the bug. The errors should help me figure it out and I can give you new commands to try. If it's too different, I might have to make a special i9000 version, but I hope not.

Note that with Linux, no output from the command means that it worked, there's no positive feedback, only negative. :)

Reading your post again, it sounds like you unziped the file and manually pushed the files into the /system/bin directory and set permissions. That's fine, as that's all the update.zip really does with them anyway. However, you do need to execute the enable.sh from a root shell in recovery. That's where flashing the ZIP comes in handy, it does that bit for you. "sh enable.sh" should do it, just cd to the directory you pushed the script to first. Don't do this stuff booted into Android, it causes weird stuff to happen. :) Not a problem for you right now, but just FYI.

Without enable.sh, the files didn't get copied to the SD card. :)