I have the Galaxy Tab 7.7 (p6800).
When I have my stereo bluetooth headset connected, the sounds for Phone Ringtones, Notifications and the Text-to-Speech reader (reads your texts to you) all come out of the tablet speaker and the bluetooth headset.
I'm looking for a way to disable the tablet speakers either manually or automatically when connected to bluetooth.
Would placing a bounty of say $50 be enough to be worth someones time to create an App that does this? If so, is there a process I need to follow to set up the bounty?
Thanks
Is $50 enough to develop a custom application?
No, but it would be a nice reward, and may get someone thinking about a profitable application they could submit to the Android market.
Turning off the internal speakers when connected should be part of the Bluetooth driver options.
Good place to look would be Android Market - look up "Bluetooth Switcher", and maybe contact the developer. That app looks like mono only currently.
Robert
Note: This seems to be a problem that some people see when using Wired Headphones, as well
Issue 16667: Notifications are played through external speaker when headphones are plugged in (http://code.google.com/p/android/issues/detail?id=16667)
Would that be driver related also?
First post here, so apologies and let the flaming begin but I am trying to determine if my Nexus 4 "issues" are unique to me or normal for this phone.
1. Issue #1 - Bluetooth functions only for numeric dialing, no voice (say name phonetically) dialing or other voice actions seem to work. You can speak the numbers you wish dialed and that's about it. Maybe others can confirm whether this is unique to me. Android ver 4.2.1. Using with a Sena SMH10 bluetooth motorcycle headset
2. Minor issue, but also related - I can not use a stereo headset with my phone and expect the handset mic to work. Something that simply works in every other smart phone I've owned. You plug in a stereo headset (3 conductor earbuds only, not 4 conductor with mic for example) and the phone ideally recognizes the lack of 4th conductor and sends output audio to headphone while using handset mic. So, if you wish to make a call, you can do so. And if you wish to communicate with your phone using verbal commands you may do so as well. You may get "some" functionality using a 3 conductor headphone, however try making a call to someone and it simply doesn't work.
I don't think my phone issues are unique, but perhaps I got a lemon? Nexus support can't seem to confirm whether or not its a known issue.
Anyone else have these "features"?
Thanks in Advance.
Issue #1. Confirmed hands free dialing works over Bluetooth using blue ant s4. In fact I was excited they actually reworked the voice dialer to be accurate!
Sent from my Nexus 7 using Tapatalk
Well that's certainly weird. The headset I am using lists the following profiles:
Key Specifications:
• Bluetooth v2.1+EDR, Class1
• Supporting profiles: Headset Profile, Hand-Free Profile (HFP), Advanced Audio
Distribution Profile (A2DP), Audio Video Remote Control Profile (AVRCP)
The Settings tab of this headset in my Nexus say it is paired for:
-Phone Audio
-Media Audio
I have paired/unpaired and reset bluetooth device to factory.
This headset worked flawlessly with my previous phone, an HTC MyTouch 4G running Android 2.3
When i attempt a call, I get a prompt from the phone "Voice Dialer" that says:
"Say Call, followed by a name or a number"
If i speak the numbers to dial, it works perfectly. If I say the name of any person in my google contacts list, it balks and exits right away, sometimes saying "Sorry, I didn't catch that"
HF Dialing has been horribly broken in Android for some time. You might try disconnecting it from A2DP to see if that helps. For me, since I use a moto headset, I went with Motospeak and it works pretty well.
chas4android said:
2. Minor issue, but also related - I can not use a stereo headset with my phone and expect the handset mic to work. Something that simply works in every other smart phone I've owned. You plug in a stereo headset (3 conductor earbuds only, not 4 conductor with mic for example) and the phone ideally recognizes the lack of 4th conductor and sends output audio to headphone while using handset mic. So, if you wish to make a call, you can do so. And if you wish to communicate with your phone using verbal commands you may do so as well. You may get "some" functionality using a 3 conductor headphone, however try making a call to someone and it simply doesn't work.
Click to expand...
Click to collapse
This works fine for me. I've used it a number of times in the car, where I have a stereo cable to an FM transmitter, and I just tested it with a no-microphone set of headphones: my voice went through the phone microphone with no problems.
chas4android said:
Well that's certainly weird. The headset I am using lists the following profiles:
Key Specifications:
• Bluetooth v2.1+EDR, Class1
• Supporting profiles: Headset Profile, Hand-Free Profile (HFP), Advanced Audio
Distribution Profile (A2DP), Audio Video Remote Control Profile (AVRCP)
The Settings tab of this headset in my Nexus say it is paired for:
-Phone Audio
-Media Audio
I have paired/unpaired and reset bluetooth device to factory.
This headset worked flawlessly with my previous phone, an HTC MyTouch 4G running Android 2.3
When i attempt a call, I get a prompt from the phone "Voice Dialer" that says:
"Say Call, followed by a name or a number"
If i speak the numbers to dial, it works perfectly. If I say the name of any person in my google contacts list, it balks and exits right away, sometimes saying "Sorry, I didn't catch that"
Click to expand...
Click to collapse
I understand your frustration. Hands free dialing is a feature I don't like to do without. After jumping to jellybean from ICS on my fascinate handsfree was horrible.
When I set up my blue ant with any phone it goes through a "transferring contacts" part of the setup. Perhaps this is why it can recognize the peoples names and not just the numbers.
Does your headset "transfer contacts" like the S4?
Sent from my Nexus 7 using Tapatalk
No, the headset is strictly a phone headset as far as that goes. Not a sync device like some cars, etc. In that case, it might work since dialing could be handled by the Bluetooth device?
I'm no expert, but relying on the nexus dialer seems to be the issue. What baffles me is that when not using Bluetooth and using the Google voice search, it actually works. If pressing the "pickup/hangup" button actually launched Google voice actions... It would solve the problem as well as give me further hands free operations such as nav and music control.
Anyone know how to make that action occur with Bluetooth button?
As for #2, I actually called nexus device support, and while speaking to the rep plugged in my skull candy ear buds. He confirmed that mic sounded extremely garbled and not understandable. These same ear buds world fine on my old my touch and my girlfriends iPhone. Both of those phones recognize them as basic stereo headphones and keep the handset mic intact.
I'm going to call them back and just get a replacement today. Screen has done the flicker/vertical lines thing now at least once too.
I'm having bt issues with my car stereo. It's after market that worked fine with my GNex. I can pair it with the N4 and it shows Phone Audio, but then after a few seconds disconnects. Could bt be bad on my N4? I normally have the headphone jack plugged in through aux and can take calls that way, but I'd like to get bt working again.
Update: after powering off the stereo and powering it back on it seems to be connecting ok
Lttlwing16 said:
Issue #1. Confirmed hands free dialing works over Bluetooth using blue ant s4. In fact I was excited they actually reworked the voice dialer to be accurate!
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Just checked... Blue ant uses its own voice recognition to pair contacts with numbers and thereby bypasses phone voice dialer. That's why it works for you.
I just got a SMH10 as well. I am able to voice dial okay as well as use google music, what I don't like is no access to Google Now without handling the phone (which would require me to stop and get my phone out of my pocket). Not sure if this is an issue with the SMH10, or with android 4.2.x.
I know it's been over a month since you posted in here, curious about your usage and if you have found any tricks to get google now to work in place of the voice dialer only. Since google now should handle voice dialing I am hoping to get that to work so I can also use the navigation when needed.
Sending a note to Sena as well to see if they have a solution as well.
Hands free out-calling issue
As of last week the bluetooth hands free calling feature was working fine on my Nexus 4. A couple days ago I went to call out using the hands free, and the display on my car stereo went blank for a few seconds and came up saying 'Not Supported'. I can receive calls fine, but for whatever reason the hands free voice recognition doesn't want to open when I ask it to now. Anyone have a similar problem?
ssj4kevin said:
As of last week the bluetooth hands free calling feature was working fine on my Nexus 4. A couple days ago I went to call out using the hands free, and the display on my car stereo went blank for a few seconds and came up saying 'Not Supported'. I can receive calls fine, but for whatever reason the hands free voice recognition doesn't want to open when I ask it to now. Anyone have a similar problem?
Click to expand...
Click to collapse
I've had exactly the same thing happen. Weeks and weeks of working voice dialing through my Blueant S4. Now, it doesn't work at all. Incoming calls can be answered, but I can't dial out by voice.
Is this just broken completely?? The forums are loaded with questions about people trying to get voice dialing or voice search working with their bluetooth devices (headsets, car radios, etc.).
I just bought and installed a new Pioneer headunit for my vehicle and the bluetooth is FANTASTIC with the one glaring exception that I can't do any voice command through my car microphone.
I see a couple of different apps (one is chinese..?) on the play store that seem to imply they fix the problem (see below)
https://play.google.com/store/apps/details?id=com.lukasoft.android.voicecontrol&hl=en
I am super confused. Do I need a custom ROM or some special app just to enable the siri/eve/google voice or whatever to work in my car?
Isn't using hands-free bluetooth in your car (asking about the weather, asking for navigation directions, etc.) kinda the whole point of having bluetooth in the first place?
Is this just an oversight by google or am I missing something obvious?
When Google first added voice dialing via Bluetooth a couple of years ago, they said that the data rate over the Bluetooth connection was too low to use with their normal voice recognition algorithms -- while they could handle the limited vocabulary for voice dialing with the Bluetooth data, they needed a higher bitrate for full voice recognition. I don't know if that's still the explanation or not, as I haven't heard anything about it since those early days.
nyvram1 said:
Is this just broken completely?? The forums are loaded with questions about people trying to get voice dialing or voice search working with their bluetooth devices (headsets, car radios, etc.).
I just bought and installed a new Pioneer headunit for my vehicle and the bluetooth is FANTASTIC with the one glaring exception that I can't do any voice command through my car microphone.
I see a couple of different apps (one is chinese..?) on the play store that seem to imply they fix the problem (see below)
https://play.google.com/store/apps/details?id=com.lukasoft.android.voicecontrol&hl=en
I am super confused. Do I need a custom ROM or some special app just to enable the siri/eve/google voice or whatever to work in my car?
Isn't using hands-free bluetooth in your car (asking about the weather, asking for navigation directions, etc.) kinda the whole point of having bluetooth in the first place?
Is this just an oversight by google or am I missing something obvious?
Click to expand...
Click to collapse
I'm pretty sure the voice commands you want aren't part of google voice/NOW yet as its still in early development. I know it can't play music from your phone by voice command so I don't see it being able to play through bluetooth either. Also you have to use Google Now directly through the phone. Not sure if you can have it start up by voice recognition, there is an app that does that though but its another separate voice recognition app and I believe you need to have the lockscreen turned off to have it actively listening for voice commands. Not sure if Google Now can even do that yet. Its pretty limited to what it can do right now.
http://www.androidauthority.com/how-to-setup-configure-and-use-google-now-98749/
Found the other app its Dragon, from Nuance, they did speech to text apps for windows a long time ago.
https://play.google.com/store/apps/...1bGwsMSwxLDIxMiwiY29tLm51YW5jZS5iYWxlcmlvbiJd
kzoodroid said:
I'm pretty sure the voice commands you want aren't part of google voice/NOW yet as its still in early development. I know it can't play music from your phone by voice command so I don't see it being able to play through bluetooth either. Also you have to use Google Now directly through the phone. Not sure if you can have it start up by voice recognition, there is an app that does that though but its another separate voice recognition app and I believe you need to have the lockscreen turned off to have it actively listening for voice commands. Not sure if Google Now can even do that yet. Its pretty limited to what it can do right now.
http://www.androidauthority.com/how-to-setup-configure-and-use-google-now-98749/
Found the other app its Dragon, from Nuance, they did speech to text apps for windows a long time ago.
https://play.google.com/store/apps/...1bGwsMSwxLDIxMiwiY29tLm51YW5jZS5iYWxlcmlvbiJd
Click to expand...
Click to collapse
dragon seems like it might work..but i'm not sure about the 'driver mode'. does that use the car's mic or is it still listening from the nexus 4 itself?
iow, i couldn't really have my phone charging in the glovebox and still have hands-free discussions about the weather and tell it to call people
nyvram1 said:
dragon seems like it might work..but i'm not sure about the 'driver mode'. does that use the car's mic or is it still listening from the nexus 4 itself?
iow, i couldn't really have my phone charging in the glovebox and still have hands-free discussions about the weather and tell it to call people
Click to expand...
Click to collapse
Not sure on the driver mode but most of these things just work off the phones mic for now. I didn't use dragon too long as it was a battery hog when I tried it. The driver mode I would assume is for when you have the phone in a docking station or cradle in the car and are using it as your navigation device. I don't think it can open too many apps either but just do the basics like Google Now but its been over 8 months since I tried it. I liked it as it had the feature to wake the phone by voice command.
I have had several different cell phones over the years, pre and post-smartphone. They have all been different brands. I also have used a Bluetooth earpiece from the time they became available. The Bluetooth's I have used have been made by different companies too. Regardless of who manufactured the phone or the Bluetooth earpiece, they have all worked exactly the same way. The way they work this way is so that when you are around others or are in a quiet place any audio is only played through the BT. This way you do not disturb others around you. Steps below:
1. Pair BT device to phone.
2. Connect the phone to the paired BT device.
3. Place the BT device in your ear.
4. Now that the phone is paired and connected to the BT device all of the audio is rerouted directly to the BT device.
5. If a call is ringing the phone or you receive a notification from any app, the sound is ONLY played through the BT device.
6. This works as described above even if you have not turned off the phone's speaker.
In October 2015, I purchased a Samsung S6. Supposed to be the best, right? WRONG! There isn't much that I like about this phone but that is for another thread. With the S6 BT works like this:
1. Pair BT device to phone.
2. Connect the phone to the paired BT device.
3. Place the BT device in your ear.
4. Now that the phone is paired and connected to the BT device all of the audio is routed to the BT device AND the phone speaker.
5. If a call is ringing the phone or you receive a notification from any app, the sound plays on the BT AND the S6 speaker. Music does appear to play through only the BT. However, videos with sound also play through both the phone speaker and the BT.
6. If you mute the S6 you don't get audio ANYWHERE. If the S6 is set to vibrate then the phone vibrates and most of the time you don't hear anything in the BT either.
What the f*** is up with that? I have spoken to multiple people at different support levels of at Samsung and some of them say that is the way it is supposed to work. The others say that it ISN'T supposed to work the way it does. Those people generally blame the BT device. I have tried 4 or 5 different brands of BT devices and they ALL work as described above on the S6. No one seems to know what the real answer is!! Can anyone tell me why you would bother with a BT if you are going to hear the sound on the phone speaker also and disturb others around you, say for instance in a meeting? OR does anyone know how to make this work as a BT should or know a brand of BT earpiece that works with the S6. I am on calls all day long and need my BT to work correctly. In a cube environment, others do not always enjoy hearing your special ringtone or notification sounds. PLEASE HELP ME SOMEBODY! PLEASE, PLEASE, PLEASE I AM BEGGING YOU. I have so many issues with this phone that I want to smash it with a hammer until it is nothing but tiny bits of metal, glass, and plastic. IF Samsung is reading this your phone is a very expensive piece of Sh**!!!! Your tech support department is the worst that I have ever encountered for any product.
I have a use case that seems pretty basic but I can't find a solution for. The watch is non-LTE, so it's bluetooth/wifi to the phone. If I use Google Assistant to start a call via the watch while my phone is in my pocket, the call takes place on the phone but it always chooses the watch as the audio device when I'd like it to use the default (e.g. the bluetooth handsfree in my car). A while ago I was able to force this to happen by disabling calling in the bluetooth pairing on the phone - assistant would start the call but the watch wouldn't be seen as a device for the call audio. Some recent update has changed this behaviour, however, and now the watch flat refuses to start the call unless this is enabled on the peering. If it's enabled, the phone will always choose the watch as the audio device.
Is there any way to get this working? This is a Samsung Galaxy Watch 4 running Wear OS 3.5, system version 11. The phone is a OnePlus 7 Pro running Lineage OS 18.1 (Android 11)