Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.mobile.android > #56860 > unrolled thread
| Started by | Arlen Holder <a%rlenh.older@no.spam.net> |
|---|---|
| First post | 2018-10-26 22:45 +0000 |
| Last post | 2018-11-14 01:52 +0000 |
| Articles | 20 on this page of 128 — 11 participants |
Back to article view | Back to comp.mobile.android
Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen Holder <a%rlenh.older@no.spam.net> - 2018-10-26 22:45 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Diesel <me@privacy.net> - 2018-10-27 05:39 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen Holder <a%rlenh.older@no.spam.net> - 2018-10-27 08:38 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Diesel <me@privacy.net> - 2018-10-31 05:51 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) "BurfordTJustice" <burford/associate@uk.MI15> - 2018-10-31 07:12 -0400
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Diesel <me@privacy.net> - 2018-11-01 23:44 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Bill <Billaboard@gmail.com> - 2018-10-30 00:14 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen Holder <a%rlenh.older@no.spam.net> - 2018-10-30 19:51 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen Holder <a%rlenh.older@no.spam.net> - 2018-10-30 20:13 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Diesel <me@privacy.net> - 2018-10-31 05:51 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen Holder <a%rlenh.older@no.spam.net> - 2018-10-31 07:26 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Bill <billaboard@gmail.com> - 2018-11-01 12:21 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen_Holder <a%rle%20nh.older@no.spam.net> - 2018-11-02 03:04 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Diesel <me@privacy.net> - 2018-11-01 23:44 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen_Holder <a%rle%20nh.older@no.spam.net> - 2018-11-02 06:29 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Diesel <me@privacy.net> - 2018-11-02 08:03 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen_Holder <a%rle%20nh.older@no.spam.net> - 2018-11-02 22:01 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Diesel <me@privacy.net> - 2018-11-03 02:00 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen_Holder <a%rle%20nh.older@no.spam.net> - 2018-11-04 06:56 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen_Holder <a%rle%20nh.older@no.spam.net> - 2018-11-04 07:50 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Diesel <me@privacy.net> - 2018-11-04 08:46 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen_Holder <a%rle%20nh.older@no.spam.net> - 2018-11-05 17:04 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen_Holder <a%rle%20nh.older@no.spam.net> - 2018-11-05 18:32 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen_Holder <a%rle%20nh.older@no.spam.net> - 2018-11-05 20:47 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen_Holder <a%rle%20nh.older@no.spam.net> - 2018-11-05 23:43 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Diesel <me@privacy.net> - 2018-11-04 08:46 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen_Holder <a%rle%20nh.older@no.spam.net> - 2018-11-06 03:20 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Bill <billaboard@gmail.com> - 2018-11-06 16:58 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen_Holder <a%rle%20nh.older@no.spam.net> - 2018-11-06 21:43 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Bill <Billaboard@gmail.com> - 2018-11-07 16:39 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen_Holder <a%rle%20nh.older@no.spam.net> - 2018-11-08 10:24 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Bill <Billaboard@gmail.com> - 2018-11-08 17:45 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen_Holder <a%rle%20nh.older@no.spam.net> - 2018-11-08 19:27 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Bill <Billaboard@gmail.com> - 2018-11-08 20:43 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen_Holder <a%rle%20nh.older@no.spam.net> - 2018-11-09 11:40 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen_Holder <a%rle%20nh.older@no.spam.net> - 2018-11-10 10:34 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Bill <Billaboard@gmail.com> - 2018-11-12 10:20 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Bill <billaboard@gmail.com> - 2018-11-12 12:37 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen_Holder <a%rle%20nh.older@no.spam.net> - 2018-11-12 20:27 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Bill <Billaboard@gmail.com> - 2018-11-12 23:55 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Bill <Billaboard@gmail.com> - 2018-11-14 17:55 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) arlen michael holder <arlen_michael_holder@example.com> - 2018-11-15 05:56 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) arlen michael holder <arlen_michael_holder@example.com> - 2018-11-15 07:02 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Bill <Billaboard@gmail.com> - 2018-11-16 00:19 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) arlen michael holder <arlen_michael_holder@example.com> - 2018-11-16 19:29 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Bill <Billaboard@gmail.com> - 2018-11-17 15:37 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) arlen michael holder <arlen_michael_holder@example.com> - 2018-11-17 19:49 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Bill <Billaboard@gmail.com> - 2018-11-18 20:14 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) arlen michael holder <arlen_michael_holder@example.com> - 2018-11-19 03:36 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Bill <Billaboard@gmail.com> - 2018-11-19 09:43 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) arlen michael holder <arlen_michael_holder@example.com> - 2018-11-19 20:43 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) arlen michael holder <arlen_michael_holder@example.com> - 2018-11-20 05:50 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Bill <billaboard@gmail.com> - 2018-11-21 10:27 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) arlen michael holder <arlen_michael_holder@example.com> - 2018-11-21 17:40 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) arlen michael holder <arlen_michael_holder@example.com> - 2018-11-21 17:42 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Bill <Billaboard@gmail.com> - 2018-11-21 20:13 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) arlen michael holder <arlen_michael_holder@example.com> - 2018-11-22 07:15 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) arlen michael holder <arlen_michael_holder@example.com> - 2018-11-22 07:49 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Bill <billaboard@gmail.com> - 2018-11-23 20:47 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Bill <Billaboard@gmail.com> - 2018-11-29 10:05 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) arlen holder <arlen@holder.com> - 2018-11-30 19:48 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) arlen holder <arlen@holder.com> - 2018-11-30 21:38 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) arlen holder <arlen@holder.com> - 2018-11-30 21:58 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) arlen holder <arlen@holder.com> - 2018-11-30 21:59 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) arlen holder <arlen@holder.com> - 2018-11-30 22:00 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) arlen holder <arlen@holder.com> - 2018-11-30 22:01 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) arlen holder <arlen@holder.com> - 2018-11-30 22:02 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) arlen holder <arlen@arlen.com> - 2018-12-01 03:09 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) arlen holder <arlen@arlen.com> - 2018-12-01 07:40 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) arlen holder <arlen@arlen.com> - 2018-12-02 03:22 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) arlen holder <arlen@holder.com> - 2018-11-30 19:22 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Bill <Billaboard@gmail.com> - 2018-12-01 16:43 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) arlen holder <arlen@holder.com> - 2018-12-01 19:25 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Bill <Billaboard@gmail.com> - 2018-12-03 18:20 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Bill <Billaboard@gmail.com> - 2018-12-07 16:24 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) arlen michael holder <arlen_michael_holder@example.com> - 2018-11-15 01:24 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) arlen michael holder <arlen_michael_holder@example.com> - 2018-11-15 22:36 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Bill <Billaboard@gmail.com> - 2018-11-10 10:43 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen_Holder <a%rle%20nh.older@no.spam.net> - 2018-11-10 11:36 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen_Holder <a%rle%20nh.older@no.spam.net> - 2018-11-10 11:50 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen_Holder <a%rle%20nh.older@no.spam.net> - 2018-11-12 06:04 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) arlen michael holder <arlen_michael_holder@example.com> - 2018-11-15 22:43 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) arlen michael holder <arlen_michael_holder@example.com> - 2018-11-16 05:08 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Bill <Billaboard@gmail.com> - 2018-11-16 15:33 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) arlen michael holder <arlen_michael_holder@example.com> - 2018-11-16 18:52 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) arlen michael holder <arlen_michael_holder@example.com> - 2018-11-16 20:08 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Bill <Billaboard@gmail.com> - 2018-11-17 00:04 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) arlen michael holder <arlen_michael_holder@example.com> - 2018-11-17 02:38 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) arlen michael holder <arlen_michael_holder@example.com> - 2018-11-17 05:25 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Bill <Billaboard@gmail.com> - 2018-11-21 17:04 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) arlen michael holder <arlen_michael_holder@example.com> - 2018-11-22 07:11 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Bill <Billaboard@gmail.com> - 2018-11-24 23:48 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) arlen michael holder <arlen_michael_holder@example.com> - 2018-11-16 05:08 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Diesel <me@privacy.net> - 2018-10-31 05:51 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) "BurfordTJustice" <burford/associate@uk.MI15> - 2018-10-31 07:11 -0400
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Bill <Billaboard@gmail.com> - 2018-10-31 10:54 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen_Holder <a%rle%20nh.older@no.spam.net> - 2018-11-02 03:33 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Bill <billaboard@gmail.com> - 2018-11-02 19:51 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Bill <Billaboard@gmail.com> - 2018-11-02 20:07 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen_Holder <a%rle%20nh.older@no.spam.net> - 2018-11-02 23:16 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Bill <Billaboard@gmail.com> - 2018-11-03 00:03 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen_Holder <a%rle%20nh.older@no.spam.net> - 2018-11-03 01:44 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Diesel <me@privacy.net> - 2018-11-03 02:00 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Bill <Billaboard@gmail.com> - 2018-11-03 11:56 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) "Apd" <not@all.invalid> - 2018-11-03 15:31 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Bill <Billaboard@gmail.com> - 2018-11-03 18:45 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Diesel <me@privacy.net> - 2018-11-04 08:46 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen_Holder <a%rle%20nh.older@no.spam.net> - 2018-11-06 01:27 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Diesel <me@privacy.net> - 2018-11-06 15:33 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen_Holder <a%rle%20nh.older@no.spam.net> - 2018-11-06 02:56 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen_Holder <a%rle%20nh.older@no.spam.net> - 2018-11-06 03:20 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen_Holder <a%rle%20nh.older@no.spam.net> - 2018-11-06 00:57 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Diesel <me@privacy.net> - 2018-11-06 15:33 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen_Holder <a%rle%20nh.older@no.spam.net> - 2018-11-06 19:06 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Diesel <me@privacy.net> - 2018-11-02 08:03 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen_Holder <a%rle%20nh.older@no.spam.net> - 2018-11-06 09:26 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen_Holder <a%rle%20nh.older@no.spam.net> - 2018-11-08 09:59 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Diesel <me@privacy.net> - 2018-11-10 03:24 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen_Holder <a%rle%20nh.older@no.spam.net> - 2018-11-10 05:04 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Diesel <me@privacy.net> - 2018-11-10 07:04 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen_Holder <a%rle%20nh.older@no.spam.net> - 2018-11-10 09:57 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Diesel <me@privacy.net> - 2018-11-12 07:08 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen_Holder <a%rle%20nh.older@no.spam.net> - 2018-11-12 21:19 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Diesel <me@privacy.net> - 2018-11-12 23:58 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen_Holder <a%rle%20nh.older@no.spam.net> - 2018-11-15 01:55 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) nospam <nospam@nospam.invalid> - 2018-11-12 20:25 -0500
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Diesel <me@privacy.net> - 2018-11-13 13:05 +0000
Re: Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) Arlen_Holder <a%rle%20nh.older@no.spam.net> - 2018-11-14 01:52 +0000
Page 1 of 7 [1] 2 3 4 5 6 7 Next page →
| From | Arlen Holder <a%rlenh.older@no.spam.net> |
|---|---|
| Date | 2018-10-26 22:45 +0000 |
| Subject | Report: My first "hello world" using Android Studio freeware on Windows worked just fine (in about an hour) |
| Message-ID | <pr05f2$t0d$1@news.mixmin.net> |
Report: My first "hello world" using Android Studio freeware on Windows
worked just fine (total elapsed time was about an hour).
<http://www.bild.me/bild.php?file=7570013helloworld01.jpg>
<http://www.bild.me/bild.php?file=4072224helloworld02.jpg>
<http://www.bild.me/bild.php?file=7646977helloworld03.jpg>
<http://www.bild.me/bild.php?file=3369563helloworld04.jpg>
The main issues to deal with are:
o OEM USB Drivers for your phone (I had driver issues but surmounted them)
o Phone set to USB Debugging Mode (already a basic setup for most users)
o Android Studio (freeware, easily installed & seemingly powerful)
o Android SDK (Android Studio handles this well)
o Java (Android Studio handles this well, at least for Hello World)
Getting a "hello world" to work on an Android phone may sound like an
accomplishment, but it's not really that much since all you do is punch
buttons, given that the Google Android Studio freeware literally writes the
entire app for you.
<https://developer.android.com/studio/>
What takes the hour elapsed time is that Android Studio downloads a
separate SDK, and a few other things, plus there was, in my case, a minor
hardware emulation issue on my old desktop, and a USB debugging issue
(perhaps because I've been playing a lot with my USB MTP drivers lately).
<https://groups.google.com/forum/#!topic/comp.mobile.android/SHR2YmpfVwo>
The installation of Android Studio takes about an hour to download stuff:
<https://developer.android.com/studio/install>
You want to plan ahead to decide where you want to put things though:
o Studio: c:\app\hardware\android\studio\
o SDK: c:\app\hardware\android\sdk\
o Projects: c:\tmp\android\projects\myfirstapp\
o c:\users\<you>\.android\ (I'm not sure why stuff was put here)
o c:\users\<you>\.AndroidStudio3.2\ (I'm not sure why stuff is here)
etc.
My main noob mistake was to keep this default, which I should have removed:
[x]Performance Intel HAXM
Hardware-assisted virtual engine to speed up Android app emulation
Another noob mistake I made was that I had to re-install the original
OEM (LG Stylo 3 Plus) USB drivers before Android Studio could see it:
<https://developer.android.com/studio/run/oem-usb#Drivers>
Even though Windows had no problem seeing the phone over USB, Android
Studio didn't see the phone until I installed the OEM LG drivers from
<https://developer.android.com/studio/run/oem-usb#Drivers>
Specifically the LG TP450 driver for the $130 LG Stylo 3 Plus:
<https://www.lg.com/us/support/software-firmware-drivers?search=lg+tpe450#>=
Then all you do is follow their step by step tutorial which just works:
<https://developer.android.com/training/basics/firstapp/>
This is my first (baby) step to writing simple Android/iOS apps that are:
o Forever free
o No ads
o No servers
o No spyware
o Simple user interface to do a given simple job the simplest way possible
<http://www.bild.me/bild.php?file=7570013helloworld01.jpg>
One catch-22 was that emulation required hardware acceleration, but that
wouldn't work for me, so I can _only_ run on the phone right now (which
isn't too bad, for now) until I figure out a way around that gotcha.
Later, I'll deal with getting a hello world to work on the iOS devices.
<https://www.androidauthority.com/developing-for-android-vs-ios-697304/>
[toc] | [next] | [standalone]
| From | Diesel <me@privacy.net> |
|---|---|
| Date | 2018-10-27 05:39 +0000 |
| Message-ID | <XnsA98812FA7BE47HT1@I7w5O61WtaKs6p1nJ9Lx.Ma5cjSo80I8O.yY3> |
| In reply to | #56860 |
Arlen Holder <a%rlenh.older@no.spam.net> news:pr05f2$t0d$1@news.mixmin.net Fri, 26 Oct 2018 22:45:55 GMT in alt.comp.freeware, wrote: > Report: My first "hello world" using Android Studio freeware on > Windows worked just fine (total elapsed time was about an hour). > <http://www.bild.me/bild.php?file=7570013helloworld01.jpg> > <http://www.bild.me/bild.php?file=4072224helloworld02.jpg> > <http://www.bild.me/bild.php?file=7646977helloworld03.jpg> > <http://www.bild.me/bild.php?file=3369563helloworld04.jpg> What does this have to do with alt.comp.freeware or the various other usenet newsgroups you've spammed this to? > The main issues to deal with are: > o OEM USB Drivers for your phone (I had driver issues but > surmounted them) o Phone set to USB Debugging Mode (already a > basic setup for most users) o Android Studio (freeware, easily > installed & seemingly powerful) o Android SDK (Android Studio > handles this well) o Java (Android Studio handles this well, at > least for Hello World) These are only issues for people like you who don't know what you're doing and don't bother reading documentation. Others who download it realize it's a programming environment and are most likely well aware of the 'main issues' you had trouble with, and likely won't require help dealing with them. Unlike yourself. > The installation of Android Studio takes about an hour to download > stuff: > <https://developer.android.com/studio/install> Nopers, not for me it didn't. More like 20 minutes or so. You must have a shitty amount of bandwidth allocated to you. I'll have 1gbit input to my home and office very soon for the same price as I'm paying now for the 100mbit connection I have at both places; which is quite nice considering. > You want to plan ahead to decide where you want to put things > though Coders and/or serious programmers already do this when we setup the compiler/programming package(s) we're using. I don't know why you feel it necessary to re-invent the wheel here. And again, don't know why you felt it necessary to include all of these groups: comp.mobile.android alt.comp.freeware microsoft.public.windowsxp.general What the fuck does windows XP general (especially considering that your previous comments in another thread concerning XP entirely dismiss it as old news) have to do with your recent discovery here? > My main noob mistake was to keep this default, which I should have > removed: No, it wasn't. You've made much better noob mistakes. Your first one was calling me a moron when I've been a certified (having multiple certifications) professional computer repair technician for over two decades. Have you succesfully gotten a drive letter to represent either the internal and/or external memory on your phone yet? It's been almost two weeks since your first thread creation asking how. > Another noob mistake I made was that I had to re-install the > original OEM (LG Stylo 3 Plus) USB drivers before Android Studio > could see it: > <https://developer.android.com/studio/run/oem-usb#Drivers> That wasn't actually necessary. Your system had the physical files from your previous installation. It was missing the registry settings. > Even though Windows had no problem seeing the phone over USB, > Android Studio didn't see the phone until I installed the OEM LG > drivers from > <https://developer.android.com/studio/run/oem-usb#Drivers> > > Specifically the LG TP450 driver for the $130 LG Stylo 3 Plus: > <https://www.lg.com/us/support/software-firmware-drivers?search=lg > +tpe450#>= That only applies to your stylus, due to the firmware revision your using. Others may/may not have to do the same. Still yet, they may have to select other 'generic' drivers to use their Android product. Do you understand yet, Arlen that not all Android devices are created equally? Or, do you need more time and yet more examples of that before it sinks in? > Then all you do is follow their step by step tutorial which just > works: > <https://developer.android.com/training/basics/firstapp/> > > This is my first (baby) step to writing simple Android/iOS apps > that are: Ayep, baby step. You haven't got the foggiest idea what you're doing. Do you expect to pickup coding (well, scripting, even if it's java) overnight or something? Are you planning to make the next great thing in a couple of days time? You don't have the experience yet to write code at the level I and many of my peers do, Arlen. In other words, I don't expect to see freeware created entirely by you anytime soon. Perhaps, you'll release something 2019 or first part of 2020 if you keep with it. At the rate you're going getting a drive letter to represent internal/external memory on an Android phone over wifi and/or usb though, it's looking more like 2020... > One catch-22 was that emulation required hardware acceleration, > but that wouldn't work for me, so I can _only_ run on the phone > right now (which isn't too bad, for now) until I figure out a way > around that gotcha. *yawn* I didn't know usenet was your personal journal? -- To prevent yourself from being a victim of cyber stalking, it's highly recommended you visit here: https://tekrider.net/pages/david-brooks-stalker.php =================================================== 110 people once tied for second prize in the Powerball Lottery after playing the same lucky numbers from a fortune cookie.
[toc] | [prev] | [next] | [standalone]
| From | Arlen Holder <a%rlenh.older@no.spam.net> |
|---|---|
| Date | 2018-10-27 08:38 +0000 |
| Message-ID | <pr186r$m6i$1@news.mixmin.net> |
| In reply to | #56863 |
On Sat, 27 Oct 2018 05:39:49 -0000 (UTC), Diesel wrote: > What does this have to do with alt.comp.freeware or the various other > usenet newsgroups you've spammed this to? It's all about Windows & Android freeware, whether you realize it or not: o It's a test of Android Studio freeware (which downloads SDK freeware) o And it's about _writing_ Android freeware that does not yet exist The whole reason I tried the Windows freeware was so that I could overcome basic issues with current Android freeware, such as the fact that Android doesn't have non-ad, non server, non spyware, etc., freeware that... o Sets native Screenshot file output to a folder on the external sdcard o Creates a single press "10" minute alarm that requires no other action o Pops up a keyboard that _defaults_ to the microphone (for God's sake!) o Camera that works better with gloves under a vehicle in awkward positions o Outputs an editable file of all apps installed & versions & URLs o Single press surreptitious recording of ambient conversations o Keyword-driven locally processed custom virtual assistant etc. As per this recent thread: What are the most fundamental basic apps that are (apparently) lacking on Android? <https://groups.google.com/forum/#!topic/comp.mobile.android/SZk_fXWqg88> > Nopers, not for me it didn't. More like 20 minutes or so. You must > have a shitty amount of bandwidth allocated to you. You might have cable. We are too far away from civilization for that. There are no wires or pipes that come or go from my house to a "public utility" other than the power lines (and even they fall down about a dozen times a year, which is a perennial beef we have with our power company). And we have both a femtocell & a cellular repeater for our cell signal: <http://www.bild.me/bild.php?file=8809135cellular01.jpg> Which I've tested to see which works best in which room of the house: <http://www.bild.me/bild.php?file=8831319cellular04.jpg> Where we get pretty good at cellular & WiFi signal-debugging freeware: <http://www.bild.me/bild.php?file=3792112cellular02.jpg> But if you know of better WiFi debugging freeware, please let us know: <http://www.bild.me/bild.php?file=1851937cellular03.jpg> Because we're _always_ looking for better WiFi & cellular debug freeware! <http://www.bild.me/bild.php?file=1793606cellular07.jpg> > I'll have 1gbit > input to my home and office very soon for the same price as I'm > paying now for the 100mbit connection I have at both places; which is > quite nice considering. Our net speeds are nothing like yours with cable at the price you pay. Our WISP Internet comes through the air from quite a few miles away, so we're all pretty good at setting up radio antennas, and our plots are large, so we have plenty of spare radios where I personally have about a dozen access points like this one scattered about the house and property: <http://www.bild.me/bild.php?file=5562233cellular06.jpg> > Ayep, baby step. You haven't got the foggiest idea what you're doing. > Do you expect to pickup coding (well, scripting, even if it's java) > overnight or something? Are you planning to make the next great thing > in a couple of days time? You don't have the experience yet to write > code at the level I and many of my peers do, Arlen. While we're both very old men, the big difference between me, and you, Diesel, is that I'm an average adult of average intelligence. Even so, I _hate_ coding, where the _last_ time I wrote in a bona-fide programming language (not just shell scripts) was when I took COBOL, PL/1 (yes, this is before "C"), IBM Assembly language (yes, in the days when "duplex" was a big deal), and Fortran (yes, before Fortran 77 even existed). I hated "write(x,y)" statements then, and I'd likely hate them now. :) Same with "Error 42" codes that we looked up in a big fat book outside the paper output bins and the punch-card readers. The problem is that I hate software that doesn't do the simplest of things, as I described above. So I'm going to see if I can write it. All my software will always be o freeware o no ads o no servers o no spyware o simple as can be to do a single job well It will _always_ be provided so that _everyone_ can use it for free. You can either help, or complain. In short, to answer your question about freeware, this thread happens to be o About Windows freeware o To write Android freeware
[toc] | [prev] | [next] | [standalone]
| From | Diesel <me@privacy.net> |
|---|---|
| Date | 2018-10-31 05:51 +0000 |
| Message-ID | <XnsA98C14E8586D7HT1@3Y3w3.zZV3L2KG.TO> |
| In reply to | #56867 |
Arlen Holder <a%rlenh.older@no.spam.net> news:pr186r$m6i$1@news.mixmin.net Sat, 27 Oct 2018 08:38:52 GMT in alt.comp.freeware, wrote: > On Sat, 27 Oct 2018 05:39:49 -0000 (UTC), Diesel wrote: > >> What does this have to do with alt.comp.freeware or the various >> other usenet newsgroups you've spammed this to? > > It's all about Windows & Android freeware, whether you realize it > or not: o It's a test of Android Studio freeware (which downloads > SDK freeware) o And it's about _writing_ Android freeware that > does not yet exist Fair enough. What does it have to do with Windows XP specifically though? You've previously dismissed WIndows XP as being irrelevant in this day and age. You incorrectly assume that no person and/or business still makes use of it. In fact, you really have no idea how much in use it still is. alt.comp.freeware isn't actually a programming newsgroup though. I don't know if the others you've selected are, but, alt.comp.freeware isn't. There are newsgroups specifically for discussing programming in a wide variety of languages. You may want to check and see if your news server(s) carry one or more. You may find help more specifically tailored towards programming on them. >> Nopers, not for me it didn't. More like 20 minutes or so. You >> must have a shitty amount of bandwidth allocated to you. > > You might have cable. We are too far away from civilization for > that. Indeed, I do. Spectrum. I've also got a spiffy Intel box that I used to examine the SDK with; hence my times aren't anything like yours. The intel box I used has all the requirements and then some... :) If it helps, it's an i7-8700K (that's an unlocked chip my friend) with 32gigs of gskill ram running at 3400 in pairs. (2x16) With a half tb SSD drive that was used for the download and install. [g] Sitting on an MSI z370 pro series mainboard, WD drives, EVGA super nova 1kw power supply. Nvidia 2080K series (gross overkill and has nothing to do with the Android SDK).. Yes, it's liquid cooled; as in refrigerant with a small compressor just like you'd find on your window based air conditioner unit. It easily cruises upto 5ghz and remains stable as fuck, thanks to that cooling system. I've got *alot more* CPU horsepower than your AMD phenom 2 ever even thought about. And that's just ONE machine here. suffice to say, it's a fucking monster. I've got more cores, more threads on each core, and a shitload more cache as well as clock cycles. Your AMD can't touch it. One of the perks of being a certified technician, you actually know WTF you're doing and are more than capable of spec'ing a build as well as final assembly. I can do it in my damn sleep. > Our net speeds are nothing like yours with cable at the price you > pay. No, they aren't. I have a package deal at both places, so, I'm not paying much for what I'm getting. > While we're both very old men, the big difference between me, and > you, Diesel, is that I'm an average adult of average intelligence. That's just one difference. That being said, I would like to see the post I wrote to you where I ever claimed I was a genius? I'm not an idiot, by no means, but... genius? That depends on what you consider genius to be and in what field specifically. Or trait. > It will _always_ be provided so that _everyone_ can use it for > free. You can either help, or complain. Actually, I have a third option. I can choose to do neither. :) -- To prevent yourself from being a victim of cyber stalking, it's highly recommended you visit here: https://tekrider.net/pages/david-brooks-stalker.php =================================================== There's always more going on than you think. And it's always worse than you imagine.
[toc] | [prev] | [next] | [standalone]
| From | "BurfordTJustice" <burford/associate@uk.MI15> |
|---|---|
| Date | 2018-10-31 07:12 -0400 |
| Message-ID | <prc2nb$1vv$1@dont-email.me> |
| In reply to | #56952 |
Still only 2 bit "brag" and name calling...LOL "Diesel" <me@privacy.net> wrote in message news:XnsA98C14E8586D7HT1@3Y3w3.zZV3L2KG.TO... : Arlen Holder <a%rlenh.older@no.spam.net> : news:pr186r$m6i$1@news.mixmin.net Sat, 27 Oct 2018 08:38:52 GMT in : alt.comp.freeware, wrote: : : > On Sat, 27 Oct 2018 05:39:49 -0000 (UTC), Diesel wrote: : > : >> What does this have to do with alt.comp.freeware or the various : >> other usenet newsgroups you've spammed this to? : > : > It's all about Windows & Android freeware, whether you realize it : > or not: o It's a test of Android Studio freeware (which downloads : > SDK freeware) o And it's about _writing_ Android freeware that : > does not yet exist : : Fair enough. What does it have to do with Windows XP specifically : though? You've previously dismissed WIndows XP as being irrelevant in : this day and age. You incorrectly assume that no person and/or : business still makes use of it. In fact, you really have no idea how : much in use it still is. : : alt.comp.freeware isn't actually a programming newsgroup though. I : don't know if the others you've selected are, but, alt.comp.freeware : isn't. There are newsgroups specifically for discussing programming : in a wide variety of languages. You may want to check and see if your : news server(s) carry one or more. You may find help more specifically : tailored towards programming on them. : : >> Nopers, not for me it didn't. More like 20 minutes or so. You : >> must have a shitty amount of bandwidth allocated to you. : > : > You might have cable. We are too far away from civilization for : > that. : : Indeed, I do. Spectrum. I've also got a spiffy Intel box that I used : to examine the SDK with; hence my times aren't anything like yours. : The intel box I used has all the requirements and then some... :) : : If it helps, it's an i7-8700K (that's an unlocked chip my friend) : with 32gigs of gskill ram running at 3400 in pairs. (2x16) With a : half tb SSD drive that was used for the download and install. [g] : Sitting on an MSI z370 pro series mainboard, WD drives, EVGA super : nova 1kw power supply. Nvidia 2080K series (gross overkill and has : nothing to do with the Android SDK).. : : Yes, it's liquid cooled; as in refrigerant with a small compressor : just like you'd find on your window based air conditioner unit. It : easily cruises upto 5ghz and remains stable as fuck, thanks to that : cooling system. I've got *alot more* CPU horsepower than your AMD : phenom 2 ever even thought about. And that's just ONE machine here. : suffice to say, it's a fucking monster. : : I've got more cores, more threads on each core, and a shitload more : cache as well as clock cycles. Your AMD can't touch it. One of the : perks of being a certified technician, you actually know WTF you're : doing and are more than capable of spec'ing a build as well as final : assembly. I can do it in my damn sleep. : : > Our net speeds are nothing like yours with cable at the price you : > pay. : : No, they aren't. I have a package deal at both places, so, I'm not : paying much for what I'm getting. : : > While we're both very old men, the big difference between me, and : > you, Diesel, is that I'm an average adult of average intelligence. : : That's just one difference. That being said, I would like to see the : post I wrote to you where I ever claimed I was a genius? I'm not an : idiot, by no means, but... genius? That depends on what you consider : genius to be and in what field specifically. Or trait. : : > It will _always_ be provided so that _everyone_ can use it for : > free. You can either help, or complain. : : Actually, I have a third option. I can choose to do neither. :) : : : : -- : To prevent yourself from being a victim of cyber : stalking, it's highly recommended you visit here: : https://tekrider.net/pages/david-brooks-stalker.php : =================================================== : There's always more going on than you think. And it's always worse : than you imagine.
[toc] | [prev] | [next] | [standalone]
| From | Diesel <me@privacy.net> |
|---|---|
| Date | 2018-11-01 23:44 +0000 |
| Message-ID | <XnsA98DCAE52C293HT1@pX7n2hFF.h4707X5M757uYdSGm0I2e174mbOawYQlnxmQU4Mf4I426r9ai83> |
| In reply to | #56967 |
"BurfordTJustice" <burford/associate@uk.MI15> news:prc2nb$1vv$1@dont-email.me Wed, 31 Oct 2018 11:12:40 GMT in alt.comp.freeware, wrote: > Still only 2 bit "brag" and name calling...LOL Burford, we already know technical subjects aren't your forte. Why the need to embarrass yourself (further) and put on another demonstration? -- To prevent yourself from being a victim of cyber stalking, it's highly recommended you visit here: https://tekrider.net/pages/david-brooks-stalker.php =================================================== System error 4C: kernel panic
[toc] | [prev] | [next] | [standalone]
| From | Bill <Billaboard@gmail.com> |
|---|---|
| Date | 2018-10-30 00:14 +0000 |
| Message-ID | <Pz3jrhdwJ61bFw9L@end.of.the.universe> |
| In reply to | #56860 |
In message <pr05f2$t0d$1@news.mixmin.net>, Arlen Holder <a%rlenh.older@no.spam.net> writes >Getting a "hello world" to work on an Android phone may sound like an >accomplishment, but it's not really that much since all you do is punch >buttons, given that the Google Android Studio freeware literally writes >the >entire app for you. > <https://developer.android.com/studio/> Thanks, Arlen, for posting this. I hadn't heard about it before, and it looks as though it might be useful as a way to knock up one or two specialist apps in the future. I tried building the Hello World app and got it working without any problems. But, it took me a whole afternoon on a i5-2520M laptop with 8GB of ram, and during that time everything else on the machine became almost totally unresponsive. The processor appears to support HAXM, but I missed the place to check to install this. Everything was so slow that I kept thinking the installation/build had crashed. Can I ask the spec of your old desktop? -- Bill --- This email has been checked for viruses by AVG. https://www.avg.com
[toc] | [prev] | [next] | [standalone]
| From | Arlen Holder <a%rlenh.older@no.spam.net> |
|---|---|
| Date | 2018-10-30 19:51 +0000 |
| Message-ID | <pracn5$el0$1@news.mixmin.net> |
| In reply to | #56916 |
On Tue, 30 Oct 2018 00:14:40 +0000, Bill wrote: > Thanks, Arlen, for posting this. I hadn't heard about it before, and it > looks as though it might be useful as a way to knock up one or two > specialist apps in the future. Thank you Bill for posting that it helped you, as that's my goal, which is to help everyone at the same time that I help myself. I've always been that way, so I'm completely different than most people who are only about themselves. Maybe we can help each other. I am hoping to use Android Studio to write a "beep in ten minutes app". Here's my current status of the "hello world" in Android Studio: <http://www.bild.me/bild.php?file=9210567androidstudio05.jpg> Where this is the result on the Android Nougat 7.0 LG Stylo 3 Plus: <http://www.bild.me/bild.php?file=2116419androidstudio06.jpg> I haven't spent a lot of time with Android Studio (just that first hello world), but I'm willing to get the first app to work, which, I hope to be a simple timer app that has the fewest buttons possible, and that goes away and of course, no ads, no servers, no spyware, nothing but the basic app. - Press here to beep in 5 minutes (and then go away until beep). - Press here to beep in 10 minutes (and then go away until beep). - Press here to beep in 30 minutes (and then go away until beep). - Press here to beep in 1 hour (and then go away until beep). - Enter the time to beep [___]minutes (and then go away until beep). etc. The _great_ news about Android Studio is that it literally _writes_ your first app for you and puts it on your phone, and the app actually works! From there, it's learning how to add bits and buttons. :) Layout file: Source file: > I tried building the Hello World app and got it working without any > problems. Good for you. I can't get the emulation to work on my old Win10 desktop. <http://www.bild.me/bild.php?file=5625744androidstudio01.jpg> But the app works perfectly on the phone (Nougat LG Stylo 3 Plus, 64GB). Here's the error I get during emulation: <http://www.bild.me/bild.php?file=3629764androidstudio03.jpg> o Emulator: emulator: ERROR: x86 emulation currently requires hardware acceleration! o 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. o Emulator: Process finished with exit code 1 o Gradle build finished in 1 m 15 s 77 ms > But, it took me a whole afternoon on a i5-2520M laptop with > 8GB of ram, and during that time everything else on the machine became > almost totally unresponsive. Truth be told, all DIYs are "idealized" in that they take longer than the person said they did, where my initial efforts also took longer. I just said an hour as a guess, but I let it run and so the elapsed time was overnight but I didn't calculate exactly how much time was idle so I "assumed" about an hour of actual actions (but it was likely longer). In reality, I agree with you that it takes longer, so double that, or triple that or something, but Diesel's assessment of '20 minutes' is just dead wrong, and unachievable, I would think. (Diesel is always trying to prove how smart he is so take anything he says with a grain of salt.) I have no desire to prove I'm smart, so I have no problems admitting when I screw up, or when I'm wrong, or when I'm ignorant of something, so you can trust me more than you can trust most people who can't admit when they're stupid. If I were to have a gun put to my head, I'd assess the time at, oh, a "few" hours, so the "whole afternoon" seems reasonable to me, as it does have to download and then unpack a _lot_ of stuff the first time around (and the Google site is super sloooooooooooooooooow where it gets stuff from). > The processor appears to support HAXM, but > I missed the place to check to install this. I first had HAXM (whatever that is) turned on by Android Studio by default, and then I had to turn it off so when I re-installed Android Studio (which takes less time than the first install because the SDK is already there by then), I turned off the HAXM (whatever that is). I think you won't _see_ the Android Studio HAXM setting unless you ask to do a _custom_ install. I have no idea what HAXM is, by the way, and I didn't google it because HAXM isn't what I want to do right now. If you have a clue what HAXM is, and how to tell if my machine has it, that would be useful, but don't go to any trouble unless you already know offhand as I could look it up. > Everything was so slow that I kept thinking the installation/build had > crashed. The zip files from Google take a looooooooooong time to download. I just walked away and came back later, so my _elapsed_ time was likely as long as yours was (I didn't actually count the time). > Can I ask the spec of your old desktop? Sure. Ask anything. We can help each other. My old desktop has 16GB of RAM, so that's the one good thing, and it's Win10, so that's another good thing, but everything else is just old. It's an HP Pavilion P6230, 2.6Hhz, AMD Phenom2 CPU, with an Nvidia graphics card. Nothing fancy. I'm working on simply getting the "hello world" button to beep. <https://developer.android.com/training/basics/firstapp/building-ui> Here's the crappy look at the moment, but it's my first button. <http://www.bild.me/bild.php?file=3610557androidstudio04.jpg> The buttons don't do anything yet, but they'll eventually ring an alarm: <http://www.bild.me/bild.php?file=2116419androidstudio06.jpg> If we can work together on something like this, or if others have a suggestion, it would be nice to get a handful of interested folks to pick a SIMPLE action (like ring a bell) and then work together toward that goal. That would make Usenet very useful, don't you think?
[toc] | [prev] | [next] | [standalone]
| From | Arlen Holder <a%rlenh.older@no.spam.net> |
|---|---|
| Date | 2018-10-30 20:13 +0000 |
| Message-ID | <prae1i$gqd$1@news.mixmin.net> |
| In reply to | #56940 |
On Tue, 30 Oct 2018 19:51:20 -0000 (UTC), Arlen Holder wrote: > I think you won't _see_ the Android Studio HAXM setting unless you ask to > do a _custom_ install. Hi Bill, Does your Windows computer motherboard have an Intel CPU or AMD CPU? <http://www.bild.me/bild.php?file=3945600androidstudio07.jpg> Apparently, "HAXM" isn't on Windows, by default, nor, apparently, will it install on AMD computers (which mine is). o Intel Virtualization Technology (VT, VT-x, vmx) extensions o AMD Virtualization (AMD-V, SVM) extensions (only supported for Linux) If your motherboard has an Intel CPU, this HAXM information may help you. Installation instructions for installing HAXM on Windows <https://github.com/intel/haxm/wiki/Installation-Instructions-on-Windows> Download software for Intel Hardware Accelerated Execution Manager <https://software.intel.com/en-us/articles/intel-hardware-accelerated-execution-manager-intel-haxm>
[toc] | [prev] | [next] | [standalone]
| From | Diesel <me@privacy.net> |
|---|---|
| Date | 2018-10-31 05:51 +0000 |
| Message-ID | <XnsA98C14E689EF0HT1@3Y3w3.zZV3L2KG.TO> |
| In reply to | #56941 |
Arlen Holder <a%rlenh.older@no.spam.net> news:prae1i$gqd$1@news.mixmin.net Tue, 30 Oct 2018 20:13:41 GMT in alt.comp.freeware, wrote: > Hi Bill, > > Does your Windows computer motherboard have an Intel CPU or AMD > CPU? > <http://www.bild.me/bild.php?file=3945600androidstudio07.jpg> > > Apparently, "HAXM" isn't on Windows, by default, nor, apparently, > will it install on AMD computers (which mine is). > o Intel Virtualization Technology (VT, VT-x, vmx) extensions > o AMD Virtualization (AMD-V, SVM) extensions (only supported for > Linux) > > If your motherboard has an Intel CPU, this HAXM information may > help you. Did you miss this part? Message-ID: <Pz3jrhdwJ61bFw9L@end.of.the.universe> But, it took me a whole afternoon on a i5-2520M laptop with 8GB of ram, and during that time everything else on the machine became almost totally unresponsive. The processor appears to support HAXM, but I missed the place to check to install this. ***end snippit paste Do you see the i5? That's an Intel designation. He has (wait for it) an Intel based system. Do watch who you refer to as dumb, ignorant, stupid, or any other choice assinine comments you have for others, next time around; n00b. -- To prevent yourself from being a victim of cyber stalking, it's highly recommended you visit here: https://tekrider.net/pages/david-brooks-stalker.php =================================================== Modem: A great deterrent to phone solicitors
[toc] | [prev] | [next] | [standalone]
| From | Arlen Holder <a%rlenh.older@no.spam.net> |
|---|---|
| Date | 2018-10-31 07:26 +0000 |
| Message-ID | <prble9$utq$1@news.mixmin.net> |
| In reply to | #56947 |
On Wed, 31 Oct 2018 05:51:26 -0000 (UTC), Diesel wrote: > Do watch who you refer to as dumb, ignorant, > stupid, or any other choice assinine comments you have for others, > next time around; n00b. This post is for Bill, where it is apparently considered normal for it to take a long time for Android Studio to initially set itself up for you. <http://www.ntu.edu.sg/home/ehchua/programming/Android/Android_HowTo.html> Notice that site agrees with you, Bill, in that: "The installation and many operations take a LONG time to complete." "It takes time - from 30 minutes to n hours to forever." While the Android Studio IDE takes care of everything, here are the parts: 1. Java JDK (includes JRE) <https://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html> (The Android Studio IDE will download & unpack the JDK for you.) 2. Android SDK <https://developer.android.com/sdk/older_releases> (The Android Studio IDE will download & unpack the SDK for you.) 3. Android Studio IDE <https://developer.android.com/studio/install> (This is all you need since it will set up the SDK & JDK for you.)
[toc] | [prev] | [next] | [standalone]
| From | Bill <billaboard@gmail.com> |
|---|---|
| Date | 2018-11-01 12:21 +0000 |
| Message-ID | <prer46$cg3$1@dont-email.me> |
| In reply to | #56954 |
On 31/10/2018 07:26, Arlen Holder wrote: > This post is for Bill, where it is apparently considered normal for it to > take a long time for Android Studio to initially set itself up for you. > <http://www.ntu.edu.sg/home/ehchua/programming/Android/Android_HowTo.html> > Notice that site agrees with you, Bill, in that: > "The installation and many operations take a LONG time to complete." > "It takes time - from 30 minutes to n hours to forever." Here is where I'm up to. I moved from the Lenovo X220T machine to an older X201 - Intel i3 (1st generation) and have started again. Setting up Android studio seemed much quicker this time - somewhere around 1.5 hours. No obvious reason why. The Hello World app was set up quickly onto an emulated phone. All fine except for a warning that there had been reports of instability of the drivers for my Intel GPU when displaying the emulator. It looked OK and I'm using the latest drivers. Started the button and text box next stage of the app and all went well until I reached the end of the "Make the text box size flexible" section, where suddenly both the text box and button vanished from the blueprint display. Edit->Undo didn't bring them back. I don't think this is a graphics problem. I have now started again, but with, hopefully, all the files in a real directory rather than the stupid Windows Users directories. This might make it simpler to poke around and understand where some of the files are and what they do. I'm in the UK. back in the mists of time I took a Java course at Liverpool University. It is now clear that I have forgotten all of it! -- Bill --- This email has been checked for viruses by AVG. https://www.avg.com
[toc] | [prev] | [next] | [standalone]
| From | Arlen_Holder <a%rle%20nh.older@no.spam.net> |
|---|---|
| Date | 2018-11-02 03:04 +0000 |
| Message-ID | <prger8$136$1@news.mixmin.net> |
| In reply to | #57019 |
On Thu, 1 Nov 2018 12:21:22 +0000, Bill wrote:
> Here is where I'm up to.
Hi Bill,
I'm like you, in a way, in that I only put a few minutes per day to this
and that I'm on an older machine (very old) and that I don't know java.
> I moved from the Lenovo X220T machine to an older X201 - Intel i3 (1st
> generation) and have started again.
I started again also, this time on app02 ... which is pictured below.
<http://www.bild.me/bild.php?file=9813868app02.gif>
> Setting up Android studio seemed much quicker this time - somewhere
> around 1.5 hours. No obvious reason why.
Good for you. I've had "issues" getting back to the main GUI where I had to
delete and re-install Android Studio a few times myself, just to get back
to the point that matched the documentation I was following. :)
o activity_main.xml ==> this is what your design looks like
o MainActivity.java ==> this is your java code
BTW, I made _one_ change to the default settings:
File > Settings > Editor > General > Auto Import >
Change from:
[_]Add unambiguous imports on the fly
[_]Optimize imports on the fly (for current project)
Change to:
[x]Add unambiguous imports on the fly
[x]Optimize imports on the fly (for current project)
I'm told that will make things easier if/when problems occur.
> The Hello World app was set up quickly onto an emulated phone. All fine
> except for a warning that there had been reports of instability of the
> drivers for my Intel GPU when displaying the emulator. It looked OK and
> I'm using the latest drivers.
Good for you that it works with emulation. I found lots of people on the
net asking about AMD emulation, which, if I get around to it, I'll explore.
For now, I'm running on the actual phone, which seems to work fine for me.
> Started the button and text box next stage of the app and all went well
> until I reached the end of the "Make the text box size flexible"
> section, where suddenly both the text box and button vanished from the
> blueprint display. Edit->Undo didn't bring them back. I don't think this
> is a graphics problem.
I feel for you, in that I too have had "issues" with putting buttons and
text boxes where I want them to go. Luckily, the graphical editor is
amenable to experimentation, where those 'constraints' don't seem to take
every time (for some odd reason).
<http://www.bild.me/bild.php?file=1608334app02a.gif>
> I have now started again, but with, hopefully, all the files in a real
> directory rather than the stupid Windows Users directories.
Yup. I always put absolutely nothing in "Users" although there are two
"dot" directories that go in Users by default by the Android Studio IDE:
o c:\users\<you>\.android\ (I'm not sure why stuff was put here)
o c:\users\<you>\.AndroidStudio3.2\ (I'm not sure why stuff is here)
Here's where I put the stuff that Android Studio downloaded:
o Android Studio IDE: c:\app\hardware\android\studio\
o Java SDK: c:\app\hardware\android\sdk\
o Projects: c:\tmp\android\{app01,app02,app03,etc.}
In the Android Studio IDE, these seem to be the most important files:
Android > app
manifests = (which activity is the starter activity)
java folder (where all java code goes)
o package1 = official package
* MainActivity = *** important ***
resources
o drawable package = application icon, pictures included
o layout package = what the app looks like
* activity_main.xml = *** important ***
o values package = holds string names such as app name
* strings.xml = *** important ***
> This might
> make it simpler to poke around and understand where some of the files
> are and what they do.
I agree completely that there is a _steep_ learning curve.
Here are the critical files, as I see them, so far:
Android > app
manifests = (which activity is the starter activity)
java folder (where all java code goes)
o package1 = official package
* MainActivity =
o package2 = testing package
o package3 = testing package
resources
o drawable package = application icon, pictures included
o layout package = what the app looks like
* activity_main.xml =
o mipmap package =
o values package = holds string names such as app name
* strings.xml = where your strings are defined
> I'm in the UK. back in the mists of time I took a Java course at
> Liverpool University. It is now clear that I have forgotten all of it!
I am old. My last class was COBOL and Fortran _before_ 77 existed.
I took IBM assembly language and PL/1 before C existed (AFAIK).
But those were many decades ago. Obviously. I haven't coded since.
Coding isn't an issue though, as I can learn what I need to learn.
Luckily, so far, everything has been cut and paste and graphical:
<http://www.bild.me/bild.php?file=1608334app02a.gif>
I've almost given up on that original text tutorial, simply because I was
spending ten seconds reading a sentence and then ten minutes trying to find
the button the tutorial said to press.
<https://developer.android.com/training/basics/firstapp/>
Instead, I looked for *better* tutorials, specifically in YouTube
o EVERY step now has a graphical point-and-click direction, and,
o My rather smallish desktop monitor is freed up for the Android Studio IDE
Here are 8 Android Studio beginner tutorials I think "might" be good,
bearing in mind I sorted them by year, and I removed any that didn't sound
intelligible or useful in the first 30 seconds, so I've only skimmed this
bunch - hence consider it only the first cut of the tutorials on the net
that _may_ be useful.
----------------------------------------------------------------------------
a) 3. Introduction to Android Studio (AS 3.1.3)
by Johan Jurrius, Published on Jul 16, 2018 (mp4)
https://youtu.be/_418iSKJuOk
----------------------------------------------------------------------------
b) How to Make an Android App for Beginners
by Treehouse, Published on Apr 20, 2018 (mkv)
https://youtu.be/EOfCEhWq8sg
----------------------------------------------------------------------------
c) Android App Development for Beginners (2018 Edition):
by Daniel Malone, Published on Dec 31, 2017 (webm, mkv, mp4)
(Uses Kotlin)
https://youtu.be/LN8fBh7LH9k (part 1)
https://youtu.be/u5Gj-_ifxUo (part 2)
https://youtu.be/axwFF4oSDi8 (part 3)
https://youtu.be/ASzpxZ504Es (part 4)
https://youtu.be/GR_JtJWzh4Y (part 5)
----------------------------------------------------------------------------
d) Android Studio For Beginners Part 1, 2, 3, 4
by Bill Butterfield, Published on Jun 13, 2017 (mp4)
(It's a slightly older version of Android Studio.)
(You build a basic calculator adding app.)
https://youtu.be/dFlPARW5IX8 (part 1)
https://youtu.be/6ow3L39Wxmg (part 2)
https://youtu.be/rdGpT1pIJlw (part 3)
https://youtu.be/bu5Y3uZ6LLM (part 4)
----------------------------------------------------------------------------
e) How to Make Android Apps with Android Studio and Java - Ep 1 - Start Here
by London App Brewery, Published on Apr 20, 2017 (webm, mkv)
https://youtu.be/agk01JKps8w (part 1)
https://youtu.be/NSoFTHDHY40 (part 2)
https://youtu.be/fFzpWuHGyhc (part 3)
https://youtu.be/gSRKhxuXTw4 (part 4)
https://youtu.be/g3jPYU9wCKg (part 5)
https://youtu.be/G4SJFk8PdAc (part 6)
https://youtu.be/e_Xe4sTWxTw (part 7)
https://youtu.be/qS9rZV-Qbpk (part 8)
https://youtu.be/8IZfYuTbCnY (part 9)
https://youtu.be/A6YE5jadnGo (part 10)
https://youtu.be/YeR2y3HdO1Q (part 11)
https://youtu.be/z87fVhI4Yt0 (part 12)
https://youtu.be/xIwFd-u6yKw (part 13)
https://youtu.be/wHA0AnURQ_M (part 14)
https://youtu.be/nYqxyfKOXBw (part 15)
----------------------------------------------------------------------------
f) Android Studio Tutorial - Streaming Video
by EDMT Dev, Published on Mar 12, 2017 (webm)
https://youtu.be/oEgpGv2CF1U
----------------------------------------------------------------------------
g) Writing your first Android app - everything you need to know
by Android Authority (Gary Sims), Published on Jun 30, 2015 (webm)
https://youtu.be/mAJeK283j0I
----------------------------------------------------------------------------
h) Tutorial: Android Studio, from zero knowledge to something basic
by Jonathan Warner, Published on Feb 2, 2015 (mkv)
https://youtu.be/-igAiudpBng
----------------------------------------------------------------------------
Bill,
This tutorial from the list above seems pretty good, which makes a simple
addition calculator app, which I've been following for about an hour
o d) Android Studio For Beginners Part 1, 2, 3, 4
o by Bill Butterfield, Published on Jun 13, 2017
After about an hour of that tutorial stop and go, stop and go, stop and go,
I have this:
<http://www.bild.me/bild.php?file=9813868app02.gif>
<http://www.bild.me/bild.php?file=1608334app02a.gif>
[toc] | [prev] | [next] | [standalone]
| From | Diesel <me@privacy.net> |
|---|---|
| Date | 2018-11-01 23:44 +0000 |
| Message-ID | <XnsA98DCAE596010HT1@pX7n2hFF.h4707X5M757uYdSGm0I2e174mbOawYQlnxmQU4Mf4I426r9ai83> |
| In reply to | #56954 |
Arlen Holder <a%rlenh.older@no.spam.net> news:prble9$utq$1@news.mixmin.net Wed, 31 Oct 2018 07:26:01 GMT in alt.comp.freeware, wrote: > On Wed, 31 Oct 2018 05:51:26 -0000 (UTC), Diesel wrote: > >> Do watch who you refer to as dumb, ignorant, >> stupid, or any other choice assinine comments you have for >> others, next time around; n00b. > > This post is for Bill So you responded to me specifically (and snipped a considerable amount of my post, clearly showing your ignorance concerning the machine Bill already told you he had as well as HAXM, etc. [g]) for what reason, then? Here's what you snipped for reasons not known to me...: Did you miss this part? Message-ID: <Pz3jrhdwJ61bFw9L@end.of.the.universe> But, it took me a whole afternoon on a i5-2520M laptop with 8GB of ram, and during that time everything else on the machine became almost totally unresponsive. The processor appears to support HAXM, but I missed the place to check to install this. ***end snippit paste Do you see the i5? That's an Intel designation. He has (wait for it) an Intel based system. One could say you practically edited my post prior to responding to it, intending the reply to be for another person? You know what that smells like, right, Arlen? , where it is apparently considered normal > for it to take a long time for Android Studio to initially set > itself up for you. It depends on several variables, as I already wrote above... Now, for the purposes of downloading, just to show you how wrong and off base you actually are... The main .zip file, downloaded from the 3rd url you provided (on linux of course) was 1004 or so megabytes in size. Average dl speed was just under 23megabytes (yea, megabytes) a second. The oracle SDK linuxx64 bit rpm package was 168megs and took roughly 35 seconds or so to leech. The megabytes bounced from just below 12 to averaging out at around 4.5 for the remainder. grabbed the largest sdk from your older versions url. 248megs, got in less than 25 seconds. rofl. The remainder of the 20 minutes, give or take a few; I was doing several things at once at the time on various machines here was spent doing the actual 'installation' phases. So yea, within 20 minutes or so, I was up and running, IDE open on the primary desktop screen, ready for use. That's a properly cooled and configured, I7-8700K for you. Installation times (not dl times) would vary if I were to install it on various other machines here, due to hardware specification differences and only that. Bandwidth isn't the issue. [g] > <http://www.ntu.edu.sg/home/ehchua/programming/Android/Android_How > To.html> > Notice that site agrees with you, Bill, in that: > "The installation and many operations take a LONG time to > complete." "It takes time - from 30 minutes to n hours to > forever." The site doesn't disagree with me, either, Arlen. The entire time table is an estimate. It depends on several variables which most likely, would exceed your level of expertise to delve into. Suffice to say, > While the Android Studio IDE takes care of everything, here are > the parts: 1. Java JDK (includes JRE) > <https://www.oracle.com/technetwork/java/javase/downloads/jdk8-d > ownloads-2133151.html> (The Android Studio IDE will download & > unpack the JDK for you.) > 2. Android SDK > <https://developer.android.com/sdk/older_releases> > (The Android Studio IDE will download & unpack the SDK for > you.) > 3. Android Studio IDE > <https://developer.android.com/studio/install> > (This is all you need since it will set up the SDK & JDK for > you.) Yep. It doesn't take very long for me to download or install it on the machine I provided some specs on previously, Arlen. What you wrote below is entirely, false. Further, you yourself provided time table estimates which DIRECTLY CONTRADICT what you wrote and yet, support what I told you, the first time. What you specifically attacked me for in this snippit of one of your posts, below: MID: <pracn5$el0$1@news.mixmin.net> In reality, I agree with you that it takes longer, so double that, or triple that or something, but Diesel's assessment of '20 minutes' is just dead wrong, and unachievable, I would think. (Diesel is always trying to prove how smart he is so take anything he says with a grain of salt.) ** end snippit You have an older machine which has an older cpu that you prior to a few days ago, knew next to nothing about. You didn't even know that it couldn't possibly support HAXM regardless of your desire to enable/disable it. MID: <pracn5$el0$1@news.mixmin.net> I have no desire to prove I'm smart, so I have no problems admitting when I screw up, or when I'm wrong, or when I'm ignorant of something, so you can trust me more than you can trust most people who can't admit when they're stupid. *** end snippit When do you plan to admit you were wrong and screwed up quite badly here? You went out of your way to attack me in a reply supposedly written for Bill. Are you going to own up to your mistake, Arlen? As i've suggested before, You should watch whom you refer to as stupid in the future. As, sadly, you've actually demonstrated you suffer from it on multiple levels, yourself. -- To prevent yourself from being a victim of cyber stalking, it's highly recommended you visit here: https://tekrider.net/pages/david-brooks-stalker.php =================================================== System error 4C: kernel panic
[toc] | [prev] | [next] | [standalone]
| From | Arlen_Holder <a%rle%20nh.older@no.spam.net> |
|---|---|
| Date | 2018-11-02 06:29 +0000 |
| Message-ID | <prgqrv$mff$1@news.mixmin.net> |
| In reply to | #57026 |
On Thu, 1 Nov 2018 23:44:10 -0000 (UTC), Diesel wrote:
> Bill already told you he had as well as HAXM, etc. [g])
> for what reason, then?
Woo hoo!
This is for Bill, where my first app (named "app01") was the
"Hello World" app from the Android text tutorial, but where
I was finding that I was taking 10 seconds to read an
instruction but then 10 minutes to find the button they
said to hit (since the text tutorial didn't _show_ the
buttons well).
<https://developer.android.com/training/basics/firstapp/>
My second app (named "app02") went a _lot_ smoother!
If Bill (or Diesel, or anyone else who is a noob but who
wants to write Android apps using freeware) wants to follow
along, here is my running log file of app02, which worked
after I realized that the older Android Studio used in the
tutorial had a very slight syntax differnece with the new
Android Studio, which caused a "compiler error".
==========================================================================
app02.log
============================================================================
Screenshots:
<http://www.bild.me/bild.php?file=9813868app02.gif>
<http://www.bild.me/bild.php?file=1608334app02a.gif>
<http://www.bild.me/bild.php?file=9175315app02b.gif>
============================================================================
Following this video:
d) Android Studio For Beginners Part 1, 2, 3, 4
by Bill Butterfield, Published on Jun 13, 2017 (mp4)
(It's a slightly older version of Android Studio.)
(You build a basic calculator adding app.)
https://youtu.be/dFlPARW5IX8 (part 1)
https://youtu.be/6ow3L39Wxmg (part 2)
https://youtu.be/rdGpT1pIJlw (part 3)
https://youtu.be/bu5Y3uZ6LLM (part 4)
============================================================================
This is what we accomplished in the first video above:
https://youtu.be/dFlPARW5IX8 (part 1)
a. Set up an Android Studio Project
b. Create a simple calculator app that added two integer numbers
c. Debugging step by step through the code
============================================================================
CHANGEFROM:
============================================================================
package com.app2company.app02;
import android.os.Bundle;
import android.support.v7.app.AppCompatActivity;
public class MainActivity extends AppCompatActivity {
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);
}
}
============================================================================
Note that the tutorial uses 'view' but the Android Studio uses 'v'.
Tutorial: public void onClick(View view) {
AndroidStudio: public void onClick(View v) {
This alone seems to have caused a compiler error, which complained about
a missing semicolon (;), but where there was no missing semicolon. Go figure.
============================================================================
CHANGETO:
============================================================================
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().toString());
int num2 = Integer.parseInt(secondNumEditText.getText().toString());
int result = num1 + num2;
resultTextView.setText(result + "");
}
});
}
}
============================================================================
Screenshots:
<http://www.bild.me/bild.php?file=9813868app02.gif>
<http://www.bild.me/bild.php?file=1608334app02a.gif>
<http://www.bild.me/bild.php?file=9175315app02b.gif>
============================================================================
[toc] | [prev] | [next] | [standalone]
| From | Diesel <me@privacy.net> |
|---|---|
| Date | 2018-11-02 08:03 +0000 |
| Message-ID | <XnsA98E2B6984822HT1@YMHc9WdP.R3Ec> |
| In reply to | #57029 |
Arlen_Holder <a%rle%20nh.older@no.spam.net> news:prgqrv$mff$1@news.mixmin.net Fri, 02 Nov 2018 06:29:20 GMT in alt.comp.freeware, wrote: > On Thu, 1 Nov 2018 23:44:10 -0000 (UTC), Diesel wrote: > >> Bill already told you he had as well as HAXM, etc. [g]) >> for what reason, then? > > Woo hoo! > > This is for Bill, where my first app (named "app01") was the > "Hello World" app from the Android text tutorial, but where > I was finding that I was taking 10 seconds to read an > instruction but then 10 minutes to find the button they > said to hit (since the text tutorial didn't _show_ the > buttons well). > <https://developer.android.com/training/basics/firstapp/> > > My second app (named "app02") went a _lot_ smoother! > > If Bill (or Diesel, or anyone else who is a noob but who > wants to write Android apps using freeware) wants to follow > along, here is my running log file of app02, which worked > after I realized that the older Android Studio used in the > tutorial had a very slight syntax differnece with the new > Android Studio, which caused a "compiler error". a noob at what specifically? Writing code for Android, specifically or writing code in general? You'd be wrong on both counts... <big fucking grin>; Remember when I told you freeware existed to do what you wanted? I might not have mentioned I may have written something for the task and might have shared the apk with you, and entire source code for that matter; had you not been a prick towards me. You only stated it had to be freeware; you didn't say any of it couldn't be home brew. ROFL! And no, I wasn't trying to trick you; only one of the solutions I know of to get those drive letters you want is of my own doing. The others (except for one) are freeware written by other people. Sometimes, an entire team of programmers. Btw, I did try to get the app on google play; for reason(s) unknown and not clearly explained to me, it wasn't approved. It contains no adware, spyware, nothing of the sort, but, wasn't allowed. Maybe I violated some rule with the way in which I got access to the device? Like I said, google wasn't forthcoming with any real explanation. Is there a specific reason you're responding to my replies but addressing Bill rather than me? And why do you still refer to me as a noob when it's clear as day that you're the only n00b in the thread? -- To prevent yourself from being a victim of cyber stalking, it's highly recommended you visit here: https://tekrider.net/pages/david-brooks-stalker.php =================================================== If you consider television dangerous but routinely carry explosives in your clothing, you may be a Muslim.
[toc] | [prev] | [next] | [standalone]
| From | Arlen_Holder <a%rle%20nh.older@no.spam.net> |
|---|---|
| Date | 2018-11-02 22:01 +0000 |
| Message-ID | <prihg6$fq7$1@news.mixmin.net> |
| In reply to | #57040 |
On Fri, 2 Nov 2018 08:03:33 -0000 (UTC), Diesel wrote:
> Btw, I did try to get the app on google play; for reason(s) unknown
> and not clearly explained to me, it wasn't approved. It contains no
> adware, spyware, nothing of the sort, but, wasn't allowed. Maybe I
> violated some rule with the way in which I got access to the device?
> Like I said, google wasn't forthcoming with any real explanation.
Hi Diesel,
What is the trick to get Android Studio to _use_ the MS Android Emulator?
Thanks for your helpful advice, Diesel, where I'll return the favor by
letting folks know that _before_ they install the Android Studio IDE,
they need to consider whether they're on an Intel or AMD CPU.
o If they're on Intel, the HAXM emulation will likely work for them
o If they're on AMD, the HAXM defaults will prevent emulation from working
If they are on an Intel CPU, these two URLs will help them out:
o Installation instructions for installing HAXM on Windows
o <https://github.com/intel/haxm/wiki/Installation-Instructions-on-Windows>
o Download software for Intel Hardware Accelerated Execution Manager
o <https://software.intel.com/en-us/articles/intel-hardware-accelerated-execution-manager-intel-haxm>
If they're on AMD, like I am, there are AVD decisions to be made, where I
suggest that they not check the AVD box when installing Android Studio:
o [x]Android Studio
o [_]Android Virtual Device
Where I suggest they install an AMD-compatible Android emulator separately.
===========================================================================The Android emulator "booted" up, standalone, on Windows with the AMD CPU!
<http://www.bild.me/bild.php?file…62677amd_emulation_05.jpg>
===========================================================================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?*
<http://www.bild.me/bild.php?file799337amd_emulation_01.jpg>
<http://www.bild.me/bild.php?fileP17616amd_emulation_02.jpg>
<http://www.bild.me/bild.php?file†15530amd_emulation_03.jpg>
<http://www.bild.me/bild.php?file™50110amd_emulation_04.jpg>
<http://www.bild.me/bild.php?file…62677amd_emulation_05.jpg>
===========================================================================AMD owners can use the Microsoft Visual Studio Emulator for Android stub:
o <https://visualstudio.microsoft.com/vs/msft-android-emulator/>
Microsoft documentation (from 2014) is here:
o Introducing Visual Studio¢s Emulator for Android
o <https://blogs.msdn.microsoft.com/devops/2014/11/12/introducing-visual-studios-emulator-for-android/>
Which says, about Hyper-V...
o Conflict with Hyper-V on Windows.
o Many emulators require you to disable Hyper-V
o Or they don¢t work as well with Hyper-V as they do without Hyper-V
o Using Hyper-V is part of the setup for many developer activities
o Restarting (multiple times a day) to toggle Hyper-V is not acceptable
It says, about ADB...
o The emulator is ADB-connected
o So it also works well with your Android Studio projects
o See: Using Visual Studio Emulator for Android from Android Studio
o <https://blogs.msdn.microsoft.com/devops/2015/07/20/using-the-visual-studio-emulator-for-android-from-android-studio-or-eclipse-with-adt/>
o Which says:
o We¢ve 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 ...
===========================================================================The MS stub is extremely dumb, in that it doesn't ask where to be put. :(
You know you will have problems the moment you see programs _this_ dumb!
The stupid MS program installer is so utterly dumb that there was no indication
whatsoever _where_ it put itself, but rooting around found changes inside:
o C:\ProgramData\Package Cache (234MB in 17 directories)
o C:\Program Files (x86)\Microsoft Visual Studio Emulator for Android (183 MB)
o C:\Program Files (x86)\Microsoft Emulator Manager (1MB)
o C:\Program Files (x86)\Microsoft XDE (30MB)
I hate when stupid programs pollute the nice clean neighborhood like this
where they defy any attempt to control them (like a pack of rabid dogs).
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!
===========================================================================When installing, the stub will download from the net
Microsoft Visual Studio Emulator for Android API 19 Platform
===========================================================================There is documentation on setting up the Hyper-V on Windows 10:
o <https://blogs.msdn.com/b/visualstudioalm/archive/2014/11/12/introducing-visual-studio-s-emulator-for-android.aspx>
===========================================================================At this point, I wiped out Android Studio, & all user settings, & started over.
(This has to be the 20th time I've had to wipe out Android Studio. Sigh.)
o First I installed the Microsoft Visual Studio Editor for Android
o Then I installed Android Studio sans the AVD option checked
o Android Studio went into C:\app\editor\android\studio\.
===========================================================================There were no projects in C:\tmp\android (since I wiped them out).
So in the Android Studio version 3.2.1 GUI at the bottom left, I made
this one setting change (which is unrelated to the AVD setup):
o Configure > Project defaults > Settings > Auto Import >
o [x]Add unambiguous imports on the fly
o [x]Optimize imports on the fly (for current project)
===========================================================================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/>
===========================================================================This is related to the AVD setup:
o Configure > Project Defaults > Run Configurations > Defaults >
Android App > General > Depoloyment Target Options >
Open Select Deployment Target Dialog
[x]Use same device for future launches
This will prompt you to select an ADB-connected device when you debug the
first time, then remember that device for subsequent debugging sessions.
===========================================================================This is related to the AVD setup:
o C:\Users\x\Desktop>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
===========================================================================o Configure > Settings > Tools > External Tools > (click the green "+" sign)
Name: MS Android Emulator Group: External Tools
Description: Quick Launch 4.4 XXHDPI Phone
Tool Settings:
Program: C:\Program Files (x86)\Microsoft Emulator Manager\1.0\emulatorcmd.exe
Arguments: /sku:Android launch /id:363F7AED-462C-46BD-9FEC-F1DD3B79916C
Working directory: C:\Program Files (x86)\Microsoft Emulator Manager\1.0
Show in: [x]Main menu [x]Editor menu [x]Project views [x]Search result
Advanced Options
[x]Synchronize files after execution
[x]Open console for tool output
[_]Make console active on message in stdout
[_]Make console active on message in stderr
===========================================================================At this point I wanted to customize the menus to add it, but I needed to
"Create an Android Project" first, I guess, in order to get the main toolbar.
Start a new Android Project >
o Application name: My Application (change to: app00)
o Company domain: ap00.com (notice the single "p")
o Project location: c:\tmp\android\app00
Hmmm.... the Microsoft Android emulator didn't work...
===========================================================================After pressing "Run", I get this in the Android Studio IDE:
Select Deployment Target > Connected Devices > LGTP45071afb6a4
[UNAUTHORIZED - Press OK in the 'Allow USB Debugging' dialog on your device.]
On the phone, it says:
Allow USB Debugging?
The computer's RSA key fingerprint is:
AF:F9:F4:2B:BB:45:A3:4F:BC:AF:D3:BF:DD:5E:22:AA
[_]Always allow from this computer
[Cancel][OK]
===========================================================================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.
===========================================================================At some point, I tried the following...
Android Studio: Tools > AVD Manager > Create Virtual Device >
Category > Phone > Import Hardware Profiles > Select path:
C:\Program Files (x86)\Microsoft Visual Studio Emulator for Android\1.0\Default\Devices\5_KitKat_(4.4)_XXHDPI_Phone.cfg
OK
The only "Select a system image" that works is "Pie".
But that failed miserably ... (same emulation error as always).
Sigh.
===========================================================================Then, I tried the following...
Android Studio: Tools > External Tools > MS Android Emulator
That put a Run windows on the bottom, saying:
"C:\Program Files (x86)\Microsoft Emulator Manager\1.0\emulatorcmd.exe" /sku:Android launch /id:363F7AED-462C-46BD-9FEC-F1DD3B79916C
Validating emulator arguments...
Determining if emulator is already running...
Preparing virtual machine...
You were previously added to the Hyper-V Administrators security group, but the permissions have not taken effect. Please sign out of your computer for the permissions to take effect.
Process finished with exit code 5
===========================================================================Hmmm.... OK. I guess I'll sign out of Windows and sign back in I guess.
I didn't exit out of Android Studio before signing out so I restarted
Android Studio when I signed back into Windows.
===========================================================================Android Studio: Tools > External Tools > MS Android Emulator
That put a Run windows on the bottom, saying:
"C:\Program Files (x86)\Microsoft Emulator Manager\1.0\emulatorcmd.exe" /sku:Android launch /id:363F7AED-462C-46BD-9FEC-F1DD3B79916C
Validating emulator arguments...
Determining if emulator is already running...
Preparing virtual machine...
Up pops a dialog:
Visual Studio Emulator for Android
Click "Retry" to run the emulator in elevated mode.
You do not have permission to modify internal Hyper-V network adapter
settings, which are required to run the emulator.
[Retry][Close]
I hit the "Run" at the very bottom left of Android Studio
(which I had never seen or hit before)
Woo hoo!
The Android emulator "booted" up, standalone, on Windows with the AMD CPU!
<http://www.bild.me/bild.php?file…62677amd_emulation_05.jpg>
===========================================================================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?*
<http://www.bild.me/bild.php?file799337amd_emulation_01.jpg>
<http://www.bild.me/bild.php?fileP17616amd_emulation_02.jpg>
<http://www.bild.me/bild.php?file†15530amd_emulation_03.jpg>
<http://www.bild.me/bild.php?file™50110amd_emulation_04.jpg>
<http://www.bild.me/bild.php?file…62677amd_emulation_05.jpg>
===========================================================================Diesel,
Do you know the trick to get Android Studio to _use_ that MS Android Emulator?
[toc] | [prev] | [next] | [standalone]
| From | Diesel <me@privacy.net> |
|---|---|
| Date | 2018-11-03 02:00 +0000 |
| Message-ID | <XnsA98EE20208E07HT1@5t05cEN5k6D.R80GNo8TET> |
| In reply to | #57067 |
Arlen_Holder <a%rle%20nh.older@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. -- To prevent yourself from being a victim of cyber stalking, it's highly recommended you visit here: https://tekrider.net/pages/david-brooks-stalker.php =================================================== 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).
[toc] | [prev] | [next] | [standalone]
| From | Arlen_Holder <a%rle%20nh.older@no.spam.net> |
|---|---|
| Date | 2018-11-04 06:56 +0000 |
| Message-ID | <prm56r$plp$1@news.mixmin.net> |
| In reply to | #57073 |
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:
o I can pop up the Microsoft Android Emulator from Android Studio 3.2.1
o But Android Studio 3.2.1 "adb" will not send the java file to the 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
BEFORE:
PATH=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.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\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files (x86)\Microsoft Emulator Manager\1.0\;C:\Users\[user]\AppData\Local\Microsoft\WindowsApps;c:\app\hardware\android\sdk\platform-tools;c:\app\hardware\android\sdk\platform-tools;
[toc] | [prev] | [next] | [standalone]
| From | Arlen_Holder <a%rle%20nh.older@no.spam.net> |
|---|---|
| Date | 2018-11-04 07:50 +0000 |
| Message-ID | <prm8c7$vfq$1@news.mixmin.net> |
| In reply to | #57117 |
On Sun, 4 Nov 2018 06:56:28 -0000 (UTC), Arlen_Holder wrote: > I made no progress, where the current status is the same as before: > o I can pop up the Microsoft Android Emulator from Android Studio 3.2.1 > o But Android Studio 3.2.1 "adb" will not send the java file to the emulator 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>
[toc] | [prev] | [next] | [standalone]
Page 1 of 7 [1] 2 3 4 5 6 7 Next page →
Back to top | Article view | comp.mobile.android
csiph-web