yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] krispuniq:
I had this issue when I upgraded to 1.6 OTB on commRom 2.0. I just did a boot into Recovery, disabled 100MHz & re-Enabled it. reboot system & set the scheduler to BFQ. That solved the problem for me.

hope this helps u
[Fascinate Android Development] drnihili:
Hmmm, no luck with that so far. I'll let it sit overnight and see if things are better in the morning.
[Fascinate Android Development] Izeltokatl:
dont bother with 100mhz it draws the same voltage as 200mhz, hence why all the kernels have it disabled from the get go.
[Fascinate Android Development] PeterGunz:
Any fans of OTB 1.2 find 1.6 stable?

I might give it a run after work tomorrow. So far 1.2 has remained the best for me.
[Fascinate Android Development] mengineer:
Been running it on UKB since nem released it other day. Battery life and performance are great, no shock there, haven't had a single problem. I'm not OCing just UVed 25-75 mv on 100-1000mhz, I use my Xoom if I need better performance anyways so never bothered with OC. So if you're going to OC maybe someone else will chime in on how that's going for them.
[Fascinate Android Development] nemesis2all:
Teaser shots of .35 cm7 kernel. My phone has never been able to complete quad at 1300 Mhz. On this .35 kernel I can complete quads at 1400, which is the highest freq. at the moment.

http://dl.dropbox.com/u/17898921/cpu.png

http://dl.dropbox.com/u/17898921/linpack.png

http://dl.dropbox.com/u/17898921/quadsa.png
[Fascinate Android Development] saps:
Its close but 1.2 for me is still the most stable in terms of OC, so yes I'm still on it. 1.6 is close though just get more freeze on it with the same voltage profile I can run 1.2 trouble free at 1.3 ghz all day long

Including infinite quadrant loops you name.
[Fascinate Android Development] saps:
Wow nice report there. I'm stable at 1.3 ghz and can linpack at 1.4 ghz but not complete a quad. Very encouraging stuff nemesis. Keep dominating!!!!
[Fascinate Android Development] drnihili:
Nope, still not working. I'm getting some odd behavior from Voltage Control though. If I tell it to write settings for boot and then I have it remove them, it says that there is nothing to remove. I checked in init.d and the only thing I see is

#set 100MHz on boot

So it looks like there's an issue with either CWM or Voltage Control not really enabling the setting.

Ideas?
[Fascinate Android Development] garywojdan81:
Are you on the older voltage control that's packaged in comrom or the updated "lite" version? The packaged version is the only one that works reliably for me with any of the otb kernels.
[Fascinate Android Development] drnihili:
I believe I'm on the one from comrom. It reports as 3.0.3.
[Fascinate Android Development] saps:
Wilshyre, great info. I've never used tegrak before but will definitely try it now. Thanks for the knowledge
[Fascinate Android Development] wilshyre:
Saps, tegrak overclock ultimate is definitely worth it. Unfortunately, to tune the "internal" voltage and "core" voltage with overvolting support, you have to buy the paid app, but someone had mentioned this a while back and I thought that tweaking and slightly raising internal voltage might help, and it damn sure did. Like I said, now I can overclock 300mhz faster on otb 1.6 than before. But the free edition does not allow overvolting, which is what enables you to raise internal voltage where needed for higher overclocking stability. But I think the ultimate is only 1.99, and its good to support the dev that allows our phones to gain so much performance, and overclock by another .3 ghz

Sent by way of unspeakably black magic.
[Fascinate Android Development] ssewk2x:
I've been using OTB kernels all along. 1.6 seems to be the best yet in terms of stability. And holy sh!t, my battery lasts forever now!

I'm OC to 1400 mhz, Uv is -25 above 1000 mhz, and -50 on the rest. Quad always completes, and I haven't seen a crash in a long time. I have most of the states enabled as well, only 1500 and 100 are disabled. Cfq scheduler, conservative governor.

Solid like a brick.
[Fascinate Android Development] akellar:
So I know there are some issues with having to reboot to get steps to enable correctly. Is there a way to check to see if voltage settings are actually changing or if you need to reboot to get those to activate as well?
[Fascinate Android Development] saps:
Am I correct to say that tegrak overrides the voltages of voltage control? So lets say I need to increase internal voltage for the 1400 step, when I go in there it seems like I'm going to have to change all the voltage steps is this correct?
[Fascinate Android Development] PeterGunz:
Also very interested in this.

Please please please (if you feel like it) post your experiences with Tegrak Ultimate if you go forward with it.

I would love to make OTB 1.6 act similarly to 1.2 (which we both seem to have the most success with).

Edit: Went ahead and got ultimate...not exactly sure what I am doing. Might need a tutorial. Searching for one now.
[Fascinate Android Development] speedingcheetah:
Battery charging

Not sure if this is has to do with the kernel or comm rom 2.0, but I have noticed that before, when I was running com rom 1.3 and otb 1.5, I could have the phone plugged into the charger all night and it would stay fully charged at 100% no matter how long it was plugged in....

Now with the new rom and kernel, it does not do that..i woke up today to 97% and after only a few minutes it was down to 85% (btw, i have the Sedieo 3000mah battery).

Anyone else notice this? If its a kernel thing, where can I download a otb 1.5, I don't want to re-flash the whole rom again just for the kernel.
[Fascinate Android Development] beray5:
If OTB v1.2 was the best for you...

Set Internal Voltage (droop compensation) to 1150mV for 400000-15000000 freq slots, 1100mV for 100000-200000 freq slots (Samsung default way over compensating the lower slots for worst case hardware).
[Fascinate Android Development] PeterGunz:
Thank you for that information. Before I try it I have a stupid question (yes, they exist), I use Tegrak in conjunction with voltage control, correct? I don't get rid of VC because, like Saps asked, I'm curious if Tegrak overrides VC.
[Fascinate Android Development] beray5:
Sorry, I had not use Tegrak since version 0.1.6.0 and can't help you there.
[Fascinate Android Development] wilshyre:
Saps,

Use tegrak only to change voltage settings. Leave voltage settings in voltage control app alone completely, because tegrak WILL override the voltage settings as long as you do not change the voltage settings from stock in voltage control app. Use voltage control to enable the overclock steps you want and change scheduler only, and then I recommend just hitting "apply" several times, as it seems to take 2 or 3 times of hitting apply before it actually applies for me.. but do not enable those settings at boot because the overclock frequencies will kick in at boot before tegrak voltage settings do, because tegrak makes you confirm those settings at boot before applying them for safety reasons, so enabling those extra steps at boot in voltage control would freeze my phone up because my phone won't handle anything above 1200mhz im otb 1.6 without first changing internal voltage settings in tegrak to be higher.

This is just my experience and how I got tegrak to work for my phone, as well as how I got my phone to handle the higher overclock steps enabled in otb 1.6. I hope it helps.

Sent by way of unspeakably black magic.
[Fascinate Android Development] wilshyre:
Do you mean 1000mv for 100mhz and 200mhz steps for internal voltage? As thats what is stock for 100-200 in otb 1.6, and it works just fine, so I see no reason why you would up the voltage for those steps when they work fine at 1000mv instead of 1100mv.

Sent by way of unspeakably black magic.
[Fascinate Android Development] PeterGunz:
You are the man. I'm going to give this a shot right now and then report back.
[Fascinate Android Development] beray5:
For droop voltage compensation (Internal Voltage for new generation techies), the greater the Internal Voltage the less droop compensation, the smaller the Internal Voltage the greater the droop compensation.

Nominal voltage of 1300mV and Internal Voltage of 1100mV = 2dB droop voltage compensation.

Nominal voltage of 1300mV and Internal voltage of 1000mV = 3dB droop voltage compensation.
[Fascinate Android Development] wilshyre:
Yeah, i'll admit I don't know all the details about all that, I just know that a higher internal voltage on the higher steps makes them more stable and able to use for me.

But, if internal voltage is the exact same thing as droop compensation, then how is it that a higher internal voltage means less droop compensation, and vice versa? Or is it more so that internal voltage directly correlates with droop compensation so that the higher you set internal voltage, the lower droop compensation you have, and the lower the internal voltage, the higher droop compensation you have? Honestly I don't know, as I dont know what droop compensation is exactly, so im not trying to contradict you or anything, as my knowlegde is limited at best in these matters. Does that mean that the larger the difference in core voltage and internal voltage you have, the more the droop compensation, and the smaller the difference you have between core and internal voltages, the less droop compensation you have? So does that mean that if you have your 200 mhz step set to 1000mv internal voltage and 1000 mv core voltage, the droop compensation is non-existent?

Sent by way of unspeakably black magic.
[Fascinate Android Development] beray5:
Start with nemesis2all post #597 -> http://xdaforums.com/showthread.php?p=13374554#post13374554 and follow through a few pages.
[Fascinate Android Development] PeterGunz:
Here is my overview of what I have experienced thus far:

Did exactly as you said. Weird thing, Tegrak would force close each time I would apply a voltage change, but when i would reboot it claimed the change remained. So, I got through all the internal voltage changes and then went to do core voltage changes, same thing happened.

So far so good. I'll update if this works out.
[Fascinate Android Development] wilshyre:
Hmm, I havent had tegrak force close on me for changing voltages at all.. do you have boot settings saved in voltage control or something? If so, perhaps you should use voltage control app to remove boot settings, or even use recovery under advanced menu to remove voltage settings.. might not help, but maybe it will.

Sent by way of unspeakably black magic.
[Fascinate Android Development] Izeltokatl:
Maybe a stupid question, but I noticed this kernel has the "Ext4 formatter" implemented into it. Does that mean once i've flashed the kernel the big 4 sections have all been formatted to ext4? Or do I have to manually apply them within the kernel?

thanks in advanced!

i assume this formatter is basically like:

http://xdaforums.com/showthread.php?t=1090127

which does it all in one shot.
[Fascinate Android Development] tripacer99:
Voltage control has been acting pretty strange recently. Before comrom 2.0 came out, I was having random system halts and SoD's. Voltage control was reporting normal UV levels (I use 200-1000 MHz, -75 for 200-600, -50 for 800 & 1000). After flashing the comrom 2.0 & OTB 1.5 kernel bundle, I checked voltage control and saw that my UV for 200 MHz had been set to -175, which is nowhere near the -75 that I always have it at.

The past few days, I started getting system halts again. VC told me everything was normal...flashed 1.6 a few minutes ago and checked VC again, and turns out my 400 MHz UV was at -175. Again. I don't know why this keeps happening. After I set my voltages, I don't touch them.
[Fascinate Android Development] akellar:
I wondered this too. Also does it wipe everything like the ext formatter in the other thread?
[Fascinate Android Development] scarmon25:
From what I have seen in order to get it to convert the four parts, system,cache,data, and dbdata you disable then reenable lagfix. I did this on my wifes phone with no data loss.

Tap-a-Talked
[Fascinate Android Development] Eris _2.1_2010:
Awesome work nemesis2all!!! Does startup sound work with 1.6?
[Fascinate Android Development] drnihili:
I'm having similar issues. In general it seems that changes made in Voltage Control aren't actually being implemented in the system. So, whenever VC gets data from the system (e.g. on reboot) it resets to previous values.

On my phone 200mhz is the most commonly used state. So I disabled 200mhs in VC, reset the timers in CPU Spy, and guess what, 200mhz is still the most common state. I think that VC is actually having no effect at all on my phone, though I don't know how to independently check voltage levels.

CommRom 2.0, OTB 1.6, VC 3.0.3
[Fascinate Android Development] scarmon25:
There is a command that can be entered into terminal emulator or adb that tells what the votage states are and such. I don't know what it is right off but it was mentioned in the thread somewhere. As far as the voltage settings part. I have not had this issue. Mine has stayed at what I set it at. I will look for the command or if someone else knows it please share as I would like to test this as well.

Tap-a-Talked
[Fascinate Android Development] garywojdan81:
Are you using the app packaged in comrom or the "lite" update for it from the market. For me, only the packaged one works.
[Fascinate Android Development] drnihili:
I'm using the CommRom one, 3.0.3.

I'll try ferreting the apk from the ROM and reinstalling it to see if that helps.
[Fascinate Android Development] tripacer99:
Would you mind posting it if you find it? I think i'll give that version another shot.
[Fascinate Android Development] beray5:
Everyone with VC not working properly, seemingly not able to change anything, the problem starts with 3.2.0.0 recovery not working correctly.

Use this one -> nemesis2all's OTB CWM3 Recovery v3.0.2.8x.OTBv2 -> http://www.multiupload.com/8VDE8GX69P , and make sure you reset voltages in the advance sub menu within the recovery, also use the built-in VC which came with the rom.

If still needed also USE reset WITHIN VC on first use afterward.
[Fascinate Android Development] saps:
Well, well, well. Tegrak FTW.

Who knew all it took was a little extra internal voltage to stabilize this OC.

For the record with OTB 1.2 and its mini internal boost I was able to run Linpack at 1.4Ghz but could not complete a quad. So upping the internal to 1150mv and boom, ran like 15 quads in a row just because I could. Then seeing Wilshyre's advice I said what the heck lets try 1.5Ghz. Sure as sugar it works. I am at 1400mv core and 1175mv internal. As of now I ran multiple linpacks and quads just for the obligatory bench shots. Then I did some real world testing like the camera and gallery which often freeze on a borderline OC and extensively used the browser and xda app. Some games and it seems stable for the most part. I will admit I had a freeze once I don't recall what the circumstances were but overall I would almost say 1.5Ghz is useable and stable. I might need an extra 25mv on either core or internal but Im already kinda nervous being at 1400mv and 1175mv respectively.

Now here is one thing someone else commented on. Using Tegrak, I first tried changing the 1400Mhz step and once I made a change the app would essentially hang. I wonder if this is what others were referencing. My only solution was to it the home key which did work, then go to task manager and end the app. Returning to the app however the changes I made did take. However, using the 1500Mhz, the top step of the OTB 1.6, I can make changes to that step and hitting apply gives me the same haptic buzz we get when we load the module and its instant.

So here is my question. I set my top step at either 1400 or 1500mhz, I then have my next step at 1000Mhz. I have Voltage Control to boot with a 1200Mhz top step. After a reboot I go into Tegrak and replace the top step of 1200 with either 1400 or 1500, second step is always 1000. But what Im wondering is if I change only this top step in Tegrak and don't change any of the other steps in Tegrak will it still use the respective UV voltages I have set in Voltage Control? Or do I have to manually adjust each and every step in Tegrak?

Oh and here is the proof in the pudding of my 1.5Ghz OC
[Fascinate Android Development] beray5:
Its basically had to do with LLC (load line calibration), you're manually guesstimating and establishing a load line calibration curve for each at various preset voltage levels.

Too much or too little droop compensation both caused ripples in your voltage load line.

Automatic LLC does all this and fill in the numbers for you automatically. Your Fascinate does not have automatic LLC period, not likely Tegrak would do it for you currently, wait for updated versions.

Typically you only need a single calibration load line, the cal would be used everywhere with an additional +1dB at bottom freqs and lowest voltage presets, preventing transistors low forward transconductance causing failures.
[Fascinate Android Development] saps:
beray5 frankly everything you said is a bit above my head but thanks for trying to explain it to me. Bottom line appears to be Im fine at stable and at the end of the day I suppose thats all that matters to me.
[Fascinate Android Development] bdubbin:
Using Saps core & internal values, I'm running 1.5 pretty stable. Thx dude!

Question, I have the latest miui & seems that the only way I can run above 1ghz by using voltage controls/tegak performance setting for throttle... conservative throttle won't let me go above 1ghz & all other throttle modes instalock... Anyone experiencing this or know what's wrong?
[Fascinate Android Development] saps:
Yeah what a goldmine Tegrak's internal voltage are. I never imagined 1.4 was possible on my phone stable let alone 1.5. The .35kernel nemesis built for CM7 seems to be an even better OC'er than anything he made for Froyo via OTB series. He's stable at 1.4 with it whereas before he wasn't stable on Froyo with 1.3. Good times.

Sadly, I don't use miui so I cannot help you there.
[Fascinate Android Development] beray5:
OTB's kernels had been this way for many versions, except for conservative I don't think other modes are fully implemented and do very oddball things.
[Fascinate Android Development] beray5:
Once you've found your optimal droop compensation value. The next thing you can do is lowering your preset voltages.

You should be able to use -100 for 100000-600000 freq slots without problem, enable greater power saving and less power loss on idle.
[Fascinate Android Development] saps:
Lower these values in Voltage Control or Tegrak? Are you talking cpu core voltage or internal voltage?

It probably goes without saying that yes I use an undervolt on my steps for the cpu voltage. -100mv at 100,200 and 400, -50 at 800 and 1000. That's in Voltage Control. But I don't touch anything in Tegrak except the 1500 step. I suppose this returns me to my question of by changing only that one step in Tegrak are all my other settings in Voltage Control still as I set them there? Because in Tegrak it shows the default values for the kernel and not what I set in voltage control.
[Fascinate Android Development] beray5:
Droop Voltage = Internal Voltage.

OTB v1.6 default voltages.

I suggest

-100 for 100000-600000

-75 for 800000

-50 for 1000000

"Too much or too little droop compensation both caused ripples in your voltage load line."

Without ripples you can use more uv.
[Fascinate Android Development] PeterGunz:
That was me that commented on the "hang". If you wait for about a minute and hit the back key, Tegrak should force close. I am going to try your method, as I assume it will speed the process up.

Only problem I had was when I saved the settings on boot. Tegrak asks for confirmation, and then hangs. Once I get past the hang, the setting are not applied.

I am trying again in a second. I have never been able to hit 1300. Here is my plan if I try (I think):

1300 Core: 0 Internal: 1175

1000 Core: -25 Internal: 1150

800 Core: -50 Internal: 1150

400 Core: -75 Internal: 1150

200 Core: -100 Internal: 1100

Why did I get rid of 600? nemesis did this as a default on one of the OTB's and it seemed to help with stability so I have done it ever since.

Saps, I may also try what you did. Leave everything alone but adjust the internal voltage of the top step only.

Another question I have, like Saps does, where is it best to set the Core settings? For this attempt, I will try and do it all from Tegrak even though the hang after applying settings is annoying.
[Fascinate Android Development] drnihili:
Still not working.

One clue may be that when I hit reset within VC, I get a response of "not implemented yet".
[Fascinate Android Development] saps:
Peter you shouldn't need more than 1150 internal to stabilize 1300mhz. Heck I'm using 1150 internal for 1400 mhz, but yeah good luck. Tegrak has certainly given most people the ability to reach higher OCs
[Fascinate Android Development] PeterGunz:
Update: Phone is flying. I think Tegrak is overriding Voltage control, Saps. Only because my phone is not using much battery on idle. No freezes on gallery or camera.

I normally can't be on 1300 for even 3 seconds without a lock, so this is what I did.

1. Recovery, wiped voltage settings.

2. Went into Tegrak, made all my changes that I indicated I would in my last post.

2b. Used the Saps trick of task manager to speed through each hang.

3. Opened voltage control and enabled steps I want to use

4. Kept default deadline and conservative settings, then moved the slider over and applied.

5. Awesome.

Now I need to figure out how to have this all applied at boot. Any tips Saps? You seem to hang like my phone does.
[Fascinate Android Development] beray5:
You need to find your optimal droop compensation value (Internal Voltage), typically this value is the same for all preset core voltages with small exception for transconductance consideration.

Don't bother with changing other freq slots being too time consuming, simply try for just one such as 13000000, simply step through from 1100mv-1300mv, one 25mV step at a time. You already said at default you can't do 13000000, as you step up Internal Voltage it'll become more stable, when you go too far it will be unstable again.

"Too much or too little droop compensation both caused ripples in your voltage load line."

Use Tegrak for Internal Voltage, use Voltage Control for others.
[Fascinate Android Development] PeterGunz:
Okay, I'll give that a shot. Only reason I went to 1175 like you did for 1500, was because I can normally never be on 1300 for more than 3 seconds.

Is too much dangerous? Or should I say, what is the downside?
[Fascinate Android Development] beray5:
NO. not at all...
[Fascinate Android Development] PeterGunz:
Great, so what I'll try next time I reboot is this to keep everything normal and adjust the cores of everything in tegrak but the internal only of 1300 and test stability.
[Fascinate Android Development] PeterGunz:
Haha, I mean I know way too much is probably bad. I was just wondering if it isn't locking at 1175, then should I be worried.
[Fascinate Android Development] beray5:
There's also consideration of worst case hardware. You may have to step down instead of stepping up your Internal Voltage. But it'll still work out the same in the end.
[Fascinate Android Development] beray5:
Nothing to worried about period. :)
[Fascinate Android Development] PeterGunz:
This is great help. Thank you. I'll keep tinkering and see what happens, but so far this thing is flying with the settings I posted earlier.
[Fascinate Android Development] drnihili:
Here it is. I have no idea if this is all that's needed or if installing it will bork your phone. But it's the apk from CommRom2.0 OTB. I tried to install it, but haven't yet figured out how to get the current one uninstalled. I figure if I screw something up I can always just start over from scratch.