yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] saps:
Confirmed. Yes on the previous version of OTB where there was no 100Mhz I was getting insane battery life. Initially I wasnt with OTB reloaded nor was I able to run as much UV. However, after awhile I am now running my lowest voltage settings ever and I have had to pull the battery since I set these three days ago.

I would do a screen shot but it wont fit on just one so this will suffice:

100&200Mhz = 825mv [-125mv]

400Mhz = 950mv [-100mv]

800Mhz = 1125mv [-75mv]

1000Mhz = 1200mv [-75mv]

1200Mhz = 1250mv [-50mv]

1300Mhz = 1300mv [-75mv]

I believe I could even drop the 100Mhz by 25mv and possibly the 800, 1000 and 1300 but 3 straight days of perfect stability have me content here. The uv is lovely. Provided I have consistent signal. If I dont get any data transmission, at rest it takes this phone with this profile between 1-2 hours to use a single % of battery. Obviously its not nearly as good when used. But its to the point where I can almost not charge it nightly if I have a light use day.

Also I use cfq as well but find the highest IO scores in quad with sio
[Fascinate Android Development] Tenburn:
Even using no clocking or UV, this kernel makes my phone randomly shut down. Going back to JT's.
[Fascinate Android Development] Bubbadogg14:
I have SOD on jts 4/15 kernel so lets test out the 1 everyone is SOD on lol worth a shot
[Fascinate Android Development] beray5:
Anyone with better knowledge and superior English please feel free to add and expand further.

For those who do not know.

SIO is the old reliable standard round robin pipeline burst I/O scheduler.

CFQ is stochastic based scheduler the equivalent of windows XP interrupt driven I/O scheduler.

BFQ is enhanced version of CFQ and the equivalent of windows 7 interrupt driven I/O scheduler.
[Fascinate Android Development] cpfeifer:
What this "quad" cause cause I can't get category specific scores on Quadrant standard, do I need a pro?
[Fascinate Android Development] saps:
Yeah quad advanced breaks it down per test
[Fascinate Android Development] lasportsfan:
I flashed this kernel strictly for the sound and lagfix so my phone would run smoothly again. If I leave the settings as is will I be okay? I also didn't hear the voodoo lady's voice when I flashed and when I checked in adb I still see rfs files does that mean I didn't flash the kernel correctly?
[Fascinate Android Development] droidzach:
You prob haven't enabled lagfix yet. Either do it from recovery or the voodoo control app
[Fascinate Android Development] lasportsfan:
That's exactly what it was. Sheesh I'm still such an amateur. Thanks for the help.
[Fascinate Android Development] cpfeifer:
So I'm searching the Market and I'm not seeing anything like "quad advanced" what exactly is the app called?
[Fascinate Android Development] suppliesidejesus:
I don't think there is a market version of the Advanced app, I think you have to acquire it through...other means.
[Fascinate Android Development] cpfeifer:
Can you pm me with these "other means"? I already tried the only place I knew.
[Fascinate Android Development] suppliesidejesus:
I don't actually have it, that is just what I have heard. :(
[Fascinate Android Development] egorzilla:
Looks like you can find quadrant advanced at this forum

http://forum.mobilism.org/viewtopic.php?f=438&t=134804

there is an updated link on the 2nd page.
[Fascinate Android Development] Dj-Dubster_TN:
So I am new to this kernel with voltage control thing, could someone shoot me a link on how to set voltage control, or just give me your best most stable settings, much appreciated.
[Fascinate Android Development] scarmon25:
Keep in mind I'm on a mesmerize and every phone is different in what it can handle as far as overclocking and undervolting but I have had good luck with these settings.

I have 200 ,400,600,800,1000,1200 mhz enabled. with -75 off 200-800 and -50 off 1000 and 1200 mhz

with the Max clock set to 1200 mhz.
[Fascinate Android Development] bmeek:
PBJ or OTB? questions on clockspeed...

I've used nemisis2all's OTB kernel in the past with its support for granular, user-defined clock speed + voltage level steps, but don't feel qualified to make the best choices for each step (nor inclined to experiment continuously :-).

Since the Fascinate seems plenty fast when running properly, I had taken to using the excellent PeanutButta Jelly Time UV kernels from imnuts for battery life, up-to-the-minute voodoo support and plain ol' simplicity.

Now the "Community ROM" has me running the OTB kernel again, and my curiousity is piqued. Several questions come to mind that I haven't seen clearly answered yet...

What is the default clockspeed for this device? Is it 1000mHz all of the time? Are there any lower-speed steps by default?

Put another way: If there was a "Voltage Control" step+voltage setup for "Samsung defaults" what would it look like? How many steps at what levels? If I use the OTB kernel and never mess with Voltage Control, what clockspeed(s) will my phone run at? Is the same as the Samsung default?

Finally, what activities or utilization levels trigger a step change?
[Fascinate Android Development] deaffob:
I wonder if nemisis is planning on adding voodoo sound 8
[Fascinate Android Development] nemesis2all:
V8 will be in next update. All clocks and volts are stock unless you change them yourself.
[Fascinate Android Development] garywojdan81:
Just tried it. All the links are down..
[Fascinate Android Development] beenz:
Is this the same kernel in the Community Rom? And if so, when there are updates, will they be included in the Community Rom, or will they have to be applied via this thread?
[Fascinate Android Development] ekowanz:
same question
[Fascinate Android Development] mrtonee:
hey i was just wondering were does it shows your usage for each setting??
[Fascinate Android Development] saps:
3rd party app like Root system tool
[Fascinate Android Development] mrtonee:
thank you..........
[Fascinate Android Development] tapout27:
Awesome downloading now sir....thanks alot
[Fascinate Android Development] tysdad08:
Hey is this the same kernel in the com rom
[Fascinate Android Development] tapout27:
yes it is and im sure in the future they will use his updated kernels as well but for now you can flash it from this thread

EDIT: meant yes it is the same dev and kernel just an older version included in the Comm ROM
[Fascinate Android Development] nemesis2all:
It is an updated version of the kernel in community rom.
[Fascinate Android Development] nemesis2all:
Another good tool for checking time in state is cpu spy from market.
[Fascinate Android Development] DevinLeFevere:
Awesome! Thanks Nem
[Fascinate Android Development] brossma1:
thank You for all you do is this the kernel in the new com rom?
[Fascinate Android Development] beenz:
^^Look 4 posts back...
[Fascinate Android Development] scarmon25:
just flashed. so far so good. great work man. thanks
[Fascinate Android Development] djk21108:
My memory is fading me. Is OTB 1.2 brand new as of today?

Was the OTB I got a few days ago also version 1.2? Is this just a slight update? Or does the change log for 1.2 on the OP reflect a butt load of changes in this kernel?

I sure hope so, can't argue with progress!
[Fascinate Android Development] nemesis2all:
1.2 is new an updated as of today.
[Fascinate Android Development] saps:
Grabbed that one too, thanks. Oddly, it reports much differently than Root System Tool does. Not sure who to believe. Not sure how to quantify deep sleep as well. Maybe its screen off 100Mhz [my bottom step] as opposed to screen on 100Mhz :confused:
[Fascinate Android Development] nemesis2all:
I am unsure what qualifies as deep sleep as well. Miss seeing you on irc.
[Fascinate Android Development] speedingcheetah:
Would it be a good idea to flash this on SC 2.9.2?? Or would it screw things up? I think SC is running EC10 based kernel..How do you check what kernel your running anyway..just get numbers in About phone..I think SC is still EB01 based right..

Anyway, just looking to the newest/best updated kernel that would go good with SC.

I am holding off trying the Comm. romm till this 3g data problem blows over..since I am not experience any problems at all with my current setup..
[Fascinate Android Development] nemesis2all:
Should be fine for any froyo touchwiz based rom.
[Fascinate Android Development] speedingcheetah:
Don't need to do a data wipe do I?

Also, if i don't want to mess with the voltage settings, can i still just use Setcpu to adjust governor and speeds..?
[Fascinate Android Development] saps:
Thanks buddy. Yeah new job a few months ago and my days as a mad-dog kernel tester are on hiatus. Still on the edge of the loop, via here but yeah Ive not been in irc in maybe 2 months, maybe more :eek: I'll parade my azz back in there one day. Till then luvin the OTB, luv - in - it :D
[Fascinate Android Development] nemesis2all:
Do not use setcpu. It cannot set clock speeds properly. Voltage control can even if you do not want to adjust volts make sure to use voltage control.
[Fascinate Android Development] speedingcheetah:
Got it..just flashed..so far so good..noticeable improvement..been wanting the voodoo color thing..

Can u point me to where a description of all the cpu governers(edit..i mean schedulars) are...and what one is the best?
[Fascinate Android Development] djk21108:
I'm a little hazy on the whole CWM fiasco that seems to be enveloping our phone. However, the change log mentions something about CWM 3, but when I go to recovery I still see 2.5.1.x. Is that just a relic, and the actual version is 3, or am I missing something?
[Fascinate Android Development] speedingcheetah:
Running beautifuly..love it..video look much better..How do u control all of voodo options..i have voodoo control pluss..but has no options for color..just sound

Only noticed one thing..phone locks up when use back button to exit camera app...

Also...why is default scheduler deadline...a lot of posts seem to point to bfq as the best...would be nice to find a detail description of how each one of these work...
[Fascinate Android Development] nemesis2all:
Reason why I changed schedulers was because of camera issues. Others are still there if you want to use them, but know that they might be a little buggy. Should be able to find any info that you want about different schedulers via google.
[Fascinate Android Development] nemesis2all:
Depends if you got this kernel from comm rom it is not flashing recovery in that script. If you got this kernel from this thread then it should have flashed recovery.
[Fascinate Android Development] beray5:
Shedulers performance comprised of 2 basics - Latency and Throughput, most people only pay attention to throughput and none for latency.

Unfortunately, fast or slow Throughput affect only good or bad data performance. Missing Latency meant complete LOSS of data - Hangs, Forced close, Quench, Reboot....
[Fascinate Android Development] saps:
Almost sounds like we need a poll, in addition to posting what our respective voltages ans steps are we should say which scheduler we use. I was on cfq went to bfq now back with cfq. I was getting a random lock up with bfq in this new monopoly app I'm currently hooked on. Otherwise they both seem the same to me
[Fascinate Android Development] nemesis2all:
I have actually thought about that.....mostly to get a poll going on which scheduler seemed most stable and provided good performance as well. For me when I set to bfq it seems to lock my camera everytime when i try to exit....I see it happen maybe once in 10 times on sio, have not seen it at all deadline.
[Fascinate Android Development] GoBruins:
Just found some time to flash everything up to date....

Running BFQ

1200 1275mv

800 1125mv

400 975 mv

200 850 mv

100 850 mv

Been only a few hours, but stable so far!
[Fascinate Android Development] beray5:
I've been using this same setting for 2 days.
[Fascinate Android Development] PeterGunz:
Same here. Only thing that locked up my phone was the camera issue, which is now been gone since going deadline.

Anybody else tried another camera app? Like MIUI camera? I wonder if that would have the same hang ups on bfq like the stock one does.
[Fascinate Android Development] bhfd64:
My camera freezes regardless of scheduler or voltage setting. Can't take more than 6 or 8 pictures in a row without the phone crashing and having to reboot it twice to get it back to normal.
[Fascinate Android Development] thelandon:
I flashed the OTB 1.2 kernel last night. As of noon today, Cpu Spy says that I'm using/spending a large amount of time at 100 mHz even though I have not applied that frequency in Voltage Control. I thought that this newest kernel included a patch to keep Voltage Control settings correct/as entered?
[Fascinate Android Development] nemesis2all:
Did you disable 100mhz step in vc?
[Fascinate Android Development] Dragonblade02:
I've Read a lot of post here of ppl trying to UV their phones and how great is working for them so i decided to try it out, im a total noob at this...

so Flashed comm 1.2 Last night with deadline set as the Scheduler, I tried the camera out I took a pic and it froze on the spot when trying to review.

this with Stock settings right after flash

Switched over to Bfq. with no other changes.

and it worked fine till noon today after playing words with Friends.

I tried a few settings but no matter what i did, Words with Friends and the camera at times would just keep locking up.

also about 90% of the time I change the Settings and " Save the Boot " and Try to reboot my phone the phone locks up. anyone else seeing this?

i've gone really light in my UV. atleast I think soo. compared to what other ppl have posted, you can find my UV's below with both bfq and cfq.

and got a couple of lock outs within a few hours under both settings. the checked states that i have are 1200,1000,800,600,400,200,100

1200-25

1000-50

800-50

400-50

200-50

100-25

1200 -25

1000 -25

100-800 - 75

any future help would be appreciated.

maybe my phone is just stupid ( or the Owner :p )
[Fascinate Android Development] thelandon:
Yes, I selected 200, 400, 800, 1000, and 1200 only. Strangely, 600 mHz was also showing usage.

I wish I knew how to fix it, as I suspect that this is why my phone is so unstable at 1300 mHz, ie: I'm running too many steps (although, not on purpose).
[Fascinate Android Development] nemesis2all:
When you change schedulers do you reboot? I just took 10 pics in a row with oc and uv. I am trying to find a way to repeat your issue. Anything else you can think of that could help me?
[Fascinate Android Development] bdube:
been dealing with the same wwf freezing issue every time i attempt to undervolt even just one step...still experimenting though
[Fascinate Android Development] Ianxcom:
Im new to the fascinate and this is my first kernel flash. Once i flash this do i have to goto voodoo and do the lagfix?
[Fascinate Android Development] speedingcheetah:
Have to UV

So..Do u have to set an under volt if use states above 1000mhz..cause I didn't move the slider for voltage at all. just set scheduler to bfq and have states 400, 600, 800, 1000, 1120, 1200 enables...

do i need to adjust the voltage...i don't want to damage phone..or is it fine the way it is??
[Fascinate Android Development] iceman1183:
Voltages are stock if you don't mess with them, so if you don't want to undervolt at all that's fine, it won't hurt anything.

Sent from my SCH-I500
[Fascinate Android Development] bhfd64:
Do you mean reboot without saving as boot settings so that my scheduler change doesn't stick? I always just set as boot when I'm finished because everything else works flawlessly. I'm playing with jt's CM7 at the moment but when I switch back I'll take a more detailed note of what happens. Didn't mean to *****, other than the camera everything is great. Battery life and performance are among the best I've seen from my phone.
[Fascinate Android Development] saps:
Voltages are stock up to 1ghz, after that they are nemesis best guess for some overhead as of course anything beyond 1ghz is beyond stock
[Fascinate Android Development] thelandon:
Cpu Spy now reports my settings correctly. I reflashed the Com Rom v1 and v1.2 then fully rebooted. After booting, went into recovery again and flashed OTB 1.2. Previously, I had flashed all 3 zips at the same time in the same order stated above.
[Fascinate Android Development] chrisexv6:
Pardon the possibly dumb question, but how does this kernel compare to the one thats included with CommROM?

I thought nem had mentioned the CommROM kernel was slightly different.....will any OTB kernel be workable with CommROM from now on?

Thanks.

-Chris
[Fascinate Android Development] saps:
Same kernel, 1.2 otb is in comm rom
[Fascinate Android Development] nemesis2all:
A more detailed response is in comm rom 1.0 a kernel was included that was based off of 1.1 with a fix GizmoDroid did for wiping data. As far as ver 1.2 the kernel posted here is the same as the one in the 1.2 comm rom patch. Only difference is the kernel posted here flashes recovery while the one in comm rom does not. They have decided to stay away from flashing recovery for now.
[Fascinate Android Development] kidserious:
What are the differences between this and 1.2? I don't use TouchWiz but I'm assuming you are going to release one for AOSP and CM7 right?
[Fascinate Android Development] scarmon25:
Thanks. last version didn't play nice with me. so far this one is stable. great work man. glad to be back on OTB

Update: Just wanted to add with the first version I was able to run -75 off 100-1000, and -50 off 1200with 200,400,600,800,1000, and 1200 enabled no problems.

These same settings would not run on version 1.2. I could barely get it to run with -25 off each step.

With v1.3, I can run my original settings with BFQ and it runs like a dream. What ever you did in this version, thanks man.

Rockin Heinz 57 w/ OTB Voodoo ( For today at least)
[Fascinate Android Development] speedingcheetah:
Just flashed 1.3..no problems so far..

So..any reason for the change of scheduler to sio?..Ive tried them all...can't really tell a difference..so I just stick with bfq...

EDIT: Actually, i do..i think i had this problem on 1.2 kernel..but just now noticed it...get SOD when unplug charger cord from phone when screen is off...just reboots after a bit..doesn't do it if i wake the phone up before un plugging it..
[Fascinate Android Development] BeeDubs:
Which imnuts kernel?

Thanks for the feedback!

Sent with my thumbs.
[Fascinate Android Development] speedingcheetah:
looks like I have this problem too..even on the 1.3 kernel and superClean 2.9.2...I plug in the phone, but if if unplug it with the screen off(ie. While it is sleeping)...nothing...SOD..phone reboots..don't seem to do it if i turn on the scree and unlock it then pull out the cord...

Any ideas what is causing this..I am using bfq scheduler..if that helps:confused:

EDIT: Where is the Stay Awake mod setting people are talking about...I can't seem to find it...??
[Fascinate Android Development] saps:
Settings, applications, development
[Fascinate Android Development] speedingcheetah:
O!.. whoops..didn't think to look there...:o...Thanks...
[Fascinate Android Development] speedingcheetah:
Well. I set the Stay awake setting on...but still it locks up if I unplug it after a few minutes of the screen turring off..

I'm sure I say a thread about this somewhere...

Gues i'll just have to wake it up before unplugging..not a big deal..
[Fascinate Android Development] iviustang50h:
Is this the same kernel included in Community Rom 1.2?
[Fascinate Android Development] djk21108:
Great work on the Kernel man. Made switching to CWM 3 very easy. Runs great!
[Fascinate Android Development] beenz:
That setting is so the screen doesn't turn off when plugged in. Not the phone not going to sleep.
[Fascinate Android Development] beenz:
Seriously?
[Fascinate Android Development] suppliesidejesus:
No freezes unplugging and plugging my phone into my work laptop today with this new kernel!

I also did a full uninstall and reinstall of the Samsung drivers and my VM software, so it could have been that, but I'm hoping you just inadvertently fixed whatever was causing my phone to do that. :D

I'll be testing it all day. Voltages seem to be doing well!

Rock on.
[Fascinate Android Development] BeeDubs:
What voltages and steps?

Sent with my thumbs.
[Fascinate Android Development] ezas:
This was just asked and answered about 2 hrs before your post.

http://xdaforums.com/showpost.php?p=13349723&postcount=561

While I realize that scanning a long thread can be a challenge I don't think a scan back of a few pages (or a day or two) is unreasonable.
[Fascinate Android Development] suppliesidejesus:
Well, it froze when I plugged it in. Gonna see if it was the SIO scheduler causing that, since I was on BFQ before.

EDIT: Nope. Freezes upon plugging in no matter what voltage settings or scheduler I use. Shame I can't get any logs on it.

EDIT 2: Something I've noticed - When using your kernel, sometimes I get "USB Device Not Recognized" and I have to reboot to recovery and reboot again for the adb drivers to be recognized again. This usually happens after it freezes and I reboot the first time. Again, this does not occur with any other kernel. And also, sorry again that I can't get any logcats for you. :(
[Fascinate Android Development] iviustang50h:
Oops - my fault. I did browse this thread and must have glazed right over that. I am sorry. Thank you for the info, though.
[Fascinate Android Development] shorto85:
Thanks for the updated kernel. So far everything seems to be working fine.
[Fascinate Android Development] inkdrink:
Set cpu profiles

Is is possible to use Setcpu profiles with this kernel, such as "screen off?" Usually when I use that, my phone eventually won't wake back up from being off, even at varying speeds.
[Fascinate Android Development] nemesis2all:
I have not tested that. This kernel is still in need for some testing as far as the overclock goes and how setcpu will react with it. I do recommend using conservative in setcpu. Please feel free to test profiles and report back to me. With logs if available.
[Fascinate Android Development] garywojdan81:
Just saw you updated the op with ver.2 & it's listed as having cwm. Is that the red 2.5.x or the new orange? I have jt's permanent red installed so if I flash this will I have a problem?
[Fascinate Android Development] dricacho:
Mine was fine for about an hour, then started to lock up. I reverted back to non-OC EC10 voodoo kernel.
[Fascinate Android Development] tapout27:
It flashed fine for me...no issues with my existing red voodoo CWMR
[Fascinate Android Development] mgrimmenator:
to anyone having issues with boot loop. i have run into this issue before as well with other roms/kernels. when you flash DO NOT WIPE CACHE. after 1st bootup then you can wipe the caches out. don't know why this is but everytime i have had an issue this is why. even if i try and run superclean. if i install from cwm and then immediately wipe the caches and then try and boot, i will always get a boot loop. this kernel may be the same way. not 100% sure but might help someone out.
[Fascinate Android Development] Coolsaber57:
Flashed this kernel today. It worked fine for a while, got me a 1753 on quadrant (not that that really means anything)

But then it locked up and rebooted twice in a row, so now i'm trying the UV kernel.
[Fascinate Android Development] bL33d:
could not run n64oid zelda very long b4 crashing :( went back to new jt voodoo and runs zelda fine damn i want a oc kernel :P
[Fascinate Android Development] TheSonicEmerald:
My phone has again fallen in love with one of your kernels Nemesis, phone never felt more snappier!
[Fascinate Android Development] kuronosan:
Mine works great. Stopped getting a sleep of death bug when I turned off "Display Off" profiles in SetCPU.
[Fascinate Android Development] blackmamba0730:
great work on this kernel. ran a quadrant and got 1791, my highest to date:) keep up the good work
[Fascinate Android Development] kuronosan:
Okay, I just figured it out. It seems as though when you receive a call or notification while the display is sleeping it will permanently stay that way.