yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] wildmonks:
@mousse04

Sorry for the delay, but I wanted to test the camera first. Looks to be working (on a plain old vanilla stock FRF91 Camera app)

2.6.35_SVS-925mV_CFS_AIX_No720p_NoAB_1267Mhz_TEST_081110.zip
[Nexus One Android Development] mousse04:
You are going to think that I'm a pain in the neck but I love AudioBoost...

So it is a mistake from you on the name or you really don't put the AudioBoost???

Sorry for all the work I give you !!!
[Nexus One Android Development] wildmonks:
ack.. well.. its my bad.. I read it wrong your request. Well.. maybe someone out there will want it lol. Standby, making your kernel now. (It should take as long as before since I'm done testing).
[Nexus One Android Development] mousse04:
For sure, regarding people loving noAudioBoost kernel, someone will want it.

Thanks a lot for your great job.
[Nexus One Android Development] wildmonks:
@mousse04

ok, here's your real kernel! (I hope)

2.6.35_SVS-925mV_CFS_AIX_No720p_1267Mhz_TEST_081110.zip
[Nexus One Android Development] HTCDevil:
No 720p has crashed my camera on a stock FRF91 deodexed. Hope you resolve ;)

I'll try mousse's kernel too :D
[Nexus One Android Development] mousse04:
Thanks a lot wildmonks....

This kernel works perfectly for me!!!!

You're the best ;-)!!!
[Nexus One Android Development] wildmonks:
@mousse04

Oh good! I can sleep now :D

@HTCDevil

Hopefully mousse's kernel works for you too :)
[Nexus One Android Development] mousse04:
Yes I think you should go sleeping before I want a new version of your perfect kernel :p
[Nexus One Android Development] HTCDevil:
I'd like the same kernel but with 1113Mhz. :D

Thanks for your work. I appreciate it and use your kernels only, but i want it now on my FRF91 official based :D

aufs.ko is for audioboost? Is there any other module for 720p that i can manually remove from other kernel i would like to test ?

Thank you man :D
[Nexus One Android Development] damanrico:
You can use that kernel, just set the max Mhz to 1113. That's 100% the same as a 1113Mhz max kernel. Saves wildmonks some time compiling an extra kernel.
[Nexus One Android Development] derekv6:
Wildmonks can u please compile with axi noaudioboost 720p 1113mhz and cfs 950mv for use with cm6... thx in advance :-)
[Nexus One Android Development] damanrico:
If I'm not mistaken this one is for CM6: http://www.mediafire.com/?cl7ojzla5be3gfw

Just set the max to 1113Mhz.
[Nexus One Android Development] HTCDevil:
If i knew which file i have to edit...
[Nexus One Android Development] evilive27:
Thanks for all your hard work!!
[Nexus One Android Development] codesplice:
Use the SetCPU app. Much easier :)
[Nexus One Android Development] HTCDevil:
I like to know what i'm doing...i don't like easy ways my friend :D
[Nexus One Android Development] nenco:
This work very good for me too, thanks :D
[Nexus One Android Development] Autinhyeu:
Sorry, but i dont know "AIX" in 1267 version :D
[Nexus One Android Development] uoY_redruM:
Man, I just don't get it.

I could run 1228 before just fine, now my phone just won't handle it. It causes FCs and won't even run linpack (freezes while calculating results).
[Nexus One Android Development] damanrico:
It might be cause the phone wasn't really made for that. :p

I guess you were lucky the first time.
[Nexus One Android Development] uoY_redruM:
Luck doesn't strike for a week straight! lol

It was working fine, using it for a week (not for daily use though) and hitting nice linpack scores and quadrant scores. Running perfectly. Switched back to 1190 kernels just simply because they were being updated frequently. Got in contact with wildmonks about creating the newest AIX super overclock kernel and 1228 is now a no go for me :(
[Nexus One Android Development] ogdobber:
here's the depressing part, with the "new" linpack and a stable 1190 kernel, your mflops just dropped to 38
[Nexus One Android Development] uoY_redruM:
Yup. I'm scoring 38's to 42's.
[Nexus One Android Development] germandark:
Will the 2.6.35 kernel "break" the camera on my frf91 root rom? I am sorry if this is a simple answer but I have been confused. I believe I read that the 720p works with cyanogen and is stable with it. I don't care if I have the 720p recording or not, I do want my camera though. Would someone care clarify since I cannot figure it out haha.:D
[Nexus One Android Development] ax0r:
Qft. The 1190 aix bfs avs kernel puts out way better numbers. Atleast the test version I have. 120 Ms @ 1190 and 139 Ms @ 1228. 1267 is instant freeze
[Nexus One Android Development] wildmonks:
You will need to use the kernels labeled No720p. You can get the 1113MHz kernel version here or the superclocked kernel here.
[Nexus One Android Development] germandark:
Thank you for the quick reply and the links to the needed downloads. If for some reason all world goes wrong for my N1 I can revert to a stock kernel via a nand back up or a recovery via clockworkmod? Pardon my extensive questioning.
[Nexus One Android Development] Vlad83:
Wildmonks, whats the latest on AIX? I haven't noticed any performance gains but battery seems to drain faster. Whats your observation?
[Nexus One Android Development] damanrico:
Yes, you can.

Be sure to do a nandroid backup before flashing the kernel. If it doesn't work out you can restore the nandroid backup and all will be the same as before flashing this kernel.
[Nexus One Android Development] germandark:
Thank you. I wanted to verify that the kernel would be included in the nand backup. I was thinking it was obvious that it would be, but it is safer to just ask someone that would know for sure before diving head first into it.
[Nexus One Android Development] wildmonks:
Personally, my observations have been the same. But I have gotten a report from a user that says it does work for them. I'm going to test out a kernel with the latest HAVS patch from IR that already has AIX and I'm gonna see if there's any difference in battery with the two combined.

Its good practice to always make a nandroid backup before flashing. And yes the kernel does get included in a nandroid backup.
[Nexus One Android Development] pakraider:
maybe we should code up a kernel kitchen and let the poor man have some sleep every now and then! :p
[Nexus One Android Development] wildmonks:
That would be so cool :)
[Nexus One Android Development] derekv6:
Thanks damanrico and wildmonks!!

Yea so far I've noticed slightly faster battery drain with the aix on default cpu speeds...
[Nexus One Android Development] Vlad83:
Wildmonks, what voltage is 1152mhz if 1113 is 1275mh and 1190 is 1300mh?
[Nexus One Android Development] RieGo:
@wildmonks: what about the ~120MHz option you talked about a while ago? i think this could save some energy in standby...

did you already take a look at it?
[Nexus One Android Development] kamasi36:
see if this works. don't know what image I have here.
[Nexus One Android Development] kamasi36:
1228.8 stable . I think this is the right one.
[Nexus One Android Development] wildmonks:
1153MHz@1300mV

I never bothered to make it because poochie2 said I didn't have to.
[Nexus One Android Development] RieGo:
Well, do you think it could be of use to allow lower voltages? if so, then i would highly appreciate if you could make one to test. i would definitely spend you a drink or two :)
[Nexus One Android Development] wildmonks:
Okay its been uploaded to the two usual TEST folder locations.

Its labeled: 2.6.35_SVS-900mV_CFS_AXI_720p_1228Mhz_TEST_081210.zip

-So this one has a low mV value of 900 which is only applied at 128MHz.

-Limited the max MHz to 1228 since there's not point is having a 1267MHz speed if no one can use it.

-It also has the new memory reconfiguration from cyanogenmod's github to free up some ram. Not sure if this new memory configuration will affect the HTC Camera...

And before anyone asks, I won't be making any variations of this kernel. I need to get back to working on HAVS. ;)
[Nexus One Android Development] poochie2:
I'll try it! A few quick questions:

- a 1228 MHz kernel without SetCPU will default to 998 MHz max 256 MHz min?

- Which ROMs are officially supported? CM6RC2 and its children for sure, other one like Enomther's or eViL's Q&D HTC Sense?

- Is this NEON "optimized"?
[Nexus One Android Development] uoY_redruM:
Well, definitely more memory! I've never had more then 291 on available memory (right after boot) and with the boot up running this kernel, I was at 306 available memory :)

Linpacks (with 1190) are 39, almost every time.

I'll run this all day tomorrow, its my sons birthday so I'll be out all day long, and see how battery life is.

One weird thing I'm noticing is the speaker sound. When I got a text message after installing this kernel, its a really weird "muffled" type sound instead of the clear sound. Not sure why. I haven't flashed a new nightly so its not that..
[Nexus One Android Development] wrinklefree:
I think we have a winner! Running it on enoms ROM and it's Smoooooth and stable so far.
[Nexus One Android Development] wildmonks:
Do you know if the 5MP HTC camera still works?
[Nexus One Android Development] wrinklefree:
Yes it does.
[Nexus One Android Development] kamasi36:
going to test and let you know.
[Nexus One Android Development] wildmonks:
-Uninstall SetCPU, reboot and it will default to 998MHz max. Not sure about the min. Will find out.

-Yah, the CM6 roms and Enom's rom. Stock FRF91 will require custom kernel for support. Desire based roms are probably out of the question with my kernels :(

-Yup, NEON optimization is present.

Cool Thanks guys. I'm still testing out the HAVS kernel on CM6 nightly so I don't have a chance to switch back to Enom's rom.
[Nexus One Android Development] kamasi36:
yes sir. 5mp works.
[Nexus One Android Development] wildmonks:
@kamasi36 & wrinklefree

Nice, thanks for testing! :)

@poochie2

Its just as you said, uninstalling SetCPU will also make the the min default to 245MHz.
[Nexus One Android Development] kamasi36:
Hmm. So far notice short bench is higher on average with this kernel 1228 max. And mflops are lower as well. The temperature is cooler though. After quick test I think the 1267max gets better performance.1228 runs cooler and slower IMO.
[Nexus One Android Development] HairyMerkin:
How do we set the minimum to 128mhz, or did I read this wrong?

Don't worry, flashed the kernel, it's all cool now.
[Nexus One Android Development] kamasi36:
Consistently getting 49.66 and 49.12 mflops with 1267 max kernel and short bench on average 140 low is 123. This kernel is definitely faster and smoother than the 1228 max.
[Nexus One Android Development] kamasi36:
Using 081110 1267mhz kernel. Forgot to mention that.
[Nexus One Android Development] ax0r:
bfs or cfs? the cfs version of that kernel is not that fast for me. im getting 200 ms setcpu's.

2.6.35_AVS-925mV_BFS_AIX_1190Mhz_TEST_080810 and the CFS variant both were extremely quick but somewhat unstable over 3+ hours. but the score were quick
[Nexus One Android Development] kamasi36:
Bfs, it's the only one with 5mp that I tried.1267
[Nexus One Android Development] knightnz:
Running the 900mV CFS AXI 720p 1228Mhz kernel here on the latest CM6 nightly and it works great. Very snappy, although Linpack won't give me anything higher than 39 for some reason.

Camera works fine, 720p recording works fine, WiFi works, HSPA works. GPS turns on but can't test a lock as I'm in the office :)

Smells like victory!
[Nexus One Android Development] ogdobber:
new linpack right?
[Nexus One Android Development] irishrally:
What voltages are being used for frequencies 1113mhz-1228mhz?
[Nexus One Android Development] wildmonks:
1113MHz@1275mV

1150MHz@1300mV

1190MHz@1300mV

1228MHz@1325mV
[Nexus One Android Development] wildmonks:
Compiled a set of AVS kernels for you all to test. Seems fairly stable even when using 128MHz@900mV so I included it in these kernels. (you will need SetCPU to access the 128MHz speed)

You'll find the No Audio Boost versions labeled "NoAB" and a separate set of "No720p" kernels for stock based FRF91 roms.

Also, all these kernels contain the memory tweak by Cyanogen.

Direct links here, mediafire links here.
[Nexus One Android Development] irishrally:
I restored my backup of the old version. Hopefully they will wipe the database of curent rankings and I will have a nice advantage.
[Nexus One Android Development] uoY_redruM:
I was going to say. With the new linpack, I CANNOT clock over high 39's..
[Nexus One Android Development] mousse04:
Thanks a lot wildmonks for your perfect work :)!!!!!
[Nexus One Android Development] Latentk:
Monks, the newest 1228 AVS kernels are STABLE. So far at least. Been up on my phone for about an hour now with no issues. Its also fairly snappy, possibly that extra mem? Feels good, will keep running it and let you know. Great work!
[Nexus One Android Development] kaotikking:
Anyone try using the newest AVS-tests with psx4droid I am getting freezes and reboots. I dont have that issue with any other kernels, I know they are tests I just want to make sure its not just me. Im using stock speeds and interactive governor in setcpu, and a wiimote to play if anyone cares to replicate it.

Sent from my Nexus One
[Nexus One Android Development] SimFox3:
With the new AVS test kernels, my phone rebooted once during initial boot.

Still initializing first boot, but I'll keep updating this post.
[Nexus One Android Development] mousse04:
I also experiment reboot during boot. Not each time.

I will try to catch some informations...

@Wildmonks

I got many Reboot and freeze with CFS AIX no720p AudioBoost.

edit2: After investigation, I think the problem comes from the 900mV... Is it possible to have same kind of kernel (128MHZ min) but with 925mV?
[Nexus One Android Development] poochie2:
What about a full voltage list? That will make it easier to choose how to calibrate setcpu profiles :-)

Something's wrong: using 2.6.35_AVS-900mV_CFS_AXI_720p_1228Mhz_TEST_081210.zip works fine for me (CM6RC2 and my Rodriguez R21), using the no 720p version hangs randomly everywhere as if something else is different and not only the 720p setting.

Ps: nevermind my issue... I used the AVS kernel thinking it was SVS :-). SVS 720p works fine, AVS no 720p doesn't.

Pps: unfortunately there is no no720p svs 900mV kernel, must I change ROM or could it be cooked? :-)
[Nexus One Android Development] RieGo:
thank you very much for the 128MHz and enjoy your drink :)

the kernel is stable for about 10 hours now and my battery was very nice. will you leave the 128MHz option in your kernels?

and also can you make one with 850/875mV @ 128MHz? I'd like to see if this would still be stable...
[Nexus One Android Development] poochie2:
I'm ready to try 875-850 mv ^_^ (only at 128 MHz)
[Nexus One Android Development] MrCDWJR:
how does the battery life compare for those using the latest CFS or BFS with 720 support and NoAB (pretty much monks latest) and enom 2.11.3 stock kernel? I've used monks on previous roms but not i would like to know if the battery life is better with monks kernel or enoms stock kernel. thanks.
[Nexus One Android Development] nenco:
Hang and reboot for me too with no720 version

I will try 720p version
[Nexus One Android Development] mousse04:
same thing here!!!!
[Nexus One Android Development] nenco:
720 version hangs too,

I will back to 2.6.35_SVS-925mV_CFS_AIX_No720p_1267Mhz_TEST_081110.zip

That work flawless
[Nexus One Android Development] mousse04:
Maybe the problem comes from the voltage...
[Nexus One Android Development] kamasi36:
Okay been doing some testing and this is what I found. On Enom's latest build using setcpu from the market at 998mhz you can hit 35 with the new linpack for android from the market. At 1113 you can hit as high as 38, however with the 1267 720P at 998 it wont go any higher then 33 never reaches 34. for some reason it comes up 2 mflops short. That's the difference between getting 40.6 at 1228 using 81110 bfs and hitting 42.6. Comes close but I can never hit 41 at all with new linpack on this kernel. Wildmonk any idea what could be making this kernel fall off a couple notches?
[Nexus One Android Development] mtw4991:
ummm...I can't even get the 1228 to boot past the CM splash screen. Did it once but hung and froze right after unlocking the screen:( Maybe the 900mmV isn't enough to get it to boot, idk.
[Nexus One Android Development] flak0:
@wildmonks so I noticed on setCPU with the latest 1228 Bfs 900 MVP kernel that my phone spends 80% of the time at 128mhz. This is definitely a battery saver. For those who want optimal battery performance set your setCPU sleep profile to 998max 128 min and conservative governor . Works like a charm. Also if you keep the regular to 1075 max and 128mhz min with interactive governor the phone wakes up without lag since the governor ramps it up. Hope this helps.
[Nexus One Android Development] mtw4991:
Damn, my phone has been very stable, but I can't get the 1228 BFS or CFS to boot. I wipe cache, dalvik cache, battery stats, flash and then it hangs. Any thoughts? What ROM are you on? I'm on latest CM6 nightly btw.
[Nexus One Android Development] flak0:
Screen shot:

Kernel

Linux version 2.6.35-900mV-BFS-AVS-AXI-720p-1228MHz-Monks-081210 (root@monks-desktop) (gcc version 4.4.0 (GCC) ) #53 PREEMPT Thu Aug 12 16:35:32 PDT 2010

Battery

Battery Temp: 31.5° C (88.7° F)

Battery Level: 70%

CPU

Frequency: 1113600 kHz

Load Average: 3.68 2.31 1.14 2/412 1272

Processor	: ARMv7 Processor rev 2 (v7l)

BogoMIPS	: 738.83

Features	: swp half thumb fastmult vfp edsp thumbee neon

CPU implementer	: 0x51

CPU architecture: 7

CPU variant	: 0x0

CPU part	: 0x00f

CPU revision	: 2

Hardware	: mahimahi

Revision	: 0081

Serial	: 0000000000000000

Time in State

128000 37830

245000 5766

384000 2385

422400 347

460800 416

499200 232

537600 585

576000 361

614400 408

652800 331

691200 387

729600 349

768000 298

806400 295

844800 337

883200 527

921600 189

960000 261

998400 6680

1036800 151

1075200 92

1113600 8160

1152000 0

1190400 0

1228800 0

Memory

MemTotal: 425540 kB

MemFree: 61296 kB

Buffers: 8536 kB

Cached: 171940 kB

SwapCached: 0 kB

Active: 229340 kB

Inactive: 107296 kB

Active(anon): 156112 kB

Inactive(anon): 1748 kB

Active(file): 73228 kB

Inactive(file): 105548 kB

Unevictable: 0 kB

Mlocked: 0 kB

HighTotal: 303104 kB

HighFree: 2684 kB

LowTotal: 122436 kB

LowFree: 58612 kB

SwapTotal: 0 kB

SwapFree: 0 kB

Dirty: 0 kB

Writeback: 0 kB

AnonPages: 156184 kB

Mapped: 48112 kB

Shmem: 1700 kB

Slab: 11064 kB

SReclaimable: 4496 kB

SUnreclaim: 6568 kB

KernelStack: 3296 kB

PageTables: 10820 kB

NFS_Unstable: 0 kB

Bounce: 0 kB

WritebackTmp: 0 kB

CommitLimit: 212768 kB

Committed_AS: 4231012 kB

VmallocTotal: 778240 kB

VmallocUsed: 113464 kB

VmallocChunk: 625668 kB
[Nexus One Android Development] mtw4991:
new nightly build in 5 minutes
[Nexus One Android Development] wildmonks:
I'm thinking the cause of the boot loops is the 900mV. I can raise the min to 925 and see if that improves things.

As for the 720p, it now seems apparent to me that I have to make 3 different versions of the code relating to the camera.

-One version that has 720p enabled that's compatible with the camera in cm6 nightly and is currently compatible with the HTC Camera add on that's available in Enom's rom.

-A no720p version that's compatible with cm6 RC2 and earlier.

-A no720p version that's compatible with FRF91 stock (this version is what's in yesterday's AVS test kernels and I see now its giving trouble to some).

Why the difference between the no720p is somewhat complicated to explain but its related to code responsible to making the kernel compatible with both CM6 nightly camera and HTC Camera.

So anyway, I'll work on making a 925mV@128MHz kernel with a small modification to AVS with the hope that it will be the last TEST AVS kernel so then I can roll it out to the main kernel batch.

As for my personal findings with yesterday's AVS Test kernel. I did encounter 1 hard lock on my phone. Everything completely froze including my computer that it was connected to which is very odd. After that, its been completely stable and I have noticed an improvement in battery life. I'd say the drain is now comparable to the old AVS code that was proven to be not adjusting the voltages. If the 925mV AVS kernels that I will make prove to be stable for those that had boot problems with the 900mV kernels then it seems I will have to make 2 different sets in the future....

I'll get started on making the 925mv@128MHz kernels late tonight if possible.
[Nexus One Android Development] fitsnugly:
I wouldn't worry about a no720 for RC2, RC3 should drop any day...
[Nexus One Android Development] chowlala:
The no720p is also for people who aren't on CM's. Or are just using rooted stock version but would like to use the kernel.
[Nexus One Android Development] wildmonks:
What would ideal is for everyone to adopt 720p support in their rom, including Google.:p
[Nexus One Android Development] damanrico:
wildmonks, just saw that you created a new custom kernel for me. Sorry I didn't see it earlier, sadly mediafire doesn't have some kind of service that shows when a new file gets uploaded.

Will try that kernel and let you know how it works out.
[Nexus One Android Development] fitsnugly:
Did u not read the 3 different options he listed in the post before mine?
[Nexus One Android Development] chowlala:
Do you not realize there are people who won't jump immediately onto RC3?

And would like to maintain RC2 for daily usage purposes while the bugs are kinked out on RC3?
[Nexus One Android Development] Latentk:
Is it just me or does it feel like making the jump between Screen Off to fully active profiles in SetCPU is slightly sluggish in the latest 1228 test kernel? It seems that the phone may take a sec to initially set its clocks when waking it. Not sure, but this latest build might run a little slower overall as compared to the 811 builds.

Also, I noticed a rather substantial difference in battery life (worse off) in the 812 vs the 811 builds. No idea why but it seemed to eat more battery... Any idea monks?
[Nexus One Android Development] B1ny:
I have boot problems as well on the 900mv, so looking forward to the 925mv since I am curious about the 128MHz.
[Nexus One Android Development] fitsnugly:
You didn't say that in your previous post. All you said was other ROM's and FRF91.
[Nexus One Android Development] damanrico:
wildmonks, the 1000 mV kernel acted the same as a 950 mV version. When I woke up today, I needed to pull my battery.
[Nexus One Android Development] RieGo:
do you use the interactive governor? if so, try to use on-demand and see if it still freezes.

i have had this problem when i tried interactive... otherwise it's really weird that 1000mV doesn't work.

edit: oh sorry, i missed we're already on avs again :) then the problem probably is avs
[Nexus One Android Development] damanrico:
I'm using ondemand. The reason why it doesn't work on my phone is that I have a weird device that doesn't like low voltages. Apparently I need at least 1050mV for my phone not to freeze.

Wildmonks is kind enough to create custom kernels for me. :)
[Nexus One Android Development] RieGo:
OK, I see

then i'm really lucky to be able to run on 900mV :)
[Nexus One Android Development] Latentk:
I also woke up and had to pull my battery. Do I have to tell both the screenoff and charging profiles to use an on-demand governer? I may set the screen off to conservative, I have it on powersave right now. This is so odd that it'd freeze randomly overnight...
[Nexus One Android Development] wildmonks:
The 925mV AVS kernels have not been uploaded. The No720p code that you see in these kernels is for Cm6 rc1 or rc2

I uploaded your usual 1050mV version that usually solves this problem for you. You'll find it in your folder. If your phone doesn't like this kernel then your only working solution at this point is 1050mV using SVS. :(

Sounds like SVS is better suited for your device or at least the current AVS code doesn't mix well for your phone. The 925mV AVS kernels I just uploaded does have a small tweak to AVS. I don't believe it will solve the freeze or sluggish issue for you though but I could be wrong.