yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] scarmon25:
Noticed these changes right off. I'm sure there is more.

Removed 1500mhz step

Added back 1120mhz step

Edt: Also. Does this include the BFQ v2 that was mentioned before?

Tap-a-Talked.
[Fascinate Android Development] quadracin42:
How do you enable 100 mhz?

Thanks
[Fascinate Android Development] kidserious:
If you check out his recent commits on his git I believe it says he added the v2 bfq support. And I believe it's the 1600 MHz step that he removed as well as the 1120 and the 900.

Sent from a depraved XDA junkie and flashaholic
[Fascinate Android Development] kidserious:
Via cwm recovery. Under advanced in main menu.

Sent from a depraved XDA junkie and flashaholic
[Fascinate Android Development] scarmon25:
Yeah, the 900,1500,1600 mhz steps are no longer in it. I'm at work and unfortunately the websense on these PC's blocks out github and related sites. Kinda surprised it doesn't block out XDA. I'll have to check it out when I get home. Doesn't really matter though cause even the BFQ v2 doesn't play nice with my phone. No biggie as it runs superurb on the CFQ anyways. Just wanted to know mainly to see if it made a difference between v1 and v2. Thanks for the info.
[Fascinate Android Development] kidserious:
My version of the OTB 1.5 GB has the 1500 step in it. What has been removed in mine is the 900, 1120 and the 1600 steps.
[Fascinate Android Development] scarmon25:
That was how mine was when I was on the one nevenedrob first put together. The one he just put out today is different for me anyway.

Tap-a-Talked
[Fascinate Android Development] kidserious:
You're running the TW version huh?

Sent from a depraved XDA junkie and flashaholic
[Fascinate Android Development] scarmon25:
Yeah.

Tap-a-Talked
[Fascinate Android Development] scarmon25:
Tap-a-Talked
[Fascinate Android Development] scarmon25:
The one posted here

Tap-a-Talked
[Fascinate Android Development] scarmon25:
This was asked of me and don't feel any reason why I shouldn't fill the request.

I guess I should have put in this is from user. Yoonee

Tap-a-Talked
[Fascinate Android Development] CHANGiism:
Same for me. I just flashed the latest that Navendrob built for us and I noticed that scheduler is back to SIO and 1120 is back. 1600 and 1500 is removed. I feel like I'm back to 1.4 or something........
[Fascinate Android Development] scarmon25:
I honestly never got mine higher then 1300 mhz. So these changes don't effect me the same as others that were able to go higher. The biggest difference I see is it seems to be more stable when doing certain task. For example downloading. On previous versions the phone would become laggy at the end of a download. It hasn't done that on this one. As always not complaining. Just my observation.

Tap-a-Talked
[Fascinate Android Development] kidserious:
Interesting..... the GB kernel is different.

Sent from a depraved XDA junkie and flashaholic
[Fascinate Android Development] scarmon25:
Hell I though you were on the TW. LoL. I was begining to think I was flippin out :)

Tap-a-Talked
[Fascinate Android Development] kidserious:
Lol, no I'm running Jt's CM7. getting some serious undervoltage with a 1.3 oc as well.

Sent from a depraved XDA junkie and flashaholic
[Fascinate Android Development] scarmon25:
Mine will run at 1.3 but I don't see a difference between that and 1.2 performane wise on my phone. I've been running the same settings since 1.3 and I honestly have become content with it. She performs the way I like it. I can tell ya though. Recently did the whole go back to stock and then flash the setup I wanted. I didn't realize just how much that voodoo lagfix and OC did. I mean wow. Like night and day.

Tap-a-Talked
[Fascinate Android Development] kidserious:
Yea, sometimes you need a reference point just to see how awesome these custom kernels make our phones. It really allows you to see stock for what it is and all it's suckage. Lol

Sent from a depraved XDA junkie and flashaholic
[Fascinate Android Development] ssewk2x:
Oh yeah! My wife recently got a fascinate and after using it for a few minutes in stock configuration, she insisted that I "fix it" to "be like yours," lol. It's just about unusable the way vzw sells it, imo.
[Fascinate Android Development] scarmon25:
I would have to agree. A guy at work has the facinate and after using my phone for a few minutes was like damn. What did you do to yours? A couple flashing sessions later and now he actually likes his phone thanks to this and other kernels. Nemmises really has a good thing going here. I have tried all of the kernels released. JT's. Imnuts and Times Infinity. All have the pros and cons buf the OTB just plain out rocks and when you have to mess with a stock phone mesmerize or fascinate you really start to appreciate these great kernels. It is truely amazing. Anywho. So far this one seems to be the most stable on my phone I've tried. When ever theres one released it goes on mine and my wifes phone and neither of us have had any issues so far. Great work.

Tap-a-Talked
[Fascinate Android Development] DigitalDementia:
What's the latest OTB? I thought there was a 1.4? I know community rom uses it. Anyone know where I can find this?
[Fascinate Android Development] scarmon25:
Another user put together 1.5 using nemessis latest updates on github I believe. He posted a link a few post back. I figure nem has been busy with other things and such so navendrob was nice enough to put this together. Thanks man. Anywho. Try it out. It seems a little more stable on mine although your results may vary. :)

Tap-a-Talked
[Fascinate Android Development] AuroEdge:
I installed this over stock ED03. Everything seems great. Only problem I am having is that it's showing the verizon boot animation with the green android letters over it sideways. Anyway to eliminate this?
[Fascinate Android Development] sfobrien:
Just installed the latest 1.5. Quick question, what are you guys setting the limit clock to? I'm trying the below settings I found a few posts back as my first trial run with this kernel.

(scheduler: deadline)

1200Mhz @ -25mV

1000/800Mhz @ -50mV

600/400 Mhz @ -75mV

200/100Mhz -100mV
[Fascinate Android Development] kidserious:
The clock limit should correspond with your highest used step. So, in looking at your settings, you need to set the clock limit to 1200.
[Fascinate Android Development] sfobrien:
Great thanks. I've never set anything higher than 1000 before so wasn't sure. I adjusted it to correspond. So far the new kernel is doing real well with these settings.
[Fascinate Android Development] kidserious:
Well then, let me be the first to welcome you to the world of overclocking lol.
[Fascinate Android Development] Skrazz:
I just flashed a new boot animation in CWM. You can find them HERE
[Fascinate Android Development] sfobrien:
Hey glad to be here, little late to the party but I'm here!
[Fascinate Android Development] vdelsan:
first of all awesome kernel keep up the great work but what is the best battery and stability settings on 1200 thanks
[Fascinate Android Development] AuroEdge:
It is difficult to troubleshoot stability when undervolting since you can be right on the borderline of problems and hardly ever cross it. But when you do you incur freezes and/or corruption. I have these steps as a compromise:

1200: Stock

1000: -50

800: -50

600: -50

400: -50

200: -50

100: -50

Rule of thumb I follow is your voltages from low to high clock speeds should be the same or increasing
[Fascinate Android Development] Chewy1576:
For some reason, I'm losing my Voltage Control settings after a reboot. Either it isn't saving my settings or isn't reading them properly after rebooting. I'm running the latest OTB 1.5 kernel and ComRom 1.3.

EDIT: I determined that VC isn't saving my settings. After pushing "Save as boot settings", I push "Remove boot settings" and a warning pops up that says no settings were found.

EDIT #2: I reflashed ComRom 1.3 and kept OTB 1.4 that came in the zip. Save settings works now.
[Fascinate Android Development] drumtrucker:
phone was working pretty well on 1.5 (with NO settings changed), but when disconnecting from PC, the PC would BSOD. I went back to 1.3 and tried once and it did not BSOD.

What I liked about the kernel is that this problem:

http://xdaforums.com/showthread.php?p=10253144#post10253144

was FINALLY solved in conjunction with:

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

I haven't confirmed that this is still the case with 1.3, will try tomorrow.
[Fascinate Android Development] King Mustard:
How do I install this kernel?

I've moved it to the root of the SD card and booted into Samsung Recovery Utils - but there is no option to install a custom zip.

I can never appear to get ClockworkMod to successfully work on the Mesmerize.

Any ideas?
[Fascinate Android Development] AuroEdge:
I do not know why v1.5 is not in the original post. I must say that it is working quite well and have not had an issue on Community ROM v1.3. Battery is lasting my all day on light usage in an area with sparse coverage
[Fascinate Android Development] jman2020:
can you install a kernel with stock recovery or do you need CWM?
[Fascinate Android Development] mellen_hed:
You need cwm
[Fascinate Android Development] fortesquieu:
Where did you get 1.5 from?
[Fascinate Android Development] jpricesd:
Someone posted a link back on page 70. Here ya go http://xdaforums.com/showpost.php?p=13860811&postcount=734
[Fascinate Android Development] uslacson1:
Minimal Clock Steps

I've been running OTB for a while, just flashed 1.5 and tried experimenting with the settings. I've noticed that clock steps has the highest time in state for steps

100, 800 and 1200.

I've set it to run only the 3 steps at -50UV, initial result is i'm getting 2 hrs for every 5% battery. Looking great so far. I have not yet experienced any freezes or lags.
[Fascinate Android Development] navenedrob:
Hey guys, please use this compile of the kernel: http://xdaforums.com/showpost.php?p=13979474&postcount=805

It contains some updates that mine does not, which is getting linked. I am working on getting nitsuj17 to update the wrap-up thread with this link, that thread is here: http://xdaforums.com/showthread.php?t=1013312

Keep an eye out for the updated link in that wrap-up thread, you can find what you are looking for under Kernels (when it gets updated the link will be there). Since the OP has not been updated this will be much easier for you all to find. Please make a note of that.
[Fascinate Android Development] PeterGunz:
I can get almost any settings to work on my phone except for when I use the camera.

Anybody have insight into what step causes this to constantly freeze?

I have been using 1.5 and my usual settings are

1200 -0 or -25

1000 -25

800 -25 or -50

600 -25 or -50

400 -25, -50, or -75

200 -125, -100

I'm mostly just curious what causes the camera to freeze the most. Should I eliminate a step or is it from too drastic differences between voltage steps?
[Fascinate Android Development] minho422:
Where can i get the 1.4 version? For me it was the most stable one until i flashed 1.5 and it constantly freezes.
[Fascinate Android Development] scarmon25:
OTB V1.4 TW

http://db.tt/UJkfjhL

Its my dropbox so download may be a little slower than normal.

Tap-a-Talked
[Fascinate Android Development] minho422:
Thank you!
[Fascinate Android Development] scarmon25:
Anytime

Tap-a-Talked
[Fascinate Android Development] Skrazz:
Is it just me or does 1.5 never hit 100 mHz? Using bfq scheduler.

Sent from my SCH-I500
[Fascinate Android Development] CHANGiism:
You need to enable 100mhz from CWM advanced menu.
[Fascinate Android Development] Skrazz:
Very well. Thank you!

Sent from my SCH-I500
[Fascinate Android Development] dablitzkrieg:
My cwm does not have this in the advanced settings. Does anyone have a link to this version?
[Fascinate Android Development] landshark68:
If you flash the OTB 1.5 kernel by itself you will get that CWM.
[Fascinate Android Development] Skrazz:
Rolled back to 1.4 last night. Very strange behavior with 1.5 with my setup. I use very moderate uv settings as well. Been stable ever since.

Sent from my SCH-I500
[Fascinate Android Development] dablitzkrieg:
Thank you landshark
[Fascinate Android Development] PeterGunz:
Just some advice for anybody having trouble with lockups, going back to 1.2 solved all my problems. From 1.3-1.5 I would get at least one lockup a day (often from camera). After reverting back to 1.2, no problems. Not even camera. I think somebody much smarter than me explained in an earlier post in response to Saps that this has something to do with droop values being higher. Not sure what that means, just relaying it.

1.2

Deadline

1200 - 0

1000-25

800-25

400-75

200-100
[Fascinate Android Development] saps:
Correct, hence why I'm still on 1.2 myself
[Fascinate Android Development] beray5:
So am I.

nemesis2all latest initial settings in the 2.6.35 GB kernel here -> https://github.com/nemesis2all/sch-i510_kernel/commit/b62f0d702e3edac7b5872c873356c14535f259de

+ {1500000, 1400, 1100, 0},

+ {1400000, 1375, 1100, 1},

+ {1300000, 1300, 1100, 2},

+ {1200000, 1300, 1100, 3},

+ {1000000, 1275, 1100, 4},

+ {800000, 1200, 1100, 5},

+ {600000, 1175, 1100, 6},

+ {400000, 1050, 1100, 7},

+ {200000, 950, 1000, 8},

+ {100000, 950, 1000, 9},

Assuming 1300mV nominal voltage.

400000-1500000 have 2dB of droop compensation.

100000-200000 have 3dB of droop compensation (probable default samsung OEM to avoid Nyquist/Johnson noise causing transistor faults - SOD or instant lockups on idle/screen-off).

It would be great if 400000-1500000 had the choices of 1150, 1125, 1100, (and 1075 or 1050 toward worst case hardware quality).

Typically without droop voltage compensation, the processor had to be overvolted to be stable. For example, 1300mV setting required to avoid dropping below 1100mV under loading level current with no compensation, simple and plain 1100mV setting use with droop compensation enabled allowing for lower CPU power consumption as well as stability.
[Fascinate Android Development] minho422:
After I installed 1.5, the browser won't open and force closes. It fixed with 1.4. Anyone having this issue?
[Fascinate Android Development] stephenj37826:
The droop value can be controlled outside of the kernel. Tegrak oc ultimate can adjust those values on the fly. I sent the creator of voltage control a message about this idk if it will be considered but it would be so awesome
[Fascinate Android Development] saps:
This would be a nice addition to VC
[Fascinate Android Development] CHANGiism:
Thanks. I thought I saw for this version BFQ is the default IO but noticed that the deadline was the default. Also, I noticed the Voodoo Sound is still v8 but I don't even know what v9 is supposed to enhance. Thanks for all the hard work nem!
[Fascinate Android Development] nemesis2all:
YW. I meant to v9 sound but forgot about it until after I posted the kernel. If i get extremely bored I may add it in, but I am more concerned about cm7 and .35 kernel.
[Fascinate Android Development] scarmon25:
NEM!!!!:) Great to see ya man. Hope all is well. Just flashed your new OTB. The new voltage control is kinda weird lookin. I know that's not your doing. Anywho so far she's running strong man. Thanks for your work and as always you rock.

Update; So far so good. No issues and the problem I was having with it getting unresponsive directly after a download seems to be gone. I am in the process of cycling my battery and after a day or two I will post my battery life results. Wont know anything for sure until then. As far as my settings they really haven't changed much but I will share them again for anyone who may want them.

Max Clock 1200 mhz, CFQ scheduler, Conservative CPU setting

1200 mhz -50mv

1000 mhz -75mv

800 mhz -75mv

600 mhz -75mv

400 mhz -75mv

200 mhz -75mv

I had really good results with these settings on prior versions of OTB so I tend to stick with them. Again thanks for the hard work I know you put into this. It is very much appreciated.

Tap-a-Talked
[Fascinate Android Development] ssewk2x:
Looks pretty good to me. I did notice that it took a very long time to start using the OC states I enabled. I even ran linpak and such to try and force it to higher speeds, but it peaked at 1ghz. I had to save as boot settings and reboot in order to see a change. Anyone else see this?

Certainly not a showstopper, I love these otb kernels! Can't wait for a fully functional cm7 build to try one out on :D
[Fascinate Android Development] nemesis2all:
I noticed that issue as well when using new voltage control version. Not sure if that was the cause bc I did not test an older version of vc as well. I just chalked it up as an annoyance and not a major problwm.
[Fascinate Android Development] scarmon25:
I had this issue as well and a reboot fixed it. No worries

Tap-a-Talked
[Fascinate Android Development] Ianxcom:
Anybody else feel they get best performance with the noop scheduler? Maybe its a placebo but my phone seems more 'snappy' and stable. No sleep of death either.

I found a post through good that seems to explain a little about schedulers in lamens terms but I dont know how accurate it is. Can anyone in the 'know' comment on it?

http://www.motorolafans.com/forums/motorola-e8/29407-app-io-scheduler-advanced.html
[Fascinate Android Development] scarmon25:
Honestly I haven't had many SODs since I quite using the 100 mhz and BFQ. I use CFQ and seem to get good performance but will try out the NOOP and see what things are like.

Tap-a-Talked
[Fascinate Android Development] Ianxcom:
Yeah 100MHz and bfq do that to me too. Also interactive and on demand sometimes as well. Bfq and interactive was awesome in my incredible.
[Fascinate Android Development] SOTK:
Would somebody mind explaining the whole enable/disable 100mhz thing for me? I've seen it in cwr. I'm currently running PBJ -100 but thinking about running this new kernel. Thanks.
[Fascinate Android Development] scarmon25:
Ok so I don't know what you did in this one Nem but damn man. I'm getting freaking killer battery life. At present time I have been up for 6.5 hours and am at 51% battery. This is with about 2 hours on standby. I have Never got battery life like this. I'm using the same settings I have used on your previous kernels but this is flipping me out man. The performance is spectacular and battery life has me puzzled, but in a good way. Dude seriosuly. Thanks :)

Tap-a-Talked
[Fascinate Android Development] AuroEdge:
Please add a description of the schedulers to the OP
[Fascinate Android Development] beray5:
NOOP - First in first out, pipeline burst, the simplest old reliable scheduler.

Deadline - Minimum latency based. Optimal for known, predetermined, constant latency I/O accesses randomized or not.

SIO - Dealine + NOOP based. (Deadline-)

Anticipatory - First generation primitive predictive I/O scheduler.

CFQ - Second generation stochastic based scheduler, the equivalent of windows XP interupt driven I/O scheduler.

BFQ - Third generation scheduler, the equivalent of windows 7 interupt driven I/O scheduler.

The first 4 schedulers are only good for older or simple dedicated hardware devices, not suitable for multi-purpose complex realtime Android phones.
[Fascinate Android Development] vlucchetti:
Are you on UKB 2.0?
[Fascinate Android Development] scarmon25:
UKB2.0?

Tap-a-Talked
[Fascinate Android Development] hecantbreathe:
Community Rom 2.0 aka ultimate kang bang
[Fascinate Android Development] scarmon25:
Ahh. No I'm on a Mesmerize and running Heinz 57 w/ Ultimate Honeycomb.

On another note: So I did the conditioning yesterday. Charged to full, wiped battery stats, ran down battery to about 10% and charged back to full. Today, holy cheeseballs, phone unplugged for 2 hours and 36 minutes and battery is at 86%. Normal use, which means checking XDA like crack addicts need a fix. Tecting my wife. Surfing the web a few times. Checked market for app update. Checked amazon for free app of the day. That is my normal use.

For as long as I have been on XDA I have heard people say they get 12-16 hours of use but honeslty I never believed them. I could never get more than 8 hours of battery no matter what I did. I mean I could go all day and then some on standby but really, not use my phone. No way. Yesterday when I checked before I plugged in my phone, the up time was 11 hours 39 minutes and I believe it was at 11%. I wish I could post a pic but Im at work now so I may later. Nem you have made me very happy. I know I have said it before but after going through like every kernel that you, imnuts, JT, and Times_Infinity has put out. I believe I have finally found what I have been looking for. If this is the last Froyo you do. I believe you finished strong my friend. Thank you.

Tap-a-Talked
[Fascinate Android Development] vlucchetti:
never mind! :)
[Fascinate Android Development] beray5:
ukb 2.0 + otb 1.6
[Fascinate Android Development] scarmon25:
Simply put: Damn!

Tap-a-Talked
[Fascinate Android Development] speedingcheetah:
not receiving calls

so I flashed this updated kernel yesterday... everything seems fine and works great. Using bfq and OC to 1300mhz with 100 and 200 mhz steps disabled on Com Rom 1.3..same settings I had before flashing 1.6 kernel.

Phone has been on all day now, but just noticed 2 new voice mails, but the phone never rang..3g works, but tried to call phone and it went to voicemail. I rebooted my phone and 3 new text messages suddenly appeared and now the phone will ring.

Sounds like it is disconnecting from the cell network or something after a bit of inactivity or sleep????

I remember see posts somewhere about this but it was quite a while ago...

Any ideas?
[Fascinate Android Development] scarmon25:
Finally got a pic of battery usage. God I love this kernel. As for the forementioned problem. I have not had this trouble yet. Though I am on a different set up then you so I may never have it. But if I do I will post back.

Tap-a-Talked
[Fascinate Android Development] AuroEdge:
This post you made about performance and voltage settings is very very helpful. Please continue to post these with images when you change them!
[Fascinate Android Development] GoBruins:
Which kernel are you running? 100? Hows stability / issues?
[Fascinate Android Development] scarmon25:
Using OTB v1.6. These are my settings. Another thing that may need to be taken into account is that I have really slimmed down my phone as far as system apps. I only have one keyboard, third party gallery. and have replaced alot of the stock system apps with ones from the market which may or maynot have anything to do with it. But here they are.

Max Clock 1200 mhz, CFQ scheduler, Conservative CPU setting

1200 mhz -50mv

1000 mhz -75mv

800 mhz -75mv

600 mhz -75mv

400 mhz -75mv

200 mhz -75mv

I do not use the 100 mhz step. As far as stability. I haven't had any SOD's and freezes yet. This is technically day two so there could still be some problems ahead but so far this has been the best one yet for me. I am still trying to grasp the kinda performance and battery life I am getting. As I said I have never gotten more than 8-9 hours of use. I unplugged at 8:am today and it is now 4;pm. I have 42% on my battery and have been using it quite often. Nem I cannot thank you enough man. This has made me love this phone all over again.
[Fascinate Android Development] nemesis2all:
NP glad you enjoy it... hopefully people will enjoy my .35 cm7 kernel more:)
[Fascinate Android Development] hecantbreathe:
I know I will!
[Fascinate Android Development] Grimis:
+1
[Fascinate Android Development] scarmon25:
I may have to finally take the leap to CM7 just to try it out. :)

Tap-a-Talked
[Fascinate Android Development] drnihili:
I'm on CommRom 2.0 with OTB 1.6 on top of it. I've enabled 100mhz in CWM and have verified that it's enabled in voltage control (using CFQ). But cpu spy says I'm never entering the 100mhz state. The 100mhz is the primary draw for me due to the potential battery savings. Any idea about why it may not be happening?