yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] Gilg@mesh:
2.6.35_AVS-925mV_CFS_AXI_720p_1228MHz_TEST_081910.zip seems to be stable for me, I have made a couple of phone calls and just playing around with the phone, I'm running ondemand scaling and when screen is off I use conservative scaling,I have set max cpu @ 1075MHz even though I know 1113MHz+ runs fine but I need the battery hehe,but I will test it more tomorrow at work and report back. thanks
[Nexus One Android Development] GIKE:
Updated with my report.:)
[Nexus One Android Development] poochie2:
@WM #2 (#1: http://xdaforums.com/showpost.php?p=7765318&postcount=1749): did you check this one out? http://xdaforums.com/showthread.php?p=7688417

I'd try booting at 1000 ^_^
[Nexus One Android Development] ChronoReverse:
Tried out Interactive governor again but it's just not usable. Makes the animations (I set the interface to use full animations in order to put more on the CPU) when I start or switch programs choppy sometimes.

Ondemand and Conservative I'll have to stay on. So far 900mV is working out...
[Nexus One Android Development] bigmase521:
I've been running the 950mV AVS 8/19 kernel since this morning and it's been working great for me so far (knock on wood). Booted first try, stable, no crashes thus far. Running Kang-o-rama 1.0 b2 w/ SP1 (CM RC3). First AVS to boot/work for me in awhile!

Edit: Added myself to the Google doc.

This has been happening to me too since b2 came out. I have to open it manually and then I get the "SetCPU has been granted Superuser permissions" and THEN my profiles work. BUT, every once in awhile I'll hit the widget, the SU message will pop up again and I'll see the speed drop to 128 and the jump to 1152 like it should..almost like the profiles aren't working correctly :confused:
[Nexus One Android Development] ChronoReverse:
Anyone else using the Current Draw Widget? The new set of AVS kernels seem to draw more current when my screen is off compared to the set I was using before.

Before I get from 3-5mA draw with the screen off, now I'm getting from 10-40mA. I wonder what the change could be from.

I'll run some comparisons to the SVS once the AVS steadies the voltages later. AVS used to steady quickly but it seems to be continuing trying to adapt a lot more now =(
[Nexus One Android Development] nexusonemeover:
I am about to flash 2.6.35_SVS-925mV_BFS_AXI_720p_1113MHz_081910. Its the first kernel I will have ever flashed to my device...

I presume I just flash the zip in ClockworkMod, and thats it?

If I dont like the results, do I just reflash the ROM I was using (CM6 RC3)?
[Nexus One Android Development] damanrico:
Yes, and yes. You can also do a nandroid backup just to be sure, although it's not needed. But for a first time flasher you might want to be on the safe side.
[Nexus One Android Development] nexusonemeover:
thanks... flashed, so far so good...
[Nexus One Android Development] antiochasylum:
Ever since switching to 925mv svs things have been running fine for me. No crazy crashes. Thanks monks :)

Edit, is there a way to get the 8/19 svs kernel on 925mv with 720p at 1228mhz it even 1190?
[Nexus One Android Development] musashiken:
Ok, 925mV SVS 081910 CFS works good for me. But BFS runs crap everytime I start up Aldiko and read a book and it slows down the phone to a crawl.
[Nexus One Android Development] Robdyx:
900 and 925mV AVS crashes with the stock web browser after a while, specially with videos. Please other testers check this.
[Nexus One Android Development] uoY_redruM:
Ok, some more testing:

2.6.35_AVS-950mV_CFS_AXI_720p_1113MHz_081910

1d, 2h & 23m with regular use and I'm at 70% battery still.

34% Display, 27% Cell Standby, 24% Phone Idle, 6% Android System, 3% Dolphin HD, 2% Android OS, 2% ChompSMS, 2% LauncherPro

SetCPU is running 245/1075 ondemand with Screen Off profile set to 128/245 powersaver.

I'm not charging tonight and crossing my fingers I make it through tomorrow as well. I have to work, so if my phone dies I'll cry LOL

I'll post back tomorrow with battery stats again.
[Nexus One Android Development] ogdobber:
regular use? you have no calls. also are you set on 3g or edge?
[Nexus One Android Development] uoY_redruM:
3G, never edge. I don't use my phone as an actual phone too often, as silly as that sounds lol. I haven't had a phone call all day, no.

By regular use, I mean I used it to surf the web, send texts, surf the market, download, etc.
[Nexus One Android Development] ogdobber:
thats still pretty good i guess. calling in 3g kills the battery compared to edge
[Nexus One Android Development] uoY_redruM:
Definitely better then usual. I use to charge my phone to 100%, go to work (6 hours or so) and when I'd get home, I'd be around 77%.

In this case, I've had my phone unplugged since Thursday night, worked an 8 hour shift at work Friday (today) and I'm just now at 70%.

So far, in my experience, the addition of AXI and 128MHz has helped for me personally.

The only bad thing, I guess you could call it, is 128 SUCKS when coming from screen off. Can take a second or two to actually get off the black screen at times. That, and with the last two kernels I've flashed, I've had complete lockups when "stressful" web browsing. Hasn't happened with this kernel yet *knock on wood* though.
[Nexus One Android Development] ellesshoo:
For your screen off profile, I believe using the powersave governor will simply hold the CPU at the min frequency so no need to set 128/245. Someone correct me if I'm wrong.

Also, 128 is a ***** when coming out of the lock screen IMO.
[Nexus One Android Development] uoY_redruM:
Oh, awesome.

Yeah, as I said a post above yours, I agree 128 is a ***** when coming out of lock screen lol.
[Nexus One Android Development] uoY_redruM:
Well, I take that back on reporting after 48 hours of no recharge. I decided to flash the latest nightly so obviously that requires a reboot.

Will test this again in the next few days probably.
[Nexus One Android Development] cdmove:
eh..well i'm doing a nand restore right now. i'll try the kernel again later after work. :(
[Nexus One Android Development] watercool:
nand restore can't be wrong.

I saw some people saying that wiping cache is completely unnecessary but i was flashing about 15 times a kernel yesterday and with some my phone panics completely.. after doing a cache wipe everything was perfect...
[Nexus One Android Development] chowlala:
Is there any way we could tweak the sensitivity then? Maybe run it on a scale or something?

I'm no engineer btw, just babbling thoughts. Lol.
[Nexus One Android Development] dictionary:
Re: [Kernel] Hybrid AVS + 1113Mhz Overclock (.33.5 & .34)

With the 605 925cfs kernel I keep getting kernel panics. Regardless of how I wipe. Wipe then flash. Flash then wipe. Flash no wipe. Wipe flash wipe.
[Nexus One Android Development] mtw4991:
I used the flash zip from recovery method and turning wifi on is causing a full freeze requiring a battery pull to reboot on 0605_925mV_CFS:( Do I need to extract the 4329.ko and push it to system/lib/modules?

Edit: Just got a Handcent popup SMS and phone froze again...wtf?
[Nexus One Android Development] chowlala:
Yeah, there's been a bunch of freezes and lockups here and there when the AVS pushes the kernel to OC. Not sure why, BFS/CFS doesn't make any difference, it's the AVS that seems to be unstable I reckon.
[Nexus One Android Development] dirwdirw:
oh, no.

i flashed the latest kernel(cfs 925mv), my phone got a sequence of reboot. it freezed at destop and reboot.

i wiped cache/dalvik cache/battery already.

now i back to 0604 cfs 925mv, works well.

avs seems not stable for me. i used ivan/raven's kernel before, some version worked well but some didnt.
[Nexus One Android Development] nazrin313:
Re: [Kernel] Hybrid AVS + 1113Mhz Overclock (.33.5 & .34)

yeap, I concour...wifi n pop ups freezes or reboots the phone...flashing the older 925 cfs till a more kernel comes out...good effort thou
[Nexus One Android Development] chowlala:
Did you wipe cache and dalvik cache before flashing the kernel?
[Nexus One Android Development] mtw4991:
ok, tried to push the .ko file...didn't work. wifi is definitely broken for me on 0605_925_CFS.:( I even used SetCPU to set it at 998??
[Nexus One Android Development] dirwdirw:
i wiped after flashing because the issue. is it the point??

but i didnt wipe anything when i used pershoot's kernel before.
[Nexus One Android Development] chowlala:
If you're switching from kernel to another kernel - should always wipe before that. I'm sure that's probably not the source of the prob though. But... you never know. =) But did wiping fix the boot loops?
[Nexus One Android Development] mtw4991:
I wipe as standard procedure before flashing any new kernel and wifi/sms popups kill the beast. I can confirm USB mount/unmount does work just fine though!:D Gotta go back to 0604 still this issue is resolved. Great work wildmonks...were you the first to get USB issue resolved?
[Nexus One Android Development] dirwdirw:
i think i find my point.

i closed wifi before flashing the latest kernel, and it worked. but when i opened wifi, my phone freezed and got a reboot.

i have tried twice, same action same issue.
[Nexus One Android Development] dirwdirw:
+1

same here.
[Nexus One Android Development] irishrally:
I was boot looping with the 6/5 version of 925mV CFS after wiping cache/dalvik cache. Never had any problem with any of your other kernels. Going back to 6/4 for now.
[Nexus One Android Development] chowlala:
From what I gather, you should be turning off your wifi first before shutting down and going into recovery. Apparently the wifi causes the bootloop or something like that, can't confirm though cause I didn't have any issues flashing the kernel.

But I did revert back to pershoot's kernel due to stability issues.
[Nexus One Android Development] wildmonks:
I can confirm that there was a problem with the compiled wi-fi module that caused the kernel to panic and caused overall instability. I have started over from scratch (again -_-...) and re-added the cyanogen commits. Wi-fi seems to be working again and will continue to test throughout the day. If you would like to help I have posted the new kernel below. I won't be making the other versions until I know this one works.

2.6.34_AVS-925mV_CFS_1113Mhz_TEST_060510.zip

Update: Test is over, new kernels posted.
[Nexus One Android Development] THATTON:
I flashed the previous version from earlier today and all went well but as soon as I turned the wifi on, the phone rebooted so I will download and test this one right away and let you know. Keep up the good work man.
[Nexus One Android Development] RinTinTigger:
When will i get my 800's back? CFS and BFS?
[Nexus One Android Development] Latentk:
Monks are we going to see an update to the test kernels? I know you've been working on sorting out the other issues poping up and that is preferred :P. Just curious! And as always your hard, or at least tedious, work is appreciated!
[Nexus One Android Development] ChronoReverse:
I don't have trouble coming out of 128 mhz. I set it to 128-500 conservative though.

Incidentally, if your display isn't using at least 50% of your battery, you could say you're only using the phone lightly.

I drain only like 5% overnight (8 hours)
[Nexus One Android Development] Surgent:
925-BFS-SVS-AIX-720-1228-081910 Runs great! Epic stable & 40+ lin. Cheers mate.

Haha, This is my favourite thread ^_^
[Nexus One Android Development] wildmonks:
There some 900mV kernels here if you want to try them out. They haven't been working all that well for me so I wont be doing 900mV regular releases but I'll make it on a per request basis.

Oh, and IR has kindly set his kernel code to boot the phone at 998MHz so its already present in the 081910 kernels :).

There's a set of SVS kernels running at 1228MHz in the test folder but I have not made a set for stock FRF91 rom users. In otherwords, they all have the 720p code.
[Nexus One Android Development] wildmonks:
This probably caused by this commit change to try and reduce the AVS instabilities for some users.
[Nexus One Android Development] Latentk:
Ah that link escaped me earlier. Thanks monk!! Flashing now!
[Nexus One Android Development] poochie2:
Already using them ^_^ I had troubles in the past after the 16th using the interactive governor (maybe because of going from minimum to max frequency too fast). Since I began using the ondemand scheduler everything's been fine and pretty smooth!
[Nexus One Android Development] damanrico:
Wildmonks, I've been thinking about something and I'd like your opinion and knowledge on it:

Since I need 1050mV for my phone to work, you set every Mhz setting to at least use 1050mV if I'm not mistaken.

What if I use a normal kernel, and set the min CPU Mhz to a Mhz setting that uses 1050mV.

So lets say the normal kernel would use 1050mV for 400Mhz and higher, I would just set my min Mhz to 400Mhz.

Since I'm not an expert, I probably don't see the downside to this, but for me it sounds like I have a faster phone (as in, I can set the min Mhz higher, meaning my phone is faster while the screen is off) and yet still it only uses 1050mV while running at a higher min Mhz.

The only downside I could think of is that it could be bad for the phone to always stay at a higher min Mhz than 245. I'm not sure if this is true, so I hope you can explain that a little further.

So to sum up, is this a crazy thought, or does it actually hold some truth? Thanks in advance for taking time to answer.

To other users: again this is a very specific question for my phone only, since I have a weird device that needs at least 1050mV to not freeze.
[Nexus One Android Development] nenco:
I think that 1050mv at 400hz use more mA from battery than 1050mv at 245hz
[Nexus One Android Development] Robdyx:
900mV worked stably for me, but only with SVS, looks like AVS need at least 950mV. I'm currently using 2.6.35_AVS-950mV_BFS_AXI_720p_1113MHz_081910, have done a network stress test and seems like it can handle well.

BTW, the stability survey is for AVS or AVS & SVS?
[Nexus One Android Development] wildmonks:
@damanrico

Actually, that's a great idea in your situation and worth trying. I think you'll be surprised how little of an increase of battery you'll experience due to tasks being completed faster (so less time the CPU is actually working). So to try 499mhz first, it uses 1025mV, then flash a normal SVS kernel. If you want to use 1050mV first instead then you'll have to set your min to 537. (I haven't adjusted the voltage table to match to pershoots yet, next release I will...)

Staying at a high MHz won't be bad for then phone at all so I wouldn't worry about that.
[Nexus One Android Development] damanrico:
Cool, I'm glad you don't see any problems with it. I'm going to try it for sure.

Should I stay on my custom kernel, or do I need to flash a 950mV version (925mV won't even boot for me) and adjust it to either 499 or 537 before my phone freezes?

Is it too much trouble if I ask you to paste the voltages tables for both my custom kernel and the latest SVS 950mV CFS kernel?

That way I can be sure I won't set wrong Mhz values.

Thanks again for helping me out.
[Nexus One Android Development] yiannit:
anyone use 1228 @1228mhz kernel 24/7?

and is there an app that checks cpu temps and voltage?
[Nexus One Android Development] uoY_redruM:
I did a while back with WMs original "secret" super overclock kernel, before he started releasing them that high, and nothing went wrong with my phone.

SetCPU monitors temp as well as enabling you to adjust the speed..
[Nexus One Android Development] Robdyx:
I think it would get hot as hell, wouldn't recommend that.

For CPU temp, you can use setCPU widget, no idea about the voltage, sorry.

Try searching for cpu voltage in the market, maybe....
[Nexus One Android Development] yiannit:
i thought thats battery temp
[Nexus One Android Development] Robdyx:
Only fot those phones whose hardware and kernel support it, but yes, it can.

I've checked my N1 and I think it may not be supported on it...
[Nexus One Android Development] ellesshoo:
Question for you bfs users... I've tried bfs in the past and while it does give great benchmarks I felt CFS was more responsive wiith regard to touch screen interaction and definitely seemed better rendering in the browser. Have you BFS users noticed this? Maybe the newer versions are better.

Also, is there a consensus on axi at this point? Is it really doing much of anything?

Finally, any results on battery draw comparing 900mV or 925mV SVS vs 950mV AVS? Which do you think would consume less batt?
[Nexus One Android Development] ChronoReverse:
So far looking at the survey, it looks like I'm the only one using the no720p version. I feel a little alone :(;)

I have excellent stability though. Comparing the AVS voltages being set in the log to the SVS 900mV table, I consistently have voltages at least 25mV lower across the board.

The real question is whether actual power savings are had from this...
[Nexus One Android Development] ellesshoo:
which one has 25mV less?
[Nexus One Android Development] uoY_redruM:
In my experience, so far, BFS just doesn't cut it for me. Not responsive enough when it comes to touch screen and interaction. AXI definitely seems like it makes a difference in my case compared to the old kernels without it. AVS seems great for me so far as well, using the 8/19 test kernel. SVS kept causing lockups for me during use. I have had a few lockups with AVS though, every time it happens it happens with "stressful" internet use (like surfing more then one tab or downloading and loading another tab).
[Nexus One Android Development] ChronoReverse:
AVS does. For instance, at 500MHz, SVS 900mV uses 1050mV. AVS 900mV will start at around there and bring it down to 900-950mV.

BFS is very unusable for me. For any of you where it seems to work, download and install Aldiko. Grab one of the free books and open it. BFS invariably slows the system down to a crawl while CFS runs it like butter.
[Nexus One Android Development] ax0r:
Bfs does good numbers on benchmarks but it is not stable
[Nexus One Android Development] Latentk:
Hmm a lot of this talk about bfs makes things a little clearer. I noticed that while running bfs, while at first stable, it eventually got to the point where my phone seemed to completely and utterly crawl. Trying cfs and we will see if it makes a difference. So far svs 950 819 is completely stable. I tried 925 avs but that lasted about 30 minutes lol. Monks these things continue to improve thanks to your efforts! I cannot imagine using any other kernel!
[Nexus One Android Development] nexusonemeover:
ive been running 2.6.35_SVS-925mV_BFS_AXI_720p_1113MHz_081910 for almost 24 hours. as stable as stock kernel for me. i did not overclock. i dont have any improved battery performance though.

phone was full at 100% at 10am local time, its now 130pm (3.5 hours) and phone has been idle but for reading 4 incoming emails (no other use, screen has been off 3.45 of those 3.5 hours) and im down to 83% battery.
[Nexus One Android Development] yiannit:
the way i test battery is at night charge to full turn off wifi/data and sleep, most of the time i get 1% per hour one time i somehow lost 2% in 3 hrs
[Nexus One Android Development] myplague:
I been running the 0819 900mV AVS CFS kernel for about two days now and I just compared my voltage to the SVS table and came up with this

128 -384 run at 900mV but everything after just follows the minimum of the table

no issues with the phone aswell execpt had a game that froze once

Is AVS good for me to use or should I be using a higher voltage kernel?

Thanks!
[Nexus One Android Development] ChronoReverse:
If it freezes in use, then that level of AVS is probably too low. If it's just once then maybe it's okay.
[Nexus One Android Development] myplague:
no just once in the game other than that never froze for anything else
[Nexus One Android Development] ChronoReverse:
Well, you're testing so note down what causes it to freeze if it's reproducible.
[Nexus One Android Development] uoY_redruM:
Appears this may possibly just be a nightly issue, as someone said

in the nightly thread.
[Nexus One Android Development] MicroMod777:
Wildmonks, do these have audio boost?
[Nexus One Android Development] poochie2:
Even if you don't overclock you should use SetCPU to enable 128 MHZ as minimum clock instead of 256.
[Nexus One Android Development] HTCDevil:
Thanks wildmonks, this 2.6.35_SVS-925mV_CFS_AXI_No720p_1113MHz_08192010

works like a charm on Stock deodex FRF91 ;)
[Nexus One Android Development] nexusonemeover:
good call!
[Nexus One Android Development] Robdyx:
Try 2.6.35_SVS-900mV_CFS_AXI_No720p_1113MHz_08192010, should work stable too.
[Nexus One Android Development] HTCDevil:
Oh, thanks ;)

I'll try it as soon :)
[Nexus One Android Development] uoY_redruM:
WM, you see what's going on over here?

http://xdaforums.com/showthread.php?t=741322&page=8
[Nexus One Android Development] HTCDevil:
I can't find it...:(
[Nexus One Android Development] Robdyx:
Sorry, my fault. I meant these two:

2.6.35_SVS-900mV_CFS_AXI_720p_1228MHz_081910.zip

2.6.35_SVS-900mV_BFS_AXI_720p_1228MHz_081910.zip

CFS version should work properly, BFS.... could work well too but I've not tryed it.

Use SetCPU to limit overclock and set idle at 128.
[Nexus One Android Development] snxxxxx:
Im using cm6 now.. wich kernel that its good for daily use for me..?? sorry for my english.. im indonesian.. :-)
[Nexus One Android Development] Latentk:
Hey there. For every day use, and if you could care less about maxing your N1 out, you should prob start with a 1113mhz cfs kernel with 900mv. If you find that is unstable you can try the 925 or even 950. No need to push it to 1228 on a test kernel for daily use.
[Nexus One Android Development] nenco:
he use no720p version (me too):p
[Nexus One Android Development] Robdyx:
Aw I didn't noticed you were of those........ tssss

:p
[Nexus One Android Development] Vlad83:
Just realized that ondemand governor saves a lot more battery than interactive. In case anyone is using it and wants to conserve more batt...
[Nexus One Android Development] ChronoReverse:
For that matter I still haven't discovered the benefits of the Interactive governor in its current form. It's supposed to not ramp up to maximum as fast as the Ondemand governor and thus save power but in practice I don't seem to see the benefit plus I start getting lag everywhere.
[Nexus One Android Development] Vlad83:
I thought it was the opposite? Interactive to me feels just a tad snappier and I thought it ramps up to max cycles instantly...
[Nexus One Android Development] poochie2:
Quote
[Nexus One Android Development] ChronoReverse:
I think someone explained it as ondemand snaps to full then lowers in response to load while conservative stays low and moves up slowly in response to load while interactive is supposed to increase intelligently to load, ramping up quickly but not to the highest immediately.

Either way, turn on full animations in your ui and watch the lag when opening or switching apps on interactive.
[Nexus One Android Development] Robdyx:
BFS should be more responsive and get better MFLOPS than CFS, but i found it more laggy when swipping and the marks are slightly worse, so I'm going back to CFS. Anyone else goin' better with CFS?
[Nexus One Android Development] fiftyclick:
Actually, it seems snappier for most things, but occasionally it gets really sluggish. Ondemand lacks the minor increase in snappiness, but has never caused me any grief. Likely better for battery too?
[Nexus One Android Development] Vlad83:
From my observation Interactive was snappier but a lot more battery draining, but thats just me... Interactive never got sluggish, it increased responsiveness but took a toll on my batt...
[Nexus One Android Development] ChronoReverse:
So interactive doesn't add choppiness to ui animations when they're set to full for you guys?

Basically the zoom out and in, slides, etc.
[Nexus One Android Development] Vlad83:
I didn't notice any...