Some of you may know that we have been hard at work on an update to our very-outdated built-in Windows emulator for quite a while. We now have something we're ready to release in Open Beta. This new emulator is running SDK 30, i.e. Android R(ed Velvet Cake).
Keep in mind: we're a small team, and we can only test a few platforms. It's still likely that some people will run into issues, especially those running Windows 7. Windows 7 specific troubleshooting information is at the bottom of this post.
If you have problems, please report them on our issue form: [REMOVED]
System requirements:
Intel machines
64-bit
Windows 7 and up
We expect to make a 32-bit version available in the future. We're also looking at our options for non-Intel machines.
Known Issues:
The new emulator installs two supplemental apps: C++ redistributable and Hardware Accelerated Execution Manager (HAXM). You will see a pop-up notification for C++, but you don't need to do anything. For HAXM, you will need to click through the installer. This is expected behavior.
The first run of the emulator may take significant time. This is only for the first run, while the emulator sets itself up. Please be patient and know that future runs will be faster.
You may see a notification "Waiting 20 seconds" that lasts a lot longer than 20 seconds while the aiStarter window scrolls a long list of eChecks. This is a minor issue on our end that will be resolved in the final release.
Without further ado here is the link to the new installer: [REMOVED]
Issues specific to Windows 7:
Windows 7 is out of its support window, and providing updated emulator support has been challenging. Support for this operating system is very much a work-in-progress. If you are running Windows 7, we want to hear from you whether the emulator works or not. Success stories are just as important for us as problems.
If the HAXM installer reports that it's already installed, as shown below, you may click Yes or No. Either one should be fine.
If you see a pop-up asking to wait for installer, shown below, you will need to click cancel.
We are still investigating this issue and haven't determined the exact cause. If you see this popup and attempted to cancel, the emulator may freeze instead of continuing to load. If you see this popup, whether it continues to load after canceling, please let us know.
When the installation happened, did you get any errors during the Visual C++ Redistributable Package installer? This is Microsoft software needed for aiStarter to work correctly. Also, are you up-to-date with Windows Updates? You will need SP1 at a minimum.
Actually, looking at your screenshot it shows 30.262.0. The version that we are testing is 30.263.0, which uses an older version of Python. The 30.262.0 used Python 3.9, which does not support Windows 7. This newer one uses Python 3.6, which does support Windows 7.
Did the emulator ultimately shut down? I do see "Saving state on exit" so that suggests it should be fine. The other messages are mostly noise but unfortunately there's no easy way for us to print some but not others.
I notice the Companion in this emulator image is version 2.63 and it did not notice it was behind the ai2 server (2.64u).
Also, there was no response in the emulator to use of the ai2 Help->Update Companion pulldown.
I was, however, able to use the emulator's drag and drop facility to take the freshest downloaded Companion .apk file and drag it onto the emulated phone's home screen for an install over the 2.63 version.
Here aer my command line window logs for tonight, if they help ...
App Inventor version: 30.263.0
Architecture: AMD64
AppInventor tools located here: C:\Program Files\MIT App Inventor
ADB path: C:\Program Files\MIT App Inventor\from-Android-SDK\platform-tools\adb
Bottle v0.12.13 server starting up (using WSGIRefServer())...
Listening on http://127.0.0.1:8004/
Hit Ctrl-C to quit.
127.0.0.1 - - [03/Sep/2022 21:58:28] "GET /ping/ HTTP/1.1" 200 39
127.0.0.1 - - [03/Sep/2022 21:58:30] "GET /echeck/ HTTP/1.1" 200 39
127.0.0.1 - - [03/Sep/2022 21:58:30] "GET /echeck/ HTTP/1.1" 200 39
AVD exists. Starting emulator...
127.0.0.1 - - [03/Sep/2022 21:58:30] "GET /start/ HTTP/1.1" 200 0
emulator: Android emulator version 30.3.5.0 (build_id 7033400) (CL:N/A)
127.0.0.1 - - [03/Sep/2022 21:58:31] "GET /echeck/ HTTP/1.1" 200 39
handleCpuAcceleration: feature check for hvf
127.0.0.1 - - [03/Sep/2022 21:58:32] "GET /echeck/ HTTP/1.1" 200 39
added library vulkan-1.dll
Failed to open /qemu.conf, err: 2
HAX is working and emulator runs in fast virt mode.
127.0.0.1 - - [03/Sep/2022 21:58:33] "GET /echeck/ HTTP/1.1" 200 39
emulator: INFO: GrpcServices.cpp:288: Started GRPC server at 127.0.0.1:8554, sec
urity: Local
Your emulator is out of date, please update by launching Android Studio:
- Start Android Studio
- Select menu "Tools > Android > SDK Manager"
- Click "SDK Tools" tab
- Check "Android Emulator" checkbox
- Click "OK"
127.0.0.1 - - [03/Sep/2022 21:58:34] "GET /echeck/ HTTP/1.1" 200 39
127.0.0.1 - - [03/Sep/2022 21:58:35] "GET /echeck/ HTTP/1.1" 200 39
127.0.0.1 - - [03/Sep/2022 21:58:36] "GET /echeck/ HTTP/1.1" 200 39
127.0.0.1 - - [03/Sep/2022 21:58:37] "GET /echeck/ HTTP/1.1" 200 39
127.0.0.1 - - [03/Sep/2022 21:58:38] "GET /echeck/ HTTP/1.1" 200 39
127.0.0.1 - - [03/Sep/2022 21:58:39] "GET /echeck/ HTTP/1.1" 200 39
127.0.0.1 - - [03/Sep/2022 21:58:40] "GET /echeck/ HTTP/1.1" 200 39
127.0.0.1 - - [03/Sep/2022 21:58:41] "GET /echeck/ HTTP/1.1" 200 39
127.0.0.1 - - [03/Sep/2022 21:58:42] "GET /echeck/ HTTP/1.1" 200 39
127.0.0.1 - - [03/Sep/2022 21:58:43] "GET /echeck/ HTTP/1.1" 200 39
127.0.0.1 - - [03/Sep/2022 21:58:44] "GET /echeck/ HTTP/1.1" 200 39
127.0.0.1 - - [03/Sep/2022 21:58:45] "GET /echeck/ HTTP/1.1" 200 39
Found emulator at emulator-5554
Found companion version 13026300
127.0.0.1 - - [03/Sep/2022 21:58:47] "GET /echeck/ HTTP/1.1" 200 66
Found emulator at emulator-5554
Found companion version 13026300
127.0.0.1 - - [03/Sep/2022 21:58:47] "GET /echeck/ HTTP/1.1" 200 66
Device = emulator-5554
Warning: Activity not started, intent has been delivered to currently running to
p-most instance.
127.0.0.1 - - [03/Sep/2022 21:59:09] "GET /replstart/emulator-5554 HTTP/1.1" 200
0
emulator: INFO: QtLogger.cpp:68: Critical: Failed to load https://maps.googleapi
s.com/maps/api/mapsjs/gen_204?csp_test=true: The 'Access-Control-Allow-Origin' h
eader has a value 'qrc://' that is not equal to the supplied origin. Origin 'qrc
://' is therefore not allowed access. (qrc:/html/js/location-mock-web-channel.js
:0, (null))
emulator: INFO: QtLogger.cpp:68: Critical: Failed to load https://maps.googleapi
s.com/maps/api/mapsjs/gen_204?csp_test=true: The 'Access-Control-Allow-Origin' h
eader has a value 'qrc://' that is not equal to the supplied origin. Origin 'qrc
://' is therefore not allowed access. (qrc:/html/js/location-mock-web-channel.js
:0, (null))
C:\Program Files\MIT App Inventor\from-Android-SDK\emulator\qemu\windows-x86_64\
qemu-system-x86_64.exe: icmpv6 ICMP6_ECHO_REQUEST failed
C:\Program Files\MIT App Inventor\from-Android-SDK\emulator\qemu\windows-x86_64\
qemu-system-x86_64.exe: icmpv6 ICMP6_ECHO_REQUEST failed
C:\Program Files\MIT App Inventor\from-Android-SDK\emulator\qemu\windows-x86_64\
qemu-system-x86_64.exe: icmpv6 ICMP6_ECHO_REQUEST failed
C:\Program Files\MIT App Inventor\from-Android-SDK\emulator\qemu\windows-x86_64\
qemu-system-x86_64.exe: icmpv6 ICMP6_ECHO_REQUEST failed
C:\Program Files\MIT App Inventor\from-Android-SDK\emulator\qemu\windows-x86_64\
qemu-system-x86_64.exe: icmpv6 ICMP6_ECHO_REQUEST failed
C:\Program Files\MIT App Inventor\from-Android-SDK\emulator\qemu\windows-x86_64\
qemu-system-x86_64.exe: icmpv6 ICMP6_ECHO_REQUEST failed
C:\Program Files\MIT App Inventor\from-Android-SDK\emulator\qemu\windows-x86_64\
qemu-system-x86_64.exe: icmpv6 ICMP6_ECHO_REQUEST failed
C:\Program Files\MIT App Inventor\from-Android-SDK\emulator\qemu\windows-x86_64\
qemu-system-x86_64.exe: icmpv6 ICMP6_ECHO_REQUEST failed
C:\Program Files\MIT App Inventor\from-Android-SDK\emulator\qemu\windows-x86_64\
qemu-system-x86_64.exe: icmpv6 ICMP6_ECHO_REQUEST failed
C:\Program Files\MIT App Inventor\from-Android-SDK\emulator\qemu\windows-x86_64\
qemu-system-x86_64.exe: icmpv6 ICMP6_ECHO_REQUEST failed
C:\Program Files\MIT App Inventor\from-Android-SDK\emulator\qemu\windows-x86_64\
qemu-system-x86_64.exe: icmpv6 ICMP6_ECHO_REQUEST failed
C:\Program Files\MIT App Inventor\from-Android-SDK\emulator\qemu\windows-x86_64\
qemu-system-x86_64.exe: icmpv6 ICMP6_ECHO_REQUEST failed
C:\Program Files\MIT App Inventor\from-Android-SDK\emulator\qemu\windows-x86_64\
qemu-system-x86_64.exe: icmpv6 ICMP6_ECHO_REQUEST failed
C:\Program Files\MIT App Inventor\from-Android-SDK\emulator\qemu\windows-x86_64\
qemu-system-x86_64.exe: icmpv6 ICMP6_ECHO_REQUEST failed
C:\Program Files\MIT App Inventor\from-Android-SDK\emulator\qemu\windows-x86_64\
qemu-system-x86_64.exe: icmpv6 ICMP6_ECHO_REQUEST failed
C:\Program Files\MIT App Inventor\from-Android-SDK\emulator\qemu\windows-x86_64\
qemu-system-x86_64.exe: icmpv6 ICMP6_ECHO_REQUEST failed
C:\Program Files\MIT App Inventor\from-Android-SDK\emulator\qemu\windows-x86_64\
qemu-system-x86_64.exe: icmpv6 ICMP6_ECHO_REQUEST failed
C:\Program Files\MIT App Inventor\from-Android-SDK\emulator\qemu\windows-x86_64\
qemu-system-x86_64.exe: icmpv6 ICMP6_ECHO_REQUEST failed
C:\Program Files\MIT App Inventor\from-Android-SDK\emulator\qemu\windows-x86_64\
qemu-system-x86_64.exe: icmpv6 ICMP6_ECHO_REQUEST failed
C:\Program Files\MIT App Inventor\from-Android-SDK\emulator\qemu\windows-x86_64\
qemu-system-x86_64.exe: icmpv6 ICMP6_ECHO_REQUEST failed
C:\Program Files\MIT App Inventor\from-Android-SDK\emulator\qemu\windows-x86_64\
qemu-system-x86_64.exe: icmpv6 ICMP6_ECHO_REQUEST failed
C:\Program Files\MIT App Inventor\from-Android-SDK\emulator\qemu\windows-x86_64\
qemu-system-x86_64.exe: icmpv6 ICMP6_ECHO_REQUEST failed
C:\Program Files\MIT App Inventor\from-Android-SDK\emulator\qemu\windows-x86_64\
qemu-system-x86_64.exe: icmpv6 ICMP6_ECHO_REQUEST failed
C:\Program Files\MIT App Inventor\from-Android-SDK\emulator\qemu\windows-x86_64\
qemu-system-x86_64.exe: icmpv6 ICMP6_ECHO_REQUEST failed
C:\Program Files\MIT App Inventor\from-Android-SDK\emulator\qemu\windows-x86_64\
qemu-system-x86_64.exe: icmpv6 ICMP6_ECHO_REQUEST failed
C:\Program Files\MIT App Inventor\from-Android-SDK\emulator\qemu\windows-x86_64\
qemu-system-x86_64.exe: icmpv6 ICMP6_ECHO_REQUEST failed
C:\Program Files\MIT App Inventor\from-Android-SDK\emulator\qemu\windows-x86_64\
qemu-system-x86_64.exe: icmpv6 ICMP6_ECHO_REQUEST failed
C:\Program Files\MIT App Inventor\from-Android-SDK\emulator\qemu\windows-x86_64\
qemu-system-x86_64.exe: icmpv6 ICMP6_ECHO_REQUEST failed
C:\Program Files\MIT App Inventor\from-Android-SDK\emulator\qemu\windows-x86_64\
qemu-system-x86_64.exe: icmpv6 ICMP6_ECHO_REQUEST failed
C:\Program Files\MIT App Inventor\from-Android-SDK\emulator\qemu\windows-x86_64\
qemu-system-x86_64.exe: icmpv6 ICMP6_ECHO_REQUEST failed
ERROR: The process with PID 5392 (child process of PID 7148) could not be termin
ated.
Reason: This process can only be terminated forcefully (with /F option).
ERROR: The process with PID 7436 (child process of PID 7148) could not be termin
ated.
Reason: This process can only be terminated forcefully (with /F option).
ERROR: The process with PID 7148 (child process of PID 6988) could not be termin
ated.
Reason: One or more child processes of this process were still running.
ERROR: The process "emulator.exe" with PID 6988 could not be terminated.
Reason: This process can only be terminated forcefully (with /F option).
Killed emulator
Killed adb
127.0.0.1 - - [03/Sep/2022 22:12:14] "GET /reset/ HTTP/1.1" 200 39
127.0.0.1 - - [03/Sep/2022 22:12:24] "GET /ping/ HTTP/1.1" 200 39
127.0.0.1 - - [03/Sep/2022 22:12:26] "GET /echeck/ HTTP/1.1" 200 39
Found emulator at emulator-5554
Found companion version 13026300
127.0.0.1 - - [03/Sep/2022 22:12:26] "GET /echeck/ HTTP/1.1" 200 66
AVD exists. Starting emulator...
127.0.0.1 - - [03/Sep/2022 22:12:26] "GET /start/ HTTP/1.1" 200 0
emulator: Android emulator version 30.3.5.0 (build_id 7033400) (CL:N/A)
emulator: ERROR: Running multiple emulators with the same AVD is an experimental
feature.
Please use -read-only flag to enable this feature.
Device = emulator-5554
127.0.0.1 - - [03/Sep/2022 22:12:48] "GET /replstart/emulator-5554 HTTP/1.1" 200
0
ERROR: The process "emulator64-crash-service.exe" not found.
ERROR: The process with PID 5392 (child process of PID 7148) could not be termin
ated.
Reason: This process can only be terminated forcefully (with /F option).
ERROR: The process with PID 7436 (child process of PID 7148) could not be termin
ated.
Reason: This process can only be terminated forcefully (with /F option).
ERROR: The process with PID 7148 (child process of PID 6988) could not be termin
ated.
Reason: One or more child processes of this process were still running.
ERROR: The process "emulator.exe" with PID 6988 could not be terminated.
Reason: This process can only be terminated forcefully (with /F option).
Killed emulator
Killed adb
127.0.0.1 - - [03/Sep/2022 22:18:50] "GET /reset/ HTTP/1.1" 200 39
127.0.0.1 - - [03/Sep/2022 22:20:02] "GET /ping/ HTTP/1.1" 200 39
127.0.0.1 - - [03/Sep/2022 22:20:04] "GET /echeck/ HTTP/1.1" 200 39
Found emulator at emulator-5554
Found companion version 13026300
127.0.0.1 - - [03/Sep/2022 22:20:04] "GET /echeck/ HTTP/1.1" 200 66
AVD exists. Starting emulator...
127.0.0.1 - - [03/Sep/2022 22:20:04] "GET /start/ HTTP/1.1" 200 0
emulator: Android emulator version 30.3.5.0 (build_id 7033400) (CL:N/A)
emulator: ERROR: Running multiple emulators with the same AVD is an experimental
feature.
Please use -read-only flag to enable this feature.
Device = emulator-5554
Warning: Activity not started, intent has been delivered to currently running to
p-most instance.
127.0.0.1 - - [03/Sep/2022 22:20:25] "GET /replstart/emulator-5554 HTTP/1.1" 200
0
Failed to open C:\Users\ABG\Desktop\Screenshot_1662258179.png, err: 13
Defaulting fps to 24 fps
For future reference, here are two short videos on how to identify the Companion version in the new emulator.
(The aistarter command line window also identifies the version found as an integer.)
Starting the Emulator (leftover app session still in progress in the Companion)
The emulator packge we've published has never shown the textbox for the code. There's a prebaked code used when you connect to the emulator since it's happening on loopback and so we don't need to rendezvous (the IP address is known).
On the test server in question, what happened when you tried Connect > Emulator?
