New beta 11.x

[orux]

Hello!

It's time for a new test, but be careful, this version has an important change, read before installing!

Google Play has become very restrictive with the 'access to all files' permission. It has not allowed me to update to version 11.0 of the app without removing that permission.

This implies important changes in file management, for those who used the public folders (the root directory of the internal storage or SD).

Now the app has to use the private folders again, the files used by the app cannot be shared with other apps/versions. Now the app uses the folder in Android/media/com.oruxmaps... The advantage of this folder is that it is visible to any file manager, which was not the case with the Android/data/ folder.

I'm sorry for the inconvenience. At the moment that permission can be kept by the version of the app that is on Amazon, which is more tolerant, it has not put up any obstacles to uploading the update to version 11 of the app.

For those of you who have a lot of maps, and want to try this beta, I recommend NOT migrating the mapfiles/ folder and then, after the migration, from settings > app storage > import resources, copy some of the maps, to test.

Sorry about the problem, but those are Google Play rules...

____________________________________________

Es hora de una nueva prueba, pero atención, esta versión tiene un cambio importante, leer antes de instalar!

Google Play se ha puesto muy restrictivo con el permiso 'acceso a todos los ficheros'. No me ha permitido actualizar a la versión 11 .0 de la app sin eliminar ese permiso.

Esto implica importantes cambios en la gestión de ficheros, para aquellos que usaban las carpetas públicas (el directorio raíz del almacenamiento interno o SD).

Ahora la app tiene que volver a usar las carpetas privadas, los ficheros que use la app no pueden estar compartidos con otras apps/versiones. Ahora la app usa la carpeta en Android/media/com.oruxmaps... La ventaja de esta carpeta es que es visible para cualquier gestor de ficheros, lo que no ocurría con la carpeta Android/data/

Siento el inconveniente. De momento ese permiso lo puede mantener la versión de la app que está en Amazon, que es mas tolerante, no ha puesto impedimentos a subir la actualización a la versión 11 de la app.

Para aquellos que tenéis muchos mapas, y queréis probar esta beta, recomiendo NO migrar la carpeta mapfiles/ y luego, después de la migración, desde configuración > almacenamiento app > importar recursos, copiar alguno de los mapas, para probar.

Ya siento el problema, pero Google Play es así...


beta1:
-->New storage restrictions. Migration to /Android/media/ folders
-->Updated SDK to 35 level, some changes in UI, themes,..



Please, report problems during the migration process! It is important for testing purpose, install this beta with the previous beta installed, to test the migration.



https://oruxmaps.org/OruxMaps11.0.0beta1.apk




orux

[Tronpo]

Hola Orux!! Después de aceptar la mala noticia , te informo , realice 6 pruebas de actualización de la beta anterior a la nueva para verificar la migración .
Las tres primeras hubo problemas , error humano , una vez solventandos(mal direccionamiento de directorios , permisos mal concedido )la app realizó la migración con éxito 20gb , varios formatos de mapas y temas Mapsforge comprimidos y sin comprir , todo ok .

Solo encontré un problema no solucionable.
 Si antes de la migración beta antigua , la app tiene configurada como carpeta secundaria de mapas un directorio de la targeta SD.
Cuando hacemos la actualización y damos el permiso y se inicia el proceso , se interrumpe y sale esta pantalla .

Aquí entramos en un bucle , por mucho que demos el permiso a la carpeta de la targeta sale el cartel mil veces , si salimos sin dar el permiso la app entra en un bucle interminable con la venta de movíendo archivos , pero en esta o acción no avanza ni sale información del porcentaje del proceso.

Tengo algunos videos más tarde los preparo y te los mando por privado .
Saludos !!

Edito:  en la migración las imágenes georreferenciadas no se mueven ,se mueve la carpeta con el archivo xml , pero la imagen no , en mi caso jpg

[Tronpo]

Añado que sería importante informar al usuario que en la migración los archivos no se mueven , se copian , esto quiere decir que el usuario necesita el mismo espacio de memoria libre como minimo que el espacio que tiene los archivos de OruxMaps para poder ejecutar el proceso .

Se tiene 20 GB en OruxMaps , necesita 20gb libres  así de simple .
No todo el mundo tiene tanto espacio disponible .

Saludos

[Lenz]

Hello Orux,
it is really annoying that Google's restrictions again and again cause problems for users and developers. So first of all I thank you for struggling with these inconveniences in order to provide this great app.

Now my first impressions (of course with the first problems):

The migration to the media folder worked well. I support Tronpo's suggestion to inform the users that the files are copied and not moved.

With bRouter I found two issues:

• OM isn't able to load the updates ('Error, OruxMaps can't write in that directory!') - which should be a logical consequence of not beeing able to use other folders.
• The route planner doesn't show all brouter profiles - probably the same reason.

And another problem with the path to the legends:
I collected all my legends in a folder called 'legends' in the OM folder. Now I moved this folder to the private folder but in OM I can only choose files within the mapfiles or mapstyles folder and not navigate to my legends folder.

Best regards
Martin

[Tronpo]

Hello Orux,
it is really annoying that Google's restrictions again and again cause problems for users and developers. So first of all I thank you for struggling with these inconveniences in order to provide this great app.

Now my first impressions (of course with the first problems):

The migration to the media folder worked well. I support Tronpo's suggestion to inform the users that the files are copied and not moved.

With bRouter I found two issues:

• OM isn't able to load the updates ('Error, OruxMaps can't write in that directory!') - which should be a logical consequence of not beeing able to use other folders.
• The route planner doesn't show all brouter profiles - probably the same reason.

And another problem with the path to the legends:
I collected all my legends in a folder called 'legends' in the OM folder. Now I moved this folder to the private folder but in OM I can only choose files within the mapfiles or mapstyles folder and not navigate to my legends folder.

Best regards
Martin

Hi Martin, brouter errors have easy solution, orux has much of the work done, only the last big step remains, the total integration of brouter in OruxMaps !! Grapphhoper offline is no longer there, it has the slot available and our beloved planner does not have to miss these wonderful advances that you have commented on.


Put your "legend " folder in the maptyles folder on Android media, and you're good to browse

🅃🅁🄾🄽🄿🄾

[Tronpo]

Añado que sería importante informar al usuario que en la migración los archivos no se mueven , se copian , esto quiere decir que el usuario necesita el mismo espacio de memoria libre como minimo que el espacio que tiene los archivos de OruxMaps para poder ejecutar el proceso .

Se tiene 20 GB en OruxMaps , necesita 20gb libres  así de simple .
No todo el mundo tiene tanto espacio disponible .

Saludos

Hello again, after other tests with a second terminal, I have realized that the app already contemplates the necessary space for migration, if there is no space it informs about it and does not allow migration.
Also at the end of the migration, the app informs that the original files still exist, in this way to be able to check that nothing is missing and if it is missing move it later.

Best regards

[Lenz]

Hi Martin, brouter errors have easy solution, orux has much of the work done, only the last big step remains, the total integration of brouter in OruxMaps !! Grapphhoper offline is no longer there, it has the slot available and our beloved planner does not have to miss these wonderful advances that you have commented on.


Put your "legend " folder in the maptyles folder on Android media, and you're good to browse

🅃🅁🄾🄽🄿🄾

Hi Tronpo,
thanks for your quick reply.
I'm looking forward to the full brouter integration.

I've already copied my (now) two legends folders into the mapstyles/mapfiles directory. I've just reported the behavior of OM not being able to browse other folders within android/media/com.orux.oruxmapsbeta in search of legends. I think this should be possible even with Google's restrictions. (Background: I used to have one folder for both 'theme legends' for vector maps and 'map legends' for raster maps.)

Best regards
Martin

[Tronpo]

Hi Tronpo,
thanks for your quick reply.
I'm looking forward to the full brouter integration.

Best regards
Martin

I have put this in my letter to the Magicians