yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] youneek:
I have used much higher kernels and can say the absolute best scores I have got are on the 1190 kernel. Its the phones sweet spot I think. When I went higher, the phone becomes less stable and hits the same scores. I have been tweaking other things on the phone and seeing great results just from those tweaks. The highest scores I get are when I do a total wipe, don't install google apps and run the tests in airplane mode at 1190 and you can see my scores all over linpack. There are 2 kernels in other parts of the forum that are way overclocked at the highest setting possible but it never runs very well and would be pointless to run other than to say you have a high score. I currently run at 1190 always with no problems and hold a tom of the highest scores. I've helped a few other people on there get their scores to with simple tweaks to the phone.
[Nexus One Android Development] flak0:
@Wildmonks this kernel is awesome very little heat increases compared to the previous ones. Only thing is I'm getting 1850 in quad with 1152 and 1771 with 1190. Both ondemand and performance. Results vary slightly. Any ideas what may cause this. I noticed the neon optimizations are an improvement in graphic intense applications.
[Nexus One Android Development] damanrico:
Well after a reboot the 1707 kernel also shows slightly less MFLOPS, but still ~1 MFLOPS higher than the 2307 kernel. Maybe it was just a little unlucky, not sure. Will keep testing.

Don't look into it too much. I'm just saying what I experience, but since there are so many factors that can cause lower scores, I'll keep testing to really make sure if it's the kernel or not. So for now just ignore my posts, unless more people are noticing it, hehe.
[Nexus One Android Development] B1ny:
I see the same, dropped from 47 to 43. Haven't gone back to double check though.
[Nexus One Android Development] wildmonks:
As the development of 2.6.35 progresses, performance is bound to fluctuate. If there is a large drop in performance then the kernel community will get worried and act to try and resolve it. In fact this is what happened in early June. http://www.phoronix.com/scan.php?page=news_item&px=ODMxNQ

There is a site dedicated to monitoring kernel performance daily, unfortunately there is no specific android platform in which these tests are run but you can get a sense on how kernel performance fluctuates. In fact there seems to a slight downward trend in some of the benchmarks.... http://www.phoromatic.com/kernel-tracker.php

(BTW, don't use IE to go to this site, IE doesn't work, and chrome has trouble displaying the results table. Firefox seems to work fine).

From a user standpoint, if performance is your number #1 priority then its best to use a kernel that gives you the best performance.

Moving on to other realms of kernel testing, I've notice an increase in battery life when on standby. (overnight drain 5% in 7 hours). This can be somewhat subjective but from looking at the dsmsg logs, battery life is pretty good with this kernel. To my eyes, mA drops that's in the single digits is good :) http://pastebin.com/w9kHMtuJ

Hmm.. not really sure. I'll have to double check, I might have made a mistake in the MHz table... For now, I suggest sticking to the kernel that works best for you needs and wants.
[Nexus One Android Development] waylo:
Thanks so much for the adb commands. And also entertaining the apparent only guy who hasn't jumped on the 35/6.0rc1 bandwagon :p

I finally got the screen to become unresponsive (at work) then left it in that state and got home to pull the log. Looks like it starts off with a few mmc0 errors in the beginning, which gradually become more significant. The very last entries show a lot of mmc0 errors, brought on by attempts to turn on the screen, consistent with this:

http://code.google.com/p/cyanogenmo...ty Version Model Owner Summary Stars Modified

Running the latest 34.1 925mv to see if I get the same thing.
[Nexus One Android Development] wildmonks:
Ah, very informative, thanks for the link to that issue thread! So it would seem there's a link between abnormal sd card operation and the screen becoming unresponsive.

The commenter suggests the user's sd card is getting bad but I'm not so sure about that. From looking at your logs (thanks for providing it :)) your device has trouble reading/writing to the card mostly when it is idle at 800mV. My guess would be that your sd card (or the chip on the phone involved in read/write to sd card) needs more voltage.

Let me know if 925mV works out for you. If not, then your current sd card or your device needs more power for normal read/write operations.
[Nexus One Android Development] waylo:
Thanks for the commentary. After seeing those same errors, I figured it was probably the undervolting altering the ability to access the sdcard.

Do you have any recommendations/warnings about running the .35 kernels with CM5.0.8? Is it compatible? The pershoot .35 kernels have this warning (of which I understand very little!):

Known Issues (this only effects non-froyo users):

-vold will throw a SIGSEV upon kernel boot. You can download a patched vold below, which will return 0 for SDIO during UEVENT, in attempts for some speed up during this process. vold’s structure has changed for Froyo, and as such, no patched vold is needed (it terminates once it connects) for that platform.

-when unplugging and then plugging back in (USB), then hitting USB mount, vold will throw a SIGSEV. Wait until you hear the USB notification on the phone (after hitting mount the first time), prior to hitting mount again. Then you will see the popup on your computer.

-Slight delay in showing USB pulldown, when unplugging and then plugging back in.

-if you repeatedly receive a USB notification while plugged in (and vold is SIGSEV’ing), try rebooting the phone with the cable plugged in, or unplug, wait a few seconds and replugging back in.

-After mounting and the window with the contents of your sdcard appears on your computer, after transferring contents and closing the window, the USB mount will automatically dismount.
[Nexus One Android Development] wildmonks:
Hmm.. I can't verify pershoot's findings with .35 and cm5.0.8 and his workaround because I have not tried this combination but I greatly trust his observations and methods.

My recommendation would be to avoid using .35 on cm5.0.8 (or any non-froyo based rom). The above mention issues looks too inconvenient to work with. If you decide to try .35 and you run into issues like delay in USB mounting to the computer or long boot time then you can try flashing pershoot's vold patch.
[Nexus One Android Development] whoisthedrizzle:
So the superuser issue is marked as fixed by cyan on the issue tracker!

Just downloaded the new nightly but I don't think the change made it to this build :eek:

Maybe tomorrow...
[Nexus One Android Development] wildmonks:
Awe... well, I hope a new build gets compiled and released soon.
[Nexus One Android Development] wildmonks:
Update for kernel .35:

-Changes since 072310

-input: gpio_event: make driver be more robust against incorrectly configured lvl trigger irqs

-Input: gpio_event: Don't call gpio_cansleep before gpio_request.

-net: wireless: bcm4329: Add wakelock processing in ioctl and messaging

-[ARM] msm: kgsl: Remove support for mmap from the kgsl driver.

-ashmem: Fix ASHMEM_SET_PROT_MASK.

-cpufreq: interactive: New 'interactive' governor

-UTF-8 has been enabled for unicode support

2.6.35-rc6_AVS-800mV_CFS_1113Mhz_072410.zip

2.6.35-rc6_AVS-925mV_CFS_1113Mhz_072410.zip

2.6.35-rc6_AVS-800mV_BFS_1113Mhz_072410.zip

2.6.35-rc6_AVS-925mV_BFS_1113Mhz_072410.zip

No Audio Boost versions can be found here.

Special thanks to whoisthedrizzle for graciously donating his server space and bandwidth to mirror these kernels! :D

You can access the new mirror site by going to http://wildmonks.whoisthedrizzle.com
[Nexus One Android Development] whoisthedrizzle:
:D Ah good now at least it's getting used! Use the hell out of it 'til bluehost tries to upsell me :rolleyes:

Instant transfers FTW! 4-6 Seconds from media fire is just too long these days:p
[Nexus One Android Development] wildmonks:
Again, major thanks for the host :o
[Nexus One Android Development] andrewv88:
tethering working on new .35rc6 ?

coz i have troubles with it on my .34.1 pershoot kernel
[Nexus One Android Development] whoisthedrizzle:
So what's up with this new governor - should I be using interactive vs. ondemand now?

edit: interactive seems to be the sweet spot i guess.. averaging 1875+ in quadrant... closest I've gotten to the 1908 I got last week :D 1894 on the 7/24 BFS on Interactive @ 1190
[Nexus One Android Development] wildmonks:
Just confirmed that Wi-Fi and USB tethering via the built in options in CM6 nightly 07232010 using kernel 2.6.35-rc6-925mV-CFS-072410 works.

Not sure if your problem is kernel related though.. What rom are you using and which tethering method?
[Nexus One Android Development] wildmonks:
Sorry... it would have been a good idea to post some documentation on the interactive governor... my bad, hehe

Too early for me to tell. I'll start using interactive exclusively to see what I can observe. From reading the document, it looks like a replacement to BFS. :confused:

Edit: Just saw your Quadrant score.. whoa, nice! :D
[Nexus One Android Development] yuripave:
wildmonks you are awesome!

Did you add unicode because of my question on the mount cifs thread or you just add it because you need it as well?

It works beautifully btw.

Now I can stream my media at home to my N1!

Especially very useful combined with RockPlayer =)

I was trying to figure out where I can get the arm-based nls_uft8.ko but I fail. You made my day.

Thanks for the kernel and I've been using the 800mv CFS and it's stable for me.

Before Cyanogen Mod 6.0 RC1, I was having problems on camera with your kernel (both 800 and 925). It might be 6.0 or your updated kernel fix my problem.

THANKS

I am gonna buy you an orange juice, stay tuned:)
[Nexus One Android Development] wildmonks:
Lolz, I did actually saw your question and wondered if I can integrate it. Found out I can and it didn't make the kernel any bigger so I enabled it for everyone to use :D

I too have a several unicode file names (anime) on my media drive so it is some benefit for me as well ;)
[Nexus One Android Development] whoisthedrizzle:
Yeah first thing I noticed with this kernel/governor was the increased response on BFS and it's not like I had issues with response before, but even at 998-1075 Mhz it sometimes lagged pretty bad after being asleep overnight. It would just sort of slow to a crawl until I got some random ADW FC and had to reboot.

CFS is nice and solid too @ 1775-1825 in Quadrant without much fluctuating and seems to like ondemand > interactive.
[Nexus One Android Development] wildmonks:
I like the interactive governor. It ramps up near instantly when I wake the phone from standby and start swiping the homescreen. Ondemand would take a split second longer creating a noticeable stutter when I do this.
[Nexus One Android Development] whoisthedrizzle:
yep. I'm going to try out a 245/245 sleep profile again and see if I get any issues waking
[Nexus One Android Development] wildsjustin:
Can someone explain how to install Kernel thr ADB push way? :(
[Nexus One Android Development] wildmonks:
First off you need to make sure you have an unlocked bootloader and root access in order to use adb and flashboot.

From the zipped up kernels provided, extract the "zImage" file (in the /kernel folder) and the "bcm4329.ko" file ( in the /system/lib/modules folder).

Use adb to push bcm4329.ko to the phone.

adb push bcm4329.ko /system/lib/modules

After its been pushed sucessfully, restart the phone into the bootloader menu

Note: You can use this command to do this for you quickly.

adb reboot bootloader

Once your in the bootloader screen type:

fastboot flash zimage zImage

Note the capital "I" in zImage.

After the flash is complete, restart the phone and your done.
[Nexus One Android Development] wildmonks:
I actually stopped using 245/245 sleep and instead use '245/998 sleep conservative'.

Reason being because during a call, when I put the phone next to my face, the screen turns off and it uses the sleep profile (which really, its the screen off profile). I don't know what the consequences are for forcing the phone to use 245MHz during a call but I thought it would be better not to force 245MHz while the phone is being used for something important.
[Nexus One Android Development] whoisthedrizzle:
Ah true. I actually hardly use my phone as a phone these days, I didn't even consider that :o

fun fact: Disabling dithering with some of the LWPs seems to be a little more stable with this beast

temps are so low... try as I might, I can't break 33 degrees.... high linpack for the night:
[Nexus One Android Development] damanrico:
The latest CFS 1190 kernel runs really great. I'm not noticing the slower linpack scores anymore. It's as fast as the 1707 kernel and before.
[Nexus One Android Development] wildmonks:
Oh really? That's unexpected, good to hear :)
[Nexus One Android Development] damanrico:
Yeh, I guess I was just a bit unlucky with the previous kernel. As I said in one of my posts it was just me writing what I noticed, I couldn't say if it was the kernel for sure. So maybe it was something else, who knows.

But I'm glad the latest kernel is working great from the start, saves me time comparing kernels. :)
[Nexus One Android Development] damanrico:
The bringer of bad news and weird problems is back again.

The wifi problems I said I had using the 2307v1 kernel are also in the 2407 kernel. My wifi connection dropped down to 1 mbits, and I keep getting no connection could be made or similar errors while trying to access internet content.

Flashing back to 1707 for now, which never caused that problem for me.

EDIT: Before flashing back to 1707 I noticed I couldn't reconnect to the network. It kept saying 'Disconnected' and you couldn't see it trying to connect (a common problem for me, sadly). After flashing back to 1707 I get the same 'Disconnected' error. So now it doesn't seem to matter which kernel I use, I'm having the 'Disconnected' problem. So maybe I'm just having bad luck using the newer kernels, and 1707 could actually have the same problem. The problem happens quite randomly, so ignore what I said again, it's probably bad luck on my part.

EDIT2: After waiting for a few minutes on the 1707 kernel, I was able to connect to my network again. Lets see if the 1 mbits problem popups, as uptill now I haven't seen that problem while using the 1707 kernel yet.
[Nexus One Android Development] dogiedogie:
Question, is there 1190Mhz 800mv RC6 BFS somewhere that im missing?
[Nexus One Android Development] Autinhyeu:
here: http://www.mediafire.com/download.php?68xb2mb6pjrf15f
[Nexus One Android Development] dogiedogie:
Thats the 925 I already found :(
[Nexus One Android Development] wildmonks:
I have yet to make a 800mV version of the 1190MHz kernel. If you want, I'll make one for you. :)
[Nexus One Android Development] dogiedogie:
Please ;) Im so OCD about battery, yet I need my mhz, such a terrible combination.
[Nexus One Android Development] whoisthedrizzle:
Still running smooth 12+ hours in! No slowdows or stutters at all so far!
[Nexus One Android Development] wildmonks:
Awesome! :D

And the host you donated is holding up just fine ;)

(I have the first post kernels linked to your host)

Here yah go just for you ;)

(well anyone can download it I guess heh)

2.6.35-rc6_AVS-800mV_BFS_1190Mhz_TEST_072510.zip
[Nexus One Android Development] whoisthedrizzle:
Going to ninja this to test too :cool:
[Nexus One Android Development] dogiedogie:
*slaps hand* mine bizatch xD
[Nexus One Android Development] wildmonks:
Heh! Now now, there's nuff for everyone :p
[Nexus One Android Development] whoisthedrizzle:
I see you snuck your way into the top 10 :D

Which kernel date was that?
[Nexus One Android Development] andrewv88:
cm6-rc1

strange, before i updated the kernel the tethering works fine to me

by the way what a difference between regular and the nightly mod ?

thanks
[Nexus One Android Development] wildmonks:
Actually, that's not me. It's YouNeek, he said he would do a post in my name if I made him a kernel. (a highly unstable one btw).

Oh, that does sound like a kernel thing since it happen right after you flashed his kernel. He recently released a new kernel that you can try, if you havent already, and see if tethering is restored or you can try one of my kernels (clearing cache/dalvik before flashing might help too).

The latest nightly has made lots of changes since RC1 like the ability to change color of the status bar and music controls on lock screen (and many more) but it also has introduced some bugs that have been affecting some or all users.
[Nexus One Android Development] ManticoreX:
In the CM6 nightly I am using (and should work in all CM6 versions I assume) I was using an HID bluetooth keyboard (Apple Wireless keyboard). After flashing your kernel I loved the performance increase, but the keyboard would connect but not function. Is this missing in the current release of the kernel? When I restored my nandroid backup the keyboard worked once more.

Thanks again for the great kernel. Otherwise it seemed perfect (Never seen benchmark scores so high on my phone!)
[Nexus One Android Development] whoisthedrizzle:
Bluetooth is probably still boned in the nightlies since 7/24
[Nexus One Android Development] wildmonks:
Oh, you know what, I have not enabled support for apple BT devices since well... personally I don't have one haha. Which kernel are you using/like the most? I will compile it again with apple device support and give it to you to try. Then I'll make sure to include it in all future release.

BTW, this applies only to apple BT devices, the current kernels will work with other BT mouse/keyboard devices (Tested with a logitech dinovo mini).
[Nexus One Android Development] ManticoreX:
I would appreciate it. I am using the 2.6.35-rc6_AVS-800mV_BFS_1113Mhz_072310.zip version. (I haven't played with it enough to know if the 800mV will give me problems. Are there any telltale signs that it wont work correctly? I tried the camera and it seemed to work fine)

Thank you
[Nexus One Android Development] wildmonks:
With the 800mV I personally experience constant edge/3G switching when at work (low reception at work). The 925mV stops this for me. Also 800mV may cause touchscreen problem when waking the phone from sleep/standby.

Sorry I can't make a new full set of kernel at this time. Currently away from home and I'm going to use VNC to remote access and compile this kernel for you. :)
[Nexus One Android Development] knightnz:
I'm guessing Apple's idea of the Bluetooth "standard" differs from everyone elses then?
[Nexus One Android Development] wildmonks:
Hah, yes your right. It takes a extra set of code to support Apple HID and another set of code to support the Apple Mighty Mouse.
[Nexus One Android Development] wildmonks:
Here you go. Let me know if it works. :)

2.6.35-rc6_AVS-800mV_BFS_1113Mhz_AppleHID_072510.zip
[Nexus One Android Development] ManticoreX:
Works perfectly with the keyboard! Thank you. Quadrant seems to be benchmarking it seems to clock in ever so slightly slower than previously, but I am going to just chalk it up to randomness. Thank you for building this version for me!
[Nexus One Android Development] wildmonks:
Cool! Thanks for reporting.

I don't think enabling Apple HID support would affect speed so yah, its probably benchmarking score variance. From now on, I'll enable this in future releases since it doesn't add a noticeable amount of bulk to the kernel.
[Nexus One Android Development] nxt:
This should work just fine with RC2 CM6 right (just released)
[Nexus One Android Development] brian(::
thaaanks :)
[Nexus One Android Development] wildmonks:
It should, I just updated to RC2 and flashed the latest 925mV CFS kernel. So far so good.
[Nexus One Android Development] whoisthedrizzle:
still having to flash SU 2.1?
[Nexus One Android Development] wildmonks:
SetCPU seems to be working fine for me. It sets the min/max scaling like it should @boot
[Nexus One Android Development] jbbandos:
I still have to flash it... With 2.2 quickboot won't work, rom manager won't reboot into recovery, fancy widget takes some minutes to show the time, etc.
[Nexus One Android Development] wildmonks:
Weird... reboot into recovery using rom manager works for me. I'd say try to wipe everything and flash RC2, but that's a pain in the ass to reload all the apps/settings. I'd rather just flash su 2.1 if I were in your shoes and save the wiping for the final CM6 release.
[Nexus One Android Development] kindiboy:
First of all I want to say thanks alot for all your hard work and joyful spirit.

I have a question wildmonks, I have no clue if this is the right place to ask but here it is anyways

the company that made the wireless radio released a new driver to fix the sleep loss of wireless connection (even when it's set to 'never') is the kerenl where this goes? if that's correct, would you be able to put that in ?
[Nexus One Android Development] wildmonks:
Thanks for your kind words and compliment :o

There was a "fix" that has been included in these kernels. Are you still experiencing this issue on the latest kernels? I have not personally experience this problem (problem seems to only exist on first byte, non-zero wireless Mac address) so I can't verify if the fix solves the issue (I believe it does, I had a request to add it in and have not heard a compliant about the fix not working yet).

http://xdaforums.com/showpost.php?p=7316173&postcount=811
[Nexus One Android Development] whoisthedrizzle:
i can confirm this is a pain in the ass. just megawiped and it didn't seem to make much difference. def keep su 2.1 handy...
[Nexus One Android Development] wildmonks:
Hmmm.. I hope others who experience this too, report it so this can be properly fixed for all users.

Guess that means I won't be taking off the superuser downgrade from the server anytime soon. :p

BTW, kinda unrelated but I find that in the past nightly, only if I megawiped, I would have to change the vm heap size to 24 and reboot to stop the FC. After doing that, the FC stop and I can restore the heap size back to 32. Dunno if this is required in RC2.
[Nexus One Android Development] whoisthedrizzle:
yeah RC2 either way isn't playing nice with me. no matter what kernel i try they are all auto detecting at 833/userspace w/ the slider maxed, which I don't recall ever happening.:(

1113 and 1190:
[Nexus One Android Development] wildmonks:
I was able to reproduce your finding and have confirmed its a superuser issue.

What I did was after rebooting the phone I immediately unlocked the screen and tried to load up SetCPU as fast as I could. Notice it took a over a minute for SetCPU to load up and when it finally did I got exactly what's on your screenshoot.

What I usually do after rebooting the phone is let it sit for a minute at the lockscreen (wait for the screen to turn off by itself at the lockscreen) and then unlock the screen and load up SetCPU. When I do this, SetCPU is working normally.

For curiosity sake, I downgraded Superuser to 2.1, rebooted the phone, unlocked the screen right away and loaded up SetCPU as quickly as I could and found that it loaded up with my settings normally. (I noticed too that it loads up all my widgets much more quickly when I downgraded to SU 2.1).

So it looks like the new SU still doesn't load up as quickly as the old SU 2.1.

At this point I see two solutions, wait at the lockscreen for a minute or so when you first startup/reboot the phone or downgrade to SU 2.1.

Hopefully this gets fixed soon, this issue might help reduce all the other problems I'm seeing in the recent posts on the CM6 thread.