yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] wildmonks:
Awesome, thanks for the feedback. Glad its working out for yah. After much thought, I guess it couldn't hurt to setup a beer fund so a posted a link on the OP post. Not much of a drinker but I guess its a good time to become one :)

In other news, I've been investigating the FC/reboot problem that some are experiencing. I was able to reliably replicate this on my phone by streaming a 30min flash video in the browser with the performance governor and max set to 1113MHz). Despite increasing the voltage to 1325mV and turning off optimizations, it would still crash the browser or reboot the phone. After taking a close look at the AVS debug output I discovered that the AVS refuses to lower the voltage (when at idle) on 1113MHz. This seems to collaborate what IR said in his post.

But when I set the max to 1075MHz (performance governor), AVS works normally (voltage drops when possible) and the FC/reboots disappear for me when streaming flash video. Today I tested the phone in 91° F weather, while driving with the navigation GPS on, and achieved a phone temperature of 111.2° F but it still won't FC, reboot, or lockup, so 1075MHz seems like a good speed to use with AVS.

I'll continue to see if tweaking the AVS code will bring stability to 1113MHz but in the mean time, I would like to release a stable kernel in the next release so I've been thinking of setting the max to 1075MHz. Performance drops a little (I get linpack 41.01 max and quadrant 1735 max @1075MHz) but I think the added stability is worth it. Or should I leave it at 1113MHz and leave the choice to you to set the max in SetCPU?

BTW: I don't know if setting the max to 1075MHz will help your phone achieve kernel stability but try as I might, I can't lockup or kernel panic my phone at 1075MHz.
[Nexus One Android Development] intersectRaven:
Hmmm...if all else fails, I suggest going the REALLY HYBRID way. That is, to set all voltage above 1075Mhz to go back to static voltage switching. :)
[Nexus One Android Development] wildmonks:
Oh, good suggestion! I dunno if I can achieve that with my current programming capability, but I'll give it a shot. When I have time...
[Nexus One Android Development] irishrally:
I think it would be nice to still have the option of running at 1113MHz.
[Nexus One Android Development] Daswolven:
Simpleminded question: While I don't mind at all setting the max to 1075MHZ to get the AVS to function properly, you note performance governor. Does setting to OnDemand affect this in any way?
[Nexus One Android Development] wildmonks:
Unfortunatly it was the same outcome with the other governors. :( I was using the performance setting as a quick way to prevent the CPU from throttling down when testing. I have concluded that the more time the CPU spends at 1113MHz, greater the chance of encountering stability issues.
[Nexus One Android Development] crunked:
i installed this and my n1 became very unstable. besides deleting setcpu, how do i revert back to the original settings before i flashed this kernel?
[Nexus One Android Development] watercool:
flash the original or an other kernel
[Nexus One Android Development] cdmove:
i flashed this 2.6.34_AVS-925mV_CFS_1113MHz_NoAudBoost_060510.zip and few instances where the radio got reset or something because the phone would asks for my pin and lock pattern.
[Nexus One Android Development] irishrally:
I never had this issue, but you might want to try the same kernel dated 6/6/10.
[Nexus One Android Development] chowlala:
You've been a badboy and have been watching *ahem* haven't you? Lol.
[Nexus One Android Development] wildmonks:
Sounds like your phone really doesn't like AVS+OC...

If you made a nandroid backup before flashing, that would be the best to restore your phone. Otherwise flashing the stock kernel or using the other more stable kernels (pershoot's or raven's) should bring stability back.

You can grab the 6/6/10 version here: 2.6.34_AVS-925mV_CFS_1113MHz_NoAudBoost_060610.zip

I too have never seen that before. :confused: It could be due to general instability from running at high MHz. Try lowering the max MHz to 1075 or 1036 via SetCPU.
[Nexus One Android Development] wildmonks:
I did what you suggested. It took me some time and thought on how to accomplish this but I was able to figure it out once I learned what each part of the code does. The result was absolute stability for me running at 1113MHz when streaming flash video! I'll continue to do more stress tests and if it goes well I'll release the usual versions. For now, if you want to try out the version I'm testing you can click here:

2.6.34_AVS-925mV_CFS_1113Mhz_BETA-TEST_061010.zip

The debugging/logging code I'm using is still present so if you want to see it for yourself in realtime use the adb command:

adb shell cat /proc/kmsg
[Nexus One Android Development] THATTON:
I will download now and test! Good job bro!
[Nexus One Android Development] wildmonks:
Crossing my fingers that it works for yah :o
[Nexus One Android Development] dictionary:
Re: [Kernel] Hybrid AVS + 1113Mhz Overclock (.33.5 & .34)

Testing this on Evil-One, evils new FroYo ROM. Will report
[Nexus One Android Development] apnoia:
Re: [Kernel] Hybrid AVS + 1113Mhz Overclock (.33.5 & .34)

It seems my N1 can't run stable at 1113, however this is the first kernel that allows me to play asphalt 5 for almost 10 minutes at 1113 :-) 1075 is fine for me no fc or reboot, same as latest pershoot kernel. Great work!

-------------------------------------

Sent via the XDA Tapatalk App
[Nexus One Android Development] intersectRaven:
Nice. It's easy when you get the hang of how the kernel does things isn't it? :)
[Nexus One Android Development] chowlala:
Sounds good. =)
[Nexus One Android Development] samarium:
Flashing 18/b2 now. Thanks.
[Nexus One Android Development] samarium:
The best method I've come up with is to uncompress /proc/config.gz & grep for things. It would be great if the details were encoded in the kernel revision and could be retrieved by uname -r, however at least you get to see wildmonks there, so that is a start.
[Nexus One Android Development] mik101:
I had one wakelock freeze all day with 17b1-975mV... not sure it wouldn't have happened at stock voltage though.

Will flash to the new kernel when I get home in a couple hours.
[Nexus One Android Development] wildmonks:
I use to provide a more detail descriptor in the kernel when I was compiling them one at a time (110410). I have since made use of a large compiling script (that also packages the kernel into a update.zip) that I made. It's a whole lot easier for me to leave in the same descriptor for each kernel. I could modify the script to include individual kernel names but I don't want to complicated my script any more then it already is. I'm already faced with a decision to add more kernels to compile for those users that can't run on 950mV.
[Nexus One Android Development] temasek:
Stress tested AVS 975mV beta2 for more than 1 hr. No issues. I'm staying at avs for awhile :)
[Nexus One Android Development] jameztcc:
Thanks wildmonks, Goggles working on 950 Ave beta2. Testing it now.
[Nexus One Android Development] Vlad83:
I've noticed that I don't lose signal in class with 975 as I do with 950. Other than that both work fine in all other aspects...
[Nexus One Android Development] mtw4991:
On 253 and 11/18 avs 950 also n all is good so far, doing a learn cycle on the batt right now. Will test more tomorrow.
[Nexus One Android Development] mik101:
Testing on todays betas -- I'm trying out the stock voltage now because I've been having a little lag on 975mv-svs.

AVS seems to cause random lag and freezes. The 950mv kernels are lag and crash city for me unless I tread lightly. Haha.

Had one lockup over night with 975mv-nov17-svs-b1. Best kernel for me thus far. :)

Edit: Freezes/Hot reboots with all of todays kernels on CM6.1 nightly 253.

Will go back to yesterdays kernel and retest to see if it's something in 253.

btw pretty much all the kernels will pass stress testing in setcpu on my phone.... its the waking transition or when its on my dock with the screen on for a while.

Edit, stock voltage one from today is working well for me. Not much difference for me with or without the commits that you reverted today. I don't care too much about the undervolting as long as it's fast and stable. :)
[Nexus One Android Development] nitrox1:
950mV avs beta2, all good so far. Cm6-r1. 245-1113 mhz ondemand

Sent from the 25th century.
[Nexus One Android Development] Vlad83:
Oh what a tease WM you are... creating an empty 11/19 folder... Now my phone has blue balls:eek:
[Nexus One Android Development] wildmonks:
Then I guess its time to do a general release ;)

New kernels posted, go here to get them on the new landing page :)

http://wildmonks.iblogger.org/
[Nexus One Android Development] simms22:
so ive been on the 2.6.35.8_SVS-975mV_CFS_AXI_720p_1152MHz_111810_beta2. i have to say i love the stability and the snappiness of the kernel. one thing though, battery drain is much faster than the 11/10 and 11/11 releases. anyone else have faster battery drain? anyways, the kernel is so awesome that im ignoring that the faster battery drain, its a non issue for me :D
[Nexus One Android Development] simms22:
on my way there :)
[Nexus One Android Development] simms22:
thanks for the custom kernels link :D
[Nexus One Android Development] temasek:
Actually I feel the faster battery drain too. My n1 moved too fast I have like totally forgotten about it.
[Nexus One Android Development] makelegs:
I agree. Really solid kernel. Battery drains a lil quicker than I'd like. Good stuff though, overall!
[Nexus One Android Development] wildmonks:
Yah, kinda of a bummer as I really like those scheduler improvements. But note that the BFS kernels don't have the patches (BFS is incompatible with those patches).
[Nexus One Android Development] simms22:
im going to have try the bfs to compare.
[Nexus One Android Development] temasek:
Hard fight. Round 1........win cfs.
[Nexus One Android Development] wildmonks:
I'll work on making BFS custom kernels (975mV) for you then.
[Nexus One Android Development] mik101:
All of todays kernels are giving me shell reboots. Back to stock voltage 111810 and phones flying along great again.

I'd chalk it up to my phone being a b***h.

I like how 111710 behaves at both 975 and 1050 but I want the tty ondemand scheduler patch. Haha. :)
[Nexus One Android Development] simms22:
cool!!! :D
[Nexus One Android Development] simms22:
did you wipe your dalvik before flashing todays kernels?
[Nexus One Android Development] mik101:
Always.

For ****s and giggles I've even tried both CWM and RA for wiping and flashing and neither seems to make a difference -- nor should they.

Im still having freezing issues with the Nov 18 stock voltage as it sits here on my dock. Trying the Nov 17th again to see if I can narrow anything down. *yawn* I think it's time for some sleep right now though.
[Nexus One Android Development] j3di:
I'm now on 2.6.35.8_AVS-950mV_CFS..........111910.zip

With the phone charging (at around 86%) noticed the battery charging icon had gone back to not charging. The Lockscreen showed it was no longer charging also, however the orange charge light was still lit.

Pulled and re-inserted the charge plug and it has resumed charging...

I'm happy to report that otherwise my N1 has been OK on this kernel, I'd have normally gone for atleast a 975mV version!
[Nexus One Android Development] Robdyx:
Am I too wrong or is Dalvik which contains the information of all the apps installed? Do you really wipe it every time you upgrade the kernel, that is, every day??? :confused:

BTW, I still haven't posted it here -Or I don't remember doin' it- Welcome back WM!!
[Nexus One Android Development] nitrox1:
Hi Wildmonks,

Just got used to your last site, glad to see your new one. Just, I am not used to it, I noticed there are 2x 950mv kernels, with no AB is that right? Both with Common and not Brain F'er.? But saw others with BFS.

Thought from the last couple of msg's that the BF'er was not available in your newest selection?

Sorry for being confused.

Edit: completely confused, I would needed A Mk. 1 etc, or beta 3

Edit edit: Sorry Blind to the 111810, and the 111910, but still confused as was expecting them all to be CFS

Edit edit edit: Why should we wipe dalvik-cache between flashing Kernels's?
[Nexus One Android Development] wildmonks:
I've run into this as well, and although I know the part of the code that is causing this, I haven't yet thought up a suitable solution that won't interfere with changes made by RogerPodacter & theloginwithnoname to the battery driver. But honestly I haven't put much thought into it because the simple solution as you discovered is to pull out and in the usb plug to start the recharge.

Generally no, unless your experiencing some problem. Pretty much the only time I clear the cache and the Dalvik is when I flash between stock and cm roms. And thx, good to be back :)

Yes to you question about there being another set of kernels just to have noAB (No Audio Boost). Sorry about not making direct links to the kernels but its such a pain to do so with all those different variant types :(. I rather just Compile, upload, and post quickly, then move on. Using the compiling script I made, moving to wordpress to create simple posts, and just mass uploading to the server helps me save a lot of time :D
[Nexus One Android Development] nitrox1:
Thank you for your reply.

That's cool, not a problem, just got confused :-b As only see 111 :-D

Edit: Worse when you use root explorer, or Amon_Ra, and the end of the kernel name disappears :-D
[Nexus One Android Development] Vlad83:
Oops wrong thread, sorry
[Nexus One Android Development] phewizzo:
Hahaha Vlad.

Sent from my Nexus One...
[Nexus One Android Development] mik101:
I'm back to todays stock voltage cfs one... might have just been a weird hiccup on my phone.

I clear the dalvik because mine doesn't take long to rebuild anyways with very few apps permanently installed on the phone. Most are installed as needed through aTrackDog(SD). Most of the time unless something is wrong you really don't have to unless switching between different roms (ie stock to cm6 to miui etc)
[Nexus One Android Development] dirwdirw:
http://passing.tk/index.php?q=YUhSM...0TDJ0bGNtNWxiQzh5TGpZdU16VXZNVEV4T1RFd0x3PT0=

why i got HTTP404 when i clicked this link???

how can i get the latest kernel?
[Nexus One Android Development] jlevy73:
http://wildmonks.whoisthedrizzle.co...-975mV_CFS_AXI_720p_1152MHz_Custom_111910.zip

I'm using the above kernel with the MIUI Rom and getting fantastic results. Rom seems ultra smooth and very fast.
[Nexus One Android Development] dirwdirw:
thank you very much
[Nexus One Android Development] dirwdirw:
any improvement of battery performance?
[Nexus One Android Development] musashiken:
According to wildmonk's site, he says that battery drainage is more obvious due to the new scheduler improvement mod.
[Nexus One Android Development] simms22:
ok, speaking of battery drainage... im using 2.6.35.8_SVS-975mV_BFS_AXI_720p_1152MHz_Custom_111910 right now.

yesterday i was using a CFS kernal(975) and noticed that the battery dropped at a pretty fast rate, today i flashed the BFS(975) custom kernel and i am seeing the complete opposite, in battery drainage, to the CFS kernel. after flashing the BFS i noticed right away that the battery drainage was slower. so this is what i did to really test it out. before i left work, i charged my phone to 99% and deleted my batterystats.bin file. then i powered it off. it took another 45 minutes for that light to change from orange to green. then when i left work, i powered it back on. right after i plugged my headsets, turned on my music player, put the phone in airplane mode, then caught the train to go home. i listened to the music player for almost exactly an hour before the battery percentage dropped to 99%(see 1st screenshot). after taking this screen, i turned off airplane mode and started using data(web, twitter, etc.). notice at 8:07pm its at 99% after 1hour 22min and 55sec. now its 9:33 and im at 88%, after 2hours 28min 24sec(see 2nd screenshot).

i have to say this is an amazing run on battery use. wildmonks, you did an amazing job on an amazing kernel. and thank you for your personal touches when you upload these kernels(custom). that says a lot about you as a person. thank you :D
[Nexus One Android Development] temasek:
Seems like simms22 simply have superuser access to WM kernels :eek:

*peeping at the word custom in the kernel filename*
[Nexus One Android Development] musashiken:
I think the custom kernels are just requests by certain users to WM. You can get the kernels from his site anyway.
[Nexus One Android Development] simms22:
and its available to you too, check out the link "custom kernels" ;)
[Nexus One Android Development] temasek:
Awwww its meant to be a joke to simms22. Uuuuuuuu LOL :D

EDIT:- when WM said he could make a custom kernel just for u......its a big WOW!
[Nexus One Android Development] sl8125:
Oh man I just tried 111910 kernel super smooth and fast. Without WM I don't know what I would do. I will never need to upgrade for a new phone.
[Nexus One Android Development] simms22:
edited... :D
[Nexus One Android Development] jlevy73:
And just to emphasize that no two phones or conditions are alike, I get just the opposite. Where BFS sucks battery at a clip of approx 4%/hr sitting idle on my desk, CFS is only 2%
[Nexus One Android Development] simms22:
which one are you using right now?
[Nexus One Android Development] jlevy73:
This one:

2.6.35/111910/Custom_Kernels/2.6.35.8_SVS-975mV_CFS_AXI_720p_1152MHz_Custom_111910
[Nexus One Android Development] simms22:
i flashed that one earlier today also. great kernel. i just wish the battery drop wasnt so fast(when being used). with wildmonks suggestion, i tried the BFS version he uploaded after. also, a great kernel! im happier with the battery loss on the BFS, then the CFS. i noticed it right away.
[Nexus One Android Development] jlevy73:
What about from a performance perspective? You notice any increase or decrease with BFS versus CFS?
[Nexus One Android Development] simms22:
i tell you what, besides for the battery drain, ive only really noticed one thing. my icon for files in Astro load faster on CFS than on BFS. they are both fast kernels. both smooth. both make my nexus one feel like an new updated model(nexus).
[Nexus One Android Development] jlevy73:
Interesting observation. The only difference for me is for some reason (who knows why) call quality seems better with CFS than BFS. Beyond that I can't really discern between the two.
[Nexus One Android Development] Dalibor31:
Its one thing that dont work well. Whatsapp. I get messages later. With pershoot kernel is it ok.

Can anybody test it
[Nexus One Android Development] temasek:
Whatsapp work fine here. At times it depends on their own server so may not be immediate. But after 1st year it will be yearly fee for android users. My wife who uses iPhone only pay one time fee. Wtf.....
[Nexus One Android Development] makelegs:
http://www.whatsapp.com/android/

Try this latest build. The message lag is gone. Make sure whoever else ur talking to is updated, also.
[Nexus One Android Development] mik101:
Sorry guys had to sleep there. Left the phone stressing with the stock voltage kernel from yesterday and have been using it for a couple hours since I got up on cm6.1-254 and its ROCK SOLID. (Plus my phone is running cooler than it has in a long time according to setcpu). Consider what a skank my phone usually is. Congrats WM.

I know you get thanked a lot -- but heres another. THANK YOU! :)

Plus damn close to 39M on linpack with no major OS customizations (besides CM61-254 and WM-Nov19-1050mv-CFS) doesn't hurt. ;) This is with all my usual apps in the background. I'm sure it could do better in airplane mode, but thats not really useful for much but offline gaming.
[Nexus One Android Development] vivmar:
someone have tested the 1050mv version?
[Nexus One Android Development] nitrox1:
I refuse to give in on low mV kernels, as have seen them working.

But had a reboot today while using copilot (never fun loosing your journey ;-) )

Believe I was using BFS, 950mV, 111910

Also been having problems with google nav and GPS lock. But that's a radio issue isn't it? Can anyone recommend one for the UK, with TMO?

Here's last_kmsg:

http://pastebin.com/98UxveHD

Thanks
[Nexus One Android Development] simms22:
try the BFS 975mV 111910 here http://wildmonks.whoisthedrizzle.co...-975mV_BFS_AXI_720p_1152MHz_Custom_111910.zip

if youre still having problems, theres a 1050mV version as well :)
[Nexus One Android Development] nitrox1:
Nope, 950mV or lower is the way forward.

1%/Hrs baby.

Edit while being at, at least 1113Mhz ;-)
[Nexus One Android Development] jlevy73:
True but not every phone can handle that voltage. This is why many experience lockups, wake issues, etc when going to 950mV. It's the reason why CyanogenMod doesn't go below 975mV on his kernels as stability is more important than a minor improvement in battery life.
[Nexus One Android Development] mik101:
x2... I have issues with stock cyanogen kernels once in a while. I usually don't get full reboots, but lag and weirdness. Sticking with 1050mv kernels that WM is producing now have been working without a hiccup *knock on wood*.

(I know this is the longest ive gone without a single hiccup at all when running a non stock rom -- and still counting).
[Nexus One Android Development] makelegs:
Simms22

You seem pretty sold on the recent bfs version, lately, as it pertains to battery life. I'm gonna give it a try.
[Nexus One Android Development] simms22:
yup, past day great battery life :)
[Nexus One Android Development] gravufo:
I too prefer BFS, seems to run better on my phone giving me a bit better results in Quadrant but most importantly making the UI feel much smoother!

Battery life seems pretty good too, although I haven't tested thoroughly on that...

I'm running the 950mV version, no lag, no freeze, no hiccups...PERFECT :)

Thanks WM
[Nexus One Android Development] jlevy73:
Damn you Simms I was completely contempt with CFS now you're gonna make me give BFS another go :p
[Nexus One Android Development] mtw4991:
Using 975 bfs also with miui right now. Seems strong...had to go to 975, as 950 wouldnt wake up quick enough to amswer the phone with screen off at 128/345
[Nexus One Android Development] simms22:
youre too young to be contempt anyways :p
[Nexus One Android Development] makelegs:
So far.... I have no contempt whatsoever for the bfs kernel. In fact... I'm perfectly....content. ;)
[Nexus One Android Development] simms22:
Updated kernels http://wildmonks.whoisthedrizzle.com/kernel/2.6.35/112010/

read @wildmonks tweet for the changelog ;)
[Nexus One Android Development] makelegs:
Crimeny!... Where to begin? :)
[Nexus One Android Development] wildmonks:
Cool, maybe I can just leave it to you to update the thread concerning my releases :D
[Nexus One Android Development] jameztcc:
Cool! Just updated, previous 950 AVS bfs worked well. Now trying this out.
[Nexus One Android Development] simms22:
:eek:

btw, no freeze, zombiness, wake problems with 2.6.35.8_SVS-975mV_BFS_AXI_720p_1152MHz_Custom_112010.zip at all. running great listening to pandora and wirelessly tethering right now.
[Nexus One Android Development] Imperial.mack:
I tried bfs but its just not as smooth as cfs. Like I would watch a flash video, press home, then bring it up again n it will start cracking and skipping slightly. That didn't happen with cfs. And browser scrolling is more jumpy then cfs. Just my 2 cents.

Sent from my Nexus One
[Nexus One Android Development] jlevy73:
Which Rom are you using?
[Nexus One Android Development] Imperial.mack:
Cm nightly, 253 I think. Oh and I always use avs, 950 kernels for what its worth

Sent from my Nexus One
[Nexus One Android Development] jlevy73:
I installed the BFS 11/20 975mv kernel and so far so good. Very fast indeed, no lockups yet. Curious to see about battery life.
[Nexus One Android Development] simms22:
the bfs battery life is still treating me well. btw, check your pm's :)