yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] wilshyre:
Saps, i'm glad you were able to stabilize the higher frequencies enabled in otb with tegrak. I hate to hear you guys are having force close and freezing issues with tegrak, because it works perfectly for me, and I do all the voltage settings in tegrak. But I might try your method of mixing both apps to get stable boot settings implemented. Anyway, good to hear you were able to get the same results as I was using tegrak with the higher oc steps because of internal voltage. I just wish I still had my old fascinate that was able to overclock so high on 2.1 roms with no problem. I cant help but feel I could run almost any frequency from the otb kernels on it because it never had a problem running otb's highest frequencies before.. and then I got my refurb and wasn't even able to get 1200mhz stable on 2.1 roms when running 3d games.

Sent by way of unspeakably black magic.
[Fascinate Android Development] SmokeyDP:
I'm running this with UK 2.0 and it runs great. When I run it with -50v on all the steps except for 1000mhz it works fine, but CPU Spy never shows any time spent on 100mhz, instead it shows 'Deep Sleep'.

Also, my ASOP unlock pattern screen seems to have issues where parts of the screen are way too sensitive and it takes multiple tries to get the swipe code in. Sometimes if I wipe off the screen with a cloth it helps for a little while. When I run everything at the stock voltages I never see the issue. It seems that my screen is overly sensitive on the right side for some reason.
[Fascinate Android Development] kallell:
Exactly what i was wondering...

how can you tell if its worth going to 1.6?
[Fascinate Android Development] beray5:
UKB 2.0 + OTB v1.6

Preliminary 11 HR power usage result with plan daily use of slight OC'ed to 13000000, everything on except haptics and rotation disabled.

Total 4 calls, 3 emails, and net browsing for ~1 HR and 10 HRs of idle.
[Fascinate Android Development] kallell:
Thanks, but i specifically meant going from 1.5 to 1.6, seems the only change was for those who had problems with the kernel not saving voltage states
[Fascinate Android Development] beray5:
There isn't anyway to read back the CPU core preset voltages.

If that ever was possible then you would not need to manually set them ever, because it also meant automatic LLC (load line calibration) by Samsung would be implemented through using the voltage feedbacks for load line calibration. It would work just like desktop CPUs, all you need is setting a CPU voltage number and the auto calibration would generate and fill in all other numbers required.
[Fascinate Android Development] kallell:
What. Benchmark tools are those? Linpack and what else?
[Fascinate Android Development] beray5:
1.5GHz Neocore, Smartbench, Linpack, and Quadrant -> http://xdaforums.com/showpost.php?p=14478825&postcount=887
[Fascinate Android Development] JWFokker:
I've also found that I need to bump the Internal by .50 to get a stable overclock above 1GHz. Interactive governor gives me the most trouble too. Using On Demand 200-1400 currently.

MIUIWiz 1.1 ROM - OTB Reloaded 1.6 TW kernel - ED03 radio - XDA App
[Fascinate Android Development] AuroEdge:
My phone won't go into deep sleep at all

Edit: It won't go to sleep when plugged in but will when unplugged. Weird?
[Fascinate Android Development] nemesis2all:
Not weird. That is normal operation.
[Fascinate Android Development] jpolzner:
Does this kernel have the hotspot AP dummy code in it? I didn't see it in the list of features.
[Fascinate Android Development] Sc0tt777:
I like to under clock to 900 mhz but I don't see that option in the latest release. I have to go back to v1.3 to have that option in the power control app. Can it be put back in?
[Fascinate Android Development] BeeDubs:
Are you running OTB-1.6 ?

Guys,

What's the consensus on most stable/best battery life? OTB 1.6 or 1.2 ?

I get SoDs frequently. I think I'm on ComaVolt but want to try a different kernel.

And it seems like I should use TegraK instead of Voltage Control, right?

Can someone who is getting better than 15 hours battery life please post their voltage/freq settings? (including what kernel)

Thanks!
[Fascinate Android Development] ssewk2x:
Hey,

I ran otb 1.6 for a couple weeks, and had some issues with it, mainly that my bluetooth was flakey.

I went back to the 1.5 version that comes with the comRom 2.0 and things have been very good. I get 20+ hours of battery life with moderate to heavy usage. I know I posted my settings before, but here they are again. States I don't list are disabled:

1400mhz, -25mv

1300mhz, -25mv

1200mhz, -25mv

1000mhz, -50mv

800mhz, -25mv

600mhz, -50mv

400mhz, -50mv

200mhz, -50mv

Cfq scheduler. Conservative governor. Anything else for those two settings makes my phone wildly unstable.

One other thing I noticed on both 1.6 and 1.5 is that occasionally something would keep the phone awake 100% of the time. It happened more often on 1.6, though. Spare parts would report a wake-lock held by "android system," and a reboot would allow the phone to sleep again. I haven't been able to get a good logcat for that issue yet. But, this might be happening to you as well if you're experiencing sub-par battery life.

Good luck.

Edit: I use the latest voltage control from the market, btw.
[Fascinate Android Development] xcoryedgex:
Stupid question. Just wanting to make sure though. Since I've seen people talk about using OTB 1.6 with UKB 2.0, would it still be okay to use OTB 1.6 with UKB after I flash 2.1 over 2.0?
[Fascinate Android Development] saps:
Yes
[Fascinate Android Development] xcoryedgex:
Awesome. Thank you. Oh and, I've been having problems with roms. I'll flash it, get everything set. Like ringtones, volume, TSM parts, etc. Then if I turn my phone off, then back on, or it dies and I turn it back on, or reboot it, basically any way that the phone is off then on, all settings are like, reset. Is this because of using the wrong kernals? I don't over or under volt ever.
[Fascinate Android Development] Smitty9803:
What recovery are you using?

I was having the same issues until I flashed a newer CWM3 and then all was solved.
[Fascinate Android Development] kuronosan:
I'm still getting the super sleep of death.
[Fascinate Android Development] BeeDubs:
Should I run setcpu? It can't seem to access root for some reason.
[Fascinate Android Development] ssignature:
I'm Lovin' It

This kernel is the biggest improvement to performance and especially battery life for me yet! Two requests-- +1 on the non-OEM battery fix and Adrenalyn had some kernels with a patch to the Samsung SMS that would split txts longer than 160 characters instead of converting to MMS. Not being a dev, I would think first that this would be a ROM thing, but I lost it in SC 2.9.2 when I flashed this kernel.
[Fascinate Android Development] dricacho:
An hour and 10 minutes after I flashed the updated SV kernel, my phone locked up. I did a battery-pull and my phone came back on. Since then, no lockups so far. I'm using CPU tuner set to conservative. Not sure if CPU tuner is causing issues but I have used this app before with older OC kernels and never had any lockup issues except for UV kernels.
[Fascinate Android Development] grenade01:
Initially I couldn't even flash it or any kernal for some reason... Re odined my recovery even though I had superclean 292 which comes with recovery (strange)... so I finally got the kernel my phone...

I was having all sorts of weird problems, but I think it had nothing to do with the kernal. I think the kernal was just somehow bringing out the fact that my flash was garbage.

I removed voodoo and restarted from stock, upgraded to froyo, upgraded to superclean ALL TWICE actually... wiping everything both times

Somehow, whatever was messed up was finally fixed (not the first time around though weird)

anyway after all that rigamarole its running super awesome now on the overclocked/undervolted.

Even though my phone seemed fine until I tried to install your kernel... I'm glad i allowed me to discover something was fubar.

Anyway thanks for the hard work.
[Fascinate Android Development] meowcats:
I see you have CIFS... any chance of adding NFS too?
[Fascinate Android Development] jbjarko:
I fixed mine after i read something in some other thread. Do you happen to use YouMail?

I did, and that was the cause for my SOD issues. Been running 2.9.2 and JT's latest kernel with no issues for a day and a half now.

Josh
[Fascinate Android Development] tapout27:
When can we expect support for non-OEM battery use in this kernel??
[Fascinate Android Development] nemesis2all:
To those requesting features the first thing I am working on is a 13 step kernel to 1.6 ghz. When that is stable I will add in more things. It is currently booting. Will have steps for 1.1, 1.2, 1.3, 1.4, 1.5, and 1.6.

I am watching the thread and am following the issues and requests.
[Fascinate Android Development] vdelsan:
awesome job can't wait
[Fascinate Android Development] Spaniard85:
Jealous of the 1.6 OC on the Thunderbolt? :P
[Fascinate Android Development] nitsuj17:
u mean the overclock that makes ur battery so hot its unusable?

if you have something constructive to say for a phone you no longer have..great...

if your gonna troll gtfo
[Fascinate Android Development] nemesis2all:
Do not have youmail. PM me or catch me on irc.
[Fascinate Android Development] jbjarko:
I was trying to help out the other poster. Youmail was the root of my issues, I'm good now :)
[Fascinate Android Development] saps:
The uber kernel, :D sounds like a dream. I should get back into the irc loop so I can beta test again :p

Looking forward to this next revision kernel guru ;)
[Fascinate Android Development] minsung0315:
No, not really.
[Fascinate Android Development] kuronosan:
Had TouchDown for Android 2.0 running as a WakeLock on my phone... is that safe to remove? I think it came as part of Nitro's HC theme.
[Fascinate Android Development] Spaniard85:
Sorry guys, I'm not trying to troll. I was merely razzing a buddy of mine. vdelsan and I are coworkers, and in fact I actually still use a rooted Fascinate as my work device. I have/had no intention of bad talking this amazing device, nor the fantastic development that is taking place for it. If you check out my history, I'm sure you'll see my previous posting in the Fascinate forums.

As for the TB, I'm aware of the "not for prime-time" status of the kernel I'm using. I was just having some fun fellas, and am looking forward to this kernel for the SF and kaoscinate v6.

Again, sorry guys. Not trying to get anybody's panties in a twist.
[Fascinate Android Development] dricacho:
Almost 24hrs into the SV OC kernel, my phone locked up twice requiring a battery-pull. I am running CPU tuner at conservative setting. I am also using Blackhole 4.3 ROM. Perhaps, I will try the latest SC ROM with this kernel and see what happens.
[Fascinate Android Development] nickfury718:
Was running 2.9.2 non voodoo. wiped cache, then dalvik, then flashed the kernel.

Was a bit laggy at first, but after a few reboots (4, maybe 5) it's running very smoothly with overclock and undervolt. Never had sod issues, there is the occasional lag with swype (any particular reason for this? anyone else experiencing the same thing?). Other than that, butter.

Thanks nemesis!!
[Fascinate Android Development] xcoryedgex:
I'm using a CWM3 from times_infinity. It's the orange though. Not one of the colors.
[Fascinate Android Development] GrainOsand:
Holy sh*t! Orange is no longer a color. When the Fu*k did that happen. I gotta get off this site. I miss all the big news!

Trollin in my 5.0!
[Fascinate Android Development] dc iz 2 legit:
Can i flash this with stock edo4 rom
[Fascinate Android Development] jselden:
I have been having a problem for the past two weeks. I had the GB leak and the flashed back to DL09 and ota up to ED04. Then i flashed this kernel. Then did a nandroid restore and all last week I kept getting lockups and the screen would report Kernel Panic Upload Mode.

Last night I redid this all again and then flashed 1.6 Kernel. then debing debloated ROM. Then did a Nandroid restore. I tried to reboot into recovery just a few minutes ago and again got the Kernerl Panic Upload Mode.

Any help would be great.

I am running ED04 Debinged Debloated with sbrissen mods(5/20 i believe) and 1.6 OTB Kernel. Also I have Voltage settings all set to default with it over clocked to 1200Mhz (-25) and Voodoo is enabled.

This all started when I got off ED01 and went to ED04.
[Fascinate Android Development] landshark68:
When you say you are doing a nandroid restore, do you mean you are doing a nandroid backup? Because if you are doing a restore, you are wiping away everything you just did before it. A nandroid restore restores your entire system except modem and kernel to the exact setup you had at the exact time you did the nandroid backup. So if you did the nandroid backup a week ago and were running the stock build, you just restored the stock build over the debinged/debloated ROM. If your nandroid is of a debinged/debloated ED04, then you are fine. But if your nandroid backup was from a while ago, you may be carrying over previous problems and bugs. So it sound more like it may be a problem with something else in your set up rather than this kernel.
[Fascinate Android Development] Codiusprime:
The heck, wrong thread. Don't know what happened.
[Fascinate Android Development] jselden:
Thanks for the response.

Yes I do realize that a nandroid restore would overwrite all the settings I had. It was a previous backup I had when i was on 2.2 Baseband ED01 that I was restoring to. But now after the restore in About Phone it says that I have Base band ED04 and Build ED01. And I have the OTB 1.6 kernel Flashed. I do not know if something changed in the ED04 that is effecting this, it ran so smoothly when I was on ED01. It actually happened to me again and I wrote down the message on the screen as it gave me a bunch of IRQs however that was at my work and I do not have them with me.
[Fascinate Android Development] landshark68:
That's weird. Sorry I don't have an answer for you. I was running the ED04 modem on Comm ROM until the EC09 modem became available. There are just a few other people I have seen with that error message. Not sure if all of you previously flashed the EC09 leaked ROM or some variation.
[Fascinate Android Development] jselden:
I think I might just upgrade to the commrom. I do enjoy the touchwiz launcher though but since GB leak I have been having problems. Thanks again though.
[Fascinate Android Development] dhouston10:
Excellent!
[Fascinate Android Development] Skrazz:
Just made this leap. Quite pleased! Just make sure you do your wipes. Wipe voltage settings and cache after flash as well. This cleared any issues I had previously.

Sent from my SCH-I500
[Fascinate Android Development] andrew1263:
Sorry if it's already been posted, but what recovery does not have the data wipe "freezing" problem? I'm not sure which one I'm running but it's a red 3.0 OTB one.
[Fascinate Android Development] ezas:
3.0.x recoveries do not freeze on data reset. That includes the recovery from times_infinity. FYI the ones that freeze work they just freeze on the last step of a data reset.
[Fascinate Android Development] scarmon25:
I'm using the otb 3.0.2.8v2 and haven't had a single issue. I've got it in my dropbox if you want it. I believe navendrob put it together.

Tap-a-Talked from my Mesmerize
[Fascinate Android Development] Skrazz:
And apparently the freezing is after completion of the wipe.

Sent from my SCH-I500
[Fascinate Android Development] Syndacate:
Hey,

I'm not too familiar with only kernel flashing, so please don't shun me for this.

I'm using the OTB 1.5 that came with UKB 2.0, to upgrade to 1.6, can I just:

- Clear dalvik cache

- Clear regular cache

- Clear voltage settings

- Clear battery settings

- Turn off - pull battery

- Start in download mode

- Use odin to flash the 1.6 OTB image

- Put battery back in and restart a couple times

Or do I need to do something additional?

I'm thinking of possibly changing the clock, seems the 1150/1200 is pretty popular as a stable setup, I'm not looking to hit super high bench marks or anything, I just want awesome fast UI response :). Though I suppose not if it rapes my battery.

I guess the only question I have is the what does "-50mv" mean? Like I get "what" it means, but 50mv from what? It seems to be independent of the internal voltage... (*waits for flames telling me to search and not be a newb and how I should know everything - always!*)
[Fascinate Android Development] scarmon25:
All you do is clear dalvik and cache. Voltage settings clear them as well. Then flash in recovery. That's it. No odin :)

Tap-a-Talked from my Mesmerize
[Fascinate Android Development] Syndacate:
Oh, it's something that can be flashed by CWM, guess that works fine, too.

I'll have to do that tomorrow - thx.

EDIT:

I'll probably be back in here at some point tomorrow complaining about my phone being FUBAR'ed because I didn't know something, lol.

I don't have to disable lag fix or anything like that, right?
[Fascinate Android Development] scarmon25:
If your on a voodoo kernel and flashing a voodoo kernel then no you don't. Voodoo over voodoo is fine. :)

Tap-a-Talked from my Mesmerize
[Fascinate Android Development] Syndacate:
Yeah, that's what I heard somewhere. I'm on OTB 1.5 so it should be fine.

I just figured I'd run into problems when I do it - that typically happens, lol.
[Fascinate Android Development] scarmon25:
You shouldn't. But if ya do just let us know. Should be able to fix it.

Tap-a-Talked from my Mesmerize
[Fascinate Android Development] Syndacate:
Thx =)

---
[Fascinate Android Development] andrew1263:
Thanks for the help! I had the wipe issue before and it was annoying..
[Fascinate Android Development] Syndacate:
Seems to have gone pretty smooth, but is there any way to get confirmation that it was installed?

Now, I just got to figure out how to use voltage control, lmao. Are there any write-ups on that? Like I get that you can set the step for each clock...but what if multiple steps are set? Also, how long does it wait between steps? Blah, need a how-to on this thing >.<.
[Fascinate Android Development] scarmon25:
For verification. If voltage control says it confirmed then your on it. But you can download cpu spy and it will tell you what version your on.

For votlage control try these settings. I have used them for a good while and they are pretty stable. Don't set anything as boot settings until you know they are good. Meaning you have ran them for at least a day or two without issues.

Scheduler CFQ with conservative set

Steps enabled (meaning green in new voltage control app) and there settings

1200 -75mv

1000 -75mv

800 -75mv

600 -75mv

400 -75mv

200 -75mv

I have used these for a good while without issue. That's a good starting point. And can play with it from there. Hope that helps ya.

Tap-a-Talked from my Mesmerize
[Fascinate Android Development] scarmon25:
As for multiple steps. You can generaly have up to six steps enabled at the same time. Doesn't mean they all are running. Just means that those are the predetermines clock speeds. Meaning the cpu won't run at 1120mhz. It will run at 1200mhz instead. depending on the work load depends on how long it will stay at that speed. Also 100mhz is disabled in the kernel.by default. If you choose to use that step you will have to boot into recovery and enable it under advanced.

Tap-a-Talked from my Mesmerize
[Fascinate Android Development] Syndacate:
That worked like a charm, thx. Nice little observation program, too.

Yeah, I know not to set them as default until you're 100% sure they're stable, but that's about all I know, lol.

Also, if they became unstable and you set them as default, and now the phone won't boot (I'm guessing that's the issue at hand), can't you just clear the voltage settings using CWM? Because the CWM recovery doesn't use the installed OS kernel.. People just making it sound like your phone is bricked, so I was j/w.

Anywho, so what does that mean, it will step 75mv at a time to reach that clock?

So if multiple steps are enabled, does it just pick one to use depending on what CPU frequency it's aiming for? :-\, I'm just confused as to how the system works, I guess. I would think it's more of a matter of: insert input voltage, set clock speed, sometimes you need to bump the voltage more for a higher clock - like it is with regular CPU's, though I haven't OC'ed my CPU's that much, just my I7, where I just bumped the multiplier (as I have a locked multiplier) until I got a CPU freq that I wanted where it was running stable - didn't want to overvolt it.

So I guess a format I would comprehend better would be:

- This is Q, it does/means X, Y, and Z, turning it up means R, turning it down means S

So there's sliders at each frequency, but then there's also a max. I would expect to just change one step which is the step to that max. Also wondering where the minimum, is.. So I guess what does each slider at each frequency mean..maybe is my final question?
[Fascinate Android Development] scarmon25:
The sliders are the voltages for each step. By putting them at -75 you are saying to the phone when at this step use thos votage and save battery. The phones load determines which step to use. So of you have a max freq set at 1200 and have six programs open the phone will auto bump itself to 1200 till some of the load is taken off.

In votage control under the first tab. The two sliders are min and max freq. That means the phones cpu will not go lowe then. 0.2ghz and not more than 1.2ghz. Now this also doesn't acct for deep sleep"phone locked with screen off" so even though the min is. 0.2ghz it will still go into deep sleep which you can see in cpu spy

The second tab is voltages per step. That is your battery savers. By hitting the green/red dots you enable/disable those steps. Thos are the predetermined steps of the kernel. The phone will only run at those speeds. And by moving the sliders on each step you adjust the voltage for those steps. So with the settings I posted. You are saying you want to run each step at -75 milla volt under the stock voltage. And that only those siz clock speeds can be used. Depending on what type of load is on the phone. Depends on what clock speed to use. It will switch between them on its own. All you have to do is tell it which steps it allowed to use and at what voltages to use them. Hope that helps

Tap-a-Talked from my Mesmerize
[Fascinate Android Development] Syndacate:
I think we're either talking about different apps or different versions.

I'm using VC 3.0.3 - there appears to be no tabs.

I see the 1500Mhz - 100Mhz, and the mV rating next to it, and the amount you're pulling from it as a slider - so I'm guessing for each clock you can pull Mhz from it (undervolt) to save battery. Guess the question comes about how much voltage can you pull from each clock before it becomes unstable...I'm guessing that is typically -50mV across the board and -75 on some phones/clocks? Are there any general rules for undervolting (ie. as the clock goes up, you can generally not pull as much from the voltage?).

Then this version also has like a check box, as to which clocks to use.

Though this just has the scheduling algorithm and the max clock, it doesn't appear to have the minimum clock. I guess that's controlled by the "states" drawer - but then it begs the question of why have a maximum, the tick boxes in the states drawer already handle the maximum like they do the minimum.

Thanks a lot for your explanations, that helped a lot, I think we have different versions, though.

I'm running the specs you suggested, and did a benchmark with atutu or whatever it's called, everything seems stable. This benchmark kind of sux because it requires all specs to be tested to score good, but like, my SD Card R/W will not be good because it's the OEM one (which is a pretty low class IIRC). Is there anything that shows like, a breakdown by clock?