macOS Sierra doesn't detect USB connected Pine64 with Android - android

I hope someone will be able to help me. I've been trying to make it work for days.
My goal is to use the Pine64 with Android and the touchscreen to debug a game using Unity Remote.
The board is PineA64+ 1GB, the touchscreen is the one from the Pine64 store, the SD card is the 32GB card from the store, and the Android is the 6.0.1 for LCD (http://wiki.pine64.org/index.php/Pine_A64_Software_Release#Android_6.0.1_.28LCD_Panel_Video_Output.29_.5B20170209.5D).
My computer OS is macOS Sierra (10.12.6).
I've installed the Android SDK using Android Studio (version 23.0.3 of the build-tools, since I use Android 6.0.1). When I use 'adb devices' to list the devices, it is not listed. But when I go to System Information to check if it's even detected, under Hardware > USB, nothing appears. So it seems that is not that 'adb' doesn't recognize the device, but the USB connection doesn't appear to be there; the computer doesn't detect it.
USB debugging is on, I've tried changing the USB mode between MTP and PTP, I've tried different USB ports from my laptop (if I connect my phone, Android too, it works in both), I've tried different USB cables, I've tried the different USB ports in the board (using Linux the USB ports work well, so I assume is something with Android, and not the board). I've also tried adding the vendor id in adb_usb.ini, as indicated in adb not finding my device / phone (MacOS X)
Could anyone help me? Should I use Android 5.1.1? Do I need to change some configuration, or install some app?
Thank you and best regards.

Related

Unable to connect Android Studio to Pixel 2

I'm running Android Studio Arctic Fox 2020.3.1 Patch 2 on my Dell XPS 13-9370 running Linux Ubuntu Ubuntu 20.04.3 LTS and when I try to connect either of my two Pixel 2s via USB, Studio fails to see them. I have USB debugging enabled and have tried setting Default USB configuration to both File transfer and PTP, to no effect. I also tried swapping USB cables and all the other steps described in the Android Studio Troubleshoot Device Connections.
I should mention that I have no problem connecting Studio to my Samsung Tab A running Android 11, or to any of the emulated devices. They all connect just fine. When I plug the USB cable into the Pixel 2s, I don't even get the permission prompt, even after revoking USB permissions.
I've been knocking my head against a wall on this for a couple of days now, trying out every relevant suggestion I've found on Stack Overflow. I used to have no problem connecting my two Pixel 2 devices up until a few days ago. The problem also occurs on the previous version of Android Studio. I thought it might have something to do with several new third-party apps I installed, but I forced stop them, rebooted the device and still the problem remains.
You can hard reset your devices because in some cases that works.
Otherwise, You can use the developer options wirelessly on your phone.
Just read this article for a step by step guide for how to do this.
Use Android device for development wirelessly
are you using same usb cable for other devices in which it is working ?
try this once - open developer option and select 'Select USB Configuration' . make it mtp and also check if usb debugging is turned on.
Instead of doing it with a cable you could do it wireless just install the plugin adb wifi rest all the instructions are given when you will install that plugin.
Android WiFi ADB
Steps to do this(in short)
Connect your device to your computer using a USB cable.
Then press the button picture of a button to be pressed on the toolbar and disconnect your USB once the plugin connects your device over WiFi.
You can now deploy, run and debug your device using your WiFi connection.
NOTE: Remember that your device and your computer have to be in the same WiFi connection.
Sometimes it happens for the USB connector manager of your operating system. You can uninstall the USB connector manager from your OS Device manager and then restart your laptop. I faced this issue several times and this solution worked for me.
Try to install Genymotion Emulator and Launch it first before running your app. I did it and it helped me and i think it will be work

Android Studio 3.5.2 can't find USB connected device (but found through adb terminal)

The title pretty much says it all: I'm working on an Android Studio (3.5.2) project on my Windows 7 64-bit running laptop, I connect my Samsung J7 (2016) to the laptop through the original Samsung cable but Android Studio simply can't see the device. If I try to do the same on my desktop computer (same Android Studio version but on a Windows 10 64-bit OS) everything works just fine.
Here comes the funny thing: the "adb devices" command shows the device (and I'm 100% sure it's my smartphone since it's the only device connected). The Android Studio toolbar keeps showing "No devices" anyway.
I've spent 3 hours on this and couldn't find a solution. I already tried every suggested solution around the web (stackoverflow.com included), but I achieved nothing:
Disabling/Enabling USB Debug function in the Developer Settings of my smartphone (including revoking USB debugging authorizations)
Running Android Studio as admin (sometimes it solves strange stuff...)
Trying to USB connect through PdaNet+
Android Studio built-in troubleshooting service (re-scanning for devices actually makes me see my smartphone but it's treating it as if it can't be used as a debugging device; anyway the smartphone-computer connection is just fine: I can browse my files and all. Killing and restarting the ADB server does nothing)
Tried connecting both as PTP and MTP
Tried both the Google USB Drivers and the Windows Update drivers (those the computer gets when you first connect the device)
Thanks in advance :)
if you use linux as your PC OS. may be try to install adb will help you..
apt-get install adb
that's work for me.

Android Studio doesn't recognize any emulators

Android Studio is not recognizing any external emulators (phones) connected to it.
I have tried the following mentioned things without any success:
Installed the device driver. (It is working fine. The device recognizes my
phone.)
Turned on USB Debugging.
Kill-server and then start-server commands.
I am using Android Studio for Windows.
Probably you haven't installed the driver for your phone (if you use Windows). For instance, if you use Nexus or Pixel phones, you should install this. If you use Samsung phones, try this link.
It worked for me. If you still cannot see any of the devices, try calling 'Invalidate Caches / Restart' in the File menu in the Android Studio and restarting the system.
Hope it helps!
I had the same problem, my problem was I was using a cable that cam with the phone that acsually would not transfer any data from\to the phone, the moment I changed the cable it worked like magic.
Just try changing a cable 1st, the PC has to recognize the device even if You have no drivers, if Your phone doesnt ask You to give permission to access from PC than the cable is just a charging cable!
Hope it helps.
Set up a device for development (android documentation) :
On the device, open the Settings app, select Developer options, and
then enable USB debugging.
Set up your system to detect your device.
For Windows: Install a USB driver for Android Debug Bridge (adb). For an installation guide and links to OEM drivers, see the
Install OEM USB Drivers document.
When you connect a device running Android 4.2.2 (API level 17) or
higher to your computer, the system shows a dialog asking whether to
accept an RSA key that allows debugging through this computer. This
security mechanism protects user devices because it ensures that USB
debugging and other adb commands cannot be executed unless you're able
to unlock the device and acknowledge the dialog.

Is ther any collision between Genymotion and hardware device on Android studio?

Is there any collision between Genymotion and hardware device on Android studio?? Yesterday, I tested my android phone as a debug machine on android studio. It worked perfectly. However, today, after installing genymotion and run my project on it, Android studio couldn't detect my phone....
I followed these steps :
check whether USB debugging is enabled
check sony xperia USB drive (I installed it from websites, and reinstalled it automatically after conneting my device)
reset Android device monitor
reboot my phone
reboot my computer
plug on/off usb cable
There is no collision between Genymotion and hardware devices. But Genymotion does come with its own copy of adb which introduces potential adb client/server mismatch possibility. So just delete the adb binary from the genymotion\tools folder (you may need to kill all running adb processes first) and you should be ok.

Can't find Android device to test

I'm trying to test an Android application and have a device connected via USB. The device detects (and charges off) the USB connection but I can't seem to find any record on the computer (running Windows 7) that the device is connected. I looked in Device Manager and did not see an "Android Devices" category, nor did I see an "Other Devices" category. I looked on the device manufacturer's website to see if they had drivers; I could not find any. Does anyone have any idea as to how I could get the device to show on the computer? Thanks!
Most probably windows and especially android adb will see your android device after installing the Google USB Driver
I had the same problem for many of my android devices and most of them are running fine with the driver from google. Only for some sony devices I had to install special drivers.
In Android Studio go to Tools -> Android -> Android Device Monitor. Once it opens close it, this will reset your adb and you should be able to see your device
Your problem sounds related with drivers
the Google USB Driver works only for some android models, some other drivers are installed as plug and play but some others you have to install manually.
http://developer.android.com/intl/es/tools/extras/oem-usb.html
Also sometimes it happened to me that the adb didn't recognize the device while the screen was locked so you could also check that out.
It turned out that the USB cable I was using was a charge-only cable. After switching the cable out, the device showed on ADB.

Categories

Resources