yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] angryPirate12:
OC kernel base is v7

i'm currently running benchmarks with the OC kernel using both deadline/conservative and deadline/ondemand, to see the difference, i'm also taking it a step further and doing the other 3 types (noop, anticipatory, and stock cfq) configured with both conservative and ondemand
[Vibrant Android Development] numba1cuban:
Hey what did u have to do to run the virtual ext4 I would like to run that partition instead of the original ext2 virtual partition. Is there instructions on how to do this please help me pretty please with a cherry on top =) Thanks.
[Vibrant Android Development] tweezit:
so far oc version is working great for me so thanks :)

edit: cant wait to try your other oc versions to see how far this phone can go :D
[Vibrant Android Development] angryPirate12:
Using JAC's OC1 kernel, RyanZA ext2, and eugene373's Vibrant4 ROM - was ran 2 times each

With deadline/conservative

With deadline/ondemand

With noop/conservative

With noop/ondemand

With anticipatory/conservative

With anticipatory/ondemand

With cfq/conservative

With cfq/ondemand

an easier to read chart:

D/C: 2456 2478

D/O: 2469 2520

N/C: 2420 2511

N/O: 2508 2556

A/C: 2408 2544

A/O: 2476 2505

Q/C: 2467 2519

Q/O: 2482 2518

clearly neither setup is far superior to another in benchmark tests, the Noop/OnDemand setup as yielded higher results more consistently for me. I guess the only real question is, which setup is best for daily use? to figure that it, just have to set something and use it.
[Vibrant Android Development] zimphishmonger:
I manually converted it to EXT2 in recovery, and replaced a script in init.d to mount it as EXT4 instead of EXT2. I wrestled w/ the scripts A LOT to get it to work, so I dont quite have a fool proof method from going from Virtual EXT2 to Virtual EXT4 yet. Will let you know when I do.
[Vibrant Android Development] zimphishmonger:
Hey JAC, I noticed something peculiar. Running v6 kernel, No issue w/ wake lag, it responded almost instantly. Then updated to v7\v8\oc1 (tried all three) and 2-4 wake lag is back. I didnt change anything else, so I can only assume something about the kernel caused the change. Any idea?

I know you and some of the other SGS devs are working on a wake lag fix, and I figured this may help narrow it down. Something about v6 worked perfectly in that respect. Now using OC1 (as its not crashing now, for whatever reason), and wake lag is about 2-3 seconds. Cant wait till you guys knock that bug out :D

AngrtyPirate, how did you change the battery color and the error notification from red to blue?
[Vibrant Android Development] kopykatkiller:
Yay!
[Vibrant Android Development] The_Chrome_Coyote:
Didnt have to, I never applied the RyanZA mod in the first place. I was just asking you how to do it.

I got the 2100 just on Stock JFD with JAC's OC Kernel w/ EXT 4 on only a class 4 card.

So far, running super stable. Color me impressed
[Vibrant Android Development] zimphishmonger:
When you say EXT4, do you mean the ext partition on your external SD or the virtual partition we are mounting as /dev/loop0? You mentioned you never used the loopback mod. So you are still using the regular "EXT Hack" from JAC's kernel?

Im getting about ~1900 using Virtual EXT4 loopback set-up.
[Vibrant Android Development] angryPirate12:
using metamorph, framework-res.apk files, although they're not supposed to be yellow and blue, for whatever reason screenshot has F'd them up.

notification is supposed to be yellow

battery is supposed to be green

juice defender should be yellow as well

oh well long as it looks good on my screen
[Vibrant Android Development] zimphishmonger:
Oh Ok, you just metamorphed it. Did you modify the images yourself, or pull them from another build? Id like to use them, if its okay. Im tired of this blue battery
[Vibrant Android Development] MINUS Stl:
Edit: NVM

I need to read posts more thoroughly and not text while reading them too. :rolleyes:
[Vibrant Android Development] angryPirate12:
yea i'm lazy, unless someone makes something i absolutely love, i always pull someone else's work, then mod the files to my liking. This for example i just took the stock template, pulled the files i wanted, did color overlays in photoshop, then merged them with Clear Bar. It requires knowing basic XML.

unfortunately for you, i do pull other people's work, i don't redistribute unless i know who i got it from and where so i can properly link and credit, and half the time i don't remember any of it, but i am happy to help

Official Vibrant Morph Thread should have all the info you need
[Vibrant Android Development] kaizasoshi:
Hey Jac..any way of getting a boot.img for this?
[Vibrant Android Development] zimphishmonger:
There isnt a method for doing that yet
[Vibrant Android Development] kaizasoshi:
Thanks for the heads up Zimp..i haven't been keeping up with what's been going on with the development for vibrant..just miss the ease of flashing coming from the G1
[Vibrant Android Development] Novek:
Just to inform, my vibrant freezed with the OC-kernel... It worked for some hours, then freezed while it was "sleeping", and it resulted in my phone was like "off" for people trying to call me. It didn't give more than ~300+ in quadrant anyways (getting 2260 with RyanZA and 2575 with the OC-kernel).

Not that I don't appreciate your work, but I'll use the stock kernel until next version :P
[Vibrant Android Development] The_Chrome_Coyote:
Yeah. Just using the regular ext4 hack on my external SD and JAC OC kernel.

Been running all day without incident. Though wake lag is still present. Coming from an iPhone I'm used to it so I don't mind as much as others seem to though.
[Vibrant Android Development] justanothercrowd:
Anyone having issues with the OC kernel can you post you CPU revision you can find it in setCPU under info.
[Vibrant Android Development] frank707:
I have some freezes with the overclock, and with the on demand v7 kernel there were little lags. But the v8 runs smooth for me. I'm also using the ext 4 loopback, phones runs great. Looking forward to a resolution for this wake lag.
[Vibrant Android Development] micric100:
Sorry for being a big noob in advance, but I will learn more about this and figure this out after I get an answer to this one question.

When 2.2 is released officially, will all the kernals, scripts, etc. created to fix the speed problems need to be updated to be used with 2.2? or is it possible that samsung will pack 2.2 with it’s own fix to have fast NAND flash memory like other android phones?
[Vibrant Android Development] angryPirate12:
i get screen lock every now and then, mainly when the CPU is being tasked heavily, like running quadrant back-to-back. Sometimes it'll do a soft reset and come back, other times i have to long press the power button, and its only happened once so far but last night doing the benchmarks i had to remove the battery to reboot my device

CPU Rev. 2
[Vibrant Android Development] angryPirate12:
the brave few US Galaxy S owners and the many European owners are using 2.2, and the lag fixes are reported as working in 2.2, as of now! may change later
[Vibrant Android Development] MINUS Stl:
Had this issue again with v7 and v8. Haven't tried the new oc kernel yet.
[Vibrant Android Development] zimphishmonger:
I have cpu rev 2 and have issues with the oc1 kernel. Freezes and phone turns off randomly. Reverted to v7, issue disappeared. Guess mine cant handle 1.2ghz at stock voltages, may need a lil extra juice.....

Thanks for your help!
[Vibrant Android Development] MINUS Stl:
Just flashed the new oc jebel and this hasn't froze up on me yet. Downside is it also loses all my settings. :(
[Vibrant Android Development] micric100:
thank you, but in your opinion is it possible that when the final official 2.2 is released to the US that samsung will have fixed the problem themselves doing something similar? or is this not likely?
[Vibrant Android Development] PowSniffer0110:
Hahah.. Who knows bro. Atleast we'll have jit and flash
[Vibrant Android Development] The_Chrome_Coyote:
After a full day without issues, OC kernel was hanging constantly today.

CPU revision 2
[Vibrant Android Development] aenima4six2:
Also CPU revision 2...

I only had a hang when trying to run Wireless Teather..

It appears this kernel has some incompatibility with the latest build.
[Vibrant Android Development] j_r0dd:
i am n00b to samsung phones, but won't Koush's AnyKernel Updater work here since it is just a zImage??
[Vibrant Android Development] ttabbal:
JAC:

Any shot you can help me figure out why my script doesn't run in v8? It works in v6 just fine, but updating the kernel breaks it. It works if I do "/system/xbin/busybox run-parts /system/etc/init.d/" in clockwork recovery adb shell, but durring boot, I get this over and over:

I//system/xbin/busybox( 2194): [: not found
I//system/xbin/busybox( 2194): [: not found
I//system/xbin/busybox( 2194): [: not found
I//system/xbin/busybox( 2194): [: not found
I//system/xbin/busybox( 2194): [: not found
I//system/xbin/busybox( 2194): [: not found

The error makes me think it's related to my script's if blocks, but I don't get why it runs in recovery but not during boot, and why v6 worked fine with it. Here's the script, let me know what you think.

It looks like conditionals aren't working at all, and complex structures aren't working either, removing this type of thing gets it to boot, but the ifs are still not working right.

MMC=/dev/block/mmcblk0
# wait for the device to settle
COUNT=6;
until [ -b "$MMC" ] || [ $COUNT -lt 1 ];
do
sleep 1;
COUNT=$((COUNT-1));
done;
[Vibrant Android Development] CharonIDRONES:
For those that say they do not experience wake up lag with this, could you detail your setup?
[Vibrant Android Development] aenima4six2:
Hey guys, not to change the subject but I was hoping someone might be able to clear up my confusion.

I understand that the initial "07a2sd" script moves all Dalvik and data to the SD-Card, but I'm confused as to how and when the kernel is actually running the apps from the SD card. When I navigate into /data/app/ I see all my apps. Is the kernel loading all of these into an alternate folder or mount point at boot?

Also.. have been running a many of the various loop back hacks and was analyzing dev/block/. Can anyone confirm their /dev/block/ looks like this?

/dev/block # ls
ls
bml0!c bml7 loop7 ram10 ram6 stl4 tfsr12
bml1 bml8 mmcblk0 ram11 ram7 stl5 tfsr2
bml10 bml9 mmcblk0p1 ram12 ram8 stl6 tfsr3
bml11 loop0 mmcblk0p2 ram13 ram9 stl7 tfsr4
bml12 loop1 mmcblk0p3 ram14 stl1 stl8 tfsr5
bml2 loop2 mmcblk1 ram15 stl10 stl9 tfsr6
bml3 loop3 mmcblk1p1 ram2 stl11 tfsr0!c tfsr7
bml4 loop4 mmcblk1p2 ram3 stl12 tfsr1 tfsr8
bml5 loop5 ram0 ram4 stl2 tfsr10 tfsr9
bml6 loop6 ram1 ram5 stl3 tfsr11
[Vibrant Android Development] byt3b0mb:
i believe that the script moves the app settings/data to the sd card, not the app itself.
[Vibrant Android Development] aenima4six2:
Yeah, i was reading through it. It def does not move or touch the "app" folder.. I then pondered.. "then what does ?"
[Vibrant Android Development] byt3b0mb:
to move your apps to the sd card you need to setup an a2sd script, im sure there are some in the thread somewhere.
[Vibrant Android Development] aenima4six2:
I was under the impression the Kernel internally did this.. hence the higher scores in quadrant..
[Vibrant Android Development] zimphishmonger:
You can't use the kernel without a script, at least initially. You installed it before the kernel, called vibinit.d.zip

Sent from my SGH-T959
[Vibrant Android Development] aenima4six2:
Right.. but that script only moves dalvik and data.. not the actual app contents in the "apps" folder. I was under the impression this was internally being handled by the kernel but after further digging into things its not.
[Vibrant Android Development] zimphishmonger:
No, the kernel has nothing to do w/ apps2sd (or apps2ext), and does nothing to apps, data or dalvik, those are all done thru scripts (except the apps). Also, there hasnt been any mods for the Vibrant that Ive seen that even touch the apps, just the data and dalvik-cache
[Vibrant Android Development] ttabbal:
There are different versions of the script. Some of them move apps, some don't. I had them moved on my phone, but I found that protected apps wouldn't install if I did that. They will run if already installed, but won't install fresh. I did try moving app-private as well, no joy. Moving them doesn't do much, just makes installs faster, so it's not a big loss.

All the moves are done the same way, bind mounts in a boot script. Some versions used sym links, but they aren't as efficient. The kernel gives us ext4 and boot scripts that will finish before the system boots.
[Vibrant Android Development] zimphishmonger:
Any luck getting your scripts to work properly using Kernel v7 or v8?
[Vibrant Android Development] nickerrides:
how is there not a fix for the wake up lag yet?!?
[Vibrant Android Development] ttabbal:
Nope. I suspect something in the ramdisk changed that is preventing my ifs and loops from working properly, it's like the test command in the shell isn't working. But only during boot. It works fine in recovery and normal shells.
[Vibrant Android Development] ttabbal:
If it's so easy to fix, where's your patch?
[Vibrant Android Development] javacody:
+1

People need to show some respect.
[Vibrant Android Development] robavila721:
+2 I'm tired of people DEMANDING things.
[Vibrant Android Development] morfic:
I didn't catch it, which wake up lag is talked about

You press power and nothing happens, you press/hold it and then after a few seconds it wakes up?

Only been running stock kernel so far, but seen that with setcpu and a low frequency "screen off" profile

Have seen it once more when trying ondemand governor from command line. Not seen it since then.

Just wondering what's causing this wake up issue if y'all don't use ondemand...
[Vibrant Android Development] couped:
Thanks for this. Using anom's rom with this kernel and the vibrant is running better. Thanks again!

Sent from a Samsung Vibrant.
[Vibrant Android Development] nickerrides:
Didn't realize I was demanding anything. All I'm saying is I expected a fix by now. Guess I was wrong :/
[Vibrant Android Development] javacody:
You might not have meant it, but it seemed like you were being demanding and complaining.

If it was an easy fix, I'm sure JAC would have a new kernel out by now.
[Vibrant Android Development] nickerrides:
If I knew how to patch it I probably wouldn't be asking for a patch now would I? And I know its not easy but instead of putting out different versions of the kernel why not fix the wake up lag?
[Vibrant Android Development] zimphishmonger:
Its a work in progress. Several devs are working hard to fixing the wake lag, so shut up and wait for it, or figure it out yourself. You may not see it, but your comments are both demanding and complaining. Its significantly easier to compile 3 kernels, two for different cpu goveners and one w/ OC, than it is to fix a significant bug within Samsung's source.

By "expecting" a fix, you are essentially demanding it. Every kernel but stock has been experiencing wake lag, so its a pretty major issue that cant be solved easily. Give them a break.
[Vibrant Android Development] javacody:
Dude. Ever heard of attitude of gratitude? Seriously. If you don't mean to come off as demanding, then maybe you should stop being demanding? LOL

I'm not sure if you are an adult, and if you are, what field you work in, but coming from a software development background myself, I can promise you that if the fix were not hard to track down, it would already be fixed. I cannot even imagine digging through all that code trying to figure out the problem. I don't think you can even begin to understand the potential scope and difficulty of such an issue.

That's why I'm cutting you slack, because I'm certain you have no idea what you are asking.

Do me a favor, download the kernel source, and look through it. Then let us know how you feel...
[Vibrant Android Development] siirial:
** clap ** clap **
[Vibrant Android Development] aloxotls:
Why has nobody ported gingerbread for the vibrant yet! WTF!! Hurry up!
[Vibrant Android Development] MINUS Stl:
** clap ** clap ** clap ** clap **

:D
[Vibrant Android Development] CharonIDRONES:
I completely agree, especially when there hasn't even been a single update yet for the phone. As my understanding is that they need the zimage from an ota update in order to properly flash the kernel at that. Just as with the g1, the development community took a minute to get off the ground, but ut will get there once we have the ground work done
[Vibrant Android Development] kopykatkiller:
JAC should have already ported the Blackberry OS over for our phones by now, I mean come on. Come to think of it, while your at it...Can you port over Windows 7? I'm tired of having to login to my computer.
[Vibrant Android Development] ttabbal:
I'd rather have osx. And a pony, can I have a pony? :)
[Vibrant Android Development] robavila721:
Why not get IOS while he's at it they already confuse my phone with an iphone
[Vibrant Android Development] nickerrides:
you guys are gonna make me cry :(
[Vibrant Android Development] ttabbal:
Ummm... What are we mad about again? :) So, ummm... Any new info on kernels out there?
[Vibrant Android Development] zimphishmonger:
Agreed. Ive been backflashing too much, time for something new :)
[Vibrant Android Development] j_r0dd:
i just wanted to chime in about the wake lag. it is minimal for me after i uninstalled setcpu. sometimes it would not even wake with the stock kernel with setcpu running

BTW: does anybody have any links or tutorials how to make the full zImage with the ramdisk?? This is my 1st samsung phone so I am a n00b again lol. I have compiled the kernel with ext4 support added but the zImage is only 2.6MB.
[Vibrant Android Development] gilsken:
Which kernel's version did you patch ? (2.6.29 or 2.6.32 ?)

Except adding the ext4 filesystem, did you change anything else ?

Thanks for your work.
[Vibrant Android Development] zimphishmonger:
Thanks a lot, just flashed it and will report back with results :)
[Vibrant Android Development] byt3b0mb:
JAC will this enable adb to run as root, or is that still in the boot image? if the latter, is there anyway to edit boot for this device to make so?
[Vibrant Android Development] davbran:
It's golden :)
[Vibrant Android Development] justanothercrowd:
You should be able to run "adb root" without any modification with this kernel.
[Vibrant Android Development] blackerwater:
Nice work.
[Vibrant Android Development] justanothercrowd:
.29 is the only source that has been released AFAIK. There are quite a few config changes and changes to the ramdisk etc. This is pretty darn close to stock though I wanted to get something that is stable for people first. I will continue to add performance modifications and will be doing quit a bit of testing between the different scheduler setups etc. Overclocking is also in the works.
[Vibrant Android Development] davbran:
jac,

have you tried your volume buttons since updating the kernel? they're reversed now.

Down turns up the volume and up turn's it down
[Vibrant Android Development] ttabbal:
NICE! Unfortunately, no windows on my Netbook, so no Odin. sad.

I'll mess with it at home when I get time and I'll be updating my stuff to work with this kernel. MUCH better than the playlogos hack, and we can update the script to do fsck and such to keep the filesystem nice and clean.

Thanks again JAC! And we've got Ben here!! WOOT! SuperF, ohhh... how I would love me some SuperF. :)
[Vibrant Android Development] zimphishmonger:
Okay, results.....

This eliminates almost all of the lag I was getting. Not sure if it's the ext hack or the kernel, but excellent work.

Issues

Making a backup using clockwork recovery fails to produce an md5 checksum every time.

Volume keys are switched.

Nothing major, but issues I noticed.

Thanks again for such a quick release! Can't wait to see what is in store for this kernel :-)

Sent from my Vibrant
[Vibrant Android Development] rhcp011235:
Great work.

Did you see anything about the FM tuner or wireless AP in the kernel source? Just curious. I havent been able to look at all. too busy
[Vibrant Android Development] justanothercrowd:
Yeah I forgot to mention. I fixed all other mapping besides those and they arent labeled anyways so I let em be. All the softkeys work as they should which was the main issue at first. Well one of them lol.

This is just the beginning. Have some ideas for the FMTuner as well.
[Vibrant Android Development] justanothercrowd:
I think I may know whats causing the MD5 issue. I'll look into it tonight.
[Vibrant Android Development] rhcp011235:
Great work. Check into the FM + wireless AP issue :)

Maybe we can figure out a non-odin way if this all works. it will be worth it :)
[Vibrant Android Development] zimphishmonger:
Thanks a lot, jac! This is flying so far. Glad you already know about the volume keys, can you remap them back to the original setup for the next release, I keep turning my volume down by mistake lol. Looking forward to the next release already.... Thanks!!

Sent from my Vibrant
[Vibrant Android Development] justanothercrowd:
Yup these are on the list for sure.
[Vibrant Android Development] bbuchacher:
Woot word!
[Vibrant Android Development] bbuchacher:
@ Jac - Did you end up merging the samsung kernel source into a google .29 source? or did you just use the instructions/method samsung provided?
[Vibrant Android Development] kelmerp:
using the included microsd (the one that had avatar on it) and an ext4 partition I get a score of 1741. thank you so much!
[Vibrant Android Development] sl8125:
Just curious if this fix will work on the Captivate. I assume it is same hardware, how much difference in software? right?

I know i am in the wrong forum, but i was just in need of a fix. I am sure we would share if there was a lag fix. i hope vice versa.
[Vibrant Android Development] zimphishmonger:
I also noticed that w setcpu a while ago, but I just tried to recreate the fix without success. Uninstalled setcpu and I still have 2 to 3 sec lag on wake lag (currently using OC1 kernel)

Sent from my SGH-T959
[Vibrant Android Development] jlaval:
no /system/etc/init.d folder

Tried to flash vibinit.zip on Vibrant4 ROM but dont get the /system/etc/init.d folder...used Rom Manager. Any idea?

Also tried stock recovery and says "installation aborted".

Also have Setcpu and Ryan's lag fix installed. Can that be the problem?

:confused:

Thanks
[Vibrant Android Development] zimphishmonger:
re-download the file. It may be corrupted. Also, undo the lagfix, you will need to use a different version after successfully flashing the kernel, one that uses /system/etc/init.d for scripts. It will most likely say "for those using a lagfix"
[Vibrant Android Development] jlaval:
Sorry zimphishmonger 4 waisting ur time. It turns out that the "Files" app in the Vibrant doesnt show the root directory... :o So flashed the OC kernel and all is good till now, even w/ lagfix preinstalled. Got 2474 quadrant :D
[Vibrant Android Development] gehlersjr:
Somebody please help I am coming over from the cdma hero forums and an completely new to the whole odin thing now being a pc tech with extensive knowledge of mac and windows plus a bit of linux from the early 2000's and recent use with ubuntu and ultimate so I am quite a bit knowledged yet not an expert. I get the use of odin but I can't get into download mode, all I get is the vibrant in white then back off, I have clockwork installed and have tried both up and down combinations to no avail, what's up do I need to flash back to regular samsung update mode before trying or what already patched init.d so that is done.