yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] sracercelica:
The Flashable ZIP - WiFi-N + 4G for stock/custom kernels is what you need to flash to fix your wifi/4g. That is not a kernel and that is why you didnt notice any changes when you flashed that. So now that you did flash the kernel go back and flash that zip again.
[EVO 4G Android Development] Mast3rpyr0:
Any change i could get the 5.2 beta? im having some issues with 5.1.1 for some reason and im only getting 31ish fps now( i used to get 52.. dunno what happened). I went back to 4.2 where i would get my 52 again, but that breaks things like video and Asphalt doesnt play as well anymore even with the fps increase. I would love to try out 5.2

Thanks
[EVO 4G Android Development] sracercelica:
Have you tried changing the T2 settings with Evo Switch?
[EVO 4G Android Development] Mast3rpyr0:
Oh ya i tried all the settings with evo switch, too nervous to try my own numbers though
[EVO 4G Android Development] kdog1234:
5.2

do you know what the success rate of the low voltage kernel is? and it wont decrease performance if i use that one right?
[EVO 4G Android Development] Philosuffer:
Sounds like you might have an Epson panel if 4.2 worked for you but 5.1.1 doesn't.

If I understand correctly, 4.2 was based off of toasts godmode kernel which had the Epson fix included.

5.1.1 is based off of the HTC released kernel source and doesn't work with Epsons.
[EVO 4G Android Development] Sporkman:
This kernel with baked snacks rom = insane im.getting 65 fps on f2d switch is.locked at 247 im.sure the 65 is a.fluke but it's happend 5-6 times

sent with my evo from a sapensesecret place
[EVO 4G Android Development] toneman1984:
Are there any online videos of people navigating around their evo phone with the 60fps fix? I tried Youtube and all I could find was a video of benchmark tests. Or could someone film it and post it somewhere like on youtube? That would be really cool. I haven't bought my Evo yet and would like to see the difference in speed before purchasing one.
[EVO 4G Android Development] gtkansan:
I would love to test 5.2 as well.
[EVO 4G Android Development] prodigy2m:
I had the same issue, you need to:

1) Wipe cache/restore factory from Recovery

2) Wipe SD Partition before you restart after applying this patch.

That's how I fixed mine. Good luck.

(Be advised, all your applications will be removed!)
[EVO 4G Android Development] prodigy2m:
Use 247 for 45 frame stable!
[EVO 4G Android Development] kawasaki00:
I have the 002, nova and I am getting 45fps with oc on performance 1.113, and t2 on 437, any lower and it drops back to the low 30ish range.
[EVO 4G Android Development] Rudementry:
On EvolutionV9 and OC at 1075 performance I get 45fps very steady with T2 432. (the standard)
[EVO 4G Android Development] kfree:
could someone toss me 5.2?

on 5.1.1 I'm getting 42fps stdev: 9.56.. pretty smooth..

i'd love to test :)
[EVO 4G Android Development] Rudementry:
I'd be happy to test 5.2. I've had great results with 5.1.1, getting 45fps with about 3stdev.
[EVO 4G Android Development] kpkimmel:
Stop asking for 5.2 those who have are testing for ffolkes, has some issues, be patient
[EVO 4G Android Development] KERKEDAGAIN:
yeah..no worries, you're really not missing much. It's a great proof of concept but there are issues to be ironed out (issues, I guarantee, that would lead to a bunch of "i'm going back to x.x until this gets fixed) So, patience, dear friends :D
[EVO 4G Android Development] jvasco2010:
fresh .5.3

if i do wipe it and flash this kernal will i have to just wipe it again for 5.2 and other ones? it seems im the only one that seems to have to go through a hastle to put a simple kernal on the phone because it takes a good 2 hours ever time just to get all my **** back to the way i like it. not sure what i should do...
[EVO 4G Android Development] jerryparid:
Stop complaining.

I only wiped dalvik and cache, with 247, I get 41-42 fps stable. Looks like Epson fix is now back ahead of the Nova one.
[EVO 4G Android Development] sracercelica:
What issues have you had? I am running 5.2 and so far it has been smooth sailing. I do notice occasional tearing but not consistently. No reboots either or loss of responsiveness. Been running it for about 24 hrs with heavy use.
[EVO 4G Android Development] Animatorman:
Im interested in how v5.2 is getting these results. I'd be running a fps2d test and it will stop before finished but it will be showing a fps in the high 100s and sometimes 200s.

If this could be made a bit more stable it would be amazing. Can anyone confirm if EVO switch works with v5.2 because I try using it and its hard to tell if its affecting results due to the large fluctuations in FPS.

Also ran An3DBench and scored a 4411 which I believe is right on par with most other stock phones hitting 60fps that dont have a dedicated GPU.
[EVO 4G Android Development] Mast3rpyr0:
Nope definitely Novatec. It was working great ever since it came out but today it just decided not to give me 52fps.. my 3d game played well without the FPS though and failed with 4.2. i dont understand that but oh well.
[EVO 4G Android Development] Animatorman:
Ive definitely had stability issues. Yesterday my phone became unresponsive had to pull the battery. I was overclocked so I backed that down to stock uninstalled evo switch and reverted back to v5.1 which resulted in a much more stable system. Now back to testing and Im again running v5.2 evo switch is installed and cpu clocked at 1075. The system seem pretty stable scrolling seems ok but typing on the keyboard of all things seems to lag and hang up an some letters and space bar.
[EVO 4G Android Development] Philosuffer:
Hmm, that is wierd then, because with 5.1.1 you should be getting about 41-42fps with a T2 setting of 250, and around 44-45fps with a setting of 437 (default for 5.1.1 I think).

The fact that you were still only getting 31fps is what made me think you that didn't have a Novatek.
[EVO 4G Android Development] Mast3rpyr0:
Hmm maybe i had something running in the background last night. today im getting a very solid 45/46 with stdev 3.15. so im happy with it today :) I know stdev has something to do with tearing but could someone elaborate a bit more on it?
[EVO 4G Android Development] MrTheGeekGuy:
Unable to start wifi?

just flashed 5.1.1, getting unable to start wifi... anybody else getting this?
[EVO 4G Android Development] jblazea50:
flash the appropriate wifi 4g fix that's posted in the 1st post
[EVO 4G Android Development] MrTheGeekGuy:
oh wow, how did i miss that, thanks for the quick reply
[EVO 4G Android Development] derik123derik123:
Flashable ZIP - Normal-volted kernel v5.1.1 for use with 2.1 (Eclair) ROMs

Is that the stock? If i flash that will it be like i had it before? get rid of this?
[EVO 4G Android Development] 12MaNy:
I'm running newest software (1.47), newest radio (2.05), DC 3.2.3 and using the normal-volted kernel v5.1.1/2.1 (eclair) version and getting mad random reboots...even with less agressive settings.
[EVO 4G Android Development] Rudementry:
Edit: I get about 50 max in gears though.
[EVO 4G Android Development] Philosuffer:
I think it stands for Standard Deviation (basically, one way of measuring the fluctuation of the frames per second)

http://en.wikipedia.org/wiki/Standard_deviation
[EVO 4G Android Development] sracercelica:
Because Gears mesures 3D which the Evo sucks at (because of the GPU)
[EVO 4G Android Development] surferpr:
does this mean we are getting closer to the epson guys? Over at the epson thread they state 55 fps without tearing. Dunno since I am on nova. Im just wondering if with the nova we can fiscally do 60fps.

Btw this is a win for the community this is probably the last HTC device I buy, they always gimp their stuff.
[EVO 4G Android Development] 12MaNy:
Getting reboots from the undervolted version as well.
[EVO 4G Android Development] itmustbejj:
What did they gimp on the nexus?
[EVO 4G Android Development] MrTheGeekGuy:
are you overclocked?
[EVO 4G Android Development] edtate:
No, but it's the fact htc revels on how their the "premier android phone manufacturer of the world" (my words there,but it does describe them), and we even get charged premiums just to own the freakin phone, yet, we have to have guys spend endless hours on here fixing things we never have had to fix. On a more topic related note, I'm on newest software (1.47), newest radio (2.05), stock rooted rom, and using the undervolted eclair 5.1.1 kernel getting rebooted to the point it's unusable. Since multiple people have had this problem, it seems like its not just a random occurrence that hasn't been explained yet (to my knowledge it hasn't). Any ideas?
[EVO 4G Android Development] M@XLOL:
Use normaal volted kernel.
[EVO 4G Android Development] halorin:
They botched the touch screen.
[EVO 4G Android Development] omegatyrant:
I got reboots with both the undervolt and normal volted versions. is it a problem with the hack or an incompatibility with DC?
[EVO 4G Android Development] OneStepAhead:
no problems like that here with DC 3.2.3

@netarchy: Could you enable support for loop devices so we can use this kernel with Ubuntu? It's just 1 line of code..

CONFIG_DEV_BLK_LOOP=y
[EVO 4G Android Development] wuclan48:
X2 I really want to boot ubuntu but I don't want to lose the benefits of this kernel to do so.
[EVO 4G Android Development] 12MaNy:
Not sure. Might even be a setting in DConfig. I'm working, so I'll play around with it a little later.
[EVO 4G Android Development] Philosuffer:
Well, really you are only supposed to use the kernels in post 2 of the DC thread. TrevE modified them to work with DC (and DConfig more specifically). There's a modified ffolkes 5.1.1 kernel there.
[EVO 4G Android Development] toneman1984:
Just for redundancy perposes: If anyone has a video camera and an evo with the kernal that uncaps the 30fps lock, please film the smoothness of navigating home screen etc. and post it online. I would really appreciate that. Once I get my evo i'll be contributing and testing as much as possible.

Thankyou all for your dedication to making the evo as great as it can be. You all are awesome.
[EVO 4G Android Development] surferpr:
True, but its kinda hard for them to gimp something google is pampering directly. Mostly im talking about my experience with htc you see this is my 4th htc. Every time it was something different. The evo has finally thought me this lesson.
[EVO 4G Android Development] SteveDusa:
Got the Wifi and Wimax fixed with updated zip in the front page.

Now I noticed that the amount of free RAM decreases a lot when I use the screen a lot... any thoughts?
[EVO 4G Android Development] leeh41:
I'm using UV kernel from here with DC 3.2.3 and no problems. I did notice my Mflops dropped quite a bit (was 6.x now 4.x).
[EVO 4G Android Development] Philosuffer:
It might work without any apparent issues, but supposedly DConfig (and obviously the DConfig profiles) do not play nice, or simply do not work at all if you do not use the kernels posted in post 2 of the DC thread.

The Mflops drop could just be that some other CPU intensive process was running.
[EVO 4G Android Development] audiophonicshz:
I have the dc 323 Rom with the uv kernel for dc roms running in performance mode on setcpu on rev2 hw. Just wanted to chime in that I'm getting great battery life, bout double stock. No reboots, 45fps 3.5 stdev. The devs have done a great job. Aces.
[EVO 4G Android Development] Cicatrize:
I can't for the life of me find where I saw it, but anyway, it doesn't matter.

The Hero uses the same MDDI platform and doesn't run at 30fps, does it? :p

EDIT: Btw, the MDDI clock rate for the Evo is set to 384MHz. The only possible bus I could see holding it back is the I2C, but it doesn't appear the display is on I2C. Could be wrong though.
[EVO 4G Android Development] jerdog:
First I acknowledge my complete lack of knowledge, but a desire to search and find answers.

MDDI is a standard like USB 1.1/2.0/etc, right? From what I am seeing is MDDI just the industry standard governing interfaces, so that something can be marked MDDI 1.1 compliant? If so, then from what I see an interface (LCD panel) that is marked as MDDI 1.1 compliant would be able to handle up to 400MBps....? An example I found while searching was here -http://www.digchip.com/datasheets/parts/datasheet/487/TC358720XBG.php

They mention MDDI 1.1 as a standard that an interface is to meet, not an actual physical thing (software or hardware).... So the LCD panel would operate at xxxHz while the data bridge/interface, being MDDI 1.1 compliant, would be able to send data to it up to 400mbps?

Or am I missing the boat?
[EVO 4G Android Development] Cicatrize:
You hit the nail on the head.

And as you can guess, 400Mbps is plenty of bandwidth to be able to handle every single thing on the board.
[EVO 4G Android Development] nenn:
im boot looping running fresh .5

:(
[EVO 4G Android Development] jerdog:
Ok - so then I am looking for clarity so I understand the issue...

The guy in Sprint's Phone tech department said "the hardware doesn't support the higher refresh rate" - he would then be referring to the LCD panel's refresh rate [which is different from fps right?] not being able to handle a higher refresh rate - but doesn't specify that the MDDI bridge can't handle it since it isn't measured in refresh rate (Hz) but in data, which the max it could handle is up to 400mbps....?

With that being the case, then aren't we still dealing with the LCD panel being able to handle a higher refresh rate, but quite possibly not an extended fps of over 50+? Even though I know 50 has been attained. Or would it be the other way around?
[EVO 4G Android Development] jmxp69:
Really? http://www.youtube.com/watch?v=cAjTo602sQM

I don't see any tearing.
[EVO 4G Android Development] AssassinsLament:
I think he was referring to the epson models. But yep, it's silky smooth on the Novatek models. If we could find reference material on the epson model, we may be able to make it silky smooth also... but until then, we'll see tearing.
[EVO 4G Android Development] Westibone:
Can you remind me what the model/part # of the Epson panel is?
[EVO 4G Android Development] Mrtankjump:
I'm still getting some odd lines down one side of my screen, seeming after talk or text data happens. I also turned the screen on at one point to a very blown out, flickering, and just cycling the screen on and off fixed that. I guess my EVO is going out since no one else is reporting these issues.
[EVO 4G Android Development] nonpointtruth:
I have flashed this "hack" twice today.. Once before updating my DamageControl ROM to 3.2.2.. Once after.. I saw no real noticeable gain visually, I did see an increase in the FPS using fps2d.. Didn't see much difference in numbers when I compared before and after with Linpak.. So I still fail to see what this actually helps.. Couldn't get Youtube to play to save my life.. Hopefully a more stable workaround appears soon.. Until then, keep up the good work devs.. Much appreciated!
[EVO 4G Android Development] Krandor311:
Linpack has nothing to do with your framerate, so I don't why you should even be expecting to see a difference there.
[EVO 4G Android Development] Cicatrize:
Attn ffolkes: The T2 parameter is a full 10 bit binary code, so we're not really looking at this the right way. The reason why you had problems setting 0xb102 to anything over 250 is because it's only 8 bits, so it can't accept anything over 255. I'm surprised it even let you do 0x190 without screwing up, actually.

EDIT: I realized you probably have to be doing this, or else the 400 would really mess things up.
[EVO 4G Android Development] AssassinsLament:
No, you set the 10 bit with both T2's

0xb101 = 01 (upper T2)

0xb102 = 90 (lower T2)

= 190h
[EVO 4G Android Development] Cicatrize:
Isn't that exactly what I just said? :confused:

I was implying that he may be using 0x190 for the lower and 0x00 for the upper....
[EVO 4G Android Development] AssassinsLament:
lol, OK. :D

My bad then. But yeah, he's been doing it right cause he posted it many times.
[EVO 4G Android Development] KERKEDAGAIN:
..if i may...just a slight request...:o

any way you can update your kernel to run w/ the latest OTA? It currently breaks 4G and WiFi but after experiencing its sheer speed i don't wanna use the stock kernel!
[EVO 4G Android Development] grafixguy123:
successful flash!

just flashed this kernel on hardware version 0002 with novatec screen running damagecontrol 3.1.2 and it works like a charm! silky smooth transitions between homescreens and overall snappy performance! (really quick top draw action, quick window animations, smoother browser scrolling, it prints money...)

no charging issues as of yet (didn't have to remove battery etc.) and the disk mounts and unmounts as normal.

so far only thing missing (that i use anyway) is the camera. small price to pay imo.

well done all!
[EVO 4G Android Development] jmxp69:
I didn't see mention of Epson in the post, so I didn't connect the dots there.
[EVO 4G Android Development] ChristmasGT:
Yeah it's such a world of difference! But Losing 4G makes it a bit difficult, also the charging issue :(
[EVO 4G Android Development] halfline:
mddi_remote_read() has this in it:

if (wait_for_completion_timeout(&ri.done, HZ/10) == 0 &&
!ri.done.done) {
printk(KERN_INFO "mddi_remote_read(%x) timeout "
"(%d %d %d)\n",
reg, ri.status, ri.result, ri.done.done);
spin_lock_irqsave(&mddi->int_lock, irq_flags);
mddi->reg_read = NULL;
spin_unlock_irqrestore(&mddi->int_lock, irq_flags);
ri.status = -1;
ri.result = -1;
}

at the bottom of the function it returns ri.result cast to unsigned int (so -1 is cast to 0xffffffff). It will try exactly twice to get a value in the above wait_for_completion call before giving up and just returning -1. Note HZ/10 is 10ms.

So why would it fail? It means complete(&ri->done) isn't getting called within 20ms (10ms * 2). that complete call serves to wake up the wait_for_completion_timeout function. complete(&ri->done) is called in interrupt context: mddi_isr -> mddi_handle_rev_data_avail -> mddi_handle_rev_data -> case TYPE_REGISTER_ACCESS. It doesn't get called in this case:

if (ri->reg != rev->reg.register_address) {
printk(KERN_INFO "rev: got reg %x = %x for "
"wrong register, expected "
"%x\n",
rev->reg.register_address,
rev->reg.u.reg_data, ri->reg);
break;
}

Do you see that in dmesg? If so, then somehow mddi->reg_read is getting overwritten while that call is pending. It is protected by a mutex, but there might be some locking issue or other problem along those lines. If you aren't seeing that message, then the interrupt is probably getting cleared somehow.
[EVO 4G Android Development] kfree:
installed 5.2 on dc 3.2.3..

get the following in fps2d (ran it 5 times..)

running fps = 23, avg = 52

that's with evo switch set at 247...

nenamark says 10.1fps
[EVO 4G Android Development] drunkenmonger:
5 points and 2 points of touch

I have two EVOs, both rooted, running Damage Control 3.2.3 roms. When I did my first phone I got 44fps and 5 points of touch using the Dotty app. When I did the other phone I got 44fps and only 2 points of touch. Both phones have the same hardware versions. Does anybody know why this would happen?
[EVO 4G Android Development] KERKEDAGAIN:
gotta admit..it DOES feel nice gettin' numbers like this...(sorry for the box on top)
[EVO 4G Android Development] dglowe343:
Was your screen off? Im still kind of a noob, but I think the lower your stdev the better. I usually avg around 4-5
[EVO 4G Android Development] drunkenmonger:
What frequency do you have your screen set at?
[EVO 4G Android Development] beastmods:
What did i do wrong?

Running DC 3.2.3

when i try 370 i get like 27 fps.

if i take it to 250 then i can get 42.

stdev 6.5

overclocked to 1.19 and did not do much better.

could anyone maybe guide me to see 57 fps?

Oh yeah tried the undervolt and the normal volt kernel.

Also never got 5 point touch to work. (only 2)

Thanks
[EVO 4G Android Development] lloydcabraham:
Thanks a bunch for this kernel, it's great. One question though, can anyone confirm if hdmi still works?
[EVO 4G Android Development] MrTheGeekGuy:
How can i get those numbers?
[EVO 4G Android Development] apollooff320:
To bad the phone performance feels nothing like what you see. Scrolling is laggy as hell.

Sent from my PC36100
[EVO 4G Android Development] KERKEDAGAIN:
set my frequency at 250 from the latest evoswitch in the themes/apps section running baked snack 9.6 overclocked to the max w/ the 5.2 kernel...and the performance is decent but not exactly what you'd think from seeing those numbers
[EVO 4G Android Development] k wizzle:
Been running v5.1.1 for a while and it seems pretty stable. No issues whatsoever.

Averaging 47fps in fps2d and between 12.8 and 13.8 in NenaMark.

Can't wait to test newer versions.

:edit: Running Baked Snack 9.6
[EVO 4G Android Development] ek9manr:
I got the 5. 1. 1 kernel and im getting 46 fps. I would like to try the 5. 2 v if anyone would like to share please. I want to see what difference does it have over all other kernels ive tried.

Sent from my Evo Fresh 4G Device
[EVO 4G Android Development] _Burst_:
I want 5.2 also. I dunno what would be added though. Just tweaks? 5.1.1 is working fine.
[EVO 4G Android Development] Philosuffer:
What T2 setting did you use to get these results?
[EVO 4G Android Development] ek9manr:
I tried fps2d thats when i get 46fps. Then downloaded quadrant standard for general benchmark 3d and 2d but my fps did not seem to increase much plus graphics did not look good neither.

Sent from my Evo Fresh 4G Device
[EVO 4G Android Development] k wizzle:
248.......
[EVO 4G Android Development] mrkmrk:
Just a thought to put out there about the apparent lagginess of 5.2: When running the benchmark, it's evident that, while we do get a damned high average, we also get a ridiculously large spread (that high a percentage of the fps shouldn't be within a 40-fps range). Whenever things are actually happening on screen, it's going to tend to the lower end of that (i.e. sub-30)--and we have more on the lower end than do those running 5.1.1. So I surmise that while we can get very high numbers out of this, the stresses of actual use cause it to be a little bit worse, in many cases, than 5.1.1.
[EVO 4G Android Development] ruben8448:
Ok, so i am very new to this and i believe i did everything correct but every time i test it i get 9.7 or 9.5 fps. the highest i got was 12.4. whats going on?
[EVO 4G Android Development] ruben8448:
Scratch what i said, i was getting 12.4 with nena and i just ran it with aps2d and i am getting 43 with stdev at 8.33. cheers
[EVO 4G Android Development] riassan:
was wondering if im flashing a new rom coming from this should i just do the normal wipe to remove the effect of this kernel or no??

Thanks to all the great developers and testers who keep all of us going with being excited to see the max amount of things HTC didnt want it to do

!!
[EVO 4G Android Development] leeh41:
tried again after reboot, use ATK to kill tasks, checked running services and nothing extra running. still getting about 4.x from Linpack... might test with normal volt kernel.
[EVO 4G Android Development] hacketbt:
Amazing job ffolkes! Thanks so much. This is a much better experience with your patches. A few days after I got my EVO i was using my ipod touch and that was when I first noticed how truly poor the touch/scrolling was on the EVO. This is a big step towards the experience we all want, and deserve.

46 fps on 5.1.1 without tweaking evoswitch at all yet.

I'd love to try 5.2 if anybody is feeling charitable. :D
[EVO 4G Android Development] ffolkes:
i've been working on a new technique to squeeze a little more fps out, but i'm not sure i like it. what do you guys think of this? faster than before? is it too choppy? but is it more responsive?

http://www.comfx.com/evo/boot_t2_v5.2.1-e-signed.zip

you'll need the godmode wifi+4g for this, and eclair.

edit: i forgot to mention, if it interests anyone, all 5.2+ versions have support for loop file systems (for use with ubuntu)
[EVO 4G Android Development] _Burst_:
About to flash it.

I'll test it over the day and get ya some feedback.