Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 3 years ago.
Improve this question
I'm looking to get a device (phone, tablet, etc.) for developing Android applications. I know I can use the emulator to get me started, but I feel like that will only get me so far along. I'm looking for something reasonably priced, and I don't want a phone contract, data plan, etc. Anyone have any suggestions?
I would recommend either a Nexus One or ADP2 ( you can get via Market once you sign in as developer. ). Other option is ebay. All attendees of google i/o got moto droid as a gift. And several devices are on ebay, priced around 350-400.
I wouldn't buy G1 for a reason i think it close to end of life. I'd also avoid devices alternative homes and ui ( blur, touchwiz, sense ). You want to clean google experience phone.
Advantage of Nexus of Dev phone - you'll have engineered bootloader, which let you to install custom roms and you can get root access which among other things allow you to use awesome tool hierarchyviewer ( from SDK ) on the device .
As a registered Android developer you can get an unlocked phone for $399. However, I am sure if you keep an eye on ebay you can find something that will suit your needs at a cheaper price. I see a bunch of Motorola Droids listed for a little over $300.
While the Nexus One and ADP2 are great because you can load custom builds of Android on them, that doesn't really sound like what you are most interested in. In fact, doing so will preclude you from running the Market application. For application development, you really just need any phone that lets you load non-market applications over ADB. You may want to consider getting a phone that has a keyboard to ensure that it works properly for your application. Finally, take into consideration which version of Android you are targeting. Newer phones run newer versions of Android.
If you plan developing something that might take an advantage of a hardware keyboard, get Motorola Droid/Milestone or a G1 (which you can turn into ADP1). I'm using the latter as my apps are targeted at 1.5+. Nexus One is the other option.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
Im developing an Android app and I would like to test it on a real device so that I'd like to get a phone, on which a different version of Android can be installed, upgraded and downgraded.
Which phone can run most of Android versions? How should I choose it ?
Thank you.
[This answer applies to official Google releases of the Android software, not to alternate distros like Cyanogen.]
There are very few devices that even support more than one or two versions of the Android system. Carriers and OEMs seem reluctant to upgrade devices at all, and when devices do receive major upgrades, they rarely get more than one.
Of course, Android is open source, so you can build whatever version you want, right? Not really. Although the base OS is open source, OEMs have no obligation to release the actual source used to build the kernel and userland for any particular device. With a closed-source device, upgrading is out of the question. The best you can hope for is a downgrade, if you can find the right binaries.
As one commenter noted, Nexus devices are in general a good choice. They are usually supported for at least three OS revisions, and can be upgraded and downgraded easily. With few exceptions, they run 100% open source software.
If you're willing to get your hands dirty, the device that supports the most versions is the Panda board, which for many years was the standard test board for the Android Open Source Project. It was recently replaced by the HiKey board, which is more powerful and less expensive. If you don't mind building a device out of raw components, the combination of a HiKey and a Panda will cost less than a single Nexus device and likely remain valid for years to come.
I recommend you to go with the emulators but if you want a real device you should test on a Nexus device, but even nexus devices can't cover all the platforms
You can find most of the Android official versions here
Also you can find custom ROMs for different phones here
Note
Even if you flash ROMs on some devices, you still might get into different issues on different platforms because Android is customized by each phone manufacturers. For example, the Android that runs on the Nexus devices is the official Google version, but is different than the one that runs on a Samsung, HTC, Sony, etc.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
In real world , no can test his App in all android devices available in market.
Is there a tool to test my app to check performance and etc.
Or, What is the best way of testing android apps.
Update:
best way is to create emulators and test it. But we don't know all devices with models.
Can you share your valuable thoughts. Thank you
If you need to test for specific devices, Samsung has a remote test lab, this way you can test real devices virtually and a large variety of devices.
Or else you can go for
http://www.keynotedeviceanywhere.com/mobile-testing.html
http://www.perfectomobile.com/
https://www.lesspainful.com/
Got this answer from Other SO, Just combined some answer.
I would like to answer your question from an automation point of view -
There are some really cool tools in the market to help you perform automated testing for Android, iOS & Windows phones.
My personal favorite of them all will be SeeTest (by Experitest). There are others like FoneMonkey, MonkeyRunner, Meux-Test, Robotium etc.
These tools are very advanced - they provide good reports, have image recognition & cross device support. Suppose you write a automation code for Android App, you can find ways to reuse those for iOS. This will save a lot of your time in SDLC.
All these tools have a CLOUD based testing model also. The way this works - buying and testing across many devices is a costly and a time consuming process. These automation tools - have a remote cloud system, which you can leverage for a fee. They will have almost all the devices that are there in the globally accepted markets. Once you have written your automation test codes, you can run them on any device from their cloud system.
So to test across so many devices, its NOT possible manually - you have to use an automation tool. The automation tools today are building this kind of a framework to capture the QA market.
This is the best way to test an App across a wide variety of phones (like in Android).
I hope this helps.
This may help http://developer.android.com/guide/developing/device.html.
If you're on Windows you will need to install the USB driver. Then, on your Devices tab (Window->Show View->Other->Android->Devices) you should see a new row appear when you connect your device to your workstation with a USB cable (although LG handsets are problematic in my experience).
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 2 years ago.
Improve this question
Is there any emulator, which tests the APK, for all kind of android devices. There is one called YouWave, but it is not good.
What I want is, one emulator, when the APK file is loaded, performs automatic testing like UI interface, performance, etc, and provide a report for the same. Saying that for this combination your APK does not works correctly.
This might not be the answer to your question but just from my
experience I would like to share that the best practice would be to
get as much real devices as you can. Obviously devices costs but
that's how you can be sure about it.
As also suggested above you can give a try to bluestacks as would get the wifi and system tools easily connected to you i.e. better in performance then the native emulator provided by Android.
With that the best thing would be to get your app tested on some devices of different Classes.
By classes above I mean ,
Different resolutions
Screen sizes
Android versions
Or, these days some testing organizations are also there who have got a number of devices and they do the testing for you on real devices hence you won't need to pay for a device , its just a suggestion or you can suggest to someone.
--Edit--
I recently have gone through Genymotion and I have found it better then any other emulators,
http://www.genymotion.com/
--Update - Nov 2020--
Bluestacks has improved a lot lately and is free to use for most of the features. I have tried testing multiple instances of the app and it worked like charm by emulating two phones, sharing data via links etc.
Use manymo.com. This is an Online emulator for android.
Take a look at:
http://www.neotys.com/product/mobile-load-testing.html
http://www.perfectomobile.com/portal/cms/services/android
http://www.t-plan.com/robot/
Meanwhile, if you don't find a solution, here you have some common android virtual device configurations, so you can easily configure yourself different devices in the AVD:
HTC Evo 4G
Google/HTC Nexus One
Motorola Droid
T-Mobile/HTC G1
Archos 5 Internet Tablet
If you want the application to work perfectly in all kind of android devices, then the answer is "NO".
As Prateek suggested in his answer, you will have to get your app tested on some real devices of different Classes.
If you don't have the resources to do the testing yourself, go for getting help from someone who have got a number of devices and tests the Apk file on real devices.
to test online, use appetize and upload your apk. very easy. they will send a link to test.
The android SDK comes with a UI tester that allows for automated UI tests, full details can be found on the android developer site:
http://developer.android.com/tools/testing/testing_ui.html
You can test buttons, rotating the screen and get detailed information, it sounds as if it's perfectly capable of meeting your requirements
Andyroid will do exactly what you need:
Provides seamless sync between desktop and mobile devices.
Connects Win/Mac with Android apps for launching, push notifications and storage.
Enables app download from any desktop browser direct to Andy OS.
Ensures most up to date Android OS at all times.
Brings your favorite communication and entertainment mobile apps to the desktop.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
Buying devices to test your apk/ipa/alx on different android/ios/blackberry phones is getting heavy burden on pocket since it turns to be a dead investment very fast as technology is progressing too fast and you can't just keep on buying to know your app's user experience.
Is there any company that provides the services to save our dead investment? I've explored Keynote DeviceAnywhere which is pretty good but the rates are quite high.
I'm waiting for a solution asap.
Thanks.
Definitely.
I am not familiar with Eclipse or the Android simulators/emulators (nor BB or winPhone 7), but in any case you want to test on the real thing.
Even if the behavior is the same (some times it isn't), the performance is completely different between a real device and a simulator.
Android
Definitely YES. Applications run munch faster on devices than on emulator. In the long run , buying devices will save developers time thus save you money. The best devices for developers are Nexus line unaffected by OEM software (think of Samsung Touchwiz , HTC Sense).
Samsung lets you use their real device over the network for a certain period of time.
iOS
YES . The simulator is pretty close to reality. If you're on budget, you may buy second hand :
iphone 4 or wait for the upcoming iphone 5
iPad only if you're
targeting this support.
Add the developer licence extra cost too , to run on a device you must have a licence . iOS developer Standard = 99 USD and more for Enterprise Program = 299 usd
Blackberry
Don't know
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
not much of a programming question, but development related still,
I'm starting Android development and have been at it for just a little over a week. So far so go regarding progress, specially for someone who hadn't touched Java in his life (but have good C#, Objective-C, VB.NET and Fortran experience)
As I'm looking into a testing device I'm undecided on the phone to get. I need it to be unlocked, so I'm looking into Dev Phone 2 or Nexus One. The difference being $120~ish in price.
Anyone having one of those and using it for development? which do you consider is the best choice. Is the extra speed and screen in the Nexus One worth it?
I'm targetting SDK 1.6 but down the road I can see myself playing with 2.1.
Any input is appreciated
Regards
Something I learnt today was not to let a developer work on the faster model of mobile device when most of your users have the slower model. If it's good on the faster one, it's not always good on the slower device. I'd get a retail G1 as they can be flashed to all kinds of Android revisions. Plus they'll be cheap.
If you go for the Nexus 1, your apps will look better but only to Nexus 1 owners, mostly!
From what I've heard all Android devices are going to get a bump to some form of 2.1 in the future. The specific feature set of each particular build would depend on the hardware capabilities of the device. Neil makes a good point about speed and polish but with a device like the G1 (which I have and love) you will yourself to be limited by the hardware whereas with the Nexus One you can choose to limit yourself or you can choose to develop Live Wallpapers!
Also, you've asked 7 questions and haven't accepted any answers. If you keep that up you'll soon find that people are less willing to spend the time answering your questions.
If you want a test device go for the g1. If you want a good android phone for everyday use go for the droid or the nexus one.
For development be careful which carrier you buy the phone from, some of them like AT&T will change them to forbid installation of software from unknown source etc. to enforce the market. Those are pretty useless for a developer then.