Andrey (Sapozhnik)
My feedback
8 results found
-
92 votesAndrey (Sapozhnik) supported this idea ·
-
12 votesAndrey (Sapozhnik) supported this idea ·
-
152 votesAndrey (Sapozhnik) supported this idea ·
-
322 votes
Hi all,
Thank you for voting for this suggestion!
We’d like to know if this is still relevant, or if the issue was solved through auto-complete for prioritized Waze addresses.
Please let us know in the comments if it was, so we can close the suggestion.
Thanks!
-StaffAn error occurred while saving the comment An error occurred while saving the comment Andrey (Sapozhnik) commentedWe have a lot of streets which were renamed last several ears but anybody changed them in Google. We have a multilanguage search which correctly understand google but doesn't understand Waze at all. We have long names of street which don't work correctly in Waze.
Everything it can be solved by linking RPPAndrey (Sapozhnik) shared this idea · -
82 votesAndrey (Sapozhnik) supported this idea ·
-
259 votesAndrey (Sapozhnik) supported this idea ·
-
706 votes
An error occurred while saving the comment Andrey (Sapozhnik) commentedI think user can choose
- optimal (like present)
- short (without real-time statistics)
- fast (only real-time statistics)Andrey (Sapozhnik) supported this idea · -
12 votesAndrey (Sapozhnik) supported this idea ·
Auto-complete was broken several years ago and doesn't work correctly at all.
Bugs in center code ware opened but still ignored.
Auto-complete doesn't solve problems of incorrect data from google