yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] Untouchab1e:
I found it difficult to believe as well, but thats what it did..
[Nexus One Android Development] bt1980:
For the most part this kernel is stable in general use scenarios. The quick breakdown is this:

0429 is the failsafe - always works.

Everything since 0429 has had issues connecting to a WiFi network with a hidden SSID; but otherwise works perfectly. Apparently that issue is now fixed in the latest release.

BFS and HelixLauncher don't get along. CFS is the better choice if you use HelixLauncher.
[Nexus One Android Development] paulk_:
I think quite a few people have experienced this, sometimes after flashing something new, the battery remains stuck at 100% for quite a while. Therefore that would be possible since playing music doesn't take much battery.
[Nexus One Android Development] Untouchab1e:
Havent flashed anything for quite a while.. Phone has been on for 6h53m.. Battery at 93% atm.. Just very sad that for seemingly no reason, battery life just drops really quickly after disconnecting it from the charger..
[Nexus One Android Development] bewA:
Are there any benefits with the HTC Desire (bravo) kernel source being made available?
[Nexus One Android Development] Infin8cyn:
1) Are you wiping battery stats?

and

2) Are you sure you're not just experiencing this (look at post #8 & #9):

xdaforums.com/showthread.php?p=6461665
[Nexus One Android Development] East_Coast:
Probably a dumb question, but oh well..lol

Can someone clarify the install instructions for this? Do i just push the wifi driver, then reboot into recovery and flash the zip?

Or do i need to push recovery, and zimage, and that is it?
[Nexus One Android Development] sluma:
following his instructions I pushed the wifi driver rebooted then flashed in recovery then rebooted again.

Taken from RI's instructions in first post

Instructions for zImage and bcm4329.ko driver extracted from the update.zip(from command line):

1.) adb remount

2.) adb push bcm4329.ko /system/lib/modules

3.) adb reboot bootloader

4.) fastboot flash zimage zImage

5.) fastboot reboot
[Nexus One Android Development] East_Coast:
That is kind of what confused me.. Because the instructions say:

So both the .ko and zimage need to be pushed, then go into recovery and flash OR is that all that needs to be done(push both)

The first part of the instructions seems like i would just flash the update.zip from recovery and no pushing needed.
[Nexus One Android Development] jblazea50:
his kernels are in update.zip format, so you can just download it and place it in the root of your SD card; go into recovery and just flash

this won't mess with anything else you have on your phone because he uses some script which creates the boot.img from the current rom you're using
[Nexus One Android Development] jblazea50:
yes, you can just flash the update.zip from recovery
[Nexus One Android Development] kbeeveer46:
Has anyone else noticed that when their phone is idle and they receive text messages that the phone never vibrates or does anything to alert you that you have a message? But, as soon as you push the power button to come out of standby the phone sends all the alerts all at once. It's happened about 3 times today after installing this kernel. I thought maybe SetCPU might be causing it but I don't think it is because I've always had it installed but this started happening after installing this kernel today.
[Nexus One Android Development] timothydonohue:
which one exactly did you put on? he put up 8 of them, lol.

i put on the 'bigger' 925 CFS 33.4 kernel. no problems here. all notifications as normal, on enom's rom
[Nexus One Android Development] kbeeveer46:
20100514_14XX 925 CFS is what I installed today. I'm running the latest Cyanogenmod.
[Nexus One Android Development] timothydonohue:
ah. i'm using the 20100514_10XX - 1100 radio, on enom's rom.

maybe that's the difference
[Nexus One Android Development] x986123:
Latest kernel, 2.6.34-rc7_AVS-925mV_CFS_20100514_1435.zip having extreme audio skipping again. The previous versions where perfect.
[Nexus One Android Development] intersectRaven:
I'm still working on a bigger bug for awhile. I'll get back to reintegrating the updated drivers when I finish. This touchscreen unresponsiveness bug is SS priority. :)
[Nexus One Android Development] Docmjldds:
Just an FYI, that I installed Paul's R22 Desire update today. (Long time since he had posted R21 long time ago). Anyways, basically installed with a major wipe of Data, and both caches. Rebooted twice, Then flashed 2.6.33.4_AVS-925mV_CFS_20100514_1425.zip from recovery (update.zip method). Wifi would NOT start. Unzipped the file and manually pushed ko file, then fastboot flashed zimage and wifi worked. I have since gone back to CM ROM, but waiting for future Desire releases. Basically wanted to test Ravens Kernel on the Desire ROM was basic intention today, as well as method of install. My guess would be if I stayed with Desire ROM that subsequent installs via update.zip method would probably work. Just a guess :cool:
[Nexus One Android Development] Rattamahatta:
Since flashing 20100514_14XX (CFS,800mV) most of the calls don't get put through and the caller is redirected to my mailbox.

Going back to the defaut CM kernel everything is working fine again.

Anyone else experiencing this problem or is this just a temporary problem with my provider?
[Nexus One Android Development] intersectRaven:
Does anyone still want to use the 800mV kernels even after kmobs' study results returned that 925 is the best in terms of battery life? If there is still significant demand, I'll continue releasing them. :)
[Nexus One Android Development] jblazea50:
personally, i did not notice much difference between the 800 and 925 kernels (based on my daily usage) and now i am only using the 925mV kernels

however, if it doesn't take too much time to create and upload the additional 800mV kernel, then you should still keep it around because some people like the lower voltage; if it takes too much time to maintain both, then get rid off it
[Nexus One Android Development] pzumk:
yes /123456
[Nexus One Android Development] hah2110:
Yes!

+1

Last night, after going back to 4/29, I rode on 100% for 3.5 hours in standby. It almost felt better than sex. BUT after that, I was losing 1.5%/hour overnight. :-(
[Nexus One Android Development] b1337:
+1

Last night, after going back to 4/29, I rode on 100% for 3.5 hours in standby. It almost felt better than sex. BUT after that, I was losing 1.5%/hour overnight. :-([/QUOTE]

wow guy that's just pathetic....seriously. .
[Nexus One Android Development] yiannit:
i think my battery is stuck at 100 its not going down. im using 925 cfs 0515 1323

i got music playing and browsing and its stuck,

edit

haha i spoke to soon at 99 now. this is sick i had it on for 3hrs let see if its consistent
[Nexus One Android Development] THATTON:
After hearing how much you talk about your battery life I believe that you think WATCHING your phone stay on 100% for 3 hours was better than sex! I'm a recovering heroin addict and I don't think I was ever obsessed with the needle as much as you are obsessed with your battery life!! I think you need help! Do they have DRA meetings (Discharge Rate Anonymous)? We all know your posts are coming before you even post them. Sometimes its best to not say anything at all. Save yourself the scrutiny of the other members!!!
[Nexus One Android Development] jblazea50:
lol, that was hilarious:D
[Nexus One Android Development] mtw4991:
+1 for keeping the 800mV also. I still haven't decided between 800 & 925 yet...maybe till next week, IR?
[Nexus One Android Development] sthoeft:
Good news. BFS seems to be stable with Helix Launcher (one not Helix2). Great
[Nexus One Android Development] mtw4991:
LMFAO!!!:D
[Nexus One Android Development] sir*mez:
We dont need the 800mv. There's no use for it anymore. The tests have spoken. The lastest 0515 test kernel is working perfect.
[Nexus One Android Development] mtw4991:
Curious, 0515 kernel....33.4 or 33.rc7, CFS or BFS??
[Nexus One Android Development] mtw4991:
it's getting confusing...the concensus is using which kernel????:confused:
[Nexus One Android Development] jblazea50:
kmobs blind study showed that 925mV gave the best battery life

as for Raven's, i believe the 925mV CFS .33.4 should give better battery life than the BSF and .34 kernel as .34 isn't stable yet
[Nexus One Android Development] Docmjldds:
Please pick which one:

2.6.33.4_AVS-925mV_BFS_20100515_1317.zip

2.6.33.4_AVS-925mV_CFS_20100515_1323.zip

2.6.34-rc7_AVS-925mV_CFS_20100515_1329.zip

I would assume since .34 has stability issues then you are saying the xxx1323.zip is your reference working perfect?

I am ruling out BFS also regarding Helix Launcher which I sometimes use, depending on do I want to mess with customizing my screens or not :cool:

Have not updated my sig to reflect latest 5/14 .33 CFS, BTW
[Nexus One Android Development] sir*mez:
CFS 33.4. I don't use anything out of the ordinary. I like near stock. Sorry for not being clear.
[Nexus One Android Development] intersectRaven:
.34 Update!

20100516_1300:

- finished driver updates (no more audio skipping!)

- includes the capacitative button fix (for better positioning of capacitative buttons)

- *hopefully* fixed the touchscreen hang bug

- #1 has been changed to 925mV as result of kmobs' study (800mV will still be released for hard-headed people out there) :p

20100516_1300:

925mV -> http://www.mediafire.com/?y2uzjiw5liu

800mV -> http://www.mediafire.com/?jxzyqzto4hz
[Nexus One Android Development] Henchman:
Killed the WiFi on pauls rc22
[Nexus One Android Development] bewA:
is the USB mounting still an issue? :)
[Nexus One Android Development] intersectRaven:
Unfortunately, yes. :(
[Nexus One Android Development] Untouchab1e:
Quick question.. What is the recommended procedure for wiping battery stats? I am still trying to figure out this variable battery life issue and this might be a point of interest..

So far, I have been turning the phone off, charging it until I get a green light, then boot into recovery and wiping battery stats. Anyone else do it differently?
[Nexus One Android Development] knightnz:
Thanks so much for this, it's made my N1 much less annoying to use! Will see what it does to the screen losing calibration when it gets cold.

Now I just need to work out how to get it to receive MMS's. Same problem on my old Hero, the only ROM it ever worked with was the ones based on the Eris leak.
[Nexus One Android Development] Oletros:
Hi, a little off topic but I don't know where to ask this.

I have Cyanogen 5.0.7 T2 ROM and 2.6.33.4_AVS-925mV_CFS_20100515_1323 kernel.

I don't use any kind of task manager and the only "strange" thing I have installed is Overclock widget configured to 245 998 frequencies, I don't use scree off frequencies.

At 23:00 I changed the phone to Airplane mode and wifi off with 94% of battery.

At 8:00 battery has dropped to 62% and when I look at spare parts battery information it says "Running" How can I check which process/program is preventing phone sleeping?
[Nexus One Android Development] bewA:
bugger :(

keep up the great work!
[Nexus One Android Development] pzumk:
is this CFS?
[Nexus One Android Development] GIKE:
Yes both are CFS, if you pick in the links, you will see ;)
[Nexus One Android Development] pzumk:
Ah damn, I forgot! Thanks :)
[Nexus One Android Development] www1:
USB plugged bug.

I can't disable usb in 34rc

edit.

Also kill my phone and I can reflash with .33

I try the recovery.
[Nexus One Android Development] paulk_:
Check partial wake usage under Spare Parts > Battery History?
[Nexus One Android Development] www1:
After I flash with kernel .34 and reboot.

Mu N1 stay on initial boot X.

No way to boot.

I retry to flash kernel but same result.

Now I try to reflash cyanogen rom.

What It made?
[Nexus One Android Development] intersectRaven:
Try flashing using fastboot. It may be that your N1 can't handle the size of this kernel. :)
[Nexus One Android Development] www1:
I retry to flash but same error.

Do you suggest to reflash kernel again? (I have done It several time)

edit.

same problem.

I try to reflash rom.

edit2.

resolved reflashing rom
[Nexus One Android Development] intersectRaven:
Odd. It should boot properly if there was no error in flashing. Maybe an app you have is causing the problem. Just revert to .33 for now I suppose. :)
[Nexus One Android Development] cmarti:
I wonder if this kernel will work with the Desire camera, I tried the ones released before and the video function when you are using the Desire camera hangs.
[Nexus One Android Development] ryanpence:
newest kernel working for me

I Have had no problems installing the kernels. Just make sure you wipe your caches before flashing kernel.
[Nexus One Android Development] danielherrero:
nice kernel. thanks. no providence

problems here and all is very fast
[Nexus One Android Development] yiannit:
Re: [.33.4 & .34-rc7]intersectRaven's Kernel (Hybrid AVS *Stable*) 05/16/2010 01:10pm

My phone has been on for 26hrs with some texting phone calls and about an hour of web use and I'm at 42% the web use is what drained it the most. This is the best results ive hAd

ExcePt I had to reboot because my phone was running real slow,

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

Sent via the XDA Tapatalk App
[Nexus One Android Development] Docmjldds:
So far NOT good for me. Specifically I use BTunes for music app. Widget non responsive. Starting app from normal icon, screen is black with music playing. FC occurs but music still plays. Cannot shut it off without reboot. I will try a different music app. This is regarding latest .34 RC7 just posted (xxx1300.zip) . Yes, I wiped caches prior to installing as update.zip file.

Edit: BTunes seems to be non compatible since Meridian, my alternative media player works fine. No audio skipping. I listen to .flac files, which is why I use either meridian or BTunes. BTunes automagically installs cover art which is why I use that. (Paid app, BTW). (Looks identical to iPhone music app)

Desire camera video still a no go. Records for 2 seconds, then shuts down on it's own.
[Nexus One Android Development] hotweiss:
I really don't think wiping will help, unless you are updating dalvik or an app. Correct me if I'm wrong.
[Nexus One Android Development] milton007:
Works fine...you need to manually PUSH the wifi module into system/lib/modules
[Nexus One Android Development] Henchman:
Actually, after re-flashing rc22, wiping caches and re-flashing the new kernel, all works fine
[Nexus One Android Development] milton007:
My desire r22 rom doesnt accept the update.zip format under either recovery.Itll install the kernel but WiFi will not function correctly afterwards. Ive tried numerous times. The only way i get WiFi to work is,ill extract and copy the wifi module over to sd card,then use root explorer to unmount and place BCM into modules directory,boot into recovery,wipe batt stats,then cache,then flash kernal,wipe cache again,and then reboot and everything is fine-well, everything functions fine,but battery life is abysmal on all the CFS&BFSkernels ive tried. My best (and thats for my device--DOESNT mean that itll be the best on yours)kernel as far as batt goes is STILL the 4/29-1010(925) release!
[Nexus One Android Development] schahr01:
I have just been wiping batt stats, caches as part of my routine for installing a new kernel but I tend to agree with you. The dalvik cache contains the dalvik executable (dex?) files post java .class conversion for the dalvik jvm. A new kernel isn't going to change the dex files that are generated. Not sure about the other "cache" listed in the recovery though.
[Nexus One Android Development] coldchillen:
trying out your kernal (.34rc7) and seems like the capacitive buttons may be a hardware issue? buttons still feel like the upper third still needs to be pushed. as always, maraming salamat! mag inoman tayo :D
[Nexus One Android Development] sir*mez:
Aahhh I wish the .34-rc7 kernel was stable. I love the feel to it. I tested the linpacks for .33.4 and .34-rc7 and rc7 is smoother and faster. Battery life is still great so I have no need to report on that. I will be using the rc7 kernel for another 24hrs. and then ill report back.
[Nexus One Android Development] jblazea50:
tried out the latest .33.4 CFS release from 05/15 and it wasn't playing nice at all; battery drain was heavy (not during standby, but during light/moderate usage); lost about 25% in 3 hours with maybe 30min of usage and 2.5hrs standby

btw, this was on Enom's 1.9.1
[Nexus One Android Development] cmarti:
Just would like to say that this is the best kernel so far!
[Nexus One Android Development] hondaguy:
I was under the assumption that these newer kernels were universal but I had tried one last week with the previous enomthrs Rom and battery life was poor. Battery life was pretty good using a cyanogen Rom, though. Are these roms only meant for cyanogen roms?
[Nexus One Android Development] apetzinger:
Re: [.33.4 & .34-rc7]intersectRaven's Kernel (Hybrid AVS *Stable*) 05/16/2010 01:10pm

.34-rc7 random reset...

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

Sent via the XDA Tapatalk App
[Nexus One Android Development] mrandroid:
awesome.... lost 6% all day... Texting, calls and occasional GPS usage.
[Nexus One Android Development] mtw4991:
Which kernel are you using...that seems like awesome battery life!
[Nexus One Android Development] intersectRaven:
2.6.34 has been released. The new Opportunistic Blockers don't seem to play well though so maybe I'll just go back to wakelocks like what Termana does with his kernel? Anyways, I'll release after a few minutes. :)
[Nexus One Android Development] Bay Harbor Butcher:
What voltage do you suggest for N1 with Cyanogen 5.0.6 between 800mV or 925mV?
[Nexus One Android Development] THATTON:
925mV seems to work best for the masses according to most users as well as Kmobs experiment... I have always gotten better performance/battery life with the 925mV kernels.
[Nexus One Android Development] Bay Harbor Butcher:
But if N1 works good,without lags and delays, running Kernel 800mV I think is good to keep it..battery should drop slower with 800mV than 925mV,right?
[Nexus One Android Development] jblazea50:
the problem many experienced with 800mV is that the radio will use more power at lower voltage, therefore, it will drain the battery faster compared to 925mV

unless you are always around max signal, then it shouldn't matter (i'm assuming)
[Nexus One Android Development] intersectRaven:
Update!

20100517_0731_.34:

- updated to .34 release

- still uses the opportunistic blockers (will be migrated to wakelocks soon if Google doesn't fix it)

20100517_0731_.34:

800mV -> http://www.mediafire.com/?yayh5ywzzz2

925mV -> http://www.mediafire.com/?ddwzmzzjtom
[Nexus One Android Development] Breece:
Will try this one :) Thank you!

[edit]

Judging by the first couple of minutes: This kernel is fast :D
[Nexus One Android Development] jblazea50:
thanks for the fast release; is the .34 now stable? again, this is great; just flashed it and will report back if i notice any issues
[Nexus One Android Development] intersectRaven:
.34 is stable. The android port isn't. :p There's still the problem of the replacement for wakelocks not working properly thus making the system consume too much power even while idle. :(
[Nexus One Android Development] schahr01:
I don't think that was ever proved out. There's no correlation, in AVS kernels I believe, between the radio/modem voltage and the CPU voltage usage - I don't get better signal on 800 vs 925. That said, there might be something at play - More work to throttle up from 800 to the desired voltage for 998MHz (fixed at 1.275V I think)? Unless you cap the max with setCPU most applications will want to use as much as they can get.
[Nexus One Android Development] Bay Harbor Butcher:
Where I live signal is very strong,I think It doesn't need so much power to keep signal.

If I see any problem in receiving signal I flash 925mV kernel..I always put both on my sd card.:-)

Waiting for Froyo..still a couple of days..
[Nexus One Android Development] Docmjldds:
Main reason I had switched back to .33 before your current .34. I could live with Desire Video bug, but I watched battery drop 5% points inside of 30 min, just sitting idle.
[Nexus One Android Development] intersectRaven:
Yeah. I've been trying to implement workarounds but it still won't act like the wakelocks in .33. :(
[Nexus One Android Development] Docmjldds:
Same problems again with this update as last. Battery drain bummer. Back to .33. Still, appreciate the efforts and will be happy to try anything that comes our way :)
[Nexus One Android Development] Wysie:
Have yet to flash the latest .34 release, but with the previous -RC7 one, I had no problems mounting my USB drive, but was unable to "Turn off USB storage" from the phone after that. Had to reboot. Not sure if the latest one fixes it but I didn't see it being mentioned :P
[Nexus One Android Development] intersectRaven:
That one is also not fixed. :p
[Nexus One Android Development] Wysie:
I *knew* it! :P
[Nexus One Android Development] bobdude5:
wow latest kernel is sooooo smooth..its better than iphone smooth WITH live wallpaper..asphalt runs full speed no stutters..going to test battery for the next few hours see how it goes
[Nexus One Android Development] intersectRaven:
I'll spare you the test. The battery kinda sucks on this one. :p
[Nexus One Android Development] Lazat:
intersectRaven, can you recommend me one of your kernels that doesnt eat up the battery? just trying out your latest now, and the forumthread has 270 pages! :D

thanks for your great work!
[Nexus One Android Development] Wysie:
Lazat: Any of his .33.X kernels should be fine. It's the .34 that is bad with battery.
[Nexus One Android Development] Lazat:
Wysie: ah okej, thanks :) ill just take the latest .33 then :)
[Nexus One Android Development] sir*mez:
Happy with the new 051710 925mv cfs .34 kernel!!

latest 051710 925mv cfs .34 kernel is fast and smooth. im so in love with it that im going to live with the unmount bug. Besides that its yielding good enough battery life so far for me.:D
[Nexus One Android Development] jlevy73:
With .34 there should be a marked improvement in graphics as that is were most of the optimizations are
[Nexus One Android Development] jlevy73:
Those battery results are fantastic. If I even look at my phone it drops 2%
[Nexus One Android Development] intersectRaven:
I agree. With my own phone the top user is cell standby and not display! :p
[Nexus One Android Development] jlevy73:
Same here, display is only at 5%
[Nexus One Android Development] johnsin:
I always like the previous .34rc, and the .34 now is even better. Do you guys run setcpu at the background? I am still confuse whether I need to run the setcpu. Thanks.
[Nexus One Android Development] Bay Harbor Butcher:
Did you flash 800mV or 925mV version?
[Nexus One Android Development] jblazea50:
Battery life isn't good with .34. Last night lost about 8% in 25 min of browsing and similar this morning
[Nexus One Android Development] Docmjldds:
Some discussions here have shown set CPU not needed. I uninstalled and don't miss using it. I am still using the more stable .33 that has better battery, for now. .34 seems to eat battery when in standby, more than display.
[Nexus One Android Development] Bay Harbor Butcher:
I tried last release 800mV this night and I got 1% for any hour of standby.

Phone was available but not connected to internet.I think it is a good result..when I call battery drops faster,but I think it is normal..
[Nexus One Android Development] Docmjldds:
Just an FYI...Wavelocks is the issue for sure. Just tried Termana latest .34 build 1 just posted today. No bugs that I can find. Desire Camera video works. USB unmount works. BTunes works. Audio smooth, no skipping. Standby Battery is back to what appears to be normal, but still testing that aspect. So far only see 1% drop during last hour, in standby.

Edit: Termana uses OC which I do not prefer, BTW.
[Nexus One Android Development] Breece:
Battery is fine with .34 but my Home++ launcher crashed and the phone with it ;-)