yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] ttabbal:
If you want to use the lag fix that uses the external SD card, then yes, you do. If not, you don't. Partition 1 is FAT32, Partition 2 is Linux ext4. Both Primary.

There's also the RyanZA style lag fix that uses a loopback filesystem on the internal flash. I noticed corruption issues with that style and moved back to the external SD card. It's a tried and true method from the G1 days. :) Benchmarks are a little slower, but real-life performance feels about the same to me. Particularly with the oc-3 kernel. Even at lower clock speeds, this kernel seems to speed up the feel of the phone. It's.... smoother... or something. :D
[Vibrant Android Development] skater4690:
must say the first time trying the oc kernel and now im kicking myself in the head (really hard to do that lol) i should have used this a long time ago but thought there was no need ocv3 makes my phone way better theres no need for lag fixes i didnt like using them to begin with cause i would still have wake up lag and this gets rid of it completely now my phone completely destroys my coworkers iphone4's the wakeup lag was the only bad thing about my phone. thank you sir for this amazing kernel :D:D:D
[Vibrant Android Development] allareconnected:
Kernel Version???

Sorry for the noob question... I want to make sure jac's no lag oc kernel is still installed after doing a nandroid restore... What should be the version? I am showing 2.6.29. Thanks in advance.
[Vibrant Android Development] chadti99:
Just flashed the kernel last night and my phone has been running great all day set to performance mode in SetCpu at 1200Mhz. Any chance we'll see a 1.3 or higher kernel? I'd like to see if my device can handle it.
[Vibrant Android Development] ttabbal:
The only way to flash a kernel that we know about is Odin. So unless you used Odin, you are still on whatever the last kernel you flashed is. Hopefully, the OTA package will give us the tools to flash from recovery as Odin is a POS.
[Vibrant Android Development] daobn24:
ok so i did everything as instructed but it is not working for me. This is what happened;

I get to step 4 "Reboot into download mode and use ODIN to flash the kernel. Use the CSC field with no PIT file. This will flash the kernel/recovery"

I did exactly that, but when I click start in ODIN the message box says; <OSM> All threads completed. (succeed 0 / failed 0)

i then rebooted and nothing has changed, what am I doing wrong?
[Vibrant Android Development] neasoon:
Make odin work first. Perhaps you have a 64bit windows.
[Vibrant Android Development] allareconnected:
Awesome, thanks! I guess that explains why my phone is working so fast!
[Vibrant Android Development] mygti02:
Wow, i have mine set to Max 1200 Min 800, I also have the Lagfix applied and my Quadrent rating was 2564!!!! holy hell!! My phone is FLYING!!! Nice work!!
[Vibrant Android Development] allareconnected:
Which lagfix & rom??? That is truly amazing!
[Vibrant Android Development] trusteelfan:
great work, cant wait to see a good rom with your kernel built in.
[Vibrant Android Development] mygti02:
stock Rom, rooted with this lagfix: http://xdaforums.com/showthread.php?t=760267

and obviously this OC Kernel :)

cant say it will be the same on yours but, it will for sure be fast. Im also using Launcher pro.
[Vibrant Android Development] The_Chrome_Coyote:
I'm with you, I noticed that the loopback method causes stalling at very odd times, while even with a class 4 card, the external SD card method is buttery smooth.

I'm going to give the ext 4 loopback method a try before I switch back though.
[Vibrant Android Development] likingandroid:
Booting into download mode looses connection to ODIN. Seems like the USB drivers will not load. When I boot the phone up the usb drivers load with no issues. Any ideas?
[Vibrant Android Development] siirial:
Any idea why we are using CSC and not the PDA? And why no PIT file? Older versions used to use the 512 PIT, and the kernel was selected in the PDA field I thought...

Either way, I was unable to flash OCv3 using CSC and no pit, screen would go black, and ODIN just hung at zImage.... numerous times. And it would go into that phone/comp screen immediately when plugged in, so getting back in d/l mode was a pain.

Oddly, I was able to flash it the older way... with the 512PIT and PDA.
[Vibrant Android Development] zimphishmonger:
Flashed to OCv3 when it was released, been running since its release without issue until now. So strange, The time is not accurate, or at least it isnt for long. It is fine when you boot the phone and it auto-updates time from the network, but after a few hours it is off. For example, its current 2:10p, but my phone said 2:23. I enable\disable airline mode, which causes it to resync with the network, and it corrects itself. Woke me up at 4:30 this morning, and the phone said it was 5:30.

I just applied JAC's OCv3 kernel 2 days ago, but I didnt notice any issues until today. Anyone else having a similar issue? It is quite annoying when you cant rely on your cell phones clock lol

Yes, I am using the correct time zone, and No, the inaccuracy isnt always 1 hour. It slowly seems to lose sync. No idea why

Never had this issue prior to flashing the newest kernel, so I figured this would be a good place to see if others have this issue.

Thanks!
[Vibrant Android Development] jackiechan8:
Are you using setcpu? The clock problem was reported on other oc kernel topic too. There someone noticed removing setcpu solved the problem, but it was not confirmed that it was setcpu causing the clock to get out of sync.
[Vibrant Android Development] zimphishmonger:
No, I am not using SetCPU, I dont even have it installed because of the "deep sleep issues" ive had w/ it.

I just compared the phone's clock to an "accurate" clock, and its ony counting 57 seconds per minute, so its 3 seconds off for every minute, which adds up over time, and is causing the sync issue.

WTF, I have no idea whats going on. Any help?
[Vibrant Android Development] Docavelli:
What are you using to change the clock speed? Is there a script out there that sets the clock?
[Vibrant Android Development] zimphishmonger:
Letting the kernel do the clocking, JAC's OCv3 & v1 kernel clock on its own to 1.2Ghz max.You can also use a command, but I forgot it atm. Its def in this thread just a few pages back.

Anyone else notice the clock issue using OCv3?

Thanks!

Seems some folks in the i9000 forum have experienced the same issue. Most say removing SetCPU fixed it, but Im not running SetCPU :(
[Vibrant Android Development] siirial:
I saw @jbowdach has been tweating about it. Haven't found or heard of a fix or of where to look to try and fix....
[Vibrant Android Development] MINUS Stl:
:D Zimp is JBowdach.
[Vibrant Android Development] likingandroid:
Holly smokes. I got a quradrant score of 2621 using Kernel OCv2 set at 1.2.

jrleny@gmail.com
[Vibrant Android Development] zimphishmonger:
Haha, thanks. Ya, I am JBowdach on Twitter. Still havent found anyone using the Vibrant OC kernels that had this issues, but a few in the i9000 forums had it. Waiting to hear from JAC, or someone who knows more about how an OC could affect the system time (besides "its counting faster" lol).

It doesnt seem to affect the SCv9 kernel, so I may try and go back to the OCv3 and see if I can recreate it.

Here ya go, some good reading material: http://androidspin.com/2010/08/23/my-quadrant-is-bigger-than-your-quadrant/
[Vibrant Android Development] CharonIDRONES:
Is anyone else here getting force closes when doing the OCv3 that is out with an ext4 partition? I have an ext4 partition (formatted in Ubuntu) at 1.5GB, I flashed to stock through ODIN, applied the root update, installed and flashed Clockwork recovery, then flashed 's Vibrant6, applied the vibinit.d.zip, then I flashed the kernel, did I miss something with this? Titanium backup is force closing, so is twitter, and a few others. Would appreciate any help. Thanks.
[Vibrant Android Development] zimphishmonger:
Sounds like something is trashed. You can try to run a fix_permissions but you gotta find the script, as its not in Clockwork Recovery. Otherwise, I would try wiping back to stock, and possibly dont apply Vibrant6. Eliminating a variable may help narrow down the issue.

I noticed that too, but found that flashing kernel using the CSC mode & no pit worked more often than PDA + PIT did. ODIN still locked up fairly often, but it was better. I usually end up 'soft bricking' everytime I flash a kernel, but its quite easy to get back to download and retry. Opening ODIN prior to connecting your phone may help as well, as well as using the below technique - gets me in download EVERY time.

Hook up to USB, and from the "PC ! Phone" screen (if your stuck there), Hold both volume and power. Release power as SOON as the screen goes black, and that yellow digger should pop right up :D
[Vibrant Android Development] vibrantFTW:
Deodexed 1.2, Init.d, and Jac's new kernal is fast and stable! Not a single issue. Thank you very much! 2100 quartant with a stock POS memory card.

Regards,

B
[Vibrant Android Development] zimphishmonger:
Okay, got down to business testing OCv3 to verify and reproduce the "system clock lag" issue. From my testing, It seems linked to how often your device sleeps, and how often you wake it. It seems each subsequent wake pushes the clock more and more out of sync, by about 3-5 seconds each wake (either forwards or backwards, it seems to do both).

Using the app clocksync, I ran a few controlled tests to see how reliably I could reproduce this issue. My screen shots are below. The phone's clock was synced with the atomic clock prior to beginning this test, so the offset was 0. Each picture was taken after performing one sleep\wake cycle, except for #6 & 7 - there was a minute or so of sleeping between 5 & 6, and #7 was just to show how quickly the seconds start to add up: within 20 minutes, I'm almost 3 minutes out of sync. See my screenshots below for the results.

After some investigation in the i9000 forums, it seems to be related to unhelpful's OC patch.

Thats as far as my own testing and knowledge can provide. Hopefully JAC can take a look at this :D
[Vibrant Android Development] siirial:
You dirty bastard! Trickery!
[Vibrant Android Development] siirial:
I'll have to try that next time i soft brick. cuz we all know it will happen again as long as we have to flash with odin.

Any idea what the difference is between PDA and CSC etc?
[Vibrant Android Development] zimphishmonger:
I'm not hiding anything, its in my signature :rolleyes:

Ya, they are for different parts of the system (Modem, radio, factoryfs, etc). I was accidently using the pit\pda method for a while before I realized that JAC's instructions said to use CSC. Both seemed to work, but I'd rather follow the man's instructions, even if they do conflict.

I can say the CSC method has a better success rate in my own usage...but ODIN still f***s up quite regularly either way.
[Vibrant Android Development] The_Chrome_Coyote:
In having the clock lag issue too. Though I'm not certain how related it is to wake lag cycles bc I first noticed the issue after leaving my phone asleep all night
[Vibrant Android Development] zimphishmonger:
That's how I first encountered this clock glitch as well, I just noticed the wake/sleep cycle made glitch out, but sleep seems to affects it as well

Sent from my SGH-T959
[Vibrant Android Development] skater4690:
Ok I gotta say that I'm having the clock issue as well mine was off about 10 minutes when I woke up this morning...
[Vibrant Android Development] ttabbal:
I noticed the clock issue as well, I just downloaded an app called ClockSync that will synchronize you with NTP. I just set it to update every hour, only when awake, so it won't kill the battery. If you use your phone as an alarm clock, you might want to enable it while the phone is sleeping as well. :)

Even the every 3 hours setting is probably good enough. I don't really mind if my phone is a few minutes off.
[Vibrant Android Development] zimphishmonger:
Glad others can reproduce this as well. Clocksync is hopefully a temporary band-aid, as this is a pretty big glitch\bug that can hopefully be fixed easily, as I rely on my phones clock fairly often.
[Vibrant Android Development] 18.4009:
Oh how funny! My alarm on my phone went off. I got up and ready for work to find myself 45 minutes early when I arrived! So sitting there waiting to start my shift I read this thread and it all makes sense now.
[Vibrant Android Development] CharonIDRONES:
And now mine also works, using the same setup, although getting 1900 with a class6 card, although meh could care less about that really as long as it is working. Only thing I did different this time was updated busybox (through Stericson's app). Weird.
[Vibrant Android Development] zimphishmonger:
Hah, all it took was for everyones alarm to go off early for this bug to surface. I can confirm scv9 is accurate within 1 second

Sent from my SGH-T959
[Vibrant Android Development] MINUS Stl:
I'm still not having the clock sync issue on OCv3. Guess I'm a lucky one.

It seems like one of the few that has never had an issue with Odin either. Open it up, get into download mode 1st try (phone off, hold both vol, then hold power), and flash whatever I'm flashing 1st try everytime. I've even been flashing the kernels using PDA. :p
[Vibrant Android Development] daobn24:
So i got to step 4 and is still stuck there, trying to get ODIN to work propertly... is there any way to revert the update.zip that i flashed in step 2? is it even necessary, to get back to the original? Sorry for being such a noob at this, but I realized that I shouldn't mess with this mod until i know more about this stuff. Thanks guys.
[Vibrant Android Development] zimphishmonger:
Dont worry about the revert, should be fine.
[Vibrant Android Development] StefanB86:
I'm having the clock issue too, my alarm went off 10 mins earlier this morning. :D

Going to hold off with this kernel today to see if there's any fix... if not, i'll have to go stock i guess.
[Vibrant Android Development] zimphishmonger:
the Non-OC SCv9 doesn't seem to have the clock lag issue. I tested it fairly thoroughly last night, and it doesn't go more then 1-2 second out of sync. Use Clocksync to check up on it. Makes it REAL easy to see exactly how "in sync" your clock is. it can also be used as a temporary band-aid by force-syncing the time to the atomic clock every X mins, but I really rather not do that (as we shouldnt have to, its the CLOCK lol)
[Vibrant Android Development] ArbitrageMan:
If you're reverting to stock by way of flashing the stock kernel, then no, you don't need to revert this update. I don't know of an easy (non copying files from the ext card to the internal card) way to revert without flashing back to stock in fact.

If you're worried about bricking your phone, let me tell you that I've been over the edge and brought the phone back. I was having issues and was able to flash the stock firmware and everything went back to original.

What trouble are you having?
[Vibrant Android Development] chadti99:
How difficult would it be to create a 1.3Ghz kernel or faster? I'd like to try going faster if it's possible.
[Vibrant Android Development] Compliance:
Restart causes endless launcher force close

I noticed a few people are having this similar issue...any word on what causes it?
[Vibrant Android Development] MINUS Stl:
I don't know what happened, but OCv3 has gotten rid of the wake lag, but now I just have normal lag (major at times). I know Quadrant scores aren't all that matters, but I went from 1500's back down to 900's. :confused:

I've Odin'ed back to stock, rooted, clockwork, reformatted my sd, created a new ext4 partition, flashed vibinit.d, flashed kernel and then ttabbal's dc2sd-v2.zip (also tried the loopback and anamolous's manual method) . It's the same setup I had been running for awhile with the v6 kernel. Seriously stumped.

Get rid of one lag, and I get another.....that's worse. :(
[Vibrant Android Development] justanothercrowd:
Check that you only have BusyBox in /system/xbin and that you have busybox period. Tabbal was having issues with his scripts not running because of this. It sounds like yours arent running either with those scores.

I get 1500 quadrant scores with data on ext4 and OC. With loop hack and OC its 2200+

Looking into the clock issue it appears all the OC kernels are having it now that we have changed some code. (us dev's share alot of the code we improve)

SC9 should not have the clock issue or revert to an older OC kernel for now.

I got stung by a bark scorpion last night and am feeling rather ****ty. I will get to this ASAP.
[Vibrant Android Development] MINUS Stl:
Ok, I'll check it out.

Hope you get better soon, man. Bark scorpion doesn't sound like fun. :p Nowhere near as bad, but I got stung by a jellyfish on vaca last month. :)
[Vibrant Android Development] justanothercrowd:
1.3 may require enough voltage to be stable that it may damage peoples phones. We have already had one guy fry his phone overvolting. 1.2 is about the border line that we can safely hit without putting our hardware in danger.

It will be made available once we can ensure it wont kill peoples phones.
[Vibrant Android Development] zimphishmonger:
Many thanks JAC! Appreciate you looking into the clock issue. Hope ya feel better, bark scorpions are crazy critters

Im fairly positive that you went down to 900 because your "lag fix" isnt working anymore, and not because of the kernel. What you describes sounds exactly like an issue I was trying to work on w/ Tabbal, and I ended up fixing it by updating Busybox to 1.18 (I already had it installed, but the update made all the difference. I think thats also the reason why you are having issues w/ my "manual" method of creating the loopback ext4. However, you probably would have the same issues w/ the other loopback mods, as they all are very similar, but because you are inputting one command at a time, you can really see where the errors occur. Should make it a lot easier to get it up and running.
[Vibrant Android Development] ttabbal:
I'll be updating the zips to make sure busybox is installed to the proper location.
[Vibrant Android Development] MINUS Stl:
I see. Well, I checked /system/xbin (as JAC said) and busybox is indeed there. Just Odin'd back to stock (yet again) to give it another try. I'm assuming busybox 1.18 is the latest?

I swear I've been completely stock more in the past 2 days than I have been since buying the phone. :rolleyes:
[Vibrant Android Development] zimphishmonger:
Lol, try stericson's Busybox updater from the market anyways. 1.18 is indeed the latest version
[Vibrant Android Development] ttabbal:
Are the busybox symlinks in /system/xbin? Just the binary isn't enough. I'm going to post some ZIPs over in my thread that should fix busybox up. Hopefully it helps you guys.
[Vibrant Android Development] MINUS Stl:
Well, I ended up flashing the v6 kernel and was able to flash ttabbal's v2.zip. Everything is working again. Had to get something working tonight and can deal with a little wake lag over touchscreen/app lag. :) Will give it another shot tomorrow.

One note: downloaded Stericson's busybox app and on first run, it said it couldn't find busybox in /system even though I checked /system/xbin and it was there. After installing 1.18 via the app, it then said I had multiple busybox installs? :confused:
[Vibrant Android Development] anomalous3:
bark scorpion stings are no bueno. "rather ****ty" is about what I remember. hope you feel better
[Vibrant Android Development] brandnewsimmy:
Screen timeout?

So after I tossed on OCv3 I had some screen timeout issues. It seems like after like 15-24 hours (not sure exactly) the phone screen will never timeout. I can manually get it off when I hit lock, but if a text comes in or something the screen will turn on and stay on. I was also experiencing the clock issue so with both of these I decided to go back to stock for now, however I still have this same problem. The issue will go away when I restart the phone, but has come back each time. Other than that, the OC worked great and the wake-lag was totally gone! Anyone else experience this or have an idea for a fix? Thanks.
[Vibrant Android Development] Lunatixz:
I'm also experiencing time issues o initially though it was the oc so I set setup back to stock... but it didn't fix it.. any ideas?
[Vibrant Android Development] zimphishmonger:
I'm pretty sure that's normal for the first run of the busybox app. Try SCv9 kernel, works great and no wake lag or clock lag. Until JAC can take a look at the oc kernel, I'm keeping this set up.

Sent from my SGH-T959
[Vibrant Android Development] justanothercrowd:
Yeah this is the most stable kernel ATM and has no issues such as wake lag etc.

I've been working with some other devs from i9k forum that are having the same issue as well as unhelpful whos kernel is having the same issue. We will get it fixed dont worry. We got the wake lag fixed :)

Just sit tight. I'm not going to just stop deving on this kernel. Working a bit on CM6 but havent got anything done today really feeling like crap from that sting. Soon my friends.
[Vibrant Android Development] The_Chrome_Coyote:
Im having really strange behaviour lately, I decided to switch back to EXT4 External SD lagfix rather than the loop method...

So I flashed JFD w/ Odin

Installed Root, Clockwork, Busybox

Flashed Vibrant6

Flashed Vibinit.d

Rebooted to ensure Busybox, and Init.d folder existed

Flashed Kernel OC3

... now this is where it gets strange, swapping back from OC3 to v9 caused a complete settings erasure of all apps on SD, and disassociation with all apps resulting in constant FC's

This never happened before when jumping from OC to non OC kernels... Thoughts? Did I do something wrong?
[Vibrant Android Development] vibrantFTW:
Can a kernal mess with reception? My bars have gotten noticebly different with deodexed and jac's newest kernal. Hope it isn't my phone. As always thanks for the hard work! I'm just curious if it is possible or I need to look at something else as the culprit.

Regards,

B
[Vibrant Android Development] MINUS Stl:
Ill try SCv9 tonight and see how that goes. Definitely appreciate all the help and I know it'll get worked out.
[Vibrant Android Development] justanothercrowd:
arg. Still seeing the clock issues on OC. Same with unhelpfuls kernel. Weird thing is not everyone is having it. But most seem to be.
[Vibrant Android Development] justanothercrowd:
This kernel shouldn't touch anything on the Internal SD and only on the external SD if you have a ext4 partition. Doesnt sound like you did anything wrong though. OC3 and v9 should have the same exact RAMDISK and inits so they tech shouldn't be acting any different on boot.

Well the only diff is that the OCv3 and v9 kernel is v9 loads the FMradio module which was a request made. I doubt it would cause erase issues though.
[Vibrant Android Development] zimphishmonger:
Thanks for working so hard on nixing that issue. Appreciate your effort. I have no doubt you guys will figure it out :)
[Vibrant Android Development] Lunatixz:
I noticed the time offset occurs when the screen goes into standby...

Instead of flashing to a new kernel I downloaded a clock sync app from marketplace.. I'll wait for a fix...

Thanks for the great work
[Vibrant Android Development] The_Chrome_Coyote:
I didnt think it affected anything which is what made the situation so strange to me. I mustve gone through the exact same process with your other Kernels without an issue. It seemed like everytime the app2SD script was run from init.d that it reset settings and disassociated all the apps.
[Vibrant Android Development] anomalous3:
Every time your phone switches to or from roaming or non t-mobile networks the time and date get updated. so those of us who live in areas where t-mobile doesn't have great coverage won't see it as much because we'll be switching networks often enough to keep things in sync.
[Vibrant Android Development] MINUS Stl:
No wonder I never noticed the clock issue. Signal here at work is HORRID! Guess that's one reason bad service can be a good thing. :D