> As I saied the same code runs great on every feature phones from JP5 > to JP7 and newer. > SAME CODE means that I converted the JavaME calls to android one, we > are talking about exactly the same code. > We are talking about 100-180MHz phone and Is this your answer? > The app isn't well optimized?
Comparisons like this are meaningless if you don't specify the screen resolution. An app running well on a slow CPU can run much faster at a low resolution than the same app running on a fast CPU at a high resolution. I am not denying that your app worked well on Java ME feature phones but this doesn't mean it optimized to run on the GPU at 1280x720. If you could tell me more about what your app does exactly I would be able to help. Could you show me an example of the drawing code used by your app please? > You are talking about drawLines() over the drawLine(), should we > abandon antialiasing to draw some > lines on a 1.2GHz smartphone? (drawLines() does not support > antialiasing) If drawLines() doesn't do antialiasing then there's a bug. It should. If so, please file a bug at http://b.android.com. I was recommending drawLines() not because of antialiasing but because it can batch operations on the GPU which is a great optimization. And again, the CPU speed has nothing to do with performance of the GPU (since you love to talk about frequency, the GPU in the Galaxy Nexus runs at 384 Mhz; this is meaningless since you cannot really compare frequencies between CPU and GPU.) -- Romain Guy Android framework engineer [email protected] -- 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
