Amigo not seeing current speed limit

[Wibbly]

Over two months on and, sadly, 9.547.0 (beta) does not fix the issue for me.

1. Configure Amigo to start in overlay mode and start when connected to the car's Bluetooth
2. Turn on the car's Bluetooth - Amigo starts in overlay mode as expected, but does not update the speed limit as I drive from one speed limit to the next
3. Tap the overlay and select Fullscreen - Amigo goes to Fullscreen/map mode as expected
4. Wait until the speed limit (lower left) updates
5. Tap the speed limit (lower left) and Amigo returns to overlay mode, as expected
6. Now, in overlay mode, the speed limits are updated

I suppose I need to be grateful there is at least a clugy workaround

 

[Tobired]

Over two months on and, sadly, 9.547.0 (beta) does not fix the issue for me.

1. Configure Amigo to start in overlay mode and start when connected to the car's Bluetooth
2. Turn on the car's Bluetooth - Amigo starts in overlay mode as expected, but does not update the speed limit as I drive from one speed limit to the next
3. Tap the overlay and select Fullscreen - Amigo goes to Fullscreen/map mode as expected
4. Wait until the speed limit (lower left) updates
5. Tap the speed limit (lower left) and Amigo returns to overlay mode, as expected
6. Now, in overlay mode, the speed limits are updated

I suppose I need to be grateful there is at least a clugy workaround

For me it is the same. At least it is working with the work around but it is a bit annoying. I am wondering why it is so difficult to fix when it was working fine before.

 

[Willy875]

I think the problem comes from certain phone models.
I'm Android 13 and I have no problem.

 

[Wibbly]

I think the problem comes from certain phone models.
I'm Android 13 and I have no problem.

I'm on Andorid 14 (Pixel 8 Pro). Used to work on that, and now doesn't. But as you say they may consider it an Android bug and are waiting for Google to fix that. In which case the next change is probably Android 15...

 

[AndyMc]

I'm on Andorid 14 (Pixel 8 Pro). Used to work on that, and now doesn't. But as you say they may consider it an Android bug and are waiting for Google to fix that. In which case the next change is probably Android 15...

Still the same same issue as you and used to work on Moto G31(w), Android 12 and Moto G(9) Play, Android 11...

 

[Tobired]

Does anyone have an update on this issue? Any word from TomTom when they will fix it?

 

[JuergenAMS]

I need to check. I thought it's fixed in the navigation SDK that the app builds on.

 

[Wibbly]

Not seen even a beta update that I've seen since 9.684

 

[JuergenAMS]

It was a map issue that has been fixed on the server side. Are we talking about the app itself or overlay mode?

 

[Wibbly]

Still have this issue

1. Configure Amigo to start in overlay mode and start when connected to the car's Bluetooth
2. Turn on the car's Bluetooth - Amigo starts in overlay mode as expected, but does not update the speed limit as I drive from one speed limit to the next
3. Tap the overlay and select Fullscreen - Amigo goes to Fullscreen/map mode as expected
4. Wait until the speed limit (lower left) updates
5. Tap the speed limit (lower left) and Amigo returns to overlay mode, as expected
6. Now, in overlay mode, the speed limits are updated

 

[JuergenAMS]

In overlay mode it is indeed still an issue. And I'm afraid there is a risk that it cannot be fixed. Overlay is a legacy of the previous Speed Camera app.

I now see that a colleague has already logged an issue for your report (DDAPP-19648).

 

[Wibbly]

Yes that was a couple or more (?) of months ago. So even a roll back to an old version of the app will no longer work to solve this problem?

 

[JuergenAMS]

You could give it a try if you can find an older version on an APK client. But then Android Auto would no longer be supported in cas you use that.

 

[Wibbly]

Well hopefully it's fixable on the current app and there's motivation to do it

 

[Joshuadasilva747]

Perversely, as I open the app full screen it starts blue and changes to grey a few seconds later.

That's an odd behavior! It might indicate a rendering issue or delay in loading assets when switching to full screen.

 

[__YANNICK__]

Hey,

I just tried a whole bunch of old versions and 9.315.0-20262 seems to work for now.

Thanks

 

[Wibbly]

Hey,

I just tried a whole bunch of old versions and 9.315.0-20262 seems to work for now.

Thanks

Thanks for doing the work on this!