I changed graphics to software, now it shows the phone but the screen remains black and the phone won't start. However, I still cannot get the app running on an ADV.
So why doesn't it work on Debian Testing now? Did I forget something?ĮDIT: I am now able to use my phone to run the android application by using USB 2.0 instead of USB 3.0! Is that a normal behavior since it works with native adb? I mean, if I buy a new PC after some years which has got only USB 3.0 ports, will I not be able to use phone debugging with Android Studio or is this just an issue? It is still known since 2014 ( ). I remember that I was able to run it on LMDE2 some time ago. I really would like to get it running on Debian because I do not want to install Windows for this. I have never experienced anything close to this on other systems. I tried to do it until now and couldn't find a solution. Today I managed to have the emulator start by setting graphics to software but it just shows a black screen and doesn't power on. reinstalled everything: JDK, Android SDK and Android Studio.installed all the SDK-platforms since Android 4.3 and Android.Android Studio recognizes my phone properly.
My device is a Samsung Galaxy S3 with LineageOS (Android 7.1.2) and root permissions. The same happens when I try to start it in an emulator (gets stuck on 'Waiting for target device to come online'). However, if I try to do it with Android Studio, it gets stuck on 'Installing APKs'. With adb I can install it without having any problems. I wanted to run a HelloWorld application (just a blank activity) but weren't able to run it. Yesterday I downloaded Android Studio for my Debian Testing system.
INFO Start installing (golang) with apt-getįailed to check emulator boot status, error: error: device 'emulator-5554' not found - exit status 1Īll I want is to start the emulator and then run a. When this occurs, the build never finishes and I have to actually abort the build instead of it just failing… I saw in this forum a suggestion to change the AVD Manager back to version 0.9.1, so I did, but I get a different error: +-+ com/bitrise-steplib/steps-wait-for-android-emulator/issues | INFO * Step dependency (go) installed, available.įailed to check emulator boot status, error: * daemon not running starting now at tcp:5037
When the AVD Manager step is at the latest version (0.9.2), the AVD Manager step says it runs fine and started the emulator, but on the Wait for Android emulator step it fails: INFO Start installing (golang) with apt-get I am attempting to use the AVD Manager and Wait for Android emulator steps in order to run connectedAndroidTest via the Gradle Runner step, but keep getting weird errors on the Wait for Android Emulator step.
0 kommentar(er)
