You are currently browsing the tag archive for the ‘Android Google Maps API Ver 2.0’ tag.

This is in continuation to the first two articles of Android Google Maps Api Ver 2.0.

https://mirnauman.wordpress.com/2013/06/11/our-first-android-google-maps-api-ver-2-0-application-part-1/

https://mirnauman.wordpress.com/2013/06/18/our-first-android-google-maps-api-ver-2-0-application-getting-the-android-google-maps-api-ver-2-0-key-part-2/

The objective of this article is to test our Google Maps Api Ver 2.0 Application that we have developed so far in the first two parts of this series of articles on a Physical Device. We need a physical Android device. The one that I have is HTC One X.

HTC-ONE-X

HTC-ONE-X

Identifying which  Android USB drivers to use

Before we start to install the drivers we need to identify which drivers are we going to install.If we have an Android Developer Phone (ADP) like Nexus we will use the Google USB Drivers.  The latest Google USB Drivers can be downloaded using the following link. http://developer.android.com/sdk/win-usb.html and help on how to install it . Only the Galaxy Nexus drivers are provided by Samsung and not Google. We can get the drivers for Galaxy Nexus from the following link. http://www.samsung.com/us/support/downloads/verizon-wireless/SCH-I515MSAVZW . If we have a device other then the above mentioned, we will use OEM Drivers. I own an HTC ONE X so in this article we will go the the OEM Drivers.

Installing the Android USB Drivers

Now that we have identified which device do we have and which drivers we will install. In my case I ll install the OEM drivers for HTC ONE X. The link shows a list of devices and their links from where their USB drivers can be downloaded.  http://developer.android.com/tools/extras/oem-usb.html . So we will go to the HTC page and will click on support to get the drivers. HTC Sync Manager will do the job.  When the appropriate drivers are installed on the computer than  we will move to the next phase.

Setting up Eclipse for our Physical Device

Run Eclipse,  open the DDMS tab. If our emulator is running we will only see the emulator in DDMS. We wont see Physical Device in DDMS.

DDMS not showing the Physical Device

DDMS not showing the Physical Device

Enable the USB debugging from the device. Then in DDMS select the Devices Tab and click on the right most arrow to get the drop down menu , click on Rest adb.

Resetting the adb.

Resetting the adb.

When we Reset the adb, the DDMS will show our Physical Device in the Devices Tab. If not make sure that the device is properly connect to the computer with the USB connecting cable.  This is what you will see when everything goes fine.

DDMS showing our Physical Device in the Devices Tab.

DDMS showing our Physical Device in the Devices Tab.

Deploying our application on the Physical device.

Close all the Emulators, Make sure the Device is connected properly with the computer. In DDMS check in the Devices Tab if its still showing our Physical Device, if it is than its ok, if not then Reset adb as explained earlier. After having the Physical Device in the DDMS go to Run Configuration Screen from where we normally select the AVD or emulator to Run our application. The image below shows the screen.

Deploying our Applicaiton on device.

Deploying our Applicaiton on device.

In the Target Tab click on the dropdown menu, it has three options

  1. Active AVD’s/Active Devices
  2. Active AVD’s
  3. Active Devices

Select the 3rd option, “Active devices” Then Click Apply and Run. If the device is properly connected, and it appears in the DDMS, the system will automatically search for active devices. In our case HTC One X is the active device. The application will be directly deployed on our Device.  When we make some changes to the code, we can deploy the application directly to the device exactly the same way again, but its better to un install the last deployed application and then deploy a fresh copy of our application again on the device from Eclipse.

Note:- This article is not specific for deploying just Google maps applications on Physical Devices. Any application can be deployed on Physical Device using the steps in this article. Secondly , earlier it was not possible to run Android Google Maps APi ver 2.0 on AVD or emulator so we had to test the application on Physical Device. But now its not necessary , now we can test our Android Google Maps API Ver 2.0  applications on emulators or AVDs.

Thats all for now, I ll come up with testing and deployment on emulator soon

I believe that you have gone through the first part of this article. i.e,

https://mirnauman.wordpress.com/2013/06/11/our-first-android-google-maps-api-ver-2-0-application-part-1/

In this part we will go through a detail explanation of getting the Api ver 2.0 key one baby step at a time. I ll try not to skip even the smallest step so that fresh developers finds it easy to make it to the finish line successfully. The main sections covered in this article are

  • Signing the application and why its necessary.
  • Retrieving our application’s certificate.
  • Registering our project
  • Our Api project creation.
  • Obtaining the Api key
  • Adding the Api key to our application

Signing the application and why its necessary.

The signing of the application is not something very complicated or suspicious thing. It is used to identify the author of a certain application. Their is no signing authority involved and it is allowed to use self signed certificates for android application. The private key is with the developer of the application. Without signing our application we will not be able to  get the Android Google Maps API Ver 2.0 key. So we have to do it as any cost.  We will skip a lot of boring theory about this signing application and will go through the important part but if the readers are interested in some more details they can always click on the link “Signing Application Details“. Signing can be in two modes. Signing in Debug mode and Signing in Release mode. In this article I ll only go through the Signing in Debug mode.

Signing in Debug mode

To sign our application in Debug mode first we will make sure that we have the “keytool” utility present at our JDK, JRE install location. The keytool is used to create the debug keystore and key automatically. The key is than used to sign the application automatically. The location of keytool on my system is  “C:\Program Files\Java\jre7\bin\keytool.exe”. the debug.keystore is created with predetermined names and passwords. e.g,

  • Keystore name: “debug.keystore”
  • Keystore password: “android”
  • Key alias: “androiddebugkey”
  • Key password: “android”
  • CN: “CN=Android Debug,O=Android,C=US”

Wc can change the location and name of the debug keystore but for now we will leave it as it is. One thing to make note of is that the self signed certificate of debug mode has a validity of 365 days, than it expires. Now to complete the process we have to retrieve our SHA-1 fingerprint and use it to sign our application and get the api key.

What is SHA-1 fingerprint , where and how to find it.

SHA-1 fingerprint is a unique text string generated by SHA-1 hash Algorithm and as it is unique , Google Maps uses it to  identify the application. To find it there are two ways, first use keytool to generate the SHA-1 fingerprint through command prompt. The command is explained in detail in the  link How to get Google Maps API Key but there is a simple way to find out SHA-1 fingerprint but before we get this fingerprint we need to understand that there are two type of certificates through which we can generate the SHA-1 fingerprint.

  1. The Debug Certificate
  2. The Release Certificate

The Debug certificate is created automatically by the SDK tools when the application is built without exporting it as released application. This certificate can only be used for testing and not for publishing the application as released version. The Release certificate is generated by the SDK tools when a release built of the application is done. With this certificate you can the application can be published. For testing and development we will use the Debug certificate. To display the SHA-1 fingerprint on Debug certificate go to Windows menue in Eclipse and click Preferences, than select Android from the list and click Build. We will see the following screen.

Debug keystore and SHA-1 Fingerprint

Debug keystore and SHA-1 Fingerprint

This is the easiest way to display the SHA-1 fingerprint. Note down the SHA-1 fingerprint. Keytool commands from command prompt can also be used to display the same SHA-1 fingerprint. But i guess using Eclipse to display this is alot easier.

Registering our application

We will use our gmapv2 application that we have created in Part # 1 of this series for registration process. Open a browser and navigate to the following link. Google API Console.

You will be prompted for logging In, Log In with your gmail id and password. You will be taken to the following screen.

Google API Console Main Page

Google API Console Main Page

Expand the top Left Dropdown list Where it is written API Project V2 and click Create. A dialog box will appear where will give our new API Project Name, In the above snapshot I have named it API Project V2. Click the Create project button and you will taken the the following screen.

The services tab in the google api console

The services tab in the google api console

Scroll down in the services and find “Google Maps Android API V 2“. The button in front of it will be showing Off. Click it to turn the service on.

Turning the Google Maps Android API v2  service on

Turning the Google Maps Android API v2 service on

When we turn on the service we will be prompted for Terms of Service. Agree and and click Accept button to proceed. Almost at the finish line to get our API key. Get to the Google API Console. In the navigation bar to the left click API Access.

Obtaining The API Key

API Access Page

API Access Page

From the above screen click on “Create new Android key” button. This will bring us to the following screen.

Configure Android Key for our project

Configure Android Key for our project

Copy your SHA-1 that we have previously displayed and noted down. Paste that in the empty text box and than enter a “;” semicolon at the end of the string and write your complete package name so the complete string becomes SHA-1 fingerprint+;+complete package name.

Key Generation

Key Generation

Click create and you will come to the previous screen with the following addition.

Our Google Maps Android API Ver 2.0 Key and Fingerprint with package name

Our Google Maps Android API Ver 2.0 Key and Fingerprint with package name

As you can see on the screen. Our API Key is listed and below that is the SHA-1+;+complete package name that will be some what like this.

A7:95:FC:3D:A8:1E:4B:CD:9D:D3:E2:E0:1B:D4:9C:39:5A:30:74:7F;com.android.gmapv2

The API Key will look like this.

AIzaSyAlm8fZijW4ViYnxfp-zF8-4-WK6LFY0ik
Copy the key and move on.

Adding the key to our gmapv2 application Open the gmapv2 application in Eclipse. Open the AndroidManifest.xml file and write the following code with your own API Key. Just above the application ending tag.

Putting the API Key in AndroidManifest.xml file

Putting the API Key in AndroidManifest.xml file

Now add the necessary permissions to AndroidManifest.xml file.

Setting up permissions in AndroidManifest.xml file for our first Android Google Maps API Ver 2.0 Application

Setting up permissions in AndroidManifest.xml file for our first Android Google Maps API Ver 2.0 Application

Code of the complete AndroidManifest.xml file will look like this.

Complete code of AndroidManifest.xml

Complete code of AndroidManifest.xml

So far we are done with getting the API Key and putting it in our gmapv2 application. In the next part of this series we will go through all the steps of how to deploy or test this application on actual device. How actual device can be connected to Eclipse. What challenges we will face and what are the solutions for that.

Note : Source code for this article

https://docs.google.com/file/d/0B7W5NGdltb1jeXBvRDNqaV9maFk/edit?usp=sharing

Update 1.0 of this article at the bottom of the page.

Driving agent for this article

There was some stuff that my readers were eagerly waiting for. With the launch of Android Google Maps API Ver 2.0 everything that was in progress with API Ver 1.0 was a mess. The switching had given a hard time to alot of developers as the way even the sample app is successfully executed is way too complicated. I received tons of emails and requests for support specially for getting the Google Maps API Ver 2.0 key and the part where everything seems fine but map is not displayed. A couple of days back i started working on Google Maps API Ver 2.0. I solved the above two issues and alot more but didn’t posted anything because i was in the middle of successfully executing and displaying the Map. The aim was that I’ll start writing once am done with at lease one successful running application and today i have that running app. During this series of articles i ll take my readers from basic setup and configuration to a successful run of their first Android Google Maps  API Ver 2.0 Application.

Before we start I need my readers to keep this in  mind that they need a physical device to develop and test their API Ver 2.0 Application. I am using HTC One X as my physical device

HTC-One-X

HTC-One-X


What we have and what we need

I believe that we have Eclipse installed,  JRE installed and in place as without JRE Eclipse won’t work and Android SDK downloaded and installed, if not Google has made it easy for us with a single download. Download the ADT Bundle for the following link http://developer.android.com/sdk/index.html . The ADT (Android Developer Tools) Includes Eclipse with ADT PlugIn, Android SDK Tools, Android Platform Tools and the latest Android Image for the emulator. You might need to download the JRE and install it to run the IDE. We need the following to get rolling.

  • Physical Device ( I have an HTC One X)
  • Google Play Services
  • Android Support Library
  • An API Ver 2.0 Key
  • OEM USB Drivers (For windows, as am using Windows 7 Professional 64bit)

In part 1 we will only get all these bits and pieces together so that we can make it work in the later sections bit by bit and piece by piece. Lets say we have the Physical Device so we will move to the next thing in the list i.e, Google Play Services. But before we do that we need to start a new project with the name gmapv2 with Android 4.2.2 and Google API Lever 17. (I hope the reader has some background of basic android development.)

Installing Google Play Services

To get the Google Play Services Launch the SDK Manager from within Eclipse. Click Windows>Android SDK Manager. Scroll down the list and mark Google Play Services.  Click the “Install Packages” button and wait till the installation is completed.

Installing Google Play Services

Installing Google Play Services

When the Installation is done, we will add to our project. The easiest way is Right Click on the project and click on Import>Android>Existing Android Code Into Workspace . Browse to the location of the library project.

Importing Google Play Services

Importing Google Play Services

The location of my library project is

F:\Android\adt-bundle-windows-x86_64-20130219\adt-bundle-windows-x86_64-20130219\sdk\extras\google\google_play_services\libproject\google-play-services_lib

We have to take care when doing this. we have to go to the google-play-services_lib inside libproject that is inside the google-play-services folder. When the import is done successful. Now we have to add a reference to our project.

Reference to Google Play Services

Right click on our project and click on Properties. From the list click on Android. Click Add, browse to the google-play-service_lib.

Reference to Google Play Services

Reference to Google Play Services

Now that we are done with Google Play Services, we will come to Google Support Library.

Android Support Library

To add the Google Support Library , right click on the project and click on Android tools. Than click on Add Support Library.

Adding Android Support Library

Adding Android Support Library

Accept the license agreement and install the support library.

Installing Support Library

Installing Support Library

Save your project and we are done with part 1st of this tutorial. In Part 2 we will learn step by step how we will get Google Maps API Ver 2.0 Key. Getting the API key is the most tricky part.

For Android Google Maps Ver 1.0 developers should click on the following link

https://mirnauman.wordpress.com/2012/01/30/using-google-maps-in-android-development-tutorial-part-1/

Note : Source code for this article

https://docs.google.com/file/d/0B7W5NGdltb1jeXBvRDNqaV9maFk/edit?usp=sharing

Update 1.0 (30th JAN 2014):- Before it was not possible to test an Android Google Maps Api Ver 2.0 on Emulator but now its possible. I ll post both the articles soon . Testing the App on physical device and Testing the App on emulator.

Blog Stats

  • 328,669 hits

Enter your email address to follow this blog and receive notifications of new posts by email.

Join 233 other followers

%d bloggers like this: