Dianne,
it's not just broken. we does NOT have HW graphics at all. our CPU has a
plenty of hardware threads. we expect to write software graphics pipeline in
kernel and implement in-house opengl. s/w graphics will make use of hardware
threads to deliver decent performance.
the graphics
For a production-quality device, you need hardware acceleration of at least
surface compositing. This has become increasingly true as screen resolution
has increased. The software rendering path for surface flinger is only
there for bring-up and the emulator.
Further if you planning on running
we ported android 2.3.1 to our architecture and board. the response time is
terrible up now.
according to my profile, i think it's because drawing windows are very
slow. i have 2 clues which drawed my idea on graphics:
i) bootanimation is slow;
ideally, bootanimation is 12fps. however, we can
If the boot animation is that slow, your graphics driver is very broken.
On Thu, Sep 8, 2011 at 10:26 PM, Liu Xin navy.x...@gmail.com wrote:
we ported android 2.3.1 to our architecture and board. the response time is
terrible up now.
according to my profile, i think it's because drawing
Hi,
On my device the system regularly goes into a state where launch of
apps takes lot of time ( 5-10 secs ). This happens after using the
system for sometime and more often with apps with GLSurfaceView.
My device config
RAM - 384 MB
Resolution - 1024 * 600
CPU - 1 Ghz Tegra dual core
In this
