Steven
My feedback
41 results found
-
66 votes
“Ok Waze” was replaced with Goggle Assistant which allows for voice search, voice reporting and much more!
An error occurred while saving the comment Steven
supported this idea
·
-
12 votesSteven
supported this idea
·
-
87 votes
Thank you for your suggestion. We will add this voice request to our User Request wish-list.
Steven
supported this idea
·
-
8 votesSteven
shared this idea
·
-
4 votes
An error occurred while saving the comment Steven
commented
Perhaps that could be an option, but it shouldn't be the only way of doing it. It's one thing for me to tap a couple big buttons on the screen while driving (I have my phone on a dash mount, so I can do it while still keeping an eye on the road, and it's less of a distraction than messing with the radio). But to look at a map and try and figure out the exact spot something is would be too distracting. It doesn't have to be perfect, but placing it like I suggested would make it a lot more accurate than it already is. A better way to do it based on your suggestion would be to allow other drivers to correct the position, so somebody driving could report it and have it be close enough, but somebody riding as a passenger could come by and move it to a more accurate location.
Steven
shared this idea
·
-
2,264 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
An error occurred while saving the comment Steven
commented
@Anonymous - Not at all surprising since Waze is owned by Google, and they're notorious for ignoring big issues for years. When they bought Waze, I knew it was going to go downhill, and so far, it seems I was right.
Steven
supported this idea
·
-
272 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
An error occurred while saving the comment Steven
commented
That's only possible with root, and neither root nor the inconvenience of having to go through and mess with that should be required when the developers can simply add a volume for it and/or option to disable it (I know you're not saying it's a reasonable fix to the problem but rather a workaround that at least allows some users to solve it, so not criticizing you, but rather the development team).
An error occurred while saving the comment Steven
commented
I don't even necessarily want to mute it, but there needs to be an option to turn the volume of the recalculating beep down. It's far louder than the warnings and other audio from the phone like podcasts and is literally painful.
Steven
supported this idea
·
An error occurred while saving the comment Steven
commented
I don't even necessarily want to mute it, but there needs to be an option to turn the volume of the recalculating beep down. It's far louder than the warnings and other audio from the phone like podcasts and is literally painful.
-
478 votesSteven
supported this idea
·
-
3 votesSteven
supported this idea
·
-
1 voteSteven
shared this idea
·
-
6 votesSteven
supported this idea
·
-
6 votesSteven
supported this idea
·
-
254 votes
An error occurred while saving the comment Steven
commented
Allow the buttons and speedometer on the main (GPS) screen to be moved to custom locations (with lock/unlock setting to make sure they're not moved accidentally during use).
Steven
supported this idea
·
-
17 votes
An error occurred while saving the comment Steven
commented
It would have to be individually customized. If you have it reorder based on a particular region, then going from one region to another would cause it to change and would cause significantly more problems.
-
245 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
Steven
supported this idea
·
-
341 votes
We plan to work on Quick-report presets in the near future. In the meantime, make sure you’ve got the latest version of Waze for all the latest features.
Steven
supported this idea
·
-
4 votesSteven
supported this idea
·
-
3 votesSteven
supported this idea
·
-
84 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
Steven
supported this idea
·
An error occurred while saving the comment Steven
commented
I don't even necessarily want to mute it, but there needs to be an option to turn the volume of the recalculating beep down. It's far louder than the warnings and other audio from the phone like podcasts and is literally painful.
-
15 votesSteven
supported this idea
·
An error occurred while saving the comment Steven
commented
Only thing is I would strongly suggest each alert type be able to be toggled. What would be really great is to be able to set up profiles that can be quickly switched, so you could set one up to only do what you deem are critical alerts and one that will alert for everything (or almost everything), and switch based on where you are.
Many times, including yesterday, when I press the microphone button to use text-to-speech (TTS; text to speech) to navigate somewhere, it says it's updating, which means it's unusable. This means I have to type instead of speak, which is less convenient and less safe. When the user presses the mic button, indicating they want to use that feature, it is NOT the time to initiate an update of it. That would be like if a launcher app decided to update the drawer when you go to open it, basically saying come back later to find and open the app you're trying to use. Update in the background, either when the app isn't being use or once navigation is started, but STOP updating right when I'm trying to use it.