yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] wildmonks:
All done, 800mV versions are now up. Enjoy :)

Which kernel are you using? I'll make one for you to try out. In my test the difference in battery drain between 800 and 925 is small so I would guess 875mV would be even smaller.

1190mhz kernels coincide with the 1113mhz release so:

-Apple HID support

-kmobs bluetooth sleep fix

-Bunch of little updates from kernel community. See IR's github (7/26 to 7/28)

I usually flash right on top without any kind of wipe. I've added code to the updater package so that it will clean after the currently installed kernel files (modules) automatically.
[Nexus One Android Development] Bamdroid:
Wifi, camera, video all working for me. haven't noticed any issues. Looks solid. I even flashed the TA succession with it and it's still rockin. :cool:
[Nexus One Android Development] Autinhyeu:
i cant load http://wildmonks.whoisthedrizzle.com/ :( i must find in Mediafire folder :(
[Nexus One Android Development] wildmonks:
Thx! And i like the name, BAM!-droid hehe :D

FYI: 073010 folders on mediafire are the latest kernels. Good thing I have more then one place to host the files.

btw: http://wildmonks.whoisthedrizzle.com/ is currently working for my location, at this time
[Nexus One Android Development] uoY_redruM:
Worked fine for me on the nightly :)
[Nexus One Android Development] wildmonks:
Very good to know. Just downloaded the latest nightly and will be giving it a try too :)
[Nexus One Android Development] ChronoReverse:
Anyone experiencing any problems with interactive and the new kernel? So far it seems to be working fine for me.

It turns out the 3g problem I was having was just network based.
[Nexus One Android Development] Latentk:
Just now flashed from 2.6.34 to 2.6.35 rc6 @ 1190 925mV while running CM6 RC1. I can say that so far my phone is running faster and possibly more stable then at .34. This kernel is outstanding. Possibly the mix between the interactive governer and the amazing kernel. Thank you to monk, the setcpu guys, and everyone that made this kernel great/stable. Awesome work!
[Nexus One Android Development] wildmonks:
Thanks for your feedback Latentk! I gotta say most of the thanks goes to intersectRaven and his amazing skills in putting together a .35 AVS kernel for the Nexus and the amazing amount of detail he posts on his github. The same goes to team douche and their cyanogenmod project. I guess my part would be in maintaining stability for undervolt and overclock operation and to provide all these variant kernels. :rolleyes:

Thanks for your kind words and I'll continue to provide these kernels and answer any questions to the best of my ability :)
[Nexus One Android Development] poochie2:
I couldn't download the 2.6.35-rc6_AVS-800mV_CFS_1113Mhz_073010.zip kernel, the others were fine. I'll just use the 1190 800 mV CFS kernel and keep it low if not just for a small bench.

I tried 2.6.35-rc6_AVS-800mV_BFS_1113Mhz_073010.zip which behaved fine, I liked the interactive governor (I'll use it only when charging for the moment :-) ) but with BFS the touchscreen behaved badly to swipes in LauncherPro.
[Nexus One Android Development] redpress:
@wildmonks big fan of ur work. not a question or anything, i shudnt b doin this sorry. just came by to give u buncha compliments that wud b pretty endless id say if i started.. ive been flashing ur kernels since the .34's and ur work has always been so accurate. my previous account on xda couldnt b accessed i dunno why, but im gun keep following ur well-crafted kernel job of yours. cheers.
[Nexus One Android Development] damanrico:
I hope I don't speak too soon, but after hours of testing I haven't got the 'wifi to 1 Mbps' issue yet while using the latest 34.1 kernel.

Wildmonks, is the wifi module in the 34.1 kernel the same as in the 35 kernel?
[Nexus One Android Development] wildmonks:
They both use the same wifi version (dated 5/1810) but in the .35 kernel, its compiled differently to make it compatible for the .35 kernel.
[Nexus One Android Development] skorpioneMM:
The interactive governor works fine for everyone least for me, i dont understand how this can be :(
[Nexus One Android Development] damanrico:
Since we don't know what's causing this issue for me, do you think the difference in compiling could have something do with it?
[Nexus One Android Development] wildmonks:
Could be difference in rom (rc1 vs nightly), visiting different websites, or a difference in settings.

Example, I'm not always using the flash plugin. I have plug-ins set to On demand. I also clear the cache periodically and run a task killer once and awhile (I like to get my memory back whenever I can :)).
[Nexus One Android Development] wildmonks:
Maybe, it hard to say at this point. Sometimes you don't have the problem, sometimes you do when using .35. I dunno if this will change with .34.

If the difference in compiling is the cause (and not something else like router differences), you can take comfort in the fact that .35 is a "work-in-progress" so as it develops, the problem maybe eliminated. Remember, .34 is more mature, or "stable" which is why its used in the cm6 roms.
[Nexus One Android Development] damanrico:
The router is 100% the same, I haven't changed it's configuration since I noticed this issue. You're right that when I used the 1707 .35 kernel I only got the problem 1 time in 12 days, and with all newer versions of the .35 kernel I've been having this issue multiple times a day.

I'll keep testing new .35 to see if it did get fixed. Thanks for your help.
[Nexus One Android Development] wildmonks:
I mean your router being different then mine. I have yet to run into this problem when I use .35 (but it doesn't mean I will haha).
[Nexus One Android Development] damanrico:
Haha well I'm going to correct you on that, I also have DIR-655, although I have the EU version. ;)
[Nexus One Android Development] wildmonks:
Lol! I had this weird feeling that you might have the same one as I do :p
[Nexus One Android Development] antiochasylum:
If the DIR 655 just that popular? Same router I run. I get sustained 2.5 megs down on my laptop. Wireless N for the win.
[Nexus One Android Development] wildmonks:
I guess it is popular :)

In other news, there some new wifi code (dated 7/21/10) posted on the cyanogenmod github. I'll start working on integrating this into these kernels. If everything goes well, I'll do another release late tonight or early tomorrow.
[Nexus One Android Development] damanrico:
That's great news. I can't wait to try it out. :)
[Nexus One Android Development] antiochasylum:
I know back a while ago there was some bench mark problems, I just flashed the latest rc6 and couldn't peak over 43.7 in linpack, went back to 7/14 1190 immediately clicked 47.4, not sure why...?
[Nexus One Android Development] wildmonks:
Yah... happened around the time I moved from rc5 to rc6. Its been very difficult to pinpoint the change (or changes) that caused the decrease because of the huge amount of little changes in rc6. I'm hoping that as the .35 gets closer to rc7 or to stable status that the performance will return (it usually does).

Maybe after I get this new WiFi module integrated into the kernel, I'll look harder in trying to find the change that affected linpack.

At least it's still a smooth and stable user experience :rolleyes:
[Nexus One Android Development] uoY_redruM:
With the 1190 (7/30 release) and the nightly from 7/28, I hit pretty consistent 44's on linpack and I'm peaking at 48.333 (I literally just hit that about 5x).

Everything still seems smooth with mine..
[Nexus One Android Development] wildmonks:
Update for kernel .35:

-Changes since 073010

-net: wireless: bcm4329: Update to 4.218.245 (combo scan) (cyanogenmod)

-net: wireless: bcm4329: Update to Version 4.218.246 and setband fix (cyanogenmod)

-msm: camera: invalidate frame and stats buffer. (cyanogenmod)

-[ARM] msm: camera: Replace dmac_inv_range hack with dmac_map_area hack (cyanogenmod)

-bcm4329: disable combo scan, for now. (cyanogenmod)

2.6.35-rc6_AVS-800mV_CFS_1113Mhz_073110.zip

2.6.35-rc6_AVS-925mV_CFS_1113Mhz_073110.zip

2.6.35-rc6_AVS-800mV_BFS_1113Mhz_073110.zip

2.6.35-rc6_AVS-925mV_BFS_1113Mhz_073110.zip

2.6.35-rc6_AVS-800mV_CFS_1113Mhz_NoAudBoost_073110.zip

2.6.35-rc6_AVS-925mV_CFS_1113Mhz_NoAudBoost_073110.zip

2.6.35-rc6_AVS-800mV_BFS_1113Mhz_NoAudBoost_073110.zip

2.6.35-rc6_AVS-925mV_BFS_1113Mhz_NoAudBoost_073110.zip
[Nexus One Android Development] damanrico:
Just tested the latest .35 kernel, but sadly my issue is still around. The moment my phone was booted, I wasn't connected to wifi. Disabling/enabling wifi fixed that, but immediately the connection speed dropped to 1 Mbps. When disabling/enabling wifi again, it wouldn't reconnect to my network at all.

I'll probably just get a new router, this issue is starting to annoy me.

EDIT: Well now the 34 kernel is giving me the same problem. So that's it, I'll send my router back for replacement. If only I'm having this problem, and none of you with the same router, there must be something wrong with my router. Sorry to have wasted your time, wildmonks.
[Nexus One Android Development] wildmonks:
You never was a waste of my time! I wanted to solve your problem just as much as you:). Before you get a new router, maybe you can try a few things just to see if it makes any difference.

-Update your router's firmware (you probably already have..)

-Try connecting with 802.11g only.

-Temporary disable security or try a different setting (I'm using WPA2 only, AES)

-Try connecting to another router like to a friend's or to an open hotspot (don't know how realistic this test can be since you can't really do this test for long periods of time).

If any of these makes a difference, then maybe it is your router.
[Nexus One Android Development] damanrico:
- Firmware is up to date.

- Tried 802.11g only sometime ago, but it made no difference.

- Also tried different security settings, again no difference.

- I have a second router, a Sitecom one, but when I connect to that router I get another wifi problem, the well-known 'wifi disconnects when screen is off'. I read that a lot of N1's have problems connecting, or staying connected to, different types of routers. That router seems to be one of them. I don't have the '1 Mbps' issue while using that router though.

I have tried some testing on my DIR-655 router using a laptop, and it seems like whenever I reboot my router it can take up to 30min before my laptop can connect to the router. And even when it's connected, the connection sometimes slows down by a lot.

It shouldn't do those 2 things, so alone for that I could send in my router for replacement. The router doesn't seem to be as good as it used to be.

I still find it weird that some kernels hardly give me this issue, while others almost instantly give it. I guess the wifi drivers/modules differ how well they can handle an apparently bad wifi connection.

It will probably take a few weeks to get a new router, once I do I'll let you know how things worked out.

Thanks again for all the time you put in to helping me think of a solution.
[Nexus One Android Development] pzumk:
I don't have problems with any of the latest BFS 1113 925mV .35 rc's
[Nexus One Android Development] wildmonks:
No problem damanrico, just sorry I couldn't have been any more help. I wish you luck with your new router!

Nice, I hope you continue to not have any problems xPatriicK :)
[Nexus One Android Development] damanrico:
Haha, you're way too kind (as many people have said so already).
[Nexus One Android Development] whoisthedrizzle:
as a final last resort (if you haven't done so already) I would reset your router to it's stock firmware and reupdate it. Remove the network from your computer and recreate a new one. Make sure to "forget" the network from your device too. After it's setup, reboot everything and hope...
[Nexus One Android Development] Goonish:
Crazy question monks, I got an extended battery and when running one of your kernels its not taking full advantage of all the extra mAh. It just stops charging at around 1400mAh. Is this even feasible that within the kernel its somehow limiting this new battery?
[Nexus One Android Development] JonInAtl:
Did you try wiping the battery stats in recovery? Don't know if it would help but its the first thing that comes to mind.

I don't believe the kernel could be limiting the charge though.
[Nexus One Android Development] damanrico:
I hate doing this to you, wildmonks, but here I go again:

My absolute last attempt at getting my wifi working well, I tried intersectRaven new 35 kernel he released today. Till now, I have had no problems with it. My wifi speeds have increased, it's extremely stable, and I've tried creating wifi problems (resetting my router, using different router settings, totally abusing my wifi connection with lots of speedtesting, etc) and it keeps being stable and fast.

I don't know if a new wifi driver/module has been implemented in his latest 35 kernel, if not, do you use a different wifi driver/module than intersectRaven, or do you keep the one he uses?

Again, I hope I didn't speak too soon, and the problem won't return 5 minutes after I post this, but I have good hopes for this kernel version.

If you want me to test something, please act quick, as I won't be home for a couple of days starting tomorrow.

I hope this info can lead to at least identifying what can be the problem. Although it could as well be my bad router, but I still find it weird that one kernel behaves better than the other. So it seems like the kernel does have some impact on the wifi performance.

Again, thanks a lot for all your efforts.
[Nexus One Android Development] wildmonks:
@Goonish

Yes, try wiping your battery stats. I ran into a similar situation as it seems to have solved it for me.

Interesting, IR latest kernels is using the previous wifi code BUT 2.6.35 is now out of RC status and he has already updated his kernels to match. I'd like to make you a test kernel using totally his source with the additions of the overclock but I have to leave in a couple mins for work and won't be back home till tonight (8 to 9 hrs from now). I'll try to make one as soon as I can. Till then keep me informed if IR's kernel is continuing to work good for you.
[Nexus One Android Development] damanrico:
It's working great. My speeds stay around 1200-1500 KB/s, while for some reason the 34 kernel from you that worked fine for me gave me upto 400 KB/s max. This kernel has been nothing but stable for me.

Don't hurry yourself, for me it's 17.25 atm, and I'll be off to bed at 22.00. After that I'm probably not home for at least 1-2 days, but could be more. So I can't really test it until then.

When you say 'previous wifi code', which wifi code are we talking about? As I stated before, the only 35 kernel that worked fine for me was the one dated 1707, although my speeds were also up to 400 KB/s. So if it's that wifi code, that would link some things together.

I'll be sure to donate some extra orange juice. It's so nice of you to create a custom kernel for everyone, it consumes a lot of your valuable time.
[Nexus One Android Development] wildmonks:
Every kernel before 073010 have been straight the same as IR in terms of wifi.

Don't worry about the wasting my time. I'm more then happy compiling/coding for you guys :)
[Nexus One Android Development] damanrico:
Hm, weird that I experienced different things between those kernels.

The moment I'm home I'll test the custom kernel right away.
[Nexus One Android Development] damanrico:
Argh, I got the issue again. So don't bother creating a custom kernel. Glad it happened now, saves you time.

This really was my last attempt at trying something with my current router. Apparently it likes some kernels better than the others, but it's still giving me trouble. I'll send it back to D-Link ASAP.

Sorry for giving false hope.

Btw, what happened to your orange juice glass? This way I can't fill it with fresh orange juice.
[Nexus One Android Development] wildmonks:
Awe shucks, I was hoping it was fixed for you so I can track down and integrate it for others. I really am stumped as to the real cause of this issue.

Oh, my glass for orange juice was lost temporarily when I was digging around the xda account settings hah. Ill work on fixing that tonight, but for now, you will find it at the bottom of the first post :o
[Nexus One Android Development] uoY_redruM:
Just out of curiosity, Wildmonk, how are further overclocks achieved?

I've seen in the linpack tests a guy who had a 1210 (or 12something) overclock kernel and I was a bit curious.
[Nexus One Android Development] wildmonks:
Pretty simple for SVS kernels. You just have to add more speed steps in the frequency table. AVS gets a tiny bit more complicated, in addition to the SVS frequency, AVS has its own table too so more entries are added to that as well. Then to keep things stable I had to code in a routine to switch back and forth from AVS and SVS when the frequency enter and exit 1113MHz or higher.

You can see an example of what the SVS frequency table looks like by going here.

The frequency table is labeled "struct clkctl_acpu_speed acpu_freq_tbl[]"
[Nexus One Android Development] uoY_redruM:
:eek:

I wouldn't know the first thing about understanding that, lol. I was just curious a bit cause I saw others were using an overclock higher then your 1190 (which I assumed was the highest it would go). I'm a fan of the old Tim Taylor "more power!" saying, haha. I run mine at 1190/245.
[Nexus One Android Development] wildmonks:
Update for kernel .35:

-Changes since 073110

-Updated to non-release canadiate status (kernel.org)

-NFS: Fix a typo in include/linux/nfs_fs.h (intersectRaven)

2.6.35_AVS-800mV_CFS_1113Mhz_080210.zip

2.6.35_AVS-925mV_CFS_1113Mhz_080210.zip

2.6.35_AVS-800mV_BFS_1113Mhz_080210.zip

2.6.35_AVS-925mV_BFS_1113Mhz_080210.zip

2.6.35_AVS-800mV_CFS_1113Mhz_NoAudBoost_080210.zip

2.6.35_AVS-925mV_CFS_1113Mhz_NoAudBoost_080210.zip

2.6.35_AVS-800mV_BFS_1113Mhz_NoAudBoost_080210.zip

2.6.35_AVS-925mV_BFS_1113Mhz_NoAudBoost_080210.zip
[Nexus One Android Development] greywolfnz:
USB devices

Have you tried to integrate this http://sven.killig.de/android/N1/2.2/usb_host/

in your kernel ?
[Nexus One Android Development] wildmonks:
I have not, mainly because of a lack of interest... But maybe on my next day off, I'll check it out.
[Nexus One Android Development] Bamdroid:
Dude...this kernel kicks ass.

...that is all.
[Nexus One Android Development] youneek:
Some roms include crazy overclocked kernels (1267+) I have tested pretty much every kernel I can get my hands on and wildmonks are my favorite. After testing way overclocked kernels and some standard, cranking them up doesn't make a difference usually. There is some sweet spot that appears to vary by phone right around 1190. I have had the best success by messing with vm heap sizes, airplane mode, removing gapps, apps on sd, etc. If you are looking for a boost just for linpack scores, try tweaking other things on the phone. You'll be surprised by the difference it can make.

Sent from my Vibrant
[Nexus One Android Development] greywolfnz:
:-) that will be great
[Nexus One Android Development] HTCDevil:
Great over CyanogenMod v6.0.0-RC2. Linpack: about 45 mflops, before only 33. Thanks
[Nexus One Android Development] uoY_redruM:
Thanks for the advice dude.

I was kind of interested in getting my hands on a Wildmonks 1300MHz kernel myself :D
[Nexus One Android Development] pzumk:
1300MHz?! What the hell!
[Nexus One Android Development] uoY_redruM:
It doesn't exist, I was just being unrealistic :D LOL
[Nexus One Android Development] atomizasser:
It is possible add to 2.6.35 kernel the option of 720p that Cyanogen released for 2.6.34 kernel?
[Nexus One Android Development] wildmonks:
Sure! I'll work on it the next chance I get, which should be tomorrow night.
[Nexus One Android Development] nenco:
Thank you so much!
[Nexus One Android Development] HTCDevil:
Thanks so much. Linpack doesn't lie ;)
[Nexus One Android Development] uoY_redruM:
I'll be waiting for this!

I realized after flashing the 720p support MOD that I had lost your kernel :(

Can't wait to get back on a wildmonks WITH 720p!
[Nexus One Android Development] poochie2:
Hello!

I used the 800mV CFS kernel with no problems (2010 07 31 I think). After updating to 2010 07 31 (but I think that the problem was caused by my location) I suffered overheating and very short battery duration in GPRS, which I think is caused by the heavy undervolting interacting with the antenna power. Since then I went for the 925 CFS kernels, but I love low voltages (my battery widget reported at least 2hrs more of battery each day with a lot of standby, 19-21h a day) so I'd like to try some intermediate voltages if you would be so kind to bake me a 1190 CFS kernel at 850-875 mV.

A question: Given all the different clocks supported by the kernel, what voltages are applied to every frequency? I'd like to know so that I can understand better what and how much is undervolted in every situation.

PS: Is it possible to set the CPU at 128 MHz like in the Acer Liquid?
[Nexus One Android Development] codesplice:
My understanding is that the kernel will use the Adaptive Voltage Scaling method at clock speeds below 1113MHz, so it's hard to say exactly what voltage is being used. The undervolt kernels simply set the lowest limit of the voltage for use with AVS. Beyond 1075MHz (so 1113MHz and up), the kernel will switch to using Static Voltage Scaling, and that's when a kernel-supplied voltage table would be used.

And I don't think the clock can get below 245Mhz... that appears to be the lowest the frequency multiplier will allow.

Granted, I'm not a kernel guru so I could be way off on this.... just trying to contribute what knowledge I think I've picked up.
[Nexus One Android Development] poochie2:
The Acer Liquid uses the same CPU, underclocked, and supports that clock. It would seem weird to me that this cannot be done :confused:
[Nexus One Android Development] wildmonks:
Yup, what codesplice said about AVS varying the voltage was spot on! But each MHz speed does have a setting to tell AVS what is the maximum amount of voltage to use. This table in located in the avs.c subroutine and you can see it here.

As for the 128MHz setting, I don't know the reason but its specifically coded to avoid using that speed. But I can reactivate that speed and make a custom kernel for you with your voltage request. I'll work on it tonight when I get back home from work. I'll then work on supporting 720p.
[Nexus One Android Development] mtw4991:
Geezus....720p @ 30fps @ 1190MHZ with 36 hr batt life...what will the mad scientists think of next:D:D:D
[Nexus One Android Development] damanrico:
Wildmonks, the 1 Mbps issue now also starts happening while using my secondary router. So I guess it must be my N1 that has some kind of hardware issue. I can't imagine that 2 totally different routers give me the same problem using all kind of different kernels/ROMs.

If no one else even knows about this issue, it can hardly be a software/kernel problem.

I don't think I can send my phone to HTC for such a small problem (especially with my phone being unlocked).
[Nexus One Android Development] nenco:
this morning i was getting 41 mflops with linpack (froyo+wildmonks), then I played with some roms and later done a nandroid restore, after that i get only 38 mflops

I tryed to wipe all cache and reinstall wildmonks kernel, but i always get 38mflops at max

what can be the reason?

Edit:

installed cfs version over bfs and back to 41 mflops :confused:

Edit2:

back to bfs and 41 mflops still there
[Nexus One Android Development] bigmase521:
Awesome thanks! I was gonna ask about the 720p too :p

See I'm the opposite, I flashed the latest kernel over KoR 1.0 b2 knowing I'd lose 720p, but actually lost the entire camera function lol. I figured I'd live w/o it for a few days but someone just released a patch to disable 720p for other kernels so my cam is back. Now monks kernel + 720p is a match made in heaven!
[Nexus One Android Development] HTCDevil:
With CyanogenMod v6.0.0-RC2 and your 2.6.35 BFS@ 1113Mhz, that's my linpack: