android debug bridge compatibility question - android

Sorry for the stupid question, but since i don't know the inner workings of android system, i have to ask this. I'd like to buy an android tablet and it's a pretty recent model (link at the bottom), but the fact is that i need it as a development device so a connectivity with adb is a must. So i wanted to ask if its possible that a device would not work with adb on absolutely all operating systems? Is adb a standard os feature that every device has or is it something that a manufacturer has to implement and so may choose not to?
Thank you for your thoughts
The device:
http://www.goclever.net/pl/tablet/359-GCT-T73-.html

So i wanted to ask if its possible that a device would not work with adb on absolutely all operating systems?
Yes. If the device does not legitimately have the Android Market on it, it may or may not support adb, and it may or may not have Windows device drivers for adb.
The device you link to should not have the Android Market on it, as it does not meet the Compatibility Definition Document requirements for Android 2.1 and therefore would not qualify.
I would not use this tablet as your primary development test hardware, unless you are only developing applications for this tablet.

Related

How to use a locally known android phone brand for app development?

i know it might be the same as this question. i am from the philippines as well but the phone mentioned in that link is a samsung which is an internationally well-known brand and i know that adb supports that brand. what i am planning and really want to buy is this locally known phone. it got a really nice specs but i am worrying that i might not be able to use it on app development. i found adb drivers on the net and installed it but i don't know how to use them with android studio. the reason why i want to use a phone for development is because my laptop slows down with i run android studio and the emulator at the same time. if some co-pinoy already know a phone that they already used for app development within the same price range of flare x, please let me know. please guys i really need help on this matter.
Any phone that allows you to enable USB-Debugging will be suitable for android development. Most developers try to stick to a phone that has a clean Android base like a Nexus or Moto X, as it rules out any interference with vendor specific changes to Android (like Samsungs TouchWiz).
See this page for further information on using a hardware device for development. Google does not recommend any specific device.
Also see this list for device vendors providing ADB drivers. If you want to play it safe, stick to these vendors.
This download page suggests that the Google provided driver is suitable for the Cherry Mobile Flare X too.

Difference between Android dev phone, Android normal phone and Android rooted phone

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.

Android - writing apps for not-yet-released devices

I am looking to write an Android app for a device that has not been released to the market yet, and so I will not have the hardware to test upon. I have created an AVD (Android Virtual Device) with as much information as is currently available on the web, so assume that this is as like the device as is possible to get.
However, does anyone have any tips or ideas to make the process of developing for this platform as easy as possible? My current apps have been for personal use on my own phone, so can test performance on the hardware etc. which is obviously not possible in this case. Any gotchas to watch out for (apart from the possibility of the device never being released..!!)
Just follow the SDK.
AVD behaves similar to a real device. I really can't think of something it behaved different on a device and on the AVD.
The only device that brought me trouble is the HTC Hero, first phone with HTC Sense. It didn't follow the SDK and they were calls that weren't there. Newer phones with HTC sense doesn't have this issue, as far as I can tell.

Develop on AT&T Phones

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.

Android installation in a mobile

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.

Categories

Resources