yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] wildmonks:
I haven't seen that 1%/3hrs since I fully charged the battery... It might be because the battery was fully top up with charge that it took awhile for the precentage to start dropping.

I'm now seeing the usual 1%/hr drain on standby. My wifi has been off the whole time.

How about you?

edit: I just hooked up my phone to the computer and looking at the kernel msg, I can see a steady decrease in battery capacity where I did not see one when the battery was fully charged. I don't think this wfi_rate change works in the long run for avs... :(
[Nexus One Android Development] intersectRaven:
Too bad...anyways, I really didn't think it would work since it's just used as a condition check in pm.c. (unless there's a hidden call somewhere...) :p As for me, the kernel I tested last night was the one with wfi_rate modification ONLY and I was consuming 1% as usual. I also have WiFi on BUT set it to turn off when idle and unplugged. :)
[Nexus One Android Development] big_adventure:
Hi Wildmonks (and iR - following along) -

I used the 601 .34 BFS 800mv OC kernel on my Nexus for 10 days with zero issues. I ran it for 5 days OC'd to 1113, then 5 more with the OC reduced to 1075 (following the revelation that the CPU didn't support AVS at 1113). No application problems, no slowdowns, no lockups, nothing.

On Friday, I pushed the 0610 800-BFS-.34 and started to have issues:

- Twice, the phone was unresponsive while sleeping - it wasn't off, but it did not respond to the power button (or any other button) at all - the screen didn't come on. Unfortunately, I was not by the computer either time, so I couldn't ADB to see what was what. My only recourse each time (since I needed the phone) was to pull the battery (I tuened my N1 into a CrackBerry?!?!?!).

- Three times the phone became nearly completely unresponsive while using the Gallery. It eventually popped me a "process system" wait/FC dialog. In each case, I had to reboot the phone.

- Launcher Pro became unresponsive twice and had to be killed.

During all of this, I was OC'd to 1113 and running the ondemand governor.

Regrettably, I spent an hour trying to force a problem while connected and logcat'ing, to no avail - I couldn't recreate the problems.

So I've gone back to the 0601 kernel (since Saturday evening) and have had zero problems since under extreme use (several hours of calls, 50 SMS, a couple of hundred GTalks, multiple apps, video and photos, a bunch of email, some twitter and facebook, etc.). I bumped the clock back to 1075 as well.
[Nexus One Android Development] intersectRaven:
wildmonks, when I applied your power_collapse tweak, I got errors when the N1 was trying to go to sleep fyi. :)
[Nexus One Android Development] taney:
I've been using your 1190 kernel since the last update. It's still the fastest kernel for me that's stable. It's missing a lot of the new CM commits. No pressure, but I was wondering if you were planning to release an update in the future.

Thanks again!
[Nexus One Android Development] eidros:
+1 This is the most stable and best performance for my N1.
[Nexus One Android Development] Androidity3000:
Dear Wildmonk,

Do you plan on continuing to update your kernel with new CM7 changes? Also, if you are even still active or alive, can you give us a link to download. I cant find one ANYWHERE.

||

Or: anyone know of a similar yet updated kernel with a valid link?
[Nexus One Android Development] earth08:
Is camera working on this new version?
[Nexus One Android Development] Bi0haZarD:
http://www.mediafire.com/?w6dcq9haowdrd
[Nexus One Android Development] hkxforce:
Does anyone still got the kernel file?

The MediaFire link "Shared Content Belongs to Suspended Account.", not working anymore.
[Nexus One Android Development] XIPRELAY2010:
Diddo

Does anyone have a copy of these ?
[Nexus One Android Development] manuel16:
copy please

---------- Post added at 06:32 AM ---------- Previous post was at 06:22 AM ----------

please post it again, anyone who have a copy please upload it again

thanks ! :)
[Nexus One Android Development] Gablu:
I need a mirror... Thanks :)
[Nexus One Android Development] Imperial.mack:
yes does anyone have a mirror?
[Nexus One Android Development] clustered:
anyone got a mirror?? thanks...
[Nexus One Android Development] ocd_amp:
Link is DEAD! No files Found! Need Mirror!
[Nexus One Android Development] lamaqc:
Need Mirror too !

Thanks !
[Nexus One Android Development] pajerm:
here they are! I found these kernels in my hard drive, should be the latest available. :highfive:

2.6.38.8_AVS-CM7_CFS_20110707_0839

2.6.38.8_CAVS-CM7_CFS_20110707_0841.zip

2.6.38.8_AVS-CM7_CFS_20110713_1002.zip

2.6.38.8_AVS-CM7_CFS_20110724_2035.zip

2.6.38.8_AVS-CM7_CFS_20110917_1151.zip

[MENTION=4115515]lamaqc[/MENTION] [MENTION=5882238]ocd_amp[/MENTION] [MENTION=260795]clustered[/MENTION]
[Nexus One Android Development] ocd_amp:
Well which one to use? And supports 2 way call recording from Kernel?

I forgot to say Thanks.

Right now I'm using MIUI 2.3.30 which comes with Cyanogenmod's toxygene kernel. Call Recording is horrible on this kernel. But it is stable, and smooth, everything else works. I am quite confused about which kernel listed below to use. I need Stability, and call Recording function. I don't care much for overclocking and flashy governors. Ondemand and Deadline are the ones I believe are in use in MIUI even though there is no mention of it in MIUI but I believe that's whats in use. Again thank you for uploading these. Let us know which you are using and why?
[Nexus One Android Development] mrtornt:
How about this..

intersectraven.euroskank.com/kernels/Nexus%20One/2.6.38.8/20120112_14XX/
[Nexus One Android Development] ocd_amp:
Thank you!
[Nexus One Android Development] Alefello:
Anyone could post the kernel or a mirror for it?

I'm searching a 1190 kernel, and those posted in the previous post are intersectraven's kernels with lower OC.

Thank you
[Nexus One Android Development] dictionary:
Running the 6/12 CFS 925uVoC kernel, ran into some issues in sleep. Phone would become unresponsive. Hitting power button would sometimes bring the screen to full brightness. Other times, just the capacitive lights would turn on. When the screen DID turn on however, it would not respond to touch at all. Once you hit the power button while the phone was in this state, it brought half power the screen, as it would barely light up. Only resolution was a crackberry battery pull. =\.
[Nexus One Android Development] mtw4991:
Flashed the 0612_925mV_CFS yesterday and got 1.3% per hour overnight drain. SetCPU was 1113-Performance with sleep profile set to 245/245. Sync'ing gmail and twitter, email accts x 2, battery graph and 3 widgets running in the backgroud with LWP.

I've had no issues whatsoever with sleep state, touchscreen, fc's, etc. Quadrant ran at 1113/1113 w/performance governor was 1809! Linpack avg was around 40 avg and short bench was around 190-200.

Fyi, I calibrated my battery correctly(finally) and it auto-shutdown this morning with 9mAh@1% left!

Nice job Wildmonks!
[Nexus One Android Development] wildmonks:
Very nice! I too get somewhere between 1-1.5% overnight drain on that version, which is the same as the 061010 version. The commit I added is not doing anything for AVS (not hurting either it seems) so I'll probably remove it in the next release.

It's probably a good idea for me as well to recalbrate my battery after all the battery testing I've been doing with this and other kernel (and getting that 1%/3hr drain at 100%.... -_-; )
[Nexus One Android Development] overground:
Is the battery recalibration we're talking about 1. running down the battery till the phone will not power on anymore 2. plugging into ac power until 2hrs after led is lit green 3. wiping battery stats in recovery? Thanks again...enjoying these kernels.
[Nexus One Android Development] mtw4991:
Pretty much. I ran the battery down completely, tried to reboot a couple of times until nothing, plugged into ac wall charger until full plus 30 minutes, wiped cache, dalvik, battery stats, then flashed kernel.
[Nexus One Android Development] Mr.Kakarot:
So being new, how do I know which kernel to use? I am on a rogers nexus 1, rooted and unlocked now...

thx?

ps: how do I apply the kernel?
[Nexus One Android Development] mtw4991:
You read, research, read, research, learn, test, curse, read, research, read, research, test, curse....you get the idea
[Nexus One Android Development] wildmonks:
-If you haven't done so already, install Amon_RA's custom recovery.

-Copy the kernel (zip file) to the root of your sd card.

-Boot into recovery mode

--Boot the phone while holding down the VOLUMEDOWN-key.

--Navigate to RECOVERY with the the VOLUMEDOWN-key.

--Press the POWER-key to select.

-Do a "Nand backup" (if something goes wrong you can then do a "Nand restore" to restore your phone back to the way it was).

-Use "Flash zip from sdcard" to flash the kernel into your phone.

This kernel is a popular one (of the 4 I made) so you might want to try this first: 2.6.34_AVS-925mV_CFS_1113Mhz_061010.zip
[Nexus One Android Development] wildmonks:
Lol! "curse" :p
[Nexus One Android Development] wildmonks:
Bleh... okay. I'll work on that :(

Thanks for the heads up :)
[Nexus One Android Development] wildmonks:
Because it looks like there's no observable improvement in battery life with the 061210 version and the power_collapse tweak that I added causes sleep errors (thanks IR for pointing that out), I recommend using the 061010 kernels.
[Nexus One Android Development] SimFox3:
Thanks for making a HAVS kernel WITHOUT the Audio Hack. Please continue releasing the 925mv-CFS version without the Audio hack.

Thanks again.
[Nexus One Android Development] MrNameless:
how can i make a boot.img ?
[Nexus One Android Development] intersectRaven:
The easiest way would be to use fastboot to flash it on your device, make a nandroid backup and copy the resulting boot.img. :)
[Nexus One Android Development] wildmonks:
No problem dude, I will :)

Agree with IR, that's much easier. But if your curious on how to make one on the computer see this post by pershoot (that was posted on IR's thread :).
[Nexus One Android Development] dictionary:
Everything okay? lol, haven't seen any movement in here, when there was usually a post every 20 minutes.
[Nexus One Android Development] wildmonks:
Heh, sorry, been a little busy. But I may be able to post a minor release later. Notice there's been some updates in the various githubs.
[Nexus One Android Development] wildmonks:
Update:

-Changes since kernel date 061210:

-Reverted changes made to power collapse and wfi_rate functions (no observable power saving)

-Adjusted for more camera PMEM and 411MB of RAM.

-sched: replace migration_thread with cpu_stop

-misc: uidstat: Adding uid stat driver to collect network statistics.

-net: activity_stats: Add statistics for network transmission activity

-sched: kill paranoia check in synchronize_sched_expedited()

-sched: correctly place paranioa memory barriers in synchronize_sched_expedited-()

-rcu: need barrier() in UP synchronize_sched_expedited()

-scheduler: cpuacct: Enable platform hooks to track cpuusage for CPU frequencies

-scheduler: cpuacct: Enable platform callbacks for cpuacct power tracking

-Revert "Update Compcache to 0.62."

-Staging: ramzswap: Remove backing swap support

-Staging: ramzswap: Handler for swap slot free callback

-swap: Add flag to identify block swap devices

-swap: Add swap slot free callback to block_device_operations

2.6.34_AVS-800mV_CFS_1113Mhz_061710.zip

2.6.34_AVS-925mV_CFS_1113Mhz_061710.zip

2.6.34_AVS-800mV_BFS_1113Mhz_061710.zip

2.6.34_AVS-925mV_BFS_1113Mhz_061710.zip

2.6.34_AVS-925mV_CFS_1113Mhz_NoAudBoost_061710.zip

(No audio boost version, for those that don't like the increased volume during calls.)
[Nexus One Android Development] SimFox3:
Trying it out right now =)
[Nexus One Android Development] lch920619x:
Good Job, trying it:D
[Nexus One Android Development] mtw4991:
Wildmonks,

Other than the obvious swipe of some mem for charan_singh's camera mod, what else should we expect to see from the changes vs. the 0610 925 CFS?
[Nexus One Android Development] hah2110:
Overnight total or overnight/hour? What ROM?

Are you on FroYo?

In IRs version of this, I saw an improvement where others didn't - odd

+1
[Nexus One Android Development] wildmonks:
Actually very little in terms of speed and battery. A lot of these changes relate to improved memory management. Although you might see a slight battery improvement because of the changes made to monitor network activity.

Yes, currently using a non-modded froyo rom. I need web flash capability so I can watch soccer online :D

After spending so much time measuring battery usage before and after, I saw no change whatsoever. I know that the power collapse tweak produces sleep errors so I removed that and I thought I play it safe and remove the tweak to wfi_rate as it appears to have no effect because of HAVS.

I'm not sure if IR's test kernel involves the wfi_rate tweak or something else.... if it does, I suppose I can add it back it.

Edit: Oh, I forgot to mention, some of the commits I notice on github increased power drain when I tried it out. I left those out and the power drain returned to normal.
[Nexus One Android Development] phewizzo:
Holy smokes W.M. this new 6/17 925 CFS kernel is BLAZING FAST.
[Nexus One Android Development] wildmonks:
Update:

-Changes since kernel date 061710:

-Updated with IR's latest commits (2010-06-18)

Notable changes include:

-Wi-fi updated to support 2.6.35 compatibility and fix memory leak in

set_multicast_list

-rcu: refactor RCU's context-switch handling (CPU threading related)

2.6.34_AVS-800mV_CFS_1113Mhz_061910.zip

2.6.34_AVS-925mV_CFS_1113Mhz_061910.zip (updated link)

2.6.34_AVS-800mV_BFS_1113Mhz_061910.zip

2.6.34_AVS-925mV_BFS_1113Mhz_061910.zip

2.6.34_AVS-925mV_CFS_1113MHz_NoAudBoost_061910.zip
[Nexus One Android Development] THATTON:
I'm getting a verification error and the installation aborts while trying to flash the 925CFS?
[Nexus One Android Development] wildmonks:
Something must of happened when I was uploading it to mediafire. I reupload it. Try this link:

2.6.34_AVS-925mV_CFS_1113Mhz_061910.zip
[Nexus One Android Development] superg81:
im running IR latest bfs as of today and battery life is quite good.i would like to try this with your OC.any chance of that?thanks
[Nexus One Android Development] wildmonks:
Re: [Kernel] Hybrid AVS + 1113Mhz Overclock (.33.5 & .34 STABLE)

Yeah, I posted the BFS on OP and also my update post. Save you the trouble here's the links :)

2.6.34_AVS-800mV_BFS_1113Mhz_061910.zip

2.6.34_AVS-925mV_BFS_1113Mhz_061910.zip

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

Sent via the XDA Tapatalk App
[Nexus One Android Development] superg81:
well,after i posted that i realized it had the right date.:rolleyes: i should have paid more attention.sorry bout that.
[Nexus One Android Development] wildmonks:
Re: [Kernel] Hybrid AVS + 1113Mhz Overclock (.33.5 & .34 STABLE)

No sweat, happens to the best of us ;)

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

Sent via the XDA Tapatalk App
[Nexus One Android Development] superg81:
;) flashing now
[Nexus One Android Development] mtw4991:
Just flashed over froyo72... Linpacks of 41~43, quadrants of 1,760~1839.Smoking fast, hope battery life is good too...gonna test for a couple of days
[Nexus One Android Development] wildmonks:
I just moved over to FRF72 as well. So far everything is the same compared to FRF50 (1-1.5%/hr standby, Linpack 41~, quadrants 1750). Hard pressed to find what was updated in FRF72. Maybe its just a bug fix thing.
[Nexus One Android Development] chowlala:
The fix was a scam!!!! They just included a minor tweak and said OMGBUGFIXED!

Haha, just kidding. I don't know either. =)
[Nexus One Android Development] mtw4991:
I am seeing smoother scrolling between screens and maybe a bit more speed in doing so, but it's my understanding that the update was to stabilize wifi issues and screen sensitivity issues. overall it seems faster as linpack/quadrant prove. Personally, I think we are cheap testers/labor for Google who happen to know what we are doing. They write it we test it,IR pershoot Cm fix it, Google comes out with a version lol
[Nexus One Android Development] chowlala:
/offtopic

You have to admint it's a brilliant strategy though. Google is the King of the Kang! Haha. They sure know how to release a test/beta and get us to finalize for them. Rofl.
[Nexus One Android Development] SimFox3:
Latest 925mv-CFS-NO-AUDIO-HACK working like a DREAM. Thanks.
[Nexus One Android Development] wildmonks:
No problem sf3. I finally got around to making a nice 1-click compiling script so making all these different kernels is no longer a chore for me :)
[Nexus One Android Development] mtw4991:
Wildmonks, you are doing a great job...keep it up man!
[Nexus One Android Development] wildmonks:
Thanks mtw! Really appreciate it! :o
[Nexus One Android Development] diab0lik:
thanks for the no audio boost kernel. all the audio boost kernels seem to screw up my plantronics bluetooth headset. this one works great
[Nexus One Android Development] wildmonks:
np diab0lik. It's interesting to see the number of downloads for the no audio boost version increase with each new release. There is a good portion of users that prefer/need it.
[Nexus One Android Development] hondaguy:
i cant tell you how much aggrevation the audio boost causes me when i use a bluetooth headset (1 hr worth of calls per day). thanks for making the no boost versions, i appreciate it too
[Nexus One Android Development] big_adventure:
Hi Wildmonks,

Thanks for all the work on this. You facilitate my laziness.

Here's a up-to-the-minute history with your kernels on my Nexus:

Installed the 601 800 BFS - I ran it at 1113 for a week, then backed down to 1075 when you and IR discussed how it AVS wasn't working at the higher speed. I ran that kernel for 10 days, and never had any problems at all. It was the first AVS kernel that worked without issues on my personal nexus - Ivan's and IR's both gave me problems, especially the more agressive power configurations. Plus, I always seemed to get lag with IR's work - perhaps linked to the "default" conservative governor of the earlier models?

Tried the 610 800 BFS - This one was meant to correct some problems with AVS, but I had some big issues with it. Specifically, on two occasions, the phone was on but completely unresponsive - even the lock button would not turn on the screen. I was never near a computer, so I couldn't get a logcat. I also saw a few FCs in system and in LauncherPro. I went back to 601-800-BFS at 1075.

Yesterday morning, I installed FRF72 and the 619-CFS-800 kernel, and everything has been perfect since. The phone is smooth, I've seen no FCs, benchmarks are good (though not the best I've seen - with my usual program load, I have seen 910 BenchmarkPI and 45 linpack, and I've not seen that with this combo yet), everything is great. Really nice work so far. Thanks again!
[Nexus One Android Development] antiochasylum:
Flashed the latest and greatest kernel yesterday, and maybe is my imagination however pulling my phone off charger at 3:15am, not touching it till 4:55am and I'm at 87% battery. That seems like a fast drain for me.

I might revert back to the 060610 kernel to see if its the kernel or my phone.

I have done nothing else but change kernel. Running leoFroyo 0.3.0
[Nexus One Android Development] THATTON:
The LeoFroyo rom has very rapid battery drain for me in comparison with Kang-O-Rama. I tried a few different Rom/kernel combos with Leo's Rom but the battery life was worse than I'd ever seen before. Now I am back to Kang-O-Rama b2 and I get <1%/hr drain on standby. I'm using the latest 925 CFS at the moment.
[Nexus One Android Development] irishrally:
Have you used eViL's ROM also? How would you compare the three?

The battery drain and performance in general interests me when observations are made when using the same kernel on each of the different ROMs. I don't fully understand how devs optimize their ROMs, other than removing unnecessary parts, without touching the kernel.
[Nexus One Android Development] antiochasylum:
Switched to kang o rama and the out come was far better. Had 95% battery at the same time yesterday I had 87% with leofroyo. This is on the kernel that came with kang. Might try a new one today any suggestions?

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

Sent via the XDA Tapatalk App
[Nexus One Android Development] dictionary:
I haven't tried out Kang-O-Rama, but in comparison to LeoFroYo, I get WAY better battery life with eViL's ROM. I'd give either Kang or eViL a shot.
[Nexus One Android Development] THATTON:
I did try evil's rom but in all fairness, it was only for about 36 hours. I just like the look and feel of Kangorama. The battery life has been the best, by far, on Kang-o-rama though. You may want to check it out. It is a very fast, well constructed ROM!
[Nexus One Android Development] mtw4991:
Cyanogen tweet "Froyo just hit on AOSP"!!!
[Nexus One Android Development] wildmonks:
Update:

-Changes since kernel date 061910:

Minor changes were added from IR's / Cyan's repositories including:

-network: wireless: bcm4329: Reduce driver loading time

-AUFS module was added

2.6.34_AVS-800mV_CFS_1113Mhz_062310.zip

2.6.34_AVS-925mV_CFS_1113Mhz_062310.zip

2.6.34_AVS-800mV_BFS_1113Mhz_062310.zip

2.6.34_AVS-925mV_BFS_1113Mhz_062310.zip

2.6.34_AVS-925mV_CFS_1113Mhz_NoAudBoost_062310.zip

(No audio boost version, for those that don't like the increased volume during calls.)

Edit: In case anyone is wondering, these kernels seems to be working well for me on FRF83. No problems so far.
[Nexus One Android Development] SimFox3:
Flashing =)

Edit: 0623_NoAudioBoost Working perfectly!
[Nexus One Android Development] wildmonks:
Awesome! =]
[Nexus One Android Development] superg81:
would you happen to be updating to IR latest? love these kernels :D
[Nexus One Android Development] superg81:
nevermind :rolleyes::rolleyes:
[Nexus One Android Development] wildmonks:
Actually.. technically, these kernels are updated up to IR's 20100622_xxxx release. His latest release (the 20100624_xxxx) doesn't contain any new changes so there isn't anything for me to add or remove.

He just reworked his source from top to bottom in an effort to solve the touch screen issue that some are experiencing (some little change might have sneaked in causing the problem). His latest kernels is the result of that.

I wonder, is anyone experiencing the touch issue with my kernels? A majority of the code I use is identical except for 1 or 2 commits that I left out (not including the overclocking and SVS related stuff).

Knowing if the problem exist or not in my kernels might help IR track down and fix the touch issue...
[Nexus One Android Development] intersectRaven:
Yeah this is correct. I only learned of Git's cherry-pick mechanism so I've been doing MANUAL merges of commits which could have introduced the problems. :p
[Nexus One Android Development] knightnz:
What is the AuFS driver for? I understand it's a unioning filesystem but I'm not sure what use the Android OS would make of it. (For merging an ext A2SD partition perhaps?)

About to overlay the latest kernel over the new MCR r19 build until CM6 is out, thanks very much for your work.
[Nexus One Android Development] wildmonks:
I so wanna learn how to use git. That will be on the top of my to do list this weekend. :D
[Nexus One Android Development] intersectRaven:
It will help you A LOT once you learn it. I'm currently pushing for moving our office's source control mechanism to it just because of the ease it actually works once you get the hang of it. :D