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?