Yes, testing on real devices is important and useful for all the reasons you gave. But there are others. For one, it takes a ridiculously long time to launch the emulator. Hook up a real phone via USB instead, and it is ready in under 10 seconds. Another: the permissions are different on a real phone and the emulator. You automatically have root permissions on the emulator. Not so on the phone. This means that if you want to test the software in the environment the user will see (and you really should want this), you get a much closer match by using a real phone.
So summarizing briefly, yes, you can do a lot of useful testing on an emulator, and it is a cheap and easy way to test on various screen sizes. But before you release your product to the market, it must be tested on a real phone, and should be tested on as many as possible. On Tuesday, October 2, 2012 5:40:32 PM UTC-7, gjs wrote: > > Hi, > > >The world doesn't comprise Eclipse alone. > > Wow really! Thanks for letting us all know... > > A real device is useful for testing various hardware features - bluetooth, > nfc, hd video recording, sensors - accelerometer, barometer, compass, gryo, > magnetic, wifi direct etc etc > > Regards > > > On Tuesday, October 2, 2012 6:22:44 AM UTC+10, Lew wrote: >> >> gjs wrote: >>> >>> >>> I'd suggest using the latest Google Android device, currently that is >>> the (Samsung) Galaxy Nexus, but rumors suggest it is to be updated very >>> soon (?) >>> >>> Main reason is that the Google phones allow you to see your own debug >>> message on the console pretty easily, where as most other phones have so >>> such junk debug messages on the console, that they swamp your own debug >>> messages making it difficult to test & debug your own apps. You can filter >>> debug messages but the console fills quickly (in Eclipse) anyway & then has >>> to be reset. >>> >> >> I assume that by "debug messages" you mean the logcat contents. You can >> filter those by command-line >> quite readily also, for example into a text file, that you can examine at >> your leisure. You can also modify >> the buffer size to capture more data, or run the "adb logcat" command in >> the background redirecting to a file >> for an arbitrary amount of data. >> >> >>> If you can live without relying on debug messages through Eclipse then >>> any good & recent phone will likely do, eg Samsung Galaxy S3, HTC One X, >>> etc. >>> The Google phones get OS updates before other phones as well. >>> >> >> The world doesn't comprise Eclipse alone. >> >> >>> >>> >>> >>> Nilashis Dey wrote: >>>> >>>> I am new to Android Development and would like to know which phone I >>>> should get to test my apps? Obviously, I would like the phone for which >>>> drivers for all devices are easily available and for which I would find >>>> the >>>> most amount of support discussions online - for when I run into problems. >>> >>> -- 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
