yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] B1ny:
My phone seems to be OK now with the new 925mv, no boot problems. Will see tomorrow morning if its still alive and kicking :)
[Nexus One Android Development] mtw4991:
Trying the newest 0814 925 BFS and it still doesn't want to get past the boot screen, just keeps rebooting back to the cyan logo with the sperm swimming round n round n round n round. Me thinks I need 950mV:(
[Nexus One Android Development] damanrico:
Sadly enough I had to pull the battery. Seems like AVS is out of the picture for me.

Thanks for trying though.
[Nexus One Android Development] mick2021:
Kinda newbie question but how do you confirm if the kernel you using is stable? Do you run the stress test in SetCPU?
[Nexus One Android Development] mtw4991:
:D:D:D sorry, couldn't help it....you'll know if it isn't stable as you won't be able to boot up past the X screen or past the CM logo or past the lock screen or into the system or everything you touch force closes on you or sends you back to re-boot or your phone freezes and nothing works except pulling the battery out or performance drags n lags really bad or the phone BLOWS UP on you at the kitchen table and the wife doesn't understand how you just blew up a $530 phone that you've had for what,...2 weeks?

EDIT: sorry again...I couldn't stop myself ;-)
[Nexus One Android Development] mtw4991:
Wildmonks, any chance of a 950mV kernel for = 2.6.35_AVS-925mV_BFS_AXI_720p_1228Mhz_TEST_081410.zip ?
[Nexus One Android Development] antiochasylum:
My phone must be a freak, set it to 1228mhz and it runs smooth as glass, and boots up just fine with 925mv, just flashed the 8/14 no720p 1228mhz cfs 925mv kernel.fantastic work. 1228 got me back over the 40 mark in linpack
[Nexus One Android Development] kamasi36:
I wouldn't say smooth as glass. I've tried the 925 and 950. 950 works better for me. My mflops went from 50+ to 40.66 with new linpack. I can't hit 41 at all. I played tnt channel the entire night at 1190 woke up and it was still on. When I closed the browser the phone was unresponsive except for trackball. I navigated to quick boot and hit reboot. Phone booted back up to normal but never had that problem at all with enom's 1113 stock. So went back to it. I've put all the 1267 kernels to the test with flash and they all start lagging after awhile. The speed is there at first but eventually stability wanes.

Never once had to pull the battery though.1228 and below. 1267 got to home screen and froze.

appreciate his work though. At least Wildmonk gave us the option to experiment with those types of speeds.
[Nexus One Android Development] Kepster:
Guys just a question. I'm using enoms latest and 925mv kernel of wildmonks. I notice random stock/dolphin browser freeze up which requires hard reset. Is this due to compatibility issues? Thanks!
[Nexus One Android Development] mick2021:
:p thanks.

Wasn't sure if it's similar to ocing a PC where it's only stable when u do stress test for a couple of hours.

Tried the 2.6.35_AVS-900mV_CFS_AXI_720p_1228Mhz_TEST_081210 and it locks the phone when it's at 1228. Seems to be fine with 1113 and 1190.

btw awesome job, WM. :)
[Nexus One Android Development] mortzz:
Mine's the same. I've ran it all night and today and haven't had a problem.

I have it idle at 998MHz max though.

The new Linpack sucks.
[Nexus One Android Development] antiochasylum:
Same as me, run it normal at 998, just like the 1228 ability :), but +1 on the new linpack
[Nexus One Android Development] LevitateJay:
I want to try this 128MHz low freq, sounds great for battery. Are there any downsides? and where can I get one of the kernals that supports this? Atm I'm running 2.6.35_SVS-925mV_BFS_1113Mhz_080710.zip8010

Also... My phone has been locking up or something when the screen turns off. When I press power to wake the phone nothing happens so I have to pull battery and press button and then it boots up. Anyone had something similar? Should I try higher MV to fix this? Or could it be my SetCPU profile? Any suggestions?
[Nexus One Android Development] sngweizhi:
Mine had the locking issue as well, but when I kept pressing the power, after a few tries, it wakes.

And btw do you know you can press power + down vol + trackball to restart when phone hangs? No need to go through the hassle of pulling out the battery
[Nexus One Android Development] navillos:
2.6.34.2_SVS-950mV_CFS_1113Mhz_080610.zip

no 720p +audio boost, AXI

one AVS and ons SVS please
[Nexus One Android Development] B1ny:
Have been on this for the last 12 hours: 2.6.35_AVS-925mV_CFS_AXI_720p_1228Mhz_TEST_081410.zip

Works perfect and didn't freeze up during the night either.

Around 1% cpu usage, and just above 0.5% power usage at idle.

That's at 128-1113 mhz.

So it looks like the 128mhz setting works for me, just like it do on my Liquid.
[Nexus One Android Development] wildmonks:
Sorry the AVS didnt work out for yoh. But dont worry, I'll continue to provide you with the SVS kernel.

Your answer was spot on mtw! I couldnt have said it any better. :D

Sure! Its been posted in the usual places under the date 081510.

Yes, try the 950mV AVS I just posted and see if that helps at all. You can also try setting your min to 245MHz to see if it was the 128MHz setting that was giving you this problem.

i had this happen to me once as well. my initial thought was that because the min is now set at 128MHz, that i was experiencing a little lag waking up the phone. I wasnt really able to test this because this lag hasn't reappeared yet for me. If this is happening to you a lot, try setting up a screen off profile that uses ondemand with min/max of 128MHz/537MHz or something similar. If the problem still occurs then the next setting to try would involve a min of 245MHz.

Looks like 925mV is a good Min setting to use with AVS for most. I'm curious to find out if 950mV helps at all for those that have trouble with the 925mV kernels.

I'd be happy to do this for you but I have yet to update my .34 kernel to support the requested features except for the audio boost. Its going to take me some time to do so. Honestly I was hoping to move away from the .34 kernels because the .35 kernels and all its variants is already occupying so much of my time...
[Nexus One Android Development] Latentk:
Haha monks always the busy guy. RC3 posted a bit ago, any need to update the kernels?
[Nexus One Android Development] wildmonks:
Took a quick look at the latest kernel code on cyanogenmod. I don't see any major changes so my guess (and hope) is no, lol. Ill know for sure when I update to RC3 or the latest nightly. Whichever is newer...
[Nexus One Android Development] cypher21:
Hi Monk

Appreciate the work! Especially the NoAudioBoost Kernels

I've just updated to CM6 RC3, and tried

these kernels.

2.6.35_SVS-925mV_CFS_1113Mhz_NoAudBoost_081010.zip

2.6.35_SVS-925mV_BFS_1113Mhz_NoAudBoost_081010.zip

WIth both I get an error on the camera app that it can't connect to the camera.

Hope to see a fix soon :)
[Nexus One Android Development] wildmonks:
Sorry, I missed this question. Do you experience this with enom's stock kernel? If so then it's probably not a kernel related problem but something else. It may even be the app itself.
[Nexus One Android Development] wildmonks:
Bleh.. More work, lol. I'll look into this after some sleep.
[Nexus One Android Development] damanrico:
I'm on RC3 as well (wipe cache + dalvik and upgraded from a nightly) and it's working fine for me using a .35 081010 kernel.
[Nexus One Android Development] cypher21:
Strange,

I updated from RC2 to RC3 and also whiped dalvik and cache.

Will give it another go then

EDIT:

did a full whipe, Reflashed CM rc3

rebooted, full whipe again, flashed 2.6.35_SVS-925mV_BFS_1113Mhz_NoAudBoost_081010 kernel,

rebooted and everything works fine.

After this reflashed data partition to have everything back again, and still works.

strange it didn't work in the beginning though, but at least i've got the noboost kernel again with everything working :)

Edit2:

Camera works now, but sometimes FC's or causes a reboot with this kernel.
[Nexus One Android Development] antiochasylum:
The 128mhz rocks. Seriously, phone has been off the charger since 6am this morning, its now noon, my battery is at 95%, wow. Simply wow. Awesome job monks.
[Nexus One Android Development] navillos:
ok then what about

2.6.35-950Mv_AXI_no720p+AB-1113mhz

one AVS and one SVS
[Nexus One Android Development] notxel21:
What rom are you using the kernel with?

Thanks! :cool:
[Nexus One Android Development] notxel21:
I'm kindly asking for suggestions for a WM Kernel version that works well on RC3?:confused:

Thanks in advance! :cool:
[Nexus One Android Development] Latentk:
Still using 811 bfs 950mv 1267 build and it is completely stable for me on rc3. Only running at 1113 but still. I had another overnight freeze up on the 814 monks I think you're right. My phone is strictly svs it'd seem. Any chance I could get one of this same kernel (950mv 1267/1228 bfs svs aix 720p aid boost) but with the new memory hack and at 128 plz?
[Nexus One Android Development] innisdb:
whyyy do these kernels make launcherpro not work right? anyone notice that u have to swipe a few times to move homescreens? its somehow unresponsive most of the time and laggy
[Nexus One Android Development] antiochasylum:
Kang o rama 0.9 SP3, I refuse to flash any RC rom. This rom is super stable.
[Nexus One Android Development] evilive27:
Looks like my nexus needs svs and 950. Otherwise 1228 MHz doesn't work. Works alright at 1152 with avs and 925. But with a 950 and svs kernel I get my highest linpack scores.
[Nexus One Android Development] Eddiemc:
I've had that a lot on bfs kernels, try cfs and see if it makes a difference:)

-e
[Nexus One Android Development] poochie2:
I confirm that 900mV SVS + 128 MHz ROCKS!!! Please include this in future kernels because it's a real battery saver, just have to let some power available in SetCPU profiles to make answering/unlocking smoother.
[Nexus One Android Development] B1ny:
Just had a complete pull battery freeze up on the 925 mv, have switched over to the 950 mv.
[Nexus One Android Development] B1ny:
Yes, mine seems to be able to run at a higher mhz with svs than avs as well.

So I would also like to test this.
[Nexus One Android Development] Gilg@mesh:
2.6.35_AVS-925mV_CFS_AXI_720p_1228Mhz_TEST_081410.zip works great! nice with the 128MHz option too, Im running it @ max 1075MHz (don't need more power atm) and conservative scaling, no problem at all! :)
[Nexus One Android Development] sl8125:
Quick question on flashing the kernel. After flashing with a new rom do I need to reflash the kernel again.

I too have the same kernel with new cm6 rc3 rom that was up today. A days use with CPU set at 1190mhz no problem. No freeze ups or lock ups. Getting consistant linpak score of 38-40. Quad is up in the 1600. Love it.
[Nexus One Android Development] damanrico:
Yes, you always need to flash the kernel after you flash a ROM or a ROM update.
[Nexus One Android Development] sl8125:
Cool thanx.
[Nexus One Android Development] ChronoReverse:
For some reason the no 720p 925mV cfs avs version from the 14th still breaks my camera.
[Nexus One Android Development] antiochasylum:
U

Same with me. Exact same kernel, freezes my phone, and causes the temperature to sky rocket.
[Nexus One Android Development] wildmonks:
Kernels using the 925mV and CFS have been working well for me on RC3. Whether it be AVS or SVS.

I'll get working on your request as soon as you tell me which rom your using so I can use the correct "no720p" code.

I'll get to work on making 900 and 950 SVS for you two right now. I'll include the 720p code since I'm assuming you two are running cm6 and I'll assume your using CFS unless you two say otherwise.

It has come to my attention that I need to make two different "no 720p" versions depending on the rom. Tell me the rom you are using and I'll make you a kernel with the correct camera code.
[Nexus One Android Development] Latentk:
Monks, again you may hear this again and again but it must be said again and again; thank you for your continued work and efforts. You really put a lot of work into these (at least it seems such) and we are thankful. I wish you had a donation button readily available so we could compensate you at least one way or another :P.

I am probably going to jump on the SVS versions of the most recent kernel when they come out.

Out of curiosity, monks, what home launcher do you use? I seem to get the same slight lag associated with BFS kernels, I may try a CFS to confirm.
[Nexus One Android Development] B1ny:
Got freeze on the 950 mv avs as well.

I am back on 2.6.35_SVS-950mV_CFS_AIX_720p_NoAB_1267Mhz_TEST_081110.zip until the new svs kernels comes out.
[Nexus One Android Development] wildmonks:
Requested SVS kernels have been posted here. Now these are using the latest kernel updates from the cyanogenmod github and I will be releasing a set of AVS kernels soon for everyone based on this update. Now these both have the 720p code so if you need a "no 720p" kernel, PM me and I'll make you one. Please include the ROM you are using, min mV, CFS or BFS, NoAudBoost/AudBoost, and max MHz and I'll make you a kernel with your requested configuration.

Donation link is back, I was hesistent bringing this back for personal reasons but for the time being, I guess I'll display it :).

I'm using LauncherPro. I do get the lag (sometimes) that was reported earlier and its happened ever since I made min 128MHz available.
[Nexus One Android Development] ChronoReverse:
I'm using geo411m's nearly stock Froyo ROM.
[Nexus One Android Development] B1ny:
Thanks :)

I will have a go at this first: 2.6.35_SVS-900mV_CFS_AXI_720p_1228Mhz_TEST_081510.zip
[Nexus One Android Development] Latentk:
Good man! Plan on seeing some bucks soon! ANd thanks for the updated kernels, is it to much trouble to try for a BFS version?
[Nexus One Android Development] wildmonks:
Hopefully this works, I've only tested this on a purely stock FRF91 rom but I'm thinking it should.

2.6.35_AVS-925mV_CFS_no720p(stockFRF91)_1228Mhz_081510_TEST.zip
[Nexus One Android Development] wildmonks:
I'll get to making a SVS BFS kernel versions after I post the main release batch (which will be in 10 mins or so).
[Nexus One Android Development] wildmonks:
Update to .35

-Changes since 081010

-HAVS Code has been intergrated from IR's Github with a modification from Ivan to make it more OC friendly.

-net: wireless: bcm4329: Fix "setsuspend" behavior (cyanogenmod)

-net: wireless: bcm4329: Fix unregister_early_suspend() in dhd_detach() (cyanogenmod)

-net: wireless: bcm4329: Add memory barriers to wait functions (cyanogenmod)

-mahimahi: Give 1MB back to pmem_adsp for decoder (cyanogenmod)

-vdec: Add VDEC_IOCTL_GETVERSION (cyanogenmod)

PLEASE NOTE: The above kernels has not been declared fully stable. If your having issues with these kernel then I

suggest using an SVS kernel. Make your request to me and I'll make one or use the 081010 SVS kernel batch.

Any request for a custom kernel, please PM the following details, your current ROM, desired min mV, CFS/BFS, NoAB/AB, and

max MHz.

Link to Kernels

MediaFire Mirror Link
[Nexus One Android Development] ChronoReverse:
It works great! Interesting how there needs to be two variations of the no720p code.

Thanks as always for the compile.
[Nexus One Android Development] wildmonks:
BFS kernels of SVS 900 and 950mV have been uploaded. Find em here.

Ah, very good to hear. Interestingly I had to revert one additional commit from cyanogenmod to get that kernel to work. It seems little by little, cm6's camera is changing away from stock.
[Nexus One Android Development] Gilg@mesh:
thanks 2.6.35_AVS-925mV_CFS_720p_1113Mhz_081510.zip working great!
[Nexus One Android Development] Pochemuchka1977:
Tried the 2.6.35_AVS-950mV_CFS_NoAB_720p_1113Mhz_081510.zip - got the boot loop, can't even access kmsg :-( .

Running CM6 RC3, cache and dalvik cache were cleared prior to flashing the kernel

Going back to 2.6.35_SVS-925mV_CFS_1113Mhz_NoAudBoost_081010.zip which works without a flaw
[Nexus One Android Development] cypher21:
Same thing here with the 2.6.35_AVS-925mV_CFS_NoAB_720p_1113Mhz_081510 kernel

It's looping on the X

Flashed back to the 081010 kernel and everything works fine again

@monk, If you have time, can you make a NOAB, 128mhz CFS,720p enabled kernel?

I'm running CM6 RC3
[Nexus One Android Development] Pochemuchka1977:
+1, but I think SVS will be preferable since my device is acting really strange with AVS ...
[Nexus One Android Development] nenco:
any AVS kernel = hangs after some minute for me too
[Nexus One Android Development] musashiken:
2.6.35_AVS-925mV_CFS_NoAB_720p_1113Mhz_081510 kernel works fine for me.

On Enom's 2.11.3. Been nearly 4 hrs, surfed some web, made some calls. Seems fine except for one time when it froze while someone was calling in. Turning off and on the screen made it into a missed call and it unfroze. Was in the elevator at that time.
[Nexus One Android Development] B1ny:
Been on this now for 7 hours: 2.6.35_SVS-900mV_CFS_AXI_720p_1228Mhz_TEST_081510.zip

Seems to run great, at 128-1113mhz I have just below 1% cpu, and around 0.5% power consumption at idle.

Max performance is at 1190 mhz.
[Nexus One Android Development] GIKE:
Installed 2.6.35_AVS-925mV_CFS_720p_1113Mhz_081510 on last enomther, and get some force closes, and after a hour in stand by, the screen don't lights up.

I'm back to 2.6.35_SVS-925mV_BFS_1113Mhz_081010. :D
[Nexus One Android Development] wildmonks:
Hmm.. from the feedback I'm reading and the requests that I'm receiving, it looks like I better make SVS versions of the 081510 AVS kernels. I'll work on that as soon as I get off from work and I'll fulfill the requests that I received and anymore that I get while I'm away.

Guess I shouldn't have made this release using AVS. :(
[Nexus One Android Development] chowlala:
Just getting off from the 1st June revisions. I can confirm there's been quite a bunch of FC's and random bugs - which, i still believe are still being caused by how the BFS handles requests. Am reverting back to Pershoot's latest to compare some battery life time.

Will flash the CFS when you're done with it wildmonks. Thanks again for some very interesting work on particularly the battery life. =)
[Nexus One Android Development] wildmonks:
Okay, I believed I traced it down to this commit that I added from cyanogen.

I shouldn't have added this commit since its a debugging related thing. I'll upload a test kernel very soon. Again MAJOR sorries to everyone -_-
[Nexus One Android Development] chowlala:
No probs wildmonks. You're doing great! Looking forward to doing some testing between the AVS kernels and normal kernels like Pershoots! =) Hope to be able to find some good findings. =)
[Nexus One Android Development] wildmonks:
I do feel really bad about this but yah, thanks for the words of encouragement ^^;

Here's the test kernel I promised:

2.6.34_AVS-925mV_CFS_1113Mhz_TEST_KERNEL_060510.zip

To be safe, I started back over to my 060110 kernel code and added only the USB fix. I'll do more testing before I add in the other commits and after that I'll make the other kernel versions
[Nexus One Android Development] watercool:
thanks for your work. may you please release the 0.925 cfs with and without audio hack when ready?
[Nexus One Android Development] sultan-mrm:
you are the best , its works 100% like you :D

I'll update it to cm5.0.7.1 if arabization release or direct to cm6.0 (froyo) :)

Thanks bro and best regards,
[Nexus One Android Development] watercool:
should the conservative give better battery than the on demand?
[Nexus One Android Development] wildmonks:
Yes it should because the conservative governor, unlike the on demand governor, doesn't jump up to max MHz unless the program running demands it. And lower the MHz, lower the voltage that is feed into the CPU.

But the on demand governor has the advantage of not feeling laggy because the MHz jumps to max right away.

Good news, I finished my testing and I'll be posting up the new kernels very soon.
[Nexus One Android Development] dirwdirw:
looking forward to
[Nexus One Android Development] wildmonks:
Here are the new kernels:

I have tested each new addition from cyanogen and looked at the kernel logs carefully. I have not witness the MHz go super crazy (jumping from min to max non-stop) with the on demand governor like it did with the previous 060410 kernels. Hopefully that won't happen again -_-...

What was added to these kernels since the 060110 release:

-network: wireless: Add get_mac_addr functionality to platform

-network: wireless: bcm4329: Update to Version 4.218.238

-network: wireless: bcm4329: Fix MAC address import

-[ARM] msm: mahimahi: Debounce power key

-msm: camera: replace dmac_inv_range with dmac_flush_range

-gadget: Fix deadlock in UMS fsync_sub

2.6.34_AVS-800mV_CFS_1113Mhz_060510.zip

2.6.34_AVS-925mV_CFS_1113Mhz_060510.zip

2.6.34_AVS-800mV_BFS_1113Mhz_052710.zip

2.6.34_AVS-925mV_BFS_1113Mhz_060510.zip

Thank you all for your patience and understanding. And please continue to report your findings like you have been doing :)

Here yah go:

2.6.34_AVS-925mV_CFS_1113MHz_NoAudBoost_060510.zip
[Nexus One Android Development] chowlala:
Awesome. I just tested the 925mV CFS TEST kernel earlier, and it seems to feel very buggy. Had a few bad scenarios with swype and launcher pro going whack on me. Never had this issues before except on these hybrid kernels. Seems to happen when I set min and max SetCPU at 1113 each to run linpack and stuff. Need to do a little more testing I think.

Flashing on the newer ones right now to trial run. =)
[Nexus One Android Development] watercool:
i just want to confirm this. I have perfect 3G (HSDPA) coverage here but with the 0.800 it switches sometimes to E for a fraction of a second.

In addition (not sure if this is related to the 0.800) my wifi won't connect sometimes. I never ever had any wifi problems, yesterday was everything perfect but today it said "connecting..authenticating..disconnected..connecting..authenticating" a.s.o. for 15 minutes.. and then it connected :D

Everything perfect with the 0.925 so i'll stick to that too.

Someone using profiles @ setcpu with this kernel? Like sleep profile with 245min/460max or is that unnecessary
[Nexus One Android Development] wildmonks:
Good question: I like to use the sleep profile when I use the on demand governor because it prevents the cpu from reaching max when some background event is occurring. I never paid attention to this until I investigated THATTON's issue.

If your using the conservative governor, then you don't need to do this. The cpu stays in the low MHz range on its own.
[Nexus One Android Development] wildmonks:
Yah, overclocking can get pretty problematic with the hybrid avs for some it seems. This is probably why intersectRaven refuses to use it (good reason IMAO). But at least you can choose when to use it by using SetCPU.
[Nexus One Android Development] watercool:
Thanks!!! :)
[Nexus One Android Development] nazrin313:
Re: [Kernel] Hybrid AVS + 1113Mhz Overclock (.33.5 & .34)

Testing the new 925 cfs kernel right now....will update on my findings...
[Nexus One Android Development] intersectRaven:
Yeah. Tested it out once and found that AVS' sensitivity to the scorpion core's sensors actually caused all sorts of problems when achieving maximum clock. :(
[Nexus One Android Development] cdmove:
hey i tried this and now my phone won't boot.

it freezes for a second during the x logo animation and the screen with the unlocked lock shows up and back to the x logo animation and it freezes...

i did a nand backup before installing the kernel...i can go back right???
[Nexus One Android Development] watercool:
try to wipe cache and dalvik cache first. If this does not help just flash another kernel from recovery. I think you do not have to do a complete nand restore.
[Nexus One Android Development] watercool:
same happend for me, but it seems to work if you oc just a bit.. not to maximum. But anyway, Froyo is so fast that overclocking makes not a real sense.. but it is always cool to know you are on OC hehe.

Is there any major difference between wildmonks and interesects Kernel apart from the oc?