yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] sir*mez:
thats what i thought. im using the 20100417_1756: 875mv kernel.

edit: getting adb kmsg right now to see if theres a difference.
[Nexus One Android Development] intersectRaven:
Also, try using the 800mV one. I think AVS is stable enough now to handle the correct voltage to deliver to the CPU. :)
[Nexus One Android Development] Markdental:
is there a way to wipe the logs so I know it is only from the newest kernel?
[Nexus One Android Development] intersectRaven:
I can't see any AVS messages there. If ever, a good way to find out is that if in the beginning you see some, it's active. AVS won't be turned off afterwards and it will throw an error if ever it fails to initialize. :)
[Nexus One Android Development] Markdental:
Well, I am having major issues, just tried the 825 AVS, and still wifi won't work.

Any suggestions?

Also, the log is not showing any AVS like others out there getting multiple AVS spam.

Can anyone help?

BTW: In the phone info, it says kernel #2, used to say kernel #1 when I had the 800 AVS installed and then switched trying to get my wifi back.
[Nexus One Android Development] Markdental:
That looks good to me, how did you get the AVS messages? Did you let the phone sit on the plug after running adb?
[Nexus One Android Development] bskim23:
just typed "adb shell cat /proc/kmsg" in cmd prompt
[Nexus One Android Development] intersectRaven:
You're fine. You can see AVS is scaling down at 998Mhz (@20). :)

Only the lower voltages seem to be scaling for you. Anyways, it's still working and the limits set by the hybrid seems to be keeping the higher frequencies undervolted still. :)

Have you been pushing the wifi driver? That's the only thing I can think of wherein wifi won't work. As for AVS messages, assuming you're on the stable one, as long as you can see the initial AVS messages on bootup, you're fine. Also, #2 is correct for 825mV kernel. :)
[Nexus One Android Development] zdiamant:
For some reason, my phone will not charge... It says charging when looking at the initial screen, however under battery info it says battery status:full and is slowly uncharging even while connected to computer. This just started when trying to update to lower and lower hybrid models. I am now running the 925 version, but it happened with all versions. I may have to restore CM5.0.6 and then your kernels again if noone has an answer.

Thanks for all the time and effort you put into making this phone the best I've ever had!
[Nexus One Android Development] Markdental:
This is after installing the 800 AVS:

Still having problems with wifi, I use the button to activate in the powercontrol and instead of the color underneath lighting up all the way, it lights only a little and never completely activates. This is after pushing the .ko file before and even after flashing the zimage.

Is there another .ko file I can try?
[Nexus One Android Development] paulk_:
I get that problem when my battery still has over 90% left and i try to charge it. Shows the exact save thing as you're experiencing. Not sure what it's due to, keep forgetting to post anything asking about it.
[Nexus One Android Development] sir*mez:
this is normal behavior. it also happens on cyans kernel. OK it happens on all kernels. this feature is to protect you battery from overcharging and something about full battery life cycle, something like that. i forgot the exact words.
[Nexus One Android Development] zdiamant:
My phone did have over 90% left.. I tried it again just now with 89% left and it is charging now! I love these kernels! Thanks again!
[Nexus One Android Development] Markdental:
Is anyone else having issues with wifi? And YES, I pushed the .ko file. :)
[Nexus One Android Development] Markdental:
Shoot, I don't know what to do. The kernel is working great, but wifi won't startup even after pushing .ko file.

I am running the newest CM. Any other .ko files I can try?
[Nexus One Android Development] jblazea50:
try extracting the .ko file from another kernel (maybe 825mV or 850mV) as they are all the same and shouldn't matter anyways
[Nexus One Android Development] rjhay22:
Booyah, now I can flash the 800mV, I couldnt go pass the X-Lock screen with the previous kernels. Raven bro................. I think I love you man! hahahahaha!

Ill report back in a few hours. Hope this is stable.
[Nexus One Android Development] paulk_:
Wow the AVS 800 really seems stable for me now. Now that it's sleeping the cpu speed isn't changing either (not sure if that's usual, but while sleeping the cpu speed would keep changing while I was using the last 2 kernels). Here's part of my log from after rebooting and just before sleeping:

<6>[ 63.838684] batt: 34%, 3796 mV, 66 mA (

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

<6>[ 67.490905] AVS setting V to 800 mV @20

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

<6>[ 69.037689] AVS setting V to 1200 mV @20

<6>[ 69.137725] AVS setting V to 800 mV @20

<6>[ 69.688598] AVS setting V to 1200 mV @20

<6>[ 69.888793] AVS setting V to 1175 mV @20

<6>[ 69.938629] AVS setting V to 1150 mV @20

<6>[ 69.988555] AVS setting V to 800 mV @20

<6>[ 70.338928] AVS setting V to 1150 mV @20

<6>[ 70.438995] AVS setting V to 800 mV @20

<6>[ 71.640136] AVS setting V to 1150 mV @20

<6>[ 71.690216] AVS setting V to 1125 mV @20

<6>[ 71.740600] AVS setting V to 800 mV @20

<6>[ 72.290893] AVS setting V to 1125 mV @20

<6>[ 72.370910] AVS setting V to 800 mV @11

<6>[ 75.223968] AVS setting V to 1125 mV @20

<6>[ 75.284057] AVS setting V to 1100 mV @20

<6>[ 75.334014] AVS setting V to 800 mV @20

<6>[ 75.434997] AVS setting V to 1100 mV @14

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

<6>[ 77.065948] AVS setting V to 800 mV @2

<6>[ 85.100738] request_suspend_state: sleep
[Nexus One Android Development] paulk_:
Hmm, for some reason after the first time it sleeps (when you unlock your SIM card and then don't touch it so it sleeps) it doesn't show voltage/CPU speed changes anymore. Rebooted to make sure that's the case. Anyone know why this is happening?

Here are some more results to show the AVS in action:

<6>[ 40.054473] acdb: 588 bytes for device 607, rate 48

<6>[ 40.120086] AVS setting V to 800 mV @20

<6>[ 41.071014] AVS setting V to 1150 mV @20

<6>[ 41.172180] AVS setting V to 800 mV @20

<6>[ 41.323516] AVS setting V to 1150 mV @20

<6>[ 41.521850] AVS setting V to 800 mV @20

<6>[ 41.621948] AVS setting V to 1150 mV @20

<6>[ 41.671997] AVS setting V to 1125 mV @20

<6>[ 41.771789] AVS setting V to 1100 mV @20

<6>[ 42.172393] AVS setting V to 800 mV @20

<6>[ 42.372314] AVS setting V to 1100 mV @20

<6>[ 42.922851] AVS setting V to 1075 mV @20

<6>[ 43.123016] AVS setting V to 1050 mV @20

<6>[ 43.173095] AVS setting V to 1025 mV @20

<6>[ 43.223144] AVS setting V to 1000 mV @20

<6>[ 43.373291] AVS setting V to 975 mV @20

<6>[ 43.423339] AVS setting V to 950 mV @20

<6>[ 43.473693] AVS setting V to 925 mV @20

<6>[ 43.523437] AVS setting V to 900 mV @20

<6>[ 43.623657] AVS setting V to 875 mV @20

<6>[ 43.673645] AVS setting V to 850 mV @20

<6>[ 43.784210] AVS setting V to 825 mV @20

<6>[ 44.034912] AVS setting V to 800 mV @20

<6>[ 48.793151] mahimahi-microp 0-0066: Setting Jogball
[Nexus One Android Development] Markdental:
Oh well. No luck with wifi. Back on pershoots and wifi works great.

Can anyone think of something I could have done wrong when pushing the. Ko file? I even went into root explorer and moved it that way.

Does anyone have an older .ko file I can try for this kernel?
[Nexus One Android Development] Markdental:
Double post sorry
[Nexus One Android Development] jblazea50:
you can go here: IntersectRaven Kernel Folder and get whatever kernel he created and try one of the .ko files

also, when you pushed the ko file, did you make sure adb recognized the device and you did remount prior to pushing?

usually, i push the ko file first via adb with this command: adb remount (sees that remount successfull), then adb push bcm4329.ko /system/lib/modules/bmc4329.ko

once that is done, i do adb reboot bootloader

then fastboot flash zimage zImage

and reboot
[Nexus One Android Development] TheMorpheus:
Re: [Kernel - .33.2]intersectRaven's Kernel (new Hybrid AVS) 04/17/2010 06:13pm

With Hybrid AVS@800 no problem at all, no reboot and no freez!!

Start testing now.

Sent from my Nexus One using the XDA mobile application powered by Tapatalk
[Nexus One Android Development] acantril:
I get this as well - the V changes and kmsg displays it, after the first sleep it isnt shown anymore and i wonder if its actually changing as required.
[Nexus One Android Development] seanowns:
Re: [Kernel - .33.2]intersectRaven's Kernel (new Hybrid AVS) 04/17/2010 06:13pm

Like others, the 800 kernel is rock solid now. Before 825 was as low as I could go. Impressive!!!
[Nexus One Android Development] paulk_:
Well the CPU speed is changing as expected, no idea about the voltage though..
[Nexus One Android Development] immiMIK:
Is the latest kernel based on cyan 5.0.6 kernel?

thx
[Nexus One Android Development] Gimpeh:
I wonder how kernels below 800 would run now that 800 appears stable for everyone.
[Nexus One Android Development] iVisionX01:
Couldn't get any of the AVS versions to work. My phone keeps freezing while it sleeps for a long time. Maybe it's because I have too much stuff running on my phone? Anyway I'm about to test the SVS and see if my phone won't freeze.
[Nexus One Android Development] RieGo:
Re: [Kernel - .33.2]intersectRaven's Kernel (new Hybrid AVS) 04/17/2010 06:13pm

you should try the version posted a few pages before. it 's not on the first page.
[Nexus One Android Development] RieGo:
Re: [Kernel - .33.2]intersectRaven's Kernel (new Hybrid AVS) 04/17/2010 06:13pm

oh sry, i was wrong...
[Nexus One Android Development] paulk_:
From the first post:

20100417_1112:

- reconfigured the kernel to use cyan's latest configuration with the ff. modifications
[Nexus One Android Development] rameshb_v:
Asphalt Lag

I installed the 800mv Hybrid & 850mv Hybrid, but both are lagging in Asphalt... Was using 850mv AVS before and was perfect.

PS: I m on Cy 5.0.6

Edit: Issue resolved after wiping the ROM and re-installing it. I am now using 800mv Hybrid and no lag..
[Nexus One Android Development] britoso:
Re: [Kernel - .33.2]intersectRaven's Kernel (new Hybrid AVS) 04/17/2010 06:13pm

Whats up with all the log clutter?

Use pastbin.com guys !!!
[Nexus One Android Development] hah2110:
Re: [Kernel - .33.2]intersectRaven's Kernel (new Hybrid AVS) 04/17/2010 06:13pm

not good. on the newest 825 and lost 15% in 30 min using maps

Sent from my Nexus One using the XDA mobile application powered by Tapatalk
[Nexus One Android Development] hotweiss:
Great work, but with your latest kernel my N1 is hot as an iron after tethering... Usually it does not heat up at all when tethering.
[Nexus One Android Development] Markdental:
What setCPU setting is everyone using for best battery life and performance?

Ondemand?
[Nexus One Android Development] RaistlinMaje:
conservative would probably give better battery life than ondemand from my knowledge of the different cpu governors. mine is on min:245 max: 768 with conservative and my battery life is pretty good I think compared to stock.
[Nexus One Android Development] SimFox3:
Ok so previously I've been unable to run even the 925avs because of reboots, but i'm running the latest 800avs without anyyyyyy reboots.. Great job.
[Nexus One Android Development] Gimpeh:
My g1, ion, cliq and nexus have always gotten extremely hot with tethering on. I doubt his kernel is the cause.
[Nexus One Android Development] SimFox3:
When looking at the /proc/kmsg logs, I see a second number after @ sign.. like the "800 mv @ 2" sometimes "800 mv @ 20".. The second number varies between the other voltages too, but what does it mean?

sorry, I didn't go through all the previous posts... too many =(
[Nexus One Android Development] Markdental:
the number is what you multiply by 128 to get frequency.
[Nexus One Android Development] RieGo:
20*128=2560 :)

Would be nice, but i don't think it's right...

but it's something like this... (20=998MHz)
[Nexus One Android Development] r8zer:
49.9 * 20 = 998
[Nexus One Android Development] Markdental:
Sorry guys. Wrong number. But you got the idea. 20=Max stock freq
[Nexus One Android Development] myakove:
In /proc/kmsg i see only after boot logs for AVS, Is AVS working?

and I get this errors:

<6>[ 1013.226654] binder: 137:150 transaction failed 29189, size 96-0

<6>[ 1013.228851] binder: 137:150 transaction failed 29189, size 96-0

<6>[ 1013.231323] binder: 137:150 transaction failed 29189, size 96-0

I'm using latest AVS 800 kernel.
[Nexus One Android Development] SimFox3:
myakove,

plug in your usb cable, restart your phone, and when the phone has fully loaded look at the /proc/kmsg again. You might need to scroll up, but you should see messages like these:

<6>[ 1686.294006] AVS setting V to 1000 mV @6

<6>[ 1687.895355] AVS setting V to 1050 mV @9

<6>[ 1688.106079] AVS setting V to 1075 mV @10

<6>[ 1688.696472] AVS setting V to 1150 mV @14
[Nexus One Android Development] 2000impreza:
Decided to give the hybrid avs/svs kernels another try. I've went low as 850mv and seems to be very stable. Even tried rebooting multiple times repeatably trying to throw the device in a boot loop with no success which is good. Great job on the kernel!
[Nexus One Android Development] SimFox3:
I was unable to even run AVS 925mA before, but the latest build of 800mA hasn't crashed even once. I've been heavily using it for the past four hours. So try the 800mA too =)
[Nexus One Android Development] Daswolven:
Same here, reverted to Ivans kernel after I failed to maintain boot stability on any of these. Now on the 800mV I'm singing along and booting in one try every time. Awesome job man. :D
[Nexus One Android Development] intersectRaven:
You're both wrong! :p It's just the index in the frequency table that is in acpuclock-scorpion.c. @20 is the highest while @2 is the lowest enabled frequency. :)
[Nexus One Android Development] 2000impreza:
Couldn't resist so I just flashed the 800mV as well and appears to be very stable :)
[Nexus One Android Development] intersectRaven:
Since everyone seems stable on 800mV now, I'll just drop all the others and mark this as stable! (Weee!!! :p) I can also drop the debugging options (except the AVS messages which many people seem to like seeing :eek:) and go back to SLUB, etc. etc. :D
[Nexus One Android Development] paulk_:
raven, do you have any idea why some of us aren't seeing any CPU speed changes after our phones go to sleep for the first time since rebooting?
[Nexus One Android Development] m00moo:
Using the 800mv version and everything seems fine, although Im not very clear on whats happening...kind of. lol

<6>[ 952.111602] AVS setting V to 825 mV @20

<6>[ 952.281860] AVS setting V to 800 mV @2

<6>[ 953.302856] AVS setting V to 825 mV @20

<6>[ 953.613159] AVS setting V to 800 mV @2

<6>[ 954.564025] AVS setting V to 825 mV @20

<6>[ 954.674194] AVS setting V to 800 mV @2

<6>[ 958.427795] AVS setting V to 825 mV @20

<6>[ 958.497985] AVS setting V to 800 mV @2

<6>[ 963.432647] AVS setting V to 825 mV @20

<6>[ 963.572906] AVS setting V to 800 mV @2

<6>[ 972.141204] AVS setting V to 825 mV @20

<6>[ 972.321411] AVS setting V to 800 mV @6

<6>[ 974.133453] AVS setting V to 825 mV @20

<6>[ 974.375488] AVS setting V to 800 mV @2

<6>[ 974.393402] AVS setting V to 825 mV @20

<6>[ 974.613647] AVS setting V to 800 mV @2

<6>[ 976.135070] AVS setting V to 825 mV @20

<6>[ 976.245239] AVS setting V to 800 mV @2

<6>[ 977.276184] AVS setting V to 825 mV @20

<6>[ 977.296264] AVS setting V to 800 mV @2

<6>[ 979.738616] AVS setting V to 825 mV @20

<6>[ 979.818603] AVS setting V to 800 mV @7

<6>[ 979.838714] AVS setting V to 825 mV @20

<6>[ 979.938842] AVS setting V to 800 mV @2

<6>[ 989.838439] AVS setting V to 825 mV @20

<6>[ 990.088775] AVS setting V to 800 mV @2

a small section of my kmsg, it keeps updating - is this fine? my governor is set to ondemand right now. Changing it to conserve stops the AVS msgs. Thanks btw!
[Nexus One Android Development] intersectRaven:
The only thing I can think of is that your CPU isn't changing frequencies that much which is why your CPU is not complaining to AVS to change its voltage. :)

That's fine. Conservative governor tries to keep your CPU at 245Mhz so as long as there is no heavy usage, you won't change to a significantly higher frequency which will prompt for an AVS voltage adjustment. :)
[Nexus One Android Development] paulk_:
I think I wasn't too clear in my post, should've mentioned that this is happening when my phone is active, as in I go to the setcpu app and see the speeds changing, but nothing's changing in kmsg.
[Nexus One Android Development] intersectRaven:
Hmmm...in that case, I have no idea why that's happening. I tried what you said in my N1 and the AVS messages keep popping up. :confused:
[Nexus One Android Development] wind0zer:
working

After reading the last many posts I straight away flashed the 800 AVS kernel, wiped cache & battery, and booted properly (impressive). I can see the log messages after entering the adb command. Will be following the developments here.
[Nexus One Android Development] intersectRaven:
Updated!

20100418_0816:

- AVS now stable

- all mV steps have now been dropped in favor of 800mV which is now stable

- SLUB block allocation

- debugging options have been removed (except AVS messages)

20100418_0816:

Hybrid AVS:

http://www.mediafire.com/?ezmizz2egny
[Nexus One Android Development] Daswolven:
04/17/2010 08:18am

If I'm running the prior 800mV release and everything seems well, will there be a benefit to the new kernel?

Sent from my Nexus One using the XDA mobile application powered by Tapatalk
[Nexus One Android Development] intersectRaven:
You can skip it. It only introduces SLUB memory allocation and removed debugging features of the kernel. :)
[Nexus One Android Development] Markdental:
What about a 775 kernel? Or even lower?
[Nexus One Android Development] intersectRaven:
Not possible. The regulator only supports up-to 800 if my memory serves me right. :)
[Nexus One Android Development] hah2110:
What SetCPU settings is everyone using? Does anyone touch advanced?
[Nexus One Android Development] rjhay22:
Raven. You did it brother. Thank you. Sent you some beer like promised. Keep up the good work man.
[Nexus One Android Development] jazzor:
Would you be so kind as to tell me what parts of the code you changed that was related to honz observation?
[Nexus One Android Development] wildmonks:
Do you think you'll update your github with the new code? I'd love to see if I can intergrate it to the kernel I'm using :D
[Nexus One Android Development] hah2110:
Why would anyone now use anything but AVS Hybrid? I see almost no battery life difference in these kernels, I don't get it.
[Nexus One Android Development] wildmonks:
I compile my own kernels. Currently using the AVS code that's posted on intersectRaven's github (last updated April 10th) with Ivan's code for overclocking. This combination is giving me some great battery life with the added bonus of overclocking. Although currently the April 10th AVS code is only stable for me at 850mV. I'd like to see if using the new code will give me the 800mV that you all are enjoying :p

Based on previous posts, I'm thinking that the hybrid portion of his new code is responsible for achieving 800mV stability but I have no idea how to intergrate that in without looking at the current code :confused:
[Nexus One Android Development] die-hard:
Hi Raven,

can u add overlooking in your kernel?

Sent from my Nexus One using the XDA mobile application powered by Tapatalk
[Nexus One Android Development] die-hard:
My kmsg:

<6>[ 29.588592] AVS setting V to 1175 mV @20

<6>[ 29.698425] AVS setting V to 800 mV @6

<6>[ 29.758728] AVS setting V to 1175 mV @20

<6>[ 29.798400] AVS setting V to 1150 mV @20

<6>[ 29.798645] AVS setting V to 800 mV @6

<6>[ 29.858520] AVS setting V to 1150 mV @20

<6>[ 29.898498] AVS setting V to 1125 mV @20

<6>[ 30.038726] AVS setting V to 800 mV @6

<6>[ 30.380889] a1026_bootup_init: starting to load image (842 passes)...

<6>[ 31.760406] AVS setting V to 1125 mV @20

<6>[ 31.770324] AVS setting V to 1100 mV @20

<6>[ 31.820404] AVS setting V to 1075 mV @20

<6>[ 31.870788] AVS setting V to 1050 mV @20

<6>[ 31.920806] AVS setting V to 1025 mV @20

<6>[ 31.970886] AVS setting V to 1000 mV @20

<6>[ 32.020996] AVS setting V to 975 mV @20

<6>[ 32.070617] AVS setting V to 950 mV @20

<6>[ 32.120666] AVS setting V to 925 mV @20

<6>[ 32.171112] AVS setting V to 900 mV @20

<6>[ 32.221099] AVS setting V to 875 mV @20

<6>[ 32.271148] AVS setting V to 850 mV @20

<6>[ 32.321197] AVS setting V to 825 mV @20

<6>[ 32.421325] AVS setting V to 800 mV @20

Is good?
[Nexus One Android Development] lore2486:
how the heck do you get 800@20??? mine is always at 12xx when @20 lol

on a side note i finally was able to boot on the 800mv kernel dont know what you changed but it works, dont know if its stable but atleast it boots
[Nexus One Android Development] henrypeter:
sorry for being a noob here!

Wanna ask is it possible to wipe only the battery stats and cache but not all the apps and settings and where i can found it.

I'm Using CM 5.0.6

Cheers
[Nexus One Android Development] lore2486:
no need to wipe anything (i never do).... where can you find what?
[Nexus One Android Development] lore2486:
either yo have something running that makes your proc spike in standby or something else, you should try the governor set to conservative it will give you more battery at little to no performance cost
[Nexus One Android Development] henrypeter:
From the very first page of this thread.

***For AVS kernel first timers, please wipe the cache and battery stats before booting. This should help minimize the issues encountered a few times after flashing AVS kernels. If it still doesn't boot after a few reboots, revert to non-AVS as the AVS doesn't work on your CPU.***
[Nexus One Android Development] lore2486:
yep i read that, but i didnt do it and never had any trouble no restarts or somethig like that, anyway how do you clear the bat stats?
[Nexus One Android Development] prepster6:
Battery Logcat

I've been looking everywhere but I havn't been able to find it. How do you get this logcat with adb? I dont know the correct option to put. :confused:
[Nexus One Android Development] paulk_:
Go to recovery, there's an option under wipe.
[Nexus One Android Development] henrypeter:
I've found it!

Just under the "Wipe" in the Recovery, will try it later

Cheers~~
[Nexus One Android Development] mgear356:
like to state it is finally stable!

no more boot loops and crashes on new 800 kernel!

cheers!
[Nexus One Android Development] paulk_:
In the command prompt:

adb shell cat /proc/kmsg
[Nexus One Android Development] lore2486:
lol ok im using clock work recovery thats why i couldent find it, just flashed Ra 1.7 and wiped my bat stats thanks for the info
[Nexus One Android Development] henrypeter:
have flashed the new AVS kernel,

thx for the hardwork~
[Nexus One Android Development] die-hard:
Why my CPU voltare are not stable?

I set in SetCPU ondemand governor, if i set conservative it is stable (so and so :( )
[Nexus One Android Development] Homotechual:
My phone is rooted with Enomther's rom, but i'm new to Kernals? Can you give me detailed instructions on how to install this please, and if it will fix all Audo it's really quiet.

Thanks for the help, where is ADB is that in Recovery mode, or on my computer?:confused:
[Nexus One Android Development] paulk_:
+1

Now that the kernel is stable with good battery life, a little OC would make it even better ;)