yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] Docmjldds:
RE-Userspace.....

http://www.simplemobilereview.com/android-rooted-setcpu-and-cpu-governance/

<<During a comment discussion on a recent post about configuring the setCPU app (Android Rooted: setCPU and Profiles), reader Ben Pike pointed me to an interesting post found in the DroidForums.net forums, where ‘Mike’, the author of the setCPU app describes some additional settings around CPU Governance in the setCPU application.>>

The OnDemand governor is the default option used by Android. It scales the CPU speed between the minimum and maximum speeds depending on CPU load. If the system needs more speed, the kernel will rapidly scale up the CPU speed.

- The Conservative sets the CPU speed in a similar way to the Ondemand governor, but scales the CPU up much less rapidly. This would theoretically save battery power, but may lead to less responsiveness.

- The Userspace governor is currently useless. It’s another way for applications to set the CPU speed that setCPU does not use.

- The Performance governor always keeps the CPU at the maximum set frequency.

Additionally, he makes reference to another option, which is not currently part of the setCPU app, so I am assuming that this is one that was removed in later versions.

- The Powersave governor always keeps the CPU at the minimum set frequency.
[Nexus One Android Development] mtw4991:
Ok, I think I have got it...seems that IntersectRaven has several kernels, all of which max at a select mV parameter. If one isn't stable, just keep moving up until you get stable..is that it?
[Nexus One Android Development] intersectRaven:
I think you're referring to the old AVS kernels. The latest is only one kernel which is stable for all. :)
[Nexus One Android Development] sir*mez:
I'm on 8hrs 10mins and on 70% battery so far. I say this is a winner. Will provide a screenshot when I'm done testing. This is for the 4/20 kernel. I also will update to the 4/21 when finished and continue testing on that kern.
[Nexus One Android Development] intersectRaven:
You can continue using the 4/20 kernel since the 4/21 only contains an extremely minor update. :)
[Nexus One Android Development] sir*mez:
yea but im always finding a reason to flash soimething, lol. i always have to have the newest :D but im very happy with this kern, kern!!
[Nexus One Android Development] redraiderj:
Well, I noticed the title is "[Kernel - .33.2]intersectRaven's Kernel (new Hybrid AVS *Stable*) 04/21/2010 09:47pm". While I found nothing mentioned the "Stable" in the release notes. Was the "Stable" added when 4/18? Coz' I see the words below:

20100418_0816:

- AVS now stable

* correction: it's still unstable (I think) since the incorrect edit just deactivated the voltage setting

Maybe you just forgot to remove the "STABLE" from the title since then?
[Nexus One Android Development] S_Dot:
I'm on the first kernel release that became stable (like a week ago) I believe.. Can anyone tell me any updates since then?
[Nexus One Android Development] intersectRaven:
The latest releases are stable now. :)
[Nexus One Android Development] redraiderj:
Great! I'll try it after work. Maybe you can add it to the release notes to make it clear:)
[Nexus One Android Development] christiankk:
Battery life with this kernel is simply amazing me.

Lost 2% over night in airplane mode and 45% in one day with 1 hour of VOIP talk with sipdroid over wifi and other surfing.

Thanks intersect! :)
[Nexus One Android Development] die-hard:
In 15 h battery status is 46%.

My N1 is on 3G network with sync enabled.
[Nexus One Android Development] GlenH:
Is there much point running SetCPU with this kernel?

Obviously it allows you to select the CPU governor that is being used, but is there any point limiting clock speed when sleeping for example, or will this kernel do something along those lines anyway?
[Nexus One Android Development] Pochemuchka1977:
On of the problems I found that some program running in background causes my CPU to jump to 998MHz every couple of seconds ...

Setting SetCPU idle profile with different governor (powesave) fixed the problem
[Nexus One Android Development] codington:
I am running Enom's The Official 1.8.1 and for the past few days I have been running the 20100418_0816 release with no problems. Just tried the latest release 2.6.33_AVS-800mV_20100421_2237_Update.zip, and was unable to boot. Logcat reported an exit due to busybox not being found at /system/xbin - on Enom's ROM, busybox is found at /system/bin. Did I do something wrong or was there a change in the kernel code? I nan-restored and all is well again.
[Nexus One Android Development] intersectRaven:
Use the non-Update.zip (zImage) file to install. The Update.zip method replaces your boot partition with something that does not have busybox. :)
[Nexus One Android Development] GlenH:
Yeah, powersave governor will help with that, because it locks the cpu to it's minimum speed (245Mhz)!

fyi, any activity at all will cause your cpu to jump to 998Mhz when you use the standard (ondemand) governor, because that's what it does - as soon as there is load it increases to maximum frequency and then drops back down dependent on the amount of cpu load.

If you want a governor that allows cpu frequency scaling, but doesn't jump straight to max, use the 'conservative' govenor.
[Nexus One Android Development] bewA:
well i'm pretty impressed so far!

I'm on this kernel and with SetCPU on Conservative i'm on 74% since unplugging just before 8AM :)

wifi enabled, checked emails 20 odd times, sync'ing enabled made one short phone call and sent a couple of txt's :)

Not had any reboots or lag :)

If I upgrade to a new version of this kernel do i still have to push the wifi driver file?
[Nexus One Android Development] hah2110:
Ugh how does this thing charge so fast with this kernel? Green light from 50% after like 30% over USB!
[Nexus One Android Development] LunatikBunnie:
hey raven, do you think you can implement Desire camera as well? :x
[Nexus One Android Development] pzumk:
What do you mean?

(FYI you can use Desire Cam + Raven's Kernel, just flash the cam and the kernel after it)
[Nexus One Android Development] Webstarr:
loving this kernel...dropped about 15% in about 4 hours with 3G on
[Nexus One Android Development] tokyomonster:
If I'm not mistaken, flashing the camera update.zip will replace the kernel.
[Nexus One Android Development] sthoeft:
Torn between the Kmobs .850 V Kernel and the AVS Kernel. Witch do you think is better? Where do you get better battery life and performance?
[Nexus One Android Development] sir*mez:
All phones are different. Please run your own tests. This is like asking what rom is better. Everyone likes different features.
[Nexus One Android Development] dictionary:
That's why you don't take the easy mans route of using the update.zip, and flash the fasboot flash method. ;) When you fastboot flash the kernel, everything works as it should.
[Nexus One Android Development] sir*mez:
Awesomeness!!! Over 25hrs!!

17hrs with 19% to go at 9am. its now 5:45pm and im on 9% so thats over 25hrs. of fun. (oh just turned off on me while writing this couldnt get the screen shot, huh.) very happy with this!! :D
[Nexus One Android Development] dictionary:
Yah, with moderate use, I just got 8hrs of use, mostly gtalk, engadget, and web browsing and was down to 69%. The phone WAS idle for probably 4 hours out of that time though. Absolutely amazing during idle. Just ran back to pershoots kernel to test, but the latest kernel has worked amazing with no hiccups. Only thing that bugs me is when it's on conservative, the gradual ramping up. Well worth it for the battery life though.
[Nexus One Android Development] MaxiJavi:
It depends, most versions of the Desire cam crash with this kernel, however, if you use this one :

http://xdaforums.com/showthread.php?t=668265

As stated before it'll overwrite the kernel ...

So then fastboot the kernel ... And it works :-)
[Nexus One Android Development] jonasl:
I love this kernel and just want to say thanks. Sent you a donation also.
[Nexus One Android Development] intersectRaven:
I don't think I need to. You can use the fastboot method with the zImage in order to get this kernel working with Desire cam I believe. :)
[Nexus One Android Development] dictionary:
That is entirely incorrect, lol. You've just been doing it wrong

First you install the r2 desire cam

THEN you fastboot flash zimage zImage - install the kernel.

It doesn't have to be the one from that thread .. because I've been using a desire cam on pretty much all of Cyanogens updates, even tests, with no problem. And that's going through all different kernels. The problem lies when people were flashing the desire cam, and then not flashing a kernel on top. When I say flashing a kernel, I don't mean via recovery. That will not yield positive results. You have to install the cam via recovery yes, but you have to fastboot flash zimage zImage the kernel over that. Trust me, I've been doing this forever .. the one in that thread STILL needs you to overwrite the kernel via fastboot, lol .. so really I don't see the point of it. My cam has been working flawless from the day I installed it properly, thanks to distortedloop. :p
[Nexus One Android Development] jblazea50:
I guess it varies because i can't get it to work. I'm using cyan with nextheme and goodies. I went into recovery and flash the camera and fastboot the zimage, but always get force close.
[Nexus One Android Development] dictionary:
Do it over a nandroid backup, that should work. If not, try a fresh install, then gapps (if cyanogen), then desire, then fastboot flash
[Nexus One Android Development] MaxiJavi:
You didn't read what I wrote :-(

Flash camera (but the right version)

Then flash kernel (fastboot)
[Nexus One Android Development] dictionary:
Well, I have only seen the r1, and r2 of the desire cam. By now, I figure most people are running r2. I'm not sure what other versions there are floating around that you're speaking of. I just don't understand what's special about that camera he posted, when you still have to fastboot flash a kernel. It's the exact same as the r2 camera, lol. Anyway, not really kernel related so to speak, and I don't want to ruin intersectRaven's thread anymore. =)

intersectRaven. Quick question. Your latest kernel gives me awesome standby life on conservative, using lower mhz on standy by. However I was using a conservative profile while active as well, and noticed a bit of lag. Is it safe to say that I should still get the great standby time with the conservative profile only on the standby? The lag when using the phone drove me nuts, lol.
[Nexus One Android Development] intersectRaven:
Yes. :) The lag is part of the trade-off with the conservative profile. If it becomes too much for you, you can always go to ondemand. :p
[Nexus One Android Development] MaxiJavi:
I have a question ...

Any idea if some of the Cyan commits did something to 3g/2g ?

They switch much more intelligently with this kernel, and in general my mobile internet seems a lot better ...

I might be dreaming though :-)
[Nexus One Android Development] hah2110:
No update in a couple of days.... Is this "complete" and considered a success?
[Nexus One Android Development] dictionary:
Or he has a life? Will you STOP spamming threads with these questions? I mean seriously, it's beyond annoying. The latest version is rock solid for me, but if you have an issue, change out to a new one. I'm sure intersect is going to continue releases, as more and more he fine tunes it, but you constantly harping on these kernel and ROM threads man, just wow.
[Nexus One Android Development] Enndr:
I have a question on this subject. Let me know if Im reaching too far on this or if it would be possible.

Ok, so we all know how the conservative and on demand settings work for setcpu.

Would there be a way to create a new profile and in a way give you a best of both world or something to be as close as we could?

Example:

On demand throws the CPU to max anytime there is any activity then throttles down depending on use. Pros: less lag, snappier experience.

Conservative throttles the CPU ALOT less and decides what is needed after going at it a second. (If I'm a little off on this one let me know)

Solution????

Could something be written to do something like the following:

Say you're overclocked to 1.113 ghz. You don't want your phone to throttle to max everytime you wake the phone to check time or a simple text.

Could it be made that you change to what level the conservative setting goes? Say 1 ghz in this situation.

So basically if you're doing something silly and mundane its throttles you to 1ghz i/o the max then assess need and goes higher or lower like it already does.

Could this be applied accoss the entire spectrum as well? Say people who don't overclock but are all in it for the battery. So maybe someone who keeps their normal clock at 1ghz. Maybe make it throttle to a max of 700ish mhz and then goto full if needed?

If this doesnt make sense, already is close to how it works or is stupid just tell me and I'll shut up.

Thanks
[Nexus One Android Development] intersectRaven:
This seems to be a great idea for a userspace program that will regulate the CPU speed. That is beyond me though. :p
[Nexus One Android Development] pzumk:
that's why I said:

Flash the Camera first and then the Kernel.
[Nexus One Android Development] b1337:
check the 5.0.6 change log there was a addition to the build.prop file
[Nexus One Android Development] Enndr:
Let me look into some stuff and see if I can help with this. Maybe this could be something incorporated in the future. A "smart" CPU management feature.
[Nexus One Android Development] www1:
What we need in new version:

:D

Audio hack (bost sound of ringtone)

wifi - n

:D
[Nexus One Android Development] intersectRaven:
I think the N WiFi driver has already been committed in cyanogen's latest kernel updates (correct me if I'm wrong). As for the audio hack, I've not seen any significant updates with regards to it. :(
[Nexus One Android Development] Wysie:
As I was saying, pershoot's xtra really helps, and part of the xtra is the 3d msm stuff. The rest are as per this post: http://xdaforums.com/showpost.php?p=6245201&postcount=1661

Not too sure if it's already included, but do take a look! Thanks intersectR :P!
[Nexus One Android Development] www1:
I have to test in my N1.

Anyone can tellme if there is an application for test?

edit.

my speedtest.net (Adsl 20 mb)

down 6950

upl 894

do you think it's wifi n?
[Nexus One Android Development] intersectRaven:
The only things I haven't implemented are the v4 block device, deadline and 3 errata. I'll try to implement the first two after I finish with the modifications on my github fork. As for the errata, I'm reluctant in enabling them since the scorpion core may already have addressed those issues since it is a different implementation by Qualcomm. :)
[Nexus One Android Development] xCALLmeKING:
Flashing via Superboot?

Has anyone flashed this with Modaco's Superboot? and if so what steps do I follow?

I have the file downloaded, do I unzip it somewhere? any help would be appreciated. The instructions in the OP are so vague, and as I said before I have Superboot installed on my PC.
[Nexus One Android Development] crawler9:
Overclocking?

Raven is there any chance you could add the ability to overclock to your kernel? I love the slightly faster 1.113ghz but the battery life offered in your AVS kernel seems to be a lot better even when kernels that support OC are left at the same clock speed as yours.
[Nexus One Android Development] wildmonks:
This question sure gets asked a lot.. I'm sure he gets tired of answering this question so I'll answer for him.

Hmmm.. if there's that much of a demand for an OC version, I may give out a version with Raven's permission...
[Nexus One Android Development] sir*mez:
I believe overclocking and undervolting just contradicts itself. No battery is saved when overclocked since CPU has to run full mv in order to obtain oc. Correct me if I'm wrong (this is what I've read and understood. So if its wrong info, let me know cause its good to know the right info).
[Nexus One Android Development] intersectRaven:
Why do you need my permission? Everything we do here is open source so do as you wish! (which is why I'm now starting to publish my personal mods on github more completely...although I do admit this *really* complete publishing was triggered by my incompetent flash drive :p) ;) I just really have my own principles to follow. :cool:
[Nexus One Android Development] wildmonks:
Yup, your right. No battery power is saved while the CPU is throttle up. Its when the phone is in standby, and the CPU is throttled down that you get the most battery savings.

My phone spends a majority of its time in standby so its saves a lot of battery power. But it does have a nice, noticeable feel when I do use it because of that little extra Mhz. Which is why I personally overclock.

I guess if I ever do use it for a prolong amount of time, I'll just cap the Mhz to stock via SetCPU, thus avoiding that extra power drain.

Sorry Raven, I forgot that this is all open source, haha. It's been so long (8 something years) that I've done any sort of programming -_-;
[Nexus One Android Development] crabnebula:
If I recall power consumption is proportional to CPU frequency times voltage squared. In other words, reducing voltage has a much greater impact than raising CPU frequency slightly.
[Nexus One Android Development] intersectRaven:
I just finished pushing all of my modifications for Hybrid AVS on my github. If ever anyone has any ideas on how to modify the "hack" to use the regulator framework without sacrificing stability, please contact me on github, twitter or post here. ;)
[Nexus One Android Development] d.cortez:
quick question: what are the benefits of pershoots audio boost values when compared to those used by rotohammer? does pershoots lower/increase the volume, etc? thanks!
[Nexus One Android Development] intersectRaven:
Well, in my phone it's a bit louder. I don't know if it really is. Just that my perception seems to sense that it is. :p
[Nexus One Android Development] intersectRaven:
Updated!

20100424_1336:

Hybrid AVS:

http://www.mediafire.com/?zgij0mgnikg -> ZIP format

http://www.mediafire.com/?ito2yqdickn -> Update.zip format

*If you have something which requires a custom kernel (e.g. Desire camera), please use the fastboot method instead of the recovery update.zip method.
[Nexus One Android Development] vipermo:
cant get past the boot screen with this one strange
[Nexus One Android Development] Wysie:
Flashed the latest one, running fine so far!
[Nexus One Android Development] christiankk:
Last one also looks good here, thanks! :)
[Nexus One Android Development] intersectRaven:
Did you use the recovery update.zip method and are you using anything which requires you to flash a custom kernel? (e.g. Desire camera) If so, try using the fastboot method instead of the update.zip method. :)
[Nexus One Android Development] Docmjldds:
Updated via zip format. No problems here.
[Nexus One Android Development] xCALLmeKING:
Can someone please tell me if I need to Unzip the file before I place anything into the tools folder? and if so what do I place into the tools folder after it is unzipped?

I finally got my drivers updated for AndroidSDK just need to know what to do with the ZIP file after I download it.
[Nexus One Android Development] intersectRaven:
Read more about the tools if you want to use the fastboot method. If not, flash the update.zip version through recovery. :)
[Nexus One Android Development] jblazea50:
pushed it through (adb/fastboot methos), no issues so far

SpeakEZ, if you are using the adb/fastboot command, then you need to download the zip version, extract it, and place the zImage and bcm4329.ko file into the AndroidSDK/tools folder and go from there
[Nexus One Android Development] vipermo:
fastboot works thanks bud
[Nexus One Android Development] jblazea50:
for those who uses the adb/fastboot method, here's ADB/Fastboot GUI for desktop, used it today and it does the job without any issues and saves time by not having to type out all the command to push the kernel

ADB Gui to Push Kernel
[Nexus One Android Development] intersectRaven:
Updated the OP with this. I always forget... :p
[Nexus One Android Development] xCALLmeKING:
Thanks, this did it for me!
[Nexus One Android Development] fabioccoelho:
Nice work mate. I´m using now and works fine and battery no drain fast also Desire ROM with ur Kernel.

All works fine:

Cyan-5.0.6 + Desire Camera + Latest IntersecRaven´s Kernel

:p

Thanks hard awesome work!

;)
[Nexus One Android Development] zdiamant:
Thanks for wonderful work.. Already donated! Quick question.. is there any advantage at this point to update from previous stable version, or are the changes just minor so I can wait for your next release.
[Nexus One Android Development] Nedlinin:
Im just curious as to what happened to the changelog :(

EDIT: Found it squeezed in there.. was looking for the long list that we used to have!
[Nexus One Android Development] intersectRaven:
I got overzealous in trying to put it all in one place (a text file I was supposed to upload to my github) and forgot to actually copy it in the text file. :o
[Nexus One Android Development] awdlexusis:
loving the battery life with this kernal,love the update.zip
[Nexus One Android Development] Vandam500:
I know this is a noob question but here goes. I currently am using persiansown's kernel (latest) and want to try this one out. How do I go about doing this? Also, I am using Trackball Alert Pro, is this compatible with it? Thanks in advanced for your help
[Nexus One Android Development] jblazea50:
You should be able to use this over persiansown. It shouldn't be an issue. There are two version (zip file and update.zip) so you can either flash going into recovery (this will flash boot.img, so it will overwrite some stuff if you are using say, the desire camera) or you can just extract the .ko file and zImage file and using Adb/Fastboot commands to flash (this won't mess with your prevous boot image)

As for your second question, I have no idea. But I would assume that it should be fine if you flash using the Adb/fastboot method. Btw, there's a link in the 1st post that includes ADB/Fastboot GUI for desktop. Makes flashing much easier.

Hope this helps.
[Nexus One Android Development] Vandam500:
Thank you for the info!! And yes, it helps tremendously :)
[Nexus One Android Development] Henchman:
FYI, this kernel completely fixed my non properly functioning capacitive buitons om Pauls desire ROM.

TY
[Nexus One Android Development] Pochemuchka1977:
Installed the latest version, working just fine.

The only question I have is what does these debug messages mean:

<6>[ 166.669738] AVS setting V to 1200 mV @17

<6>[ 166.689605] AVS setting V to 1150 mV @14

<6>[ 166.699645] AVS setting V to 1125 mV @14

<6>[ 166.709655] AVS setting V to 1225 mV @20

<3>[ 167.220367] AVS: Voltage can not get high enough!

<3>[ 167.320465] AVS: Voltage can not get high enough!

<3>[ 167.370452] AVS: Voltage can not get high enough!

<3>[ 167.720855] AVS: Voltage can not get high enough!

<3>[ 167.770965] AVS: Voltage can not get high enough!

<3>[ 167.970764] AVS: Voltage can not get high enough!

<3>[ 168.171081] AVS: Voltage can not get high enough!

<3>[ 168.671539] AVS: Voltage can not get high enough!

<3>[ 168.821594] AVS: Voltage can not get high enough!

<6>[ 168.921813] AVS setting V to 1050 mV @9

<6>[ 168.941833] AVS setting V to 1225 mV @20

<3>[ 169.032135] AVS: Voltage can not get high enough!

<3>[ 169.232330] AVS: Voltage can not get high enough!

<3>[ 169.282379] AVS: Voltage can not get high enough!

<3>[ 169.482574] AVS: Voltage can not get high enough!

<3>[ 169.582672] AVS: Voltage can not get high enough!

<3>[ 169.933013] AVS: Voltage can not get high enough!

<3>[ 170.233306] AVS: Voltage can not get high enough!

<3>[ 170.583312] AVS: Voltage can not get high enough!

I was running SetCPU stress test when I saw these messages
[Nexus One Android Development] intersectRaven:
It means your CPU is whining about the power caps. It should be fine as long as you don't experience any instability. :)