12.19 3d package with better performance for testing - Page 9

**[ACL]** · #81 (**permalink**) 12-01-2010, 02:15 PM

Quote:

Originally Posted by tiad8

ACL.
COULD THIS BE POSSIBLE. a new framebuffer?. THANKS

I'm already running a new frame buffer from .35 kernel. Its not that big of a change but it does allow us to get up to date code from google directly.

Right now i'm narrowing down where the bottle neck is with the framebuffer. Bottom line is we need to reach about ~32ms to render each frame so we can get at least 30fps. Right now we are probably close to 50ms for each frame.

tpdjr · #82 (**permalink**) 12-01-2010, 02:16 PM

Quote:

Originally Posted by tiad8

ACL.
COULD THIS BE POSSIBLE. a new framebuffer?. THANKS

sorry what I meant to say is would we have to update to .35 framebuffer before we get anymore improvements and thanks for everything you are doing.

tpdjr · #83 (**permalink**) 12-01-2010, 02:18 PM

Hey acl is that the new framebuffer you are running on nand? just curious is 30 fps really snappy?

**tiad8** · #84 (**permalink**) 12-01-2010, 02:49 PM

Quote:

Originally Posted by [acl]

i'm already running a new frame buffer from .35 kernel. Its not that big of a change but it does allow us to get up to date code from google directly.

Right now i'm narrowing down where the bottle neck is with the framebuffer. Bottom line is we need to reach about ~32ms to render each frame so we can get at least 30fps. Right now we are probably close to 50ms for each frame.

thank you. You awesome

**[ACL]** · #85 (**permalink**) 12-01-2010, 02:50 PM

Quote:

Originally Posted by tpdjr

Hey acl is that the new framebuffer you are running on nand? just curious is 30 fps really snappy?

yeah its nand.. but im not able to get 30 yet (thats my goal).

Also anyone know if wince has vsync enabled or disabled by default? wondering if we are being capped by the vsycn

tiger2wander · #86 (**permalink**) 12-01-2010, 03:17 PM

Hey guys, how about internal memory access now? is Android will run much better if we gain more RAM by remove some from WinMo and get everything load directly from internal memory instead of SDCard? BTW apps will load much faster combine with this driver IMO.

**arrrghhh** · #87 (**permalink**) 12-01-2010, 05:45 PM

Quote:

Originally Posted by tiger2wander

Hey guys, how about internal memory access now? is Android will run much better if we gain more RAM by remove some from WinMo and get everything load directly from internal memory instead of SDCard? BTW apps will load much faster combine with this driver IMO.

The NAND boot isn't really a full NAND... still depends on the SD card pretty heavily. I'm assuming that's what you mean by 'internal memory access'...

With that said, we won't gain any additional RAM. Haret boots WinMo out of memory - there's nothing left of WinMo when Android is started.

Apps loading faster... I guess it's possible that with improved 3d apps don't have to work as hard to startup... But that would only apply to a few apps I would think. I don't think the majority use any 3d... I'm not positive on that.

manekineko · #88 (**permalink**) 12-01-2010, 07:26 PM

Phenomenal job tiad8. I can confirm that with your build.prop loaded, Angry Birds Lite 1.3.5 Beta 2 loads and plays. It's significantly faster than Angry Birds Full, playable, though not exactly silky smooth. Some textures still appear to be missing, i.e. backgrounds.

**tiad8** · #89 (**permalink**) 12-01-2010, 07:55 PM

Quote:

Originally Posted by manekineko

Phenomenal job tiad8. I can confirm that with your build.prop loaded, Angry Birds Lite 1.3.5 Beta 2 loads and plays. It's significantly faster than Angry Birds Full, playable, though not exactly silky smooth. Some textures still appear to be missing, i.e. backgrounds.

for best performance. speed, stable, and fast. i used 3d driver 11.26 and gralloc 11.30 (and the build.prop). frx03 overall is very stable. thanks

manekineko · #90 (**permalink**) 12-01-2010, 08:11 PM

Quote:

Originally Posted by tiad8

for best performance. speed, stable, and fast. i used 3d driver 11.26 and gralloc 11.30 (and the build.prop). frx03 overall is very stable. thanks

Thanks, I'll try the 11/26 driver later.

Right now I'm using 11/29 driver, 11/30 gralloc, and 12/1 build.prop. Without a doubt, performance is much, much better over stock FRX03, no chance of this being placebo.

OpenTyrian on detail settings low went from being borderline unplayable to fairly smooth and totally playable. In OpenTyrian, flying the ship with the stylus and autofiring with the keyboard is an amazing experience. Maybe one of the few games out there where our TP2's might have the world's best control scheme, with no fingers in the way blocking the screen.