Older Android versions
-
Wonderful to see the 5.0 version released. But what Android versions are supported?
I am hesitant to use my expensive new smartphone as navigation on my motorbike. I have an older smartphone that is still working fine for that purpose, but it has Android 9 (and can't be updated). In 5.0 the 'Routes & Tracklogs' menu item gives a map on the screen but you can't do anything anymore but go back. Any chance that this can be fixed?
~ Gijs Jonker, Westland -
Wonderful to see the 5.0 version released. But what Android versions are supported?
I am hesitant to use my expensive new smartphone as navigation on my motorbike. I have an older smartphone that is still working fine for that purpose, but it has Android 9 (and can't be updated). In 5.0 the 'Routes & Tracklogs' menu item gives a map on the screen but you can't do anything anymore but go back. Any chance that this can be fixed?
~ Gijs Jonker, Westland@Gijs-Jonker, that's probably related to this issue, we see on older Android versions indeed:
https://forum.myrouteapp.com/post/71353 -
Thanks for the quick response! It looks a bit like the other issue but not exactly.
From the main menu everything works fine except two menu items: Routes & Tracklogs and Activity Feed. They both give the map on the full screen (portrait and landscape mode) and nothing is possible anymore, no scrolling, absolutely nothing. Only the Android back button goes back indeed and everything else seems to work.
I have 3 Android 9 devices and they all react the same; device reboot doesn't help. On Android 11 all the (main) menu items work as expected. -
I expect a fix rather soon for that issue!
-
Unfortunately the v5.0.1 release hasn't resolved the (Android 9) issue I mentioned.
-
Have you tried each of the new "advanced" settings in the map layer settings?
-
I believe they need to find a solution. It's not acceptable to have to buy a new phone running Android 15 or later just for the application to work correctly. As I understand it, the issues begin with Android 14 and older versions, according to their announcement for the new release 5.0.1.
-
I believe they need to find a solution. It's not acceptable to have to buy a new phone running Android 15 or later just for the application to work correctly. As I understand it, the issues begin with Android 14 and older versions, according to their announcement for the new release 5.0.1.
@GEORGIOS-PANTELIDIS-0 I am using Blackview BV7100 running android 12 & have not seen any issues with 5.0 or 5.1, so I would expect android 13 & 14 to also be fine
-
I believe they need to find a solution. It's not acceptable to have to buy a new phone running Android 15 or later just for the application to work correctly. As I understand it, the issues begin with Android 14 and older versions, according to their announcement for the new release 5.0.1.
@GEORGIOS-PANTELIDIS-0 said in Older Android versions:
I believe they need to find a solution. It's not acceptable to have to buy a new phone running Android 15 or later just for the application to work correctly.
It's worth noting that Google forces developers to update their apps at least once a year, to keep up with the latest 'target' SDKs. This regularly causes support for older Android versions to drop off, or some older features to become 'broken', withdrawn, etc.
Furthermore if developers don't move up ... 'Out-of-date apps are unavailable to new users of devices that run newer versions of Android.'
So - do I p*ss off the older device users, or do I lose the newer device users?
Catch-22.Realistically it's not an option to ignore Google's updates, and (depending on the change, and technology used) it's no fun for the developer having to update everything either.
In summary that dropping of older Android versions isn't really in MRA's control, it's in Google's, so place the blame squarely in their court!
Offering some settings to try and support older devices is a good solution - probably the only solution in fact, I would guess.
-
I don’t want to say anything bad about the app — I absolutely love it — but since I have two phones, a Motorola G32 with Android 13 and a Ulefone X12 Pro that I use for navigation, I noticed that the Motorola had an issue. I think it might have been fixed with the settings offered for older phones, though I’m not 100% sure yet, but it seems like it’s resolved.
However, since I also use other apps from time to time, those don’t have any issues with older Android versions. How that happens, I honestly don’t know.
