yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] intersectRaven:
HAVS (I think he reverted to SVS for the time being) and OC. :)
[Nexus One Android Development] Vlad83:
Raven, since wildmonks has been gone for almost a month do you know if ivan still overclocks your kernels? Love your kernels but at 1113 :)
[Nexus One Android Development] mik101:
That was my issue, I guess it wasn't really a freeze. I didn't have time to screw with it at the time so I just 3-finger saluted it and went back to business.

x2 for the previous post, except 1075mhz for me -- my CPU must be a little b**** haha.
[Nexus One Android Development] scote:
Just come to this thread looking for improved battery life.

My ROM is CM6

I know the .5 kernels are broken as posted here, I tried all the below and they were very unstable, random reboots, sd card disappearing, hangs and freezes

2.6.35.4_AVS-950mV_BFS_20100921_0847.zip

2.6.35.5_AVS-950mV_BFS_20100921_1507.zip

2.6.35.5_AVS-CM-950mV_BFS_20100921_1513.zip

Eventually settled on

2.6.35.4_AVS-CM-950mV_CFS_20100915_0952.zip

No problems with this one so far and battery life is looking good initially at least, so this got me wondering why? different camera and scheduler. Are kernels with BFS scheduler known to be problematic? I would have thought that BFS would be a good light weight low latency scheduler ideal for phones, not so good for servers running lots of threads though.

BTW thanks for the work!
[Nexus One Android Development] AdamG:
Question to iR, could you add your configs to arch/arm/configs, it would make it easier than extracting them.
[Nexus One Android Development] FabiANUS:
AVS

I have a big problem with all the AVS Kernels.

They are very unstable (rebooting every 2minutes), but very responsive and snappy.

So I would love to see AVS working on my nexus.

I'm not really an expert in all these stuff, so I'm asking you guys if you can see what the problem is.

Here are the last logs from my last_kmsg:

"[ 16.436584] msm72k_udc: ept #8 in max:512 head:ffa02440 bit:24

[ 16.436706] msm72k_udc: ept #9 in max:512 head:ffa024c0 bit:25

[ 16.436920] msm72k_udc: ept #10 in max:512 head:ffa02540 bit:26

[ 16.437042] msm72k_udc: ept #11 in max:512 head:ffa025c0 bit:27

[ 16.437255] msm72k_udc: ept #12 in max:512 head:ffa02640 bit:28

[ 16.437377] msm72k_udc: ept #13 in max:512 head:ffa026c0 bit:29

[ 16.437591] msm72k_udc: ept #14 in max:512 head:ffa02740 bit:30

[ 16.437713] msm72k_udc: ept #15 in max:512 head:ffa027c0 bit:31

[ 16.437927] usb: notify offline

[ 16.438049] msm_hsusb: enable pullup

[ 16.441406] msm72k_udc: msm72k_udc: suspend

[ 16.458770] batt: charging SLOW

[ 16.548553] msm72k_udc: msm72k_udc: reset

[ 16.550842] msm72k_udc: msm72k_udc: portchange USB_SPEED_HIGH

[ 16.710174] msm72k_udc: msm72k_udc: reset

[ 16.712463] msm72k_udc: msm72k_udc: portchange USB_SPEED_HIGH

[ 16.914031] ### notify_usb_connected(1) ###

[ 16.914154] android_usb gadget: high speed config #1: android

[ 16.914367] msm72k_udc: ept #4 in max:512 head:ffa02240 bit:20

[ 16.914489] msm72k_udc: ept #3 out max:512 head:ffa02180 bit:3

[ 16.914733] msm72k_udc: ept #3 in max:512 head:ffa021c0 bit:19

[ 16.914855] msm72k_udc: ept #2 out max:512 head:ffa02100 bit:2

[ 62.704132] batt: 100%, 4153 mV, 184 mA (185 avg), 30.8 C, 1425 mAh

[ 67.283386] save exit: isCheckpointed 1

[ 73.532989] FAT: invalid media value (0x00)

[ 73.533111] VFS: Can't find a valid FAT filesystem on dev mmcblk0.

[ 87.769287] save exit: isCheckpointed 1

[ 98.474151] save exit: isCheckpointed 1

[ 98.582183] Restarting system.

[ 98.582397]

[ 98.582519] Restarting Linux version 2.6.34-cyanogenmod (shade@toxygene) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Mon Jun 28 20:07:00 EDT 2010

[ 98.582519]

No errors detected"

I attached the whole last kmsg file if it's necessary.

Thanx for your help,

Fabian
[Nexus One Android Development] intersectRaven:
Uhm...that's not my kernel...it's cyanogen's... :p

"Restarting Linux version 2.6.34-cyanogenmod (shade@toxygene) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Mon Jun 28 20:07:00 EDT 2010"
[Nexus One Android Development] alkaline810:
My issue with 20100922_21XX is that I can only turn on Bluetooth once. If I disable it, I have problems re-enabling it until I reboot.

Other than that, works great!
[Nexus One Android Development] intersectRaven:
That's odd...is that CM or Desire ROM? Are you using the proper kernel? :confused:
[Nexus One Android Development] FabiANUS:
So does that mean, that I have "no last kmsg" as you wrote in your first post?

Because I'm shure I flashed your kernels!

-> So do I have a cpu that does not like AVS, or is there still a chance of a solution?

Thx so far for your work and support!
[Nexus One Android Development] intersectRaven:
The kernel you're running isn't mine. It's cyanogen's so it's not AVS that's causing your problems. If it was mine, the restart message would have indicated -intersectR rather than -cyanogenmod. :)
[Nexus One Android Development] nurre:
I can confirm bluetooth issues with CM.
[Nexus One Android Development] alkaline810:
I guess I was using the wrong kernel. I changed to the CM one and it works now. Whoops...
[Nexus One Android Development] redstar3894:
IR,

Don't know if you saw my post about your latest "semi-test" (2010926_0813) kernel before xda had a brain-fart :p

Basically what happened was on the first boot, android.acore fc'd almost immediately as surfaceflinger started up, but then after a few seconds, everything was running fine....at least as far as I was able to tell...

So after I rebooted it once, it froze a second or two after surfaceflinger started, I had to do the three-finger salute to get it restarted and it repeated this behavior after several reboots....

At the time I was unable to get a logcat since I wasn't at home, I'll see if I have more time to test this tonight and hopefully I'll be able to get you some info here...

I'm running evil's desire ROM v1.20 and I was coming from your previous kernel on 9/22 (CFS), I wiped both cache and dalvik before flashing the "test kernel"...

I don't think my phone has any problems with AVS, since I've been running your kernels since I first got my nexus back in May and they've always been rock-solid, I've also compiled my own kernels a couple times from your source and there have never been any problems.... :D

Also, I think eViL had posted right before my post that he attempted to compile from your source last night and his phone wouldn't even boot...:eek:

So, just wanted to restate what happened there since those posts were lost and all...I'll see if I have some time later to test that kernel...
[Nexus One Android Development] intersectRaven:
That's odd. This version is the most rock stable for me. The only significant change was the implementation of the TPS regulator stack code from CodeAurora's repository to make sure AVS can set voltages quick enough. :confused:
[Nexus One Android Development] redstar3894:
Yeah, I saw that when I was looking over the recent commits on your github, so I was a little confused too, especially since that was the only recent major change...

The part that was really strange (this may have been user error on my part) :o is that the first time it booted up, there were no problems, except for the acore fc, and it only froze after a reboot....but like I said, that may have been something I did...not sure...:confused:

I'll have time in another hour or so to test that kernel again, and I'll see if I can get you a logcat as well...

I wasn't sure about reporting this, and I don't claim to be an expert here, but like I said, I've been using your kernels for a while here, and this is the first I've had problems with... I'm pretty sure it wasn't me, but that could be a possibility... :o

And like I said, eViL had posted something just before my post stating a similar problem...so idk if he was able to resolve that or not...
[Nexus One Android Development] redstar3894:
Yeah... false alarm here.... :o

I finally had some time to reflash and test this kernel.... I wiped both cache and dalvik twice and had the logcat all set up and....it booted right up with no problems :eek:.... even after several reboots, everything is fine... :o

Sorry about that, I feel like an idiot now... :(

It must have just been something stupid I did when flashing it the previous time... I agree with IR in that this kernel seems to be even more stable than the previous iteration....

Here you go IR, have a beer on me :D

You've done outstanding work with these kernels, keep it up! ;)
[Nexus One Android Development] RellikZephyr:
latest test kernel, 2010926_0813, still unstable for me. get the wont wake issue

dont know how to create last kmsg so cant help there

just letting u know. i guess im prob an unlucky one, that it doesnt like my phone

i really want to use ur kernel, cause i see most others are based of urs, so why not use original

hope a fix comes

RellikZephyr
[Nexus One Android Development] intersectRaven:
Try the latest in my MediaFire folder. I release periodically without announcing here (only in my Twitter feed). :)
[Nexus One Android Development] eViL D::
No, my phone booted, but it would not come out of sleep/standby.
[Nexus One Android Development] RellikZephyr:
Damn it, between you and cyanogen,I might have to sign up to twitter

OK will check your mediafire after work

Thanks for the great work IR

Rellikzephyr
[Nexus One Android Development] MicroMod777:
IR, wanna update with a better kernel that would give greater 3G signal and come in and out of wifi more smoothly for my Desire ROM. What u recommend?
[Nexus One Android Development] Pochemuchka1977:
The 2.6.35.6_AVS-950mV_CFS_20100929_0806.zip has a issue with bluetooth and CM 6 stable
[Nexus One Android Development] jim13524:
2100929 will not wake the screen for me
[Nexus One Android Development] intersectRaven:
Update released! :)
[Nexus One Android Development] sabiwa:
This new kernel doesnt seem to be able to connect to wifi.
[Nexus One Android Development] Cpt.Curry:
does the new kernel work with enoms new rom.
[Nexus One Android Development] intersectRaven:
It should but I don't know which base that is made from so you should test if camera is functional using both the non-CM and -CM builds. :)
[Nexus One Android Development] mescieux:
2.6.35.6_AVS-CM-950mV_CFS_20101001_2200 booted and worked fine for a while but still gave me a black screen and not waking up on CM6 stable.
[Nexus One Android Development] houzuoguo:
thanks a lot for your work IR :)

I'm running latest Enomther at moment and will your kernel on it soon..
[Nexus One Android Development] intersectRaven:
Hmmm...do you have a last_kmsg? I think I have an idea though of what you're experiencing and I may release a "fix" for that soon. :)
[Nexus One Android Development] houzuoguo:
Haha... shall I wait for the fix or.. continue installing?

anyway I'm installing your kernel now, I'll get back to you kernel messages if I encounter any problem
[Nexus One Android Development] intersectRaven:
If you can't wait, I think setting your minimum frequency to above 384Mhz using SetCPU will stabilize it. :)
[Nexus One Android Development] houzuoguo:
yah now I have encountered the problem.

I'll get you the latest kernel message..

sorry... why there isn't last_kmsg file in my /proc....
[Nexus One Android Development] sassafras_:
Since when are your kernels overclocked? Not that I'm complaining. :)

sassafras
[Nexus One Android Development] intersectRaven:
Since I rebased from Cyan's kernel. I don't know what effect it has though since the avs files don't support the voltages in the enhanced table but I think it falls back to SVS automatically. I still don't endorse it though. Use it at your own risk and I won't be maintaining AVS for it as well. :)
[Nexus One Android Development] sassafras_:
Actually I have no need for overclocking. When I've built my own kernels they never seemed to be quite as stable as the stock one, even with overclocking disabled. I like yours because the HAVS gives me much better battery life than the stock kernel. Should I stick with one of the few week old ones or use the latest if I'm going to keep it at 1 GHz anyway? The 9/22 seemed plenty stable enough for me.

Oh, BTW... Thanks for all your hard work. :)

sassafras
[Nexus One Android Development] RellikZephyr:
Over clocked? Aww another reason I liked your kernels was the stock clock,I have no desire for overclock

Rellikzephyr
[Nexus One Android Development] intersectRaven:
You can always set the limit to regular clocks so it should be fine. Anyways, if you don't use SetCPU to change it, you'll be stuck at userspace governor and 806Mhz. (well, at least using Evil's ROM you will be...) :p
[Nexus One Android Development] RellikZephyr:
I do have SetCpu, and set it for 998. It wont stop me from using your kernel, i seem to have stability finally. Yours is the only kernel I have found that actually provides better battery life over cyanogens kernel

Rellikzephyr
[Nexus One Android Development] ~~Tito~~:
I am getting really low scores in quadrant, like under 1200 :O. Running Pauls v24 Desire Sense. With your CFS Kernal 10/02/10.

It is however really smooth, and snappy! Just confused about the low scores.
[Nexus One Android Development] intersectRaven:
Don't rely on those benchmarking tools. As cyanogen stated (if memory serves me correctly) it's easy to fool those tools to give out a higher rating. You should rely on your own usage benchmark rather than synthetic benchmarks. Anyways, I haven't applied other optimization techniques in the compiler so maybe those will make a difference once applied. I was too focused on stabilizing AVS you see. :D
[Nexus One Android Development] ~~Tito~~:
NICE, it is pretty stable man! Your older kernals where jittery, now its pretty awesome!! :eek:
[Nexus One Android Development] houzuoguo:
so far so good :) thanks for your work
[Nexus One Android Development] Pochemuchka1977:
Wow, this is the first HAVS kernel that runs stable (so far) on my device even when the phone was idle.

Thanks you !!!
[Nexus One Android Development] houzuoguo:
IR You're awesome :D

So far so stable, and so power saving!!

Great!!
[Nexus One Android Development] intersectRaven:
It does increase the level of stability greatly right? I'm still not satisfied though since there's still a few freezes every now and then. :D
[Nexus One Android Development] ~~Tito~~:
Yup. :). Just needs to be tweaked a bit more for that extra little snap that will make it really amazing :).
[Nexus One Android Development] sabiwa:
Is any of you able to use wifi with the new 10-02 kernel. When I want to enable wifi it gives me the message "Error" and nothing else in the wifi.

I am using Modaco Desire r24 and didnt had this problem before with any of the IR kernels.
[Nexus One Android Development] houzuoguo:
I had that problem few times, please try using Cache Cleaner (available on Market as freeware) to clean cache and try to enable wifi. It worked for me few times.

Also when you flash a new kernel it's good to disable wifi before flashing...
[Nexus One Android Development] houzuoguo:
Just a little problem :)

(After installed the latest 1128 kernel)

Telsa LED doesn't work

Camera doesn't work

(Enomther latest )
[Nexus One Android Development] sabiwa:
Didnt helped for me going back to older kernel Long Life Nandroid
[Nexus One Android Development] intersectRaven:
Have you tried both the non-CM and -CM for the camera? As for the LED, I have no idea what that is. :p
[Nexus One Android Development] mezmer1ze:
The .6 CM CFS kernels don't seem as snappy for me as .4, the movement in drawer or on desktop is a little bit choppy.

Battery life seems to be worse than with kernels contained in latest CM nigtlies which is strange :-(
[Nexus One Android Development] yuripave:
intersectRaven can you please add Unicode support when mounting cifs share? this is the only reason I am still using wildmonks's kernel.

Thanks in advance.
[Nexus One Android Development] intersectRaven:
How do you enable that? I don't see any Unicode option in CIFS' menuconfig. Is it in the Native Language section? :confused:
[Nexus One Android Development] yuripave:
I am not familiar with linux kernel, but when I was discussing with wildmonks, I mentioned when I mount cifs with iocharset=utf8 option, the error says nls_uft8.ko is missing before he implemented it.

But when I use your latest kernel, I insmod your included cifs.ko, and able to mount without iocharset=utf8 option, but with it the errors says a shared library is missing.

Hope this information help.

edited: a search on xda with 'cifs utf8' leads me to 2 posts on desire development that might help

showthread.php?t=754793

showthread.php?t=751296
[Nexus One Android Development] intersectRaven:
I'll enable UTF8 in the next release. I also made a small change to increase stability of AVS. :)
[Nexus One Android Development] mescieux:
Even more stability! :eek: Your newest CM CFS has been working great for a whole day with no wake issues. Thanks for your great work IR!
[Nexus One Android Development] intersectRaven:
There are still instances I've experienced wherein the Adreno panics. Not sure if it was caused by the low voltages but I just had to be sure so I increased the delay before allowing AVS to tamper with anything. :)

*Will be releasing in a few minutes. Compiling CFS-CM now. :)
[Nexus One Android Development] zyonee:
Tried your last two releases and they seem to work just great! I'm VERY thankful that the kernel image doesn't reach (or doesn't seem to reach) 0x200000 in size, as my NAND has a bad block there in the boot partition. Finally, I can manage without flashing the boot.img to my recovery partition in order to be able to reboot my phone.

Keep them small, and thanks a lot for your hard work!
[Nexus One Android Development] xzr3b0rnzx:
I feel that 1003 cfs kernel was laggier than 1001.. I am using evils 1.20
[Nexus One Android Development] intersectRaven:
Hmmm...the delay I increased is supposed to delay frequency changes just enough to get AVS stable. If you're experiencing more lag, it may be that there's an app that's causing too much frequency fluctuation in the background which making the delay more apparent. Try using the interactive governor to keep the frequency at a higher level until it's not needed. :)
[Nexus One Android Development] pzumk:
Does this kernel actually supports 1113MHz? setCPU allows me to set it that high but I think you always said you wont overclock

It also seems to be laggy at 1036MHz or higher, thats why i set it to 998 now
[Nexus One Android Development] intersectRaven:
I don't really know what AVS will do while at those levels. I didn't modify AVS to support OC so maybe it will work and maybe it won't. Use it at your own risk. :)
[Nexus One Android Development] Untouchab1e:
Your latest kernels makes my phone crawl. A quadrant score of less than 800.. Modaco's Desire ROM. Other kernels run fine.. Any idea whats wrong?
[Nexus One Android Development] pzumk:
Haha okay, I'll stick with 998 then ;)

are there no other kernel devs on xda now? wildmonks disappeared and only you are left O_o
[Nexus One Android Development] mescieux:
Is interactive governor stable with AVS? I remember reading that we should use ondemand with AVS. I tried using interactive for a while and got random hang-ups where the phone would get unresponsive for a bit, especially when playing solitaire. Though it might just be a problem with solitaire since I think I had similar problems using interactive with CM's stock kernel.
[Nexus One Android Development] intersectRaven:
You could try tweaking the advanced values for ondemand using SetCPU instead. I forgot that interactive has a bug which causes weirdness every now and then. :)
[Nexus One Android Development] RellikZephyr:
Damn, just got a no wake problem with 20101003-1336

Was fine all day yesterday, but not today I guess.

Learn me how last msg thingy via pm, so I can help

Rellikzephyr
[Nexus One Android Development] Untouchab1e:
Ok, so I switched over to a rooted stock FRG83 ROM and performance is awesome, however, bluetooth doesnt turn on and the camera doesnt work. The camera doesnt work because its not the 720P mod, however, Im unsure where to get it? Ive seen the hack posted here but it seems to be for CM only?

I have no idea how to get bluetooth working though? Anyone care to help?
[Nexus One Android Development] intersectRaven:
If you use the -CM kernels, bluetooth should work. As for the camera, you'll have to switch to a ROM which has 720p support as far as I know. :)
[Nexus One Android Development] clustered:
Same thing happen to me... :( running 20101003_13XX: CFS HAVS-CM
[Nexus One Android Development] Pochemuchka1977:
Same here, last_kmsg attached

For any of you who don't know how to get last_kmsg.

- If you use adb, type the command "adb pull /proc/last_kmsg c:\last_kmsg" without quotes on your PC when the phone is connected. The file last_kmsg will be located in your c:\ directory in case it exists on the phone.

- If you use file manager, navigate to /proc directory on your phone and copy the last_kmsg file to your SD card. This way you can copy it later to the PC
[Nexus One Android Development] intersectRaven:
After reanalyzing the last_kmsgs I've received, I may have found the TRUE problemm. Still testing it though so you'll have to wait for > 24 hours if this proves true. :p
[Nexus One Android Development] houzuoguo:
good to hear that you've found true problem again :) hihi

by the way last night i flashed your lastest kernel on latest enomther, both cm and non-cm, seems like the camera on enomther doesn't work with your kernel...
[Nexus One Android Development] intersectRaven:
I've also started to doubt how TRUE the TRUE problem is since I've found so many TRUE problems before. :p

Too bad that it doesn't work on enom's. I don't know why that is though since I only know of two bases. Either cyan's or desire's. (maybe enom doesn't support 720p?) :confused:
[Nexus One Android Development] houzuoguo:
You're right.... I just read this on Enomther's rom page:

"--- Optional 720p camera support w/HTCCamera"

I haven't used video camera since installed the rom on last 29th so didn't realize that the stock camera doesn't support 720p...

Well actually I didn't really want to use Enomther's rom because CM is more powerful, but I'm kind of.. addictive to flash new roms, so I flashed Enomther rom :)

I love your kernels, I remember when CM5.0.8 was released, your AVS kernel had 800mV version, and I flashed CM508 together with your 800mV AVS kernel, battery life was great, best result was that battery drained only 1% every 2 and half hours.
[Nexus One Android Development] RellikZephyr:
Got no wake issue with 20101004-0839, hope you find the issue. Cause I have given up on finding an alternative kernel until yours is fixed. None of the others perform like yours, only this annoying little hard to kill no wake bug

Keep up the great work

Rellikzephyr
[Nexus One Android Development] houzuoguo:
hi hi~

I've been trying to find where is code for AVS these days

finally I find it:

http://github.com/intersectRaven/ir-kernel/blob/ir-kernel-2.6.35/arch/arm/mach-msm/avs.c

eh.. I'm just wondering, does Nexus One CPU have temperature sensor..?
[Nexus One Android Development] intersectRaven:
The snapdragon has a "sort of" temperature sensor. It's the one being accessed by GET_TEMPR in avs.c. I believe it returns a "temperature region" (that is, the temperature lies in a specific range which is defined as a region) on where the current temperature lies so it's not exact. That's not AVS only basis though. :)
[Nexus One Android Development] intersectRaven:
If my theory about how to TRULY solve the wakeup problem is correct, I *MAY* release an 800mV version. I just prefer not doing so since, in my personal use, I found an area (geographic location) during my travel to and from work where there is a noticeable effect on signal reception while using a lower voltage. :)