Updated beta! 4.4.1 (407)
-
Hi all!
Been out testing today and released a new beta immediately.
Waypoint skip
There was a small mistake causing the waypoint skip to never be triggered when driving below 50 kph. That should have been a different value. Oopsie.Furthermore I added some extra logic to detect rejoining the route and picking the logical next waypoint.
Android app language
Added button in our app to open language settings directlyHave a nice weekend!
Corjan@Corjan-Meijerink, Where did you get that idea...
Android just came in
-
Topp
Danke dafür !!!!! -
Hey @Corjan-Meijerink,
I don't really use the automatic waypoints (WP) skipping, that didn't convince me until now, especially in the Alps where many bends follow each other and MRA sometimes chooses interesting abbreviations, which you better not drive, because the actual road offers a nice curve. Thanks to zooming +/- you can see it early enough, and with a simple DC I can easily skip WP myself.
..
Should I really think about setting it to automatically skip waypoints to test it again ..
In one week it goes for 11 days through Germany, also to the Odenwald and the Erzgebirge...
VG
-
Hi @Corjan-Meijerink
Since update 406 it is impossible for me to get acces to the bottum of the phonescreen in the forum section but also in the screen that should give acces to friends, groups etc at the bottum
Honda Goldwing GL1500,
Honda Silverwing GL 650
DMD2 T865X 8 inch Android tablet using MRA next for navigation
Garmin XT (almost in the cupboard)
Samsung S24FE mounted on a Quadlock and using Android Auto in my car -
Hi @Corjan-Meijerink
Since update 406 it is impossible for me to get acces to the bottum of the phonescreen in the forum section but also in the screen that should give acces to friends, groups etc at the bottumIt is blokkend by the phone menu buttons, even when I select not to show fullscreen
Honda Goldwing GL1500,
Honda Silverwing GL 650
DMD2 T865X 8 inch Android tablet using MRA next for navigation
Garmin XT (almost in the cupboard)
Samsung S24FE mounted on a Quadlock and using Android Auto in my car -
It is blokkend by the phone menu buttons, even when I select not to show fullscreen
@Marinus-van-Deudekom Only on Android I think. On iOS I can acces every menu.
-
-
Thnkx @Hubert-Thoring but I just found out it has nothing to fit with MRA. I've got a new phone and there was a function I didn't comprehend quite good. Now I've got it
-
The moment you posted this I knew it had nothing to do with our app. Glad you figured it out
-
The moment you posted this I knew it had nothing to do with our app. Glad you figured it out
@Corjan-Meijerink yep this week I’ve got this new phone and some things are just different. This one I didn’t notice up till now. Problem solved
-
407 is available in the Google Play Store
-
Did a test with the 407 with my new phone and AA. New Phone is a Samsung S24FE
Battery level at the start 44% after 90 minutes drive Battery level 26% not connected to power outlet
So I say good job done teamHonda Goldwing GL1500,
Honda Silverwing GL 650
DMD2 T865X 8 inch Android tablet using MRA next for navigation
Garmin XT (almost in the cupboard)
Samsung S24FE mounted on a Quadlock and using Android Auto in my car -
Did a test with the 407 with my new phone and AA. New Phone is a Samsung S24FE
Battery level at the start 44% after 90 minutes drive Battery level 26% not connected to power outlet
So I say good job done team@Marinus-van-Deudekom that’s a very decent power usage
-
@Marinus-van-Deudekom that’s a very decent power usage
@Corjan-Meijerink That’s indeed what I thought so a good Reading to share it with you all
-
The moment you posted this I knew it had nothing to do with our app. Glad you figured it out
@Corjan-Meijerink said in Updated beta! 4.4.1 (407):
The moment you posted this I knew it had nothing to do with our app. Glad you figured it out
Hmm, there are problems with window/widget depth in 407 though.
Here's the version number obscured on a thoroughly modern Android 16 Pixel 9a (admittedly with the not-so-modern optional 3-button navigation bar).
Possibly related to edge-to-edge layout being forced in Android 15/16 (API 35/36)?
-
I've seen the same on several screens where the bottom information is blocked by the android navigation.
