yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] Congo123:
@Rudementry: Download the program linked in the initial post and use it to change your T2. I am on the same ROM as you and your fps was what mine was. Im still trying to find the sweet spot, but changing it to 250 gave me 42 fps.
[EVO 4G Android Development] tmotech88:
im lovin it. going very well so far! ill keep ya posted if anyting changes ;)
[EVO 4G Android Development] Rudementry:
Thanks for the help, you were very kind and polite even though I should've read that. Sorry don't see how I missed it.
[EVO 4G Android Development] neles86:
I'm using the undervolted kernel 5.1.1 and getting an average of 44 fps but i had to change the T2 to 248 to eliminate tearing. Everything is running excellent! I'm going to try the normal volted kernel because i get boot loops as soon as i increase the cpu frequency even at 1036 Mhz :-/
[EVO 4G Android Development] itmustbejj:
You guys should try out T2 timing of 460 works better than 250 for me with no tearing.

Normally at 44/45 as opposed to 40/41 at 250/248
[EVO 4G Android Development] mpike78:
rooted running fresh 0.5.3 flashed 45fps getting 44fps on fps2d
[EVO 4G Android Development] Rudementry:
Thanks for the tip, I'm getting 43/44 at 460 as opposed to 41/42 at 250.
[EVO 4G Android Development] neles86:
yea unfortunately anything over 250 doesnt give me good results. At 460 i achive no more than 24fps. My evo's sweet spot seems to be @ 248 hitting 46fps (sometimes lol). I'm using Fresh's 0.5.3 rom.
[EVO 4G Android Development] docsparks:
****. Killed the antenna? no 3g/data/anything

Sorry, nevermind.

For the sake of saying, ive googled the error. found information. waiting for room mate to call me with different phone.

we'll see how this turns out. Thanks guys.
[EVO 4G Android Development] neles86:
for some reason this happened to me the first time i flashed the custom kernel but it went away right away. So issues since.
[EVO 4G Android Development] catpunt:
Thanks, that does work better for me!

Edit: However I notice that the touchscreen lag is a little more with that setting. Still better than stock though.
[EVO 4G Android Development] Rudementry:
What can I type in ADB to tell me the cpu frequency?
[EVO 4G Android Development] kevyli85:
Update: I wiped and reloaded the Rom + kernel and my camera now works fine
[EVO 4G Android Development] forceOnature:
WiFi tether may have been affected on my phone. I'm seeing my laptop drop WiFi tether link every few minutes and it doesn't reconnect unless I tell WiFi tether to stop and then start tethering again...

Sent from my EVO
[EVO 4G Android Development] rjmjr69:
I cant seem to get anything from this kernal. I flashed over dc3.2.3 and I get no multi touch just two points. my fps are at 24?????? Volume is barely audible? I did a davik wipe
[EVO 4G Android Development] lafrad:
So, I'm starting to question the accuracy of the FPS tests... I've jabbed at the EvoSwitch numbers a bit, and, while its changes are very obvious in what the screen "looks like" when it comes to drawing... it hasn't changed the overall feel of the "NON Input" related framerates... Gears may say 50 fps, but it still has that slight "jerkyness" of a lower framerate...

Does anyone have the ability to capture the screen refreshes with a high speed camera to see if we are really changing the display FPS?

My Hat's off to the devs for getting this hack out to increase the responsiveness of the display... I just want to know if its the path to better response to interactions... or if its truly overcoming a limitation...
[EVO 4G Android Development] kpkimmel:
Bad news. Htc says the 30fps issue is hardware related due to giving most power to the stupid ****ing hdmi port that most will never use, its not software based, the phone is architectured that way, we are simply forcing the cpu to momentarily trick itself into giving power to the lcd. Bout ready to cancel sprint junk this phone amd get the droid x
[EVO 4G Android Development] mrkmrk:
Yeah. They've been saying that for a long time. Hasn't stopped anybody here.
[EVO 4G Android Development] kpkimmel:
I dont think we are truly breaking 30 fps
[EVO 4G Android Development] sniggle:
I disagree, I definitely notice higher than 30fps using these kernels. The stuttering does exist, but when it's smooth it's definitely more than 30fps.
[EVO 4G Android Development] strung:
I seem to be getting great power performance with the low voltage kernel--this is with wifi, bluetooth and GPS on...and the 1.47 ROM

Bluetooth and Wifi reporting 20% battery use each, so with those off should be even better.
[EVO 4G Android Development] maejrep:
So 4G worked for you on this? That's interesting... I haven't been able to see it connect yet with any of our custom kernels. What ROM are you running?

Excellent work, thanks for the contribution :D To confirm, you're using this?

{ 0xb101, 0x01 },
{ 0xb102, 0x90 },
[EVO 4G Android Development] maejrep:
No assumption necessary. A simple remote_read() will confirm:

$ adb shell dmesg | grep T2
<7>[ 41.022247] supersonic_mddi_init: Pre-init novatek T2: h154 d340
<7>[ 41.151855] supersonic_mddi_init: Post-init novatek T2: h190 d400

val = 0;
val |= client_data->remote_read(client_data, 0xb101) << 8;
val |= client_data->remote_read(client_data, 0xb102);
printk(KERN_DEBUG "%s: Pre-init novatek T2: h%x d%u\n", __func__, val, val);

FYI: with this value, I'm seeing 25fps, stdev 5.68. XC hardware rev.

EDIT: Interesting, on a second reboot, I see a different pre-init value:

<7>[ 40.617523] supersonic_mddi_init: Pre-init novatek T2: h114 d276
<7>[ 40.747131] supersonic_mddi_init: Post-init novatek T2: h190 d400
[EVO 4G Android Development] halfline:
So one thing I wrote this evening after figuring out how to get a kernel cross compiled, etc is a patch for making it easier to dump some of the registers.

I've attached it for those interested. You basically mount debugs (with mount -t debugfs debugfs somedirhere)

and then can

cat somedirhere/novatek_registers

to get a list of registers and their currents values (only some of them because i was too lazy to type them all in)

You can also modify the registers one by one with e.g.,

echo '0xc101 0x5' > somedirhere/novatek_registers

I haven't had a whole lot of time to play with it yet.
[EVO 4G Android Development] maejrep:
Funny you mention that, earlier this weekend I added a device attr for the novatek client device specifically for the t2 register, but it could be expanded. As much as I like to tweak, it can be dangerous to accept arbitrary registers and values, so I prefer to create targeted tweak levers.

/sys/devices/platform/mddi_c_b9f6_5582.1 # cat t2
T2: d340, 0x0154h
/sys/devices/platform/mddi_c_b9f6_5582.1 # echo 400 > t2
/sys/devices/platform/mddi_c_b9f6_5582.1 # cat t2
T2: d400, 0x0190h

patch: http://xda.privatepaste.com/74abf959bb
[EVO 4G Android Development] frankenstein\:
I'm running Flipz rooted stock ROM in these tests. The .6 rev with the OTA update incorporated.

I should probably add a few points to this.

First, I can normally get 4G svc at my home although it is only a single bar of svc that occasionally drops to 0 bars but the connection stays up and runs. I wasn't able to connect at the house with this kernel.

I went out to pick up some dinner and I know the area the restraunt is in has excellent 4G svc, a stable 4 bars of svc. When I enabled 4G at the restraunt and began testing, the link dropped a number of times and the phone fell back to 3G operation. After 4 or 5 flips back and forth between the two the link finally settled into 4G operation and began to transfer data.

Also, the link was weaker than with the stock kernel, 1 or 2 bars as opposed to 4 bars I normally see in this area. In addition, the link speed was slower than I would normally see with 4G svc in the area but I'm resonably sure it was 4G because my ping times were much lower than I normally see on 3G.
[EVO 4G Android Development] Tikerz:
I had the charging problem with the first T2 patch, but just now trying the 2nd one I don't anymore.
[EVO 4G Android Development] ffolkes:
that's really nice! makes it easy to change settings on-the-fly. but i'm getting intermittent problems with it, and i don't know why.

# echo 300 > t2
# cat t2
T2: d4294967295, 0xffffffffh
# echo 340 > t2
# cat t2
T2: d340, 0x0154h
# echo 300 > t2
# cat t2
T2: d300, 0x012ch
[EVO 4G Android Development] AssassinsLament:
Ok, now I'm confused. I can't get it above 30fps anymore.

Basically :

{0xb100, 0x01}, // VPA
{0xb101, 0x01}, // T2
{0xb102, 0x90}, // T2

I'm using maejrep's fork... could that be why?

edit: Nope, that code just doesn't work for me.. ffolkes what is your VPA at?

b101 = 00

b102 = fa

works for me though.
[EVO 4G Android Development] halfline:
ah neat.

Well it's clearly not an "upstreamable" patch. Just something thrown together to aid in debugging this particular problem.

One thing I noticed is if you change some registers it sometimes changes other registers at the same time.

Getting the dump is useful for seeing that kind of stuff. Anyway, i haven't had time to fiddle much and look at the results.

Cool! Sounds like we're on the same wavelength.
[EVO 4G Android Development] Cicatrize:
Hey ffolkes. Nice work. I noticed something interesting though. With the stock kernel, everything caps at 30Hz, even the touch input (I'm using Input Benchmark from market). With your first fix associated with just the T2 hack, the touch input was 40Hz and I was also getting 40fps in 2d and 3d tests. Now, here's where it gets interesting. This new one makes me average 49-50fps in graphics testing, but the touch input is still 40Hz. That's pretty damn strange to me. What else did you change? Do you have a fork I can look at?
[EVO 4G Android Development] ffolkes:
thanks! :D

all that was changed was setting T2 to d400. i'm not sure what clock limits the touchscreen, or why changing the lcd timing ever changed that in the first place. maybe 40hz is the real speed it wants to run at, and the lcd was dragging it down to 30? i'll have to look into it again.
[EVO 4G Android Development] Cicatrize:
I think it wants to run at 60Hz or more, actually. I'd be led to believe the T2 timing affects the entire NT35582 bus timing, but if that were the case, it's curious that we're still seeing 40Hz on the Atmel response.
[EVO 4G Android Development] jabbawalkee:
4G also works for me on this kernel just fine...speed test of 4mb down and here's a screenshot of 4G on with your kernel: http://twitpic.com/20qqc6
[EVO 4G Android Development] codeman05:
^ Weird, I can connect to 4g, show 3 bars...but as soon as I try to run speedtest or open a webpage, it disconnects from 4g and starts searching for a network again. HW0002
[EVO 4G Android Development] KERKEDAGAIN:
no worries, that's not kernel related..happens at my office with stock kernel, but is cool on my way home.
[EVO 4G Android Development] jabbawalkee:
Well it works wonderfully for me (may be the area you're in). I speed tested it and got 3-4mb down and then went to a webpage and it worked well
[EVO 4G Android Development] phobia:
Hi Cicatrize,

While going through the novatek nt35582 datasheet, i stumbled upon this

Can we change those bits? I have no linux experience and am not a dev by any means, just trying to help...
[EVO 4G Android Development] jerryparid:
Looks like Epsen is not getting any support, since it is much less common.

;-<
[EVO 4G Android Development] Cicatrize:
So far I haven't found any evidence this is happening, but I still look for it.

If we find the root of the problem, both panels should be fixed.
[EVO 4G Android Development] phobia:
By changing the VPA and T2 settings, the NT35582 can function at a low frame frequency to display a still picture (reducing power consumption), and at a high frame frequency when displaying a moving picture (which requires data to be rewritten at high speed).

So we need to enable high speed Ram write?
[EVO 4G Android Development] kthejoker20:
I garuntee we will get a fix for it.

Whether it gets fully hacked, or fix released...

or... if toast gets the solder gun out...

One way or another we will get it.

Just have to wait.
[EVO 4G Android Development] mrkmrk:
Yeah, but you're wrong :P.
[EVO 4G Android Development] kfree:
Same with me at first.. I was also getting very sluggish rom.. it was real slow at menu switching and also when I did a linpack, I got like 1.9MFLOPS vs like normal 6MFLOPS with dc3.2.3 w/o the ffolkes kernel..

I did 2 things.

downloaded:

setcpu

evo switch (found in the link in post 1, its an apk file)

I set my evo switch to around 250 and went from 24fps to 42fps... and I also set setcpu to around 1.1GHz..

so far it's pretty solid.. had a few issues right off the bat like the error 67 where it can't login to sprint vision... but it went away.. also had a few boot loops and freezes, just tweaked my settings and realized I can't push 1.2GHz and can't push the 450 mark on evo switch.

hopefully that helps.. so far it seems real solid.
[EVO 4G Android Development] kfree:
might want to drop the setcpu to around 1.1GHz.. I think 'max' is around 1.2GHz.. and yea, mine froze at that speed too..

I have EVO Switch set at 250, getting 42-45fps, . . and set cpu set at around 1.15GHz.. getting around 8MFLOPS on linpack...
[EVO 4G Android Development] kfree:
wow, with the newer kernel I get 533 on Quadrant set to the same min/max on setcpu.. that's quite a bit of difference...
[EVO 4G Android Development] topdnbass:
Reverting back to stock kernel

I can't seem to get WiFi working over here, so for now i'm going back to the stock kernel..

Will try again if a WiFi fix is found.

This is how to revert:

(I extracted the kernel from whitslacks method)

* Download this ZIP: http://www.sendspace.com/file/po4wls

* Drop it in your sdcard root directory

* Boot up holding vol down and power.

* Wait for it to do its thing then hit vol up to begin update..

* Reboot and any problems caused by this kernel should be fixed..

* Don't forget to delete the file from your root dir afterwards.

@Ffolkes

Is the Wifi fix in your op supposed to replace the following files in etc/firmware?

Through ADB i did an ls in that dir and noticed there are two .hcd files (see below)

One that was already there and another from your fix.

Is the hcd in your fix (*.0361.hcd) supposed to replace the stock one (*.0402.hcd)?

BCM4329B1_002.002.023.0396.0402.hcd

BCM4329B1_002.002.023.0360.0361.hcd

I tried mounting r/w and replacing the stock file with yours but it didn't help.

Well i'll try again once things are optimized :D

Thanks for your work
[EVO 4G Android Development] geeserver:
Unvoltage kernel is too unstable. Went for 6hrs with it and now I constantly get reboots. Going back to normal voltage.
[EVO 4G Android Development] XmemphistoX:
Undervolt kernel is running fine here. 12+ hours going strong.
[EVO 4G Android Development] :
is there any new leads to the real source of the 30fps cap?

when the official source dropped toast remarked how sloppy HTC's hdmi code was, wondering if there were leads there?

http://pastebin.com/h7TQiv5a
[EVO 4G Android Development] daneurysm:
I was going to return my Evo for a new one...I'm on the list, I'm buddys with the guy at RS. But I don't think I will anymore, even with light leakage. I got one of those gel skins for it and I don't even see it anymore.

But the real reason is that I have a Nova panel and I love the performance. I have Wifi working (it doesn't worked on Baked Snack but it does on Fresh, no tweaks), ~44fps, smooth as silk, JIT, 1.2ghz _stable_...I'm one of the lucky very few apparently. 9mflops, give or take an mflop or two depending on whats running...~40mflops with JIT on froyo, give or take 5mflops.

EDIT: I dunno if 4g works, not in a 4g market...yet, and who knows if I broke it with all of the flashing I've done.

This phone is just so badass. I get pretty decent battery life too, I have screen-off set to 128/128, I think that helps. Though it reacts a little funky for a second when I turn the screen on. I can cope with that.

I have been tweaking the T2 settings and I can't find any rhyme or reason for the wildly differing performance (FPS vs screen tearing vs std. dev etc). Sometimes a difference or 1 or 2 past a previous setting causes completely different results, and from what I've read it seems that all phones don't seem to get the same results from the same settings, though that may be a matter of perception and preference.

Anyone have any theories as to the meanings of the differing range of settings?
[EVO 4G Android Development] rjmjr69:
Anyone have an asnwer as to maybe why this kernal doesnt completely flash? I get some of the features but not all? No multi touch for one no increase in fps
[EVO 4G Android Development] d3xn2o:
For Some Reason Everytime I Flash it Breaks Wifi... Any Ideas?
[EVO 4G Android Development] kthejoker20:
its funny how many posts i read about wifi not working.

If people actually read all the directions on the first post, it would tell you to expect that.

Then download the wifi-n .zip file below the kernal file on the first post, and flash that after you flash the kernal. Wifi will then work.
[EVO 4G Android Development] nugzo:
Anybody else having problems getting this to work with Avalaunchmods Froyo/Sense Rom? I get boot loop with UV and regular kernel.
[EVO 4G Android Development] :
hmmm after about 6 hours of underclock kernal, started getting reboots (was laying in bed and saw my phone lite up). rebooted like 3 times in a row, finally stopped and the top menu bar was missing, widgets werent working, all sorts of problems.

002

fresh .53

underclock kernal (didnt touch cpu settings)

evoswitch set to 248 (was getting 41fps with stdev of around 7)

was getting the 5 finger touch

gonna try the non clocked kernal now
[EVO 4G Android Development] ilovemytilt1:
Just to be sure this only works on novatek panels, correct?
[EVO 4G Android Development] DeMiNe0:
I'm running the latest Fresh Rom 1.0 Beta with the Newest OTA, Radio and WIMax integrated in it. I'm not sure what kernels I need to flash. Also is there a guide on flashing kernels here?
[EVO 4G Android Development] jabbawalkee:
I see that you can type...so I'm assuming that you can also read. Look at the title of this thread, question answered.
[EVO 4G Android Development] mrono:
Hw 2

DC 3.2.3

Undervolted kernel

T2 - 244

Fps - 42

stdev - 7.79

Works like a dream
[EVO 4G Android Development] katmandu421:
Just wanting to post a thanks. Undervolted kernel along with setcpu profiles for underclocking during screen off and <20% battery remaining has resulted in INSANE battery life. Over 24 hours.

Flashed over Damage Control 3.2. Hardware version 002. 46fps average WITH ondemand profile (vs the suggested performance setting) in DConfig. No wifi issues, but I had flashed a wifi-n .zip previously over this ROM. Cannot comment on 4G since I am not in market.

Great work! The current best phone just keeps getting better, and with this community I'm sure will remain a viable competitor for many, err... months, to come.
[EVO 4G Android Development] topdnbass:
Don't be so sure..

I did everything exactly right and it still broke my wifi..

EDIT: Got it working by wiping and redoing everything.

Seems to be flawless!
[EVO 4G Android Development] EtherealRemnant:
Don't be a ****. 4.2 and prior builds off of toast's source worked... I'm using 4.2 right now on my EPSON panel. 56FPS thank you very much.
[EVO 4G Android Development] kpkimmel:
Using t2v4 with evo set to 361 and 55 fps
[EVO 4G Android Development] kpkimmel:
Hey ffolkes can you incorp v4 with cam functio, want to try out on froyo too
[EVO 4G Android Development] jayjay7411:
Moving up :-)
[EVO 4G Android Development] topdnbass:
That seems like a sweet spot, i'm getting avg of 41-42 with very little deviation (6.75-7.36) on the normal volt kernel.

Not as much FPS as some other settings but it's worth it for the tight stdev.
[EVO 4G Android Development] kpkimmel:
Tweaked v4 to 373 and get 56 fps and stdev of 5.03
[EVO 4G Android Development] miguel11691:
if i install this kernal to a froyo rom will my camera work?
[EVO 4G Android Development] topdnbass:
Performance wise, looking much better than before..

When overclocked to 1075MHz (performance scaling)

I'm getting ~550 on quadrant, and 13.7FPS on nenamark.

Ill try and get some more out of it, soon..

EDIT: Wow getting 45+AVG with stdev of 6.21
[EVO 4G Android Development] freeza:
Hi, can this be used on fresh 0.3?
[EVO 4G Android Development] neles86:
Yes, i have it on my Fresh 0.5.3 working smoothly. But i had to change the T2 to 248 to have everything lag free. It might not be the case for you.
[EVO 4G Android Development] dkotoric:
well I just tried using this with the 2.2 froyo winse sense thats out and now my phone is just sitting at the startup screen. I have reflashed the stock kernel but its still just sitting at the startup screen. I'm flashing a different rom now to see if it will start.
[EVO 4G Android Development] rustyman14:
Im running EVOlutions X2 Rom with your 4.2 Kernel (Cause i have the Epson Panel) I scored 1409 on quadrant, 45avg Mflops, 45avg FPS, And Nenamark was 13.5... This is the best setup so far...
[EVO 4G Android Development] hdad2:
Curious about this as well. We all think/hope it can be truly fixed and I don't want to sound ungrateful for the awesome kernels we have. But I'm hoping for a tease or something indicating that more than a "dirty hack" suggested in the OP is possible.

Any update or glimmer of hope?
[EVO 4G Android Development] wphend00:
OK, can I get a lil bit of help...

I have a one of the baked roms that includes the OTA updates (1.47)... which files doa I download.
[EVO 4G Android Development] itmustbejj:
"one of the baked roms" does not help. One is froyo based and one is eclair based as are the kernels on the first page. Find out which one you are using and use the correlating kernel from here.
[EVO 4G Android Development] wphend00:
Sorry, let me re-iterate, I have baked snack's rom version 9, which includes the recent OTA updates.

It is an Ecliar rom.

Do I grab the Eclair 5.1.1 patch, and is that all I need?
[EVO 4G Android Development] itmustbejj:
and the wifi patch. Did you read the first post? The instructions section clearly covers all this.
[EVO 4G Android Development] jayv1717:
60fps possible or not???????
[EVO 4G Android Development] kennyc1:
eventually, maybe.
[EVO 4G Android Development] sracercelica:
I seriously doubt it! I had read that maybe once the source was out, but the source has been out for about a week now and still no hint of a possibility.
[EVO 4G Android Development] kennyc1:
dev can't fix the 60fps in the first week then all hope is lost!!

Common everyone! the source just came out. let's be reasonable here.. these people have jobs and other thing they do then just coding 24/7. Give them some time and breathing room.

I am a complete noobie at this. I rooted my evo for the first time last night @ 11pm. Even I know asking for a solution that HTC can't get right within the first week of source drop is a little outrageous.
[EVO 4G Android Development] strung:
No, 60fps not possible. Close thread.
[EVO 4G Android Development] itmustbejj:
so has anyone made any progress with devices not getting the 5 touchpoints working on the 5.1.1 kernel?

I am dying to try it out with snesoid!
[EVO 4G Android Development] mastermayhm:
with froyo and its kernal i get stuck in a boot loop.

with enclair kernal it boots but camera broken
[EVO 4G Android Development] freeza:
Hi,

Will this kernel mess up apps2sd or compcache or any other enhancements to a previous kernel?
[EVO 4G Android Development] hdad2:
I don't think anyone wants to be unreasonable and I for one definitely take my hat off to the awesome devs for what we've got.

But I cant help be curious if anyone is on to something more intriguing with finding the real cap. There is of course the possibility that the cap is not in the kernel. In which case what we have is not bad at all. But a little tease or update would be cool. At least I want to imagine people much smarter than me on some irc chat somewhere trying to figure this thing out. I'm just still hoping the cap IS in the kernel. :)