yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] numba1cuban:
Imma try with the stock rom. Hope it fixes things and i will report back.
[Vibrant Android Development] MINUS Stl:
Flashed this last night. Came from rooted stock. Occassionally, I'll have the wake-up lag, but sometimes I don't.
[Vibrant Android Development] zimphishmonger:
Thanks a lot, JAC! Rev2 now works fine when using Clockwork to backup, and the volume keys work perfectly (far less important than the backup issue, imo, but glad they are both fixed) :D

Next step, figuring out why my benchmarks are only at ~1100 as opposed to the ~1400 or better everyone else is getting after using this kernel. :confused:
[Vibrant Android Development] neasoon:
Have one issue after flashing the new kernel.

adb install doesn't work. always get an error message

/sbin/sh: pm: not found
[Vibrant Android Development] zimphishmonger:
NM, there is still a bug w/ Clockwork Recovery. It does not work when you attempt to backup/restore or flash from the app, but it DOES work when you control it completely from within the recovery
[Vibrant Android Development] neasoon:
update for the adb install issue.

flashed the v2 kernel, adb install issue gone

however, the a2sd script no longer works.

it can mount my ext4 partition to /sd-ext but the data and dalvik-cache dirs are not created.

so the quadrant score is only around 900 under this kernel.
[Vibrant Android Development] justanothercrowd:
I just deleted my sd-ext folder and everything was moved back after a reboot (data/dalvik-cache)
[Vibrant Android Development] neasoon:
i tried that, no luck

when i try to manually execute the script by

/system/bin/sh 07a2sd

i see the error is at the first if then clause at line 14

if [ "$? = 0 ];

the error message is:

[: not found

it's so weird that i found /system/bin/sh behaves differently for the v1 and v2 kernels.

for v1, adb install doesn't work because in normal mode the shell sh fails to execute "pm"

for v2, adb install is fine, but the 07a2sd fails...

i'm pretty sure the shell is different since after v1, the prompt for normal user is sth like

~#

while after v2, it's

#
[Vibrant Android Development] Gr8gorilla:
Odin is a finicky *****!

Had issues with install, reverted to stock, odin hangs about 4/5 times when flashing something.

Got the install, and hung on buysbox. Took 30 mins to get flashed back to stock to try yet again.

Odin is a long way from fastboot, I can say that for sure...........
[Vibrant Android Development] justanothercrowd:
I hate ODIN.
[Vibrant Android Development] neasoon:
en...

it's hard to make odin work.

i tried to use odin in win 7 last night. always stuck and made my vibrant into that phone/computer screen.

finally i gave up and swithed to ubuntu, installed a win xp virtual machine in vmplayer. now i can flash my vibrant smoothly...
[Vibrant Android Development] justanothercrowd:
Thanks for the feedback working on a fix :)
[Vibrant Android Development] The_Chrome_Coyote:
I actually dont have any trouble with ODIN, as Ive had to flash the JFD stock maybe a dozen or so times yesterday.

Its that up until I install the new kernel my device works in ADB, and I can pull logs, but the second I reset after installing the kernel I get "waiting for device" in ADB and it hangs at the Vibrant screen.
[Vibrant Android Development] neasoon:
perhaps another issue

after flashing v2, i installed Rom Manager with ClockwordMod 2.5.0.4 for vibrant

if i click reboot into recovery in Rom Manager. the first reboot succeeds into Rom Manager's recovery while the strange thing is looks like there is a 5-second timer. So after 3 seconds, the phone reboots again to the stock recovery automatically...
[Vibrant Android Development] Gr8gorilla:
Interesting thing I noticed is that if you are on stock and have yet to flash the root update with busy box, via stock recovery, you wont have busybox and it hangs at the s screen. When I tried to flash the root after flashing to stock the first few times, I did this:

Flash stock through odin.

boot into clockwork - flash root.zip -

boot into download - flash kernel -

hang -

adb logcat = nobusybox

repeat and check for superuser/busybox before flashing kernel to find its not there, repeat flash with clockwork, still no root - (that is without rom manager just using the fake flash method)

anyway using stock recovery puts busybox and super user on, gonna flash kernel again and see what I get this time!
[Vibrant Android Development] zimphishmonger:
Have the EXACT same issue, I managed to get it to not reboot after the second time (reboot to recovery, reboots to standard, flash update.zip for clockwork, now you should be in Clockwork) by disconnected the USB cable. Not sure why that would cause it to reboot though.
[Vibrant Android Development] numba1cuban:
This is not working for the 3 sec lag im having even with the new completely stock rom. I flashed a total of like 5 times rooted and everything from scratch but no lag fix. The V2 is not working for me neither its like flashing the stock kernel back on the phone. Went back to the first kernel and get a quadrant score of 1552 so im keeping that till these bugs get fixed. ONLY down sides im experiencing is the 3 sec wake up lag and reversed volume keys.

Seems im having this same issue:
[Vibrant Android Development] justanothercrowd:
/kernel-vibext4-5.tar.md5

Try this kernel. I created some symlinks to the missing commmands. The only shell in v2 is the stock shell. The sh in v1 was linked with busybox.

Tested adb install and adb logcat and watched the script create the folder and move data and dalvik.
[Vibrant Android Development] zimphishmonger:
Although the link says its v3, the download is v2

Corrected Link : http://www.justanotherdev.slackdev.com/kernel-vibext4-3.tar.md5

Thanks, as always!
[Vibrant Android Development] justanothercrowd:
Only v1 should have the reversed volume keys.
[Vibrant Android Development] justanothercrowd:
EDIT:working now

I'm also thinking of implement Clockwork as the stock recovery like v1 but i need to take care of the MD5 issues with Nandroid in that setup.
[Vibrant Android Development] justanothercrowd:
I don;t want to include busybox in the ramdisk as I want people to be able to update it through the busybox app in the market if needed. I will put a note in the OP that you need to have busybox installed prior.
[Vibrant Android Development] zimphishmonger:
Thanks, got the new v3 kernel, will give it a shot. Thanks for working on the clockwork issue! Im sure EVERYONE here appreciates it :D Thanks!
[Vibrant Android Development] neasoon:
updated to v3. a2sd script still doesn't work. same issue as v2. i flashed it twice to make sure about that
[Vibrant Android Development] justanothercrowd:
Can you reflash the initd update or check the perms on the file? I'm not able to duplicate this issue ATM. And I havent got a report from anyone else with the same issue.
[Vibrant Android Development] Gr8gorilla:
I too am having the issue. Quadrant score of 861. So data is not on SD for sure. I will reflash the script and check the permissions.
[Vibrant Android Development] neasoon:
the same after reflash the initd update

the perms on 07a2sd should be fine, it's

-rwxr-xr-x root system 1591 2008-08-01 08:00 07a2sd

i see that my /system/bin/sh is still the stock shell, so i get the same error message.

i fixed it by changing the shell interpreter in 07a2sd to "/system/xbin/busybox sh", it works now.
[Vibrant Android Development] Gr8gorilla:
I have the same permissions, will use the same fix as neasson
[Vibrant Android Development] justanothercrowd:
shoot it looks like i upload the wrong kernel. I will have one up shortly sorry bout that.
[Vibrant Android Development] zimphishmonger:
Heh, was about to say something is wrong, as my quadrant is ~900 now as well. Glad you were able to figure it out ;)
[Vibrant Android Development] mytmouse:
Can someone post a link to a EXT4 partition tutorial? I've been able to flash the latest kernel, but could use some steps on how to go about formatting my SD card properly.
[Vibrant Android Development] neasoon:
i have a sd card reader and i use ubuntu linux.

so i pull out the micro sd card, plug it into my linux box, use fdisk to partition it.

first of all, remove the remaing partition

then make two primary partitions. the first one is fat16 and the second is linux ext

finally, use mkfs.vfat to fomat the first while use mkfs.ext4 to format the second partition

that's all
[Vibrant Android Development] krichek:
Personal preference I guess, But I prefer and would reccomend using fat32 over fat16.
[Vibrant Android Development] ArbitrageMan:
You need a linux box and some sort of card reader. I used Ubuntu.

1. Put the SD card in to your computer

2. In the terminal, type "sudo gparted". You might need to enter your admin password at this point, if it asks you.

3. Gparted will start, and from the dropdown box at the top right of the screen select your flash drive.

4. Go the device menu and select Create Partition Table. Click apply or accept to whatever warnings come up, but make sure you have selected your flash drive, and not your hard drive.

5. Take the flash drive out.

6. Put the flash drive back in.

7. In Gparted, from the Gparted menu select Refresh Devices.

8. Right click on the unallocated partition and select New

9. Set up the partition size you want for the fat32 partition. This will be the first partition on the drive, so you want it to be fat32. Obviously don't use the entire disk, as whatever space is left will be used for the ext4 partition. I created a partition big enough to leave about 1024 MB left for the 2nd partition.

Create as: Primary Partition

File system: fat32

10. Then click Add.

11. Right click on the unallocated partition and select New.

12. This time I selected all the remaining space, and chose file system of ext4. Primary partition remains the same.

13. click Add

14. From the edit menu, select Apply All Operations, and then click Apply in the warning box.

That's it. If you get an errors, make sure you removed your flash drive and put it back in before trying to apply the partition table changes.
[Vibrant Android Development] bildo:
#4

Kernal #4 is back up to 1772 in quadrant
[Vibrant Android Development] neasoon:
I see performance degradation if the data and dalvik-cache is moved to the external ext4 partition.

Although the quadrant score goes up from ~900 to ~1700. The actual user experience on data intensive apps are worse than keeping them in the /data directory on the rfs partition of the internal sd card.

You can try the xda forum app.

1. run adb shell vmstat to monitor the system usage

2. choose a very long thread in xda forum app, tap menu -> refresh

The result is, you will see "wa" (Time spend waiting for IO) keeps as high as > 90 for several seconds.

in the internal sd case, it much much better.

Am I wrong or is there anything I miss for this performance fix?
[Vibrant Android Development] zimphishmonger:
Man, 1700..thats a great score. Even w/ Kernel 4, I can only get around ~1100, no idea why.

Also, there are issues backing up w/ Clockwork on Kernel4, and I need to be able to nandroid:-(. Guess Im waiting for v5

Error:

E: Can't Mount /dev/block/stl11

(no such file or directory)

E: Cant Mount CACHE: Recovery/Command

E: Can't Mount /dev/block/stl11 (no such file or directory)

repeats twice more

If you try to do anything in recovery, it gives a mount error. Got one for /data when I tried to manually nandroid from the recovery itself
[Vibrant Android Development] justanothercrowd:
Okay just reflashed JFD re-rooted, installed init.d.zip and then the latest kernel juuuuust to make sure lol

Tested

adb install

adb logcat

adb root

adb shell

verified files residing in

/sd-ext/data/

/sd-ext/dalvik-cache

Quadrant score 1593

Verified that you can reboot into Clockwork recovery from ROM Manager. No more reboot and then ending up at stock recovery.

Verified NANdroid backup and restore from recovery.

EDIT:Clockwork fixed

www.justanotherdev.slackdev.com/kernel-vibext4-5.tar.md5

MD5:21cead190436504c52e7f50c06c1b810

Wake lag is next on the list.
[Vibrant Android Development] bildo:
Do you have ext3 or 4? I was getting 1100 with 3
[Vibrant Android Development] zimphishmonger:
I was using EXT3. but converted yesterday to EXT4 to test. No increase in scores. I have a lot of apps, but Ive disabled most of them from starting at bootup (AutoRun Killer), using AutoKiller (also disabled it to test), disabled LW, and nothing gained :(
[Vibrant Android Development] zimphishmonger:
I Know, why is it causing so many issues. Its totally trashed on kernel 4....well, not trashed, but it cant mount anything. Appreciate the quick fixes :-)
[Vibrant Android Development] ivanmmj:
Are you using the stock initramfs with some mods? Or are you using a modified version of the i9000?

I'm wondering where all the bugs are coming from.

The delay turning on the display, especially.

As far as the speed of the phone when using Apps2sd, I agree. Benchmarks are definitively higher, but the phone is slower. Maybe we should only move /data/data to the SD and not the rest of the data or dalvik.
[Vibrant Android Development] justanothercrowd:
initramfs is pretty much all stock besides some symlinks. Alot of the files between the two are identical anyways (hash)

I'm pretty sure the wake bug is in the kernel source. Lets just say samsung did a crap job in their README.txt/build_kernel.sh... Alot of config issues with the defconfig as well.

I thought the key mapping where in initramfs (and there is a file containing some mappings) but the ultimate issue lied in the kernel.
[Vibrant Android Development] justanothercrowd:
I've got about 50 zImages amongst my cluttered Desktop some for various platforms. I really need to organize my stuff to avoid stupid things like this.

I also tend to only have time to work on stuff at night after a long day which doesnt help either ;)

Clockwork is back to normal. Everything mentioned besides the wake delay should be resolved at this point. Please let me know.
[Vibrant Android Development] neasoon:
stock firmware + root hack + init.d hack + rev3 kernel here.

it's a joke that quadrant score is almost doubled while data intensive app's speed is much much slower before the hack.

do you have a reasonable explanation? i'm curious.
[Vibrant Android Development] Gr8gorilla:
I agree that is really retarded. I think we certainly need to try something new.

I like the idea of only data/data and leaving the rest on internal. We have to try something, because while I love a good benchmark score as much as any geek, I really don't want it at the expense of the usefulness of my 500$ phone!
[Vibrant Android Development] Gr8gorilla:
I think we need to have a stock kernel posted up too. Because having to wipe to revert is a real pain in the ASS. A link to one would be nice in any case!
[Vibrant Android Development] justanothercrowd:
Here ya go.

www.justanotherdev.slackdev.com/kernel-vibrant-stock.tar.md5.tar

MD5:9f89f8c5a6c785ff967806a4ca70906f
[Vibrant Android Development] justanothercrowd:
Also the main difference in size between my kernel and the stock is just zeroed out space to fill the partition (on the larger stock kernel).
[Vibrant Android Development] zimphishmonger:
No worries, man. We appreciate all the work you are putting into this kernel. Just flashed v5, and report back w/ my results.

Thanks again! :cool:
[Vibrant Android Development] justanothercrowd:
Sounds good. Please let me know. :)

Enjoy!
[Vibrant Android Development] danielmid84:
So when do we get the OC+UV? lol

Just flashed V5, jumped from V1. Great to have the volume keys fixed.

512mb EXT4 partition, quad score right after flashing V5 is 1548
[Vibrant Android Development] justanothercrowd:
Once the wake delay issue is resolved. I've already played around with different schedulers/governers and for the most part not too much of a perf difference so far.
[Vibrant Android Development] zimphishmonger:
Ok, small issue w/ Clockwork again. For whatever reason, when I am connected via USB, and activate a backup from within Rom Manager, it reboots into clockwork, starts backing up for a few seconds (~3-5 seconds), and then flashes back to the Clockwork recovery main screen. I know the backup hasnt been completed, because it just stopped and the files are way too small (also, it happened way to quick).

I am going to try and do a backup while NOT connected to USB and see what happens.

Best benchmark was 1127 on Quadrant, next step after a successful nandroid is a wipe, clean install, kernel, and then test to see if this score can be improved.
[Vibrant Android Development] ttabbal:
I haven't noticed anything like what you are talking about. I've tested with Newsrob, which hits the DB quite hard, and Tapatalk, which is the full version of the XDA app posted about earlier. I'll keep fooling around, but here's a version with just /data/data on SD, it leaves the dalvik-cache. That's how the first script I wrote for this worked, dalvik was requested. I didn't see a big difference either way, but feel free to try. Note that if you already have the dalvik on SD you should put it back first. The disable-dc2sd.zip in the userinit thread should handle that for you.

I haven't tested this version on my phone, but it's a very simple change from the last version I did test on my phone. All I did was take dalvik out of the list of directories to copy.
[Vibrant Android Development] justanothercrowd:
Manual backups should work (rebooting into clockwork and NANDroid from there) as I tested them that way.

I've never actually used the backup ROM option in Clockwork (in fact I know not all the options in clockwork are working proper with the Vibrant but I dont maintain Clockwork/ROM Manager) I am looking into replacing the stock recovery with clockwork like in V1 but i really want to get the wake delay resolved first.

As long as the Manual backup works I'm not too worried about doing it through ROM Manager.
[Vibrant Android Development] zimphishmonger:
Okay, manual backups work fine (Phew!). You just cant manage or restore using the app. @Koush has been great to patch\fix any issues in Clockwork so Im sure he can help if its an issue within Clockwork. Ive been using clockwork since it was released for the Vibrant, and I can confidently say that every feature\option in Clockwork is working on the Vibrant.

Funny enough, with all my apps, I have very little issues with a wake delay, but Im sure that is more important that fixing this issue w/ Clockwork Recovery.

It would be great if you could integrate clockwork like in V1, that was awesome :-)
[Vibrant Android Development] justanothercrowd:
It will most likely end up going that route :) Don't worry ill get it fixed one way or another.
[Vibrant Android Development] zimphishmonger:
I'm not worried, you're doing an excellent job w/ this kernel (4 releases in a day, pretty dedicated). Glad we have a competent developer working on this phone :D

Ill say it again, cause it should be said, Thanks for everything!
[Vibrant Android Development] krichek:
For what it's worth I never could get the "backup rom" option to work on my original Droid either. So the manual backup is how I've always done it and it is working ok for me.
[Vibrant Android Development] zimphishmonger:
SUCCESS!!!!! Converting EXT4 gives a major boost to the Quadrant score - 1531. WAY better than the~1100 i was getting before. Stupid G1 didnt actually convert ext3 to ext4, even though it said it did. Thanks!
[Vibrant Android Development] robavila721:
So how did you convert it. I use my old g1
[Vibrant Android Development] MINUS Stl:
O.o Might have to check mine now. Used my G1 last night to partition my card and convert ext.

Granted I got a score of 1497 though.
[Vibrant Android Development] zimphishmonger:
You are probably fine. Check with "mount" in terminal while booted. It should say mounted as ext4, not ext3. What a PITA lol, G1 said completed successfully, and the file system checker didnt complain either

Anyone else who is stuck at ~1100, convert your EXT to EXT4 :D
[Vibrant Android Development] zimphishmonger:
http://xdaforums.com/showthread.php?t=746327
[Vibrant Android Development] MINUS Stl:
Yep. ext4. :D
[Vibrant Android Development] mytmouse:
thanks ArbitageMan!

v5 is clocking in at 1611 on Quadrant! What a different justanotherdev!
[Vibrant Android Development] zimphishmonger:
Damn! Its failing on the MD5 Checksum creation again during a manual backup, using kernel 5. tried 3 times. Is there any type of log I can look at\send you to see why its failing?

Thanks, JAC!

EDIT: Backing back down to v2 for the time being. That was the last version that I could do a nandroid backup successfully, w/o mount errors or md5 issues.
[Vibrant Android Development] Mark271:
Where should I start if I am interested in this and REALLY new to android/smart phones?

I am really interested in tweaking this phone, but dont want to **** up this phone either, ya know.
[Vibrant Android Development] ArbitrageMan:
v5 is on board.

- The phone seems faster, if thats possible, but my Quadrant dropped to 1400 something.

- Rom Manager > reboot to clockwork > nandroid backup = works

- volume buttons, fixed
[Vibrant Android Development] zimphishmonger:
READ.....a lot! You will slowly pick it up. When I started "tinkering" w/ my G1 almost 2 years ago, I knew very little about android and linux. Just by messing around CAREFULLY, reading, and asking intelligent questions (like how to undo something before you actually do it, in case things dont go so well). You will pick up a lot just by browsing on XDA. Start in the general forum for the phone, read the stickies, especially the Tips and Tricks thread.

Hope that helps!
[Vibrant Android Development] zimphishmonger:
Okay, Ive been flashing, and restoring all day. Here is what I've found...

Using V5 of the kernel (data and dalvik-cache over to /sd-ext):

Volume buttons are fixed

Have sporadic issues using Clockwork Recovery (Using Reboot to Recovery in

ROM Manager) - 1 out of 5 times it successfully completed a nandroid backup. Every other time there is a mount error for everything but /system, or the md5 fails.

Using EXT4 is significantly faster that EXT2/3, adds about 300 points to your Quadrant score

Significant improvement in lag, stalling from stock kernel

Ive run the backup 10+ times trying to isolate this issue, but I cant. I know its not the SD card, because ive had no issues backing up w/ V2 or stock kernels.

Mount error Example: E: Can't mount /dev/block/mmcnlk0p2 (no such file or directory) Can't Mount /data/!

I
[Vibrant Android Development] robavila721:
Is the wake up lag fixed in v5?
[Vibrant Android Development] ivanmmj:
V1 with data moved to sd but NOT dalvik cache.

The phone is VERY quick. NO lag.

Quadrant score: 1712 (class 6 SD)

Going to load V5 now to fix the volume controls.
[Vibrant Android Development] numba1cuban:
No the issue is still there.
[Vibrant Android Development] zimphishmonger:
Did you by any chance try moving both data + Dalvik? Im interested in the speed differences if you only copy data compared to both.
[Vibrant Android Development] ivanmmj:
I moved dalvik BACK to the internal storage because the phone was very laggy when running dalvik from the SD card. (Now that I have the dalvik on the phone, it's buttery smooth.)

Now I'm on v5 and my Quadrant is at 1749 (class 6 sd card.)
[Vibrant Android Development] davbran:
Due to user error, I had to reflash to clean install. So I went to stock, then rooted, installed lastest busy box, flashed init.d and Odin'd v5. On reboot I am sitting on Vibrant ... have been for over 5 minutes. Can anyone think of anything I might have missed?
[Vibrant Android Development] ttabbal:
Wipe the ext partition? The old data and dalvik might be causing a problem. I'll look into having the script detect this type of thing.
[Vibrant Android Development] davbran:
there's a problem with the just data update. The update script is pointing to a script in init.d that isn't there.
[Vibrant Android Development] ttabbal:
Do you have the log for me? It's in /tmp/recovery.log

Which script? All I did was change one line and re zip and sign it. The cleanup stuff might complain about trying to delete files that don't exist, that's ok.