JhonnyD Hi Jhonny, it is actually what I have done. I have totally disabled the Navigation Widget (I am using minimal mode), and I have set up a task that launches TomTom 12 seconds after the WiFi of the Dudu7 is connected to my phone hotspot. That way I have the navigation prompts on the top left correctly. 🙂
I also think that TomTom will not bother to correct this, but neither will the DUDU team, from my understanding. TomTom needs to correct at least the startup bug that holds the app from launching if there is no internet connection. On this topic, when I am in an underground commercial center parking lot here in my town, I don't have internet until I have come up to the surface. So in that case:
- Dudu WiFi still connects to my phone's hotspot moments after I have I have switched on my car.
- Then twelve seconds later, TomTom is being launched by the task I have configured in DUDU.
- TomTom stays at the splash screen with the spinning cycle while I am still underground without mobile data on my phone.
- Once I have exited the parking lot and I am on the surface, after a while, TomTom completes the startup and opens the map.
I tried Sygic also maybe to replace TomTom, which I have in premium too. It runs faster compared to TomTom a tad smoother, I'd say, but the navigation environment of TomTom is way better of any other navigation software. Sygic looks so out-of-dated... In Sygic there is no bug like with TomTom with the next-turn navigation prompts on the top-left when you change from the navigation widget to full screen (they appear in the same place as TomTom).
Waze also has a problem when in full screen... The bottom portion of the screen in Waze is covered by the bottom navigation bar of DUDU OS, so when you want to cancel the route, for instance, you need to hide DUDU's navigation bar so that you have access to the cancel button in Waze.
DUDU-Meng I am not sure that it is Waze or Sygic or TomTom that is the problem. In my previous android headunit, a vertical one, there where also some bugs with the systems taskbars but in different apps. So in that one TomTom and Waze were working perfectly even during resizing of the home screen. Google Maps on the other hand, had a portion at the top of the screen covered by the top application shortcuts bar (that could be hidden). If I hide that app taskbar, I had the full screen of Google maps appeared but there was a grayed out transparent overlay rectangle appearing at the place of the hidden taskbar... Sygic was not being displayed correctly as well; the top half of the screen was blue, like extending the next turn navigation signs.
So, to my understanding, I think that the issues are not really related to the apps themselves that cannot understand the screen layout or resolution, but to the implementation/customisation of the Android ROM of each different headunit... For instance Waze and TomTom could understand that the top taskbar was hidden when I hid it, and they were extending upwards correctly. In DUDU OS, Waze cannot understand the bottom navbar. To me, as this is my second android headunit, it seems that the correct appearance of the apps is a hit or miss and depends on each OS customisation by the manufacturer...
I also have a different problem with a different app with DUDU OS, "Cosmote TV", a greek legitimate paid TV provider. So Cosmote is not allowing the channels to be played in an Android unit that has been rooted for obvious reasons. And guess what? Root Checker tells me that my Dudu7 is not rooted, but the Cosmote TV app tells me that there was a problem during playback because the Android system seems to have altered/modified root permissions. This is to say that, to my understanding, you have made some heavy modifications to the stock Android OS, and that's why there are bugs... I don't think that every time it is the other apps to blame...
