I installed virtual android in genymotion, but after installing the phone, I press start and the phone screen comes up and suddenly turns off.
Related
So I am running Android Studio 3.3 on my Mac that's running High Sierra v. 10.13.4. My code compiles fine and runs on the emulator, but when I try to plug in my 2 Samsung Tab A's that I'm working with, Android Studio throws this error during the build:
java.io.IOException: Broken pipe
Error while Installing APK
Device samsung-sm_t580-5203b3db5aa1b4cfdisconnected, monitoring stopped.`
I've looked around and other people have suggested killing all ADB processes and restarting which I did. I've also restarted my Android Studio and my computer and the tablet. And it seems that the Android studio can find the tablet as it pops up on the ADB device listing, but just can't connect to it. I also saw something about Eclipse and Android studio running concurrently and causing issues, but I don't have Eclipse running so it can't be that either. However, when I tried my roommate's Android phone (Pixel XL 2), that works fine and the code builds and runs on the phone.
So at this point I'm a little baffled at why I'm having this issue. Any thoughts or suggestions would be awesome!
Every time I try to launch an AVD in Android Studio 3.0, it crashes my entire laptop. I'm on MacOS 10.13 (High Sierra), and the crash happens when qemu launches (it never gets close to actually emulating a device). I have deleted all existing AVD devices, uninstalled and reinstalled Android Studio, the emulator (and HAXM), and even used homebrew to install qemu separately (to see if there was a different version that would NOT crash).
I have no idea where else to look or what else to do... I can run my app successfully on my phone that is connected, but just can't use the emulators at all.
Anyone have any ideas?
I am using Macbook Pro 2015. I installed Xamarin Studio and Android SDK
I created AVD like this
When I start my AVD, it never moves further than screen showing "android" on it, even 1/2 hour after starting it
adb devices command shows:
adb devices
List of devices attached
emulator-5554 device
Is there something I am doing wrong in setting my emulator. I am aware that android emulators are slow but it wasn't this slow. I am also aware of HAXM but I found instruction to install them bit to flaky and I dont want to take a risk. I also know about Genimotion but that is not an option for me.
Is there another way to speed up the android emulator?
I had the same problem and I used an alternative solution to fix this problem.
Install VMware or VirtualBox
Download the ISO file of your android platform http://www.android-x86.org/download
Create a virtual machine with the ISO file
You can use these settings:
Target OS: Choose Linux
Target Os version: Other
1 GB RAM
Add a new hard drive: VDI drive, dynamically sized
Start the VM
Now you can connect Xamarin to the VM.
Find the path to your Android sdk-platform-tools
Open a terminal in your Host and locate sdk-platform-tools and type ./adb connect
Now you can run your code from Xamarin to the virtual machine, which is really fast compared to simulation from Xamarin.
make sure that Android version of your Target Framework is the same of smaller than Android version of your emulator you have chosen to build.
I am implementing a Xamarin app for UWP (and Android and iOS). I'm using VS2015 in VMWare Fusion VM on a Macbook Pro. I am able to build and debug the UWP app in an Emulator without any problems. However I am not able to deploy and debug to a connected Lumia 950 phone over USB. The deployment starts and fails after a while with the message: DEP0001: Unexpected Error -2147023436.
It looks to me as if the file transfer over the USB is not working - however the device is connected and I can communicate with it from the virtual machine.
I have tried a lot, such as using the WinAppDeployCmd.exe command line tool to deploy to the phone. It recognizes the device and starts the package upload and then hangs.
Anybody had the same problem?
I try to debug my windows 8.1 application on the device (lumia 630) but I get the following error:
"The application could not be launched for debugging. Ensure that the target device screen is unlocked and that the application is installed."
The application is installing and I can run it without problems on the device. I also can debug the application in the emulator. The only problem appears when trying to debug on the device. I tried everything I could find with a google search...This inclues restarting the Windows Phone IP over USB service, reinstalling the W8 SDK, un-installing the app before debugging.
If someone has an idea, no matter how stupid it is I would like to hear it. I really need the phone debugging.