Quote:
Originally Posted by gmfeny
So does adding "hw3d.force=1" to the startup.txt make a difference in speed performance???
|
As I understand it, the hardware 3d only comes into play in a very limited set of circumstances -- seems to be mostly for games and tech demos.
Hardware 3d has nothing to do with the rendering of the android home screen, or the transitions or animations. Those will all run the same with hardware 3d enabled, with software 3d, or with broken 3d.
The fact that the system is being booted from WinMo (as speculated by someone else) also has no effect on the speed or responsiveness of the GUI.
As far as what actually is slowing down the interface, I have heard mention that reading the entire system from SD causes a great deal of overhead. Apparently SD reading and writing is actually fairly processor intensive. Additionally, there might be some issue with the method used for blitting (for writing efficiently to the screen).