yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] coutts99:
Ok, based on some quick benchmarks I have done, I have built some kernels with the VR IO scheduler enabled as default instead of BFQ.

If anyone can be bothered to do some tap benchmarks before and after installing that would be appreciated :)

*EDIT* - VR now default in kernel
[Desire Android Development] Terepin:
BFS, class 6 SD card:

Ext2:

BFQ -> 2434

VR -> 2720

Ext3:

BFQ -> 2670

VR -> 2732

Ext4:

BFQ -> 1955

VR -> 2679
[Desire Android Development] beanbean50:
Before (using 2.6.32.28_OC1190_HAVS@875mV_BFS_BFQ_SLQB)

Details of Performance on /data

Iterations: 6 - Single Test Duration: 1000

Timestamp: 20110117T141413

Overall Performance: 2620(206)

Database Performance: 287(16)

FileRead/Write Performance: 1282(66)

StressTest Performance: 1051(195)

DB writes: 40(21) Writes/s

DB reads: 178(5) Reads/s

DB deletes: 212(13) Deletes/s

File writes 10k: 1064(61) kB/s

File writes 1M: 2409(14) kB/s

File reads 10k: 6022(663) kB/s

File reads 1M: 9060(21) kB/s

File write Overhead: 5.242(0.535) ms

File read overhead: 0.557(0.183) ms

StressWrite 1M: 1050(310) kB/s

StressRead 1M: 8695(53) kB/s

StressWrite 10k: 392(51) kB/s

StressRead 10k: 2836(749) kB/s

After (using 2.6.32.28_OC1190_BFS_VR_SLQB)

Details of Performance on /data

Iterations: 6 - Single Test Duration: 1000

Timestamp: 20110117T142207

Overall Performance: 2723(164)

Database Performance: 292(7)

FileRead/Write Performance: 1319(25)

StressTest Performance: 1112(162)

DB writes: 56(2) Writes/s

DB reads: 185(6) Reads/s

DB deletes: 196(10) Deletes/s

File writes 10k: 1108(32) kB/s

File writes 1M: 2364(78) kB/s

File reads 10k: 6333(80) kB/s

File reads 1M: 9132(466) kB/s

File write Overhead: 4.789(0.294) ms

File read overhead: 0.484(0.059) ms

StressWrite 1M: 1187(62) kB/s

StressRead 1M: 8849(64) kB/s

StressWrite 10k: 522(57) kB/s

StressRead 10k: 2922(640) kB/s
[Desire Android Development] Terepin:
I think you can safely ditch crappy BFQ and start using better VR instead.
[Desire Android Development] coutts99:
Have done, mind deadline came a very close second.
[Desire Android Development] Terepin:
Give us kernels with deadline too, please. But I'll be testing only on Ext3.
[Desire Android Development] coutts99:
Deadline is already in.

echo deadline > /sys/block/mmcblk0/queue/scheduler;
echo 1 > /sys/block/mmcblk0/queue/rotational;

for i in 0 1 2 3 4 5;
do
echo deadline > /sys/block/mtdblock$i/queue/scheduler;
echo 0 > /sys/block/mtdblock$i/queue/rotational;
done;
[Desire Android Development] Terepin:
Is it normal to get better score if I move more apps to Ext partition? I had few apps on FAT32 with score ~2200, but after moving them back "into phone" I got 2800.
[Desire Android Development] melethron:
Hmm. Maybe the extrem low score on ext4 has something to do with delayed allocation of ext4 ....

Thats most likely random. Do more than 1 run. It can be that you have bad luck on one run and get a low score because of more "block erases". Only thing that would explain this is that your sd-card has ****ty wearleveling. If it wrote to non empty blocks on first bench and then ... after there apps were moved (and writen on those blocks) it wrote to blocks that where already empty. Well as i said. Do several benches.....
[Desire Android Development] melethron:
Hmm. I compiled your kernel with "deadline" default. V(R) was mainly build for testing and its still experimental. Deadline has proven to be stable on ssd for years now....
[Desire Android Development] Terepin:
Funny:

2. run -> 2480

3. run -> 2520

4. run -> 2820

:confused:
[Desire Android Development] beanbean50:
yes you're right, I just moved a dozen or so apps back to the phone memory and the TAP score has jumped nearly a thousand points...

so I guess all this benchmark is measuring is the speed of ones SD card...?
[Desire Android Development] Muxeu:
2 coutts99: could you compile VR scheduler for test line (btrfs, jfs, reiserfs)?
[Desire Android Development] coutts99:
I think its in, just needs enabling. I might be wrong though.
[Desire Android Development] woti23:
some roms start a script in 99complete (eg /system/bin/optz) which sets it back to cfq or deadline ;-)

just if some tests different scheds, one should check which is really activ
[Desire Android Development] coutts99:
Good point, which is why I only used to compile one in, that way its always used :)
[Desire Android Development] ownhere:
BUG report for VR, seems VR easily lead to SD card error:

<3>[ 321.222839] mmc1: Data timeout
<3>[ 321.222961] mmc1: DMA channel flushed (0x80000004)
<3>[ 321.223297] mmcblk0: error -110 transferring data, sector 30947328, nr 24,
card status 0xc00
<3>[ 321.386413] mmc1: Data timeout
<3>[ 321.386779] end_request: I/O error, dev mmcblk0, sector 30947328
<3>[ 321.387390] Buffer I/O error on device mmcblk0p3, logical block 90112
<4>[ 321.387695] lost page write due to I/O error on mmcblk0p3
<3>[ 321.388305] end_request: I/O error, dev mmcblk0, sector 30947336
<3>[ 321.388641] Buffer I/O error on device mmcblk0p3, logical block 90113
<4>[ 321.389251] lost page write due to I/O error on mmcblk0p3
<3>[ 321.389556] end_request: I/O error, dev mmcblk0, sector 30947344
<3>[ 321.390167] Buffer I/O error on device mmcblk0p3, logical block 90114
<4>[ 321.390747] lost page write due to I/O error on mmcblk0p3
<3>[ 322.001617] mmc1: Data timeout
<3>[ 322.001953] mmc1: DMA channel flushed (0x80000004)
<3>[ 322.002990] mmcblk0: error -110 transferring data, sector 30489144, nr 8,
card status 0xc00
<3>[ 322.146179] mmc1: Data timeout
<3>[ 322.146514] end_request: I/O error, dev mmcblk0, sector 30489144
<3>[ 322.147125] Buffer I/O error on device mmcblk0p3, logical block 32839
<4>[ 322.147460] lost page write due to I/O error on mmcblk0p3
<4>[ 323.301757] JBD: Detected IO errors while flushing file data on mmcblk0p3

this log can be get with:

adb shell "dmesg|grep mmc|tail -20"

set rev_penalty to 1 will cause this error occurs more frequently.
[Desire Android Development] coutts99:
Good catch.

My dmesg is completely clean, anyone else have errors?

*EDIT* Pushed some large files onto sdcard, and still no errors.

*EDIT 2* No matter how hard I try and stress the SD card, I don't get these errors.
[Desire Android Development] ownhere:
I use data2ext, /data/data is location to /dev/block/mmcblk0p3, so maybe the system need write lots of things to SD, which lead VR report error.

change scheduler to DEADLINE is ok. no error.
[Desire Android Development] coutts99:
Can anyone on data2ext and using this kernel please check this out?

Thanks
[Desire Android Development] marse.online:
is it recommended to use the new kernel with leedroid 2.3d ?
[Desire Android Development] coutts99:
Should be OK, but read the last couple of posts about a possible bug.
[Desire Android Development] Fightspit:
It is a sense kernel, so you can use it in a sense ROM like yours :)

Edit: grilled :D
[Desire Android Development] Nitin985:
I've had no nifty copying files with vr its a lit smoother and my benchmarks have slightly increased , good work coutts
[Desire Android Development] woti23:
im running VR since yesterday on ext4 and have no error messages in dmesg

only thing i get about mmc is

[80627.324310] mmc1: Starting deferred resume

[80627.935272] mmc1: Deferred resume completed

same kernel and patch source than coutts
[Desire Android Development] Semmy7:
how to change scheduler in init script?

Please tell me how to change the scheduler in init.d ?

Nothing has changed after flashing the new 99complete with strings:

#!/system/bin/sh
sync;
setprop cm.filesystem.ready 1;

echo bfq > /sys/block/mmcblk0/queue/scheduler;
echo 1 > /sys/block/mmcblk0/queue/rotational;
for i in 0 1 2 3 4 5;
do
echo bfq > /sys/block/mtdblock$i/queue/scheduler;
echo 0 > /sys/block/mtdblock$i/queue/rotational;
done;

I still have cfq as default:

#cat /sys/block/mmcblk0/queue/scheduler

noop deadline [cfq] bfq sio vr
[Desire Android Development] DroidBois:
Hi, I am running Alex-V.

I tried to install "couttstech-2.6.32.28_OC1190_BFS_VR.zip" from

http://mirror.couttstech.com/android/index.php?dir=bravo/kernel/Sense/BFS/

Using the link

http://mirror.couttstech.com/androi...S/couttstech-2.6.32.28_OC1190_BFS_VR_SLQB.zip

By going in to Recovery and Installing from Zip.

After a very long boot, I was presented with error "System is not responding - Force Close or Wait".

Did I install this in the correct way or use the wrong kernel?

Thanks for the hard work everyone - fantastic job and appreciated by all.
[Desire Android Development] Ninsassin:
I want to try out this new kernel, but I'm not sure what ext my partition is.

I was wondering is there a way to check what ext I'm currently using.

I partitioned it 6months ago so I'm not sure is it ext2,ext3, or ext4.
[Desire Android Development] woti23:
kind of strange:

on ext4 (looped image) on sd class 2 sandisc

------- scheduler VR

did some test (TAP) with different rev_penalty values

started with rev_penalty=10 (default)

3 times about 2950-3050 overall

changed to 1

3 times about 2900 +/-30

changed to 5

3 times: 2850, 2760, 2850

changed to 10

5 times: 2778, 2507, 2432, 2392, 2385

changed to 1

5 times: 3062, 3037, 3009, 3042, 3081

changed to 10

5 times: 3169, 3003, 3018, 2944, 2796

changed to 1

5 times: 2661, 3022, 2943, 3009, 3008

change to 1000

5 times: 3228, 3173, 2895, 2908, 2872

change to 1000000

5 times: 2815, 2738, 2756, 2807, 2802

change to 1

5 times: 2640, 2411, 2366, 2316, 2243

change to 10

5 times: 2215, 2128, TAP-crash*, 3043, 3147, 3048

--------deadline

10 times: 3103, 2937, 3019, 3222, 3135, 2926, 2893, 2897, 2790, 2894

------ sio

5 times: 2631, 2455, 2340, 2313, 2266

------- cfq

5 times: 2274, 2221, TAP-crash*, 3026, 2941, 3046, 3063, 3133, 3001, 3082

TAP-crash*: tapping on check free space (accidently) and canceling with hardware key crashed TAP app
[Desire Android Development] melethron:
Seems to be more like a block erase pattern from the controller than a proper comparsion of schedulers. Of its loop cache dependent. You could try "nodelalloc" as ownhere suggested.
[Desire Android Development] woti23:
nodealloc makes at least deadline 200-300 slower
[Desire Android Development] chihliouma:
Hi there, I've tried the vr cfs @875mv in http://mirror.couttstech.com/android/index.php?dir=bravo/kernel/Sense/CFS/

and it works very good but one syptom that disturbe me is when I charge DESIRE by using the USB cable, it will start charging normally (yellow color led), but when I switch to USB drive mode, it will become green color led signal and shows 100% immediately which is actually a FAKE charge becuase I unplug and plug the USB again, it will start to charge normally. I am not sure if this is my special case or it's a known bug. Thanks for any advice.
[Desire Android Development] marjanstrife:
leedroid

is leedroid 2.3c compatible with this kernel?
[Desire Android Development] coutts99:
Did you chmod 755 99complete
[Desire Android Development] melethron:
But should make the results more steady. Writes are more force to disk then because it disables the delayed allocation. Question is does it

feel

faster?
[Desire Android Development] coutts99:
Yes

10chars
[Desire Android Development] DroidBois:
Can we ruin our SD cards with any of these optimisations?
[Desire Android Development] melethron:
@ coutts99:

What is the

default

"screen off" profile? Powersave?
[Desire Android Development] beanbean50:
Since using Sibere's battery fix my battery stops charging at 4.138v but in Sibere's own words 'keeps your battery @ 4.200v' (I've lost count of how many times I've recalibrated the battery and wiped stats)

So I was wondering if anyone else has this same 'problem'?

But it's not really fair to call it a problem as according to my battery widget (see pic) I can get 4 days+ out of the old dear..
[Desire Android Development] Semmy7:
Yes i do it in update script after replace file.
[Desire Android Development] melethron:
Modern li-ion have a controller that disables charging on its own if the values are too high. Not sure if this is the case here but maybe the internal measure of the battery has 4.2 V and disables charging then. If this is the case it cant be changed in the kernel. Even if the Battery driver "guarantees" to charge to 5V it wont charge above a certain value. Maybe battery internal controller measures 4.2V and android only 4.138V but im not sure where android gets its values from. I think calibrate battery only tells Android when the charging is considered full by the battery itself an sets that value to be 100%.
[Desire Android Development] marse.online:
Is the Kernel couttstech-2.6.32.28_OC1190_BFS_VR_SLQB a good choice for Leedroid 2.3d ?
[Desire Android Development] Anakha56:
This new scheduler seems to be working like a charm :). Thanks coutts :).
[Desire Android Development] Muxeu:
Kernel

Linux version 2.6.32.28-froyo_bravoV5-couttstech.com (stevec@aoede) (gcc version 4.4.0 (GCC) ) #24 PREEMPT Sat Jan 15 09:29:52 GMT 2011

dmesg | grep scheduler
<6>[ 11.851928] io scheduler noop registered
<6>[ 11.852050] io scheduler deadline registered
<6>[ 11.852661] io scheduler cfq registered
<6>[ 11.853088] io scheduler bfq registered (default)
<6>[ 11.853210] io scheduler sio registered
<6>[ 13.540954] BFS CPU scheduler v0.363 by Con Kolivas.

Isn't VR in kernel.
[Desire Android Development] Terepin:
VR is in version from 17th January. See OP.
[Desire Android Development] Muxeu:
The version from 17th January doesn't support btrfs filesystem
[Desire Android Development] Terepin:
That's because only test version has support for additional FS.
[Desire Android Development] Terepin:
coutts, can you look into it, please?

http://gparted-forum.surf4.info/viewtopic.php?id=13428
[Desire Android Development] takabriga:
difference between two types of kernel

Hello little question from newbie, someone who can Speg is the difference 'between CFS and BFS KERNEL? THANKS:confused::confused::confused:
[Desire Android Development] Muxeu:
http://www.cs.unm.edu/~eschulte/data/bfs-v-cfs_groves-knockel-schulte.pdf
[Desire Android Development] takabriga:
thanks a lot friend.:D
[Desire Android Development] coutts99:
I can only find a read only driver?
[Desire Android Development] beanbean50:
Thanks for the explanation it all makes perfect sense now, so I guess it's my very expensive battery that's the problem? .... (made in China/13 quid/Ebay) ...

BTW it got over the 4.138v mark and went up to 4.187v and is now showing nearly 6 days usage, if only it was true...!
[Desire Android Development] melethron:
Thanks for that. Since "latency" and "interactivity" is more important than "turnaround time" on a phone it clearly shows what the best scheduler is for the desire.
[Desire Android Development] wollyka:
the question lest is between BFS and VR now? :p
[Desire Android Development] Terepin:
Correction: BFQ and VR.
[Desire Android Development] melethron:
But even with the correction it still has nothing to do with CPU scheduling ;)
[Desire Android Development] davebugyi:
Right now i am using the latest CFS version of this kernel, and have to say, it does the job!

Great work there :)
[Desire Android Development] wollyka:
oops, mys mistake :p
[Desire Android Development] Muxeu:
2 coutts99: please, add the VR IO scheduler to BFS test kernel (for btrfs, reiserfs, jfs)
[Desire Android Development] Terepin:
Yes, but since I can't check progress in this matter, I thought you can.
[Desire Android Development] melethron:
http://www.ziggy471.com/2011/01/02/overcharging-batteries/

im a bit skeptic about tickle charge now ^^
[Desire Android Development] Alex-V:
mmmhh..i think the chinese man have a cheap rebuild battery...anyway...i think with build 2.29...htc released a 99% reload kernel...?!?

I have trickle charge on all my older phones i think....on htc polaris and also on nokia n 70 etc....

i always woke up with 100% and not with 90%

with kind regards...Alex
[Desire Android Development] ahac85:
HI with the new kernel my battery shutsdown when at 13%, sometimes 5%, and ive callibrated aswell i also notice when it reaches 89% it jumps to 100% straight after using battery indicator pro the voltage shows as 4216mv.....whats going on??
[Desire Android Development] elmalote:
Coutts do you have an idea to why I get Bad Cgroup Data in my logcat when using ur BFS kernel in HD roms?

Unfortunately my phone doesn't boot up on CFS kernels..
[Desire Android Development] melethron:
Well but you still don't know how they changed the charge (for example charge to 100% ... let it drop to 99% -... charge again - siberes battfix uses "slow charge"). Also you dont know if they decreased the max voltage it is charged to.
[Desire Android Development] EddyOS:
Coutts, just dropped you a PM regarding something. If you can answer I'd appreciate it but if not I'll get it up in this thread as well...
[Desire Android Development] woti23:
well, ziggy may or may not have a point on this, but the sources he cites are crap.

pc-world, endaget, tech-ex ... the experts, omg

did you read those articles?

tech-ex - the only thing thats seems clear is that it happend in china

" It's also unclear if the battery was truly at fault, or if the cell phone exploded, but realistically --- come on, it was China."

endaget:

"The make and model of the phone and battery have yet to be identified, but seeing how this is the seventh high-profile case of an exploding phone in China in the last six years."

so 1 from how many sold phones per year?

pc-world - conclusio:

"With close to 300 million cell phones sold in the world last quarter, such battery explosions are considered extremely rare."

- this is nokia failure battery in australia, which had a short circuit
[Desire Android Development] elmalote:
But what about when you charge the phone while its off? Then the kernel has nothing to decide? So that means that the built in protection of the battery is doing all the overcharge protection. Maybe sibere's hack does the same.

Sent from my HTC Desire
[Desire Android Development] Anakha56:
@ melethron I always enjoy reading your posts :). Thank you :). Do you know if cm has fixed the car dock problem with thier battery charging hack? The reason why this kernel went back to sibere's fix (only one I know of) is because with the cm fix whenever the phone was put into a car dock it would reboot. If the problem has been identified and fixed I am pretty sure coutts would compile it back in? :)

/I know I am asking a lot from coutts by saying that... :)
[Desire Android Development] elmalote:
Thanks for the explanation melethron :)
[Desire Android Development] beanbean50:
has coutts left the building...?
[Desire Android Development] coutts99:
Nope I'm here, just not much more I can do with this kernel really. Anyway I've moved to AOSP so I can concentrate more on 2.6.37 :)

I'd consider this kernel pretty much unmaintained now.
[Desire Android Development] Musko:
My Desire in the warranty servise with camera.

Then I want use coutts kernel with LeeDroid 2.3 (on original LeeDroid I have problem with car charger - phone restart after connect usb car charger).

Please can anybody advise which kernel I use?

BFS or CFS?

I was read read read more about this but ... I dont know.

Thak you.
[Desire Android Development] Nitin985:
Bfs
[Desire Android Development] Schwarz33:
coutts99, I'm trying to use 2.6.32.28_OC1190_BFS_VR_SLQB kernel with rooted HTC stock rom 2.29.405.5. I prefer not use setcpu, but w/o it i only have 960 Mhz maximum freq with your kernel. Why not 998?
[Desire Android Development] HzeMaffe:
Could ya put a bit more info bout the choice? I too am interested in the differences of CFS/BFS in practise.
[Desire Android Development] Alex-V:
:) http://www.cs.unm.edu/~eschulte/data/bfs-v-cfs_groves-knockel-schulte.pdf

:)

more info: svs ---havs

"SVS (static voltage scaling) is the standard to set the Mhz and HAVS is a method from intersectraven which mixes SVS and AVS (AVS uses the temperature of the cpu to set the clock). HAVS uses slight less battery." _but more risk of reboots

with kind regards...Alex
[Desire Android Development] hispeedworm:
hey can you comment on regular vs 925 vs 875mv kernels.... pros and cons?
[Desire Android Development] scorpion50:
Can someone tell me the difference between those 3 zip files? what does havs, bfs, vr, slqb mean?
[Desire Android Development] Zordracc:
My reactions from using "couttstech-2.6.32.28_OC1190_CFS_VR" can only be like this:

Its the best version of kernel i`ve ever used! Its just soo smoooth in everything and feels so stable.

One difference ive noticed from other kernels is that after a reboot it needs a little more time to "get in the beat",

but after that... Wow! What a feeling. Stable is the word im thinking of here mostly.

Im running reflexTsense 1.6.1 DHD rom with moderate use of the "native" appkiller app. I have downclocked

my proc to 750mhz and it has NEVER felt this smooth, even at 1 ghz with another kernel.

I read the document about CFS vs BFS and it just felt right to use CFS, and im thinking about one

main difference between them and that is CFS prioritize true "democracy" :D LOL . Seriously it just looked more multitasking

comparing to the BFS that prioritize processes tougher and lets less important things to skip cycles..

I didnt like that thinking and therefore i choose CFS. Its just my personal choice.. this time.

And i read somewhere that HAVS had some problems in "calibrating" clockcycles for the processor

(really sorry for the noobtalk, im just not comfortable with the right vocabulary and cant really use it correctly :o ) and that

it calibrated it all the time.

Im not sure what this all means, but what i do know is that its STABLE in my current combination!

If your wondering how i set my phone up, i first flashed my rom, then without rebooting

i flashed the kernel. I felt it really needed time to set things right from the beginning, but it was soo worth it!

Thank you coutts for this kernel!
[Desire Android Development] melethron:
LOL. Democracy... that would be a strange democracy... its like you give foodstamps to the rich because its "fair" that everyone gets the same... The same applies to a fair treating of all processes.... it is simply not necessary that the background sync gets the same treatment as the app you use.... that's why HTC messes with cgroups to make cfs more interactive which is just ... fail...
[Desire Android Development] Zordracc:
Sorry Melethron, but this configuration is just the most stable one up to date :o. And i did try the BFS with HAVS before this one.

It just cant match up in my Desire.

I didn´t say it would be easy to hear, its just my feeling when handling my phone.

I´d say, give it a shot, it could definitively be a winner!
[Desire Android Development] Diewi:
Just found this:

http://www.gossamer-threads.com/lists/linux/kernel/1060090

Seems like a mixture of I/O schedulers (deadline for write/noop for read) increases the performance on a SSD. This could be interesting for us. I explicitly don't say it will help, as SSD got way better and more complex logic units as our phones, but it would be worth a try because both have a NAND Flash memory. Unfortunately I don't have the time for editing/testing, but at least I wanted to leave this as note. Maybe somebody is interested in this.
[Desire Android Development] hojnikb:
I dont know if its just this kernel faults im using or something else since i get avfully slow speeds on my sd card when connected to pc (4MB read / 2MB write)

Just like there wouldnt be any sdfix at all.

Although when i tested with sd card speed on phone it showed real speed (11mb r/4mb w).

Any ideas what am i doing wrong ?

Anyway im using this kernel and leedroid rom and a Kingston 8GB class 4 microsd card.
[Desire Android Development] th3:
coutts99:

This is really odd. I used your AOSP kernels and _thalamus' with Gingerbread ROMs, and everything below 975mV crashes/bootloops. Consistently. Kmsg shows it to be CPU related.

Now, I used your 2.6.32.28_OC1190_HAVS@925mV kernel with Desire HD ROMs and it runs perfectly fine... ? 3 days no crash/bootloop in any scenario. So what could be the problem with the AOSP version?
[Desire Android Development] Murd0ck:
could be the kernel versions.. this runs 2.6.32.28 while the ASOP runs 2.6.37 or .35