I tried to install Openauto on my Raspberry Pi 3b+ and everything seems to start normal. But when I connect my old Samsung Galaxy S5 (Android 6) with it, sometimes Android Auto starts to work for some seconds and the quits. Most of the time it states an error message with "Unable to open MTP device".
When I run mtp-detect from the shell this is the result:
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
Found 1 device(s):
Samsung: Galaxy models (MTP) (04e8:6860) # bus 1, dev 47
Attempting to connect device(s)
error returned by libusb_claim_interface() = -6LIBMTP PANIC: Unable to initialize device
Unable to open raw device 0
OK.
I tried the Crankshaft Image on the Raspberry where Android Auto works without any problems. So I guess there is a configuration problem with the android smartphone and the Raspberry.
Did anybody had a similar issue?
Thanks in advance!
The error you are getting is LIBUSB_ERROR_BUSY, in documents it states that this error code is received when the resource you are trying to access is busy. This usually happens if a program or driver has claimed the interface, meaning that 2 processes try to claim the same interface at the same time.
Try to check the processes currently running on your raspberry pi, maybe you opened multiple instances at the same time, or you are trying to use multiple programs that use the same interface.
Related
I am developing a C# Windows app with feet32 library that is suppossed to initiate phone calls on a cell phone (in my case SAMSUNG S8) through bluetooth by passing ATD command. I have spent days trying to make it work. Unfortunately, I keep getting CME error message code 4 (operation not supported). I have tried different Bluetooth services including HandsFree etc. No success. What could be the reason? I am new to Bluetooth or AT commands topics and I got lost a little bit.
I am unable to attach VS2017 to my unity android app. Here's my setup.
I have adb connected via wifi.
C:\Users\Diamonds\AppData\Local\Android\sdk\platform-tools>adb devices
List of devices attached
192.168.86.20:5555 device
Unity successfully sends the build to the android phone, and logs show up when the app runs on phone:
I've got the app just running on the phone. Inside VS2017 the phone shows up correctly. When I select it, VS2017 spins for 20 seconds then does nothing. No error in VS2017 or in Unity.
Oddly I do not have the phone connected via USB. I do not know why it shows up there.
I think you can try USB instead of WIFI.
According to Microsoft's documentation
Wifi is versatile but super slow compared to USB because of latency. We saw a lack of proper multicast support for some routers or devices (Nexus series are well known for this).
using USB is a better option.
ref:
https://learn.microsoft.com/zh-cn/visualstudio/cross-platform/troubleshooting-and-known-issues-visual-studio-tools-for-unity?view=vs-2017
Recently I bought an Orange Pi 2G IOT board which runs Android 4.4.2 by default.
This device has not an lcd display nor an hdmi port. So i just do tests/development just using ADB for shell/system prorgamming (it is root device) or via Android Studio App development.
Every thing went ok, but after a while I no more could run app from android studio and the logcat shown following two errors for multiple apps.
"E/Capability﹕ Standby get error"
"E/Capability﹕ Active get error"
Please help me on how to solve it.
I've got a Samsung Galaxy S2 and am taking an android development class. For the past two months, I've been using the emulator to run the activity.
Recently, I've been trying to get it connected to my device. Now, the drivers are installed on my computer as I can see the device (and view the files) through "My Computer" (Windows 7 Professional). However, using something like
adb devices
does not show the device, nor through the app launcher in eclipse (when choosing between a virtual device or connected one).
Any help on trying to get it recognized by adb?
Some misc. things:
the model is SPH-D710
I've enabled USB debugging from the phone
OP here, through some help on #android (on freenode), I was able to get this fixed.
The steps I took were,
Remove all pre-existing drivers
I installed a universal driver linked by: http://forum.xda-developers.com/showthread.php?t=1514942
And it worked after that.
Thanks davieslacker
Im using an application in android. I want to enable logcat in eclipse when the project running in external device. Im trying to load the application when USB Cable is mounted to system. But Im not able to saw anything in logcat and cant acess the device view also. If anyone know about this please help me..
Add the devices view and then select the device there and you should be able to see the log.
I am sure more than 1 devices are attached to your PC, among that 1 may be an emulator and other may be real devices(i.e. either mobile or tablet).
So whenever you are having multiple devices, at that time first check the devices attached to your system by using adb devices command at command prompt.
Once you are having serialnumber, you need to run the below command:
Solution: $ adb -s <serialnumber> logcat
PS:
If you just use adb logcat while having multiple devices attached your PC, then below message are being continuously raised:
error: more than one device and emulator
- waiting for device -
It should work with no problem (I did nothing and works)
Maybe you're using a filter of another application.
On the left column (in LogCat view), choose to see "All messages" or create a filter of your own for that application.