yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] woti23:
it can, you need

a linux flavoure, depending on that if not allready included

- a kernel that supports btrfs (either in the kernel or module)

- the btrfs-tools

(apt-get install btrfs-tools # if you have a debian-like linux)

same applies for other filesystems: jfs, xfs, nilfs2 ....

also older gparted versions (in older linux distris) have a bug with btrfs, so get an actual version or download it from gparted org instead from your linux distribution

GParted 0.7.0-git actually works on ubuntu
[Desire Android Development] coutts99:
Well, extremely laggy and crap quadrant scores (about 1200).

Changing some config options and rebuilding

Another version

http://mirror.couttstech.com/androi...dv2.2f_HAVS@925mV_CMBattFix_AUTOGROUP_CFQ.zip

Changed some options and changed BFQ to CFQ
[Desire Android Development] ssauger:
Will there be a 875mV OC1190 Mhz Kernel with auto group on?
[Desire Android Development] coutts99:
From the results I'm getting, no it's not worth it, haven't had a quadrant score over 1300 yet.

Need some more feedback before I decide whether to bother or not.

Personally, I'm going back to BFS/BFQ, everything was fast and smooth for me.
[Desire Android Development] coutts99:
Some interesting comments from Con Kolivas about the patch here -:

http://ck-hack.blogspot.com/2010/11/create-task-groups-by-tty-comment.html
[Desire Android Development] superfurryallan:
I definitely notice a much smoother experience with the lock screen, and scrolling in the browser and apps. I can confirm that my quadrant scores are not particularly high, however i'm not terribly concerned about benchmarks.

This is based on siberes 850mV HAVS GCS kernel, which has suprisingly been stable for the last few hours for me.
[Desire Android Development] coutts99:
Can you do the following via adb on siberes kernel?

cat /proc/sys/kernel/sched_autogroup_enabled
[Desire Android Development] superfurryallan:
C:\android-sdk-windows\tools>adb shell

* daemon not running. starting it now *

* daemon started successfully *

# cat /proc/sys/kernel/sched_autogroup_enabled

cat /proc/sys/kernel/sched_autogroup_enabled

/proc/sys/kernel/sched_autogroup_enabled: No such file or directory
[Desire Android Development] coutts99:
Ok you haven't got autogroup enabled.
[Desire Android Development] superfurryallan:
haha, i cant for the life of me figure out whats going on with this kernel then :) its very very smooth. moreso than any I have tried previously.

Incase it helps, heres some more information on anything I can see sched mentioned in, in the same directory.

# cat modules_disabled

cat modules_disabled

0

# cat sched_child_runs_first

cat sched_child_runs_first

0

# cat sched_rt_period_us

cat sched_rt_period_us

1000000

# cat sched_rt_runtime_us

cat sched_rt_runtime_us

950000

# cat sched_compat_yield

cat sched_compat_yield

1
[Desire Android Development] coutts99:
Can you do adb pull /proc/config.gz and send it to me
[Desire Android Development] superfurryallan:
renamed as a text file and attached.

Thanks.

Allan
[Desire Android Development] coutts99:
No mention of, "CONFIG_SCHED_AUTOGROUP", so it hasn't been patched into the kernel properly.

I'd say this is a case of the placebo affect :)
[Desire Android Development] superfurryallan:
very well, i'm inclined to think that something is happening somewhere, as I stand by the fact that it is very smooth.

I've posted on siberes thread now and will see what he says. As long as the kernel is not quietly destroying the inside of my phone, I am happy for now :)

Will be interested to see how this works out. Thanks for your help mate.

Allan
[Desire Android Development] coutts99:
Have you tried one of my BFS kernels? Personally, I find them very smooth from lockscreen as you say you found siberes, I'd be interested to see if you notice any difference..
[Desire Android Development] sffmandrake:
hi,

i've got a black screen when i try to wake up the phone...
[Desire Android Development] sffmandrake:
with the last, couttstech-2.6.32.26_LeeDroidv2.2f_HAVS@925mV_CMBattFix_AUTOGROUP_CFQ
[Desire Android Development] coutts99:
Hmm that one was fine for me (abliet a bit slow), just recompiling it actually as it is using BFQ by default instead of CFQ.
[Desire Android Development] superfurryallan:
couttstech-2.6.32.26_LeeDroidv2.2f_HAVS@875mV_CMBattFix_BFS_BFQ

I used this for an hour or so yesterday. I noticed that battery drain was decent. I did find it to be slightly less responsive from the lock screen, and when scrolling. I have not used this kernel for as long as the sibere one, so I would really need to go back and test this again to check for differences.

I'm a little reluctant to do this currently as i'm pleased with how things are running with my 850mV kernel currently, and will be leaving the office shortly.

I'll see what sibere says regarding the GCS on his kernel and try your kernal I have mentioned above, over the weekend.

I'll let you know once I have given it a fair chance.
[Desire Android Development] coutts99:
Updated it
[Desire Android Development] Alex-V:
is this a svs kernel..? I have problems with the latest Cfs svs kernel (sense)...phone getting hot..fc´s after a while and reboot :confused:

For some reason..its better know..will test with charger again

No problems with cfs Havs 875

A Idea..? Will try this kernel :)

with kind regards...Alex
[Desire Android Development] Terepin:
And while you are at it, could you make test kernel with deadline scheduler? If I'm not asking to much... :o
[Desire Android Development] melethron:
Deadline is already included (and set as default in my Rom):

bash-3.2# cat /sys/block/mmcblk0/queue/scheduler
noop [deadline] cfq bfq
[Desire Android Development] Leno2002:
Dear coutts99, could you try to compile a kernel driver called "vocpcm". In the kernel source from HTC to file "arch/arm/mach-msm/qdsp5_comp/vocpcm.c". The kernel must be compiled with support for this driver is necessary for recording programs off the line, but I think such a program is needed for many users of Desire.

I beg you to answer a post in private because they do not know the English language (using auto translation from the site) and therefore do not have the ability to track responses to the topic.
[Desire Android Development] Terepin:
But I'm not using your ROM, as you can see.
[Desire Android Development] coutts99:
Deadline is already in I think
[Desire Android Development] Terepin:
Maybe I'm missing something, but deadline is "just" another I/O scheduler, just like CFS and BFS, right? Then why those two need separate versions of kernel and deadline doesn't?
[Desire Android Development] woti23:
CFS/BFS are cpu scheduler

BFQ/CFQ/deadline ... i/o scheduler
[Desire Android Development] coutts99:
This isn't in the kernel source for 2.6.32.
[Desire Android Development] coutts99:
Kernel with BTRFS and JFS

http://mirror.couttstech.com/android/bravo/kernel/Test/SVS-CFS-BTRFS-JFS.zip
[Desire Android Development] coutts99:
I also came across this -:

http://git.zen-kernel.org/zendroid/commit/?h=vr&id=b2c62f944181ef1d62ffbff8ee85cdf3d7b5ee63

http://www.gelato.unsw.edu.au/IA64wiki/IOScheduling/VRscheduler

No idea if it will be any use (haven't read about it much yet), but it's in the test kernels if you want to have a play with it :)
[Desire Android Development] coutts99:
Took out CK patchset from BFS kernels, and download locations have changed slightly, see first post for new details.
[Desire Android Development] teorouge:
Did you try with Parted Magic 5.9 (fresh release) live? Think it's a nice alternative to GPartED and maybe it works ok.
[Desire Android Development] woti23:
guess what it is using for partitioning?

right: gparted

to get it running, the kernel must have fs support (eg for btrfs) and the fs-tools must be installed (eg btrfs-tools)
[Desire Android Development] melethron:
Then kernel support is not enough. You need to set it up.

V(R) seems close to useless to me (as I/o scheduling on nand in general):

In 1987, Geist and Daniel published a paper describing a new I/O scheduling algorithm they called V(R). The parameter R, a real in the range [0,1], denotes the penalty for a reverse seek (that is, changing the current head direction), such that the effective seek distance for reversing the head direction is the actual seek distance plus R times the size of the disk. The request with the nearest effective distance to the last request is chosen next, thus V(0) is SSTF (shortest seek time first), and V(1) is SCAN.

By tuning this parameter, one can obtain different scheduling behaviours on a continuum between SSTF, which typically provides good throughput but is particularly prone to starvation, and SCAN, which is inherently free from starvation. Geist shows that V(0.2) provides excellent performance; better than SCAN, SSTF and V(0.1).

We dont have a disk. We dont have a moving arm with a head. We dont have "seek times".

>> We don't need seek time optimization.

Could still be used to "prove" that our flash drive is not rotating. There should be no difference in stress writes between V(0) ... V(0.2) .. V(1).

I already benched noop (FIFO) and cfq (queue sorting respects "seek time"). Here a bench from a german linux journal on a hard disk:

Noop is much slower (the more seconds the worse) on HDD stress writes . But on flash its different:

1. Noop:

DB overall: 402,4

Stress overall: 915,4

2. CFQ:

Db overall: 397,4

Stress test: 909,2

Those are scores (not seconds) from TAP benchmark and noop is even a bit better (less cpu because it doesn't need to sort I/O requestst).

BTW: Thanks for the Kernel.
[Desire Android Development] Fightspit:
coutts99,

Why you didn't update some HTC files from the AOSP kernel git repository (these files in this link : http://git.couttstech.com/?p=couttstech-asop.git;a=commit;h=08e076cc4bf5ede139e401f12eecbe9f7f9bb9c2 ) in the Sense's one ?

I updated them manually in my computer, compiled your repo + new Htc files and it worked :)
[Desire Android Development] coutts99:
I've neglected this kernel for a bit to be honest :)

*EDIT* The patch barfs
[Desire Android Development] Fightspit:
And maybe the new camera drivers from HTC also ? :D

http://git.couttstech.com/?p=couttstech-asop.git;a=commit;h=e15831268ec62fac357e925268630fe45947aed5
[Desire Android Development] Anakha56:
I take it that means it does not compile? :p
[Desire Android Development] theooo:
Hello again, i've just flashed ur latest 925 HAVS BFS kernel today and i got strange thing happened on my desire, no matter what governor i use (i tried conservative, smartass, and ondemand) my CPU wont go to lower clock.. It always on maximum clock (984 for screen on and 245 for screen of). Any idea why this is happening?? Thanx in advance dude, other than that your kernel is superb! :D
[Desire Android Development] coutts99:
Can anyone confirm this?
[Desire Android Development] LoQo_:
On 875 all works good
[Desire Android Development] theooo:
FYI: when i use earlier build of 925Havs BFS same thing happened to me. Even in SetCPU info tab i saw on clock time usage that almost all the time my cpu working only at 984 and 245 (other than that clock usage time is only about 50-90)

I've tried to uninstall SetCPU, upgrading to latest 925HavsBFS and wipe cache + dalvik cache but it's still happening.. :(
[Desire Android Development] Alex-V:
Don´t know..maybe a screenstate scaling script in etc/init.d..?

have you tried another kernel from coutts to compare..?

all fine here

with kind regards..Alex
[Desire Android Development] theooo:
Yes, just revert to original baadnwz 1.7c kernel but still got same problem.. Maybe its not couts's kernel related problem. But can you help me? Now with original kernel (leedroid 2.3 kernel based on 2.6.32.15) it still show maximum clock everytime with different governor.. And Temp+CPU v2 widget show CPU load is 99% all the time.. :(
[Desire Android Development] woti23:
look at /system/bin/

some roms have there a shellscript "strt", which is startet automatically.

and this script starts more other scripts like ssts (screen state scaling)

and ssts is a very simple loop that changes between screen on and off to different govenors

some roms have/had also in /dada/config/..

camprio scripts that changed the gov/freq
[Desire Android Development] theooo:
Thanx dude, but still can't find the problem because screenstate is fine, from logcat i saw when screen off screenstate working. :)

I just did a clean ROM reinstall and it seems now the problem gone, hopefuly its not coming again. :(

Thanx for your help dude. :)
[Desire Android Development] melethron:
"adb shell busybox ps". The third value is cpu time. There you see what needs the cpu power.
[Desire Android Development] Nitin985:
I was wondering what is the best governed for havs, I'm in 875 and ondemand is really slow and smartass dosent work properly ?
[Desire Android Development] teorouge:
Didn't get that, sorry... just read the release title in RSS news I get. :rolleyes:
[Desire Android Development] melethron:
@coutts99: I browsed around a bit in zendroid source. There is quite some interesting stuff:

+config IOSCHED_SIO
+ tristate "Simple I/O scheduler"
+ default y
+ ---help---
+ The Simple I/O scheduler is an extremely simple scheduler,
+ based on noop and deadline, that relies on deadlines to
+ ensure fairness. The algorithm does not do any sorting but
+ basic merging, trying to keep a minimum overhead. It is aimed
+ mainly for aleatory access devices (eg: flash devices).

merging + deadlines... thats what i call an i/o scheduler for flash, not crappy bfq/cfq with its reduced interactivity from "seek times" sorting.

Also the higher ramp ups of smartass sound interesting: http://git.zen-kernel.org/zendroid/commit/?h=smartass

Edit: what did you comile? 36 or 35?

EDIT2: should have read proberly ... you only added that scheduler .... thought you compiled a completly new kernel. Well i think the zen kernel would only work proberly with aosp anyway....
[Desire Android Development] coutts99:
Yes there is some good stuff on zendroid once you find your way round. Ill take at these tomorrow.
[Desire Android Development] wolfeno:
Hi! How can i change governor to smartass without installing SetCPU?

And thank you for great kernel.
[Desire Android Development] coutts99:
That appears the have patched correctly, I'll rebuild the test kernels with it enabled.

We already have the same ramp up/down steps -:

/*
* Freqeuncy delta when ramping up.
* zero disables causes to always jump straight to max frequency.
*/
#define DEFAULT_RAMP_UP_STEP 384000
static unsigned int ramp_up_step;

/*
* Max freqeuncy delta when ramping down. zero disables.
*/
#define DEFAULT_MAX_RAMP_DOWN 384000
static unsigned int max_ramp_down;

/*
* CPU freq will be increased if measured load > max_cpu_load;
*/
#define DEFAULT_MAX_CPU_LOAD 80
static unsigned long max_cpu_load;

/*
* CPU freq will be decreased if measured load < min_cpu_load;
*/
#define DEFAULT_MIN_CPU_LOAD 30
static unsigned long min_cpu_load;
[Desire Android Development] theooo:
Tried this one but i dont understand the result dude. But now everything is fine after doing some cleanup and reinstall ROM. :)

Thanx for your help.
[Desire Android Development] b-george:
Here is my snapshot, what do you think is my battery drain high?
[Desire Android Development] karma0321:
Hi everybody! Thank you coutts for your kernels I've been using them for some time lately and I like them a lot.

I just wanted to add my 2 cents for battery life.. I'm testing a combination that seems to work well, I have set 499-1075 with conservative governor for screen on and 245-460 with conservative governor for screen off. The phone is quick and responsive and I'm noticing a good difference as regards battery drain..

Using bfs .28 kernel havs 875 with Z 0.6 rom.

Hope it can be useful to somebody out there. :)

Have a nice day!
[Desire Android Development] Anakha56:
I cant comment on your battery drain but please tell me what app you are using to view that? :)
[Desire Android Development] b-george:
Here :)

SystemPanel App / Task Manager

by NextApp, Inc.

10,000 downloads, 2899 ratings (4.7 avg)

$2.99
[Desire Android Development] melethron:
CFS test kernel:

zcat /proc/config.gz | egrep "BFS|GROUP"
# CONFIG_SCHED_BFS is not set
# CONFIG_GROUP_SCHED is not set
CONFIG_CGROUPS=y
# CONFIG_CGROUP_DEBUG is not set
CONFIG_CGROUP_NS=y
CONFIG_CGROUP_FREEZER=y
CONFIG_CGROUP_DEVICE=y
CONFIG_CGROUP_CPUACCT=y
CONFIG_CGROUP_MEM_RES_CTLR=y
CONFIG_CGROUP_MEM_RES_CTLR_SWAP=y
# CONFIG_SCHED_AUTOGROUP is not set
CONFIG_CGROUP_BFQIO=y
CONFIG_NET_CLS_CGROUP=y
# CONFIG_BFS_FS is not set

+

E/dalvikvm( 432): Cannot get policy, owner thread id=445
E/dalvikvm( 432): Cannot get policy, waiter thread id=436
E/dalvikvm( 432): Bad cgroup data {1:cpuacct:/uid/1000
E/dalvikvm( 432): }
E/dalvikvm( 432): Bad cgroup data {1:cpuacct:/uid/1000
E/dalvikvm( 432): }
E/dalvikvm( 432): Cannot get policy, owner thread id=436
E/dalvikvm( 432): Cannot get policy, waiter thread id=445
E/dalvikvm( 432): Bad cgroup data {1:cpuacct:/uid/1000
E/dalvikvm( 432): }
E/dalvikvm( 432): Bad cgroup data {1:cpuacct:/uid/1000
E/dalvikvm( 432): }

# CONFIG_GROUP_SCHED is not set ????
[Desire Android Development] coutts99:
Ah bugger :) I always think CONFIG_GROUP_SCHED is CONFIG_SCHED_AUTOGROUP!

It'll be tomorrow when I get to fix :)

*EDIT* Building now, will upload later!

stevec@aoede:~/dev/phone/kernel/couttstech-bravo$ egrep "BFS|GROUP" .config
# CONFIG_SCHED_BFS is not set
CONFIG_GROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
# CONFIG_RT_GROUP_SCHED is not set
CONFIG_CGROUP_SCHED=y
CONFIG_CGROUPS=y
# CONFIG_CGROUP_DEBUG is not set
# CONFIG_CGROUP_NS is not set
CONFIG_CGROUP_FREEZER=y
# CONFIG_CGROUP_DEVICE is not set
CONFIG_CGROUP_CPUACCT=y
# CONFIG_CGROUP_MEM_RES_CTLR is not set
# CONFIG_SCHED_AUTOGROUP is not set
# CONFIG_CGROUP_BFQIO is not set
# CONFIG_NET_CLS_CGROUP is not set
# CONFIG_BFS_FS is not set
[Desire Android Development] melethron:
Those test kernels are in the "origin/exp" branch?
[Desire Android Development] coutts99:
No just normal branch, I've just been changing .config by hand. The exp branch has nothing interesting in at the minute.

Normal kernels have defconfigs.
[Desire Android Development] coutts99:
Download again :)
[Desire Android Development] melethron:
compiled it myself with some minor changes. I saw that V(R) is not in anymore so i added that back (Its more interresting than i thought). Apart from that i added nilfs2 and xfs as modules.

I also change cgroup to this (equal to stock settings):

CONFIG_GROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
# CONFIG_RT_GROUP_SCHED is not set
# CONFIG_USER_SCHED is not set
CONFIG_CGROUP_SCHED=y
CONFIG_CGROUPS=y
CONFIG_CGROUP_DEBUG=y
# CONFIG_CGROUP_NS is not set
CONFIG_CGROUP_FREEZER=y
# CONFIG_CGROUP_DEVICE is not set
# CONFIG_CPUSETS is not set
CONFIG_CGROUP_CPUACCT=y
CONFIG_RESOURCE_COUNTERS=y
[Desire Android Development] woti23:
this works since a few days - compiled coutts CFS branch

zcat config.gz |grep GROUP

CONFIG_GROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
# CONFIG_RT_GROUP_SCHED is not set
CONFIG_CGROUP_SCHED=y
CONFIG_CGROUPS=y
# CONFIG_CGROUP_DEBUG is not set
# CONFIG_CGROUP_NS is not set
CONFIG_CGROUP_FREEZER=y
CONFIG_CGROUP_DEVICE=y
CONFIG_CGROUP_CPUACCT=y
# CONFIG_CGROUP_MEM_RES_CTLR is not set
CONFIG_SCHED_AUTOGROUP=y
# CONFIG_NET_CLS_CGROUP is not set

actually i'm not sure it does anything than provide stats anyway

as there is

- no libcgroups.so

- no cgconfig

- no /etc/cgroups.conf

which some linux distros have
[Desire Android Development] melethron:
Y debug shouldnt be needed. I just set the options from stock and made the rest with menuconfig. Devices should also not be needed.
[Desire Android Development] DroidBois:
Is it possible to get a version that is not overclocked? My phone has always been rock solid and fine without having to overclock it and I worry about hardware damage by fiddling around with CPU speeds.
[Desire Android Development] coutts99:
It won't overclock unless you tell it to with setcpu
[Desire Android Development] theooo:
Hello, even this kernel was OCed it doesnt't mean that your desire will run at OCed clock all the time. U can set it to normal clock with SetCPU. And by default if u flash this kernel it was set on default desire clock (998.4Mhz) :)

--edit--

Wow you are fast coutts :)
[Desire Android Development] Broquen:
Is the couttstech-2.6.32.28_OC1190_BFS_BFQ_SLQB (jan 14th) using 875mV too?
[Desire Android Development] beanbean50:
well well mr coutts it looks like you've out shone yourself with your latest HAVS creation (2.6.32.28_OC1190_HAVS@875mV_BFS_BFQ_SLQB)

I can hardly believe the TAP benchmark results myself ...well done old chap...!
[Desire Android Development] woti23:
http://www.phoronix.com/scan.php?page=article&item=linux_2637_video&num=1

but without CONFIG_SCHED_AUTOGROUP=Y i believe it does nothing than statistics, because there is no manual config for autogroups like /etc/cgroup.conf and no libcgroups

auto group sched is the "magic" 200 lines of code, the answer from mainline kernel devs (mike galbraith) to BFS

i could be wrong, but otherwise to ditch BFS and not to take the advantages of the mainline patch would be scurile
[Desire Android Development] coutts99:
Unless you compile kernels on your phone with lots of threads, autogroup won't help with anything. As we also don't have ttys, again its useless.
[Desire Android Development] woti23:
so why is cgroups implemented at all in the 1.72 rom's if nothing uses it?
[Desire Android Development] melethron:
EDIT: forgot that post. Are you benching on nand or on sdcard?

Cgroups != tty autogroup

check this: http://www.mjmwired.net/kernel/Documentation/cgroups.txt

Cgroups isn't autogrouping tty. It has to be set up "manually". Dalvik attaches processes to cgroup. Here is a bit of the code:

http://gitorious.org/0xdroid/dalvik...ed9f51d68cedbee59cc936685?diffmode=sidebyside

From what i see cgroups seems like a "workaround" for for a bad scheduler behaviour considering interactivity. From what i see (at least from cgroup documentation - code is beyond my "league") it isn't intended to speed up "user expirience" but to control user groups on hardware that wont fit in a phone ^^

Also tty autogroping isnt for a workload you have on phone.... make -j64 isnt something you do on a phone ...^^ (would still be funny xD)
[Desire Android Development] beanbean50:
it says 'Benchmark on /data'

I'm using the Espresso HD A2SD+ ROM but not quite sure why my score has jumped a thousand points since flashing the HAVS kernel, quadrant score still the same at around 1700
[Desire Android Development] dimdroid:
Hi guys,

First of all i want to thanks coutts for his great job.

I ran a Quadrant with 2.6.32.28 HAVS@875mV kernel, clocked at 998Mhz and i got about 1700 points max. With the previous version (2.6.32.27 HAVS@875mV) my score was about 2000 points and now to get this score i need to o/c at 1190Mhz. Both tests were with Leedroid 2.3d + data2whatever with 1Gb ext2 partition.

I dont trust Quadrant but i m just wandering why i see about 300 points reduction to score...
[Desire Android Development] Hammerhand.17:
Hi, I don't know if I am doing anything wrong, but I have a problem:

With kernel couttstech-2.6.32.28_OC1190_CFS_BFQ_SLQB I use SetCPU and it says it is set to smartass, 245-998, but in the cpu freq it is always 998. What's happening?

Edit 1:

Well, I see in quick system info that "android system" is always at 80-90% of cpu, and "HTC Sense:remote" 25-27% (yes, more than 100%); if I finish HTC Sense:remote, everything goes well a little time, then it restarts and everything happens again

In logcat there are a lot of errors like these:

E / dalvikvm (209): Cannot get policy, owner thread id = 237

E / dalvikvm (209): Cannot get policy, owner thread id = 238

E / dalvikvm (209): Cannot get policy, waiter thread id = 314

Edit 2: If I disable everything in HTC sense sync account, the charge of the CPU seems to be fine, but the errors in logcat doesn't dissapear.