yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] CrucialBT:
Would you mind explaining what you changed in terms of voltage? Only because after extensive testing it seemed my phone would reboot randomly even when I had all the voltages set to 0. Also how do you test stability on your own phone. I'm curious how a dev tests it, as it has to be a better method than mine is.
[Fascinate Android Development] nemesis2all:
OP updated
[Fascinate Android Development] TheSonicEmerald:
1.6ghz here I come!!! Awesome Nemesis!
[Fascinate Android Development] bobloblaw1:
1.6? 60% oc? I predict "human sacrifice! Dogs and cats living together! Mass hysteria!"

Seriously amazing that you can push the chip this far.
[Fascinate Android Development] TheSonicEmerald:
Lockups in the first min, and root is lost. Hmm....
[Fascinate Android Development] nutrulz:
edify

I have to agree with wanting to keep up with the newest thing, meaning Edify scripts.

With that in mind, does anyone have an edify zip to flash to CWM 2.5.1.x and/or the latest busybox (1.19 I think)?

These would be extremely helpful for some.

But do continue with the edify scripts. It pressures other devs to move in the right direction.

Thanks!
[Fascinate Android Development] beray5:
Reporting.

100MHz permanently disabled even when 100MHz state was toggled back off and on again.
[Fascinate Android Development] nemesis2all:
Did you read the main page about enabling 100 mhz?
[Fascinate Android Development] beray5:
Yes I did, manually edit "scaling_min_freq" works but do not retain setting on reboot.
[Fascinate Android Development] vdelsan:
Can anyone please show me the correct steps to flash this new kernel but I do not want to be stuck on cwm3 since devs are still using cwm2 to flash themes and roms thanks:-)
[Fascinate Android Development] nemesis2all:
I'll see if that can be taken care of on a future release then. Need to get these mount issues worked out so people quit losing root, and that would probably fix that as well. I do not have the know how to get that done tho. I'm lost in the initramfs and new mount.wrapper. Hopefully jt will work on it some more.
[Fascinate Android Development] dfgas:
how much talk time did you have on it? over 14 hours is nice and thats what i am looking for.
[Fascinate Android Development] dfgas:
was that only in recovery they are having the issue? cwm3 if so is that why you removed it?
[Fascinate Android Development] wideopn11:
1.3 seems stable for me but my phone locks up at anything over that almost instantly. Is there anything I can do to push it to 1.4 or 1.5 or is my phone just not going to take it.
[Fascinate Android Development] vdelsan:
Thanks for the reply so just to be on the same page flash new kernel under cwm2 and by doing so will that auto give me cwm3 and new kernel... but before reboot flash 2.5.x zip right thanks:-)
[Fascinate Android Development] akellar:
If you don't want cwm 3 just use sgs kernel flasher from the market. It's simple to use and worked fine for me. It only flashes the kernel itself.
[Fascinate Android Development] bwheelies:
Yes.

running on premium!
[Fascinate Android Development] beray5:
That package do not have CWM3 period, you just flash it as any other CWM2 package.
[Fascinate Android Development] nemesis2all:
I didn't include cwm3 this time because i flashed with cwm2.5 and ran into the issue of not having root. With cwm2.5 mounting system and flashing su zip allowed me to get root access back. I didn't test with cwm3 so I left it out for the time being. It is difficult for me to test every scenario people will run across. My testing has only been done with this kernel from a stock odin to eb01.
[Fascinate Android Development] vdelsan:
Thanks for the info guys
[Fascinate Android Development] Jmatch:
if we only try the 1.6 overclock it cant hurt ur phone instantly can it sorry if this is a dumb or answered question
[Fascinate Android Development] jkat797:
Why do I keep flossing root when I flash this? And fixes?
[Fascinate Android Development] PeterGunz:
For those of us unable to achieve the 1.4 and 1.6 OC's and that are using something smaller like 1.2 or 1.3, would it be in our interest to flash the 4/14 kernel? In other words, would it be more stable for us or do things that would make sense for us to flash it over the 4/12? Only thing I can tell that is really different for the lower end is the extra step and lower voltage on 1300 and I am unsure how much that will affect me (1200 OC).
[Fascinate Android Development] bwheelies:
I have tried it and it locked instantly. My phone still works fine.

running premium
[Fascinate Android Development] bwheelies:
Maybe try using super one click or z4root.apk. I think those give permanent root options. I have not lost root yet.

running premium
[Fascinate Android Development] Jmatch:
Thanks
[Fascinate Android Development] DevinLeFevere:
Does anyone have CWR ver. 2.5? I already booted using 3 and I can't revert back. I've tried using the SF TW OTB cwr2.5 kernel, but I still get the edify warning.
[Fascinate Android Development] shorttripp86:
Flash this via ODIN (in PDA):

http://adbdev.com/danknub/cwm-recovery-ALL-3-30-FIX.tar

Then d/l sgs kernel flasher from the market, and use that to flash any new kernels that have cwr 3. This will keep the new cwr from being installed.
[Fascinate Android Development] DevinLeFevere:
Thanks man!
[Fascinate Android Development] suppliesidejesus:
4/14 Kernel Voltages

4/14 Voltages

Update 1:

I have upped the 800 MHz setting, as I feel like that one is often one that causes instability if it gets too low. All other steps should be the same.

Hey all, thought I would make a new post for this. I have updated my voltages and steps for 1300 MHz with the advent of the new steps. I cannot get 1400 MHz running at all since it has been limited to 1300mv with the 4/14 kernel. If nemesis2all bumps this value back up to 1375mv, I think I can get it stable again and post those settings as well.

As you will see below, I have added in a conservative voltage setting for 100 MHz (in the past, it was not stable for me at 850mv) to try and eek out some more battery life. Here are my settings for 1300 MHz:

[U]1300 MHz[/U]
1300 MHz || 1300mv ( -0 from default)
1200 MHz || 1275mv (-25 from default) drops 25mv
1120 MHz || 1250mv (-50 from default) drops 25mv
1000 MHz || 1225mv (-50 from default) drops 25mv
900 MHz || 1200mv (-75 from default) drops 25mv
800 MHz || 1175mv (-25 from default) drops 25mv
600 MHz || 1100mv (-50 from default) drops 75mv
400 MHz || 1000mv (-50 from default) drops 100mv
200 MHz || 900mv (-50 from default) drops 100mv
100 MHz || 875mv (-75 from default) drops 25mv

Enjoy!
[Fascinate Android Development] bwheelies:
You are using 9 steps successfully?

I know it is subjective but are you getting decent battery life?

Thanks in advance.
[Fascinate Android Development] cvs0115:
suppliesidejesus, I used your configuration and built a 1400 MHz with 7 steps.

1400 MHz || 1400mv ( -0 from default)

1200 MHz || 1275mv (-0 from default)

800 MHz || 1150mv (-50 from default)

600 MHz || 1100mv (-50 from default)

400 MHz || 1000mv (-50 from default)

200 MHz || 900mv (-50 from default)

100 MHz || 875mv (-50 from default)

My Quadrant Score is between 1900 and 2000.

However I'm not sure how it will affect my battery and how stable it is. I'll run it for a few days and let you know.

Thanks suppliesidejesus, nemesis2all, and all.
[Fascinate Android Development] akellar:
Just thought I'd share my setup. Still running the 1.0b version.

1300 Mhz:1325 - 50 = 1275mV

1200 Mhz:1300 - 50 = 1250mV

1000 Mhz:1275 - 50 = 1225mV

800 Mhz:1200 - 75 = 1125mV

600 Mhz: 1175 - 75 = 1100mV

400 Mhz: 1050 - 100 = 950mV

200 Mhz: 950 - 100 = 850mV

Been running for almost 2 days now and completely stable. Battery life has increased an estimated 30% over Comavolt.
[Fascinate Android Development] suppliesidejesus:
Yes, aside from one freeze (which I think was caused by my 800 MHz setting) it has been fairly stable. I don't have any info on battery life with these settings, as I will be plugged in until the morning (double today...woot). I'll update with my battery life once I've had a chance to test it.
[Fascinate Android Development] dalrym05:
Do you plan on releasing some with higher voltages for anything about 1.4?
[Fascinate Android Development] vicous707:
i cant even get to the app :( after the memory scans the sd card my phone just freezes..... Im using a mesmerize btw. but i can clock it to 1400 ghz -25mv on the older version of this. It runs perfect too. Can u plz fix it :) thank you for sharing ur HARD WORK!!
[Fascinate Android Development] xHoLyx:
App Freeze happened to me too
[Fascinate Android Development] dricacho:
My phone locks up an hour after over-clocking to 1.3ghz and beyond. I've tried the 04/09 kernel and tried many combinations of voltage and clock settings but my phone just can't deal with anything over 1.2ghz. I tried wiping the cache before reflashing this kernel to no avail. I don't wanna fry my phone since I've already fried one before, I'm on my second Fascinate. And I have noticed the phone getting noticeably warmer to the touch when over-clocking. So I went back to the 04/07 kernel and my phone is happy and stable at 1.2ghz, conservative governor using SetCPU. I'm pretty much staying here and I don't really see the point of trying the newer kernels that OC's even higher. It's pointless for me, I don't think Verizon will give me another replacement phone if I fry this one.
[Fascinate Android Development] suppliesidejesus:
If you are experiencing freezes upon boot after flashing the new 04/14 kernel:

WIPE CACHE IN CWR AND FLASH THE KERNEL AGAIN!

This will wipe out your current voltage settings. That needs to be done going from one of the older kernels to this new one. You should be able to get into the app after that.

If CWM3 gives you an error after you wipe cache about RFS, ignore it, as it means nothing (voodoo users will get that error).
[Fascinate Android Development] NOsquid:
Wow, what do you mean by fry exactly? How did it happen?
[Fascinate Android Development] BrwnSuperman:
There is a reason why it's called OTB.
[Fascinate Android Development] PeterGunz:
Edit: In reply to SSJ

Can't wait to hear how it goes as you are the only person posting a log with that many steps!

I am too stable at 1200 on the last kernel to jump to the next one without some more feedback first.
[Fascinate Android Development] CrucialBT:
Peter, I jumped last night and so far my phone is much more stable already than the last kernel. (I'm the one who responded to your post on the androidforums about this) as a matter of fact, i think I was able to uv some steps more than before and that's accounting for nemesis' default increase on some voltages.
[Fascinate Android Development] dricacho:
No sh1t! I was brave enough to burn out my first one but not the second one. I'd rather spend my money on a newer phone if I was to pay full retail again. :)
[Fascinate Android Development] ssewk2x:
Latest kernel is unusable for me. Freezes as soon as media scanner hits the sdcard. I did wipe cache and dalvik (or however it's spelled).

1.4ghz is way faster than I ever thought this POS would run, so I'm gonna stick with 1.0b for now.

Thanks!
[Fascinate Android Development] dalrym05:
I think the voltages are to low on the 4/14 kernel. I can almost run 1.5ghz but its not stable. Bring voltages back up to 1375 for anything above 1ghz-1.4 and need voltages like 1450mv above 1.4.maybe it will give people more range to mess with.

Very good work every kernel has worked good for me so far. Keep up the great work.
[Fascinate Android Development] Domush:
Thank you for removing CWM3.. makes it easier. Great kernel so far.
[Fascinate Android Development] CrucialBT:
Nemesis, my man. I love this kernel. I love being able to tweak my settings to what's optimal for my phone.

Now I just wish my phone was capable of lasting more than 45 seconds at 1.3 Ghz. 1.2 Ghz works perfectly at 1250, but I can't even get 1.3 to stick at the full 1300. I tried 1500 just for giggles and it froze up on me soon as I hit the apply button. :)

A big thank you for everything you've done and whatever you will do with this kernel.
[Fascinate Android Development] 123SIT:
+1 on this because I was able to run 1.4ghz before the 4/14 kernel, but now I can't. Regarding the 1.5 and 1.6 cycles, I lockup every time. Regardless, nemesis great work on everything you've done and to all the other devs who made this possible.
[Fascinate Android Development] suppliesidejesus:
I seeing a lot of the same sentiment in a lot of the last posts about the new 1500 MHz steps and 1600 MHz steps, and I tend to agree. As far as I can tell, 1500 and 1600 are just plain unusable unless we can get the voltage higher, and many people can't get 1400 MHz stable without running it at 1375mv. Some can't even get 1300 MHz running at 1300mv, which is the max limit in 1.1b.

My suggestion would be to axe 1500 MHz and 1600 MHz in exchange for new steps at lower speeds and up the max voltage for 1300 MHz and 1400 MHz once again.

Just my two cents, running 1.1b with 10 steps stable. Love this kernel!
[Fascinate Android Development] rsswga:
Everything is good but phone freezes when closing video recorder

???
[Fascinate Android Development] stephenj37826:
I would like to see the higher voltages on 1.5 and 1.6. I can run 1.4 at the new voltage I can almost run the 1.5. I think the higher voltages would be fine. I'd also like a setcpu friendly version. I don't use screen off profiles but I used the temp one back when I was overclocking my vibrant to 1.4. Worked like a charm. If battery temp hit 105 it would scale down to 1.0. Out only got warm when I was charging it and I would get a phone call. Started unplugging it when in call.

Once again thanks for everything you do for us all here.
[Fascinate Android Development] vdelsan:
So...would also love to see this kernel be used on setcpu cause of the different profile for adjustment
[Fascinate Android Development] zantopad:
To fix the video recorder sound issue, use the voodoo control app (free in the market), under microphone presets set your recording preset to "original". This worked for me.

NOTE: This will let you record audio with the video camera, but will not let you use the other audio recording presets (obviously). Until supercurio gets a fix for voodoo sound this is probably all we can do.
[Fascinate Android Development] cpark_12:
I guess mine didn't like it...it froze up twice after I cranked it up to 1200!
[Fascinate Android Development] xHoLyx:
If anyone posts that this kernel improves the phone,

I will flash it, until then, JT is the BOSS. :D
[Fascinate Android Development] garywojdan81:
Thanks man. It worked for me too.
[Fascinate Android Development] cvs0115:
Great work... The fascinate is much more responsive... I'll post battery depletion rate in two or three days.
[Fascinate Android Development] saps:
Fabolous work as always nemesis2all. This thread brought me out of a slumber on the fascinate. Currently running this kernel. Looking forward to further reductions in voltage as well ;).

BTW, I also had the aforementioned bootloop the first re-boot. I pulled the battery and was golden on the 2nd boot, fwiw
[Fascinate Android Development] boostedjti:
No boot issue for me with this.

This makes me miss dj05 that much more. Thanks for all your work!
[Fascinate Android Development] bL33d:
No boot issues and not useing setcpu as it seems more trouble then its worth... Got 1680 quadrant and running very snappy. thanks.
[Fascinate Android Development] jthompson0019:
Liking so far. Battery life has been okay but I have also been a heavy (ab)user today plus my wife pulled my phone off charger a hour and half before I woke up, She won't do thy again,because it was going off. So it vibrated and lit up the whole time. So time will tell.
[Fascinate Android Development] NOsquid:
Great, thoughtful contribution :rolleyes:
[Fascinate Android Development] theGross1:
My phone went to sleep never to wake up. Might be do to overclocking
[Fascinate Android Development] boostedjti:
Back on dj05 I learned that not all phones can handle overclocks and undervolts the same. I used them to feel out how my phone responded to it... It could be either one of which for you, not really certain.
[Fascinate Android Development] neyenlives:
yeah, boot into clockwork recovery and flash the nandroid backup you made before flashing this kernel, your CPU probably isnt stable at 1200Mhz, many aren't, especially at -50mV
[Fascinate Android Development] s44:
One of you guys want to try integrating supercurio's latest Voodoo Sound v7 for the Fascinate before jt gets around to it? Curious to see if it fixes the occasional call sound issue.

nm: checked the git and it looks like jt's base *is* v7
[Fascinate Android Development] dricacho:
Just flashed this, so far so good. Using CPU Tuner set to conservative.
[Fascinate Android Development] theGross1:
I'm familiar with that as well. It does appear to be overclocked related. After a battery pull and reboot, I've had no problems at stock freq. I did hit 17+ on linpack.
[Fascinate Android Development] Syn Ack:
The overclock works just fine on my phone. Once my phone hits 1.3Ghz though, it starts locking and acting up. So 1.2 is perfect.
[Fascinate Android Development] nemesis2all:
An updated kernel is incoming shortly. Will have cifs and some other things. Sorry for those of you that are experiencing issues with the oc. Not all phones are the same when it comes to oc. In the future I want to try to add bfs, adjust volts if necessary, add more freq steps, and other misc tweaks.
[Fascinate Android Development] saps:
Still chasing the uber kernel ;)

New kernel ideas look good. I know some struggle with the OC and or UV but there are some of us who can tolerate a tad more OC or UV as well, especially on those lower steps for the UV
[Fascinate Android Development] stayin100:
No 3g data connection for spme reason... Any ideas?
[Fascinate Android Development] nemesis2all:
Setcpu version isn't going to happen. The way the steps work isn't compatible with setcpu. I am working on a new version from ground up. Hopefully will be ready by end of next week. Taking my time on it. Hopefully everything will be as close to stable as a kernel like this can be when released.
[Fascinate Android Development] saps:
Sounds excellent I have no doubt it will be worth the short wait.
[Fascinate Android Development] Snyperx:
Since I am looking for battery life rather than a 2GHz cell phone, what are the recommended voltage settings when undervolting?
[Fascinate Android Development] dalrym05:
Every phone is different you really just have to play with it. My phone personally is undervolted -100mv from 200mhz all the way to 1000. But I keep overvolt on speeds above that.
[Fascinate Android Development] saps:
The above are my fail safe voltages. That is, this above voltage profile is 100% stable for me. Please note I do not use the 600 and 1120 steps.

I have tried dropping every value by -25mv more than the above shown and something is amiss there. I have not made the time to individually test each step to determine which can and cannot take -25mv more uv than shown. I can run imnuts -100uv kernel so I think I should be able to run 1000-200Mhz at -100mv and maybe just keep 1200 and 1300 where they are. But I haven't bothered testing it. What I have listed above really is super on battery life and all the speed I need.
[Fascinate Android Development] nemesis2all:
op updated w/ OTB-Reloaded
[Fascinate Android Development] bigmike88:
is the ed01 radio a must?

Edit: really loving this kernel after about an hour ish...thanks for the sweetness, god among men
[Fascinate Android Development] tapout27:
sweet im gonna give this a try...thanks

downloading now
[Fascinate Android Development] nemesis2all:
I've heard no reports of a certain radio being needed, but I would assume any of the radios from eb01 or newer should be fine.
[Fascinate Android Development] nemesis2all:
Also as far as 1500mhz and 1600mhz go I've seen limited reports of success using 1500mhz at between 1400mV and 1450mV. It will take a very good overclocking phone with lots of trial and error to hit 1500 mhz or 1600 mhz.
[Fascinate Android Development] scarmon25:
Just flashed over previous 1.1b. No issues. Lots new stuff in this one. As always thank you so much for your work. It is very appreciated.
[Fascinate Android Development] saps:
Awesome nemesis and sooner than anticipated.

Two questions since I havent flashed it yet.

You added bfq is that a replacement or addition to cfq scheduler. If an addition which do you recommend?

Have you thought of adding the SD speed tweak imnuts has?

I got a mission critical conference call in a couple hours so Im not going to tinker with this bad boy till after that.
[Fascinate Android Development] dalrym05:
Just flashed a little bit ago working great. I can run 1.5ghz at 1425 mv but it doesn't seem to be a benefit. Deffinately out of its efficiancy range. Sticking with 1.4 at 1375mv. Thanks for all the hard work.
[Fascinate Android Development] ssewk2x:
Grrr, the mediafire link isn't working. I click the "download this file" link and all it does is reload the page. Any ideas?

Thanks.

Edit: never mind, I got it.
[Fascinate Android Development] beefdog:
Just beat out tegra in gfx
[Fascinate Android Development] nemesis2all:
BFQ is an addition, CFQ is still there. I have tested mainly with simple i/o and it seems pretty good and snappy. You can switch and see what works best for your usage.
[Fascinate Android Development] heloguy:
I installed this kernel but my phone didn't like it. I re installed jt's kernal and now I lost root. Any ideas how to get it back?
[Fascinate Android Development] ssewk2x:
One small issue with this kernel. I have the 100mhz state disabled, but I notice it still gets used occasionally. At least according to the temp/cpu widget I'm using.

It does not seem to use states higher than my limit (1.4ghz).

Any ideas?
[Fascinate Android Development] nemesis2all:
My best guess is it is getting used some in boot process before voltage control and init.d have time to tell it otherwise. If that is not the case you can set min via adb. Don't have the command handy atm, but if you look thru this thread you should find it.
[Fascinate Android Development] scarmon25:
Got a question. I have been using the same settings for a good while now and wanting to set those a boot settings. In the event that something goes wrong. Would reflashing the kernel undo that setting and take it back to the default settings.
[Fascinate Android Development] nemesis2all:
You'd probably have to wipe cache to clear the settings and then re-flash kernel.
[Fascinate Android Development] ssewk2x:
I managed to figure out how to set it. Tried it, and it worked...until I rebooted. So you're probably right.

Maybe a solution would be to have VC update scaling_min_freq in the generated init.d script? Meanwhile, I can write a hackey init.d script to do it. I'm perplexed as to why the kernel seems to be ignoring the fact that the 100mhz state is disabled, though. I did verify that the file that does that looked right, too...odd.
[Fascinate Android Development] scarmon25:
That's cool. Honestly I don't think I will have any issues. Just wanted a backup plan just in case. Thanks for you quick reply. I've tried all of the EC10 kernels and by far this is the most stable and versatile one yet. Thanks for your work man.
[Fascinate Android Development] BeeDubs:
Is there a list of steps and voltages that would be considered the safest to use? E.g. -25 mv at 7 steps or something?

Sent with my thumbs.
[Fascinate Android Development] dalrym05:
Read the first post.
[Fascinate Android Development] dalrym05:
Just because this works for me doesn't mean it will for you but I Use...

400. -75mv. The rest stock.

800

1000

1200

1400

To many steps can sometimes be worthless. Just keep it in mind. If it doesn't lock up or do weird stuff your probably ok.
[Fascinate Android Development] Mubassmastajoe:
Sorry if this has already been answered, but is tethering safe on this kernel?