yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] S_Dot:
lol.. kernels are too experimental, keep trying
[Nexus One Android Development] massivevoid:
Before, I was using 20100504 800mV CFS and was losing 2% at one hour idle (was not using the phone). I loaded the 925mV CFS version and it stayed at 100% at one hour idle.

My settings are Wifi/bluetooth/GPS off, syncing two email (one work, one personal), and brightness at automatic.
[Nexus One Android Development] hah2110:
Which CFS are you using? Which 925 date?
[Nexus One Android Development] massivevoid:
2.6.33_AVS-925mV_BFS-pmtest_20100505_1127
[Nexus One Android Development] dictionary:
Latest 925 CFS before pmtest .. and battery life is amazing. Playing Asphalt 5 with a tiny tiny bit of lag, and phone lasts for hours. I have my data turned off though, but this kernel is a keeper. So much so, that I labeled it as intersect504CFS925BESTDAMNKERNEL.zip
[Nexus One Android Development] hah2110:
Weird... PMTest isn't yielding as good as the one Dictionary mentioned.

Quite an appropriate name. Have you tried pmtest?
[Nexus One Android Development] mtw4991:
@Raven...

I just installed the 2.6.33 AVS 925mV CFS 0504_1327 and I too noticed that total memory went from 403 to 416 per SetCPU info. That's only a gain of 13mb and missing the other 8mb from the 21mb hack.

Could possibly the missing 8mb be from your first hack and coolbho3k only added an extra 13mb for a total of 21mb?
[Nexus One Android Development] hah2110:
27.5 hours and 43% left... I THINK I am seeing more drain with 925 but i can't be sure yet.
[Nexus One Android Development] MaxiJavi:
Still, not that bad if you've been using the phone ...

Hopefully you are a little happier now :-)

I am following in Untouchab1e/dictionary's footsteps ... We'll see how it goes ...
[Nexus One Android Development] hah2110:
Ya I agree this is pretty good. You are using Dictionary's?
[Nexus One Android Development] b1337:
its from all your spamming the battery questions
[Nexus One Android Development] zha50:
Was your previous kernel already a +8MB one? IIRC the 21MB hack included the previous 8MB hack, with a difference of 13MB but net gain from a stock kernel of 21MB. Happy to be proven otherwise tho.
[Nexus One Android Development] Docmjldds:
<<This is weird and ungodly! What is your standby time like? Most of these kernels really help with standby time but the screen is a battery sucker. I'd drop probably 6-8% if I used the phone with the screen on for 30 minutes.

My standby time I posted in a later message. I also posted a screen shot of after one hours use. Basically less than 1% drop over a one hour period. Too small to even measure. I also showed basically a 1% drop after one hour of an app (Cardiotrainer) I use outdoors with GPS tracking. Totally killer battery times, and this is on the stock battery. Like you, I have the Seidio 1600mAh battery. Not happy with it. Was going to return it. Had an RMA, but never got around to it.
[Nexus One Android Development] crabnebula:
Yesterday I upgraded to 100504 from the 100429 release which was running completely stable for me.

Unfortunately the phone crashed and rebooted spontaneously on three occasions since. I was on the 800 mV version at first, and after the second crash, I switched to the 925 mV, but it crashed again.

On two of these three occasions, it rebooted just after I activated WiFi with the power widget, so it might be WiFi related...?

I'm reporting this in case anyone else experiences it too. Will let you know if I can reproduce it consistently.

Cheers and many thanks for your work intersectRaven.
[Nexus One Android Development] mtw4991:
yes, the previous one was 0429_1009 which I believe already incorporated the 8mb hack. So the extra 13mb gain makes sense which is what I thought. Thanks for the confirmation.
[Nexus One Android Development] Docmjldds:
Same here.
[Nexus One Android Development] Docmjldds:
I have to believe that your phone is probably either, buggy, defective, weird, all of the above, pick one. The PMtest 925 version when I first installed here, made me ponder if the battery indicator was defective, much like the other user (untouchab1e?) stated. I basically had to reboot phone to get it to drop to 99%. But others here are reporting similar results. Until someone can post proof that the battery indicator status is somehow wrong, these results are phenomenal, but I also have to believe that CM 5.0.6 has something to do with this.
[Nexus One Android Development] mtw4991:
Docmjldds, you are using the 05 pmtest version of 925 CFS right? I'm using the 04 pre-pmtest version of 925 CFS and although it seems snappier than 04_1009, I got a 6% drop in the first 2 hours.

Is the 925 pmtest version that much better?
[Nexus One Android Development] THATTON:
I never knew that it was even suggested to completely charge the phone before flashing kernels. This could be an explanation why so many people including myself get such different results with the same kernels. I am going to have to try this from now on and see if my results differ even with the same kernels...
[Nexus One Android Development] Docmjldds:
This is sooooo good, I think we need to buy someone a lifetime supply of beer. Sorry for "slightly" off topic, but these results really are mindboggling, IMHO.
[Nexus One Android Development] hah2110:
Phone definitely isn't defective because I am getting superb results on the 800 kernels. Just loaded 800 pmtest and will see how it goes.

+1
[Nexus One Android Development] Docmjldds:
Yes, it's that much better, at least according to what I am seeing. I have to wonder if these are really true readings, since it seems almost impossible. 2.6.33_AVS-925mV_CFS-pmtest_20100505_1138.zip is the file.
[Nexus One Android Development] Docmjldds:
I don't think it was ever suggested. I just chose to do this for consistency as far as what I was seeing, and saw another user doing same. Just seemed to make sense.
[Nexus One Android Development] THATTON:
That makes sense. Especially with so many other variables I guess it would be wise to keep as many as possible consistant. After reading your last couple of posts I am going to test the latest 05-05 925 CFS Kernel and who knows, maybe I will be renaming it to BESTDAMNKERNELEVER as well!!! We shall see.
[Nexus One Android Development] intersectRaven:
Just got to the office and got surprised at the number of new posts. Anyways, I found one which I think I should reply to...

I could include the BFS and CFS in the root string but as for the frequency, that would require another change with "maker" (my automated kernel builder) which I don't think is justified since it's an extremely minor thing. Anyways, there is an easy way which requires no modifications, #1 is always 800mV while #2 is always 925mV. :)
[Nexus One Android Development] schahr01:
Thanks, much appreciated. Fair enough - #1 = 800, #2 = 925 , Starting with new builds?

What to do about the introduction of suspend blockers vs orig wakelock? :D
[Nexus One Android Development] intersectRaven:
That convention has been around for quite a few builds actually. (the reasoning is that I always like using the 800mV kernels but don't like any number other than 1 showing in the build string :p) As for the suspend blockers, maker doesn't support branch switching yet so I'll have to modify it before it can integrate the build string. :)
[Nexus One Android Development] schahr01:
Thanks! Seriously though, it's just a nice to have. You already do so much for the community.
[Nexus One Android Development] mtw4991:
Umm...my kernel say #4? It's the 20100505_1138 AVS 925 CFS pmtest version.
[Nexus One Android Development] crabnebula:
Just wanted to confirm that this does indeed occur consistently.

If I turn WiFi off, then back on, the phone just reboots after a few seconds with WiFi on and everything then seems OK.

I had another identical crash/reboot at another moment, but I can't recall what I was doing.

I am using CFS by the way.

EDIT BFS does the same.
[Nexus One Android Development] intersectRaven:
I must have used an old version of maker to compile yesterday's pmtest. It should be #1 and #2 only.
[Nexus One Android Development] THATTON:
I've noticed a few over the last week that have been #4 also. I think it was the 5/03 925 and the 05/05 925 Test CFS that were both #4... Oh well, as long as the work like they do I don't care what they are called!
[Nexus One Android Development] S_Dot:
Is there any problems with the latest version? also are people getting better results with BFS or CFS
[Nexus One Android Development] hah2110:
32 hours and 23% left!

Sent from my Nexus One using the XDA mobile application powered by Tapatalk
[Nexus One Android Development] bobdude5:
what rom and kernel are you using? Heavy (hours of internet, games, texting, music, brightnes, talking), medium ( alittle browsing, some games, texting, talking) or light usage ( very little browsing, no games, some texting)?
[Nexus One Android Development] crabnebula:
I noticed that the latest zips have a different version of the bcm4329.ko driver.

This seems to be what is causing the reboot issue for me. I tried pushing the wifi driver version from the 0429 zip after flashing the 0505 kernel in recovery. I no longer get the reboots, but on the other hand I can't connect to my network anymore either.
[Nexus One Android Development] hah2110:
cm 506 on 800 pmtest. I would say between light and medium. I don't do any gaming but I do some web browsing, downloads, etc. I had a few hours of phone calls as well but heavy texting and emailing.

Sent from my Nexus One using the XDA mobile application powered by Tapatalk
[Nexus One Android Development] intersectRaven:
Test Update!

- updated to latest cyanogen commits

- upon testing, these have better battery life for me

- still marked as -pmtest

Latest links are at my MediaFire folder.
[Nexus One Android Development] dnsmo:
anything new with the wifi driver? thanks for the goodies
[Nexus One Android Development] archillion:
just downloaded the 925mv CFS kernel form 5/5. Will post results later
[Nexus One Android Development] intersectRaven:
WiFi driver is still the "same" (pertaining to the source). :)
[Nexus One Android Development] dnsmo:
i just update to the bfs 800 avs version and notice that i can't use /proc/meminfo command, it said permission deny

do i have to use command from the computer to check it or it's okay to check using the terminal emu in the phone?
[Nexus One Android Development] SeriousX:
After clean install of CM 5.0.6 flashed latest CFS kernel with extra 21mb, went to sleep, woke up rebooted my nexus and it lost FAT partition. Restored nand to stock kernel
[Nexus One Android Development] Untouchab1e:
As I described earlier, I am getting extremely good results with the 925mV CFS kernel.

However, I have discovered an issue that may or may not affect us all..

I rebooted the phone, and when it came back up I quite quickly noticed the battery drain to be huge. Within 5 minutes, it had already dropped 2-3%. I turned it off, charged it a bit, turned it back on, and then it got back to the normal 1% drain ever 30-60 minutes..

This has happened to me before as well.. Anyone have any ideas?
[Nexus One Android Development] sir*mez:
A kernel did this? Really? But seriously, if you lost your fat partition, how did you nandroid restore? Nandroid is stored on the fat partition.
[Nexus One Android Development] mykenyc:
:D:D:D:D:p:p:p;):D:D:D
[Nexus One Android Development] die-hard:
I installed your latest test kernel, it have 10th MBPS less then pershoot kernel.

Fix this issue pls
[Nexus One Android Development] intersectRaven:
Updated!

20100506_14XX-15XX:

- updated to latest cyanogen commits

- 21MB memory hack v2

- 800mV represented by #1 925mV by #2 in kernel string

- indicates CFS or BFS in kernel string as well

*See OP for the links! :)
[Nexus One Android Development] abrixxxx:
its late

just wondering whats better for performance/battery life bfs or cfs i cant remember right now, thanks or what do you run op?
[Nexus One Android Development] vegetaleb:
Nextheme will not work with the latest kernels (BFS) ?

I mean it's based on helixlauncher :confused:
[Nexus One Android Development] mythamp:
noob question, I just installed kings desire2nexus v1 rom, which is the safest and best kernel for me from the list (BFS/CFS?/950/850??). Slightly confused. Thanks would really appreciate the help.
[Nexus One Android Development] citronbitare:
Probably CFS 925.
[Nexus One Android Development] intersectRaven:
CFS is the most stable. BFS has problems with third party launchers. As for the voltage, choose what's best for you. Both are safe since they're not overvolts. :)
[Nexus One Android Development] abrixxxx:
retracted

10 chars
[Nexus One Android Development] MaxiJavi:
Hi,

pmtest 925 seems to be running pretty well for me ...

Standby time seems about the same, active time seems better.

Is this possible ?
[Nexus One Android Development] intersectRaven:
I think it is. If what I understand about them is correct (and please feel free to correct me on this :p) wakelock needs to be triggered in order to enter sleep state while suspend blockers check for criterias to be met in order to enter sleep mode. In other words, wakelock is reactive in the sense that an app needs to tell the OS to sleep while suspend blockers are proactive in the sense that the OS determines whether it can sleep. :)

*Ignore that...they operate the same I think after rereading the specs on wakelock... :p

Wakelock and Suspend Blockers are both mechanisms that tell the OS NOT to sleep. :p
[Nexus One Android Development] MaxiJavi:
So then it may be down to the suspend blocker being a better implementation ?

Or are any battery differences figments of my imagination ? :-)
[Nexus One Android Development] intersectRaven:
It maybe a better implementation. We must consider that Suspend Blockers are going to be implemented in the main line of the Linux kernel. (It's already in .34!) :)
[Nexus One Android Development] bskim23:
I have a question. I noticed in your mediafire folder, there are pmtest for all 4 different types of kernels. What does that mean? Thanks in advanced :)
[Nexus One Android Development] intersectRaven:
Those use the new suspend blockers instead of the android wakelocks. :)
[Nexus One Android Development] bskim23:
Sweet thanks! I'll be giving those on BFS a run! :D
[Nexus One Android Development] hah2110:
Are these the same?
[Nexus One Android Development] intersectRaven:
Yes and no. Yes in that the source are the same with regards to the -pmtest kernels. No in that the maker script was updated to modify the kernel build strings in the latter release. :)
[Nexus One Android Development] hah2110:
Gotcha... So, in theory, no battery difference. What is your stance on the whole 800 vs 925 thing?
[Nexus One Android Development] intersectRaven:
I personally have better power savings with 800 so I'll have to stick with 800 is more power efficient. (Is this an interview? :p) :)
[Nexus One Android Development] MaxiJavi:
My understanding is that there could quite a battery difference, as it depends which implementation is more efficient. Currently I seem to be getting better battery with the pmtest ... But it is too close to call, and it might all be in my head.

As for voltages, 925 definitely seems to work better for me.

I have a lot of marginal reception, which may be a factor.
[Nexus One Android Development] schahr01:
Sounds like you should go back to that kernel then. There's nothing of value in your post. If you're going to provide feedback your post can't be vague or information-free.
[Nexus One Android Development] schahr01:
/proc/meminfo is a file, not an executable. Use 'cat /proc/meminfo' from the terminal to see output, su not required. As an alternative, use Astro file manager to open the file as a text file.
[Nexus One Android Development] SeriousX:
I posted earlier that i los fat partition. The thing is that i see fat partition through recovery: i can do nandroid, i can install rom that is in sdcard root, but in android a cant see it. I wrote that i testored a cleqn nandroid but few hours later i lost partition again, i refreshed rom by updating it again and no use - still dont see fat pwrtition while in android OS, in recovery all is fine. Is that a kernel to blame? "mount sdcard" command in terminal doesnt help.
[Nexus One Android Development] schahr01:
Excellent - I like my new "2.6.33.3-CFS-intersectR root@raven-lx #2" kernel :D
[Nexus One Android Development] bskim23:
Installed 800 BFS pmtest and have been running it for about an hour on cyan 5.0.6. Messed around with a little bit of everything (facebook, twitter, maps, news, some games, camera, benchmark cpu and linpack). Everything's running smoothly. Will report back with more later. Mad props to Raven for a kick @$$ kernel!
[Nexus One Android Development] kbeeveer46:
EDIT: Disregard this post. I forgot the kernel version is in the "About" section in settings. It says "2.6.29-01117-g4bc62c2 android-build@apa26 #1"

Does anyone know if by reflashing the Nexus One stock userdata.img, boot.img, system.img, and recovery.img if that also removes any custom kernels like this one in this thread? I installed this kernel yesterday but put everything back to stock last night and didn't know if I still have this installed as the instructions located here didn't mention the kernel. Thanks.
[Nexus One Android Development] bewA:
I believe if you flash over the boot.img that's the kernel that would overwrite it...
[Nexus One Android Development] MaxiJavi:
I had a lockup when rebooting :-(

I then had a look myself at the kernel mailing lists ... They sure seem to pushing a lot of patches for the suspend blocking stuff, which leads me to believe it may not be as mature as the default Android implementation.

So I am back to the latest 925CFS ...

Thanks !! :-)
[Nexus One Android Development] schahr01:
Right - Discovered this early on as well.

"fastboot flash boot IMAGE" is synonymous with "fastboot flash zimage IMAGE"
[Nexus One Android Development] intersectRaven:
Yes. It's still under heavy development so stick to non-pmtest if you're not comfortable with it. Anyways, it's just a test. :p

This is just wrong. Fastboot flash BOOT assumes you're flashing a WHOLE BOOT.IMG thus replacing the ENTIRE BOOT PARTITION. The fastboot flash zImage flashes JUST THE KERNEL in the existing boot partition. :)
[Nexus One Android Development] mezmer1ze:
I tried the 800mV CFS kernel from 4.5.2010 but it drained like 17% of battery per 7 hours - and I didnt do anything extraordinary, some texting and calls and didnt see any suspicious activity in battery usage or spare parts. So far the best option for me is still the 800mV kernel from 24.4. which drained about half of this rate.
[Nexus One Android Development] ratson:
@intersectRaven could you add optional OC to your kernel? with stock defaults. Ivan's Diet is pretty cool but not updated....
[Nexus One Android Development] mtw4991:
So, if I'm already running on 0505_1138 CFS 925 with a #4 in the kernel string, these latest updates will only change the #4 to #2 and indicate visually whether it is CFS or BFS, correct?
[Nexus One Android Development] slyydrr:
He's mentioned many times in this thread that he won't be adding any OC options to his kernel... sorry.
[Nexus One Android Development] mtw4991:
Read the thread or search, IR don't do OC'ing. Ivan does.
[Nexus One Android Development] schahr01:
Doh! Sorry for the misinformation then.
[Nexus One Android Development] playin4sheezy:
Ok. So i have flashed each of the kernels and tested them. After 2hrs of very minimal use(texting maybe 5 times and checking facebook once) I have a 12% battery drain. Im running the latest Cyanogen ROM.

I keep reading posts from people getting all this great battery life and am wondering what it is that I am doing wrong?
[Nexus One Android Development] hah2110:
I was in your boat as well. Some of these kernels don't provide benefit to everyone the same way. I would make sure you charge to 100% (plus 30 minutes) and then wipe stats and just keep flashing until you find the sweet spot.
[Nexus One Android Development] Amrosorma:
What kernels are you all using for awesome battery life? What phone features are you disabling? What screen brightness?

I'm getting the same results as playin4sheezy with 5/04's 925 CFS :(

I'm trying the latest 925 CFS out though :)
[Nexus One Android Development] playin4sheezy:
Ok. Thanks alot! Ill keep trying and eventually ill find it lol
[Nexus One Android Development] slyydrr:
Alright, something that I've noticed on essentially any kernel after the 20100429_XXXX kernel: Toggling wifi on IMMEDIATELY following a fresh flash (aka, no reboot after the flash) causes the phone to reboot. Unless you manually reboot the phone, it will continue to lock up every time wifi is toggled on.

Furthermore, even after a reboot following a fresh flash (which allows the wifi to be turned on), I've noticed a couple of times where the phone cannot disable the wifi (shows "Unable to stop wifi" in the settings).

Has anyone else experienced something similar to this?

It seems like there might be an issue w/ the latest wifi driver perhaps?

EDIT: Okay, even worse now. I'm getting a FC in wifi settings followed by a freeze/reboot. I'm going to try manually flashing the new kernel w/ the old wifi driver from 4/29 and see how that works. Can anyone else please confirm wifi instability with the latest kernels when trying to toggle it on/off?
[Nexus One Android Development] Amrosorma:
Let us know which one you pick :)
[Nexus One Android Development] slyydrr:
Sorry for quoting myself but I feel it is important for this situation and keeps the posts related. I'm obviously realizing now that there's more of a relation between the wifi driver that comes packaged with the kernel and the kernel itself as the 4/29 wifi driver won't work with the 5/06 kernel. However, it really seems that there's a bug in the wifi drivers post-4/29 as I haven't been able to successfully toggle wifi on/off since that kernel version.

Intersect, can you take a look at this by chance, or can anyone perhaps point me in the direction of a log file that might show any exceptions I'm encountering?

Thanks!
[Nexus One Android Development] intersectRaven:
Are you perhaps connecting to an access point which has a hidden SSID? There is an issue with it. :)
[Nexus One Android Development] bt1980:
I was having similar problems (even connecting to an open wifi with broadcasting SSID - while I was in a restaurant yesterday showing Layar and Sky Maps to someone and my N1 started embarrassing me like I had misbehaving children haha...) but that was apparently only with BFS kernels. I switched back to CFS-800, and it looks like the problem may have subsided for now...

edit: In case it matters, I'm using CM-5.0.6, Desire Camera, and HelixLauncher 1.
[Nexus One Android Development] slyydrr:
Damn you're good! That'd be it! I apologize if this was documented elsewhere in the thread... I've been keeping up w/ 99% of the posts (I thought it was 100% but perhaps I missed a post? :)) Any ideas on when that might be fixed?

Thanks!
[Nexus One Android Development] intersectRaven:
Helix Launcher has problems with BFS so that might be it. :)

When the updated WiFi driver works it should be fine. Although it might also be an issue with a modification I made just to enable loop unrolling in linux_osl.c. :confused:
[Nexus One Android Development] slyydrr:
Hmmm okay that's what I figured. If you felt like making a new wifi driver without the loop unrolling and wanted to PM it to me, I wouldn't mind testing it for you if that helps! I'm not sure why that would cause the issue but then again I'm not sure what the loop unrolling does and how it could/would affect wifi in the first place.
[Nexus One Android Development] Ownatik:
been running latest kernel 925 bfs and pmtest for a couple of hours now without a single problem. everything is smooth. good work and keep it up!
[Nexus One Android Development] lorloff:
So I searched the thread and found it has to do with cyanogen driver revert, but that's all I could find. Is there more explanation somewhere else?