OK, the android studio really drive me crazy.
At first, AVD cannot launch and I have post my issue here to AVD not running and failed to create new virtual device Throwable: Failed to create the SD card
After install Android SDK Tool from sdk manager and HAXM installer, it finally can lunch but emulator cannot start up.
After I increase the emulator memory, my emulator works fine but I cannot use real device to run my project.
Error: Power Surge On Hub Port: A USB device has exceeded the power
limits of its hub port
I'm not sure whether the error exists is due to the emulator setting because it can run before the emulator memory get increased. Anyone can help? It totally frustrating.
Try restart your system. I faced the same issue before, but it solved after I restart my system.
This happened because I select TB in emulator setting. After change to MB and restart the system again, it solved
Related
I created a game in unity that I want to download on my phone. I plug in my Samsung galaxy s7 edge and click on build and run.
It starts building as usual, but then the error shows:
I don't know why this is happening. I have enabled USB debugging on my phone and did all the requirements-(click build number seven times, enable USB debugging)
I also disabled and re-enabled the USB debugging but it didn't work. I even downloaded the SDK and JDK!
Few solutions to this problem.
Someone already mentioned try plug/unplug. Sometimes you have to change option from charging to transfer files or other.
Another solution that will probably work is killing adb server. Launch your OS console and type:
adb kill-server
then restart it by
adb start-server
This will force pc-phone communication to be restarted, and probably will solve your problem. Make sure the Android SDK path is correct in your Unity settings too.
My Android Studio version is 2.1.2 in Windows 10. there is no problem before, but today this occurred. And I can not debug my app.
How to solve ?
emulator: WARNING: VM heap size set below hardware specified minimum of 384MB
emulator: WARNING: Setting VM heap size to 384MB
And
emulator: WARNING: ./android/metrics/metrics_reporter_toolbar.cpp:164: Can't upload usage metrics: Error
Run
Event Log
go to tools-->android-->avd manager
edit android virtual device and select show advanced settings
go to memory and storage and set VM heap 400MB
click finish and run avd
Do you see any errors? Try to
adb kill-server
Connect only one device through usb, close all the running emulators. Now run the project. It would show the device to run. Later start emulator and run the app, this time the emulator also would be shown to run the app.
This happened to me also, I have resolved in the above said way.
So up until today everything was working and after doing some trouble shooting on why my app's code was no longer updating, I uninstalled it from the emulator. Now when I go to run it again, it no longer launches or even displays as existing in my emulator. How do I get it to install on the emulator (again) so that I can continue to develop it further? Thanks guys
The Run Logs: Worked before, nothing unusally here.
C:\Users\Will\AppData\Local\Android\Sdk\tools\emulator.exe -avd x86-L
Hax is enabled
Hax ram_size 0x20000000
HAX is working and emulator runs in fast virt mode.
audio: Failed to create voice `goldfish_audio_in'
qemu-system-i386.exe: warning: opening audio input failed
console on port 5554, ADB on port 5555
Strange thing is that when I read through the Android Monitor it appears to be building the app each time I launch it. but it wont launch/display/install it. not sure how to put it into words sadly.
Any and all suggestions on this matter are welcome. Id love to be able to try different ways to make this work.
It seems that your avd memory is greater than your haxm memory. Set avd memory equal or less than haxm memory. For example if haxm memory is 512mb. Set avd memory equal or less than 512mb.
Using the K3b's way of using ADB an a apk file to manually install the app worked. Missing some core functionality by doing this way since some features dont work now but its a start at least.
adb install {file.apk}
whenever i start eclipse or android studio an emulator is constantly running in the background. when i try to turn it off it restarts again immediately. no matter if i work with a real device or an emulator i have created, this other emulator is not stoppable. in the android debug monitor this emulator is listed as emulator-5554 - Online - ? [2,3,4, debug] (Version API10). i never created or used this emulator, and there is no place to find and delete it.
actually i am able to work with eclipse or android studio with that annoying emulator, but it seems to slow down the performance and i would like to get ride of it.
Were you using BlueStacks back then by any chance?
It uses the port 5554, and that might have been your problem too!
It happened to me as well and found the solution in another question:
Eclipse Android Emulator-5554 is always displayed
Strange, but should be able to kill a "hidden" emulator instance from the command-line by connecting to its console, i.e.:
telnet localhost 5554
kill
Replace 5554 with your emulator instance's number.
I use AndroVM. For me its perfect.
Todo is:
install VirtualBox first
download AnroVM
file will open in VirtualBox
start the machine and set USB debug on (settings >> dev. options)
in commandprompt goto your "sdk\platform-tools" type adb connect 192.168.15.101
When it's ok you will see your device in Eclipse.
edit: When your Eclipse is not working well, just download a new bundle again
I am getting these error at console.
hax is not working and emulator runs in emulation mode eclipse.
So I am unable to run the app in emulator.
After spending a lot of time,I am come up with the answer.
If you are getting emulator-x86.exe has stopped working Error means:
Try these two steps:
Change the resolution of the device 1280X800 to 800X600.
Reduce the size of the Ram by 512 MB or less.
If you are getting Hax is not working Error means:
Try these three steps:
1.Hax software would be located
in
C:\Program
Files\Android\android-sdk\extras\intel\Hardware_Accelerated_Execution_Manager
Install the HAXM Driver by running "IntelHaxm.exe" in command Prompt.
2.. if the installer fails with message that Intel VT must be turned on,
you need to enable this in BIOS.
For Eg:
if You are using windows 7, press F12 key to enter into bios setting.
There you can see the Intel Virtualization Technology placed in System Performance.Turn it on as enabled
3.Then again run the "IntelHaxm.exe" in command Prompt.Everything will be works fine.
In Android Studio, AVD Manager, edit the AVD you want and disable Use Host GPU under Emulated Performance. This eliminated this problem for me.
In my case, I solved this by un-selecting Multi-Core CPU.