yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] EtherealRemnant:
did anyone notice the fps test in the engineering Rom? It reports 63 to 65 when it is run. I wonder of HTC temporarily lifts the frame rate cap using this app? It may be worth looking into...
[EVO 4G Android Development] halorin:
This. Is. Awesome!!!!
[EVO 4G Android Development] kpkimmel:
What is awesome
[EVO 4G Android Development] halorin:
Right now we can only have two touch inputs at a time. What I'm gathering from his post is that he got 3 to work.
[EVO 4G Android Development] Cicatrize:
I'm confused. So is the Epson using mddi_client_epson.c as the driver, or something generic due to the 0 product code? If so, any reason you left the mdelay(3) out of the vsync interrupt? Perhaps that may be a problem contributing to the vsync issues on the "hacked" epsons?
[EVO 4G Android Development] ffolkes:
thanks maejrep! :D

it seems you can set it as high as you want. i'm so glad this issue has been resolved - i was previously annoyed that htc used a high-end touch controller capable of unlimited points, then went and capped it.

i went up to 5 before i thought "what's the point?" ;) but this does raise the possibility of some interesting 3+ finger gestures someday. for example, three point rotation would be cool, especially in things like google earth where there's no easy way to rotate a sphere relative to a definable axis.

if you do this, only dotty and Input Benchmark see >2 points. other apps, like Multitouch Visualizer just get confused and crash.
[EVO 4G Android Development] ffolkes:
this is just a random thought, it's stupid to even mention, but what the heck.

all this talk of multiple frame buffers...what if htc was alternating sending frames between the lcd and hdmi? just a thought.
[EVO 4G Android Development] Cicatrize:
I thought about this too, but they're on different interfaces, so I'm not sure that would have any effect.
[EVO 4G Android Development] Cicatrize:
Toast/maejrep/anyone else,

Is there an IRC channel or something that development for this platform is going on? I think it'd be nice if we could all chat real time instead of wasting time doing things other devs have already tried because we didn't know.
[EVO 4G Android Development] joeykrim:
+1

been wondering this same thing myself. if an irc channel already exists, it would be great to join. if there isnt one already, im sure we could start one.
[EVO 4G Android Development] halfline:
someone posted logs to #htc-linux on freenode a while back.
[EVO 4G Android Development] halorin:
How about Google Wave? I think that would work well, too.
[EVO 4G Android Development] Jus10o:
The mms issue i think is something in darchdroids source. The same kernel is used on Fresh Toast and absolutely everything works, even mms download.

Someone with an Evo, use this kernel and flash it to your phone. Obviously you would have to be rooted Toasts method. Double check to see if everything works. If it does then everyone can get OC'ing to work.

I bet toast would be working on this right now, but im sure he is trying to figure out the locked NAND before he starts developing for the Evo.
[EVO 4G Android Development] Hero_Over:
quote from toast on last page:

"the kernel source is Incredible source, with Supersonic board files. its the real deal yes. it will boot and everything is known to work. this is tested by majrep. also one thing isnt in the source but can be worked around. the wimax module seems to be missing from the source. we dont know if htc will be required to release this module at all. but the work around is the local veersion. as long as u keep ur local version the same as the stock local, u will be able to use the modules from the released build. that said lets hope this module wont be closed source proprietary" So we know it works now we just need to start poppin off/testing kernels
[EVO 4G Android Development] catpunt:
has anyone installed this kernel and checked:

1. touch input lag

2. 30fps cap

3. g-sensor lag

i'd be curious if there is any improvement. didn't see mention of it in this thread
[EVO 4G Android Development] chuckhriczko:
So I just tried to compile the kernel. Worked fine. However when I packaged it up as an update and flashed it the phone did not boot even after I waited double the normal time. I made no modifications to the source. Just checked out, compiled and tested. Any ideas?
[EVO 4G Android Development] Hero_Over:
same thing happened to me. wont boot.

can someone please give me an mkbootimg file for 64bit linux???

I cant find one online and in order to compile all the tools i must use java 5 and its not working. please if you can upload a mkbootimg for 64bit linux
[EVO 4G Android Development] Hero_Over:
i just checked the kernel from the froyo rom that toast said he compiled and it has the exact same byte size as the stock kernel.

maybe this source cant compile a kernel for our devices?
[EVO 4G Android Development] chuckhriczko:
From what I understood the FroYo kernel is Toast's source. Toast, when you get on we need direction bro.
[EVO 4G Android Development] Hero_Over:
unpack the image and compare the kernel with the stock kernel. they are the same file. All I know is ive been working on this for the past 3 days to find out its probably not gunna work.
[EVO 4G Android Development] ffolkes:
i seem to be the only one who can't get this to compile.. it fails with:

make[3]: *** No rule to make target `net/ipv4/netfilter/ipt_ecn.o', needed by `net/ipv4/netfilter/built-in.o'. Stop.

what am i doing wrong?

edit:

it appears this is an issue with my filesystem being case insensitive. i'm using os x, so i could probably make an image using a case-sensitive format and compile on that, but since toast just confirmed this kernel doesn't work on non i/o evo's, i'll do it later.
[EVO 4G Android Development] toastcfh:
Yeah it seems that when me and maejrep were testing we only had his I/O evo and it booted with no issues. Once I got my evo and tried loading the boot.imgs I had made for maejrep to test on his evo, I found they wouldn't boot on my evo. But without a doubt they would on his. Because I had to compile the kernel special for froyo a2sd to work and I did that for him.

Also an easy way to tell if its a kernel I compiled, u can look in software info in settings and the kernel should say toastcfh@OlDsChOoL in the kernel versuon. If it says htc@blah then I forgot to add the kernel I compiled to the boot.img. in any event it seems there is an issue and I suspect its small. I managed to reverse .29 source to the heroC I imagine with a little time I can find the issue here. That ill put as priority #1 since full root us solved.
[EVO 4G Android Development] npace:
Nice

I've been banging my head all day trying to get this thing to run and make some modification to drivers/video/msm/mddi_client_novb9f6_5582.c

Trying to see if I can disable "vsync" or if that even remotely makes sense and if it can fix the "30 fps" issue.

Also wanted to change clk_rate in arch/arm/mach-msm/board-supersonic-panel.c to see what happens...

I'm clueless why it wouldnt boot.

Is there a way to see dmesg while this thing is trying to boot or any kind of output that would help?
[EVO 4G Android Development] maejrep:
FYI

It has recently been discovered that newer (as of June 4 launch) phones are shipping with hardware revision 3, and the I/O phones are hardware revision 2! The code we have here only knows about revision 2, and does not have the code necessary for hardware revision 3. So if you try to compile this and boot it on your post-launch device, it probably will not work.

I've been working on reverse engineering the system_rev 3 changes from the kernel binaries that shipped on the phones, and have found several differences so far; however, it still doesn't boot on rev 3 devices. So far the bulk of the differences appear to be with the LCD panel: rev 2 devices use a novatec panel, but rev 3 devices use an epson panel. The differences here are seen in the panel_type ATAG: 0 means epson, 1 means novatec. You can see both the system revision and the panel type in the first several lines of the kmsg (dmesg) output:

revision 3:

<7>[ 0.000000] tag_panel_parsing: panel type = 0
...
<4>[ 0.253173] supersonic_init() revision=3
...
<6>[ 3.666107] mddi: registering panel mddi_c_4ca3_0000
<6>[ 3.666137] mddi: publish:
<7>[ 3.666778] mddi_epson_probe

revision 2 (I/O):

<7>[ 0.000000] tag_panel_parsing: panel type = 1
<4>[ 0.253204] supersonic_init() revision=2
<6>[ 4.328552] mddi: registering panel mddi_c_b9f6_5582
<6>[ 4.328552] mddi: publish:
<7>[ 4.329254] mddi_novtec_probe

I haven't noticed any other significant changes that aren't already accounted for in the code that we have. I'm still analyzing the stock binary, trying to get the updated code reversed, and then I'll give it to toast as a patch so that it will boot for revision 3 devices too.
[EVO 4G Android Development] Hero_Over:
We need more in the source. Camera/accelerometer/ and some other sensors are broken. Did u notice that when u compiled?
[EVO 4G Android Development] Vinny75:
Weird, I got my phone on June 4 and its showing hardware revision 2 in the settings hardware information
[EVO 4G Android Development] toastcfh:
updated first post :mad:
[EVO 4G Android Development] Hero_Over:
Hey could you share those board files? Pretty please lol
[EVO 4G Android Development] toastcfh:
they are in the source linked in the first post.
[EVO 4G Android Development] eme82:
May be a stupid question, but have we determined if Rev 3 is any better hardware.

Also, once we get the new board files can the kernel be built to accommodate both sets of hardware?
[EVO 4G Android Development] Hero_Over:
Re: {KERNEL-SOURCE} GoDmOdE-EVO-2.6.29 {Make Shift Kernel}

Oh lol I have been kinda high for the last couple hours. So what you were saying is that the board specific files only work with i/o rev. So that's why those parts are broken?
[EVO 4G Android Development] :
Ahaha, take that non atteendees :P (Actually it could be in our face, if our phones have something wrong with them)

In all realism why a hardware revision already?
[EVO 4G Android Development] AssassinsLament:
Has anyone else tried this? if so, maybe maejrep and toast can tell us what the difference is in the kernel?
[EVO 4G Android Development] EtherealRemnant:
I tried playing with it for awhile. It is in the HTC SSD TEST apk under display fps. I used the CPU clock tool to see if I could reduce the framerate but it froze the phone every time I locked the frequency and then ran the test. Also it stops running when you hit the home screen (i was going to try fps2d) but if we can extract the tool from the apk and break disassemble it, maybe we will see some kernel commands that are being passed through it that lift the cap just for that test?
[EVO 4G Android Development] AssassinsLament:
Oh ok, I innitially thought you meant the kernel was able to break the 30fps, but after reading your post again, I get it now. I'm trying the ssd test and it does report 60+ fps, but hmm... I don't know how accurate that is, plus running fps2d gives the 30fps result.

I don't know if this framerate test unlocks it for the duration of the test or not but yeah it would be great if we could see what the test does, but it pretty much takes processing power away from the phone, so we can't do much with it running.
[EVO 4G Android Development] joeykrim:
usually testing programs have a bit of debugging in them and output to logs. does it show anything in the logs while running this test FPS program?
[EVO 4G Android Development] Cicatrize:
Someone try something for me while I'm at work. open up supersonic_defconfig and modify this line:

CONFIG_HAS_EARLYSUSPEND=y

to this:

# CONFIG_HAS_EARLYSUSPEND is not set

try that, and separately on CONFIG_FB_EARLYSUSPEND if the first one doesn't do anything or won't compile. Curious to see results.
[EVO 4G Android Development] AssassinsLament:
Here's the dmesg of when I started the test and ended it:

<7>[ 123.079040] ALS value: 0x9, level: 2 #
<7>[ 125.082519] set brightness = 163
<7>[ 125.131744] set brightness = 162
<7>[ 125.173339] set brightness = 161
<7>[ 125.223327] set brightness = 160
<7>[ 125.274749] set brightness = 159
<7>[ 125.332763] set brightness = 158
<7>[ 125.374389] set brightness = 157
<7>[ 125.430999] set brightness = 156
<7>[ 125.472778] set brightness = 155
<7>[ 125.517669] set brightness = 154
<7>[ 125.562744] set brightness = 153
<7>[ 125.604278] set brightness = 152
<7>[ 125.661590] set brightness = 151
<7>[ 125.703247] set brightness = 150
<7>[ 125.759246] set brightness = 149
<7>[ 125.800811] set brightness = 148
<7>[ 125.845672] set brightness = 147
<7>[ 125.898132] set brightness = 146
<7>[ 125.953796] set brightness = 145
<7>[ 125.995330] set brightness = 144
<7>[ 126.052612] set brightness = 143
<7>[ 126.094299] set brightness = 142
<7>[ 126.151214] set brightness = 141
<7>[ 126.192749] set brightness = 140
<7>[ 126.252746] set brightness = 139
<7>[ 126.294250] set brightness = 138
<7>[ 126.353240] set brightness = 137
<7>[ 126.397918] set brightness = 136
<7>[ 126.451324] set brightness = 135
<7>[ 126.493164] set brightness = 134
<7>[ 126.548431] set brightness = 133
<7>[ 126.598327] set brightness = 132
<7>[ 126.639862] set brightness = 131
<7>[ 126.684631] set brightness = 130
<7>[ 126.737915] set brightness = 129
<7>[ 126.792907] set brightness = 128
<7>[ 126.834411] set brightness = 127
<7>[ 126.891754] set brightness = 126
<7>[ 127.874145] ALS value: 0xC, level: 2 #
<6>[ 128.174194] [Port list] Add port [2479]
<6>[ 128.174194] [Port list] [1] = 9734
<6>[ 128.174224] [Port list] [2] = 16650
<6>[ 128.174224] [Port list] [3] = 3734
<6>[ 128.174224] [Port list] [4] = 2479
<6>[ 128.174591] SMD: ch 26 0 -> 1
<6>[ 128.174713] SMD: ch 26 1 -> 2
<6>[ 128.876586] batt: SMEM_BATT: get_batt_info: batt_id=2, batt_vol=4100, batt_temp=373, batt_current=92, eval_current=0, level=85, charging_source=1, charging_enabled=1, full_bat=1500000, over_vchg=0 at 125944367764 (2010-06-28 19:17:08.984886244 UTC)
<4>[ 138.464996] msmfb_pan_display timeout rerequest vsync
<4>[ 138.465026] msmfb_pan_display timeout waiting for frame start, 3031 3030
[EVO 4G Android Development] AssassinsLament:
Doesn't show too much information. The brightness setting isn't part of the test because it was apparent in the rest of the dmesg even before the ssd_fpstest.

But what is the msmfb_pan_display? hmm..
[EVO 4G Android Development] Cicatrize:
Interesting. The last line there is this in msmfb_pan_update:

printk(KERN_WARNING "msmfb_pan_display timeout "
"waiting for frame start, %d %d\n",
msmfb->frame_requested,
msmfb->frame_done);

frame_done (3030) is divisible by 30, but not divisible by 60. It seems like the framebuffer is only asking for 30 frames...hmmmm

Assassin: change #define PRINT_FPS 0 to 1 in "drivers/video/msm_fb/msm_fb.c" and see what other dmesg things you get. You should get tons of more info to the dmesg.
[EVO 4G Android Development] AssassinsLament:
Yeah, I just did that and I couldn't find fps anywhere in the dmesg, trying it again with other changes, I'll let you know what I get.
[EVO 4G Android Development] AssassinsLament:
Ok, where does DLOG output to? Doesn't seem to be outputting to dmesg.
[EVO 4G Android Development] Cicatrize:
****, my bad I didn't even look

Change this:

#define DLOG(mask, fmt, args...) \
do { \
if ((msmfb_debug_mask | SUSPEND_RESUME) & mask) \
printk(KERN_INFO "msmfb: "fmt, ##args); \
} while (0)

to this:

#define DLOG(mask, fmt, args...) \
do { \
if ((msmfb_debug_mask | SUSPEND_RESUME) & mask) \
printk(KERN_DEBUG "msmfb: "fmt, ##args); \
} while (0)

KERN_INFO usually outputs to dmesg, but I don't know why it's not here. Try the KERN_DEBUG and see if it works. If not, try KERN_WARNING
[EVO 4G Android Development] AssassinsLament:
I couldn't get that to output either, but I manually put in some printk's:

<4>[ 18.230163] XDA: full update completed
<4>[ 18.230285] XDA: fps * 100: 60
<4>[ 19.261627] XDA: fps * 100: 96
<4>[ 20.263397] XDA: fps * 100: 998
<4>[ 21.315612] XDA: fps * 100: 1710
<4>[ 22.334838] XDA: fps * 100: 1766
<4>[ 23.387237] XDA: fps * 100: 1235
<4>[ 24.423309] XDA: fps * 100: 1158
<4>[ 25.442932] XDA: fps * 100: 1078
<4>[ 26.462341] XDA: fps * 100: 1177
<4>[ 27.481567] XDA: fps * 100: 2747
<4>[ 28.500610] XDA: fps * 100: 3042
<4>[ 29.519653] XDA: fps * 100: 3042
<4>[ 30.538848] XDA: fps * 100: 3041
<4>[ 31.540954] XDA: fps * 100: 2195
<4>[ 32.542510] XDA: fps * 100: 2995
<4>[ 33.708404] XDA: fps * 100: 1629
<4>[ 34.710174] XDA: fps * 100: 2994
<4>[ 35.941528] XDA: fps * 100: 2030
<4>[ 36.960601] XDA: fps * 100: 981
<4>[ 37.963287] XDA: fps * 100: 2892
<4>[ 38.982208] XDA: fps * 100: 2649
<4>[ 40.001373] XDA: fps * 100: 2747
<4>[ 41.020416] XDA: fps * 100: 2845
<4>[ 42.022949] XDA: fps * 100: 2593
<4>[ 43.024810] XDA: fps * 100: 2395
<4>[ 44.043273] XDA: fps * 100: 2356
<4>[ 45.078308] XDA: fps * 100: 2511
<4>[ 46.096923] XDA: fps * 100: 2258
<4>[ 47.115539] XDA: fps * 100: 2356
<4>[ 48.134246] XDA: fps * 100: 2257
<4>[ 49.136352] XDA: fps * 100: 2295
<4>[ 50.155059] XDA: fps * 100: 2159
<4>[ 51.157318] XDA: fps * 100: 2294
<4>[ 52.192230] XDA: fps * 100: 2222
<4>[ 59.310028] XDA: full update completed
<4>[ 59.310028] XDA: fps * 100: 389
<4>[ 60.453887] XDA: fps * 100: 87
<4>[ 61.459350] XDA: fps * 100: 3282
<4>[ 62.514221] XDA: fps * 100: 2085
<4>[ 63.555725] XDA: fps * 100: 2016
<4>[ 64.609161] XDA: fps * 100: 2278
<4>[ 65.650329] XDA: fps * 100: 2305
<4>[ 66.945587] XDA: fps * 100: 1003
<4>[ 67.986328] XDA: fps * 100: 1729
<4>[ 68.990814] XDA: fps * 100: 1294
<4>[ 69.995178] XDA: fps * 100: 2090
<4>[ 71.011871] XDA: fps * 100: 2655
<4>[ 72.028625] XDA: fps * 100: 2262
<4>[ 73.010681] XDA: average wait time: 7781
<4>[ 73.032867] XDA: fps * 100: 2290
<4>[ 74.037963] XDA: fps * 100: 2188

Doesn't show much except that it never really goes beyond 30fps.

The "average wait time" is the print blit time define.
[EVO 4G Android Development] Cicatrize:
Run the same with the T2 hack posted yesterday that does 50+fps.
[EVO 4G Android Development] Cicatrize:
Interesting part about that too is that the msmfb_handle_dma_interrupt got called 34 times between update completions.
[EVO 4G Android Development] AssassinsLament:
I don't know what ffolkes' settings are, but I have mine at 40fps. When I don't run anything it never goes beyond 30fps, but the moment I run fps2d it does:

<4>[ 1183.376434] ASSASS: full update completed
<4>[ 1183.376434] ASSASS: fps * 100: 133
<4>[ 1184.425811] ASSASS: fps * 100: 95
<4>[ 1185.679809] ASSASS: fps * 100: 1674
<4>[ 1186.735900] ASSASS: fps * 100: 946
<4>[ 1187.755676] ASSASS: fps * 100: 2745
<4>[ 1188.775085] ASSASS: fps * 100: 490
<4>[ 1189.794586] ASSASS: fps * 100: 1667
<4>[ 1190.813934] ASSASS: fps * 100: 4120
<4>[ 1191.833312] ASSASS: fps * 100: 4120
<4>[ 1192.852691] ASSASS: fps * 100: 4120
<4>[ 1193.872100] ASSASS: fps * 100: 4021
<4>[ 1194.891296] ASSASS: fps * 100: 4120
<4>[ 1195.910552] ASSASS: fps * 100: 4120
<4>[ 1196.929565] ASSASS: fps * 100: 4121
<4>[ 1197.948547] ASSASS: fps * 100: 4121
<4>[ 1198.967346] ASSASS: fps * 100: 4122
<4>[ 1199.985107] ASSASS: fps * 100: 4028
<4>[ 1201.003173] ASSASS: fps * 100: 4125
<4>[ 1202.022033] ASSASS: fps * 100: 4122
<4>[ 1203.028015] ASSASS: fps * 100: 4075
<4>[ 1204.045501] ASSASS: fps * 100: 4127
<4>[ 1204.966888] ASSASS: average wait time: 11196
<4>[ 1205.062683] ASSASS: fps * 100: 4128
<4>[ 1206.080017] ASSASS: fps * 100: 4128
<4>[ 1207.097045] ASSASS: fps * 100: 4031
<4>[ 1208.114227] ASSASS: fps * 100: 4129
<4>[ 1209.132446] ASSASS: fps * 100: 4026
<4>[ 1210.138732] ASSASS: fps * 100: 4074
<4>[ 1211.144470] ASSASS: fps * 100: 3977
<4>[ 1212.149871] ASSASS: fps * 100: 4077
<4>[ 1213.168365] ASSASS: fps * 100: 4025

Notice how much higher the blit wait time is now...
[EVO 4G Android Development] Cicatrize:
Not really concerned about the wait time, since I think that's in ns anyway. Try it with this one: http://xdaforums.com/showthread.php?t=711964

I've been getting 50fps with that, but 40Hz on input response.
[EVO 4G Android Development] Cicatrize:
I wouldn't be surprised if you noticed ave wait time to be around 20000 with that kernel too because the T2 timing is set to 400d.

I'm going to head home right now, so I'll be able to do some compiling in about 30 mins. :)
[EVO 4G Android Development] AssassinsLament:
That one won't have my printk's.

Also, I was incorrect, average wait time isn't blit time, it's actually a time in the pan update.

I have a hunch that htc is splitting the fps by sending a frame twice, once to the screen, the other to hdmi.
[EVO 4G Android Development] Cicatrize:
Oh, just change T2 to 400d. That's all it does.

It would make sense because that guy that has the 1200fps camera said it drew the whole screen in 20 frames and froze for 20 frames. so it only draws the screen 30 times in a second but it's obviously capable of drawing it 60. I haven't found anything specific that shows HDMI is using the framebuffer though while the display paints. HDMI is also using RGB.
[EVO 4G Android Development] AssassinsLament:
I tried that, as I posted a few pages ago, and I can't get above 30,he had to of had set something else.
[EVO 4G Android Development] halfline:
I was able to reproduce his results by using his values without any other changes that I can recall. Unfortunately, I left my drive at work today on accident so my plans to play with stuff tonight has sort of fallen through. If I had the drive I would post a diff.
[EVO 4G Android Development] funjas:
Has anyone created a test video with the godmode-evo kernel?
[EVO 4G Android Development] maejrep:
Test video of what? Like test patterns? Random video to test video playback? Camcorder shot of someone playing around with the phone?
[EVO 4G Android Development] th3_g00b:
ok, i hope this isnt cluttering the thread. i've searched for this issue and have come up on nothing. so heres what i've found: i know that people have been having issues charging their phones after applying the kernels. i am running t2 and am having those same issues. i plug in my phone, the light comes on then goes off about 2 seconds later (USB and Car Charger). for some strange reason, i boot into recovery and through adb shell i do "mount /sdcard" and reboot my phone. suddenly it starts to charge normally again. like i said, i'm sorry if this has been brought to ur attention but i didnt find anything through search. thought it might help. regardless, awesome work guys!!
[EVO 4G Android Development] AssassinsLament:
Ok, just a thought... is there a way to put a printk where it writes the image to the buffer, and then calculate how many times it's writing per second or a certain time period so we'll know if it's actually writing that fast (could mean it's splitting half the time on the other interface)?

Does that make sense?
[EVO 4G Android Development] halfline:
Hdmi and the panel have different fb devices. A while back I wrote a test program that just writes to the panel fb. The results were that it blocks waiting for the DMA transfer of pixels to finish
[EVO 4G Android Development] Cicatrize:
I was talking to maejrep for a while last night about this and he spent a while educating me about the interfaces and how the shmem buffers are used (thanks, btw).

The only ideas we could come up with are:

1. [unlikely] HTC coded the radio (in asm) to alternate frames back and forth to HDMI and the panel, and this would be extremely difficult if not impossible to change.

2. [possible] There is literally a pause of 16ms in between frames sent to the buffer. This could be a deliberate pause, or an operation that actually takes 16ms, but that'd have to be pretty heavy to take that long.

3. [silly] I suggested HTC implemented a proc called: htc_stupid_fps_cap_fb_wait() This seems highly likely and we should look for it in the code. :)
[EVO 4G Android Development] fecht:
has anyone had any luck with fixing the tearing on the epson/sharp screens?

Thanks for everyone's help involved in this process
[EVO 4G Android Development] Adanedhels:
Ditto here waiting to root my EVO until there is a fps fix for my Epson panel....
[EVO 4G Android Development] p-slim:
if the 30fps fix isn't in this kernal then why does xda say it is, this is so confusing.

http://www.xda-developers.com/android/breaking-the-30-fps-limit-on-the-evo/