yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] A.VOID:
I'm not the only one to experience this. i could install the fonts fine, but when I applied them it didn't change the font.

I also started to see issues with the keyboard not responding. I would have an open text box and i typed on the keyboard, but nothing would display. I saw this in multiple apps. Kies mounting was acting up too, but I'm not sure that was related to the fix.
[Captivate Android Development] Tayutama:
Small update... Getting premissions denied :(
[Captivate Android Development] Tayutama:
Kies has always been weird in my case... reason i never use it :)

Well about the fonts i hope it will work for people when i'm done with the version i'm testing.
[Captivate Android Development] Zilch25:
Hm... well thats not good. Is it not grabbing SU?
[Captivate Android Development] Tayutama:
It's else i wouldn't get past the: Getting root priviliges...

What i'm trying to do is move the requires files to a folder on /data that the script creates so i don't need to have them in /system/xbin... that way you can have the busybox version you want yourself

But it doesn't even create the folder on /data since i get Permissions Denied
[Captivate Android Development] Zilch25:
Good point... I honestly have no idea =/ Do you have any leads?
[Captivate Android Development] Tayutama:
great not allowed to run busybox when it's on /sdcard... if i just do like normal when moving the files where busybox is on /system/xbin it works,..

next problem... it makes the file have a size of 0MB :)
[Captivate Android Development] Zilch25:
Weeeeeell you can always have it drop your own version of busybox in there under a different name like you did with mke2fs.... but the file size is another issue
[Captivate Android Development] Tayutama:
I know the reason it does it but not why :(

I'm trying to make the size of the file like this: Used /data size + 100MB = 0MB it seems...
[Captivate Android Development] Zilch25:
Hmmm, well does it have access to the answer to that query? Can it gauge the size of the /data folder at the stage in the script where it's checking? Then again if it were getting a permission denied it would be returning zero and the script should still tell it to add +100MB to that giving you a 100MB file, not zero... maybe there's just something wrong with the line in the script where it computes the size + 100?
[Captivate Android Development] Tayutama:
Added a echo $SIZE; sleep 60

Result: 47872+102400

so there is the problem.. they aren't getting added together the two sizes
[Captivate Android Development] Zilch25:
So it's just reporting back the equation rather than the answer?
[Captivate Android Development] darkamikaze:
"Download the update.zip of your choice and rename it to update.zip if you don't use Clockwork Recovery. if you do then it can keep the name."

As I learn more about android, reading this suggests when I do a nandroid backup with Rom Manager, it saves the Rom inside the update.zip file?

Also, if I just put any zip file in my internal SDcard, I am able to run the zip file? D: how do i go about this D:
[Captivate Android Development] Zilch25:
No, ROM manager creates a folder on your internal SD Card where it saves a snapshot of your current ROM. The update.zip that ROM manager creates just serves as the loader for the software.

When you do a fix like this you replace or rename the clockwork version of update.zip and if you need to roll-back you've got to either use ADB to rename the update.zip back again, or reflash/reinstall ROM manager to add the clockwork update.zip back.

(P.s. These fixes don't work too well when you use clockwork, so it's best to replace the clockwork version of update.zip with this one)

(P.P.s. If you aren't seriously savvy with this stuff you might want to wait until we get the bugs worked out of the new version of this- it will hopefully minimize the risk of your apps malfunctioning or not moving at all)
[Captivate Android Development] darkamikaze:
ahh I see I see, cool thanks. and one more question D: does this fix have any affect in battery life? Made me wonder if it makes the quadrant score go up so high .. has to be using more cpu or something lol :P
[Captivate Android Development] Tayutama:
True but that requires i can get past this problem...

SIZE=$DATA_SIZE_USED+102400

is how they are added together... and it should work damnit...
[Captivate Android Development] Tayutama:
Tbh it shouldn't have any effect on battery like but some people are saying they got increased battery drain since using the fix so yeah...

Not sure what to believe :)
[Captivate Android Development] Zilch25:
I personally haven't seen any changes in battery consumption, but some people have reported that it drains a little bit faster. I had mine running the EXT4 version yesterday morning, it was at about 85% when I installed it at around 11:30AM, and was at 40% when I went to bed around midnight... which is fairly inline with my normal battery life
[Captivate Android Development] Zilch25:
Hmm that's so bizarre, does it just not figure out the answer when it's run through the script? Can it answer the query if you enter it by just manually entering in the variables?
[Captivate Android Development] Tayutama:
nope same result...
[Captivate Android Development] darkamikaze:
yea.. I think I'll wait considering I don't really feel much lag but for here and there X_x.. I just wanted to see my quadrant score go nanners lol :P

and hearing about battery life makes me scared as I just got my phone and battery seems to be falling like cats and dogs. X_x thanks though :)
[Captivate Android Development] Zilch25:
Weird... is this taking place from the OS or during userinit?
[Captivate Android Development] Tayutama:
nvm fixed it... :D

solution: SIZE=$(($DATA_SIZE_USED+102400))
[Captivate Android Development] Zilch25:
You know the old saying: If it ain't broke, don't fix it. :)

If you're happy with your phone the way it is, then by all means, don't use any of these off-the-wall methods for improving I/O, Joe Blow probably wouldn't even notice the delays we're all knit-picking about. Also at least in my experience, the battery life seems to get less terrible in a few days of use. Do the old fashioned full drain and full charge- it should get less awful :)
[Captivate Android Development] Zilch25:
Woohoo we're back on the tracks! So it was just a syntax thing... I figured with it returning a 0. If it had just been having trouble with figuring out what $DATA_SIZE_USED was it would still be returning 0+100=100, but having a zero kinda told me it was refusing to do the math at all :)
[Captivate Android Development] Tayutama:
from one problem to the next :D it won't make the file now ^^

but that should be easy
[Captivate Android Development] Zilch25:
Hope so :D Is it just not finding the right tools to create it?
[Captivate Android Development] Tayutama:
nah the variable for the file didn't exist :D
[Captivate Android Development] jesangc:
question about flashing OTA after applying the fix

i am new to this whole android thing, so please have mercy on me if i sound ignorant. i applied this fix after rooting my phone (i didn't load any custom rom or anything though). i definitely notice a difference and really like the fix. thanks for the fix btw! my question is; if at&t comes out with an over the air firmware update, and i upgrade using that, what happens to the fix? do i need to reapply the fix? do i need to undo the fix before doing the OTA firmware update? i don't know how OTA firmware update works and where it stores the new firmware before applying it, but would this fix hinder the temporary storage mechanism of the OTA firmware upgrade? thanks in advance for fielding my ignorance.
[Captivate Android Development] Zilch25:
Good question... AT&T hasn't released any OTAs yet... so it's a mystery. I'd be prepared to wipe the phone though. You'd have to reroot, re-enable sideloading, and re-remove the AT&T garbage anyway :)
[Captivate Android Development] Tayutama:
Right scripts runs like it should... lets see if userinit.sh does what it needs to do :D
[Captivate Android Development] gotfolk:
drum roll.....
[Captivate Android Development] Zilch25:
Haha seconded!
[Captivate Android Development] Tayutama:
haha :)

Well userinit.sh does what it should do except for one thing... it doesn't make the /dbdata file
[Captivate Android Development] Zilch25:
Well then it's at least doing 3/4 of what it's supposed to do :)
[Captivate Android Development] gotfolk:
Im always keeping up with your guys thread..

i saw earlier you wanted more people to test things out on the phone... i def dont mind being a test mule, i have my son this weekend so my testing time is limited but in between naps and changing diapers i can def lend a hand.
[Captivate Android Development] Tayutama:
True... Nandroid to a backup... install apps from titanium backup and run script again with some edited in userinit.sh

Good to know :)
[Captivate Android Development] Zilch25:
That's awesome, having more test-beds is always a good thing! Most of my testing is done from fairly sterile fresh installs and fairly minimalist app usage, so it's not as "real world" as it could be
[Captivate Android Development] Tayutama:
btw how big should we make the file on /data on reboot? since space used + 100mb isn't much :)
[Captivate Android Development] Zilch25:
Well hm, we seemed to have minimal issues with overloaded storage when we stopped at 1.5GB, so I'd say 1.5GB max. Is anything significant being left behind that could overflow the remaining ~300MB over time?

I *should* say 100MB, because once you drop down to ~185MB you get the low storage nag
[Captivate Android Development] Tayutama:
the applications apk's isn't getting moved since we are leaving /data/app and /data/app-private behind
[Captivate Android Development] Zilch25:
Oh okay, well then since /app and /app-private are the ones that will be growing over time we really shouldn't need to give system too much space. Yours for example, at least from that little snippet you pasted was only ~43MB. We'd have to make provisions for cache and the like, but based on that much I dont know if it would be worth it to give the system more than 500MB and that seems really generous :)
[Captivate Android Development] Tayutama:
that 43mb you saw i posted was stock with 1 app installed or so...

restoring titanium backup atm and size of /data is 190mb and growing.

so i was thinking maybe making the file around 700-800 mb or so.

but need to run the script again to see how much of the ~200mb in /data that gets left behind and how much goes into the file
[Captivate Android Development] Zilch25:
Hmm I would have though most of that stuff would be under /app- android really loves to spread the app storage space around doesn't it =P
[Captivate Android Development] Tayutama:
Right 130MB out of 192MB stayed behind in /data/app
[Captivate Android Development] Zilch25:
Well if we're not moving /app but we're moving everything around it we really shouldn't need to give to much space to the EXT file. I mean I suppose it would depend on how fast cache builds up, and how much app data *does* end up in it. That's kind of a hard variable to keep track of methinks
[Captivate Android Development] Tayutama:
well out of those 130MB i got 1 apk that has a size of 70MB :)

The Sims 3...
[Captivate Android Development] Zilch25:
Ahhh well AT&T doesn't love us enough to give us popular video games... they preload our systems with pay GPS apps =P
[Captivate Android Development] Tayutama:
well The Sims 3 is the version that they get with the Vibrant :D

ok time to test again...

got it to make the file on /dbdata now but doesn't mount it yet
[Captivate Android Development] Zilch25:
If its not one thing it's another haha, I'm still trying to figure out how we should distribute the space =P It's a little more confusing than I thought
[Captivate Android Development] nammyczc:
So I tried installing fonts, and it didnt work, when I removed the lagfix ext2 2.3 fix it showed up and then I reinstalled it and the font change back to default. Any Idea why this is happening?

EDIT: I'm on stock rom jh6 with battery circle and evo4 black bar mod and ext2 2.3 lagfix
[Captivate Android Development] Tayutama:
Ups minor mistake... got it to be stuck in a boot loop
[Captivate Android Development] Zilch25:
I've got absolutely no idea =/ I've never tried installing custom fonts so I haven't even the foggiest idea of where they go.

Was it *all* fonts or just certain font packages you tried? Could you provide a couple so I can install them next time I run a test?
[Captivate Android Development] Zilch25:
Pfft as long as we get to stare at that pulsating "S" I'm sure we'd all be satisfied- it's a nice "S" ;)
[Captivate Android Development] Tayutama:
didn't even get to the "S" before it rebooted...
[Captivate Android Development] Zilch25:
Well then this is a MAJOR problem!
[Captivate Android Development] Fortune090:
Hate to just jump in the middle of all this, but what exactly are you 2 trying to do? lol
[Captivate Android Development] Zilch25:
Haha some refinements to the existing lag fix.

More specifically using the userinit script to move the data before the OS loads- we're hoping that will help solve some of the magical disappearing or chain FCing app problems :)
[Captivate Android Development] Tayutama:
us 2? bah :)

atm it's only me that is testing... :D
[Captivate Android Development] Zilch25:
It's true... ATM I'm just providing morale support- at least until he gives me new test code to brick my phone with! He's hogging all the bricks :(
[Captivate Android Development] Fortune090:
Oh ok, gotcha. Wasn't entirely sure... Heard a bunch of talk about FFXIV though. ;) I miss XI... Too bad I don't have a computer that can handle anything anymore... >.<

But anywho, back on topic. Hasn't someone already had a working userinit lag fix running?
[Captivate Android Development] Zilch25:
There was one that used userinit to enable an EXT3 partition on the microSD card (Sorta like mimocan's). This one is still using the same loop0 trick that the other versions of this fix uses- it's just doing all the footwork during boot instead of while all the apps are open.

We moved the FFXIV discussion junction into PMs haha
[Captivate Android Development] Tayutama:
Which i'm playing while i'm doing nandroid backups between tries...
[Captivate Android Development] Zilch25:
I'd be doing the same while waiting for new revisions... if it werent downloading at 10kbs and stuck at 2.2% >=(
[Captivate Android Development] Fortune090:
Oh ok, makes good sense. It'll get rid of all the issues people have had with apps getting corrupted... I had a low memory issue with the last ext2 flash I had... Think it was because I had JH2 without GPS logging turned off... A bit wary about flashing it again until something is set.

Gotcha, haha. ;)
[Captivate Android Development] Zilch25:
The new version also checks your phone version and applies XML fix/log removal automatically :)
[Captivate Android Development] RyanZA:
Just a heads up!

Here is an easy to use APK version of the lagfix - http://xdaforums.com/showthread.php?t=760571

It is a pretty simple lag fix, that does nothing special - only goal is to be easy to use, easy to install/remove, and to have as few complications and problems as possible. It also does a ton of checking to make sure everything is OK, and if something goes wrong, it will undo the lag fix for you!

And thanks to Zilch for helping me test it out a bit! :)
[Captivate Android Development] Zilch25:
Oh nice you finalized it eh? Still working on the V2 version, or is that too much of a nightmare to perform while the system is actually rolling?

Added it to the OP!

Speaking of OP's once Tayutama wraps up his current iteration of the lagfix I'll probably create a new thread... this one is rather daunting to newcomers ;)
[Captivate Android Development] RyanZA:
Haha, you really made this thread long enough. ;)

The APK doesn't seem to be the place for V2s or anything complicated. I spent 10 seconds actually thinking about it, and the type of person the lagfix APK is aimed at is the one who can't run these update.zips properly.

That person doesn't care if quadrant is at 2100 or 2200, or probably even if he has 1GB or 1.7GB of space. He just wants it to work!

So I went the other way, and made a 1.0+ version that is in the APK. It is very simple, it does no deleting at all (deleting is what causes any and all problems). It checks every thing it can, it rolls back properly if it hits any errors.

If it is bug free, then it is the perfect beginner lag fix. Like a gateway drug! :D
[Captivate Android Development] nammyczc:
[Q]Originally Posted by nammyczc

So I tried installing fonts, and it didnt work, when I removed the lagfix ext2 2.3 fix it showed up and then I reinstalled it and the font change back to default. Any Idea why this is happening?

EDIT: I'm on stock rom jh6 with battery circle and evo4 black bar mod and ext2 2.3 lagfix

I've got absolutely no idea =/ I've never tried installing custom fonts so I haven't even the foggiest idea of where they go.

Was it *all* fonts or just certain font packages you tried? Could you provide a couple so I can install them next time I run a test?[/Q]

I got these fonts from the themes thread for the vibrant fonts,

http://xdaforums.com/showthread.php?t=759642

Specifically, I installed the burton font and the darkness font, both I tried and both didnt register upon restart of the phone.
[Captivate Android Development] Zilch25:
Yeah once you get em hooked they start coming back for more and more lagfixes, before you know it they're playing around with custom kernels, international roms, and overclocking. Oh god they used to be such GOOD KIDS till they fell in with that lagfix crowd!

I still personally worry about the person who doesn't get update.zip figuring out how to use the root part of the apk though :) The app is *almost* granny-proof but thats the only part that requires a moment of thought (or worse... reading the instructions).

I'll make sure the next thread has a nice compilation of the different methods and what they bring to the table, if either of you guys want to throw me some bullet points you want me to put in there I'll be sure to note it- just toss me a PM with whatever blurbs you'd like.
[Captivate Android Development] Tayutama:
hehe true... i got problems atm with boot looping after fix ^^

had it going till it had to mount /dbdata and then removed something i shouldn't have done so it reboots all the time instead off only once :(
[Captivate Android Development] Zilch25:
Okay! I'll be sure to toss those into my test runs to see if we can't get to the bottom of it. It might be something specific to the vibrant fonts (we can only hope).

That's bizarre, chainfire was able to move the dbdata wasn't he? I wonder what's going on differently?
[Captivate Android Development] Tayutama:
i got it moved but i remove something i shouldn't in the script so it reboots all the time instead of just once like it should :) should have it back though now
[Captivate Android Development] Zilch25:
*fingers crossed*
[Captivate Android Development] Tayutama:
crap still doesn't mount /dbdata...
[Captivate Android Development] Zilch25:
Does it generate any sort of error? Or does it just conveniently skip that line of the script?
[Captivate Android Development] Tayutama:
it's skipping my if condition...

so it never makes the folder it needs to mount into...
[Captivate Android Development] Zilch25:
Which means it's either not meeting the condition of the if statement or there's some sort of syntax issue along the line... at least in theory O_o
[Captivate Android Development] Tayutama:
just ran the lines that i'm using in the script in adb... mounts just fine there...
[Captivate Android Development] Zilch25:
Well that makes it even more strange. Is there something that might be preceding it in the script that might be causing the script to terminate before completion?
[Captivate Android Development] Tayutama:
i think i found the error... the script was using: losetup /dev/loop1 /dbdata/dbdata-ext4 instead of losetup /dev/loop1 /dbdata/dbdata:image.ext4
[Captivate Android Development] Zilch25:
Hope that does it :D
[Captivate Android Development] Tayutama:
aaaaannnnnndddddd another nandroid backup :(

for some reason something different goes wrong every time...
[Captivate Android Development] Zilch25:
Just gotta keep chipping away at it, and eventually you'll fish out all the faulty spots and you'll be left with a solid mass of code!

You're this far along there can't be THAT many show-stoppers left :)
[Captivate Android Development] Tayutama:
wanna bet? :D since the code already should be perfect...
[Captivate Android Development] Zilch25:
Haha I'm just being optimistic!
[Captivate Android Development] Tayutama:
bah going to sleep on it...
[Captivate Android Development] Zilch25:
Probably a good idea, you've been plugging away at it all day =P It'll probably hit you while you're sleeping though- that crap happens to me all the time
[Captivate Android Development] gerbick:
I saw back on page 92 or 93 that one other person was unable to get the rest of their software back because of no Market app.

Does this still remove all of the apps? I had to recover, flashed with JH3 via Odin and reapplied Unleash the Beast; but would love to fix the lag problem I can witness on my Captivate.
[Captivate Android Development] [DT]:
OK, this is a weird (but interesting) one :)

I decided to try the ext4 fix this afternoon. Before I did it, I used ROM Manager to create a backup, though the current update.zip was actually the ext4 fix (I used the ext4-root version). I ran the ext4-update.zip via ROM manager (using the original filename), it ran, I rebooted, and it seemed to run just fine, but I didn't have the SL4A app. So I re-ran it via the regular recovery mode (Vol up+down+power) by renaming the file to update.

This time the SL4A app showed up, and I selecting the ext4 script, it seemed to run, but apps starting crashing. I let it complete, and when I rebooted, EVERYTHING was FC'ing all over the place (some of the core apps did fire up, because I was getting email notifications).

So...

I downloaded the Odin 3 bundled with the stock firmware (original non-leaked, which I guess is JF6?), got the phone into download mode (not sure why this is so tough?), flash a fresh, OEM ROM. The phone fired up, everything looked fine (though crap-tacularly stock :D). So I connected the phone, accessed the SDCARD, and moved the backup-update.zip to the SDCard root, renamed it, went back to recovery, got the ROM Rec menu, selected Nandroid [restore], and 10 minutes later, I'm back to EXACTLY where I was before the ext4 attempt. Odin, ROM Man, etc., all worked AMAZING. Nice job to the various developers.

The weirdness? The phone is SMOKING fast. No lag. Opening app grid? Super fast. Smart Shortcut? It used to have a big lag when opening it from the home screen. Now it's instant. Locked? No problem, instant unlock.

It's almost like the ext4 fix took and the restore applied the backup to the faster filesystem[?] I haven't really sat down and thought about the logistics of everything that happened, but _something_ has greatly affected (for the better) the speed (and the lagginess). Could it be the cache was flushed by flashing a new stock ROM and restoring?
[Captivate Android Development] Tayutama:
Right this is giving me to much trouble... so scrapping the idea with dbdata
[Captivate Android Development] Zilch25:
Well you probably didn't need to move dbdata anyway- it's already really fast =P
[Captivate Android Development] Zilch25:
The new version Tayutama is working on *should* do away with this problem

@ [DT] I have absolutely NO idea what happened there lol, but I'm glad it worked!
[Captivate Android Development] Tayutama:
next problem... making the remove fix script :D
[Captivate Android Development] Zilch25:
That's what Odin's for :p haha
[Captivate Android Development] Tayutama:
^^

already got the firmware check in place with the jupiter.xml file :)
[Captivate Android Development] Zilch25:
Sweet! Sounds like we're getting closer to testing time :D

Also a certain something finished downloading last night... it's installing now