yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] makelegs:
I guess I fell asleep, or something. I picked up 111410_beta2. Where the heck did these other betas come from??? :eek:

Edit: Nevermind.... found it. This is like some strange live action video game where you just keep snooping and digging around until you find the hidden treasure! ;)

What's the consensus on battery life effect using 975mV vs. 950mV???
[Nexus One Android Development] simms22:
i was having problems with freezes, nexus zombification :eek:

mik101 was probably also having issues. wildmonk made us some test kernels to figure out what the problem is. the beta2(35.7) works great for me too. the 1st beta froze my phone in seconds of any kind of multitasking with pandora or the browser.
[Nexus One Android Development] makelegs:
Looks like I'll be taking beta3 for a more thorough test drive, tomorrow. So far seems to be playing nice with 250.
[Nexus One Android Development] mik101:
Thats exactly the issue I was having. This kernel has been terrific so far. One reboot and no freezes. I think the reboot has to do with the live wallpaper I was using. Switched to a static one a few hours ago and its been rock solid since.

Been testing at pretty much everything between 128 and 1152mhz :)
[Nexus One Android Development] nitrox1:
Hello, I suggested even dropping the kernel to 875-925mV, as that was possible on the htc desire. Is the nexus one, really that much more unstable at 925-950mV? Is there a reason why?

Yes cpu's are different and don't all have the same structure, but are you saying the nexus one has a lesser quality cpu in general then?

Sent from the 25th century.
[Nexus One Android Development] mik101:
I suspect mine was a refurb.... but it was given to me so meh.
[Nexus One Android Development] damanrico:
Speaking for myself, I have a N1 that has trouble with low voltages. I can't even use the 950mV versions Wildmonks releases. My phone needs to have at least 1025mV it seems. The lower you set the voltage, the more people will probably have issues.

BTW, nice to see you back wildmonks :). Seems like a lot of users are happily using your kernels again.
[Nexus One Android Development] flak0:
@wildmonks hey man as always amazing work. Dude did u see the post in the general nexus forum about a kernel responsiveness fix that was approved by linus . Apparently we get a 60% increase in responsiveness and -10% on lag. Please incorporate this. Thanks dude. IR seems to have a test kernel out there.
[Nexus One Android Development] uw748:
Heh, I'm pretty sure wildmonks will not be missing out on testing out this kernel fix. I mean it's just too tempting. For all we know, he could already be compiling and testing the kernel right this very moment!

Patience is key here, and I can't wait for wildmonks to realease the next version.

Using latest AVS/CFS and loving it on my N1.
[Nexus One Android Development] fitsnugly:
already sent it to him yesterday via twitter ;)
[Nexus One Android Development] mik101:
I imagine we'll get the patch when he adds the new commits from IR's github.

The Nov 16 version of IRs kernel floating around has the fix in it -- but that kernel is unstable on my phone for the reasons we discussed above.

BTW. 1750 in quadrant -- best my phone has ever done by just over 150pts!
[Nexus One Android Development] duggey:
It looks like he already rolled it together... check out his website:

wildmonks.whoisthedrizzle.com/kernel/test/111710/

There's a changelog that sorta reads like he's already testing it out...
[Nexus One Android Development] simms22:
i just flashed the 2.6.35.8_SVS-975mV_CFS_AXI_720p_1152MHz_111710_beta1.zip so far so good :D
[Nexus One Android Development] nitrox1:
Hi, just trying to get a feel for nexus one's kernels when you say you like 1025mV how do you create that? Do you manipulate the setcpu mhz? As pardon my ignorance, but the avs kernel should always use the right voltage, For stability shouldn't it? Or do you allow the avs kernel the extra voltage?

Am I entering a world of people self adapting kernels?

Sent from the 25th century.
[Nexus One Android Development] j3di:
Interestingly my phone locked up with just about most of the 35.8 SVS/CFS kernels that WM has pushed out recently, even the beta versions.

I switched to the AVS/BFS kernels and didn't get a single lock-up or reboot. I am also pleased to say that i'm now on the

2.6.35.8_AVS-950mV_CFS_AXI_720p_1152MHz_111710_beta1.zip and all I can say is WOW!

Thanks, Great Work WM!
[Nexus One Android Development] simms22:
i had lock ups on all the past kernels too. as soon as i switch over to 975, no lockups :)
[Nexus One Android Development] j3di:
I spoke too soon, phone locked up upon opening Reckless Racing. Oh well, just flashed the 2.6.35.8_SVS-1050mV_CFS version. See if the increase in voltage will help. Weird though because it doesn't play up with the 950mV BFS/AVS versions...
[Nexus One Android Development] temasek:
Latest beta1 super snappy! Its a big WOW! Lets call it stable 111710. Lol. :)
[Nexus One Android Development] codesplice:
Quoted for troof.

Scrolling is so slick now.

Great job, wm!
[Nexus One Android Development] mtw4991:
Which one are you guys using? 950/975/1025?
[Nexus One Android Development] codesplice:
I'm on 950. No issues so far.
[Nexus One Android Development] simms22:
975 for me :)
[Nexus One Android Development] temasek:
950 for me
[Nexus One Android Development] mtw4991:
Avs or Svs? Trying the avs and not seeing a noticeable difference? What does linpack/quadrant score for you?
[Nexus One Android Development] samarium:
Have a look around wildmonks kernel download area and you will find them.

This is exactly what woldmonks, pershoot, intersectRaven etc are doing, self adapting kernels. If you mean are people who are not compiling kernels are patching binary kernels, I don't think so in this case, however it wouldn't be that difficult, and certainly easier now than it was 20 years ago when I can last recall kernel patching a UNIX Edition VII kernel to disable the busy test loop on the console output code because the console was broken.
[Nexus One Android Development] nitrox1:
Thanks,

was more thinking along the lines of people taking WM, Ir, and perSh, kernels, and then adapting the voltages for their own needs.

Have just discovered Wildmonks area, have been a little nosey, but as always for me, I will wait till he's happy, then install his released updates.

Had problem a while back going through original HAVS and then second run of initial HAVS releases, with bad BSOD on the desire.
[Nexus One Android Development] j3di:
I'm on the 1050mV flavour. Performance is very good and it's also behaving by not locking up on me so far!

Would love to try an AVS version of this or the 975mV kernel...

#Edit Just tried the 975mV kernel but for me it's no good, had a couple of freezes straight away when i started up Reckless Racing...
[Nexus One Android Development] temasek:
Svs 950......I don't care about benchmarks. I feel.......... :)
[Nexus One Android Development] mtw4991:
Always used svs, thought I would try avs for a change. My n1 likes 950 also... Don't care about benchmarks much either, but it's something to measure with other than just feel and intuition.
[Nexus One Android Development] j3di:
I wonder why i get more stability with higher voltage kernel or AVS over SVS. Does AVS do a better job of upping voltage with CPU load?

Right, i'm being quick to blame the kernel, sorry WM. Maybe it's Reckless Racing? I'll reinstall it later. In the mean time i've gone back to 950mV_AVS kernel and giving the racing game a night off.

I ran SetCPU Stress Test for a while at max clock freq on the 950mV kernel and no errors. That's got to be good right?
[Nexus One Android Development] temasek:
At 1075mhz linkpack max I got 37.8. Avg abt 37. Main profile I don't go beyond 1075mhz.
[Nexus One Android Development] uw748:
This kernel improvement is totally like a hardware upgrade for the nexus one, unbelievable! Using AVS 950mV beta1 and the OS just flies! And it might just be my imagination but enabling surface dithering in CM6.1 RC1 seemed to make it smoother.

Some previously slight input lags are all but eliminated now, the screen scrolls to where I want and web pages follow my finger almost immediately (where previously the web page won't start to move after my finger moved about quarter of an inch).

Haven't tested other features yet, but what an unexpected surprise this kernel fix is!

Great appreciation towards wildmonks for the hardwork!
[Nexus One Android Development] jameztcc:
Trying 950 avs beta1 ... ...

A question, will bfs be taken out of future release?
[Nexus One Android Development] knightnz:
Just ran Quadrant with beta1 here, 950mV SVS @ 128/1152Mhz, interactive governer. Got 1779 which is better than I've managed before (almost the magic 1800!) I've found that it's pretty sensitive to anything else running on the system though. It certainly feels pretty smooth.

Edit: 1785 that run with 1152/1152 & performance governer, so close...

Edit2: Woot! Killed some stray processes and got 1816 quadrant while using the OnDemand governer. Running a CM6 RC1 nightly from earlier in the week (246 I think).

Nice one WM!
[Nexus One Android Development] makelegs:
246 was pretty flippin' sweet!
[Nexus One Android Development] wildmonks:
So from the feedback I'm getting, it looks like the changes I did when going from 35.7 to 35.8 made some phones more unstable and increasing the voltage seems to have restored stability.

FYI: anything under 1050mV is considered undervolting for the Nexus One.

I unfortunately don't have time right now to make any kernels but I'll try to push out a general release in a day or two :)
[Nexus One Android Development] Autinhyeu:
+1 for new release base 35.7 111010 :) i think its stable + good batterylife
[Nexus One Android Development] Vlad83:
Thanks WM. The 11/17 beta1 works great for me...
[Nexus One Android Development] wildmonks:
No problem :). Curious, which kernel of 11/17 are you currently using?
[Nexus One Android Development] wildmonks:
Thing is I don't know exactly what is causing the instability increase in 35.8. :confused: From 111010 to the 111710 beta 1, pretty much only 3 major things were added. RCU changed to preempt+boost, battery driver update, and the scheduler patch. I suspect its the RCU change.

Oh, and totally scraped the source for 111110b so the latest beta1 has no connection with that base.
[Nexus One Android Development] temasek:
.35.8 11110b and the. 35.8 beta1 17 nov, all stressed tested superb. No issues at all. But beta1 superior.

I am starting to love monks!
[Nexus One Android Development] wildmonks:
Not sure what to say to that except thanks! :p
[Nexus One Android Development] simms22:
i see youre starting an aggressive advertising campaign... :p
[Nexus One Android Development] wildmonks:
omg.. lets do the world a favor and end it right here. :rolleyes:
[Nexus One Android Development] simms22:
i must have posted the wrong pic, this is the right one :p
[Nexus One Android Development] temasek:
Good stuffs let share to all. :)
[Nexus One Android Development] mik101:
I'm trying to stress tests all the voltages of the nov17b1. So far my phone is unstable with the AVS kernel and SVS kernel at 950mV. I ran it with 975mV most of the day with only one program crash. I'm going to try the one that's default voltage and see how it behaves tomorrow before saying for sure that it's any more stable for me than 975mV.

What I can say is I don't think my phone in particular will ever be stable with 950mV.

Thanks for your hard work!

Edit: So far 975mV is the ticket for my phone.
[Nexus One Android Development] jlevy73:
lmao, that's hilarious.
[Nexus One Android Development] temasek:
I used setcpu for stress test for hours and waited till I sleep. No issues. Is there a better stress test app?
[Nexus One Android Development] simms22:
i just put it through as heavy of a workout as i can
[Nexus One Android Development] jlevy73:
That should do it. Or you can play angry birds while listening to Pandora, browsing and gtalk at the same time :)
[Nexus One Android Development] temasek:
How I wish I can use Pandora. I heard so much about it. *sigh* I am outside the great USA.
[Nexus One Android Development] temasek:
Why don't setcpu perform stress test in background and let me try stuffs in the foreground. Lmao. Sure can stress even further. Hopefully can brick my n1 and my wife will allow me to buy n2. Lol :)
[Nexus One Android Development] samarium:
When you do make another one, hopefully you will look at cherry picking the "sched: update "automated per tty task groups" to email @ 2010/11/15 - 3:25 PM " intersectRaven kernel commit https://github.com/intersectRaven/ir-kernel/commit/ee107c66cba8ce5397dcccf983d1da21ab48426c for your CFS kernel.

I'm currently using 2.6.35.8_AVS-950mV_CFS_AXI_720p_1152MHz_111710_beta1.zip because you have both the IR patches and the ds2784 patches, and it works well, thanks.
[Nexus One Android Development] simms22:
thats the spirit ;)
[Nexus One Android Development] temasek:
EDIT:- Deleted
[Nexus One Android Development] nitrox1:
Ah, still just surprised they have the desire with same cpu hardware, maybe not all the same hardware eg. Trackball and second mic. But have it running now completely stable at 925mV, with havs, and both bfs & cfs. Even some of the phones were capable of 875mV like I mentioned.

Can't remember what the desires normal voltage is, but am amazed to see an 800mV kernel floating around for the n1.

And just for inpu,t 3 days now no problems as long as I don't use any other governor than ondemand.

Avs,bfs,950mV kernel. Setcpu set to 245-1113mhz ondemand, screen off profile 245-384mhz ondemand.

Have to admit my phone doesn't seem to like different governors, and 128 mhz makes it a little wobbly. Also I have no reason for 1152 mhz.

Thanks WM.

Sent from the 25th century.
[Nexus One Android Development] ~semsem~:
Thanks Monks, the AVS1117b1 is working flawless on CM250, it makes me feel like i hv upgraded my HW, keep the good work:)
[Nexus One Android Development] mik101:
I don't get much performance difference based on the clock scheduler alone. I usually leave it at on demand. If you need the extra cpu cycles, bump the minimum clockspeed temporarily instead.

Pretty sure most kernel devs are still saying the ondemand is stable and the interactive scheduler is in testing. I swear i read somewhere that IR doesn't recommend using profiles either but don't quote me on that; I'm tired.

I'm testing full range 128mhz-1152mhz and all is good for me with the 975mV kernel. I don't think the problem is just the minimum voltage. I think its a waking issue coming out of a low power state (bigger change in voltage suddenly). Ofcourse this is all just speculation. Forgive my ramblings.
[Nexus One Android Development] jlevy73:
Yes, you are very correct in that the predominant issue is waking up the phone coming from a low power state. Each kernel developer goes about solving the problem a little differently.

One of the culprits is the voltage used. The Nexus one stock voltage uses a minimum of 975mv and a maximum of 1275mv (although the N1 was supposed to ship at 1300mv and Google changed it at the last second). Obviously each phone will respond a bit differently but mines works best when the minimum voltage is set to 975mv. At 950mv I find myself getting lag and wakelock issues.
[Nexus One Android Development] mik101:
I get lag and wakelock issues with 950mV kernels most of the time too.

Has anyone done any research on the steppings of these cpus? Could explain why groups of people end up having similar experiences with various kernels (at various voltage levels).

As far as the clock scheduler affecting stability -- I thought about it some more. I imagine the wake bug will show itself even more the more aggressively the clock speed is changed. nitrox1 I suspect a little more voltage towards stock would fix it (or at least help) with the other schedulers.

Playing around with my phone at different voltages with each of todays test kernels seems to agree, atleast on my N1.
[Nexus One Android Development] nitrox1:
I still have to admit for the sake of a little lag, hours of extra battery life is important. I've heard of 2-3% drop in a night time period, and an approx 1% drop per hour on the snapdragon cpu. And my best has been on this kernel 30% drop in my usual day time use, which is still great!

I will bow out on this, I will try a very low mV kernel, and see for myself, can it really be that bad? But I'll be back ;-)

PS Wildmonks, thank you for making us a very stable and quick kernel, and I'm sure we all want stability over anything else, thank you again for your time.
[Nexus One Android Development] jameztcc:
Following up own post, seemed like stability is there. Feels smooth and used with camera, YouTube, email and call. Hope 950 still be avail in future to test.
[Nexus One Android Development] ChongoDroid:
I'm running the 950 now without any flaws on miuimod 1.8.1. I wonder why some n1s dont like 950
[Nexus One Android Development] temasek:
All n1 are the same yet different - reactions/tolerance to voltages.

---- from my very limited understanding
[Nexus One Android Development] jameztcc:
Am missing ipv6 module for Google Goggles. Is it somewhere or got to wait for another release? Thanks!
[Nexus One Android Development] samarium:
There seems to be some ipv6 tunneling support in the WM kernel from looking at the included module list.

I believe that intersectRaven's kernel also has some ipv6 support, however don't have one currently downloaded to inspect.
[Nexus One Android Development] jameztcc:
Goggles refused to run, saying phone doesn't have ipv6. Am on cm6.1 rc1 by the way.

I did lsmod, no ipv6.

$lsmod

bcm4329 176512 0 - Live 0xbf02e000

$ uname -ani

Linux localhost 2.6.35.8-wildmonks #151 PREEMPT Wed Nov 17 00:18:14 PST 2010 armv7l GNU/Linux

$
[Nexus One Android Development] ZetaTre:
I'm trying to narrow down the volume problem with Kineto: basically when on WiFi calling, the volume is a lot lower than when using cellular connection.

Any sense on whether this could be introduced with the required kernel changes?
[Nexus One Android Development] Vlad83:
I am using the 975 svs but I never had problems with the 950 11/11 kernel... The beta1 seems a tad faster...
[Nexus One Android Development] codesplice:
Confirmed. Same behavior here.
[Nexus One Android Development] simms22:
theres another set of test kernels out for today http://wildmonks.whoisthedrizzle.com/kernel/test/111810/

975 is all mine :D

changelog...
[Nexus One Android Development] fitsnugly:
nom nom nom nom
[Nexus One Android Development] ~semsem~:
Lol flashing the latest WM kernels is better than sex:)
[Nexus One Android Development] simms22:
well...

i dont see why they cant be done at the same time :D
[Nexus One Android Development] jlevy73:
Thanks man. Are you using AVS or SVS?
[Nexus One Android Development] ~semsem~:
AVS now is very stable for me, if yr device can handle it, its better than SVS..
[Nexus One Android Development] wildmonks:
Opps, my bad :( I left out ipv6. Thx for reporting. Will add it back in and release a 11/18 beta 2.
[Nexus One Android Development] jlevy73:
You mean 11/18 :)
[Nexus One Android Development] wildmonks:
lol, yah :rolleyes:

And, I'm using AVS at the moment (@975mv but 950mv works just as well for me)
[Nexus One Android Development] simms22:
svs

sweet! we get to flash again :D
[Nexus One Android Development] fitsnugly:
Wow. You must be getting sex from the WRONG places. ;)
[Nexus One Android Development] pwig:
Is there any way to tell what kernel you are running? I flash them so often to find one that I like and in settings about it doesn't give enough info.

I really like the one I am running but can't remember which one it is!
[Nexus One Android Development] simms22:
hes got another chance to see which is better...

beta2 is up http://wildmonks.whoisthedrizzle.com/kernel/test/111810/beta2/

THANKS Wildmonk :)
[Nexus One Android Development] fitsnugly:
were you in that folder hitting refresh waiting for them to upload, too? ;)
[Nexus One Android Development] simms22:
no, working with a customer. but i checked just in time :)

btw, beta2 is up and running. btw, goggles still doesnt work.
[Nexus One Android Development] wildmonks:
Strange, its working for me (AVS 975 beta2). I'll try your SVS kernel.
[Nexus One Android Development] simms22:
i cleared its data and i unistalled/reinstalled it to make sure it wasnt leftover data. btw, its the avs 975. i tried that one this time.
[Nexus One Android Development] wildmonks:
SVS 975mV beta2 works as well. Try reflashing the kernel.
[Nexus One Android Development] temasek:
Google googles doesn't work on SVS 950mV beta2, say doesn't have ipv6. I try the avs now.
[Nexus One Android Development] wildmonks:
SVS 950mV beta2 works for me :confused: Is there a difference in googles version? I have 1.2.1
[Nexus One Android Development] temasek:
I reflash the beta2 svs 950mV and now it works. Funny. :)
[Nexus One Android Development] simms22:
working perfectly fine now. thanks :)
[Nexus One Android Development] wildmonks:
oh good. You guys were scaring me :p
[Nexus One Android Development] simms22:
im running the svs 950 this time beta2(flashed the wrong one accidently), working great for me now
[Nexus One Android Development] j3di:
WildMonks,

Just out of curiosity do you use SetCPU?
[Nexus One Android Development] wildmonks:
Yes, I do.

min: 245

max 1113

ondemand

Profile

Screen Off

min: 128

max: 998

conservative
[Nexus One Android Development] makelegs:
I noticed this, too. Volume on wifi is definitely lower!
[Nexus One Android Development] makelegs:
Out of curiosity.... Do you folks actually use Google Goggles a lot? Or is that just an app that is being used to debug b/c it seems to break easily?
[Nexus One Android Development] simms22:
i rarely use it. was just testing making sure it worked, since the problem was kernel related.
[Nexus One Android Development] nitrox1:
or your doing it wrong ;-D

Sent from the 25th century.
[Nexus One Android Development] j3di:
Cheers, many thanks!
[Nexus One Android Development] simms22:
i had to go back to a 975(svs) from the beta2 950(svs). it started giving me slow motion scrolling on certain apps. i tried. so close yet so far away :)
[Nexus One Android Development] big_adventure:
There is no question that ondemand, even at a lower speed, will "feel" faster than conservative at a higher speed. As far as I can tell, the Conservative governor starts the CPU slow, then feeds more and more speed in as long as there is a shortfall, eventually arriving at the highest speed. Ondemand immediately scales up to the maximum speed, then steps back until it finds a sweet spot where supply = demand. Thus, that first response will always be faster with ondemand, even if the overall max speed is slower, because it starts at the max and then steps down, versus the conservative starting slow and working up. The overall task might even take longer, but because the first response is much faster, it will "feel" faster.

Anyway, I've been using this beautiful kernel since last week, the .34 800 BFS OC'd to 1.113, and I've experienced zero FCs, excellent performance, no reboots, no radio problems - nothing bad at all. I took photos and videos, posted them to facebook, gmail and twitter, played games, used my Reader, listened to music, watched a few videos, showed off Flash, did some searches, used Maps/GPS, and have WiFi running and controlled by Y5 - and I've not seen the slightest issue. I don't really use USB mounting so that hasn't been a problem.

Wildmonks, if you put up a link, I'll buy a beer...