Arlen_Holder <
a%rle%20nh....@no.spam.net>
news:prihg6$fq7$
1...@news.mixmin.net Fri, 02 Nov 2018 22:01:43 GMT in
alt.comp.freeware, wrote:
> Hi Diesel,
> What is the trick to get Android Studio to _use_ the MS Android
> Emulator?
It's not really a trick Arlen. There's a bug of sorts. I haven't
isolated it to a specific package. IE: I can't say for sure it's
Android SDK or the MS Android emulator that's causing it. A registry
key is sometimes not created or, it is created with the wrong
setting. Either of which causes the issue you're having although it's
not the only way it can happen.
I already know you aren't using default install paths, so this too
can become a problem; especially with programming packages that
support 3rd party plugins and/or other tools/packages as well. Some
may be semi hard coded to look in specific places for support files,
be it configuration data, drivers, required support libraries, etc.
If one or more can't find their 'shit' essentially, it doesn't work
as you'd expect.
I think your first order of business should be to completely
uninstall ALL of the packages you've downloaded to program on Android
with and reinstall them, one by one, using default settings (except
for the ones that deal specifically with your CPU; you already know
HAXM can't be toggled on in your case so make sure it's off). The
default settings includes their installation paths, Arlen. Don't
change any of it.
Once you've done all of that, start the MS Android Emulator and bring
the Android SDK online. See if it can see the emulator and send your
program to it, then. If it doesn't do so, follow the rest of the
instructions I left for you below. And, report back your results so
that others may benefit if this resolves the issue and/or learn more
ways in which to troubleshoot and fix it, if it does not.
> Thanks for your helpful advice, Diesel
Hmm. Haven't you been reading my previous replies, Arlen? I didn't
ask for a thank you. I've asked you for an apology for your unfounded
personal attacks. I *shouldn't* have to do that. You should be mature
enough to 0wn your screwup and take the necessary action to correct
it, entirely on your own without any prodding from me.
[snip amd/intel differences]
> ========= I'm not sure how to get Android Studio to output _to_
> that emulator though! I've hit a hundred buttons in Android
> Studio, but Android Studio still won't download the app to the
> Android emulator yet.
> *What's the trick to get Android Studio to _use_ the MS Android
> Emulator?*
I don't owe you anything, but, just to prove a small point.. I'll do
this for you...
> o Weâ–”e made the Visual Studio Emulator for Android available
> without needing to also download Visual Studio.
> o By default, Android Studio will want to debug to the slow
> Android SDK emulator. o You can configure Android Studio to allow
> you to select a target
> a. In Android Studio,
> b. Run > Edit Configurations > Defaults / Android Application
> c. Set Target Device to Show chooser dialog
> d. Check Use same device for future launches
> ... then nothing makes sense because the doc doesn't match the
> reality ...
You seem to have the worst times with hand holding GUI based
interfaces, Arlen.
Anyways.. Make sure you have the MS emulator up and running.
Goto Tools>Android>Enable ADB integration if you haven't already done
so. If you have already done so, try disabling and re-enabling; this
sometimes clears it up for you. If that doesn't work, proceed with
the following (and report, always report, back your results;
troubleshooting is a two way street you understand)
First (You can skip this part of my advice if you so desire, It's a
general thing I highly suggest people do before playing in the
registry) obtain a copy of erunt. Install and execute ERUNT as
administrator; follow the prompts, let it do it's backup. Remember
where it stores it, in the event you do something really bad in the
next few minutes by not following my directions to the letter.
Now, with that done (you really should have done it) let's proceed.
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.
Close your emulators and the SDK.
Open a console window, type the following:
adb kill-server
adb start-server
Now, relaunch your emulator and fire up the SDK.
As a precautionary measure, you may wish to go ahead and restart your
machine before firing the emulator and SDK back up.
> You're going to *need* those paths though, since Android Studio
> can't find that emulator unless and until you tell Android Studio
> where to find it!
Ayep. Changing default installation folders because they don't make
sense to you isn't always helpful either. Sadly, some programs still
use what's known as 'hard coded' paths/filenames. You should keep
that in mind as you're opting for custom installations based on your
own folder configuration.
> o Android Studio went into C:\app\editor\android\studio\.
And that's where you went wrong. :) That's not the default install
location. So you need to let it know this, by following the
instructions above, carefully. You're going to be editing the
registry Arlen; back it up before you do so.
Yes, I could easily have written you a simple registry import key and
posted it here that would do it for you, but, it's time you learn to
do somethings yourself. I've provided what you should need to get up
and running. report back your results, please.
> ========= This isn't related to the AVD setup:
> o Configure > SDK Manager > Appearance & Behavior > System
> Settings >
> Android SDK > Android SDK Location: C:\app\hardware\android\sdk
> (I need to move that, later, to the C:\app\editor\android\sdk
> location.)
> o Configure > Project Defaults > Project Structure >
> Android SDK location:C:\app\hardware\android\sdk
> JDK location: C:\app\editor\android\studio\jre [x]Use embedded
> JDK (recommended) Android NDK location: (empty) More info here:
> <
https://developer.android.com/ndk/>
Arlen,
I mean this in the most sincere kindest way I can possibly express
it, given the circumstances. Please, STOP changing the default
installation folders (especially on programming packages and support
files) because you have your own folder style layout.
You're going to have all kinds of little issues like the one you've
already run into because of what you did there. :( The Android sdk is
still under development. It's experimental and should be treated as
such. That means, DON'T CHANGE default install folders; some aspects
of it (and support libraries/plugins,etc) aren't going to properly
work if you don't leave those settings alone. There's a reason it
wants to be in specific folders. The fact it doesn't make sense to
you doesn't matter.
> ===================================================================
> ========= Even after pressing "Run" a few times and setting up
> "emulation" devices, it still didn't work, so I don't remember all
> the buttons I pressed by now.
I'm sure you've butchered it quite nicely, Arlen. I'd actually advise
you to completely uninstall it and all associated programs. Reboot
your machine, reinstall them, keeping default installation folders
and settings as they are; aside from the ones you learned your
machine doesn't support. Don't be playing around with installation
paths like this. You're only going to cause yourself unnecessary
headache and aggravation. Stop assuming you know more than the
developers of the software and supported OSes. It may not make sense
to you, but, it makes sense to them and many others who are in
various I.T related fields.
In other words, Stop trying to sort the folders and files in your own
unique style. You cannot do that with alot of software unless you
really know what you're doing and understand how to configure various
other aspects of that software package that may not be aware it's no
longer in default install paths and must (if possible) be told where
to find it's necessary files. Your luck is going to vary on that,
from program to program.
> But that failed miserably ... (same emulation error as always).
> Sigh.
You've (without realizing it of course) provided me alot of useful
information for the purposes of troubleshooting various
problems/queries you've created threads about, going back a
considerable amount of time. Despite not having laid eyes upon the
machine sitting in front of you, I don't feel it's too far a stretch
to get the impression that many of your issues are the result (direct
result) of your own efforts to tinker.
The issues you have are what I enjoy (and am paid well for) doing as
a tech for the most part. Any tech/non tech (some atleast) can build
a computer from parts, toss windows/linux on it and call it a day.
Troubleshooting, data recovery, etc, on the other hand, seperates the
wannabes (regardless of certs/college hours) from the real, hands on,
actually knows this stuff, techs (who may/may not have any/as many
certs or any/as many college hours) as the wannabes who look nicer on
paper, like a brightly shining polished turd. (Yea, I had to
interview one today for a position I'll open soon) - Needless to say,
the college instructor who suggested this particular asshat to me is
going to be hearing from me about how things went. It's actually more
difficult to find competent help in my own field than I originally
thought. :(
Basically, if you have to resort to wipe and reload to 'fix' most
issues, you're a lousy technician. I actually know several certified
techs that opt for doing that; but it's a time savings thing vs
inability to fix the issue at hand. As for me, I have the forethought
to know what a pain in the arse a reinstall from scratch can be,
especially for Windows so, if I can save the machine and stabilize it
without it looking like a patched up wall that's been blasted to hell
and back with a double barrel, that's the route i'm taking. Unless
it's just not realistically feasable to accomplish within a normal
amount of time. Then, I have to make the call to the client to see
what they want to do; how important is it to them to keep the machine
as it is (with the problem fixed of course) vs reloading.
Do they have installation media for all of their software? Is there
email stored locally on the machine or do they obtain it online via
web browser? Do they have all of the installation/product keys for
software they've acquired since initially getting the computer? If
you get a no to one or more of those questions and it's something
they care about, wipe and reload just became a last resort; mainly an
issue of cash at this point. How much are they willing to spend, and
how good are you. Can you get it done within a reasonable amount of
time, at all, or what. That's what I live for, Arlen. You don't want
to have to bill them 300 or more (I bill by the hour, like most
shops) for a computer that's not worth 150 or so. So you need to know
the trade well and need to know those telltale signs of what's wrong
with the box, so you can get it taken care of in a reasonable amount
of time.
The client isn't paying you to learn how to do this shit, that's what
you should already know. And, if you do have to do some research to
fix the problem (we all have, many times); you shouldn't be counting
that (or much of it anyway) as bench time (billable time), but,
that's just my own opinion and how I run my business myself. That
may/may not work for others. I'm not a greedy bastard and my overhead
is insanely low, so I can afford to do it this way and not starve.
Yes, I know, you think I'm crazy by writing that, right? Well, After
doing alot of local linux distro installs the past few years, I've
actually found the majority to be easier (yes, easier) to install
than DVD boot and load of Windows 10. Linux Mint (the older 17.3
flavor; i'm biased towards the later versions) and MXLinux are just
two excellent, imho, examples of distros that are very easy to
install and use right away for many users, power users, and techs
alike. I've even gone so far as to perform some semi controlled
social experiments by switching some local guinea pigs machines from
windows to one of those two aforementioned linux distros and taking a
seat back to observe.
Most of the people weren't even aware it wasn't windows, it just
looked a little different to them. I noticed the malware issues they
previously reported on went from so many per month stats to zero; as
in, none, whatsoever. And this from two who were well known for
clicking anything and everything to get access to that 'free porn'
was especially uplifting to me.
I've also converted two small businesses in this area from Windows
based small network to entirely Linux powered. From the workstations
to their file server, it's all linux now. The software they use in
house works just fine under Wine. They have access to their
documents, notes, spreadsheets, etc via libre office. They have full
access to their laser printers, even via their Android powered cells
and tablets. Even the few iOS devices present in one particular
office has access to the printers (after some research was put into
it; as I told you before, I'm not a mac person). The file server
automatically backs up any documents stored on it to several
different locations, two of which are off site via a simple automated
bash script that runs every so many hours. It even has user specific
access restrictions. [g]
I can't convert all of my clients, Linux isn't for all situations,
but..it's for many others. I know you like Windows 10 based on
reading your other threads, but, I don't and many others I know
prefer not to have it, if possible. So, I always have to have
options; it's one of the reasons people pay me. I fix whats broken.
I told you, and I wasn't bullshitting you then or now Arlen, I am a
certified technician with over two decades experience doing it
professionally for a living. I'm not some fresh out of college asshat
with a degree and no actual experience outside the classroom.
Computers have been a passion of mine since I was a kid in the single
digit age. My interest and appreciation of them has never waivered in
the entire time i've been alive, Arlen. Nor has my undying thirst to
learn more about them.
I'm not bragging when I tell you this, it's just how things are; you
aren't going to find many people like me with the knowledge I have
due to the countless hours I've lost sitting or standing in front of
one of these machines when I should have been doing something else
with the time.
I didn't spend all that time playing video games or otherwise fucking
around with them. I spent it learning, how to code, how the hardware
worked, how the software interacted with it. It increased my love for
electronics which got me into the computers in the first place. I was
the kid who took the radio and tv apart when he was five years old to
fix it, not the kid who didn't do much of anything besides watch
cartoons on it.
I'd appreciate it if in the future you wish to interact with me, you
treat me with a bit more respect than you have previously. That is,
if you want useful technical information and civil interaction with
me in the future. Prior to reading this civil post of yours, I was
about to resume filtering since I don't have time to play silly games
back and forth with you and I have no interest in any of the
political nonsense burp and fart seems intent on flooding
alt.comp.freeware with. I have no use for remailing cowards, and,
unfortunately for you, that's what you're using to post here; so the
filtering would catch you as well, even though you wouldn't be
specifically targetted.
If you just want to continue being an asshole towards me, these
series of posts will be the last ones from me to you for the
aforementioned reasons.
> Diesel, Do you know the trick to get Android Studio to _use_ that
> MS Android Emulator?
Read above. Specifically lines 55 thru 96 *should* if correctly
followed and your installations aren't just fux0red due to your non
default install paths get the studio to use the MS emulator. Again,
report back your results.
The Archbishop of Canterbury and The Royal Commission for Political
Correctness announced today that the climate in the UK should no
longer be referred to as "English Weather".
Rather than offend a sizeable portion of the UK population, it will
now be referred to as "Muslim Weather" - (Partly Sunni, but mostly
Shi'ite).