yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] dictionary:
the more beer intersect drinks, the better the kernel. hint hint. (donation sent by the way)

925cfspmtest latest running on Cyanogen 5.0.7 nightly. Running flawless for 2 hours now.
[Nexus One Android Development] intersectRaven:
It's not the loop unrolling which is being held suspect. It's the modification I made to enable it to compile with loop unrolling enabled. Without modifications, the CodeSourcery toolchain will throw an "array subscript is above array bounds" error so the modification I made may have had an effect here. :confused:
[Nexus One Android Development] bloke226:
Will be buying more beer for IR tonight ;)

Running the 925mv CFS latest release and it's very smooth, stable, no FC, consistent battery life drain with moderate use.

EDIT: Using setCPU under conservative, will post pic tomorrow of battery use. I've been getting better performance and battery life out of the latest kernel updates :)
[Nexus One Android Development] slyydrr:
Oh, well that makes a little more sense. Can the modification you made be undone if loop unrolling is disabled (assuming it's a simple on/off flag that controls it) and still allow the driver to compile?

Anyway, let me know. And the offer still stands of course if you need someone to test out a modified driver.
[Nexus One Android Development] mtw4991:
Difference in kernels question

currently using 925mV-CFS-pmtest-0505_1138 that uses wakelock, I think:confused:

What is the difference between CFS-pmtest-0506_1511 and CFS(no pmtest)-0506_1459? I know the kernel string identifiers have changed per IR post a few pages back but not sure which one uses wakelock or not?

It's hard to keep up with IR...but he's real good at it! 14hrs light/mod use and still at 70%!!
[Nexus One Android Development] dictionary:
If I read correctly, the pmtest ones use the new suspend method, while the ones without pmtest use the standard wakelock.
[Nexus One Android Development] ibegary:
With latest pmtest 800 CFS, been having an idle drain of 2.5% per hour.

Very light usage (no e-mails, no SMS, two phone calls and maybe a 5 minute browse session).

100% @ 8AM. 90% @ Noon.
[Nexus One Android Development] mtw4991:
that's what I thought, but wasn't clear about it so I was looking for confirmation.
[Nexus One Android Development] dictionary:
Getting a little bit of lag in Asphalt 5. with 2.6.33_AVS-925mV_CFS-pmtest_20100506_1511
[Nexus One Android Development] hah2110:
I was wondering this too but your battery is consistent with what I was getting. What kernel are you using?

Sounds right. What does the name PMTest stand for?

I wonder if this is implying PMTest isn't as efficient as the other?
[Nexus One Android Development] schahr01:
10% drain in 4 hours for that level of usage is higher than what people including myself are seeing. Try the 925 CFS.
[Nexus One Android Development] hah2110:
So just to confirm... The current main page kernel is NOT PMTest?
[Nexus One Android Development] THATTON:
This exact same thing happens to me all the time but it has happened mostly on the 925 kernels. If I let my battery die down to about 90% and recharge or turn it off and recharge til the green light comes on, everything is back to normal in terms of discharge rate. I have never been able to figure it out. I was thinking it was a bad battery.
[Nexus One Android Development] phunghoang24:
I'm using CFS 925 0506 - and 0504 before that . everything is smooth , but i saw memory used : increase from 35% (start boot 12h )-> 65% ( check 24h) After 12hours. until i kill all app (taskmanager) then it's 35% . someone is as me ??????:o
[Nexus One Android Development] mtw4991:
confusing for sure and somebody correct me if I'm wrong, but as I understand it on Raven's mediafire page:

800mV Kernels-

BFS

0506_1435 wakelock

0506_1447 suspend pmtest

CFS

0506_1449 wakelock

0506_1510 suspend pmtest

925mV Kernels-

BFS

0506_1436 wakelock

0506_1448 suspend pmtest

CFS

0506_1459 wakelock

0506_1511 suspend pmtest

Also, as I understand, there isn't any changes other than the kernel string identifiers being #1=800mV and #2=925mV, plus identifying whether you are currently on CFS or BFS when you look in Settings>About Phone so you can keep up with what you are flashing.
[Nexus One Android Development] hah2110:
Can anyone confirm this? I don't think PMTest is doing it for me.
[Nexus One Android Development] bloke226:
Main page (1st post) doesn't contain PMtest kernels...
[Nexus One Android Development] playin4sheezy:
So out of these kernels.. Which one should I be using?? Anybody have a preference?
[Nexus One Android Development] Nauren:
So far I prefer 800mv BFS. I'm using PMtest but I don't think it's that big of a deal at this point.
[Nexus One Android Development] playin4sheezy:
What kinda battery life are you getting with that?
[Nexus One Android Development] Nauren:
I'm fairly impressed by it, but I listen to Pandora all day on wifi (if it's in the mood) or cell radio, so my results won't be of much help and it's hard to do a day to day comparison.

I'm at 71% after 4.5 hours. Three and a half of which I was listening to Pandora. The first ten percent went away while flashing/rebooting this morning.

Display: 40%

Mediaserver: 34%

Cell standby: 10%

Phone idle: 8%

Android: 4%
[Nexus One Android Development] playin4sheezy:
DAMN!!! Im at 68% with 4 1/2 hours of nothing!!! LOL. Made maybe one or 2 short phone calls. Texted a few people but besides that I havent even done anything worth mentioning. Im on 925mv CFS. I think Im going to try out the 800 BFS
[Nexus One Android Development] mtw4991:
17.5 hours @ 60% left with light to moderate use...couple of calls, text, downloads, movie trailers, opera, etc.

2.6.33_AVS-925mV_CFS-pmtest_20100505_1138...pretty good and no issues whatsoever.
[Nexus One Android Development] playin4sheezy:
Im using that same kernel and I would CREAM myself if I got that battery life HAHA! Are you keeping WIFI on or off?? What are some more of your settings?? Any suggestions on things to do?
[Nexus One Android Development] hah2110:
I unplugged on Tuesday at 1:30pm. I was using the 5/04 800 kernel. I went all the way until last night a little after Midnight and still had 19% left.
[Nexus One Android Development] mindfrost82:
I'm at 93% after 4.5 hours using the 925 pmtest (the 2nd one last night) CFS.

I have Exchange push email on and received about 5 emails. I sent/received about 10 texts and made 2 <5 minute calls. I also have the Weather Channel app set to update every hour and Facebook sync every hour.

I've been in full HSDPA for the whole time (60dB reception...antenna is just down the street lol).

Using enmother 1.8.1.
[Nexus One Android Development] playin4sheezy:
What is enmother?
[Nexus One Android Development] mykenyc:
enomther* 1.8.1 rom:

http://xdaforums.com/showthread.php?t=614427
[Nexus One Android Development] bloke226:
Pictures? Care to elaborate on your usage? Like 70% idle :p and what is your QoS in your area?
[Nexus One Android Development] hah2110:
I posted a picture at 18 hours a few pages back but, unfortunately, plugged it into my computer for a minute to transfer a file so I lost the reading. QOS at work is great but at home is switching between edge/3g all the time. Overnight I lost about 1% an hour. Usage was light-medium with moderate browsing, heavy text and e-mail, light calling and moderate app downloads.
[Nexus One Android Development] liemivan86:
Re: [Kernel - .33.3]intersectRaven's Kernel

Guys, sorry for the noob question. Just left this thread for about a week and it is full of new developments, so I'm trying to catch up.

Anyone care to tell me what is the difference between BFS and CFS and what they do in real life?

Thanks.. appreciate any help...
[Nexus One Android Development] mindfrost82:
Yeah, that one. Sorry about that lol.
[Nexus One Android Development] jlevy73:
http://www.google.com/search?client...ference+between+bfs+and+dfs&ie=UTF-8&oe=UTF-8

:)
[Nexus One Android Development] hah2110:
I'm not seeing as good of battery life with the newest 800 non-pm. No usage, 6% drop in 2 hours.
[Nexus One Android Development] crawler9:
QUOTE=jlevy73;6408600]http://www.google.com/search?client...ference+between+bfs+and+dfs&ie=UTF-8&oe=UTF-8

:)[/QUOTE]

I'd really appreciate a more direct explanation too instead of a Google search link. I've actually looked around quite a bit already for an answer to that exact question and which performs better theoretically vs which performs better in real life. I've searched on XDA too and finally found out what BFS is, but I'm still unable to find a comparison.
[Nexus One Android Development] schahr01:
Experienced something weird this morning with the latest 925mv CFS non-pmtest kernel - Battery drain while plugged in. I saw at least 2 drops of 2% (91 -> 89, 89 -> 87) in the course of about 5 minutes. First time I've seen something like this. I did unplug the USB, reboot and connect it again - same thing, drop while USB was connected.

I am back to the 4/29 925mv kernel - Before CFS/BFS, pmtest, loop unrolling and the use of the new toolchain

This kernel seems very solid to me and linpack scores (6.8 on average) are inline with what I was seeing with the newer kernels that introduce the fancy optimization features. I don't know - Could we be imagining the performance improvements these optimization attempts claim?

Is Knuth right? "We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil"

en.wikipedia.org/wiki/Program_optimization#Quotes
[Nexus One Android Development] andythefan:
Some strange stuff has been happening lately. I don't know particularly if it is from this kernel, or if my phone/battery is defective.

My N1 will be running normally, with normal battery drain when it suddenly turns off. I can turn it back on, but then it'll keep shutting off. When it's on I can see that it is <15% battery left despite having charging it all night, and only having it on for about an hour.

I've tried wiping battery stats, but that does nothing to alleviate the situation.

Today, it did the same, but the meter was around 83% when it happened, and I even had trouble turning the phone on. It would require multiple battery pulls just to turn on. Recovery mode doesn't even work :( (Holding trackball while turning on results in the phone not turning on at all)
[Nexus One Android Development] schahr01:
I would go with your gut feeling - Sounds like a hardware issue.
[Nexus One Android Development] mtw4991:
This was mentioned several pages back by Dictionary or somebody, but the

N1 doesn't start to recharge until battery level drops below 90% I believe. So you could have been at 91% and it wouldn't take the charge until it got to 89% and then momentarily drop again if you use it or reboot, etc.

Also, USB only delivers a trickle charge of 480mA or mV or something like that, while AC delivers twice the amount of charge. So a USB charge could drop while charging...I've seen that before myself.
[Nexus One Android Development] dictionary:
crawler, the best answer for you, is to try each. BFS is horrible on my phone for battery, but amazing for others, while CFS runs amazing. So long as you know what each term means, then the rest depends on your phone.
[Nexus One Android Development] andythefan:
Arghh... I just sent in my phone not even a month ago because the power button stopped working. This is ridiculous. Is HTC even checking build quality on their devices?
[Nexus One Android Development] crawler9:
thanks for the fast reply. i know that each phone is a little bit different but it doesn't make much sense to me that they should be so different as to cause such differences for us when we use the same software.
[Nexus One Android Development] hah2110:
Be careful... I went down this path a week or so ago and got SLAMMED for it. It took me over 20 kernel flashes to find ones that hit the sweet spot for me.
[Nexus One Android Development] lorloff:
You just made the big assumption, that we're all running the same software. Sure the OS is android, but other than that, nothing is the same. Each application you have installed affects what kernel is good or bad. Almost everyone using HelixLauncher2 reports issues with BFS, but CFS is fine. Also realize the undervolting is irrelevant to OS, but is based on hardware. And even though they try, not phone is 100% exact replicas, meaning differing voltages also act differently for different people. You just have to flash and try and see what is best for you. For me its 925mv CFS since I have Helix2. The 925 is due to the fact my phone was not stable at 800.
[Nexus One Android Development] mykenyc:
I always stuck with the 925 for some reason just a hunch i always had. But im seeing amazing battery performance also, i just talked for an hour on the phone, with wifi enabled and it only dropped to 93% in two hours (after phone convo texted and sent emails stuff like that).

im a happy camper but im also wondering what do the pm (im not using the pmtest btw) stand for nobody really defined it or did i miss something just curious?
[Nexus One Android Development] Bay Harbor Butcher:
Thus I have to try 4 different kernels?

800 CFS

800 BFS

925 CFS

925 BFS

what happen to the phone if kernel is not stable?what issue should I see?ANd why should I use 800 instead 925 or why 925 instead 800?

thanks..
[Nexus One Android Development] mtw4991:
I think it is just an evening test kernel that IR put together to test some things, but it's working well for me. I'm using 0506_1138-925mV-CFS-pmtest version right now.
[Nexus One Android Development] Docmjldds:
I have never had this on my setup. And my Wifi is typically off, prior to flashing updates. I do charge up to 100% and then some, then turn off WiFi and then Reboot and time holding the trackball down to get into recovery mode, to flash.

Edit: OK I see that SSID/access point issues caused this for your situation. I'm leaving my reply just so others can possibly use same methods for consistency, prior to flashing a particular zip update.
[Nexus One Android Development] intersectRaven:
I just finished my kernel reset. Will be releasing another batch of updates later. Hopefully it will be better since it's been rebased to the original cyanogen source instead of pulling from different repositories all over. :p
[Nexus One Android Development] THATTON:
Very nice!!! Can't wait!!! Beers coming your way!!!
[Nexus One Android Development] intersectRaven:
Update!

20100507_08XX:

- rebuilt kernel source from latest cyanogen commits to get rid of accumulated junk along the way

Here're the links:

BFS:

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

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

CFS:

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

925mV -> http://www.mediafire.com/?01yowmtqm02
[Nexus One Android Development] u3819013:
Hi Raven, Termana's .34 rc6 Kernel seems stable now, no more FC Video Camera now. you may try,it's smooth and faster than .33. :cool:
[Nexus One Android Development] bskim23:
Are these running the suspend blockers?
[Nexus One Android Development] THATTON:
Are these the PMTest kernels? I'm guessing not but just to clarify...
[Nexus One Android Development] intersectRaven:
No they are not. The pmtest kernels have also been updated though. I won't post links to them on the OP though since they're test kernels. :)
[Nexus One Android Development] intersectRaven:
I'll take a look on it tomorrow. If it's stable, I'll release at the same time that I release .33 since my maker script now supports...well, everything but the kitchen sink... :p
[Nexus One Android Development] bskim23:
Sweet I'll test them out :)
[Nexus One Android Development] THATTON:
Time to test out the latest batch of 925's! CFS and PMTest here we come! I'm looking forward to seeing the results. With the last couple I have flashed I have been having quite a few issues with my Launcher2 mod(HL2) freezing up a lot! It seems to be the only app that suffers any lag.

Seems that the new Active Widget Set CPU was the reason for the lag in HelixLauncher2. I happened to stumble across a post in another thread that pointed the finger and after changing it back to the other widget everything is snappy and quick again!
[Nexus One Android Development] rjhay22:
128 is unstable atm :-( i would like that too.
[Nexus One Android Development] intersectRaven:
I'll be releasing an updated kernel in the next few hours with a slew of compiler optimizations! Just a question though, does any of you use any software which relies on floating point accuracy? I'm thinking of enabling the -ffast-math optimization but it may lead to some erroneous floating point results. :confused:
[Nexus One Android Development] guyen01:
can you use this kernel with cyan?
[Nexus One Android Development] intersectRaven:
Yes you can! I'm using it with cyan's now! :)
[Nexus One Android Development] HoOnZ:
Which ROM are you using? Cyanogen's 5.0.6 test 2? or the 5.0.5.3 stable?

Salamat Pre! ;)

- JOhn
[Nexus One Android Development] intersectRaven:
Gamit ko yung stable! Don't really like test ROMs ever since I had to wipe all my data because of it. :p
[Nexus One Android Development] Pochemuchka1977:
Will it include any AVS improvements since the last kernel was not stable to some of us (even the xtra version)?
[Nexus One Android Development] christiankk:
hmm - i donno :)
[Nexus One Android Development] guyen01:
Should I uninstall setcpu then?

Would this interfere with AVS?
[Nexus One Android Development] MaxiJavi:
Can you make it a tiny bit overclockable ?

And add a few more speed steps please ?

Thanks !!
[Nexus One Android Development] bobdude5:
wow with this latest kernel on cyan 5.0.6 i got 15 hours of heavy usage: 2 straight hours of browsing and downloading (refreshing engadget every 1 minutes during those two hours), an hour of asphalt 5 racing game, texting all day, email, 1 hour of music, 20 minutes phone calls, more games, more internet browsing, news checking oh and auto brightness too..and i was in the sun alot so lots of times at full brightness
[Nexus One Android Development] intersectRaven:
I'm not really a fan of overclocking plus the original objective of this kernel is to maximize power savings while not sacrificing responsiveness so I will have to decline your request. :( Anyways, if you want overclocking, you can always use Ivan's diet kernel! :)
[Nexus One Android Development] intersectRaven:
Don't worry since as long as you don't set anything in SetCPU, it won't affect your processor. You could just use it to monitor your CPU or change CPU governors depending on your current usage! :)
[Nexus One Android Development] MaxiJavi:
Yours seems to be better :-)

What about extra speed steps ? Right now the increments are rather large.

(I used to clock at 960)

Is there a better way to change the CPU governors ?
[Nexus One Android Development] GlenH:
How many people are finding these AVS kernels stable?

I tried this one and Ivan's diet and both crashed after a while and eventually went into boot loops.

This was with Enom's official rom btw. Do the kernals work better with Cyan's roms perhaps?
[Nexus One Android Development] danielherrero:
Same here. When I install these kernels finally I ve to restore the old one because of crashes, self resets, loops, etc...and I use Cyan 5.0.5.3

Dani
[Nexus One Android Development] Pochemuchka1977:
Same here - eventually the phone either freezes or gets into bootloop.

Using latest stable CM too. Now running with the latest non-AVS kernel
[Nexus One Android Development] intersectRaven:
Hmmm...I don't know about that...I'll try it...about the CPU governors, what do you mean by "better way"? It is the easiest way that I know of. The other would be going through terminal and change it there through the command line. :)

It's not about the ROM, its the CPU. Different CPUs react differently to AVS. Although the design is basically the same (Snapdragon), they react differently to this feature. In the first place, this feature isn't really included in the official driver so it really is a stretch if the N1's CPU supports it. :(
[Nexus One Android Development] seanowns:
No problems with any AVS kernel's to-date.

Currently trying the SUPER AVS which is undervolted down to .925 apparently. Running like dream.
[Nexus One Android Development] christiankk:
yo dawg, where did you get a "super avs" from?

edit: ah, it is an ivan kernel.
[Nexus One Android Development] Archimago:
Just tried Termana's latest. I'm still getting FC on video camera... Once was bad enough to reboot the whole system :-(
[Nexus One Android Development] u3819013:
wipe dalvik cache and reinstall kernel. it works for mine.
[Nexus One Android Development] liam.lah:
result from your link.

Thank you for being so helpful :)
[Nexus One Android Development] hah2110:
Can anyone explain why I can have fabulous results on Kernel ABC, change to another kernel, go back to Kernel ABC and not have the same results? I.e., I just moved back to the same kernel I was using the other day when I was getting kick @$$ battery life and lost 25% in 4 hours and haven't even used it except for ten minutes. I don't get it. What are people's experiences with the PMTest? Better? Worse? The only thing to note in my flashing is that I don't always do a full charge and then wipe, not sure if that is relevant or not.
[Nexus One Android Development] mykenyc:
it depends on a lot apps, and cpu load everything its like a luck of the draw with software. Never going to have the same battery life every shot you get is what i gather.
[Nexus One Android Development] rjhay22:
Thats why you should follow that rule, when it aint broke don't fix ;-) I did experience the same thing. And I wondered as well, I'm beginning to think the UV kernels dont really make much of a difference, probably help out a little, but its very much a hit or miss situation. What made me say this? After fresh flashing Cyan 5.0.6, without a UV kernel, left it overnight and it average .5% drain/hour on standby, when I woke up I installed some apps and widgets, and the PMtest 925mV kernel on top of it, battery drained like a biatch again...

I still dont understand how and what I did differently that made such results, so I fresh flashed Cyan again to see if it was a fluke, and it gave me about 1% /hour drain the second time around...... I re flashed the PMtest 925mV version again, and successfully stay at 1%-1.5% drain /hr, so I'm sticking to this one...

I just gave up on finding the perfect kernel... I just admit the fact that I have a nexus one and not a Motorala Razr.
[Nexus One Android Development] rjhay22:
Yes, definitely the apps..... Without apps = Long lasting battery, So we all should pick our APPS wisely :) I have proven this already by comparing the same exact ROM / Kernel, with / without apps. I'm just not sure why, all I have are theories. Perhaps someone that knows will enlighten us :) Or if theres a way to find out which apps are the culprit would be nice. The battery use from About Phone just doesn't help much.
[Nexus One Android Development] vegetaleb:
That's why you should use a Task Killer with autokill

Is it true that using 800mv on long term could be bad for the battery or CPU?

Is there a better kernel than the 800mv 20100429_1009 ?
[Nexus One Android Development] ratson:
you shall use AutoKiller, it will help you out in such situations. I also recommend running spare parts and see if any of your apps has high partial wake usage...
[Nexus One Android Development] bewA:
But it does tell you what apps are using whatever % of battery...
[Nexus One Android Development] vegetaleb:
20100429_1009 800mv VS latest CFS 925mv what's better for battery and stability?
[Nexus One Android Development] bewA:
Why dont you try and find out for yourself! :)
[Nexus One Android Development] vegetaleb:
Because I still didn't finish my first battery cycle with the first one ;)

It will be 48h in 7 hours and still have 40% , it's good but still not breathtaking revolution, my target is to reach 3 days with moderate use