Hi All
I have installed the Poland 6.0.1 Rom on my Note 4 and everything seem to be working correctly
When I connect my phone to my Car (Ford Ranger 2016 model) its sync's correctly, downloads the phonebook and everything. I can even from the car make a call and it pushes it to the phone correctly as the phone initiates the call and connects the call when they pick up.
The problem is that there is no audio on the speakers. I can mid call select speaker (on the phone) and can then have a conversation with someone over speaker phone but when I push it back to Bluetooth there is no audio.
This worked 100% on 5.1.1 but since the update to 6.0.1 I cannot hear anything on the car speakers even though all the other functions work correctly.
Is this something that can be fixed?
Did you factory reset after upgrade?
nemesis.sisemen said:
Did you factory reset after upgrade?
Click to expand...
Click to collapse
Yes I did. I factory reset just now and tried using it without installing any apps. I can steam music fine. Its just when you make a call that there is no audio. Everything else seem to be working perfectly. I can scroll the address book I can choose and change music, I can place calls with the exception that there is no audio when on a call.....
Did you go to bluetooth settings
nemesis.sisemen said:
Did you go to bluetooth settings
Click to expand...
Click to collapse
Yes I did and both Music and Phone is enabled for it.
I might have the same issue
Hi.
I think this is a general problem plaguing this update.
I have Plantronics E50 Headset. Worked great with 5.1.1.
I use headset as hands-free and usually place calls by holding button on headset for 2 seconds and then issuing voice command "call <contact name>".
This is not done via S Voice but via standard Google app voice.
Like said, all worked great, no issues in 5.1.1.
What I get now after the update to 6.0.1(also Poland 910C, yes, I wiped all after update, but still same behavior), is that I can place calls using the headset + Voice command ("call <contact name>") and I get two outcomes:
1. if phone is unlocked(even if screen is turned off), call is placed, I get audio in the Bluetooth headset - normal behavior.
2. if phone is locked(either auto-locked after timeout and screen off, or locked after pressing power button), call is placed after voice command, but audio remains on the phone and is not transferred to Bluetooth. I need to pick up the phone and talk from it, or press the "bluetooth" button on the dialer window.
Strange is that if I pick up the phone, while locked, and place a call using emergency/favorites contacts, I do get audio in the Bluetooth headset every time.
Problem is that hands free is not usable anymore, since you need to do something on the phone after placing the call.
I think that in your case, call being placed via car Bluetooth system, the thing should be the same.
What I can suggest is to try and see if this works in your case when phone is unlocked.
Anyway, Samsung screwed up something either related to the Phone app, or related to the lock-screen... or both
Solution would be to go back to 5.1.1 or wait for next update, hoping that Samsung fixes this...
Cheers!
ghisisan said:
Hi.
I think this is a general problem plaguing this update.
I have Plantronics E50 Headset. Worked great with 5.1.1.
I use headset as hands-free and usually place calls by holding button on headset for 2 seconds and then issuing voice command "call <contact name>".
This is not done via S Voice but via standard Google app voice.
Like said, all worked great, no issues in 5.1.1.
What I get now after the update to 6.0.1(also Poland 910C, yes, I wiped all after update, but still same behavior), is that I can place calls using the headset + Voice command ("call <contact name>") and I get two outcomes:
1. if phone is unlocked(even if screen is turned off), call is placed, I get audio in the Bluetooth headset - normal behavior.
2. if phone is locked(either auto-locked after timeout and screen off, or locked after pressing power button), call is placed after voice command, but audio remains on the phone and is not transferred to Bluetooth. I need to pick up the phone and talk from it, or press the "bluetooth" button on the dialer window.
Strange is that if I pick up the phone, while locked, and place a call using emergency/favorites contacts, I do get audio in the Bluetooth headset every time.
Problem is that hands free is not usable anymore, since you need to do something on the phone after placing the call.
I think that in your case, call being placed via car Bluetooth system, the thing should be the same.
What I can suggest is to try and see if this works in your case when phone is unlocked.
Anyway, Samsung screwed up something either related to the Phone app, or related to the lock-screen... or both
Solution would be to go back to 5.1.1 or wait for next update, hoping that Samsung fixes this...
Cheers!
Click to expand...
Click to collapse
Yes the same behavior on the Car audio system as you describe except that the audio system regardless of how the call originates from says "Privacy Mode Enabled" and you cannot hear anything or they hear you until you disable the Bluetooth or enable the speaker (that disconnects the Bluetooth)
I have downgraded to 5.1.1 official for my country and yesterday while driving home on the phone with my wife mid call it cut the voice and enabled "Privacy Mode". I could not call again or receive calls over the Car Audio and it persisted even after I rebooted the phone, Turned the radio on and off and even unpaired the phone and paired it again. The call regardless of where of how its made directly goes into "Privacy mode" and you cant disable it
I got home and turned the car off and on again and only when the audio system completely reset after pairing the phone again it could make calls from the phone and car without defaulting to the "Privacy Mode"
Dis is definitely a Android issue with the calling as its a feature in Android and not on the car audio. Music streaming works flawlessly that use the same Bluetooth connection. Its just on calls that it does this and at random
Related
Hi everyone
I have Eten M700 with WM6 ..
I tryed couple of bluetooth headsets (regular, not stereo) and i was able to pair all OK & make and recieve calls
I was even able to divert all sounds to headset to listen to my music (using either btIO or Blue Music)
I also have MS voice commander 1.6 US & it works through bluetooth without problems
I still have one problem:
when i end a phone call (touching red screen dialpad button or by hardware button) or even by waiting for the person on the other line to hang up..then my headset disconnects (i do not see the headset icon on top right of dialpad) and on the next phone call i have to restart pairing by pressing the headst button (it should start automatically & not disconnect)
i do not have to enter pairing code but it is still one extra step that i did not have to do with other phones..also, i miss some calls because when it disconnects i may not hear my phone speaker ringing as i will be away or driving
Does anyone else have the same problem?
Any fix (software, cab or reg tweak) out there to keep the bluetooth headset connected and paired inbetween calls (not disengaging after a call ends)
Thanks
I have the same problem, though i use my DS-220 as a wireless stereo also , i have no problem using it as one or another (handsfree/stereo headset) but as soon as i'm listening to something and i answer a call, sometimes, the headset disconnects itself after a call and i also have to push the button on the headset to connect it again - but not every time, best solution to resolve this problem for 70% of occasions was to uninstall Microsoft Voice Command 1.6 which was messing up with the BT on my phone, since it uses the handsfree's talk/end button as it's own "engage" button, but still, sometimes, this error occurs
I was wondering, if someone of u has working BT Widcomm or any other better BT stack (better than the microsoft bull*hit) and would mind PMing me the link, I could try it out and see, if that's the solution
BT new fix needed
This dsconnection has been happening with me even before MS voice command installation
i did not notice difference with it installed, i am alble to make commands without bluetooth droping & i give my commands through the BT headset without any registry hacks (read something about people having to give commands through phone speaker not headset) i do not have that problem
my only issue is the dropped connection after finishing a phone conversation (by ending a call or other side ending it)
I need a good developer to fix that & also, maybe work on dr.Yar BT software that shows sender/reciepient ID and file progress. that software shows blank white pop-up window when recieving files from some devices.. maybe also add a clickable line to make BT discoverable or hidden to the menu list there
i use BT only for regular mono headset & file transfer, i route music to my mono headset with BlueMusic v2 sometimes too.
If these 2 issues are fixed im all set (droped with calls & ID/progress blank window in Dr.Yar)
Thanks for looking
nothing
no one has solution for this???
I have now tried 3 different bluetooth headsets with my AT&T Tilt with Stock Rom. First was my BlueAnt V12 I used great with my RAZR then I bought a Motorola S705 now I have Sony HBH-DS980.
With the BlueAnt V12 the audio was low and tinny and couldn't hear the caller
The Motorola S705 sounded good minor choppiness but the callers couldn't hear me worth a damn. Both of these devices paired great and kept connection, only the Motorola would loose connection if I got a system alarm or if I was streaming music. For just handset operation it worked great. With the Sony it seems to be a crap shoot when they are going to work. I installed JetWare to enable Caller ID Name and Ringtone through headset and when I pair them the first time they work great all day long. However if I turn bluetooth off on the phone and then back on I have issues with disconnecting and sound not going through headset for calls.
So I installed the new Official AT&T Rom from HTC's Site the other day hoping the bluetooth improvements they made would help. I decided to try JetWare again just to see if it worked, again I started having problems again. So I hard reset and didn't install the JetWare Extensions. For the first day everything worked great. Next day I fired it up it's up to it's old tricks of disconnecting after a call.
Anyone else having these issues? My state is going to be bluetooth only while driving in about 4 months so I really need bluetooth to work.
Can you charge the sony ds980 via usb?
No it has a real strange plug for charging
Hi, I have the Sony Ds980. I've experienced similar problems in the past.
check your Bluetooth settings on the phone: communication manager --> Settings --> bluetooth. Select your device (ds-980) but don't double click on it. and then check its mode: in that window, ensure that you have checkmarks in both options (i.e, Turn on bluetooth & make sure this device is visible to other devices). Sometimes, when you restart your bluetooth headset, the second option is left unchecked, thus causing disconnections between it and the device.
another option is to trigger the headset button. sometimes, when a call comes in, I would have to do this once or twice before it connects.
I think it is a bug.
i have the Jetware extension and MSVoice, and they help with the caller ID.
HTH,
rgds, Manny
I'm trying to decided between the DS980 and the Moto S9.
I'm so tired of wasting my money on crap.
Thanks I'll have a look at those settings, I just wish JetWare uninstalled nicely
I have been running it lately without JetWare and the only issue I am having this way is the wireless stereo portion disconnects after each Incoming call it does not do this if I place a call.
With JetWare I can sometimes keep it connected no matter what the issue is it connects but when I place a test call it rings on the headset but when I answer the call it isn't comming in on the headset it is still on the phone although the call button works and ringing on the headset works. It got to be a pain to have to place a few test calls to make sure the headset was working.
dalavar said:
Thanks I'll have a look at those settings, I just wish JetWare uninstalled nicely
I have been running it lately without JetWare and the only issue I am having this way is the wireless stereo portion disconnects after each Incoming call it does not do this if I place a call.
With JetWare I can sometimes keep it connected no matter what the issue is it connects but when I place a test call it rings on the headset but when I answer the call it isn't comming in on the headset it is still on the phone although the call button works and ringing on the headset works. It got to be a pain to have to place a few test calls to make sure the headset was working.
Click to expand...
Click to collapse
Well, that does it for me. The DS980 is officially off my list.
If I have a bluetooth device connected to my XV-6800, is there a setting or something I can do that will allow me to answer the phone with the call button on the phone, but have it connect to the bluetooth device? Right now if I hit the call button, it only goes through the phones speaker as if the bluetooth device was not connected. For me to answer a call using the bluetooth device, I have to hit the button on the bluetooth device.
Thanks,
Jeff
That's really strange. I know that I don't have the same phone as you (I have touch Elf). I have noticed this. When I have my device connected to bluetooth headset or my handsfree car kit, I can still hit the green call button to anser the phone when I get a call and the call is still transmitted to my bluetooth. I can even still make a call by hitting the green call button, dialing the number and still all through bluetooth.
It sounds like your device is not associating properly with the bluetooth device. Go into your bluetooth settings and check to make sure that you are connected properly for hands free - Go to settings - bluetooth and click on your device to make sure that hands free is checked.
I have also noticed that on a rare occasion, my bluetooth does not connect properly and although paired, does not transmit and sound did come through phone when it shouldn't have. To fix this, I did a soft reset and all was good. It happened to me about three times since I bought the phone in Dec 2007.
hotrod101 said:
That's really strange. I know that I don't have the same phone as you (I have touch Elf). I have noticed this. When I have my device connected to bluetooth headset or my handsfree car kit, I can still hit the green call button to anser the phone when I get a call and the call is still transmitted to my bluetooth. I can even still make a call by hitting the green call button, dialing the number and still all through bluetooth.
It sounds like your device is not associating properly with the bluetooth device. Go into your bluetooth settings and check to make sure that you are connected properly for hands free - Go to settings - bluetooth and click on your device to make sure that hands free is checked.
I have also noticed that on a rare occasion, my bluetooth does not connect properly and although paired, does not transmit and sound did come through phone when it shouldn't have. To fix this, I did a soft reset and all was good. It happened to me about three times since I bought the phone in Dec 2007.
Click to expand...
Click to collapse
The bluetooth is properly connected. When I make a call and hit the green call button, it does go through the bluetooth device. It is only when answering a call it does not go through the bluetooth device when I hit the green call button. Yes, very strange. Oh well, I was hoping somebody might have some insight.
Jeff
jeffgman said:
The bluetooth is properly connected. When I make a call and hit the green call button, it does go through the bluetooth device. It is only when answering a call it does not go through the bluetooth device when I hit the green call button. Yes, very strange. Oh well, I was hoping somebody might have some insight.
Jeff
Click to expand...
Click to collapse
What radio and Windows ROM are you using? I know that some of the different ones fixed some BT issues. When my headset is connected it always goes to my headset no matter what I push. Sometimes I have it in my pocket and forget and then can't hear anything on the phone. I believe you can force it to go to your headset after answering the call though.
jambrose said:
What radio and Windows ROM are you using? I know that some of the different ones fixed some BT issues. When my headset is connected it always goes to my headset no matter what I push. Sometimes I have it in my pocket and forget and then can't hear anything on the phone. I believe you can force it to go to your headset after answering the call though.
Click to expand...
Click to collapse
I am currently using DCD 3.2.6 with radio 3.37.75. To be honest I am not sure I have tried it with this combination. But, I have had the problem with a DCD rom, I just don't remember which radio.
My phone has always bypassed the bluetooth earpiece if I press the answer button on the phone and not the button on the earpiece. It did it from day one with the stock verizon rom and it still does it with my custom dcd rom.
I like the option of bypassing the earpiece to answer a call, especially in a crowd. Also I have the incoming calls announced thru the earpiece. This allows me to know who is calling without even looking at the phone or touching it to answer it thru the earpiece.
This is my insight on this. I hope this helps.
Are you using Voice Command? Is the sound very low?
tommvee said:
My phone has always bypassed the bluetooth earpiece if I press the answer button on the phone and not the button on the earpiece. It did it from day one with the stock verizon rom and it still does it with my custom dcd rom.
I like the option of bypassing the earpiece to answer a call, especially in a crowd. Also I have the incoming calls announced thru the earpiece. This allows me to know who is calling without even looking at the phone or touching it to answer it thru the earpiece.
This is my insight on this. I hope this helps.
Click to expand...
Click to collapse
jeffgman said:
If I have a bluetooth device connected to my XV-6800, is there a setting or something I can do that will allow me to answer the phone with the call button on the phone, but have it connect to the bluetooth device? Right now if I hit the call button, it only goes through the phones speaker as if the bluetooth device was not connected. For me to answer a call using the bluetooth device, I have to hit the button on the bluetooth device.
Thanks,
Jeff
Click to expand...
Click to collapse
Mine operates the same way. I don't beleive this is a "flaw", and may vary by type of bluetooth device being used. OP is looking for a way to override this setting / feature if anyone knows. Personally, I like the option of taking it on the phone for privacy reasons as my BT device is through the car speakers.
ande8150 said:
Mine operates the same way. I don't beleive this is a "flaw", and may vary by type of bluetooth device being used. OP is looking for a way to override this setting / feature if anyone knows. Personally, I like the option of taking it on the phone for privacy reasons as my BT device is through the car speakers.
Click to expand...
Click to collapse
I agree, I don't necessarily think it is a flaw. I would prefer to have mine answer with the bluetooth if I hit the green call button. I was just wondering if there is a setting some where that I am overlooking to have it the way I would prefer.
I just tried it again with the DCD 3.2.6 and 3.37.75 radio. As has been mentioned above, it does not appear to be related to a rom or radio, it is a feature of the phone.
A friend of mine has an iphone, and when they get a phone with a bluetooth earpiece enabled, they get options on the screen which say answer, answer on phone, or ignore. Or something along those lines. I like having those options, but understand if it is not available on the 6800.
Thanks for all of the replies.
Jeff
Hello everyone, I run into a really weird problem on my Note 4 when receiving voice calls while using a bluetooth headset.
Summary:
If BT headset is not already connected before initiating or receiving a voice call, you have to press bluetooth button during the call to direct sound to phone and then back to the BT in order to get the mic on the headset to work.
More Details :
1. Incoming Voice call
2. While phone is ringing i turn on the bluetooth headset.
3. I answer the call(Either from phone or the headset)
4. I can hear the other party, but he doesn't hear me.
5. The bluetooth headset mic is not working, neither the phone's mic.
6. If i press the bluetooth icon on the phone(while in a voice call) to direct audio to phone, everything works fine.
7. If i press again to direct audio back to bluetooth headset, everything works fine.
8. If the headset is already connected to the phone before i receive the voice call everything works fine.
9. If i make a voice call (maybe cause headset is already connected?) everything works fine.
10. Problem doesn't occur if it's a VOIP call through skype viber etc.
10. Using plantronics Marque M165 & M55, I have unpaired both repaired, cleared bluetooth cache etc problem still there. Lollipop 5.0.1.
For me it's a big issue since if i have the phone in my bag/pocket i have to take it out in order to be able to use the headset, which kind of defeats the purpose.
Anyone facing this ? Any suggestions?
Sorry for the long post & thanks in advance !
Anyone?
Anyone with similar problems ? Any ideas or suggestions ???
Yes, I have a similar problem, but with my car's bluetooth (the only hands free I use). This problem started after I upgraded to Lollipop, and it worked fine in KitKat.
With te device connected to the car's bluetooth, I have to make the call in the phone's Speaker mode until the other party answers. Only then I can switch to bluetooth.
If I make the call in bluetooth mode, I won't hear the ringing through the car's speakers and even after the other party answers, we cannot communicate.
This is a serious bug. It is my 4th Samsung Galaxy phone, and the only one that doesn't work properly. My previous S4 worked perfectly and I regret profoundly having bought the Note 4.
Ironically i don't face the problem you have. Mine works fine with my car's BT but i suppose this happens because in my case the car's BT is already connected to the phone.
I suppose you have tried to repair the bluetooth/ cleared BT cache etc right ?
I've just tried the phone with a Samsung bluetooth and problem solved !....So it doesn't play well with the plantronic's BT , warning for potential buyers !
Hi all
I'm having this strange (but really frustrating) Bluetooth bug on my Motorola Moto X Style (XT1572) with Android 6.0. I already tried restoring the Phone to factory settings and without any extra apps but the issue persists. It just suddenly started happening (about a month ago).
Nothing has changed in the bluetooth devices that I use with my Phone. I connect my car using Bluetooth and if I'm not in my car, I use a Bluetooth hands free kit to make and receive my Phone calls.
About a month ago my bluetooth started acting weird. When I'm in my car and want to make a Phone call, it starts the call on my Phone but then my car says that something went wrong and the call couldn't be initiated, although the call is continued on my phone. I do receive my text messages on my car and can also sent them but I'm unable to make/receive Phone calls.
When I receive Phone calls, they don't come up on my cars media. However, my Phone says its using Bluetooth for the call and the bluetooth connection is up. When I'm having this issue, I can not disconnect the Bluetooth connection with my car on my phone. It refuses to disconnect and I can not switch to any other Bluetooth device. The same goes when I'm having the issue while connected to my other Bluetooth hands free kit. In the advanced bluetooth settings of the bluetooth connection on my Phone, I also noticed that when the issue occurs all Bluetooth functionality is checked (eg. 'Media audio'), except 'Phone audio'. 'Phone audio' is not checked and it refuses to check it (however it's not greyed out). When I tap on 'Phone audio' in order to enable it, you see it getting checked for like a few microseconds and then it instantly gets unchecked again.
The only remedy I found is to power off and start my Phone again. Very frustrating if you want to make a quick Phone call and that you have to wait 5 minutes each time or if someone is trying to reach you but they can't hear you and they keep calling back while you try to press the power off button and drive your car . Why do I even have Bluetooth .
I've noticed that when I keep my Phone powered on at night and let it charge, the issue is present. If I recharge my Phone while it's powered of, pull out the power plug and then power on the Phone, there is no issue.
It seems to me that it has something to do with the update process...
Any idea how I can solve this issue?
Previously I did had other bluetooth issues like sudden switches between the phone's speaker and the bluetooth hands free (without any clear reason), it would just switch the bluetooth audio off and on again. So imagine, I'm calling someone with my hands free kit and suddenly the sound is gone. I grab my Phone and hear the other person talking, I continue the conversation using my phone's sound, then the sound is gone again and I need to continue with my handsfree. Other times when the phone said it was using bluetooth audio, it actually wasn't and I had to select 'Phone speaker' and then bluetooth audio again to get audio via bluetooth.
I don't think it has got anything to do with my car's bluetooth or my handsfree because the handsfree works flawlessly with my laptop and the car's bluetooth also works perfect with my partners Phone.
I have the same problem as you and i've never found a solution someone could help us please
Anyone?
Xsaron said:
Anyone?
Click to expand...
Click to collapse
So basically since the December security update that was released in February? Yeah, we know... some people seems to have issues with Bluetooth since then, but some people don't, not sure exactly why. In the Lenovo support forums there is even some mention of Bluetooth issues (although they come short of admitting there is a problem) on the latest update.
If a factory reset doesn't cure it, then you just have to wait... we don't have the factory firmware images for the latest release to reflash and downgrading is a questionable solution at best. Hopefully the factory images become available or the Nougat update actually gets released and one of those fixes it.
Sorry, that's the best I have for you... which is basically nothing.