yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Clienterror:
It will work man, zilch got me to play pimp my cappy. I'm doing the i9000 rom with samset 1.9e with 1.2 OC kernel with the ext2 lagfix WITH the black bar battery mod. That's a mouth full.
[Captivate Android Development] Zilch25:
Oh no, I've created a monster :o
[Captivate Android Development] Citznfish:
I don't know what's wrong now but I simply can't reinstall that zip file. It acts like it installs but no icon appears in my app drawer. I still see the folder in root manager, but then I deleted it to see if I needed to remove it for a new install. This is the only problem I've had installing anything on this phone
[Captivate Android Development] Clienterror:
Just out of curiosity are you rooted. I've done better when I root with a separate update.zip then run lagfix without root.
[Captivate Android Development] no driver:
I am rooted running JH2. I'd like to try the lagfix with ext4, but it looks like it isn't going to work on my phone. I used the update_v2.2.1_ext4_with_root.zip this afternoon and the script to check the space on my phone did not return anything. I went ahead and tried running the ext4 script and got a lot of error messages. After the script ran I was back in touchwiz and most of my apps were gone. Fortunately I made a nandroid backup prior to running anything.

Tonight I tried update_v2.2.2_I897UCJH2_with_root.zip with similar results. I did try running the ext3 script first and it said that my phone couldn't use ext3. Then I tried ext4 and now I am reverting to my backup again.

I did have to sideload SL4A both times, I assumed because I never ran anything to remove the non-market apps restrictions on the phone. Maybe that's a symptom of the problem though.

Any ideas what I'm doing wrong? Any help?
[Captivate Android Development] Zilch25:
Someone earlier in the thread reported similar problems and it was due to using a prior root method and the "with root" update.zip... since you're already rooted try the version without root. That seemed to fix the problem they were having. You shouldn't need to enable side-loading to run the fix since it installs the actual stuff to run the fix in recovery mode.

Also make sure you aren't using clockwork to install the fix... that has varied results.

If that doesn't work post back here, Tayutama pays pretty close attention to these boards so if there's some glitch in the script I'm sure he'd be eager to fix it :)

I'd also say to enable sideloading before running it anyway.. just to be safe!
[Captivate Android Development] Clienterror:
When he's not spamming F5 for Final Fantasy keys :-)
[Captivate Android Development] Zilch25:
For the record... 11PM EST and they STILL aren't available. Guess it's good that he has a script for that haha
[Captivate Android Development] Tayutama:
The Check Space script only shows any numbers if you are running a lagfix, since it's a script so people can get the space they got left to install applications in.

Also like Zilch25 said is your nandroid backup rooted? And are you using Rom Manager to apply the zip? There have been reports that Rom Manager can be kinda tricky. (I know this myself from modifying framework-res.apk and then trying to use update.zip to push it back... Rom Manager did nothing at all :( )

Ofc i got addons in my firefox that auto refreshes for me... not that stupid :D

Also since they didn't get any, the next time the giveaway can start is at 8:00 AM PST :) so right after i get home from work... guess it's time to camp it again then :D
[Captivate Android Development] Zilch25:
Looks like we've got a new firmware release... and the jupiter files are different again lol.
[Captivate Android Development] Tayutama:
Any problems with the GPS this time? :)
[Captivate Android Development] Zilch25:
Well... I did a line by line comparison and the files do appear to be different... or at least shuffled around. But logging is STILL enabled and generating massive amounts of log files. (Had 4 in my log folder in about 10 minutes of use O_o)

Edit: attached the new jupiter file =P
[Captivate Android Development] no driver:
I had been running these updates through ROM Manager, so maybe that was part of the problem. Last night I updated my settings.db to allow non-market installs since it was something I had intended to do anyway. This morning I ran update_v2.2.1_ext4_without_root.zip through stock recovery and SL4A was added automatically. When I ran the install ext4 script it seemed to be doing its thing, no error messages, but when it reboot after it was finished I was back to touchwiz, a fresh install (I had to sign in to Google to enter the market) and without any of my apps. I downloaded Quadrant to see if anything was different speedwise and it gave me similar scores as JH2 stock. Actual app speed doesn't seem any different either.

I'm going to revert back to my backup and try one more time.
[Captivate Android Development] Zilch25:
That's strange. What root method are you using, just out of curiosity? Are you using anything like unleash the beast or super rooter? Just trying to figure out if maybe there's something in one of those methods that might interfere.
[Captivate Android Development] no driver:
I used the TGA_Gunnman one click root/unroot.
[Captivate Android Development] Tayutama:
Need firmware name ;)

It's recommended to use 2.2.2 on JH2 to disable the GPS logging.

Super Rooter got v2.2.2 in it so don't thin he used that one.
[Captivate Android Development] Zilch25:
Well apparently the checksum between the two jupiter files is identical, so looks like a new version shouldn't be necessary. Apparently I was hallucinating =P (That or my editor doesn't jump to the same pages at the same rate when I Page down)
[Captivate Android Development] Zilch25:
Hmm that's the same one I use... this just keeps getting weirder
[Captivate Android Development] no driver:
I just realized I am using busybox 1.18.0. I am installing 1.17.1 and trying again.
[Captivate Android Development] Tayutama:
2.2.1 and 2.2.2 shouldn't need busybox 1.17.1 anymore

Also do use 2.2.2 on JH2 so you fix the GPS log problem :)
[Captivate Android Development] Zilch25:
The script *should* install it's own version of busybox, but I've had busybox 1.18 hijack the folder before

Though the script should be calling lf_mke2fs instead of the mke2fs from xbin
[Captivate Android Development] Tayutama:
true.

Other news... ill be working on a 2.3.0 this weekend if i get time where ill look at that damn interactive menu :)
[Captivate Android Development] Zilch25:
OoooOoOooo, maybe you can toss in options for jupiter file replacement and all that jazz too, that way people won't get confused as to what files to download for which device
[Captivate Android Development] no driver:
I already applied the GPS log fix, so I think I should be indifferent to 2.2.1 and 2.2.2, right?
[Captivate Android Development] Zilch25:
Yeah you should be okay then, the only difference (as far as I know) is that it replaces the jupiter.xml file when you do the update.zip process.
[Captivate Android Development] Tayutama:
Should be doable... i think... ill make it so there will only be one file to run and there you will be able to pick what you want to do and that will call other files... ofc i won't do anything with su access before it calls the other files since that is what ****ed me up last time... if you remember that one :)
[Captivate Android Development] Tayutama:
that and it deletes any old log files when you run the script :)
[Captivate Android Development] Zilch25:
Indeed I do :) Su shmoo, who needs SU? =P
[Captivate Android Development] Tayutama:
Oh and the best feature that will be in? You can pick your own size of the file :D
[Captivate Android Development] Zilch25:
Oh that's cool... RyanZA's apk version has a little slider adjuster for file size, but so far it's only working for lagfix v1. Nice to see you guys are on the same page development-wise though :)
[Captivate Android Development] no driver:
Same outcome on the ext4 script. Reverting.
[Captivate Android Development] Tayutama:
I had it planned already for 2.2 but then i had those problems with just selecting ext so i pushed it to later :)

Generally i have been ahead of RyanZA :)

when he released his 2.2, my 2.0 still had the same features and my 2.0 came out before his 2.1 :)
[Captivate Android Development] Zilch25:
Well damn... I'm kind of tapped out on this one, any ideas?

Have you tried just a clean flash, and using the version with root and nothing else on the phone to see if it takes?
[Captivate Android Development] Zilch25:
It's like a lagfix arms race haha
[Captivate Android Development] Tayutama:
Have you tried it after a reflash with the stock firmware?

You can always restore applications after it's done.
[Captivate Android Development] Clienterror:
Actually I've found its way faster to reinstall apps after the fix and a totally clean install plus the success rate is way higher IMO. Tayutama and zilch are my idols lol.
[Captivate Android Development] Zilch25:
Yeah I always ALWAYS start fresh before running one of the lagfixes, I just don't want to take the chance that any crap is being left behind after all the paths get changed.

Also it's good to have a fan lol
[Captivate Android Development] Tayutama:
There is no definitive times, stay tuned. If it pushes past 9 PM PST, we will be waiting for 8/19 for release. 5 minutes ago via TweetDeck

:(
[Captivate Android Development] Zilch25:
Good lord... what a joke. They could just make the keys available and tell people "Okay well this is beta, the servers aren't going to be up for a week, tough luck"
[Captivate Android Development] Tayutama:
Say that to SE:... :(
[Captivate Android Development] Zilch25:
I'm not much of a conspiracy theorist, but Fileplanet makes a pretty penny from these subscriptions. They probably saw how popular the FF beta keys were and used this little server problem SE is having as an excuse to keep people subbing and F5ing for longer =P
[Captivate Android Development] no driver:
I finally gave up and started from scratch. JH2+2.2.2 w/ root and Ext4 I got 1720 quadrant. Now it's time to start getting my phone set up again. Thanks for trying to help me troubleshoot it.
[Captivate Android Development] Zilch25:
Glad you got it up and running finally :) It's kind of hard to troubleshoot when the phone has been "moved into", it adds so many variables to the equation.
[Captivate Android Development] djhaf:
Which one should I download if I currently have JH3 installed?
[Captivate Android Development] Tayutama:
That would be your department Zilch :)
[Captivate Android Development] djhaf:
Also, if I already have UTB installed, does it make a difference if i install the root or without root version?
[Captivate Android Development] Zilch25:
JH3 has the same log file issue as JH2, so you'd want the JH2 (v 2.2.2) variant of it. Since you're already rooted grab the no root version.

If you've already edited the jupiter.xml file to remove the logging you can just install the 2.2.1 version without root though!

Actually does UTB fix the jupiter file?

Edit: He doesn't say anything about it. Running the 2.2.2 version of the update.zip should be fine, just make sure you get the one without root.
[Captivate Android Development] djhaf:
No it doesn't. I just did a fresh flash of the new rom... going to hit UTB + lag fix and i'll let you guys know how it goes. Thanks!
[Captivate Android Development] Argastes:
Hmm...so does this mean the warning above the link to Tayutama's fix (DO NOT USE THIS FOR JH3, THE JUPITER FILES ARE DIFFERENT, DISABLE LOGGING MANUALLY AND INSTALL THE NON-CAPTIVATE VERSION OF THE FIX) can be removed in the OP?
[Captivate Android Development] _Opiate_:
Good question
[Captivate Android Development] Zilch25:
Yeah I should pull that out of there. The jupiter.xml file checksums are identical between JH2 and JH3
[Captivate Android Development] Tayutama:
Hf camping i'm off to bed ;) btw if there is anything you want to see in 2.3.0 Zilch just pm me when you think of it and ill look into it :)
[Captivate Android Development] Crizthakidd:
play vindictus while u wait for ff14
[Captivate Android Development] Clienterror:
Hey, thanks for making me feel old :-) I remember buying ff1 for my NES. I'm only 27...omg that's almost 30....I need a drink.
[Captivate Android Development] Tayutama:
Going to start on 2.3.0 today but ill make a 2.x.x version for you to test some thing
[Captivate Android Development] Zilch25:
Okay, sounds good :D
[Captivate Android Development] Tayutama:
Here you go.

Time to test ;)

What i have done here other then normal is i don't move /data/app and not using symlink on /data/app-private anymore.

Also made the file have a size of 900mb.

I want you to apply it and then loads apps into it and the test out how it feels.

It have the jupiter.xml fix in it
[Captivate Android Development] Zilch25:
Will do... I don't have much in the way of paid apps though, will that affect the outcome of my testing?

Just for the record, what is going into the EXT2 FS and what isn't? Also what's the objective? Ya know, just for my own personal edification ;)

Edit: Sweet, got my name in the zip file, I'm E-famous!
[Captivate Android Development] Tayutama:
It's only ext4 included this time... didn't want to make it in all 3 :)

- ext: /data/data

- ext: /data/system

- ext: /data/dalvik-cache

- non-ext: /data/app

- non-ext: /data/app-private

So we don't touch the applications apk's,.

Downside is the internal space will go down when you install applications which is why the image file only is 900mb.

There are no issues with app installations (private / non-private / early-load), all non-asset data still ends up in ext and is thus fast, cached executables are still in ext (and usually loaded from there).

Drawbacks are that apps-firstruns are a bit slower and asset loading is a bit slower, but the positive side, I think is: less issues, and "free space" showing by system is actually somewhat sane.

In some cases, like games, this may be slower (loading) than putting everything in ext. For games that store all their imagery and such on SD card and normal apps (which usually have a many chunks of data, where each chunk is relatively small) this should bring the best of both worlds.

Pretty much what i want you to do is just see how it runs in regards to the above :)

Note: This is Chainfire's idea from the I9000 board :)
[Captivate Android Development] Zilch25:
Ahhhh okay, this would also kind of leave dbdata logically "closer" (since it doesn't get moved to EXT2 either) to the apps that are calling it too wouldn't it? Or am I just totally confused haha
[Captivate Android Development] Tayutama:
Didn't move /dbdata in the current versions :)
[Captivate Android Development] Zilch25:
That's what I mean :) apps were previously moved, while dbdata was left behind... would that separation between the app in EXT2 calling data from dbdata possibly slow response?
[Captivate Android Development] Tayutama:
Tbh doubt it. What Chainfire does in his lagfix is he makes a 100mb file on /dbdata and moves the content of /dbdata/databases into that, so he still keeps them out of the same file so..
[Captivate Android Development] Zilch25:
Hmm... I'm no expert on how quickly dbdata fills up, but wouldn't that fill rather quickly?
[Captivate Android Development] Tayutama:
Nah since dbdata only have 130 mb space to begin with it doesn't, it just makes it abit faster

The size of /dbdata/databases on my phone atm with all my normal apps is 1.95MB out of 125,23MB

So all he does it move that small amount into a ext2 file on his fix
[Captivate Android Development] Zilch25:
Oh jeez I totally forgot about the 130MB limit (guess it's been a while since I played with those NAND lag fixes =P).

First impressions (Just got back from picking up lunch and goofed around with it a bit): Snappy- got a 1899 quadrant score right off the bat, dolphin hd feels nice and smooth with 6 tabs open. I've certainly got no complaints about speed or responsiveness of the system at all.
[Captivate Android Development] Tayutama:
What about when installing apps or when on the market?
[Captivate Android Development] Zilch25:
Market is fast, installing apps still has a slight delay after the download completes where the notification dropdown is not very responsive though... I'm not sure if that's avoidable though =P
[Captivate Android Development] Tayutama:
Well might be in the AOSP rom they are making :)

I still want another filesystem then rfs though...
[Captivate Android Development] Krad:
this just killed my phone...

thanks
[Captivate Android Development] Zilch25:
Yeah that would be nice, hopefully Samsung does something about RFS being awful in the future =P
[Captivate Android Development] Zilch25:
That's rather nonspecific, a little detail on the problem and what you did prior to the problem would be more helpful in either helping you or preventing other people from having the same issue
[Captivate Android Development] Tayutama:
Think i'm going to add a note in my post on the i9000 board that it's highly recommended to flash a new firmware before doing the fix... ppl are whining about losing apps after the fix...
[Captivate Android Development] Zilch25:
It's good for a covering your ass precaution, but people seem to glance over huge bolded colored words of warning and go straight for the fix then yell at you when it doesn't work.

It's impossible to thoroughly test absolutely every setup under absolutely every set of circumstances- we don't do this stuff full time and we don't have a QA team. It's just me with Odin, a half dozen nandroid images, and a lot of patience =P
[Captivate Android Development] Tayutama:
Here is one of the latest examples:
[Captivate Android Development] Zilch25:
Yeah =/ We've had a couple like that too. I've tried to be very forthcoming with the fact that it's recommended to do this from a fresh flash. When asked personally I've told people they've got about a 50% shot of their installed apps moving without a hitch.

There's just way more going on in the background to make these fixes take than people realize. The more complicated the script gets, the more places it can go wrong... the more apps installed the more possible pitfalls.
[Captivate Android Development] Tayutama:
Well could be fixed i think if i could get it to move the stuff in a boot loop like Chainfire does.

That way almost nothing is running since the phone is in boot mode
[Captivate Android Development] Zilch25:
That's interesting, I was wondering if maybe things were fouling up because of the programs actually being in use. I figured though that it would result more in corruption than failure since apparently RFS doesn't mind accessing files while they're being accessed elsewhere.
[Captivate Android Development] Tayutama:
Now the biggest problem for me atm is that when Chainfire's userinit.sh runs at boot adb isn't active yet so i can't pull them off and see how his script is :(
[Captivate Android Development] gotfolk:
I personally have always ran Advanced Task killer everytime before applying your guys speed hacks... and have never had a problem with any of my apps disappearing.. now granted this last time around my widgets wouldn't load so i removed them all from the desktops and then placed them right back up and they all worked. thats been the only weird thing to ever happen.]

again thank you guys for all your hard work.
[Captivate Android Development] CharlesIstus:
Quick post to say thanks to Tayutama for sharing your abilities with us.

A second thank you to Zilch25 for being on the front lines of applying these fixes and being a guiding/answerman for all us beginners.

Third thanks for all the folks with an "answer" and not a epeen shot.

Without these folks we would be waiting on the "Apples/ATTs/Samsungs" of this game.

These folks make this community.
[Captivate Android Development] Zilch25:
Yeah and he's been adamant about not revealing his source code =(
[Captivate Android Development] Zilch25:
@ gotfolk, and CharlesIstus

Glad we were able to help you guys out :)

@Tayutama

The apk version of RyanZA's script automatically throws the phone into flight mode and kills active tasks, though I imagine that's not possible without elevating to the Javascript level.

The whole thing would probably be more graceful if the bulk of the movement could be done before the OS is in full swing though- really makes me wonder how that could be pulled off with as little user intervention as possible.
[Captivate Android Development] Tayutama:
Well not sure if adb isn't active at that point... think ill need to reflash to a 2.1 firmware and test it out :)

And to the others 2 others above thanks :)
[Captivate Android Development] Tayutama:
Should be easy i think... make the app do the first work and then let it reboot and then run what it needs to do at boot... ofc making the file before reboot
[Captivate Android Development] Zilch25:
Hmm but if you make the file before reboot it might cause issues with people who have a ton of crap installed... then again this could be rectified by making the EXT file smaller or doing a space-check before the script initiates ... hmm...
[Captivate Android Development] Tayutama:
You make the file on /data and not on /sdcard, you make the file around 100mb bigger then the amount of data you have /data, reboot, script runs and at the end it resizes the file to a desired value.

The resize thing is something i though about for v2.4.0 :)
[Captivate Android Development] Zilch25:
I was talking about installed apps eating up the NAND haha, but I see what you're saying, if you're making the file only slightly larger than the apps, restarting, migrating the apps into the file, resizing it, and then mounting it pre-OS it might do away with these issues with people's apps going *poof* when they install the fix that would be perfect :D
[Captivate Android Development] Tayutama:
This is what Chainfires fix does ;)
[Captivate Android Development] Krad:
I followed the instructions to a T. The script was going through its motions when my phone went black and would not respond to any button including the power button.

Once i took the battery out and put it back in, the phone rebooted to a trillion force closes... Just wiped and user oden3 to reload JH3.

with root explorer i just went and deleted all the junk the script made.
[Captivate Android Development] Zilch25:
Time to up the ante! You pump em' out and I'll nuke my phone with em'! haha
[Captivate Android Development] Tayutama:
The script auto reboots when it's done and it can take up to 10 mins to complete so ofc your screen goes black.

And if it isn't done when you pull the battery then you will need to reflash it
[Captivate Android Development] Zilch25:
How long did you give it? When the script is running it eats all of your system resources while it generates the gigantic EXT files. It can take up to around 15 or so minutes for the thing to run, and during that time bringing the phone out of sleep mode is very iffy. If you yanked the battery out during that process it's no wonder the phone wouldn't restart properly.

Edit: d'aww and I thought I was fast enough =P
[Captivate Android Development] Tayutama:
So you mean interactive menu can wait? :D
[Captivate Android Development] Zilch25:
Yes! Fault tolerance should probably come before UI ;)

Plus if you want to get really cute with it there's probably a way to check phone version to see whether or not it will need the jupiter file fix. Right now I think part of the problem we're having is that there's so many different versions it gives the end user too many possibilities to get mixed up
[Captivate Android Development] Tayutama:
There is a way... already using those checks to see if the system can use ext4 ;)

for ext4 i'm checking android version aka: if [ $VERSION != "2.2" ]; then balbalbal script else echo "Your system doesn't support this filesystem" fi