yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] Latentk:
Oh jeebus I hope so. My wifi does all kinds of weird stuff. Sometimes it simply refuses to connect to my network, and if the SSID is hidden it gets really angry...
[Nexus One Android Development] uoY_redruM:
Mine has been working fine, connection wise, but I'm not getting a "good" connection....like super super laggy when playing CoD which it never did before.
[Nexus One Android Development] Latentk:
That is another thing. The speeds I once got are long gone since I started flashing ROM's and kernels. I had no idea it'd be the kernel, but that does make sense. What in particular did IR "fix?"

And Monks or anyone else, can you link your donation page?
[Nexus One Android Development] navillos:
i use both of these kernals and they both have problem with the camera. not the 720p problem but another. the flash doesnt go off at the right time. meaning that the flash is done with before the picture gets taken. its weird but they both have the same problem.

2.6.35_SVS-950mV_CFS_AXI_no720p(stockFRF91)_1113MHz_081610

2.6.34.2_SVS-950mV_CFS_No720p_1113Mhz_080610
[Nexus One Android Development] ChronoReverse:
I was about to comment on that myself. I'm still using the original test build you made for me but the flash is always too early and turns off just as the picture is taken (leading to a nearly black picture).
[Nexus One Android Development] mescieux:
Me too. I'm using the following:

2.6.35_AVS-925mV_CFS_AXI_no720p(stockFRF91)_1228MHz_081610

Either flash is early or shutter is late by a split second.
[Nexus One Android Development] elmerendeiro:
Im having total freeze after boot with your latest 925 avs cfs 720p with axi and without axi, CM rc3
[Nexus One Android Development] Vlad83:
Using and loving the 8/19 925 cfs with Enom's rom. A lot faster yet economical with the 128mhz setting. Great work once again monks!
[Nexus One Android Development] atomizasser:
What about this version "2.6.35_AVS-925mV_CFS_AXI_BFQ_720p_1113MHz_081710.zip". Nobody try it? I installed this version at 8 am with 100% of battery. I used sometimes 3G with NewRobs (abaou 1 hour), the only with syncronization a 2G. Now at 17.11 PM only have 76% of battery. It is normal?
[Nexus One Android Development] mtw4991:
I tried it this morning and was getting freezes at boot and fc's once booted. Might be that I need 950mV, who knows.

Wildmonks, is this a true AVS now or fake avs/svs like the other day, lol.;)
[Nexus One Android Development] mousse04:
+1
[Nexus One Android Development] wildmonks:
Update for kernels 35

-Changes since 081610

-Rebased source from IR's github

-Added Cyanogen's 720p modifications.

-net: wireless: bcm4329: Disable packet filtering

-vmscan: raise the bar to PAGEOUT_IO_SYNC stalls

-input: synaptics_i2c_rmi: duplicated_filter to throttle touch events

-block: introduce the BFQ I/O scheduler

-in an effort to keep AVS stable, only min. 950mV is available for AVS. (Note: A full set of SVS kernels has been made for this release in both 925 and 950mV variety).

Link to Kernels

MediaFire Mirror Link

Kernel Source

Full set of the No720p kernels will be made available later today and then after that I'll make the 1228MHz Test kernels.
[Nexus One Android Development] wildmonks:
Yah, I was testing that kernel out all day yesterday and encountered 3 freezes. I have since scrapped my source and started all over with a fresh pull from IR's github. In this latest 081910 release, I included SVS kernels and if someone wants to test, a small set of 950mV AVS kernels. All of these have 720p, I'll work on a full set of no720p kernels and then tonight a set of 1228MHz for you MHz speed fanatics. ;)
[Nexus One Android Development] dharani1234:
WIldmonks ....

Thanks a lot for your hard work ...

what are "touchscreen coordinates correction" changes ?
[Nexus One Android Development] elmerendeiro:
i'm trying the cfs one :)

EDIT: it rebooted by itself once ended the first boot...but it's ok now
[Nexus One Android Development] wildmonks:
Sorry, I didn't need to have that change listed. Its actually been in all kernels since the early part of the year (I think). Its just code to increase the accuracy/sensitivity for the capacitive buttons (back, menu, home, search).
[Nexus One Android Development] Robdyx:
Testing 2.6.35_SVS-925mV_CFS_AXI_720p_1113MHz_081910.zip

Let's see hows it goin'
[Nexus One Android Development] wildmonks:
CFS has been working well for me. BFS hasn't really since BFQ was included. I sometimes get weird benchmark numbers with BFS+BFQ but then maybe this is just me.:confused:

(This is with SVS)

I'll load up the AVS 950mV CFS kernel on my phone to test out today to see if it will freeze, crash, etc.
[Nexus One Android Development] damanrico:
Thanks a bunch for creating me a new custom kernel, wildmonks.

The last few have been working out great for me.

I know you're quite busy, but I hope you have time to answer these quick questions:

- Is the 1050mV SVS kernel actually more energy-efficient than the

old

AVS system that apparently wasn't working correctly? (since you said something about it sticking to 1225mV if I"m not mistaken, so 1050 sounds better than 1225, or am I missing something important?)

- I see you also created another AVS kernel for me to test. Does this mean that you think my phone can handle AVS, even though it can't handle 950mV SVS or lower? If so, what are the benefits, because I can't imagine AVS can do it's job when my phone needs at least 1050mV for it to not freeze.

To other users: please ignore this post, this has nothing to do with the main kernels you use. It's specifically about a custom kernel wildmonks is kind enough to create for me.
[Nexus One Android Development] Latentk:
Eagerly awaiting the TEST kernel releases :P! I've been spoiled by the unobtainable allure of 1228Mhz!
[Nexus One Android Development] mtw4991:
Just flashed the 950-AVS-BFS-0819...booted fine, linpack max was 35 vs. pershoots=36-37's. went to speed test....total freeze and battery pull:(

EDIT: Boot attempt #2: booted fine, turned on System Monitor by itself during lockscreen ramp up..weird. Same 35 linpacks...max 1644 quadrant..not bad so far
[Nexus One Android Development] elmerendeiro:
freeze + battery pull

950 AVS CFS AXI 0819

i'm giving it a second chance :)

EDIT: flashed svs, I'm going to play some football, I don't want to find my phone fried because of a freeze :)

will be happy to try next AVS release when it comes out
[Nexus One Android Development] notxel21:
I've been using the 2.6.35.2-925mV-CFS-SVS-AIX-720P-Monks-081910 with no issues since this morning.

Thanks Wildmonks!! :cool: Great work!! :)
[Nexus One Android Development] mtw4991:
2.6.35.2-925mV-BFS-AVS-AIX-720P-Monks-081910 3rd boot worked like a charm. No freezes or reboot yet...moderate usage, etc,etc....will keep an eye on it:p

EDIT: just realized I had VM Heap size set to 16 instead of 32 as I was trying Pershoots new kernel from this morning....wonder if it's helping or hurting as I really don't have a clue what Heap size does, lol:o
[Nexus One Android Development] fitsnugly:
Agreed. So far so good.
[Nexus One Android Development] atomizasser:
Where do u download the kernel? in media folder only existe 950mv version. I am trying old AVS-925mv version with CFS -AVS-AIX-BFQ and works perfect, not freeze.
[Nexus One Android Development] atomizasser:
Can u add a 925mv AVS version? I am trying old version that i publish some post before and works perfect and battery life is good.
[Nexus One Android Development] mtw4991:
here ya go:

http://www.mediafire.com/?qg50w6nb9ady6

OOPS, Just realized that I typed 925mV instead of 950mV. This is the one I'm using:

2.6.35_AVS-950mV_BFS_AXI_720p_1113MHz_081910.zip
[Nexus One Android Development] uoY_redruM:
Ok...

Flashed 2.6.35_AVS-950mV_CFS_AXI_720p_1113MHz_081910.zip and so far, so good. Booted right up. Seemed a little less "snappy" on scrolling home screens, initially, then seemed fine.

Will test all day today/tomorrow and see what happens.
[Nexus One Android Development] poochie2:
Will there be any more 900mV SVS 1228 MHz TEST kernels? I'm so in love with them! Keep up the good work ;)
[Nexus One Android Development] kaotikking:
+1 on the 900mv, im loving the battery life!!!

Sent from my Nexus One
[Nexus One Android Development] atomizasser:
Hello Wildmonks. Can u add this kernel "2.6.35_SVS-900mV_CFS_AXI_720p_1228MHz_081910.zip" but with AVS? Actuallly i still using "2.6.35_AVS-925mV_CFS_AXI_BFQ_720p_1113MHz_081710.zip" and ROCKZ!! 24hours with the kernel!!! Battery life is wondferful. All time with sync, sometimes with 3G, and always with 2G. Fantastic!!
[Nexus One Android Development] wildmonks:
It should be more energy efficient for the reasons you stated. As for the AVS, I thought maybe by some small chance this AVS could work for you, but from the feedback I'm getting, its probably best not to use AVS.

Sorry for the delay, but you'll have to wait a little longer. I've been struggling a little with the No720p kernel versions. It seems some of the commits I added from the cyanogenmod github has produced a delay in the camera flash for stock FRF91 based roms. Trying to get rid of that before moving on to making 1228MHz TEST kernels.

Thank you so much for your feedback, guess AVS still needs a little work.

I also got that less snappy feeling initially. This occurred after BFQ was to the kernels.

Sure, here you go! I only happened to make these kernels because kaotikking PM a request speficially for this type of kernel so he's the one you should thank :)

Look here in the Custom Variants folder for the kernels.
[Nexus One Android Development] wildmonks:
Oh wow, okay sure! I'll make this right now for you, then return to work on the No720p kernels. I'll also throw in a 925mV AVS kernel in case 900mV doesn't work for you (I'm thinking you'll get boot loops with 900mV CFS AVS but I could be wrong).
[Nexus One Android Development] jonata:
hi,

whre i can found this kernel ?

try but not found ....

tks
[Nexus One Android Development] wildmonks:
Click here, it will take you directly to the folder. Now back to work on the No720p kernels.
[Nexus One Android Development] jonata:
grazie, tks, merci ....

;)
[Nexus One Android Development] pakraider:
WM, 2.6.35_AVS-900mV_CFS_AXI_720p_1228MHz_081910.zip is amazing. its stable, and silky smoooth! The Linpack scores are low though (getting 29-31 @ 998 MHz); is this because of the BFQ code perhaps? this kernel is definitely snappier at UI interactions etc., so a bit confused as to the hit on Linpack.
[Nexus One Android Development] atomizasser:
Hey i think is better more battery life than a high performance. No? What do u think?
[Nexus One Android Development] pakraider:
Definitely :) I don't care for the latest and greatest OC speeds or Linpack scores (I stay at a max of 998MHz and find it fast enough for everything I do).. was just curious about things going on under the hood.
[Nexus One Android Development] wildmonks:
I think BFQ might have something to do with it too. It's really the only main difference between this kernel and the last released kernel that can affect performance for a task.

In other news, I'm too close getting the no720p kernels working, but it will have to wait till I get some sleep before I make a full batch. In the mean time I did make some 1228MHz SVS test kernels. You can find them in the usual test folder (direct link here).
[Nexus One Android Development] poochie2:
Thanks, you are my saviour indeed! I only had a little old request left for the 900mv test kernel: could I have the complete frequency/voltage table so that I can try to enable only the highest freq for each voltage?
[Nexus One Android Development] wildmonks:
For the 900mV kernel, the voltage table would look like this:

struct clkctl_acpu_speed acpu_freq_tbl[] = {

{ 19200, CCTL(CLK_TCXO, 1),	SRC_RAW, 0, 0, 900, 14000 },

{ 128000, CCTL(CLK_TCXO, 1),	SRC_AXI, 0, 0, 900, 14000 },

{ 245000, CCTL(CLK_MODEM_PLL, 1),	SRC_RAW, 0, 0, 925, 29000 },

{ 256000, CCTL(CLK_GLOBAL_PLL, 3),	SRC_RAW, 0, 0, 975, 29000 },

{ 384000, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x0A, 0, 1000, 58000 },

{ 422400, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x0B, 0, 1000, 117000 },

{ 460800, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x0C, 0, 1025, 117000 },

{ 499200, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x0D, 0, 1050, 117000 },

{ 537600, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x0E, 0, 1050, 117000 },

{ 576000, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x0F, 0, 1075, 117000 },

{ 614400, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x10, 0, 1100, 117000 },

{ 652800, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x11, 0, 1125, 117000 },

{ 691200, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x12, 0, 1150, 117000 },

{ 729600, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x13, 0, 1175, 117000 },

{ 768000, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x14, 0, 1200, 128000 },

{ 806400, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x15, 0, 1225, 128000 },

{ 844800, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x16, 0, 1250, 128000 },

{ 883200, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x17, 0, 1250, 128000 },

{ 921600, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x18, 0, 1275, 128000 },

{ 960000, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x19, 0, 1275, 128000 },

{ 998400, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x1A, 0, 1275, 128000 },

{ 1036800, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x1B, 0, 1275, 128000 },

{ 1075200, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x1C, 0, 1275, 128000 },

{ 1113600, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x1D, 0, 1275, 128000 },

{ 1152000, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x1E, 0, 1300, 128000 },

{ 1190400, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x1F, 0, 1300, 128000 },

{ 1228800, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x20, 0, 1325, 128000 },

{ 0 },

};
[Nexus One Android Development] Cpt.Curry:
so which is the best 720p kernel for battery life with enoms rom, I don't really oc, i usually keep it at 998mhz or 1075mhz, but I care a lot about battery life....
[Nexus One Android Development] wildmonks:
Give the 900mV kernel a try first. If its unstable for your phone then move up to 925mV or 950mV.

I'm currently have my SetCpu set at min 245Mhz, max 998MHz, interactive with a profile Screen Off with min 128MHz, max 998MHz Conservative.
[Nexus One Android Development] Cpt.Curry:
thanks a lot wildmonks...love your kernels...
[Nexus One Android Development] mezmer1ze:
With 925mV CFS SVS AIX from 19.8.2010 camera flash doesn't work at all for me, I'm on CM6RC3, I had no problems with kernel from 10.8.
[Nexus One Android Development] MicroMod777:
That 900mV looks good! Gonna test out for a super battery saver for Enom's ROM!

Thanks :)
[Nexus One Android Development] musashiken:
Geh first thing I see after flashing the 900mv is my sd card being damaged. And a reboot. And I forgot to do a nandroid. Now my phone works but with a damaged sd card. My apps2sd still works but my fat32 storage is gone... any ideas what to do?

Edit: Ran a chkdsk on my sd card to repair errors and all is working again :/
[Nexus One Android Development] nxt:
Am I blind? Where's the links to the new 081910 updated files? I didn't see 081510 either.

I only see 081010 and 080710.
[Nexus One Android Development] damanrico:
Wildmonks has been very busy, so that's why he probably forgot to update the first post. Just go to his mediafire account to see the latest versions: http://www.mediafire.com/wildmonks
[Nexus One Android Development] Robdyx:
2.6.35_SVS-925mV_CFS_AXI_720p_1113MHz_081910 is working like a charm, now I think I'll risk with 2.6.35_AVS-900mV_CFS_AXI_720p_1228MHz_081910 and if it doen't work, with 2.6.35_SVS-900mV_CFS_AXI_720p_1228MHz_081910....

I'l keep you informed.
[Nexus One Android Development] Bidshelf:
I'm just waithing for no720p version to upgrade.
[Nexus One Android Development] poochie2:
Thanks a lot!
[Nexus One Android Development] ChronoReverse:
Interesting table. 1050mV at 500 even for the 900mV variant huh? No wonder AVS is having trouble for so many people, it works on my n1 but it will push 500MHz all the way down to 925mV (minimum) after some time :D:p
[Nexus One Android Development] atomizasser:
I am testing 2.6.35_AVS-900mV_CFS_AXI_720p_1228MHz_081910. At moment works like a charm. No problem, only the first and second boot, but i normal use pefect.

Good work. Now i'am charging my battery. The real test will be this afternoon.
[Nexus One Android Development] Robdyx:
I also had some issues after flashing, was going to roll back to SVS 925mV when it stabilized in the third boot, guess it has something to do with the SVS > AVS change..... Now I'll increase the overclock gradually to prevent bricks ;) good luck!
[Nexus One Android Development] ChronoReverse:
Can't wait for the AVS no720p kernel lol
[Nexus One Android Development] wildmonks:
Okay.. finally I think I figured it out. Let me know if it works.

Again here are the links to all the kernels.

-Changes since 081610

-Rebased source from IR's github

-Added Cyanogen's 720p modifications.

-net: wireless: bcm4329: Disable packet filtering

-vmscan: raise the bar to PAGEOUT_IO_SYNC stalls

-input: synaptics_i2c_rmi: duplicated_filter to throttle touch events

-block: introduce the BFQ I/O scheduler

-in an effort to keep AVS stable, only min. 950mV is available for AVS. (Note: A full set of SVS kernels has been made for this release in both 925 and 950mV variety).

Link to 081910 Kernels

MediaFire Mirror Link

Kernel Source

For stock based FRF91 roms, please use the No720p kernels located here. (mirror)
[Nexus One Android Development] wildmonks:
Ack! I'm sorry this has happened to you. :( But thanks for bringing this to our attention. So everyone, please be careful if you really want to try the 900mV SVS kernel.
[Nexus One Android Development] Vlad83:
Wildmonks how can I change the aggressiveness cpu clock switching in set cpu? Its usually switching from 128mhz straight to 1113mhz and I'd like it to go to 1113 only in the most intensive tasks such as flash etc... Is it the sampling rate setting in set cpu? Also, I prefer interactive governor but I see ondemand has more settings...

Thanks.
[Nexus One Android Development] ChronoReverse:
No AVS + no720p?

Incidentally, how about improving the hybrid HAVS so that 128-245MHz still uses the SVS 925mV (for power savings) while 245-1075MHz it uses AVS 950mV (for stability) and then above it uses your SVS again?
[Nexus One Android Development] wildmonks:
I know that there is only one tunable adjustment for the interactive governor but that adjustment only changes how quickly it will ramp down the MHz. There is no setting for ramping up MHz. (And for now, this setting can only be adjusted during kernel compiling).

For the Ondemand governor, you can try adjusting the Up Threshold (Increasing this setting will add resistance to ramping up MHz) or the Powersave Bias (Increasing this setting will have a similar result).

I've tried to play with these settings in the past but gave up and used defaults instead.
[Nexus One Android Development] Vlad83:
Guess I will do some trial and error later. Thanks!
[Nexus One Android Development] wildmonks:
I'll get to making a AVS/No720p kernel the next chance I get. As for you suggestion, I'm happy you put some thought into it. I have started experimenting with using SVS at 1036MHz and above to see if this improves stability for a particular user. I don't know if its working for him as I haven't received any feedback yet but then I did just make it for him.

As for the 128-245MHz@925mV idea, I'll try that out after AVS becomes stable.
[Nexus One Android Development] ChronoReverse:
Heh, hopefully 950mV AVS will prove stable for everyone so a 925/950 HAVS Super wildmonks kernel could be made :D;)
[Nexus One Android Development] wildmonks:
Done compiling and its has been uploaded. You'll find it here or here. :)
[Nexus One Android Development] antiochasylum:
For some strange reason I can use the avs kernel however something happens and my phone becomes non responsive as in black screen and I have to do a battery pull. Its done it on every avs kernel you have recently made. How ever it didn't in the past. I switched to the cfs 925mv svs kernel to see If that works, if it doesn't I'm going back to stock cm6. Hopefully svs will work. And insight on this?

Think my phone can't handle avs?
[Nexus One Android Development] ChronoReverse:
In the past the AVS kernels didn't actually work and was applying even more voltage than SVS.

The current AVS kernels actually do work but it seems very few people have n1's that can handle it (I'm one of the lucky ones where it seems to work).

It's too bad since when I compare the voltages being set by AVS to the SVS table, it's a LOT lower. The 925mV AVS kernel uses 925mV up to 537MHz on my n1 for instance :eek:

Many thanks as usual.
[Nexus One Android Development] wildmonks:
Yah, that's the result of this commit in IR's effort to improve stability.
[Nexus One Android Development] pakraider:
yeah, I spoke too soon--AVS isn't stable on my phone either (950mV doesn't work either)

Back to 900mV SVS. WM, maybe it's worth being a bit more aggressive in the voltage tables for SVS since it seems AVS might not cut it for everyone?

and, great work as always :)
[Nexus One Android Development] Gilg@mesh:
AVS works great on my phone too :D

@wildmonks, could you please release a 925mV AVS version? Im using 2.6.35_AVS-950mV_CFS_AXI_720p_1113MHz_081910.zip and it works great.
[Nexus One Android Development] fitsnugly:
I believe that the voltage was up'd because 925 wasn't too stable...
[Nexus One Android Development] ChronoReverse:
We should compile a list of what works for whom just to get an idea of the distribution.

925mV AVS:

-ChronoReverse (no720p) [Ondemand+Conservative]

-Gilg@mesh (720p)

950mV AVS:
[Nexus One Android Development] wildmonks:
You can use my kernel that I'm personally testing.

2.6.35_AVS-925mV_CFS_AXI_720p_1228MHz_TEST_081910.zip

Just cap the max to 1113MHz with Setcpu.
[Nexus One Android Development] wildmonks:
Maybe create a google doc so everyone can enter their names in ;)
[Nexus One Android Development] poochie2:
@WM: is there a chance to try some (to be requested) voltage cuts in the usual 900mV svs kernel?
[Nexus One Android Development] ChronoReverse:
Sure why not :p

https://docs.google.com/leaf?id=0Al...CLTNWdEY5SXRldkE&sort=name&layout=list&num=50
[Nexus One Android Development] Robdyx:
So..... I thought it might not be possible, but I've been running 2.6.35_AVS-900mV_CFS_AXI_720p_1228MHz_081910 for half day with absolutely no problem! no reboots, no crashes..... and I've tryed even 3D games at max speed!
[Nexus One Android Development] ChronoReverse:
Add yourself then: https://docs.google.com/leaf?id=0Al...CLTNWdEY5SXRldkE&sort=name&layout=list&num=50

BTW, I'd like to try 900mV AVS no720p too ;)
[Nexus One Android Development] Robdyx:
Sorry, the page (or document) you have requested is not available.

Please check the address and try again.​

Check if that's the real address
[Nexus One Android Development] ChronoReverse:
https://docs.google.com/leaf?id=0Al...CLTNWdEY5SXRldkE&sort=name&layout=list&num=50

Try this one (oh Google...)
[Nexus One Android Development] wildmonks:
Ok, your kernel is will be posted soon ;)
[Nexus One Android Development] Robdyx:
This one works, put it highlighted in the first post, it'll be very usefull for new users ;)

I've added another column for highest stable clock speed, feel free to delete it if you don't like it
[Nexus One Android Development] ChronoReverse:
It's only for sharing AVS information so it doesn't matter what columns are there =)

BTW, camera flash is no longer slow for the AVS 950mV no720p build. Great work!
[Nexus One Android Development] wildmonks:
Done, its in the first post now :)

And here's your kernel :).
[Nexus One Android Development] Gilg@mesh:
thanks, I report back :)

edit: I'm trying this first: 2.6.35_AVS-900mV_CFS_AXI_720p_1228MHz_081910.zip

btw BFQ, good or bad?
[Nexus One Android Development] flak0:
Contrary to belief I have gotten reboots today. What governor are you using. Im using kangorama b2 sp1 (rc3) and im getting odd behavior I think its related to super user version. I have to manually go into set CPU if not it will show as 245 min and 998 max.