yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] EtherealRemnant:
Nova 0002 - locked at 30 FPS on DC 3.2

Installing Fresh right now.

My radio is the stock radio... so that's not the issue since everyone else has the newest and still has problems.

EDIT: Are you guys flashing with AmonRa or ClockworkMod? That seems to make a difference at times.
[EVO 4G Android Development] kpkimmel:
for the people without the cap..you can suck it....soooooooooo jealous:cool:...
[EVO 4G Android Development] vinscuzzy:
I haven't noticed any at all. No visual glitches what so ever.
[EVO 4G Android Development] abiezer:
OK Damn IT! Now I'm pist! I'm getting screen tearing specially when switching between screens and having the HTC clock on the screen. I have the Epson. So no tearing for you guys?
[EVO 4G Android Development] vinscuzzy:
Clockworkmod for me.
[EVO 4G Android Development] kpkimmel:
clockwork...i would use fast boot..but don't know how..
[EVO 4G Android Development] tyrnight:
No tearing.. 002

Using clockwork, due to the signing issue on RA
[EVO 4G Android Development] mdaddy:
Factory wiped, instability continued..
[EVO 4G Android Development] sweteg:
I'm using the default HTC clock/weather and main screen. Scrolled back and forth between the screen and no tearing.
[EVO 4G Android Development] EtherealRemnant:
No change on Fresh either. In fact I went from 30 FPS average to 29 now... consistently.
[EVO 4G Android Development] vinscuzzy:
I can't imagine what this phone is gonna be like when froyo is released and htc officially removes this cap(if they ever do).
[EVO 4G Android Development] Tikerz:
None for me either. It's working great. I'm trying out some games and definitely notice a difference in speed and playability.
[EVO 4G Android Development] tyrnight:
I also tried 2.2 with the patch.. It doesn't like it
[EVO 4G Android Development] AssassinsLament:
Good work ffolkes, get some sleep!

Ok for everyone trying this out, this still isn't a good solution, but it should hold everyone over until we can find where HTC is halfing our fps or until we get the source code from them. But the important part is that it can be done!
[EVO 4G Android Development] EtherealRemnant:
So what's the issue with those of us it DOESN'T work for?
[EVO 4G Android Development] Holyrolla:
May be extreme, but go back to factory settings...reprotect the NAND, unRoot, stock kernel, and flash the stock ROM.

Then go through the Root, Recovery, and NAND unprotect process again and flash the new kernel and a rooted ROM and see if it changes anything.
[EVO 4G Android Development] AssassinsLament:
I'm not sure, in theory it should. All Novatek panels should take the init changes. Have you guys tried putting the phone to sleep then waking it back up and testing fps2d again? I know ffolkes had set it to start automatically but it's worth a try.
[EVO 4G Android Development] crackerstyle:
I don't think I used either? I just rebooted my phone into the standard recovery console where you do nand backups and just flashed the zip from the sd card.
[EVO 4G Android Development] EtherealRemnant:
I see the command right here...

mddi: setting VPA to 41 (29h)...

mddi_novtec_probe

This kernel is supposed to be WITHOUT VPA, correct?
[EVO 4G Android Development] Varo210:
OK, I'm running stock rooted and nand unlocked with clockworks custom recovery. Flashed the .zip file and I'm getting:

Done avg=46 stdev=14.86

I've got an 003 nova.

Outstanding work!!!
[EVO 4G Android Development] Jykinturah:
You probably have Amon_Ra.
[EVO 4G Android Development] crackerstyle:
if you go to settings -> About Phone -> Hardware information it will be the Hardware version.

If it says 0002 you have 0002 and nova, if it says 0003 you could have either, and I'm not sure how you check that.
[EVO 4G Android Development] crackerstyle:
One thing I've noticed now is Quadrant seems to hang on the last item on CPU.. Video compression or whatever. Other than that this runs great and I love it :)
[EVO 4G Android Development] timgt:
AMAZING WORK!! I am getting 54FPS in fps2d. However, if I play doodle jump it is soooo choppy to the point of making me naucious.

Works great for 2d it appears but still needs some work for 3d. All around great improvement (just not on doodle jump)
[EVO 4G Android Development] EtherealRemnant:
I'm trying to do the manual version using adb and it is giving me a no room left on device error when I run the cat /dev/zero > /dev/mtd/mtd3 - anyone?
[EVO 4G Android Development] dteze88:
Avg 43 stdev 18.86

003 nova. Running joeys rom v7 full root/nan unlocked. I just flashed it right over the rom, after a nandroid of course. I didn't clear the cache or do a wipe either. It does break camera. Thanks everyone!
[EVO 4G Android Development] joeykrim:
off the top of my head, sounds like nand protection
[EVO 4G Android Development] apristel:
Well,

I've tried on Damage and Fresh, no go.

I also tried flashing it with Amon Recovery and Clockwork... notta.

Radio Evo-1.39.00.05.31 (06/06/2010)

Wonder what the dealio is?
[EVO 4G Android Development] EtherealRemnant:
I've unlocked NAND... Unless there is something that overwrites it...

I've been using custom kernels like crazy - that wouldn't work if my NAND was locked, would it? Nor would DC's JIT ROMs...
[EVO 4G Android Development] amdchip:
So from looking at the posted results here it appears 002 nova are averaging about 10fps higher than the 003 nova with this fix?
[EVO 4G Android Development] joeykrim:
i would suggest doing it from recovery mode.

the other method is to use the flash_image tool. thats what i do as opposed to manually loading into the partition.

flash_image boot boot.img
[EVO 4G Android Development] EtherealRemnant:
When I did that, it said something about a bunch of zeros and being skipped.
[EVO 4G Android Development] crackerstyle:
Well, I just had to restore back prior to the patch. I went into the gallery and my phone froze. After that it wouldn't boot, it would just hang at the htc evo 4g screen prior to the sprint bootloader screen.
[EVO 4G Android Development] EtherealRemnant:
I updated to the latest radio... no change...

Is the kernel version: 2.6.29-a2443432

Matrix@MacBookPro #112

??

EDIT: Definitely NAND unlocked - created and removed a folder on /system using adb shell.

EDIT 2: Nevermind, looked back. Its running the kernel, setting VPA, and it is having no effect on the frame rate cap except making it 1 frame worse than it already was.
[EVO 4G Android Development] jayv1717:
Not working for me either..just my luck..still capped at 30..i have 002
[EVO 4G Android Development] Cicatrize:
This is just the kernel. The adjustment ffolkes made didn't do that.
[EVO 4G Android Development] gerald410:
nova 2 running fresh v3 no change thanks for the effort anyway
[EVO 4G Android Development] Jykinturah:
Just flashed it and it works. Hardware revision 002, nova. Win7 64bit

I used Amon-RA recovery.

Nandroid backup.

Wiped everything. (Data, cache, dalvik)

Flashed fresh 0.3, rebooted.

Set everything up. (Google account, downloaded FPS2D, multitouch vis)

Rebooted into recovery via 'adb reboot recovery'

Flashed kernel, rebooted.

Delicious uncappedness.
[EVO 4G Android Development] toastcfh:
Do a git diff and pastebin it for reference please
[EVO 4G Android Development] crackerstyle:
Unless joeykrim used a custom kernel in his rom, I'm using the stock one. Oh well.
[EVO 4G Android Development] joeykrim:
+1

if you dont have a chance to setup the git, etc. i do have git setup and forked. if you wanna post/attach the two files, mddi.c and board-supersonic-panel.c you modified here, i can push them back to toast's git.

heck, toast could do it himself if the two modified files were attached here.

im hoping this "dirty" hack will give us some momentum in the right direction!

thanks ffolkes!

i didnt.

as an FYI, if you flashed the modified kernel posted here with the fps hack, it would overwrite any other boot kernel.
[EVO 4G Android Development] wuclan48:
tried this on an 0002 build running fresh 0.3. Averaging 47fps. BUT anyone else notice you cannot access anything on the SD card? Wallpaper, music, files etc.
[EVO 4G Android Development] Jykinturah:
Isolated case. Everything for me works fine, except camera which won't work with any customized kernel currently anyway.

Attempt reboot?
[EVO 4G Android Development] EtherealRemnant:
I'm attaching my dmesg log... Maybe something in it shines light on why it doesn't work on my device.

EDIT: Attached HTML version. Txt version is a mess.
[EVO 4G Android Development] joeykrim:
i seriously take offense to that but i accept the apology. not sure what exactly you were linked to, but my work has absolutely nothing to do with him. in fact, i started compiling kernels because i strongly disliked his attitude and subsequently his results.

i appreciate your reply and openness to further work on the kernel. i'll do my best to help out where i can. i dont feel like i can be very detailed cuz i dont even own the phone yet and have no HTC android experience! im def excited and grateful for all the work you've already done!
[EVO 4G Android Development] PlankLongBeard:
ToaST.. The Evo root? Please hit me up on twitter.. @planklongbeard..
[EVO 4G Android Development] toastcfh:
Heh sorry I don't know the drama between u guys. But feel free to look at my twitter for the full conversasion. He's. Actually one of the first people to @ me so should e easy to track. But yeah I was linked to. Ur site so idk. Anyhow **** all the drama Im happy to. Work with anyone with some skill.
[EVO 4G Android Development] joeykrim:
+1. perfect.
[EVO 4G Android Development] PlankLongBeard:
Yup.. Some people forget that about $40,000 was invested in education for this madness, cause it is Java and Linux.. Learning samali and baksamali and such as well.. I myself am enrolled in Devry for the Love of Android and The passion of the Limitless ways it has..

+Damn-1
[EVO 4G Android Development] KERKEDAGAIN:
hey toast, would this be of any use for our device, seeing as it's taken from the HD2?
[EVO 4G Android Development] maejrep:
Does anyone really know just how similar the two devices are, hardware-wise? Even if it has the same GPU (kind of thinking it may not be, particularly since HD2 is winmo, and this is linux, so the requirements in a GPU are pretty different), the APIs are going to be very different, so the only use that driver would be for us is if we need to make similar modifications in our linux version of it. However, I have a pretty strong feeling that the driver in the linux kernel for the GPU is already done well, and if it's not, it would be much easier for us to fix in the linux kernel than to use that patch directly -- a more intelligent solution would be to pick Chainfire's brain about what modifications were required, and make those changes in the kernel source that we already have. If it's implemented at the library layer, a similar patch could be needed, since we don't (and never will) have source for the libs.

But basically I get the feeling our hw3d libs and the GPU itself are going to be different enough that their winmo bugs wouldn't affect us in linux.

Note, I didn't look much into Chainfire's files, so if it's just a configuration change, then it's virtually guaranteed it won't affect us anyway. Only if it required an actual driver patch, and the GPUs are identical and our drivers have the same bugs, would it be necessary to port his patch to the linux driver.
[EVO 4G Android Development] Shidell:
Hey Toast & Maejrep,

(Please bare with me, I'm a junior developer, but eager to assist & learn..)

I'm wondering where this kernel source came from? I know HTC makes a practice of making the kernel available (as they have to thanks to Linux's license), but they haven't released the EVO kernel yet. Is this a leak?

I was waiting to see it arrive on developer.htc.com, as I was hoping that their kernel would allow us to use the drivers/software changes from their stock 2.1 EVO ROM to take advantage of functionality such as the camera, 4G, WiFi, etc.

Can you guys comment on this kernel, as well as the (hypothetical) situation that using their kernel with an AOSP 2.1 build should be work-able and fully-functional in the near future?

(PS, is there a specific ARM toolchain to use to build the kernel for the EVO, or is the ARM toolchain chip-agnostic? For example, I'm using http://www.codesourcery.com/downloads/public/gnu_toolchain/arm-none-linux-gnueabi/arm-2008q3-72-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2 -O arm-2008q3-72-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2 to build for the HTC Touch [Vogue]; would the same toolchain build correctly for the EVO, despite the Vogue using an Arm6 MSM7500 and the EVO using Snapdragon?)
[EVO 4G Android Development] joeykrim:
i can only answer regarding the toolchain, i have no other experience with HTC.

the toolchain will work, but will need to be recompiled with the target architecture changed to support the EVO processor (i believe).

which makes me wonder the same question with a bit more detail, what ARM setting is best used for the EVO architecture when compiling the toolchain?
[EVO 4G Android Development] coolbho3000:
The prebuilt toolchain that comes with Android works fine.

http://source.android.com/source/download.html

You can enable flags like NEON and vfp to try to improve performance.
[EVO 4G Android Development] Shidell:
This works fine for building both the Kernel and Android?
[EVO 4G Android Development] toastcfh:
yes and its the toolchain i and most developers for Android use.
[EVO 4G Android Development] Shidell:
Thanks Toast. :)

Can you comment on the Kernel?
[EVO 4G Android Development] toastcfh:
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
[EVO 4G Android Development] Shidell:
Interesting--thanks.

I look forward to HTC releasing the official EVO kernel source--between that, AOSP, and the files we have from the original 2.1 EVO ROM, I think we can make it all fly. :)
[EVO 4G Android Development] toastcfh:
Come to think of it the kernel in my froyo port was compiled by me for froyo.
[EVO 4G Android Development] Hero_Over:
oh rly!!! thanks for throwing this in the wild toast. us devs appreciate it alot. and good thing i have no 4g in cali so i wont regret my own kernel
[EVO 4G Android Development] bcnice20:
Hmmm... couldnt this kernel be compiled for aosp 2.1
[EVO 4G Android Development] joeykrim:
i saw maejrep say he was running this on the dev froyo ROM, it prob shouldn't be an issue having it run on the 2.1 AOSP.

i havent read thru this thread in a while cuz it was released a while before the EVO official came out....but camera, 4g and perhaps a few other features might not be working 100% yet w/o the HTC kernel source.
[EVO 4G Android Development] bcnice20:
The combo of darchstar and toast got aosp fully working on our heros with the Eris kernel source

Wait take that back mms still doesn't work right that's all
[EVO 4G Android Development] ffolkes:
yep, i'm still up.

i made something for those of you who aren't having any luck with the vfa kernel. as i mentioned before, there are two timing settings to change, vfa and T2. the vfa change was getting me 55+fps so i used that, but let's see what happens if we leave vfa alone and change T2. for me, this results in only 40fps, but who knows what you might get. it's worth a try.

you can flash this over anything you want.

in dmesg you should now see "mddi: init commands sent. vfa is default (not set), T2 set to 250d" which will confirm the flash was successful.

IMPORTANT: you will HAVE to turn your display off and on after it boots. i took out the code i stuck in mddi.c in case that was causing problems, so it won't update it upon boot anymore.
[EVO 4G Android Development] apristel:
flashing now .. thanks. will report back.

EDIT: This one def. works getting 41 average stdev=3.99. run 2 41 and 7.62..

I wonder why the other hack for the nova panels works on some and not the others...could there be a different rev of nova panels? I'll rip mine apart and see if there is any markings to determine if needed

Thanks for the hard work.
[EVO 4G Android Development] toastcfh:
I'm thinking if this is actually working then try to writel the value/values needed on Panel init or something along those lines. Possibly everytime the CPU hits max freq, or better yet look at kmsg and writel it on the last thing called when the device comes back from sleep. Idk but this is how I got around CPU restraints for the heroc and enabled overclocking. Just an idea
[EVO 4G Android Development] EtherealRemnant:
41FPS with lots of higher spikes.

EDIT: Quadrant's planet simulation runs at a good 41 but spikes up to 50 at times.

So it seems like something is different on our devices? Panel programming maybe? Any chance that BOTH of those commands might make a difference?
[EVO 4G Android Development] th3_g00b:
Ok, i flashed the first novafpsboot and firsy time i didnt wipe and it stuck at the fresh screen. Second time i wiped data and cache but it wiped all my apps from my app drawer. I ran fps2 and it was capping ay 29. Did nandroid restore and waiting on another kernel to test. Thats my report :-)
[EVO 4G Android Development] EtherealRemnant:
Try the new kernel posted a few posts above.
[EVO 4G Android Development] timgt:
Ok, I am lucky enough that both fixes work on my novatec panel.

1st Fix: 54fps average but VERY VERY choppy in certain thing like games (doodle jump)

2nd Fix: 41fps average, with a WAYYY lower stdev (which is better) and everything runs butter smooth. Doodle jump no longer is choppy and it runs better then it did stock so I can tell I am getting the extra frames.

Conclusion: I think we need to focus on the 2nd fix more, it seems to be the correct direction.
[EVO 4G Android Development] EtherealRemnant:
Okay maybe I won't ***** about the ~40 cap lol. So its still smoother but actually runs better than a higher frame rate?
[EVO 4G Android Development] mdaddy:
1st Fix - flashed over EVOlution Froyo v8 Rev A - fps2d starts at 60 then quickly jumps down to 30. System very unstable.

2nd Fix - flashed over EVOlution Froyo v8 Rev A - fps2d avg 42!!!!. System very unstable (not usable).

HW: 0002

Panel: Nova
[EVO 4G Android Development] th3_g00b:
Same deal. Not sure what im doing wrong

I have an 003 nova
[EVO 4G Android Development] EtherealRemnant:
Its not like Froyo likes ANY custom kernel right now...
[EVO 4G Android Development] madsquabbles:
t2 worked for me on fresh .03.

i'll try dc 3.2 later

42 avg fps.

hw 0003.

oh yeah, multivis test is way more responsive. 10 fps makes a difference.
[EVO 4G Android Development] luisrcastillo:
1st fix did not work but 2nd fix works. Getting 41fps and stdev=8.77.

Great Work!!! Thank you!!
[EVO 4G Android Development] tyrnight:
def works here.. at 41 FPS on gears and 40 on Fps2d when the first patch didn't work at all.. YAY!!!
[EVO 4G Android Development] jayv1717:
2nd fix working here too!!

Edit:Multi touch is alot better too

Edit 2:The improper grounding issue seems to have completely left
[EVO 4G Android Development] joeykrim:
used: novfpsT2-signed.zip

hardware: rev 2 novatec panel

rom: joeykrim - odex - 1.0.8

kernel: Matrix@MacBookPro #114

Fps2d: #1 - Avg=39 stdev=6.78, #2 - avg=40 stdev=4.87, #3 - avg=40 stdev=3.72
[EVO 4G Android Development] EtherealRemnant:
Gears 42 even when wildly flipping them around the screen... If we can get this cap completely lifted, we may very well have the fastest android device in existence...

Also, has anyone else noticed that while snapdragon supports OpenGL ES 2.0, we are only running 1.1 drivers? LAME!

Took it off sleep and gears was running at 89 for a split second :O
[EVO 4G Android Development] Jykinturah:
I have a hardware rev 002 nova panel. I uploaded a video. It looks smoother, but I think touch input still has a weird kind of lag, especially with quicker gestures.\

It is still processing, but I have to go to class.

http://www.youtube.com/watch?v=DHptyK6RQzo
[EVO 4G Android Development] EliWay:
HOLY ****, yes i can also confirm the grounding ISSUE IS GONE

Touch screen lag, FPS cap and grounding issue ALL FIXED IN JUST ONE FIX.

YOU GUYS ARE AMAZING!
[EVO 4G Android Development] EliWay:
[ Server Double posted ;/ ]
[EVO 4G Android Development] timgt:
Use the 2nd fix instead. I am having ALOT better results with it.
[EVO 4G Android Development] gerald410:
The 2nd one did the trick! thx again
[EVO 4G Android Development] EtherealRemnant:
The second fix still results in the multi touch lag displayed in that video. I just tested it. It is NOWHERE near as bad as "stock" though.
[EVO 4G Android Development] Tikerz:
Wow, I can also confirm the T2 patch got rid of the grounding issue. Nice!
[EVO 4G Android Development] EtherealRemnant:
Is it possible to make a kernel that raises the bar to 60FPS, even if it results in tearing? I've read a bit through the thread and I understand that we're still running half of what we should be - ie., we should be seeing 80 with this patch, but I would be interested in a kernel just for testing purposes that pushes the 60-80 envelope.
[EVO 4G Android Development] clubtech:
So this is suppose to break the camera?

I know the godmode kernel breaks it, but does this patch also break it?
[EVO 4G Android Development] EtherealRemnant:
Any custom kernel breaks the camera. And will continue to do so until we get the HTC source or someone takes a LONG time programming the two cameras into the kernel based on the limited documentation we have on them.
[EVO 4G Android Development] madsquabbles:
works with dc 3.2 also.

very quick work around to get the camera back working. just boot into recovery, do an advanced nandroid and only restrore boot. it's a lot faster than a full restore.
[EVO 4G Android Development] clubtech:
So restoring only boot is going to keep this fix or is this fix is inside boot.img?
[EVO 4G Android Development] amdchip:
Probably wont see anything 60 or above until the kernel source is released by HTC
[EVO 4G Android Development] crackerstyle:
Wild. I tried the 2nd file, and since it didn't give me any fps jump I went to restore my nand backup and can't. Now it tells me Error : run 'nandroid.sh restore' via adb!

Gonna try flashing a rom and seeing if it'll let me restore after that.
[EVO 4G Android Development] madsquabbles:
it'll override the fix.

this mod replaces the boot partition. when you restore you boot you'll be back to the previous state.
[EVO 4G Android Development] howdyace:
works for me

002 novatec panel

Using 2nd fix i avg 41 on fps2d with a stdev of 6.97 and running doodle jump was a joy.

flashed on top of DC's 3.2 rom with a wipe on both .
[EVO 4G Android Development] wildgillis:
working now at 41fps stdev=8.09 gears running at 43
[EVO 4G Android Development] madsquabbles:
isn't the screen only 60hz? if so then it wouldn't matter if they had the source, you'd still see tearing. your gpu will be rendering images faster than the screen can display.

i guess maybe they could oc the screen...
[EVO 4G Android Development] AssassinsLament:
For all your people not following this thread, realize that this nova cap kernel/fix is just a temporary fix for now, HTC is cutting half our framerate somewhere and the way we overcame it was by forcing the nova panel to 80hz. And with that, we are seeing 40 - 55 fps, again, only half of what we should get. Please be aware that this is experimental, plus any custom kernel right now will not have a working camera. Toast and Maejrep have gotten most of the other sensors working, but again, this is experimental... play at your own risk.
[EVO 4G Android Development] crackerstyle:
That worked. I flashed a fresh rom then rebooted and wiped again and it allowed me to restore. whew!