yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] fitsnugly:
I popped an 1805 on a nightly once before, nothing that high tho ;)
[Nexus One Android Development] waylo:
Have still been getting these funny touch-screen no-response episodes on both 800mv and 925mv kernels, essentially forcing a battery pull since I can't reboot the phone. Happens when I wake the phone and try to unlock it.

Possibility it's not the kernel but some other conflict? 508 itself? I also use a program called Lock Delay which lets you turn on the lock pattern after a set number of minutes.

Have switched to pershoot kernel for now (sorry, don't know what else to try). If it comes again, maybe it's some other strange conflict causing the issue.

Haha, just for kicks, here's my quadrant rating, on 5.0.8. Tremble before my might! :p
[Nexus One Android Development] wildmonks:
Perhaps... If you don't get the touchscreen issue while on the stock kernel then we know its definitely something wrong with the kernel not working correctly with the rom.

I've read about this similar problem with other kernel threads (I think it still occured on a froyo rom for one user). I can only see one commonality so far, they all undervolt (anything under 1000mV stock is undervolting). It could be that your touchscreen is sensitive to undervolting and needs a value higher then 925mV (could explain why not everyone has the problem).

Pershoot and kmobs use 950mV, so you may want to try one of theirs. If you'd like I can also modify my kernels to a different min volt value for you of your choice. But this is all speculation, I don't know for sure if that's the case or if its some unknown code that none of us knows yet...

BTW: I had to look twice when I saw that score heh. Soon cm6 will be officially released. ;)
[Nexus One Android Development] flak0:
@WildMonks thanks for offering to help with the Kernel compile. I will let you know. By any chance have you started messing with increasing the Overclock to a bit over 1113mhz as you specified it would be stable at 1250mv. sorry I dont know the exact value that you listed like 2 days ago.
[Nexus One Android Development] wildmonks:
Actually I have been after i got a private message request. Spurred on by his successful testing of that kernel I guess I'll go ahead and post it here.

I changed the code involved in switching between AVS and SVS so that they can function properly at higher mhz speeds and i limited the max volt to 1300mV for 1152 and 1190mhz. (I flat out refuse to go beyond 1300mV as I believe this will result in damaging the voltage regulator). These changes seems to keep the temperature in check so.

You can find the kernels in the TEST folder.

Before you try these kernels out I gotta say this. I am not responsible if these kernels result in damaging your phone. Its purely for testing purposes and I really dont recommend using it as your everyday use kernel.
[Nexus One Android Development] xda890:
OpenVPN works like a charm with your kernel... Thx... :)

(and thx for the no audio boost option! :D)

btw, I installed the 2.6.35 kernel, is that the one I should use or should I stick with the latest 2.6.34 kernel?

(I am running CM 6.0 RC1)

BTJ
[Nexus One Android Development] flak0:
I'm going to go ahead and try. The n1 is rated at 1300mv isn't it? Should I be on the look out for high temps? I'm testing the CFS version.

Try1: this thing is fast. I'm only at 1152. I GOT 45 ON LINPACK
[Nexus One Android Development] fitsnugly:
Well the cats out of the bag now!

I haven't had my in-case temps go above 30.7C using the 1190 bfs

Been watching like a hawk, but no heat & stable!
[Nexus One Android Development] rodigezstyle:
@wildmonks

Please add FM support in the next Kernels the 2.2 sense is coming...

and the 1190Mhz Kernel Looks good no Problems so far... maybe a Option for the First Post ?
[Nexus One Android Development] flak0:
What are your settings in SetCPU? Post benchmarks
[Nexus One Android Development] Autinhyeu:
Testing 1190 CFS on the CM 6 RC ROM, result: 34c temp, Linpack score: 47,620, Quadrant score: 1710

0.o
[Nexus One Android Development] pzumk:
Linpack 47 is great! did you send the score? Do it!

also:

Restart -> Kill all apps -> do the quadrant benchmark like 3 to 5 times in a row
[Nexus One Android Development] rodigezstyle:
i got 47 MFLOPS with my MCR Mod & the BFS 1190Mhz Kernel..
[Nexus One Android Development] flak0:
1750 on Quadrant! Running Stock Froyo
[Nexus One Android Development] fitsnugly:
1845 on quadrant, see pic a few posts up
[Nexus One Android Development] notxel21:
Where is everyone getting this 1190 kernel?

Thanks! :cool:
[Nexus One Android Development] fitsnugly:
http://xdaforums.com/showpost.php?p=7150418&postcount=637
[Nexus One Android Development] notxel21:
Much Appreciated! :)

Thanks! :cool:
[Nexus One Android Development] wildmonks:
Ah cool! I thank you so much for testing that out. Its been on my mind for a long time whether or not OpenVPN works these kernels. Very good to hear that they do :)

Awhile ago, the original source code from google's open source had 1300mV as its max. That has since changed to 1275mV max. I feel comfortable using 1300mV but definatly not any higher then that. Yes, be on the look out for high temps. Expecially if your overclocking, running benchmarks (stressing the cpu) and charging the battery at the same time. That'll definitely heat up your phone. It maybe good to know that in the code, they have implimnted a check during battery recharging that if the phone reaches a certain temperature it will automatically stop charging the phone. I forget what that temperature is, I'll check when I have time (start of the work week, won't be able to until later).

Done, I added it to the opening post under the Q and A section. Sure, FM support would be awesome. I'll keep an eye on the new thread about this and add it as soon as IR does his awesome magic on it to make it functional on 2.2 froyo sense. :)
[Nexus One Android Development] damanrico:
Wildmonks, you are a sneaky guy. I've been asking you questions, and checking this thread many times a day, and it took me up till now to see your donation signature (make it a little bigger :p). I had been wondering if you took donations or not.

So donated 2 bucks, hope that's enough for a drink. :)
[Nexus One Android Development] wildmonks:
Wow dude, thanks! Heh, yeah, I'm a bit bashful when it comes to this.. :o
[Nexus One Android Development] eViL D::
Nice stuff bro. Which kernel is this? Also, have you had problems with setcpu and .35 kernels?
[Nexus One Android Development] antiochasylum:
The 1190mhz kernel actually slowed my phone down, I couldnt break out of the 1650 range in quadrant and that was off a fresh reboot, nor get anything faster than a 40.3 in linpack. Going back to the .34 kernel that I was on, I was gettin 1780's on quadrant and 44's with linpack!
[Nexus One Android Development] flak0:
+1 on this however Wildmonks did state it was a test. SetCPU does some weird stuff with this Kernel. The step below 1190mhz performs the best. i got 1750 in Quad and 43 linpack and 32.1 in Neocore.

temperature has hit close to 100 degrees F, however phone doesnt feel hot, im wondering if something is wrong with the code in the kernel. Wildmonks can you chime in on this?
[Nexus One Android Development] flak0:
Are u using CFS or BFS?
[Nexus One Android Development] antiochasylum:
I even tried that, still slow. Went back to the latest 2.6.34 and immediately hit 43 in linpack, and a 1744 in quadrant.

As I should have stuck with my gut, never flash an RC of ANYTHING.
[Nexus One Android Development] antiochasylum:
Using the Cfs version
[Nexus One Android Development] mtw4991:
I tried the bfs and got slower speeds also plus fc's on quadrant:-(
[Nexus One Android Development] wildmonks:
The 1190Mhz overclock kernels is based on .35-rc4. (I see rc5 is out, I'll start working on that soon). I haven't encountered a problem using .35 and setcpu, have you?

This sounds like your CPU can't use 1190MHz without increasing the voltage even further. Something I notice during testing, if I don't feed enough voltage to the CPU, things start to slow down and lag. This was something I was able to replicate when feeding 1225mV at 1113MHz. However, I think most CPUs will be able to run correctly at 1152MHz @ 1300mV. Personally I'm not a big fan of these "super" overclock kernels but I'll continue to update them with the usual kernel releases for those that want to use them. I may also just get ride of the 1190mhz setting because I have the feeling more people cant use it without increasing the voltage even more.

The 100 degree temperature thing maybe the result of your CPU doing erroneous calculations from being overclocked too high.

Have you by chance updated to the latest quadrant? Ever since I did, I've been getting lots of fc's on quadrant when using any of the BFS kernels. Thankfully I kept an old copy (1.0-beta8) in Titatium Backup and the fc's are gone. There something in the latest version that doesn't like BFS...

Other then that, your symptoms look like your CPU can't handle the high clock speeds of 1190MHz.
[Nexus One Android Development] fitsnugly:
Same here, I restored the old version as well and no more FC.
[Nexus One Android Development] wildmonks:
Okay, so it's not just me. I'll try to submit a bug report and hopefully it will get fixed in a future release.
[Nexus One Android Development] antiochasylum:
I would opt for you too set it back to 1152mhz, since most of us can't even use the 1190mhz.

I just went back to the 2.6.34 070110 cfs kernel and phone is running normal again. Back to high 1700's in quadrant and 42-44 range in linpack. I guess you found the limit of the cpu on stock voltage.
[Nexus One Android Development] fitsnugly:
but some of us can ;) and the highest temp i've ever gotten with it so far has been 31.5C
[Nexus One Android Development] pzumk:
Where do you live and do you even use your phone?

My phone is idle right now (no usage for the last ~1h) and it's at 30.7°C

During usage I get up to 40 these days.

(Summer, Germany)
[Nexus One Android Development] fitsnugly:
Light use (in the case, btw) this morning (texting, facebook) and I'm at 29.5C

When I ran quadrant and popped a 1845 I was at 28.7C :D

FYI SetCPU profile is 245/245 on standby
[Nexus One Android Development] pzumk:
I have the same setCPU profile :P
[Nexus One Android Development] fitsnugly:
itsnotabugitsafeature?
[Nexus One Android Development] pzumk:
eh, what? It's a feature that I get higher temperature?
[Nexus One Android Development] fitsnugly:
twas a joke ;)
[Nexus One Android Development] antiochasylum:
True, you can and maybe a few others, however 5 or 6 out of hundreds is not good odds lol. Just saying. And besides do you actually use the phone to its potential at 1190mhz? No lol, I have the 1113 OC kernel however my phone stays set at 768, saves battery and it's still plenty fast to text, watch you tube and play flash games, just saying...
[Nexus One Android Development] fitsnugly:
Little pretentious to assume you know how I use my phone, isn't it? :rolleyes:
[Nexus One Android Development] mtw4991:
Have you by chance updated to the latest quadrant? Ever since I did, I've been getting lots of fc's on quadrant when using any of the BFS kernels. Thankfully I kept an old copy (1.0-beta8) in Titatium Backup and the fc's are gone. There something in the latest version that doesn't like BFS...

Other then that, your symptoms look like your CPU can't handle the high clock speeds of 1190MHz.[/QUOTE]

Wildmonks, the Quadrant version I have is 1.0 revision 1258 build 07112010 and have 1.0(beta-8) on Titanium backup also....not sure if they are the same though, lol.

EDIT: reverted back to 1.0 Beta-8 and got no fc's after 5 tests...1769 highest on 2.6.35 925 BFS, not the test kernel.
[Nexus One Android Development] antiochasylum:
Ok the average person on xda will not ever use 1190mhz on their nexus. Plain and simple. Not saying you don't apologies on my part, however the average user will not, you and I both know that.
[Nexus One Android Development] mtw4991:
Ok, reverted back to Quadrant 1.0 Beta 8 and ran the 1190 kernel again...

Linpack 44.372 highest @ 1190

Quadrant 1852 personal best @1152

Very nice job, but not comfortable keeping it on. Back to 0708 :)
[Nexus One Android Development] :
Richard trip on the desire forum has a kernel of 1.267ghz running very stable. Wildmonks could you transfer part of that kernel and introduce it to this one... I'm sure its safe as i ran my desire on it with no extra heat or reboots... The desire haas the same cpu so it must be possible.

JD
[Nexus One Android Development] dictionary:
Does it really MATTER? He could OC the damn thing to 238103829038120mhz .. if you only want to run it at 1113, then set it to run at 1113. If you want to be bold, set it to max. Why should he not make it as high as he wants, and leave it to the end user to turn it down?
[Nexus One Android Development] harmohn:
Whoa, the 2.6.35-rc4_AVS-925mV_CFS_1190Mhz_TEST kernel seems very robust; no issues at all (BFS caused a few reboots).

:)
[Nexus One Android Development] wildmonks:
Hmmm, okay. You convinced me to unlock the multipliers all the way up to 1.267GHz. I see he set his max to 1300mV as well so I will do the same. I'll work on this after I complete work on the .35-rc5 kernels. Which maybe tonight or tomorrow night. Depends on how long it will take me to compile and fix any errors that may come up.
[Nexus One Android Development] zizoty:
Not possible for n1 to go higher than 1113 and be stable as pershoot, gorilla, interraven tried to do this in the past. If you read the last few pages of oc gpu page in this forum, you will read jack explanation for why n1 is stucked at 1113 eventhough its very similar to desire.
[Nexus One Android Development] wildmonks:
Update:

Changes since kernel date 070810:

-Updated with IR's latest commits to rc5 (2010-07-09 to 2010-07-12)

2.6.35-rc5_AVS-800mV_CFS_1113Mhz_071310.zip

2.6.35-rc5_AVS-925mV_CFS_1113Mhz_071310.zip

2.6.35-rc5_AVS-800mV_BFS_1113Mhz_071310.zip

2.6.35-rc5_AVS-925mV_BFS_1113Mhz_071310.zip

No Audio Boost versions can be found here.
[Nexus One Android Development] eViL D::
I haven't seen Richards acpuclock, would be nice to though. BTW, I can't get setcpu to work with .35 at all. Screen goes blank and fc's me. Talking about my kernel. :cool:

Just flashed your .35 and setcpu works. Gonna have a look at your config I guess. My .34 kernels work with setcpu and I used that config too. Weird......
[Nexus One Android Development] wildmonks:
Can you post your acpuclock file? (in my case its acpuclock-qsd8x50.c). Maybe I can find the problem for you :)
[Nexus One Android Development] eViL D::
Sure, but I don't think that's the problem. Never know though.
[Nexus One Android Development] wildmonks:
I believe your using IR's source but you only want to have SVS. So you change your config to not have AVS correct?

If this is the case, I don't think a that one change is enough as your acpuclock is still continuing to use the code that designed by IR for AVS operation. Specifically this function:

static int acpuclk_set_vdd_level(int vdd)
{
if (drv_state.acpu_set_vdd)
return drv_state.acpu_set_vdd(vdd);
else {
/* Assume that the PMIC supports scaling the processor
* to its maximum frequency at its default voltage.
*/
return 0;
}
}

You will want to change it to something like this:

static int acpuclk_set_vdd_level(int vdd)
{
if (!drv_state.regulator || IS_ERR(drv_state.regulator)) {
drv_state.regulator = regulator_get(NULL, "acpu_vcore");
if (IS_ERR(drv_state.regulator)) {
pr_info("acpuclk_set_vdd_level %d no regulator\n", vdd);
/* Assume that the PMIC supports scaling the processor
* to its maximum frequency at its default voltage.
*/
return 0;
}
pr_info("acpuclk_set_vdd_level got regulator\n");
}
vdd *= 1000; /* mV -> uV */
return regulator_set_voltage(drv_state.regulator, vdd, vdd);
}

I don't know if this will fix your setCPU problem but it's one issue I see in your acpuclock if you want to only use SVS.
[Nexus One Android Development] flak0:
@wildmonks any luck with 1267mhz @1300mV?
[Nexus One Android Development] eViL D::
Right on. Seems there's a problem with my config. Gonna go through it slowly....
[Nexus One Android Development] wildmonks:
Very enlightening post from Jack. This totally explains the difference between the desire and nexus. I agree with zizoty, if it was possible to overclock the nexus to desire levels, it would have been done by those who are way more talented then me.

I do believe obtaining a stable clock at 1152 is very possible @1300mV for some users so I will continue to update the higher overclock kernels and post it in the TEST folder.

While on the subject of overclocking, I have bad news to report. I have made an error in the code involving the 1190MHz clock speed. This error results in an actual clock speed of 1152MHz even tho setCPU reports 1190MHz. So for those who thought you were stable at 1190MHz, your probably not...:( (My phone randomly crashes).

This error also seems to be the source of the poor performance and lag that some have seen when setting their max to 1190MHz. So again.. my bad here for thinking the poor performance and lag was something else... :(:(

I fixed this error and posted it in the TEST folder.

I'm not sure anyone will be stable at 1190MHz but your welcome to try.

@flak0

I think you can forget about 1267MHz for the Nexus. Its just not possible without increasing the voltage to insane levels. My phone crashed real hard and instantly when I tried it. I don't want you to experience the same thing. :(:(:(
[Nexus One Android Development] :
Its such a shame:( thanks for the effort wildmonks;)

At least we know for sure now mate.

JD
[Nexus One Android Development] flak0:
New 0713-cfs-1190mhz working perfect here. No crashes . 1780 on quad and 46 linpack. All ondemand
[Nexus One Android Development] damanrico:
Wildmonks, if I use the 1190 mhz version and set it to 1036 max, will it be the same as using the 1113 mhz version and setting it to 1036?

If so, I might just use the 1190 and only clock it that high if I want to get my benchmark fix for the day.
[Nexus One Android Development] antiochasylum:
Not sure what you did monks but on rc5 1190mhz 0713 my phone peaked at 46.3 in linpack at 1152mhz, and I was running 1190 with consistent 44.0-45.2 in linpack. Nothing higher then 45.2 on 1190 though. 1152 still only brought me a 1718 in linpack, could be cause of my class 2 sd card though.
[Nexus One Android Development] fitsnugly:
HOLY COW!

Just broke 1900+ in quadrant with the latest 1190mHz kernel & latest CM6 nightly...

Running rock solid at 28.1C
[Nexus One Android Development] fitsnugly:
Update: 1190 is being unstable when using handset, not any other app tho? Might just be an issue with that app since I was fine until I started using it.
[Nexus One Android Development] wildmonks:
Whoa... well this was a huge surprise. I'm both happy that there are some users out there that are "blessed with cooperative silicon" and sad that I was not :p.

I still wouldn't recommend using the max 1190mhz daily on your phone (use only for testing purposes) since your stressing out your cpu even more then usual and battery life will suffer, which brings me to this question...

Yup using the setting of 1036MHz will be exactly the same on either kernels. So as long as you keep your max at that speed, you will receive the same battery savings benefits.
[Nexus One Android Development] wildmonks:
I think 1153mhz is the sweet spot for your cpu @1300mV. A linpack of 46.3 is very impressive!

Benchmarking does stress out your CPU more then your usual app so if there is any chance of instability, benchmarking should find it.
[Nexus One Android Development] fitsnugly:
Ran quadrant and linpack numerous times with no issues, as well as other apps. Just handcent seemed to bomb out.
[Nexus One Android Development] harmohn:
Beautiful ;)

Sent from my Nexus One
[Nexus One Android Development] THATTON:
Latest 925BFS running nice and cool, fast as hell too!
[Nexus One Android Development] antiochasylum:
So I thought my phone was done at 46.3, Driving home for giggles set it to 1190mhz and 4-5 runs later hit 47.072 in linpack. When i submitted it, it was the 69th fastest device :)

Here is the submission on the website, and a screen shot, sorry for the horrible screen shot, however its coming from my work cell phone
[Nexus One Android Development] wildmonks:
Oh, my bad, thought it was a benchmark app that fc on you. >_<
[Nexus One Android Development] fitsnugly:
A couple reboots today @ 1190, but absolutly stable @ 1152. Temps not an issue at either speed. Gonna do some more testing @ 1190 after the next update to see if its just too unstable or if its just this release.
[Nexus One Android Development] flak0:
What exact settings are you using on SetCPU. I noticed that having Apps2EXT via Darktremor script and Dalvik-Cache on SD causes reduction in performance when it comes to benchmarking.
[Nexus One Android Development] antiochasylum:
I run ondemand and have it set at 998 for everyday use, for the benchmark I turned it to 1190 and set it on performance, My linpack is installed on my sd card as well as my dalvik cache. This is a 16gig class 2 card.

The only profile I use is while charging, cpu is set too 499mhz

Edit: its 7:47 pm where I live, phone has been off charger for 17 hours, and I have 10% battery left, I've texted, flashed the sp3 from the kang o rama rom, and flashed this kernel. Pretty impressive I must say.
[Nexus One Android Development] SimFox3:
Frequency Voltages starts Differing

WildMonks,

I'm noticing a minor glitch with this kernel (or my phone?), but I'm pretty sure I've seen the same issue on stock intersectRaven kernels: Over time, the voltage applied for different frequencies starts varying.

I'm running the 7/8-925mV-CFS-No-AudioBoost. My SetCPU "Battery" profile is set to 998/245 ondemand.

When I first boot up the phone (no charger), and then quickly use OSMonitor to monitor "dmesg", I see:

AVS setting V to 925mV @ 245 MHz

AVS setting V to 1200mV @ 998 MHz

AVS setting V to 925mV @ 245 MHz

AVS setting V to 1100mV @ 998 MHz

AVS setting V to 925mV @ 245 MHz

AVS setting V to 1000mV @ 998 MHz

AVS setting V to 925mV @ 245 MHz

AVS setting V to 1000mV @ 998 MHz

AVS setting V to 925mV @ 245 MHz

AVS setting V to 950mV @ 998 MHz

AVS setting V to 925mV @ 998 MHz

Within a minute, I don't see ANY more AVS messages in DMESG, and I can safely assume that the regulator decides that 925mV is enough voltage for 998Mhz.

If I check back after six hours, I still don't see any AVS output messages, indicating that the voltage is still a steady 925mV for both 245Mhz and 998Mhz.

However, I check after maybe 18 hours or so, then I find constant AVS messages in DMESG:

AVS setting V to 925mV @ 245 MHz

AVS setting V to 1100mV @ 998 MHz

AVS setting V to 925mV @ 245 MHz

AVS setting V to 1100mV @ 998 MHz

AVS setting V to 925mV @ 245 MHz

AVS setting V to 1100mV @ 998 MHz

AVS setting V to 925mV @ 245 MHz

AVS setting V to 1100mV @ 998 MHz

These messages are constantly being generated in the the logs. Somehow, the 925mV is no longer adequate for 998Mhz.

The actual duration before voltages differ AND the final voltage applied to 998Mhz varies from day to day. Sometimes the the voltages start differing within 5 minutes of a phone boot, and sometimes it might take 2-3 days. Step final voltage at 998Mhz is somewhere in-between 950mV - 1500mv.

Just wondering what "triggers" the 998Mhz to use a HIGHER voltage than what it was initially happy with.

Also, would it make sense to for the regulator to periodically (every hour?) re-hunt the frequency-voltage mapping IF they're out of sync? Similar to what happens at system boot.