Is it true that ANY Android phone can be used for App development and testing?
I'm trying to find some inexpensive off-contract hardware for development and testing of our Apps. I've found some devices I can buy New with No Contract for $150 to $300 (like the HTC Aria or the Huawei Ascend). Is there anything that would prevent me from using these devices for USB debugging and app testing? I guess I'm concerned because I've read how the HTC Aria has been locked down by AT&T to limit applications. I suspect this won't affect me loading apps using ADB, but I'd like to be sure.
Yes, you can use any phone for testing applications via the Android development tools. This includes the HTC Aria of what I've read.
You can read more here: http://developer.android.com/guide/developing/device.html
And it is not true what Sam Dufel wrote. A developer phone have messaging and phone features. It's just as any other ordinary unlocked phone. The only difference between the dev-phones is that they have unlocked bootloaders so you can install and customize your own Android-system and install it. It is rooted by default.
Google actually sells development phones - after you create a developer account, they give you an option to buy one of a couple different models. You don't get any messaging / phone features though, obviously.
Related
I am planning a new application that I would like to put on the smartwatch. I would like to have it usable also when there is no phone nearby. The app needs no Internet connection to work, could synchronize data to the phone later and I do not need anything from the phone while the app is running. However I could use the phone no problem to install the app.
I have googled, there are some foggy talks on a web that this is not possible, Android watch must always be connected to the phone for apps to run. How much is it true?
With Android Wear 2.0 it is possible to now develop standalone applications and thus eliminates the need for a mobile 'companion' completely.
Please follow this link for more information: https://developer.android.com/wear/preview/index.html
As I am aware, the current Android Wear version always requires a companion app for installation purposes etc. But with 2.0 this is no longer necessary. It would probably make sense for you to start developing with 2.0 now. That being said, it is still in a development preview and can officially run on only two smart watches (Huawei Watch and LG Watch Urbane 2nd Edition)
Wearable apps are run directly on wearables and don't require presence of a phone except for installation or phone-provided features (voice recognition, SMS, internet connection etc.)
Note that some features are wearable-provided or phone-provided depending on the hardware configuration of the watch/wearable (eg. GPS).
Yes, it is most definitely possible. As long as the wearable app doesn't require any functionality from the phone then it can operate as a standalone device. It will require a companion app on the phone to install the app on the wear device.
There are several wear apps that work without the need to be tethered to the phone, including Google Play music. There is the possibility of designing wear apps for hardware on only a few wear devices - I know that Ghostracer has standalone functionality using GPS, but it requires the wear device to have a GPS chip (it is designed for the Sony SmartWatch 3).
I've developed a couple of Enterprise iOS apps for our users in the field. Some have expressed a preference for Android devices over Apple, and I fully understand. I do not have an Android phone, nor do I want to get one and have a second account to maintain. I'm wondering if I can use an inexpensive Android tablet to reliably test an application that will ultimately be running on an Android phone? The app will need to communicate via internet to a server via cell connection or wifi.
Also, any advice for an Android newbie developer would be appreciated.
Yes you could test on a Android tablet but it would be hard to see how it render on a phone.
You could also use the Android Emulator to test different size and android configuration.
Yes. I developed my first major Android app using only a couple of cheap tablet devices. It's fine; the only thing you can't really test is "what happens to my app when a phone call comes in." Plus if you can get the emulator working under HAXM, or some other similar setup where it doesn't work like a tortoise trapped in amber, you can test on a variety of simulated devices perfectly well.
Other things to consider:
You'll probably want to test your app on a variety of different hardware and Android versions, in particular I'd recommend testing on older devices. This means that you friends' old Android phones are a great source of cheap test devices. I regularly gather phones from friends that would otherwise just end up lingering in the back of a drawer as a "spare" that will never actually get used. Bear in mind that you can use all the features of a phone apart from the actual phone bit without a SIM, including a WiFi-based data connection.
You may find that you can find good, contract-free "pay as you go" phone SIMs. I use a provider whose "credits" don't expire, so I have a phone connection for my test devices where there's no ongoing cost, apart from the actual calls I make when testing.
I just want to know the actual difference between android dev phone, android nomral phone and android rooted phone.
Can we not buy dev phone from a physical shop or from some where else except android marketplace?
Can we buy android rooted phone?
If yes then from where ?
A developer phone can only be bought from Google, if you are a registered developer. The Android source tree contains (almost) all source code needed to re-build and flash the phone.
A normal phone is what you can buy in a shop.
A rooted phone is a normal phone that someone has gained root access to. Root access does not necessarily mean that you can re-build the software, although there are some community-driven projects that will help you do that, for example CyanogenMod.
You can't buy a rooted phone, instead you buy a "normal" phone and root it yourself. Have a look at XDA Developer's forum for some guidelines.
The one exception is the Samsung Nexus S that you can buy as a "normal" phone, unlock the boot loader and then build software for using the Android open source project. I assume the Galaxy Nexus will give you the same possibility, but I haven't tried it myself yet.
If you are developing apps, you do not need root access. You can just use any normal Android phone for that. But if you are developing some platform features, you need a rooted phone or a developer phone. Or you can get one of the many developer boards available, like the Beagleboard and the Pandaboards. These boards will not look like a phone, but they are superb for platform development.
Basically, it all boils down to what you are going to use it for.
You can develop software on almost every android phone but there are some differences.
Dev phone has unlocked bootloader, and will allow you to flash new OS images easily. (but you can unlock bootloader on other phones too, almost every bootloader out there was already hacked, and some phones are unlocked as well)
Phone coming from carrier will contain a ton of crappy carrier branded software, and you will be unable to remove it (but you can root phone, unlock bootloader and flash another OS image voiding all the warranty in process), and there could be some restrictions like "you bad boy do not uses VoiIP - we like to sell you minutes) - but you can also develop software with it
Rooted phone is the same phone, but OS is hacked to allow you root access (there is a linux below the covers) - some applications need this, but it is not really portable. You can develop software with it, but some things working with rooted phone may be unavailable to real users in field.
Conclusion: if you like to see what most users in field are experiencing, stick to standard phone without alterations.
I'm currently stuck on AT&T due to my wife having a new iPhone so I've been eagerly waiting for a phone to come out on AT&T that would be working picking up. That time comes this Sunday with the Samsung Captivate... but I'm concerned with something. With AT&T locking up it's phones to non-Marketplace apps... does that hinder me in any way on developing on the phone?
Sorry if that seems like a stupid question or doesn't belong here... hoping a user with an AT&T phone (HTC Aria or... something) can help.
I'd be surprised if ATT not allowing you to install non market apps would make it so you can't use the phone for testing/debugging. Before you buy an ATT android phone, check out Settings -> Applications -> Development and if you can enable USB debugging then you will be able to use the phone to test your applications.
Hope this helps.
Update: It looks like the HTC Aria has been rooted too which would allow you to basically whatever you want with the phone. This is why Android is the superior mobile OS :)
It is required, for an device to be able ship with Android Market, for it to be usable as a development target. That means full adb support (including installing apps with adb) for integration with the development tools.
ATT is still disabling installation of non market apps so you will not be able to install apps from places other than the market.
You can still develop apps and test/debug on the emulator that comes with the SDK tools though.
Is it possible to install Android in a normal mobile phone?
I have Sony Ericsson Naite which has only key pad interface (No touch). I would like to install Android in my phone for experimenting with it. It will be great if its possible to dual boot Android with Symbian :-).
Do we need any other special hardware to install operating system in a mobile phone? Will Android work on a key-pad mobile?
Any pointer/suggestion is appreciated.
Thank you in advance.
The Naite is a fairly simple handset running on the Sony Ericsson JP8 platform.
End users are not supposed to be able to update the firmware on the phone.
Only Sony-Ericsson partners are supposed to get the PC software to update the firmware and only Sony-Ericsson is supposed to be able to create new firmwares.
(maybe you can hack the phone so you get it to boot on android or symbian but that's going to be unsupported behavior that nobody will guarantee)
If you want to experiment with creating your own android firmwares, I suggest buying an ADP2 handset from google.
If you want to experiment with creating your own Symbian firmwares, I suggest buying a Texas Instrument Zoom 2 device since it is the reference platform for Symbian.
The Zoom 2 seems to also support Android, by the way.
If you just want to experiment with application development on both platforms, I suggest using the two SDKs and emulators first.
There are some pretty cheap Symbian phones out there, particularly in the Series60 3rd edition range and, depending on where you live, you might even be able to find a Pay-As-You-Go Android phone like the Pulse.
I STRONGLY encourage you to go visit the XDA Forums and visit their Android sections for this kind of information.