Arlen_Holder
news alt.comp.freeware, wrote:

On Sat, 3 Nov 2018 02:00:32 -0000 (UTC), Diesel wrote:

It's not really a trick Arlen. There's a bug of sorts. I haven't
isolated it to a specific package.

Thanks for the help where I spent a few hours on the problem
today. I made no progress, where the current status is the same as
before

It shouldn't have taken you a few hours to do what I suggested,
previously.

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.

Yes, it's a common and known issue. As is the suggested fix I
provided for you, which works most of the time, when properly
followed. I'm not surprised to see that you didn't follow it to the
letter as I previously wrote for you to be doing...

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.

Wow. Really? It's not a key problem though.

o Any solution for Intel CPUs does _not_ apply to AMD CPUs.
o Any solution for AMD CPUs does _not_ apply to Intel CPUs.

Obviously this is not accurate. The possibly working solution (as I
said, this works the majority of the time, pending no serious
corruption issues with the SDK installation) I presented to you
already doesn't care what CPU you're using.

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.

I really don't know where you get this information from...The
solutions you're writing about have to do with tweaking the
emulation/stabilizing it, etc. Not getting it initially up and going
with your application on it. Readers would be well advised to ignore
the 'advice' you've provided on this subject at this point, Arlen...

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.

Nope, it's not. You did not follow the instructions I provided you. I
don't know what you spent hours doing, exactly, but it sure as hell
wasn't doing what I wrote for you to do...

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.

adb being added to the path is more for your convenience than much
else. The actual issue is the newly created, but, incomplete registry
key. It's incomplete because you (a) didn't follow my instructions
and (b) are too arrogant to ask for clarification or further help
with that. You just made assumptions and rolled with them. Which,
clearly, didn't give you the results you were hoping for.

8. The developers of the MS Android Emulator store this hard-coded
path
to the Android SDK in the Windows registry:

It's not a hard coded path if you can change it, Arlen... [g]

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

Did you actually set Android SDK Tools 'string value' to 'C:\app
\hardware\android\sdk'?

So you glanced over this part of my instructions then?

*** begin copy
If the key had to be created , be sure you create the string
variable, Path and input the information above. Close regedit.
Obviously by information above, I specifically mean the location to
where Android SDK installed by default.
*** end copy

Not only did I specifically tell you to reinstall the programs using
their default settings, I also provided very specific instructions
concerning the creation of the key as well as a very specific piece
of it, if it wasn't already present on your machine. You clearly
didn't follow through with all of the instructions. Despite them
being present...



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

add to the path? I didn't tell you to add anything to the path,
Arlen...

MID:

Open regedit, navigate to

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Android SDK Tools

If you don't have this key, create it-- That means, add the key
'Android SDK Tools' under Wow6432Node as you see above.

Under the key if it already exists is a string variable called Path.
edit it to point to the location of your Android SDK Installation.
Example: C:\Program Files (x86)\Android\android-sdk
(If you haven't mucked with the default installs, that example
*should* be what you need to add. Verify for yourself, though.

If the key had to be created , be sure you create the string
variable, Path and input the information above. Close regedit.
Obviously by information above, I specifically mean the location to
where Android SDK installed by default.
*** end snippit

I don't know where you got PATH= out of what I wrote to you...I
specifically wrote 'string variable' which needs to be named, Path
and set to the installation folder for the SDK; which would be
default, had you done what I wrote for you to do, to the letter, as I
told you to do. There was a specific reason I wrote for you to do it
as I wrote it to be done, Arlen.

Are you ****ing playing games with me, Arlen, or do we have a
communications issue of some kind going on here? I suppose it could
be both at this point...

One last time, either follow the instructions as I wrote them to the
****ing letter Arlen, or I leave you to **** in the wind on this one
too.

Go back and re-read my post. Follow the instructions, to the ****ing
letter, every single one of them. Report back your results.

The following url will provide you with most of the post I already
wrote (that you skipped and partially ignored) containing the
instructions that most likely will get the emulator up and going for
you. That is, if you follow them all.

http://al.howardknight.net/msgid.cgi?ID=154132021900

Last chance, Arlen, then I'm done wasting time on your dumb ass.
Unless you can demonstrate in the future that you can read and
understand what you're reading by following the ****ing directions,
i'm going to refer to you as a dumb ass.

It's not a simple matter of a single ****up on your part, this is the
second easily shown one in a matter of days; you clearly don't
understand what you read and make poor decisions based on what you
thought you read, rather than ask for clarification or further
assistance. Those are two classic ear marks of a dumb ass.



--
To prevent yourself from being a victim of cyber
stalking, it's highly recommended you visit he
https://tekrider.net/pages/david-brooks-stalker.php
================================================== =
Nobody expects the Spanish Inquisition!