yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] :
Maybe if you just use one reliable, mature governor instead of using different governors when the screen is off you would have less issues. I have no sleep issues with interactive or ondemand.

My preferred governor now is interactive and I have 0 wake problems with it and an insignificant battery drain at idle.

Leaving it on the same governor all the time will not result in additional battery drain. The whole point of a CPU scaling governor is to scale to the device usage, so if it's idle it'll be on the lowest frequency and swapping governors when idle will not change that.

If it's 'total bull****' as you so elegantly and politely put it, I challenge you to produce some hard evidence which can be easily reproduced by anyone that messing about with different governors whilst the display is sleeping gives you increased battery life. :rolleyes:
[Desire Android Development] sfjuocekr:
You failed to understand my writing.

As I explained I have problems if I use smartass in combination with another governor during screen off. If the screen goes off with the smartass governor active, no matter which governor is used during screen off the sleep issues persist.

As for battery life I have very concrete evidence. I charge my phone during the night when I sleep, phone is on the left of me next to the window. When I wake up I from the alarm clock (phone) at 12 in the morning I remove it from the charger and start reading news, updates etc etc. When I return at home I place my phone next to my laptop.

With using conservative governor during screen off my phone still has juice in it when I goto bed. Without conservative during sleep off my phone is dead before I goto bed.

So then I put it on the charger when I goto bed, my cat becomes playful around 5-6 in the morning and usualy plays with me moving in bed and usualy rips the charger cord from it's socket. By this time the phone has already got a decent charge in it, but when it's alarm is supposed to go off at 12 it is dead if I don't use the conservative governor during screen off.

I have Skype and SIPDroid running in the background, which are both draining battery.

Since you told me a few days ago that using conservative is counter intuitive I was set to try it out despite my previous findings just to conclude again that battery life is alot better when I use conservative during screen off.

So please next time read what I had written. Sleep issues persist when using smartass as the default screen on governor no matter the governor used during screen off. Did you test this yourself? I highly doubt it, but I did test it.

Example in SetCPU set the governor to smartass, under profiles add a single profile for screen off and set it to whatever you like. Leave the phone on your desk and bring it back from sleep ... tadaaaa you have to press the power button numerous times or for a few second to make the phone respond again.

So my conclusion is, smartass influences sleep behaviour.

/edit: I just noticed your signature "Fully read the thread and use the site search and Google before asking questions as otherwise you will be told to do just that."

Now I am telling you to get a better understanding of what I wrote, how hilarious :s
[Desire Android Development] Benee:
I'm using auto brightness too and auto sync and so on too and I'm satisfied with the battery usage. But hard to tell. Try it (best HAVS)
[Desire Android Development] Dactylion:
thx did not want to go through the code. pls link to it in your first post.

seems like you use 975mv for 245 mhz. other kernels use 950 mhz
[Desire Android Development] Benee:
nope all kernel use 975mv vor 245 Mhz. 128 Mhz and 19 Mhz 950mv. If I give the kernel in 245 less voltage it may become unstable on many Desires (due to flaws in the fabrication of the cpu) and I want to compile a stable kernel ;)
[Desire Android Development] hk5354:
nice work! going to test now:D

but i think.. it should be a overclock one~
[Desire Android Development] Benee:
It is overclocked .. but only 113 Mhz more. My Desire don't like too much OC so I made a stable kernel ;)
[Desire Android Development] hk5354:
Light sensor seems not work some time, need to reboot and get it work again.
[Desire Android Development] Benee:
Ok strange. But if it works now ;)
[Desire Android Development] wiggles87:
is this based on the CM nightly kernel, or 6.0.1? I'm just wondering if it's suitable for CM nightlies
[Desire Android Development] @ngel:
Tried HAVS on DeFroST 4.1 (no wipe), it didn't go after HTC logo.
[Desire Android Development] jastonas:
Same thing on DeFroST 4.2 :(

I would really like to try a kernel with battery tweaks...
[Desire Android Development] dorin89:
mine worked,on 4.1 an 4.2 defrost with havs kernel from defrost,at 1305 mhz is the power drain fast,1113 is the best havs

one problem:the undervolt zip after dl we do something to it or we instal it in recovery and thats all?
[Desire Android Development] actasci:
im getting artifacts with stock desire rom. compatibility issue?
[Desire Android Development] Benee:
The Kernel is for AOSP/CM .. until HTC release the source code
[Desire Android Development] Benee:
The base kernel is the cm one. With all changes/tweaks etc the cm guys made. So schould work with CM and the AOSP/Cm mix roms (all using the same kernel)
[Desire Android Development] Benee:
Could you try the SVS kernel and report if you experience the same issue? Then I know if it is the HAVS or the other tweaks
[Desire Android Development] actasci:
huh ok. sorry :D
[Desire Android Development] fwers:
used the havs kernel for 24 hrs. so far so good, installed it on CM nightly built. haven't had a single problem yet. battery life seems better with this. thanxs again :)
[Desire Android Development] golf60:
I have problems with wifi with the r2 Kernel. Not always connect.
[Desire Android Development] westernmg:
I Tried the R2 HAVS Kernel on Opendesire 4.0.15 today.

I had Problems connecting to mobile internet (2G/3G), it took a very long time to connect.

Not tested the WIFI...

Linpack was somthing about 37.3 Mflops without Setcpu ,thats pretty nice :)

But the "Break the Block" game was running only on 40-50FPS, the OD Kernel gives me continuous 61FPS@1113Mhz.
[Desire Android Development] Benee:
The OD Kernel is Oc'ed more. Wanted to provide some stable for everyone Kernel ;) Wifi update is comming in r3
[Desire Android Development] :
No, I didn't, what I was implying is that if you use 1 reliable governor instead of setting messing about with different ones during screen off you will have no sleep issues. Maybe I didn't state that clearly enough, but for the record, that is what I was trying to say, and I changed my first point on my previous post to reflect that.

Seems a bit more coincidental than concrete, but if you believe that, fair enough. In reality I believe you can't possibly be right though. :)

I did, and I responded accordingly.

Sounds more like SetCPU isn't changing the governor than smartass 'influencing' anything. Have you actually checked to make sure that the governor is being changed?

Cheap shot there, but I'll let you have that one. ;)
[Desire Android Development] sfjuocekr:
Lets double check that :)

Screen on:

# cat scaling_governor

smartass

Screen off:

# cat scaling_governor

conservative

It does work, I have to say it baffles me too as to why it behaves like this.

Maybe it's just a freak accident caused by something leftover in memory?

/edit: /sys/devices/system/cpu/cpu0/cpufreq is the directory that contains CPU related information.
[Desire Android Development] :
The kernel unregisters the current governor and registers the new one. I can't see how it is possible that anything is leftover. It can't run 2 at once. :confused:
[Desire Android Development] sfjuocekr:
How does the "wake up" work btw?

I was thinking it might be happening when you press the button it switches to smartass and thus triggering the sleep issue as it was still in sleep?
[Desire Android Development] MrDevil:
How'd you do that?? I'm still getting laggy playback with rockplayer.
[Desire Android Development] Tyheam:
Could this possibly cause any errors with a more customized rom like MIUI?
[Desire Android Development] heartwork:
this is a great kernel! running r8 with no problems (though with 'smartass' governor i still get the wake-up issue...using 'interactive' instead) in cm6.1 nightlies.

i was wondering whether it's possible to somehow reduce the output- base- signal/volume of the headphonejack via kernel- modifications. with my akg k370 (pretty good in-ears) i get some rather disturbing 'white noise' as long as there's a signal on the headphone- jack which (i think) wasn't there with the original HTC- rom/kernel. however...i thought it could be some kind of volume- boost in the kernel that's responsible for that?!

thanks for your work!
[Desire Android Development] navalynt:
I can't stress enough how highly experimental this is but I managed to compile for the CDMA Desire and it seems to work (minus WiFi, I have not been able to successfully compile the module for that yet).

I've compiled CM6.1 from source before, but this is my first time compiling a custom kernel. I run The Ultimate Droid 2.0.0 ROM (not CM6.1) and this Kernel is booting up and giving some fairly impressive Linpack and Quadrant scores.

Before I compiled I cloned the git from vorkKernel to my drive but I don't understand the file/directory structure to make edits. Where do I go to edit the frequencies and voltages so I can test out how well this phone overclocks?
[Desire Android Development] Benee:
Here this is a CDMA compile script. You only need Linux and set it up for compile (CyanogenMod wiki: Just get all the packages mentioned in this part "Install development support packages"). You will get a signed zip in the Builds folder.

I have done this because I have no CDMA Desire. So I can give no support for this.

Download
[Desire Android Development] navalynt:
The compilekernel is looking for vork-Kernel instead of vorkKernel. I just corrected it and letting it compile now.

Thanks!
[Desire Android Development] Benee:
Oh .. thanks need to fix this ;) and improve it more. But this should work for the cdma users.
[Desire Android Development] navalynt:
It was having some issues with test-signing so I temporarily removed those lines of code. It compiled, booted up just fine, and although wifi is working this time the mobile network will not connect. My signal bars just show an x.

EDIT: Finally compiled it right and everything seems to be working fantastically (including wifi)! AnyKernel update.zip attached!

I would be SUPER appreciative if someone could tell me where in the source to find the table for frequencies and voltages. I can't seem to find that information anywhere!
[Desire Android Development] goz5000:
I'll test it out. This is going too be sweet

Update

working great, not one issue yet. I'll test it longer and see how it does. Thanks for this.
[Desire Android Development] navalynt:
Updated CDMA kernel attached. I've been playing with voltages/frequencies all evening and found what I think is the most optimal layout (for now). Frequency range from 235Mhz to 1228Mhz. I was able to get the CPU up to 1422Mhz but the voltage increase to make it stable was insane and not recommended.

I attached a screenshot of this kernel clocked at 1228Mhz running quadrant. This was the best out of 12 runs which ranged from a low of 1549 but seemed come out mostly in the 1650 to 1725 range.
[Desire Android Development] goz5000:
Will test thanks again

Edit

Working fine no probs yet, now all we need is a way to make the GPU run faster lol
[Desire Android Development] ghmail2:
it seems in r8 the gpu result in quadrant is better,always over 400 ,what did you do?xD
[Desire Android Development] Benee:
Updated Kernel ;) Now a optional CFS version is there (nearly as smooth as BFS). And now more r version. Using date now.
[Desire Android Development] ghmail2:
which is better bfs oder cfs?
[Desire Android Development] K900:
Think BFS is still better, tho the new CFS patch does wonders under heavy load.
[Desire Android Development] ghmail2:
aha you mean that 200 lines improvement:p
[Desire Android Development] StuMcBill:
Which kernel is more stable and suited for everyday use?

Or is it a case of "suck it and see"?

Sent from my Amiga 500 using Workbench
[Desire Android Development] Benee:
I personally run the BFS one because i'm a big con kolivas fan. He makes really good clean code. But anyway I wanted to provide a CFS version with the new patch because it does wonders in smoothness and performance to stock CFS. Your choice. Would say test both and stick to your favorite.
[Desire Android Development] malaga82:
The new patch you are talking about for CFS is THIS ?

Just to be more clear :p
[Desire Android Development] LuffyPSP:
which on do i need? BFS or CFS? and how do i know that is the one i want? i'm using the previous version currently but at that time no option to choose like this.

Thanks! oh and btw using CM6.1 RC1 btw.
[Desire Android Development] Benee:
@malaga

Exactly that patch

@luffy

Test both and stick to the one which you like more (more stable, less laggier, smoother, better performance). I use the BFS version bit CFS isn't really worser than the BFS one.
[Desire Android Development] Das IceDice:
"[ERROR] acpuclock: Unable to drop ACPU VDD from 1275 to 1226 setting rate to 844800."

I get this after 18novBFS kernel update.

(Running @ stock clock)
[Desire Android Development] malaga82:
WOW, thanks Benee, im going to try CFS then ;)
[Desire Android Development] Benee:
@Das IceDice

Oops hope that was no tipping mistake >.< … looking into it tomorrow ASAP. Thanks for the info
[Desire Android Development] LuffyPSP:
ooo i see. but BFS is the default kernel/base? CFS is just a modified one?
[Desire Android Development] Benee:
No cfs is the original base (only one in linux mainline). But if you look at my github you notice that I have to branches one with bfs and one with cfs.
[Desire Android Development] malaga82:
I've done some tests with linpack, quadrant and neocore...and BFS still better than CFS.

I have a problem with setcpu anyway: if set a profile for "screen off", after lockscreen it stay always at 245.

I don't know if it's a MIUI problem this thing.

Edit: i have this issue if i set as main governor "interactive"...if i choose "on demand" freq is scaling correctly.
[Desire Android Development] Benee:
Kmsg would be helpful. Sorry can't give exact instructions (only my desire here with internet access) but google should have a small guide.
[Desire Android Development] fllash:
It may be completely pointless to know, but what is the minimum voltage in these kernels?

Thanks

Josh.
[Desire Android Development] LuffyPSP:
flashed the BFS one and working great!
[Desire Android Development] bland.life:
I'm seeing the same on OpenDesire 4.0.36.

Setting my profiles to ondemand for now.

Using the BFS version.
[Desire Android Development] EViollet:
Smartass

Hi

Currently testing the BFS kernel... and wondering why did you remove smartass? Was there any problems with it? ( apart from the wakeup issue but I can live with it without any problem)

I actually liked that governor... :)

Regards,
[Desire Android Development] heartwork:
same here with CM6.1 nightly...didn't happen with v8.
[Desire Android Development] faddys123:
What's bfs and cfs ?
[Desire Android Development] GuestK00150:
battery consumption

how are BFS and CFS doing ragarding battery consumption?

Thanks in advance
[Desire Android Development] mkolonko:
try google: http://www.stackednotion.com/2010/06/04/what-are-bfs-and-cfs
[Desire Android Development] Benee:
Yeah wake issues and cleaned up my git. Never thought anyone used it because I only heard wake issues. So I killed it. But I could add it back in next release. After the bugfix one that's building right now ...

925 mv to 1300 mv. But the 925 steps aren't used so 950 mv.

Bugfix:

Mistake in one freq step. Sorry

BFS CFS​
[Desire Android Development] omosiro:
Hi there~ I have used ur Kernel with thanksful mind.

Here, I have some problem with BFS.I flashed BFS. when the phone booted completly, It works very fine. But, when I try to reboot my phone, sometimes phone fall in loop.

CFS dont have this state, only BFS have it.

I have maked Korean translated MIUI ROM. and I recommanded vork CFS,BFS.

they have same problem in BFS, when they tring reboot , occasionally.

I would like to use your fantastic Kernel ,continuously. Thanks ;)

sorry for poor my English.
[Desire Android Development] wiggles87:
When I switch to interactive governor in SetCPU it gets locked to the max frequency and doesn't scale down. Using latest BFS kernel
[Desire Android Development] StuMcBill:
Yeah I found this too. Seems to work ok on CFS.

Sent from my Amiga 500 using Workbench
[Desire Android Development] puschkin:
Try the new kernel from 19-11-2010..seems to work :)
[Desire Android Development] Benee:
Yeah had a very stupid mistake in the freq table... Think that's the reason for the interactive issue. Sorry again
[Desire Android Development] StuMcBill:
Could this have been the reason I was getting massive battery drain on the kernels from the 18th?

Sent from my Amiga 500 using Workbench
[Desire Android Development] Benee:
yep. Device couldn't ramp down and stays at high freqs.
[Desire Android Development] StuMcBill:
Thanks, great work!!

Thanks for the quick reply!

Stu
[Desire Android Development] Das IceDice:
Nice work Benee! All running ok @ 19novBFS.

QScore 1822 @ stock clock :-)
[Desire Android Development] StuMcBill:
I only get 1680 on BFS with SetCPU on performance?

The interactive governer still seems to be stuck on max when using BFS from 19th November.

Stu
[Desire Android Development] ourfear:
without setcpu, i tested 3 times

1. 1446

2. 1714

3. 1715

good enough
[Desire Android Development] malaga82:
In performance i got 1804 with BFS and some tries(no oc), but it's all about in what is running in your device.

Compare with different devices and systems, is not suitable.

I tested both CFS and BFS, and the last one(BFS) is better in everything...at least in my device(tested quadrant,linpack and neocore).
[Desire Android Development] StuMcBill:
Just installed CFS and the interactive governer works ok, BFS gets "stuck" on max frequency.
[Desire Android Development] Minux31:
No, with latest BFS version, Interactive governer works fine ...
[Desire Android Development] EViollet:
I can confirm it's sticky. Just tried right now. I flashed a couple of hours ago.
[Desire Android Development] StuMcBill:
I think its sticky on CFS too, just had it stick on 384Mhz on mine.

Changed to ondemand and everything is ok now.
[Desire Android Development] malaga82:
I have another problem.

Audio level is very very LOW, compared with defrost or other vork release.

Even at max level, it's about 60% less than before.

I was thinking i managed sound levels, but it's the kernel that have very low sound output.

MIUI rom.
[Desire Android Development] StuMcBill:
Benee in the first post you said you "adjusted audio gain" - does this refer to the audio coming from the speaker when on a call (the normal front facing speaker, not the back one)?

Because in my case, while on a call, the sound from the speaker is FAR too loud, even on the lowest volume setting?

Is there any chance you could tweak this down a bit?

Thanks

Stu

Sent from my Amiga 500 using Workbench
[Desire Android Development] Benee:
Yeah when I fixed my laptop again then I will revert the audio mod and match pershoots version.
[Desire Android Development] StuMcBill:
Ah I see the full post now.

Thanks Benee.

Keep up the good work on this great kernel.

Sent from my Amiga 500 using Workbench
[Desire Android Development] malaga82:
too loud?

im in opposite side, for me and others with miui, audio output is too low...what a strange thing.

tnx anyway beene, good job!

Sent from my HTC Desire
[Desire Android Development] ghmail2:
After flashing new kernel, i barely hear my ringtone...but the speaker for telephone is just too loud, hmm pls fix this ,other than that, your kernel just rocks thanks for your work
[Desire Android Development] worstenbrood:
I get really slow usb transfer speeds with vorkKernel-SVS-BFS-SIO-19-Nov-2010 (930 KB/s). I must say i use apps2sd but with the standard CM kernel i get 2 Mb/s+. Anyone else suffering from this ?
[Desire Android Development] ghmail2:
after a reboot , it is gone....
[Desire Android Development] ourfear:
I get 1.8Mb/s+ with vorkKernel-SVS-BFS-SIO-19-Nov-2010
[Desire Android Development] twicejr:
Great thanks :)

Works fine.
[Desire Android Development] kf810110:
i want smartess,why discard it??
[Desire Android Development] danarama:
Tried this kernel. 1152 managed 2003 on quadrant. Best I've ever got at that clock. Haven't got close since though. Good work.

Going back to a HAVS though, for battery reasons.

What are the min / max voltages on vork?

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

DeFroST FAQ... http://xdaforums.com/showpost.php?p=6622965&postcount=2
[Desire Android Development] crapula512:
can you restore smartass and havs? especially havs, its a show-stopper for me.
[Desire Android Development] simonthor:
What's best. Bfs or cfs?

Sent from humanity's last hope.
[Desire Android Development] Murd0ck:
this where answered around 3 pages back but here is the link again.

http://www.stackednotion.com/2010/06/04/what-are-bfs-and-cfs
[Desire Android Development] Sarsippius:
Hi Benee, I have also noticed this issue posted by omosiro. Using 19.Nov BFS occasionally the phone will get stuck in a boot loop. It's a little different to boot loops I've had before where you can see the boot animation stall and then restart. This one the animation never noticeably stalls, just goes on and on. Other users of the MIUI_Au rom which includes your kernel have had similar issues. I'm trying CFS now and will report if the same issue is present.

By the way thanks for providing a CFS version, I hope you will continue to do so as my aforementioned video playback issues seem to definitely be related to BFS. 19.Nov BFS is the best so far but still has intermittent lag/skips, CFS is completely smooth.
[Desire Android Development] Benee:
Maybe I will provide soon more versions. Like HAVS with CFS/BFS but for now compiling takes long enough. Getting soon a cpu upgrade so compiling time is no issue more. Additional than I try to improve overall performance by finding the best variation (io, slab, rcu).
[Desire Android Development] navalynt:
Any idea why the IO on the Droid X scores so high in quadrant?
[Desire Android Development] K900:
Probably buffered, not real NAND (or whatever it has) speed
[Desire Android Development] faddys123:
What setCPU profiles you use ? For good battery , occasionally I play games a few and a bit of Facebook
[Desire Android Development] Benee:
No profile. Nothing. Only enabled interactive and two more freq steps via adb (to lazy to hack ramdisk everytime I test a new rom). The govenor does everything for me.

But I recommand setcpu because it is easier to use. Only change govenor to interactive and enable overclocking (if it is wanted).
[Desire Android Development] Murd0ck:
i'm just using the ondemand. and i didn´t have any problems and got fine battery life.
[Desire Android Development] mad-murdock:
hmm, i experience sever system lags with interactive. its like this:

boot (or reboot), and everything is fine. after an undefined while, the system slows down extremly. just like the cpu frequency stays down at 245 (at least it feels like that). at first i did reboots to make this go away. but since i changed from interactive to ondemand, i got no problems anymore.

running cyanogen nightly 184 (latest), vork kernel 19-11-2010, setcpu with the following profiles now:

- default=245-998mhz, ondemand

- temp > 42 degress celcius -> 245-576mhz powersave (in case phone gets hot in sun or oven)

- charging ac -> 245-1152mhz, performance

- charging usb -> 245-998mhz, ondemand

- screen off -> 245-384mhz, powersave

- battery < 31% -> 245-729mhz, ondemand

the ondemand values have been interactive when i encountered problems.

any idea what might be wrong? since it is told here, you should use interactive.