yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] dmasjz45:
Either kernel is undervolted too high at 1000mhz and locking up my phone, or maybe even the lower steps are too low? Or there is an issue with waking up from sleep, I can't tell which
[Fascinate Android Development] nemesis2all:
I will release one at stock voltz for those having issues.
[Fascinate Android Development] Hilbe:
Having some weird random freezing. Maybe I need a 1.1ghz slot?
[Fascinate Android Development] xHoLyx:
Quadrant Score has been widely accepted that it is not reliable and trustable.

I Saw someone posted picture with Score of 4xxx. LoL.
[Fascinate Android Development] mesmerbelly:
I know I know but will it work for mesmerise I used a 1400 oc/uv from dj05 and ran great thanks
[Fascinate Android Development] mrjake1970:
Thanks for this kernel.. Flashed with zero issues, been running it since mid afternoon with no bugs.. does feel and look quicker.. i don't have setcpu loaded at the moment, and i'm hesitant to install it again..

i wonder if some of the issues are with the setcpu or similar apps? i remember i toyed with the setcpu settings while on DL30 voodoo and i got the same symptoms some are getting with this (random crashes/freezes, sleep of death)
[Fascinate Android Development] cpark_12:
I'm with you...i ran 1.1ghz on dj05 with zero problems. Can this be done?
[Fascinate Android Development] Hilbe:
How many speed slots can we have? I'd be curious to see some with a 1.1ghz, 1.3ghz, and 1.4ghz slots. Maybe have ones with standard voltages, low voltage, and ultra low voltages.
[Fascinate Android Development] ChadZ:
Will this work with Evil Fascinate 3.4.2 ED01?

Do I flash this in CWM recovery?
[Fascinate Android Development] ChadZ:
Before I blow my phone away, can someone(s) suggest the best settings for both battery saving and also powerhouse?

Installed this kernel, voltage control is so far set to 1200MHz max. I didn't do anything else and have no idea what mv is, which is why I'm asking here first :D

Edit: which is the best free benchmarking software? I'm trying Quadrant and also AnTutu as well. I got 1492 in Quadrant (is that good?).
[Fascinate Android Development] nemesis2all:
Yes and yes
[Fascinate Android Development] ChadZ:
Yikes, need help.

Just applied this (and even saved as boot)

http://xdaforums.com/showpost.php?p=12801545&postcount=252

My phone froze on Quadrant benchmark.

Edit: got back in my phone for now. Recommendations appreciated :)
[Fascinate Android Development] suppliesidejesus:
Yes.
[Fascinate Android Development] tripacer99:
Has anyone here even been able to achieve 1.5 or 1.6 stable/tolerable? Just a bit curious.
[Fascinate Android Development] bhfd64:
I really just think it's some incompatibility with my particular phone and your kernel. I spent hours tonight playing with settings and taking dozens of pictures and it just will not work properly. My GPS doesn't like it either. My GPS actually only seems to like Adryn's EB16 kernel. I've preached so many times that each phone can react differently to a kernel, I think that's all that is going on here.
[Fascinate Android Development] stephenj37826:
My phone isn't liking this one as well. I could run up to 1.5 stable on the 1.2 otb reloaded but on this one I get freezes on 1.4 what has changed? I run 1500 @ 1375 anyway so what is dvinst voltage ?

I checked out the chanelog but I guess I don't understand lol.
[Fascinate Android Development] chrisexv6:
The default scheduler changed, so if you were never changing the scheduler previously, you might need to change back to what the old default was.

Im also noticing previously stable settings not working for me, but Im willing to toy around with it some more before calling it an issue.
[Fascinate Android Development] nemesis2all:
I could be wrong, but I believe the vdd int (dvsint) voltage is similar to voltage droop. Kudos to you on the cpu speed did not realize anyone was running at a speed like that regularly. I can bump it back up on next release if your instability is due to that.
[Fascinate Android Development] stephenj37826:
Oh its ok I'm back on 1.2otb but I rarely run more than 1.3. I just didn't know what that was. So was the dvinst lower or higher than stock before?
[Fascinate Android Development] nemesis2all:
It was higher than stock before. Stock is 1100 I had it set to 1125. I had not heard any complaints on oc until now when I switched it for ver1.3. So no big deal to raise it back up.
[Fascinate Android Development] stephenj37826:
Cool. Thanks for all these great releases so far. So how does that setting affect stability? Wondering if you bumped it higher could I get 1600 lol. I use setcpu to monitor temps and how I do it is I don't allow it su so it cant change anything. So far as long as I'm not plugged in the temps stay safe imho.
[Fascinate Android Development] beray5:
Too bad it isn't exposed for usage in Voltage Control app. :D

It works exactly as I mentioned here in this thread -> http://forums.anandtech.com/showthread.php?t=271760
[Fascinate Android Development] Daswolven:
Nemesis,

Keep going back and forth on these kernels. I freaking love what you've done here but have very little opportunity to test for solid stability.

The mute issue seemed to resolve when I upgraded radio, but I have occasional reboots in the middle of calls. Going to play with some settings today as I have some down time, but I was wondering if you were aware of a solid way to circumvent the reboot issue.
[Fascinate Android Development] beenz:
Anyone else having issues with BLN? I can get the lights to turn on, but not flash. Would it be an issue with the kernel, or Blinky? I tried disabling BLN, uninstall Blinky, reboot, and reinstall, but that didn't help. I don't feel like paying for BLN Control if Blinky can do it for free, but will if other people have success with it.
[Fascinate Android Development] nemesis2all:
Thanks for the read man. I have always been more of xtremesystems.org guy but I don't mind visiting anandtech or hardocp either :)
[Fascinate Android Development] nemesis2all:
I am on a different kernel I am working on but I have not touched any of the bln settings in kernel and went to market and installed blinky to test and it worked fine for me. If someone else can test blinky that would be great.
[Fascinate Android Development] nemesis2all:
I have not had the issue. I am not sure if you are referring back to some of the things with using a headset or not that you have mentioned before. If that is the case I have no headset to test issue. Other than that I do not get reboots while talking on the phone normally.
[Fascinate Android Development] saps:
Fyi, I tried 1.3 and it froze twice on me. Back to 1.2 for me and all is stable again. Of note and as mentioned earlier, it sometimes takes a couple charge cycles to see the battery savings. But when it finally kicks in wow. I drained only 16% in 16 hours yesterday and last night. I didn't charge it because it didn't need it. Mind you that was light use but still, a few texts, a but of score center app and of course xda
[Fascinate Android Development] mrtonee:
when I look under cpu spy my deep sleep is 68% is that normal I am using the latest builded plus com rom 1.2
[Fascinate Android Development] scarmon25:
From what I can tell the deep sleep happens when the phone is in standby. Mine shows higher when Ive not been using my phone so thats why I assume that is what it is. Depending on how much your phone is on or in standby would depend on how much the deep sleep percentage should be. So if you have had your phone in standby for over half the time is has been powered on, then the 68% would be normal.

Again this is what I think, and may or may not be fact.
[Fascinate Android Development] beenz:
Thanks for looking into it. Now to figure out why mine isn't working
[Fascinate Android Development] Daswolven:
Thanks for the response. I am always on bluetooth or wired, so I can only speak to those. Now and then I'll simply get a reboot that occurs between 5 and 15 minutes into a call. Haven't seen it on this latest yet, but will let you know.

I was more interested in knowing if you felt one scheduler was significantly more stable than the others.
[Fascinate Android Development] beenz:
I got it fixed. I uninstalled Blinky, reflashed your amazing kernel, wiped cache and dalvik 3 times each, ran fix permissions in recovery, then reinstalled Blinky. All is honky dory now.
[Fascinate Android Development] mrtonee:
thanks I will keep a eye on it....
[Fascinate Android Development] dablitzkrieg:
Fyi....my voltage control is maxed at 1300 and working pretty quick.

1300 and 1200 at -50

1000,800,600,400 at -75

200 at -100

The above are the only settings I use. Very fast and very stable thus far.
[Fascinate Android Development] OhioYJ:
The latest one built on the new source (4-30-11), still include the hotspot dummy module?
[Fascinate Android Development] stephenj37826:
what is your plan for droop voltage on your next one? I bet if you went 1150 there would be more stable oc for more people. One question though how would it affect heat build up? I would love to test one out with that setting. I use the heck out of my phone so battery life isn't a big deal to me. As long as it will last 10 hours with 30 min charge at lunch I dont care lol.
[Fascinate Android Development] rivaaaa253:
Would this work with DR 3 (I feel old skool for asking.. xD) ??
[Fascinate Android Development] bichigo:
Going on about 14.5 hours with 53% battery left and moderate use (5-10 txts per hour, 30 min phone call, web browsing, instant messaging).. not bad. Latest kernel is super stable too might I add, thanks!! :D
[Fascinate Android Development] beray5:
Since Load Line Calibration (more than 30 years old technique) only required and needed to be used recently in the last 3 years with latest CPUs, most CPU experts didn't quite get it yet, a lot of them don't even have factual garden variety PSU common sense.

Would an educated guess be OK?
[Fascinate Android Development] stephenj37826:
Of course lol
[Fascinate Android Development] beray5:
:D

LLC normally required feed back but some cases are done blind, the droop rate is guesstimated by the design engineer and plug in a best guesstimated compensation value without any feed back from the CPU.

Most likely that is what being used in the Fascinate. In ideal LLC implementations, the CPU power usage (heat) drops when enabled, in blind compensation the chance of over compensating is very high. eg, the CPU would use more power and generate more heat than otherwise.
[Fascinate Android Development] stephenj37826:
I see..... So I guess in future chips the cpu will dictate when to up the voltage according to load. That should lead to better battery life.
[Fascinate Android Development] beray5:
Currently it's very much similar to us plugging in different uv values for different clock frequencies.
[Fascinate Android Development] ChadZ:
Anyone having problems with 3G going out and 1x locking in, sometimes not even, only 4 dots?

I ran *228 option 1 and 2, called Verizon (no known issues).

I'm using Evil Fascinate 3.4.2 rom and this kernel.
[Fascinate Android Development] Elmojo:
Is there a version of this kernel for the US Cellular Mesmerize, or is this kernal directly flashable to the Mesmerize?

-Mike
[Fascinate Android Development] suppliesidejesus:
I haven't seen this at all. What radio are you using?
[Fascinate Android Development] scarmon25:
This works on the mesmerize. I have personally flashes all of his kernels onto my mes.
[Fascinate Android Development] ChadZ:
The default ED01 from the EF 3.4.2 ROM.

Verizon says no known issues

Ran *228, options 1 and 2.

Problem persists.

PS: anyone recommend battery life saving voltage control settings?

Thanks.
[Fascinate Android Development] ChadZ:
How'd you get that? What's your voltage control settings? What ROM you using too?

Thanks.
[Fascinate Android Development] neyenlives:
http://xdaforums.com/showthread.php?t=1051543

3G Signal Loss - Try DMU Rest or ESN Swap

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

[Howto] 3g Problems (The 1x lock)

Verizon is full of **** and I can prove it. You sound like you have the loss of 3G service (resulting in 1xRtt lock) like many others with Fascinates who upgraded to ED01. I got one of the techs to admit it and read me a memo that said they knew of some people without 3G service. You will have them try to get you to do all sorts of **** like clear browser cache and do a factory data reset. Just call them, play along like you did all that scrap, and keep asking them to do a ESN swap to another device (on their end) and back. If you aka for a DMU swap you will get all sorts of grief from "there's no such thing" to "you just need a new phone" which are all bull**** excuses for not simply taking ownership of their problem
[Fascinate Android Development] suppliesidejesus:
ED01 radio doesn't come with anything except the ED01 OTA. Go to Settings -> About Phone and tell me the Baseband Version.
[Fascinate Android Development] neyenlives:
He just needs an ESN swap. Bet you a dollar he has ED01 radio.
[Fascinate Android Development] suppliesidejesus:
Couldn't he just do an ESN swap on his own with his Verizon account if he has an extra phone lying around?

EDIT: An ESN swap would only need to be done if he upgraded to the ED01 radio, I wanna make sure that the ED01 radio is actually there.
[Fascinate Android Development] neyenlives:
Yes and yes, but only ED01 radio devices have had that problem. Its present in OTA and custom ED01 rims alike. Most people don't have a spare device lying around to use. That and I have also been told they deactivated and.then reactivated their device without actually swapping it also. I also wish VZW would own up to it and as long as nobody is calling in they will keep telling people "nobody else is having issues in your area". Bullcrap I tell ya'. I was just the first to notice and call. There's no way you're going to tell me I was the only person in the Louisville,KY area to have that problem.
[Fascinate Android Development] ChadZ:
S:i500.04 V.EB01
[Fascinate Android Development] neyenlives:
Oh damn! Hrm.
[Fascinate Android Development] ChadZ:
James, help me out at least :)
[Fascinate Android Development] neyenlives:
Chad there are other people reporting data issues all over but its sporadic. 4G, 3G, Fascinates or otherwise. You should just try the ESN swap method if you can, it certainly wont hurt. Or you could update to ED01 first actually that way in case you get it after that you wont have to fix it twice.
[Fascinate Android Development] stephenj37826:
What is the difference between droop voltage and uv. If I'm understanding droop its the value that the cpu falls to @ 1000 mhz + when not under load. The value of course shouldn't apply at lower click speeds if I'm thinking correctly. So my question is does each step have its own value?
[Fascinate Android Development] suppliesidejesus:
Try Odining the EC01 radio and see if you have any improvements.

http://www.mediafire.com/?wwwly9tk3d15tll

That's the EC01 Odin file. Just plop that in Odin (PDA PDA PDA) and Odin the modem in Download mode.
[Fascinate Android Development] Mystique:
@Nemesis2all

For whatever it's worth..

The wife and I are having lockups on this 1.3 where we didn't have any on the 1.2. Not sure if others are as well. Radios are fine.. I am on ED01 wife on EC01.

Deadline or SIO and I am 75 off all, and wife is 50 off all.

We seem to get it when we do "fast" things with the camera or when hanging up the phone and immediately doing something.. wife has the phone weakness and I have the camera..

Thanks again for all the tweaking ;-)

~Mystique
[Fascinate Android Development] beray5:
The Fascinate has a built in programmable voltage regulator for the CPU, uv steps are whatever you told the voltage regulator what you want the output to be 1.1V, 1.2V, etc...

Voltage droops are caused by non-ideal voltage regulator. Its internal output impedance is not zero, the more output current flow, the more output voltage is lost to the internal output impedance and less actual output voltage for the CPU. (eg, 1.1V step is no longer 1.1V, 1.2V step is no longer 1.2V)

No, each step does not have its own value, its the same non-ideal internal output impedance at any steps.
[Fascinate Android Development] bichigo:
Rom: Evil Fascinate 3.4.2

Radio: EC01

Build: ED01

Voltage Setting:

bfq

200mhz - 75

400mhz - 75

600mhz - 75

800mhz - 75

1000mhz - 75

1200mhz - 50

This has been working for me so YMMV ;)
[Fascinate Android Development] bobloblaw1:
1.3 seems a bit more temperamental but I think I've gotten it stable. I'm not saying these are ideal settings but they are the best I've achieved so far without lockups.

My settings for reference:

sio

1200 = -50

1000 = -50

800 = -75

600 = -75

400 = -75

200 = -50

100 = -75
[Fascinate Android Development] luke949:
So I've only been able to go -25 on states 100 to 1000 without any lock ups. I get lock ups on -50. I will continue testing to see what works for my phone
[Fascinate Android Development] stephenj37826:
So how does the droop value change this drop because of impedance?
[Fascinate Android Development] Eris _2.1_2010:
Is there a mirror for 1.3?
[Fascinate Android Development] shorto85:
http://db.tt/6d2jLV4
[Fascinate Android Development] beray5:
The design engineer knew the all of the voltage regulator design parameters, you don't design a voltage regulator with unknown regulation and unpredictable regulation, it is supposed to be regulated. If the voltage regulator was design for 4% regulation then that is what used for droop correction. For example...

Let say the CPU voltage is supposed to be at 1300mV and the voltage regulator had 16% regulation load line, for full current load the engineer would plug in the droop voltage number 1100mV. The engineer could change this 1100mV for something else for a different regulation load line.

This regulation baseline allowed the droop rate to be known as 16% which could be applied to any voltage steps.
[Fascinate Android Development] Dj-Dubster_TN:
Voltage Control Settings

100-200: -125

400 & 800: -100

1000: -75

1200: -50

1300: -75

cfq scheduler

clock limit 1300

Had 6 1/2 hours of heavy use including texting, browsing, games, and wifi tethering, and it was running fast as hell, try the settings out, lemme know if anyone else gets the same result or close to it

No freeze ups FC's or reboots either
[Fascinate Android Development] stephenj37826:
I see wonder why the oc is more stable with a higher than stock dvinst value. As the voltage is pushed above stock is the regulator not as accurate?
[Fascinate Android Development] beray5:
My best guess for the Fascinate is its a 9% droop rate compensation. With exacting precise compensation value you get a perfect flat voltage load line, both over and under compensating caused upward or downward voltage ripples.

The greater the compensation discrepancy value the greater the voltage load line ripples. In your case, you actually needed less compensation than stock provided (1100+ higher number is less droop compensation).
[Fascinate Android Development] stephenj37826:
I see. So is there variances in regulator silicon quality like there is in cpu quality? What I'm asking is would the optimum dvinst value change from phone to phone similar to oc/uv?
[Fascinate Android Development] cvs0115:
Usings Saps settings has been the best for me. A week on it and only froze once on me. Not sure what speed it locked up on me

Thanks Saps :-)
[Fascinate Android Development] saps:
Most welcome and as aforementioned, everyone will get potentially different results
[Fascinate Android Development] beray5:
They do have variances but not as much as the peripheral components being used with them. With LLC implemented properly, you can ignore variances as it compensated for variances and allowed for practically perfect 0% regulation load line.

Very much so. Similar to optimized comma-volt setting, 1100 is the nominal value that would work for practically any phone, but it may not be the best value for a particular phone.
[Fascinate Android Development] stephenj37826:


Sounds like I need to compile my own personal kernel huh. I have no experience with linux but got to learn some time. Thanks for the info.
[Fascinate Android Development] beray5:
Good luck to you and you're welcome. :)

If you do proceed with your own kernel, keep in mind that 1100 is not a directly apply voltage number, it's only for establishing voltage calibration baseline. eg, it could be any stepping and not stuck to 25mV, 50mV, or 100mV steps which allowed for even more granular precise steppings.
[Fascinate Android Development] garywojdan81:
Trying your settings on 1.3 kernel & comm.rom 1.2. So far great after almost 8hrs. Smooth, fast & no freezes or reboots so you are definately on to something. How's your battery life? I'm down to 49% after 8hrs of moderate(for me) use, so I'm pretty happy. Thanks for sharing.
[Fascinate Android Development] drose6102:
running the same voltage settings but running evil 3.4.2 cleared my battery stats first time and haven't charged yet. I will update after a few days. No lock ups or FC's, she runs great. So far thou 18% battery at 21 hours, display at 89% 2h 10 min, cell standby 8% time without signal 41%(bad service at work) and idle 3%. Thank you nemesis
[Fascinate Android Development] skynet11:
This is my first time using oc/uv settings. Trying those settings now, except for the 100mhz state - I'm not planning to use it. Is there any reason I should? I heard 100mhz is not recommended on some other kernels.

Another Fascinating post by my XDA app...
[Fascinate Android Development] saps:
Only way to truly know is to try and see. If I OC up to 1.3Ghz then I do seem to have a bit better stability not using a 100Mhz step. If you dont OC though its perfectly fine to use it [a la the imnuts type kernel]. Equally true many people can use the 100Mhz step with big OC's 1.3 even 1.4.

I suppose I recommend trying it at first. If you can great. If you have stability issues try removing it, using 200Mhz as your bottom and see if that makes a difference.

Almost everyone puts the same degree of uv on 100 and 200 Mhz steps. So in reality if you have a -100mv UV on 100 vs 200Mhz you're truly not consuming that much more power when the phone is asleep with the screen off.

For the last 3 days I've been running a bottom step of 200Mhz with a -125mv UV. At those settings when its in "Deep Sleep" to borrow the Cpu Spy term Im pretty sure Im getting comparable battery life to someone running a bottom step of 100Mhz with a -100mv UV, maybe even better. [I'll let the science nerds debate it.] Please note I have not had any issues with stability during this time period.

Bottom line. Try 100Mhz as a bottom step, some can and do have success with stability using it alongside a OC/UV combo. If you get problems often times replacing the bottom with 200Mhz does the trick. Not a cure all mind you but often works.
[Fascinate Android Development] neyenlives:
Just ran a 17.8 Linpack run....fastest I have ever seen on my device. Running 1300 max with -50mV on all steps 100,200,400,800,1000,1200,1300
[Fascinate Android Development] zeroxg4:
What scheduler are you using?
[Fascinate Android Development] neyenlives:
BFQ my bad forgot
[Fascinate Android Development] zeroxg4:
I have no freaking clue how you guys get such good Linpacks. I freaking copied your exact settings and it stays in the low to mid 14's. :mad:
[Fascinate Android Development] neyenlives:
well i have no idea. i think sdcard condition and type might have something to do with it when it comes to IO scores. that being said i am running the stock sdcard, but i have formatted it a few times and i am running the voodoo conversion, assuming you are too

what kind of quadrant scores are you seeing? i see like 1850 ish at the above settings