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
- calsign June 2014
General Emulator question
Hello, i try to build a first Android app using Processing. Building a simple project and deploy to real device, works ! But i can not run it in Emulator. My question. Should it be possible to emulate a Samsung Galaxy Tab 3 (intel Atom x86) on a 32bit Linux (OpenSuse13.1) using SDK etc. and Processing ? recent error messages seems to be a permission or path problem (?)
-post-build:
debug: adb -s emulator-5566 install -r /tmp/android7882314764269976310sketch/bin/col_p002-debug.apk status: 1 231ms stdout: rm failed for /data/local/tmp/col_p002-debug.apk, No such file or directory stderr: failed to copy '/tmp/android7882314764269976310sketch/bin/col_p002-debug.apk' to '/data/local/tmp/col_p002-debug.apk': No such file or directory Shutting down any existing adb server...>
thx wally
Answers
The emulator should work... but as a general rule, you should test on a device if you can. The emulator is incredibly slow (it can take a couple of minutes to start and it's slow to operate) and it lacks some features that you may want for testing (such as an accelerometer). A physical device, once set up properly, is much easier to test with and closer to the end user experience.
If you still want to get the emulator working (if you want to test when you don't have a device available, for example), then I / we can probably help you... but this is a new error message for me. Perhaps this StackOverflow question will be helpful.