New beta 11.x version

[Explorer]

I haven't seen where anyone else has posted this issue with the release of the beta v11.0.2beta2 and I still get the same error message after installing the latest beta v11.0.2beta3.  This happens on both my Samsung Galaxy Note 9 phone and on my Samsung A9+ tablet. When I first turn on Orux 11.0.2beta3 I get the popup screen, "This is an old beta version; it is near to stop working! Go to Google Play and check if there is anew version"; and I have to click on Cancel or Accept to make the popup go away. The next time I turn Oruxmaps on I get the same popup every time. This happens on both my phone and tablet every time. 

I believe this popup only starting happening after v11.0.2beta1 had been out for a long time and was updated, but started showing up immediately when v11.0.2beta2 was initially installed soon after it was released, and now continues to happen with the new release of v11.0.2beta3.

Anyone else seeing this?  It did not use to be the norm until a beta version had been out for quite some time.

[Andrea65]

Hello @Explorer, I am having the same problem on my Samsung Galaxy S21 (Android 15).

[Tronpo]

I haven't seen where anyone else has posted this issue with the release of the beta v11.0.2beta2 and I still get the same error message after installing the latest beta v11.0.2beta3.  This happens on both my Samsung Galaxy Note 9 phone and on my Samsung A9+ tablet. When I first turn on Orux 11.0.2beta3 I get the popup screen, "This is an old beta version; it is near to stop working! Go to Google Play and check if there is anew version"; and I have to click on Cancel or Accept to make the popup go away. The next time I turn Oruxmaps on I get the same popup every time. This happens on both my phone and tablet every time. 

I believe this popup only starting happening after v11.0.2beta1 had been out for a long time and was updated, but started showing up immediately when v11.0.2beta2 was initially installed soon after it was released, and now continues to happen with the new release of v11.0.2beta3.

Anyone else seeing this?  It did not use to be the norm until a beta version had been out for quite some time.

Hello it is not a mistake, the betas are test versions and have an expiration date.
The official version of Google play does not expire.
The message will continue to appear in the beta version until it is no longer operational.
Until a new beta version.
Beta versions are for testing and reporting.

[Explorer]

Hello it is not a mistake, the betas are test versions and have an expiration date.
The official version of Google play does not expire.
The message will continue to appear in the beta version until it is no longer operational.
Until a new beta version.
Beta versions are for testing and reporting.

What I am referring to is that the 1st day that the new beta v11.0.2beta2 was released it immediately started showing the near to stop working message; then when the latest beta v11.0.2beta3 was released it continues to give the same error message on the 1st day of it's release.  This is something new that has never occurred before with prior beta releases (all the way back to the beta v7.4 series of beta releases), until the beta v11.0.2beta2 was released.  It appears that beta versions v11.0.2beta2 and v11.0.2beta3 did not get their expiration dates updated when they were initially released to the public.

[Tronpo]

What I am referring to is that the 1st day that the new beta v11.0.2beta2 was released it immediately started showing the near to stop working message; then when the latest beta v11.0.2beta3 was released it continues to give the same error message on the 1st day of it's release.  This is something new that has never occurred before with prior beta releases (all the way back to the beta v7.4 series of beta releases), until the beta v11.0.2beta2 was released.  It appears that beta versions v11.0.2beta2 and v11.0.2beta3 did not get their expiration dates updated when they were initially released to the public.

Well, it is not my case, nor that of other users who are in a group, until last week the expiration message did not jump in beta 3.
And with beta 2 it also took a while before it showed the message
What is true is that in these betas the period of life has been reduced.
Greetings and sorry if I didn't understand you.👍

[Explorer]

Well, it is not my case, nor that of other users who are in a group, until last week the expiration message did not jump in beta 3.
And with beta 2 it also took a while before it showed the message
What is true is that in these betas the period of life has been reduced.
Greetings and sorry if I didn't understand you.👍

Ok, Thanks for letting me know.  It seems that the beta versions used to go about 6 months before the expiration notice would appear.  I believe beta v11.0.2beta3 was released on July 9 so if I am understanding correctly what you said, then v11.0.2beta3 went about 1 month for you, before you got the about to expire pop up window.

[Tronpo]

Ok, Thanks for letting me know.  It seems that the beta versions used to go about 6 months before the expiration notice would appear.  I believe beta v11.0.2beta3 was released on July 9 so if I am understanding correctly what you said, then v11.0.2beta3 went about 1 month for you, before you got the about to expire pop up window.

Correct, it seems that José has reduced the expiration time.
For me it would be ideal if we could credit the purchase of the GP version in the beta version and remove the expiration of it.
To avoid waiting for an update in the play store, and that the beta It wouldn't be to have a free premium app.

[kkolesar]

Correct, it seems that José has reduced the expiration time.
For me it would be ideal if we could credit the purchase of the GP version in the beta version and remove the expiration of it.
To avoid waiting for an update in the play store, and that the beta It wouldn't be to have a free premium app.

I completely agree with this suggestion. I really hope Jose reads this ... We have already written a few suggestions here on how to stay on the beta version, because the GP version is somehow a step backwards comparing to the beta.

[Explorer]

Correct, it seems that José has reduced the expiration time.
For me it would be ideal if we could credit the purchase of the GP version in the beta version and remove the expiration of it.
To avoid waiting for an update in the play store, and that the beta It wouldn't be to have a free premium app.

Completely agree.  I would expect that anyone who follows Oruxmaps.org most likely already has the GP version of Oruxmaps and for those that don't follow Orux here online but use it somewhat regularly also have already paid for the GP version, at least the 15-20 individuals in my group have already paid for the GP version.

[Lenz]

Hello Orux,
it is obvious that the result of the 'circular trip' function is not a route which is exactly as long as entered, as it depends on the routing profiles and the ways in the area around the starting point. But in my case the route is always about five times as long as the value entered.
In addition to this bug, the circular trip can not be recalculated when you change the routing profile - it simply disappears from the map.

Best regards
Martin

[kkolesar]

Hello Orux,
it is obvious that the result of the 'circular trip' function is not a route which is exactly as long as entered, as it depends on the routing profiles and the ways in the area around the starting point. But in my case the route is always about five times as long as the value entered.
In addition to this bug, the circular trip can not be recalculated when you change the routing profile - it simply disappears from the map.

Best regards
Martin

...  in addition to the above, OM crashes if you press 'ok' on empty fields.

br

[Explorer]

What I am referring to is that the 1st day that the new beta v11.0.2beta2 was released it immediately started showing the near to stop working message; then when the latest beta v11.0.2beta3 was released it continues to give the same error message on the 1st day of it's release.  This is something new that has never occurred before with prior beta releases (all the way back to the beta v7.4 series of beta releases), until the beta v11.0.2beta2 was released.  It appears that beta versions v11.0.2beta2 and v11.0.2beta3 did not get their expiration dates updated when they were initially released to the public.

Looks like the expiration date for getting the pop-up window about the beta version soon to expire has been updated with the latest beta v11.0.2beta4.  No longer get the soon to expire pop-up with the beta 4 release. 

Thanks Orux/Jose.  Appreciate all the hard work that goes into keeping Oruxmaps going and regularly updating.

[Explorer]

It seems there is a problem when making a "Composite" map when using 2 or more "Offline" maps.  The problem I am encountering is that my base-map, a Mapforge Map (.map file), does not get added as a "Layer" when you click on "Add Layer" when creating a Composite Map.  The foreground map a Garmin vector map does get added as a Layer, but when you select the newly created Composite map to display, all you see is the Garmin map with a blue background and the Mapforge Map does not appear at all.  This is something that started happening sometime with beta version 11, not sure which beta 11 version it started with.

The Garmin maps and the Mapforge Maps in question do display correctly as a "Composite Map" in the GP version of Oruxmxaps v10.7.4 GP.  I have tried 4 different Garmin type maps with 4 different Mapforge maps that all do display correctly as Composite Maps in the GP version, and also used to work correctly in the older beta versions prior to the release of beta versions 11, but now none of my Composite Maps display correctly with Mapforge Maps using the newer beta version v.11.0.2beta4.

I have played around with changing several of the map settings to see if that would help and so far nothing has made a difference where the Mapforge map will display when combined as a "Composite Map".  This seems to be a problem just since the new beta 11 versions were released.  The Mapforge Maps will display correctly when they are used as a stand alone map and not as a Composite Map.

Has anyone else experienced this when making a Composite map, using a Mapforge map as 1 of the maps?  Was wondering if I am missing some setting in the settings with the newer v11 beta versions, or if this is a bug in the beta v11 of Oruxmaps?

[Tronpo]

It seems there is a problem when making a "Composite" map when using 2 or more "Offline" maps.  The problem I am encountering is that my base-map, a Mapforge Map (.map file), does not get added as a "Layer" when you click on "Add Layer" when creating a Composite Map.  The foreground map a Garmin vector map does get added as a Layer, but when you select the newly created Composite map to display, all you see is the Garmin map with a blue background and the Mapforge Map does not appear at all.  This is something that started happening sometime with beta version 11, not sure which beta 11 version it started with.

The Garmin maps and the Mapforge Maps in question do display correctly as a "Composite Map" in the GP version of Oruxmxaps v10.7.4 GP.  I have tried 4 different Garmin type maps with 4 different Mapforge maps that all do display correctly as Composite Maps in the GP version, and also used to work correctly in the older beta versions prior to the release of beta versions 11, but now none of my Composite Maps display correctly with Mapforge Maps using the newer beta version v.11.0.2beta4.

I have played around with changing several of the map settings to see if that would help and so far nothing has made a difference where the Mapforge map will display when combined as a "Composite Map".  This seems to be a problem just since the new beta 11 versions were released.  The Mapforge Maps will display correctly when they are used as a stand alone map and not as a Composite Map.

Has anyone else experienced this when making a Composite map, using a Mapforge map as 1 of the maps?  Was wondering if I am missing some setting in the settings with the newer v11 beta versions, or if this is a bug in the beta v11 of Oruxmaps?

Hello, do you have the vtm viewer activated?
If you have activated the vtm viewer, either in the map settings, or in the Mapsforge settings, in both settings at the bottom is the checkbox to check uncheck.
The VTM viewer does not support composite maps.
My Composite Map  are working correctly in the beta.

Best regards.

[Explorer]

Hello, do you have the vtm viewer activated?
If you have activated the vtm viewer, either in the map settings, or in the Mapsforge settings, in both settings at the bottom is the checkbox to check uncheck.
The VTM viewer does not support composite maps.
My Composite Map  are working correctly in the beta.

Best regards.

Thank you for the information and quick reply.  Not sure if I do or not but will definitely check.