yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] MicroMod777:
Did you wipe your cache and dalvik-cache first before flashing? If you didn't that will cause wifi freeze also.
[Nexus One Android Development] 2000impreza:
I'm running the Cyanogen 5.0.5.3 rom. I've reverted to running a non-avs rom for now. The CPU in my nexus one can handle a non avs kernel running at 925mv without issues at all. I'm still hoping for a more stable avs kernel. So far I've found the most stable AVS kernel to be the 1000mv AVS posted by raven yesterday (April 10).
[Nexus One Android Development] LunatikBunnie:
Maybe the bootloader might be one of the reason of AVS instability? Can those who has 850uv working report with their BOOTLOADER used?
[Nexus One Android Development] intersectRaven:
No need to setup a failsafe on SetCPU since AVS already has a built-in failsafe. You can still customize the speed set by SetCPU if you wish.

Yes it would but based on the previous release of both, not many will be running stable on it. Only a few lucky ones such as myself (800 mV) can run it without any issues at all. :)

Go to my MediaFire folder and sort it by date. You'll find the link on my first post. :)

It shouldn't really impact performance all that much. You can't really get it user configurable since AVS is loaded before the kernel can even load the filesystem so you really have no choice there. :)
[Nexus One Android Development] dandyd449:
I may be a retard but how do you go about checking the:

"enabled AVS debugging display of voltage being set to processor"

Thanks
[Nexus One Android Development] intersectRaven:
Go to adb and issue a cat /proc/kmsg and you should see it in realtime. :)
[Nexus One Android Development] intersectRaven:
I could run 800 without any problems so I guess I'm included in the people you're asking. My HBOOT version is 0.33.0012. :)
[Nexus One Android Development] lore2486:
full command is

adb shell cat /proc/kmsg
[Nexus One Android Development] rjhay22:
Hmm if you said you have successfully ran em all, and if you're bored :P I think you should give the 850mV a try again and see if it still bootloops...

Because I had the same problem this morning with Enom's ROM, and could not replicate it on Cyan's 5.0.6. Now I'm back to Enom's ROM, rebooted it 5-6 times already and everything is running smoothly so far. A hiccup maybe? or a hit and miss situation? hehe.
[Nexus One Android Development] lore2486:
just tried the cat command and saw that my voltage kept fluctuating between 850 and 1225 on sleep, any idea why? any one else saw this?
[Nexus One Android Development] dandyd449:
My HBOOT is also 0.33.0012, im ready to try lower voltage with this kernel.
[Nexus One Android Development] intersectRaven:
Is it on the same frequency? (You should see the @*insert number here*).

If its not, then something is using your CPU while your display is suspended. If you want to see a constant speed and voltage, set your power governor to powersave when you're not using it to keep it at 245 Mhz (@2 on the AVS debugging message). :)
[Nexus One Android Development] intersectRaven:
Good luck! :p
[Nexus One Android Development] lore2486:
goes between 2 and 4
[Nexus One Android Development] intersectRaven:
Those should be 245 Mhz and 384 Mhz if I remember correctly. So your CPU goes to 1225 mV at 384 and 850 at 245 mV? You may be better off using the non-AVS since you're ending up consuming more power at 384 Mhz with AVS than non-AVS. :(

*You could also use SetCPU to regulate your CPU speed at idle. :)
[Nexus One Android Development] Pochemuchka1977:
I have this fluctuation too while my device is in suspend mode, but the jumping is from @2 to @20 mostly

<6>[ 2704.284362] AVS setting V to 1250 mV @20

<6>[ 2704.554656] AVS setting V to 1225 mV @4

<6>[ 2704.557434] AVS setting V to 975 mV @2

<6>[ 2707.057403] AVS setting V to 950 mV @2

<6>[ 2709.289276] AVS setting V to 1250 mV @20

<6>[ 2709.439483] AVS setting V to 950 mV @2

<6>[ 2711.784606] AVS setting V to 925 mV @2

<6>[ 2713.813690] AVS setting V to 1250 mV @20

<6>[ 2713.923889] AVS setting V to 925 mV @2

<6>[ 2714.304168] AVS setting V to 1250 mV @20

<6>[ 2714.384368] AVS setting V to 925 mV @2

<6>[ 2720.320068] AVS setting V to 1250 mV @20

<6>[ 2720.360351] AVS setting V to 1225 mV @4

<6>[ 2720.360687] batt: 82%, 4070 mV, 317 mA (258 avg), 32.0 C, 1112 mAh

<6>[ 2720.390075] AVS setting V to 1250 mV @20

<6>[ 2720.490295] AVS setting V to 925 mV @2

<6>[ 2725.334930] AVS setting V to 1250 mV @20

<6>[ 2725.375030] AVS setting V to 925 mV @2

<6>[ 2743.552764] AVS setting V to 1250 mV @20

<6>[ 2743.823089] AVS setting V to 925 mV @2

<6>[ 2764.042663] AVS setting V to 1250 mV @20

<6>[ 2764.082794] AVS setting V to 1225 mV @4

<6>[ 2764.103088] AVS setting V to 925 mV @2

<6>[ 2770.398925] AVS setting V to 1250 mV @20

<6>[ 2770.438964] AVS setting V to 925 mV @2

<6>[ 2775.413818] AVS setting V to 1275 mV @20

<6>[ 2775.446899] batt: 82%, 4070 mV, 316 mA (289 avg), 32.1 C, 1116 mAh

<6>[ 2775.453948] AVS setting V to 1175 mV @4

<6>[ 2775.544006] AVS setting V to 925 mV @2

<6>[ 2803.611328] AVS setting V to 1250 mV @20

<6>[ 2803.851593] AVS setting V to 925 mV @2

<6>[ 2808.726257] AVS setting V to 1250 mV @20

<6>[ 2808.826416] AVS setting V to 925 mV @2

<6>[ 2813.260711] AVS setting V to 1275 mV @20

<6>[ 2813.300811] AVS setting V to 1225 mV @6

<6>[ 2813.321105] AVS setting V to 925 mV @2

<6>[ 2820.487854] AVS setting V to 1250 mV @20

<6>[ 2820.507873] AVS setting V to 1225 mV @4

<6>[ 2820.547851] AVS setting V to 925 mV @2

<6>[ 2825.512725] AVS setting V to 1275 mV @20

<6>[ 2825.532989] AVS setting V to 1250 mV @11

<6>[ 2825.552978] AVS setting V to 925 mV @2

<6>[ 2825.558715] batt: 82%, 4074 mV, 317 mA (293 avg), 32.1 C, 1121 mAh

<6>[ 2863.669952] AVS setting V to 1275 mV @20

<6>[ 2863.770080] AVS setting V to 1225 mV @9

<6>[ 2863.790313] AVS setting V to 925 mV @2

<6>[ 2864.490661] AVS setting V to 1275 mV @20

<6>[ 2864.530792] AVS setting V to 1175 mV @4

<6>[ 2864.551086] AVS setting V to 925 mV @2

<6>[ 2875.601531] AVS setting V to 1275 mV @20

<6>[ 2875.621826] AVS setting V to 1225 mV @6

<6>[ 2875.641876] AVS setting V to 925 mV @2

<6>[ 2875.669830] batt: 82%, 4074 mV, 317 mA (316 avg), 32.1 C, 1126 mAh

The device is connected to PC - might it be the reason for all the jumpings ?

And what do these debug lines mean:

<3>[ 2998.156036] msm_pm_wait_state(2, 0, 0, 0) failed 11001

<6>[ 2998.156036] msm_sleep(): msm_pm_wait_state failed, 11001
[Nexus One Android Development] intersectRaven:
The only thing I can think of is that an application is running in the background which is causing your CPU to switch to 998 Mhz every now and then. :)
[Nexus One Android Development] Pochemuchka1977:
Well, with SetCPU with standby profile on 245Mhz and powersave governor the fluctuations stopped ...

Interesting, how can I find out what application causes this ?
[Nexus One Android Development] intersectRaven:
That I can't help you with. :confused: Maybe someone reading this thread can shed some light to your situation. :)
[Nexus One Android Development] Pochemuchka1977:
Well, the only way I see is to run both dmesg and logcat with redirection of stderr and stdout at the same time and to see what causes the spikes
[Nexus One Android Development] hah2110:
Howcome there is no 800mv or 825mv listed on mediafire? Also - what is the difference between 2.6.33_AVS_850UV_20100411_2113.zip and 2.6.33_AVS-850mV_20100412_1010.zip?
[Nexus One Android Development] intersectRaven:
I restored the .5mV difference in min and max values for AVS and changed AVS timing. :)
[Nexus One Android Development] Pochemuchka1977:
I always wipe cache and dalvik cache before flashing the new kernel - this isn't the reason for the freeze. With WiFi on the freeze hapens much faster than without WiFi on. Of course, during the regular work everything is fine, freezes always happen when the device is idle.
[Nexus One Android Development] intersectRaven:
REAAALLY last DEBUG kernel posted. This tweaks the AVS timer and also alters the delay in frequency setting. :)
[Nexus One Android Development] fibroman:
intersect Raven. Would it be possible to make a small boot kernel for people with the bad boot block N1's?

Micromod is working on a desire rom, and he said the only hope left for it to work with the people with the bad boot blocks is your kernel in a smaller form.

Please let me know if this is possible.

Thanks.
[Nexus One Android Development] MicroMod777:
That would be great, especially if its as good as regular version so I don't have to make two ROM's! :D
[Nexus One Android Development] Pochemuchka1977:
So far looks like this is really working :-) - except for the bluetooth which is not working (on CM6). I will let my phone to be idle for several hours to see how the device respond (and will it respond ;-) )
[Nexus One Android Development] Festaman:
Wifi Not working

So after this update, the wifi doesnt seem to work anymore. I will be able to Browse for a second or 2 then nothing, But it says its connected fine i have an ip and everything.

I have reflashed and wiped Dalvik before both times. Anyone else having this issue?
[Nexus One Android Development] mezmer1ze:
It may be a problem more related to cyanogenmod, but I noticed that sometimes when I take a picture my camera freezes, the screen is black and then it FCs, of course the picture is not stored on SD card and I can't get my camera app back on, because it says it can't be initialized, it lasts until I restart my phone.

It was happening even with wildmonks kernel but since it was based mainly on your work I guessed it must be related somehow :o
[Nexus One Android Development] intersectRaven:
I think the port to .35 isn't finished with cyan's kernel branch. (I'm not sure since I'm not the expert with the camera) All I know is I haven't changed anything there from cyan's .35 branch so we should have the same problems if ever. ;)

Posted another DEBUG kernel. This one makes the i2c bus faster (as in you really could feel the entire N1 fly) so that AVS doesn't overload it with requests. :)

*Pochemunka please test! (my apologies if the spelling is wrong but that's what I can remember) :p
[Nexus One Android Development] Pochemuchka1977:
Downloading it now ... The previous one still up :-)

It looks like you finally overcome this :-)
[Nexus One Android Development] Festaman:
This is driving me Nuts, My wifi works for liek 15 seconds then stops since I flashed this. I have reflashed with wifi off and dalvik wiped. I am on 2.2 with the newest radio i for get the number. Anyone else have the problem?

it only seems to stop when i start to download something wether it be form a site or the market place
[Nexus One Android Development] Pochemuchka1977:
With the latest debug kernel I have no problem with WiFi.

Check, may be you have some application that block the communication ?

If you are on stock ROM, might be wpa supplicant is not suitable for the driver ?
[Nexus One Android Development] Festaman:
I am using CM 6 it jsut started when i switched to this kernal, I tried it at work and home it does the same thing. Whats the debug kernal? I saw it on media fire but if its newer i will give it a shot. I just flashed the non CM on to try
[Nexus One Android Development] Pochemuchka1977:
There is an issue with HAVS stability, so for the last several days intersectR releases DEBUG kernels and I am as one with this issue check them :-)

With two last ones seems that the freeze issue was finally resolved (will be smarter after leaving the phone idle for the whole night)
[Nexus One Android Development] Festaman:
what also, I may have just noticed its the stock apps. google listen seems to be downloading my podcasts ok over wifi, but the market will not download and the browser will not browse, this is so odd

Update: yeah its just the stock apps its seems i wonder if something got screwed in my CM6
[Nexus One Android Development] xghostyxjokerx:
Help Help Help

im using cyanogen rom 6.0 stable version and the battery life on it sucks which kernel on here can i use to improve the battery alot!!! please help!!! thanks:confused:
[Nexus One Android Development] Pochemuchka1977:
The joy was too early - the last one (2125) froze the device without last_kmsg created.

The previous one (1347) froze the device, last_kmsg attached. Both kernels were with WiFi on.

I will try the last one again ...
[Nexus One Android Development] mezmer1ze:
Well if you like cutting edge, try the latest kernel from 15.9.2010, if you experience problems you can always switch to SVS kernel or wildmonks' kernels (which are based on intersectraven's work but seems to be discontinued for now).

I use the IR's kernel from 15.9.2010 with some setcpu profiles set and I can always get at least 2 days of battery life with really heavy and by heavy, I mean really HEAVY usage :D Lots of internet use, calls and texts.

edit: I share your pain, I switched kernels on the day I installed stable CM6, because it has some real battery sucker kernel.
[Nexus One Android Development] Lazat:
What kernel is it that you are running,

Changelog:

20100915_20XX:

- fixed NEON optimization in the kernel compilation so it should work faster now

- added AVS information for debugging faults

BFS HAVS -> http://www.mediafire.com/?66eap7bpb0re0ai

BFS HAVS-CM -> http://www.mediafire.com/?o2rnkzkcs7ki41n

CFS HAVS -> http://www.mediafire.com/?lc9nybzmc78ylb2

CFS HAVS-CM -> http://www.mediafire.com/?m0pzxbxop650ozd

?

Thanks =)

Edit: i also wonder if this kernel is with 720p or not? because im running Leofroyo rom, which currently doesnt support 720p

Edit2: i must have searched like a .... because a search now just got me the answer =) its 720p.
[Nexus One Android Development] xghostyxjokerx:
so im trying the bfs havs-cm 1592010 is this the battery kernel u are talking about?
[Nexus One Android Development] Pochemuchka1977:
Well, with the last DEBUG kernel got freeze again with no logs available. Looks like my device really dislike HAVS. Reverting back to wildmonks latest.
[Nexus One Android Development] intersectRaven:
Seems like it. I haven't suffered an overnight freeze like the previous kernels with the latest but I don't really like the edit I made. :)
[Nexus One Android Development] intersectRaven:
Major update to AVS stability. :)
[Nexus One Android Development] eViL D::
Any commits? :D
[Nexus One Android Development] intersectRaven:
I'm still unconvinced about stability so I haven't committed it yet. I'll send you a temporary diff for it instead. :)
[Nexus One Android Development] poochie2:
#1: Is your kernel directly compatible with Evil's Sense ROM?

#2: Could you very kindly illuminate me and tell me if you know how is it possible to tweak the kernel in order to enable overclock even without using SetCPU or similar apps? Thanks!

I've been compiling here and there some kernels and I found some very low limits with stability which maybe could work for quite a bunch of Nexus-es out there ^_^ (mine can take, in SVS, the stock 998 Mhz at 1200 mV (I set 1225 just for enhanced stability while jumping from one freq to another) and 499 MHz can take as low as 900 mV, which I keep as standby freq in conservative scaling giving me great idle battery. Not a problem in the last two days in Evil's kernel from his repo. :)
[Nexus One Android Development] intersectRaven:
1.) Yes. I use that as my ROM currently.

2.) Please rephrase. :p

:)
[Nexus One Android Development] poochie2:
Very good!

Well, I'd like to know if it's possible to make a kernel work over 998 MHz without having to use any OverClock utilitiy. Looking at the kernel source (I'm noobie :-) ) I cannot understand where it is written that the default max should not exceed 998 MHz even when the frequency table goes up to 1228 MHz.
[Nexus One Android Development] intersectRaven:
It should be possible to alter the maximum frequency through the terminal. Of course, you'd need to download a Terminal app. I think it's easier to use SetCPU if you're going to overclock since you still need to download something. :)
[Nexus One Android Development] poochie2:
So the kernel cannot be configured to overclock by itself? I think that some Hero ROM did that but I cannot remember very well now, if it's not possible then I must be wrong :p
[Nexus One Android Development] intersectRaven:
I'm sure that there is no limiter (aside from frequency table) in the kernel so it's not there that is the problem. I think like the governor, there are files/drivers in the ROM itself which set the minimum and maximum frequency at boot. (correct me if I'm wrong with this...) :)
[Nexus One Android Development] intersectRaven:
Updated to 2.6.35.5! :D
[Nexus One Android Development] mezmer1ze:
I've run CFS HAVS CM (with CM6 ROM) and it is very stable for me with great battery life.
[Nexus One Android Development] mezmer1ze:
The newest kernel is odd, it started ok but when it went to standby (screen switched off), I can't fire it back up, only the buttons backlight works, screen is still black.
[Nexus One Android Development] intersectRaven:
Do you have the last_kmsg? :confused: Also what newest kernel? 2.6.35.5?
[Nexus One Android Development] mezmer1ze:
Yep, newest 2.6.35.5, I had no such problems with .4 and I can even reproduce this bug.

Used CFS HAVS CM.
[Nexus One Android Development] intersectRaven:
Just revert to the last .35.4 kernel for awhile. When I merged .5 there was a conflict I'm not so sure how to handle and just pushed it so maybe it affected stability. :o I'll examine it later when I have time. For now, I can't replicate it on my N1. :(
[Nexus One Android Development] lordc:
Hi,

I'm using cyanogemod 6 and using lcd changer o nexus one, you last havs-cm, kernel 2010-09-21 09xx, fail with "system service stop" message.

ps: sorry for my english i'm not native english speaker.

ps2: your work is great!
[Nexus One Android Development] intersectRaven:
Can you provide me with your last_kmsg?
[Nexus One Android Development] Gilg@mesh:
same problem here, also my SD card seems to be "damaged" when using latest 35.5 kernel, switched back to stock CM6 kernel no more problems.
[Nexus One Android Development] Pochemuchka1977:
For the first time I have my phone running with HAVS kernel for the whole day without freezes :-)

It was really MAJOR update :D

P.S. There are several "Unable to drop vdd" messages in the kmsg log, but the phone is running fine
[Nexus One Android Development] Beezkneez:
Was having freezes all day with 2.6.35.4_AVS-CM-950mV_CFS_20100915_2029

Just flashed the newbie 2.6.35.5_AVS-CM-950mV_CFS_20100921_1524

fingers crossed
[Nexus One Android Development] haozheng91:
this seems very unstable on me..

previously with the 2.6.35.4 kernel it constantly freeze and have to pull the battery. and sometimes it reboots into boot loop even when I am not touching it..

now using 2.6.35.5 on CM6.0.0 somehow the screen doesn't always wake up after timeout.. though the soft buttons can light up.
[Nexus One Android Development] houzuoguo:
Hi IR

I don't know much about Linux kernel and I only know little bit about C++ and C, but I'm interested in how does AVS work but unfortunately I can't find the code by myself :D

Could you please kindly tell me which file controls AVS algorithm?

Many thanks!
[Nexus One Android Development] phewizzo:
Screen goes off and doesnt come back on, I can see most people here are having the same exactly problem, good job though IR.

Sent from my Nexus One
[Nexus One Android Development] houzuoguo:
Few months ago, when there was CM 6.0 RC-1, when there was 800mV AVS, I thought that kernel has excellent stability, and my best outcome was, synchronizing 4 accounts + news & weather, battery drained 1% every 2 hours.

But since the algorithm used in that kernel was considered incorrect......
[Nexus One Android Development] intersectRaven:
Sorry. Didn't post it here that .35.5 is REAAAALLY UNSTABLE. I think I made a wrong commit with the conflicting files. Sorry!!! :o
[Nexus One Android Development] sassafras_:
Same. It seems your newest commit with the new kernel version is quite unkind to the SD card.

The previous 9-21 with the .4 kernel is great though, no lockups yet.

sassafras
[Nexus One Android Development] davelis828:
hello

i m runnin cm6 on my nexus,and was wondering: how can i get the HTC radio app to work with your kernel?

is it possible yet?
[Nexus One Android Development] intersectRaven:
Not possible. You need to be running a Desire-based ROM. :( (unless someone ports the app OR MIUI releases the kernel source for their FM app) :D
[Nexus One Android Development] davelis828:
thanx man!
[Nexus One Android Development] xghostyxjokerx:
so just got done using the bfs havs cm and it was no good....please which oneplease be detailed...which one is good to use for the cyanogen mod 6.0n1 something real stable....thanks!:confused:
[Nexus One Android Development] mik101:
I had one lockup in the past day using the Sept 21, CFS CM6 on yesterdays Cyanogen Nightly (6.0.x). Usually I don't have any using the CM6 nightly stock kernel at 1075mhz, this was at 998mhz. Nexus One.
[Nexus One Android Development] kazprotos:
Errors about damaged SD card, telling me I've removed the SD car when when haven't. Back to older and its OK. CM6 with an 8gb Nokia sd card.
[Nexus One Android Development] intersectRaven:
Again, don't use the .35.5 versions. I made a booboo with a revision I made to fix a conflict while merging. :o
[Nexus One Android Development] xghostyxjokerx:
maybe you can help there are so many kernel on here i dont know which to choose??? im using the cyanogen mod rom 6.0n1 and seem to have a battery problem besides the setting in which i set up which kernel is the very best u say to use for battery saver??? please help anyone....:mad:
[Nexus One Android Development] intersectRaven:
I really can't say which is the best for your battery. It depends on too many factors you see. Anyways, try which is best AND most stable for you. :)
[Nexus One Android Development] xghostyxjokerx:
do you think it could be a radio issue or not?

hmm can u at leat recommend a kernel to try..all the kernel listed with cm right?
[Nexus One Android Development] intersectRaven:
Yeah. The -CMs are the ones for Cyan's ROM. :)
[Nexus One Android Development] intersectRaven:
Update! Last modification to i2c wasn't *that* stable. This should be stable since this is the version I tested extensively last time. :)
[Nexus One Android Development] xghostyxjokerx:
error: can't open 2.6.35.4_avs-cm-950mv-cfs20100922_2154.zip

bad

im unable to flash this please fix...i have recovery 1.8.0.1??
[Nexus One Android Development] Pochemuchka1977:
Just flashed it - everything is ok. Download it again ...
[Nexus One Android Development] xghostyxjokerx:
okay downloading now...will report back...
[Nexus One Android Development] phewizzo:
New kernel still has wake problems, screen goes off, when u press the power button only the menu buttons light up but the screen is still black, had to pull the battery and flash Pershoots kernel again and everything is fine.
[Nexus One Android Development] mezmer1ze:
Strange, I had these problems with .5, but .4 is still OK for me, even the latest one.
[Nexus One Android Development] xghostyxjokerx:
okay i redownload the kernel now attempting to use the phone will report after a few hours and see this improves the battery or if not i might just switch the rom to a different one.... :(
[Nexus One Android Development] Pochemuchka1977:
Usually the problem is not with the ROM and kernel, but with applications installed on your phone ... For example I had one VOIP application that drained 20% of the battery in one hour ...
[Nexus One Android Development] intersectRaven:
Yeah. I also got that with the latest kernel. Will continue to investigate. (at least it's still a lot more stable than before though) :p

.5 is reaally bad...anyways, I'll wait for the proper merge from Google or Cyan. :)
[Nexus One Android Development] intersectRaven:
HAVS CFS-DEBUG kernel released...please test: http://www.mediafire.com/?f56oc2q9sz1i027
[Nexus One Android Development] yumcax:
IR vs WM Kernels

Hello, what are the differences between these kernels and Wildmonk's kernels?

Thanks,

-Yumcax