yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] anomalous3:
Incidentally, the screen also seems to rotate MUCH faster on the v9 and OC3 kernels than on the stock kernel :)
[Vibrant Android Development] neasoon:
Perhaps those who don't see the clock issue never have their phone entered mem sleep state.
[Vibrant Android Development] justanothercrowd:
Most of the OC code is the same as before so im hard pressed to see why its changing the time sync now.

I'm rebuilding a few toolchains with diff configs to see if that helps since it popped up around the same time as the new toolchain was used.
[Vibrant Android Development] _Opiate_:
Quick question guys....if I already have an internal SD ext4 lag fix variant on my Vibrant and I flash the included update.zip and kernel is it going to break the lag fix?
[Vibrant Android Development] zimphishmonger:
Yes they still probably conflict. You should probably remove the lag fix. I'm assuming your using one that uses one of the play logo hack versions

Sent from my SGH-T959
[Vibrant Android Development] _Opiate_:
Yes a Tayutama ext4 fix. Should I wipe and flash this first or what?
[Vibrant Android Development] MINUS Stl:
Update on my situation. Started all over again today and flashed the SCv9. Went through the whole process and started anomolous's manual method. Got to the "busybox cp....." parts and got the same "No such file or directory" errors. Then I noticed the errors were pertaining to every app I had on my phone before I flashed back to stock (which wipes the phone). :confused: No, I didn't get a logcat....again. :rolleyes:

Yesterday before starting over, I repartitioned my sd using my wife's MT3g with Amon_RA's recovery. Shouldn't that have formatted it as well? Just not sure how those apps were showing up. :confused::confused:
[Vibrant Android Development] neasoon:
curious about how you fix the wake lag issue. you did that by turning off the driver debug option in kernel config file?
[Vibrant Android Development] raspdeep:
my 2 cents on this issue:

- Uninstall setcpu, reboot and check for clock lag (use overclock widget if needed but our kernel work ok without setcpu or overclock widget)

- undo any tweaks on the OC kernel (can use my patch file in my OC thread) and rebuild

- use the toolchain config that I've also mentioned in my oc thread
[Vibrant Android Development] neasoon:
JAC, you can try to comment out line 1247 in arch/arm/plat-s5pc11x/pm.c, that is:

#ifdef CONFIG_CPU_FREQ

s5pc110_pm_target(BOOT_ARM_CLK);

#endif

I believe the bug lies in s5pc110_pm_target. this func tries to directly set the desired frequency when entering mem sleep state. however, it forgets to notify other parts of the kernel.

When entering mem sleep, and before calling s5pc11x_pm_enter->s5pc110_pm_target, the frequency is locked to table entry 0 and 1 in kernel/power/main.c, around line 553~557. 0 and 1 in Oced kernel are 1.2G and 1G while in non-oc kernle are 1G and 800M.

BOOT_ARM_CLK is set to 800M. So actually in non-oc kernel, the frequency usually is already set at 800M and s5pc110_pm_target just exits early and there is no actual frequency change. while in the OCed kernel, the lowest possible frequency is 1G, so there is a frequency transition.

Hope this is the root cause.
[Vibrant Android Development] justanothercrowd:
The Wake_Lag issue is fixed by building with a diff toolchain than CS.

Crosstool-ng works
[Vibrant Android Development] anomalous3:
I was able to create an update.zip using the new redbend_ua for the OC kernel for you folks running linux or mac. Will upload it shortly.
[Vibrant Android Development] justanothercrowd:
I am using the exact toolchain config as you are and have tried a few others as well. All of them fix the wake lag with crosstool-ng.

I have added a few more changes to the OC code and and yes running without setCPU does seem to keep the issue in check. Hmm
[Vibrant Android Development] justanothercrowd:
This is how all my new kernels will be released update.zip instead of ODIN :)
[Vibrant Android Development] anomalous3:
Cool, just figured I'd save you some work and help some folks out if you're cool with it. I'm still at the bottom of the learning curve when it comes to the compiling stuff (just now starting to play around with making my own kernels for my old MyTouch) so I try to make myself useful where I can.

Nolag v9:

http://www.getyourboneon.com/JAC-v9.zip

OC v3:

http://www.getyourboneon.com/JAC-OCv3.zip
[Vibrant Android Development] justanothercrowd:
Can you test this Kernel without setCPU installed and see if it keeps the drift in check.

It includes the following changes from unhelpfuls v1.2. I left interactive out because he said its still having some issues.

Fix scaling bug, performance level was set past end of table on sleep

Scaling enhancement, selectable clock source for GPU

GPU clocked at 222MHz for all speeds except 100MHz, where it matches CPU clock

http://www.justanotherdev.slackdev.com/Vibrant-OCv4.zip
[Vibrant Android Development] zimphishmonger:
Will test and get back to you about the time sync. Thanks a lot
[Vibrant Android Development] zimphishmonger:
Would you mind letting us know how you got them into update.zip form? I'd love to know how to do that for future reference

EDIT: NM, just took a look at the zip file and the update-script. Super easy! Great work all around guys
[Vibrant Android Development] justanothercrowd:
Its easy..just look at the update.zip. We found a new way to use a binary already included with the phone to flash bml partitions.

redbend_ua

so

redbend_ua restore /files/zimage /dev/block/bml7

would flash your kernel etc.
[Vibrant Android Development] zimphishmonger:
Awesome, just flashed OCv4. Will test it out and see if the clock has any issues. Will report back. Thanks again JAC

EDIT: For whatever reason, the calender FCs on boot-up each time after applying OCv4, even after fix permissions. Doesnt seem to be an issue in the app, as it loads okay, just a FC on boot-up.
[Vibrant Android Development] justanothercrowd:
Hmmm... this is jsut s dirty test kernel there may be some changes to the ramdisk that where experimental.

It should be fine enough to test the time drift though :)
[Vibrant Android Development] zimphishmonger:
Okay, I'll ignore all other things except the time sync issue. Upon benchmarking (using Quadrant. ya, I know its totally inaccurate) I found it to be slightly slower than SCv9, but now that you mention its just a quick and a dirty, I'll just focus on the sync issue.

Seems the time issue is still there, put it to sleep 3 times, woke it up, and i'm already 6 seconds off. While I was writing this edit, it slipped to ~30 seconds off. Make that +53.382 seconds off. Seems to still have the time drift issue, unfortunately.

Back to SCv9 till the next test kernel. Its so much easier now that we can flash from an update.zip :D
[Vibrant Android Development] aloxotls:
I just ran linpack with the OC v4 and I am only getting +/-6.1 MFLOPS.
[Vibrant Android Development] neasoon:
i see. i use the toolchain from codesourcery, arm-2010q1.

i took another way to fix the wake lag. i did some debugging and found that the wake lag issue is in console_resume(). console_resume() resumes the printk console during wake up from mem sleep state. The problem i see is perhaps by default the driver debug option is enabled, so there are a lot of printk messages output from various device drivers who sleep then wake up. unfortunately, console sleeps very early and wakes up very late. so when console_resume() is called, there is a lot of kernel messages to output. usually, this call takes around 2 seconds.

after turning off the driver debug option, the whole delay is reduced to 0.5 ~ 1 second, originally it's around 3 seconds.
[Vibrant Android Development] justanothercrowd:
Yeah dont worry this is just a test kernel and you have to use echo or setCPU to set it to OC its 1Ghz on boot I get 9.7 once OC'd...thats why its not in the OP

Found the issue with time drift. Seems the toolchain that fixed wake lag introduced the time drift. Its not the OC code or anything. Working on a solution now.
[Vibrant Android Development] aloxotls:
echo 1200000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq;

I put that in a script and placed it in the init.d folder and still got low MFLOPS. I did not try setcpu, but I have one of the weak Vibrants anyhow :( so it is probably best for me to stick with v9.

Thank you for all your hard work
[Vibrant Android Development] b0ricuaguerrero:
Jac can you please add usb tether support for wired tether for root users app
[Vibrant Android Development] justanothercrowd:
Okay I have another test. It appears to be fixed on my end.

www.justanotherdev.slackdev.com/Vibrant-OCdrifttest.zip

Same deal defaults to 1Ghz on boot and use setCPU or echo to OC. setCPU shouldnt cause any issues that ive seen on this Kernel but most users report less drift without it installed on prev kernels that where having time drift.

Linpack in the 9.7~ OC'd
[Vibrant Android Development] zimphishmonger:
Thanks, will test and report back in this post

EDIT: JAC, you are the man! Can't get the clock offset to get above .5 seconds (OCed using echo commands, No SetCPU installed) Great work! Still have a FC for Calender and Calender storage on boot, but I know this is still just a test to fix the time drift, which seems to be done. I will continue testing and see if it gets any worse, but its looking good :D BTW, dont know if you've noticed, but you have like 5 of the top 10 scores for the Vibrant in Linpack...bumped me off a while ago it seems :-p
[Vibrant Android Development] skater4690:
the new update.zips do you flash them from stock recovery or clockwork or does it matter?
[Vibrant Android Development] justanothercrowd:
Ill get a final version up tonight. No one else and I can't replicate the issue try and reflash your rom and let me know
[Vibrant Android Development] The_Chrome_Coyote:
Awesome. Fixed the time drift with the latest. Flying with almost 10 in linpack.

Loving the new updates via clockwork. As a tip, people should leave the clockwork update on their SD, so if you ever have to boot into stock recovery, you can use reinstall packages to launch clockwork and restore a backup or flash a new ROM / kernel
[Vibrant Android Development] morfic:
With all this kernel making love, why don't you build a kernel with bfs patched in, people would be surprised how much they love their phones then :)

Or if you share how you build them, i can see to get bfs on it myself, but without a link where i can double check i am not missing anything, i am not going to flash a kernel of my own doing.

It's the difference between making mt3g and liquid boot.img that make me cautious, even if i built/put together boot.img for either once i had the tools. (And on both i used fastboot and here it's a unfamiliar tool, although if it's all stuffed in a update.zip in the end, that point is moot)

Thanks,

Daniel
[Vibrant Android Development] anomalous3:
dawg, BFS is sooo 2009, BFQ I/O is what's hot.

But seriously, the way BFS runs seems to interrupt processes like the touchscreen for a lot of people. There will always be a few people who really prefer it of course, but for most people there are better options out there.
[Vibrant Android Development] justanothercrowd:
I have built kernels with bfs just not for the vibrant yet. Don't worry this is just the b.eginning many diff mods to come. And yes bfq is preferred. Bfs is never as stable either imo
[Vibrant Android Development] skater4690:
ok i flashed the kernel through clockwork i had some really weird blue words that were too exploded to read pop up and then it said it installed so i rebooted and now my phone is stuck on vibrant screen...

edit: ok found my problem busy box was deleted from system xbin...
[Vibrant Android Development] morfic:
It'd still be great if you shared the process, this way i can feel good about tinkering away and if it doesn't turn out as i wanted, noone's time was wasted, if i get to where i want to be, you can try and see if we both like the same ;)

Or you could confirm the kernel is/isn't monolithic and you do not need to build any modules that need to be moved over too. (Like not having wifi with a missing wlan.ko on mt3g :P) All i see is suggesting it is, but thinking != knowing.

Awesome, looks i skipped a few of the good pages in this thread, going to see if i can see what all is on those i skipped.

Starting to look simpler and simpler.

Still wanna know that:

What's the last bfs version you used on which kernel version for what phone, out of curiosity?
[Vibrant Android Development] skater4690:
yay got my phone to work again!!! i F'ing hate odin... it never wants to flash the stupid zimage... had to try like 10 times lol

edit: ok even though i F'ed my phone up i reinstalled busybox and went back to clockwork and flashed the oc kernel and its working yay!!!
[Vibrant Android Development] zimphishmonger:
JAC, got the calender FC issues fixed by wiping their cache for storage and the system app. Things are running great now. Thanks again for all your hard work. Will test out the final release you let it loose.

For those that prefer to not have SetCPU installed, for whatever reason (although JAC has stated that SetCPU is not causing the the time drift), feel free to use the attached 03overclock file (remove txt extension, push to /system/etc/init.d, chmod it to 755) and the overclock will be set on boot-up. Gotta love the init.d folder :)
[Vibrant Android Development] All~G1:
Im guessing that even though we can now flash the kernel, it is still recommended to flash it from the stock ROM. If so, could someone possibly make a flashable stock ROM and load it? The way I understand it redbend is running prior to the code that is already set at boot to flash the kernel. So anything that was done prior (ie; lagfix, ROM flashing) would need to be undone or reverted to avoid problems.

If anyone could clear this up for me that would be great!!! Thanks in advanced and thanks to the Development that is taking place here in this thread.
[Vibrant Android Development] morfic:
1.16.1 from the root update.zip is missing them, anyone else missing them can just run:

busybox --install -s /system/xbin

keep an eye on the fact binaries in /system/bin are first in path, so if you use a script and it complains about an option it does not know, you run the old binary, get rid of it.

on terminal, type: which cp

after you installed the symlinks and you see what i mean
[Vibrant Android Development] danielmid84:
I am running Eugene's Vibrant6 with the sc9 kernel flashed, I rebooted into clockwork and flashed Vibrant-OCdrifttest.zip, weird fonts and rebooted. Running great, put the echo OC on and went to town. Sorry JAC for taking top spot away from you on Linpack.
[Vibrant Android Development] Goog1e Phone:
I'm running a stock rom with SCv9 and ext4 with ttabbal's script. If I was to flash the new OC kernal, would you guys recommend just flashing it on top of what I have now? Or what should I do in order not to run into any problems?
[Vibrant Android Development] fit333:
OCv3 made my clock advance 10mins/hr
[Vibrant Android Development] dumbkkid:
Im super confused. Im a noob at this. I just flashed the new kernel through clock work and used set cpu to oc,. But a little after oc ing my phone freezes up. O.o any tips anyone can give me? Any help will be appreciated :/
[Vibrant Android Development] zimphishmonger:
Read the last several pages, its a known issue that is almost fixed

Not every CPU can handle 1.2ghz at that voltage. Each CPU is unique in how far it can be clocked.
[Vibrant Android Development] justanothercrowd:
Use the test kernel for now Time drift and wake lag are fixed and it is OC'd and stable.

I will have the final up by tomorrow working on some more changes to the CPU/GPU clocks. Also i know now what casued the time drift so i can avoid it in the future.

But yeah the test kernel is perfectly fine to use and has a slightly OC'd GPU :)
[Vibrant Android Development] justanothercrowd:
lol :) its OK
[Vibrant Android Development] jroid:
ok so I flashed the kernel, I just wanna confirm this is 2.6.29 correct? that's what I'm reading under about phone
[Vibrant Android Development] davbran:
Yep, that's what it is.
[Vibrant Android Development] The_Chrome_Coyote:
Can I flash this kernel on to Eugenes de bloated ROM.?
[Vibrant Android Development] skater4690:
Hey I'm kinda wondering would this kernel fix problems in eugenes froyo Rom? If so I think I might give it a try
[Vibrant Android Development] ArbitrageMan:
I was able to do this with no problem. And considering this is the first "real" thing I've done to the phone besides set up ClockworkMod, I was pretty nervous.

Immediately I could tell the system was faster. Quadrant went from 900 to 1754! And that was with a class 2 SD card! I used an ext4 partition, and I'm glad I was able to because I don't think I would have done ext2.

Sweet! Thank you.
[Vibrant Android Development] ArbitrageMan:
I want to say one other thing. Holding volume down and power does not work on my phone to reach download mode. After trying a bunch of combinations, I figured out that the only thing that works for me is to power off the phone, plug it into the computer, wait for the green battery symbol, then hold both volume buttons and power till the screen goes black, then release power.

Hope that helps someone.
[Vibrant Android Development] davbran:
Try powering down, unplug phone, hold volume down + volume up and plug phone in, wait and download will come up, simple.
[Vibrant Android Development] FastKatt:
I had problems with vol down and power as well. Finally used "adb reboot download" to get in.

JAC, so far everything works great. I'm now using ext4 and the phone flies! Thanks for improving an already awesome phone!
[Vibrant Android Development] masr1979:
Guys a little help here, I tried flashing it an odin keeps freezing

Doesn't go past there, I'm using anomalous3's deodexed rom, and right now the phone is stuck in that "phone ! PC" picture (we really need to come up with some short hand way of saying that). I can get into download mode, but will try to revert back to stock first.

*Nevermid guys, I took of the MD5 from the end of the file and it's working now.... freak accident, or was I supposed to do that?, if so JAC please update the OP, so that others know"
[Vibrant Android Development] numba1cuban:
Well I dont know if has been happening to any of you but i get lag when waking the phone from the locked and sreen off state. once it comes on like 3 seconds later it is really fast. Is there a way to fix this?
[Vibrant Android Development] davbran:
Just act as if your at the battery, that state is there mostly to stop it from booting broken, also switch usb ports to get a new com port.
[Vibrant Android Development] ArbitrageMan:
Lets call it the "g spot". Its elusive...
[Vibrant Android Development] Goog1e Phone:
How much should I partition my SD card to EXT4? I usually did 500-1000 MB on my G1 and myTouch, but that was with Apps2SD. Since this is D2SD, should I have my partition smaller? What do you guys recommend?
[Vibrant Android Development] The_Chrome_Coyote:
Im really not having any luck with ROMs lately...

Hangs on Vibrant Screen
[Vibrant Android Development] amerikian:
Will this work on a captivate? Any quadrant/speed increases?
[Vibrant Android Development] zimphishmonger:
There is a lot going on underneath that logo. "Hanging" tells us nothing useful that we can use to help you. Use adb logcat to see whats happening. Possibly stuck at a busybox prompt. I had the same issue earlier

Thats a question for JAC, although it MAY work fine. You can either be a brave soul and flash it, or wait for confirmation.
[Vibrant Android Development] MINUS Stl:
I just pulled a Quadrant score if 1497 (but I'm on a class 2 sd card). I believe my Quadrants before this kernel were around 800-900.
[Vibrant Android Development] ttabbal:
Just a little thing, e2fsprogs with ext4 support. The ones I posted earlier in the userinit thread didn't support ext4. Flash from recovery. :)

I'll be updating the a2sd script here soon. In the mean time, you guys with ext4 partitions can fsck and such on the phone now. :)

Binaries pulled from Amon-RA 1.7, compiled for ARM and work fine on the Vibrant. I just used them to upgrade ext3 to ext4 and fsck it.
[Vibrant Android Development] ttabbal:
There have been reports of issues with partitions larger than 2G on the stock kernel. No idea why, but it might have taken longer to mount the larger partition. This kernel does away with that problem at least. Mine is 1G and I'm using 180M. This version of the script moves dalvik-cache and data to the /sd-ext, still shouldn't need a ton of space though.

FWIW, my Quadrant score is faster with ext4 than ext3. :D 1698 now. Phone is performing great with this kernel + dc2sd. I'll likely be posting an update for the sd-ext script tomorrow with on boot checking and some other little goodies. Mostly to help stability, the core stuff is working fine.

Many thanks to JAC and all the other devs around here, we couldn't do it without you guys. Now that we have a custom kernel, a real AOSP froyo ROM shouldn't be too far behind. Not to mention overclock and undervolt possibilities. Good stuff. :D
[Vibrant Android Development] anomalous3:
Yeah, ext4 brought me back up to about 1900 after ext3 took me down to 1200. Lovin this.

So I take it the zimage contains both the kernel and the ramdisk? If so I'll need to spend some time with the kernel source and documentation to find out what's going on.
[Vibrant Android Development] speedysilwady:
eek just flashed the latest test kernel through clockwork recovery and i thought id be extra safe and wipe cache and dalvik cache, then reboot and now im stuck at the vibrant screen and the phone wont load up =/

Running Stock Rom

edit: oops i just read the first post again, i didnt flash the init.d update >_<; FAIL!

problem is i dont know how to load the clockwork recovery so i can put those init.d files on the internal sdcard

double edit: first time using ODIN, thank you search button! Everyone please read the main post multiple times and dont flash roms and kernels at 4 in the morning half asleep lmao
[Vibrant Android Development] brandnewsimmy:
If you still have the Clockwork update.zip on the root of your internal you can just reinstall packages from stock recovery and boot into Clockwork. I have had to do that a few times :D.

Also you may be able to 'adb push' stuff I have never tried but I know I was able to 'adb reboot recovery' from that Vibrant screen.
[Vibrant Android Development] speedysilwady:
no i was stupid and didnt have clockwork in my internal sdcard...epic fail x2! lol

i just took a shot with odin and came back! thanks though! :D
[Vibrant Android Development] morfic:
Ok, so no .zip i looked at has a ramdisk, so all we do is build 2.6.29 kernel with the stock ramdisk and hope for the best?
[Vibrant Android Development] rei165:
Two questions:

- the 03overclock.txt file that was posted a couple of posts earlier... does it news to be pushed via adb or can I just move it via root explorer?

- for all future kernals being released update.zip style, is it necessary or wise to revert the kernal back to stock or can I just flash directly over my previous kernal?
[Vibrant Android Development] floepie:
Just a quickie: Is there a reason that the update.zip version of kernel updating is not on the front page? Is it because it hasn't been widely tested enough, and that there are more potential risks than flashing with ODIN?
[Vibrant Android Development] kassy_ok:
sorry danielmid for taking your spot away :D

vibrant rocks !!

EDIT: Quadrant 2640 points :)
[Vibrant Android Development] xalucardx:
I installed the drift fix oc kernell last night and is working great , great job!
[Vibrant Android Development] skater991:
work with 2.2?

Will this overclock work with the i9000 android 2.2 update.

Id really like to see oc froyo quad scores!!!!!
[Vibrant Android Development] anomalous3:
Probably not, I believe that the 2.2 Ramdisk requires some things changed, and these kernels are actually more like the "boot.img" of yore, a complete kernel and ramdisk package, except they can't yet be disassembled and reassembled.