• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root One Stop Shopping for Fascinate Kernels

Hey Saps,

How are you handling wiping battery stats with these OTB kernels? I always thought voltage differences between kernels was one of the big factors that makes a battery stats wipe necessary. Are you just waiting until you find the sweet spot on a set up that works, and then finally wiping the stats? Because I would assume every time we tinker with the voltage, it would likely require a new wipe.

Also, my phone hates these kernels but they are too addicting. I can't find ANY COMBINATION that is stable while on this...but I must keep trying. (Still on the 4/8 with red cwm 2.5 because I have no clue what the deal is with the orange cwm 3.0)
 
Upvote 0
Hey Saps,

How are you handling wiping battery stats with these OTB kernels? I always thought voltage differences between kernels was one of the big factors that makes a battery stats wipe necessary. Are you just waiting until you find the sweet spot on a set up that works, and then finally wiping the stats? Because I would assume every time we tinker with the voltage, it would likely require a new wipe.

Also, my phone hates these kernels but they are too addicting. I can't find ANY COMBINATION that is stable while on this...but I must keep trying. (Still on the 4/8 with red cwm 2.5 because I have no clue what the deal is with the orange cwm 3.0)
I'm not Saps, but lemme see if I can help. :)

Firstly, I am still putting some finishing touches/tweaks on my OTB kernel voltage setup, but while I was tempted to wipe my battery stats, I'm going to hold off until Adrynalyne and TDB drop their collective ROM on xda. Soon as I install that, I'm going to double check my kernal voltages and then I'll wipe. No real point doing it now since i'm relatively sure they'll have their ROM out by the weekend and I'll just be doing it all over again then anyhow.

As for the voltage combination, my phone doesn't seem to be as much of a beast as Saps and some of the others phones are and can't handle the OC and UV's their's can. With that said, here's my current setup. I've been 24 hours freeze free and I've been actively trying to freeze it up.

I use the following steps (voltages are in brackets):
1120 Mhz {0uv} - I plan to tweak this more today.
1000 Mhz {50uv}
800 Mhz {50uv}
600 Mhz {50uv}
200 Mhz {75uv}
100 Mhz {75uv}

I plan on adding the 1200Mhz this morning, and MAYBE trying out the 1300 as well.

Note: You may want to try 50uv for the 100 and 200 Mhz ranges. This is where I most notably got the "Sleep of Death" problem.

I ended up testing each step separately. To test I ran the TuneIn Radio (any station should work) app and turned my screen off (I had the media volume set to 0 so I couldn't hear it). Within 15 minutes I would know if the voltage settings were too low as the phone would freeze up. If there's a better way, please feel free to let me know. Also note that, while your phone may not freeze up when testing a single step, adding multiple steps certainly might. So I'd suggest starting from the lowest step and working your way up adding a step each time. (Also note, 400mhz on my phone seemed to crash constantly so I completely just skip that step).

Hope this helps!
 
Upvote 0
Also nklenchik I tried mimicking imnuts straight uv values with -100mv at everything and something was amiss. As always YMMV but I believe some of my steps could be dropped by another -25mv maybe even -50mv on the lowest two I just haven't made the time to test each one individually to find the perfect combo yet. The voltages above for me are 100% stable. I would judge this to have for me on par battery life with nem's 1.2Ghz with -50uv, its not quite as good as imnuts -100mv but then again Im also gaining the extra 30% in top end clockspeed. This really is the best of both worlds in terms of performance and battery life.

I've been using it on 1.2...working great so far. I think the problem was I was going a little too undervolted haha
 
Upvote 0
I use the following steps (voltages are in brackets):
1120 Mhz {0uv} - I plan to tweak this more today.
1000 Mhz {50uv}
800 Mhz {50uv}
600 Mhz {50uv}
200 Mhz {75uv}
100 Mhz {75uv}

Hope this helps!

Thanks a lot for explaining that.

Here is what I have finally gotten to work:

7 Steps, 200-1200. I had everything set at -25, and it worked briefly, but then I got a lockup while web browsing. So, I lowered 1200 to -0. Then I went 24 hours like it was nothing. Rock solid and no lockups. (I never tried the 100 step, as I kept hearing that people were having the most trouble with that one)

Now that I had everything -25 except for the 1200, I decided to start dropping the bottom steps. I started with 200 and dropped it to -50. It locked up pretty fast. I switched back to -25 and worked all day with it and, again, no problems.

Does this mean I can never undervolt the bottom step? I think I am missing something as to how this works because I have absolutely ZERO problems running imnuts -100 kernels or the Comavolts.

Also, I have now gotten rid of the 1200 step and tried 1300. so it looks like this:

1300 - 0
1120 - 25
1000 - 25
800 - 25
600 - 25
400 - 25
200 - 25

So far I have been stable for over an hour. Update: Locked up on the lockscreen.

One more question (sorry) how do you know when to cut out a step in the middle? For example, cutting out 400, 600, or the 1120 step.

Update 2: Now running this just to see what would happen:

1200
1120 - 25
1000 - 25
800 - 50
600 -50
400 - 75
200 - 75

And for whatever reason, I have been stable for hours. I don't get it. My phone has multiple personalties.
 
Upvote 0
Peter, the biggest problem I've seen is that SOMETIMES you can use the phone for a long time and it'll seem stable but eventually something'll lock it up. And SOMETIMES it'll lock up immediately. I've yet to find a way to make it reliably lock up each time. Like I said though, I have one application that seems to test the limits pretty quick. I ended up testing my phone on straight stock speeds yesterday at one point and it still rebooted. So I'm not sure what the deal is. I can only assume it's a specific step that was causing the problem. I'm waiting for Nemesis to release his latest OTB kernel and I'm going to try again. This kernel is a tweakers dream, I just wish/hope I can use it. :/

If you locked up at -50, then yeah I'd say you probably can't undervolt it anymore than it already is. Keep in mind though, that Nemesis already undervolted the steps to areas he thought was safe. So all you're really doing is undervolting the steps even further.

As for cutting out steps in the middle, there's not right or wrong I don't think. I kinda just selected every other step when I was testing. I didn't really feel there was a need to use every single step, but maybe I'm wrong?
 
  • Like
Reactions: PeterGunz
Upvote 0
Peter, the biggest problem I've seen is that SOMETIMES you can use the phone for a long time and it'll seem stable but eventually something'll lock it up. And SOMETIMES it'll lock up immediately. I've yet to find a way to make it reliably lock up each time. Like I said though, I have one application that seems to test the limits pretty quick. I ended up testing my phone on straight stock speeds yesterday at one point and it still rebooted. So I'm not sure what the deal is. I can only assume it's a specific step that was causing the problem. I'm waiting for Nemesis to release his latest OTB kernel and I'm going to try again. This kernel is a tweakers dream, I just wish/hope I can use it. :/

If you locked up at -50, then yeah I'd say you probably can't undervolt it anymore than it already is. Keep in mind though, that Nemesis already undervolted the steps to areas he thought was safe. So all you're really doing is undervolting the steps even further.

As for cutting out steps in the middle, there's not right or wrong I don't think. I kinda just selected every other step when I was testing. I didn't really feel there was a need to use every single step, but maybe I'm wrong?

Thanks for the feedback. Unfortunately, I use TuneIn almost everyday! But it is a good way to test it, just not when I am on a bus and have to pull my battery while trying to keep balance in a crowd.

Still been on 7 steps, 200-1200 at -75,-75,-50,-50,-25,-25,0 and I have not locked up. But I feel I am due.

I find this kernel to be good even without tinkering with it in voltage control. I am excited for his next one.
 
Upvote 0
I had always used 100 as my bottom step since day 1. With a 1300 top end I get a freeze about once maybe twice a day. Moving to a 200 bottom has eliminated this for me. Knock on wood. I have moderate stability with 1.4Ghz @1300mv but I can't complete a quad so honestly Im thinking Im done with the OC search I kinda wanna try the 1.5 just to see a linpack and then forever be content at 1.3 as a daily driver with a nice uv on the bottom
 
Upvote 0
I had always used 100 as my bottom step since day 1. With a 1300 top end I get a freeze about once maybe twice a day. Moving to a 200 bottom has eliminated this for me. Knock on wood. I have moderate stability with 1.4Ghz @1300mv but I can't complete a quad so honestly Im thinking Im done with the OC search I kinda wanna try the 1.5 just to see a linpack and then forever be content at 1.3 as a daily driver with a nice uv on the bottom

I'm with you on the top end, but mine is 1.2. I can't seem to get 1.3 to go. Right now I am using 8 steps:

1200 - 0
1125 -25
1000 -50
900 - 75
800 -75 (Update: Eliminated this step, feels smoother)
600 - 75
400 - 100
200 - 100

Thrown everything at it without any lockups for the last couple hours, but it feels a tad sluggish. I am assuming it is the undervolt causing it, or too many steps since with fewer steps and more voltage my phone felt snappier.
 
Upvote 0
I'm with you on the top end, but mine is 1.2. I can't seem to get 1.3 to go. Right now I am using 8 steps:

1200 - 0
1125 -25
1000 -50
900 - 75
800 -75 (Update: Eliminated this step, feels smoother)
600 - 75
400 - 100
200 - 100

Thrown everything at it without any lockups for the last couple hours, but it feels a tad sluggish. I am assuming it is the undervolt causing it, or too many steps since with fewer steps and more voltage my phone felt snappier.
Don't feel bad Pete, I can't hit 1.3 either. Second I get to the stairs in Quadrant it locks right up (actually once it got to the top and froze in the room with the two canisters glowing).

I've got the following on the new kernel:
1200 - 50
1000 - 50
800 - 75
600 - 75
400 - 50 (I wasn't too brave with this step just yet)
200 - 125 (Love this part)
 
Upvote 0
Don't feel bad Pete, I can't hit 1.3 either. Second I get to the stairs in Quadrant it locks right up (actually once it got to the top and froze in the room with the two canisters glowing).

I've got the following on the new kernel:
1200 - 50
1000 - 50
800 - 75
600 - 75
400 - 50 (I wasn't too brave with this step just yet)
200 - 125 (Love this part)

I haven't tried undervolting the top yet. That is the next step. Battery life is excellent source far for me.
 
Upvote 0
I haven't tried undervolting the top yet. That is the next step. Battery life is excellent source far for me.
I ended up still having some instability with the top uv'd. I left 1.2 at 0 for now, and dropped 1.12 to -25. Boosted 400 up to -75 though. I stopped using 600 and 1000 all together now. If I can run this without any problems today, I'm gonna back 1.12 and 1.2 down -25 more each and see how that works out.
 
Upvote 0
This is my current voltage profile:
snap20110418_103701.png

Please note I do not use the 600 and 1120 steps. So I have 7 total. I tried uv-ing's every step shown by 25mv and it was unstable. I think some of the above shown steps could be dropped by 25mv [particularly the 200] but as of yet I have not tried out individual steps. Frankly even if I am leaving 2-3% of uv on the table somewhere this kernel [OTB 1.0b] with this OC/UV combo is best ever. Im getting all day life with plenty of performance. For better or worse this is honestly probably as good as its going to get for me ever but hey I'll take it
 
Upvote 0
My phone is seriously annoying the shit out of me lol I tried your values, even a bit lower on 1.2ghz and it froze while i was switching music
Yeah every phone is different. I can even run 1.4Ghz pretty stable. Its fine in regular stuff and is fine for linpack but every once in awhile it will freeze. Mind you this is with 1300mv and 1325mv, more voltage than that doesnt help it actually hurts. But rather than having a 1.4Ghz phone which I have the pull the battery from every day I have a 1.3Ghz that I set and forget. If nemesis' new kernel gives me stability at 1.4 sure I'll use it but stability trumps all else. I probably would say performance over battery life as well only because with the uv I got the little extra I'd lose on 1.4 versus 1.3 is small since 65% of the time my phone is idle.
Yeah remember that battery life savings are mostly achieved when the phone is idle so dont try and uv the top steps too low looking for battery life. Screen is what uses the most battery and then data transmission so with the screen on you can only save so much. Bottom line is 1250mv with screen on will always use more juice than 850mv with screen off. So definitely use enough voltage on the top end steps. If you need 1300mv for stable 1.2Ghz then use it
 
Upvote 0
Any chance somebody could give a rundown of what the differences are with the scheduler settings?

No clue what the differences are, or which are recommended. I know cfq was supposed to be used before, but now sio is default and bfq has been added. And I have no clue if anybody uses the others, such as noop.

P.S. Here has been my most reliable setup:

1200
1120
1000 - 25
800 - 50
600 - 50
400 - 75
200 - 100

I can't do -125, as it puts my phone to battery pull sleep. I have never tried the 100 step, mostly because I hear it causes problems when overclocking but I might do it just for the heck of it.
Also, I have never done fewer than 7 steps. Does anybody find this helps in anyway? I notice some people using 5-6 steps instead of 7.
 
Upvote 0
Any chance somebody could give a rundown of what the differences are with the scheduler settings?

No clue what the differences are, or which are recommended. I know cfq was supposed to be used before, but now sio is default and bfq has been added. And I have no clue if anybody uses the others, such as noop.

P.S. Here has been my most reliable setup:

1200
1120
1000 - 25
800 - 50
600 - 50
400 - 75
200 - 100

I can't do -125, as it puts my phone to battery pull sleep. I have never tried the 100 step, mostly because I hear it causes problems when overclocking but I might do it just for the heck of it.
Also, I have never done fewer than 7 steps. Does anybody find this helps in anyway? I notice some people using 5-6 steps instead of 7.

Just started using this today. It's been pretty stable considering I can only oc to 1.2ghz lol

1200: 0
1000: - 25
900: - 50
800: - 50
600: - 75
400: - 75
200: -100
100: -100
 
Upvote 0
Just started using this today. It's been pretty stable considering I can only oc to 1.2ghz lol

1200: 0
1000: - 25
900: - 50
800: - 50
600: - 75
400: - 75
200: -100
100: -100
Well I flashed the last OTB reloaded and had zero success with 1.5Ghz even at 1450mv and I didnt feel like trying more voltage. But then I could not get the same stability at the same voltage levels I had before. So I tried switching back. Sadly, the voltage profile above was still not stable for me. So some of my values have come up by 25mv .
The other weird thing is with 1.0b[4-12] the 200Mhz step was the bottom one as 100 deactivated unless you turned it on via adb. With OTB reloaded 100Mhz is in effect but even when I de-select it under voltage control it is still being used:thinking:
Anyway, Im a bit unhappy about this whole thing as I was getting killer battery life on the previous kernel. I mean at idle rest if I didnt get a text or call I could go a couple hours before I lost a single % of battery. Thats at 200Mhz with -100mv. I don't know maybe I can dial this in closer to that old one. Sadly last night I flashed back and forth between the two maybe 2-3 times each kernel and sadly my ultra-low setting seem to be forever gone :(
 
Upvote 0
Any chance somebody could give a rundown of what the differences are with the scheduler settings?

No clue what the differences are, or which are recommended. I know cfq was supposed to be used before, but now sio is default and bfq has been added. And I have no clue if anybody uses the others, such as noop.
I have been curious about this too since nemesis wrote that he added the bfq scheduler. No idea of the difference though.
 
Upvote 0
Well I flashed the last OTB reloaded and had zero success with 1.5Ghz even at 1450mv and I didnt feel like trying more voltage. But then I could not get the same stability at the same voltage levels I had before. So I tried switching back. Sadly, the voltage profile above was still not stable for me. So some of my values have come up by 25mv .
The other weird thing is with 1.0b[4-12] the 200Mhz step was the bottom one as 100 deactivated unless you turned it on via adb. With OTB reloaded 100Mhz is in effect but even when I de-select it under voltage control it is still being used:thinking:
Anyway, Im a bit unhappy about this whole thing as I was getting killer battery life on the previous kernel. I mean at idle rest if I didnt get a text or call I could go a couple hours before I lost a single % of battery. Thats at 200Mhz with -100mv. I don't know maybe I can dial this in closer to that old one. Sadly last night I flashed back and forth between the two maybe 2-3 times each kernel and sadly my ultra-low setting seem to be forever gone :(

How are you tracking the use of 100Mhz? I thought Nemesis said on XDA that he thought that the registering of 100Mhz could be due to the phone using it to boot before the application of "set on boot" was applied...or something like that.
I'm sorry to hear you are having trouble on this kernel. I have been stable on my usual settings (which are by no means impressive), but haven't had any luck with anything lower in voltage or higher in OC.
 
Upvote 0
How are you tracking the use of 100Mhz? I thought Nemesis said on XDA that he thought that the registering of 100Mhz could be due to the phone using it to boot before the application of "set on boot" was applied...or something like that.
I'm sorry to hear you are having trouble on this kernel. I have been stable on my usual settings (which are by no means impressive), but haven't had any luck with anything lower in voltage or higher in OC.
Well its a bit better now. I cannot get my voltages from post 488 but I am at least running the ones from post 472. So basically there is a 25mv difference for me at 400, 800, 1000 and 1200. I can live with that for now.
I use Root System Tool to track the Mhz usage. It has a nice % graph
snap20110420_105333.png

As you can see 100Mhz is in full effect. I dont use 600, 900 or 1120 but you can see small fractions of use. This very well could be what nemesis spoke of. But clearly the 100Mhz issue is different
 
Upvote 0
OK so I see this thread has gone the way of the dodo bird. But just so everyone knows if you are looking to breathe some new life into your SF OC give Tegrak Ultimate a try. If you are inclined to use nemesis2all's OTB kernels Tegrak allow you to up the so called internal voltage. Without this adjustment I am only stable at 1.3Ghz on the OTB 1.2 kernel and 1.2Ghz on all other OTB's. [OTB 1.2 has a slightly higher internal voltage; this is exactly what Tegrak allows you to manually adjust yourself.
To give some numbers perspective. Normal/default internal voltage for steps 400-1000 is 1100mv. In OTB 1.2 nemesis raised that to 1125mv and this gave many people like myself the ability to hit 1.3Ghz and many could do 1.4Ghz. Using Tegrak I can hit 1.4Ghz stably with 1150mv internal and even 1.5Ghz with a 1175mv internal. Grant there is some overvolting on the cpu core voltage as well but the point remains the same that most people can gain 100-300Mhz on their top end OC by merely raising that aforementioned internal voltage. Give it a try if you are one who chases a bigger OC.
This is what 1.5Ghz looks like on my phone:
snap20110608_045056.png
snap20110608_050620.png


BTW, Tegrak Ultimate is found in market for $1.99 and OTB kernels on xda as well as the OP
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones