View Single Post
  #49  
Old November 7th 18, 05:39 PM posted to comp.mobile.android,alt.comp.freeware,microsoft.public.windowsxp.general
Bill[_40_]
external usenet poster
 
Posts: 346
Default Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour)

In message , Arlen_Holder
writes
On Tue, 6 Nov 2018 16:58:26 +0000, Bill wrote:

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?

I haven't really checked any speeds. The emulation seems quite slow to
appear, but, because I've stayed with the text instructions, I haven't
actually got any buttons to press that do anything on the emulator. I am
still stuck where I enter the java message stub under the heading "Start
another activity". I haven't had much time and have spent it mainly
trying to get the instance of the program on the other machine - with
default settings everywhere - working.

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.


Further to that, there is a transient error message that appears, but it
is beneath the visible parts of the emulator, and I haven't managed to
move the emulator to see the message. I have run Sysinternals Process
Monitor, which shows a bunch of entries like this.

" 23:55:27.9635626 emulator64-crash-service.exe 6968 CreateFile
C:\Windows\Prefetch\EMULATOR64-CRASH-SERVICE.EXE-C784D2C2.pf NAME NOT
FOUND Desired Access: Generic Read, Disposition: Open, Options:
Synchronous IO Non-Alert, Attributes: n/a, ShareMode: None,
AllocationSize: n/a "

but I haven't investigated further.


Snip about cpu types

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?


I have a spare Android 6 phone that I've been using. I also have an
Android 4 phone and a couple of Android 4 tablets, but haven't tried any
of these. ( I've kept them all because each has a special feature eg an
A4 tablet receives off air TV)

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.

"Catch up" is not the right phrase!

I will probably concentrate on the machine where the emulator works,
concentrate on getting the java to work, and then look at where to go
from there. I think the timer app is a great basic thing to aim for, and
have at least one idea of my own for a further "one button" app.
--
Bill

---
This email has been checked for viruses by AVG.
https://www.avg.com

Ads