Waze on startup.
- 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.
- Edited
chosan
The thread start does not describe whether it happens in PIP or not. It says "setup to start on startup": If it is a PIP app, you don't have to mention that. Tasks are setup on startup.
I could go on what has not been mentioned in the first post and "all" the possible other issues that have been mentioned after. That as such is not a problem, but users only saying they have the same issue do not help in specifying the issue. And please note that on this forum all kind of languages by all kind of international users are used.
You have to be specific to not get things lost in translation.
I have very similar problem. Each time I start Waze (pip) without internet connection (I have sim card installed but often I park in underground garage without cellural signal) it takes very long time (like 10 minutes) for Waze to connect to internet. Usually it hangs and it's faster to reboot radio.
If internet is present when radio boot, there is no problem.
In my case (DUDU7 3.5), Waze is in a PIP tile and a SIM card is installed. When waking up from standby, often (not always) the app shows a white map with not much response. The way to reset it is (as others have mentioned), open another PIP app (so Waze loses focus), open Waze from the app drawer, it opens as a black screen, then kill it via task manager. After that when going to the Waze PIP tile again, it restarts and all is good.
Also often when this happens (white Waze map), when trying to access the AC controls app via the floating button (touch assistant), it doesn't open at all. Going through the Car Settings app, then opening the AC app through there gives a result. It's as if the OS is busy after waking up from standby.
Doing a system restart fixes things in all cases.
It`s very annoying having to reboot everytime I start a drive.
The shinny new Dudu headunit is losing is lustre very quickly.
Ich würde langsam mal kontrollieren was in der Fabrik passiert beziehungsweise verbaut wird.
Es kann yoch nicht der Anspruch von DUDUAUTO sein, Geräte zu verkaufen die ständig neu starten.
Versteht mich nicht falsch, ich finde, dassvdas DUDU bisher das beste Radio auf dem Markt ist, aber ich bin kritisch und hinterfrage.