yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] intersectRaven:
The .33 branch has always been stable. :) Anyways, what I didn't hear though is that .33.4 has been released. Thanks! :)
[Nexus One Android Development] b1337:
didnt see any in the changelog but didnt do a side by side comparison, im not here to use correct punctuation, but i will try harder just for you buddy
[Nexus One Android Development] intersectRaven:
Update!

20100513_10XX:

- updated to 2.6.33.4

- merged latest commit from cyan

20100513_1024:

BFS:

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

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

CFS:

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

925mV -> http://www.mediafire.com/?zkmzdmmedmy
[Nexus One Android Development] x986123:
Awesome, about to try!
[Nexus One Android Development] bskim23:
Are the new updates set to run on CM 5.0.7 T2?
[Nexus One Android Development] intersectRaven:
You can use it on 5.0.7 T2 but I haven't reoptimized it for it yet. (as in making NEON optimizations instead of VFPv3 ones) :)
[Nexus One Android Development] Docmjldds:
Will this work with Desire Camera video?

Edit:...Nevermind...IT WORKS!!!!

FYI...installed as update.zip from recovery, instead of ADB push and fastboot flash etc.

Battery temp staying a bit high at 33.7 since installed and basically idle

Edit#2*******Never Mind these posts***********

Installed the latest .33 update and NOT the .34
[Nexus One Android Development] Docmjldds:
Installed USB switcher from market and I can mount and unmount using the app, FYI ;)

Edit: Just realized that two versions posted. I installed the .33 version, so disregard USB switcher app as workaround. My bad...Sorry....
[Nexus One Android Development] intersectRaven:
I see. I still want it done through the interface though. :)
[Nexus One Android Development] bewA:
have you stopped doing the 33.3 kernels?

If so how long till you think the 33.4 ones will be stable enough e.g. usb mounting (sorry that's the only one i've come across so far, i'm sure there are more)?
[Nexus One Android Development] dessanct:
Unmounting works for me now with the new 5/13 update.
[Nexus One Android Development] intersectRaven:
Nope. I'm maintaining 2. Namely, .33.X and .34-rcX. The one with USB mounting problems is the latter. :)

That's because it's the .33.X kernel which is stable. :)
[Nexus One Android Development] kitman8888:
Using the 0513 BFS 925mv version,could't play video smoothly.
[Nexus One Android Development] Docmjldds:
Agreed, but workaround better than having to boot to recovery/USB toggle when required.

Edit:...Just realized from your post to another user that I installed an update based on .33..not .34. Disregard the USB switcher
[Nexus One Android Development] m00moo:
normally after installing a new rom i instantly flash IR kernels over, but upon installing cm507t2 last night i decided to stop. Sorry to say battery drain on your kernel is almost double to stock for me :confused: normally over night i lose about 1% per hour idle with your kernels, but last night i lost 5% in almost 8-9 hours. Anybody noticing the same?
[Nexus One Android Development] L10nH34Rt:
Use 33.x branch :) 5% in 9 hrs is impossible to achieve. Must be sth wrong with your battery stats.
[Nexus One Android Development] snavid972:
hows the 5/13 kernal running for yall I just installed it the 800 one..
[Nexus One Android Development] bt1980:
5/13 kernel 33.4 CFS 925mV

I have noticed that when on "conservative" governor, my CPU remains clocked at max setting (according to SetCPU active widget). I have switched to On-Demand governor and it appears to be working correctly. As a result I have no comment on battery life.

Otherwise, everything seems to be working great with 33.4. It is stable and all of my apps work just fine (including Desire Camera mod and video camera). I am using HelixLauncher1 and CM-5.0.6. Everything seems very responsive; but that may be because I am using a more performance oriented governor than I previously was.

My WiFi connects at "65 mbps" which must mean that 802.11n is working. I observe this by going to Wi-Fi settings and tapping on the connected network.
[Nexus One Android Development] m00moo:
not impossible. ive done it before on the early cm 505's. and i do a complete wipe EVERY time i install a new rom. Its funny to doubt just because you haven't achieved it. lol
[Nexus One Android Development] myplague:
Re: [.33.4 & .34-rc7]intersectRaven's Kernel (Hybrid AVS *Stable*) 05/13/2010 10:42am

Try having setcpu auto detect again.

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

Sent from my Nexus One
[Nexus One Android Development] bewA:
oh so this has the new wifi driver for N and FM (although the FM probably won't work without other stuff)?
[Nexus One Android Development] jblazea50:
So, in order to have 802.11n working, I'm assuming you'd need to have a router that supports the n configuration?
[Nexus One Android Development] Chahk:
Similar experience here on 5.0.7-t2 with latest IR kernel (2.6.33.4_AVS-925mV_CFS_20100513_1031). From yesterday evening to this morning the phone lost about 5%. Combined with the preferred network type change, I'm seeing a lot less power drain when phone is sleeping. Battery Use reports Cell standby at 22%, as opposed to close to 50-55% I was averaging on stock 5.0.7-t1 kernel and "WCDMA preferred" setting.
[Nexus One Android Development] bewA:
just out of interest. Is this USB mounting problem a driver issue or something else?
[Nexus One Android Development] Jack_R1:
Bug report, on all latest kernels. Didn't happen on 0429 kernel, happens on at least 2 latest kernels - 0508 and 0513 with CFS.

One of the WiFi networks I connect to uses hidden SSID with open connections (no encryption). I have this network remembered, naturally. When I turn on WiFi in range of that network using Power widget (not going into WiFi settings), I get a phone restart instead of connecting to the network. If I keep WiFi settings open when trying to connect, sometimes it restarts and sometimes it doesn't.

When the phone boots with WiFi enabled in the range of that network, it connects without problems.

Tested 0429 kernel, no problems there, connects and disconnects with no hassle.
[Nexus One Android Development] bt1980:
I just did that and it seems like Conservative governor might be working again. That is strange. I've never had that problem before (and I've flashed lots of kernels). Thanks for the advice!

This was mentioned in the thread earlier. I had to change my SSID to be visible and all is now well. You're correct tho, after 04/29 is when it began. It has affected every kernel since then.

Dunno about FM; but looks like N is there.

Yes, your router also has to have 802.11n capabilities.
[Nexus One Android Development] mtw4991:
I'm using WCDMA Preferred and routinely get 20% cell standby times...umm I never got 50-55%. Are you using GSM Auto(PRL)? What network are you using...T-mo US?
[Nexus One Android Development] jlevy73:
It's a kernel issues associated with .34rc7.
[Nexus One Android Development] bobdude5:
Latest 800 cfs 33.4 kernel is draining the hell out of my battery

1 percent every two minutes
[Nexus One Android Development] mezmer1ze:
Didn't notice any excessive drain with the latest 33.4 kernel, it seems comparable to me with the other .33 (~1% drain at standby per hour) and I'm using the one you mentioned.
[Nexus One Android Development] hah2110:
Can anyone else confirm battery life like this?

Agreed... I've never seen cell standby that high.
[Nexus One Android Development] dictionary:
me 2

10 chars
[Nexus One Android Development] Chahk:
I'm on AT&T. I believe the reason my cell standby has routinely been in mid-50% is because of the horrible reception in my office at work. The phone had to constantly hunt for the signal which was killing the battery. Switching to "GSM Auto (PRL)" helped a lot. Combined with Raven's under-volted kernels my phone can now easily last through the day and have ~45% by evening.

Latest .33.4 CFS version has been rock-solid on my phone btw. But then again, the .34 RC7 never gave me issues either.
[Nexus One Android Development] android_future:
Re: [.33.4 & .34-rc7]intersectRaven's Kernel (Hybrid AVS *Stable*) 05/13/2010 10:42am

The lateat kernel, is producing the best battery life for me since I've started using his kernels.

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

Sent via the XDA Tapatalk App
[Nexus One Android Development] britoso:
Just wanted to report that the standby time is simply awesome now.

2 hours since unplugged 96% left. Wifi, Sync, bluetooth, auto brightness, gtalk. Only 4% battery used! 67% on the display.
[Nexus One Android Development] wildmonks:
After further investigation on my end, I found out that I can use the new wi-fi driver to connect to networks that don't hide their SSID.

I usually set my router's SSID to hidden, thus I have to click on "Add Wi-Fi network" on my nexus under Wi-Fi settings and manually type in the SSID and WPA. After doing that, my nexus started rebooting by itself.

So as long as I avoid using the "Add Wi-Fi network" option, I can use the new bcm4329.ko.

Of course I can just not push the new bcm4329.ko as christiankk suggested and I will never encounter this strange problem. :confused:

(I have repeated this many times over so this strange problem is reproducible for me. . .)

BTW: This new kernel is totally awesome. Seems to run a little more smoother while still benefiting from the AVS feature. It's close to feeling like this kernel is running overclocked :D
[Nexus One Android Development] Markdental:
Am I to understand that the xtra is the more stable AVS kernel?

So that is the one to start with correct?
[Nexus One Android Development] overground:
Well, MAY be more stable, depending. Some processors like the xtra, some don't. Try 'em and see what works best for you. But, yes...I'd start with the xtra and work down from there.
[Nexus One Android Development] Markdental:
Great thanks, just tried xtra and froze three times on opening animation.

On to the next
[Nexus One Android Development] wildmonks:
Yah, I'd start with the xtra version as it certainly won't hurt anything permanently.

And uh.. to all those concerned about the wi-fi thing I mentioned, don't be because I believe I'm the only one experiencing it, haha
[Nexus One Android Development] Markdental:
Well, I tried both the AVS kernels and both froze on me either during the boot animation or right after I got to the homescreen. I must ahvea weak CPU or something. I am running Cyan 5.0.3.

Is it possible that it is something I did? I wiped cache before boot also.

Oh well, I tried.
[Nexus One Android Development] overground:
All I can tell you is, if you wanna keep experimenting, keep your phone hooked up via usb to your pc, and if in bootloop, adb reboot. I've read that it can take 4-5 boots to get up and going, although I did not get any. Makes me wonder if I did something wrong. :p
[Nexus One Android Development] rori~:
This makes me want to try it too...

Edit:

fastboot & push...worx straight away...let´s see how it performs! - thanx intersectRaven*
[Nexus One Android Development] MaxiJavi:
OK, powersave does use a little less battery, but is very sluggish at time.

conservative is smooth as silk and working well on the latest kernel !

Thanks again !
[Nexus One Android Development] Paraglider1982:
I went back to non AVS, since the last updates I have problems with it.

The phone reboots or shuts down.

With the earylier releases all was fine.

Now without AVS it's fine again.
[Nexus One Android Development] HoOnZ:
Can someone point me to what the differences are between the non-AVS, AVS and AVS+Extra kernels? i did some searches but can't find anything concrete.

Thanks!

- JOhn
[Nexus One Android Development] intersectRaven:
You're one of the lucky ones. Even I had to experience 1 reboot the first time I did AVS. :D

Difficult to say. Even debugging AVS don't yield concrete clues as to what is causing the lockups/reboot. It will just work for some or not at all. :(

Stable should work for everyone. If you want to look at it in another way, the xtra is the non-undervolted version of the AVS. (I'm beginning to think I should make that the default and drop the forced undervolted AVS since I already confirmed that AVS is properly regulating the voltages.) ;)

I see...a very weird problem. Maybe its because cyan rolled back the wifi driver to an older version on his latest commit?

Lucky! :p

Non-AVS = Undervolt voltages is fixed to the frequency

AVS = voltages are dynamic and can be adjusted based on the CPU's request; the maximum voltage is also undervolted (1250)

AVS_xtra = same as AVS but the maximum voltage is stock (1275) :cool:
[Nexus One Android Development] hah2110:
Just flashed the newest one. WiFi worked without the kernel and it booted on the first shot. Conservative was really sluggish for me (and powersave was even worse) 2 versions ago so we will see how this does. So far, seems to be better.
[Nexus One Android Development] HoOnZ:
Thanks a lot! That helped on which version I want to load. :)

- JOhn
[Nexus One Android Development] Pochemuchka1977:
Well, after flashing the last version, I still receive a lot of reboots and freezes

A quick print of dmesg log shows, that i have a lot of these:

<6>[ 174.617919] do_imprecise_ext: ADFSR = 0x00000004

<6>[ 174.618103] do_imprecise_ext: DFSR = 0x00000436

<6>[ 174.618255] do_imprecise_ext: ACTLR = 0x000c0037

<6>[ 174.618438] do_imprecise_ext: EFSR = 0x00000004

<6>[ 174.618530] do_imprecise_ext: L2SR = 0x00010000

<6>[ 174.618682] do_imprecise_ext: L2CR0 = 0xc0050f0f

<6>[ 174.618865] do_imprecise_ext: L2CPUESR = 0x00000020

<6>[ 174.618957] do_imprecise_ext: L2CPUCR = 0x000000e0

<6>[ 174.619201] do_imprecise_ext: SPESR = 0x00000000

<6>[ 174.619293] do_imprecise_ext: SPCR = 0x0000000f

<6>[ 174.619384] do_imprecise_ext: DMACHSR = 0x00000001

<6>[ 174.619598] do_imprecise_ext: DMACHESR = 0x00000000

<6>[ 174.619689] do_imprecise_ext: DMACHCR = 0x0000000f

<6>[ 174.619873] do_imprecise_ext: TCSR_SPARE2 = 0x0000a037

<1>[ 174.620025] Unhandled fault: imprecise external abort (0x436) at 0x4838a00

0

What do these errors mean ?

P.S. Tried to flash the Ivan's AVS kernel - run much more stable so far ... As I understand the AVS code is the same - so the problem might be in compiler's optimizations ?
[Nexus One Android Development] jombay:
Everythings working great on CM5053. Haven't had ANY problems with today's release... so far :P

Keep up the good work.
[Nexus One Android Development] intersectRaven:
Might be...I'm too aggressive with my compiler optimizations... :p
[Nexus One Android Development] Pochemuchka1977:
Yeap, that might explain why the kernel is so unstable on specific devices ... And i thought it's the AVS fault :-)

Is it possible to compile a less optimized kernel? I would really like to run your kernel as the most updated one, but seems that the optimizations are far too aggressive for my device
[Nexus One Android Development] intersectRaven:
I'll turn off the optimization which makes it possible for erroneous floating point results and lets see how that goes. That's the only compiler optimization which I think COULD break something. As for me, the error you experience in your previous post hasn't been present here. I consulted ARM's documentation and found that it could be an application that triggers it. :)

Here's the file:

http://www.mediafire.com/?yxmoy2ifmyx
[Nexus One Android Development] S_Dot:
40 hours since boot.... Thanks Intersect, for those who said it cannot be done it can!

Light/Moderate use, lots of texts, some browsing and some calls.

here:

..still got 10% left :p
[Nexus One Android Development] Breece:
How come your display is at 3% ?
[Nexus One Android Development] THATTON:
What kernel were you using?
[Nexus One Android Development] abrixxxx:
next time click on display and show how long the screen was actually on for

3% how mines like atleast 40ish even with light use
[Nexus One Android Development] Docmjldds:
His sig shows this:

Kernel:intersectRaven's AVS Kernel .33.2 (0424)

I do wish everyone here would reference there current kernels etc when posting, either specific in the post or in their sig. Would drastically cut down on asking the same question. No reflection on you or his posting. Just commenting overall, when someone posts, "Best battery life to date with your latest Kernel." Latest doesn't really say much.

IE:
[Nexus One Android Development] dnsmo:
I am having the same problem with the wifi with the latest .33.4 also
[Nexus One Android Development] abrixxxx:
small request/possibility

having a kernel with the desire camera as i think it is superior to the nexus one's you update the kernel's frequently so i dont think youd mind it, but it may be more work than i think either way thank you for all your work it is greatly appreciated by the community
[Nexus One Android Development] timothydonohue:
wow. consider some punctuation, lol
[Nexus One Android Development] THATTON:
What? Did your keyboard stop working? You can flash the Desire Camera with IR's kernel combo and then reflash any of his kernels on top of it and the Desire Camera still works fine. Is that what you were saying?
[Nexus One Android Development] bt1980:
.33.4 cfs 925mV 05/13

Well I the conservative governor seems a lot less conservative than usual while I watch my setcpu active widget. I unplugged 4h ago and I have been mostly on WiFi and I'm down less than 50% battery. Think I'm going back to 0429 for a bit.

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

Sent via the XDA Tapatalk App
[Nexus One Android Development] PhantomRampage:
Can anyone tell me what the difference is between the BFS and CSF releases?

This will be my first time trying out IntersectRaven's kernels so im not to knowledgeable with his work
[Nexus One Android Development] dictionary:
http://xdaforums.com/showthread.php?t=653598&page=260&nojs=1#goto_threadsearch
[Nexus One Android Development] PhantomRampage:
I've been able to put together that the CSF kernel plays better with helixlauncher and BSF with with Launcher2 but that doesn't answer my question.

I also still don't know which to go with since i use HelixLauncher2 which to my understanding is a Launcher2 mod.

Any help please?
[Nexus One Android Development] dictionary:
Both will work with Helix. BSF will require you to let it sit for about 5 minutes after initial boot, otherwise you'll get a ton of force closes and lag. After that you're fine until you reboot. CSF doesn't have that issue. It comes down to preference after that. Try them both out. Usually, I would load up BSF (with Helix2), hit the power button once the phone booted, and would wait like 5 minutes before trying to use the phone. Worked everytime like a charm. Seemed to drain faster on my device though, while in use, so I went back to CSF.
[Nexus One Android Development] intersectRaven:
Update!

20100514_10XX - 1100:

- fixed the WiFi problem

20100514_10XX - 1100:

BFS:

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

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

CFS:

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

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

*updated .34 has also been uploaded but the music skipping and USB issues haven't been fixed yet.
[Nexus One Android Development] PhantomRampage:
Thank you for your insight. I appreciate it
[Nexus One Android Development] phunghoang24:
newest (Hybrid AVS *Stable*) 05/14/2010 11:12am

I flash kernel from SDcard ---> failse when reboot . Can't boot to Screen , only "X"
[Nexus One Android Development] 2000impreza:
Just tried flashing the latest kernel(20100514_10XX) using the adb push method and got the error "FAILED <remote: partition update fail>". It didn't allow me to reflash another kernel so the solution was to restore from a previous nandroid backup I did a day ago. Flashed back to yesterday's (20100513) kernel which has been working very well over the last day.
[Nexus One Android Development] intersectRaven:
Sorry about that! It seems that the loop unrolling option from the other compiler made the kernel much bigger than usual. I'll release an update in a few minutes. :o

*I really have a very good N1 since I can flash this kernel successfully on mine. :p
[Nexus One Android Development] Pochemuchka1977:
I had no problem flashing it either, so far everything is working
[Nexus One Android Development] sir*mez:
I guess we have the same luck, since my N1 is running perfect..
[Nexus One Android Development] intersectRaven:
Update!

20100514_14XX:

- replaced loop unrolling optimization with loop peeling to minimize image size

- BFS was modified with something that will *hopefully* increase graphics performance

20100514_14XX:

BFS:

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

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

CFS:

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

925mV -> http://www.mediafire.com/?zhezjd52ym3
[Nexus One Android Development] Realtyem:
Hehe, I got the last one to work on mine too, took forever to finally boot but it worked. Refresh my memory please what are we currently looking for in the way of bugs? USB is a given but what else? Video playback, music? I'll have to wait till the morning to test out this latest one as I'm on my way to bed. Night
[Nexus One Android Development] intersectRaven:
For .34, the only bug I know of is the audio skipping bug. This will be resolved as soon as I gradually rollup the driver updates from .33. If there are any other bugs which are major show-stoppers, please tell me so I can try to resolve it as soon as possible. :)
[Nexus One Android Development] Bay Harbor Butcher:
In last release did you fixed sd unmounting issue?
[Nexus One Android Development] Gilg@mesh:
does BFS still don't work with Helixlauncher?
[Nexus One Android Development] phunghoang24:
i have tested 2hours ago . now it's very good . i'm very very happy .official for me! best camera for my phone and take video 720p so fine quality . now i'm testing battery's life . thank intersectRaven .
[Nexus One Android Development] RussianSolja:
Forgive me for asking for I'm a newbie when it comes to kernels, but could someone kindly link me to the appropriate kernel download for modaco's desire Rom? Thank you to who ever helps. :-)
[Nexus One Android Development] Docmjldds:
Hard to give a good answer since Paul just posted in last 24 hours R22 Desire update. I just downloaded this as I write. Best answer would be make sure you have good Nandroid backups and basically see what works for you. Probably latest 925mv CFS .33 version would work, which I will find out in a shorty bit of time ;)

2.6.33.4_AVS-925mV_CFS_20100514_1425.zip is latest just posted
[Nexus One Android Development] RussianSolja:
What's the difference between CFS and the other one ? Sorry another newbie question.
[Nexus One Android Development] L10nH34Rt:
http://en.wikipedia.org/wiki/Brain_Fuck_Scheduler
[Nexus One Android Development] Untouchab1e:
Anyone have any idea why many of us are getting the very variable battery life?

Ive just worked out for an hour while listening to music the entire time and battery is still at 100%.

However, yesterday, the battery dropped 15 % after 30 minutes of some light menu browsing and emailing.. I then just turn the phone off, charge it up and then I may or may not get the awesome battery life. I am very puzzled by this because if I got the amazing battery life every time, then battery would no longer be an issue. But currently, its just not reliable enough!
[Nexus One Android Development] jay7stone:
I find it hard to believe you were listening to music for an hour and it remained at 100%
[Nexus One Android Development] kbeeveer46:
Can anyone let me know how stable this kernel is? The title of the thread says "stable" but there have been daily updates (even multiple times a day) that fix bugs and whatnot. How can something that needs fixed so often considered stable? How is battery life? I really want to try this out but I feel like I'd just be a beta tester when I need my phone to be as stable as possible.
[Nexus One Android Development] mrandroid:
Get the CFS - 925 version if you're worried. It's stable, no issues.
[Nexus One Android Development] :
Playing music uses very litttle resources.