yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] suppliesidejesus:
UPDATE: Battery life with my 1300Mhz setting is pretty good. Dropped from 74% to 43% in 7 hours and 51 minutes with moderate use. I'm on EC01.

UPDATE 2: My phone has been shutting off while in sleep mode every once in a while, so I have upped the voltage for the 200 MHz step from 875mv to 900mv. I have adjusted my post below.

Hey all. I've been playing with this kernel for the last few days, and I think I've found some stable settings for 1300 MHz and 1400 MHz. As I'll show below, I based my uv settings on increasing voltage drops from step to step. The speeds shown in the field below are the steps I have selected:

[U]1300 MHz[/U]
1300 MHz || 1300mv (-25 from default)
1120 MHz || 1275mv (-25 from default) drops 25mv
1000 MHz || 1225mv (-50 from default) drops 50mv
800 MHz || 1175mv (-25 from default) drops 50mv
600 MHz || 1125mv (-50 from default) drops 50mv
400 MHz || 1000mv (-50 from default) drops 125mv
200 MHz || 900mv (-50 from default) drops 100mv

I've found these settings for 1300 MHz to be VERY stable. I don't use 100 MHz because I found that speed to cause tons of lockups. Haven't tested battery life yet, but my guess would be that it's pretty good. If your phone cannot seem to handle 1300 MHz, try 1200 MHz at the same voltage.

I also have some adjusted settings for 1400 MHz. See them below:

[U]1400 MHz (EDITED)[/U]
1400 MHz || 1375mv ( -0 from default)
1200 MHz || 1300mv ( -0 from default) drops 75mv
1000 MHz || 1225mv (-50 from default) drops 75mv
800 MHz || 1175mv (-25 from default) drops 50mv
600 MHz || 1125mv (-50 from default) drops 50mv
400 MHz || 1000mv (-50 from default) drops 125mv
200 MHz || 900mv (-50 from default) drops 100mv

These settings are beta, and the voltage drops are a little different, but it seems stable so far. I have been running them for a few hours without any lockups, but nothing for sure yet. NOTE: Not all phones can handle an OC to 1400 MHz.

Just thought I would share with the class! Feel free to play around with these voltages and the different steps.

EDIT: My phone did end up having a random shut down at 1400 MHz @ 1350mv. Since I don't want to cook the phone at 1375mv, I've reverted to my top voltage settings, with 1300 MHz as my max clock. I am convinced that 1400 MHz would be stable (for those that can use 1400 MHz at all) @ 1375mv, but like I said, I don't want to use my phone as a toaster.
[Fascinate Android Development] saps:
I'll let the pictures do the talking. Please note on the steps though not shown my 100Mhz voltage is the same as the 200Mhz.
[Fascinate Android Development] jrobinsky:
im running the same settings as SSJ and im stable so far at 1400!

I didn't take pics, I can but

Linpack-19.501

Smartbench 2011-1220

Quadrant-1882

Benchmark PI-993
[Fascinate Android Development] dalrym05:
My setjng are noop IO

100mhz -100mv

200mhz -75mv all the way through 1000mhz

Then I skip to 1400. Not undervolted. Very stable no issues. Yet.....
[Fascinate Android Development] dricacho:
After trying to push my phone to go to 1.3 and 1.4ghz while on the SF_OTB_OC_TW_1.4ghz_0409 kernel, it started locking up even after stepping back down to 1200 where my phone normally doesn't lock up at all. Tried different steps in clock and voltage, phone just locked up all the time. So now I'm back to SF_OTB_OC_TW_0407 kernel.
[Fascinate Android Development] nemesis2all:
Wiping cache and reflashing kernel may take care of that.
[Fascinate Android Development] ssewk2x:
Are the default voltages stock, or are some already slightly undervolted already?

Also, I can't seem to find stable settings for 1400 mhz. Bummer :(

When my phone doesn't lock up, everything seems to work fine, including bt, camera, wifi, gps, etc.
[Fascinate Android Development] saps:
They are stock for the mesmerize kernel source up to 1Ghz of course. Everything above 1Ghz cannot be stock per se. They are nem's values for sufficient voltage.

It seems to me if you could run 1.3 on eclair you can run 1.4 on froyo. Not an absolute rule but a general average of an extra 100Mhz over eclair. Those who could not run 1.2 on eclair also seem to be struggling with even 1.3 here
[Fascinate Android Development] onemotodroid:
Great work - i have learned so much about how my phone responses to voltage and freq changes

it can handle the higher freq but it does like like the 50mV drops in voltage

working on best setting for battery at higher freq

Please work on a kernel for AOSP - i would like to run cm6 and be able to change the freq and voltage settings
[Fascinate Android Development] scarmon25:
Some pretty next gen **** going on here. Great work to all thos that contributed to this kernel. I have mine set to max at 1200mhz. Using the same voltage settings as saps and so far no issues. Still waiting to see how batt life is but performance is rockin. Great work guys,
[Fascinate Android Development] ssewk2x:
My phone was rock solid on eclair running 1300mhz uv. I am currently trying out SSJ's settings and those seem ok so far.

My experience has been that this kernel would run fine for hours, then lock up, usually while doing haptic feedback and/or using facebook. Weird.

I'll be happy if these current settings prove stable - I have nice clock speed and respectable uv at least :)
[Fascinate Android Development] cbalt:
love this kernel just wish i could get it not to lockup on quadrant with 1400mhz. Any

plans of releasing one with more ov along

with 1600mhz? Im not worried about you

really turning up the ov and mhz wick with

having the ability to drop it at any time with voltage control. I think since it isnt my

phone i use for anything but play i dont

really care about pushing it to its limits and

beyond. I can be a ginea pig if u want to

add 1500 and 1600mhz steps with crazy

ov. Im not sure how hard that is for you

since ive never made a kernel or rom.
[Fascinate Android Development] beray5:
Signs of slightly too much uv, the first thing usually to be affected by uv is the I/O interface. Typically I/O are level shifted and first to be affected causing data corruption in writing data to destinations such as DBDATA, SDcard...
[Fascinate Android Development] dricacho:
Will give this a shot.
[Fascinate Android Development] scarmon25:
Just throwing this out there. I've been using the following settings and so far have been getting pretty good battery life and performance. Been on for about three hours with moderate to heavy use and still have 75% battery left. Which is slightly better than what I was getting on JT's latest Voodoo Kernel. I'm running the EC10 PnP v.4 ROM and this Kernel. So far this thing rocks.

Set Max OverClock to 1200 mhz

Settings for 1400 and 1300 made no changes as these steps are not enabled.

1200~1250mv -50mv from stock settings

1120~1250mv -50mv from stock settings

1000~1200mv -75mv from stock settings

800~1125mv -75mv from stock settings

600~1100mv -75mv from stock settings

400~950mv - 100mv from stock settings

200~850mv -100mv from stock settings

100~850mv -100mv from stock settings

Steps Enabled

1200 mhz

1120 mhz

1000 mhz

800 mhz

600 mhz

400 mhz

200 mhz

Edt: Got some of those values wrong. Read from wrong column.
[Fascinate Android Development] ssewk2x:
Yeah, that's what I thought, too. Until it locked up with no uv at all, lol.

Now I'm starting to think the 100 mhz state was the culprit since I've been running all day with SSJ's settings plus 1400 mhz at -25mv.

Gonna stay with this until it crashes and see what happens. I really love being able to fiddle with this stuff on my own, btw!
[Fascinate Android Development] beray5:
Yeah, lower states uv usually cause lockups, higher states uv usually cause data out corruptions.
[Fascinate Android Development] garywojdan81:
Is it common for this kernel to break root? I was getting some freezing today even after tweaking the voltage settings so I flashed back to the last kernel I had run, times_infinity's latest voodoo comavolt, and lost root. Got it back with z4 root though so I flashed back to this one using the red cwm package that was posted in this thread & all's well so I'm gonna try more tweaking.
[Fascinate Android Development] dricacho:
The first Fascinate that I had, before it fried, used to be able to handle 1.3 on OTBtest5ul1300-DJ05. My current one is stable at 1200 mhz but not 1300 or higher. I just take this as fact now, not all Fascinate can be stable at any given OC speed.
[Fascinate Android Development] TheSonicEmerald:
Random lockups at random times. Its usually after several hours too like 10+. Playing with voltages at 1.4ghz....
[Fascinate Android Development] bwheelies:
I am tempted to try this again. I was on Nameless V3 and I thought I had it going at 1.4GHz but then I realized you have to apply settings in Voltage Control and then it went down hill from there. Constant lock-ups. Tried 1.3 and it was a little better.

When the lock ups occur it seems to really mess with the phone to the point that I need to do an ODIN back to EB01 stock and start again.

Also, just in case anyone needs to flash something else or wants to retain the Red CWM, flash the kernel in Red CWM and before you reboot flash the CWM_330_FIX.zip or whatever it is called and then reboot. It retains Red CWM.
[Fascinate Android Development] durakbane:
For those getting a ton of lockups..while it is most likely that you are trying to undervolt/overclock too much, you may also want to try removing some of the steps/stages. I read on another forum that too many steps can jack up the phone as well. I reduced mine down to five (instead of 7) and I am able to undervolt a little more...still testing though.
[Fascinate Android Development] nemesis2all:
op updated
[Fascinate Android Development] scarmon25:
Flashed, No issues. Smooth as always. Great Work.
[Fascinate Android Development] DevinLeFevere:
Leaving as default and its running great! Thanks!

Edit: Running -25 UV
[Fascinate Android Development] tonu42:
I have no idea what happened, but I some how lost root?
[Fascinate Android Development] nemesis2all:
Reflash su zip. I do not have a link, but that should fix it.
[Fascinate Android Development] saps:
Nem how does 1.0b differ from the previous version? It too was 10 steps topped at 1.4 with it seems the same bells and whistles this one has???
[Fascinate Android Development] nemesis2all:
cwm3 has voodoo options, improved updater-script to hopefully handle mounting of system correctly. some other initramfs changes. 200-1000 only enabled as default to make it more stable. Battery hack from sirgatez, and couple of other little things.
[Fascinate Android Development] saps:
As always a masterful job. Luvin how personal we can take your awesome handi-work with our own individual top end's and uv profiles. No tunaboat for me. This kernel keeps me with the Fascinate for awhile longer and happily too.
[Fascinate Android Development] ssewk2x:
I also lost root, and was able to get it back by flashing the previous kernel. My cwm went from orange to red, too - what's with that?

Anyway, I'm happy again - it would be nice to know why some of us lose root and others don't, though.
[Fascinate Android Development] AuroEdge:
Been using these settings and haven't had any lockups yet. Seconded

Edit: Just kidding freeze galore!
[Fascinate Android Development] nemesis2all:
I would like to know as well. It is not an issue I have seen with 1.0b but I am on cm6 and aosp version. cwm is red now because of voodoo additions.

Edit: for some it could need a cache wipe and reflash of kernel. guid for root did change with this kernel. also could need to have su forget current settings and re add apps with root access. I cannot test it myself at the moment tho unless i switch back to touchwiz.
[Fascinate Android Development] ssewk2x:
On my phone, it appears the su binary is actually gone. There's a symlink in /system/xbin/su that points to a non-existing /sbin/su. I'm going to see if I can get it back somehow...
[Fascinate Android Development] fgvb:
I googled xda and su.zip. I downloaded su.zip and flashed it in cwm red (? the voodoo one ?). That seemed to take care of my root problem.
[Fascinate Android Development] nemesis2all:
If this problem persists I may start including su in the update zips.
[Fascinate Android Development] suppliesidejesus:
Hey all. If the 4/12 kernel breaks SU after flashing, flash this:

http://bit.ly/su2361ef

That will restore the SU binary and all of the correct symlinks.

BTW, one of JT's kernels did the same thing last week. Check in with him, he should have a fix.
[Fascinate Android Development] ssewk2x:
got root back

Based on what I've found out, I would definitely do that. It seems like this latest update.zip deletes /sbin/su. Here's how I have come to that conclusion:

1. Starting from the previous OTB kernel (which rocks, btw), opened terminal emulator and did the following:

# ls -l /sbin/su

(showed a binary with appropriate perms)

# ls -l /system/xbin/su

(showed a symlink to /sbin/su)

2. Reboot into recovery and flash the OTB 1.0b kernel from the updated OP. Tested root by opening voltage control app, which complained it couldn't get root access. Then I did the following (terminal emulator again):

$ ls -l /sbin/su

(file not found)

$ ls -l /system/xbin/su

(same symlink pointing to /sbin/su)

3. Reboot into recovery again and flash the old (test2) OTB kernel (same one I started with in step 1). Booted that kernel, and voltage control now has root, yay! Then (terminal emulator again):

# mount -o rw,remount /dev/block/stl9 /system

# rm /system/xbin/su

(removed the symlink)

# cp /sbin/su /system/xbin

(copied su binary into /system/xbin)

4. Reboot into recovery again and flashed 1.0b OTB kernel. On boot this time, voltage control (and presumably everything else) gets root, YAY! Just to verify, opened terminal emulator again:

# ls -l /system/xbin/su

(shows binary with appropriate perms)

# ls -l /sbin/su

(file not found)

# cp /system/xbin/su /sbin/su

(just in case, now it's in both places again)

So anyway .. yeah .. it's fairly conclusive that something about flashing the 1.0b OTB kernel is nuking /sbin/su. Others may not be losing root because they have (a copy of?) the actual su binary somewhere else that their system is falling back to, or whatever.

I hope that helps - maybe you can just include su in your zips, or find what's deleting it in this one?

Thanks!
[Fascinate Android Development] ssewk2x:
Keeping that on my sdcard for future reference.

Thank you, Jesus! (heh)
[Fascinate Android Development] suppliesidejesus:
I love when people thank me that way.

Makes me feel special.

It also makes me feel like I will meet an untimely death at the age of 30.
[Fascinate Android Development] nemesis2all:
In previous otb i had su in sbin with a custom script to handle that and other things. New mount wrapper and updates with cwm3 was wreaking havoc with it tho. If flashing su via that zip is fixing it i will be satisfied for now on the issue.
[Fascinate Android Development] CrucialBT:
I've been testing mine all day trying to find the appropriate uv for each step since my fascinate doesn't seem to be as butch as some of the others on here.

Here's what I got so far:

1200mhz = 0uv (Disabled)

1120mhz = 0uv (Disabled)

1000mhz = -50uv

800mhz = -50uv

600mhz = -50uv

400mhz = 0uv (I don't use as testing this one on stock speeds froze my phone)

200mhz = -75uv

100mhz = -100uv

I've had my test going for almost 30 minutes now without a problem. Previous attempts all crashed around 10-15 minutes in.

I plan to test the higher steps a little later, but I wanted to make sure I had the bottom steps covered so I was relatively sure it was the higher steps causing the problem.

Hope this helps some of you.
[Fascinate Android Development] ssewk2x:
My advice: disable 100 mhz and try again with the higher speeds.

Since I did that, I have 1400 enabled at -25mv and the rest at -50mv. Worth a try anyway. Good luck.
[Fascinate Android Development] garywojdan81:
Just flashed 4/12 kernel in red cwm after wiping cache & dalvik, reflashed cwm-all.zip & flashed ssj's su.zip(thanks man), all before booting. Caught a bootloop, so I pulled battery, rebooted & it came up but was really laggy. So I reentered recovery(red one, phew) from the power menu & fixed permissions & rebooted. Once up, everything was fine. Thanks for all the input on the uv settings. I went with:

1400

1300

1200

1000

800

400

200

All set for 50uv & so far stable after an hour.

Quadrant: 1883

Linpack: 19.346

Smartbench: 1405/3206

Update: 3hrs of constant use now & still no trouble...
[Fascinate Android Development] jkat797:
I've lost root. I flashed this many times, and have also flashed the su.zip given above . yet, I still don't have root access. I got it back by flashing my old.kernel but I would like to have this kernel. Can somebody please give me step by step help? I would really appreciate it. Thanks
[Fascinate Android Development] bmangia1:
Had that issue with JT's Kernel. This was a quick fix for me, "http://xdaforums.com/showthread.php?t=803682".
[Fascinate Android Development] xHoLyx:
1.4ghz

1.12ghz

1.0ghz

0.8ghz

0.6ghz

0.4ghz

0.2ghz

all set to -50uv

Running fine for 2 hours, will update.

EDIT: Locked up after 3hrs.
[Fascinate Android Development] exzacklyright:
I still don't really get all these steps nor how to test.. but after further testing maybe I'll try this :confused:
[Fascinate Android Development] suppliesidejesus:
1.4 does NOT respond well to uv. 1.3 does, however.

Sent from my Fascinate using the XDA app
[Fascinate Android Development] bwheelies:
Are you new to this stuff?

You have the kernel then the app which controls it called 'voltage control' in the market. Use the app to change settings and stress test it.

running on premium!
[Fascinate Android Development] beefdog:
Wow I cant belive my phone is doing 1.4 For more than 30 seconds
[Fascinate Android Development] saps:
Interestingly I've been playing around with 1.4Ghz and lower voltages. I can linpack all day with as low as 1300mv but I do freeze in quad and smart bench. 1325mv is the same. 1350 and 1375 are worse. My phone I guess prefers lower voltage. Still 1.4 isnt really stable enough for long term use so Im just topping it at 1.3
[Fascinate Android Development] jkat797:
Thanks ill try that out.
[Fascinate Android Development] ssewk2x:
Re: 1.4 ghz low voltage.

I had mine set at -50mv for this speed for a day or so with no problems...until I used the camera to scan a bar code, then it locked up. Seems to work fine at -25, though.

So I guess the moral of the story is try out all your apps before you consider your settings stable :)
[Fascinate Android Development] nemesis2all:
If anyone out there is still having issues with su I may have included wrong recovery binary. I also have pulled in some fixes from GizmoDroid. Changes need testing tho. So if you are having issues and feel like testing find me in irc.
[Fascinate Android Development] chrisexv6:
Question - is there a way to verify that Voltage Control is doing what its supposed to?

Ive manually applied the settings that SupplySide posted (thanks!), but was curious if there is a way to tell what the active CPU voltage really is.

Since Im not setting them on boot (yet), does Voltage Control need to be running in the background ?
[Fascinate Android Development] zeroxg4:
seconded. I'm sure it doesn't have to be left open, but I also applied the exact same settings for 1300Mhz that SSJ posted (and it's been working well) but I get Linpack's in the 14's.
[Fascinate Android Development] xHoLyx:
1400

1300

1200

1000

800

400

200

All set for 50uv

running fine for day w/o any lockup.
[Fascinate Android Development] CrucialBT:
Once you hit apply, I'm relatively sure that the app changes them on the fly. Then you can just back out of the app without a problem. The app does what it says though, so you don't HAVE to verify it. :) If you so choose you can download a different app to let you know what your current proc speed is. I downloaded an app called "Stability Test" from the market that showed me the current top speed. However, I find it failed at truly testing the "stability" of my current setup very well. It only really tests the stability of the top most step.
[Fascinate Android Development] nemesis2all:
from adb shell

cat /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
[Fascinate Android Development] chrisexv6:
Thanks for that, confirmed that it shows the same mV drops vs what is in Voltage Control.

For those trying this, note that it shows mV values for every step even if you arent using them, so the first mV value is for 1400 and the last is for 100.
[Fascinate Android Development] nemesis2all:
from adb shell

cat /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table

to check which steps are enabled same thing with 1400 to 100.

ex for 1000 to 200 enabled 1400,1300,1200,1120, and 100 disabled.

0 0 0 0 1 1 1 1 1 0

0 is disabled

1 is enabled
[Fascinate Android Development] uslacson1:
I've tried below settings since yesterday, I find it to be very stable.
[Fascinate Android Development] nemesis2all:
Have 1600 mhz testing. If testing goes well you all might be in for a treat.
[Fascinate Android Development] bwheelies:
If we can't get the 1400mhz to work, 1600 is out of the question, right?

Meaning, you haven't done anything else to the kernel to allow the higher frequencies?

I have finally gotten 1300mhz stable

Settings are

CFQ scheduler

1300Mhz Limit

States

1300-0

1120-0

1000-25

600-25

200-25

Has been like a rock. I purposely open and close applications multiple times and get the camera going, music, browser....anything that can slow the system down. This setup has worked well.
[Fascinate Android Development] nemesis2all:
Who knows, volts and other things are different. SSJ hit 1500 on it.
[Fascinate Android Development] Jmatch:
My phone is unusually cold like 64°F or like 20 C its never been.like this... I like
[Fascinate Android Development] kuronosan:
Stable at 1300Mhz. Not going to try 1400 yet and 1600 is out of the question for now. I don't even go lower than 400Mhz.
[Fascinate Android Development] syborg:
ugh...having brain cramps. I used to know but can't think right now...what does OTB stand for?
[Fascinate Android Development] xHoLyx:
OTB = Only the Brave
[Fascinate Android Development] vicous707:
i got 1400 -25 w.e on my mesmerize cant wait for 1600!!!!!! GIMMIE GIMMIE also thanks for ur hard work!
[Fascinate Android Development] Domush:
Why, oh why, does a kernel contain an (as of yet) unsupported CWM.. or any CWM at all.. being a kernel and all?

Why not simply package the CWM3 separately, in a different thread, so those of us trying to flash ROMs don't get stuck in a CWM loop of death, because we can't flash an old CWM, because it uses Amend scripts and we can't flash even the newest EC01 ROM because it isn't Edify yet.

Sucks we have to go through these hassles just for a kernel. At the very least, include a CWM2 version. Though, a kernel should never include a recovery, just as a recovery should not include a kernel.
[Fascinate Android Development] bwheelies:
You can flash the cwm_recovery_zip via sgs kernel flasher(market app) to switch back to 2.5.1.x cwm. You can also flash that same zip after flashing the kernel before rebooting and it retains the old clockwork.

I am for the new clockwork. Everyone just needs to implement it so we can use the new and improved version(s).

running on premium!
[Fascinate Android Development] nemesis2all:
As of right now 1600 is up and running. For those complaining about cwm3, odin cwm2.5 or whatever other method you choose. Another thing is you can extract the zip and remove one line from updater-script and it will not flash recovery. I always want the latest stuff and since I make kernels for myself and choose to share them with everyone else this is how they end up. If you think it is too many hoops to go thru build your own or use something else.

Current steps in 1600 I am testing

1600 - new step

1500 - new step

1400

1300

1200

1120

1000

900 - new step

800

600

400

200

100

There are some voltage changes as well.

Oh Yeah it looks nice in Voltage Control.
[Fascinate Android Development] beray5:
Here you go.