yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] poochie2:
I'll be ready to try the new voltage, but never mind the 128 MHz if there seem to be reasons not to do so :)
[Nexus One Android Development] ChronoReverse:
Hmm, IR just pulled all his AVS kernels. Does this affect yours at all?

I haven't encountered any issues with the non-RC .35 CFS 925mV kernel.
[Nexus One Android Development] flak0:
@ Wildmonks, so yeah IR pulled all AVS Kernels and he states "As for those who asked how far this has been present, all versions of AVS are affected. It seems as if the reason why it's been stable is because IT WASN'T SETTING VOLTAGES!!! " So that means that AVS has not worked and we were still seeing advantages in battery life, I can only imagine what we will see upon AVS being fixed. SVS works though.
[Nexus One Android Development] daveid:
For me, even if it is not adjusting the voltage it is a great kernel. I get 1%/hr drain when idle, and I don't have the stupid audio hack for deaf people (which is the #1 reason I use a WildMonks kernel anyway).
[Nexus One Android Development] flak0:
So can you imagine the benefits we will gain once AVS is working. See I thought something was weird about AVS as I noticed the voltage never changed in the logs the way "Setting V to" was always scrolling through the dmesg. or " cat proc/kmsg
[Nexus One Android Development] THATTON:
I know, I just read that in the other thread too. Crazy right? I am still a fan of both of these guys' work and I can only imagine what we will see with real AVS working?!!!
[Nexus One Android Development] flak0:
Well whats cool literally is AVS is not working. I am set at 245 - 1075mhz and my temps are 23. 9 C. Lowest they have got in a long time (almost since the idea of UV Kernels on the N1). Battery is at 82% and I disconnected at 12p with moderate use.
[Nexus One Android Development] wildmonks:
Wow, so I was reading this as I was driving home, quite a big revelation!:eek: So then I'm not quite sure what the future is with these kernels. With the AVS code out of the picture, then its not necessary to use the code I've added to keep it stable for overclocking, which makes these kernels pretty much the same as pershoot's. I think now I can only be of use to you guys by continuing to fulfill requests like no audio boost and stuff. What do you guys think?
[Nexus One Android Development] uoY_redruM:
As I've said many times before, I know nothing about kernels but I had a question when I heard about this. If the AVS wasn't scaling the voltage, does that mean that the overclocking up to 1267 immediate crash could possibly be caused due to lack of power?
[Nexus One Android Development] fitsnugly:
BFS 1190 ftw
[Nexus One Android Development] wildmonks:
It mostly means that AVS wasn't adjusting the voltages dynamically and instead it just set the voltages to a static voltage just like SVS.

As for the 1267MHz crashing question, at speeds above 1075MHz I totally bypassed the AVS code so AVS wasn't involved in that. And well it crashing at 1267Mhz, feeding more voltages would make it more stable but that really puts a danger to your CPU so I'm a big opponent of feeding any more voltages then what I am already.

Lol, well, that I can continue to provide in SVS flavor :D
[Nexus One Android Development] SimFox3:
wm, you have a total of '404' posts =)
[Nexus One Android Development] wildmonks:
Lol! Thx for pointing that out, major geek creds to you.:p

Reminds me of podcast show of the same name that I listen too daily.

Well I guess for now I'll continue to make 1190 flavor kernels and fulfill the request for 850/875mV kernels for poochie2 and then see what I can do with 720p support.
[Nexus One Android Development] codesplice:
lols not found ;)
[Nexus One Android Development] daveid:
Whatever you do make at least one version with no audio hack, and I will gladly donate to you after my vacation (tight on money) next week. I really cannot stand the audio hack.
[Nexus One Android Development] uoY_redruM:
Hey man, you have a follower here. I'll continue using your 1190 kernels. Well, right now I'm not because 720p isn't working...but once that's on, I'm back to WM Kernels all the way! :D
[Nexus One Android Development] wildmonks:
Ah, sure no problem! Please don't worry about donating, remember it's purely optional and certainly I don't want to put financial strain on anyone :o
[Nexus One Android Development] waylo:
Is there some app or setting (aside from following the dmesg logs) that will reveal the voltage being supplied at that moment?
[Nexus One Android Development] wildmonks:
I don't believe so. I think the only way for sure is to open up the phone and connect it to a voltage meter.
[Nexus One Android Development] SimFox3:
WildMonks, intersectRaven is recalling his AVS kernels. Are you going to follow suit? =/
[Nexus One Android Development] wildmonks:
After I release the next set of kernels, I'll be moving all the AVS kernels to the archive and then rename the thread appropriately.
[Nexus One Android Development] SimFox3:
This is a sad day indeed :(
[Nexus One Android Development] ChronoReverse:
I wouldn't give up entirely, IR's post seems to indicate that it's a fixable problem.
[Nexus One Android Development] bigmase521:
+1 In fact he's already got a Test Kernel up w/ the new AVS mods.

Back in business (I/we hope)! :D
[Nexus One Android Development] damanrico:
Please keep making kernels. In addition to my weird wifi problem, my phone can also not handle pershoot's kernels. They keep boot looping on me, even on fresh installs, with every possible ROM out there. Even a fresh CM 5.08 flash, which has a kernel with pershoot's kernel tweaks boot loops on me from minute 1.

I have no clue why that is.

So basically my phone can only handle the stock kernel, and yours and IR's kernel.

I can't wait for 720p support on your kernel, since the stock CM 6 Nightly kernel is also boot looping on me (probably same tweaks as pershoot uses), and using your current kernel results into having a non-working camera.

Keep up the great work.
[Nexus One Android Development] atomizasser:
Incorrect message sorry
[Nexus One Android Development] daveid:
Is there any chance of getting a kernel with the latest CM updates, to fix the camera, with no audio boost, even if AVS is not working/included?
[Nexus One Android Development] mtw4991:
I'm not a coder, developer or anything else of much importance, but I can test, fail, recover, test, succeed, etc and I can tell you one thing WM; even if AVS was really only SVS in different clothing, there was something there that was working EXTREMELY WELL as far as battery life goes+benchmarking+stability+your excellent responsiveness/willingness to help others and humility. It is rare to see these days in a world of "when, when, when, me, me, me".

I for one really appreciate your work and have permanently moved away from Pershoots and IR's kernels in favor of yours due to your attitude. And I'm not bashing those guys either, I really respect them fyi. You just have the whole package.

Ramblings are done for today. Thank you and keep up the good work!:)
[Nexus One Android Development] Ivan Dimkovic:
Actually, AVS was not SVS either - because in case you enabled AVS you would get to a "dummy" voltage regulator function (practically dummy, because it would always fail due to uninitialized I2C client variable called "tpsclient")

I actually found it when AVS changes rendered my phone much slower if I enabled overclock, which motivated me to dig deeper - apparantly, what happened was that my phone was stuck at 1.225v (boot voltage) and forcing it to 1.1 GHz would triger unexpected slowdowns...

Anyway, my opinion on this is that this just shows that undervolting brings very little to the overall battery life, as the biggest consumers are display and GSM/3G radio - most likely application pattern does influence life much more than any savings achieved by undervolting.

That is not to say that we shouldn't make AVS work - we definitely should. Even if it does not bring huge gains in battery life, it would make phone run cooler (and possibly CPU would last longer, if that is important at all in practice)
[Nexus One Android Development] intersectRaven:
I just finished modifying the tps65023 function I added in the previous version of AVS (which didn't work) to get the tpsclient device. Should be an interesting test if it will be stable or not. :p
[Nexus One Android Development] Eddiemc:
Please make anything that will work on cm nightly, without audioboost..

I'm hooked on cm, and I've been using your no audioboost kernels since day one.

Unfortunately due to the 720p inclusion in cm, your kernel breaks the camera. Please please please create something.

I'd rather have a broken camera than that audioboost, but i do miss the opportunity to take photos:)

Regards -e
[Nexus One Android Development] wildmonks:
Cool! I guess there was a lively discussion when I was away :).

Well.. try as I might, I could not get 720p working with the .35 kernels but I can get .34 with 720p. There must be something I'm missing so I'll trace back slowly and see if I overlooked something but for now I'll have to use .34. If you guys want to try out the .34 kernel with 720p, you can grab it here. (BFS version will be posted soon in the same folder). Its currently using SVS only but I'll re-add the latest AVS code tonight after work.

@IR

Nice! I'll update the AVS code and compile as soon as I can tonight. Thank you IR and Ivan for all your hard work and skillz! Really respect your knowledge ;)

@daveid & Eddiemc

okay, just saw your request. I'll start making a no boost version right now and post in the same folder.

@poochie2

Sorry, I didn't forget about you I'll try and post your request using the .34 kernels as soon as I can.
[Nexus One Android Development] fitsnugly:
*****in' :)

EDIT: Flashed BFS version, having all sorts of lag... SetCPU short benches were over a second (use to be 150ish ms)... flashing CFS version now...
[Nexus One Android Development] damanrico:
My phone freezed when using the latest kernel while having the video camera open and scrolling through it's settings.

Also, and this is a big one, when you set 1152 or 1190 Mhz the phone slows down to 5-10 MFLOPS. It's like the kernel isn't correctly set to use these Mhz settings. Everything up to 1113 Mhz works fine, I even got 44 MFLOPS while setting my max to 1075, while I only got max 40.3 with the latest 35 stable kernel. So the kernel seems very speedy.
[Nexus One Android Development] SimFox3:
I was just going to "+1" the .34.1-SVS-NoAud but noticed that you JUST uploaded. Thanks =)
[Nexus One Android Development] fitsnugly:
Twas my problem too... I had to at 1152 from boot. scaled down, and it's much less wonky.
[Nexus One Android Development] wildmonks:
Hmm.. confirmed. Looks okay at 1113Mhz. Investigating...
[Nexus One Android Development] wildmonks:
DOH! Found the problem. It wasn't setting the 1300mV voltage @ 1152MHz and up. This means I have to recompile the whole set.... sigh....
[Nexus One Android Development] fitsnugly:
Hug?

10chars
[Nexus One Android Development] mtw4991:
WM, this doesn't support the 720p video recorder....yet, right?
[Nexus One Android Development] damanrico:
It actually does.
[Nexus One Android Development] damanrico:
:(

I've finally remembered to donate again, so at least you can get yourself some fresh orange juice while you're recompiling. :p
[Nexus One Android Development] mtw4991:
Really? CM6+720p+1190oc'd? SWEET!

This one right?:

2.6.34.1_SVS-925mV_CFS_1190Mhz_720p_TEST_080510.zip
[Nexus One Android Development] wildmonks:
Thank you damanrico! The orange juice will probably help replenish the hair on my head as I was ripping it out in frustration when trying to get .35 + 720p working last night :D

Yah, hopefully 720p is working (haven't fully tested it yet) and its only on the .34 version of the kernels...

Okay, upload complete. Both CFS/BFS & no audio boost versions are up. Hopefully these work ok. Next goal is to add back in the new AVS code and do a general release but that all for tonight. For now gotta run to work!
[Nexus One Android Development] SimFox3:
WM, Thanks you're the best!! =)

I'm getting some weird error messages with latest 925mv-BFS-SVS-NoAud

<3>[ 2135.092315] acpuclock: Unable to drop ACPU VDD from 1175 to 925 setting rate to 245000.

<3>[ 2135.782989] acpuclock: Unable to drop ACPU VDD from 950 to 925 setting rate to 245000.

<3>[ 2139.906982] acpuclock: Unable to drop ACPU VDD from 1225 to 925 setting rate to 245000.

<3>[ 2145.142089] acpuclock: Unable to drop ACPU VDD from 950 to 925 setting rate to 245000.

<3>[ 2150.277069] acpuclock: Unable to drop ACPU VDD from 950 to 925 setting rate to 245000.
[Nexus One Android Development] wildmonks:
I remember seeing those a lot when I was compiling SVS for myself way back in days. When I move back over to AVS, those should go away hopefully...:rolleyes:
[Nexus One Android Development] damanrico:
The latest version (2.6.34.1_SVS-925mV_CFS_1190Mhz_720p_TEST_080510.zip) is giving me contast boot loops.

It won't even load till the CM boot logo, it keeps being stuck at the X with unlock logo. Pulling battery and trying again won't help, it keeps being stuck.

Anyone else having this problem (please check filename of the kernel before saying yes/no).

EDIT: FYI, this also happens to me using IR's latest version.
[Nexus One Android Development] Stanleypain:
Same, exact problem here. Had to do a nandroid restore to get back up and running.

I'm not running any custom rom though. Stock, rooted Froyo + latest radio.
[Nexus One Android Development] wildmonks:
By chance were you 2 using the 1190MHz setting (previously or currently)? I suspect the 1190MHz setting is the cause as I have seen boot loops when using that speed (which leads me to conclude I can't run 1190MHz on my phone).

I'm limiting myself to 1113MHz on this CFS Test kernel and its working normally so far.
[Nexus One Android Development] damanrico:
Nope, limited myself to 1075Mhz before I flashed the new kernel.

Here's what happened:

- Wipe cache, wipe dalvik cache, flash CM nightly, flash your latest kernel.

- I manually click on reboot phone. This all went fine till now.

- Phone makes its initial boot, the X with the unlock logo at the bottom, after a few seconds it reboots, BEFORE it even showed the CM boot logo.

- After this reboot it keeps being stuck at the X with the unlock logo. I've let it be stuck for over 5 minutes, it just keeps being stuck (no more reboots).
[Nexus One Android Development] wildmonks:
Weird that I'm not getting this...

(I'm on the Cm6 nightly 08052010, flashed without wiping)

What I'll probably do is rebuild the entire .34 kernel, then add in the 720p driver. Boot loops are notoriously hard to pinpoint the cause....:(
[Nexus One Android Development] damanrico:
I'm on the same nightly (there have been 2 today, i'm on the latest one).

I flashed back to the stable .35 kernel, and things are working fine again.

I don't know what more to tell you, the first 720p kernel you released today, the one with the 1152 and 1190 Mhz problems, worked fine for me.
[Nexus One Android Development] wildmonks:
I'm on the first nightly with that date.

As for the previous test kernel being stable, maybe I'll just revert back to that
[Nexus One Android Development] waylo:
Hey WM, can you help clarify what the error has been in AVS implementation?

If it wasn't working properly, why were there still multiple "AVS setting V to xxx mv @ xxx Mhz" entries in dmesg?
[Nexus One Android Development] wildmonks:
Avs was trying to set to those voltages but it wasn't being applied by the voltage regulator.
[Nexus One Android Development] pzumk:
2.6.34.1_SVS-925mV_BFS_1190Mhz_720p_TEST_080510.zip is the latest for the nightly cam fix, right? Flashing it..

Edit // ah, a site ago. Ok
[Nexus One Android Development] mtw4991:
xPartiick,

Did you flash it, and if so, how is it working for you?
[Nexus One Android Development] Eddiemc:
How are the .34.1 test kernels compared to cm6 latest?

Is cm kernel .35?

If they are very different (I'd assume cm kernel has some cm6 special changes), is it possible to recompile cm6 to loose the audioboost?

You could call it cyanomonk;)

Sorry to nag about this, but latest cm6 runs great for me atm, I just have issues with the audio.

-e
[Nexus One Android Development] B1ny:
2.6.34.1_SVS-925mV_CFS_1190Mhz_720p_NoAudioBoost_TEST_080510.zip works great on latest nightly. Thanks a lot :)

Have been losing a lot of blood through my right ear, during the last 24 hours with the standard kernel :(

You have saved me having to go get a blood transfusion.
[Nexus One Android Development] SimFox3:
LOL i lose a lot of blood too on the standard kernels... and yes, the BFS-SFS-925mv is so far rocking great. I'm seeing some exceptional battery life with this one.
[Nexus One Android Development] HTCDevil:
Anyone tried last test 2.6.34.1 kernel on a stock FRF91?

There are 2 version on mediafire (one is 3.25MB and the other one 3.26). Which one have you choose?

Thanks guys and wildmonks (i've always flashed your kernels only) ;)
[Nexus One Android Development] wildmonks:
Thanks HTCDevil :)

I'm curious about this too. I'm hoping they are compatible. BTW: posting new kernels in the next few minutes ;)
[Nexus One Android Development] wildmonks:
Update for kernel .34.2

Changes since 073010

-Reconstructed source from CyanogenMod Github (So now you have 720p support for the latest nightlies :))

-Added BFS code from IR's Github

-Added latest AVS code from IR's Github but had trouble with stability. For now AVS is disabled.

-Dropped 800mV setting. Was unstable for SVS operation.

-Some users may experience boot loops with 925mV kernels. 950mV kernels may alleviate this so they are provided.

-UTF-8 has been enabled for unicode support

2.6.34.2_SVS-925mV_CFS_1113Mhz_080610.zip

2.6.34.2_SVS-950mV_CFS_1113Mhz_080610.zip

2.6.34.2_SVS-925mV_BFS_1113Mhz_080610.zip

2.6.34.2_SVS-950mV_BFS_1113Mhz_080610.zip

2.6.34.2_SVS-925mV_CFS_1113Mhz_NoAudBoost_080610.zip

2.6.34.2_SVS-950mV_CFS_1113Mhz_NoAudBoost_080610.zip

2.6.34.2_SVS-925mV_BFS_1113Mhz_NoAudBoost_080610.zip

2.6.34.2_SVS-950mV_BFS_1113Mhz_NoAudBoost_080610.zip
[Nexus One Android Development] damanrico:
You're right. The 925mV version still give me a boot loop, while the 950mV version boots just fine.

Thanks for the quick kernel update.
[Nexus One Android Development] wildmonks:
I had a feeling this was the case. I spent a great many hours coding with SVS tonight and learned a lot of stuff from it and why pershoot use the settings he used with his SVS kernels. :)
[Nexus One Android Development] Eddiemc:
Thanks a lot mate. I justed flashed your last. 34.1, and its nice and stable, but now I'll try this:)

Keep up the good work.

-e
[Nexus One Android Development] damanrico:
Bad news:

- Phone worked fine after first boot, even when doing an extra reboot.

- After that it was on for 5 more minutes, with screen off.

- Tried to wake the phone, but it didn't wake. It kept being dead for over 3 minutes, after which I pulled the battery.

I'm using the CFS 950mV NoAudioBoost version.

Setcpu settings: 1075/245 interactive, 460/245 interactive when screen off.
[Nexus One Android Development] wildmonks:
Thanks for reporting this.

I'll look into this and see what I can do. Interesting that this occurred with that kernel. It's possible I compiled one incorrectly...
[Nexus One Android Development] damanrico:
Do you want me to try the same one with audio boost?
[Nexus One Android Development] wildmonks:
If you have time, yes. If the problem is still present then it probably something I added to all the kernels that's the cause. If this is the case, I suspect the HAVS code as its still present but not being actively used. HAVS and BFS are the only 2 major additions I did to the stock cm6 kernel or it could be the stock cm6 kernel as pershoot has stated...
[Nexus One Android Development] damanrico:
Well it's not a reboot for me. My phone just acts dead. No matter what way I try to wake my phone, it just keeps being dead. Like there's no battery present.

Testing the audio boost version atm.
[Nexus One Android Development] daveid:
925 No AudioBoost working here (booting up at least). Thank you for this, I leave for vacation at 2PM today (after a half day of work) so this is my last morning for messing up my phone. Just flashing the latest nightly and your kernel now, should keep me happy!
[Nexus One Android Development] damanrico:
This time it would work for about 45 minutes. After that my phone appeared to be dead again.
[Nexus One Android Development] antiochasylum:
I'm still on your 7/17 1190 cfs kernel lol, seems to be working the best for me, entirely to many bugs with all this new stuff. I'm waiting till non RC with cyanogen as well as .35 editions with 720p. My gf already hates my nexus enough so i had to stop flashing all the time. Lol. Keeps my phone stable and keeps me off it sadly.
[Nexus One Android Development] pzumk:
Yes and its working fine
[Nexus One Android Development] THATTON:
Has anyone tested on Enomther's ROM yet? With 720p?
[Nexus One Android Development] monkeydrufy:
Hi guys,

I can use this kernel with official froyo 2.2?

if yes, does 720p recording work?

thanks
[Nexus One Android Development] RieGo:
yes and yes (only 34.2)

try your luck

I'm currently running 925 mV with no problems so far.
[Nexus One Android Development] THATTON:
720p will not work with official froyo. Only a rom that has it "built-in".
[Nexus One Android Development] wildmonks:
I'd like to get to the bottom of this so if you can, give this test kernel a try.

This one is almost straight up stock cm6 but it has the BFS code in it (but not used).

If this doesn't work, then I will just compile a totally virgin cm6 kernel and see what happens...

2.6.34.2_SVS-950mV_CFS_1113Mhz_0806100-TEST1.zip
[Nexus One Android Development] uoY_redruM:
Are you planning on (or did you already do) an 1190 with 720 support? :D
[Nexus One Android Development] fitsnugly:
already done ;) in the test folder...
[Nexus One Android Development] wildmonks:
Yup, test folder here or you can find it on the bottom of this page if you want direct links.
[Nexus One Android Development] damanrico:
Boot loop + stuck at the X logo. Are you sure it's a 950mV version?

If you want me to collect logs or anything, let me know, I'd be more than happy to.
[Nexus One Android Development] wildmonks:
Yup, its the 950mV version. I have not touched the voltage table so its the exact same as the stock cm6 kernel which uses pershoot's settings. One more kernel for you to try but this one is straight up cm6 stock. If error then you can post your last_kmsg log.

Now this kernel I did not touch a single thing in the code. If this doesn't work, I don't know what it could be...

2.6.34.2_SVS-950mV_CFS_1113Mhz_0806100-TEST2-Virgin.zip
[Nexus One Android Development] damanrico:
Trying it right now.

Pershoot's settings you say? That could explain things. Please read what I wrote here:

http://xdaforums.com/showpost.php?p=7515159&postcount=1085
[Nexus One Android Development] wildmonks:
Oh wow, so sorry I didn't read that carefully! :(

Interesting... so it was the old AVS kernels that prevented the boot loops for you. You know what then.. I have an idea why its boot looping then. I'll make you a kernel asap.