yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] zimphishmonger:
Great! Glad its already working. If you need an additional tester, feel free to pm or tweet me.

I've gone through the source, but my linux vm is trashed so I can't compile it myself until I set up my vm again :-|

Sent from my SGH-T959
[Vibrant Android Development] p()()pypants:
Sadly my phone seems to be one of the few that can't handle the overclock@ 1200... It freezes up and seems to do so more often during graphic intensive talks but will do so even without them sometimes (poo).

Wondered if you can give me an idea if the 1900 quadrant is with a stock kernel or only the oc kernel, and what the stock kernel can do with this new ext system???

I'm seriously so poised that my phone won't overclock that I'm going to return the phone, usb port has been loose since I bought it anyways
[Vibrant Android Development] CharonIDRONES:
Patiently waiting for the new version! Can't wait. Get rid of that ****ty rfs and go with a good ol' standard. Can't wait to be running Vibrant9 with your kernel!
[Vibrant Android Development] Goog1e Phone:
Ohhh I just wet my pants. Extremely excited about this!

Sent from my SGH-T959
[Vibrant Android Development] krylon360:
I so cant wait for this.
[Vibrant Android Development] Arcadia310:
Nice, can't wait to finally get an appropriate lagfix.
[Vibrant Android Development] t1h5ta3:
cant wait, sounds like eugeenes 1.0 is going to have this and posably be out late today!!?
[Vibrant Android Development] Goog1e Phone:
So I'm guessing with the new lag fix, I'm not going to need my external ext4 on my SD card right? I'm running ttabbals script that is built in on JAC's SCv9 kernal.
[Vibrant Android Development] zimphishmonger:
Correct, has nothing to do w/ your external SD
[Vibrant Android Development] Goog1e Phone:
So when I flashed this, I flashed the Data and Dalvik init.d lagfix. I had an external EXT4. Now I want to remove the lag fix. What do I need to do in order to do this besides removing the EXT4 partition on my external SD card? Any zip files that I can flash to basically revert it?
[Vibrant Android Development] BrianLangley:
I can't wait for the 1.6ghz! That would be almost 2/3 of my computers processor! I love my vibrant! Can't wait for a froyo rom either, definitely a lot of speed improvements in froyo! Make sure this is compatible with the first stable froyo rom! :D
[Vibrant Android Development] Arcadia310:
1.6Ghz?:confused:
[Vibrant Android Development] djnutz:
And totally different processor. It's not just how fast its clocked.
[Vibrant Android Development] zimphishmonger:
The CPU is theoretically rated for up to 1.6Ghz, but we will never get there. Our 1Ghz hummingbird CPU is very sensitive to voltage, and raising the clock that high would require a significant increase in voltage, which would likely kill it, we don't want that. We may get 1.3Ghz stable out of it for some lucky people, but def not more, and possibly less.
[Vibrant Android Development] Arcadia310:
Thought the new kernels would be up last night?
[Vibrant Android Development] zimphishmonger:
Same :-( Need my voodoo fix lol
[Vibrant Android Development] robavila721:
I think there was a problem when trying to remove the fix or when flashed over it. Something along those lines. thats why curio was going to release a beta2 first.
[Vibrant Android Development] skater991:
setcpu?

I have noticed lower quadrant scores with setcpu uninstalled? has anyone else noticed this? i guess cause it isnt scaling to 1200 like with setcpu?
[Vibrant Android Development] jumpymonkey:
Awesome job on this kernel! Donation heading your way when I get home from work.

With all the great work you do, you continually reaffirm my wise decision to purchase the Vibrant. Same was true before with my G1.
[Vibrant Android Development] r6kid:
You guys should make a support "app" on the market for us folks that don't have paypal (at the moment). I would send money your way if I could do it by way of the market.
[Vibrant Android Development] blackerwater:
Bump...... Any progress on v5?

Sent using xda app.
[Vibrant Android Development] Jayrod1980:
Any word of when the ext4 cadiz worth no rfs at all will be ready with this kernel?
[Vibrant Android Development] blackerwater:
I think some errors came up. Im patiently waiting also ;)

Sent using xda app.
[Vibrant Android Development] Jayrod1980:
Stupid swype, don't know how it put cadiz there. I'm really looking forward to the kernal using ext 4 exclusively. I think this would eliminate the criticism that the lag fix io numbers in quadrant are artificially inflated.

Once this is out, I think this will make the vibrant run the way it should have from the beginning. I wonder too what samsung has done in the hardware of this phone that makes having a vanilla rom so difficult, our perhaps it's in the firmware.

Anyway, shouldn't running ext natively at least help the situation?
[Vibrant Android Development] blackerwater:
What scripts are people using at startup?

Sent using xda app.
[Vibrant Android Development] angryPirate12:
JAC said hes getting around 1900 with curio's ext4 data tweak. Which is consistent to what i was getting when i used ext4 partitions with the loopback lagfix's in use now.
[Vibrant Android Development] morfic:
Maybe there is some double caching going on with loopmount version of the fix, I used their userinit.sh and been mounting ext2 partition on external sdcard, 1800 vs 2100 with loopmount, more importantly I have no crazy stalls.

So let them cry, 1800 is real. If froyo has newer kernel, we might see a bfs version for even more smoothness in usability.

Sent from my Vibrant.
[Vibrant Android Development] ju5tiiv:
From jac's twitter feed about a half an hour ago...

All bugs resolved with the voodoo _lagfix beta1. Beta two will have calibrated screen color as well. Things are looking good

Followed by a few other more recent posts, making sure curio gets credit and thanked.
[Vibrant Android Development] blackerwater:
Nice

Sent from my vibrant
[Vibrant Android Development] morfic:
Calibrated to what and by who? Or does this mean it can be calibrated by us?
[Vibrant Android Development] zimphishmonger:
Possibly, just wait and find out. We dont know anymore than what supercurio has told us on twitter.
[Vibrant Android Development] questgraves:
Hope this helps

Hey guys i found this other day pretty interesting i dont have time to read all 71 pages to see if someone posted this or not. i apologize before hand if im being redundant

(add the h's without w's here)pdadb.net/index.php?m=repository&id=644&c=samsung_s5pc110_microprocessor_user_manual_1.00[/url]

ok it doesnt link... anyway its 2000+ pages but a few quick searches brought up max and min voltages, frequencies and other potentially useful overclocker info
[Vibrant Android Development] draztik:
If I restore to my stock nandroid backup will this kernel still be on my phone?
[Vibrant Android Development] Alkaloid:
Yes. If you want to go back to the stock Kernel you'll have to flash back to it. Instructions to do so are in OP.
[Vibrant Android Development] Goog1e Phone:
I'm seriously updating this thread every hour to see when the new lag fix is coming out. So exited!

Sent from my SGH-T959
[Vibrant Android Development] skater4690:
lol im in the same boat as you
[Vibrant Android Development] dattas:
Instead of doing that why not just follow him on twitter? Seems like testing is going well.
[Vibrant Android Development] PSP_Hacker:
What version is this kernel? If it is 2.6.32 then it has HIGHMEM support which is great!

Also, when does the 1.2 Ghz setting take effect? Immediately after the kernel starts? Can I put a script in init.d so that it never boots with that frequency?
[Vibrant Android Development] Alkaloid:
You have to set the overclock manually using setCPU. So if you don't want to boot with that frequency, simply don't set it.
[Vibrant Android Development] joe.kerwin:
I used the update.zip to flash the most recent 1.2ghz kernel. So if I restore, and the kernel remains, are there any flashable stock revert zips I can use through clockwork? Noticed my battery life has gone down since flashing this. Thanks.

EDIT: Again, I see that there is a stock revert, but I want to know if it exists in the form of an update.zip to use through recovery.
[Vibrant Android Development] glensta:
Yeah me too - work seems boring next to waiting for the new lag-fix. Hope my boss don't see this :-)
[Vibrant Android Development] PSP_Hacker:
I'm also waiting for this, just in case sonething screws up :D

by the way, are you able to enter recovery with your phone only? The new Vibrants appear to have this ability removed, so ADB or a Terminal is required. I don't like this :|
[Vibrant Android Development] joe.kerwin:
What do you mean? I can access recovery via Rom manager or holding down volume keys. I did get my vibrant the week it was released though.
[Vibrant Android Development] The_Chrome_Coyote:
Check out Eugene's Vibrant9 Thread, he has a stock kernel as an update.zip posted
[Vibrant Android Development] joe.kerwin:
thanks man
[Vibrant Android Development] PSP_Hacker:
I forgot to mention that ROM manager works, but the volume keys will not get the phone into recovery. I got my Vibrant 3 weeks ago. There's a thread about this issue in the development section :(
[Vibrant Android Development] ajftl:
U guys use setcpu? If yes conservative or ondemand?
[Vibrant Android Development] rpesigan6:
CONSERVATIVE. if you read throughout the thread, there are people still having problems with the phone shutting off with low cpu profiles.
[Vibrant Android Development] bagayas:
Conservative. I believe there's a blurb in the setcpu faq online that says that all Galaxy S variants should use the conservative setting as there's a known problem with the ondemand setting.
[Vibrant Android Development] PSP_Hacker:
Low CPU profiles causing shut downs? This explains why my phone shutoff even with the conservative scaling set; I was setting the CPU to 100-400 when the screen was off. Am I correct?
[Vibrant Android Development] PSP_Hacker:
This kernel is fantastic. Even with 100-1000 Mhz, I get better benchmark results than the stock kernel at the same speeds.
[Vibrant Android Development] r6kid:
Is anyone else checking this thread religiously for voodoo? :)
[Vibrant Android Development] kaizasoshi:
+1...should be close
[Vibrant Android Development] r6kid:
From jacs twitter it seems like he's got a stable version
[Vibrant Android Development] drhonk:
hah..of course
[Vibrant Android Development] rizzxx7:
damn these devs are fast
[Vibrant Android Development] jphilpot:
not sure if anyone else is having this issue but everytime i have it overclocked using this kernel it causes all games to lock up. any fix ?
[Vibrant Android Development] t1h5ta3:
loving oc4 hitting consistant 9.7 - 9.75mflops w/o any lag fix etc. cant wait for vodoo!!
[Vibrant Android Development] p()()pypants:
Get a new phone... Mine does the same, guess not all the processors were made equal and some can't handle the over clock.... Mine can do it just multitasking and doing something like opening maps, boom, frozen and have to pull the battery.

I had a problem with the usb/charging port being loose anyways and am sending mine in on a replacement, hoping that it can a) handle an overclock and b) access recovery via hardware..... B) is actually a reason in and of itself to get a replacement by the way guys, its a known defect and t-mobile will take it back and give you a new one for that alone.

Pooped from my Samsung Vibrant using XDA app...

Dont mind the skidmarks...
[Vibrant Android Development] zimphishmonger:
Been following this project since before it was called "voodoo". Very excited for beta2 :D
[Vibrant Android Development] zimphishmonger:
Its probably your CPU. Not all CPUs can clock that high using stock voltage, and playing a game is stressing the CPU\GPU so it makes sense it work lock up. Wait for JAC to release a version w/ slightly higher voltages
[Vibrant Android Development] p()()pypants:
Saw some of the tweets.... Sounds super close, can't wait honestly, i definitely want this instead since I'm getting a replacement and keep reading there's problems with corruption from the ext2 and noticed that all the lags I've tried start begin sooner or later....

Pooped from my Samsung Vibrant using XDA app...

Dont mind the skidmarks...
[Vibrant Android Development] PJcastaldo:
So if your phone won't acess recovery, then that's a reason for replacement?

I don't have that problem, but I have a nick in my screen and was going to turn it in on warranty for a "loose" usb port but I was afraid I would have root problems...
[Vibrant Android Development] p()()pypants:
yes. I actually just received my replacement today since posting that, it was hardware locked, immediately called 611 got in the tech support center and they are having me hang onto my og phone send back the replacement instead and then sending me one with a note for them to ensure it boots into recovery fine before they send it.

might be careful on sending a phone back with some physical damage, they might void your warranty and deny your claim.... in other words send you a replacement and just charge you instead.... that would suck.

also tested the phone while i had it and checked to see if it could handle the overclocked kernel, it could. So ill be extra pissed if I get ANOTHER one back again that cant overclock correctly without freezing or some other stupid defect...
[Vibrant Android Development] zimphishmonger:
that doesnt sound like a reason to return it, and they may not return it with the nick in the screen. Depends how observant the salesperson handling the return is.
[Vibrant Android Development] drhonk:
My phone seems to have its battery life worsen after I installed setcpu. Is that normal? Now if I don't use setcpu is that mean that my phone will always use 1.2GHz ?

UPDATE: I ended up uninstalling setcpu .. :D
[Vibrant Android Development] rizzxx7:
I'm ready for this update, I just flashed back to stock :D
[Vibrant Android Development] Arcadia310:
I'm not sure about this. I've been using ondemand for weeks now and it works perfect. In fact it the screen wakes up faster in ondemand.
[Vibrant Android Development] djnutz:
What do you have the on demand settings set as?
[Vibrant Android Development] jdkackley:
Im curious too. What do you have it set at? I dont even use set cpu for the plain reason that i have to do battery pulls all the time from the dreaded sleep coma. I found that overclock widget from the market works better for me. I set mine to clock from 100 to 600 with screen off and from 100 to 1200 with screen on. Pretty basic, I know. But its super stable for me. And helps a little with battery life. For what its worth.:cool:
[Vibrant Android Development] Jayrod1980:
Too bad I don't use twitter, can't wait for this new kernel
[Vibrant Android Development] drhonk:
What is the name of that overclock widget you were talking about?
[Vibrant Android Development] djnutz:
SetCpu. Available in the market.
[Vibrant Android Development] zimphishmonger:
Seems Beta2 for the i9000 was released, hopefully JAC will release his kernel w/ the "voodoo" fix soon :D
[Vibrant Android Development] jdkackley:
Its just called overclock widget, search the market, its free.
[Vibrant Android Development] Goog1e Phone:
YES! Can't wait for this. Hopefully when I come home from work tonight, JAC will be kind enough to have it ready! *drools*
[Vibrant Android Development] jdkackley:
Just read on twitter that JAC has voodoo beta ready to be ported! Everyone keep their eyes peeled! He said it will be on xda!
[Vibrant Android Development] blackerwater:
Now that's something to get excited about. Hook it up jac! I love your work :)

Sent from my vibrant
[Vibrant Android Development] jdkackley:
Word! +1! Screw that new weak ass update!
[Vibrant Android Development] drhonk:
HAHA ... good one :D
[Vibrant Android Development] Gr8gorilla:
so why cant you get the best of both worlds and flash the update and then flash the JAC kernel?
[Vibrant Android Development] jdkackley:
We probably can, but I'm holding off on the update to see what happens with voodoo tonite. From what I read, the update looks like a fart in a wind storm. I'll wait for voodoo. I've got too much blood sweet and tears into this phone to just flash the first thing to come along that looks like an update. Eugene and Jac have both reverted back to pre update. I'll wait for now. Just my opinion.
[Vibrant Android Development] I7oobie:
+1, I'll take the Voodoo kernel over the new update. Me smarts, me read a lot...
[Vibrant Android Development] blackerwater:
I thought this was coming out tonight? Ive been checking every half hour :)

Sent from my vibrant
[Vibrant Android Development] tweezit:
thats from his twitter page.
[Vibrant Android Development] glensta:
Thanks for the update on this.
[Vibrant Android Development] blackerwater:
Yes thanks! Now I can sleep

Edit: I'm back still no update here or twitter :(

Sent from my vibrant
[Vibrant Android Development] mikey98277:
delete please
[Vibrant Android Development] justanothercrowd:
More kernels are to come. Just been busy with the Voodoo project. There will be OC flavors available with Voodoo with user-script support and stock Voodoo kernels a flavor for everyone.

Also more GPU OC and I'm torn on user configurable UV as that may be a hassle for some people but may be easier if an .apk is made like for other kernels. Since UV can cause some stability issues obviously :)
[Vibrant Android Development] djnutz:
*sets display to no time out and watches thread eagerly*
[Vibrant Android Development] morfic:
UV causes the same instability issues as OC, same difference on CPU quality, those that OC better will UV better. give people a kernel that boots to default and let them pick to OC or UV and by how much?
[Vibrant Android Development] The_Chrome_Coyote:
Logcat just reads Waiting for Device and never posts anything
[Vibrant Android Development] masr1979:
Holy.... 1900? Damn I was happy I was getting 1447 or something. I can't wait to see the scores once we get froyo going on these babies.

Any pointers on how to get get up to your results? Not that I'm not satisfied with how things are running right now... but any excuse to tinker more with the device is welcomed :D
[Vibrant Android Development] zimphishmonger:
Funny enough, that tells us something. Your device isnt getting recognized by the PC, either because the phone isnt getting to the point during boot-up where ADB will work, or the USB drivers\ADB set-up isnt working.

Were you able to use ADB w/ the phone before this issue? If not, thats where you should start.

If ADB is for sure working on your PC, then I would use the JFD ODIN image (from Samsung) to restore your phone to factory spec, and try again. Make sure your ADB is working before flashing anything, ADB and terminal are lifesavers.
[Vibrant Android Development] zimphishmonger:
He may have confirmed my sneaking suspicion that EXT4 is faster for this purpose (it has been shown that EXT4 is actually slower than EXT3 for the type and size file we use, but those are just benchmarks).

I am running on EXT3, w/ the kernel, using the EXT hack on a 1GB EXT3 partition on a class 6 card, yet Im stuck at around ~1100. I am going to attempt to convert to EXT4 and retest, hopefully ill be seeing these ~1400 scores that everyone else is getting, and would confirm my hunch.

EDIT: Nope, didnt do much after converting to EXT4. Still got~1100 on Quadrant
[Vibrant Android Development] davbran:
What sdcard is everyone using? I have a Class 6 and it must be total dog crap because using ext4 on a clean install I only get 1100 ish.
[Vibrant Android Development] The_Chrome_Coyote:
JFD Odin'ed maybe a dozen times today lol Im good with that step in the process.

I was using ADB beforehand with this device; here is my process:

1. ODIN JFD Image

2. Install ROOT

3. Install Clockwork

4. Reboot Clockwork Recovery

5. Flash vibinit.d.zip

6. Verify folder under /system/etc

7. Reboot Download via ADB

8. ODIN Kernel

9... Hangs on Vibrant Logo "waiting for device" on logcat

You said it hangs on Busybox? Maybe if I install the Busybox installer to make sure Im running the latest version?

I can get the ROM from anomalous3 to work, but Eugene's hangs at Vibrant screen as well

EDIT: nope. Installed latest version of BusyBox and it still hangs with no ADB Log activity.
[Vibrant Android Development] mytmouse:
Having the same issue. It is pretty annoying.
[Vibrant Android Development] zimphishmonger:
You are not the only one man, I have a Kingston Class 6 MicroSD (1B EXT4) and i'm stuck at ~1100 and clueless as to why. Thats a pretty big difference for no real reason, at least what I can see. Ive disabled LW, using AutoKiller (tried disabling it as well). Nada...

Okay, so you certainly have everything down. No issue there.

Your issue has nothing to do w/ BusyBox, now I know. It tells you that using ADB

I'm actually pretty stumped by this one. For some reason, either your phone isnt getting to the stage of boot-up that provides ADB access, or its just not making a connection with your ADB server, which starts up when you an adb command .:confused:
[Vibrant Android Development] numba1cuban:
I was gonna revert back to the stock rom and reflash this kernal since im using the unodexed rom version but im just gonna wait on Jac and se what he says about it. I agree it is really annoying. hope this doesnt get overlooked could be a possible bug.
[Vibrant Android Development] Goog1e Phone:
On step 3 of the instructions, should it be named kernel-vibext4.tar?

Or is it really suppose to be named kernel-vibext4.tar.md5? Maybe that's why people are having issues flashing this. Can anyone confirm?

Also, are people getting the 3 second lag because they flashed the unodexed rom version before? Or is EVERYONE getting the 3 second lag when waking up the phone?
[Vibrant Android Development] danielmid84:
I flashed it named with the md5 and it worked fine.

I came from a rooted stock rom with the d2sd enabled already, and I have the lag.
[Vibrant Android Development] The_Chrome_Coyote:
I sort of answered this question by just turning up the volume on my comp. I dont hear the Beep indicating the computer has made a connection with the device after flashing the kernel. It just makes no sound at all
[Vibrant Android Development] gilsken:
@JAC

An idea I've got is to avoid issues if flashing your kernel without installing the init.d directory, can I add a script file, myinit.sh for instance in /system/etc, and change in the init.rc

myinit.sh

#!/system/bin/sh

if [ -d /system/etc/init.d ]

then

/system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d

fi;

and in init.rc

service sysinit /system/etc/myinit.sh

What do you think about that ?

Thanks.
[Vibrant Android Development] justanothercrowd:
Revision 2 is up

UPDATE:Volume rockers fixed

Cleaned up RAMDISK

Updated Busybox

Stock recovery fully reverted

Enjoy!
[Vibrant Android Development] justanothercrowd:
I think the way you mentioned is how CM6 does it. It really doesn't matter as long as theres something setting the prop after checking for user scripts.
[Vibrant Android Development] justanothercrowd:
This is a known issue at this point. Not sure whats causing it but it is being looked into.
[Vibrant Android Development] mesajoejoe:
love love love
[Vibrant Android Development] frank707:
Do we re apply the update through recovery or take any other measures before updating to rev 2? Or is it just flashing the kernel through odin.

Sent from my SGH-T959
[Vibrant Android Development] justanothercrowd:
Just flash the kernel. Volume rockers where the main complaint so i had to get those fixed. More fixes/improvements to come.
[Vibrant Android Development] ArbitrageMan:
I don't know if you're still having issues, but I read that Odin wouldn't work if ADB was running... When I did this flash I specifically did NOT "adb reboot", and instead went into download mode manually. Odin threw up a COM port immediately when, after being in download mode, I unplugged and replugged the usb cable.
[Vibrant Android Development] ArbitrageMan:
I came from the stock rom. I do not have the 3 second wake-up lag.