I'm running Mammon's 1.0.4 DK28. This isn't really important as it's happened w/ every DK28 ROM I've used and it's the most extremely frustrating thing for me.
It goes like this...
I have my phone synced to a jabra earpiece and to the radio in my truck (Clarion CZ500)
I don't use my jabra much but when I do, I get the same weird behavior as in my truck.
In my truck, I get bluetooth connected. I can hear sounds etc. from my speakers. I can stream Pandora, etc. and it works fine. I can make a phone call and it will connect, but no sound unless i switch to speaker, then back to bluetooth.. After I hang up, I can't get bluetooth to produce sound at all. I disable bluetooth and try to listen to music etc. from the external speaker and only get sound from the phone's earpiece. If I make a call, and put it on speaker, still no sound from external speaker, only from the phone's earpiece. Then, after completing a phone call, the phone is sitting idle and makes a popping sound from the earpiece.. random time intervals but still happens until I power cycle the phone.
Any ideas as to how or why this is happening ?? It's extremely frustrating.
Thanks
Related
is there any way to change this? i use my headset to listen to tunes while @ work and the gym, and the whole idea is to eliminate noise coming from the phone (and my desk!)
however, to listen to music you need to turn the sound on - but when you do, and you receive an incoming call, the ringer sound comes right from the phones speakerphone externally. when i get texts it stays within my ears (im pretty sure)
i know you could drop the phone call volume to 0 but what would that do? would you not hear it at all then, even in the headset? would the music even stop playing to signify an incoming call or would it keep playing since theres no need to output any other sound (the ringer)
anyone have a fix or an idea?
same issue in htc athena advantage x7501
real pain in the neck, since it doesn't vibrate.
and with the bluetooth, you solve that problem, but you still can't have any system sounds through the bluetooth headset.
this really wasn't well thought through.
any ideas?
a patch soon?
help?
Bought a Moto S10-HD headset, and it sounds great, but I noticed that when I get notifications, my music pauses like normal, but the notification sound gets played on the phone, and it's not passed along to the headset. Music resumes as normal after the notification. That doesn't happen when using the wired headphones, but if I'm using a bluetooth headset and I leave my phone in the other room, the only way I'll know if I get a notification will be the music pausing.
Any ideas?
It does that to me with my Car stereo when its hooked up via BT. It isn't really an issue for me since I am never far enough away from my phone where i don't hear the notification coming from the phone. I never thought about why it does this, but since you brought it up, I would love to know as well.
A quick google search shows that this is apparently the holy grail for bluetooth headphone users. However, I think the same thing happens with wired headphones as well.
I too, would like to know why and have it solved.
My stock wired headphones play the notification tone fine.
While I'm here, another thing I noticed is the system sounds that are played over bluetooth are somewhat quiet compared to music. That also doesn't happen on the wired headphones.
I'm having a strange problem that I'm trying to see if it's bluetooth stack or CM 10.1 related. When I'm sitting here at work listening to my bluetooth headphones (Jabra BT3030), anytime a phone call comes through, the headphones mute and the ringer AND the music I'm listening to start blaring out of the rear phone speaker. I have to reject the call, stop the music player, and then call the person back. The headphones I'm using also function as a handsfree headset, so, in theory, the phone ring, music, and all answer/deny functions should be handled by the headphones. They've certainly worked this way on every other Android phone I've owned, so I was just curious if this might be an oddity of the new BT stack on 4.2.1, a bug in CM 10.1, or even possibly a setting I'm missing that's causing me this issue. Anyway, when I call the person back, the headphones take on the role of handsfree headset just fine.
Thanks in advance!
I am experiencing the exact same issue on my Galaxy S3 using Moto S305 headphones and CM10.1. I've been searching all over for a solution to this problem and haven't had any luck.
I figured out how to stop the music player audio from coming out of my speaker when receiving a call while on bluetooth. If you turn your ringer volume up then it won't send the music from the player out the speaker phone. When you have the ringer set to vibrate only then it sends your music out the speaker. But I don't want ringer noise either, I just want it to vibrate. My solution was to take my favorite ringtone and insert 5 seconds of silence before it starts to ring. That way I have 5 seconds to either reject the call or answer it before it starts making noise.
Did a search and didn't see this problem discussed...
My Moto X Pure has great audio volume by itself through its own speakers, until...
My problems arise after turning on bluetooth, connecting to something such as my car's radio or my Vizio bluetooth sound bar, listening to music a little bit or even a while and then turning off bluetooth and just using my phone normally. When I return to using my phone normally, my audio is so low. I can barely hear any notifications, lock/unlock sounds, music, etc. All volume sliders are still turned all the way up but still, low audio.
Again, this only happens after I've used bluetooth audio, stopped using it and returned to regular phone speaker operation.
The only fix I've found, and it's not a fix obviously, is to reboot the phone. Audio is back to normal, loud after the reboot. But then connect it via bluetooth to something and play music, stop, turn off bluetooth, the audio is once again verrrryyyyy low even though all volume sliders are all the way up.
Anyone else having this problem?
Android 6.0.0 here.
TL;DR I LOVE my phone, these Bluetooth issues are going to make me smash it into a million pieces. Any custom rom's or fixes for the OEM rom that FIXES them once and for all? I had NONE of these issues on Android 5 on my old phone. A factory fresh phone with no added apps is STILL unstable.
Long read:
I pre-ordered the 6P and have had a mixed relationship with it the past 6 months, the thing pissing me off most is the Bluetooth on this thing.
I DID install MHC19I and it did not help, with anything.
Here's what's happening.
#1 I have a Moto 360 watch that drops bluetooth connection and when it restores, google voice search on the watch remains broken until I restart the phone. This was not an issue on my old phone.
#2 I also am having hell with headsets/speakers. I will be listening to a speaker, get a call, and the damn music doesn't pause and starts playing over the headset AFTER I answer the call, this isn't everytime, but it happens enough to piss me off.
#3 When I hang up the call, the sound does not always go back to the speaker, it says it is, but I hear nothing OR it says it is, and I hear the music coming from the phone. Play Music, Pandora, and Spotify. I have to go into bluetooth settings and force a reconnect. This is happening in my Car, in my house with my Yamaha BT receiver, with a Logitech BT adapter, and a jbl bluetooth speaker.
#4 Sometimes when I first reconnect to the speaker after being out of range, the sound stays at the phone even though it says the speaker is connected.
#5 Just can not keep a stable connection with my 2016 Acadia. The phone has locked up on multiple occasions when either making or receiving phone calls through the car. "Phone has stopped" or something like that.
I upgraded to Android N in an attempt to improve my situation in the least and I don't know what I expected. It's way worse.
Compound all the issues above with:
#1 Delayed notifications to my watch (it starts vibrating to notify me of a call AFTER my ringer has already been ringing 30 seconds)
#2 "mute phone calls on the phone" when connected to watch is broken (The ringer goes off no matter how many times I flip the setting on and off)
#3 It stops broadcasting the playing song information to the display via bluetooth to my car or receiver FREQUENTLY
#4 Answering a phone call via bluetooth occasionally locks up requiring a disconnection from the headset and then I can proceed with the call on the phone.
#5 It either doesn't send the audio to the headset and/or the bluetooth and watch controls lock up (can't change song or control volume, but the music continues playing fine.)
#6 The BIGGEST issue was my 2013, and now my 2016 GMC Acadia. I am going to crash it one of these days with all the dicking around I am doing with the phone when trying to listen to music or take a phone call.
Anyone? I am seriously contemplating giving up EVERYTHING I like about android and getting an iPhone JUST because of these Bluetooth issues (which DO NOT exist on the iPhone 6s).
I solved all my bluetooth issues by turning bluetooth volume all the way up, then turning it down 4 steps from full volume. No drop outs or disconnects from anything since!
I think you must have a defective phone. I have zero problems with Bluetooth on the 6p and I have 10+ Bluetooth devices I use at least 3 of them daily.
Sorry you're having trouble...
I completely factory reset my phone. NO third party apps. Running MHC19I. Music has been fine all day, phone calls are still a problem.
I dial a number, it say's dialing, but I never hear it ringing in my headset. Then the caller picks up and the call timer starts counting. I can clearly see it says it's sending audio via bluetooth and I hear NOTHING. Same on my car shows it's being sent to the radio, but the radio never get's the clue. It works when it wants too, and a restart of the phone always fixes it when it isn't working. It's very frustrating.
I think u might have a defective device BC I'm not experience any of these with my Bluetooth headset. And I'm Stock on MHC19i also .. Sorry u having these bad experiences.
Sent from my Nexus 6P using Tapatalk