Indicator, Thanks for a detailed answer. For anyone who come across this post the following could be a solution to the fragmentation problem: http://duarlander.ning.com/
Promote this community, developers can help other developers. On Sep 19, 12:03 pm, Indicator Veritatis <[email protected]> wrote: > That is a very open-ended question. But I can make a good start on > answering it by saying: > > 1) before you even test on various phones, you should test in the > emulator using AVD files for versions 1.5, 1.6, 2.0, 2.1 and 2.2 and > with a variety of different screen sizes and densities. Complete > coverage is a good idea (large screen, small screen, normal; medium, > low and high density). > > 2) Depending on what you are doing, you may need to test on multiple > vendors and models of phones for each of the combinations listed in 1. > This is because multimedia support has different limitations and bugs > on different phones and versions. Similarly with OpenGL: what looks > fine on one vendors phone may look bad on another; it may even crash. > > 3) If you are doing a r-e-a-l simple app, you can get away with less. > But be careful. Do Google searches in these groups and elsewhere to > determine what the fragmentation is like for the particular Android > features your app requires. > > On Sep 18, 2:24 pm, Tabman <[email protected]> wrote: > > > > > hello > > > my app works fine on samsung galaxy and nexus one. It is giving > > problem on htc incredible. How should I test my application for > > various phones ? -- 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
