yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] masr1979:
My experience with setcpu hasn't been that great on the vibrant. I'm using the OC kernel, applied the lagfix using chainfires application, with an ext2 partition, and the moment I enable setcpu my device turns off at random intervals when it's sleeping. Without it I've got no problem, and the wakelag isn't constant either.

What settings were those of you that had problems with setcpu using? I'm thinking it's the "screen off" profile, had mine set to 800 - 400, ondemand.

Well there's plenty of material on how to get into download mode, so I just feel I should remind you to please search; however, might as well help you out :D

Two ways to go about it, easiest is if you have adb access (which you should before you start messing with your phone) simply do

If you don't have adb access, or you feel like doing it another way (did I mention I strongly urge you to have adb access?) then you will need to

1) Turn off your phone

2) Open odin

3) Connect your phone to the pc (disable Kies or New PC Studio if either are installed)

4) Wait for the battery icon to come up

5) Press and hold vol + and - (middle of the volume button) and power

6) Wait for the screen to go blank and release power, while leaving vol + and - pressed

7) You should be in download mode now, check odin to make sure that it sees your phone; under ID:COM you should see a the com port being used by the phone.

If you don't see a com port, unplug your phone from the pc, close odin, open it once again (not really necessary) and you should it pop up. Point is odin needs to be opened BEFORE your phone boots into download mode (connected to the pc)

Do a bit more reading, and triple read whatever the instructions are for what you are flashing with odin, good luck.
[Vibrant Android Development] zimphishmonger:
Hook up to USB, While its on, hold vol - , vol+, power. Let go of power as soon as the screen goes black
[Vibrant Android Development] gehlersjr:
ok will try
[Vibrant Android Development] gehlersjr:
As I said

I have quite a bit of working knowledge with adb and the android Sdk, like I said I have tried all button combinations w/Odin on and seeing the device plugged and unplugged. The only time that I had not seen was this last saying to do adb reboot download. And I have searched googles and all.
[Vibrant Android Development] gehlersjr:
Big problem

I was in the middle of flashing with odin and my computer chimed and the odin window said removed apparently the usb got disturbed in the middle because phone powered off now I get a computer and phone symbol and can't get it back into download mode to reflash what to do!!!
[Vibrant Android Development] ttabbal:
Keep working on it. The only way out of that is download mode and odin. It will work, just not as reliably as we would like.
[Vibrant Android Development] zimphishmonger:
Try hooking it up to USB while trying, I found that GREATLY increased my success rate of getting from that exact screen to download mode. Now I can do it in one try :-)
[Vibrant Android Development] justanothercrowd:
New OC kernel us up. We ARE working on the wake_lag..its just been a real pain. The new OC kernel has the steps added back in and more aggressive threshold settings while trying to maintain a balance of perf and battery life.

I also tested some of tabbals scripts as i noticed he was having some issues. Didnt have any of the unexpected exits in logcat. Maybe try updating BB i know the past few revisions have had some bugs.

This one that just moves data worked fine for me. PM me if you keep having issues tabbal.

I am also working on getting CM6 running on the Vibrant ATM.

#!/system/bin/sh

BB=busybox
#BB=echo

/system/bin/e2fsck -Dyf /dev/block/mmcblk1p2;

$BB mount -o noatime,nodiratime -t auto /dev/block/mmcblk1p2 /sd-ext;

if [ "$?" = 0 ];
then
for i in data;
do
if [ ! -d /sd-ext/$i ];
then
$BB mkdir /sd-ext/$i;
fi;

DATA=`$BB du -s /data/$i | $BB awk '{print $1}'`;
EXT=`$BB du -s /sd-ext/$i | $BB awk '{print $1}'`;

if [ $DATA -ge $EXT ]
then
$BB rm -r /sd-ext/$i;
$BB cp -rp /data/$i /sd-ext/;
$BB chown 1000:1000 /sd-ext/$i;
$BB chmod 771 /sd-ext/$i;

if [ -d /data/old-$i ]
then
$BB rm -r /data/old-$i;
fi;

$BB mv /data/$i /data/old-$i;

$BB mkdir /data/$i;
$BB chown 1000:1000 /data/$i;
$BB chmod 771 /data/$i;
$BB sync;
fi;

$BB mount -o bind /sd-ext/$i /data/$i;

done;
fi;
[Vibrant Android Development] justanothercrowd:
I can get download mode without fail if turn the phone off and disconnect the USB cable. Then hold both volume buttons and with a live USB cable (plugged into the computer) plug the USB and it will trigger the phone to power on and it will go right into download mode. Has never failed me yet. No power button pushing is needed.
[Vibrant Android Development] djkdawg:
it too me a while, but i finally got everything setup right and man look at my results :)

everything moves fast for me, other then i have some problems waking the phone up when i use setcpu app. so i uninstalled the app and the only problem i have now is the 3 sec delay to turn the screen on, no biggy to me!!!!!
[Vibrant Android Development] tweezit:
So I take it since the new oc kernal is a tar we need to run it as a pda file and use a pit file right?
[Vibrant Android Development] zimphishmonger:
Thanks so much for the updated OC kernel. I look forward to your eventual fix for the wake lag, and I VERY much look forward to CM6 on our Vibrants, whenever it is ready. Its much appreciated! :D

EDIT: Although I dont trust Quadrant as far as I can throw it (its terribly inaccurate as a general system benchmark), I am noticing a fairly significant decrease in Quadrant scores after applying the Ocv2 kernel, moving from OC1. No idea why, if the up/down thresholds are more aggressive. Several retests to confirm the lower scores. Anyone else?
[Vibrant Android Development] robavila721:
won't seem to flash

I have no problem getting into download mode and using odin, but i tried to flash the old oc kernal a few days ago, and it wouldnt flash, it would just get stuck, forcing me to go back to stock since i would get the phone-computer icon. i followed the instructions that said not to use the .pit file and put it on the csc part.
[Vibrant Android Development] djkdawg:
you will leave the pda file blank and the pit area blank, just lost the kernal into the csc file and then flash it
[Vibrant Android Development] merrifield69:
When flashing odin gets stuck at zimage and just sits there

is where something i'm doing wrong?
[Vibrant Android Development] djkdawg:
no, i had this problem , it took me like 20 times for it to work right, try switching usb ports , thats what i did and it just so happen to work right
[Vibrant Android Development] merrifield69:
lol, i just think its weird that it doesn't work because using the same usb port i can flash the stock kernel back.

whatever ill keep trying tho, thank you!
[Vibrant Android Development] robavila721:
does it matter what "COM" number is displayed i had read to make sure it said COM7?
[Vibrant Android Development] The_Chrome_Coyote:
Same issue here. With OC 1 I was hitting 2500+ on quadrant, now I'm getting 1800 ish which isn't any better than what I was getting with kernel v 8 non OC
[Vibrant Android Development] Klyentel:
my phone got stuck at the phone to pc screen. what do i do?
[Vibrant Android Development] irishmn69:
Hold vol up and down with power until screen goes off, then let go and you be at the downloading triangle again, try again.
[Vibrant Android Development] Klyentel:
I tried that. The screen went off....then came back on at the phone to pc image again.
[Vibrant Android Development] neasoon:
Is the wake up lag still here? I suspect it relates to power management. Sometimes there is delay sometimes not. And with the wake up delay, the battery can last much longer. For example, flight mode with wifi off, virtually no background tasks, the battery is still 100% after 9 hours... On the other hand, it might consume 10-20% battery if the screen instantly turns on after clicking the power button.
[Vibrant Android Development] Klyentel:
Nevermind got it! The trick is....hold the power button alone until the screen turns black, as soon as it does let go of the power button and quickly press and hold the up and down volume keys until the screen comes back. Then there you go....back to download mode. :D
[Vibrant Android Development] justanothercrowd:
Try linpack to just test the CPU . I noticed quadrant scores arent as high which is a bit weird but quadrant isnt a very good benchmark for CPU.

I'll go over the code changes i made to see if i can find why it isnt performing as well as the first OC with higher up thresholds. I have an idea why though..now to test it out.
[Vibrant Android Development] tweezit:
Great cant wait to hear your results :)

Also just curious if you plan on posting any higher oc builds comming up if the 1.2 works out good?
[Vibrant Android Development] ArbitrageMan:
Ive been running version 2 of this kernel for a while now, its been awesome!!

However, I was never able to update busybox, and since I need to do that, I wanted to update to the latest version of this kernel, 8. The problem is that after I flash the kernel, the phone restarts and sits at the Vibrant screen and never goes further. I left it sitting for half an hour with no change.

I am able to flash back to version 2 without issue. What am I doing wrong? Do I need to flash back to stock?

I don't know if this is relevant or not, but I'm running anomalous3's deodexed rom.

Odin seems to think everything went fine:

<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> Enter CS for MD5..
<ID:0/007> Leave CS..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> zImage
<ID:0/007> Removed!!
<ID:0/007> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
[Vibrant Android Development] ArbitrageMan:
Things just got a lot worse. I cant flash anything now...odin keeps getting stuck on zimage. Ive tried different usb ports. Battery pull. Restarting computer.

This is not good...
[Vibrant Android Development] The_Chrome_Coyote:
Running only an 8 in linpack
[Vibrant Android Development] jlaval:
can u share your settings? (ROM, kernel, etc)
[Vibrant Android Development] justanothercrowd:
Are you going into set CPU and raising it to 1200 before this. It is defaulted to 1000mhz out of the box for stablity reasons. You have to OC it it with set CPU unlike OCv1 that just ramps up to 1200 automatically.

Once set to 1200 i get 9.2-9.9 in Linpack check top devices and look at my scores.

Otherwise out of the box capping at 1000mhz it would make sense the scores look the same as the stock kernel. Let me know.

Ans yes I have a 1.3 version kernel but i doubt it will be stable on everyones phone. This CPU is very voltage sensitive. I am working on a 1.2Ghz UV and a 1Ghz UV kernel ATM as well.

You should also have no issue replacing busybox in any kernel since v7 since it was removed from the ramdisk at that point. I have no issue using stericsons utility.
[Vibrant Android Development] zimphishmonger:
I have a major issue w/ SetCPU causing my Vibrant to never wake up from deep sleep (several different ones actually). The only fix I found was removing SetCPU. Anything you can suggest?
[Vibrant Android Development] justanothercrowd:
Issues overall or with a specific kernel?

I only have issues in setVPU when i use it to change the CPU governer..when i do that my phone sometimes wont wake up after sleeping for a long period.

Other than that ill have it show min freq's and have to have it re auto-detect but thats about it. I dont think the app has been designed specifically for the vibrant and dont know when it may get updated.

I can put up a kernel that defaults at 1.2 Ghz like OC1.

I just saw unhelpful had implemented that to keep peoples phones running ok if they run into issues at 1.2 as on a reboot your back to 1Ghz unless you used setCPU to set on boot and thought it wasn't a bad idea.
[Vibrant Android Development] justanothercrowd:
btw are you going into setCPU and setting the OC as that needs to be done on this kernel. It defaults to 1.0Ghz on boot.

Your Linpack's should be in the 9's at least. I may put up another that defaults to 1.2Ghz automatically.

or in a terminal if you dont have setCPU

echo 1200000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq;
[Vibrant Android Development] zimphishmonger:
I was having issues w/ all your kernels, so its most likely overall. I'll probably add the terminal code to manually set it, for the time being. Im sure a lot of us would appreciate a version that clocks to 1.2ghz natively like OC1, but I understand your reasoning behind having it boot at 1ghz. Thanks for your work! Its much appreciated :D
[Vibrant Android Development] anomalous3:
Also, for those who don't want to run setCPU, this can be put in a script in init.d so you can avoid setCPU troubles.
[Vibrant Android Development] danielmid84:
I had Eugene's Vibrant6 ROM flashed and RyanZA's 2.3 lagfix applied, I flashed the vibinit.d, removed the 07d2sd script, and flashed the OC kernel then ran SetCPU and set to 1200mhz and touched no other settings. Linpack in the high 9's and this quadrant right after boot.
[Vibrant Android Development] ttabbal:
Hey JAC: I've been experimenting with the SetCPU issue. I think there's a kernel bug, possibly in the Samsung source. If you set scaling_max_freq lower than scaling_cur_freq, you get the crash. Seems to be reproducable on my phone using your v6 kernel. I haven't updated yet, I also haven't tested against the stock kernel. I wrote some scripts that run via Tasker's screen on/off events that wait for CPU speed to drop to or below the set value and have not seen any crashes after a couple days use.

Just something that might be worth checking into, maybe you can fix Samsung's bug. :)
[Vibrant Android Development] zimphishmonger:
From JAC's twitter:

Looks like we will have a wake lag fix and UV soon :D JAC is the man!
[Vibrant Android Development] anomalous3:
Any chance of getting HiMem included in the next version so we can make use of all 512MB of RAM?
[Vibrant Android Development] justanothercrowd:
I havent looked in to HiMem but i think it may be enabled already samsung just reserved a TON of mem for WiFi video capture etc. We may be able to adjust those amounts to get closer to the whole 512 instead of having it wasted. We have to be careful we dont break the camera Wifi etc.

Wake Lag fix coming up tonight. I'm working on compiling my own toolchain that is known th fix the wakelag and add some more optimizations for the cortex-a8 CPU.

Just got home and am about to get to it.
[Vibrant Android Development] MINUS Stl:
Hmmm..... Might have to set my alarm to wake up a little earlier tomorrow morning and flash a UV kernel. :D
[Vibrant Android Development] j_r0dd:
please uncomment Si4709_driver.ko from the init.rc
[Vibrant Android Development] justanothercrowd:
Wake lag is fixed. OC version available now. Stock clocks coming shortly.

Also the OC version reverts back to the default of overclocking to 1.2Ghz on boot. No needing to set with setCPU.
[Vibrant Android Development] rpesigan6:
yeahhh buddy !!
[Vibrant Android Development] ju5tiiv:
WOO HOO!!! No more wake lag! Great Job JAC! Thank You.

Quad Score: 2589

anomalous' rom and ext2
[Vibrant Android Development] justanothercrowd:
lol oh geez this was uncommented but the init.rc was prob rebuilt and i forgot to amend that change.

I'll have it done for you guys playing with the FM Radio.

Stock clocked Kernel is up with NO WAKE LAG. I would have had them up earlier but i wanted to personally build the toolchain.

EDIT: uncommented it for you in the stock Kernel i just put up. I'll fix it in the OC kernels later. Since the FM Radio isnt working now anyways there is no rush.
[Vibrant Android Development] rei165:
kudos to you! =)
[Vibrant Android Development] MINUS Stl:
JAC, I noticed the 2 "no lag" kernels don't have the ext4 in the filenames. Do they not take advantage of it?
[Vibrant Android Development] j_r0dd:
Thank you for that change to the init.rc for the stock kernel. Now I can hopefully get that fmradio working!!

Sent from my GalaxyS
[Vibrant Android Development] morfic:
I did the lag fix, moved things to mmcblk1p2 instead of the loop device. Mounted in userinit.sh.

What do I need to revert, what can I keep?

Moving userinit.sh to init.d/01userinit would be the least problem.

Did I miss something, I need to use odin? There is no kernel image I can flash from recovery?

I much prefer not touching windows tools.

Mt3g I just did everything I had to with adb, fastboot, recovery.

Is it not possible, or do I just have to crank up my google-fu?
[Vibrant Android Development] aloxotls:
My vibrant locks up when using the OC Kernel v3, is there still stability issues with this version? I am using Vibrant 6 with the modaco lag fix.

I flashed the non-OC v9 and I am having no issues. The no lag wake is awesome, thanks for all your hard work.
[Vibrant Android Development] darkoutsider:
Flashed it this morning. So far so good. Using Vibrant6 and RyanZ Lag fix. I noticed my Quadscores went down a bit (was 2700ish now down to 2200). Going to uninstall the lagfix and try without it, then reinstall.
[Vibrant Android Development] gehlersjr:
I to have been experiencing the same freeze issue as well. I overclocked with setcpu and for 24 hours of the same use I have yet to experience it again. Mostly the freeze occurs during typing. Initial thought was that it was issue with swype becoming unstable under overclock but still occurred using other keyboard options. I wish I knew more as to be able to read error reports, does this rom include logcat? Let me know what I can provide to help out in solving this issue.
[Vibrant Android Development] xalucardx:
I installed OC kernel and so far is running great with Vibrant6 and sugested lag fix , no wake lag and no freeze only I noticed if I set setcpu profiles when screen goes of then the phone freeze, but so far so good!
[Vibrant Android Development] Klyentel:
works

just installed ocv3 kernel wake lag fix no problem! First try and everything is speedy and working. One click on power button and screen comes alive almost instantaneously, :D

For those having problems getting stuck in Odin with zimage I suggest turning the phone off first, plug it to the usb, then turn on into download mode while odin is already open, should work no problem.

Linpack- 9.86

Quadrant- 1280
[Vibrant Android Development] justanothercrowd:
Not EVERYONES CPU will be able to handle the freq/voltage of the OC'd kernels. Phone A might be stable 24/7 at these settings and phone B may not.

This is because all CPU's are not created equal and the overhead you may be able to squeeze out of them is diff for every chip.

Now 1.2Ghz seems like the border line with a reasonably small voltage increase. I really dont want to increase the voltage much more due to reports of peoples radios dying etc. So I'm playing it safe. If your phone can't run stable with OCv3 I will MAYBE put up another with slightly higher voltage which should correct the freezes etc.

You have to understand you are using it at your own risk though. Right now I'm trying to get my UV'd kernel squared away because the same rule applies there.

On top of everything else the Hummingbird CPU is ALOT more sensitive to CPU Freq/Voltage changes compared to the snapdragon.
[Vibrant Android Development] j_r0dd:
just an fyi SCv9 looks like it lost ability for adb remounts

nvm. it looks like we can push away without remounting:D
[Vibrant Android Development] MINUS Stl:
Definitely looking forward to your UV kernel. Just flashed the no lag OC and works well. Although, the phone's already fast. Having the battery last even longer would be killer. :D
[Vibrant Android Development] ludachez:
help?

i am running JACs original OC kernel from earlier in the month...when i flash his new kernel over it using Odin, everything is screwy. my HTC ime mod FCs all day, and setcpu cant overclock or auto detect. should i revert back to stock and reflash everything?
[Vibrant Android Development] MTC44:
Incredible. Kept hanging on zimagine and it was driving me nuts. You made my life a lot easier, thanks!
[Vibrant Android Development] pshadey:
has anyone else had a issue with the phone going into a coma like state and not waking up, forcing me to pull the battery. i just flashed the OCv3 kernel thinking it would eliminate the issue, but unfortunately it hasn't. i have Eugene Vibrant6.zip rom, with jacs kernel ocv2&3 and the lag fix....does anyone have any ideas
[Vibrant Android Development] MINUS Stl:
Quick question...are you running SetCPU? If so, it should be set to 'conservative'.
[Vibrant Android Development] Goog1e Phone:
First time trying JAC's kernal (I was waiting for the WAKE UP fix) and so far so good. Stock rom + ext4 + SCv9. Quadrant is 1579 if that even matters. Overall, the phone feels a little snappier.
[Vibrant Android Development] rUsTyRuSs:
I'm running OCv3 kernel with Eugene's vibrant 6 + lag fix. I seem to have a problem when over clocking using set cpu to 100-1200. (no profiles and set to conservative set) My phone randomly freezes while under high cpu load. I downstep the settings to 100-1000 and i have not duplicated the freezes. Any ideas?
[Vibrant Android Development] Goog1e Phone:
Read a few posts back.
[Vibrant Android Development] rUsTyRuSs:
Got it. Thank you :)
[Vibrant Android Development] trusteelfan:
Is it just me? I do not see a link for OCv3.
[Vibrant Android Development] zimphishmonger:
Great info, thanks for letting us know. Def a rule of thumb for all undervolting and overclocking, not every CPU is identical. Very interesting to know how sensitive the Hummingbird CPU is to voltage change.

My results have been very positive so far. Running all day using OCv3 at 1.2Ghz, putting fairly heavy load on it all day, and no wake lag (INCREDIBLE!). no freezes, crashes, or "deep sleep comas" either. Thanks a lot!
[Vibrant Android Development] allareconnected:
Any reason why both launcher pro and now adw go into a force close loop after a restart?? -- love the speed btw, Ty jac!

I am running the oc no lag kernel with eugenes v6.
[Vibrant Android Development] Goog1e Phone:
I'm still on the fence with overclocking since my phone feels pretty snappy. But just wondering, do you notice any difference when overclocking to 1.2 ghz? Also, I don't really care too much about battery life, but I still wonder how much juice does it suck up compared to before? Any answers would be great. Thanks.

And especially thank you to you JAC!
[Vibrant Android Development] Goog1e Phone:
I'm using LP and I haven't had this issue yet using JAC's kernal.
[Vibrant Android Development] zimphishmonger:
As we are using the conservative CPU governer, which only clocks the cpu up in ~20% increments to handle load, it doesnt eat too much battery. Cant give you a percentage but its negligible. I do notice a difference, but its not night and day. Its a little snappier in games (esp. 3d games), but nothing incredible. I just like having a fast phone :cool: Im the same way with PCs
[Vibrant Android Development] vtecbros:
Do we really have to have a partition SD card? If so in What partition order?

Sent from my iPhone .5g
[Vibrant Android Development] jaysins:
So after benchmarking it seems that my cpu is definitely faster and all the benchmarks that deal solely with that have increased. However, any dealing with the gpu have seen a bit of a hit. My fps on neocore has gone down and my quardrant scores have gone down slightly even with the faster cpu speeds and I again, I'm assuming, it's the gpu. Anyone else have any thoughts on this? Running 1.3 no lag, vibrant 6 and ryan's 2.3 lagfix. Awesome kernel though Jac, thanks for all the work.