Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 3 years ago.
Improve this question
I am using Ubuntu 18.04, and
I am trying to create Android apply using Android-studio.
For that purpose, we are going to connect the Android machine to the PC and debug it.
I connected the Android machine to the PC using USB, but the Android machine was not loaded.
At first it thought that it was caused by not adding a rule to udev.
Fortunately, since my Android machine was HTC, we added a rule toudev with reference to the official documentation.
However, it was still not loaded.
I checked lsusb, but the Android machine information such as the vendor ID was not loaded.
The following is the execution result of lsusb.
$ lsusb
Bus 001 Device 002: ID 8087:8000 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 003: ID 0bda:b002 Realtek Semiconductor Corp.
Bus 002 Device 002: ID 056e:00e3 Elecom Co., Ltd
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
From the developer mode on Android real machine, USB debugging is enabled, USB configuration is MTP.
I think that the cable is the cause of such a problem.
However, trying with multiple USB cables did not solve the problem.
Therefore, I think that there is a cause in Ubuntu's system.
I would like to inform you that you can identify the cause of this problem in more detail and need to investigate further.
Solution
This problem is solved.
The reason was that I was using USB-C cable.
I used a cable for charging.
I could connect successfully when I bought a new cable.
Below is the URL in amazon.
https://www.amazon.co.jp/dp/B0791FBQ83/ref=cm_sw_r_tw_dp_U_x_X5IHCb2V1KVZB
Thank you for answering.
Please check your ADB driver if you not install, first install it.
https://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
And if that does not work, you can try running:
sudo apt-get update
sudo apt-get install dconf-editor
make sure you're using root and run this commands on your terminal
adb kill-server
adb start-server
check if daemon was successfully then write this:
adb devices
It should show list of device attached to your system.
Related
I have written an application using the FT232h with libftd2xx.so.1.4.24 for GPIO assess. I had it running on two machines, a Linux openSUSE desktop and an openSUSE laptop. Both run the same kernel and both are Windows 10 boxes running VMware to give me the virtual openSUSE machines. For some reason it suddenly stopped working on the desktop. I have been using the same FTDI FT232H device on both machines.
On the laptop, the FTDI chip is detected. dmesg | grep -i usb says:
usb 2-1: New USB device found, idVendor=0403, idProduct=6014, etc.
On the laptop, lsusb says:
Bus 002 Device 004” ID 0x0403:6014 Future Technology Devices International. Ltd: FT232H
Single HS USB-UART/FIFO IC
This information does not appear on the desktop. The desktop does not seem to detect the FT232H.
On the laptop I do sudo modprobe -r ftdi_sio usbserial and then perform an FT_Open(0, &fthandle) in libftd2xx.so.1.4.24.
On the desktop, ftdi_sio is not loaded. When I try to FT_Open(0, &fthandle) it fails with FT_DEVICE_NOT_FOUND. It dose the same thing when I run my app as root.
What do I need to do to get my desktop to run my app again? I haven’t blacklisted anything, to my knowledge.
I’m really stuck! Please advise.
VMware may assign the USB to the host or to the guest. If the FT232H is plugged in but lsusb doesn't show the FT232H, then select VM -> Removable Devices -> Future Devices USB Serial Converter -> Connect (Disconnect from Host)
lsusb should now show the FT232H device and you should be able to invoke FT_Open on it.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
Something strange has happened to my Lenovo IdeaPad 310 with Windows 10 latest updates.
My Bluetooth headset was working fine.
But now the toggle to switch Bluetooth on/off has gone missing.
Settings > Bluetooth and other devices
Bluetooth on/off toggle is missing
Settings > Bluetooth and other devices > Senheiser MB Pro 2
Bluetooth is turned off
My headset is listed as a Bluetooth device but the buttons "Connect" and "Remove device" are both disabled.
Device Manager > View > Show hidden devices
The Bluetooth section contains four entries :
Bluetooth Device (RFCOMM Protocol TDI)
Microsoft Bluetooth Enumerator
Microsoft Bluetooth LE Enumerator
Qualcomm Atheros QCA9377 Bluetooth 4.1
All have a faded blue Bluetooth icon.
Right-click on any of them has the same message :
Currently this hardware device is not connected to the computer (
Cede 45 ). To fix this problem, reconnect the hardware device to the
computer.
Right-click any of them and select "Update driver" :
The best drivers for your device are already installed.
Windows has determined that the best driver for this device is already
installed. There may be better drivers on Windows Update or on the
device manufacturer's website.
Troubleshoot > Bluetooth > Run the troubleshooter
Device does not have Bluetooth
Bluetooth is not available on this device. Please try using an
external adapter to add Bluetooth capability to this computer.
I restarted my PC but doesn't seem to have any effect.
I checked for Windows Updates but it does not find any new updates.
I used the Lenovo Service Bridge utility to scan my system and check for any updated drivers but it says I'm up-to-date. I went ahead and downloaded the Bluetooth driver package 75l804af086x.exe and did a manual install and then power-off / power-on but nothing has changed - I'm still on Qualcomm Atheros QCA9377 Bluetooth 4.1
Sometimes with windows updates, few things get broken mostly happen with my wireless driver. You can try reinstalling bluetooth drivers or you can remove the one installed and check in windows updates if there is any updates for bluetooth.
After this shutdown your system(important not restart, shutdown). On reboot your bluetooth will be working fine.(works for my wireless driver). Give it a try
This solution fixed the issue on my Dell which has the same Bluetooth chip.
https://www.dell.com/community/XPS-Desktops/XPS-8930-Qualcomm-QCA9377-Bluetooth-failures/m-p/7402161#M28463
I shutdown the XPS 8930, unplugged the power cord for a few minutes, then powered it back on. I then went to Device Manager and uninstalled the Unknown USB Device (Device Descriptor Request Failed). When I then did a Scan for Hardware Changes, the Bluetooth appeared in Device Manager. This resolved the issue.
I'm trying to figure out how to use a chinese RFID/NFC device (Euhoyan ER301) on my Kali Linux.
I have installed the libnfc and all the dependencies. But executing the command "NFC-LIST" theres no devices found.
Executing lsusb I can see the device:
"Bus 003 Device 012: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light"
Apparently the driver CP210x is installed too.
I'm not quite sure if it is the good way to communicate with the device and if it is compatible with the libnfc.
Does someone has more experience about this devices?
Thanks in advance.
In Samsung Galaxy S6 Edge with Android 6.0, when the device is rebooted, phone complains that the connected computer doesn't recognize the phone and the device is not any more reachable over ADB from the connected Linux PC. The phone in fact instructs user to install proper drivers for Windows or Mac OS, but as the phone is connected to Linux host, there is no help here.
This means, that in order to continue debugging over ADB, one must manually toggle the USB mode from phone from MTP to PTP, after which phone is connected through ADB again. This makes test automation impossible, as the test scheduler needs to reboot the target device between test rounds.
With previous Android versions, rebooting the device remotely and getting ADB connection back was possible, but with Android 6.0, this became a problem. This particular device had earlier Android 5.1 and there were no problems with remote reboots.
As manually toggling of USB mode solves the problem, it might help, if this mode could be automatically toggled after reboot. So far, only solutions I have seen require device rooting and that is out of question.
Does someone have any idea, how Android 6.0 device could be automatically recognized by ADB after reboot?
The solution was after all simple: the Linux user, who starts up the adb server, needed to be added to the "plugdev" group. This group was defined in file /etc/udev/rules.d/51-android.rules with line:
SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
With previous Android versions, this didn't seem to be important as we didn't have any users in that group and everything worked fine.
I have bought an IOGEAR GBU521 bluetooth dongle as per the instruction on Apple's technote:
http://developer.apple.com/library/ios/#technotes/tn2295/_index.html
I have also configured it as instructed and I'm trying to get the temperaturesensor demo to work but the Bluetooth under settings never seems to turn on (keeps spinning). Looking at the console, here is what I see:
2012-11-02 4:17:08.114 PM Preferences[862]: BTM: setting discoverable status enabled
2012-11-02 4:17:08.114 PM Preferences[862]: BTM: setting connectable enabled
2012-11-02 4:17:08.115 PM Preferences[862]: BTM: enabling device scanning
2012-11-02 4:17:08.115 PM Preferences[862]: BTM: failed to start scanning with error 111
Any thoughts? I've seen people ask about this but has anyone got this approach to work?
Best,
Throw away the IOGEAR and pick up a Cirago BTA8000.
I bought the IOGEAR you mention, in addition to the Cirago BTA8000, and the MediaLink 4.0 adapter. Turns out that anything based on the Broadcom chip won't work despite my MacBook having the exact same one built in, which means the MediaLink and IOGEAR don't work. My Cirago shipment just arrived this morning, and the Bluetooth slider in the iOS Simulator flicks to "ON" in less than a second.
If you want to experiment, I'd love to hear if other non-Broadcom chips work too.
I just bought a GBU521 from amazon to upgrade the BT in my MacBook8,3
I had the same problem of it not showing up. Reading the same article you referenced (TN2295) I did a sudo nvram bluetoothHostControllerSwitchBehavior="always" which tells the system to ALWAYS switch to a bluetooth controller if one is plugged in.
The default option:
when a new HCI is connected, the built-in driver only disconnects from the built in HCI and attaches to the external HCI if the new module is not an Apple module.
I presume that because the vendor IDs matched (0xa5c) that it was not switching over to the new dongle. Setting it to always causes OSX to always switch to a new BT adapter. This is confirmed by the following statement in TN2295:
Open the System Information application to verify that the system Bluetooth driver is matched to the built-in Bluetooth host controller interface (HCI). For the Hardware->Bluetooth setting, verify that the Vendor ID is "0x5AC".
Rebooting after the nvram update and I was able to re-pair all of my devices without incident.
HOWEVER this will not work for iOS BT LE development due to the following statement in TN2295:
If the system Bluetooth controller is matched to the Bluetooth LE USB adapter, then the iOS simulator will not be able to use the external Bluetooth controller for Bluetooth LE services.
Actually, you can mod the Info.plist inside the BroadcomBluetoothHostControllerUSBTransport.kext found here:
/System/Library/Extensions/IOBluetoothFamily.kext/Contents/PlugIns/BroadcomBluetoothHostControllerUSBTransport.kext/Contents/Info.plist...
Just copy another Broadcom dictionary and modify it or use the following additon to the Info.plist. You'll need to do this as an admin (i.e. sudo nano or vi this file after making a copy of the original).
<key>Add an appropriate name here</key>
<dict>
<key>CFBundleIdentifier</key>
<string>com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport</string>
<key>IOClass</key>
<string>BroadcomBluetoothHostControllerUSBTransport</string>
<key>IOProviderClass</key>
<string>IOUSBDevice</string>
<key>idProduct</key>
<integer>8680</integer>
<key>idVendor</key>
<integer>2652</integer>
</dict>
May need to reboot after the edit. Did this on 2012 MacBook Pro, ran XCode, and it allowed access to the Bluetooth dongle in iOS Simulator!
I hope this helps!