After *Android OS*'s last system "update" (to build # BP3A.250905.014) you cannot use *Bluetooth* keyboards to enter 2-factor-authentication codes to access your Google accounts. If you focus the input box, all keypresses cause the input box to lose focus, so that you can not enter your code. How to restore *Google* access? - Do you have to undo the update (roll back to the old version) to restore this ("Alt + Tab" switches)? Have the stock *Android OS* (not [**AOSP**](https://source.android.com/) , which includes sudo); is it possible to go back to the old version on devices without sudo? - Do you have to purchase a new phone (and remember to disable all processes related to "updates" / "provisioning" (and *Google* still asks, refuse those))? - If you can not refuse those: use without the **SIM** card (so *Google* can not force those), or [switch to a new **OS** (such as *Ubuntu Phone*) which allows you to use your phone](https://android.stackexchange.com/questions/57674/ubuntu-for-android) ? If you press "More ways to veridy", there is a option to use **SMS**, but build # BP3A.250905.014 also [breaks **SMS**](https://android.stackexchange.com/questions/262245/build-bp3a-250905-014-prevents-you-from-sending-or-receiving-sms-messages-which) .

Before *Android OS 16*'s last update (to build # BP3A.250905.014), this menu (which you can still pull down with the mouse cursor) , can scroll (horizontal axis) through the numerous pages (if you long-press and drag with the mouse). But now, you can not scroll this menu unless you use the stylus (or your hand) to, which smudges the monitor, since this menu now does not move (when dragged with the mouse). How to restore mouse use on the *Quick Settings* menu? - Do you have to undo the update (roll back to the old version) to restore this ("Alt + Tab" switches)? Have the stock *Android OS* (not [**AOSP**](https://source.android.com/) , which includes sudo); is it possible to go back to the old version on devices without sudo? - Do you have to purchase a new phone (and remember to disable all processes related to "updates" / "provisioning" (and *Google* still asks, refuse those))? - If you can not refuse those: use without the **SIM** card, or [switch to a new **OS** (such as *Ubuntu Phone*)](https://android.stackexchange.com/questions/57674/ubuntu-for-android) ?

I have a Jabra Move headset that has been working wonderfully for months. However, today it started having connection problems to my Motorola Moto Z: it connects and remains connected indefinitely, as long as I don't start playing any sound. If I have sound from Google Music or Facebook, the headset plays 3 seconds, disconnects, and reconnects. I have no idea how to solve this. Here's what I tried: 1. Restarting the mobile phone 2. Restarting the headset 3. Reset the headset 4. Unpairing and pairing back I am running Android 7.1.1. I have no idea how to fix this, please help.

I have an issue with the Bluetooth settings that I can't find a fix for. I have 1 connection that I use to connect to my car for phone calls only and the other connects to my android screen for music, nav etc the reason I do this is because the android screen doesn't use the cars microphone and speakers instead it uses it's own and they are terrible I am able to set the Phone toggle to off for the android screen but it automatically switch's back on causing the android screen to become the default device for phone calls. I have removed the phone permission for the screen but it then makes using the phone via the car's interface very clunky and certainly not handsfree. The screen uses android auto for the connection and I believe this is causing the issue?

First of all, hello friends. My issue is briefly as follows: I want to transfer incoming calls to an Android device to an iPhone. I have two phones, one Android and one iPhone. What I want to do is instantly transfer incoming calls and SMS from the Android device to the iPhone and be able to make calls from the iPhone through the Android device. What I want is something that the devices already support (like Android Auto or CarPlay). I have several different methods in mind, but I haven't found an app or a method that can do what I mentioned. It could be done using one of these methods: 1. Incoming calls to the Android device can be transferred to the iPhone via Bluetooth. 2. If we use the Android device only as a tether and connect from the iPhone via Wi-Fi, I can make and receive calls and SMS over Wi-Fi (presumably VoIP) even when the iPhone is not registered. I can do this by getting a twin SIM card, but when the Android device connects to the phone network, the iPhone becomes inactive, meaning it only needs to connect to the network for internet like a mobile Wi-Fi. 3. The simplest solution, which I can't find, is to transfer incoming calls and SMS to my iPhone via a third-party application. This request may seem strange to you, but unfortunately, if you don't register the device in Turkey (which costs approximately 1000 USD), you can only use the device with your SIM card for 8 months of the year.

I am retrieving bug-report HCI snoop logs from my android 15 mobile phone after my phone app sends chunks of data via BLE to another BLE device (device 2). Then viewing the logs in Wireshark. The data is transferred through the HCI as 'Write Command' ATT frames which contain a 12 byte header and a 136 byte payload (beginning with b1 b1). Once one or more of the Write commands are sent, the controller responds to the host with a 'Number of Completed Packets' HCI_EVT frame. The problem I am having is that my payloads are being corrupted when I 'print' them at application layer on device 2 (always the last 16 bytes of the first corrupted payload and then all bytes of any subsequent payloads). The final 16 bytes of frame 42 (see logs at bottom of question) is the first place that corruption happens. I have no way to view HCI logs at the device 2 end. And currently no way to sniff the data over the BLE connection. I have noticed that at the time of corruption, the Number of Completed Packets does not reflect the number of Write Commands sent previously. You can see at frame 44 of the logs the controller reports that only one packet has completed, even though 3 have been sent consecutively. The controller then catches up at frame 47 and reports that 4 packets have completed. Questions: 1. Could this delay between the write commands and the completed packets response be the cause of my corruption i.e. the host is bombarding the controller with packets faster than it can send them on? Or is it more likely to be a symptom of a problem with the BLE stack etc? 2. I have noticed that the Dynamically Allocated Channel in the Connection oriented channel frames (frame 45) seems to change very frequently (roughly every 2-5 write commands it will increment by 0x0100). Is this normal? I noticed this doesn't happen with my android 13 phone (and also no corruption with android 13 phones). 3. Does any other part of these logs jump out as being non-standard or concerning? Thanks for your help. Frame 41: 148 bytes on wire (1184 bits), 148 bytes captured (1184 bits) Encapsulation type: Bluetooth H4 with linux header (99) Arrival Time: Aug 19, 2025 15:11:22.690757000 GMT Daylight Time UTC Arrival Time: Aug 19, 2025 14:11:22.690757000 UTC Epoch Arrival Time: 1755612682.690757000 [Time shift for this packet: 0.000000000 seconds] [Time delta from previous captured frame: 0.006802000 seconds] [Time delta from previous displayed frame: 0.006802000 seconds] [Time since reference or first frame: 1.338975000 seconds] Frame Number: 41 Frame Length: 148 bytes (1184 bits) Capture Length: 148 bytes (1184 bits) [Frame is marked: False] [Frame is ignored: False] Point-to-Point Direction: Sent (0) [Protocols in frame: bluetooth:hci_h4:bthci_acl:btl2cap:btatt] [Coloring Rule Name: Write Command] [Coloring Rule String: btatt.opcode == 0x52] Bluetooth [Source: 00:00:00_00:00:00 (00:00:00:00:00:00)] [Destination: 00:00:00_00:00:00 (00:00:00:00:00:00)] Bluetooth HCI H4 [Direction: Sent (0x00)] HCI Packet Type: ACL Data (0x02) Bluetooth HCI ACL Packet .... 0000 0000 0101 = Connection Handle: 0x005 ..00 .... .... .... = PB Flag: First Non-automatically Flushable Packet (0) 00.. .... .... .... = BC Flag: Point-To-Point (0) Data Total Length: 143 Data [Expert Info (Error/Protocol): Frame is out of any "connection handle" session] [Source BD_ADDR: 00:00:00_00:00:00 (00:00:00:00:00:00)] [Source Device Name: ] [Source Role: Unknown (0)] [Destination BD_ADDR: 00:00:00_00:00:00 (00:00:00:00:00:00)] [Destination Device Name: ] [Destination Role: Unknown (0)] [Current Mode: Unknown (-1)] Bluetooth L2CAP Protocol Length: 139 CID: Attribute Protocol (0x0004) Bluetooth Attribute Protocol [Expert Info (Warning/Protocol): Packet size exceed current ATT_MTU] Opcode: Write Command (0x52) Handle: 0x0013 (Unknown) Value […]: b1b18000000000008cc66e6c588f0000faa19132916001ec20a1f42f00000000629384000080a0e1d81f0402c7a1462693eaff1f4e634712208112208684ce4147e30fd40c1c40edef8226061bf901f111eccf032061143046221501efdbc600c0346e0c1080e0ee660c044e420c671cef Frame 42: 148 bytes on wire (1184 bits), 148 bytes captured (1184 bits) Encapsulation type: Bluetooth H4 with linux header (99) Arrival Time: Aug 19, 2025 15:11:22.776272000 GMT Daylight Time UTC Arrival Time: Aug 19, 2025 14:11:22.776272000 UTC Epoch Arrival Time: 1755612682.776272000 [Time shift for this packet: 0.000000000 seconds] [Time delta from previous captured frame: 0.085515000 seconds] [Time delta from previous displayed frame: 0.085515000 seconds] [Time since reference or first frame: 1.424490000 seconds] Frame Number: 42 Frame Length: 148 bytes (1184 bits) Capture Length: 148 bytes (1184 bits) [Frame is marked: False] [Frame is ignored: False] Point-to-Point Direction: Sent (0) [Protocols in frame: bluetooth:hci_h4:bthci_acl:btl2cap:btatt] [Coloring Rule Name: Write Command] [Coloring Rule String: btatt.opcode == 0x52] Bluetooth [Source: 00:00:00_00:00:00 (00:00:00:00:00:00)] [Destination: 00:00:00_00:00:00 (00:00:00:00:00:00)] Bluetooth HCI H4 [Direction: Sent (0x00)] HCI Packet Type: ACL Data (0x02) Bluetooth HCI ACL Packet .... 0000 0000 0101 = Connection Handle: 0x005 ..00 .... .... .... = PB Flag: First Non-automatically Flushable Packet (0) 00.. .... .... .... = BC Flag: Point-To-Point (0) Data Total Length: 143 Data [Expert Info (Error/Protocol): Frame is out of any "connection handle" session] [Source BD_ADDR: 00:00:00_00:00:00 (00:00:00:00:00:00)] [Source Device Name: ] [Source Role: Unknown (0)] [Destination BD_ADDR: 00:00:00_00:00:00 (00:00:00:00:00:00)] [Destination Device Name: ] [Destination Role: Unknown (0)] [Current Mode: Unknown (-1)] Bluetooth L2CAP Protocol Length: 139 CID: Attribute Protocol (0x0004) Bluetooth Attribute Protocol [Expert Info (Warning/Protocol): Packet size exceed current ATT_MTU] Opcode: Write Command (0x52) Handle: 0x0013 (Unknown) Value […]: b1b18000000000005320291e52c0288c28142aa2ca8432f073c0091e7220088c2814baa40282e0efef81260652f0ef610088629846a28c02d81f8c00f80400046e2cbaa60080e1e9dbfa468024321400208c2003388518046e2c2aa06293840086a40e84019020eac6511b0b27254e22c8 Frame 43: 148 bytes on wire (1184 bits), 148 bytes captured (1184 bits) Encapsulation type: Bluetooth H4 with linux header (99) Arrival Time: Aug 19, 2025 15:11:22.860785000 GMT Daylight Time UTC Arrival Time: Aug 19, 2025 14:11:22.860785000 UTC Epoch Arrival Time: 1755612682.860785000 [Time shift for this packet: 0.000000000 seconds] [Time delta from previous captured frame: 0.084513000 seconds] [Time delta from previous displayed frame: 0.084513000 seconds] [Time since reference or first frame: 1.509003000 seconds] Frame Number: 43 Frame Length: 148 bytes (1184 bits) Capture Length: 148 bytes (1184 bits) [Frame is marked: False] [Frame is ignored: False] Point-to-Point Direction: Sent (0) [Protocols in frame: bluetooth:hci_h4:bthci_acl:btl2cap:btatt] [Coloring Rule Name: Write Command] [Coloring Rule String: btatt.opcode == 0x52] Bluetooth [Source: 00:00:00_00:00:00 (00:00:00:00:00:00)] [Destination: 00:00:00_00:00:00 (00:00:00:00:00:00)] Bluetooth HCI H4 [Direction: Sent (0x00)] HCI Packet Type: ACL Data (0x02) Bluetooth HCI ACL Packet .... 0000 0000 0101 = Connection Handle: 0x005 ..00 .... .... .... = PB Flag: First Non-automatically Flushable Packet (0) 00.. .... .... .... = BC Flag: Point-To-Point (0) Data Total Length: 143 Data [Expert Info (Error/Protocol): Frame is out of any "connection handle" session] [Source BD_ADDR: 00:00:00_00:00:00 (00:00:00:00:00:00)] [Source Device Name: ] [Source Role: Unknown (0)] [Destination BD_ADDR: 00:00:00_00:00:00 (00:00:00:00:00:00)] [Destination Device Name: ] [Destination Role: Unknown (0)] [Current Mode: Unknown (-1)] Bluetooth L2CAP Protocol Length: 139 CID: Attribute Protocol (0x0004) Bluetooth Attribute Protocol [Expert Info (Warning/Protocol): Packet size exceed current ATT_MTU] Opcode: Write Command (0x52) Handle: 0x0013 (Unknown) Value […]: b1b1800000000000d84801007a42a6ec9884e238ca623210002032f08000ef616238c6800080c0ef2402100046b260ee2605c6153aaba6244710d201a8c4600269c108028081c0e346f08c876e6c08643aa7dbf224321802582f0400eaa48c026e0c8a452080e0ec02840080840e002562 Frame 44: 8 bytes on wire (64 bits), 8 bytes captured (64 bits) Encapsulation type: Bluetooth H4 with linux header (99) Arrival Time: Aug 19, 2025 15:11:22.864229000 GMT Daylight Time UTC Arrival Time: Aug 19, 2025 14:11:22.864229000 UTC Epoch Arrival Time: 1755612682.864229000 [Time shift for this packet: 0.000000000 seconds] [Time delta from previous captured frame: 0.003444000 seconds] [Time delta from previous displayed frame: 0.003444000 seconds] [Time since reference or first frame: 1.512447000 seconds] Frame Number: 44 Frame Length: 8 bytes (64 bits) Capture Length: 8 bytes (64 bits) [Frame is marked: False] [Frame is ignored: False] Point-to-Point Direction: Received (1) [Protocols in frame: bluetooth:hci_h4:bthci_evt] [Coloring Rule Name: bthci_evt] [Coloring Rule String: bthci_evt] Bluetooth [Source: controller] [Destination: host] Bluetooth HCI H4 [Direction: Rcvd (0x01)] HCI Packet Type: HCI Event (0x04) Bluetooth HCI Event - Number of Completed Packets Event Code: Number of Completed Packets (0x13) Parameter Total Length: 5 Number of Connection Handles: 1 Connection Handle: 0x8005 Number of Completed Packets: 1 Frame 45: 496 bytes on wire (3968 bits), 496 bytes captured (3968 bits) Encapsulation type: Bluetooth H4 with linux header (99) Arrival Time: Aug 19, 2025 15:11:22.865584000 GMT Daylight Time UTC Arrival Time: Aug 19, 2025 14:11:22.865584000 UTC Epoch Arrival Time: 1755612682.865584000 [Time shift for this packet: 0.000000000 seconds] [Time delta from previous captured frame: 0.001355000 seconds] [Time delta from previous displayed frame: 0.001355000 seconds] [Time since reference or first frame: 1.513802000 seconds] Frame Number: 45 Frame Length: 496 bytes (3968 bits) Capture Length: 496 bytes (3968 bits) [Frame is marked: False] [Frame is ignored: False] Point-to-Point Direction: Received (1) [Protocols in frame: bluetooth:hci_h4:bthci_acl:btl2cap] Bluetooth [Source: 00:00:00_00:00:00 (00:00:00:00:00:00)] [Destination: 00:00:00_00:00:00 (00:00:00:00:00:00)] Bluetooth HCI H4 [Direction: Rcvd (0x01)] HCI Packet Type: ACL Data (0x02) Bluetooth HCI ACL Packet .... 1110 1101 1100 = Connection Handle: 0xedc ..10 .... .... .... = PB Flag: First Automatically Flushable Packet (2) 00.. .... .... .... = BC Flag: Point-To-Point (0) Data Total Length: 491 Data [Expert Info (Error/Protocol): Frame is out of any "connection handle" session] [Source BD_ADDR: 00:00:00_00:00:00 (00:00:00:00:00:00)] [Source Device Name: ] [Source Role: Unknown (0)] [Destination BD_ADDR: 00:00:00_00:00:00 (00:00:00:00:00:00)] [Destination Device Name: ] [Destination Role: Unknown (0)] [Current Mode: Unknown (-1)] Bluetooth L2CAP Protocol Length: 487 CID: Dynamically Allocated Channel (0x5bff) Payload […]: 0019000001007eea5b60db014340df5965059f65052e0a86658c019c4348df89601e011e431ce086601e011e4324e089322601264348e086322601264360e05965059f65052f0a86658c019c4368e0883226012686322601264374e086321e01264398e089601e011643e8e086601e01 Frame 46: 148 bytes on wire (1184 bits), 148 bytes captured (1184 bits) Encapsulation type: Bluetooth H4 with linux header (99) Arrival Time: Aug 19, 2025 15:11:22.942814000 GMT Daylight Time UTC Arrival Time: Aug 19, 2025 14:11:22.942814000 UTC Epoch Arrival Time: 1755612682.942814000 [Time shift for this packet: 0.000000000 seconds] [Time delta from previous captured frame: 0.077230000 seconds] [Time delta from previous displayed frame: 0.077230000 seconds] [Time since reference or first frame: 1.591032000 seconds] Frame Number: 46 Frame Length: 148 bytes (1184 bits) Capture Length: 148 bytes (1184 bits) [Frame is marked: False] [Frame is ignored: False] Point-to-Point Direction: Sent (0) [Protocols in frame: bluetooth:hci_h4:bthci_acl:btl2cap:btatt] [Coloring Rule Name: Write Command] [Coloring Rule String: btatt.opcode == 0x52] Bluetooth [Source: 00:00:00_00:00:00 (00:00:00:00:00:00)] [Destination: 00:00:00_00:00:00 (00:00:00:00:00:00)] Bluetooth HCI H4 [Direction: Sent (0x00)] HCI Packet Type: ACL Data (0x02) Bluetooth HCI ACL Packet .... 0000 0000 0101 = Connection Handle: 0x005 ..00 .... .... .... = PB Flag: First Non-automatically Flushable Packet (0) 00.. .... .... .... = BC Flag: Point-To-Point (0) Data Total Length: 143 Data [Expert Info (Error/Protocol): Frame is out of any "connection handle" session] [Source BD_ADDR: 00:00:00_00:00:00 (00:00:00:00:00:00)] [Source Device Name: ] [Source Role: Unknown (0)] [Destination BD_ADDR: 00:00:00_00:00:00 (00:00:00:00:00:00)] [Destination Device Name: ] [Destination Role: Unknown (0)] [Current Mode: Unknown (-1)] Bluetooth L2CAP Protocol Length: 139 CID: Attribute Protocol (0x0004) Bluetooth Attribute Protocol [Expert Info (Warning/Protocol): Packet size exceed current ATT_MTU] Opcode: Write Command (0x52) Handle: 0x0013 (Unknown) Value […]: b1b1800000000000d80f0802f754bc0112b42510f771efa111e038002af2f60f6ac1880f000010e1e64afc0f004000000000000000000000000000000000000000000000000000006ee901026ce8010228800004b21a12010d70d0822289d20193030570000000ef0d90930ea35351b292 Frame 47: 8 bytes on wire (64 bits), 8 bytes captured (64 bits) Encapsulation type: Bluetooth H4 with linux header (99) Arrival Time: Aug 19, 2025 15:11:22.956493000 GMT Daylight Time UTC Arrival Time: Aug 19, 2025 14:11:22.956493000 UTC Epoch Arrival Time: 1755612682.956493000 [Time shift for this packet: 0.000000000 seconds] [Time delta from previous captured frame: 0.013679000 seconds] [Time delta from previous displayed frame: 0.013679000 seconds] [Time since reference or first frame: 1.604711000 seconds] Frame Number: 47 Frame Length: 8 bytes (64 bits) Capture Length: 8 bytes (64 bits) [Frame is marked: False] [Frame is ignored: False] Point-to-Point Direction: Received (1) [Protocols in frame: bluetooth:hci_h4:bthci_evt] [Coloring Rule Name: bthci_evt] [Coloring Rule String: bthci_evt] Bluetooth [Source: controller] [Destination: host] Bluetooth HCI H4 [Direction: Rcvd (0x01)] HCI Packet Type: HCI Event (0x04) Bluetooth HCI Event - Number of Completed Packets Event Code: Number of Completed Packets (0x13) Parameter Total Length: 5 Number of Connection Handles: 1 Connection Handle: 0x8005 Number of Completed Packets: 4

Is there an app (because I don't see it as a feature) to limit the address book entries to a particular category when accessing via bluetooth? My car will only take 1000 phone numbers, but my address book on the phone is about 1400. My colleagues car will only take 500, and his list is 900 long. If there was a way to limit the list it would allow it to sync quicker and not miss vital people... Anyone seen anything like this? When I was using WindowsMobile I used a product from http://www.jetwaremobile.com/ to do this - is there an Android equivalent?

I have an HTC One running Android Revolution HD (ARHD), with Android 4.4.2, and I've been getting this error that says >Bluetooth share has stopped working. The problem is that I have *no clue* what's causing this error to appear. I think it started appearing after I clicked the "share" button in an app - but even after fully rebooting my device, I STILL keep getting this error. Does anyone know what could cause this error? And more importantly - how do I debug what app is causing this error? I just don't even know where to start investigating.

Most times the **Samsung** S23+ BT, with LE Audio enabled, connectivity to my **Oticon** Intent hearing aids is great. However, sometimes I think another BT device interferes causing the connectivity to drop (i.e. I can hear the party on the other end but they can not hear me!). I observe the BT icon on my phone is turned OFF due to this interference. As a result, I am forced to either turn ON the BT icon or turn on the Speaker to allow our conversation to continue. But, many times the other party believes a disconnect and calls me back. Very frustrating! Is there someway I can set the phone BT priority highest while paired with my HAs to block any other outside BT interference? Or, is there a Do Not Disturb type setting I can invoke real time to block outside BT interference? Or, is there an App I can install that would address the issue in some way? Any feedback or suggestions would be appreciated.

My computer can communicate with my Android due to being on the same WiFi network. I have Bluetooth headphones and perhaps other Bluetooth devices (Bluetooth mouse, etc). I just bought a Bluetooth dongle for my computer. However, given that my Android device can communicate with my computer anyway via WiFi, I wonder if it's necessary? If anything, if it's possible, will quality deteriorate? My question is a bit more awesome than https://android.stackexchange.com/questions/1198/how-to-use-an-android-device-as-bluetooth-usb-dongle . This one asks if Computer -> USB -> Android phone -> Bluetooth is possible I am asking if Computer -> WiFi -> Android phone -> Bluetooth is possible. In fact, I am interested in Computer -> Bluetooth -> Android phone -> Bluetooth too. Why would I? Well, Windows 10 cannot connect to 5 Bluetooth headsets at once. Maybe sending the sound to my smartphone that can connect to 5 would solve that?

I am using Kali NetHunter on a rooted Android device, and I'm encountering an issue with Bluetooth. Whenever I try to enable Bluetooth through the GUI or using the command line, it simply doesn't turn on. I can see the Bluetooth icon, but it stays stuck on "Turning on." It was working in the beginning, I could connect to headphone, I sent a video file from PC to tablet via Bluetooth.

service bluetooth status

>bluetooth is not running ... failed! Then I started

service bluetooth restart

>Stopping bluetooth: /usr/sbin/bluetoothd.\ >Starting bluetooth: bluetoothd. but this does not restart the Bluetooth. Right after start command, service Bluetooth status still says "Bluetooth is not running ... failed!" I already ran these commands:

sudo apt-get update
sudo apt-get install bluetooth bluez
sudo systemctl start bluetooth
sudo systemctl enable bluetooth

lsusb command shows this: >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub\ >Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub It does not show anything about the Bluetooth adapter I also added kali-tools-bluetooth, but this did not help either.

I'm on the Moto z and on 7.1.1 nougat. I have the JBL speaker mod and a Bluetooth speaker. But I want to use them both. How do I do that? If I connect to the speaker the mod speaker turns off.

Whenever I turn on my Bluetooth headphones, as soon as they connect to my Android phone it starts playing a song; I cannot figure out what app is playing that song or how to make it stop. I have deleted all the music-playing apps I could find from my phone and it makes no difference (in particular, I have deleted Spotify, which seems to be a leading contender for this problem). I believe that my only remaining audio apps are Audible, Libby, PocketCast, and Poweramp, none of which show that they are playing this music. I have deleted the album it was playing from my Music/ folder, so now it only plays the last song it was playing from that album and stops when it reaches the end of the song (if I turn off the headphones and turn them back on, it will play the song again (presumably because it has it and only it cached). It will stop playing if I hit the pause button on my headphones. Doing adb shell dumpsys media_session shows the last audio playback came from the package com.android.systemui which is not helpful (at least not to me). Full output of that command is below in case there is something there that I didn't understand. If someone could lend me a clue, I'd appreciate it. EDITED: added the output of "adb logcat -b all" at the bottom of this text. Full output of "adb.exe -t 14 shell dumpsys media_session": MEDIA SESSION SERVICE (dumpsys media_session) 8 sessions listeners. Global priority session is com.android.server.telecom/HeadsetMediaButton/1 (userId=0) HeadsetMediaButton com.android.server.telecom/HeadsetMediaButton/1 (userId=0) ownerPid=1407, ownerUid=1000, userId=0 package=com.android.server.telecom launchIntent=null mediaButtonReceiver=null active=false flags=65537 rating type=0 controllers: 0 state=null audioAttrs=AudioAttributes: usage=USAGE_VOICE_COMMUNICATION content=CONTENT_TYPE_SPEECH flags=0x800 tags= bundle=null volumeType=LOCAL, controlType=ABSOLUTE, max=0, current=0, volumeControlId=null metadata: null queueTitle=null, size=0 User Records: Record for full_user=0 Volume key long-press listener: null Volume key long-press listener package: Media key listener: null Media key listener package: OnMediaKeyEventDispatchedListener: added 0 listener(s) OnMediaKeyEventSessionChangedListener: added 1 listener(s) from com.android.bluetooth Last MediaButtonReceiver: MBR {pi=null, componentName=ComponentInfo{com.audible.application/androidx.media.session.MediaButtonReceiver}, type=1, pkg=com.audible.application} Media button session is null Sessions Stack - have 4 sessions: play_movies_media com.google.android.videos/play_movies_media/23 (userId=0) ownerPid=9439, ownerUid=10186, userId=0 package=com.google.android.videos launchIntent=null mediaButtonReceiver=null active=false flags=3 rating type=0 controllers: 0 state=null audioAttrs=AudioAttributes: usage=USAGE_MEDIA content=CONTENT_TYPE_UNKNOWN flags=0x800 tags= bundle=null volumeType=LOCAL, controlType=ABSOLUTE, max=0, current=0, volumeControlId=null metadata: null queueTitle=null, size=0 PocketCastsMediaSession au.com.shiftyjelly.pocketcasts/PocketCastsMediaSession/24 (userId=0) ownerPid=9640, ownerUid=10326, userId=0 package=au.com.shiftyjelly.pocketcasts launchIntent=PendingIntent{fe5169e: PendingIntentRecord{da2f57f au.com.shiftyjelly.pocketcasts startActivity}} mediaButtonReceiver=MBR {pi=PendingIntent{469694c: PendingIntentRecord{bbf2d95 au.com.shiftyjelly.pocketcasts broadcastIntent}}, componentName=ComponentInfo{au.com.shiftyjelly.pocketcasts/androidx.media.session.MediaButtonReceiver}, type=1, pkg=au.com.shiftyjelly.pocketcasts} active=false flags=3 rating type=1 controllers: 1 state=PlaybackState {state=PAUSED(2), position=458618, buffered position=0, speed=1.0, updated=202640, actions=122703, custom actions=[Action:mName='Skip back, mIcon=2131231918, mExtras=Bundle[mParcelledData.dataSize=144], Action:mName='Skip forward, mIcon=2131231919, mExtras=Bundle[mParcelledData.dataSize=144], Action:mName='Change speed, mIcon=2131230973, mExtras=null, Action:mName='Star, mIcon=2131231031, mExtras=Bundle[mParcelledData.dataSize=144], Action:mName='Mark as played, mIcon=2131231030, mExtras=Bundle[mParcelledData.dataSize=144]], active item id=-1, error=null} audioAttrs=AudioAttributes: usage=USAGE_MEDIA content=CONTENT_TYPE_UNKNOWN flags=0x800 tags= bundle=null volumeType=LOCAL, controlType=ABSOLUTE, max=0, current=0, volumeControlId=null metadata: size=9, description=Throwback Episode: 'Best Of' Vol. 3, The Sarah Silverman Podcast, Lemonada Media queueTitle=Up Next, size=0 AudibleMediaBrowserService com.audible.application/AudibleMediaBrowserService/25 (userId=0) ownerPid=14234, ownerUid=10295, userId=0 package=com.audible.application launchIntent=PendingIntent{687feaa: PendingIntentRecord{8fb6a9b com.audible.application startActivity}} mediaButtonReceiver=MBR {pi=PendingIntent{c69ce38: PendingIntentRecord{d320e11 com.audible.application broadcastIntent}}, componentName=ComponentInfo{com.audible.application/androidx.media.session.MediaButtonReceiver}, type=1, pkg=com.audible.application} active=true flags=3 rating type=0 controllers: 3 state=PlaybackState {state=NONE(0), position=0, buffered position=0, speed=1.0, updated=236754, actions=4456319, custom actions=[Action:mName='Skip Backward_morris_miniplayer, mIcon=2131231617, mExtras=null, Action:mName='Skip Forward, mIcon=2131231624, mExtras=null, Action:mName='Bookmark, mIcon=2131230918, mExtras=null], active item id=-1, error=null} audioAttrs=AudioAttributes: usage=USAGE_MEDIA content=CONTENT_TYPE_UNKNOWN flags=0x800 tags= bundle=null volumeType=LOCAL, controlType=ABSOLUTE, max=0, current=0, volumeControlId=null metadata: size=20, description= , , queueTitle=null, size=0 androidx.media3.session.id.Libby com.overdrive.mobile.android.libby/androidx.media3.session.id.Libby/26 (userId=0) ownerPid=16590, ownerUid=10304, userId=0 package=com.overdrive.mobile.android.libby launchIntent=PendingIntent{bf5b76: PendingIntentRecord{29c1577 com.overdrive.mobile.android.libby startActivity}} mediaButtonReceiver=null active=true flags=7 rating type=0 controllers: 1 state=PlaybackState {state=NONE(0), position=0, buffered position=0, speed=0.0, updated=325033, actions=4456069, custom actions=[], active item id=0, error=null} audioAttrs=AudioAttributes: usage=USAGE_MEDIA content=CONTENT_TYPE_UNKNOWN flags=0x800 tags= bundle=null volumeType=LOCAL, controlType=ABSOLUTE, max=0, current=0, volumeControlId=null metadata: size=2, description=null, null, null queueTitle=null, size=0 Audio playback (lastly played comes first) uid=10238 packages=com.android.systemui uid=1000 packages=android com.android.providers.settings com.google.SSRestartDetector com.android.location.fused com.google.pixel.iwlan com.android.dynsystem com.android.server.telecom com.android.DeviceAsWebcam com.google.android.settings.future.biometrics.faceenroll com.android.localtransport com.google.android.repairmode com.google.pixel.camera.services com.android.inputdevices com.android.keychain com.android.qns com.google.android.iwlan com.android.settings Media session config: media_button_receiver_fgs_allowlist_duration_ms: [cur: 10000, def: 10000] media_session_calback_fgs_allowlist_duration_ms: [cur: 10000, def: 10000] media_session_callback_fgs_while_in_use_temp_allow_duration_ms: [cur: 10000, def: 10000] media_session_temp_user_engaged_duration_ms: [cur: 600000, def: 600000] Full Output of 'adb -t15 logcat -b all' (starting at the time I turned on my headphones, ending when I was hearing music): 07-24 22:08:00.008 1407 1991 D ConnectivityService: NetReassign [no changes] [c 5] [a 6] [i 14] 07-24 22:08:02.565 1185 1185 I auditd : type=1400 audit(0.0:4508): avc: denied { write } for comm="TracingMuxer" name="traced_producer" dev="tmpfs" ino=1289 scontext=u:r:gxp_logging:s0 tcontext=u:object_r:traced_producer_socket:s0 tclass=sock_file permissive=0 07-24 22:08:02.565 1185 1185 W TracingMuxer: type=1400 audit(0.0:4508): avc: denied { write } for name="traced_producer" dev="tmpfs" ino=1289 scontext=u:r:gxp_logging:s0 tcontext=u:object_r:traced_producer_socket:s0 tclass=sock_file permissive=0 07-24 22:08:02.987 979 1030 I WifiHAL : Creating message to get link statistics; iface = 47 07-24 22:08:03.066 979 979 I WifiHAL : Getting cached scan results, iface handle = 0xb4000074adc28850 07-24 22:08:03.066 979 979 E WifiHAL : Creating message to get cached scan results 07-24 22:08:03.075 979 979 I WifiHAL : In GetCachedScanResultsCommand::handleResponse 07-24 22:08:03.149 1407 1991 D ConnectivityService: NetReassign [no changes] [c 6] [a 6] [i 14] 07-24 22:08:06.123 979 979 I WifiHAL : Creating message to get link statistics; iface = 47 07-24 22:08:06.190 979 1030 I WifiHAL : Getting cached scan results, iface handle = 0xb4000074adc28850 07-24 22:08:06.190 979 1030 E WifiHAL : Creating message to get cached scan results 07-24 22:08:06.196 979 1030 I WifiHAL : In GetCachedScanResultsCommand::handleResponse 07-24 22:08:06.255 1407 1991 D ConnectivityService: NetReassign [no changes] [c 4] [a 6] [i 14] 07-24 22:08:06.438 2239 2363 D TemperatureStateSource: sequence=6079 actualDelay=10002 07-24 22:08:06.446 2239 2363 D TemperatureStateSource: Reading temperature: sequence=6080 07-24 22:08:06.458 1698 1698 I pixel-thermal: VIRTUAL-SKIN:29.6132 raw data: VIRTUAL-SKIN:29613.2 VIRTUAL-SKIN-SUB-1:29613.2 VIRTUAL-SKIN-SUB-2:26912.9 VIRTUAL-SKIN-SUB-3:29154.9 charger_therm:31394 gnss_tcxo_therm:29991 modem_therm:30770 quiet_therm:29635 rffe_therm:30058 soc_therm:29791 usb_conn_therm:29791 07-24 22:08:06.459 2239 2363 D TemperatureStateSource: getDeviceTemperatures: sequence=6080 deviceTemperatureType=3 temperatureSource=0 temperatures=[29.613201] 07-24 22:08:06.459 2239 2363 D BusinessScope: Enqueuing the block 07-24 22:08:06.459 2239 2363 D TemperatureStateSource: sequence=6080 waitTime=10000 07-24 22:08:06.460 2239 2454 D BusinessScope: Start running the #12176 block 07-24 22:08:06.463 2239 2454 D BusinessScope: Enqueuing the block 07-24 22:08:06.464 2239 2454 D ImpulseStateSource: Notify clients: 6087 07-24 22:08:06.464 2239 2454 D BusinessScope: Finish running the #12176 block 07-24 22:08:06.468 2239 2454 D BusinessScope: Start running the #12177 block 07-24 22:08:06.472 2239 2454 D BusinessScope: Finish running the #12177 block

I'm using a Redmi 13C and a M25 earbud, 4 days ago my mom shut it down and hid it away. Find my device from Google doesn't work, I don't enable power on schedule yet why does it still connect to my ear buds Bluetooth?

I'm using an iPega Bluetooth controller with my HTC Desire 510. For most things it works great, but I am running into some issues with Ravensword 2. Ravensword finds my controller and connects fine, but when I start playing, certain actions can't be performed (attacking being one of them). Is there a way to custom map my controller? I'm not on a rooted phone as I can't find a reliable way to root this device.

I'm having issue where my Bluetooth will occasionally turn off. This is an issue because I have a smartwatch that connects with Bluetooth. My SO also has a smartwatch, but doesn't have this issue. I noticed in my battery usage that Bluetooth shows up as an entry in my phone, but does not on my SO. When I tap on Bluetooth, there is an option for '**Adjust Power Use'**. It's apparently set to 'Turn off Bluetooth when not in use.' I can tap on this option, but all it does it take my to the Bluetooth pairing screen, which doesn't seem to have any way to change the option. I also do not have battery saver mode on. There's a variety of things that are battery optimized, but my list of apps matches my SO's phone as well, so I don't think that's an issue either. Clearly I don't want my Bluetooth to turn off, otherwise it makes my watch kind of useless. Does anyone have any ideas on how to fix the issue?

Overall, I'm quite happy with the speed and, in particular, the camera performance of the Samsung Galaxy S25 Ultra. However, like its predecessor, the Samsung Galaxy S24 Ultra, the S25 intermittently jitters when playing Bluetooth audio via hands-free connection to my 2011 Mazda 3 hatchback. It happens when playing Spotify music, and even during a phone call. That phone call audio jitter is heard also by the other party on the call. This problem is severe because a smartphone is used primarily for its mobile communication feature, so that you can speak to others remotely, especially during emergencies. It doesn't matter how nice the other smartphone features are; phone calls have got to work effectively and consistently every time! Even worse, the Galaxy will also intermittently mute its audio via certain third-party Bluetooth FM radio transmitters like the Anker Roav, to which I've tried to switch in order to mitigate the S25 Bluetooth issue in the 2011 Mazda 3. This problem is not mentioned anywhere in the online forums, and apparently, no Samsung technician can help either via their support channel. With the Anker Roav Bluetooth FM transmitter, when the Samsung Galaxy S25 Ultra broadcasts audio (especially from YouTube videos) onto the Roav, the audio is intermittently muted for exactly 13 seconds each time while the video keeps playing. I've noticed that other audio output such as TTS guidance from Waze is also affected. You can imagine what a dismay it is to have lost your exit on the highway where you were supposed to get off because the voice navigation failed to play audibly. The same problem happened to me on the S24. **UPDATE** (April 14, 2025): the audio skipping issue has now begun happening also on the Samsung Galaxy Buds3 Pro playing audio from the Samsung Galaxy S25 Ultra! The audio mutes itself for exactly 6 seconds intermittently. Each time it's 6 seconds of silence. This is followed by an undetermined period of perfect audio, and then another sudden 6 seconds muted! It seems to happen randomly and I can't correlate it with anything, except that each time it's 6 seconds of silence. All audio is affected, including for instance Spotify music streaming and Waze GPS navigation. Has anyone experienced anything similar to this on either model smartphone, and how did you correct it?

Seems like the volume control button on my bluetooth headset is broken, is there any way to change the bluetooth volume directly on the phone? I am on Android 4.1.2, just in case it's relevant. I found settings to change the normal front speaker volume, but nothing for the bluetooth volume.

I recently transferred two videos from a Samsung Android phone to my Oppo Reno 4 using Bluetooth. The transfer took a few minutes, and I received a notification confirming that both videos were successfully received (2 successful, 0 failed). However, when I checked the Oppo device, the videos were nowhere to be found—neither in the gallery nor in any file manager. I’m not looking for a fix, just trying to understand: is this a known issue on Android? What could explain a successful transfer notification followed by missing files? I ended up re-sending the files, which worked the second time, but having to wait again was frustrating.

Samsung devices have the [Dual Audio](https://www.samsung.com/au/support/mobile-devices/setting-up-dual-audio) feature. > Dual Audio allows you to send your media audio to two different Bluetooth devices at once. This means that not only can you use two pairs of headphones at one time but you can share between two different sets of Bluetooth speakers as well. It doesn't seem this is possible on Pixel or OnePlus devices. Does anyone know if any manufacturers other than Samsung have Dual Audio?