Related
Hello guys,
I just got a Sony bluetooth headset and I am trying to use it with my HTC TYTN II. At first I paired the phone and the headset and I was able to listen to music and talk through the headset, all perfect. When I was listening to music, the bluetooth icon on my phone represented a music note and a headset over it.
When I turn the headset off once and then on again, it connects automatically with the phone but in some other mode. The bluetooth icon now represents the bluetooth sign with a headset over it. Now when I listen to some music, it comes from the speaker of the phone, not from the bluetooth headset. Talking through it is not a problem.
If I pair the phone and the headset again, it works just fine (showing again the music note) but once I turn the headset off and on again, I lose the music mode.
Does anyone know how to fix that? Thanks in advance.
I fixed the issue by installing AutoA2DP (found in this forum).
I've had a similar problem on my Tilt. I originally posted the following on the ROM thread. Since then, I have found that the AutoA2DP has not fixed the problem. I still have this issue about 70% of the time, and sometimes I can't get the bluetooth to work at all, not even after a soft reset. Sometimes it seems as if the bluetooth has no power, the phone can't communicate with the headset except when within a few inches of one another. Then it magically seems to resolve itself. Anyway here's my original post from the ROM thread.
The other day I installed an app on my phone called Schaps Network Plugin, which allows you to map network drives to the phone the same way you can do with a desktop. It allows me to access the home network directly via my wifi. It was something I needed and it seemed to work great, for a day. The next day my bluetooth headset would not connect. Long story only slightly shorter, it seems the problem was with the headset connecting via A2DP and doing so automatically. This always worked just fine in the past. Suddenly it wouldn't work. I tried a ton of things including a "fresh" install of everything and formatting my memory card to start with nothing on it. I flashed the original rom and then flashed this rom. I did hard resets each time. Did this twice. Even tried the bluetooth in the oem rom to see if I still got the problem. I did, and it is still with me. I can manually get the headset to connect via A2DP using the bluetooth settings, though even then it may take reconnecting several times to get it to work. However, when I turn the headset off and then on again, the A2DP does not reconnect, just the hands free. But the sound is not routed through the phone's speaker either, at that point. In fact you often get no sound at all, nothing via the headset or the speaker. OTOH, if you activate Voice Command, the headset does work while Voice command is running. After it shuts off, you are back to no sound. It seems as if the hands free works fine, but the audio gets partly routed to A2DP but does not connect to the headset. If I reset the phone, the headset connects correctly and efverything works until I turn the headset off again. Also if I pair the headset again, everything works correctly until I turn the headset off. Though pairing is not as trouble free as it used to be either. Sometimes it will not pair up wihtout repeated attempts. I did find this program, AutoA2DP which has patched the problem. It detects when a paired bluetooth device connects, and forces a connection via A2DP as well. But I never had this issue in the past, and my wife's phone still has no problem. I am not sure the Schaps Network plugin had anything to do with it, other than the timing. Seems odd to me that the bluetooth stack would suddenly develop issues that persist even after two fresh flashes of the rom. Any ideas, suggesitons, etc.? This is really bugging me, and although the patch seems to be working, the phone is still not acting "right." In the past, and on my wife's phone, if a bluetooth headset is turned on, it automatically connects, and all sounds, including the system sounds, are routed through the headset. Now, sometimes they are, and sometimes they aren't.
So I can connect a various number of bluetooth devices to my tablet. It connects just fine and says it is connected for both phone and media. However, when I play media....I get nothing. There is no sound at all. Nothing! Any suggestions on what to do? Here's what I've tried:
Unpairing and repairing the bluetooth device
Clearing bluetooth cache
Turn something on without bluetooth connected, then, while it's playing, connect bluetooth device. Sound stops playing even though the video continues.
Thanks.
Issue
When the headphones (the ones that are bundled with the phone, but I guess it applies for others as well) are plugged in, audio will work in headphones for few seconds (or minutes, if you are lucky), and then the audio will stop (or rather, pause) playing, as if your headphones are disconnected. I tried with music players only, because when headphone is disconnected while music is being played, the music playback will be paused, not sure what happens while playing games but I think audio will start playing from speakers. Anyway, going albeit in depth, when headphones are plugged in, I get a notification from "Samsung USB-C headset" which would say "Checking firmware version", audio can be played via headphones during this time though (naturally), the notification would stay on for quite a few seconds and then disappear (not sure what this thing actually does during this time but OK), audio would still play from headphones, only until you get another notification from Samsung USB-C headset. When this happens, any audio playback will be paused or routed to the speakers as if the headphones are disconnected. You can press the play button in the music player app that you were using to resume playback (can't tell what happens while playing games, because haven't tried), and the audio will play from headphones (sometimes it would play via speakers as well), and it will continue until you receive the same notification again, and this goes on and on. The cycle is like: Plug in headphones -> receive notification -> play audio -> receive notification again which pauses playback -> play audio again -> receive notification again which pauses playback -> .... and it goes on like this.
This is a very frustrating issue as it will make it impossible to use the headphones as this thing repeats itself in intervals of few seconds. Sure, one can use wireless headphones but there are many people like me who prefer the wired ones over the wireless ones. Nonetheless, for normal users this will look like a headphone disconnection issue, and audio via headphone is a basic thing for a phone (or at least, it should be), and having it basically broken is straight unacceptable.
Cause
So like I was saying, we were getting notifications from the Samsung USB-C headset app which caused this disconnection behavior. "Samsung USB-C headset" is a system app by Samsung which kinda manages the firmware versions and codecs and stuffs like that. I haven't checked the logs, and cannot really say for sure, but its the version 1.2.05 version of this app that is causing all these troubles, I think its broken and Samsung needs to fix it ASAP.
That being a system app, it is not possible to disable or downgrade it, I tried various ways to do so, but its no longer possible (for system apps).
Ways to fix
Factory reset - Yes yes I know factory reset won't be a feasible option for many as it can be a bit tedious to go through the backup and the restore process that follows, especially when it is your primary phone (which is why I mentioned "ways to fix" and not "solution"), but yeah, factory reset will fix this issue. What factory reset will do is it will "downgrade" the Samsung USB-C headset app to version 1.1.51, and this version seems to work correctly. When you plug in your headphones, it will say a firmware update is available, simply follow the steps (basically dont unplug headphones while update is in progress), and it will work fine from then on, no issue. Btw, I am on June security patch at the time of writing this. From my observation, I would suggest to not update the Samsung USB-C headset app, and let it be in version 1.1.51. To prevent auto update, go to galaxy store, disable auto updates (luckily this is not there in play store).
This is a software problem, not hardware and Samsung needs to fix this ASAP.
TLDR;
Issue - Wired headphones keeps on disconnecting frequently.
Ways to fix - Factory reset and prevent auto updating Samsung USB-C headset app. Otherwise wait for Samsung to fix.
It didn't work.
You can go to older version of the system app without performing factory reset. It is possible. Go to Apps->then select System Apps option by tapping on 3 dots at upper right side, then select app Samsung USB-C headset-> tap on 3 dots at right side you will get option Uninstall Updates once you tap on it, it will go to last available version or factory version.
corphish said:
Issue
When the headphones (the ones that are bundled with the phone, but I guess it applies for others as well) are plugged in, audio will work in headphones for few seconds (or minutes, if you are lucky), and then the audio will stop (or rather, pause) playing, as if your headphones are disconnected. I tried with music players only, because when headphone is disconnected while music is being played, the music playback will be paused, not sure what happens while playing games but I think audio will start playing from speakers. Anyway, going albeit in depth, when headphones are plugged in, I get a notification from "Samsung USB-C headset" which would say "Checking firmware version", audio can be played via headphones during this time though (naturally), the notification would stay on for quite a few seconds and then disappear (not sure what this thing actually does during this time but OK), audio would still play from headphones, only until you get another notification from Samsung USB-C headset. When this happens, any audio playback will be paused or routed to the speakers as if the headphones are disconnected. You can press the play button in the music player app that you were using to resume playback (can't tell what happens while playing games, because haven't tried), and the audio will play from headphones (sometimes it would play via speakers as well), and it will continue until you receive the same notification again, and this goes on and on. The cycle is like: Plug in headphones -> receive notification -> play audio -> receive notification again which pauses playback -> play audio again -> receive notification again which pauses playback -> .... and it goes on like this.
This is a very frustrating issue as it will make it impossible to use the headphones as this thing repeats itself in intervals of few seconds. Sure, one can use wireless headphones but there are many people like me who prefer the wired ones over the wireless ones. Nonetheless, for normal users this will look like a headphone disconnection issue, and audio via headphone is a basic thing for a phone (or at least, it should be), and having it basically broken is straight unacceptable.
Cause
So like I was saying, we were getting notifications from the Samsung USB-C headset app which caused this disconnection behavior. "Samsung USB-C headset" is a system app by Samsung which kinda manages the firmware versions and codecs and stuffs like that. I haven't checked the logs, and cannot really say for sure, but its the version 1.2.05 version of this app that is causing all these troubles, I think its broken and Samsung needs to fix it ASAP.
That being a system app, it is not possible to disable or downgrade it, I tried various ways to do so, but its no longer possible (for system apps).
Ways to fix
Factory reset - Yes yes I know factory reset won't be a feasible option for many as it can be a bit tedious to go through the backup and the restore process that follows, especially when it is your primary phone (which is why I mentioned "ways to fix" and not "solution"), but yeah, factory reset will fix this issue. What factory reset will do is it will "downgrade" the Samsung USB-C headset app to version 1.1.51, and this version seems to work correctly. When you plug in your headphones, it will say a firmware update is available, simply follow the steps (basically dont unplug headphones while update is in progress), and it will work fine from then on, no issue. Btw, I am on June security patch at the time of writing this. From my observation, I would suggest to not update the Samsung USB-C headset app, and let it be in version 1.1.51. To prevent auto update, go to galaxy store, disable auto updates (luckily this is not there in play store).
This is a software problem, not hardware and Samsung needs to fix this ASAP.
TLDR;
Issue - Wired headphones keeps on disconnecting frequently.
Ways to fix - Factory reset and prevent auto updating Samsung USB-C headset app. Otherwise wait for Samsung t
Click to expand...
Click to collapse
getting this problem in my mi phone
I know this is old but am getting this same issue on my Nubia red magic 6 pro too, it's really frustrating.. Audio keeps cutting when am using type c audio. example same as you explained. I did a Factory reset and did test all wires. and even bought new adapters for audio and all have same thing. seems like it's a software issue.
My P6P (US Unlocked) no longer plays media via bluetooth in my car. It just decided to stop suddently (while playing). Calls are still fine.
Things I tried:
- Bluetooth On/Off (On the car and on the phone)
- Unpairing/Pairing
- Reset Network Preferences on the phone
- Tried another phone with the car (works fine)
- Enabled/Disabled the bluetooth media profile (kept the calls and contacts sharing)
- Paired other bluetooth speakers to the phone and they work fine.
The phone seems to think that audio is playing and so is the car, it's just silent. I'm on the December update.
Any thoughts?
Are you by chance having this problem with SOUNDCLOUD? It's been trouble since my Pixel 2 & 3XL / Android 11. And I can get it started with force stop + clear cache, but it is a pain!
lambdaman said:
Are you by chance having this problem with SOUNDCLOUD? It's been trouble since my Pixel 2 & 3XL / Android 11. And I can get it started with force stop + clear cache, but it is a pain!
Click to expand...
Click to collapse
Nope, it's Youtube music, pokecasts and Google maps. I suppose it's everythings except calls.
slimfady said:
My P6P (US Unlocked) no longer plays media via bluetooth in my car. It just decided to stop suddently (while playing). Calls are still fine.
Things I tried:
- Bluetooth On/Off (On the car and on the phone)
- Unpairing/Pairing
- Reset Network Preferences on the phone
- Tried another phone with the car (works fine)
- Enabled/Disabled the bluetooth media profile (kept the calls and contacts sharing)
- Paired other bluetooth speakers to the phone and they work fine.
The phone seems to think that audio is playing and so is the car, it's just silent. I'm on the December update.
Any thoughts?
Click to expand...
Click to collapse
I've had a similar issue since getting the P6P. Usually it's (randomly) when I try to skip/restart a song or when the song ends the phone will still think it's playing, but the display for the car will show it's paused so audio will stop. To get it playing again I have to turn the phone screen on and press pause then play and it'll start playing normally. As you mentioned, only an issue in the car. No issues with any other bluetooth devices.
I haven't been able to get to the bottom of it, but I updated to the December build last night hoping that might fix the issue. Haven't been anywhere yet today to see if it worked, but your post is giving me doubts now lol.
Edit: Just to add, this is playing music locally from storage with the Retro Music app.
Since the December update i have the same problem, it will connect to phone but will disconnect and not reconnect to play media
On the December update. Was in the car today playing all my media. Iike Spotify and local music and works like a charm. Sounds awesome in my Mazda 3 through Bluetooth. Also same call signal as before more or less. Right now at least is good....but haven't left my area as it's the weekend. LOVE MY P6P!
More things I tried:
- In Developer Settings, changed Bluetooth AVRCP to version 1.3, 1.4 and 1.6.
- In Developed Settings, disabled hardware A2DP.
Still no dice, maybe I should go for a factory reset? Man this phone is weird
Yeah my bluetooth headphones and my home theater amp do not skip a beat, but my car keeps cutting out the music, only just started happening, slightly after decmeber update, so I think they pushed other updates (playstore) which caused these issues. Rebooting the phone fixed it, but nothing else including mentioned in the OP repairing the phone to the car, seemed to make it slightly better.
I too have also noticed the similar issue where the music just stops for no reason, and the phone app thinks its still playing, phone reports it's still connected.
For the OP, if you rock the volume keys up down and up again does it change, beause I did have mine at some point force to zero volume.
Update, it scould be related to temperature because in the morning do not seem to have the same problem, only in the afternoon, temp about 30deg C
danw_oz said:
Yeah my bluetooth headphones and my home theater amp do not skip a beat, but my car keeps cutting out the music, only just started happening, slightly after decmeber update, so I think they pushed other updates (playstore) which caused these issues. Rebooting the phone fixed it, but nothing else including mentioned in the OP repairing the phone to the car, seemed to make it slightly better.
I too have also noticed the similar issue where the music just stops for no reason, and the phone app thinks its still playing, phone reports it's still connected.
For the OP, if you rock the volume keys up down and up again does it change, beause I did have mine at some point force to zero volume.
Click to expand...
Click to collapse
I tried to rock the volume buttons on both the car and the phone and it doesn't seem to change anything. Both the car and the phone actually think that music is playing (as if it was on mute) and the progress time is always in sync.
slimfady said:
Nope, it's Youtube music, pokecasts and Google maps. I suppose it's everythings except calls.
Click to expand...
Click to collapse
Sounds like you're having moble data CONNETIVITY issue!
lambdaman said:
Sounds like you're having moble data CONNETIVITY issue!
Click to expand...
Click to collapse
Nope, It was actually fixed after factory reseting the car's headunit. Weird but at least it's all good now....
slimfady said:
More things I tried:
- In Developer Settings, changed Bluetooth AVRCP to version 1.3, 1.4 and 1.6.
- In Developed Settings, disabled hardware A2DP.
Still no dice, maybe I should go for a factory reset? Man this phone is weird
Click to expand...
Click to collapse
Hi mate, i had same issue, installing android 12L beta 3 fix all my problems, battery is awesome, fingerprint fast, animations smooth like butter....give it a chance and try, maybe fix all your problems.
I know it's a long shot but you should check the settings for automatic do not disturb. I had that happen when the phone realized I was driving and it drove me nuts. Uncheck and mystery solved.
Now if someone can tell me why at completely random times and within a call the device switches back to phone speaker or watch Bluetooth while on an Android auto phone call I'd be appreciative.
slimfady said:
My P6P (US Unlocked) no longer plays media via bluetooth in my car. It just decided to stop suddently (while playing). Calls are still fine.
Things I tried:
- Bluetooth On/Off (On the car and on the phone)
- Unpairing/Pairing
- Reset Network Preferences on the phone
- Tried another phone with the car (works fine)
- Enabled/Disabled the bluetooth media profile (kept the calls and contacts sharing)
- Paired other bluetooth speakers to the phone and they work fine.
The phone seems to think that audio is playing and so is the car, it's just silent. I'm on the December update.
Any thoughts?
Click to expand...
Click to collapse
Try disabling a2dp hardware offload in the developer settings, fixed all my bluetooth issues.
Hi all,
I have a quite common problem as I see in Samsung forums (example). A few weeks ago I connected my A50 to a BT speaker, then as soon as I disconnected it, the sound stopped working (system sound, media sound, etc.) and the audio & video playback is on FastForward like 5x mode. So if I play a video, an audio message, etc, I see the seconds of playback go crazy, sometimes at 2X rate, sometimes at 5X, sometimes slowing down...
As soon as I connect a BT audio device, the playback is normal again and I can hear everything. Sometimes if I reboot the phone, the sound from speaker comes back for a few minutes, but then it disappears again. Lately even reboot does not help.
I updated to latest version (A11, Jan 2022 Patch) and did a factory reset via recovery. The problem is still there.
Rebooting in Safe Mode make the sound works! But not immediately, I have to reboot in safe mode, let the phone settle down a few minutes and then I hear sounds. I check the sound with secret code *#0#*. Then when I go back to normal mode, even without any google and samsung account connected, without all personal apps, without SIM, the sound does not work.
Will a custom ROM solve this issue definitely? Or do you know how to solve it while keeping the stock ROM?
I also tried to debloat the phone disabling 125 apps via Universal Android Debloater but it did not help.
Im facing the same problem , did u find any fix?
This occurred on default os - i did factory reset and it wasnt fixed - installed a custom os and stil nothing.
Have you tried cleaning out the headphone jack? Sometimes if there's gunk in there it'll cause an intermittent or long term short that makes it think there's headphones plugged in.
linuxgator said:
Have you tried cleaning out the headphone jack? Sometimes if there's gunk in there it'll cause an intermittent or long term short that makes it think there's headphones plugged in.
Click to expand...
Click to collapse
But even when headphones are plugged in its the same.