yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Tayutama:
Where did you get the one in /system/bin?

Because i don't have one there... but i guess i can set the script to delete the one in bin also or else i need to specify in the script to use /system/xbin/mke2fs instead of just mke2fs
[Captivate Android Development] Zilch25:
A previous install of busybox... when you run their installer it automatically sets everything up in /bin by default. Probably a good idea to have it kill the one in bin or replace it since A LOT of people are going to have prior busybox installs to contend with. I guess you wouldnt run into this hiccup with EXT2/3 assuming the end-user had busybox 1.17 previously though

The other side of this though, is what happens when people update their busybox versions and end up overwriting mke2fs, is that going to retroactively screw things up or is mke2fs unnecessary after file creation? If that's the case it might be prudent to tuck the correct version away somewhere and have the script explicitly calling it
[Captivate Android Development] Tayutama:
well already deleting alot in /system/bin anyway so one more or less doesn't matter much :)

Ofc what i delete is included with busybox ^^

Ill make a new version then
[Captivate Android Development] Zilch25:
Okay, I'm rolled back again so just bump when you post up the new version.

Kind of a pain that busybox doesn't include this stuff to begin with =/ There's so little consistency with the releases
[Captivate Android Development] Tayutama:
Hmm the file is needed for removing the fix also.

If i can make the script like i want to later i can get away from that and only use resize2fs with the remove fix, but atm mke2fs is needed

File attached
[Captivate Android Development] Zilch25:
That's why I was thinking... once people install this fix they're going to go hog-wild installing apps and the like... and along with that most likely a new version of busybox which brings its own broken version mke2fs and would make uninstall impossible (but not before shuffling user data around to the point of requiring a wipe).

Downloading/installing now!
[Captivate Android Development] Tayutama:
hmm where to put the file then

btw got a fun result from running ext4 script here:

$ df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 162.8M 0 162.8M 0% /dev
df: /mnt/.lfs: Function not implemented
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/stl9 275.8M 251.4M 24.4M 91% /system
/dev/block/mmcblk0p2 1.9G 1.5G 385.8M 80% /data
/dev/block/stl10 127.2M 1.1M 126.2M 1% /dbdata
/dev/block/stl11 30.1M 48.0K 30.0M 0% /cache
/dev/block/stl3 5.9M 4.0M 1.9M 68% /efs
/dev/block/mmcblk0p2 1.9G 1.5G 385.8M 80% /data/app
/dev/block/mmcblk0p2 1.9G 1.5G 385.8M 80% /data/app-private
/dev/block/mmcblk0p2 1.9G 1.5G 385.8M 80% /data/data
/dev/block/mmcblk0p2 1.9G 1.5G 385.8M 80% /data/system
/dev/block/mmcblk0p2 1.9G 1.5G 385.8M 80% /data/dalvik-cache
/dev/block//vold/179:1
5.8G 114.3M 5.7G 2% /sdcard
/dev/block//vold/179:9
7.4G 6.9G 495.7M 93% /sdcard/sd
$
[Captivate Android Development] Zilch25:
You could conceivably rename it to something else and put it into bin/xbin without having to worry about busybox messing with it... something like ext4mke2fs =P Has a ring to it!

Script ran great this time, hitting 1833 without the AT&T tax on my tweaked up nandroid backup with EXT4

I got this:

df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 162.8M 0 162.8M 0% /dev
df: /mnt/.lfs: Function not implemented
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/stl9 275.8M 210.5M 65.3M 76% /system
/dev/block/mmcblk0p2 1.9G 1.6G 296.8M 85% /data
/dev/block/stl10 127.2M 2.1M 125.1M 2% /dbdata
/dev/block/stl11 30.1M 116.0K 29.9M 0% /cache
/dev/block/stl3 5.9M 4.0M 1.9M 68% /efs
/dev/loop0 1.4G 81.2M 1.4G 6% /data/data-ext4
/dev/loop0 1.4G 81.2M 1.4G 6% /data/app
/dev/loop0 1.4G 81.2M 1.4G 6% /data/app-private
/dev/loop0 1.4G 81.2M 1.4G 6% /data/data
/dev/loop0 1.4G 81.2M 1.4G 6% /data/system
/dev/loop0 1.4G 81.2M 1.4G 6% /data/dalvik-cache
/dev/block//vold/179:1
13.4G 1.1G 12.4G 8% /sdcard

What the heck is eating all of your storage space? Do you have an ext2 file living inside your ext4 file?
[Captivate Android Development] Tayutama:
Notice the /dev on yours and mine next to /data/data-ext4...

got no idea why it does that but it mounted it to /dev/block/mmcblk0p2 which is /data...
[Captivate Android Development] Zilch25:
Oh wow I didn't even notice that... and you're running the exact same script I am?

What the heck is up with that? It's not using loop0 O_O

So yours created the file but decided it didn't want to use it?
[Captivate Android Development] Tayutama:
I Pretty much yeah....

Think ill change the userinit.sh to it doesn't use variables anymore... but no idea why it did that on mine... since it have worked before with this script
[Captivate Android Development] Zilch25:
That's really strange... it's like these devices have a mind of their own. It's just bizarre that people have such varying results even when they're running the same components
[Captivate Android Development] max_warheads:
Just to chuck my two cents ;-)

Id say that using our own known good executables seems to be a good idea. Prefix with lf_ such as lf_mke2fs and then off we go.

Also, for the problematic su command and user input after it, why not simply collect all the information we need prior to making the call to su, solving our problem. There may be tidbits we need to work with in the same scenario but we should be able to figure all of that out as we go.
[Captivate Android Development] Tayutama:
Agreed...

Right removed the changes i made to updater-script so it doesn't delete mke2fs and that from /system/bin, renamed the 3 files and changed the scritps to called those.
[Captivate Android Development] Zilch25:
Lol reverting my nandroid again =P
[Captivate Android Development] max_warheads:
Lmao
[Captivate Android Development] Tayutama:
^^

I should be thinking about bed soon... it's 3:40am here in denmark ^^
[Captivate Android Development] max_warheads:
Only 9:41pm here

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] Zilch25:
Yeah 9:42 here... but we do appreciate your willingness to tweak bash scripts with fuzzy vision :)

Running the update.zip as we speak
[Captivate Android Development] Zilch25:
If it helps you sleep any better: The script applied properly and there's almost no fire coming out of my Captivate (just the usual amount that AT&T installed).

1764 quadrant
[Captivate Android Development] Tayutama:
Guess ill sleep then and release this version when i get up.

Ill check here first to see if you find some bugs though :)
[Captivate Android Development] Zilch25:
Yeah I'll run it overnight and see if it breaks anything, but I doubt we'll find anything that hasnt already turned up with the other fixes
[Captivate Android Development] Tayutama:
Well you never know... :)

Anyway goodnight :)
[Captivate Android Development] Zilch25:
Nite, thanks again for all the effort! I'll hold off linking this out in the OP till you make it official!
[Captivate Android Development] Clienterror:
Dang that ext4 is nice! I finally got all my apps to install where their suppose to be wahoooo! But here's the weird thing, I'm losing my internal memory space as I use my phone. It started at 296, and now its down to 242. It seems to drop a lot if I use google maps...is there a way to delete that info or what's up?
[Captivate Android Development] Zilch25:
I might be wrong, but the reason the 2.2 version of RyanZAs fix didn't work is because there were some programs that were ROM backed, like the google apps and they would stop working properly once they got moved from the dbdata folder into the virtual one. It stands to reason that these same apps would still force storage into the same areas on the phone and fill it up slowly.

Kinda makes me wonder if maybe we should be using 1.2gigs or so so that dbdata can grow safely without putting us near the low memory threshold

The way it is now, we've got about a 100MB buffer to use for dbdata stuff before the phone goes into low memory mode. Which is ALSO stupid because instead of setting an actual numerical threshold they decided to go with a percentage. For example nexus ones could safely get down to 20MB internal memory before the phone flipped and started dropping text messages and restricting market use... we get it at 185 =/
[Captivate Android Development] Clienterror:
Dang so basically were doomed for low memory no matter what we do?
[Captivate Android Development] Zilch25:
I wouldn't go THAT far, since dbdata is just application data, not apps, so I suppose over a long enough timeline and an impossible amount of terribly data intensive apps you would run out of memory. Perhaps for Joe blow who doesn't have a ton of apps the 100MB margin for dbdata is probably enough, but I think I'd personally prefer a larger margin, at least until a more elegant solution to the problem is found.
[Captivate Android Development] Clienterror:
Hmmm yea I see what you mean. The only thing is I've only had the ext4 lagfix on my phone for 4 hours and I've used google maps like 3 times playing with gps settings and I went from 296 to 242? That's nuts, if I open it like 5 more times I'll have a low mem warning :-p
[Captivate Android Development] Zilch25:
Out of curiosity are you running JH2?
[Captivate Android Development] IStern:
One observation...after a few days of uptime the lag comes back. Perhaps due to a less efficient ext2 since there's an avg of 65mb of ram free instead of ~120 after a fresh boot?
[Captivate Android Development] Zilch25:
Hmmm file system shouldnt effect your usable RAM... have you installed anything new recently?
[Captivate Android Development] Clienterror:
Yea, think that might be the issue? Maybe I'll try jh1 tonight. Just for the heck of it I did *#*#1472365#*#* and wiped my gps data and did the location test or what ever its called and it gobbled up 10 more megs in like 2 minutes.
[Captivate Android Development] IStern:
Sorry, just to clarify. From what I understand ext2 achieves speed and efficiency by buffering writes using ram. After a few days of phone usage I tend to have around 65mb free, which means ext2 is forced to perform more writes directly to disk? Just wondering...
[Captivate Android Development] Zilch25:
Actually that might be exactly your problem, in the JH2 thread they mention that JH2 is a test build, and due to the push to resolve GPS issues they've got GPS logging turned on which DEVOURS drive space. You can edit an xml file to turn it off.
[Captivate Android Development] Zilch25:
Hmm I wish I knew more about the specifics of EXT2 so I could confirm or deny this, but I generally have a pretty awful available RAM level at all times on JG6 and JH2 installs and I've never really noticed any ill effects.
[Captivate Android Development] Clienterror:
Yep you were 100% right, I loaded the stock rom and I'm not having any issues. So yea unless you turn off the GPS logging in JH2 it will obliterate your 297mb remaining storage. It's kinda funny because supposedly JH2 fixes GPS by letting you track more than 8 satellites....but when I just went outside and tested GPS with the stock rom I locked on to 10 lol. I think I'll just stick with the stock rom since all it does is "Help" GPS but I didn't notice much of a difference.

sssssooooo.

*******WARNING*****

This fix +JH2 with GPS data logging left on will get you a low memory warning fairly fast.
[Captivate Android Development] Zilch25:
Oh if you want to see things fly load up JM5 (You lose haptic feedback though =/) and throw on Samset or one of the other optimized I9000 ROMS... I'm only goofing around with the stock ROMS for the sake of testing out these fixes for you guys... the I9K ROMS are miles ahead of us
[Captivate Android Development] IStern:
quick question, would loading jh2 wipe all my user data/apps/etc?
[Captivate Android Development] Zilch25:
Yup it's a full firmware flash so it would wipe everything on your internal NAND storage
[Captivate Android Development] Clienterror:
If I do JM5 and then samset do I have to do A2SD lagfix to make it fast? Or is samset that bad ass out of the gate?
[Captivate Android Development] Zilch25:
You've gotta do Samset 1.9d without using his lagfix kernel (Its an i9000 kernel and won't work on the cappy), then you can throw on the EXT2/3/4 lagfix the same way you do with stock and it'll be smokin... and look pretty good doing it
[Captivate Android Development] Clienterror:
Ok so just to clairify. I flash the JM5, root it, then load the samset 1.9d .update.zip and I'm GTG?
[Captivate Android Development] kennethpenn:
I may have bricked the un-brickable. My device will not boot into download mode after the EXT2 (v2.3). Really odd. I've been able to get into download mode very easily, but now I can't. Something's up.

Notice the "mount: invalid argument" stuff.
[Captivate Android Development] Clienterror:
Have you tried to get to download mode manually? or are you doing "adb reboot download" in terminal?
[Captivate Android Development] kennethpenn:
Manually. Adb won't work when my phone is in: PHONE--/\--COMPUTER mode.
[Captivate Android Development] Zilch25:
Heck if you can get it into even recovery mode you can use ADB to go to download mode.

If not:

Pull out the battery, pull out the sim and SD

Open up Odin

Put the battery back in

Plug in USB

Push the two volume buttons (not power) and it should go to download mode
[Captivate Android Development] kennethpenn:
Weird... I've been getting into Download mode from PHONE--COMPUTER screen by pressing all three, waiting till the screen goes black, and letting go of power.

Any way to get into recovery from this phone--/\--computer screen?
[Captivate Android Development] kennethpenn:
Nice! Designgears gave me this procedure which worked:

pull the battery, sim card, sdacard...

put in the battery, hold volume down, plug in the usb cable and keep holding volume down until you get into download mode.

Super super odd. I've been getting taking this thing into download mode like every 2 minutes since I've had the device. Never had a problem till now!
[Captivate Android Development] Zilch25:
Hmm usually the two black screen flash trick works from the phone/computer screen... are you using stock firmware or are you using one of the I9000 ones? If you're using the I9000 its usually just volume down instead of both volume buttons

Edit: Ah, guess it works for regular stock captivate then too, assuming you were using a stock cappy rom
[Captivate Android Development] kennethpenn:
I was on JH2. I was freaking out, because I'd taken this thing in and out of d-load mode like 100 times before with the two black screen flash trick. Always worked for me.

Maybe JH2 only requires Vol Down? I dunno. Anyways, thanks for the help! Re-doing the EXT2 now... working fine.
[Captivate Android Development] Zilch25:
Ya know come to think of it I think I had an issue like that too... when you flashed did you use the pit file or did you just flash it straight up?
[Captivate Android Development] kennethpenn:
I used the PIT file.

BTW: Just for kicks and giggles:
[Captivate Android Development] acandia007:
Isnt that going to drain the phones life?

Because thats pretty dope..im tempted, bt dont wanna mess up the phone
[Captivate Android Development] Tayutama:
Right seeing as Zilch25 hasn't found any bugs with the current test build ill go publish it on the i9000 board and he can link to it in here :)
[Captivate Android Development] Zilch25:
Ahhh that explains it. When you use the PIT file from samsung-firmwares it seems to convert the phone over to the I9000 button combos... so download mode is now down volume on power on and recovery mode doesnt work unless you invoke it from adb
[Captivate Android Development] Zilch25:
Worked like a charm all night! One issue encountered on the captivate though, but it isn't due to your script. Apparently our new firmware (JH2) that we're all flashing from Samsung-firmwares has gps logging enabled. This wouldn't be a huge problem but the log files are ENORMOUS and get deposited into NAND space outside of the EXT file... which results in the NAND filling up and throwing up the out of space error.

Fun eh?
[Captivate Android Development] Tayutama:
in /dbdata or another folder?
[Captivate Android Development] Zilch25:
I'm actually not sure exactly it's throwing the gps data (Hadn't looked that closely yet) but it's a known issue with this firmware, and using the dialer combo to clear the GPS cache fixed the problem for a user who was getting out of space warnings last night. So even if we cleared it out the issue would crop up after using the GPS a little bit.

Let me see if i can find out where it stores the GPS logs
[Captivate Android Development] Zilch25:
They're tucked into /data/gps/logs
[Captivate Android Development] Tayutama:
well it would be easy to add that folder to the fix but it will also fill up at one point.

btw spamming fileplanet atm... gief FF XIV beta key :(
[Captivate Android Development] Zilch25:
Yeah, the best way to handle it is to just disable the logging, you can just edit an xml file, push it back and fix permissions and gps logs are never a problem again.

Also wow they're doing beta keys for that already? O_O
[Captivate Android Development] Tayutama:
Yeah but they are limited... :( they release them in daily batches...

Fun part... you need an american ip to get it... vpn ftw :D
[Captivate Android Development] Zilch25:
I dont know why they do that... Theres so many ways around it haha
[Captivate Android Development] Tayutama:
Well Square-Enix might have told them to but dunno.

Btw i can make a zip version specificly for JH2 if you want but i just need that xml file from the firmware then :) and ofc what the folder it needs to be placed in
[Captivate Android Development] Zilch25:
Ill attach a copy as soon as I get back to the computer unless someone beats me to it!
[Captivate Android Development] Zilch25:
Alright! Home, the original file is the jupiter.xml.bak, the altered one that's running on my phone is jupiter.xml.

Also if you add this you should probably have it clear out the contents of /data/gps/log just in case someone had been running this pre-fix... apparently using GPS for a couple days is enough to generate 1GB of log file- that can't be intentional haha

Edit: Zipped because xda hates .xml files =P
[Captivate Android Development] Clienterror:
Yea man I'd believe it, I did the GPS position test for like 2 minutes and it ate 15mb lol.
[Captivate Android Development] Tayutama:
Right ill see if i can have the zip up and running before bed... aka 30 mins... and still no FFXIV keys released... damn fileplanet
[Captivate Android Development] Tayutama:
and what folder does those belong in Zilch25? :)

Nvm... /system/etc ^^
[Captivate Android Development] Zilch25:
Yup that's it :)
[Captivate Android Development] Tayutama:
Right you better be grateful.... just lost the chance to get a FF XIV key today...

They put them up while i was editing the script and they was gone 3 mins later...

The zips are up in the usual spot.... *CRY* :mad:
[Captivate Android Development] Zilch25:
:( Sorry about that... Who would have thought that trying to make our phones more snappy would come at such a high cost?
[Captivate Android Development] Tayutama:
problem is they only got keys till tomorrow also and well... this time i waited 4 hours and missed it with like 1 min...
[Captivate Android Development] Zilch25:
Well I'll try to get one while I'm at work tomorrow, If I manage to nab one I'll send it your way!
[Captivate Android Development] Tayutama:
ill be trying myself also :) btw so far it has been between now and 4 hours before (Dunno what timezone they go after but yeah... That is between 8pm and 12pm GMT+1
[Captivate Android Development] Zilch25:
That works fine for me... thats like lunchtime-clockout time, so easy peasy. Just nandroided myself back btw, tossing the update.zip up now!
[Captivate Android Development] amwbt:
I ran the update.zip, it rebooted the phone and I don't see an sl4a app. Can anyone tell me what I did wrong?
[Captivate Android Development] ovenfresh:
i ran the sl4a on my captivate, it reboots, and all my application are gone. under manage applications, theyre all still there, just my phone cant use them for some reason???
[Captivate Android Development] Zilch25:
I'm testing the current one now, I'll let you know if it does the same thing to me =/

Which version of the lagfix are you trying to use?
[Captivate Android Development] Zilch25:
Are you running the update.zip through clockwork or just through regular system restore?
[Captivate Android Development] amwbt:
I am rooted and I used update_v2.2.1_ext4_with_root.zip.
[Captivate Android Development] Zilch25:
If you're using clockwork to run this, try dropping the file on the root of your sdcard, rename it to update.zip and try running it through system restore... I've had clockwork do weird things
[Captivate Android Development] amwbt:
I went through Rom Manager and tapped reboot into recovery the 1st time then I just ran the update.zip straight through rom manager/clockwork.
[Captivate Android Development] Zilch25:
Thats veeeeeery strange. Are you using JH2 or JF6? I'll flash to stock and see if I can replicate it
[Captivate Android Development] Zilch25:
That's really bizarre. I just ran the latest version of it and all of my stuff transfered over without a hitch =/

Which version of the sl4a script were you running? I'll see if I can make it choke up too
[Captivate Android Development] amwbt:
I am using stock rom. Does it matter that I have not reversed the ext2 lagfix thats installed?
[Captivate Android Development] Zilch25:
Hmmm I'm not sure if that would affect it's ability to install the sl4a script since it's supposed to be in a different area of the device, but it very well could be the issue.
[Captivate Android Development] Tayutama:
Zilch25: hf with bug fixing ;) If there are any major bugs or something that needs fixing pm me since i'm going to bed now and ill see what i can do about it... might have time to fix some at work...
[Captivate Android Development] amwbt:
I just don't see the app in the app list to run the script. I can find the scripts in my file manager but no way to run them.
[Captivate Android Development] Zilch25:
It might be due to having a previous fix installed. The scripts themselves live on the SDcard, but the sl4a software itself has to be installed like any other app. Once you perform one of these fixes all of your data lives inside of a file, and it wouldn't be mounted or linked when you're at the system restore stage. So what's happening is that the update.zip is placing the files in the location where the phone would ordinarily look for apps, but since there's a fix in place those locations are no longer valid as they're all linked to the EXT file when the OS starts up.

In short, yeah you'd have to revert and probably have to reinstall the update.zip in order for the system to see sl4a :)
[Captivate Android Development] Zilch25:
Haha will do, hopefully we haven't stirred up the bee's nest =P
[Captivate Android Development] Tayutama:
sl4a is installed in /system/app so the fix shouldn't do anything about it.
[Captivate Android Development] amwbt:
Ok I will give it a try, and let you know.
[Captivate Android Development] Zilch25:
Well then... any ideas? lol
[Captivate Android Development] ovenfresh:
i was trying to use the ext4 one
[Captivate Android Development] amwbt:
Lol
[Captivate Android Development] Zilch25:
I'd still say try to revert it back and give it a whirl... It *SHOULDNT* behave that way, but one thing I've learned since I started messing with these phones is that NOTHING works the way it should and barely anything is consistent =P
[Captivate Android Development] Zilch25:
Okay and you were on JH2 or regular stock JF6?

Also just for giggles, have you manually restarted it since the phone auto restarted? I don't expect this to fix it, but just so that we can say we've tried all the obvious
[Captivate Android Development] amwbt:
That's cool. I think I'll just reflash stock rom and start over. It needs to be cleaned up anyway.