yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] intersectRaven:
Minimum voltages are the same so if your N1's CPU can handle the lowest voltages from 2++ to 422 then there'd be no difference. :)
[Nexus One Android Development] jameztcc:
Thanks, trying 128 in the profiles for now. Thanks for the kernels ;p
[Nexus One Android Development] slava86:
are 128mhz and 245mhz have the same voltage?
[Nexus One Android Development] suenos:
question

ok guys need some help can some one tell me wy wen i flash this kernel my wifi dosent work i know that in the first page tells u how to flash and i have done that like this..1 push ko file reboot bootloader 2.flash zimage reboot everything is ok exept wifi dosent work and wen i plug in my phone to computer it dosent find my phone also i read that says push wifi drivers first but how do i do that and wer are the drivers hope some one can help me out thanks in advans.:confused:
[Nexus One Android Development] k3vink3vin:
My ears almost bleed when I enabled dynamic range compression in DSP while listening to music on earphones, running CM7 #28, 2.6.37_AVS-CM7_CFS_20110130_1213.zip
[Nexus One Android Development] daveid:
On a serious note, Cyanogen made some important kernel updates, will we see a build today?

Thanks!!
[Nexus One Android Development] intersectRaven:
Already done. You can find them at the usual. :)
[Nexus One Android Development] daveid:
You absolutely rock! Just in case you didn't already know that...
[Nexus One Android Development] relax24:
Silly question in most likelihood, but can cm6.0 users use the kernel .37 CM7 Kernel, or will it all go horribly wrong?
[Nexus One Android Development] doctorspeed1:
I second that!
[Nexus One Android Development] PauseZ:
just flashed the latest for CM611

2.6.37_AVS-CM6_BFS_20110201_2202 and I realised that whenever I connect my phone to the PC, it doesn't detect that there is any USB connected.

the debugging notification is gone as well!

I think I had this problem on a previous 20110125 release as well.

Battery life is absolutely awesome though..
[Nexus One Android Development] tehgeekguy:
From my experience with this issue, debugging is still enabled, you just don't get the notification. For the SDcard part of it, you can download a handful of apps (free and paid) from the marketplace that let you mount your sdcard. Search for "mount" and you'll find them. But I'm very happy with the battery life too :)

It is kind of annoying not to have the native option anymore, but I can live with it until it's either fixed, or Gingerbread is official and CM7 gets closer to a stable build with official drivers :)
[Nexus One Android Development] scalp42:
intersectRaven

2.6.37_AVS-CM6_CFS_20110201_2157.zip

with NO audio boost please ? :)

Please again ? :o
[Nexus One Android Development] knightnz:
It knocked about 150 off my quadrant scores which isn't promising.
[Nexus One Android Development] ellesshoo:
Anyone know if there have been any changes to the CM6 kernel since about Jan 6 or are they just recompiled automatically with the cm7 kernels? Thanks in advance. I don't really understand how to interpret code commits.
[Nexus One Android Development] ellesshoo:
Speaking of not understanding how to read commits... Is there a plain text file showing the voltages/ranges used by AVS at each frequency?
[Nexus One Android Development] theloginwithnoname:
A quick post to point out that your latest WIFIFAST kernel fix the WiFi issue (after a period of time on wifi, it/tcp stops sending/receiving data but remains connected) for me, but it is still there with your NOBOOST!

On first day using it (AVS, CFS), battery life seems about same as CM7 and WildMonks - but as WiFi fixed, it's all good.

Keep up the excellent work IR!
[Nexus One Android Development] intersectRaven:
New HAVS Kernel released!

- reintegrated some zen-kernel modifications
[Nexus One Android Development] ellesshoo:
English translation?
[Nexus One Android Development] intersectRaven:
More improvements? :p
[Nexus One Android Development] houzuoguo:
Hi IR :)

I ran your latest kernel on my phone and got higher benchmarking score compare to CM's kernel, but I notice that with heavy load and full brightness screen, your kernel drains ~100mAh more than CM's kernel...
[Nexus One Android Development] blahbl4hblah:
Yeah I noticed that as well. My battery died about 3 hours sooner then usual
[Nexus One Android Development] intersectRaven:
must be because the compiler is translating more code to vfp which is why it's faster while consuming more energy...
[Nexus One Android Development] paulk_:
Phew I thought I was the only one experiencing bad battery drain. Was losing 6% per hour with light usage. Kernel before that is lighter on the battery.
[Nexus One Android Development] blahbl4hblah:
Oh alright that makes sense to me, Will you be updating your kernels due to this?

Also, pershoot released a new kernel as well, just a heads up
[Nexus One Android Development] paulk_:
Pershoot's kernel is still for Froyo though. Not supporting CM7 nightlies yet
[Nexus One Android Development] blahbl4hblah:
I'm well aware haha, but I'm pretty sure raven can find somethings in there and add it to his kernel
[Nexus One Android Development] paulk_:
True, true!
[Nexus One Android Development] britoso:
I just tried 2.6.37_AVS-CM7-WIFIFAST_BFS_20110207_2204.zip on top of CM7/passion/36 and got stuck at the X.

Switched back to the windmonk variant : 2.6.35.10_AVS-950mV_BFS_AXI_720p_1152MHz_010611_CM7.zip and its all working again.
[Nexus One Android Development] intersectRaven:
New HAVS Kernel released:

- compiled with hard-floating point option

- new compiler by redstar3894 with more optimizations
[Nexus One Android Development] paulk_:
Just happened to check your mediafire folder before your announcement and already using it! Seems good so far!
[Nexus One Android Development] pearl62:
So which CM6 versions have audio boost? I've tried a few versions that didn't have NOBOOST in the name but they still dropped in volume in the car dock...
[Nexus One Android Development] paulk_:
Those that don't have the NOBOOST tag should have audio boost.
[Nexus One Android Development] pearl62:
I agree, but that's not what I'm seeing...
[Nexus One Android Development] intersectRaven:
Haven't made one yet for CM6. :p

*Here:

http://www.mediafire.com/?k7b4v1d111ty4jy
[Nexus One Android Development] NinjaSverre:
whats the difference between the "WIFIFAST" and the onces without (besides the obvious)?
[Nexus One Android Development] houzuoguo:
I think "wififast" keeps wifi awake when making call over internet~~

by the way the latest kernel is very nice :D
[Nexus One Android Development] dirwdirw:
+1 .
[Nexus One Android Development] intersectRaven:
By the way, the latest release has swap support for those people who still want to use swap. (not recommended due to Android's memory management techniques)
[Nexus One Android Development] makelegs:
Hey, IR...

just running some wonk tests. Here's a dmesg following a wonk using cm7 bfs wifi fast 2/9/11 : http://pastebin.com/iZJjNyEj

Can you, by chance, extract any meaning from it??? Some fairly interesting descriptions in it as best I can tell. But I'm an idiot....

Edit: here's another one using cfs, too

Edit: and another:

Hope any of this is useful in some way
[Nexus One Android Development] fitsnugly:
had a panic, cm7 wififast cfs 0209 version...

http://pastebin.com/CDDEu7Hu

had some i2c errors right at the end, just like in the dmesg above, unknown if it's related or not
[Nexus One Android Development] redstar3894:
Those errors look awfully familiar.... almost identical to the i2c errors that pop up when the kernel boots up and is initializing everything.... strange.... :confused:

I'll have to wait till I have more time to look at it in detail and see if I can reproduce this.... what exact steps did you guys take to cause this panic?

I think we'll also have to wait for iR to get a chance to look at these and see what he thinks, but there's a possibility we could be hitting an underlying i2c bug, or it could even be a problem that my tricked out compiler is exposing.... :p

I added a miscellaneous i2c fix from upstream to my kernel that isn't in iR's kernel, so if you want, you could give the kernel in my signature a try, I think its the latest one ... and see if that solves the problem.... because like I said, I haven't had the wonk happen on any of my kernels (yet....)

Sent from my Nexus One
[Nexus One Android Development] fitsnugly:
Was a random panic, I looked down & my phone was rebooting.

Prebuilt CM kernel was updated tonight, gonna see how that runs, then I'll try yours redstar...
[Nexus One Android Development] houzuoguo:
Hi IR, thanks for the updated kernel :)

By the way what does "customizable" kernel mean..?
[Nexus One Android Development] intersectRaven:
You're fast! I was just about to post! :p
[Nexus One Android Development] intersectRaven:
HAVS Kernel AVS-CUSTOMIZEABLE released!

- runtime modification of AVS minimum and maximum voltage limits

- runtime toggle of AVS debug printouts

- refer to OP for instructions

- CFS, NOBOOST, CM7 only for now until I get more feedback
[Nexus One Android Development] houzuoguo:
:p haha I see ~~

all right, flashing your kernel now~

by the way, it soudds really exciting that your kernel can modify voltage table dynamically :D that's quite a good news!

I'll see whether my dear nexus is able to handle voltage under 950mV :rolleyes:

"cannot create avs_adjust: read-only file system" :rolleyes:

Aha i forgot to mount system as rw sorry :D

I've a question, does my customizable value keep at next reboot? Is there a way to show current voltage table?
[Nexus One Android Development] intersectRaven:
you seem to be doing it wrong...the avs_adjust is in the /sys folder...also, it will reset upon reboot...
[Nexus One Android Development] houzuoguo:
oh i was doing it wrong :D

well now I've set:

128000,800,900

245000,800,925

although in SetCPU I see my CPU frequency drops to 128mhz, but I can't see any AVS message at that frequency..?

oh nevermind :D my mistake, i just got one 950mv at 128mhz :rolleyes: i hope the voltage will go lower~~
[Nexus One Android Development] intersectRaven:
if you're not seeing messages, it may be that your N1 doesn't like to go down...you can force it by setting the voltages to the same mV...
[Nexus One Android Development] dirwdirw:
why just noboost version？
[Nexus One Android Development] intersectRaven:
It's the kernel I use for my N1 and my testmaker script. ;)
[Nexus One Android Development] houzuoguo:
this is what i've run:

cd sys/module/avs/parameters

echo 128000,800,800 > avs_adjust

but in dmesg I still get message 950mV @ 128Mhz, what did I do wrong?
[Nexus One Android Development] intersectRaven:
Did you see a message which says "Manual adjustment successful"?
[Nexus One Android Development] houzuoguo:
no i didn't.. at which step should i get the message?
[Nexus One Android Development] intersectRaven:
The moment you adjust, you should see the message that "Manual adjustment begin" and also whether it succeeds or fails and why. :)
[Nexus One Android Development] houzuoguo:
ok let me wait for someone else to test the kernel... I don't get any response from avs_adjust..
[Nexus One Android Development] intersectRaven:
Hmmm...I think I found the problem. The kernel was limited to 950 as minimum. Please wait. :p
[Nexus One Android Development] intersectRaven:
Here's the corrected kernel:

http://www.mediafire.com/?m32mi1744ksb55m

I also updated the OP to point to it as the latest. :o
[Nexus One Android Development] houzuoguo:
Works pretty well :) thanks a lot

I randomly get message saying a volt is too high for a frequency, for example, I just set 245000,875,900, and in dmsg I got

"Manual adjustment success for 245Mhz"

"1275mV too high for 245000"

when I set 128000,875,900 I got:

"Manual adjustment success for 128Mhz"

"950mV too high for 128000"

Is that a bug?

By the way, my phone plays Angry Birds happily at 875mV @ 245Mhz :D
[Nexus One Android Development] makelegs:
If anyone is interested or speaks dmesg.....here's a WONK dmesg using the updated stock cm7 kernel:

http://pastebin.com/saPUu5RC

Edit: and another....

http://pastebin.com/AjE1jfLD
[Nexus One Android Development] intersectRaven:
The too high messages are ok. It means AVS sees the adjustment and will readjust the voltages to within the desired limits.

*I'll have to look as to why 245Mhz had a 1275mV voltage though... :confused:

Seems like your a1026 proximity sensor is the cause. :)
[Nexus One Android Development] makelegs:
Thought that was the noise-cancel mic chip. I have no clue, really. Here's one with the most recent kernel from ur op. Really not trying to be obnoxious. Just trying to get as much info out there to people who hopefully understand it better than I do........that would be pretty much everyone! ;)

http://pastebin.com/ks2GRAkj
[Nexus One Android Development] intersectRaven:
Oh. Right! It was the voice cancellation thing. My bad! :p
[Nexus One Android Development] houzuoguo:
Hey IR, can you please post a link to your default voltage table? Thanks!
[Nexus One Android Development] paulk_:
Does this voltage table follow pershoot's values for max voltage?
[Nexus One Android Development] houzuoguo:
I'd like to share my voltage settings, I set lowest frequency to 128Mhz and highest to 614Mhz using SetCPU:

echo 128000,875,900 > avs_adjust

echo 245000,875,900 > avs_adjust

echo 256000,875,925 > avs_adjust

echo 384000,900,925 > avs_adjust

echo 422400,900,925 > avs_adjust

echo 460800,900,950 > avs_adjust

echo 499200,925,950 > avs_adjust

echo 537600,925,950 > avs_adjust

echo 576000,925,950 > avs_adjust

it's pretty stable for me, so far.

I'll run no higher than 576Mhz and tomorrow I'll go higher frequency~
[Nexus One Android Development] jbr7rr:
Thx its fun to expiriment with the avs table :)

but when i read the dmesg it seems avs is only setting to the max Voltage,

is this normal?

Here is my table for now (thx to houzuoguo who inspired me):

echo 128000,875,925 > avs_adjust
echo 245000,875,925 > avs_adjust
echo 256000,875,925 > avs_adjust
echo 384000,900,950 > avs_adjust
echo 422400,900,950 > avs_adjust
echo 460800,900,975 > avs_adjust
echo 499200,950,1000 > avs_adjust
echo 537600,950,1000 > avs_adjust
echo 576000,975,1025 > avs_adjust
echo 614400,1000,1050 > avs_adjust
echo 652800,1025,1075 > avs_adjust
echo 691200,1050,1100 > avs_adjust
echo 729600,1075,1125 > avs_adjust
echo 768000,1100,1150 > avs_adjust
echo 806400,1125,1175 > avs_adjust
echo 844800,1150,1200 > avs_adjust
echo 883200,1150,1200 > avs_adjust
echo 921600,1175,1225 > avs_adjust
echo 960000,1175,1225 > avs_adjust
echo 998400,1175,1225 > avs_adjust
echo 1036800,1225,1275 > avs_adjust
echo 1075200,1225,1275 > avs_adjust
echo 1113600,1225,1275 > avs_adjust

note: if you want to use them you need to copy them line by line into the terminal else it will not work.

edit: here is wildmonks voltage table i used them as a base http://wildmonks.whoisthedrizzle.com/kernel/2.6.35/Voltage_table.txt
[Nexus One Android Development] fitsnugly:
yeah, we know. cyan believes it's a possible race condition, the a1026 driver failing to start because of the i2c bus being busy. we're posting you dmesg logs not to have the obvious pointed out, but to see if more eyeballs on the problem can help solve the actual issue.
[Nexus One Android Development] ellesshoo:
+1.. This. I've asked before but I think it got lost in the mix of a kernel release and the subsequent posts. I would love to know the default values.
[Nexus One Android Development] SimFox3:
The latest cfs noboost kernel is running great on cm7. Thanks again for making a noboost kernel
[Nexus One Android Development] intersectRaven:
The default values are on my GitHub page. Just navigate to arch/arm/mach-msm/avs.c to see the current defaults for AVS. :)
[Nexus One Android Development] houzuoguo:
I managed to save 20% of battery by adjusting avs voltage table yesterday :p HOORAY!
[Nexus One Android Development] intersectRaven:
Good to hear! I'll be releasing a HAVS-C kernel soon with SVS limits (meaning the limits to minimum and maximum for each frequency is tied to the SVS values so it will act like the other SVS kernels) soon for advanced users to tinker with and optimize by their own preferences! :)
[Nexus One Android Development] houzuoguo:
:D for me your AVS kernel is already SVS kernel... I'm driving my CPU crazy by feeding up to 1V at 652Mhz hahaha...

By the way, I have very limited knowledge about C... so for example I have following two entries in voltage table:

128000,875,900

245000,875,950

If AVS is feeding 900mV to CPU when it's at 128Mhz, then when CPU switches to 245Mhz, does AVS feed 875mV or 900mV at beginning?
[Nexus One Android Development] ellesshoo:
for everyone who doesn't feel like finding it... this is what I got:

{ 19200, 950, 950 },

{ 128000, 950, 950 },

{ 245000, 950, 975 },

{ 256000, 950, 975 },

{ 384000, 950, 1000 },

{ 422400, 950, 1000 },

{ 460800, 975, 1025 },

{ 499200, 1000, 1050 },

{ 537600, 1000, 1050 },

{ 576000, 1025, 1075 },

{ 614400, 1050, 1100 },

{ 652800, 1075, 1125 },

{ 691200, 1100, 1150 },

{ 729600, 1125, 1175 },

{ 768000, 1150, 1200 },

{ 806400, 1175, 1225 },

{ 844800, 1200, 1250 },

{ 883200, 1200, 1250 },

{ 921600, 1225, 1275 },

{ 960000, 1225, 1275 },

{ 998400, 1225, 1275 },

{ 1036800, 1275, 1275 },

{ 1075200, 1275, 1275 },

{ 1113600, 1275, 1275 },

{ 0 },

IR, do you change the table often or can we count on this being the default?
[Nexus One Android Development] waylo:
Do you normally underclock your phone so significantly, or just for this kernel's sake?
[Nexus One Android Development] intersectRaven:
Those are just the minimum and maximum values so it depends on your N1 whether it scales to what value. It first uses the upper value and drops it by 25mV increments. If the CPU doesn't complain, then it retains the lower voltage, otherwise, it goes up again. :)

I don't change that anymore although the HSVS (or CAVS...haven't decided what I'll call them yet :p) kernels I will release later will have the same upper and lower limits tied to the current maximum limits. :)
[Nexus One Android Development] houzuoguo:
I must try very carefully and set minimum voltage at each frequency, so yesterday it took me 2 hours to figure out that table up to 576Mhz. I usually ran my CPU at 1Ghz

today i spent another hour and now my volt table is:

cd /sys/module/avs/parameters

echo 128000,875,900 > avs_adjust

echo 245000,875,900 > avs_adjust

echo 256000,875,925 > avs_adjust

echo 384000,875,925 > avs_adjust

echo 422400,900,950 > avs_adjust

echo 460800,900,950 > avs_adjust

echo 499200,900,950 > avs_adjust

echo 537600,925,950 > avs_adjust

echo 576000,925,950 > avs_adjust

echo 614400,950,1000 > avs_adjust

echo 652800,950,1025 > avs_adjust

echo 691200,975,1050 > avs_adjust

echo 729600,1000,1075 > avs_adjust

echo 768000,1025,1075 > avs_adjust

echo 806400,1050,1125 > avs_adjust

echo 844800,1075,1125 > avs_adjust

echo 883200,1075,1150 > avs_adjust

echo 921600,1100,1150 > avs_adjust

echo 960000,1100,1175 > avs_adjust

echo 998400,1100,1175 > avs_adjust

With that table I'm able to run SetCPU's stress test multiple times successfully. I'll run it longer to test its stability..
[Nexus One Android Development] fitsnugly:
bump, so no further insight?
[Nexus One Android Development] paulk_:
One thing I haven't figured out, what is the 19200 frequency for?

[EDIT] Damn, your voltages are really low houzuoguo! Made my table by subtracting roughly 50 from each value, but yours substract up to 125 lol. Will give yours a try!

IR, is there any reason why the lower bound of the voltage usually follows the upper bound quite closely i.e. lower bound not more than 50 less than the upper bound? I've been using 925 as my lower bound up to 998400 and haven't had any problems.
[Nexus One Android Development] houzuoguo:
I love my CPU together with IR's kernel :D

I was very amazed by how low volt my cpu can handle :rolleyes:

By the way, I didn't only do substractions, I tried and stopped at each frequency to figure out the lowest possible volt for that frequency, thus my phone has hard-rebooted more than 15 times before I came out with that volt table~
[Nexus One Android Development] intersectRaven:
I set it that way since it's the most stable for most of the people who use my kernels. I previously set it very aggressively at 950mV as the lowest for all frequencies but most people's N1s won't even boot up properly with that. :p

Nice to hear someone else who has a very lenient CPU. :p
[Nexus One Android Development] paulk_:
So that's what you meant by spending 2 hours to come up with your table lol. Well 1175 is too low for my N1, hang followed by soft reboot as soon as I set 998400 to 1175 :(

[EDIT] Ugh my mistake! Copied the wrong values (manual copying) and was setting 998400 at 1150. 1175 seems stable for me so far.
[Nexus One Android Development] paulk_:
Will try sticking with the 925 lower for me up to 998400, seems stable somehow!

Hope you can think of a more magical way to change the voltages, pasting each value one by one after every reboot is horrible x.x. I feel your pain, houzuoguo!
[Nexus One Android Development] houzuoguo:
:D

My way of setting them is to run QuickSSHd on my phone, then start two terminals and SSH connect to my phone, one terminal runs cat /proc/kmsg | grep "AVS" another one sets voltage for each frequency.
[Nexus One Android Development] intersectRaven:
Unfortunately, it's set that way for a reason which is I only want advanced users to play with it. :p

That's also how I do it! (although I use a script to set the voltages so I don't have to do it manually if ever I fail on 1 adjustment) :p
[Nexus One Android Development] paulk_:
I just came up with my own method on my phone lol. Put everything into a text file with a <sleep 1> before each echo and run it. Works like a charm!
[Nexus One Android Development] yang901:
Instead, to speed up loading each echo for a script, I just tune it to

#!/system/bin/sh

echo "128000,950,950" > /sys/module/avs/parameters/avs_adjust

for a in $(seq 0 1 10000)

do

done

echo "245000,950,950" > /sys/module/avs/parameters/avs_adjust

for a in $(seq 0 1 10000)

do

done

echo "256000,950,950" > /sys/module/avs/parameters/avs_adjust

for a in $(seq 0 1 10000)

do

done

...

Then setting the whole freqs just takes about 1~2secs. Sleep 1 (sec) takes a little too long for me.

Plus, using Tasker with this script, everything is automatically loaded after boot.

refer to http://xdaforums.com/showthread.php?t=893388
[Nexus One Android Development] ch33kybutt:
Are the voltages set on-the-fly? If so, then we can set sleep-mode voltages even lower and auto-switch based on screenstate. Would do wonders for battery life. But constant switching may affect stability. Need to test ...
[Nexus One Android Development] paulk_:
Woah that's a lot faster! Making me brush up more on my bash which I haven't touched in ages :D. Wonder why we actually need a slight pause between each echo though.

Thanks Yang!
[Nexus One Android Development] paulk_:
Yes the voltages are set on the fly. I suppose it should be possible to do something like that with Tasker? Perhaps Yang can shed some light on it, I have no experience with Tasker at all >.<
[Nexus One Android Development] intersectRaven:
It's needed since the setting depends on the AVS timer and not on a notification signal. :)
[Nexus One Android Development] intersectRaven:
CAVS Kernels uploaded! these are AVS customizeable with SVS as beginning values so these should be stable for everyone... :)
[Nexus One Android Development] paulk_:
Noticed that I have the weird behaviour houzuoguo mentioned, the maximum CPU speed that the kernel will switch to is 1 step lower than what is set. Mine is set at default (998) using CM settings without setcpu, but the maximum it will scale up to is 960.