I have the latest version of Kies installed and the official USB driver for the Galaxy S4 installed. I'm running genuine Windows 7.
Though I can launch the software emulator from inside Eclipse Juno with no problems at all, I cannot test my applications on my physical Galaxy.
When clicking on run, I can see my device. but that's it. The "ok" button is greyed out. Something to do with the 'unknown' target I'd wager.
All help appreciated!
Related
Android studio emulator is failing on my machine and I have no idea what else I can do. I have tried the solutions on these two links :
Android device is not connected to USB for debugging (Android studio)
java.io.IOException: Unable to open sync connection! in to the Nexus
So to sum up here's what I did :
1- Downloaded Android Studio from the official website then I installed it.
(While installing I installed also Intel® HAXM)
2- I installed Android SDK API (15, 16, 19, 21, 23) plus Java JDK + JRE version 8u92 (I also set JAVA_HOME to JDK folder path and included it to the PATH variable also)
3- Dowloaded and installed google usb drivers from http://developer.android.com/sdk/win-usb.html#top (by the way my phone is totally recognized by my Windows 7 OS)
4- Made an "Hello world program" according to https://developer.android.com/guide/tutorials/hello-world.html
5- Enabled USB debboging mode on my cell phone (Alcatel Mpop One touch ; Jelly Bean 4.1.1)
6- Switched between the 3 modes ; PTP, MTP, USB... nothing happened...
Is it me or Android studio is NOT reliable...it seems it should work smoothly just by enabling usb debogging ont the phone. Still I get NO USB device or running emulator running
How can I fix this ? Or is there an alternative to adb of android studio to test my apps on my phone (with installing the app on the phone...) ?
Try to install this adbDriver it works for me on Samsung J1 and Galaxy Star Duos pro
Hmm,
Finally after weeks of searching the internet, I think my problem is related to a missing driver. Though I'm not quite sure why.
The missing driver is a driver from my Telephony service company (Orange.fr in my case). I suppose they made changes to the Android OS / the pohne itself.. anyways there is one of their driver missing.
NEVER BUY A PHONE FROM a telecommunications services company. Always get it from the manufacturer in unlocked mode...that's the lesson I get from this.
I have just migrated from Win 7 to Windows 8.1 to develop my Android project using Eclipse (Luna Service Release 1a (4.4.1)). When connect my Android device (SAMSUNG GT-N7000) on windows 8.1, it recognized by Windows and I can explore the folders of device.
But when run the Android project, Eclipse can not recognize this device and I receive below message:
Failed to find an AVD compatible with target 'Google APIs'.
It sounds like you're hoping that eclipse will run your program on the phone that is plugged into the computer, is that right? If so, why not create a virtual device instead using the Virtual device manager.
Installed updates to nexus 7 to run on 4.4.4 and installed the proper drivers from asus's support. java android teacher had a video on this and followed his steps but still eclipse does not see the nexus and there is only an option for virtual device manager, not just device manager. ran on windows 7 and 8 and mac os. Mac can't find the jre but windows could. solutions?
Try installing the Google USB driver instead of Asus.
Here's the guide to downloading the driver: http://developer.android.com/sdk/win-usb.html
Here's the guide on installing it: http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
Note that the Google USB driver page says:
The Google USB Driver is required for Windows only in order to perform adb debugging with any of the Google Nexus devices. The one exception is the Galaxy Nexus: the driver for Galaxy Nexus is distributed by Samsung (listed as model SCH-I515).
This can be due to the fact that you do not have USB debugging on for your devices. To do that, you need to activate the developer options from your settings menu. Go go settings --> about phone --> click build number 7 times until the developer options are enabled. Then, enter the developer options and enable USB debugging.
If that still doesn't work, you may need to download the driver for your Nexus. This can be found on the android developer website.
Hi so I am working through this book called Beginning Android Games because and I am having some problems with the Android 1.5 Android Virtual Device.
First the SDK for Eclipse (the program I am using) didnt have the 1.5 SDK for Android so I had it installed when you first try to run a AVD it asks has a checklist of SDK's that will be fetched and installed for you if you check the box. I did this, had the 1.5 SDK installed however when i try to run a AVD emulator using the 1.5 sdk i get a
(Failed to allocate memory: 8 This application has requested the Runtime to terminate it in an unusual way. please contact the application's support team for more information.)
type of error. But when I used the default 4.2 SDK for an AVD emulator the emulator showed up. I dont get what im doing wrong here.
Also in eclipse i have the Android ADT and SDK installed. In eclipse when i click on window then Android virtual device manager and I try to start a new emulator the 1.5 sdk i installed doesnt show. But when I click on window->sdk manager->tools->manage avds then my 1.5 sdk shows up and I can use it.
The problem was in the amount of ram for the virtual machine.
This following solution worked for me. In the following configuration file:
C:\Users\<user>\.android\avd\<avd-profile-name>.avd\config.ini
Replace
hw.ramSize=1024
by
hw.ramSize=1024MB
Go to Help -> Check for updates if there it shows some updates needed, then you can install them. May be it will work.
Lately I've been having problems developing Android applications. I'm in a Windows XP environment, using Eclipse 3.5 with the ADT tools. The emulator takes a bit of time to load, but that's always been normal. What is not normal is that when I go to run my program in the emulator at least 50% of the time Eclipse cannot connect to the emulator and either I have to use adb kill-server && adb start-server or restart the emulator or restart eclipse.
This has been happening with so much frequency that it is becoming very problematic. Should I put a newer version of eclipse (3.7) to replace this one? Any other things I can try?
Android development should be smoother as many people are developing Android apps these days.
Try Android x86. It works much more faster than Google Android emulator. Follow these steps:
Install VirtualBox.
Download iso-file that you need
Create a virtual machine Linux 2.6/Other Linux, 512 Mb RAM, HD 2 Gb. Network: PCnet-Fast III, attached to NAT. You can also use bridged adapter, but you need a DHCP server in your environment.
Install Android x86 on the emulator, run it.
Press Alt+F1, type netcfg, remember the IP, press Alt+F7.
Run cmd on your XP, change dir to your Android tools dir, type
adb connect <virtual_machine_IP>
Start Eclipse, open ADT plugin, find the device, enjoy!
Source : Why is the Android emulator so slow? How can we speed up the Android emulator?