I am trying to run the demo project by skobbler, however the app crashes the moment it starts. It runs the SplashActivity.java file which has the code to initialize the map. This is the output from on the run terminal:
Split APKs installed
$ adb shell am start -n "com.skobbler.sdkdemo/com.skobbler.sdkdemo.activity.SplashActivity" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER
Client not ready yet..Connected to process 20422 on device Pixel_API_25 [emulator-5554]
Application terminated.
I am not able to figure out what's causing the app to crash. Is anyone facing similar issue?
Android intel emulator supports openGL now
Here you can choose which GL interface you want to use on your emulator.
On macOS you can see some information about the openGL running on the emulator. Once you have downloaded the additional tools for xcode.
For some more information about emulator hardware acceleration here.
There use to be some problems running skobbler in emulator. Try on a physical device.
Related
The image describes my current situation properly. Please have a look at it first.
I am running my app on React Native. I have Android simulator on. I give the command to start the app. The app build finishes, but it says that virtual device not found, and in my simulator, if I open the app manually, it says that it cannot connect to Development server. It shows some issues.
Can anyone help?
Try run react-native run-android to connect your app to the emulator
Check USB Debugging is on(mostly running on virtual devices)
Check how you created project(react-native-cli or Expo) and run relevant app run command
Make sure your development server(node.js) is running when you run app. Sometimes it crashes then you have to again run command to run app
If all the step does not solve your issue try to uninstall app from device and run app again. Since react-native is still developing and its wired sometime these tricks works
I was having the same issue in Ubuntu 16.04. In my case the problem was that node packager wasn't running.
To check is packager is running easily you can open the browser and enter
http://localhost:8081/
You must see "React Native packager is running."
If you dont, then you can start packager from console running
react-native start
If you get an error like
" ERROR watch /your/project/path/android/app/build/intermediates/incremental/mergeDebugResources/merged.dir/values-ru ENOSPC"
Then run first
echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
Then run react-native start again and press the letter R twice in the emulator to reload.
Looking at the screenshot, seems like you don't have adb installed because there is a clear 'adb: not found error'.
Luckily Android studio ships with adb and is present in platform-tools under your Android SDK. (generally in /home/your-user-name/Android/Sdk/)
You only need to use it. Create a symbolic link in '/usr/bin/' or '/usr/local/bin/' depending how you'd like to use it.
Run the command:
sudo ln -s ~/Android/Sdk/platform-tools/adb /usr/local/bin/
After this run the app.
So I am trying to install an app called Live2d wallpaper on my android, and I can run the app to get it to install on an emulator, but when I try to run it on my android version 7.0 on my samsung galaxy s8+, I get this error:
09/17 14:35:31: Launching Live 2d wallpaper
$ adb push C:\Users\Levi\Desktop\Live2D_SDK_Android_2.0.06_1_en\out\production\liveWallpaper\liveWallpaper.apk /data/local/tmp/jp.live2d.sample
$ adb shell pm install -r "/data/local/tmp/jp.live2d.sample"
Success
Client not ready yet..
I'm new to this kind of thing, but I would appreciate any kind of help. I've already set developer options on and also turned on usb debugging, but I don't know what else to do.
I recently (2 days ago) updated my Android Studio to version 2.0.
After having troubles with my previously working application on a real device, I had to activate MultiDex to remove errors in the logcat...
All is working fine now, as it was before the update.
But when I try to launch my application in the emulator from Android Studio (which was working before the update) I face a strange error without any explanation (this is from the Android Studio "4: Run" tab):
04/13 13:20:40: Launching app
No apk changes detected since last installation, skipping installation of /.../app/build/outputs/apk/app-debug.apk
$ adb shell am force-stop com.android.test
$ adb shell am start -n "com.android.test/com.android.test.MainActivity" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER
Unexpected error while executing: am start -n "com.android.test/com.android.test.MainActivity" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER
Error while Launching activity
(I replaced the entire location by /.../ in the above lines as this is not relevant to the problem...)
The strange fact is the application works perfectly well on the AVD if launched manually (by clicking on the application icon on the virtual device)!
Now if you guys have an idea of what is happening and how to get rid of it, it would be nice.
PS: I tried removing the MultiDex, nothing changed, facing same issue...
The new "instant run" feature is a bit buggy still, delete the app manually on your virtual device and run the code again.
Sorry for write on outdated post , but i had same problem. I was using AVD with arm processor image and received this same message.
The only way for me to make Android Studio 2.1.2 runs the app with instant run was change to a X86 processor image.
I used ant to build my Eclipse project from the command line in a debug configuration. (Eclipse Luna and Android NDK-R10d is broken, so I can't use Eclipse any longer. Confer, Eclipse/ADT plugin cannot locate symbols for r10d NDK).
I then performed an install using adb:
<Project Directory>$ adb install bin/AndroidPrng-debug.apk
When I rummage for the program on the device in Apps, the program is not offered. When I attempt to search for it by name on the device (AndroidPrng and com.example.prng), I'm provided with useless web search results. When I go to Settings → Apps, the app is shown under the Downloaded tab (it shows the name as com.example.prng). It has the familiar Force Stop and Uninstall.
I have DDMS running and waiting to capture LogCat output from the program. But even though the app is on the device, I cannot figure out how to run it.
How do I run and debug the app when it does not show up under Apps?
Assuming that your app do have an Activity from where you can navigate into other parts of your app.
Try using below command:
$ adb shell am start -n com.example.yourpackagename/.YourMainActivity
or $ adb shell am start -n com.package.yourpackagename/com.example.yourpackagename.YourMainActivity
This am start command, is a command-line interface to the ActivityManager.
I have a android application that connects/send/receive to/from a server as part of its operation.
my final goal is to run this application on a number of android emulators on a remote machine(to save some computing resources on my laptop).
I SSHed to the remote machine and created the emulators remotely using android create avd -n AVD_xxx -t 1 .
I tried to run the emulators using emulator-arm -avd AVD_1 but it gave error that looks obvious : SDL init failure, reason is: No available video device
(if I run the command one the michine directly, it will run just fine)
I will appreciate if you help me solve this issue.
Note:
I don't need video provisions. is it possible to disable that by configuring AVD? this is just an example. you might have better solutions.
There are two options:
export $DISPLAY and show the emulator on some X display (tunneled or remotely existing)
run emulator -no-window [-no-audio] to start it without the need of a X display