https://github.com/JonWoodlief/android-pololu-maestro-ssc
I'm intending to use this to learn how to manipulate servos connected to a pololu maestro card hooked up to my android via micro-usb to mini-usb cable. I'm running a verizon Galaxy S5 (SM-G900V) and I'm rooted on android 5.0. I'm running Wireless ADB using Konnect-ADB.
when I run
adb install C:\AndroidStudioWorkspace\android-pololu-maestro-ssc-master\app\build\outputs\apk\app-debug.apk
I get
[100%] /data/local/tmp/app-debug.apk
Aborted
Any clue to what the problem is, or what i can do to find the problem?
Try adb install -r C:\AndroidStudioWorkspace\android-pololu-maestro-ssc-master\app\build\outputs\apk\app-debug.apk
Make sure your phone is accepting apps from unknown sources, in developer options.
Related
Google Chrome can't detect my device using chrome://inspect/#devices.
But both adb devices and Android Studio can detect it.
Google Chrome Screenshot
adb devices output:
List of devices attached
58H3Y18807006304 device
I tried reinstalling chrome, tried removing all apps and extensions but nothing worked.
But when I loaded Ubuntu on Virtual Box and connected my phone in the VM, then chrome inside Ubuntu VM detected my phone.
Please help me.
See Remote Debugging WebViews ...
unless setting WebView.setWebContentsDebuggingEnabled(true); the debug bridge won't connect.
Another possible cause are local ports having non-default values, which may require port-forwarding.
This would at least list the local ports in use:
sudo lsof -i -P -n | grep 127.0.0.1
What makes only one USB port work for transferring a file from a mac to an android phone with adb by USB cable?
When I run 'adb push file.mp3 storage/self/primary/Download' while I use the USB port on the right side of the computer, everything works. If I use the left USB port, I get a variety of errors like:
'''
adb: error: failed to copy 'file.mp3' to 'storage/self/primary/Download/file.mp3': couldn't read from device
file.mp3: 0 files pushed. 361.9 MB/s (982920 bytes in 0.003s)
'''
'''
adb: error: failed to get feature set: device offline
'''
'''
adb: error: 8-byte write failed: Protocol wrong type for socket
'''
How can I make either USB port work? I'm wondering if this is some USB driver only being installed on one of the controllers or something like that.
I installed Android Platform Tools and connected a Goggle Pixel 2 XL by USB type A on the laptop to the USB C phone port with a single cable (no adapters). Running 'adb devices' shows the phone as connected and I have developer mode set on the phone (I used this phone for android development with lots of adb install, uninstall, logcat, etc commands).
I installed adb with 'brew cask install android-platform-tools' and I have been using brew for other programs with no problems etc.
My PATH is set to use the brew version of adb instead of the android studio version (and I confirmed this by checking the versions used by each).
On a macbook pro early 2015 running 10.12.6 (macOS Sierra).
Thanks!
Amazingly, changing the USB port to which the device was connected to my Mac solved the issue... so weird.
I am trying to run my android app in my samsung device GT-S6012. I use Windows 7 Home Basic. The driver is installed properly. As soon as I connect the mobile using USB cable, for some seconds "adb devices" shows my phone. But then I get a message USB connection error, windows is unable to detect the device and USB is malfunctioning.
I tried uninstalling/re-installing driver, but no luck. I tried Google on this topic but nothing solved my issue.. Can Anyone let me know how can I fix it
windows is unable to detect the device and USB is malfunctioning
Highly unlikely. Unless your USB connector in your Samsung device is broken, USB cable is dead, or USB port in your computer is not functioning. If it's not, you can enable ADB to work with your device by doing the following:
Install the Samsung Universal USB drivers for mobile devices (which I assume you have done already).
If ADB did not ACK/started. First, open a command prompt (since you use Windows) at \android-sdk\platform-tools\ directory and type adb kill-server to kill ADB. Then, type adb start-server to start ADB. Finally, type adb devices to see if ADB has recognised your devices.
See here for a list of ADB commands you can use with Android.
Android adb can't detect Telcast G18 tpad for mac os. I've run
adb kill-server
to stop the adb daemon and run
adb start-server
to restart the adb daemon. But still failed to make adb recognize it?
According to this discussion on the google group, I am trying to modify the adb_usb.ini file by appending the correspondance device usb vendor id.
But how can I know which usb vendor id should I use? Fortunately, I managed to google a list of vendors for usb drivers here, in which case here, the usb device vendor id is:
vendor TECLAST 0x071b Teclast
I faced the similar problem with Teclast P79HD tablet PC built on Intel CPU. My Windows7 desktop detected the tablet which was connect via USB as an unknown USB device and I could not update its driver. The only program that helped me to revive the tablet was Adb_Run_v.3.78.65 by Vitaly Shipilov. You can download this program anywhere in the Internet. It's free.
You should act in the following way:
Install Adb_Run_v.3.78.65 on your Windows desktop.
Restart your PC.
Click Adb Run icon to start the program, then exit from the program. You should start it to start adb server. After that you will see adb.exe process via the Task Manager.
Go to Setting of your tablet, then Storage -> USB computer connection (additional settings) and check 'Media device (MTP)' in 'Connect as' section. Then connect your tablet to PC via USB cable.
After that your PC will detect the tablet as Media device (MTP). You will see the unit in the Device Manager as Android Phone. Now you can transfer files but you cannot use the tablet in debug mode when USB is connected. To resolve this problem you should act as it is described on the page:
Configuring Your Android* USB Debug Connection
See the second half of this article 'To install the Android USB debug driver on Windows 7, 8 or 10'. The driver which helped in my case was 'Android Composite ADB Interface v.4.0.0.0 [23.05.2014]' by Google, Inc. And I checked 'Camera (PTP)' in 'USB computer connection' instead of 'Media device (MTP)'. After this procedure Android Studio began detecting my tablet right and I was able to use it in debug mode.
I just did a factory data restore so that I could use my phone for testing.
But now I am trying to use the adb tool to put a new .apk on the device using my usb, and it says device not connected.
The phone is displaying this message: MTP: server status: connecting to computer...
But it is never able to fully connect.
I tried to go to Wireless & Networks, and enable Internet pass-through, but that option is also "Turning on..." for the last 5 minutes.
Any idea why I am not able to connect?
What kind of device is it? Make sure you have the development USB settings set under Settings, Development. Also ensure it's not a USB Drive but in USB Debugging mode.
Furthermore, if it's a device driver issue, here is an article for the HTC Thunderbolt and Windows/Eclipse:
http://www.nodans.com/index.cfm/2012/2/1/Getting-USB-Device-Drivers-Working-for-HTC-Android-Development
For OSX, Motorola has a USB Link DMG, I'm not sure about HTC though.
Maybe you show give us more information, like
What OS are you using (Windows, Mac, Ubuntu)
Is USB debugging switched on?
Did you restart the adb server
$ adb kill-server
$ sudo adb start-server
* daemon not running. starting it now *
* daemon started successfully *
$ adb devices