yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] sassafras_:
Why do you stick entirely with CFS based kernels? I've ran both CFS and BFS based kernels and I notice a subjectively better user interface and scrolling performance on a BFS based kernel. Is there a reason in your opinion to choose one over the other?

If you're indecisive, is there any way you could compile a BFS based AVS power managed kernel?

sassafras
[Nexus One Android Development] kazprotos:
Yep 2.6.35.4_AVS-CM-950mV_CFS_20100910_0957.zip
[Nexus One Android Development] Dively:
Just Wondering

I am running CM6 N1 and have just started getting into custom kernals. Anyone have a recommendation for a good kernal?
[Nexus One Android Development] intersectRaven:
I'm...indecisive?!?! I think I'm going to cry in a corner for awhile... :(

Seriously speaking though, noone asked me to release yet.

Well, cyan just began work on the .35 branch so maybe some bits are still missing? :confused:
[Nexus One Android Development] intersectRaven:
Hmm...depends on your own preferences. Here's my opinion on the matter:

Latest versions with no regard to stability (it just boots) -> mine

Latest + overclock + more stable -> wildmonks

Latest + stable -> pershoot's / kmobs'

Most stable but not necessarily latest -> stick with bundled kernel in ROM

please wait 2 seconds for an uncompressed image, or press Ctrl+F5 for original quality page
[Nexus One Android Development] madj42:
I hate to burst your bubble about bluetooth working correctly but I've had nothing but problems with it. It won't connect to my computers or my car radio correctly. The car radio it will connect to but it's not stable. Also when I go into the bluetooth options and turn on discovery mode, it doesn't count down from 120 seconds. It hangs on 120. I'll turn bluetooth off and then I can never get it to turn on again.

I've had this issue with the latest kernel from yesterday and also a previous kernel from the 7th. Would a logcat help in this situation or is there another log that will help? Forgot to mention I'm running CM6.
[Nexus One Android Development] intersectRaven:
Unfortunately, BT really doesn't work with CM6. The bluetooth stack is for Desire ROMs at the moment. Once cyan gets the evo to work with CM, I'll port whatever kernel parts are necessary. :(
[Nexus One Android Development] mtw4991:
fyi, Wildmonks has been MIA for awhile now...no updates since 0827 and it seems that poochie2 is kinda filling in for him so I don't think his kernels have the latest commits so I'm not sure about stability/feature compatibility. 2 weeks gone is a lifetime around here;)

Perhoots/Kmobs is also oc'd, just to 1113 not above it.
[Nexus One Android Development] pershoot:
correction:

kmobs - no oc. cm source.

pershoot - oc. multi-source (korg,aosp,cm,pershoot)
[Nexus One Android Development] mtw4991:
I stand corrected, lol. I thought IR meant that kmobs and yours were the same. Isn't yours in and updated with the CM nightlies though? CM nightlys are oc'd...gets so confusing trying to keep up with everyone sometimes, lol :confused:
[Nexus One Android Development] pershoot:
a good portion of it has made it in, yea.
[Nexus One Android Development] Gilg@mesh:
so bluetooth don't work with CM6?
[Nexus One Android Development] intersectRaven:
From what I've heard from those using my kernel on CM6, nope. :(
[Nexus One Android Development] Gilg@mesh:
ok thanks for answer, I was going to try 2.6.35.4_AVS-CM-950mV_CFS_20100910_0957.zip
[Nexus One Android Development] harunjo:
sory for not to give you a complete info...when that happen i was using leofroyo rom....now i am revert back to cm 6...and use kmobs latest kernel..

i will try your kernel later with cm 6 stable...sory again to make you confused
[Nexus One Android Development] wbknox:
did you fix bluetooth in cm 6?
[Nexus One Android Development] intersectRaven:
Update Released!
[Nexus One Android Development] intersectRaven:
Working on it. It only occurred to me now that you don't need the FM components in CM6. :)
[Nexus One Android Development] intersectRaven:
CM links updated with BT fix. (that is I reverted the FM components so BT should work now) :)
[Nexus One Android Development] intersectRaven:
Modified links for BFS since I forgot a commit for BFS. :p
[Nexus One Android Development] Gilg@mesh:
the GPS stopped worked, latest CFS CM... anyone else?
[Nexus One Android Development] Hirosakamoto:
I tried to download your Kernel, everytime I download one type and install it.

1: My Wifi and 3g doesn't work. Or if I install other one

2: Camera and 720p doesn't work >_<!

Do I need to install many kernels then update one afther one? I hope you can help me:)

I've Cyan 6 Rc3 with radio 5.... (Korean Radio)
[Nexus One Android Development] intersectRaven:
Since you're on CM ROM, have you tried the latest kernel with -CM on them? As for the WiFi problem, have you tried pushing the module via adb? Sometimes it doesn't work when run through recovery. :)
[Nexus One Android Development] Hirosakamoto:
Yeah I tried... I used the CFS HAVS-CM

what adb? If it doesn't work, how can i fix the problem?:)

Thx for answering!:D
[Nexus One Android Development] intersectRaven:
I think there's a thread somewhere here in XDA that will educate you about adb. Anyways, does camera and 720p work with the -CM kernel?
[Nexus One Android Development] Hirosakamoto:
Ah okey.. I will try and find it out :)! Umm Yes it does, what doesn't work are Wifi and 3G network, the sound is low( are there any sound booster)? Umm I've haven't checked much, because I need most only Wifi,3g and camera with 720p :)
[Nexus One Android Development] intersectRaven:
Ok. You just need to push the modules manually using adb commands. Just read about it somewhere here. :)
[Nexus One Android Development] Hirosakamoto:
Ah.. So I don't need to download and install any other kernel:)? Now I just need to find out the adb cmds and put it in. I searched abit, i found this link xdaforums.com/showthread.php?t=613217

can this work? or don't u know:P?
[Nexus One Android Development] intersectRaven:
Wait, I just remembered that there are instructions on the OP of this thread. You can look at it there. :p
[Nexus One Android Development] Hirosakamoto:
Or possible about u can help me over skype or something^^ I'm willing to "buy beer for u" If i can get help and it works:)!
[Nexus One Android Development] mtw4991:
Come on guys, please read first as the devs shouldn't be asked these basic ?s
[Nexus One Android Development] dessanct:
I'm not sure if this is kernel related, but after updating to your latest IR, my phone has been running noticably warmer and the data connection is slower (on/off at times).
[Nexus One Android Development] clustered:
Camera FC, open again, now cannot connect to camera.. running cfs-havs cm...
[Nexus One Android Development] intersectRaven:
Did it work before? If not, then I may have not reverted the necessary commits in that release. (it is hard to compile different kernels you know?) :p
[Nexus One Android Development] MicroMod777:
Which kernel would be recommended for Enom's 2.12.1 ROM?
[Nexus One Android Development] Hirosakamoto:
Hehe.. Not everyone are used to cmd and so;)!
[Nexus One Android Development] intersectRaven:
I don't know. What base is he using? If Desire, try the ones without -CM. If CM, use the -CMs. Whether you choose BFS or CFS is up to your preferences though. :)
[Nexus One Android Development] Hirosakamoto:
Where can I find the zImage and bcm4329.ko? file? I trying to follow this way ...

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

edit: I found the zImage and Bcm4329.ko drivers.
[Nexus One Android Development] Pochemuchka1977:
Running 2.6.35.4_AVS-CM-950mV_CFS_20100911_2026.zip with CM 6.0.0 and experiencing sudden freezes ...

Checked the last_kmsg file - Unable to drop ACPU vdd message appears just before the freeze

Is there a SVS kernel for CM6 ?
[Nexus One Android Development] Hirosakamoto:
I am on step 4 now

4.) fastboot flash zimage zImage

The problem now is, it says writing zimage. I've waited for 5minutes now, and still nothing. Did the cmd crash or so? 0_o?

EDIT: I made it! But got a new problem.... Camera and 720p doens't work.... ._.! again! I don't know what the problems i'm getting alle the freaking f****** time T_T!
[Nexus One Android Development] intersectRaven:
Minor update! :)
[Nexus One Android Development] YoMarK:
Getting FC's on the camera with the 20100913_09XX (BFS HAVS)build on MicroMod 2.6.1 Rom.

Edit: I see you got a new build, trying that one. :)

Edit2:

Problem is still there. It's seems te happen while exiting the camera. Images and video's are being recorded and saved properly, but after that the Camera FC's.

No sure if this is a kernel problem, or a ROM problem(since MM version 2.6.1 is also new for me). Never seen this on older MicroMod/Enomther ROM's though(using Wildmonks kernels).
[Nexus One Android Development] intersectRaven:
Since the problem happens when you exit, I don't think it's with the kernel. Anyways, you can try others just to be sure. :)
[Nexus One Android Development] redstar3894:
Hey IR, love the work you've been doing, thanks for keeping up with all the latest commits and everything else... your kernels are some of the most well put together (and supported) work on xda by far... :)

I was just curious what your reasoning was for switching from the 0xlab ARM optimized toolchain to the prebuilt one from AOSP.... I haven't noticed any difference in usability or responsiveness in the newest kernel so far, but I also have not had the chance to do any extensive benchmarking yet....

AFAIK the 0xlab toolchain *should* produce a slightly more optimized kernel due to the depth of the toolchain optimizations there, but forgive me if I'm incorrect here.... my knowledge of optimizing for ARM is rudimentary at best... though I'm sure all your command line optimizations make a difference as well... ;)

Great job and thanks for staying persistent with getting HAVS working!

I bought you a beer about a week ago.... ;)

Sent from my Nexus One
[Nexus One Android Development] nurre:
been on a bit of a IR break because of the bluetooth / CM incompatibilities. Are they fixed now? So the -CM kernels work with bluetooth?

Also is the work pershoot has been doing to get a bit more charge out of the battery included?
[Nexus One Android Development] ardatdat:
Hi IR, I have been using your ROM for a long time, it is fast & stable.

Recently, I have flashed your newest ROM @ 20100913,

but my camera cannot function after this.

Do you get a version that has no 720p support? (AOSP Froyo 2.2). Thanks.
[Nexus One Android Development] Hirosakamoto:
Umm intersect...

You are using CM 6 RC3, Korean radio 5..... and your kernels right? and you got no problems? right?
[Nexus One Android Development] feelmoving:
some problem

i used the CFS HAVS-CM of 20100913_1XXX，the camera can work now，

but every time after i uesed opened my phone for 3 or 4 hours，it can not open by the Power button or trackball，only why is to put off the battery and start again，but the problem still there。

bad english ，sorry
[Nexus One Android Development] intersectRaven:
Unfortunately since I've rebased to cyan's source, I can no longer provide non-720p since it's too much work to revert all the commits for it. :(

Nope. I'm using Evil's Desire ROM. No problems so far except what I will mention below. :)

I haven't really found the source of the problem as to why the KGSL is crashing which is why there is no display response after being suspended for awhile. I can say though that if you turn off the WiFi when you anticipate that you won't be using the phone for a while the problems will lessen. :confused:
[Nexus One Android Development] Hirosakamoto:
Ah I see... I found the problem:)! I tried other room, after that everything worked. But I used the kernel from the room.

which kernel do u use urself? I wanna try the same rom and kernel like you do =D! Cuz the rom I use now are alittle slow... maybe it's just me. Hope you can post the link too^^!
[Nexus One Android Development] Pochemuchka1977:
Have the same problem with the latest kernel, and yes, indeed it happened while WiFi was on. But once I have seen the "Unable to drop ACPU vdd" message appeared just before the freeze (from the last_kmsg)
[Nexus One Android Development] intersectRaven:
Hmmm...on what frequency was that? Maybe the sensor was faulty on your N1 thus causing it to drop power too much on a specific frequency. :confused:
[Nexus One Android Development] houzuoguo:
:P hihi I'm still interested in.. how does the kernel tell itself, what voltage is suitable for feeding CPU :D could anyone please give a hint.. many thanks!
[Nexus One Android Development] intersectRaven:
There are sensors on the snapdragon core that AVS uses to tell whether it can decrease voltage. As long as those sensors give an OK signal, AVS will try to decrease by 25mV increments. If at a certain point it detects a problem in one of the sensors (I believe there are 3?), it raises voltage for all frequencies below the current one by 25mV and continues operation until the sensors OK again. In HAVS, the lower limit for each frequency together with the upper limit has been specified to prevent overshooting for known stable voltages. (see avs.c) :)
[Nexus One Android Development] intersectRaven:
Minor update! :D
[Nexus One Android Development] houzuoguo:
Hi IR :)

How's bluetooth working in latest release on CM? Has anyone reported it working..?
[Nexus One Android Development] intersectRaven:
Bluetooth should work with CM now with the -CM releases since I reverted the FM modules there. :)
[Nexus One Android Development] houzuoguo:
Many thanks :)

i'll try it now
[Nexus One Android Development] houzuoguo:
2.6.35.4_AVS-CM-950mV_CFS_20100915_0952

Just tried that kernel..

:D

it works fine, very fast, i've been using it for just few minutes so can't tell about battery life yet..

1. Wifi works perfectly with hidden ssid

2. Bluetooth no longer forces close, but unfortunately it still can't find my laptop.. Lenovo Y450-a

everything else is fine so far :)
[Nexus One Android Development] feelmoving:
same problem

2.6.35.4_AVS-CM-950mV_CFS_20100915_0952

everything fine，turn off the wifi and wait for 2 hours，then the KGSL happend，:confused:can not open unless put off the battery
[Nexus One Android Development] intersectRaven:
Odd. HAVS just isn't for you then. I'd recommend switching to SVS kernels. :(

*Oh, if you want you can send me a kmsg with the error. Maybe it will yield some clues.
[Nexus One Android Development] sabiwa:
I just flashed this kernel over my rom and my phone just doesnt boot anymore.

The bootanim just disappears or stays and even after 20 mins the phone doesnt come up.

When i connect the phone to adb logcat it shows a log but at the end it just disconnects.

Only the 3 finger salut helps then.

Running it on the Modaco r24 desire port
[Nexus One Android Development] intersectRaven:
HAVS doesn't work for your phone then. :(
[Nexus One Android Development] sabiwa:
I used the previous Havs kernel of yours again and it works. The one from yesterday.

Since i use Pauls desire rom r24 i am loving your kernels :)

flashed 2.6.35.4_AVS-950mV_CFS_20100914_1715 back now and it works like a charm but only the 20100915_0926 one doesnt work. Sorry that i wasnt clear enough on my report before
[Nexus One Android Development] intersectRaven:
Hmmm...now that you mention that you're running Paul's Desire, I think I know what your problem is. (just a hunch) Try to delete the bcm.ko file from /system/lib/modules before flashing my kernel and then pushing it manually through ADB. I didn't revert the WiFi driver with the latest release so it may be causing a reboot when it tries to initialize itself. :confused:
[Nexus One Android Development] sabiwa:
I think i had the same effect now. I wiped the whole phone. Installed Pauls latest and flashed yours immediatly after. It works now again.

I must say that i had a struggle with my Renault Car system with the older kernel which caused a restart of the phone after connecting. After that it connected perfectly and without any fault. I will try that later today.
[Nexus One Android Development] Pochemuchka1977:
Same here, but in my case last_kmsg was not even created. The kernel from 0914 I got:

[ 1515.750518] AVS setting V to 950 mV @245 MHz

[ 1515.751281] PM: suspend of devices complete after 10.396 msecs

[ 1515.752624] power_suspend_late return 0

[ 1515.752990] PM: late suspend of devices complete after 1.067 msecs

[ 1515.753051] wakeup wake lock: i2c

[ 1516.750396] msm_i2c msm_i2c.0: Transaction timed out

[ 1516.750762] msm_i2c msm_i2c.0: Error during data xfer (-110)

[ 1516.751800] PM: early resume of devices complete after 997.885 msecs

[ 1516.753662] tps65023 0-0048: Write for reg 0x5 failed

[ 1516.754089] acpuclock: Unable to drop ACPU vdd.

[ 1516.775390] PM: resume of devices complete after 22.649 msecs

[ 1516.776641] Restarting tasks ... done.

[ 1516.807556] suspend: exit suspend, ret = 0 (2010-09-12 20:02:23.532466348 UTC)

[ 1516.808166] active wake lock PowerManagerService

[ 1516.808471] suspend: abort suspend
[Nexus One Android Development] intersectRaven:
Hmmm...thanks for that...it seems I'll be putting a debug there in the second next release...(I'm currently compiling a release right now so can't put it in...) :p
[Nexus One Android Development] Pochemuchka1977:
Ok, when you put the debug, I will test it and provide you with needed log files. (I hope that last_kmsg will be created this time, otherwise there is no way to get the debug info). Currently the most stable kernel I am running with is wildmonks SVS 950 from 08/27.
[Nexus One Android Development] intersectRaven:
Minor or major update! (you decide) :p
[Nexus One Android Development] sabiwa:
Anything special you want me to test on pauls rom ?
[Nexus One Android Development] intersectRaven:
Not really. I think he tested my kernel quite a lot before he decided to use it. The only problem I can think of is the HAVS causing problems. :)
[Nexus One Android Development] sabiwa:
Ok up till now it looks good very very good
[Nexus One Android Development] Robdyx:
2.6.35.4_AVS-CM-950mV_CFS_20100915_2029 tested on CM6.0.0.0-N1 stable, I've noticed very low (unusable) Wifi signal in a place where pershoot and wildmonks' kernels have very good signal.
[Nexus One Android Development] Pochemuchka1977:
2.6.35.4_AVS-CM-950mV_CFS_20100915_2029 tested with CM6.

The phone freezes after 1.5 hour of being idle, apparently the last_kmsg was not created so i am unable to provide the latest log :-(
[Nexus One Android Development] angel-78:
I haven't used a modded kernal ina few months since I stopped using my G1. I am using LeoFroYo 2.0.1 beta3 and decided to give your 20100915_20XX cfs a try. It seems to work fine except that I am having trouble with the camera, Am I able to just replace my camera app to something else without changing any other part of the rom in order to get the camera working? Thanks in advance.

Manny
[Nexus One Android Development] YoMarK:
What can we expect with the NEON optimizations??
[Nexus One Android Development] houzuoguo:
Have been using the latest release for 1 day, everything works smoothly, thanks for your great kernel IR :)
[Nexus One Android Development] Nedlinin:
I have this same issue. Phone refuses to turn back on after about an hour of being idle. Have to pull the battery and turn it back on.
[Nexus One Android Development] houzuoguo:
last night.. in about 8 hours, battery dropped from 96%to 74%...

well :) now I understand, to get AVS working on all devices take a lot of effort :)
[Nexus One Android Development] intersectRaven:
:p

As for the errors, I'm currently tracing it to the i2c bus. Odd... :confused:

***Posted a debug kernel for those who want to report hangs.***
[Nexus One Android Development] vnbuddy2002:
+1 .. Same for me as well
[Nexus One Android Development] mezmer1ze:
I use latest kernel without any issues, great battery life...

Although I must have a good CPU that handles anything it gets :D I used to use 800 mV kernels before without any issues...
[Nexus One Android Development] intersectRaven:
Yeah I modified something with the test kernel and forgot to roll it back which *MAY* fix the issues. :p
[Nexus One Android Development] Pochemuchka1977:
I have tested the DEBUG kernel and got the phone freeze with last_kmsg file. The file is containing a garbage, but readable. I have a zipped log attached it to this message.

Hope you will manage to understand the source of the problem

Thanks
[Nexus One Android Development] mezmer1ze:
Ok one thing I noticed with latest stable kernel - the signal is very unstable for me when travelling or changing phone location by other means. I have more network DCs than before.
[Nexus One Android Development] intersectRaven:
Interesting...I have a hunch as to what's causing it so I'll be releasing another test kernel soon. ;)
[Nexus One Android Development] intersectRaven:
DEBUG kernel released again. ;)
[Nexus One Android Development] wbknox:
i hope this fix cm_avs ?
[Nexus One Android Development] intersectRaven:
I hope so too. :)
[Nexus One Android Development] wbknox:
do u have plans to do a 2.6.36 kernel when u fix avs?
[Nexus One Android Development] Pochemuchka1977:
Got a freeze with the latest debug kernel .... somehow the last_kmsg was not created. Will try again tonight, hopefully the log will be created
[Nexus One Android Development] intersectRaven:
Odd. For me it marked a significantly increased stability since I now had my N1 up overnight without crashing. Maybe something else is wrong with your phone or AVS just doesn't work for you?:confused:
[Nexus One Android Development] Pochemuchka1977:
Well, I had another freeze tonight and again no last_kmsg was created

I really don't know whether it's AVS or something else. The only way to check it is to run SVS based kernel with all your commits and see ...

All I can tell is that wildmonks SVS kernel from 0827 which is based on your work, works flawlessly.
[Nexus One Android Development] intersectRaven:
I posted another DEBUG kernel since the last one froze too frequently after a reboot. :(
[Nexus One Android Development] jlevy73:
http://www.kernel.org/

It's now up to .36rc4 :)
[Nexus One Android Development] Pochemuchka1977:
Another freeze with latest 2.6.35.4_AVS-DEBUG-950mV_CFS_20100919_0854, battery pulled, even date was scrumbled to 1980 ....

last_kmsg is attached.
[Nexus One Android Development] intersectRaven:
No choice then. I'll increase voltages abit. :(

*Uploaded a new DEBUG kernel. This changes the voltage bounds to just 25mV.
[Nexus One Android Development] Pochemuchka1977:
Might be you can change the algorithm of decreasing the voltage not by decreasing the constant value of .25mV, but smaller values when you are getting close to minimum limit ... This way the voltage can be more precise near the minimum values ...
[Nexus One Android Development] intersectRaven:
The regulator cannot handle adjustments below 25mV increments so no. :)
[Nexus One Android Development] Pochemuchka1977:
Another hangup on latest 2.6.35.4_AVS-DEBUG-950mV_CFS_20100919_1032 (this was pretty fast one :-) )

last_kmsg attached

P.S. I can't get why SVS 950mV kernel is running without hangups while HAVS 950mV kernel freezes the device consistently
[Nexus One Android Development] intersectRaven:
Posted my last debug kernel since I've ran out of ideas. :p
[Nexus One Android Development] MicroMod777:
I'm using your 1st 9/19 Debug Kernel and its working perfect. Want to use for my next update. Should I use instead the newest 9/19 now?
[Nexus One Android Development] intersectRaven:
You decide. I'm a perfectionist so I don't recommend anything. :p
[Nexus One Android Development] MicroMod777:
What changed then on the 2nd 9/19 kernel?
[Nexus One Android Development] Pochemuchka1977:
Well, this one did not work either :-(. With WiFi on the freeze was pretty fast. As always, last_kmsg shows the same error.