Do you write Android apps on AMD CPU Windows 10 using Microsoft Android Emulation?

Do you write Android apps on AMD CPU Windows using Microsoft Android Emulation
http://www.bild.me/bild.php?file=8562677amd_emulation_05.jpg

*What is the trick to get Android Studio to _use_ the MS Android Emulator?*

I was able to install the Microsoft Android Emulator on AMD-based Windows
10 Pro, which _should_ allow Android Studio to run apps on that emulator
even though the dekstop is an AMD-based desktop (so Intel HAXM won't work).
http://www.bild.me/bild.php?file=3799337amd_emulation_01.jpg
http://www.bild.me/bild.php?file=5017616amd_emulation_02.jpg
http://www.bild.me/bild.php?file=8615530amd_emulation_03.jpg
http://www.bild.me/bild.php?file=9950110amd_emulation_04.jpg
http://www.bild.me/bild.php?file=8562677amd_emulation_05.jpg

But I'm not sure how to get Android Studio to run on that MS Emulator.
https://visualstudio.microsoft.com/vs/msft-android-emulator/

Do you write Android apps on AMD CPU Windows using Microsoft Android Emulation?
If so, what's the trick to get Android Studio 3.2.1 to use the MS emulator?
http://www.bild.me/bild.php?file=8562677amd_emulation_05.jpg

On 11/2/2018 6:07 PM, Arlen_Holder wrote:
Do you write Android apps on AMD CPU Windows using Microsoft Android Emulation
http://www.bild.me/bild.php?file=8562677amd_emulation_05.jpg

*What is the trick to get Android Studio to _use_ the MS Android Emulator?*

I was able to install the Microsoft Android Emulator on AMD-based Windows
10 Pro, which _should_ allow Android Studio to run apps on that emulator
even though the dekstop is an AMD-based desktop (so Intel HAXM won't work).
http://www.bild.me/bild.php?file=3799337amd_emulation_01.jpg
http://www.bild.me/bild.php?file=5017616amd_emulation_02.jpg
http://www.bild.me/bild.php?file=8615530amd_emulation_03.jpg
http://www.bild.me/bild.php?file=9950110amd_emulation_04.jpg
http://www.bild.me/bild.php?file=8562677amd_emulation_05.jpg

But I'm not sure how to get Android Studio to run on that MS Emulator.
https://visualstudio.microsoft.com/vs/msft-android-emulator/

Do you write Android apps on AMD CPU Windows using Microsoft Android Emulation?
If so, what's the trick to get Android Studio 3.2.1 to use the MS emulator?
http://www.bild.me/bild.php?file=8562677amd_emulation_05.jpg

When you receive a rim job from Donald Trump,
does he jerk your dick at the same time?

On Fri, 2 Nov 2018 22:07:45 -0000 (UTC), Arlen_Holder wrote:

*What is the trick to get Android Studio to _use_ the MS Android Emulator?*

It turns out very many people have the issue I'm having which is simply
that Android Studio won't send the app to the Microsoft Android Emulator.

A key problem that is critical to keep in mind for anyone trying
to solve this is that there are Intel & AMD CPUs out there.
o Any solution for Intel CPUs does _not_ apply to AMD CPUs.
o Any solution for AMD CPUs does _not_ apply to Intel CPUs.

This is a key distinction because _most_ of the solutions are Intel only.
Hence, if a solution doesn't list AMD, by name, that solution is worthless.

It turns out that AMD was only recently supported by Google in July 2018.
https://www.infoq.com/news/2018/07/android-emulator-amd-hyperv

Which says as of Android Studio beta 3.2 emulation should work on AMD CPUs
https://android-developers.googleblog.com/2018/07/android-emulator-amd-processor-hyper-v.html

As far as I know, I meet the requirements, but Android Studio 3.2.1 is
still not sending the java files to execute on the Microsoft Android
Emulator yet.
[x]AMD Processor
[x]Android Studio 3.2 Beta or higher (I'm using Android Studio 3.2.1)
[x]Android Emulator v27.3.8+ (I'm using the latest MS Android Emulator)
[x]x86 Android Virtual Device (AVD) - Create AVD
[x]Windows 10 with April 2018 Update
[x]Enable via Windows Features: "Windows Hypervisor Platform"

I also added "adb" (which is in the SDK) to the path and I added the
registry key which is supposedly what the Microsoft Android Emulator
is hard coded to, but neither worked any better than nothing.
https://www.clearlyagileinc.com/agile-blog/using-the-visual-studio-android-emulator-with-android-studio

1. Start the Microsoft Android Emulator set to the device to be emulated:
emulatorcmo.exe /sku:Android launch /id:363F7AED-462C-46BD-9FEC-F1DD3B79916C
2. Start your Android Studio and open up your project:
3. Configure Android Studio to use your new emulator by navigating to:
AndroidStudio321:Run Edit Configurations Defaults Android App
General Deployment Target Options Open Select Deployment Target Dialog
[x] Use same device for future launches
4. Run your app in Android Studio
AndroidStudio321:Run Run app
5. You'll be prompted to "Select Deployment Target"
6. Notice your MS Android Emulator is completely missing from the selections!
7. The issue really boils down to where the new emulator is looking for the
Android SDK. In most default installations of Android Studio bundled
with the SDK, the SDK is stored under:
C:\Users\[USER]\AppData\Local\Android\Sdk
The developers who wrote the MS Android Emulator hard-coded the path
to the SDK as: C:\Program Files (x86)\Android\android-sdk
AndroidStudio321: File Project Structure SDK Location
Android SDK location = C:\app\hardware\android\sdk
8. The developers of the MS Android Emulator store this hard-coded path
to the Android SDK in the Windows registry:
Start Run regedit
9. This key is "supposed" to exist, but it doesn't exist for me:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Android SDK Tools\
10. What exists for me is only:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\
11. So I created this key:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Android SDK Tools\
12. And set its string value to:
C:\app\hardware\android\sdk
13. It still didn't show up, so I rebooted the Windows 10 Pro desktop.
a. I started Android Studio 3.2.1
b. I started the MS Android Emulator
AndroidStudio3.2.1: Tools External Tools MS Android Emulator
c. I ran the app to get the "Select Deployment Target" window
It says "Initializing ADB" (so it's "adb" that doesn't see it!)
Drat. The MS Android Emulator _still_ doesn't show up.
c:\app\hardware\android\sdk\platform-tools\adb.exe

The question is which to add to the path?
c:\app\hardware\android\sdk
or
c:\app\hardware\android\sdk\platform-tools

Start Run %windir%\System32\rundll32.exe sysdm.cpl,EditEnvironmentVariables
BEFO
PATH=C:\Windows\system32;C:\Windows;C:\Windows\Sys tem32\Wbem;C:\Windows\System32\WindowsPowerShell\v 1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files (x86)\Microsoft Emulator Manager\1.0\;C:\Users\[user]\AppData\Local\Microsoft\WindowsApps;

AFTER:
PATH=C:\Windows\system32;C:\Windows;C:\Windows\Sys tem32\Wbem;C:\Windows\System32\WindowsPowerShell\v 1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files (x86)\Microsoft Emulator Manager\1.0\;C:\Users\[user]\AppData\Local\Microsoft\WindowsApps;c:\app\hardwa re\android\sdk\platform-tools;c:\app\hardware\android\sdk\platform-tools;

Here are related screenshots showing that everything is close,
where the _only_ thing not working, is that the Android IDE isn't sending
the java code to the Microsoft Android Emulator.

The java code from the IDE runs perfectly on the Android phone over USB:
o http://www.bild.me/bild.php?file=2116419androidstudio06.jpg

But the emulation does not work yet on the AMD CPU:
o http://www.bild.me/bild.php?file=3945600androidstudio07.jpg

Windows 10 Pro has the virtualization technology enabled:
o http://www.bild.me/bild.php?file=5832994androidstudio08.jpg

Which is compatible with AMD CPUs according to AMD checking tools:
o http://www.bild.me/bild.php?file=3975030androidstudio09.jpg

The MS Android Emulator pops up from from within Android Studio 3.2.1:
o http://www.bild.me/bild.php?file=2583074androidstudio10.jpg

But Android Studio 3.2.1 won't _send_ the java files to that emulator!
o http://www.bild.me/bild.php?file=6690816androidstudio11.jpg

Where I can't get the Microsoft Android Emulator to show up in the choices!
o http://www.bild.me/bild.php?file=2685733androidstudio12.jpg

Even though I have run the "Import Hardware Profile" GUI many times:
o http://www.bild.me/bild.php?file=1910896androidstudio13.jpg

Pointing to the cfg file provided by Microsoft for the Android emulator:
o http://www.bild.me/bild.php?file=8075950androidstudio14.jpg

*What is the trick to get Android Studio to _use_ the MS Android Emulator?*

On Sun, 4 Nov 2018 07:53:49 -0000 (UTC), Arlen_Holder wrote:

It turns out very many people have the issue I'm having which is simply
that Android Studio won't send the app to the Microsoft Android Emulator.

A key problem that is critical to keep in mind for anyone trying
to solve this is that there are Intel & AMD CPUs out there.
o Any solution for Intel CPUs does _not_ apply to AMD CPUs.
o Any solution for AMD CPUs does _not_ apply to Intel CPUs.

It seems that Microsoft "incuded" Google to fix their emulation (???)

It appears that Microsoft implies the following sequence of events:
http://www.bild.me/bild.php?file=5287229emulation01.jpg
a. Google (apparently) didn't support hardware acceleration on Windows
b. So Microsoft built an Android Emulator that did work on Windows
c. Some time thereafter, Google responded by fixing their bugs

At least that's implied when you read the orange header he
https://visualstudio.microsoft.com/vs/msft-android-emulator/
"Note: After we released the Visual Studio Emulator for Android,
Google updated their Android emaulator to use hardware acceleration.
[Hence] We recommend you use Google's emulator when you can, as it
offers access to the latest Android OS images and Google Play services.
If you have enabled Hyper-V, try out our Hyper-V Android emulator
compatibility preview to run Google's emulator on Hyper-V directly"
https://docs.microsoft.com/en-us/xamarin/android/get-started/installation/android-emulator/hardware-acceleration?tabs=vswin&pivots=windows

The good news is that this implies that Google's Android emulator "should"
work with hardware acceleration on Windows PCs, where I've learned the hard
way that Intel-based Windows PCs are far better supported for hardware
acceleration than are AMD-based Windows PCs.

It turns out that any reference that does not mention AMD is worthless when
it comes to getting an AMD-based Windows desktop to work with emulation.

The good news is that the reference above _does_ mention AMD, so it's at
least useful for those of us on the lowly AMD-based Windows desktops.

On Mon, 5 Nov 2018 17:00:31 -0000 (UTC), Arlen_Holder wrote:

The good news is that the reference above _does_ mention AMD, so it's at
least useful for those of us on the lowly AMD-based Windows desktops.

This is a classic Windows hardware acceleration setup problem, I think.

The problem is emulation hardware acceleration on Windows, since the java
code works perfectly on the phone itself when sent over from Windows:
http://www.bild.me/bild.php?file=2596267androidstudio06.jpg

What complicates things is that any reference that talks about emulation
and/or acceleration without mentioning AMD, is utterly worthless for
debugging on AMD-based Windows desktops because HAXM just won't fly:
http://www.bild.me/bild.php?file=4100603androidstudio07.jpg

Even though I was sure that Hyper-V was enabled on Windows 10 Pro based on
the output from the Windows "System Information" dialog box:
Start Run %windir%\system32\msinfo32.exe

It seems that Windows 10 was reporting false information:
http://www.bild.me/bild.php?file=1288358androidstudio08.jpg

I was also sure that Hyper-V was working based on the output from
the AMD-supplied AMD-based Windows Hyper-V checking tool:
http://download.amd.com/techdownloads/AMD-VwithRVI_Hyper-V_CompatibilityUtility.zip

Which (erroneously?) reported that all was well with Hyper-V:
http://www.bild.me/bild.php?file=8692170androidstudio09.jpg

And yet, there were hardware-acceleration errors when sending *.java code
from Android Studio to the Microsoft Android Emulator on an AMD desktop:
http://www.bild.me/bild.php?file=7953529androidstudio10.jpg

However, it seems I missed a step in enabling Hyper-V on Windows 10 Pro:
https://docs.microsoft.com/en-us/xamarin/android/get-started/installation/android-emulator/hardware-acceleration?tabs=vswin&pivots=windows

Which recommended first that we run the Windows winver command:
Start Run winver
http://www.bild.me/bild.php?file=9332564androidstudio20.jpg

And then we run the far-more-detailed systeminfo command:
C: systeminfo c:\tmp\systeminfo.txt
Should show Hyper-V (& Windows Version 1803 to at least OS Build 17134.1).

And then which suggested we run the Windows "OptionalFeatures" command:
C:\Windows\System32\OptionalFeatures.exe
In order to ensure that Windows is set to:
Enable both Hyper-V and Windows Hypervisor Platform:
Where my first results were, astoundingly, after all this, as follows:
http://www.bild.me/bild.php?file=6807107androidstudio18.jpg

*Now how did _that_ happen, even after the AMD & Windows checks?*

Moving on, obviously I checked that "Windows Hypervisor Platform" box!
http://www.bild.me/bild.php?file=7013607androidstudio19.jpg
and rebooted.

*That checkbox made a _huge_ difference in Windows hardware acceleration!*

The result was that, back in Android Studio 3.2.1, for the first time, the
default Google Android Emulator finally pops up for the very first time!
http://www.bild.me/bild.php?file=1034642androidstudio23.jpg

But it is blank and unresponsive, where Android Studio displays a
completely different set of errors that were not seen prior:
Emulator: Warning: Quick Boot / Snapshots not supported on this machine. A CPU with EPT + UG features is currently needed. We will address this in a future release.
Emulator: emulator: WARNING: Host CPU is missing the following feature(s) required for x86 emulation: SSSE3
Emulator: Hardware-accelerated emulation may not work properly!

Regarding these errors:
Emulator: Warning: Quick Boot / Snapshots not supported on this machine. A CPU with EPT + UG features is currently needed. We will address this in a future release.
Emulator: emulator: WARNING: Host CPU is missing the following feature(s) required for x86 emulation: SSSE3
Emulator: Hardware-accelerated emulation may not work properly!

These "EPT" & "UG" & "SSSE3" features seem to indicate:
o EPT = Extended Page Tables (aka SLAT second level address translation)
o UG = Unrestricted Guest (aka "real mode")
O SSSE3 = Supplemental Streaming SIMD Extensions 3 (cpu instructions)
https://en.wikipedia.org/wiki/SSSE3

Windows PowerShell will report your processor family:
PowerShell gwmi win32_processor

The Sysinternals "coreinfo" tool tells us which features exist in a CPU
https://docs.microsoft.com/en-us/sysinternals/downloads/coreinfo
Sysinternals coreinfo output shows either an asterisk or a dash where
"*" means the feature is present
"-" means it is missing
https://social.technet.microsoft.com/wiki/contents/articles/1401.hyper-v-list-of-slat-capable-cpus-for-hosts.aspx

This tells me EPT (aka SLAT) is not supported on my CPU:
C:\ coreinfo -v
HYPERVISOR * Hypervisor is present
SVM - Supports AMD hardware-assisted virtualization
NP - Supports AMD nested page tables (SLAT)

Wikipedia says my AMD FPU supports SSE3 but not SSSE3 & coreinfo concurs:
C:\ coreinfo | findstr "SSSE3"
SSSE3 - Supports Supplemental SIMD Extensions 3

So I may have to give up getting Android emulation to work on my AMD CPU,
but there's one more test I can run, I think, which is to use an ARM CPU:
https://youtu.be/OjD9t1bfYsY?t=193
Where the guy says we can "just click on the ARM processor".

On Mon, 5 Nov 2018 20:47:28 -0000 (UTC), Arlen_Holder wrote:

So I may have to give up getting Android emulation to work on my AMD CPU,
but there's one more test I can run, I think, which is to use an ARM CPU:
https://youtu.be/OjD9t1bfYsY?t=193
Where the guy says we can "just click on the ARM processor".

Solved ... sort of.

I'm not sure exactly how I solved it since I tried many things,
but here's the current status (which has a few glitches remaining)
and where I'm not sure which "trick" is what made it finally work.
o I think it was the "Windows Hypervisor Platform" checkbox
FROM: http://www.bild.me/bild.php?file=9981202androidstudio18.jpg
TO: http://www.bild.me/bild.php?file=9740339androidstudio19.jpg
o Also changing the Google emulator to run on ARM instead of X86
http://www.bild.me/bild.php?file=2999468androidstudio24.jpg

These are the three devices I currently tried to emulate:
http://www.bild.me/bild.php?file=7607398androidstudio31.jpg
o Rounded corners: Nexus S API 25 ARM (Android 7.1.1, API 25)
o Squarish corners: Nexus 5X API 25 ARM (Android 7.1.1, API 25)
o Bottom Right: MS Android Emulator x86 (Android 5.1.1, API 22)
http://www.bild.me/bild.php?file=3093498androidstudio30.jpg

One issue with ARM over X86 emulation is that ARM is 10x slower:
http://www.bild.me/bild.php?file=2999468androidstudio24.jpg

The Microsoft emulator (right) was, by far, _faster than Google_:
http://www.bild.me/bild.php?file=4854975androidstudio25.jpg

But, eventually, all three emulators (Google, ARM, & MS) came up:
http://www.bild.me/bild.php?file=6567987androidstudio26.jpg

All 3 had some issues with Android OS apps pre-installed on them.
http://www.bild.me/bild.php?file=8587828androidstudio27.jpg

But all three were invoked by the IDE; where only 1 ran the app:
http://www.bild.me/bild.php?file=1405186androidstudio28.jpg

It's preliminary to confirm that it's working, but my tentative
recommendation is to run the Microsoft Emulator choosing x86
instead of running the Google emulators on x86 or ARM.
http://www.bild.me/bild.php?file=7301488androidstudio29.jpg

Since this problem is extremely common on AMD Windows machines,
I found a lot of "guesses", many of which I tried, where I
"think" the two that finally worked, sort of, we
1. Running the Google emulators as ARM (not x86) enabled
the Android Studio IDE to invoke them and for them to
populate their operating system - but - the Android IDE
"adb" command did not send the APK to run on the emulated
Nexus devices.

2. Running the Microsoft emulator as x86 worked almost
perfectly, in that it was more than 10 times faster
than the Google emulations running as ARM, and better
yet, the Android Studio IDE "adb" was able to send the
"Hello World" APK to the Microsoft emulator, where the
only minor glitch was that there were apps that had
to be stopped in the background for some reason.

My tentative recommendation for AMD Windows users is:
o You can run the Google emulators as ARM (but not x86)
o But it's better to run the Microsoft emulator & as x86.

On Mon, 5 Nov 2018 23:42:29 -0000 (UTC), Arlen_Holder wrote:

Since this problem is extremely common on AMD Windows machines,
I found a lot of "guesses", many of which I tried

BTW, one of the "guesses" were the "paths", where I proved that the paths
were not the problem (they were just a red herring).

The task on paths when installing software is to be logically consistent.

It's no different than organizing your tools in your garage at home.
It's always logically consistent!

You don't let the Home Depot guy organize your tools in your toolbox.
He would put all the Home Depot tools in one drawer, called "Home Depot".

You don't let the Lowes tool guy organize your tools in your toolbox.
He would put all the Lowes tools in one drawer, called "Lowes".

IMHO, people should organize their tools to be logically consistent.
Their tools should be organized the way they think.

I happen to think of tools in terms of "functionality".
I organize my tools by what they "do".

For example, these new "things" needed places to go:
1. JDKs & JREs (e.g., Oracle Java development kits & runtime environments)
2. SDKs (e.g., the Google Android SDK at various API levels)
3. Emulators (e.g., Google, Genymotion, & Microsoft Android emulators)
4. IDE's (e.g., Google & Microsoft & Eclipse development environments)
5. CPU tools (e.g., Intel HAXM virtualization & AMD Hyper-V debuggers)
6. Project files (e.g., APK hierarchies)
7. Tutorial files (e.g., videos)

Just like you put your tools in your garage tool boxes where you can find
them (which is likely not in the same place your wife would leave them), I
can't tell you where to put your tools.

However, I can tell you that each of these tools, if you let it default,
will go in a completely different location than the other tools.

To keep control over where things go, I put them _all_ in logical places!
A. I put the tools in C:\app\editor\android (I never use plurals)
B. I put my projects in C:\tmp\android (I use short names when possible)

That's it.

Whenever I need to *find* something, it's either a tool (which is in a
single tool directory) or it's my temporary files (which are in a single
project directory).

For example on tools, both the Android IDE & the Microsoft IDE are in:
C:\app\editor\android\ide\{android_studio,visual_s tudio}

Note that the installers follow the same logical hierarchy:
C:\software\editor\android\ide\{android_studio,vis ual_studio}

Note that the menus follow the same logical hierarchy:
Start Menu editor android ide {android_studio,visual_studio}

The same logical consistency carries over to all the components.

It's all very well thought out, and very logical, and, it carries over from
one machine to another, such that the menus from Windows XP work perfectly
when literally copied over to Windows 10, for example.

I suggest people who install these complex tools, simply be consistent.

On Fri, 2 Nov 2018 22:07:45 -0000 (UTC), Arlen_Holder wrote:

*What is the trick to get Android Studio to _use_ the MS Android Emulator?*

Woo hoo! *EVERYTHING WORKED PERFECTLY!*
I deleted everything & started fresh with my 20:20 hindsight experience!

Only one Windows freeware package is needed on newer Intel & AMD CPUs:
a. Android Studio freware

Only two Windows freeware packages are needed on old AMD CPUs
a. Android Studio freware
b. Microsoft Emulator freeware

Once I figured out the tricks, everything worked flawlessly!
o The Microsoft Emulator freeware popped up without any errors:
http://www.bild.me/bild.php?file=9766951androidstudio33.jpg
o And the Android Studio IDE freeware ran on that emulator sans errors:
http://www.bild.me/bild.php?file=8780131androidstudio34.jpg

The result is that any apps we write using this Windows freeware...
o Can run in the Samsung Galaxy S5 emulation on Windows, or,
o They can run directly on my LG Stylo 3 Plus phone over USB.

Given my new 20:20 hindsight experience, the solution is this simple!
0. You enable Hyper-V & Hypervision in the BIOS & in Windows
1. You install the Android Studio IDE (which installs the SDK & the JDK)
2. You install the Microsoft Emulator (if you're on an old AMD CPU)
3. You configure the MS Emulator in the Android Studio IDE
(I configured it for Android 7.0, API 24, x86 Samsung Galaxy S5)
4. You start the MS Emulator from within the IDE & run the Hello World app!
Voila!

You have to know _exactly_ the syntax for a few of those steps above,
but once you have the experience of 20:20 hindsight, it's trivial!

With experience of 20:20 hindsight, even on old AMD CPUs, it's that easy!

On Tue, 6 Nov 2018 09:27:14 -0000 (UTC), Arlen_Holder wrote:

With experience of 20:20 hindsight, even on old AMD CPUs, it's that easy!

Now that I finally was able to get the Microsoft Emulator working with
Android Studio 3.2.1 on an old AMD-based Windows 10 desktop, I was able to
easily run the official Google Android Studio "Your first app" tutorial to
completion:
https://developer.android.com/training/basics/firstapp/

o The app running in a Nexus 7 emulation displays a screen for text input:
http://www.bild.me/bild.php?file=5614359androidstudio42.jpg
o You enter any desired text and hit the "Send" button:
http://www.bild.me/bild.php?file=1062599androidstudio43.jpg
o That sends the text to the next level (where all the back buttons work):
http://www.bild.me/bild.php?file=6870342androidstudio44.jpg

That seems to be the ONLY step-by-step tutorial on those web page (but
maybe I need to root around more?).

Given I'm an average noob (if even that), I wish I could speak with the
writer where what I would tell her would IMPROVE the tutorial for noobs
without adding any complexity.

I suspect it would take her a half hour on the phone to hear me out, and
then another few hours to make her edits, and those improvements alone
would be exponentially better.

Anyway, the first Android Studio tutorial is successfully completed, such
that the app works for what it was intended to do.

For those of you who have never created an Android app, this method of
handholding works, where the hardest part for me was completely unrelated
to the tutorial itself - but was a hardware/software configuration issue
which only shows up on AMD-based systems.

On Thu, 8 Nov 2018 09:58:05 -0000 (UTC), Arlen_Holder wrote:

Now that I finally was able to get the Microsoft Emulator working with
Android Studio 3.2.1 on an old AMD-based Windows 10 desktop, I was able to
easily run the official Google Android Studio "Your first app" tutorial to
completion:
https://developer.android.com/training/basics/firstapp/

Here is another app I just created using the Windows Android IDE freewa
http://www.bild.me/bild.php?file=8515596androidstudio46.jpg

If anyone on this ng knows of another good tutorial for a noob's first apps
using the Windows Android Studio freeware, please let us know as I've
exhausted the (one?) tutorial on the Android developer training site (they
only have one?).

Moving forward, I ran the tutorial here, which took about a half hour to
run (since I had done it before, a few days ago, but deleted the results
because a few things didn't work - that suddenly work now - most likely due
to a chain of fewer mis steps in button presses or coding as I get more
familiar with the software and jargon...).

Android Studio For Beginners Part 1, by Bill Butterfield,
o Published on Jun 13, 2017 (mp4)
o https://youtu.be/dFlPARW5IX8 (part 1 of 4)
===========
Here's the java code (so that others can use it directly)
===========
package com.kiss.app03;

import android.os.Bundle;
import android.support.v7.app.AppCompatActivity;
import android.view.View;
import android.widget.Button;
import android.widget.EditText;
import android.widget.TextView;

public class MainActivity extends AppCompatActivity {

@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);

Button addBtn = (Button) findViewById(R.id.addBtn);
addBtn.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View v) {
EditText firstNumEditText = (EditText)
findViewById(R.id.firstNumEditText);
EditText secondNumEditText = (EditText)
findViewById(R.id.secondNumEditText);
TextView resultTextView = (TextView)
findViewById(R.id.resultTextView);

int num1 =
Integer.parseInt(firstNumEditText.getText().toStri ng());
int num2 =
Integer.parseInt(secondNumEditText.getText().toStr ing());
int result = num1 + num2;
resultTextView.setText(result + "");
}
});

}
}
===========
Here's the xml layout (so that others can use it directly)
===========
?xml version="1.0" encoding="utf-8"?
android.support.constraint.ConstraintLayout
xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:app="http://schemas.android.com/apk/res-auto"
xmlns:tools="http://schemas.android.com/tools"
android:layout_width="match_parent"
android:layout_height="match_parent"
tools:context=".MainActivity"
tools:layout_editor_absoluteY="81dp"

android.support.constraint.Guideline
android:id="@+id/guideline"
android:layout_width="wrap_content
===========

On Thu, 8 Nov 2018 18:44:54 -0000 (UTC), Arlen_Holder wrote:

Android Studio For Beginners Part 1, by Bill Butterfield,
o Published on Jun 13, 2017 (mp4)
o https://youtu.be/dFlPARW5IX8 (part 1 of 4)

After taking an unscheduled aside to learn how to port an app
(which isn't as easy as it sounds) from "app03" to "app04"
http://www.bild.me/bild.php?file=7456135androidstudio58.jpg

I moved to the second video, part 2, by Bill Butterfield,
of the set "Android Studio For Beginners Part 1,2,3,4":
https://youtu.be/dFlPARW5IX8 (part 1) === app03 is this video
https://youtu.be/6ow3L39Wxmg (part 2) === app05 is this video
https://youtu.be/rdGpT1pIJlw (part 3)
https://youtu.be/bu5Y3uZ6LLM (part 4)

Since I'm not taking any classes, I'm learning stuff by doing, where,
for example, I learned just now by accidentally running the Microsoft
Android Emulator directly, then the emulator actually "remembers" the
previously installed apps as shown here (as opposed to flushing them every
time, which happens when I run the Microsoft Emulation Manager instead):
http://www.bild.me/bild.php?file=4126667androidstudio53.jpg

The goal, by the way, is a custom app, that simply does this:
1. You press an icon named "10"
2. It beeps to let you know it started
3. Ten minutes later, an alarm rings

If this thread gives other noobs a good starting point, then that's good.
If we can get a simple 10-minute timer app out of this, then that's good.

To that end, here's the next Android app ... app05
http://www.bild.me/bild.php?file=8495103androidstudio57.jpg
where
app01 = hello world
app02 = calls an activity within the app
app03 = adder
app04 = copy of that adder
app05 = calls activity inside and outside the app

If anyone wants or needs the working java code, here it is:
================================================== ==========================
C:\tmp\android\app05\app\src\main\java\com\kiss\ap p05\MainActivity.java
================================================== ==========================
package com.kiss.app05;

import android.content.Intent;
import android.net.Uri;
import android.os.Bundle;
import android.support.v7.app.AppCompatActivity;
import android.view.View;
import android.widget.Button;

public class MainActivity extends AppCompatActivity {

@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);

// Attempts to launch an activity within our own app
Button secondActivityBtn = (Button) findViewById(R.id.secondActivityBtn);
secondActivityBtn.setOnClickListener(new View.OnClickListener() {

@Override
public void onClick(View v) {
Intent startIntent = new Intent(getApplicationContext(), SecondActivity.class);
// show how to pass inforation to another activity
startIntent.putExtra("com.kiss.app05.SOMETHING", "HELLO WORLD!");
startActivity(startIntent);
}
});

// Attempt to launch an activity outside our app
Button googleBtn = (Button) findViewById(R.id.googleBtn);
googleBtn.setOnClickListener(new View.OnClickListener() {

@Override
public void onClick(View v) {
String google = "http://www.google.com";
Uri webaddress = Uri.parse(google);

Intent gotoGoogle = new Intent(Intent.ACTION_VIEW, webaddress);
if (gotoGoogle.resolveActivity(getPackageManager()) != null) {
startActivity(gotoGoogle);
}
}
});
}
}
================================================== ==========================
C:\tmp\android\app05\app\src\main\java\com\kiss\ap p05\SecondActivity.java
================================================== ==========================
package com.kiss.app05;

import android.os.Bundle;
import android.support.v7.app.AppCompatActivity;
import android.widget.TextView;

public class SecondActivity extends AppCompatActivity {

@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_second);

if (getIntent().hasExtra("com.kiss.app05.SOMETHING")) {
TextView tv = (TextView) findViewById(R.id.textView);
String text = getIntent().getExtras().getString("com.kiss.app05. SOMETHING");
tv.setText(text);
}
}
}
================================================== ==========================
Here's an example of the code when it runs on my phone (Nougat):
http://www.bild.me/bild.php?file=8495103androidstudio57.jpg
================================================== ========================

On Fri, 2 Nov 2018 22:07:45 -0000 (UTC), Arlen_Holder wrote:

*What is the trick to get Android Studio to _use_ the MS Android Emulator?*

UPDATE

For those of you on AMD Windows computers, this is critically important
(but also confusing as older AMD CPUs _still_ do not appear to be supported).

This article just says AMD CPUs are supported on Win10 as of 7/9/2018:
https://www.xda-developers.com/android-studio-canary-android-emulator-support-amd-windows-10/

This is the title of that article and the subtitle:
"Android Emulator in Android Studio 3.2 now supports AMD processors on Windows 10"
"Update 7/9/18: Google has announced that the latest Android Emulator release now supports Windows 10 PCs with AMD processors and Microsoft Hyper-V"

The article refers to this blog for its information:
Android Emulator - AMD Processor & Hyper-V Support, 09 July 2018
Posted by Jamal Eason, Product Manager, Android
https://android-developers.googleblog.com/2018/07/android-emulator-amd-processor-hyper-v.html

The blog says the latest Google emulator for Windows is he
https://developer.android.com/studio/run/emulator#install
But that it *requires* the following for an AMD processor on Windows:
o Android Studio 3.2 or higher
o Windows 10 April 2018 release or higher
o Windows Hypervisor Platform (WHPX) functionality
o Android SDK Tools 26.1.1 or higher
o 64-bit processor with UG (unrestricted guest)
o Must support HAXM 6.2.1 or later (HAXM 7.2.0 or later recommended)

That makes no sense to me because HAXM isn't going to be supported on _any_ AMD CPU.
https://docs.microsoft.com/en-us/xamarin/android/get-started/installation/android-emulator/hardware-acceleration?tabs=vswin&pivots=windows

Hence, it's why you'll almost always see on the net that,
for AMD on Windows, most people suggest either the Microsoft Android
Emulator or the Genymotion Personal Edition Android Emulator.
o Genymotion https://www.genymotion.com/fun-zone/ (requires login)
o Microsoft https://visualstudio.microsoft.com/vs/msft-android-emulator/

Here are the 40 devices that my Microsoft emulator supports on AMD.

C:\Program Files (x86)\Microsoft Visual Studio Emulator for Android\1.0\Default\Devices\5_KitKat_(4.4)_XXHDPI_ Phone.cfg
o Similar to Samsung Galaxy S5, Sony Xperia Z
- 5" KitKat (4.4) XXHDPI Phone (Android 4.4.4, API 19)

C:\Program Files (x86)\Microsoft Visual Studio Emulator for Android\1.0\Default\Devices\7_KitKat_(4.4)_XHDPI_T ablet.cfg
o Similar to Asus Google Nexus 7
- 7" KitKat (4.4) XHDPI Tablet

C:\Program Files (x86)\Microsoft Emulator Manager\1.0\Skus\Android\configurations.xml
o Similar to Samsung Google Nexus 10
- device.name=10.1" JellyBean (4.2) XHDPI Tablet

o Similar to HTC One X, HTC One XL, LG Nexus 4, Motorola Moto X
- device.name=4.7" JellyBean (4.2) XHDPI Phone

o Similar to Samsung Google Nexus S
- device.name=4" JellyBean (4.2) HDPI Phone

o Similar to Samsung Galaxy S4
- device.name=5" JellyBean (4.2) XXHDPI Phone

o Similar to LG Optimus L70
- device.name=4.5" KitKat (4.4) HDPI Phone

o Similar to Motorola Moto X
- device.name=4.7" KitKat (4.4) XHDPI Phone

o Similar to Samsung Galaxy Note II
- device.name=5.5" KitKat (4.4) HDPI Phone

o Similar to Samsung Galaxy Note 3
- device.name=5.7" KitKat (4.4) XHDPI Phone

o Similar to Samsung Galaxy Note 4
- device.name=5.7" KitKat (4.4) XXHDPI Phone

o Similar to Samsung Galaxy S5, Sony Xperia Z
- device.name=5" KitKat (4.4) XXHDPI Phone

o Similar to Asus Google Nexus 7
- device.name=7" KitKat (4.4) XHDPI Tablet

o Similar to Sony Xperia Tablet Z
- device.name=10.1" KitKat (4.4) HDPI Tablet

o Similar to Samsung Google Nexus 10
- device.name=10.1" KitKat (4.4) XHDPI Tablet

o Similar to Motorola Moto G, Motorola Moto X
- device.name=4.5" Lollipop (5.0) XHDPI Phone

o Similar to LG Nexus 4
- device.name=4.7" Lollipop (5.0) XHDPI Phone

o Similar to HTC One, LG Nexus 5
- device.name=4.7" Lollipop (5.0) XXHDPI Phone

o Similar to Samsung Galaxy Note II
- device.name=5.5" Lollipop (5.0) HDPI Phone

o Similar to Samsung Galaxy Note 3
- device.name=5.7" Lollipop (5.0) XHDPI Phone

o Similar to Samsung Galaxy Note 4
- device.name=5.7" Lollipop (5.0) XXHDPI Phone

o Similar to Samsung Galaxy S4, Samsung Galaxy S5, Sony Xperia Z
- device.name=5" Lollipop (5.0) XXHDPI Phone

o Similar to Asus Google Nexus 7
- device.name=7" Lollipop (5.0) XHDPI Tablet

o Similar to Samsung Google Nexus 10
- device.name=10.1" Lollipop (5.0) XHDPI Tablet

o Similar to Motorola Moto G, Motorola Moto X
- device.name=4.5" Lollipop (5.1.1) XHDPI Phone

o Similar to LG Nexus 4
- device.name=4.7" Lollipop (5.1.1) XHDPI Phone

o Similar to HTC One (M7)
- device.name=4.7" Lollipop (5.1.1) XXHDPI Phone

o Similar to Samsung Galaxy S6, Samsung Galaxy S6 Edge
- device.name=5.1" Lollipop (5.1.1) XXHDPI Phone

o Similar to LG G4
- device.name=5.5" Lollipop (5.1.1) XXHDPI Phone

o Similar to Sony Xperia Z, LG Nexus 5
- device.name=5" Lollipop (5.1.1) XXHDPI Phone

o Similar to Asus Google Nexus 7
- device.name=7" Lollipop (5.1.1) XHDPI Tablet

o Similar to Samsung Google Nexus 10
- device.name=10.1" Lollipop (5.1.1) XHDPI Tablet

o Similar to Samsung Galaxy S5, HTC One M9, HTC One M8, HTC One A9
- device.name=5" Marshmallow (6.0.0) XXHDPI Phone

o Similar to Motorola Moto G, Sony Xperia M4 Aqua
- device.name=5" Marshmallow (6.0.0) XHDPI Phone

o Similar to Samsung Galaxy Note4, Samsung Galaxy Note5, Huawei Nexus 6P, Motorola Moto X Style
- device.name=5.7" Marshmallow (6.0.0) XHDPI Phone

o Similar to Sony Xperia Z5 Premium
- device.name=5.5" Marshmallow (6.0.0) XXXHDPI Phone

o Similar to Motorola Moto X Play
- device.name=5.5" Marshmallow (6.0.0) XXHDPI Phone

o Similar to LG Nexus 5X, Sony Xperia Z3, Sony Xperia Z2, Sony Xperia Z5, Huawei P8
- device.name=5.2" Marshmallow (6.0.0) XXHDPI Phone

o Similar to Samsung Galaxy S6, Samsung Galaxy S6 Edge
- device.name=5.1" Marshmallow (6.0.0) XXHDPI Phone

o Similar to Samsung Google Nexus 10
- device.name=10.1" Marshmallow (6.0.0) XHDPI Tablet

--

On Sat, 10 Nov 2018 10:09:49 -0000 (UTC), Arlen_Holder wrote:

Here's an example of the code when it runs on my phone (Nougat):
http://www.bild.me/bild.php?file=8495103androidstudio57.jpg

Today I ran app06 successfully, after a few classic debugging issues:
o http://www.bild.me/bild.php?file=1682135androidstudio61.jpg

Android Studio For Beginners Part 1,2,3,4 by Bill Butterfield, Jun 13, 2017
o https://youtu.be/dFlPARW5IX8 (part 1) === app03 is this video
o https://youtu.be/6ow3L39Wxmg (part 2) === app05 is this video
o https://youtu.be/rdGpT1pIJlw (part 3) === app06 is this video
o https://youtu.be/bu5Y3uZ6LLM (part 4)

Download these three pictures first (which are shrunk to 640x480):
o garlic.jpg = http://www.bild.me/bild.php?file=1017694garlic.jpg
o tomato.jpg = http://www.bild.me/bild.php?file=2917965tomato.jpg
o banana.jpg = http://www.bild.me/bild.php?file=3954162banana.jpg
Note: He used peach, tomato, squash (I used garlic, tomato, banana).

Here is the code if anyone is interested in following footsteps.
================================================== ==========================
java:
C:\tmp\android\app06\app\src\main\java\com\kiss\ap p06\DetailActivity.java
C:\tmp\android\app06\app\src\main\java\com\kiss\ap p06\ItemAdapter.java
C:\tmp\android\app06\app\src\main\java\com\kiss\ap p06\MainActivity.java

res:
C:\tmp\android\app06\app\src\main\res\layout\activ ity_detail.xml
C:\tmp\android\app06\app\src\main\res\layout\activ ity_main.xml
C:\tmp\android\app06\app\src\main\res\layout\my_li stview_detail.xml

values:
C:\tmp\android\app06\app\src\main\res\values\color s.xml
C:\tmp\android\app06\app\src\main\res\values\strin gs.xml
C:\tmp\android\app06\app\src\main\res\values\style s.xml
================================================== ==========================
C:\tmp\android\app06\app\src\main\java\com\kiss\ap p06\DetailActivity.java
package com.kiss.app06;

import android.content.Intent;
import android.graphics.Bitmap;
import android.graphics.BitmapFactory;
import android.support.v7.app.AppCompatActivity;
import android.os.Bundle;
import android.view.Display;
import android.widget.ImageView;

public class DetailActivity extends AppCompatActivity {

@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_detail);

Intent in = getIntent();
int index = in.getIntExtra("com.kiss.app06.ITEM_INDEX", -1);

if (index -1) {
int pic = getImg(index);
ImageView img = (ImageView) findViewById(R.id.imageView);
scaleImg(img, pic);
}

}

private int getImg(int index) {
switch (index) {
case 0: return R.drawable.garlic;
case 1: return R.drawable.tomato;
case 2: return R.drawable.banana;
default: return -1;
}
}

private void scaleImg(ImageView img, int pic) {
Display screen = getWindowManager().getDefaultDisplay();
BitmapFactory .Options options = new BitmapFactory.Options();

options.inJustDecodeBounds = true;
BitmapFactory.decodeResource(getResources(), pic, options);

int imgWidth = options.outWidth;
int screenWidth = screen.getWidth();

if (imgWidth screenWidth) {
int ratio = Math.round( (float) imgWidth / (float)screenWidth);
options.inSampleSize = ratio;
}

options.inJustDecodeBounds = false;
Bitmap scaledImg = BitmapFactory.decodeResource(getResources(), pic, options);
img.setImageBitmap(scaledImg);
}
}
================================================== ==========================
C:\tmp\android\app06\app\src\main\java\com\kiss\ap p06\ItemAdapter.java
package com.kiss.app06;

import android.content.Context;
import android.view.LayoutInflater;
import android.view.View;
import android.view.ViewGroup;
import android.widget.BaseAdapter;
import android.widget.TextView;

public class ItemAdapter extends BaseAdapter {

LayoutInflater mInflator;
String[] items;
String[] prices;
String[] descriptions;

public ItemAdapter(Context c, String[] i, String[] p, String[] d) {
items = i;
prices = p;
descriptions = d;
mInflator = (LayoutInflater) c.getSystemService(Context.LAYOUT_INFLATER_SERVICE );
}

@Override
public int getCount() {
return items.length;
}

@Override
public Object getItem(int i) {
return items[i];
}

@Override
public long getItemId(int i) {
return i;
}

@Override
public View getView(int i, View view, ViewGroup viewGroup) {

View v = mInflator.inflate(R.layout.my_listview_detail, null);
TextView nameTextView = (TextView) v.findViewById(R.id.nameTextView);
TextView descriptionTextView = (TextView) v.findViewById(R.id.descriptionTextView);
TextView priceTextView = (TextView) v.findViewById(R.id.priceTextView);

String name = items[i];
String desc = descriptions[i];
String cost = prices[i];

nameTextView.setText(name);
descriptionTextView.setText(desc);
priceTextView.setText(cost);

return v;
}
}
================================================== ==========================
C:\tmp\android\app06\app\src\main\java\com\kiss\ap p06\MainActivity.java
package com.kiss.app06;

import android.content.Intent;
import android.content.res.Resources;
import android.os.Bundle;
import android.support.v7.app.AppCompatActivity;
import android.view.View;
import android.widget.AdapterView;
import android.widget.ListView;

public class MainActivity extends AppCompatActivity {

ListView myListView;
String[] items;
String[] prices;
String[] descriptions;

@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);

Resources res = getResources();
myListView = (ListView) findViewById(R.id.myListView);
items = res.getStringArray(R.array.items);
prices = res.getStringArray(R.array.prices);
descriptions = res.getStringArray(R.array.descriptions);

ItemAdapter itemAdapter = new ItemAdapter(this, items, prices, descriptions);
myListView.setAdapter(itemAdapter);

myListView.setOnItemClickListener(new AdapterView.OnItemClickListener() {
@Override
public void onItemClick(AdapterView? parent, View view, int i, long l) {
Intent showDetailActivity = new Intent(getApplicationContext(), DetailActivity.class);
showDetailActivity.putExtra("com.kiss.app06.ITEM_I NDEX", i);
startActivity(showDetailActivity);
}
});


}
}
================================================== ==========================
C:\tmp\android\app06\app\src\main\res\layout\activ ity_detail.xml

?xml version="1.0" encoding="utf-8"?
android.support.constraint.ConstraintLayout xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:app="http://schemas.android.com/apk/res-auto"
xmlns:tools="http://schemas.android.com/tools"
android:layout_width="match_parent"
android:layout_height="match_parent"
tools:context=".DetailActivity"

ImageView
android:id="@+id/imageView"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_marginStart="8dp"
android:layout_marginTop="8dp"
android:layout_marginEnd="8dp"
android:layout_marginBottom="8dp"
app:layout_constraintBottom_toBottomOf="parent"
app:layout_constraintEnd_toEndOf="parent"
app:layout_constraintStart_toStartOf="parent"
app:layout_constraintTop_toTopOf="parent"
app:srcCompat="@mipmap/ic_launcher" /
/android.support.constraint.ConstraintLayout
================================================== ==========================
C:\tmp\android\app06\app\src\main\res\layout\activ ity_main.xml

?xml version="1.0" encoding="utf-8"?
android.support.constraint.ConstraintLayout xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:app="http://schemas.android.com/apk/res-auto"
xmlns:tools="http://schemas.android.com/tools"
android:layout_width="match_parent"
android:layout_height="match_parent"
tools:context=".MainActivity"

ListView
android:id="@+id/myListView"
android:layout_width="match_parent"
android:layout_height="495dp"
app:layout_constraintEnd_toEndOf="parent"
app:layout_constraintStart_toStartOf="parent"
tools:layout_editor_absoluteY="8dp" /
/android.support.constraint.ConstraintLayout
================================================== ==========================
C:\tmp\android\app06\app\src\main\res\layout\my_li stview_detail.xml

?xml version="1.0" encoding="utf-8"?
RelativeLayout xmlns:android="http://schemas.android.com/apk/res/android"
android:layout_width="match_parent" android:layout_height="match_parent"

TextView
android:id="@+id/nameTextView"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_alignParentStart="true"
android:layout_alignParentTop="true"
android:layout_marginStart="48dp"
android:layout_marginTop="45dp"
android:text="Name"
android:textSize="24sp" /

TextView
android:id="@+id/descriptionTextView"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_below="@+id/nameTextView"
android:layout_alignParentStart="true"
android:layout_marginStart="45dp"
android:layout_marginTop="1dp"
android:text="Description" /

TextView
android:id="@+id/priceTextView"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_alignTop="@+id/nameTextView"
android:layout_alignParentEnd="true"
android:layout_marginEnd="27dp"
android:text="Price"
android:textSize="24sp" /
/RelativeLayout
================================================== ==========================
C:\tmp\android\app06\app\src\main\res\values\color s.xml

?xml version="1.0" encoding="utf-8"?
resources
color name="colorPrimary"#008577/color
color name="colorPrimaryDark"#00574B/color
color name="colorAccent"#D81B60/color
/resources
================================================== ==========================
C:\tmp\android\app06\app\src\main\res\values\strin gs.xml
resources
string name="app_name"app06/string

string-array name="items"
itemgarlic/item
itemtomato/item
itembanana/item
/string-array

string-array name="prices"
item$0.99/item
item$1.49/item
item$0.89/item
/string-array

string-array name="descriptions"
itemFresh garlic/item
itemFresh tomato/item
itemFresh banana/item
/string-array
/resources

================================================== ==========================
C:\tmp\android\app06\app\src\main\res\values\style s.xml

resources

!-- Base application theme. --
style name="AppTheme" parent="Theme.AppCompat.Light.DarkActionBar"
!-- Customize your theme here. --
item name="colorPrimary"@color/colorPrimary/item
item name="colorPrimaryDark"@color/colorPrimaryDark/item
item name="colorAccent"@color/colorAccent/item
/style

/resources
================================================== ==========================

On Sat, 10 Nov 2018 22:48:27 -0000 (UTC), Arlen_Holder wrote:

For those of you on AMD Windows computers, this is critically important
(but also confusing as older AMD CPUs _still_ do not appear to be supported).

Below is hard-won information for those of us on older Windows AMD CPUs.
================================================== ==========================
o AndroidStudio321 x86 emulators don't work with old Windows AMD CPUs.
o You can use the ARM EABI v7a System Image (but it's super slow).
o Most people suggest Genymotion: https://www.genymotion.com/desktop/
But you have to create an account to get the freeware (so I didn't).
o Or Microsoft https://visualstudio.microsoft.com/vs/msft-android-emulator/
o Or Andyroid: https://www.andyroid.net/
https://andydownload.azureedge.net/downloads/installer/v47/Andy_47.260_1096_26_x64.exe
o Or Blue Stacks: https://www.bluestacks.com/
https://www.bluestacks.com/download.html?utm_campaign=homepage-dl-button-en
https://cdn3.bluestacks.com/download... 964b9b92e.exe

REFERENCES:
https://stackoverflow.com/questions/31815847/external-emulator-for-android-studio
https://www.android-examples.com/manually-install-external-apk-files-android-emulator-android-studioeclipse/
https://developer.android.com/studio/run/emulator
https://developer.android.com/studio/run/managing-avds
https://blogs.msdn.microsoft.com/devops/2015/07/20/using-the-visual-studio-emulator-for-android-from-android-studio-or-eclipse-with-adt/
================================================== ==========================
You have to run this command to get the necessary info for the AVD setup!

C:\Program Files (x86)\Microsoft Emulator Manager\1.0\emulatorcmd.exe
Which is put in your path already by the installation program.

o C:\emulatorcmd.exe /sku:Android list /type:device
Identifier | Name | Version
-------------------------------------+------------------------------+------------
226C76AC-9E9A-4EBD-A495-79E8C5C5292F | 7" KitKat (4.4) XHDPI Tablet | 1.0.60404.1
363F7AED-462C-46BD-9FEC-F1DD3B79916C | 5" KitKat (4.4) XXHDPI Phone | 1.0.60404.1

That output enables construction of the following commands in Android Studio.
These commands show up later in "AndroidStudio321:Tools External Tools".
AndroidStudio321:File Settings External Tools (+)
Note they show up in the order created, first on top, last on bottom.

Name: MS 7" KitKat (4.4) XHDPI Tablet (SDK version 19)
Description: (I don't know where this matters, if at all)
Description: Emulates the Asus Google Nexus 7 tablet
Program: C:\Program Files (x86)\Microsoft Emulator Manager\1.0\emulatorcmd.exe
Arguments: /sku:Android launch /id:226C76AC-9E9A-4EBD-A495-79E8C5C5292F
Working directory: $ProjectFileDir$

Name: MS 5" KitKat (4.4) XXHDPI Phone (SDK version 19)
Description: (I don't know where this matters, if at all)
Description: Emulates the Samsung Galaxy S5 & Sony Xperia Z
Program: C:\Program Files (x86)\Microsoft Emulator Manager\1.0\emulatorcmd.exe
Arguments: /sku:Android launch /id:363F7AED-462C-46BD-9FEC-F1DD3B79916C
Working directory: $ProjectFileDir$
================================================== ==========================
You can add Google x86 emulators all you want, but they don't seem to work.
(At least not on the older AMD Windows CPUs (they are said to work on Linux).
================================================== ==========================