yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] AssassinsLament:
OMG, it does work... but the thing I found out is... all my testing has amounted to nothing because I only saw the fps go up AFTER putting the phone to sleep and waking it back up. So what this means is there definitely is a default setting that is getting called that's not part of the init.

Yes yes, who ever said that earlier was right. It is definitely loading some default settings elsewhere other than the init, like a bios of sorts.

With the above settings, I amd averaging 41fps with stdev at 5.87
[EVO 4G Android Development] ffolkes:
indeed. but that's no big deal, it only needs to be done once per boot, and can be stuck into the panel init stuff so it will happen automatically.
[EVO 4G Android Development] AssassinsLament:
Yeah, we could basically call the function at any time. Time to try to milk out as much fps as we can.
[EVO 4G Android Development] ffolkes:
there's still something holding us back. when you fill in the default numbers for that equation, you get ~60fps as your result, whereas we see only 30fps. when you fill it in with the number (~250) that gets you 40fps actual, you get a theoretical 80fps. both are almost exactly half. i think somewhere a clock is being divided still.
[EVO 4G Android Development] AssassinsLament:
Yeah, I was just about to post that, because I got around 80 in theory too. Something definitely is eating up around half the clock.
[EVO 4G Android Development] ffolkes:
anyone know of any (free) games for me to try out so i can see if they refresh alright?
[EVO 4G Android Development] joeykrim:
doing a quick google search for games with high fps and htc mentioned, found this - Raging Thunder light - free in the market

heres the article - http://pocketnow.com/software-1/video-htc-legend-high-fps-game-demo

hopefully that helps! great job with all the work!
[EVO 4G Android Development] halfline:
Remember what I quoted earlier?

"The NT35582 is able to change the liquid crystal polarity inversion cycle by setting the DIV, RTN bits to change the frame frequency. Setting a lower frequency in the partial display operation will reduce power consumption."

Also,in that datasheet it mentions:

"Reverse Rate Divisor: reverse data rate = reverse link data clock"

So, maybe that is slowing down replies from the panel to the host. Note in mddi_hw.h:

#ifndef CONFIG_ARCH_QSD8X50

#define MDDI_HOST_REV_RATE_DIV 0x0002

#else

#define MDDI_HOST_REV_RATE_DIV 0x0004

#endif

So it's even set to 2. 80 DIVided by 2 = 40, 60 DIVided by 2 = 30

Anyway, just a random guess.
[EVO 4G Android Development] geyes30:
So yesterday I was thinking that the slow down can be done in 2 ways

1. A fixed delay after every frame/line; or

2. Halving the refresh rate by some other means, after reading the refresh rate from the device.

So based on the numbers you have given, it seems like the latter is true, since the frame rate is not offset by a fixed delay (which would be the case if the former were true). Now based again on the mddi_hw.h file that was pointed out, that might make sense, though the settings should apply to Incredible as well, which means that the native refresh rate for the AMOLED screen might be 120fps?? Not sure about any of this.
[EVO 4G Android Development] sheffield:
Tried this.

#define MDDI_HOST_REV_RATE_DIV 0x0001

#else

#define MDDI_HOST_REV_RATE_DIV 0x0002

30FPS (T2@340)

30FPS (T2@250)

Also, there's the following in mddi_hw.h

#define MDDI_REV_RATE_DIV 0x002c

Tried halving this to 0x0016 and the kernel wouldn't boot.
[EVO 4G Android Development] ffolkes:
interesting idea, but setting this to 0004 does nothing, 0001 won't boot.
[EVO 4G Android Development] ffolkes:
the hero doesn't have any fps limit, and it has the same value, so that can't be it.
[EVO 4G Android Development] ffolkes:
i don't see how anything can be in the mddi*.* files, since they are the same exact files that handle the epson panel without any limits.
[EVO 4G Android Development] toastcfh:
Well epson uses mddi but not the same way nov panel does. We had to make mddi.c was actually the thing stopping us from booting after we had reversed the panel code. Look at the commits and ull see what was changed in mddi.c and such.

Btw are these frame rates only going up in 2d or 3d as well using the hacks for nov panel?
[EVO 4G Android Development] Estimated Prophet:
That sounds right. 120Hz is a pretty common refresh rate for AMOLEDs.
[EVO 4G Android Development] kpkimmel:
Quick thought, might be stupid but maybe the reason we get high frame rates when we lock or unlock is because it thinks its switching to hdmi out and so the fps shoots up?...mane the hdmi is canceling the 60 fps somehow... sorry if that's sounds stupid
[EVO 4G Android Development] Estimated Prophet:
I'm not sure about that. I think you have to plug in the hdmi cable and reboot the phone to get it to switch to hdmi out.
[EVO 4G Android Development] kpkimmel:
Well maybe it thinks to check hdmi out when the screen goes black...know my old asus used to do that..maybe disabling hdmi might help .well just an idea sorry
[EVO 4G Android Development] Cicatrize:
We've already tried this...completely removing all HDMI init...nothing happened, except we lost HDMI. :)
[EVO 4G Android Development] kpkimmel:
What if we try this.....................smash the nova screen on the floor really hard 3 times...get it replaced with new epson panel and poof problem solved..:0)
[EVO 4G Android Development] ffolkes:
i can't believe i've been at this for just about 16 hours straight. i never even ate dinner tonight - kept putting it off "let me compile it *one* more time first...", etc.

i agree it seems something is being halved somewhere, but until we can figure out what/where, this should satisfy those of us with novatek displays.

stock: average of 29 or 30fps 2d | neocore average of 22fps

now: average of 55 or 56fps 2d | neocore average of 27.3fps

real world results: interface is snappy, when grabbing the home screen (i use launcherpro) and swiping back and forth it's very tight - no more sloppy elastic feel. lists and other ui elements have an iphone-like snappiness to them. no idea if this will significantly affect battery life or not.

raging thunder lite v2 w/ stock: choppy, dropped frames every few seconds, jagged edges.

now: smooth motion, no dropped frames ever, smoother edges (might be just because of the faster frame rate)

multitouch visualizer w/ stock: finger could get disconnected from the touch point by as much as an inch or so from the yellow circle.

now: crosshair point lags by no more than 1/4", never ever outside of the yellow circle though.

the only down side i've noticed, is with things that fly by, like lists flicked as quickly as possible, it seems to refresh...for lack of a better word, awkwardly. (aka feedr, open a feed with a lot of items, and flick down once). hard to explain. but definitely tolerable compared to all the positives.

i'm going to post a boot.img for use with flipz .3 rom so people can give it a try and see how it works for them.
[EVO 4G Android Development] Cicatrize:
Nah. I like the colors of my nova display.
[EVO 4G Android Development] Cicatrize:
Awesome work man. Post it up and I will flash to check it out. Are the problems like screen tearing issues?
[EVO 4G Android Development] kpkimmel:
if you could make it damage control compatable i'll flash it and let you know of any issues..also will donate to anyone who makes this possible...oh yea....i was joking about smashing your nova screen...i think mine looks better than the epson too..
[EVO 4G Android Development] Holyrolla:
Soooo, are you saying that with the Epson and Nova phones reaching 50-60 fps, that is still being halved and the phone is capable of more? So if that "halving" is removed, we could have vsync'd 60 FPS on both phone displays?
[EVO 4G Android Development] Cicatrize:
Yeah, I think that's what he's saying essentially. I think what's happening with the Epson and probably with ffolkes' nova method is a little trickery in the panel code, but the cap is still going on elsewhere. We won't know for sure until the official kernel is out or we finally figure it out.
[EVO 4G Android Development] joeykrim:
i know the feeling but you gotta eat and sleep!

thanks so much for the dedication to tweaking, compiling, testing and repeating!

look forward to the boot.img!

would it be possible to post the board file/files you modified or push them to toast's git? thanks!!
[EVO 4G Android Development] Cicatrize:
Where's the img at, ffolkes? :)
[EVO 4G Android Development] amw1972:
+1 to this...I would be VERY satisfied if I'm in that 50-60FPS range. I have no reasons to complain about the fps to begin with since I'm coming from WinMo...but anything to better our devices!!!

about the .img, will it work with a 2.2 ROM...I'm running EVOV8 RevA. Also I'm assuming that its an .img that I can flash on top of my ROM without affecting (hopefully) anything else?
[EVO 4G Android Development] joeykrim:
prob passed out from lack of food and sleep ... poor guy! im sure when he comes to, he'll get them posted!

i'm very interested in seeing the modified board files for the final solution. feel like this was a really hard homework problem and i wanna see the solution finally!
[EVO 4G Android Development] joeykrim:
boot.img is two parts, kernel-zImage and ramdisk.img.

the kernel-zImage will prob work with froyo and all other ROMs.

but some ROMs, including froyo, might need a custom version of the ramdisk.img portion.
[EVO 4G Android Development] ffolkes:
this should work for everyone. that is to say, it leaves epson panels alone, and only changes the vpa of novatek ones. to be honest i have virtually no c programming abilities at all, but i think i've figured out how to set the vpa upon boot so there's no confusion about cycling displays. it's working for me. yes, it does check the panel type before sending out the new vpa, but someone with an epson panel try it out and see if it has any undesirable results - ideally you should notice no difference since it should be ignoring you and your panel. :P

keep in mind when you boot, don't expect to see 55fps right away - there's too much system activity going on, you'll see 50ish. then in a minute or two, if you run fps2d a few times, you'll start seeing fps in the 55-57 range.

THIS ISN'T FLASHABLE YET!

-----------------

unzip it, copy it to your phone then

./adb reboot recovery

./adb push boot.img /tmp

./adb shell

cat /dev/zero > /dev/mtd/mtd3

flash_image boot /tmp/boot.img
[EVO 4G Android Development] kpkimmel:
please clarify these steps for me..kinda slow right now..
[EVO 4G Android Development] amw1972:
thanx...think when its ready...I'm still gonna give it a shot...that's what nand backup is for right?

unless...I'll be unable to boot into recovery...then I'll have issues...:cool:
[EVO 4G Android Development] Cicatrize:
WOW, ffolkes. I just did a fastboot boot boot.img on it and ****...it seems SO MUCH more responsive. Good work. This is definitely a good start.

Touch frequency is registering around 40Hz now instead of 30Hz too. great.

EDIT: You can definitely tell while running FPS2D that something in the system keeps trying very hard to drag it down. I'm getting around 40fps because it keeps slowing down a lot.
[EVO 4G Android Development] kpkimmel:
so i copy to my sdcard and then what.....i'm confused...
[EVO 4G Android Development] Cicatrize:
Just use fastboot. Much easier.
[EVO 4G Android Development] kpkimmel:
how the hell do i do that..
[EVO 4G Android Development] ffolkes:
signed zip is coming shortly. then you can just flash it like you would any other flashable zip. i'm just testing it first..
[EVO 4G Android Development] Cicatrize:
Dude I don't know what's going on but this is so weird. In fps2d, you'll see it go steady 60fps for a while and then it'll get YANKED down to 30 fast as hell and stay there for a while, then the ball will fly again and it'll go to 60fps for a sec, then get yanked down to 30. I wish I knew why it did this... :(

ffolkes, can you please fork the git and put your files on there?
[EVO 4G Android Development] kpkimmel:
drag the boot.img to my sd card..power down, hit the volume down key and power...then i see fastboot..i select and nothing happens..
[EVO 4G Android Development] ffolkes:
here's a flashable zip. just copy it to your sdcard, reboot into recovery, and flash the zip.

this will overwrite your boot image obviously, so if you want to go back you'll have to either manually reflash the boot.img from your existing rom, or, simply do a nandroid backup first. :P
[EVO 4G Android Development] jblazea50:
you are doing it wrong; you need to boot into fastboot mode; have the phone plugged to the computer; open up command prompt from the location the boot.img is saved and fun the command "Fastboot boot boot.img"
[EVO 4G Android Development] kpkimmel:
thanks you gentleman...may God and peace be with you all your days..

EDIT: Doesn't work on Damage Control rom..still at 30fps
[EVO 4G Android Development] davidlightle:
It sounds like periodically something is trying to latch the panel back to 30 FPS, but shortly after, the kernel changes kick back in (in layman's terms).
[EVO 4G Android Development] Cicatrize:
This is what I'm getting pretty consistently:
[EVO 4G Android Development] luisrcastillo:
No changes for me. I'm getting 29 FPS in FPS2D
[EVO 4G Android Development] drbadass:
Just want to say thanks you guys for all your hard work-- you have probably saved a couple of major telecom companies a lot of money, they should put you on payroll!

If there's anything you need from a stock 0003 handset w/ a nova I would be happy to give a shot. :)
[EVO 4G Android Development] Cicatrize:
Yes. Do a full root and flash Fresh 0.3 and try this boot img. ;)
[EVO 4G Android Development] ffolkes:
to be honest, i have no idea what forking a git is lol. i'm not familiar with version management stuff. and the changes i made were very simple. it took hours and hours to try different things, but it was only one thing that worked best.

earlier we found that setting T2 to around 250d was getting us 40fps. i later realized leaving that alone and setting vpa to 41d got me around 55fps. vpa is the porch setting, which is the amount of blank lines added to the panel height beyond what the lcd actually can display. essentially this is making it think the display is a total of 841 lines tall. honestly i think it's a coincidence the framerate is going up - this is a dirty hack in that it really isn't addressing the problem, it's just screwing with the timing somehow, and getting higher framerates in the process. ideally when someone can find where the framerate is getting cut in half, we can leave all these timing settings alone, as they default to 60fps already.

and no, if you're wondering, changing T2 on top of vpa doesn't get even higher framerates, it just drops them back down to ~40fps.

essentially i'm just adding:

{0xb100, 0x29}, // VPA (29h = 41d)

to nov_init_seq[] and then adding a little bit of code at the end of mddi_probe in mddi.c to set the vpa there, otherwise you'd have to turn the display off, then on again to get it to flush nov_init_seq[] to the controller, since that array is only used when the display is reinitialized after it's gone to sleep.
[EVO 4G Android Development] kpkimmel:
how to you get a screen shot from your phone?
[EVO 4G Android Development] kpkimmel:
installed fresh 0.3 installed boot img and nothing..still at 29 fps
[EVO 4G Android Development] ffolkes:
is yours a 0002 with a nov panel, or a 0003 with a nov panel?
[EVO 4G Android Development] luisrcastillo:
Mine is a 0003 with Novatek and got the same results
[EVO 4G Android Development] kpkimmel:
002 with nov
[EVO 4G Android Development] ffolkes:
do you know how to check your dmesg?
[EVO 4G Android Development] kpkimmel:
yes, checked and says nov
[EVO 4G Android Development] ffolkes:
do a recent one, then check for "mddi: setting VPA to 41" near the top, after the panel is registered.

also, try turning the display off (button on top) then on again and see if the fps changes afterwards.
[EVO 4G Android Development] wildgillis:
I have a 0002 and stuck at 29 stdev= 3.35

Fresh 0.3 full root.
[EVO 4G Android Development] jblazea50:
wow, this is simply amazing how fast you guys got this to work; i ran the update.zip on DamagedControl 3.2 rom and i'm getting around 50fps; although it does try to drop to below 30fps at times
[EVO 4G Android Development] kpkimmel:
give me a step by step for the fastboot method..maybe thats the only way it works
[EVO 4G Android Development] luisrcastillo:
I have tried that a few times and it doesn't work for me. I'm running fresh 0.3. Here's what I got on dmesg:

<6>[ 3.864868] mddi: init() base=0xdb860000 irq=16

<7>[ 3.865112] mddi runs at 384000000

<6>[ 3.865295] mddi cmd send rtd: int 2a000, stat 8023, rtd val 6

<6>[ 3.865356] mddi: registering panel mddi_c_b9f6_5582

<6>[ 3.865356] mddi: publish:

<6>[ 3.865539] mddi: setting VPA to 41 (29h)...

<7>[ 3.866088] mddi_novtec_probe
[EVO 4G Android Development] EliWay:
Those having trouble with getting it to work with novatek displays, Start from scratch and it should work.

- Go to recovery

- Do a nandroid backup [optional]

- Wipe data and dalvik cache

- Flash Fresh 0.3 rom

- Reboot phone, finish OS customizing/setup process, turn phone off.

- Go to recovery, flash novfps.zip , dont wipe anything

Restart phone
[EVO 4G Android Development] Tikerz:
I have a 002 and I'm averaging 50fps in fps2d.

Last run: avg=50 stdev=12.46.

Flashed over Evo .3.
[EVO 4G Android Development] kpkimmel:
no go....won't go above 30 fps...
[EVO 4G Android Development] P_Dub_S:
Working great for me thank you for the beta fix.

Upon testing this breaks video playback I cant even get my videos to load gonna try a reboot.
[EVO 4G Android Development] jblazea50:
i don't think you have to be on Fresh0.3 Rom to try this; i'm on DC3.2 and it worked; i wiped the cache then flashed via recovery and it works fine
[EVO 4G Android Development] P_Dub_S:
After rebooting my videos showed up but when you go to play them its just sits at a blank screen. Youtube is broken as well.
[EVO 4G Android Development] kpkimmel:
some one tell me how to do a screen shot of my phone and i'll post the info i have for ffolkes
[EVO 4G Android Development] apristel:
try searching just the slightest...probably why nobody answered the first time.

get shootme from the market.

thanks.
[EVO 4G Android Development] sweteg:
I'm new to this FPS thing, but I did flash the boot.img.zip from recovery. I downloaded both Gears and fps2d and my average is 53 if that helps. Test 2 with fps2d gave me 54. I'm fully rooted using Fresh 0.3.

edit 1: Have a nova screen (no issues), 0003.

edit 2: Youtube works fine. Did force quit on first try, but works fine now.
[EVO 4G Android Development] splink7007:
Look for drocap 2 in the market for you screen shot app.
[EVO 4G Android Development] ffolkes:
i agree. because now that i think about it, the ramdisk i'm using (a boot img consists of a kernel, and a ramdisk) is from stock anyway. i forgot that the last time i unpacked it was when i was running the stock rom.
[EVO 4G Android Development] ffolkes:
P_Dub_S, youtube works for me, both low quality and high quality. i see gallery chokes on video *taken with the phone camera app* (obviously from stock kernels, since toasts doesn't support cameras yet). it went blank for me, then crashed, now it loads the video but stops on the first frame. however it plays my saved qik videos perfectly. it must be something with that codec.

edit: i see when i reboot, i get the blank screen for any type of movie in gallery. but once gallery force closes, and is restarted, it can view qik videos. idk what's going on. :/
[EVO 4G Android Development] tyrnight:
Im on 002 Nov. and I applied ffolks zip on Damage rom and I cant get past 29fps..

actually swiping on the rosie seems slower.. not sure why..
[EVO 4G Android Development] geyes30:
Has anyone who has tried the fix installed Quick System Info Pro from the market? It has some information about the refresh rate, so that might let us know if something at the driver level has changed.
[EVO 4G Android Development] P_Dub_S:
It must be early cuz I didn't even remember that this is based off toasts kernel which has cameras broken which will break the video gallery.

I tried another reboot and this time when i went to turn on my screen I had a green looking fuzzy picture with vertical lines over the screen. I put my screen back into sleep then and the second time waking it my picture returned. I tried playing another youtube video and it just sat at loading video but nothing ever plays and the screen just sits there blank.
[EVO 4G Android Development] joeykrim:
used: novfpsboot-signed.zip

hardware: rev 2 novatec panel

rom: joeykrim - 1.0.8

kernel: Matrix@MacBookPro #112

Fps2d: #1 - Avg=53 stdev=13, #2 - avg=54 stdev=11.99, #3 - avg=55 stdev=10.72
[EVO 4G Android Development] kpkimmel:
this **** is mindboggling........same hardware..works for some and not for others..go figure...HTC
[EVO 4G Android Development] wildgillis:
just finished still at 29 FPS
[EVO 4G Android Development] frankenstein\:
I'm running Flipz stock OTA updated rom (.6) which he rooted and released shortly after the OTA came out. I've cleaned up much of the sprint bloat but it's still pretty much stock beyond that.

I've got 0003 HW rev. and nov display. Doing fastboot boot boot.img to test. The boot image is copying over and the phone boots fine.

FPS2D is giving me 29 fps avg on multiple runs. I've cycled the display and run it again several times and it continues to avg 29 fps.

I have Evo's froyo 8 rev a rom in nand but haven't tried that yet. I'll have to wait to try it as I have a job interview to go to but I'll post results for that when I get back and give it a try. I'll also give Fresh .3 a try when I return as well.

I've learned a good deal following this thread and would like to thank everyone who's working on this for their efforts!!!
[EVO 4G Android Development] ffolkes:
tyrnight, wildgillis, kpkimmel, what radio are you guys using?
[EVO 4G Android Development] kpkimmel:
.5.31

the newest one
[EVO 4G Android Development] apristel:
I tried it on Damage and Fresh.. 30fps stiill ..

running Radio Evo-1.39.00.05.31 (06/06/2010)
[EVO 4G Android Development] ffolkes:
for what it's worth:

the sense home screen still has that annoying elastic effect. if you're running fresh 0.3, you already have launcherpro installed, so go to settings->applications->htc sense and press Clear Defaults. now press your home button, and choose launcherpro. enjoy how tightly the sliding action is tied to your finger now. :D
[EVO 4G Android Development] wildgillis:
The newest one as well
[EVO 4G Android Development] tyrnight:
Yup same here..
[EVO 4G Android Development] crackerstyle:
I'm also on 002 Nov..

I am using joeykrim's 1.0.6 rom and I flashed the signed zip on page 49. I just got 51 FPS average in fps2d. Great work ffolkes!
[EVO 4G Android Development] mdaddy:
I just flashed over EVOlutionV8-Froyo-RevA:

HW: 0002

Panel: Nova

Did not wipe data or dalvik-cache

Result:

-FP2D quickly jumps out to ~55 FPS then immediately gets throttled down to 30 FPS.

-Entire system unstable, random reboots, apps force closing

...perhaps I should wipe.
[EVO 4G Android Development] abiezer:
For the ones who have done this, are you getting screen tearing like with the Epsons?
[EVO 4G Android Development] vinscuzzy:
Biggest places i've noticed a difference, is in emulators and multitouch visualizer. Snes emulator with 0 frames skipped runs beautiful, and multitouch visualizer has almost no lag now. Haven't noticed huge differences in scrolling menus, but animations when switching apps is much smooher now. Awesome, awesome work!
[EVO 4G Android Development] itzjonjon69:
Running Fresh's 0.3 + the kernal code from page 1 and im still stuck at 29 FPS, whats this 002-003 novatec etc etc talk? how do i check what mine is?