Re: Test with framebuffer
 

ok guys. this is what i have

FPS2D 29
NEOCORE 20.4
QUADRANT 614

11.30 gralloc
11.29 3d

no flickering here. none

very stable. ACL

thanks

Re: Test with framebuffer
 

For your need, I have posted dmesg and logcat here:
- dmesg: [ 0.000000] Linux version 2.6.27.46-01232-gb703 - Uoc Nguyen
- logcat: E/Tethering( 1664): attempting to remove unknown i - Uoc Nguyen

Re: Test with framebuffer
 

Yeah, rebooting with 3D 11.29 driver, no flickering at least with boot animation :D
Very fast boot even I've just removed all dalvik-cache :D.
Continuous testing with this driver and will report soon.

Thanks!

Re: Test with framebuffer
 

18.1 on neocore
angry birds full has little if any tearing now

running 11.29/30 gralloc and lib
oc to 700

Re: Test with framebuffer
 

Here is whats I've got:
- Fps2D:
+ 1. avg: 28 stdev:6.83, highest peek is: 50 in >1 second :D, so its great to see.
+ 2. avg: 30 stdev: 4.30
+ 3. avg: 30 stdev: 4.45
- Quadrant:
+ 1. score at 450
+ 2. score at 634 after kill all running tasks and sleep for few seconds to allow my sdcard some rest and make it cooler (I has experienced with performance when heavily IO load on sdcard is not good as NAND for example: time right after boot or downloading/installing application from market, syncing something...)

So, with 11.29 3D driver there is no more flickering/tearing issue! very stable now

Again, I'm still running with OC @ 768Mhz with 64Mb of swap using /sdcard/swapfile, mounted by froyo.user.conf script.

Thanks!

Re: Test with framebuffer
 

Hey. First of all, as a first time poster, greetings to all and a big thanks to all the TP2 dev team for the effort you put on this project, specially to ACL.

These are mine results:

- Fps2D
1. avg 30 sted 4,69
2. avg 30 sted 4,40
3. avg 30 sted 4,51
4. avg 30 sted 4,11

- Neocore
1. 20,4 FPS
2. 18,5 FPS
3. 18.8 FPS

- Quadrant
1. 566
2. 611
3. 586

Running on Rhod100 with OC @700Mhz and using 11/29 3D driver.

Re: Test with framebuffer
 

Awesome.. i want to make sure all the Rhod variants are covered. I will commit this since it looks like it works for almost everyone now.

One thing some people noticed is the spike to 50fps. This is what we are working on now. I just got my hands on the novtec documentation 2 days ago so we are still trying to see how we can benefit from this.

The good news is our topaz brethren are also helping out in the quest for 50fps so lets hope one of us stumble on it. For those of you who havent heard of the theory. We cant update the screen until the vsync happens. It happens only 60times per second, so if we miss it by just a few ms, then we have to wait for the next one killing our fps by half pretty much.

I can share the documentation with anyone who can compile and are willing to make a few changes on their own. This limit was discovered by toastcfh when the 30fps cap was changed on the evo.

https://github.com/toastcfh/Superson...705a7e7fb497b5

The link above is the commit that managed to break 30fps on the evo. I already tried and it does not work for us, but maybe im missing something. Sometimes it takes a few eyes to figure this out.

i had a lot of wine so i cant think any more.. thanks fellas (those of you who tested)

Re: Test with framebuffer
 

Hey Tiger, I want to know more about the swapfile you referenced, can you share? TIA

Re: Test with framebuffer
 

I had the flickering during the entire boot animation. I am using all of your latest files, except I am using the 11/26 gles file and I'm back to the 12/2 build.prop.

Just ran Neocore, 19.7 and flickering the entire time.

I'm going to try the 11/29 gles and see what happens.

Re: Test with framebuffer
 

One last thing. Can yall test gallery3d ? this doesnt work on the Raph and is the main reason why this commit is taking so long.

It works on rhod nand but i need to make sure haret works ok as well.