TomTom GO doesnt load most of the time

referravag

Hello everyone, I am a very new user of the DUDU7 and I have been using TomTom GO since more than a year now, since I had my previous headunit with the car.

I have noticed some more problems with TomTom GO that no one has reported here, and in my opinion, they are related to the navigation widget for sure and its integration with the system. Apart from the issue that is already discussed here, the app not starting at the beginning (that I also confirm), there is also another very important bug.

Problem A: So when the system wakes up with the ignition key, TomTom Go is loaded in the navigation widget and it works fine. However, if I open the app in full screen the instructions about the next turns that are displayed on the top left of the screen are not displayed in full screen.

When TomTom is displayed through the Navigation Widget it works as expected. You can see that the instruction about the next turn is displayed here:

However, when I open the app in full screen, the instructions about the next turns disappear. Take a look here:

After playing around a bit with the settings, I have concluded that the problem is somewhere in the integration with the Navigation Widget. So I have noticed the following behavior:

If TomTom is selected as the navigation app in the Navigation Widget, then the instructions for the next turns are displayed within the widget, but they are not displayed when changing to full-screen mode.
If I select a different navigation app for the Navigation Widget and then I open TomTom from its shortcut, it will open in full screen and the instructions for the next turn are displayed correctly as expected in full screen. See here:

This behaviour is common for both Normal and Minimal modes. In my opinion, it seems to be a clear bug of the navigation widget.

Problem B: Another serious problem is that once I click the home button on the status bar in order to change from full screen to the home screen (for both Normal and Minimal modes) TomTom seems to be crashing and starting again about 85% of the time. I mean, it displays the splash loading screen with the spinning circle inside the navigation widget like it was closed unexpectedly and was forced to restart from scratch...

Problem C: Just for information, there are huge bugs, way worse to TomTom when Waze is selected in the Navigation Widget and you want to change to full-screen mode. Waze works inside the widget, but when changing to full screen, I get a black screen (the map is a black image). Only the next turn instructions appear when changing to full screen (behaviour opposite to TomTom).

The only navigation app that seems to work correctly as it is supposed to during the transition from widget to full-screen mode and back, is Google Maps. I wll try also with Sygic to see how it behaves.

In my honest opinion, there are bugs in the integration of the Navigation Widget with the system... There needs a lot of debug to be done... Please can you make a note to correct all these bugs that are related to the navigation widget? From what I understand when we select a navigation app for the widget, this apps has troubles to be displayed correctly in full screen. It is very frustrating not being able to use the navigation apps in full screen mode if they are selected in the navigation widget...

For the moment I have completely removed the navigation widget and have it replaced with a different one (no navigation widget in my home screen). I prefer to have TomTom working correctly in full screen and then put it in split screen with a second app next to it, like Spotify/Music.

Cheers to everyone, and nice to be part of the community.
Hopefully the devs will correct the problems we report in the forum soon.

PS: I am running the latest DUDU OS update version.

DUDU-Meng

referravag
The navigation app's built-in floating window may conflict with DUDU's Picture-in-Picture (PiP) feature. If using navigation within PiP mode, please disable the app's own floating window function.

referravag

DUDU-Meng I will try to make a video one of the coming days, but I have already shared some photos earlier here referravag, with a detailed description of the behaviour. Can you take a look please? In order to reproduce the bug you need to start moving the car for the instructions to appear in TomTom. Just testing it on your bench by putting in an address and starting the navigation without moving will not display the instructions about the next turns ahead.

About Waze, I need to check toggling your setting, but I am not using it as my main navigation app. I will come with feedback by the end of the week on Waze.

referravag

DUDU-Meng There is not such a setting for TomTom Go, nor for Waze. This setting is present only in Google Maps.

So for me, you will have to implement additional functionalities in your OS/widget so that it can handle correctly the transition from the widget to the Full Screen and vise versa.

This is something that your dev team needs to investigate carefully imho and find a better implementation for the next update of the OS/launcher as with your current implementation we cannot use correctly other apps apart from Google Maps...

Blaming always the other applications that have been working perfectly for everyone in different headunits is not an honest response from your side. Everyone here has bought your product because it is supposed to be robust and accepting feedback from the community for future corrections.

As the situation stands for me at the moment, the navigation widget is useless so I have completely removed it from my home screen...

MihaiFlorin

DUDU-Meng This is the problem here. The app somehow is refreshed when you reboot the launcher. This is happening sometimes also with my delivery app. And that's how I knew about this "reboot launcher" thing. I don't see the problem of this action (reboot launcher) to be added to tasks. As long it is a task it is clearly that the user wants it.

Mikescotland

MihaiFlorin it's getting supper annoying. Sygic also restarts also every time after returning from reverse or any other application.

DUDU-Meng

referravag
You can try manually disabling this permission.

referravag

Mikescotland the same is happening with TomTom... When returning to the widget screen it seems that the navigation widget forces the app to close and restarts a different process that relaunches the application again...

Another bug that I have noticed also is that when TomTom is running inside the Navigation Widget it does not appear in the recent apps window, where you can also select the apps you want to put in split screen... It is like the process running TomTom is isolated in a different container or something compared to the rest of the system somehow...

For me the navigation widget works only with Google Maps as I said... It doesn't work correctly at all with TomTom... You will need to fix the issues with your dev team DUDU-Meng for the next updates 😊

DUDU-Meng

referravag
We are currently unable to address this issue. If an app is causing bugs while running in Picture-in-Picture mode, it should be fixed by the app's developer.
For the TomTom app you're using, you can disable this permission as shown in the image I uploaded earlier. For any other issues, it's best to contact the app's developer to optimize the UI for Picture-in-Picture operation.

JhonnyD

DUDU-Meng TomTom doesn't even need that permission.

referravag

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 😉

DUDU-Meng

PIP is not compatible with all apps. If an app is incompatible, it should be addressed by the app developer.

JhonnyD

I can say one thing. TomTom support will tell you, that the app is not optimized for head units and that's it.

In this point TomTom behaves like DUDUAUTO does atm.

DUDU-Meng

JhonnyD
Maybe not, there is a difference between pip and running full screen.
Tomtom if it has some problems running in dudu's pip then tomtom running within other hardware's pip most likely has the same problem, not bothering to optimize for windowed running. It's only designed to run full screen.

DUDU-Meng

What do the issues with Waze and TomTom running in Picture-in-Picture look like?
Is there a video? My tests suggest these apps seem designed for phones and don't support multi-layout. I haven't been able to reproduce the issues you described. Waze occasionally displays a black screen for a moment during initial launch, but other apps don't exhibit this behavior.

acvdmolen

MihaiFlorin @DUDU-Meng.
The last 2 weeks i travelled more than 4000 km's through Europe. When TomTom Go didn't start correct I did a reboot launcher at the moment that my internetradio app starts playing so I am 100% sure I have internet connection, and TomTom Go starts correct. So the question about an reboot launcher Task is at this moment the only option to make it work automatic.

MihaiFlorin

acvdmolen Only @DUDU-Meng can help you with that. I am just an ordinary user of the forum.

acvdmolen

MihaiFlorin okay thanks.

DUDU-Meng

acvdmolen
To this day, I still don't understand what kind of issues you're referring to when these two navigation apps crash while running in Picture-in-Picture mode. Based on your description, I can't even imagine what the problem might look like.
Also, regarding restarting the DUDU launcher—if you restart it, all the automated tasks you've set up will execute once, and you'll end up in an infinite loop.

acvdmolen

DUDU-Meng when I do a reboot launcher after wifi is connected tomtom Go starts correct. Because the navigation Widget in my case TomTom Go start to early and keeps hanging in the start phase I do a reboot launcher after wifi is connected it starts correct. What do you more want to know? It is what I do! That's why there are several times is questioning to make a "reboot launcher Task!"

DUDU-Meng

acvdmolen
I'd like to understand what you mean by “abnormal”—specifically, what the interface looks like when it's not functioning properly.
Right now, I only see that you've mentioned it's abnormal, but I'm unsure exactly where the issue lies.
I've reviewed the posts multiple times and haven't found any photos or videos showing problems with TOMTOM running in PIP mode.

« Previous Page Next Page »