View Single Post
  #48  
Old November 6th 18, 10:43 PM posted to comp.mobile.android,alt.comp.freeware,microsoft.public.windowsxp.general
Arlen_Holder
external usenet poster
 
Posts: 96
Default Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour)

On Tue, 6 Nov 2018 16:58:26 +0000, Bill wrote:

That registry key does not exist on either of the Intel machines here. A
search finds nothing obviously relating to the Android sdk.


Thank you very much, Bill, for that independent confirmation!
As as admitted Android noob, _all_ this is _new_ to me.
So your confirmation of even simple things - helps a LOT!

THANKS!!!!!!!

In 20/20 hindsight, I think this registry edit was a red herring.
I've since _deleted_ it, and everything _still_ works perfectly!
http://www.bild.me/bild.php?file=7301488androidstudio29.jpg

I have the 2 machines the newer tablet laptop X220T on W7 and with
Android Studio using defaults and the older X201 straight laptop
running W10, with non-default directories.


Thanks for that information as our experience can help each other if we
trust what we say (where you can always trust what I say as fact).

Like you, I prefer to put things where I can find them, where I've already
explained in gory detail where I put stuff.

Early this morning, I wiped everything out & started fresh where I decided
to let Android Studio do all the downloading of everything but the
Microsoft Emulator (which you don't need since you're on Intel CPUs).

Here are the main three installation steps.
1. Install the Android Studio IDE (which adds the JDK & Google Emulators)
C:\app\editor\android\ide\android_studio
2. Optionally (if you're on older AMD), install the MS Emulation Manager
C:\Program Files (x86)\Microsoft Emulator Manager
3. Configure that MS Emulation Manager to run inside the Android Studio IDE

Then, to run the apk on either a physical phone or on an emulated phone:
A Start the Android Studio IDE
B Start the MS Emulation Manager
(AndroidStudio:Tools External Tools MS Emulation Manager)
C Pick any desired Android device under test & Android API
(e.g., Galaxy S5 on Android 7.0 using x86)
D Send your app from the Android Studio IDE to your device under test
(AndroidStudio: Run Run 'app')
Voila!
http://www.bild.me/bild.php?file=9175315app02b.gif


On both, the "Appearance and Behaviour" SDK Tools listing is identical
to yours, wxcept that the HAXM is ticked.


Thank you Bill for kindly confirming those checkbox settings inside the
Android Studio IDE.

It helps GREATLY that you confirmed the settings are the same, with the
expected exception of the HAXM checkbox because I'm on AMD while you're on
Intel.

Since you have HAXM, you can use the Google-supplied emulators; but I have
to use the Microsoft x86 emulator - which - in the end - is the same thing
since we're noobs at this stage - so _any_ emulator that works is a good
emulator.

One "choice" I don't understand yet is why we even have the choice of "arm"
or "x86", when we choose an emulator, since both work, but the arm choice
is clearly more than ten times slower than the x86, and since the X86 is
the default.
arm slow http://www.bild.me/bild.php?file=2999468androidstudio24.jpg

The X201 seems to be working well and the emulator is fine. There is a
warning about the display drivers, but I have a good display.


I too get a bunch of warnings, but everything is working so I'm not even
looking at those warnings.

I'm curious, Bill ... does your emulation work about the same speed as your
physical phone?

I haven't timed it yet, but, while the ARM emulation is dog slow...
http://www.bild.me/bild.php?file=4100603androidstudio07.jpg

The x86 emulation seems 'about the same' so far for me, but I haven't timed
it - but it's not egregious either way.
http://www.bild.me/bild.php?file=2999468androidstudio24.jpg

How is the emulation versus the real thing for you on speed?

The X220T came to me with a WWAN module installed and, presumably
working. To fit the mSATA boot SSD, this had to be removed to free the
slot.
As soon as I started trying to get the emulator to work, there were
error messages relating to the WWAN. I assume the emulator was trying to
connect to the phone components of the laptop. I have now removed all
the WWAN related software on the machine, but the emulator still doesn't
fully appear. I get the surround, but with a transparent screen.


That's interesting.

I haven't actually "played" with the emulated phone yet.
It would be interesting to see "what" it does, in terms of functionality,
e.g., it would be _great_ if it can make actual phone calls (but I suspect
it can't).

Like you ... right now ... I'm just dealing with getting the basics going,
where the difference between you and me is that I had some hell to learn
about getting emulation working on older AMD-based Windows where you
skipped that hell because you're on an Intel-based Windows. (Lucky you!)

In a posteriori 20/20 hindsight, I'd suggest that noobs _start_ on
Intel-based CPUs (if they can), or, if they can't, to start on _newer_
AMD-based CPUs.

Or, if they're on older AMD-based CPUs, to just run apps on a spare phone!
That why they'd skip the emulator hell I went through.

BTW, Bill ... I don't remember if you said whether you're using a spare
phone or if you're running on your main phone?

I don't have a spare phone with a good screen (I crushed them all,
literally), so I only have two choices:
o Load all those apps onto my main phone, or,
o Run everything in emulation

Do you run on a spare phone or your main phone?

There hasn't been time to do much more. I'm still on the text based app.


Now that I've gotten past the AMD-specific horrors, I can try to at least
"catch up" to you.

I'll post back when I have something to report of interest to all.
http://www.bild.me/bild.php?file=2596267androidstudio06.jpg
Ads