More arrows please
Lifetime Premium Member
- Jan 27, 2019
- Reaction score
- Seattle area, WA
Good point. I hadn't thought about interfering with navigation. There's already an alert speed threshold built-in so that would solve that issue for urban driving at least.I really like this idea, thanks a lot! It is also important, however, to avoid it going to the foreground on some tough intersection while GPS is guiding you through it. Probably doing it only while you're going above low-speed muting threshold should help with avoiding such cases.
LEO was roadside with a customer.Hm, that is strange. Was the LEO actually there? Maybe that was an old stale alert that already went away from the app but was still in the Waze application.
Sometimes I get the feeling Waze doesn't show marked locations on opposite sides of the road. Could this have been the reason ?Just installed and used it for a 30 mile trip. Daze alerted to a LEO but nothing popped on the app for that particular LEO. I did, however, see 2 alerts in the app for 4+ and 9+ miles away.
Increasing update rate even further is an easy way to get blockedI run VVaze 2-4 hours per day on average.
Generally it will show icons for other side LEOs but it won't alert you.
The data stream contains both sides as long as it's updated before you arrive at the location.
I'll bet this is the entire scenario for what LuCroix experienced. VVaze updated in that window between the report and arriving at that location while the app hadn't yet.
There's nothing that can be done about this rare situation except increase the polling rate in the app.
Tbh I'm not too worried about the map displaying for me. I already have my Android radio (very annoying to use with Waze and doesn't support Bluetooth for apps and messes with other things like my contacts and shuts off music if Waze alerts) for music, and Waze as my primary navigation app for my phone while it's connected to TMG remote. Waze split screen sucks on my phone so I avoid it. So if no one else has an SDK that low, I can live with the current setup.I'll check if I can work with this version but adding a map display with support of this version might be tricky. I'll check what can I do here.
On my S8 and Android Studio emulators there are not issues with font, hope to push this today. Thanks for feedback btw =)This is absolutely brilliant. Can't wait to try it out this weekend on the highway
You have a previous version of the app which doesn't have this bugSpeed looks ok on my Note 8