Howdy, Stranger!
We are about to switch to a new forum software. Until then we have removed the registration on this forum.
Categories
- All Categories 25.7K
- Announcements & Guidelines 13
- Common Questions 30
- Using Processing 22.1K
- Programming Questions 12.2K
- Questions about Code 6.4K
- How To... 4.2K
- Hello Processing 72
- GLSL / Shaders 292
- Library Questions 4K
- Hardware, Integration & Other Languages 2.7K
- Kinect 668
- Arduino 1K
- Raspberry PI 188
- Questions about Modes 2K
- Android Mode 1.3K
- JavaScript Mode 413
- Python Mode 205
- Questions about Tools 100
- Espanol 5
- Developing Processing 548
- Create & Announce Libraries 211
- Create & Announce Modes 19
- Create & Announce Tools 29
- Summer of Code 2018 93
- Rails Girls Summer of Code 2017 3
- Summer of Code 2017 49
- Summer of Code 2016 4
- Summer of Code 2015 40
- Summer of Code 2014 22
- p5.js 1.6K
- p5.js Programming Questions 947
- p5.js Library Questions 315
- p5.js Development Questions 31
- General 1.4K
- Events & Opportunities 288
- General Discussion 365
In this Discussion
- chrios1001 May 2017
- relddir12 May 2017
Emulator simply won't run.
Whenever I try and run an Android script in the emulator, the console pops up with the error: android.util.AndroidException: Can't connect to activity manager; is the system running? I've looked around and tried solutions, such as deleting the AVD processing created and creating a new one, manually starting up the emulator, updating the SDK, but so far nothing has worked. I am using Processing 3 on Windows 10 with the latest version of SDK.
Answers
The emulator takes a long time to boot up. Wait a full 24 hours before giving up.
Here are my tips: Use a real android phone if you have access, it's much much faster - and more likely to actually work.
Use a good usb cable. Keep notes while you get it set up, when everything is running well note down your working settings - It can be really handy if you have to come back to android / processing after a few weeks break and you can't remember which adb / sdk stuff was correct.