DUDU-Meng As I said the setting you sent me for Waze is not present for TomTom. So no chance to change something there. You can check it for yourself.
For me the Navigation Widget is useless especially for the minimal mode since I don't prefer Google maps for navigation... So I don't bother using it...
As for the problem that was originally discussed with TomTom not starting at the beginning if it's not connected to the internet, personally I have adapted the following solution:
- I have created a task on my phone using Macrodroid to activate my phone's hotspot once my phone losses connection to my wifi. -> That way my hotspot is already activated by the time I arrive at my car in the parking. If I am not at home, I activate it manually before starting the car. (Activating the hotspot once the phone is connected via Bluetooth to DUDU7 is not a good solution because it takes some time-few seconds already-for the phone to connect via Bluetooth.)
- I have configured two more tasks that run in my DUDU7:
2a. The first task launches Radarbot, one second after the screen has turned on.
2b. The second task launches TomTom, ten seconds after the screen has turned on.
That way the WiFi has enough time and has already managed to be connected to my phone's hotspot before TomTom is launched (full screen). So there is no need to start the apps manually. The wifi is connected almost instantly after the screen is turned on. Radarbot is starting first in full screen and then Tomtom is launched second, fullscreen on top of Radarbot. While this happens, Radabot passes to the background, it activates its widget that is placed on top of everything, TomTom included. Thus I have TomTom full screen and the Radarbot widget on a corner on top of TomTom, getting visual and sound notifications about any speed cameras down the road đ
