yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] houzuoguo:
OK :) Now I'm flashing #295 nightly and gonna try it again
[Nexus One Android Development] fcisco13:
Working good here, cm 6.1.1 turned wifi off, cleared cache, cleared dalvik, flashed kernel all is good. Thanks

N1
[Nexus One Android Development] redstar3894:
Yay iR is back! :D

Welcome back buddy! :p

Merry Christmas and Happy Holidays Dude! :)

Yeah, I know we debated the merits of PM_FAST vs PM_MAX before... :p

That did seem to greatly improve the wifi calling... at least the dropping out part... :rolleyes:

Yeah, been following some of your intermittent updates to the github/dropbox over the last week or two... ;)

Not quite sure what's going on... people have been having some issues with the wifi driver(s) in my kernels as well... maybe because cyanogen/everyone else was using the wifi driver off of AOSP's 2.6.36 branch (since that was all they updated until recently...:rolleyes:) and there could be slight differences in the calls the driver makes... IIRC they didn't drastically change the mac80211 subsystem between .35 and .36, but that could be the case... :confused:

http://android.git.kernel.org/?p=kernel/common.git;a=commit;h=6990e9491e6dae6ade8f2fd0c6e3dd4b14c942aa

That commit brought the driver up to the latest version in .35.x, whereas the .36.x branch saw the intermittent improvements that cyanogen (and by extension, everyone else...) merged in...

I was thinking about going back and trying to revert all the intermittent improvements, but no one has been really complaining recently about the wifi not working in my kernels... so not sure... the differences (if any) could be very minor between the two drivers...

Anyway, glad you're back! :D
[Nexus One Android Development] d0mo:
I know this has been answered, but what is "noboost"?
[Nexus One Android Development] houzuoguo:
No Audio boost, it may help car dock users.
[Nexus One Android Development] too_pro:
Is this kernel compatible with the latest MIUI?
[Nexus One Android Development] intersectRaven:
It should be...haven't tested though so no guarantees... :p
[Nexus One Android Development] izmar:
What is Wifi fast on the newest kernel?
[Nexus One Android Development] intersectRaven:
It's to stabilize WiFi calling app when the phone goes to standby. :)
[Nexus One Android Development] mikroN1:
Really? Answers on this same page.
[Nexus One Android Development] intersectRaven:
New 2.6.35 HAVS Kernel uploaded! This may be the last 2.6.35 I'll be releasing since 2.6.37 is on its way! Get it from the usual! :)
[Nexus One Android Development] RellikZephyr:
Hey ir

Wondering if your kernel will work with micromods stock gingerbread rom

Always loved your kernel. Thanks for the great work

Rellikzephyr
[Nexus One Android Development] fcisco13:
I beloved MM uses his kernel, i guess u can use a no720p kernel and it should work

N1
[Nexus One Android Development] houzuoguo:
trying 2.6.37 right now ;) thanks a lot
[Nexus One Android Development] intersectRaven:
I'm uploading a better 2.6.37 now. The previous had a WiFi problem. :)
[Nexus One Android Development] houzuoguo:
So true :D

I just installed the kernel, was difficult to find my router and couldn't connect ..

Now downloading 0955 kernel..

Edit:

Cool! No any problem at all :)

Although I don't believe those benchmark apps, but with your kernel I got 1463 the highest score I've got on my device.

I <3 2.6.37
[Nexus One Android Development] houzuoguo:
System has been very stable and fast :)

Battery life is a bit worse though.
[Nexus One Android Development] imfloflo:
Just add a 2nd post for the OP.

btw Can we flash this kernel with lastest AOSP Gingerbread or should we wait CM7?
[Nexus One Android Development] redstar3894:
Since the kernels are based off of cyanogen's source, it will work with AOSP based gingerbread ROMs, but there will be some strange things happening...

I tried one of my kernels with MicroMod's gingerbread ROM and while it worked pretty well, the camera was broken and the Wifi seemed a little flaky...:rolleyes:

Haven't tried one with a 2.6.37 base yet, but that might be a little more compatible depending on what cyanogen has merged into the source (haven't had a chance to take a look at it yet)...

I can't speak for iR here, but the same thing should apply for his kernels as it did for mine since we share most of the same source... but I would wait until CM7... as iR said, some of this stuff is a little experimental just yet... :cool:
[Nexus One Android Development] Gh3rT:
I've tried the new kernel, but the wifi doesn't work with the nightly 295 of CM6....

I've also tried it with the CM7 build, but i get stuck on the bootscreen.
[Nexus One Android Development] intersectRaven:
If you used the 09XX version there is a bug with WiFi. Just use the most up-to-date version I uploaded. :)
[Nexus One Android Development] evoUser112:
What's the worst thing that can happen if I install this kernel on a EVO ASOP Rom?
[Nexus One Android Development] tehgeekguy:
I don't know about the worst, but the most likely is that you'll bootloop. I can almost guarantee that will happen.
[Nexus One Android Development] blahbl4hblah:
I'm getting a Nexus One sometime soon, but I was wondering if someone could tell me the differences between the 8 kernels that are most recent, from his download folder. I did read the OP and the difference between BFS and CFS. I just don't fully understand the rest

Thanks
[Nexus One Android Development] intersectRaven:
CM -> CyanogenMod build (the first is for Desire ROM on N1)

NOBOOST -> no audio boost for making audio louder over BT headsets (if I remember correctly)

WIFIFAST -> fixes the WiFi suspend problem while using the WiFi calling application for TMobile

:)
[Nexus One Android Development] blahbl4hblah:
Thanks, fantastic, I'll probably go with the cm build then, is it based off pershoot's kernels just wondering?

EDIT:

What do you use more BFS or CFS?
[Nexus One Android Development] intersectRaven:
I use CFS more although I flashed a BFS kernel just this morning to test WiFi problem reports which seems to be just an older kernel. This is based on CM's kernel btw. :)
[Nexus One Android Development] ellesshoo:
Should those of us use with ATT use the wifi fast or regular version?
[Nexus One Android Development] savarios:
does the WIFIFAST version have the audio boost?
[Nexus One Android Development] intersectRaven:
Yes it does. Think of it as cumulative from CM -> CM+AUDIOBOOST -> CM+AUDIOBOOST+WIFIFAST... :)
[Nexus One Android Development] savarios:
is it too much to ask for a no audio boost with WIFIFAST version? :D
[Nexus One Android Development] redstar3894:
You would probably be better off going with the 'regular' version...

Wifi fast uses different power management on the bcm4329 wifi chipset that helps with problems people were having with wifi-calling when the screen would turn off...

So in theory the 'regular' kernels should be better for battery life, but I haven't noticed a major difference between the two settings with my own kernels... :p
[Nexus One Android Development] tehgeekguy:
Has anyone had any luck with these kernels and Google Goggles? I've tried IR's and WM's kernels and always get the IPv6 message. It worked a while ago, but it seems that it's no built in to the kernels anymore... is that right?
[Nexus One Android Development] navahoo:
Same error over here...
[Nexus One Android Development] houzuoguo:
:D I heard in a news that IPV4 addresses will be out in 56 days,

would IntersectRaven please put ipv6 support into further releases?

thanks in advance!
[Nexus One Android Development] intersectRaven:
Since you asked so nicely...ok. :)
[Nexus One Android Development] wbknox:
i love the new kernel.
[Nexus One Android Development] tehgeekguy:
I concur, the .37 kernel has been rock solid for me.
[Nexus One Android Development] houzuoguo:
Cheers :D

I'm not sure how much work does it require, if it doesn't take much time, could you please make a kernel with oom_killer disabled?

I think Android system frees memory automatically based on low_mem_killer, but oom_killer in kernel also frees memory according to... oom_adj or something like that.

The oom_killer mechanisms keep freeing up my memory, thus I constantly get over 150MB free memory and can not do much multitasking.

rofl :D

i just read this page:

http://lwn.net/Articles/104179/

the analogy is so funny :D
[Nexus One Android Development] intersectRaven:
I think that has already been done. The kernel already redirects the oom_killer function to the android equivalent so there should be no overlap. :confused:
[Nexus One Android Development] houzuoguo:
Through "AutoKiller" app, I see a background application's oom value increases as I don't use it for a while, and when the oom value reaches a certain number (i observed the value is 15), it gets killed automatically no matter how much free memory I have.

For example, I just observed my Facebook app had oom of 14, and free memory was around 230MB. Then I started Clock app which was never started since boot, now I see Clock app is background app, and Facebook app has disappeared (Killed by oom_killer?)

AutoKiller has a function that temporarily lowers a process' oom value, and it works well here.

so I guess... probably oom killer is still actively managing memory?
[Nexus One Android Development] intersectRaven:
I took a look at the android source and found that the lowmemorykiller driver of Android relies still on the kernel's oom_killer so it shouldn't be disabled. If you want to prevent an app from being killed, you must set the app's oom_adj parameter to -17. :)

*Btw, I believe android set's this somewhere upon application startup or something so I don't know if the value will stick if you change it.
[Nexus One Android Development] intersectRaven:
Scratch what I said before except the edit. It only relies on the parameter and not on the actual oom_kill. I don't know if it should be turned off though since Android's lowmemorykiller functions even before oom_kill is triggered supposedly. :o
[Nexus One Android Development] houzuoguo:
oh... sounds a bit complex :D

Does that mean, low-mem-killer relies both on oom value and low-mem-killer parameters (as set in AutoKiller)?

I notice that my Android always kills programs by oom value, and lowmemkiller does nothing :D but my observation might be wrong,.
[Nexus One Android Development] intersectRaven:
A bit of both maybe. It's like oom_killer runs in the background and still uses the oom_adj parameter while lowmemkiller also uses the oom_adj parameter in order to judge what app to kill. It's just that they differ in when they actually kill a task and what oom_adj value it kills. Oom_killer kills an app as long as there is insufficient free space while lowmemkiller kills apps as long as there is a process that meets its minimum oom_adj value at the specific level of free space specified in its own parameters. (these are all gleaned from browsing the source so take it with a bit of salt as I may be reading it wrong...) :p
[Nexus One Android Development] evcz:
the new .37 kernel running rock solid on my phone!

the phone appear to be sleeping way more often then before :)
[Nexus One Android Development] redstar3894:
Exactly... they both tend to work concurrently... that was my take from it as well... :p

The lowmemkiller tries to keep a certain amount of RAM free for each process level by working off the minfree settings... while the OOM killer is just the standard linux implementation that will free memory on demand when requested by a process, i.e when the lowmemkiller requests that a given process be killed....

I could be totally wrong with how I'm interpreting it, but I think at least iR and I are on the same page here... :p
[Nexus One Android Development] houzuoguo:
thanks for your explanations :)

well, sounds like I shouldn't multitask that much~

By the way, could you please recommend a guide for compiling your kernel?
[Nexus One Android Development] redstar3894:
I learned off of cyanogen's Wiki page, if it still exists.... will check when I get home and post the link.... there's a couple steps that are key.... ;)

Also, don't know what IR thinks, but I'd recommend you screw around with configuring the kernel on a desktop first if you've never done any of that, some of the config options can be a little obtuse at times.... :p and that helps you at least be familiar with how the process works....

Sent from my Nexus One
[Nexus One Android Development] Nighthound:
What a lazy phone... Lol

---
[Nexus One Android Development] m_gl:
@intersectRaven

Hi,

i´ve problems with wifi and the sleep policy.

I`am currently using your .2.6.37_AVS-CM_CFS_20110109_2104 kernel with CM7. When Wifi spleep policy is "always when screen off", i got about 30% cpu load while sleeping after 15min. With "Wifi always on" its about 3% load.

Have to say thats also a problem in cm`s kernel builds. This problem startet with cm 6.1 RC2 kernels and was never fixed.

Could you take a look on this?
[Nexus One Android Development] redstar3894:
Okay, this is generally a good starter guide for compiling the kernels...

http://wiki.cyanogenmod.com/index.php?title=Building_Kernel_from_source

You (of course) don't have to follow all the CM specific parts, and there's always more options and things to play around with, but IMO this is one of the more complete guides out there for getting started... ;)

iR might have some more additions or suggestions, and I might add more a little later... ;)
[Nexus One Android Development] intersectRaven:
It's something about the WiFi driver which is causing this. This is a known problem for sometime now but I don't think anyone has a fix for this yet. :confused:
[Nexus One Android Development] fcisco13:
Is this good?? When i sleep i do not like to be bothered..

N1
[Nexus One Android Development] wbknox:
A new .37 kernel has been updated.

Sent from my Nexus One
[Nexus One Android Development] sir*mez:
Hey IR, can you add the wifi code so that your kernel can work on CM7-Gingerbread pretty please? Here is what you need to make wifi work on CM7-Gingerbread: https://github.com/CyanogenMod/cm-kernel/commit/1db1c4837dfb5dcbf9b87dc17107912ad41e7245
[Nexus One Android Development] intersectRaven:
I'll add it in when nightly is released. It's incompatible with CM6 so I can't enable it in my current releases as I'm still stuck on 6. :p
[Nexus One Android Development] sir*mez:
Thank you sir.
[Nexus One Android Development] tehgeekguy:
Ahhh yes.... Goggles works beautifully with the new kernel. Thanks iR, another solid kernel.
[Nexus One Android Development] imfloflo:
New version for CM7 will come soon
[Nexus One Android Development] daveid:
Typically that means check is MediaFire for a download.

There are kernels posted for today... though the naming scheme is still as it was on CM6, with nothing noting CM7 support.
[Nexus One Android Development] zyonee:
Using the latest CFS for CM in his mediafire folder, and it's working well with CM7. Camera works, haven't tried camcorder yet, though.
[Nexus One Android Development] intersectRaven:
It should work...well I don't know though if they fixed the video yet so unsure since I don't really use that that much. :p I'm still trying to trace something with the mount which seems to cause a hang when copying. Not sure if it's kernel related though. :p
[Nexus One Android Development] fcisco13:
I think a couple of people had slow transfers with one of wm kernels, he said it went away after he reflashed the same kernel, doesnt hurt to give it a try...

N1
[Nexus One Android Development] bimasakti85:
I already try that, but the problem persist...
[Nexus One Android Development] bimasakti85:
Tried your kernel, but seems to have the same problem as in WM, slow rate usb transfer. I'm using nightly CM7 build 5.
[Nexus One Android Development] wbknox:
for those of you who would like to try out the new kernel 2.6.37_AVS-CM-WIFIFAST_CFS_20110118_2254.zip on cm6 push wifi from 2.6.37_AVS-CM-WIFIFAST_CFS_20110115_2201.zip
[Nexus One Android Development] redstar3894:
Wildmonks and I tracked that down, it has to do with a new commit that slightly changed how the mmc slot is initialized ... just wait a few minutes after the phone boots up before trying usb transfer and it should take care of itself.... ;)

Sent from my Nexus One
[Nexus One Android Development] intersectRaven:
Interesting. I experience the problem though even after an hour after boot. :confused:
[Nexus One Android Development] redstar3894:
Strange, this is the corresponding post...

http://xdaforums.com/showpost.php?p=10392466&postcount=2782

And this is what I was replying to...

http://xdaforums.com/showpost.php?p=10391595&postcount=2780

His assessment made sense... that commit looks the most suspect, but the same thing happened with me, it was only a problem immediately after the phone booted up.... after that it seemed to go away on its own after about 10 minutes... at least for me... :confused:
[Nexus One Android Development] intersectRaven:
Major HAVS Kernel update released! :)

- new compiler by redstar (extremely optimized) :p

- complete merge of Zen kernel
[Nexus One Android Development] bimasakti85:
Me too. I encountered that problem after 30 minute after boot.

Btw, could you make the undervolted version of this kernel? I think it would be great for battery life.
[Nexus One Android Development] Prod1702:
Hey IR will the kernel work with the latest CM 7 nightliys
[Nexus One Android Development] harmohn:
...fyi I'm using it no problems thus far :)
[Nexus One Android Development] tehgeekguy:
Can't seem to get WiFi to find/connect using 2.6.37_AVS-CM-NOBOOST_CFS_20110119_2310.zip

I'm on CM6.1.1, and I'll try out the other kernels. I've reflashed it a couple times but still can't get it to work... first time it's happened for me :(
[Nexus One Android Development] blahbl4hblah:
I was wondering if this would work on Rod's Miui rom?
[Nexus One Android Development] knightnz:
Result of a search: http://xdaforums.com/showthread.php?p=10189011&highlight=miui#post10189011

Working perfectly with CM7 build 5 here, fixes the reluctance that the default kernel had when waking up which was getting annoying. Also seems to fix the black-screen problem with the dialer, may be coincidental though.

The previous kernel build worked perfectly with the current stock MIUI build too.

Cheers!
[Nexus One Android Development] blahbl4hblah:
Oh awesome dude, Thanks for the reassurance!

Which one are you using?

Btw, When flashing this do I have to wipe cache?
[Nexus One Android Development] tehgeekguy:
Had to rollback to the 2.6.37_AVS-CM-NOBOOST_CFS_20110115_2201 kernel. Couldn't get WiFi working with any of the latest on CM6.1.1. I'm guess the new ones are more aimed at CM7.

iR, any way we can get some kind of distinction between what's CM6 and what's CM7?
[Nexus One Android Development] blahbl4hblah:
I actually flashed the latest cfs no boost right now, and my wifi is working like it should
[Nexus One Android Development] tehgeekguy:
Hmm... which rom are you on? I may just try a full wipe and see what happens.
[Nexus One Android Development] blahbl4hblah:
I'm using rod's miui 2.5.2, the thing is I think that the video doesn't look 720p
[Nexus One Android Development] tehgeekguy:
Ah, different rom, I'm on CM6.1.1, so it's hard to say. I got another N1 at home I'll try, but for the time, I'm happy with the 1/15 kernel.
[Nexus One Android Development] blahbl4hblah:
Btw, the video recording is 720p haha, my mistake
[Nexus One Android Development] ilos:
Very slow USB tranfert with 2.6.37_AVS-CM_CFS_20110119_2310 under CM7 build #7 ( around 10mns for a file of 74Mb )
[Nexus One Android Development] blahbl4hblah:
I don't have that problem for me, mine only take a few minutes and it's done.

is your ext partition a ext4?
[Nexus One Android Development] ilos:
no it's a EXT3 but don't have this issue with over kernel ( stock CM or WM )
[Nexus One Android Development] blahbl4hblah:
That's weird. EXT4 is faster and works for me
[Nexus One Android Development] intersectRaven:
Latest kernels only have functional WiFi for CM7 unfortunately. I'll see if I can customize my build scripts to get a CM6 kernel out. You can try flashing an older WiFi module if it works? :o
[Nexus One Android Development] blahbl4hblah:
It's unstable on MIUI for wifi
[Nexus One Android Development] LaZiEebOi:
WiFi not working for me on rods 2.5.2 miui using latest IR kernel
[Nexus One Android Development] rjhay22:
Seems normal in comparison to mine... Do you have widgets running right now? Thats probably whats causing the fluctuation.
[Nexus One Android Development] TFJ4:
Thanks for filling my request :) gonna test my phone at 800
[Nexus One Android Development] hah2110:
I have SetCPU, TouchDown, Beautiful Widgets Smaller Home, JuiceDefender and Advanced Task Killer but none are doing anything unless they are called upon.
[Nexus One Android Development] intersectRaven:
that's normal...it's just the OS or widgets doing some background processing...if you want to really control that, just use SetCPU to regulate your CPU speed... :)

on a side note, it seems this kernel appears more stable than the previous one? can anyone confirm this kernel working for them now than the ones before?
[Nexus One Android Development] rjhay22:
Quick question, in the OP did you just update all kernels? including the 850mV?
[Nexus One Android Development] hah2110:
This Kernel is more stable. I do use SetCPU but how would it control those background processes?
[Nexus One Android Development] xspeed9190:
Re: [Kernel - .33.2]intersectRaven's Kernel 04/12/2010 10:39pm

Any luck with 800

Sent from my Nexus One using the XDA mobile application powered by Tapatalk
[Nexus One Android Development] hah2110:
Seems like no one has 800 working well. 825 is working fine for me though.
[Nexus One Android Development] xspeed9190:
Re: [Kernel - .33.2]intersectRaven's Kernel 04/12/2010 10:39pm

850 works great for me . I will try 800 when I get home from work

Sent from my Nexus One using the XDA mobile application powered by Tapatalk
[Nexus One Android Development] Diceman4:
I have the 800 working relatively well it seems. I have not had a reboot in a while now. I'll edit this after I try it for 24 hours.

EDIT: Immediately after posting this my phone randomly jumped into a bootloop... Going back to the 825
[Nexus One Android Development] xspeed9190:
Re: [Kernel - .33.2]intersectRaven's Kernel 04/12/2010 10:39pm

Lol of course it would do that

Sent from my Nexus One using the XDA mobile application powered by Tapatalk
[Nexus One Android Development] TFJ4:
I've had 800 on for 3 hours, no problems for me so far
[Nexus One Android Development] Wysie:
Using 850 now. So far so good. About 6 hours and running. Thanks!
[Nexus One Android Development] intersectRaven:
I have it up and running fine for quite sometime now. We're a very small group of lucky N1 owners who can run this low. :D

Yes I updated all of them. I just need to update one source and my automated compile script takes care of the rest. :)
[Nexus One Android Development] rameshb_v:
Tried 825 and went to boot loop.. 850 looks stable to me...

Is there any chance of more audio volume hack ?
[Nexus One Android Development] r34p3rex:
I'm currently running the 850 AVS kernel

Is it normal for it to flucutate between 850 and 1100? During a call, it goes up to 1250. SetCPU has the limit set at 998
[Nexus One Android Development] intersectRaven:
What you're seeing is the voltage being set by AVS to the CPU. It's still fixed at 998 Mhz so don't worry. :)
[Nexus One Android Development] cjacks519:
I've had 800mV running for about 5hrs and so far so good. No bootloop, no wifi issues. :D

I don't know if this makes a difference or not, but I followed all the command line instructions listed on the first post, and instead of rebooting after flashing the zImage, I went into recovery and wiped the cache and also the battery stats (saw this on the install instructions for a different kernel). Then, rebooted

Does anyone know if the wipe makes a difference at all???

I'll post in about 24hrs or so with an update
[Nexus One Android Development] intersectRaven:
Well, according to some, it helps with stability during the initial flash of an AVS kernel. I haven't had a problem though so I can't really say. :)