Jul 19 21:21:43 rpipro2 kernel: Bluetooth: L2CAP socket layer initialized Jul 19 21:21:43 rpipro2 kernel: Bluetooth: HCI socket layer initialized Jul 19 21:21:43 rpipro2 kernel: Bluetooth: HCI device and connection manager initialized Jul 19 21:21:43 rpipro2 kernel: NET: Registered protocol family 31 Jul 19 21:21:43 rpipro2 kernel: Bluetooth: Core ver 2.19 Jul 19 21:21:43 rpipro2 kernel: usb 1-1.3.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Jul 19 21:21:43 rpipro2 kernel: usb 1-1.3.3: new full-speed USB device number 13 using dwc_otg It will output the following messages to /var/log./syslog in the terminal emulator window: The Linux system automatically detects and loads suitable kernel modules to interface with the Bluetooth Radio. I tried to put the huawei dongle both in the front and in the back but it has not ever worked anyhow in live sessions.Plugin Bluetooth Radio USB Adaptor into the USB hub connected to the Raspberry Pi. The opposite result with my pendrive: the first time I put it in a frontal usb port and it didn't work so I swapped it at back side. PS - Due to reasons I can't understand, the very first time the bt dongle didn't work because I plugged it in one of the back usb ports. Now let me know 1) if the comdex and the dongle was properly paired and 2) how to enable wifi (huawei) or merge its app to the os before working in live session. Consider the device name was ms-7b86, which is my mb's code, so I guess it referred to BT dongle. I chose "task bar" at the beginning, then clicked on the "numb" with dots in the lower left corner -> settings -> connected devices > connection preferences, then pair new devices -> pairing com-dex 410. I guess it's a very bad downside for my goal because I need comdex's app and I won't download it in a live android session because I can't connect to the web, unless it can be possible to "merge" its app to android's files within my pendrive and let it run within the live session. I've got a huawei e3131 dongle and it works properly on my ubuntu but android coulnd't find it in that live session. As soon as os started it began to search wifi. Let me show you in details what it happened: It seems BT dongle works and (it seems!) it can be paired with comdex BUT it's my veru first time with android in general (I've never got a smartphone) and I'm not sure (off everything I saw!). I put android x86 in a pendrive with rufus and I ran it live. can we consider an android box to solve my problem? I don't like to buy a smartphone only to solve this problem. afaik it's basically a cpu architecture matter, I mean android works on arm but not so good on amd cpu as mine, so my question is: does a sort of PC "hybrid" cpu with arm-like structure exist? So it's the "Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)". E353/E3131īus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubīus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hubīus 001 Device 003: ID 1c4f:0034 SiGma Microīus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)īus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub I run both win10 and ubuntu 18.04.1 (4.18.0-25 kernel) and my usb bt dongle is properly recognized in win10 but it doesn't on bluestacks.īus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hubīus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubīus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hubīus 003 Device 002: ID 12d1:14db Huawei Technologies Co., Ltd. maybe I didn't understand you, anyway I've got this usb BT dongle on amazonĪnd it doesn't work in android emulator as you know and I've already written in my 1st post. If your Bluetooth radio device is detected and works in Android
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |