yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] watercool:
how often did you run the benchmark? First run i get 1400-1500 .. second and third run 1600-1700...
[Nexus One Android Development] sultan-mrm:
Re: [Kernel] Hybrid AVS + 1113Mhz Overclock (.33.5 & .34)

hi

many kernels I flashed on cm506

but always get problemes with wifi

and WPA/WPA2. any way to fix it ?

-------------------------------------

Sent from my Nexus One
[Nexus One Android Development] _Opiate_:
Not bad

Wow Ive been using the 33.5-800mV-CFS-OC for a day and a half now and besides getting badass scores on quadrant and linpack (which is cool). Im seeing WAY WAY WAY better battery life then Ive ever seen on my Nexus. I've tried just about every kernel out there so far and this one for me is a WIN.

P.S.- Haven't tried the 33.5 BFS 800mV yet but I'm looking forward too it!
[Nexus One Android Development] wildmonks:
I'm assuming you don't have any problems connecting to your router when you are on the stock cm5.0.6 (then its not a router problem). If its not the router, then its probably because most of these roms are made for cm 5.0.7.1 or froyo and have the new wifi module. I guess you have your reasons not updating to cm 5.0.7.1 or froyo so you should stick to the older kernels like this one:

http://droidbasement.com/db-blog/?p=200

Or if your feeling adventurous, you can try this kernel that I made for you that contains the old, old wifi module (dated back in Feb 2010). I don't know if this will solve your problem but it shouldn't hurt. (I tested it on froyo and it booted up with wifi working).

2.6.33.5_AVS-925mV_BFS_1113Mhz_OldWiFi_060310.zip
[Nexus One Android Development] Daswolven:
Re: [Kernel] Hybrid AVS + 1113Mhz Overclock (.33.5 & .34)

Played with all four today, ran benchmark pi, linpack, and quadrant. Performance differences using the median of five times on each was consistent in the following order: 800 CFS, 925 CFS, 800 BFS, 925 BFS. my median quadrant on the 925 BFS was 1844. No, I cannot replicate these results on other kernels. Yes, I have tried. Well everything but gr8gorilla, he scares me.

This is good stuff.

-------------------------------------

Sent via the XDA Tapatalk App
[Nexus One Android Development] mtw4991:
I just went straight for the 925 BFS, set max/max/performance and got a high of 1836 Quadrant, SetCPU short bench of 167/long bench 321, Linpack high of 43.3 PLUS I also got some random reboots, a couple of FC's etc but nothing major. Might be because I was running wide-open and kinda warm at 35c.

Anyone else get any reboots or FC's??
[Nexus One Android Development] _Opiate_:
I've been running completely stable for the last day and a half - 33.5-800mV-CFS
[Nexus One Android Development] Daswolven:
Re: [Kernel] Hybrid AVS + 1113Mhz Overclock (.33.5 & .34)

http://25.media.tumblr.com/tumblr_l3gm5mFvsJ1qzbih3o1_400.png

Sorry, cant post links from the app. No FC yet for me on this kernel. Had one using goggles on the 800BFS, but stable after that.

-------------------------------------

Sent via the XDA Tapatalk App
[Nexus One Android Development] wildmonks:
I got a good laugh when I read this :D

BTW: gr8gorilla is a gr8 coder as it was his post that lead me to learn how to make kernels.

It maybe the BFS as its still pretty beta. It could also be your CPU needing more voltage to operate at 1113Mhz without errors.
[Nexus One Android Development] mtw4991:
BFS has been extremely stable in all of the kernels I've tested on my N1...most of IntersectRaven's kernel anyhow. It might be that mine needs more voltage...how do I do that?:confused:
[Nexus One Android Development] THATTON:
I am very impressed with this kernel so far! I didn't really expect much to be honest(no offense to Wildmonks I had just never tried or seen any of your work) but I have got to say, I flashed the 2.6.34 925 CFS last night and I have been using the phone moderately today and after about 9 hours off the charger I am at 78%! I know that might not sound like much with all these claims of people getting 40+ hrs on a single charge(People that never use their phone ;))but in comparison with what I am used to seeing this is fantastic! To top it off, the performance and speed are excellent!!! Great job man! Keep up the good work!
[Nexus One Android Development] wildmonks:
Its something I have to change in the kernel. Give me sometime and I'll make one for you just to test it out and see if it helps.

BTW: I don't know for sure if increasing the voltage will help but if you don't see FC or reboots when you set your max CPU to 998MHz via setCPU then it kinda supports this theory for your CPU.

Currently all my kernels are set to 1275mV max, so I'll increase it to 1300mV. I was a bit hesitant to use 1300mV in the first place because according to the original code, the limits are 800 min and 1300 max. Also I'm sure battery life will suffer a little with max set to 1300mV.
[Nexus One Android Development] mtw4991:
Wildmonks, don't worry about upping the voltage to 1300mV for me as I probably won't run it at max all the time anyway. I am going to try the CFS and see what I get with it also...just to compare.:D It's plenty fast at 998 and benchmarks are just that, benchmarks. Other than bragging rights or gpu intensive apps, the extra speed gets lost:p
[Nexus One Android Development] wildmonks:
Lolz! No offense taken. Too be honest, I too didn't expect this big of a jump. Before I fulfilled a request to combine AVS with OC, I was compiling the 2.6.34 kernels for myself without the OC (I thought it didn't need it because of the improvements made by froyo). Really though, a lot of the credit goes to pershoot, intersectRaven, cyanogen, and the rest of the coders as it was them that made the bulk of the modded code.

But I really appreciate the compliments, thanks! I'll try to keep up with the latest improvements and bug fixes are they are being made in the Android Open Source community. :)
[Nexus One Android Development] wildmonks:
Ah, okay, sounds good. Saves me another 50 or so minutes of my life :D. (Someday, I'll upgrade my computer.....)

FYI: When the cpu is set to 998MHz, the max voltage is set to 1225mV automatically. This is the "Hybrid" nature of the AVS that intersectRaven coded in. This should give more battery life when the CPU is set lower.
[Nexus One Android Development] _Opiate_:
Took my nexus off the charger at 7:00 this morning and it's now 6:33p.m. I'm at 81%!!!! That's just incredible. I've NEVER seen this kind of battery life improvement on my nexus. Most of the OC-UV kernels just made it worse to tell the truth but Ive been running at 1.113 all day with gov set to "on demand" and I'm seeing better life then the stock kernel or any other kernel for that matter has ever given me. I'm impressed.
[Nexus One Android Development] darkjedi:
Which one did you pick? CFS or BFS? After about 4 hours, I'm at 71% battery using BFS. Usage has been about 20-30 minutes of A2DP, and about 20 minutes of web browsing/randomly checking phone.
[Nexus One Android Development] Daswolven:
lmfao. I can take mine off the charger and not use it for 12 hours and only use 20% too. :)
[Nexus One Android Development] wildmonks:
Cool, no problem :)
[Nexus One Android Development] wildmonks:
Update for .34.1:

Changes since 070810

-Updated zip to erase previous kernel modules.

-msm: disable the allocator for pmem_camera (CyanogenMod)

-Fix packet filter to only filter out non-unicast frames. (CyanogenMod)

-Update compcache to 0.6.2 (CyanogenMod)

2.6.34.1_AVS-800mV_CFS_1113Mhz_072210.zip

2.6.34.1_AVS-925mV_CFS_1113Mhz_072210.zip

2.6.34.1_AVS-800mV_BFS_1113Mhz_072210.zip

2.6.34.1_AVS-925mV_BFS_1113Mhz_072210.zip

No Audio Boost versions can be found here.
[Nexus One Android Development] skorpioneMM:
Are you think update the 1190 Mhz kernels? In my Nexus One the 2 different kernels (CFS and BFS) works very well, the 2 kernels are very stable and i use it a lot off days ago and 0 problems, but the fastest and best kernel are the BFS (is more fast then CFS) but this i can't use because i found a bugs, in a various games when i go to play, the phone freezes, but im sure there are no problem of stability o problem with the phone, because when i underclock the phone to 1075, 1113 Mhz, i got the same problem, various games freeze my phone when i go to start.

With the CFS kernel, i played a lot off games at 1190 Mhz and never i got freezes or reboots and the maxium temperature off the phone are 37-38º.

You can check the 1190 Mhz BFS kernel? One off the games are freezing my phone are Baseball Stars 2010.

Please check it if you can, i really like the 1190 Mhz BFS kernel, with this, i got 1940 quadrant points and 49,477 MFLOPS in linpack.

Thanks for your great work.
[Nexus One Android Development] damanrico:
Please notice that he updated the 34.1 kernel.

He only creates 1190 Mhz versions of the 35 kernel.
[Nexus One Android Development] skorpioneMM:
Yeah i know, this is my question, when he update the 1190 Mhz 2.6.35 kernel...
[Nexus One Android Development] wildmonks:
Well first off, let me say that is an incredible score you got with the BFS kernel (perhaps too incredible :))

The BFS code hasn't been updated by Con Kolivas (the inventor) since back in May 18th, 2010. Until he does, I can't really touch the BFS code directly without breaking it. The BFS code makes dramatic changes throughout the kernel, so much that it's beyond my ability to try and trace the problem. (I tried with a wifi + BFS + Regulatory domain issue, failed miserably... :()

That said, CFS has been around a whole lot longer then BFS so its obviously more stable and the reason why its used over BFS in stock kernels.

Sorry its not the answer your looking for... but I'll continue to be on the lookout for updates to BFS.

By the way, the CFS scheduler is constantly being improved by the kernel community to a point where it's close to being BFS like in terms of lantency. This maybe a reason why we're not seeing any recient updates to the BFS code.
[Nexus One Android Development] skorpioneMM:
Yes the score with the BFS kernel in my phone are incredible and as I say it's really stable and fastest, just has these little issues with some games.

I had lucky with my Nexus, he never reboot or freeze with all off your kernels :D

At the moment, i am conforming with the CFS kernel, i am getting 45-46 MFLOPS and 1700-1800 quadrant points.

Thanks for you response
[Nexus One Android Development] wildmonks:
Update for .35-rc5

Changes since 071710

-Sync to IR's source

-Re-added AUFS.

-msm: disable the allocator for pmem_camera (CyanogenMod)

-Fix packet filter to only filter out non-unicast frames. (AOSP - Fix for WiFi sleep issue)

-Update compcache to 0.6.2 (CyanogenMod)

2.6.35-rc5_AVS-800mV_CFS_1113Mhz_072210.zip

2.6.35-rc5_AVS-925mV_CFS_1113Mhz_072210.zip

2.6.35-rc5_AVS-800mV_BFS_1113Mhz_072210.zip

2.6.35-rc5_AVS-925mV_BFS_1113Mhz_072210.zip

No Audio Boost versions can be found here.
[Nexus One Android Development] wildmonks:
Of course.. after I updated these kernels.. the .35 mainline gets updated to rc6...
[Nexus One Android Development] codesplice:
Way to go :p

Not to rush, but any ETA on a wildmonk'd rc6? It's a bit of a hassle for me to hit mediafire on this network, so just wondering if it's worth it to grab the updates you just posted rather than waiting a bit.
[Nexus One Android Development] wildmonks:
I'll work on rc6 and release early tomorrow. My eyes are tired from staring at the screen for too long haha.

But I would wait unless you need the wifi sleep fix. I haven't notice any speed improvements yet with this release.
[Nexus One Android Development] codesplice:
Copy, thanks.

One of these days, I'm going to have to put in the effort to learn about compiling these kernels. Til then, thanks for doing what you do ;)
[Nexus One Android Development] knightnz:
Is it still generally regarded that CompCache is not terribly beneficial? What're peoples opinions of using it these days versus not?
[Nexus One Android Development] wildmonks:
Yah, expecially with the nexus and it's large ram. But might as well include it to keep the code updated.
[Nexus One Android Development] waylo:
I re-installed and tried the 800mv CFS 7/8/10 a few days ago. In order to try to make a "cleaner" system, I did the following

* Turned off my 'screen off' profile on setcpu. Thought that might have something to do with the screen wake-up freeze.

* Wiped cache and dalvik - have no idea if that does anything but it's been a while. Any rationale to this at all?

Was running really smoothly until this AM at work. I had a strange freeze, where when I woke the phone, it had only the status bar (usually I have I have it hidden via ADW.Launcher) and the static wallpaper. No unlock passcode screen, nothing. Since there wasn't anything to touch on the screen, couldn't really tell if the touchscreen was working or not. Wasn't at a computer so I couldn't do any adb checking.

This occurred after receiving a few google voice text messages. I tried messaging myself this evening multiple times to see if I could reproduce it, but no luck.

Thanks so much for the offer. If you could make a test kernel for the 800mv CFS with audio boost, I would definitely appreciate and try it out. Care to share your theory on the cause?

Is there a logging/debug program you would recommend to help track this down? alogcat maybe?

Going to try your latest 34.1 version from today.
[Nexus One Android Development] knightnz:
Interestingly, I flashed the latest CFS kernel and Linpack won't go beyond 41.01. I went back to one from the 17th and I can get 44.738 out of it. Both lower than I was getting (48.33 at best with the OC kernel), maybe something in the current CM nightly is slowing things down, but is there anything in the last few days that should've made things slower?

I tested both after cleanboots cache/wipes after a few minutes post-boot to settle down.
[Nexus One Android Development] wildmonks:
The symptoms you've experienced is similar to what some others have reported in the past. They have since moved on to the 925mV kernels and the problem has gone away for them. (It was from this report that I wrote the 800 vs 925mV Q & A in the first post).

I believed you have tried the 925mV but still got the touchscreen problem so my theory was that even at 925mV, it was not enough to keep your device stable. Since you have no problems using pershoot's kernel and he uses a UV value of 950mV, I was going to make a custom kernel for you using 950mV as a test.

I don't use any logging apps except for OS Monitor to keep an eye on my battery drainage, instead I just look at the dmesg log.

If the device is still responsive I use "adb shell cat /proc/kmsg"

If the error involves a lockup or reboot, I use "adb pull /proc/last_kmsg"
[Nexus One Android Development] wildmonks:
Beside the commit I added from cyanogenmod github, there's also way more commits added from IR's githib (which in turn he got from kernel.org I believe). It could be any one of those commits that is affecting Linpack.

Still in the middle of adding in even more commits from rc6. Once I'm done I'll look closer at the Linpack score and see if it changes.

BTW: I experienced the same results as you, but doing a reboot and then running Linpack helped me to achieve a 44-ish score again.
[Nexus One Android Development] skorpioneMM:
I have the same issue with all kernels i am tested, first boot linpack goes to up and i get a very higher results but a few minutes later, the linpack goes down 2-4 points.

Another curious issue are with BenchmarkPi, with the 1190 Mhz CFS kernel i got good scores in linpack and quadrant, but with BenchmarkPi, my best score are 975 :confused:

I see people getting 800-850 in BenchmarkPi with no overclocked kernel and with 1113 Mhz kernel, i dont know how it is...

Greetings!!

EDIT: I forgot to say that actually i'm using the new Enomther's ROM
[Nexus One Android Development] B1ny:
Thanks for your kernel :) Been running the 1190 for several days now without any problems. Its very fast and don't seem to use any extra juice :)

Any plans to release one with higher mhz?
[Nexus One Android Development] skorpioneMM:
I am sure that are impossible apply more overclock in the Nexus One.
[Nexus One Android Development] wildmonks:
Yah, I'm sorry B1ny, but skorpioneMM is right. Any more MHz results in a lockup or crash even for my testers with seemingly good cpu's. Consider yourself lucky, my phone seems to be on the bottom of the list when it comes to overclock-ability. I can only run at most 1152MHz...
[Nexus One Android Development] wildmonks:
After you mention this, I gave it a try too with every kernel I can get my hands on (including pershoots and stock cm6 nightly) and I see the same thing. 44 Max and then it decreases down 40's after a few minutes.

I looked at BenchmarkPi and with a stock kernel from the cm6 nightly 07232010, I get results above 1000's. So yah, I dunno how people are getting 800-850 too :confused:

I'm so done with all this benchmarking, I don't want to run them anymore haha.

I just want to go back to coding in the rc6 changes :)

@knightnz

I don't know what it could be that's keeping your Linpack low on the 072210 kernels even after you did a fresh restart/wipe cache. :confused: I haven't been able to reproduce this on the rom I'm using (cm6 07222010 nightly).
[Nexus One Android Development] skorpioneMM:
Yeah i testing this for a lot off days with a lot off combinations ROM's/Kernels and i get the same conclusion that your explained here, after a some minutes was phone booted, the MFLOPS off linpack decrease 3-4 MFLOPS, i dont know if this is a issue with the linpack or really the speed off the phone decrease... :confused:

Another conclusion I have drawn is that when you wipe the cache and dalvik-cache, after rebooting you getting the same high scores, but the same thing, after a few minutes, the scores down again.
[Nexus One Android Development] wildmonks:
Update for .35

Changes since 072210

-Updated source to rc6

-Compiled using neon optimization (sorry forgot to do this on the 072210 .35-rc5 release :()

2.6.35-rc6_AVS-800mV_CFS_1113Mhz_072310.zip

2.6.35-rc6_AVS-925mV_CFS_1113Mhz_072310.zip

2.6.35-rc6_AVS-800mV_BFS_1113Mhz_072310.zip

2.6.35-rc6_AVS-925mV_BFS_1113Mhz_072310.zip

No Audio Boost versions can be found here.
[Nexus One Android Development] fitsnugly:
Biggest warning while flashing on the latest test kernel, ever. ;)
[Nexus One Android Development] wildmonks:
:o

LoL, I wanted it to be seen with no misunderstandings :D
[Nexus One Android Development] fitsnugly:
It's cool Mark Twain. LOL
[Nexus One Android Development] damanrico:
The 35-rc6 kernel seems to a bit slower for me. Even after 2 reboots I score ~3 points less using linpack. I did wipe cache and dalvik cache before updating the kernel.

Maybe it will speed up in a bit.
[Nexus One Android Development] wildmonks:
Scores have actually been about the same for me.

Linpack 44.738 best (ave ~41)

Quadrant 1775 best (ave ~1690)

This was using 2.6.35-rc6_AVS-925mV_BFS_1113Mhz_072310 and the latest cm6 nightly.

The wifi fix dealt with the wifi disconnecting as soon as the screen turns off, despite setting it to have wifi always on. This problem only affected users with wifi mac addresses that did not start with 00. Mine does start with 00, so I never saw this problem.

http://forum.cyanogenmod.com/topic/3165-wifi-fix-possible-to-include-in-cm6/

Edit:

More info: http://code.google.com/p/android/issues/detail?id=6406

http://xdaforums.com/showthread.php?t=712712&page=10
[Nexus One Android Development] skorpioneMM:
Are possible apply this fix in the 1190 Mhz CFS kernel? I have the wifi issue with this kernel...
[Nexus One Android Development] wildmonks:
Ah, ok. Forgot to update, give me a several mins.
[Nexus One Android Development] skorpioneMM:
Wooow thanks, I'll be here waiting :D

Greetings!

EDIT: I sended to you a cool orange juice for this hot summer and for you great work, check your Paypal :D
[Nexus One Android Development] wildmonks:
So sorry it took a long time, but its now posted. as 071010v2.

Wow! Thank you so much and everyone that has given me orange juice. I'll keep on trying my best on these kernels and help answer any questions about anything to the best of my ability. :)
[Nexus One Android Development] damanrico:
I'll give the v2 a go as well. The 'v1' has actually brought me an extra wifi problem. My wifi connection speed (as can be seen when you press on the wifi network you're already connected to) would drop to to 1 mbits after a few minutes. It kept at that 1 mbits. This results in my wifi not tranfering data at all.

I flashed back to CFS 1190 dated 17 july, and my connected stayed at 48-65 mbits, even after 30min of waiting.

Lets see if v2 gives the same problem as 'v1'.

And thanks for anwering my earlier questions. :)
[Nexus One Android Development] wildmonks:
Oh interesting, I wonder if this is a product of the wifi sleep bug or the rc6 changes.
[Nexus One Android Development] damanrico:
Don't seem to have the problem while using V2.

Will keep an eye out for it, if it returns I'll let you know. I've been running the 17 july version with the latest nightlys and never had this problem before, so either V1 actually killed my wifi, or it was just something random. Hard to tell I guess.
[Nexus One Android Development] skorpioneMM:
Ok thanks! I go to try the v2 now, again thanks!

Greetings
[Nexus One Android Development] wildmonks:
Okay, please do. I am looking forward to when cm6 becomes stable and release (I hope its soon). That'll make troubleshooting bugs easier.
[Nexus One Android Development] masterpfa:
Hi the links to your latest uploads do not seem to be active. The following message is received

"Invalid or Deleted File

The key you provided for file download was invalid. This is usually caused because the file is no longer stored on Mediafire. This occurs when the file is removed by the originating user or Mediafire."

EDIT: Links found at this post work, the above message is for the links in the first post
[Nexus One Android Development] wildmonks:
Whoa, thank you so much for bring this to my attention. I messed up when I copy and paste the links to the first post... :(
[Nexus One Android Development] knightnz:
The latest CM6 nightly (as of about 20 mins ago) has a patch from ChainsDD for the SuperUser app to try to fix the no-root on startup issue, which might fix the SetCPU problem of it not setting CPU speed on boot. Shall see.
[Nexus One Android Development] wildmonks:
Yep it's fixed. :)
[Nexus One Android Development] B1ny:
OK, but it feels tempting to test it a bit higher :) Been using it for 4 days now at 1190 without missing a single beat. Use it pretty hard as well, have to connect the charger 2-3 times each day. The temperatures are normal as well, even under charge and heavy use.

So it feels a bit strange if it will not manage a couple of Mhz more....
[Nexus One Android Development] jbbandos:
For me it isn't fixed. SetCPU doesn't show on the notification toolbar, and if I launch it and tell it to detect settings, it will complain of no root access... :( Nothing is working with this superuser, so I just had to flash the 2.0.1 by wildmonks.
[Nexus One Android Development] wildmonks:
Guess the fix isn't perfect yet.. Oh well, at least you have the old su version to flash at your disposal.:)
[Nexus One Android Development] damanrico:
I just went back to 1190 CFS 1707, and my linpack scores are on avarage 3 MFLOPS higher again.

The latest 1190 CFS (v1 and v2) is giving me at least 3 MFLOPS lower.

Tested 3min after eachother on the latest nightly (2407).

So I'm confirming my earlier assumption that the latest kernel runs slower on my device. Since you aren't having this issue, are there more people here that notice this?