yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] Pochemuchka1977:
Strange, the previous 875 runs just fine, this one reboots every 5 minutes ...

I have noticed, that the image size changed from 1996K to ~2250K. What is the reason for this ?
[Nexus One Android Development] sir*mez:
Re: [Kernel - .33.2]intersectRaven's Kernel (new Hybrid AVS) 04/17/2010 11:35am

well I guess ill start my test again. time to recharge.
[Nexus One Android Development] intersectRaven:
This is because I left the debugging options intact. This should help for some people who would like to debug their problems more. :) As for the reboots, I really have no idea why this should happen since the AVS code hasn't been modified from the one last night. :confused:
[Nexus One Android Development] intersectRaven:
Forgot to post the SVS version:

SVS (non-AVS):

http://www.mediafire.com/?jlm2dvtnemm
[Nexus One Android Development] Royan:
@intersectRaven:

Did you see hugonz post over in the Diet thread?

Might help explain a few things about the instability issues...

brgds

Royan
[Nexus One Android Development] Pochemuchka1977:
What I have noticed that this version tries to undervolt the @20 to 1200mV instead of 1225mV that I've seen in previous version. And this I suspect is the reason for instability

And the previous post supports my suspicion as well :-)
[Nexus One Android Development] britoso:
On 2.6.33_AVS-850mV_20100417_0039 now :) AVS+SVS hybrid!!!

Great work.

Fingers crossed hoping 850 works on my phone so I can move to lower voltages!
[Nexus One Android Development] lore2486:
my phone had a random reboot today, and also was behaving weird on phone calls

i get a muted mic without the phone registering it, droped calls (a first for me) and some other random behavior. so its either this new avs+svs or the CM 5.0.6 i have reflashed with the last AVS and will update when i get some testing time.

but great work OP awsome kernel i can say my phone didnt last half a day and now i got 25hrs on my last charge with normal usage
[Nexus One Android Development] britoso:
Got a kernel panic reboot about 20 seconds after unplugging the usb cable.

pastebin of cat /proc/last_kmsg: http://pastebin.com/iVKkfTD4

On the 875V one now :)
[Nexus One Android Development] intersectRaven:
Interesting. Unfortunately, I can't seem to find the code where that config value is used so I can't analyze it further. The commit log only points to the defconfig file. :confused:

*Found it in one file...will see the difference with the N1 source...
[Nexus One Android Development] sthoeft:
I got nightly reboots with the .800 mV AVS Kernel, but it had been stable while I used it. Now I try the .850 mV Kernel.

One interesting thing I noticed with the .850 mV Kernel: I got ~240 MB free RAM. How could this be? I used to have ~190 MB free, but this is enormous!
[Nexus One Android Development] intersectRaven:
Oop! You noticed! :p Don't worry though since it will slowly go down. :p I think it's typical on every kernel even cyan's since this is based on it. :)

*I just finished integrating the changes noted by hugonz. Will release it later after I test if it's bootable. :p
[Nexus One Android Development] intersectRaven:
Updated!

Changes:

- AVS stability fix based on honz' observation

20100417_1756:

Hybrid AVS:

800mV:

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

825mV:

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

850mV:

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

875mV:

http://www.mediafire.com/?3tz3mmjgm5z

900mV:

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

925mV:

http://www.mediafire.com/?gliywyia0tz
[Nexus One Android Development] www1:
This seem to be very stable.

Not reboot now in installing.

I try :)

Can U tell me how people can see voltages? I want to know what voltage is powered.

;)

Thanks for your work.
[Nexus One Android Development] RieGo:
the new kernel with the fix is working very well here for now. I will make a few stability tests and hope it's working. (no avs was really stable for me)
[Nexus One Android Development] intersectRaven:
Really? Have you tried the other AVS kernels before and were they unstable for you? If so, then this may be a breakthrough!!! (we can only hope! :p) Anyways, the command for seeing the voltages is:

adb shell cat /proc/kmsg

;)
[Nexus One Android Development] www1:
I have previous kernel and it's not 100% stable.

For have n1 to work I have to do 20 reboot but after It works.

Today I have upgraded to cyanogen 5.0.6 final and I have to reflash kernel.

No luck.

I have try about 30 reboot but nothig.

Return to non avs kernel.

Now I flash with latest version 925 and working (no wipe)

No reboot.

I retry to flash with 900 and working (no wipe)

No reboot.

Seem very stable.

Now I have to make some stability test.

:)
[Nexus One Android Development] die-hard:
WOW with this last release my N1 work @850mV.

With other yours releases i cant install it because my device freeze on X.

GOOD work bro.
[Nexus One Android Development] RieGo:
almost exactly the same history with my kernel testing! :)
[Nexus One Android Development] sthoeft:
For me the .850 V Kernel seems to be stable and fast and if I check the Voltages they are so low .875 V @15 for example. Thats great!
[Nexus One Android Development] die-hard:
Raven for president...

now also kernel @800mV work for me ;)

I'm very happy because in last days i cnat install it.

<6>[ 13.065582] qmi: ctl: wds use client_id 0x01

<6>[ 13.066131] qmi: ctl: wds use client_id 0x01

<6>[ 13.066497] qmi: smd closed

<6>[ 13.066802] SMD: ch 52 1 -> 2

<6>[ 13.067321] qmi: smd opened

<6>[ 13.068725] qmi: ctl: wds use client_id 0x01

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

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

<6>[ 13.148254] AVS setting V to 1175 mV @15

<6>[ 13.258361] AVS setting V to 1150 mV @15

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

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

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

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

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

<6>[ 13.910766] a1026_bootup_init: starting to load image

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

<6>[ 16.441802] AVS setting V to 800 mV @20
[Nexus One Android Development] intersectRaven:
Very good news indeed!!! If this really was the key to AVS stability, this would be extremely beneficial for power savings! I'll wait for more input though before really concluding that this is stable! So far, it seems promising!!! :D
[Nexus One Android Development] die-hard:
Now we need to stable JIT.

Can u try to make it?
[Nexus One Android Development] www1:
Also I have installed 800 kernel (previous version not work) and It seem to be very stable.
[Nexus One Android Development] intersectRaven:
Woah! 800mV @20?!?! You're running very nice indeed! :D

That is beyond me already! ;)
[Nexus One Android Development] r8zer:
i can also confirm, that this is stable, as before i run your hybrid avs 800 mv would not even boot, now im running 800mv with your latest hybrid just fine.
[Nexus One Android Development] intersectRaven:
More feedback! I demand more feedback!!! ;)

(I am really getting my fingers crossed that 800mV will be stable for everyone and that AVS will be wholly responsible for adjusting voltages soon!) :D
[Nexus One Android Development] r8zer:
do you need any logs or anything let me know.

but i have had copilot running phone calls wifi, u name it, not one single reboot.:cool:
[Nexus One Android Development] intersectRaven:
Not really. I just want to know from more people (especially those who've been unstable before) whether or not the latest release has been stable for them. :)
[Nexus One Android Development] paulk_:
Sweet! I'll definitely try the 800 when I get home later! Usually the 800 won't boot for me, I'll see how the new one does.

The previous 2 versions worked very well for me, light usage (couple of sms, email and a few mins of Opera Mini surfing over 14 hours and I lost roughly 25%.
[Nexus One Android Development] sthoeft:
Really stable but the adb shell cat /proc/kmsg order doesn't show so much any more. While booting it shows the AVS settings, but once booted it doesn't. Why is this?

Looks like this:

E:\Downloads\Android\android-sdk_r04-windows\android-sdk-windows\tools>adb shell

cat /proc/kmsg

<3>[ 120.574493] init: untracked pid 162 exited

<6>[ 163.739990] batt: 58%, 3894 mV, 225 mA (217 avg), 27.8 C, 790 mAh

<6>[ 213.862976] batt: 59%, 3894 mV, 225 mA (224 avg), 28.1 C, 795 mAh

And no AVS settings.
[Nexus One Android Development] acantril:
does the latest one not spam kmsg with voltages ? Just makes it a lot easier to see whats going on if its spamming to the log.
[Nexus One Android Development] sthoeft:
While booting it does spam kmsg, but once booted there is nothing written with AVS settings.
[Nexus One Android Development] acantril:
If this is a intentional change if it doesnt have any negative effects it might be better to switch it on - i guess im not alone in liking the numbers.
[Nexus One Android Development] intersectRaven:
I tested it and it doesn't seem to spam messages on my system anymore. But when I turned my CPU governor to ondemand, the AVS messages started appearing. It may be that your N1 already found its stable AVS "sweet spot" voltages so it isn't changing it anymore or you're on a constant CPU speed so it really has no need to update voltages. (this is also the first time I'm seeing 998Mhz at 900mV on my N1!!!)

It still has the debugging messages but it seems to be a lot less frequent now since it really does appear that AVS has reached stability! ;)
[Nexus One Android Development] Gimpeh:
I too was able to boot into the 800 kernel with no issues as well. Good Job!
[Nexus One Android Development] intersectRaven:
it's really scaling properly now!!! This is great!!! I'm getting so excited by this!!! More reports people!!! :d
[Nexus One Android Development] RieGo:
Well, I got 800mV running now and did a few benchmarks and put it in the fridge for a few minutes (I don't wanna try it longer) to test temperature stability. Everything perfect at the moment! Thank you so much for your work!

I'm looking forward to see the battery difference the next days...
[Nexus One Android Development] sthoeft:
But I find it disturbing that I don't see the AVS settings any more once it booted. I use SetCPU and it's set to on demand and min frequency 245 Mhz and max 998 Mhz. With the older Kernels it kept switching the frequency all the time now nothing.

P.S. it suddenly started posting again... don't know why.
[Nexus One Android Development] intersectRaven:
Well, the messages will only show if AVS detects the need to change the voltage for the frequency. Now that it's "stable" (and I'm really crossing my fingers on this...) there is no more need to update once it finds a "sweet spot" for your N1's voltage. If you want to see them again, try using it in a variety of ways or set your governor to conservative so as to make your N1 use more frequency steps. This should prompt AVS to update. :)
[Nexus One Android Development] RieGo:
<6>[ 911.728179]
<6>[ 987.986968] AVS setting V to 825 mV @7
<6>[ 988.086914] AVS setting V to 800 mV @12
<6>[ 988.127075] AVS setting V to 825 mV @20
<6>[ 988.166778] AVS setting V to 800 mV @7
<6>[ 988.947570] AVS setting V to 825 mV @20
<6>[ 989.007568] AVS setting V to 800 mV @14
<6>[ 989.067687] AVS setting V to 825 mV @20
<6>[ 989.087646] AVS setting V to 800 mV @14
<6>[ 989.107696] AVS setting V to 825 mV @20
<6>[ 989.127746] AVS setting V to 800 mV @9
<6>[ 989.237945] AVS setting V to 825 mV @20
<6>[ 989.267852] AVS setting V to 800 mV @12
<6>[ 989.287994] AVS setting V to 825 mV @20
<6>[ 989.358215] AVS setting V to 800 mV @6
<6>[ 989.377990] AVS setting V to 825 mV @20
<6>[ 989.397979] AVS setting V to 800 mV @6
<6>[ 994.508697] AVS setting V to 825 mV @20
<6>[ 994.553039] AVS setting V to 800 mV @4
<6>[ 995.784301] AVS setting V to 825 mV @20
<6>[ 995.804321] AVS setting V to 800 mV @6
<6>[ 995.974761] AVS setting V to 825 mV @20
<6>[ 995.994384] AVS setting V to 800 mV @7
<6>[ 996.154571] AVS setting V to 825 mV @20
<6>[ 996.174774] AVS setting V to 800 mV @6
<6>[ 996.955352] AVS setting V to 825 mV @20
<6>[ 997.015441] AVS setting V to 800 mV @10
<6>[ 997.165832] AVS setting V to 825 mV @20
<6>[ 997.185607] AVS setting V to 800 mV @7
<6>[ 997.205810] AVS setting V to 825 mV @20
<6>[ 997.265747] AVS setting V to 800 mV @11
<6>[ 997.286041] AVS setting V to 825 mV @20
<6>[ 997.335784] AVS setting V to 800 mV @14
<6>[ 997.396118] AVS setting V to 825 mV @20
<6>[ 997.415802] AVS setting V to 800 mV @14

now thatz nice! :)
[Nexus One Android Development] intersectRaven:
Nice! You're even getting better voltages than mine! I think I'll revert the stability fixes since I'm not the "best" N1 with AVS anymore... :p
[Nexus One Android Development] RieGo:
I'm so sorry for this :D

But doesn't avs turn off on high clock speeds because of your latest fix?

Or did I misunderstand that?
[Nexus One Android Development] sthoeft:
OK, that doed make sence in a way, than the .825 Kernel works better for me because there are no or very few AVS postings. Great
[Nexus One Android Development] acantril:
i dont think thats it, i change the min max CPU to the same values ranging from 256 - 998 and the CPU volts dont change at any point. On old versions it spammed a serious amount.
[Nexus One Android Development] intersectRaven:
It doesn't turn off on high clock speeds. What it does is just limit the maximum voltages you can reach so that even if you have a bad CPU that always requests for voltage increase it will only increase to 1225. It won't affect undervolting further with AVS. :)

Try unsetting it so that it can change freely. On mine the AVS still spams occasionally when CPU usage spike every second. :)
[Nexus One Android Development] www1:
My latest log file.

AVS working very well (I can conferme that It working in other four N1)

<4>[ 62.350036] wl_iw_run_ss_cache_timer : timer stops
<4>[ 62.350585] wl_iw_run_ss_cache_timer : timer starts
<6>[ 65.055114] batt: 96%, 4118 mV, 0 mA (-10 avg), 23.5 C, 1299 mAh
<6>[ 72.846435] AVS setting V to 1200 mV @20
<6>[ 72.866882] AVS setting V to 800 mV @9
<6>[ 73.196838] AVS setting V to 1200 mV @20
<6>[ 73.216888] AVS setting V to 1100 mV @17
<6>[ 73.236694] AVS setting V to 1200 mV @20
<6>[ 73.276947] AVS setting V to 850 mV @12
<6>[ 73.297149] AVS setting V to 800 mV @2
<6>[ 73.357299] AVS setting V to 1200 mV @20
<6>[ 73.477111] AVS setting V to 800 mV @2
<6>[ 73.517150] AVS setting V to 1200 mV @20
<6>[ 73.537261] AVS setting V to 800 mV @9
<4>[ 92.375671] wl_iw_set_ss_cache_timer_flag called
<6>[ 96.759735] AVS setting V to 1200 mV @20
<6>[ 97.010101] AVS setting V to 800 mV @2
<6>[ 103.398864] request_suspend_state: sleep (0->3) at 98832815072 (2010-04-17
12:17:43.412439448 UTC)
<7>[ 103.399566] flashlight_control: mode 0 -> 0
<6>[ 103.400085] flashlight_control: off
<6>[ 103.401916] capella_cm3602_ioctl cmd 1
<6>[ 103.403320] lcdc_blank: ()
<6>[ 103.403625] samsung_oled_panel_blank: +()
<6>[ 103.405364] capella_cm3602_ioctl cmd 1
<6>[ 103.426208] AVS setting V to 1200 mV @20
<6>[ 103.466339] AVS setting V to 1100 mV @15
<6>[ 103.486694] AVS setting V to 1200 mV @20
<6>[ 103.506469] AVS setting V to 800 mV @4
<6>[ 103.626373] samsung_oled_panel_blank: -()
<6>[ 103.629241] mahimahi_ts_power: power 0
<6>[ 103.639709] lcdc_suspend: suspending
<4>[ 103.772796] save exit: isCheckpointed 1
<6>[ 115.299621] batt: 96%, 4118 mV, 0 mA (0 avg), 23.5 C, 1299 mAh
<6>[ 120.032409] AVS setting V to 1200 mV @20
<6>[ 120.232757] AVS setting V to 800 mV @2
<6>[ 125.147399] AVS setting V to 1200 mV @20
<6>[ 125.387756] AVS setting V to 800 mV @2
<6>[ 170.321472] AVS setting V to 1200 mV @20
<6>[ 170.356781] batt: 96%, 4118 mV, 0 mA (0 avg), 23.6 C, 1299 mAh
<6>[ 170.381500] AVS setting V to 1100 mV @15
<6>[ 170.421539] AVS setting V to 1200 mV @20
<6>[ 170.481628] AVS setting V to 800 mV @7
<6>[ 175.416473] AVS setting V to 1200 mV @20
<6>[ 175.556732] AVS setting V to 800 mV @2
<6>[ 180.091003] AVS setting V to 1200 mV @20
<6>[ 180.231292] AVS setting V to 800 mV @4
<6>[ 200.430877] AVS setting V to 1200 mV @20
<6>[ 200.454132] AVS setting V to 825 mV @10
<6>[ 200.471160] AVS setting V to 800 mV @4
<6>[ 220.515350] batt: 96%, 4118 mV, 0 mA (0 avg), 23.7 C, 1299 mAh
<6>[ 230.460174] AVS setting V to 1200 mV @20
<6>[ 230.480865] AVS setting V to 825 mV @10
<6>[ 230.500549] AVS setting V to 800 mV @2
<6>[ 240.149597] AVS setting V to 1200 mV @20
<6>[ 240.259796] AVS setting V to 825 mV @11
<6>[ 240.280029] AVS setting V to 800 mV @2
<6>[ 245.264587] AVS setting V to 1200 mV @20
<6>[ 245.394836] AVS setting V to 800 mV @2
<6>[ 260.489501] AVS setting V to 1200 mV @20
<6>[ 260.512451] AVS setting V to 850 mV @14
<6>[ 260.529632] AVS setting V to 800 mV @6
<6>[ 265.544372] AVS setting V to 1200 mV @20
<6>[ 265.684631] AVS setting V to 800 mV @2
[Nexus One Android Development] intersectRaven:
A few more reports like this and I'm going to declare AVS as stable! :cool:
[Nexus One Android Development] Markdental:
My phone actually booted in to the 800 AVS kernel now. Never would before.

But I am having trouble with the log.

Here is what my log looks like:
[Nexus One Android Development] hah2110:
On what ROM?

I'm disappointed. I upgraded to the version before last 850 last night and left my phone overnight for 8 hours and lost 18% battery life. Screen/BT/WiFi/GPS off... I don't get it. Why do I not get any benefit from these kernels?
[Nexus One Android Development] Markdental:
Oh, and even though I pushed the .ko file first as suggested, I can't get wifi to come up.

Any suggestions?
[Nexus One Android Development] sir*mez:
Is the new release still hybrid? So far on the hybrid before this release, in 4 hours it went from 88% to 83%. I say that's good.
[Nexus One Android Development] intersectRaven:
That log is not with my kernel build. It's with cyan's. :p

Try the latest version. It's the stable candidate not the one last night. ;)
[Nexus One Android Development] intersectRaven:
Yes it's still hybrid. :)
[Nexus One Android Development] hah2110:
What is everyone using to get values now as opposed to adb shell cat /proc/kmsg in command prompt?
[Nexus One Android Development] acantril:
is there any way of seeing what V the CPU is currently supplied with ?
[Nexus One Android Development] intersectRaven:
That's still what they're using. :)
[Nexus One Android Development] hah2110:
Out of curiousity, those of you getting great battery life... what radio are you on?
[Nexus One Android Development] hah2110:
How do you copy of out cmd? Or is everyone extracting?
[Nexus One Android Development] sir*mez:
I also can't see the values now using: cat /proc/kmsg

Edit: this is what I see when I enter:

$ $su

# cat /proc/kmsg

<6>[ 263.898071] batt: 80%, 3957 mV, -113 mA (-194 avg), 33.5 C, 1096 mAh

<6>[ 314.000335] batt: 80%, 3943 mV, -303 mA (-252 avg), 33.7 C, 1091 mAh

<3>[ 363.450134] init: untracked pid 869 exited

<3>[ 363.451324] init: untracked pid 848 exited

<6>[ 364.100677] batt: 80%, 3947 mV, -210 mA (-241 avg), 33.8 C, 1088 mAh

<6>[ 414.364837] batt: 80%, 3947 mV, -207 mA (-191 avg), 34.0 C, 1086 mAh

<6>[ 464.473937] batt: 79%, 3933 mV, -245 mA (-206 avg), 34.2 C, 1083 mAh

<6>[ 475.791320] mahimahi-microp 0-0066: Setting Jogball flash period to 2

<6>[ 492.681762] binder: 632:633 refcount change on invalid ref 10

<6>[ 515.614501] batt: 79%, 3962 mV, -125 mA (-179 avg), 34.3 C, 1080 mAh

<6>[ 565.767730] batt: 79%, 3957 mV, -238 mA (-171 avg), 34.5 C, 1078 mAh

<6>[ 610.889984] mahimahi-microp 0-0066: Setting Jogball flash period to 2

<6>[ 613.760009] mahimahi-microp 0-0066: Setting Jogball flash period to 2

<6>[ 615.895172] batt: 79%, 3947 mV, -189 mA (-152 avg), 34.5 C, 1075 mAh

<6>[ 666.020507] batt: 79%, 3957 mV, -151 mA (-198 avg), 34.7 C, 1073 mAh<6>[ 716.128662] batt: 79%, 3952 mV, -146 mA (-133 avg)

Its acting like its not using avs.
[Nexus One Android Development] DebauchedSloth:
I see AVS messages early in the boot process - then they stop.
[Nexus One Android Development] Pochemuchka1977:
This is awesome version !!!!

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

<6>[ 267.921691] request_suspend_state: sleep (0->3) at 262778393916 (2010-04-1

7 13:04:30.874402439 UTC)

<6>[ 267.921936] capella_cm3602_ioctl cmd 1

<7>[ 267.923187] flashlight_control: mode 0 -> 0

<6>[ 267.923339] flashlight_control: off

<6>[ 267.924224] capella_cm3602_ioctl cmd 1

<6>[ 267.939453] lcdc_blank: ()

<6>[ 267.939605] samsung_oled_panel_blank: +()

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

<6>[ 268.143646] samsung_oled_panel_blank: -()

<6>[ 268.155120] mahimahi_ts_power: power 0

<6>[ 268.160125] lcdc_suspend: suspending

<4>[ 268.265838] save exit: isCheckpointed 1

<6>[ 273.032287] batt: 98%, 4114 mV, 0 mA (-23 avg), 32.1 C, 1342 mAh

I have never seen before my CPU neither on 800mV not on 825mV@20

Thanks you very much !!!
[Nexus One Android Development] intersectRaven:
That's fine! You can see AVS at work there! 875mV at 998Mhz. ;)
[Nexus One Android Development] acantril:
I'm just concerned that the 800mV kernel isnt using AVS anymore since the last update, or is bugged in some way. I'd like to confirm im using a lower voltage its just not changing AT all as my cpu changes, or not spamming that fact. My CPU is changing loads and speeds a lot (using stress tests etc ) and not ONE line of AVS spam.

I'd really like to confirm the voltage some way so i can be satisfied that im going to be saving some power.
[Nexus One Android Development] intersectRaven:
I understand your concern. I don't know of any way though by which to accomplish this. :(
[Nexus One Android Development] MaxiJavi:
Previously I couldn't use anything under 875 reliably.

Now the 800 works for me :

I also get messages while the phone is running that suggest AVS continues to work very well :-) :-)

Thanks for all your hard work :-)
[Nexus One Android Development] intersectRaven:
That's odd. You're exceeding the voltage cap for 245Mhz. And you can reach 128Mhz! What kernel are you using?!?! :confused:
[Nexus One Android Development] Markdental:
Well, my wifi wouldn't work even after pushing the .ko file, so went back to pershoot's kernel and it came back.

Is there a way to check the logs for AVS without going into adb?
[Nexus One Android Development] sthoeft:
I also sometimes see @1 and also the same entrys in the log as sir*mez but only when I am not plugged in and using OS Monitor.
[Nexus One Android Development] intersectRaven:
I think there's a discrepancy with what adb is reporting and what OS monitor is reporting. :confused: