Go through this blog, 11 Using inTEl HARdwARE ACCElERATEd ExECUTion MAnAgER on windows, MAC os, And linUx To sPEEd UP AndRoid on x86 EMUlATion Launch the emulator from. Configure emulator correctly, download the Intel X86 Atom system image for better performance. Make sure you have Intel HAXM & virtualization option enabled in your BIOS. Make sure you have proper SDK installed.Check Android Emulator and hit apply.If you encounter a problem connecting to the emulator, visit the pageNow you can easily use your favorite android game on your Windows and MAC PC. Uncheck Android Emulator and hit apply. Tools > SDK Manager > SDK Tools.
Android Emulator Is Not Starting Mac Version OfIf you eventually file an issue, first search on the forum to see if others have experienced similar problems. The issues are the same for MacOS and we will be publishing a Mac version of this document soon.)Please go through this procedure before filing an issue on the App Inventor forum. (This procedure is for Windows.On the other hand, if the emulator won't start for any of your projects, then continue with the debugging steps here. Please submit an issue and include the project source (aia) file. Things to check firstDoes the problem of the emulator not starting occur with just this project or with all your projects?If the problem is with only this project then there is probably something in the project that is tickling a bug in App Inventor.Similarly, App Inventor will get confused if there is more than one emulator running. The current App Inventor 2 software can handle only a single device and will get confused if more than one device is connected. In that case, try reduced versions of the project that have fewer screens or assets to see how large things before the problem occurs.Is there another device connected to your computer?If there is a phone plugged in, then unplug it. If the Companion tarts up again, asking about a QR code, press the menu key and kill it again. To do this, use the emulator on the computer screen: press the (image of the) menu key, and then the button to kill the app. If App Inventor has trouble communicating with the emulator, it may ask you to restart the Companion. If you are running this or something similar, you'll need to turn it off, or configure it to not block the App Inventor connections.Is App Inventor asking you to restart the companion?Part of the App Inventor software includes the App Inventor Companion app, running on the emulator. The setup software won't find the emulator support if it's in a different location.Is your browser running an extension that blocks connections?An example of an extension that blocks connections is the NoScript extension for Firefox. We don't know why this is, and it might not happen all the time, but we'll keep investigating. In some cases, it can stay that way for as much as several minutes while the emulator program starts up. Restarting the Companion might not solve your problem (there might be another underlying cause) but it is a good first step.When the emulator starts, it first appears as a black screen with the word Android in the middle. The Android emulator program running on your computer. Try to get help if you are not familiar with using the command console.As an overview, running the emulator involves the following This will require using the console commands. Further diagnosis and debuggingIf you've tried everything above, and there are still problems, you'll need to do some diagnosis and debugging. If things break at some point in this startup, you'll need to do some further diagnosis (see below) but the first thing is to wait. Shortly after that, App Inventor should recognize that the emulator has started and start the companion in the emulator, and then load the blocks for your app. Best usb loader for macThe adb (Android Debug Bridge) program running on your computer, which lets the computer control attached Android devices. It manages the connection between the browser and the emulator. The aiStarter program running in your computer. To diagnose this, get out of App Inventor, go to the the Commands for App Inventor directory and run the command run-emulator. This will also prevent the emulator from working. There are also cases where administrative software prevents school computers from running scripts (bat files). It might be that there is a permissions issue in accessing files or directories that keeps the emulator from starting. Whenever you want to use the emulator or the USB cable, you need to make sure that aiStarter is running. It provides communication between App Inventor running in the browser, and other parts of App Inventor. Then kill the emulator program and try App Inventor with starting the emulator as usual.What is aiStarter starter and how do I start it?The aiStarter program is installed on your computer when you install the App Inventor Setup software. (Don't worry if you see a warning about adjusting the partition size - that's normal.) After you've dealt with the problem, try run-emulator again. You should be able to start it by typing aiStarter from a terminal.How can I tell if aiStarter is running correctly?AiStarter is running correctly if the emulator (or USB) connect. On GNU/Linux, this program is in /usr/local/bin. In case aiStarter somehow does need to be started manually on the Mac, find it using Spotlight, use the Finder to go to /Applications/AppInventor/commands-for-App, and double click on aiStarter. On the Mac, aiStarter should start automatically, so Mac users should not have to worry about this. On Windows, there should be a button on your desktop that starts aiStarter. You'll need to find that program and disable it. If the status of the emulator is offline rather than connected, then you might not have waited long enough, or there might be some other program using the emulator port 5554. Disconnect any other devices. The result should show a list of devices:There should be exactly one device: the emulator. Open a console in the Commands to App Inventor directory, and run the program adbrestart and see if that helps.If the emulator is started and has been in the process of starting up for a while (and is past the completely black screen), run the command adb devices in a console window. For a blocked port, check whether there is another program on the computer that is using the port.The adb program can sometime get confused, especially if there are other issues. If you need help, file and issue and include the program source (aia file).My app runs on the emulator, but images do not appear. Check your program in the designer and blocks editor. If this doesn't work, then check if adb is running, as described above).Is the emulator hanging waiting to load blocks?If the emulator had gotten through the entire startup sequence, started loading your app and hangs waiting for blocks, then there might be a bug in your program that is preventing the blocks form being loaded. The first thing to try here is to reinstall the AI setup software as described here: How to update the App Inventor Software.
0 Comments
Leave a Reply. |
AuthorBrandon ArchivesCategories |