yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] ChronoReverse:
Interestingly enough, the AVS build you made for me is working flawlessly so far. It seems AVS isn't usable for a lot of people's n1's =(

I wonder if HAVS could be modified to combine SVS and AVS a bit further, adding a slight voltage boost offset to the AVS values to increase stability but still use AVS for those where normal AVS is unstable. It mightthe advantage over SVS in that case though and might even be a case by case scenario.

AVS is supposedly more power efficient than SVS right?
[Nexus One Android Development] nenco:
Do you see better battery life with avs?

because svs-925mv is very good anyway, and i have not tried any 128mhz version yet because of 720p
[Nexus One Android Development] musashiken:
Okay... guess I spoke too soon. Phone just died all of a sudden. Couldn't turn it on. Had to take out the battery for it to start up again...

Not sure if it's the new kernel, but I'm back to SVS.
[Nexus One Android Development] fitsnugly:
I was runnign 2.6.35_AVS-925mV_CFS_720p_1113Mhz_081510 with NO issues... but I flashed 2.6.35_AVS-925mV_CFS_AXI_720p_1228Mhz_TEST_081510 this morning and had my phone freeze completely within 10 minutes.

back to SVS as well...
[Nexus One Android Development] RieGo:
That would be great!

my favorite combo would be:

SVS CFS 128-1xxxMHz (AXI|NoAXI) 900mV 720p NoAudioBoost

btw: did anyone notice any benefit of AXI? i only read about negative results in this thread... so why is it in the kernels?

...looks like a new governor scheduler is coming if i see this right (cm's github)...
[Nexus One Android Development] B1ny:
Is by trail and error you become the best :)
[Nexus One Android Development] SimFox3:
I'm having issues with AVS as well. Loops and crashes =/

WildMonks,

Could you please make a NoAB version of 2.6.35_SVS-925mV_CFS_AXI_720p_1228MHz_TEST_081510.zip . Thanks.
[Nexus One Android Development] iamstuffed:
I'd also like a no audio boost version :)
[Nexus One Android Development] ChronoReverse:
It would be interesting to look at the OS log for those of you with AVS problems to see what the settings AVS chose are.

Also, are all of you running more custom ROMs like CM6? Anyone else using the stock Froyo kernel version that wildmonks kindly compiled for me?

Also, I'm using 128MHz-1075MHz only if that helps.
[Nexus One Android Development] poochie2:
@wildmonks

Could we try going under 900mV @ 128MHz? I'm getting awesome battery life with battery left widget (up to 40hours with mild usage and juice defender) and knowing what is the max undervolt possible really strikes me! 1200+ max MHz is also good, one can always set his lowermax freq :-)
[Nexus One Android Development] nenco:
I use the stock froyo rom
[Nexus One Android Development] ChronoReverse:
Did you try the test build "2.6.35_AVS-925mV_CFS_no720p(stockFRF91)_1228Mhz_081510_TEST.zip"? Anything interesting in the OS log?
[Nexus One Android Development] antiochasylum:
That's what I just flashed and works awesome, however the 1228 gets me 32 in linpack and 1190 gets me 40.1 ::shrug::
[Nexus One Android Development] RieGo:
me too! :)

i think it's worth a try to limit only 128MHz to 875mV...

btw: @wildmonks, it seems you're really busy. you should make something like an "online kernel generator" :D
[Nexus One Android Development] Ivan Dimkovic:
Hmm... this looks like max. voltage in board_mahimahi.c (regulator_init_data tps65023_data) is lower than the voltage that 1228 MHz setting asks for.

@wildmonks - could you please confirm that max. voltage in board_mahimahi.c is equal to the voltage needed for 1228 MHz? I am asking because I had this problem few times building my kernels :)

But of course, I might be completely wrong and the reason for your problem might be something else.
[Nexus One Android Development] poochie2:
I'd like to compile my own voltage / freq. combos, I'd need an easy tutorial and wildmonk's repository :-)
[Nexus One Android Development] pakraider:
LauncherPro finally works smoothly on 2.6.35_SVS-900mV_CFS_AXI_720p_1228Mhz_TEST_081510 :)
[Nexus One Android Development] RieGo:
well, here is a nice tut for the cm kernel: http://wiki.cyanogenmod.com/index.p..._I_compile_the_CyanogenMod_kernel_from_source

but afaik wildmonks didn't release his source...
[Nexus One Android Development] antiochasylum:
I don't think so because when I flashed the 8/14 cfs 1228mhz test 925mv no720p aix kernel at 1228 I was hitting almost 41 in linpack. And clicked 1720 in quadrant. So I know its not my phone, however that kernel broke my camera. This new one for stock froyo rom seems to peak at 1190
[Nexus One Android Development] nenco:
I was ok until the battery discharged a little, then os locked and boot loop.

Where can I find os log?
[Nexus One Android Development] poochie2:
No source, no kernel :-)

I'd really like to get, like on computers, to know the lowest stable voltage for every frequency for my phone.
[Nexus One Android Development] mortzz:
This is a little odd, but after flashing 2.6.35_AVS-925mV_CFS_720p_1113Mhz_081510 my lock/unlock sounds have become quite sporadic on CM6 RC3. Sometimes they'll work and most of the time they won't.

Edit: Now that I think about it, it may be a RC3 problem, as I flashed the two at similar times.

Edit 2: After reflashing RC3 the problem went away, so it's definitely this kernel.
[Nexus One Android Development] ewker:
Cheers for all the hard work wildmonks, your kernels are awesome. Hope the paypal donations continue to fuel future releases :D
[Nexus One Android Development] k1rth:
Just threw on 2.6.35-925mV-BFS-AVS-AIX-720p-Monks-081510 with Cyanogen RC3. Works ok but getting random reboots every now and again.

Will keep an eye on it
[Nexus One Android Development] fitsnugly:
Apparently CM's stock kernel in tonight's nightly build fixed the a/v sync issue... hope wm grabs those commits soon :)
[Nexus One Android Development] daveid:
And using the 0810 version of WM's kernel breaks video playback, so an update is needed, can so without video playback till you can update. Unfortunately, I am one who cannot use AVS in it's current state. My phone doesn't like it I guess.
[Nexus One Android Development] navillos:
.34 series just seems more stable to me. Any chance on 34.4 or are you doneat 34.2?
[Nexus One Android Development] mtw4991:
RixKliq, I might have spoke a bit to soon about the audio sync issue.I tested it right away and it appeared to be fixed, but there is still a very slight delay but nothing like before and if you are not looking for it you probably won't notice it but it is there. Also the camera was fc'ing a couple of times when trying to view the video

Reboot solved the problem but that's a pain in the ass.
[Nexus One Android Development] Latentk:
Further info for you to ponder monks, I found that my phone simply could not handle 900mV for whatever reason. I have to use 950mV for it to be stable and last the night. This may be useful info for other people as well. Also, I findthe BFS kernel you just posted (815) to be completely stable and FAST! Wooo! YOu pwn monks!
[Nexus One Android Development] wildmonks:
Wow, leave it to the expert in finding my mistake without even looking at the source! Indeed I forgot to increase the max limit in board_mahimahi.c... This happens to me all the time when I do source sync and I forget to change this setting :rolleyes:. That should solve the symptom antiochasylum is having. It will either give you a higher score if your CPU can handle it or crash it if it can't :p

I see a lot of updates to the kernel source on cyanogenmod. I'll update my source and do a SVS kernel batch release and then work on the requests. Hopefully I'll have enough time tonight to do all this ;)
[Nexus One Android Development] wildmonks:
Update for .35

-Changes since 081510

-Went back to SVS for now.

-mahimahi: Fix the memory layout. (cyanogenmod)

-net: wireless: bcm4329: Increase PMU_MAX_TRANSITION_DLY to 1 sec (cyanogenmod)

-mahimahi: Enable full light sensor range (cyanogenmod)

Link to Kernels

MediaFire Mirror Link
[Nexus One Android Development] antiochasylum:
Awesome find! Remember I'm on the stock froyo frf91 rom. No720p. Donation coming to you monks.
[Nexus One Android Development] cypher21:
Monks, thanks for the update.

I;ve tried all NOAB kernels, and the phone won't boot CM6 on all of them. They give me loops on the X logo or get stuck on the X.

Back to the 20100810 kernel
[Nexus One Android Development] Pochemuchka1977:
+1, same problem :-(
[Nexus One Android Development] Gilg@mesh:
no AVS kernel?
[Nexus One Android Development] Eddiemc:
2.6.35_SVS-950mV_CFS_AXI_720p_NoAB_1113MHz_081610.zip

This one works fine on my cm6 nightly from yesterday. No issues ATM:)

updated from wm 08/10/10 kernel with no wipe..

-e
[Nexus One Android Development] navillos:
2.6.35_SVS-950mV_CFS_AXI_720p_1113MHz_081610.zip

no 720 please can you make them regularly just like the NOAB ones as well. i like audio boost but dont use CM so i have no use for the 720p.
[Nexus One Android Development] wildmonks:
I suspect some of the changes I added from cyanogenmod kernel source is now conflicting with stock FRF91. I'll have to investigate this further. Ultimately, I might have to fork my source for CM6 and stock Froyo based roms.
[Nexus One Android Development] Gilg@mesh:
I've got several reboots with 2.6.35_SVS-925mV_CFS_AXI_720p_1113MHz_081610.zip, don't know why but with AVS it didn't happen.
[Nexus One Android Development] daveid:
I am running the latest CM nightly, not stock...
[Nexus One Android Development] flak0:
@monks can you please post a 1228mhz SVS with AIX 720p and 128mhz min at 900mV. Thanks. Donation comming your way.
[Nexus One Android Development] Vlad83:
Whats NoAB?
[Nexus One Android Development] EarthsiegeTA:
No audio boost.
[Nexus One Android Development] uoY_redruM:
Well, I'm pretty sure I can say that AIX is working well for me. I'm running, if I'm not mistaken, the AIX_AVS_CFS from 8/8 still.

I finally decided to step it up a notch and keep my phone on without charge for a full day. I USUALLY charge it every time I walk in from work, regardless if its at 90% or 40%. Yesterday (8/16), I unplugged it in the early morning and did not charge it at all. I used it moderately, not as much as I generally do for surfing the web but I definitely used it enough.

This morning, my alarm went off and woke me up for work.

1d, 5h 38m later, look at my battery results...(pictures attached)

Great job WM!
[Nexus One Android Development] Latentk:
Gilgamesh, some phones do handle AVS batter than SVS, and some phones handle SVS better than AVS. Its interesting how different each phone acts, but thats the way it is.

I have been running 815 BFS 950mV for an entire day and it is superb. I am not entirely confident in the battery life, I disabled both my LWP and my GPS and I seem to have greater drain than with them turned on? I will investigate further. BFS is so fast, LOVE IT MONKS! Now that I've been paid, donation coming your way!
[Nexus One Android Development] onesavior:
Crazy random crashes at first, But seems to be fine now, super fast, no notice on battery yet, which leads me to ask about display, what would you recommended? I am always going outdoors to indoors so I leave it on auto ( knowingly draining battery faster)
[Nexus One Android Development] Vlad83:
Thanks... Didn't realize he shortened it lol
[Nexus One Android Development] SheridanJohn:
Hi wildmonks,

I love your kernels as they really give terrific battery life and stability!

I was using AVS-080210 with some pre-RC3 nightly for quite a while and only had the small issue that sometimes over night my WiFi profile would go to deactivated and sometimes my 3G won't reconnect until I switch to airplane and back.

After upgrading to RC3 I got really bad bat-life with stock kernel.

I tried AVS-081510, both 925 and 950 mV to no avail: freezes right after boot or sudden reboots during boot.

Now, I am giving the SVS-081010 in 925 a try, looks good so far!

Thanks for your great work!
[Nexus One Android Development] flak0:
bump bump bump
[Nexus One Android Development] MicroMod777:
Wildmonks, seems Enom did an update to for the HTC 720p Cam, which now breaks under your kernels. Can you please update a new kernel for the fix he made.

Here's what Enom said;
[Nexus One Android Development] wildmonks:
You'll find your requested kernel here in the "Custom Variants" folder.

Now working on other requests made by others and I'll let you know when its been uploaded.
[Nexus One Android Development] wildmonks:
Uh, oh.. I got lucky with that other fix. I'll work on it on my next day off.
[Nexus One Android Development] wildmonks:
Your kernel has been uploaded to the Custom Variants folder.

I can probably create a small set of no720p kernels next time (maybe 950mv with CFS and BFS). I'd perfere to keep that set variations small. I can't make another full set of 8 kernels for 720p without going crazy lol. Really though, that would make it 16 kernels per release and I'm sure to get all the labeling mixed up (I already am with incorrectly direct linking to kernels and mislabeling some custom kernels that some of you have kindly pointed out).
[Nexus One Android Development] ChronoReverse:
wildmonks, you may have to reduce the set of kernels you're making before you go crazy lol.
[Nexus One Android Development] wildmonks:
Really I might :p. Yah I gotta think about it. It's eating up my time that I already have so little of reciently :rolleyes:
[Nexus One Android Development] wildmonks:
I kinda, sorta have posted my source. You'll find it at the bottom of the OP. I'll try to regularly update that link whenever I can.

I'll probably be moving away from .34. I don't think I have the time to update both 34 and 35 kernels. You should be able to find other quality updated 34.4 in this forum. ;)

I don't see any specific commit(s) for the kernel on cyanogenmod github that would address the audio/video sync issue. Unless it has something to do with the new BFQ scheduler. I have already integrated this into my source but haven't had the chance to fully test it out.
[Nexus One Android Development] nenco:
can't nobody make a script for you to build all version in one time?
[Nexus One Android Development] flak0:
@monks I may be dumb but is BFQ a replacement for BFS/CFS? Can I test it for you?
[Nexus One Android Development] ayoRad:
Is there a kernel to fix the 720p video/audio lag on cyanogen cm6 rc3? Thanks for your work by the way
[Nexus One Android Development] MicroMod777:
Well, after further testing, your Kernels seem to be working now. Don't know what happened. :D
[Nexus One Android Development] musashiken:
Hmm I seem to be having freezes once in a few hours with the recent kernels. Back to the 081010 svs for me...
[Nexus One Android Development] daveid:
What can I do to help debug what is going on for some of us with the latest nightly builds not being able to use any of your kernels? The last one that actually boots for me is from the 0810 series of SVS. I just tried the SVS 0816 and caught a boot loop with it upon initial boot, second boot got stuck at the lockscreen for quite some time, but eventually got me to my desktop. Though, I had some ANR's going on and a lot of "08-18 08:21:23.482: ERROR/dalvikvm(953): Failed to find cpu subsys" in the log. Once booted it seems fine, so I will let it run today and see if anything odd happens.

What logs can I provide, or testing can I do?

I thought these were SVS kernels, is something wrong? When I do a cat /proc/kmsg I see 1000s of repeating AVS setting V to XXX @XMHz, which leads me to believe that AVS is operating and being wonky (it is constantly in a state of flux when the phone is awake, however it seems to calm down when it goes to sleep).

This really sucks for me, as I can't stand the audio boost in the stock CM kernel. I am going to try the 0810 again (last I tried I couldn't play back any videos properly).

Is there a recent kernel of yours with no audio boost and SVS, did I over look it? Or are you only developing AVS kernels? Ok, so further testing seems to dictate to me that all your kernels are AVS now (right?, I mean even the installer script says AVS). I have installed and tested both NoAB SVS CFS kernels, the standard 925 CFS kernel, and one BFS NoAB, the last SVS kernel I can find is the 0810 series.
[Nexus One Android Development] trismegistos:
hi wildmonk,

2.6.35_SVS-925mV_CFS_1113Mhz_081010.zip is a nice kernel... go ahaed with this good work!
[Nexus One Android Development] christiankk:
Goes for me too.
[Nexus One Android Development] evilive27:
Me too. None of the new ones go above 1152 for me. Even that slows down after hours of being on. O the old 081010 works perfect at 1228 and stays fast all day. Weird I know
[Nexus One Android Development] ChronoReverse:
You should probably delineate exactly what you're going to build then. Maybe deprecate the .34 builds after getting a set that seems stable so people can go back if they want to.

The list of builds even with .35 is pretty long with the various voltages, schedulers and such:

CFS BFS

925mV 950mV

AVS SVS

no720p 720p

AB noAB

1113MHz 1228MHz

That's 64 variations if you do them all!

BTW, for the no720p builds, who would be using the non-stock-frf91 versions?
[Nexus One Android Development] wildmonks:
That latest kernels are dated 081610 and its using SVS. Sorry, I haven't updated the OP but you find the links in this previous post.

I'm currently still on RC3, I have't tried any of the latest nightlies so maybe that's why I haven't experienced any crashes. I'll try to update my phone to a nightly the next chance I get.
[Nexus One Android Development] wildmonks:
No one now I hope. Just those users that staying on cm6 rc1 and rc2.
[Nexus One Android Development] damanrico:
Haha, 64 versions is sick. And that doesn't even include custom kernels.

Maybe you could create 1 final .34 batch, 720p/no-720p, cfs/bfs, AB/noAB, Stock/CM/Enom, etc.

That way everyone can fall back to a kernel that works for him/her, but miss out on the latest kernel tweaks.

After that you could pick 1 type of kernel that you will keep on creating (most likely CM .35, 720p, cfs/bfs, AB/noAB). Maybe even stick to 950mV only if too many people have problems with 925mV.

If you stick to 1 mV version you 'only' have to create 4 versions.

I'm amazed at how long you can keep up creating kernels at this rate, but for your own best you should really cut down on the amount of kernel versions.
[Nexus One Android Development] daveid:
I grabbed the kernels I am speaking of from that 0816 folder on your media fire account. They all are using AVS, unless I am completely mistaken... I even noted that the installer script says HAVS, not SVS.
[Nexus One Android Development] loganno:
but as the kernel with 1228Mhz?
[Nexus One Android Development] ChronoReverse:
Indeed. Perhaps the list could be pruned down to something like this (with the custom stuff being when you have more free time:

CFS BFS

AVS SVS

AB noAB

no720p(stock frf91) 720p

950mV

1228MHz

This would "only" be 16 combinations lol.

I'd miss the 925mV build but I'm sure the battery life difference is probably minimal.

As for 1228MHz, it can only be set deliberately (I ALWAYS set to 1075MHz) so it seems a strict warning about it ought to be sufficient.
[Nexus One Android Development] wildmonks:
Omg, your right, its still AVS... that's what happened when one is up late at 2am compiling kernels... I will redo it when I get home. Thx for catching this.
[Nexus One Android Development] daveid:
No problem, I was banging my head against the wall trying to figure out what was going in when it struck me to watch the kmsg output.
[Nexus One Android Development] sl8125:
I am having some issues with wm kernel currently on cyanogen nightly rom with 2.6.35 abs 950mv cfs axi 720p1228 081610. My problem is when phone is asleep about hour or so it wont wake up when i try to use the phone. I have to pull battery and reboot. It is over clocked to 1190 mhz and underclockat at 284 mhz ondemand setting using setcpu. I tried the couple of other wm kernels. Still the same. I am sure its setcpu. When i do not have it of or ic it works fine. At what is the lowest mhz you can set without having the phone asleep completely.
[Nexus One Android Development] damanrico:
It's probably the kernel. People have been setting their minimum to 128Mhz and haven't had problems. I'm having it set to 245 ondemand and it always works.

The reason why it's the kernel is that the new AVS system doesn't work correctly on a lot of devices. The CPU gets too little voltage, and that makes the phone freeze.

Please try a SVS kernel dated 0810 or earlier. You will probably notice the phone won't freeze. Or wait till wildmonks creates new SVS versions.
[Nexus One Android Development] ChronoReverse:
The next time wm posts a set of kernels with both an AVS and SVS version, I'm going to compare and see if there really is a battery life savings between them.

CFS no720p(stock frf91)

Has AIX done anything for anyone btw?
[Nexus One Android Development] mescieux:
I just wanted to report that 2.6.35_AVS-925mV_CFS_AXI_no720p(stockFRF91)_1228MHz_081610.zip from the custom variant folder has been working great for me.

Running Enom's Rom with stock camera(hence no 720p). SetCPU set to 1113max 245min interactive.

Only had one freeze while tinkering with setcpu. Other than that it's been pretty flawless and stable for roughly a day. Amazing work and thank you so much wildmonks!
[Nexus One Android Development] sl8125:
Thanks. I tried every setting i could think of in setcpu. I will try the other kernels.
[Nexus One Android Development] wildmonks:
For me I do see a difference between a kernel using (925mV AVS AIX) vs a kernel using (925mV SVS no AIX) with AVS having less drain then SVS.

This will be my number one priority tonight, making a new set of SVS kernels and AVS kernels (8 variants each). I'll toss my current source and rebase from IR github. And I'll immediately post the full source too.
[Nexus One Android Development] damanrico:
Sounds like a busy evening for you sir. :p
[Nexus One Android Development] wildmonks:
I'll take it slow, and drink lots of caffeine ;) no work tomorrow for me.
[Nexus One Android Development] fiftyclick:
You are the man!
[Nexus One Android Development] navillos:
sweet! donation coming your way
[Nexus One Android Development] Drew474:
Been using your kernels for a while @wildmonks. Although hadnt used them in a while until 720p got sorted out on enoms.

So went from stock enom 720p kernel to your .35 and battery life was sooo much better.

Keep up the good work, been keeping a keen eye on developments so far.
[Nexus One Android Development] ChronoReverse:
As a quick completely unscientific anecdote, using the power draw widget shows 4mA draw with your kernel with the screen off compared to 5-7mA for the "competitors" (pershoot, IR) ;):D:p
[Nexus One Android Development] B1ny:
Its this SVS or AVS?

It is working great for me, none of the other AVS have I have tested have.

And I have tested 900mV/128MHz against the standard CM6 nightly kernels several times now, and each time I get around 1% consumption on the standard kernels vs 0.5% on your 900mV/128MHz ones.

2.6.35_SVS-900mV_CFS_AXI_720p_1228MHz_081610.zip
[Nexus One Android Development] ChronoReverse:
Trying out a pershoot kernel to check.

NVM, same thing happens. I might have to go back to the ROM I was using before to check now.
[Nexus One Android Development] antiochasylum:
I'm on stock frf91 and I was doing fine, but now I seem to be having random freezes, and random reboots :/ I guess the 1228mhz jacked up my phone :( any thing I can do?

edit: Resorted back to nandroid with a 7/17 2.6.35-rc5 kernel. It seems to be super stable at the moment till more things get worked out with newer kernels.
[Nexus One Android Development] Latentk:
Sadly we run that risk with these kernels. Taking the CPU much higher than intended. Try reapplying the newest kernel, or going back to the 811. If that fails try another kernel (ir or pershoot).
[Nexus One Android Development] ChronoReverse:
IR mentioned something about a new (and fixed) wifi driver. I suppose that is something you'd automatically incorporate since it's from the Android repositories?