Thanks for the link to this documentation. It seems to explain where those extra 64k bytes are coming from: "The buffers returned by this method typically have somewhat higher allocation and deallocation costs than non-direct buffers." Unfortunately Android >= 1.6 forces the use of allocateDirect in this situation. I cannot use 1.5 because it cannot easily handle larger screen sizes. I may have to try using VBO's to get around it. Does anybody have any idea of how many Android devices don't support vertex buffer objects? There appears to be some claims in this group that VBO's don't work with some Motorola devices...
On Friday, March 2, 2012 3:42:53 PM UTC-7, shlomi cohen wrote: > > you can find some information about direct bytebuffer in the documentation > : > http://docs.oracle.com/javase/6/docs/api/java/nio/ByteBuffer.html > I'm not sure if it help you but it's a good start. > > by the way , in the documentations it is generally recommended that you > use direct allocation if you wish to gain performance. > maybe you should try using different allocation method of the byteBuffer > class and see if it's still good in a performance manner. > > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
