yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] Fightspit:
Richard,

Based on your github, I successfully make my phone working with a "very" low voltage and I give you the acpu table I am currently using if people would like to test it:

struct clkctl_acpu_speed acpu_freq_tbl[] = {
{ 19200, CCTL(CLK_TCXO, 1),	SRC_RAW, 0, 0, 875, 14000 },
{ 128000, CCTL(CLK_TCXO, 1),	SRC_AXI, 0, 0, 875, 14000 },
{ 245000, CCTL(CLK_MODEM_PLL, 1),	SRC_RAW, 0, 0, 900, 29000 },
/* Work arround for acpu resume hung, GPLL is turn off by arm9 */
/*{ 256000, CCTL(CLK_GLOBAL_PLL, 3),	SRC_RAW, 0, 0, 1050, 29000 },*/
{ 384000, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x0A, 0, 925, 58000 },
{ 422400, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x0B, 0, 950, 117000 },
{ 460800, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x0C, 0, 950, 117000 },
{ 499200, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x0D, 0, 975, 117000 },
{ 537600, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x0E, 0, 975, 117000 },
{ 576000, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x0F, 0, 1000, 117000 },
{ 614400, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x10, 0, 1025, 117000 },
{ 652800, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x11, 0, 1050, 117000 },
{ 691200, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x12, 0, 1075, 117000 },
{ 729600, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x13, 0, 1100, 117000 },
{ 768000, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x14, 0, 1125, 128000 },
{ 806400, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x15, 0, 1150, 128000 },
{ 844800, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x16, 0, 1175, 128000 },
{ 883200, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x17, 0, 1175, 128000 },
{ 921600, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x18, 0, 1200, 128000 },
{ 960000, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x19, 0, 1225, 128000 },
{ 998400, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x1A, 0, 1250, 128000 },
{ 1036800, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x1B, 0, 1275, 128000 },
{ 1075200, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x1C, 0, 1300, 128000 },
{ 1113600, CCTL(CLK_TCXO, 1),	SRC_SCPLL, 0x1D, 0, 1300, 128000 },
{ 0 },
};

Also, don't forget to change the minimum voltage in board-bravo.c at line 663

static struct regulator_init_data tps65023_data[5] = {
{
.constraints = {
.name = "dcdc1", /* VREG_MSMC2_1V29 */
[COLOR="Red"].min_uV = 875000,[/COLOR]
.max_uV = 1300000,
.valid_ops_mask = REGULATOR_CHANGE_VOLTAGE,
},
.consumer_supplies = tps65023_dcdc1_supplies,
.num_consumer_supplies = ARRAY_SIZE(tps65023_dcdc1_supplies),
},

I can say that my phone run Quadrant or Angry Birds without FC or freeze :)

EDIT: I didn't test the HAVS but I get 1462 @ 1113600 KHz in Quadrant.
[Desire Android Development] richardtrip:
This doesn't work for all devices. If i make changes i lower the havs kernel (other table).
[Desire Android Development] heisven:
Nice Kernel. I am currently using modaco r9,

@ 1113Mhz Smartass: Quadrant Score 1540-1550.

Fine!
[Desire Android Development] usb2007:
having issues with v4, v5 and v5b..all of these issues happen randomly

1. market access stuck and unable to change SIM values

2. dialer would stop dialing and just do nothing when i try to dial a number (sometimes its just stuck and sometimes resetting market access makes it work..random behavior)

3. widgets for wifi/bt/gps/silent/etc wont work or work with a huge lag

4. j android hacker doesnt work anymore at all

5. sometimes i see roaming R with the signal

v5b

1. all of the above issues..just more often

2. permenantly stuck at roaming R all the time

reverted back to v4 and everything is back to normal..no roaming R..no random dialer and market issues and even j android hacker works now

im using IEFTM 's Official 2.2 (HTC 2.10): busybox, A2SD+, TUN, EXT4, Undervolt, SYSRW ROM

http://xdaforums.com/showthread.php?t=741663
[Desire Android Development] richardtrip:
Update: HAVS kernels

V5c HAVS kernels:

HAVS 1113Mhz@925mV minimum

HAVS 1113Mhz@875mV minimum
[Desire Android Development] Minux31:
Thx Richard :D

I'll test HAVS 1113Mhz@875mV minimum right now ;)
[Desire Android Development] sibere:
I've compiled my own kernel using Richard's git and here is my table:

struct clkctl_acpu_speed acpu_freq_tbl[] = {
{ 19200, CCTL(CLK_TCXO, 1), SRC_RAW, 0, 0, 900, 14000 },
{ 128000, CCTL(CLK_TCXO, 1), SRC_AXI, 0, 0, 900, 14000 },
{ 245000, CCTL(CLK_MODEM_PLL, 1), SRC_RAW, 0, 0, 925, 29000 },
/* Work arround for acpu resume hung, GPLL is turn off by arm9 */
/*{ 256000, CCTL(CLK_GLOBAL_PLL, 3), SRC_RAW, 0, 0, 1050, 29000 },*/
{ 384000, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x0A, 0, 950, 58000 },
{ 422400, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x0B, 0, 950, 117000 },
{ 460800, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x0C, 0, 975, 117000 },
{ 499200, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x0D, 0, 975, 117000 },
{ 537600, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x0E, 0, 1000, 117000 },
{ 576000, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x0F, 0, 1000, 117000 },
{ 614400, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x10, 0, 1025, 117000 },
{ 652800, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x11, 0, 1050, 117000 },
{ 691200, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x12, 0, 1050, 117000 },
{ 729600, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x13, 0, 1100, 117000 },
{ 768000, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x14, 0, 1125, 128000 },
{ 806400, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x15, 0, 1125, 128000 },
{ 844800, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x16, 0, 1150, 128000 },
{ 883200, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x17, 0, 1175, 128000 },
{ 921600, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x18, 0, 1175, 128000 },
{ 960000, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x19, 0, 1200, 128000 },
{ 998400, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x1A, 0, 1200, 128000 },
#ifdef USE_OVERCLOCKING
{ 1036800, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x1B, 0, 1250, 128000 },
{ 1075200, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x1C, 0, 1275, 128000 },
{ 1113600, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x1D, 0, 1300, 128000 },
#endif
#ifdef USE_EXTREMEOVERCLOCKING
{ 1152000, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x1E, 0, 1300, 128000 },
{ 1190400, CCTL(CLK_TCXO, 1), SRC_SCPLL, 0x1F, 0, 1300, 128000 },

My desire is stable for 254mhz@925 but not 900.

I would like to try 128mhz@900 but unfortunately - and I don't know why - I can't get 128Mhz with my kernel even though I can OC up to 1113600 with SetCPU.

If I reflash V5a, I can get 128Mhz again.

Am I missing an option in the kernel setup or a hack in the sources?
[Desire Android Development] martino2k6:
Thanks a lot.

I just tried the 875mV one, and I noticed that the 128MHz minimum frequency disappeared, it's 245MHz now...
[Desire Android Development] EViollet:
Can you give us a list of the voltages for each frequency for these kernels please?

Regards,
[Desire Android Development] System of a pWne!^:
I need to know a little bit more right now:

If I understand HAVS (Hybrid Adaptive Voltage Scaling) correctly, it tries to find the minimum possible voltage at a given frequency where the CPU still runs stable, so power consumption can be even lower. Is that correct?

One more thing: Is the smartass governor included in V5c also? And has anyone a description about how it works? Is it even better than the interactive?

And does the V5 wifi-module work with V5c (should)?

Thanks in advance
[Desire Android Development] Minux31:
Tried HAVS 1113Mhz@875mV minimum, everything is ok :

Quadrant smartass@998Mhz : 1466

Quadrant smartass@1113Mhz : 1588

Great job ! :D Many Thx Richard

But why 128Mhz frequency dissapeared ?
[Desire Android Development] sibere:
Bootloop @875mV

OK @925mV

(128Mhz disappeared too)
[Desire Android Development] Oijkn:
For me it's the same with this kernel and minimum CPU is 245 MHz. Good work richardtrip ;)
[Desire Android Development] martino2k6:
No bootloops for me so far at 875mV...
[Desire Android Development] Jagdish84:
my handset boots just fine with 875mV althou freezes up a min or two afterwards

just tried 925mV, boots up just fine but freezes up...HAVS test kernel works just fine thou :\

im applyin both Dalvik and cache wipes before flashing the kernel, m i missing something here?!

Edit:

i mightve figured out what was causing my handset to freeze, i nand back to v5a (1190 MHZ) and flashed the 875mV HAVS kernel over it successfully, ppl who are using the HAVS test kernel and trying to flash the new version of HAVS kernel (either 925mV or 875mV i tried em both) might want to first flash another kernel(like v5a) and refrain from flashing it over the HAVS test kernel, as it doesnt sit well with the handset(well my handset that is), i am now running Richards 875mV HAVS kernel with no probs what's or ever, hope it helps you guys...
[Desire Android Development] ssauger:
got the same result, first install th 875mV kernel i got freezes, nand and a older kernel then the 875mV and now it seems to be stable, dont know why.
[Desire Android Development] infoschumi:
It works great.I installed 875mV version over v5b HAVS test kernel without any problem.

1530 Quadrant 1113 smartass.
[Desire Android Development] Minux31:
I flashed v5c directly over v5b HAVS test kernel, and it's very stable, don't know why you had problems ...
[Desire Android Development] sibere:
Gonna try that then :)
[Desire Android Development] richardtrip:
All is on github. Cant give voltages (only start voltages at each frequency) because havs lowers the voltage automatic.
[Desire Android Development] EViollet:
I didn't know that... Very interesting. I'll have a look at how HAVS works. I'm very intrigued now... :)

I thought that there were just fixed voltages for each frequency and that was it. I'm intrigued as to how HAVS determines when to lower the voltage and by how much without being unstable.

Googling for HAVS then... :)
[Desire Android Development] sibere:
There is a table in avs.c.

It looks like a list of min/max values for the AVS driver.

struct clkctl_acpu_speed acpu_vdd_tbl[] = {
{ 19200, 950, 950 },
{ 128000, 950, 950 },
{ 245000, 950, 975 },
{ 256000, 950, 975 },
{ 384000, 950, 1000 },
{ 422400, 950, 1000 },
{ 460800, 975, 1025 },
{ 499200, 1000, 1050 },
{ 537600, 1000, 1050 },
{ 576000, 1025, 1075 },
{ 614400, 1050, 1100 },
{ 652800, 1075, 1125 },
{ 691200, 1100, 1150 },
{ 729600, 1125, 1175 },
{ 768000, 1150, 1200 },
{ 806400, 1175, 1225 },
{ 844800, 1200, 1250 },
{ 883200, 1200, 1250 },
{ 921600, 1225, 1275 },
{ 960000, 1225, 1275 },
{ 998400, 1225, 1275 },
#ifdef USE_OVERCLOCKING
{ 1036800, 1225, 1275 },
{ 1075200, 1225, 1275 },
{ 1113600, 1250, 1300 },
#endif
#ifdef USE_EXTREMEOVERCLOCKING
{ 1152000, 1250, 1300 },
{ 1190400, 1250, 1300 },
#endif
[Desire Android Development] EViollet:
Thank you very much.

I'll look into all this tonight...
[Desire Android Development] bubu.:
Any tests on how much better the new HAVS kernels perform regarding battery lifetime?

am I assuming right, that theres no difference in performance if I still set smartass governor and 1113mhz as max value in setcpu compared to smartass with 1113mhz in setcpu in v5 kernel?
[Desire Android Development] MrLuje:
Same here, everything runs fine :)
[Desire Android Development] richardtrip:
Changes a minor thing compared to this table. The min value is now at VOLTAGE_MIN which is defined in the avs.h (875mV or 925mV).
[Desire Android Development] sibere:
Yep just had a look at this :)

How can we get 128Mhz back on top of that?

Thanks for the good job richardtrip!
[Desire Android Development] ssauger:
For me 128 Mhz was laggy from wake up, no problem with 245 mhz. 245 Mhz on lower voltage may be better for battery life than the laggy 128
[Desire Android Development] bubu.:
Have just flashed the one with the lower voltage, got a syshang at the point "file system writes" in quadrant. removed the battery, rebooted and the next two benches in quadrant worked well so far... trying it out further
[Desire Android Development] abz54:
Hi, havs kernal at 875mV working great. Is there gonna be gpu+ in this kernal in the future as is in the original auraxtsense 7.9 kernal?
[Desire Android Development] sibere:
Talking about battery life, I actually think you're right.

I'm not sure that 128MHz at a slightly lower voltage (eg -25mv) would make a great difference on battery life on standby. The big thing is when the CPU is running at higher frequencies.

With 1200mV for 998MHz it's a great improvement compared to the stock 1300mV !

The best option would be to implement an "on the fly" frequency change option so everyone could try his own voltages. Every CPU differ from the other you know ;)

There's a couple of drivers where the user can adjust manually CPU voltages.

take a look at http://xdaforums.com/showthread.php?t=821372 or http://xdaforums.com/showthread.php?t=775997
[Desire Android Development] ssauger:
i read the post about the on the fly change, but dont know how to imlpement this
[Desire Android Development] sibere:
You're not but i'm sure that Richard is! ;)
[Desire Android Development] bubu.:
Ive got the feeling that the combination of low voltage and IO (read/write) isn't really good when starting a IO-bench so far. quadrant bench always is a little bit laggy when reaching the IO-benches and sd card speed is also slow at the beginning, than gaining speed and when running it twice, the second run is okay.
[Desire Android Development] MrLuje:
Hmm, in fact, I have a little issue with 5c@875 but I'm not sure if it's coming from the kernel.

Every 5 or 10 min, with the phone plugged in charge mode on my computer, I got the weird windows sound telling that a USB device has been plugged/unplugged (but there is nothing in device manager).

Since I didn't charge my phone for a few days, I'm not sure if it is coming from the v5c but I didn't have this behavior on v4
[Desire Android Development] martino2k6:
Possibly not enough power for the USB port. I had something similar happen on my old Android phone.
[Desire Android Development] sibere:
Well ATM I stick with 925mV kernel.

My CPU is getting unhappy when it's fed with less than 900mV@245Mhz :S
[Desire Android Development] Mekrel:
The 875mhz is too low for me too, which I found strange as usually I can undervolt to levels others find too low.

It seemed stable at first, but had some reboots when playing Reckless Racing :)

Edited the kernel, taken out the overclock and changed some base voltages in the CPU table and made smartass default.

Cheers richard :)
[Desire Android Development] Oijkn:
Just a feedback at the begining my device was unstable when i flashed it with the kernel V5c @875 but what i have do is flash with the V3 kernel and then with the V5c @875 and for the moment my Desire is well. Try this method and tell me if that good for you or not.
[Desire Android Development] ssauger:
the 875mV kernel freezes my phone after a while. 925mV seems stable over the night and runs fine now. maybe we can try 900mV as lowest?
[Desire Android Development] Jagdish84:
I got back to V5a, seems that 875mV freezes my handset after a restart, and feels quite unstable, i tried flashing the 925mV over it but it keeps freezing, guess i should flash a non HAVS kernel first, i might try that later...
[Desire Android Development] Oijkn:
Yes try to flash your desire with V5 or V3 for example and then flash it with V5c @875. For me that method work well ;)
[Desire Android Development] sibere:
I tried to flash back to V5a and V5c@875 but my phone is still very unstable.

900mV could be a good compromise.

Keep in mind that 900Mv is much lower than the default voltage with HTC kernel !

(Default kernel is 1050mV@245MHz and 1300mV@998.4MHz)
[Desire Android Development] Mekrel:
There's no such thing as a "flash an older kernel before the new one" fix, if your device isn't stable with the 875mhz minimum voltage then it's not stable.

For what it's worth, my phone could run Quadrant fine @875mhz but couldn't last any longer than 15 minutes when playing Reckless Racing.
[Desire Android Development] richardtrip:
V5d HAVS kernels:

Changed the avs table to scale less on the higher frequencies. Could be more stable if you have problems on the V5c havs kernels.

http://xda.richardtrip.org/kernels/Kernel_Froyo_cfq_V5d_havs@875mV.zip

http://xda.richardtrip.org/kernels/Kernel_Froyo_cfq_V5d_havs@925mV.zip
[Desire Android Development] Minux31:
Yeah ! Great work Richard, Thx :D
[Desire Android Development] hamdir:
Anyone knows what makes games run at much higher FPS in CM 6.1? It's driving me nuts, can't we add such improvements to sense roms
[Desire Android Development] tomurbanowicz:
The new kernels are for best performance or best battery life?

What is diference in volts and frequances between V3 and V5?

And what does it meam: fix slow SD card? I've got SC class 4 - the fix is for me?
[Desire Android Development] sibere:
Just had a look at the new avs tables and I stick with V5a@925mv mainly because the voltage is 1200mV@998.4Mhz whereas 1225/1275 with AVS enabled.

My phone is hyper stable with 1200mV and I must save a bit of juice compared to 1225/1275 ;)
[Desire Android Development] rum0s:
Change governor without SetCPU

Hi there,

I just flashed V5c for changing my interactive governor to smartass. Unfortunatelly there is always "interactive" set by default. I checked that by starting SetCPU.

Is there a way to change the governor by a shell command?

I found out, using "adb shell s.setgov <governor>" didn't work.

Thanks
[Desire Android Development] Diamondback:
Just had two freezes using LeeDroid 2.2e: one with 875mV and one with 925mV. Both version 5c.

Now trying version 5d.

Can someone tell me if there is a real advantage of (H)AVS comapred to SVS?
[Desire Android Development] snq-:
echo '<governor_name>' > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

list of available governors:

cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
[Desire Android Development] ssauger:
Is this true, higher voltage on 998 Mhz with v5d? The new 875mV 5d works fine now for me. I think probem with v5c was on the lower frequenes.

Great job richard, thanks.
[Desire Android Development] rum0s:
Governor Change

@SNQ

Thank you so much :-) That worked!
[Desire Android Development] tomurbanowicz:
Do You explain me my post: http://xdaforums.com/showpost.php?p=8927744&postcount=655 ? :)
[Desire Android Development] sibere:
Yes it is true! (why would I lie ;) ? )

With V5a (not v5c !) and SVS, I have 925mV@245 and 1200mV@998

according to the AVS table in the github, the values for 998 are 1225/1275:

{ 806400, 1175, 1225 },
{ 844800, 1200, 1250 },
{ 883200, 1200, 1250 },
{ 921600, 1225, 1275 },
{ 960000, 1225, 1275 },
{ 998400, 1225, 1275 },
[Desire Android Development] tomurbanowicz:
I checked kernel V3 and V5 and Quadrant. After few test (average):

- V3: 1410

- V5: 1300
[Desire Android Development] EViollet:
With V5d@850mV I get 1560 on Quadrant.

I think it's the fastest I've ever had actually...
[Desire Android Development] tomurbanowicz:
OK, but how about battery life and stability?
[Desire Android Development] EViollet:
Testing it right now. I flashed the kernel 4 or 5 hours ago, and stability when screen is off seems fine.

My kids have been playing games with my phone for almost an hour now and everything seems stable as well. Haven't heard them yell that my phone crashed yet... :D

As for battery life, I've been logging since I installed the kernel with CurrentWidget, and so far it seems very good. I think it could be better if it had 128Mhz because it seems to be the same as the Leedroid kernel @128Mhz having higher voltages.

When the screen is on, it looks as if the battery usage is lower than the standard Leedroid kernel. I get lower averages... but time will tell...

All in all it seems like a good and stable kernel. Not much to complain about, except that I think it would be perfect if 128Mhz could come back! ;)
[Desire Android Development] sibere:
Weird... My average with V5a @1130MHz is about 1550. Are you running those tests @ 998MHz ?
[Desire Android Development] ssauger:
same for me with the v5d @875mV
[Desire Android Development] Diamondback:
Now running V5d 875mV without issues and an average Quadrant of 1550 with LeeDroid 2.2e at 1113Mhz.

Thanks! =)
[Desire Android Development] EViollet:
Had 2 reboots while the phone was idle with 875.

Trying 925...
[Desire Android Development] dongerado:
For me no problems with the 5c@875 kernel, working since about 11 hours...

Thank you very much, richard!
[Desire Android Development] mendozinas:
Is V5d with audiomod? If yes - is there a way to remove/disable this mod manually before flashing?

Sent from my pocket using pen
[Desire Android Development] infoschumi:
It has audiomod.I would also like to know how to remove it.My speaker won't have a long life with it.
[Desire Android Development] crawlingroof:
richardtrip, could you pleeeease post noaudiomod versions to.

With amod, RockPlayer doesn't play some video files. :'(

Or could you be so kind to tell how to rid of it.
[Desire Android Development] bigmouth66:
Tried Froyo Kernel V5d_HAVS@875mV min for a few hours, looked very good at first sight, but after a few hours I had a reboot. Now trying Froyo Kernel V5d_HAVS@925mV min
[Desire Android Development] bluelavender:
I flashed 5d 875mhz this morning... so far very stable in my phone... let's hope it stays so :-) Thanks Richard
[Desire Android Development] hamdir:
Richard can you please help in this, regarding GPU+ improvement

i've done lots of tests, at stock 998mhz ondemand it's giving an impressive boost to the GPU performance, neocore 31.9fps, angry brids 60fps can you please add it to your kernel

i've opened a thread about this http://xdaforums.com/showthread.php?t=825304

snq- added this to my thread

diff -urN bravo-2.6.32-gd96f2c0.orightc/drivers/video/msm/gpu/kgsl/kgsl.c bravo-2.6.32-gd96f2c0.snq/drivers/video/msm/gpu/kgsl/kgsl.c
--- bravo-2.6.32-gd96f2c0.orightc/drivers/video/msm/gpu/kgsl/kgsl.c	2010-09-28 14:03:29.000000000 +0200
+++ bravo-2.6.32-gd96f2c0.snq/drivers/video/msm/gpu/kgsl/kgsl.c	2010-11-01 14:22:23.000000000 +0100
@@ -713,7 +713,7 @@
* overwrite this memory */
dmac_flush_range(vmalloc_area, vmalloc_area + len);
KGSL_MEM_INFO("Caching for memory allocation turned off\n");
-	vma->vm_page_prot = pgprot_noncached(vma->vm_page_prot);
+	vma->vm_page_prot = pgprot_writecombine(vma->vm_page_prot);
} else {
KGSL_MEM_INFO("Caching for memory allocation turned on\n");
}
diff -urN bravo-2.6.32-gd96f2c0.orightc/drivers/video/msm/gpu/kgsl/kgsl_drawctxt.c bravo-2.6.32-gd96f2c0.snq/drivers/video/msm/gpu/kgsl/kgsl_drawctxt.c
--- bravo-2.6.32-gd96f2c0.orightc/drivers/video/msm/gpu/kgsl/kgsl_drawctxt.c	2010-09-28 14:03:29.000000000 +0200
+++ bravo-2.6.32-gd96f2c0.snq/drivers/video/msm/gpu/kgsl/kgsl_drawctxt.c	2010-11-01 14:22:29.000000000 +0100
@@ -28,7 +28,6 @@
#include "kgsl_pm4types.h"
#include "kgsl_cmdstream.h"

-#define DISABLE_SHADOW_WRITES
/*
*
* Memory Map for Register, Constant & Instruction Shadow, and Command Buffers
[Desire Android Development] snq-:
hamdir: just tried it, i got 32.0fps in neocore (running this one)
[Desire Android Development] hamdir:
thanks i'll try it now and see if it gives similar results to CM6.1 and AuraxTsense

too bad the mod moved my thread.... :mad:

[EDIT] I just flashed it on teppic stock froyo rom, It Works!!!! 31.5FPS on neocore, angry birds 60fps fluid, no more judder, i will stress test it and look for any potential bugs

can you try it with richards v5 kernel?
[Desire Android Development] mr.r9:
I am also very interested to have GPU+ with version 5c of the Kernel. The results will be fantastic.
[Desire Android Development] hamdir:
same results as CM6.1 and AuraxTsense 7.9, angry birds liquid smooth, asphalt 5 much more stable

31.3/31.4FPS neocore stock 998mhz on demand, richard can you please add this to your V5 kernel so we can try it
[Desire Android Development] vnvman:
Same here :)

Tho i've noticed running 2d+3d sections only on quadrant advance with both roms, CM6 is still getting better scores...not a big deal anyway: like 139 vs 184, and it seems that CM is doing better mostly the 2d part of the bench (tho idk about the "stock" CM, cause on mine i'm running the vorkKernel 7.1).

This said i would never have expected such a great improvement on a sense rom, thanks for raising the question man, somebody had to do that sooner or later.

Thanks to you and to snq-'s great job now gaming performances aren't for aosp/cm roms only ;)
[Desire Android Development] hamdir:
vnwman, i'm will bench using quadrant and post the results
[Desire Android Development] richardtrip:
No problem to do that later tonight.
[Desire Android Development] vnvman:
Great :D

Thanks for your hard work.