Android Nougat device showing unknown target in eclipse - android

I have a Android Pixel C that has an android version 7.1.1.
I'm using MAC OS X, I have followed all the instructions, i.e. allow usb debugging/ non market apks etc, however the device is showing up "unknown target" in eclipse. See Screenshot below.
Here is some key point which need to be notice.
I'm able to install .apk file from terminal.
I'm able to transfer data from MAC to device and vice versa.
I checked USB info in system information.
Android Studio is recognizing the target and device is perfectly working with the same.
Restarting adb with this shell command and rebooting phone and MAC did not worked for me.
How can I get Eclipse to recognize the target ? Does anyone know how to fix this?

this link will help you
Custom ADT (Eclipse ADB)
https://github.com/khaledev/ADT/releases
or
if do you want only show logcat
https://stackoverflow.com/a/39632018/4359490

install your usb driver manually . Device manager> click on usb > Select action and >add legacy hardware > in select your driver zip file and install it.

Related

android studio doesn't see USB connected device

Just to be clear, the device isn't locked or anything and it works perfectly for my friend who has the same android studio version. The problem isn't with detecting the usb device (by the computer), I can access the device's content just perfectly so it connects correctly to my computer but not to android studio.
When I try to run an application, the usb device doesn't show amongst the options.
Can someone please help me with this issue, knowing that my android studio is updated.
UPDATE:
the devices I used are: Samsung J2 and J3
Have you installed Universal USB Driver, if no then you will not see any device to connect. you can also install individual company device driver.
just try Universal USB Driver to connect all devices
Download from here Universal USB Driver
Open the Device Manager window from the control panel in your computer. In the Others/Unknown Devices tab you would see an unknown android device. Right click on it and update the driver and re-run android studio.
Make sure usb debugging is on in your device.
In Android Studio
Tools->Android->Enable ADB Integration
Enable ADB Integration
Then run app
Hope it will solve the problem
Enable your ADB in your Android
-> First go to Settings->Developer Options
-> Then On or Enable your ADB Mode
Just a Restart of Android Studio worked for me.
In my case it happened because of non-interaction in Android_Studio for long.
Else, Check with Run -> Edit Configurations -> Target.
I have the same problem and I use Samsung too.
I fixed it by installing the device driver from Samsung which you can download from Samsung's website
Note
You need to enable ADB mode(Like the second comment)
You need to set Target in Android Studio to > Open Select Deployment Target Dialog
to set Target : Run > Edit
Configurations > Targets > Open Select Deployment Target Dialog

Visual Studio doesn't let me debug on android physical device

I'm developing an android app with Xamarin and Visual Studio 2013. I have connected my android applet to the computer. Sansung Kies recognizes the device. Adb recognizes it also because when I type "adb devices" the device appears in the list. But when I debug the app Visual Studio doesn't let me choose my device, it only proposes to me to use the android virtual emulator. In my device the "USB debug" option is enabled. So what am I doing wrong?
EDIT
Just got a new machine and ran into the same problem.
Following these steps:
http://visualgdb.com/KB/usbdebug-manual/
as suggested by Veverke in the comment below fixed the issue for me.
just had the same issue and fixed it with a combination of these two links. Obviously our issue isn't the exact same issue that's listed in the first link but that's why I had to use both to kind of synthesize a solution.
https://web.archive.org/web/20140410204811/http://krumelur.me/2014/01/30/xamarins-visual-studio-plugin-missing-android-devices-genymotion-and-parallels-desktop-dont-panic/
http://developer.android.com/tools/extras/oem-usb.html
Basically, in Visual Studio 2013 start the Android SDK Manager. Scroll all the way down to the 'Extras' folder, where you will find the 'Google USB Driver'. Mine was already installed, so I deleted the package, confirmed I wanted it deleted, then reinstalled it.
Then, I opened Windows Explorer and right clicked 'Computer', then clicked 'Manage' (need Admin priviledges). In the newly opened Computer Management window I clicked 'Device Manager' under Computer Management > System Tools in the hierarchy on the left.
In the main window, I expanded 'Other Devices' and saw the device I was looking for. I right-clicked it and chose 'Update Driver Software', then 'Browse my computer for driver software'.
Now you need to hit Browse... and find where you installed the packages.. for myself it was under
C:\Users\zumberge\AppData\Local\Android\android-sdk\extras\google\usb_driver.
Click next, the you need to choose to accept Google, Inc. as a trusted source.
Then the process should be finished and you'll be good to go.
Don't know if you need to restart VS2013, but I did for good measure.
Hope this helps and it's not too late.
For VS 2015, LG Nexus 4 and Windows 7, following solution works for me.
Debugging On and Off during the running instance of Visual Studio, your physical device appears in the device list.
Restart of Visual Studio 2013 has resolved the issue for me.
Details:
Visual Studio was open while I was trying to make the device visible to the system.
After installing the device driver, I have restarted the "adb" and saw that the device is added to the list "adb devices".
However the name of the device at the Visual Studio was not changed, some numbers.
After restarting the Visual Studio, real name of the device is shown "NVIDIA Shield Android TV.."
Then I did not get this error anymore.
I just ran adb command prompt and hit 'adb devices' and it showed daemon was not running. It installed itself and now i can able to see android devices there.
C:\...\...\source\repos\ABC\ABC\Ex.Android>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
ZF22Q3T unauthorized
After enabling debug mode on my android device, I found I had to change the 'USB PC Connection' option. It was set to 'Charge Device'. When I switched it to 'Media Sync (MTP)' and reconnected to my PC it then showed up in Device Manager, but the drivers did not appear to be working with VS. I reinstalled the 'Google USB Driver' in SDK Manager. I removed my device in Device Manager and added it back using the Google USB Driver. When I disconnected/reconnected the device to my PC, Windows asked what I'd like to do with the device. I realized the first time it had asked me, I quickly clicked 'Do Nothing'. This time I noticed the first option was to run an exe on the device to install the driver. After the install completed I disconnected/reconnected the device and the device prompted me to allow my PC to debug. After selecting 'Allow', the device showed up in VS while VS was already open.
Also make sure you have the correct configuration selected for your device. (eg. ARM for most smartphones)
If its set to one that your device doesn't support, then the device won't show up even if adb can see it. Simply switching the configuration solved the problem for me.
Try restarting adb server using:
select "Tools" from top bar then
select "Android". In the list there will be an option to restart adb server as "Restart Adb Server".
After clicking it everything works fine.
It worked for me.
I followed most of the steps mentioned, but still couldn't get it to work. Some things I did were:
download and install google driver from android sdk manager
locate the device in windows device manager and update driver (pointed to the google usb driver)
switch usb connection from mtp to ptp
restarted visual studio
restarted computer
Finally, what worked for me was googling the drivers for my particular android device (lg g4) and landing on this site . Once I installed the drivers I was immediately able to debug in visual studio using my device. it works whether the usb connection is mtp or ptp.
http://www.andromods.com
In case you are using Samsung and have MyKnox installed, you cannot enable USB-Debugging until you uninstall MyKnox as stated in This Link

Android studio not detecting device

I have recently installed android studio in my PC(Windows 8) and I have tried connecting my phone to test an app. But it is not displaying the phone in the device selector. The PC is detecting the phone and the USB debugging is turned on. Even eclipse is detecting the device. Android studio version 0.8.2. I have tried connecting the phone in a friends laptop(Windows 7) and same issue. It is showing in eclipse but not in android studio.
i think adb.exe is responsible for choosing device and for debugging. so pls check if adb exists in sdk path. if your eclipse android sdk path is working , pls set same sdk path for android studio too. it may help you. adb link.
You try this:
To restart adb:
power off your phone
connect the USB cable
On your phone
Run adb devices
You should see the attached device now

How to try an app on a tablet

I am doing some applications using Android + Eclipse to run on tablets. I have had too much trouble with the tablet emulator, so I would like to try my code (apps) on a real tablet. How can I do this? I have a Samsung Galaxy Tab 3. Do I need to install the adt-bundle on it?
I'd appreciate any input.
http://developer.android.com/tools/device.html
You just need a usb cable to connect your device to your pc.Go to the above link for more info
check this it may help you Run on a Real Device
Here is a copy paste, but check the link it's really good and well explained :
If you have a real Android-powered device, here's how you can install and run your app:
1-Plug in your device to your development machine with a USB cable. If you're developing on Windows, you might need to install the appropriate USB driver for your device. For help installing drivers, see the OEM USB Drivers document.
2-Enable USB debugging on your device.
On most devices running Android 3.2 or older, you can find the option under Settings > Applications > Development.
On Android 4.0 and newer, it's in Settings > Developer options.
Note: On Android 4.2 and newer, Developer options is hidden by default.
To make it available, go to Settings > About phone and tap Build number seven times. Return to the previous screen to find Developer options.
To run the app from Eclipse:
1-Open one of your project's files and click Run from the toolbar.
2-In the Run as window that appears, select Android Application and click OK.
Eclipse installs the app on your connected device and starts it.
Or to run your app from a command line:
1-Change directories to the root of your Android project and execute:
ant debug
2- Make sure the Android SDK platform-tools/ directory is included in your PATH environment variable, then execute:
adb install bin/MyFirstApp-debug.apk
3-On your device, locate MyFirstActivity and open it.

Eclipse Won't Recognize BLU Dash 3.5 As An Active Android Device

I got a new Gingerbread phone to try to develop on, but Eclipse won't recognize it.
I put it into debug mode already.
The Win7 Device Manager shows a problem with 4 Qualcomm HSUSB devices, this is certainly related to the phone.
Windows update is unable to find any updates for it.
I couldn't find any drivers support downloads from BLU either.
About the phone:
Andriod version: 2.3.5
Kernel version: 2.6.38.6-perf
Hardware version: A5.V1.2
Build number: BLU_D170_v03_GENERIC
Did you try using the Google USB driver?
For me, in device manager, I had an unknown device listed as "Android device" with a yellow exclamation point over it. Right click it, then choose update driver software. Then choose browse my computer, then choose let me pick from a list of devices...
Then click the Have disk button, and point it to the google usb driver (this should be downloaded via the SDK manager). It will be in the folder where your SDK stuff gets downloaded in the /extras/google/usb_driver folder. When browsing, select the inf file in this folder.
You should get three options that pop up, choose Android ADB Interface. It will then install the generic usb driver so you can connect your phone to ADB.
Note: I have the BLU Dash 4.0, but the driver should work on just about any android device.
First of all, are you able to transfer data to the phone normally? If you can, don't bother with the second part below.
If you can't transfer data, look at this second part. When you bought the phone, did it come with a driver disc? If it did, install the drivers from there. If it did not, try checking the official manufacturer site to see if there's a driver online.
I managed to make contact with BLU service, and they e-Mailed me a driver that only works on 32-bit Win7, not 64-bit :-(
I figured out that I can still test my apps on my DASH 3.5 by uploading the .apk file to a webserver & using the phone to browse to that link. Android will recognize that .apk is an app file it can install. So you could also distribute your own apps to anyone this way, without using any of the Android stores|markets at all.

Categories

Resources