route to speaker goes to the phones speaker, and works for me on my nexus 4.1 jellybean
yeah try the troubleshooting above, mostly deleting the waze folder after uninstalling and re-installing
after that, find a friend that has an android device and waze and hook it up to your car and see
otherwise might need a support ticket
I know that it’s worked for me on the previous beta that way. I don’t think I tested the route to speaker option in the most current beta. What I usually do if I switch from listening to Google music to the radio is turn the Bluetooth off on the phone so it stops the streaming connection
Sent from my SPH-L710 using Tapatalk 2
I did the uninstall \ reinstall today and will test on my way home. I did verify that the “route to speakers” works as expected with headphones…when I have my headphones plugged in and check the “route to speaker”, I hear it on the phone’s speakers and when it’s not checked I hear it through the headphones.
So I confirmed the behavior. I’m still not getting the sound with the phone connected to BT, but when I turned BT off on my phone I could here it.
Does anyone know how I got about submitting this to support? I can’t find how to do that.
type in for previous matches, when it doesn’t find any or you say it didn’t help, there is an option to email support
i’d be sure to include your car type as it’s something with the bluetooth on your car and or your phone
I have had a similar problem. I found that directions would play through the phone speaker when ‘prefer bluetooth’ was checked. However when I set both ‘play sound to phone speaker’ AND ‘prefer bluetooth’ OFF, the sound is routed to the bluetooth speaker. Odd!
Prefer BT only really means it will use the phone connection to the car stereo instead of bluetooth streaming. Prefer BT also means it will accept voice commands via BT headset/car connection.
With Speaker and prefer BT off, if your phone is paired with a streaming device, Waze will still use it. Not sure if that’s because of the OS, hardware or Waze, but that’s the way it works. Waze hasn’t implemented, on iOS for example, the standard audio output selection mode that every other app in the world uses…
I e-mailed support about this a couple of weeks ago, and still haven’t heard anything. Does anyone know how long it takes for them to respond?
I have a Samsung Galaxy S2 with Android 4.0.4, waze 3.5.1.4 and a Mazda 3 with BT and the only way to get a voice from waze is to switch off BT at my SGS2. Even if i switch to voice over speaker does nothing. In this case I see also if I press the volume keys that my phone still tries to output the voice over BT.
I finally heard back from support. They’re looking into it so hopefully I’ll have something to report at duke point. They made it sounds like they will be working on a code fix for it.
I’ve been having some confusion with bluetooth audio myself. When I’m streaming music via BT off of my phone, Waze does the following:
Route to Speakers off: Waze meekly talks through the music without turning it down/pausing it, and is largely unintelligible.
Route to Speakers on: Waze pauses the music to… say nothing at all.
Prefer Bluetooth: Doesn’t exist. Route to Speakers is the only thing in there.
This is one of the relatively few things other GPS apps seem to have a leg up on, so it’s frustrating to see such minor imperfections chafing at the experience.
It’s not “route to speakers” but “route to speaker.” This means the internal phone speaker. It could be that audio volume settings for the speaker are set very low? Waze is supposed to duck the currently playing audio. With “play to speaker” on, it will pause the music. That is how it is designed.
Prefer Bluetooth will appear if your phone and car/device have the bluetooth “phone” connection available.
Posting your hardware/software info is always helpful.
Isn’t the Prefer BT an iOS only option?
I honestly do not know. Why would this be an iOS-only option? (semi-rhetorical question)
In my case, with “Route to speaker” off while streaming music, I can hear the directions just fine. But I also just hear a pause in the music with “route” turned on. If I turn off BT on my phone I can hear the directions just fine over the phone speaker.
Support said that the ticket I had opened with them had been submitted to deveolpment, but still no word.
Regardless of why, it starts to appear it may be. As for hardware, I’m running a Galaxy S3 (T999). The behavior seems to have changed though. Route to Speaker now causes the music - and directions - to suddenly snap to the phone speaker rather than bluetooth speakers when directions are given. Their volume is unchanged.
The new beta version for android lowers media volume while giving directions
Sent from my SPH-L710 using Tapatalk 2
Hi @ all,
Joining your forum for the first time, I’m having exactly the problems you are discussing. I am using a Samsung GT-S 7562, also called Galaxy S Duos. “Duos” stands for Dual SIM and I am using that kind of Samsung Phones since the days of SGH-D 880.
The Samsung runs on Android 4.0.4. My car is a Volkswagen Golf Variant, I think you call it Jetta Wagon in the States. It is equipped with a Radio, which is called RCD 310 here and with a Premium Bluetooth Kit (VW Phone).
This works together well when it comes to telephone audio and media audio via BT and it struggles a little with Phone Book Application Protocol (PBAP), but this is a known issue and I had it already with the previous phone.
I got to know Waze occasionally and I think I like it a lot. I first of all fully agree with what Venatius writes:
I do not have a “Prefer Bluetooth” button on the “Sound” page
I do have a checkbox “Route sound to speaker” on the “Sound” page
If I check the box “Route sound to speaker” and the Galaxy is not connected to VW Phone telephone audio and media audio in the car, the prompts are coming via the phone speaker.
If I check the box “Route sound to speaker” and the Galaxy is connected to VW Phone telephone audio and media audio in the car, no prompts are coming via phone speakers but if I have the Galaxy MP3 Player on, the music is interrupted wherever a prompt should be.
If I do NOT check the box “Route sound to speaker” and put the BT-Audio of the car on, I hear the prompts via the car VW Phone media audio, but if the MP3 player is on as well, I hear music and prompts simultaneously as the music is not paused. So I cannot understand the prompts.
Principally all this makes perfect sense and is not a bug so far. As Alan rightly says, Waze is probably meant to work like this. The user shall usually keep the box “Route sound to speaker” checked. And as some of you can see with iPhones the sound is now meant to go via the telephone audio and not via the media audio. At the same time MP3s are interrupted in order not to miss anything.
This way has the huge advantage that you can listen to the regular radio and get the prompts. You even can leave the radio off and the prompts will come through.
The disadvantage is it does not work with Android 4.0.4. The prompts don’t come via VW Phone telephone audio. I have tried it all but I have no idea what’s up. Maybe I have forgotten to get a setting right but I am afraid that the usage of BT telephone audio service under Android 4.0.4. is buggy indeed.
I would be grateful for recommendations to get this solved. I will post this report also as a ticket to support.
Regards from Germany
Hubert
EDIT: Yesterday evening we tried the same with my wife’s Galaxy S III, running on Android 4.1.1. Exactly the same effects… Interesting by the way: The S III can connect via Remote Sim Access Protocoll (RSAP), which means that the car borrows the SIM from the cellphone and establishes the telephone connection on own hardware. At this moment the cellphone looses network connection and cannot do Internet anymore, which causes Waze to show “Searching Network Connection” and to be unable to calculate the optimum route. Is this the same with all smartphone navigations or Waze specific?
AND… I learned in the FAQ that Waze wants us NOT to check the “Route Sound To Speaker Option”. So my theory that they want to send the prompts via the telephone audio seems to be wrong. They want to send them via the media audio.
In that case you cannnot hear regular radio and you cannot leave the radio off. But then they really have a bug as they should at least stop the MP3 player when it is in use as long as the prompts are announced, like they do, when the box is checked.
Bottomline: The BT subject still needs some attention…
Regards
Hubert
So my issue is somewhat similar, somewhat different but relates to Bluetooth and speaker so I thought I would put i there. I am using an iPhone 4S with a Jabra Tour Bluetooth speaker and this combo works great for phone calls and for streaming podcasts etc. When I use it with Waze, it sort of of works. Pretty much anytime I launch Waze and choose to Navigate somewhere it starts off working fine, let’s go and all that happy stuff. Then at some point in the drive I just stop hearing turn by turn voice commands and even I stop navigating and restart, no luck, turn off and then back on the Tour speaker, no luck, but if I “switch off” and then come back in to Waze and resume navigation it starts up again with the voice prompts. The strange thing is sometimes it will go 5 minutes and then stop the voice commands, sometimes will go 30 minutes before I lose them. Also, I have tried to find a pattern, is it after a call, at a certain point in the route, etc and I can not find any correlation between the times that it stops working, it seems totally random. Has anyone else experienced anything like this with Bluetooth?
Android users; to achieve what you want (hear directions when radio is off/listening radio) you should try an app on Google Play called “AudioBT”, this uses the Bluetooth incoming call channel for routing audio from any application.