Thought this was just me to. Happening here to. Makes me wish they could get google maps to open in driving mode as an alternative.
Waze on startup.
Bananarama Yes, I noticed if I turn car off like filling up with fuel, waze will work straight away when turning car back on.
You can try using automated tasks to delay the start of waze.
Don't let it follow the system startup
Same problem here: When Waze starts it has no roads showing on my DUDU7.
I share my WIFI from my phone.
WAZE NOT WORK:
My phone share Wifi when it connects to DUDU7's bluetooth.
When DUDU7 boot up and Waze start - It have not yet got the WIFI connection.
= Waze not working.
WAZE WORK:
Before i go to car, I turn on Wifi sharing.
When DUDU7 boot up it have wifi direct and Waze work without any problem.
I hope there can be a fix for this!
I already wrote before: Start Waze via a Task, but use a 10-20 seconds delay. Then the WiFi is enabled. Please read the posts before your post.
- Edited
I must admit that I don't know. I use Google Maps and Magic Earth in my main PIP (depending the reason for my travel). I also start my phone hotspot upon the bluetooth connection between my phone and my unit.
Both google Maps and Magic Earth have no issues. There is some cached map data and GPS simply works, and after some seconds, after WiFi connection, they both do work over WiFi and use WiFi.
They are "auto correcting" on WiFi.
dogsfoot I have Waze setup to start on startup on Mekede Dudu7 head unit and sometimes it starts with no roads showing on the screen and no internet connection.
Does Waze not auto-correct? I consider that a bug. What if your phone currently doesn't have internet? Is Waze also empty and does it not auto-correct once WiFi or your data is restored?
Edit: Waze doesn't have offline data as it is completely cloud-based, but it downloads map tiles from the last route. If you start from the last position, it must show that cached map tile(s). If it is empty, this cached data is obviously removed.
surfer63 I already wrote before: Start Waze via a Task, but use a 10-20 seconds delay. Then the WiFi is enabled. Please read the posts before your post.
First: If I buy an Android unit for 500€ - I want one of the most used navigation app like Waze to work - without having to learn user made scripts with tasks to make it work. I have another 200€ unit and Waze work on that.
Maybe it’s some config in DUDU7 or Waze have a bug - I don't know, But I hope it will be fixed.
I read your statement it could be fixed with tasks. For me, that not the permanent solution, just a temporary fix. That's why I wrote, to clarify how the problem was in my setup.
My layout in DUDU7 is the 3 Apps you can have side-by side, One of them is Waze.
I been looking at Tasks today. I try make something like this:
Add Task:
Trigger Conditions: System Boot
Delay: 6s
Action to be Performed: Open the APP
The APP Associated with the Event: Waze
It makes a delay, but then open Waze over the hole screen. Not as one of the 3 apps.
How do I make the task?
Dan-LS It makes a delay, but then open Waze over the hole screen. Not as one of the 3 apps.
How do I make the task?
I mentioned one post up that I don' t know.
I now agree this is a dudu issue.
I installed Waze on my phone and opened it. After the necessary "allow this and that" I got a map and could scroll the map.
Then I closed Waze, deactivated Wifi and data, and restarted Waze. In that case I do have quite a big map tile.
If Dudu doesn't do that, it is indeed a dudu issue.
It should just work.. Should not need tasks etc....
Come on Dudu, fix this issue....
Waking the car from hibernation Waze starts before the car is connected to the Internet and has problems.
If you restart the car and turn it on, there's no problem with Waze following the picture-in-picture mobilization, is that right?
- Edited
I assume that when the nokill would work correctly, you could also add Waze to the nokill list. In that case it would not be re-initiated coming out of deep sleep and thereby losing its cache data.
But nokill doesn't work (yet?) for PIP apps.
Is it because the machine wasn't connected to the internet when Waze started?
Or is it because of the hibernation wakeup?
I've the same problem so this is a major problem which Dudu should consider to fix a.s.a.p.
chosan
Don' t say you have the same problem.
Describe your exact problem. Then the developers can hopefully do something about it.
Below some scenarios. Please answer and please describe if there are still other scenarios.
Waze on reboot in PIP window without WiFi (not active yet) -> Is Waze empty or does it used cached data from last trip?
Waze on reboot in PIP window after WiFi has established -> Is Waze functioning normally (again)?
Waze after deep sleep/hibernation in PIP window without WiFi -> Is Waze empty or does it used cached data from last trip?
Waze after deep sleep/hibernation in PIP window after WiFi has been established -> Is Waze functioning normally (again)?
If Waze is manually started full screen after reboot, but without WiFi -> Is it empty or does it used cached data from last trip?
If Waze is manually started full screen after deep sleep/hibernation, but without WiFi -> Is it empty or does it used cached data from last trip?
I tested some stuff and the way it works for me as a temporary workaround:
Waze starts automatically as primary PiP/Nav App > gets killed by tasker 5 secs after boot > Waze starts again using the "Tasks" function in Dudu Settings "Other" 7 secs after ignition.