Linked with https://android.stackexchange.com/questions/257113/why-cant-my-android-phone-play-a-sound-on-a-nearby-apple-airtag but not a duplicate. Can an Android phone: 1. show that an AirTag (that I own) is nearby? 2. make it ring? This [article](https://www.mediamarkt.ch/fr/content/handy-navigation/smartphone/airtag-android#airtag-pour-android-grace-a-l-appli) seems to show that the answer is yes, but the limitations make it totally unusable! * [Apple Tracker Detect](https://play.google.com/store/apps/details?id=com.apple.trackerdetect&hl=fr) : user review (translated): > [...] it is indicated that it must **not** be near the owner's iPhone (via Bluetooth) and that the system can take up to 15 minutes to locate it. Finally, to make it ring, you have to wait 10 minutes while standing next to it, as it says! * [AirGuard - AirTag protection](https://play.google.com/store/apps/details?id=de.seemoo.at_tracking_detection.release&hl=fr&gl=fr) : user reviews indicate it's really not handy to use TL;DR: **How to ring a nearby Apple Airtag (that I own) with an Android phone?** Is there a solution an Android that dosent't require to wait 10/15 minutes to locate a tag **and doesn't require to be *outside* of a 15 meters range from the tag for it to work?** (in this case *another* nearby Apple device is probably necessary)

In my Bluetooth settings, I have two paired audio devices: "Bedroom Speaker" is a Google Home Mini and "WH-1000XM4" are my Sony headphones. As they provide both audio and hands-free profiles, I would expect Android to assign a "headset" icon (headphones with a microphone). Instead, they are displayed with a realistic photo of the headphones themselves. My friend's Pixel Buds also display with a photo in this manner. What mechanism causes Android to display the photo? Is it a hard-coded list of "popular" devices that are added to Android for an enhanced experience? Or is it theoretically possible for any Bluetooth device to present itself in this way? I inspected the available services with nRF Connect. The short (16-bit) service UUIDs were 0xFE2C, 0xFE03, and 0x0709, but none of the characteristics supported READ operations, so I thought it unlikely that they were responsible. I am using a Pixel 7a running Android 14. My previous phone ran Android 11 and did not show a photo icon for any devices. I have not installed the Sony headphones app on this phone.

I'm using Lineage OS 18.1 and a BLE Mouse that reports its battery level. I can confirm that the battery level is reported correctly, by connecting it with my Linux computer: (See Devices: DIY Page Turner) Also from the terminal:

[fedora@fedora ~]$ bluetoothctl
Agent registered
[CHG] Controller 9C:B6:D0:94:27:00 Pairable: yes
[DIY Page Turner]# paired-devices
Device CC:50:E3:B6:91:00 DIY Page Turner
[DIY Page Turner]# menu gatt
Menu gatt:
Available commands:
-------------------
list-attributes [dev/local]                       List attributes
select-attribute                  Select attribute
read [offset]                                     Read attribute value
...
[DIY Page Turner]# list-attributes CC:50:E3:B6:91:00
Primary Service (Handle 0x0000)
	/org/bluez/hci0/dev_CC_50_E3_B6_91_00/service005f
	0000180f-0000-1000-8000-00805f9b34fb
	Battery Service
Characteristic (Handle 0x0000)
	/org/bluez/hci0/dev_CC_50_E3_B6_91_00/service005f/char0060
	00002a19-0000-1000-8000-00805f9b34fb
	Battery Level
Descriptor (Handle 0x0000)
	/org/bluez/hci0/dev_CC_50_E3_B6_91_00/service005f/char0060/desc0063
	00002902-0000-1000-8000-00805f9b34fb
	Client Characteristic Configuration
Descriptor (Handle 0x0000)
	/org/bluez/hci0/dev_CC_50_E3_B6_91_00/service005f/char0060/desc0062
	00002904-0000-1000-8000-00805f9b34fb
	Characteristic Format
Primary Service (Handle 0x0000)
	/org/bluez/hci0/dev_CC_50_E3_B6_91_00/service0028
	0000180a-0000-1000-8000-00805f9b34fb
	Device Information
Characteristic (Handle 0x0000)
	/org/bluez/hci0/dev_CC_50_E3_B6_91_00/service0028/char002b
	00002a29-0000-1000-8000-00805f9b34fb
	Manufacturer Name String
Characteristic (Handle 0x0000)
	/org/bluez/hci0/dev_CC_50_E3_B6_91_00/service0028/char0029
	00002a50-0000-1000-8000-00805f9b34fb
	PnP ID
Primary Service (Handle 0x0000)
	/org/bluez/hci0/dev_CC_50_E3_B6_91_00/service0001
	00001801-0000-1000-8000-00805f9b34fb
	Generic Attribute Profile
Characteristic (Handle 0x0000)
	/org/bluez/hci0/dev_CC_50_E3_B6_91_00/service0001/char0002
	00002a05-0000-1000-8000-00805f9b34fb
	Service Changed
Descriptor (Handle 0x0000)
	/org/bluez/hci0/dev_CC_50_E3_B6_91_00/service0001/char0002/desc0004
	00002902-0000-1000-8000-00805f9b34fb
	Client Characteristic Configuration
[DIY Page Turner]# select-attribute /org/bluez/hci0/dev_CC_50_E3_B6_91_00/service005f/char0060
[DIY Page Turner:/service005f/char0060]# read
Attempting to read /org/bluez/hci0/dev_CC_50_E3_B6_91_00/service005f/char0060
[CHG] Attribute /org/bluez/hci0/dev_CC_50_E3_B6_91_00/service005f/char0060 Value:
  2f                                               /               
  2f                                               /               
[DIY Page Turner:/service005f/char0060]# exit
[fedora@fedora ~]$ echo "Battery Level: $(( 16#2f ))%"
Battery Level: 47%

(Not sure if the value (2f) appearing twice is correct behavior, but I assume it is since Linux doesn't seem to have a problem with it.) On Lineage OS however, it doesn't show that information in the status bar: I can display it using BLExplorer though. (35 is the battery level percentage in hex. Which, converted to decimal makes 53%, which is accurate. So the battery level is transmitted properly.) What I would like to see is this btw:

I have been looking around for a demonstration of someone using the ASHA feature on an android phone, but a general google search only brings up ASHA feature being announced (from 2018) or something like this (https://www.youtube.com/watch?v=u7ZDzqC3Mak) which shows how to connect an android capable hearing aid to an android smartphone using their custom app. I believe that ASHA feature being integrated into Android means I should be able to pair with a hearing aid without need for a custom app (correct me here if I am wrong). I have an embedded system development board which claims it can work as BLE device with an ASHA capable smartphone. I also have a Samsung Galaxy s10e which is supposedly ASHA capable (cannot find any official source confirming this, but lots of online discussions imply that s10e series supports ASHA, as well as there are some options in phone settings which makes me think it probably is). One of the only hearing aids in the market that supposedly uses ASHA claims it supports direct streaming with galaxy s10e phones (https://www.resound.com/en/help/compatibility) . If I go to Settings > Accessibility > Hearing Enhancements > Hearing Aid Support > Bluetooth Hearing Aid in my Samsung Galaxy s10e, I can see that it allows me to pair with my custom BLE device (which supposedly has BLE 5.0 and supports BLE audio streaming with android). However, if I play music on the phone after pairing, I cannot hear any output on the built in speakers, but I cannot hear anything in my BLE device either. It's possible that at this moment the BLE device does not have the required codecs for audio streaming, but that is a different question. My main question is about ASHA streaming on the android phone. Am I correct in assuming that after pairing with my BLE device by going to Settings > Accessibility > Hearing Enhancements > Hearing Aid Support > Bluetooth Hearing Aid, I should be able to hear audio played on my phone from the BLE device, like I would on a regular bluetooth earphone? I haver been searching online for at least a demonstration of ASHA streaming or how the Bluetooth Hearing Aid support on the galaxy s10e is supposed to be used, but I cannot find anything. Does anyone here have any experience with this?

After migrating from a Pixel 3a to a Pixel 4a (both running Android 11), re-connecting the GoPlus (a BLE accessory) in Pokémon GO now requires two more actions, first a notification "Pairing request" where I need to click "Pair & Connect" and then I need to press "Pair" on a popup in the middle of the screen "Pair with Pokémon GO Plus" (where I can decide if I want to share contacts and call history). Unfortunately, Niantic un-pairs the device after one hour, so when you want to reconnect, it is no longer paired in Android. This is the exact same app running on the exact same version of Android, but on a device "one generation" newer. It seems strange that there would be a difference in how this works? Is there some kind of permission I can grant Pokémon GO with "pm grant" from an ADB shell, or some other setting I can change, to just allow Pokémon GO-initiated pair and connects to BLE-accessories without user interaction? ("dumpsys package com.nianticlabs.pokemongo" shows that both devices already include android.permission.BLUETOOTH and android.permission.BLUETOOTH_ADMIN under "requested permissions").

Could anyone please tell me if the Sony Xperia Z5 (or Z5 Compact) supports the Bluetooth 4.0 Low Energy profiles? I can't find any specification where this information is available (on gsmarena.com the specification does not explicitly state LE as for other phones - e.g. Samsung Galaxy S6 or even Sony Xperia Z3 Compact). Maybe somebody already tested the device with a BLE device?! Thank you in advance! MDV

Just asking for a bit of data, as I couldn't find it anywhere. Useful to know whether to develop for BLE or Bluetooth. How about percentage over time as well?

I have a Nexus 5X (running stock firmware) which [supports Bluetooth 4.2](https://support.google.com/nexus/answer/6102470?hl=en) . How do I use [6LoWPAN](https://en.wikipedia.org/wiki/6LoWPAN) to share the internet from my phone with BLE devices? Is it as simple as enabling Bluetooth tethering in settings?

Feitian MultiPass FIDO has 3 ways to work as a hardware token: BLE, NFC and USB. I'd like to use it either with NFC or BLE because the USB input can be occupied, and I have a feeling anyway that the USB usage would require some udev rule modifications (https://github.com/Yubico/libu2f-host/blob/master/70-u2f.rules) just like it did with my other token for my Linux desktop. 1. NFC: simply didn't work. I held the key to the back of the phone, moving it around a little (not sure where is the NFC sensor exactly). Since I read somewhere that the NFC is very weak in the key (which can be an advantage for security because an attacker would have a harder time to pick the signal up from distance), I even stripped my phone of it's thin OnePlus carbon protective cover, but didn't help either. 2. BLE: I press the button long and the BLE pairing icon starts to blink on the key. The Google U2F BLE setup page shows the device. Here you'd click on the device and you'd need to enter the 6 digits on it. When I select the device from the list though, the app errors out with the very descriptive "Something went wrong" error message. (That's what the Linux desktop Chrome did as well, extremely descriptive error message for sure). So how can I get this to work? Here is some logcat: https://pastebin.com/X6HLK7a0 Two errors I see: 1. Not sure how related it is: E WCNSS_FILTER: do_ioctl,tty_clock_flag=USERIAL_OP_CLK_OFF,clock=USERIAL_OP_CLK_ON 2. Related for sure: E BluetoothEventManager: Got bonding state changed for 78:8C:EB:56:23:F1, but we have no record of that device. D StatusBarManagerService: manageDisableList userId=0 what=0x0 pkg=Window{3d9a72b u0 Something went wrong} token=android.os.Binder@20e9287 which=1 E BluetoothEventManager: Got bonding state changed for 78:8C:EB:56:23:F1, but we have no record of that device. The debug entry wedged in between the two errors might be accidental. I don't see it always. Any help is appreciated, I'd like to transition to hardware tokens to be protected against SIM hijacks. One more thing: my OxygenOS is rooted because I had to use a hack to be able to run DayDream apps. Because of that I cannot use Google Pay. I hope rooting is not the reason why I cannot pair the key.

I have LG G5 H840 (SE) with unmodified stock firmware. I use cogito watch with it to receive notifications. This a Bluetooth LE hybrid smartwatch. When I go out of range and go back then my watch fails to reconnect with phone if phone is sleeping **and** running on battery. If I wake it then connection is made successfully. If I leave it sleeping but connected to charger then connection is made successfully too. I paired my watch with my wife Huawei P8 Lite and my watch works with her phone without problems described above. It looks like my LG is doing some aggressive battery optimization. I tried to disable "battery optimization" for bluetooth services and my watch application but this did not helped. Maybe someone had a similar problem and can give me some advice what could it check or change?

Does Android support Connection oriented Channel for L2CAP in BLE? What about in Android M ? Thanks !

For a project I am sniffing bluetooth communication between an embedded device and my android phone. To make this work I enabled the Bluetooth HCI Snoop log option on my Android phone in developer options. The bluetooth used is Bluetooth LE (Bluetooth Smart) The embedded device communicates through bluetooth with an app installed on my Android device. Opening the created log file with Wireshark I found some interesting results. I compared my results to that of an example bluetooth capture file and noticed that about half of communication is not present in my capture log. In my capture log there is no PIN code request/reply, no connection events (only disconnect), no link key messages and no SDP or L2CAP protocol usage. I don't understand why I am getting these strange results and I wonder if the entire bluetooth connection and communication process between embedded and android device (including the app) is not captured

I'm doing a feasibility study into Android tablets for commercial applications. I have a product that requires a Bluetooth Low Energy connection. I have a Nexus 7 tablet which is supposed to support BLE but I haven't found much information about it. Is there a way to check whether the tablet has BLE and if it's enabled or not?

I've read here http://www.bluetooth.com/Pages/Bluetooth-Smart-Devices-List.aspx among other pages that it has this technology, but i'm trying to connect to a beacon with it and the app says that "Device does not have Bluetooth Low Energy". Are there maybe any Nexus 7 devices without this kind of bluetooth or what is the problem? The device is updated and the beacons are working because i can find them with other devices.