An existing android sdk was detected the setup wizard will only

Get started: Android Studio app development on Windows 7 (Tested on LG G3 phone)

You can still follow this tutorial if you’re using another version of Windows or if you’re using another Android device. You don’t strictly have to use a Windows 7 computer and an LG G3 phone. 🙂

Being a web developer and a frequent user of Android devices, I’ve always been curious about Android app development. I’m really happy that I’m finally able to create even the simplest Android app (i.e., displaying Hello World! lol) 😆

You are on this page most likely because you are just curious like me, or because you need to learn Android app development for school or work.

My development environment as I wrote this tutorial:

• 3-year-old ASUS laptop, 32-bit system, 4 GB RAM, Intel Core i5-2410M, 2.36GHz processor (Android Studio is slowing this laptop down significantly)
• Windows 7 (you can use any other Windows version to follow this tutorial)
• Android Studio 1.4
• LG G3 as test device (you can use a different phone, of course)

How to say “Hello World!” on your first Android app

Install JDK (Java SE Development Kit)

Make sure to check if you are using 32-bit or 64-bit Windows and download the appropriate installer version. The installers for 32-bit and 64-bit Windows are not interchangeable. In my office laptop I installed jdk-7u79-windows-x64.exe but since it is for 64 bit and incompatible with my 32-bit Windows at home, I downloaded jdk-7u79-windows-i586.exe from the source.

Install Android Studio.

When someone in your team, or when you download Android Studio completely for the first time, copy the sdk folder from this path and store it somewhere for future use:

Please note that this can take a while. It took me about 30 minutes to finish copying in an old laptop that uses Intel Core i5 CPU.

The installation of Android Studio requires Internet connection for the contents of the sdk folder, and it will be trouble if you have a very slow connection to the Internet. It will be handy to keep a copy of the sdk folder as backup, so that every time you need to install Android Studio, you just have to “cancel” the download that doesn’t seem to end (when it says Downloading Android SDK Build-tools) and just paste the contents of your backup sdk folder into the folder where you are currently installing SDK into D:\Users\YourUsername\AppData\Local\Android\sdk . When you try to start a new project, you might run into an error saying “Your Android SDK is missing, out of date, or is missing templates.” To fix this, do the following:

1. Click OK to close the dialog then click Configure.
2. Click SDK Manager.
3. Find the field where you can Edit the path for your Android Studio SDK — click on “Edit”.
4. You probably see this message in red: “An existing Android SDK was detected. The setup wizard will only download missing or outdated SDK components.” Just keep on clicking Next until you can see a Finish button

Now, you can start a new Android project in Android Studio!

1. Press the back button and find the “Start a new Android Studio project” button.
2. Set your Application Name and Company Domain. Change Project Location if desired. These are up to you.
3. Click next.
4. Click next again, leaving only Phone and Tablet as our platform.
5. Select “Empty Activity” then click next.
6. Change “Activity Name” and “Layout Name” if desired (I leave them as is), then click Finish button. (It is taking ages for my project to load after creation. Ugh! :lol:)
7. If Android Studio hasn’t opened MainActivity.java and activity_main.xml for you, then follow these steps:
   1. On the left side of the screen, click Project, then in the directory tree, navigate to app -> res-> layout then double click activity_main.xml to open it.
   2. Make sure you are on the “Design” tab (at the bottom part there should be 2 tabs: Design and Text. Click Design.) This will show you a preview of the app that says Hello World!

If you see the “Hello World”, good! I would congratulate you, but if you’re like me, you probably didn’t feel any accomplishment in seeing that Hello World in your computer screen. After all, an Android app is supposed to be run in an Android device. You can stop here, or you can read the next steps as I guide you in setting up your computer, Android Studio, and Android device so that you can run the app you are developing in your phone or tablet.

Prepare your Android device for running your app.

Allow me to use the words “phone” and “device” interchangeably — just a little warning to keep you from being confused. 😆 After all, the “device” I’m using for this tutorial is a “phone” 🙂

Install PdaNetfor USB debugging of your phone (ADB driver):

1. Download PdaNet installer here. Just follow the instructions from the installer during the process. You need to finish this so that Android Studio can run apps on your phone.
2. Let me tell you how I successfully let my Android Studio run apps on my LG G3 phone…
   1. While PdaNet was installing, I closed Android Studio (it consumes a huge portion of memory in mine) during the process, hoping my computer runs the pdanet installation a little faster.
   2. I installed PdaNet from Google Play Store into my phone, as instructed by the PdaNet installer on my computer.
   3. After PdaNet was installed to my phone, I opened it and enabled the “Activate USB Tether” option.
   4. When I run Android Studio again, with my MainActivity.java and activity_main.xml still open, I pressed Shift + F10 to attempt to run the app on my phone.
   5. Yes, my LG G3 was listed as a connected device but Android Studio says that my device is offline.

   To fix the “device is offline” problem, what I did was unplug my phone from the computer and then plug it back in. On my phone, there was a prompt to “Allow USB Debugging” and I allowed it. Then, pressing Shift + F10 again on Android Studio allowed me to choose my LG G3 phone. When I pressed OK, the Hello World! screen was displayed on my LG G3. 🙂

Your device is still not able to run your app from Android Studio? Try any of these:

Possible fix #1: Set connection mode on your phone from MTP to PTP

You probably read earlier that unplugging and plugging my device back into my computer let Android Studio detect my LG G3 as an online device. I realized that my connection was already set to PTP back then.

I tried switching to MTP and as a result, Android Studio took out my device from the list.

I switched back into PTP mode and Android Studio brought my device back to the list.

So, that confirmed that LG G3 needs to connect to the computer in PTP mode so that Android Studio can run apps in it.

Possible fix #2: Install LG program/driver(s)

1. When you plug your device into the computer, you’ll see something like “Connected as Media Device (MTP)”.
2. Go to your notifications panel and click on such notification.
3. A popup will appear: “Install PC programs required when connected to computer. -If you have installed on your computer, skip by checking Don’t show this again.” Then if you click OK, you’ll see “Installing PC programs. Please check your PC.”
4. On your computer you’ll see AutoPlay dialog, click on Run_LG_PC_Programs.exe.
5. Now on your computer you’ll see “LG USB driver for LG phone is being installed”. KEEP THE DEVICE CONNECTED TO YOUR COMPUTER DURING THIS PROCESS!
6. When done, you’ll see a message in the computer: “The drivers for LG phone are now installed. You can connect your PC and phone.”
7. Click OK.

(If you’re using an LG phone and if this doesn’t work try to install LG drivers from this link too …I had to download that one for my phone to work on my office laptop’s Android Studio. )

Other notes

Each time you run the app, an APK file is generated in app/folder/app/build/outputs/apk/

Thanks, acknowledgement, sources…

Thanks to my office friends Nethki, Allen, and Peng for ideas and guidance, as well as to my boyfriend. 🙂 I probably couldn’t have started anything at all without you all. 😀

Источник

How to install Android SDK and setup AVD Emulator without Android Studio

If you are trying to develop to Android, you probably will end up installing the Android Studio to get the Android SDK and the AVD Emulator working properly.

But if you are using another code editor, like Sublime Text or VSCode, installing the Android Studio will just mess up with your setup and consume your precious RAM for no good reason.

I had a hard time figuring out how to properly do this setup due the lack of documentation about it, so i hope this article helps you. 🙂

Recommended previous knowledge:

• SDK (Standard Development Kit); Read about on Wikipedia;
• AVD (Android Virtual Device); Read about on docs;
• CLI (Command Line Interface); Read about on Wikipedia;
• Android API levels; Read about on Vanderbilt University;
• How to open, navigate and execute files in your OS terminal;
• Know what are environmental variables;

Understanding the Android SDK

Basically, the Android SDK is a bunch of packages necessary to develop for Android.

These packages stays in subfolders of a folder called “sdk” (or “android-sdk” sometimes). You do not need to know how these packages really work, just what they do.

The picture below is my Android SDK folder, these are the basic packages you will need in order to get everything working properly.

Here is a brief explanation of each package:

• tools: This package is mainly used to manage the other packages and to create AVD’s;
• emulator: As the name suggest, this is the Android emulator;
• platform-tools: Some tools to communicate with Android devices when you plug then in your computer;
• patcher: This package is automatically downloaded by the SDK. I didn’t find what exactly this is for, so just leave it as it is;

The folders bellow contain sub-folders with the packages for each Android API level.

• platforms: The platform packages are required to compile your app for the specified API level.
• system-images: These are the android images used in the emulator.
• build-tools: These are necessary to build your Android apps

Installing the Android SDK

In order to install the SDK we will use the Command Line Tools. These are some quite simple CLI’s used to manage the Android SDK. You can read the documentation here for more details.

Step 1 — Download the tools package

First, you need to download the tools package. And with this package you can download the others.

1. First, go to the Android Studio download page: https://developer.android.com/studio;
2. Then click in “ Download Options”;
3. There you will find a table named “ Command line tools only”;
4. This table contain some zip files. Download the appropriate file for your system ( Windows, Mac or Linux);
5. Extract this zip and you will get a folder called tools: This is the tools package i explained earlier;

Create a folder anywhere you prefer to place your SDK. I recommend you to stick with one of these commonly used places:

• Globally: C:\Android\sdk or C:\android-sdk (this is not default, but i usually set my SDK here on Windows)
• One user only: C:\Users\ \AppData\Local\Android\sdk

• Globally: /Library/Android/sdk
• One user only: /Users/ /Library/Android/sdk

And move the tools folder to this new sdk folder. Make sure you have admin access to this folder and any sub-folders inside it, or the tools package will fail to download new packages.

Note: You can also download a pre-build package for your SO (like the one available on Ubuntu repository). But i do not recommend you do to so, because they probably will not be updated and will be harder to manage, since it was automatically installed.

Step 2— You need Java 8!

The Android SDK packages require Java 8. If you do not have it, you need to download. If you are using a newer version, you have to downgrade to Java 8 or you will eventually get some errors, because it is not compatible.

If you do not have the Java 8 SDK, here is how you can install it:

On Ubuntu run these commands:

• # sudo apt-get update
• # sudo apt-get install openjdk-8-jdk

Sorry for MacOS users, i don’t know how to install it on this OS.

Step 3 — Download the essential packages

Now, download the platform-tools and the emulator packages, because they contain some CLI binary files you will need later. I decided to download these packages first in order to set all the necessary environment variables at once and make the rest of the process easier.

Open a terminal window (you need to use a terminal, not the file explorer), go to your sdk folder and navigate to the /tools/bin directory.

This folder contain the SDKManager binary: this is a CLI used to list the available packages in the Google’s repository and download, update or remove them from your SDK folder.

The bellow command will list all packages installed (the first items on the list) and all packages available to download:

To download the packages, simply copy the package names and pass it as a parameter to the SDKManager CLI using the terminal:

# ./sdkmanager platform-tools emulator

If you open your sdk folder you should see these packages folders there.

Step 4 — Set your environmental variables

You need to set the below environmental variables containing the path to our SDK, so any running program can find it in your pc:

ANDROID_SDK_ROOT = Path to your SDK folder

ANDROID_HOME = The same as ANDROID_SDK_ROOT. This variable is now deprecated, but i recommend setting it because some programs still using it to locate your sdk.

And add these folders to the PATH variable, making their binary files accessible from everywhere:

To add the environment variables on WIndows, just follow these steps:

1. Open the “Control Panel”;
2. Go to “ System and Security” option in the side menu;
3. In the window “ System Properties” open the tab “ Advanced”;
4. Click in the button “ Environment Variables” in the bottom of the page;
5. In the “ Environment Variables” window you will see two tables: “User Variables” and ” System Variables”.
6. If you created your sdk folder for one user only, set the variables in the “ User Variables” table;
7. But, if you create your sdk folder globally, set the variables in the “ System Variables” table instead;

On Linux, you can set your environment variables in many places. So i choose the ones I found the most appropriate:

If you created your sdk folder for one user only, set your environment variables in the file

/.bashrc;

If you created your sdk folder globally, set your environment variables in the /etc/environment file. But, be very careful! if you do something wrong with the path variable in this file you will broke your system (yes, i did this). This file is not a script, so you can’t use variables like $HOME, you need to write the full path to the folders. Variables declared in this file just will take effect after you logout .

Here is how i set these variables in my Ubuntu, using the file /etc/environment:

And sorry again, no MacOS instructions for this task.

You can find more about these environmental variables in the oficial docs here.

Now your SDK is ready! If you do not need to run the emulator there’s no need to follow the next steps.

Step 5 — Download the platform specific packages you want

You need more three packages: The platform, the system-image and the build-tools. You can download these packages for any Android version you prefer. In this article, i will download the packages for the API Level 28.

Use the “ sdkmanager — list” command to find these packages and download them using the command “ sdkmanager

Here’s an example:

Step 5 — Create a AVD device

Creating a AVD device is a simple task: run the AVDManager command (this is a binary file located in the tools/bin folder of your sdk) with the create avd option, a name for the new AVD and the image you want to use.

Here is a example:

# avdmanager create avd — name android28 — package “system-images;android-28;default;x86”

You will be asked if you want to alter some configurations. You can also modify these configurations later in the file config.ini, located in the avd folder (this folder usually is created in your user folder, under the android directory). The currently active configurations can be find in the file hardware-qemu.ini (this file just will be created after the emulator runs for the first time).

Step 6 — Run the Android Emulator

Now you just need to run the emulator command (remember that we added this package to the environmental variables?):

The emulator take some time to init for the first time. But if you done everything correctly you should see this screen:

Источник