yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] ttabbal:
I'm honestly not seeing that here on my phone. I have tried running vmstat and watching the wa column as mentioned, nothing out of the ordinary. There's always going to be SOME wait time, unless you have really, really, fast storage. Even large apps launch in less than a second with the exception of big games like The Sims or "Let's Golf". Those take a couple more seconds to load the game data.

I'm not doubting that some people are experiencing this. I'm only stating it's not universal and as such I'm inclined to think that some people have a crap SD card. Anyone know if there's a ARM version of Bonnie++ or some other block device benchmark? That would help narrow it down. Even within a "class" of SD card, some perform better than others. The reason the NAND hack shows universal increases is that we all have exactly the same NAND chip, so it should be the same for everyone with a few % difference for manufacturing tolerances. I wonder if even a dd test would tell is anything? It's not great as a benchmark, but here's a little info anyway....

The last test reads file, the first 3 are writing to the SD.

Note that this is an older card, over a year old pulled from my G1, though I did re-format the ext partition. Transcend 8GB Class6.

# dd if=/dev/zero of=/sd-ext/test bs=4096 count=1000
1000+0 records in
1000+0 records out
4096000 bytes (3.9MB) copied, 0.192862 seconds, 20.3MB/s

# dd if=/dev/zero of=/sd-ext/test bs=4096 count=10000
10000+0 records in
10000+0 records out
40960000 bytes (39.1MB) copied, 3.493555 seconds, 11.2MB/s

# dd if=/dev/zero of=/sd-ext/test bs=4096 count=100000
100000+0 records in
100000+0 records out
409600000 bytes (390.6MB) copied, 44.746980 seconds, 8.7MB/s

# dd if=/sd-ext/test of=/dev/null bs=4096
100000+0 records in
100000+0 records out
409600000 bytes (390.6MB) copied, 28.367230 seconds, 13.8MB/s
[Vibrant Android Development] neasoon:
Mine is Kingston 4G class 4. The benchmark data using dd is shown below:

# ./test.sh
bs 4096, count 1000, write
1000+0 records in
1000+0 records out
4096000 bytes (3.9MB) copied, 0.256433 seconds, 15.2MB/s

bs 4096, count 10000, write
10000+0 records in
10000+0 records out
40960000 bytes (39.1MB) copied, 2.392162 seconds, 16.3MB/s

bs 4096, count 100000, write
100000+0 records in
100000+0 records out
409600000 bytes (390.6MB) copied, 51.346742 seconds, 7.6MB/s

bs 4096, count 100000, read
100000+0 records in
100000+0 records out
409600000 bytes (390.6MB) copied, 24.944529 seconds, 15.7MB/s

IO waiting during app launching and data operations is normal. What's strange is when using data -> NAND, the IO waiting for the app i tested is much below 50 and lasts for less than 3 seconds. if i move data to ext4, for the same app, the lag is too obvious, it's higher than 80 and lasts for tens of seconds.
[Vibrant Android Development] zimphishmonger:
Here are my results, just for comparison sake. Ran each test twice to ensure accuracy. 1GB EXT4 partition on 8GB Class 6 Kingston MicroSDcard. Using DC2SD v2 and Jac's Kernel

# dd if=/dev/zero of=/sd-ext/test bs=4096 count=1000

dd if=/dev/zero of=/sd-ext/test bs=4096 count=1000

1000+0 records in

1000+0 records out

4096000 bytes (3.9MB) copied, 0.269521 seconds, 14.5MB/s

# dd if=/dev/zero of=/sd-ext/test bs=4096 count=1000

dd if=/dev/zero of=/sd-ext/test bs=4096 count=1000

1000+0 records in

1000+0 records out

4096000 bytes (3.9MB) copied, 0.241636 seconds, 16.2MB/s

# dd if=/dev/zero of=/sd-ext/test bs=4096 count=10000

dd if=/dev/zero of=/sd-ext/test bs=4096 count=10000

10000+0 records in

10000+0 records out

40960000 bytes (39.1MB) copied, 4.277199 seconds, 9.1MB/s

# dd if=/dev/zero of=/sd-ext/test bs=4096 count=10000

dd if=/dev/zero of=/sd-ext/test bs=4096 count=10000

10000+0 records in

10000+0 records out

40960000 bytes (39.1MB) copied, 3.848269 seconds, 10.2MB/s

# dd if=/dev/zero of=/sd-ext/test bs=4096 count=100000

dd if=/dev/zero of=/sd-ext/test bs=4096 count=100000

100000+0 records in

100000+0 records out

409600000 bytes (390.6MB) copied, 93.103705 seconds, 4.2MB/s

# dd if=/dev/zero of=/sd-ext/test bs=4096 count=100000

dd if=/dev/zero of=/sd-ext/test bs=4096 count=100000

100000+0 records in

100000+0 records out

409600000 bytes (390.6MB) copied, 105.067939 seconds, 3.7MB/s

# dd if=/sd-ext/test of=/dev/null bs=4096

dd if=/sd-ext/test of=/dev/null bs=4096

100000+0 records in

100000+0 records out

409600000 bytes (390.6MB) copied, 29.614911 seconds, 13.2MB/s

# dd if=/sd-ext/test of=/dev/null bs=4096

dd if=/sd-ext/test of=/dev/null bs=4096

100000+0 records in

100000+0 records out

409600000 bytes (390.6MB) copied, 25.785440 seconds, 15.1MB/s

#
[Vibrant Android Development] krichek:
Not sure if I did it right as I'm still pretty new to all of this, but running the following commands from terminal I get the following results

#dd if=/dev/zero of=/sd-ext/test bs=4096 count=1000

1000+0 records in

1000+0 records out

4096000 bytes (3.9MB) copied, 0.065400 seconds, 59.7MB/s

#dd if=/dev/zero of=/sd-ext/test bs=4096 count=10000

10000+0 records in

10000+0 records out

40960000 bytes (39.1MB) copied, 2.606294 seconds, 15.0 MB/s

#dd if=/dev/zero of=/sd-ext/test bs=4096 count=100000

100000+0 records in

100000+0 records out

409600000 bytes (390.6MB) copied, 66.758999 seconds, 5.9 MB/s

#dd if=/sd-ext/test of=/dev/null bs=4096

100000+0 records in

100000+0 records out

409600000 bytes (390.6MB) copied, 22.617679 seconds, 17.3MB/s

This is on a Sandisk 16GB class 2 card.

For what it's worth I don't see any lag except for the intial 2 or 3 seconds on wakeup. Apps seem much snappier and everything appear to run much smoother.
[Vibrant Android Development] ttabbal:
Well, those all look pretty good. Krichek's Sandisk is smokin the small reads. :D

Not sure what to look for. Perhaps it's just the small random r/w that the databases are likely to produce? Much harder to test that with something like dd. Tens of seconds seems very strange indeed. Even the games I tried don't take that long.

Are there any particular apps causing problems more than the others? Perhaps if I install something that really sucks on your phone I can reproduce the problem?
[Vibrant Android Development] davbran:
So last night I wiped my phone back to stock and rooted, flashed data only init.d, flashed Kernel v6 and flashed ttabbal's dc2sd.

After that I ran through to make sure that my /dev/block/mmcblk1p2 was formatted properly. After I converted to ext4, like some of you it seems that RA 1.7.0 wasn't converting to ext4 when it said it did, I found the following on mount.

/dev/block/mmcblk1p2 on /sd-ext type ext4 (rw,noatime,nodiratime,barrier=1,data=ordered)
/dev/block/mmcblk1p2 on /data/dalvik-cache type ext4 (rw,noatime,nodiratime,barrier=1,data=ordered)
/dev/block/mmcblk1p2 on /data/data type ext4 (rw,noatime,nodiratime,barrier=1,data=ordered)

I don't know which flash is the culprit but obviously data wasn't the only thing move to the partition.
[Vibrant Android Development] krichek:
Lol, tell me about it! That was actually the slowest result I had on the small reads. Best was 82MB/s!

I'm not seeing any slow downs either, biggest loading hog for me would be the game Nova, and it is much faster when loading now.

If you need some more guinea pigs for data points let me know.. I'm always willing to help. :D
[Vibrant Android Development] neasoon:
Well, look at my vmstat output for Rom Manager:

procs memory system cpu
r b free mapped anon slab in cs flt us ni sy id wa ir
0 0 4168 76756 104136 12320 98 176 0 1 0 0 99 0 0
3 0 4012 76760 104252 12312 167 689 0 15 0 14 72 0 0
0 0 4452 65764 104216 12312 1716 1683 0 41 0 15 44 0 0
0 0 7192 62900 104272 12340 177 331 0 5 0 5 90 0 0
0 0 8212 62884 102972 12344 509 731 1 59 0 10 31 0 0
1 0 6196 62884 105272 12336 339 315 0 22 0 5 72 0 1
1 0 4992 62884 106496 12336 609 1480 0 48 0 16 37 0 0
0 0 6044 62884 105152 12336 178 284 0 10 0 6 84 0 0
0 0 6032 62884 105152 12336 245 240 0 0 0 3 73 24 0
0 0 6068 62884 105152 12312 146 100 0 1 0 5 95 0 0
1 0 6764 62884 104428 12312 195 228 0 5 0 3 92 0 0
0 0 6764 62884 104428 12312 115 104 0 1 0 2 96 0 0
0 0 6764 62884 104428 12312 181 232 0 0 0 1 99 0 0
~~ starts here
0 2 33932 61796 106012 12272 714 1351 37 26 0 21 6 48 1
0 2 33956 61780 106012 12276 331 286 0 2 0 16 0 82 0
1 1 33956 61760 106012 12276 297 134 0 0 0 8 0 91 0
0 1 33956 61824 106012 12276 285 248 0 1 0 4 0 97 0
0 1 31512 61972 108088 12256 358 387 6 57 0 6 1 34 1
0 1 31512 61972 108088 12256 403 526 0 1 0 2 0 96 1
1 1 31512 61972 108088 12256 386 154 0 3 0 9 0 88 0
procs memory system cpu
r b free mapped anon slab in cs flt us ni sy id wa ir
0 1 31452 61972 108088 12256 578 439 0 12 0 16 0 70 2
0 1 31452 61972 108088 12232 311 171 0 2 0 5 0 95 0
3 0 31404 62776 107272 12264 337 375 2 20 0 12 0 68 0
~~ ends here
0 0 28828 63980 108380 12276 418 1003 15 30 0 13 57 0 0
0 0 28828 63980 108380 12276 327 449 0 14 0 20 67 0 0
0 0 28852 63980 108384 12256 249 311 0 15 0 12 73 0 0

Between the lines marked by "~~", WA is very high. I didn't do any particular operation, i just clicked the Rom Manager icon to launch it. As a result of the SO severe IO waiting, a black screen kept for almost 10 seconds after i clicked the app icon and before the Rom Manager UI showed up.
[Vibrant Android Development] ttabbal:
2 0 8804 80592 169884 15180 740 1514 0 38 0 18 43 0 0
1 0 8804 80592 169884 15180 755 1577 0 40 0 14 45 0 1
3 0 8804 80592 169884 15180 727 1503 0 40 0 14 47 0 0
0 0 8804 80592 169884 15180 714 1499 0 39 0 15 45 0 1
0 0 8804 80592 169884 15176 745 1603 0 29 0 15 57 0 0
1 0 8804 80592 169888 15176 723 1492 0 39 0 14 45 0 1
0 0 8804 80592 169888 15176 717 1468 0 38 0 13 49 0 1

~~~~
0 1 9652 78248 170468 15216 1275 2370 5 32 0 18 19 31 0
1 0 6652 78344 172776 15212 651 421 12 66 0 7 5 22 0
0 0 4724 79192 173624 15264 5685 11164 4 44 0 19 5 29 1
3 1 4284 79252 173756 15272 750 1123 5 34 0 9 26 31 0
~~~~

1 0 4256 79280 173792 15272 201 228 0 20 0 3 78 0 0
0 0 4264 79280 173792 15264 182 204 0 0 0 5 96 0 0
0 0 4264 79280 173792 15264 187 216 0 1 0 4 95 0 0

There's mine, and I rebooted recently and haven't loaded ROM Manager since then. I don't get it, I'm getting very good performance this way. I'll keep thinking about it, but I haven't come up with anything yet that might indicate why some people get poor results outside of a badly performing SD card. The dd test shows you get good streaming writes, but flash memory does kind of suck at random, small writes sometimes.

I guess the controller in your phone could be having an issue, but that seems less likely as the SD bus is a pretty simple serial interface. You would almost have to try to screw it up.

I doubt it matters, but I'm running the stock ROM, not the deodexed or any of the leaked ones... I would think the kernel would be the thing to matter, but maybe.. Just trying to see if there's anything else about your setup that's different from mine.

Interesting note with the wakeup lag, it doesn't happen when I'm plugged into my computer. :D No idea why.
[Vibrant Android Development] ellopr:
Hi guys

This probably not the correct treat to post this question but if any of you can direct where to find the answer ofit without flaming me will be great. I have already search but can't find the answer and here at the moment you are talking about what I want to know. Is there any place where I can find a map or info on how the internal memory of the Vibrant is distributed and the type (specs of the memory).

I would like to understand why my vibrant lags more than my G1 ever did. A good comparison is Opera Mini. It never ever lagged on my G1(it took time to load but once it was up it was always snappy) and it lags terrible in my Vibrant without the NAND hack. With the NAND hack my applications fly. Where does the problem reside, in the specs of the memory, or in the way distribute or the file system it uses, where?? Are the 16GB of memory a different type of memory than the ROM memory?

It doesn't make sense that Samsung will equip this phone with a super fast CPU and GPU and then put a crappy slow memory in it (maximum when they are one of the biggest NAND memory manufacturers). If anyone can clarify this for me and probably for a lot of us that does not understand why a 2 years old G1 sometimes performed better than this phone I will really appreciate it.

Thanks in advance and be gentle if you are flaming me!
[Vibrant Android Development] neasoon:
i'm running the stock rom too, nothing special. i have very few apps installed, around 10, i think.

well, i reverted to /data/data -> NAND and kept dalvik-cache in /sd-ext. let's see the huge difference when loading Rom Manager:

procs memory system cpu
r b free mapped anon slab in cs flt us ni sy id wa ir
0 0 46472 63200 105364 11892 178 193 0 0 0 6 95 0 0
0 0 46460 63200 105364 11892 134 139 0 0 0 4 97 0 0
2 0 41352 62212 109196 11928 460 878 36 58 0 30 11 1 0
1 0 37996 64248 110036 11972 443 1103 20 35 0 20 45 0 1
0 0 38008 64248 110036 11972 315 422 0 13 0 16 71 0 0
3 0 38004 64248 110032 11976 354 517 0 18 0 18 65 0 0
0 0 36400 65680 110432 11988 214 440 0 33 0 18 49 0 0

Noticed it? wa is only 1. and it lasts only 1 second...
[Vibrant Android Development] krichek:
My results were almost identical (although slightly lower overall) I don't know how to get the output over to the computer screen tho and I really dont feel like typing ALL of that out lol.. Could the issue be more of an individual performance thing? For comparisons sake I'm running the deodexed rom and the kernel.

Want to know another interesting note? If I turn the phone on right after I hear the message tone (email, text, whatever) there is no wakeup lag then either.
[Vibrant Android Development] neasoon:
My results were almost identical (although slightly lower overall) I don't know how to get the output over to the computer screen tho and I really dont feel like typing ALL of that out lol.. Could the issue be more of an individual performance thing?

Want to know another interesting note? If I turn the phone on right after I hear the message tone (email, text, whatever) there is no wakeup lag then either.[/QUOTE]

connect your phone to your pc via usb, then run adb shell command to redirect the output to your pc.

for example, wanna vmstat, just run

adb shell vmstat

in your window's command line
[Vibrant Android Development] neasoon:
connect your phone to your pc via usb, then run adb shell command to redirect the output to your pc.

for example, wanna vmstat, just run

adb shell vmstat

in your window's command line
[Vibrant Android Development] ttabbal:
Well, nobody would argue that SD is faster than NAND. We all know it's faster. What we don't know, is how many write cycles it can take. With apps constantly writing data, I would be much more concerned about the internal flash on my $500 phone than I would the $20 SD card that I can replace anytime I want to. I would imagine that the large 16GB storage area is slower, but can handle more write cycles. I don't have the chip specs though, and I doubt Samsung would give them to me. It might not be a problem, but I have no way to know that.

What is your test like when /data/data isn't mounted/symlinked anywhere? Have you tried another SD card? ROM Manager takes about 3 seconds to start up, but once it's up it's quick. And it's still faster than starting it without any hack applied. And that's about the longest startup time I have outside of the games. Even DB heavy apps are snappy. I don't know what ROM manager is up to during initialization. Perhaps Koush would be willing to enlighten us as to what sort of I/O he's doing in there? I know he has to hit /sdcard for info about what is in the update.zip there so he knows which version of the recovery you have installed.
[Vibrant Android Development] numba1cuban:
I tried this and its what i am currently running but wake lag is still there and i get nowhere near 1700 quadrant im about 1500. I have tried every possible combination and so far nothing has improved the wake lag.
[Vibrant Android Development] krichek:
Using the same setup and wake lag is there for me as well unless I'm connected to the computer or turning the phone on right after hearing an alert. Quadrant scores are 1780ish for me.

Rom Manager loads almost instantly for me even from a reboot.. wa is never over 25 but Layar hits my phone the hardest of everything I've tried so far and even it is pretty acceptable. Screen shot below.
[Vibrant Android Development] ttabbal:
I'm going to have to think about getting me one of those Sandisk cards, sheesh. :)
[Vibrant Android Development] AustinKnight45:
So this is a REAL vibrant kernel like its not a EU version with buttons fixed ?
[Vibrant Android Development] zimphishmonger:
Yes, it was compiled using the open source code provided by samsung, modified\tweaked by @justanotherdev to include the ext4 support, and enable a mount & file system check of an EXT partition immediately on boot.
[Vibrant Android Development] danielmid84:
Flashed back to stock rom, lag was annoying the hell out of me
[Vibrant Android Development] zimphishmonger:
You are on the stock rom, you were just using a different kernel
[Vibrant Android Development] blackerwater:
I wonder if we could use this kernel or slightly modified to flash i9000 roms? Like fixing the reversed buttons and such.

Sent using xda app....
[Vibrant Android Development] justanothercrowd:
The lag issue seems to be in the source as Captivate kernels as experiences this too. I talked with scepterr about it. I am looking into a fix and will let the Captivate guys no when i find it. Comparing the logcats between stock Launhcer appears to be pausing and resuming for some strange reason.
[Vibrant Android Development] numba1cuban:
JAC do you have any idea when you will be working on the wake up lagg? I have been running this kernel for a couple of days now but its really starting to get annoying not when you are coming from the locked state but when in a call and you need to go into the phone to get a number it will take about 5 sec some times more to wake up and let you in. This thing makes the phone fly but it just need that little thing fixed and it would make these phones so much better. Thanks for you work we appreciate everything you do for us. Thanks
[Vibrant Android Development] danielmid84:
You knew what I meant lol
[Vibrant Android Development] sonofdays:
Push in the right direction?

I keep getting an error message when I try to flash this (Step #1). I'm going to detail all that I did so hopefully somebody can figure out what I'm doing wrong.

First, I downloaded all of the necessary files (I downloaded them all yesterday). I renamed vibinit.d.zip to update.zip and put that on the internal SD card (/sdcard). After that, I rebooted into recovery mode, scrolled down to reinstall packages and selected that option. It says:

-- Install from sdcard...

Finding update package...

Opening update package...

Installing update...

Installation aborted.

Any suggestions? All I've done to the phone prior to this is flash the phone with the su/busybox update.zip and I have removed some of the annoying default stuff (Slacker Radio, other useless apps, power on/off sounds..).
[Vibrant Android Development] neasoon:
don't use the stock recovery, use ClockworkMod recovery from Rom Manager
[Vibrant Android Development] zapote21:
After upgrading to v6, DDMS will not work and I get a ADB crash message. ADB by itself works fine, but DDMS will not work anymore. Any ideas? Its a minor issue, as I'd rather live with this kernel...LOL

Thanks
[Vibrant Android Development] imthekuni:
Force Close

So I downloaded all of the files earlier today (and a few more times throughout the day hoping to fix this) and followed the instructions from the OP.

Once I get the kernel loaded through Odin and the phone restarts, I get massive FC's of all the apps. Now should this be copying data and dalvik to the ext4 or fat32 partition? I have my external SD set up as fat32 for first and ext4 for second partition. But after I apply the kernel it looks like they are being copied to the fat32.
[Vibrant Android Development] siirial:
I am having issues with ODIN. I have installed all of the samsung usb drivers in my xp computer, including kies. ODIN recognizes my phone, it comes up in the first box as COM4.

I set the pit and pda per instructions, but when I click start, it just sits at "file analysis."

Anyone have an idea what I could be doing wrong?

thanks in advance
[Vibrant Android Development] krichek:
Are you using windows 7 64bit by chance? For some reason, some of us have issues on 64bit, move to a 32 bit system and you should be fine.
[Vibrant Android Development] skater4690:
anyone know if this will work for eugenes froyo rom?
[Vibrant Android Development] siirial:
Nah. I have 64 bit 7 at home. Out of town spending time with my parents, so I am using my fiance's laptop that has xp.

I figured if someone knew of an easy fix, then great. If not, I'll be home tonight and try it on my win 7. Too bad we are still restricted to ODIN which is windows only. Prefer linux or mac solutions, but gotta use what we know so far.

What kind of issues are you having with 64 bit? Usb drivers 32 bit only?
[Vibrant Android Development] siirial:
I could be wrong, but I wouldn't think so... I think this would only work with 2.1 vibrant only and if I remember correctly, eugene's FroYo is from the international 2.2 leak which is different in more ways than one
[Vibrant Android Development] masr1979:
I experienced the FCs barrage myself, so I went back to stock and applied this mod on a clean install, so try wiping before flashing.
[Vibrant Android Development] Jayrod1980:
Does everyone get the wake up screen lag (I used EXT-4 on my partition)? I'm thinking of using this simply for the better I/O performance, as the phone lags alot sometimes without a task killer installed.

The wake up lag scares me though. Also, I know the ROM itself remains stock, but the kernal is changed. Would this affect the phone's ability to receive updates?

For example, before I returned my first vibrant, I had it rooted and removed most of the bloatware. Before this, even rooted, my phone would just say "no firmware" when clicking the update button in settings. After removing the bloatware, it would say "error, SIM (something or other), or check network." To me this says that it's checking for a stock image and since my phone doesn't match, it wouldn't update even if there was one. I was using Titanium Backup so none of the bloatware removal was permanant.

Long story short, if I were to update to this kernal, but have an otherwise stock ROM with root (ie. all bloatware still on phone), could it theorectically receive the awaited OTA 2.2 update whenever Samsung/T-mobile come out with it? Or will I be having to flash it from here like with the G-1 I had rooted the last almost 2 years?
[Vibrant Android Development] anomalous3:
One thing I noticed about the latest kernel (version 6) is that in ADB, an ls command returns all sorts of weird stuff around the actual files/contents listed, such as

#ls
ls
←[1;34mcache←[0m ←[1;34mlib←[0m
←[1;34mconfig←[0m ←[1;32mlpm.rc←[0m
←[1;34mdata←[0m ←[1;34mmnt←[0m
←[1;34mdata_tmo←[0m ←[1;34mproc←[0m
←[1;34mdbdata←[0m ←[1;32mrecovery.rc←[0m
←[1;32mdefault.prop←[0m ←[1;34mres←[0m
←[1;34mdev←[0m ←[1;34msbin←[0m
←[1;34mefs←[0m ←[1;34msd-ext←[0m
←[1;36metc←[0m ←[1;34msdcard←[0m
←[1;32mfota.rc←[0m ←[1;34msqlite_stmt_journals←[0m
←[1;36minit←[0m ←[1;34msys←[0m
←[1;32minit.rc←[0m ←[1;34msystem←[0m
←[1;32minit.smdkc110.rc←[0m ←[1;32msystem.prop←[0m
←[1;32minit.smdkc110.sh←[0m ←[1;34mtmp←[0m
←[0;0minitrd.arm.initramfs_list←[0m ←[1;34muserdata←[0m

I reverted to version 5 because this annoyed me. Still lovin it though.
[Vibrant Android Development] Jayrod1980:
Does Version 5 have the wake lag? Is the lag on all EXT, or just EXT4?
[Vibrant Android Development] anomalous3:
all versions seem to have the wake lag, on all types of ext,though I'm playing with the setcpu sampling rate to see if lowering that might not help with the lag.