Topics

[Android Settings > Applications > Special permissions > Access to all files]

In some cases it seems that Android removes the app permission to access the files, with the latest updates.

If the app cannot access Tracks or maps, check that the following permission is granted for OruxMaps:

Android Settings > Applications > Special permissions > Access to all files

This is the permission that allows the app to access folders when they are at the root of the internal storage.


_________________________________________________________________________________________

En algunos casos parece que Android le quita el permiso de acceder a los ficheros, con las últimas actualizaciones.

Si la app no puede acceder a los Tracks, o a los mapas, comprueba que el permiso siguiente está concedido a OruxMaps:

Configuración de Android > Aplicaciones > Permisos especiales > Acceso a todos los ficheros

Este es el permiso que permite a la app acceder a las carpetas cuando están en la raíz del almacenamiento interno.




orux

[Android Settings > Applications > Special permissions > Access to all files]

In some cases it seems that Android removes the app permission to access the files, with the latest updates.

If the app cannot access Tracks or maps, check that the following permission is granted for OruxMaps:

Android Settings > Applications > Special permissions > Access to all files

This is the permission that allows the app to access folders when they are at the root of the internal storage.


_________________________________________________________________________________________

En algunos casos parece que Android le quita el permiso de acceder a los ficheros, con las últimas actualizaciones.

Si la app no puede acceder a los Tracks, o a los mapas, comprueba que el permiso siguiente está concedido a OruxMaps:

Configuración de Android > Aplicaciones > Permisos especiales > Acceso a todos los ficheros

Este es el permiso que permite a la app acceder a las carpetas cuando están en la raíz del almacenamiento interno.





orux

As always, starting a new series of betas.

Version 10.6 is in progressive release, will be in GP soon available to everyone.


This beta has new features:

1. Climber. Analysis of segments by slope. In construction. This is a new screen on the trip computer views, which reports on slope segments data (configurable). These data for each route can be modified and saved for future use. In the trip computer view > Climber view, there is a button that takes us to the list of slope segments. In that screen we can see the different segments calculated. We can change the parameters (distance and slope used for the calculations, top action bar > more button). We can delete/join/split the segments.

1.1. New buttons over some graphs, to do zoom/reset to the current position, if following a route.

2. New slope graph, using the altitude graph, by colors.

3. Route planner. New option to trace sections with the finger.

4. Rearrange dashboard elements in the map viewer or trip computer views by dragging and dropping. For this purpose, a new dashboard editing tool has been added (map viewer > left panel > other tools).

5. Improved side button bars constructor, with more help to find the right buttons. The button and the description is displyed when we drag the bar to select a different button.




beta2:
--New setting in route plenner. Try to adjust the path made with the finger to an existing route in Brouter.
--bug corrections


beta3:
--New search engine (experimental) on waymarkedtrails.com Allows you to search in different ways (bbox, clicking on the routes on the map or by text) on this website. Add a tool (also experimental) to reorder the segments, since on that website they can come out of order.
--Enabled hardware acceleration in the main map viewer. An important issue to test, given that Google maps did not work well (black screen) without it when updating Google services to the latest version.


https://oruxmaps.org/OruxMaps10.6.2beta3.apk




orux

Hello!
We start a new series of betas, with interesting changes:

10.5.3beta1:
--new route planner, with more data and options during planning
--new layer manager
--changes in the interface, icons,...

10.5.3beta2:
--tracks/waypoints in two columns in landscape
--minor changes
--bug corrections

10.5.3beta3:
--minor changes

10.5.3beta4:
--new 'tweak routes' and 'tweak track' options, to tweak fine grained the visibility of all the routes shown in the mapviewer and access their properties and different tools.
--minor changes

10.5.3beta5:
--minor changes

10.5.3beta6:
--minor changes

10.5.3beta7:
--added new map overlays (slopes and relief)
--added an option to modify maximum slope value when painting the route with slopes (settings->user interface->Tracks/lines,...->Colored paths with slope)
--other minor changes

10.5.3beta8:
--minor changes

10.5.3beta9:
--bug corrections
--some changes with the interface when following a route
--other minor changes

10.5.3beta10:
--bug corrections
--automatic night mode
--other minor changes

10.5.3beta11:
--bug corrections

10.5.3beta15:
--bug corrections


10.5.3beta16:
--bug corrections

10.5.3beta17:
--bug corrections


10.5.3beta18:
--bug corrections





orux

Today we start a new series of betas.



:10.1.9beta2
-->Select Open Camera as camera for photo waypoints (settings > Application)
-->Experimental support for using RTK correction for external GPS using NTRIP servers (Settings > Sensors > GPS)
-->Download of an online map along a route, mbtiles format (click on the layout of a route, new button)
-->Simplified list of Tracks (Settings > Tracks)


:10.1.9beta3
-->Bug corrections.


:10.1.9beta4
-->changes in virtual partner. Added a button to reset the position (visible under red bottom navigation button when you are following a route, and the partner is active)
-->Bug corrections.


:10.1.9beta5
-->changes in forms (added a new time type). Now the forms attached can be edited,...
-->Bug corrections.


beta6:
-->mapsforge 0.20 libraries
-->support to mapsforge POI v3 databases


beta7:
-->bug corrections


10.1.10beta1:
-->bug corrections


10.1.10beta2:
-->update of vtm libraries
-->bug corrections


10.1.10beta3:
-->bug corrections


10.1.10beta5:
-->bug corrections


10.1.10beta6:
-->bug corrections


10.1.10beta7:
-->bug corrections


orux

Today we start a new series of betas.

1.-A major change. Added permission to access all files. In this way, it is not necessary to install any old apk so that the app can access the internal storage. The app asks when installing it (from scratch) if access to this permission is allowed.

Let's hope that Google Play does not put obstacles.


[CLOSED, STARTED NEW THREAD WITH THE FOLLOWING VERSION]



orux

Given the problems of using the sending of SMS from OruxMaps, I have created an independent app to manage this functionality, OruxSoS. It can work alone or be activated from OruxMaps.

Its cost will be €1, but from 17 Sept 2022 – 24 Sept 2022 it will be free for 8 days (the time that Google Play allows this type of promotion).


https://play.google.com/store/apps/details?id=com.orux.oruxsos


orux

Hello!

It is time for a new beta version.

beta1:
            —>Viewshed calculation (Map tools-->viewshed)
            —>Improved interface.

beta2:           
            —>New SOS SMS notification system. Given the limitations of the SOS function, that we cannot use the sending of SMS as Google restricts the use of that permission and that sending emails using a Gmail account no longer works, I have created an independent app, which does the same function, standalone or it can be activated/deactivated from OruxMaps. 
The new app (use with care, under testing!).
            —>Bugs corrections.

beta3:
            —>Bugs corrections.
            —>OruxSoS update.

beta4:
            —>New dashboard controls, averaged pitch/roll, added to the instantaneous measurements, to give stability to the values, for example using the bike. You can modify the time in global configuration-->sensors-->orientation sensors.
            —>New dashboard controls, averaged power T1 and T2. For BT and ANT+ bike power sensors. You can configure the T1 and T2 in global settings-->sensors-->Power bike BT or sensors-->ANT+.


beta5:
            —>bugs correction.


beta6:
            —>bugs correction with garmin typ files.


https://play.google.com/store/apps/details?id=com.orux.oruxsos



Use previously this beta apk if you want to use the directories in the root of the internal/SD storage.
https://www.oruxmaps.org/OruxMapsBeta0.0.1.apk






orux

Hello!

After 9.x seems to start to stabilize, we can start with new things:

9.0.4beta8:
--minor changes
--bug fixes

9.0.4beta7:
--minor changes
--bug fixes


9.0.4beta6:
--bug fixes


9.0.4beta5:
--bug fixes


9.0.4beta4:
--bug fixes


9.0.4beta3:
--bug fixes



9.0.4beta2:
--bug fixes
--route search with brouter/graphhopper offline. Now you can change the profile during route search and add segments with different profiles.


9.0.4beta1:
--custom track types (when you create a track, and select the typoe, there a new option to create your own types)
--select folders inside main folders inside private storage. If you migrated all your data to the app privvate folders, now you can use different folders, for example with dem files.
--hdr files, suppor to overlaped files. If the elevation is not available in a file, it will try to find that data in other hdr files.
--add custom datums. Configuration-->maps-->Datums manager.





orux

[a)]

Hello!
PLEASE! READ CAREFULLY NEXT INFORMATION BEFORE INSTALLING THE NEW BETA, BECAUSE IT INCLUDES THE NEW RESTRICTIONS TO THE DEVICE INTERNAL STORAGE.

The new beta can be used in the following ways:

a) If you have a previous beta installed (you do an update). Then two options will be possible:

a.1) do not migrate at all the data to the private storage of the app. Everything continues as before. But at the time of uninstalling and reinstalling, you will be in option b).

a.2) migrate the data. It is a difficult process, but it must work. The current app data (maps, tracks databases,...) is copied in the private folder of the app (it can be in the SD if an SD is used in addition to the internal storage). IMPORTANT: The old data (folders and files) in the internal storage/SD are NOT erased, to continue using them with other versions. If the user wants, he could delete them. Obviously the app no longer shares data with other versions of the app. The Tracks database is its own. Tracks recorded in the beta version will not be seen in the list of Tracks in the GP version, for example.

b) If you do not have a previous beta installed, the app will use the private storage, yes or yes, by obligation (Android no longer allows apps to access the root of the internal storage, where previous versions of the app usually store all the app information). In this case the app offers two tools in global configuration -> app storage to move/import files from/to the app:

   
• -> Import resources: With this tool you can tell the app resources (by type, map, tracks, ...) that can be copied to the app private folders.
• -> Open Android File Manager: With this tool the app opens the Android file browser, inside the private folders of the app, to allow you to copy files from the private folders of the app to another directory of your device. For example, if you are going to uninstall the app, in this way you can copy things before Android deletes all the app folders (remember that Android deletes all the app files in private folders when you uninstall an app !!).

It is stupid, but that file browser does not allow to copy entire folders! Here you can find file browsers that can do that work friendly (Working at this moment, I don't know if in a future they will be able to do that, if they compile the app with last SDK; I recommend 'Explorer' app): https://www.reddit.com/r/Android/comments/j3zgmm/managing_files_in_the_androiddata_folder_on/



POR FAVOR, LEER DETENIDAMENTE EL SIGUIENTE AVISO, LA NUEVA BETA INCLUYE LAS RESTRICCIONES DE ACCESO AL ALMACENAMIENTO INTERNO A QUE OBLIGA ANDROID.

La beta se puede usar de los siguientes modos:

a) si tienes instalada una beta previa (haces una actualización). Entonces se abren dos opciones:

a.1) no migrar los datos al almacenamiento privado de la app. Todo sigue como antes. En el momento de desinstalar y volver a instalar, se estará en la opción b).

a.2) migrar los datos. Es un proceso difícil, pero debe funcionar. Los datos actuales se copian en la carpeta privada de la app (puede ser en la SD si además del almacenamiento interno se usa una SD). Los datos (carpetas y ficheros) antiguos en el almacenamiento interno/SD NO se borran, para seguir usándolos con otras versiones. Si el usuario quiere podría borrarlos. Evidentemente la app ya no comparte datos con otras versiones de la app. La base de datos de Tracks es propia. Los Tracks grabados en la versión beta no se verán en el listado de Tracks de la versión GP, por ejemplo.

b) si no se tiene instalada una beta previa, la app utilizará sí o sí, por obligación, el almacenamiento privado (Android no deja ya a las apps acceder a la raíz del almacenamiento interno). En este caso la app ofrece dos herramientas en configuración global-->almacenamiento app para mover/importar ficheros de/hacia la app:

   
• -> Importar recursos: Con esta herramienta puede indicar los recursos de la aplicación (por tipo, mapa, pistas, ...) que se pueden copiar a las carpetas privadas de la aplicación.
• -> Abrir Administrador de archivos de Android: Con esta herramienta, la aplicación abre el navegador de archivos de Android, dentro de las carpetas privadas de la aplicación, para permitirte copiar archivos de las carpetas privadas de la aplicación a otro directorio de tu dispositivo. Por ejemplo, si vas a desinstalar la aplicación, de esta forma puedes copiar cosas antes de que Android borre todas las carpetas de la aplicación (recuerda que Android borra todos los archivos de la aplicación en carpetas privadas cuando desinstalas una aplicación).

Es estúpido, ¡pero ese explorador de archivos no permite copiar carpetas enteras! Aquí puede encontrar navegadores de archivos que pueden hacer ese trabajo de manera amigable (recomiendo Explorer): https://www.reddit.com/r/Android/comments/j3zgmm/managing_files_in_the_androiddata_folder_on/




RC3:
-->some bugs corrected


RC2:
-->some bugs corrected


RC1:
-->removed old libraries.
-->no more changes till the next release.



beta31:full support to RTL languages
changes in map calibration tool
added new information to statistics, distance ascending/descending.



beta28:-->last experiment!
Added more values to the Track statistics: Distance ascending/descending.
Georeference an image (png, jpg, pdf or tif supported). Map tools-->Image to Map.
First you have to load the image, then you have to add calibration points (four at least, recomended more). You have to select a point in the image, then that point in the map, and so on.
Then, when you select OK button, a new offline map will be created.
With that map, you can load it as a normal offline map, or as a map overlay over another map (Map overlays-->Map as overlay, the map is reprojected based on the base map).




beta26:
-->some bugs corrected
-->support to kml/kmz groundoverlay tags, loaded as map overlays, some examples:
https://oruxmaps.org/etna.kml (37.69 N, 15.03 E)
https://oruxmaps.org/mt_rainier.kmz (46.95 N, 121.97 W)
tap the ground overlay to change transparency.



beta25:
-->slight modifications in getfeaureinfo queries in WMS: added button for this function, which allows querying any of the WMS that you have. To use the WMS query with the 'long press' you now have to select the WMS you want to use in configuration-->maps-->select WMS for query.


beta23:
--last minute bug solved


beta22:
--mapsforge maps library update to 0.17 version
--calculate a route in Brouter starting from an own route. In the properties of your Tracks, a new button, 'Match in brouter' will search for a matching route in brouter. Waypoints will be added with turn information, and surface type data,...
--added the option to query the GetFeatureInfo option of a WMS, with two options:
a) long press on the map-->what's here.
b) when creating Waypoints, new option at the end, to add that information in the Waypoint description.
To select a WMS that is consulted when creating a Waypoint or with the long press option: side panel, maps-->Select GetFeatureInfo WMS. Or in the top action bar-->maps-->map settings-->Select GetFeatureInfo WMS

Examples of useful WMS (in Spain, the cadastre or the altitude WMS): https://www.idee.es/segun-tipo-de-servicio




beta21:
--added a new feature: Group waypoints if they overlap. It works with waypoints that belong to overlays or the loaded routes. You can disable that option (on by default) in waypoints menus, or in the settings-->user interface-->tracks/routes/lines...



beta20:
--some bugs corrected



beta18:
--added more tools to track segments list.
--changes in how the app paints the routes when it has many segments (in paint slope mode).
--some bugs corrected (maybe new ones were added...)



beta16:
--changes with proj4j libraries. Check if all is right about coordinates, grids,...
--added range selection in waypoints/tracks lists.
--added massive track modification.



beta15:
--->added support for files in geojson format (tracks, polygons,...)
--->new storage options (test these options carefully. Mass data movements are complex):
--added a secondary directory for maps. In this way you can have maps in the internal storage and in an external SD simultaneously.
--if you are using private storage (Android scoped storage) you can change the SD/internal storage directories independently for each resources files (DEM files, photos,...).
--added option to export all app files when using Android scoped storage to a folder on the phone's shared storage. This way everything can be recovered if the app is uninstalled/installed again from that directory.



beta14:
--solved some bugs,

beta12:
--added no-go points to brouter search engine,
--solved some bugs,


beta11:
--solved some bugs,


beta10:
--edit the properties (name, description, color, fill, ...) of each segment of a Track (new button in the properties display of a Track recorded with the app, or imported to the tracks database).



--new wizards.



--routes searched with brouter, added the option to include data of road type, surface, etc. Once you have searched for a route with brouter, click on the track, then statistics button.



--new sensor, network status. Now you can save the state of the network (if there is telephone coverage) when saving a Track, very interesting during mountain tours, or in areas with low coverage. To always save it by default, configuration - tracks -> add network status. Or when starting the recording of a Track, sensors -> start network status.

--new menus when pressing a Track. You can individually select how to display the Track:
-> slopes
-> default color
-> type of surface (only routes searched with brouter)
-> network coverage (only if the data for that sensor has been saved).





beta9:
-->changed somne icons
-->added (long press the map) an option to search images in WikiMedia databases.


beta8:
-->added icons to mapsforge searchs (some categories)
-->solved some bugs with photo waypoints.

beta7:
-->load geotagged pictures as a overlay, with thumbnails. Map overlay
-->load kmz/kml/shp overlay. Now you can select pictures. If they have georeference information, then will be shown in the map with a thumbnail.
-->import geotagged pictures to your waypoints list.
-->support to dinamic kml files.
-->Strava integration, added a new button in the Strava activities to see starred segments.
-->maps in night mode with colour (map settings-->colorized night maps.


beta6:
->bugs corrections


beta5:-->Geotiff maps improvements.-->bugs corrections



beta4:
-->added an option about Android 11 SAF. global settings-->app storage-->Restore an old installation: to copy a full OruxMaps old installation from the internal storage to the private to the app storage.
-->added coloured night mode: map settings-->colorized night maps.
-->support to garmin extension (base camp routes) in gpx files.
-->new text to speech fields (altitude up/down).



beta1:
-->Android 30 SDK storage limitations.
-->Use patterns with Waypoint names. You can use some patterns to customize the waypoint names (global settings-->Waypoints-->Waypoint name patterns).-
-->Support to a different barometer-termometer device: https://oruxmaps.org/forum/index.php?topic=40161.msg52314



The beta version:







orux

As you know, Android requires, since sdk 30, that apps use only private storage (within Android/data/) to save their own files.


OruxMaps uses from its birth the oruxmaps/ folder at the root of the internal storage, to make it easier for users to manage maps, tracks,...


Since November 1, Google enforces apps to compile against the sdk 30, so the following versions of the app will require a big change from users:

   
• The migration to the private folders of the app will be expensive, since many users have many gigas of information.
• When an app is uninstalled, everything in an app's private folders is deleted.
• The file browser that Android includes, which is the one that has access to all the folders, is a bit bad, it doesn't make it much easier to move and copy to/from private folders.
• Maps/routes can no longer be shared, between different apps, or app versions (beta, GP, ...).
• ...

At the moment the versions published in the Amazon store and in the Huawei appstore will not be affected, because I will be able to continue compiling them against sdk 29, but the GP version will have to change in the coming months.


Soon I will publish a beta to start testing,

If anyone wants to share relevant information related to this issue, or has any suggestions, go ahead.




____________________________________________________________

Como sabéis, Android obliga, desde el sdk 30, a que las apps usen solo el almacenamiento privado (dentro de Android/data/) para guardar sus ficheros propios.

OruxMaps usa desde su nacimiento la carpeta oruxmaps/ en la raíz del almacenamiento interno, para facilitar a los usuarios la gestión de mapas, tracks, etc.


Desde el 1 de noviembre Google obliga a que las apps compilen  contra el sdk 30, por lo que las siguientes versiones de la app van a requerir un gran cambio a los usuarios.

   
• La migración a las carpetas privadas de la app será costosa, ya que muchos usuarios tienen muchos gigas de información.
• Cuando se desinstala una app, todo lo que está en las carpetas privadas de una app se borra.
• El navegador de ficheros que incluye Android, que es el que tiene acceso a todas las carpetas, es un poco malo, no facilita mucho los movimientos y copias hacia/desde las carpetas privadas.
• Ya no se pueden compartir mapas/rutas,... entre diferentes apps, o versiones de la app (beta, GP,...).
• ...

De momento las versiones publicadas en Amazon store y en Huawei appstore no se verán afectadas, porque podré seguir compilándolas contra el sdk 29, pero la versión GP tendrá que cambiar en los próximos meses.

Próximamente publicaré una beta para empezar a ir probando.
Si alguien quiere compartir información relevante relacionado con este problema, o tiene alguna sugerencia, adelante.


orux

A new beta, for some quick bug fixes:




:beta8
-->some changes using DEM based maps
-->changes in time in movement calculations.

:beta6
-->some new buttons added
-->improved map composition



:beta4
-->you can build button bars with drag & drop gesture.
-->you can sort text to speech messages to hear.
-->bugs corrections.



:beta3
-->fix some problems with WMS maps
-->highlight some (or all) of the map dashboard controls, using different background colors (settings -> user interface -> dashboard -> dashboard controls -> tap and select a color for the controls you want to highlight.

:beta1
-->new button for show/hide paths.
-->new option in settings--user interface--misc.-->max render speed. If you have a 5/10 Hz GPS you can test this option. It will try to render the map position at all the Hz.
-->bug fixes searching routes (with the statistics)




orux

Unified interface.

In this beta you can activate what I have called a unified interface for the map viewer (global configuration -> unified interface).


Initially, many years ago, all the menus were in the top bar of actions.
Android later introduced other design patterns, including the left side panel, leaving the top bar only for direct actions.
OruxMaps kept the drop-down menus on the top bar, to keep the same options for old users, adding a left side panel, with the possibility of using one or the other, or both.

This situation means that the same actions can be performed from different sites, which creates confusion for new users.

The goal of the new interface is to make things can be done only from one place, or almost;)

With the new interface, which would appear to new users by default (the old ones can go to this interface, or keep the one they had) the distribution of actions would be:

- upper action bar: basic functions of GPS activation, route recording and creation of waypoints.
- left side panel, as the main menu of the app, with all the tools, access to the settings, ...
- floating button (bottom right) for navigation actions (load routes on the map, activate navigation modes, ...)
- sidebars of buttons, configurable. Initially with the minimum options, but configurable so that the user can add the direct actions that he uses most frequently.

The discussion is opened, any reflection will be positively valued.

The beta test is here:
https://oruxmaps.org/forum/index.php?topic=37447.0

This is a proof of concept, not a definitive version.


orux

In recent versions of Android, apps cannot modify the Android power managemen settings, the user has to do it in the Android settings-> battery.


Now phones are too smart, they think for us, and they don't let us configure certain things, they think we're too stupid, they are smarter.


In some phones and brands it is a common problem that when the apps go to the background (we turn off the screen, or we open another app, ...) OruxMaps might stop recording the route, and draw a straight line, until you turn it back on the screen and bring OruxMaps to the foreground. This is not the fault of the app, because what happens is that Android closes the app directly, so that it does not waste energy, and the app does not know that this has happened.


This can usually be fixed if the power management (battery) is configured properly on Android.


Each manufacturer has done it in a different way, so there is no a unique solution for all phones. Basically we have to:


1.-deactivate energy saving modes. As soon as the energy saving mode is activated, any other setting is invalidated, and apps that consume energy, such as OruxMaps, are closed when the screen is turned off.


2.-Include OruxMaps in any list of apps that can run in the background, protected, not optimized, ... it depends on the manufacturer and/or version of Android.


It is recommended, if it continues to fail, search the Internet for our phone, there are sites where they have dedicated themselves to collecting information about this problem, for example at


https://dontkillmyapp.com/






_______________________________________________



En las versiones recientes de Android las apps no pueden modificar los ajustes de Android de gestión de energía, lo tiene que hacer el usuario en la configuración de Android->batería.


Ahora los teléfonos son demasiado inteligentes, piensan por nosotros, y no nos dejan ajustar determinadas cosas, creen que somos demasiado tontos, ellos son más listos.


En algunos teléfonos y marcas es un problema común, que al pasar las apps a segundo plano (apagar la pantalla, abrir otra app,...) OruxMaps puede dejar de grabar el recorrido, y trazar una línea recta, hasta que vuelves a encender la pantalla y pasar OruxMaps a primer plano. Esto no es culpa de la app, porque lo que pasa es que directamente Android cierra la app, para que no gaste energía, y la app no se entera de que esto ha ocurrido.


Esto normalmente tiene arreglo si se configura adecuadamente, en Android, la gestión de energía (batería).


Cada fabricante lo ha hecho de una manera diferente, por lo que no hay una solución única. Básicamente hay que:


1.-desactivar los modos de ahorro de energía. En el momento que se activa el modo ahorro de energía, cualquier otro ajuste se invalida, y las apps que gastan energía, como es el caso de OruxMaps, se cierran cuando se apaga la pantalla.


2.-Incluir OruxMaps en cualquier listado de apps que pueden funcionar en segundo plano, protegidas, no optimizadas,... depende del fabricante y/o versión de Android.


Lo recomendable es, si sigue fallando, buscar en Internet para tu teléfono, hay sitios donde se han dedicado a recoger información sobre este problema, por ejemplo en


https://dontkillmyapp.com/










orux

Starting a new test series.


8.5.0 released, Google Play


What's new?

:RC5
-->bugs correction

:RC4
-->bugs correction


:RC2
-->No more changes, until it is finally published.
-->Added Nominatim server as a new geocoder provider in global settings-->application-->geocoding service.
-->bugs correction

:beta29
-->bug corrections

:beta28
-->bug corrections


:beta27
-->new tool for measuring distances on the map, with two fingers. Maps button-->tools
-->added anew option (global settings-->Tracks/Routes) to save the speed from the GPS when recording a Track. That value seems more accurate than the one calculated using the distances and times between recorded points.
-->some bugs corrected

:beta26
-->upload to Strava using tcx/fit formats (if you have a power sensor they are the formats that support those sensors)
-->changes calculating magnetic declination, if you do not use the GPS.



:beta24
-->testing new things with unified interface.



:beta23
testing new features:
->add contour lines to other maps (only Google Mercator projection) using mapsforge map overlay. You need to have a mapsforge map that includes contour lines. First time you activate contour lines you have to select the mapsforge map the app will use to get the contour lines. Enable/disable this option under map overlay submenu
->a new bubble when you tap a waypoint. Tap the name if you want to see all the information. A '+' button will be show if there are more than one waypoint tapped.
-->extend a route with a new search. After you load a route to the map, tap the first/last waypoint. A new button 'edit' allow you to add a new segment with a new search, or by hand (under work).
->changes in unified interface menus.



:beta22
--modifications in unified interface



:beta21
--testing unified interface, discussion here: https://oruxmaps.org/forum/index.php?topic=39498.0
--added an option to export to file/import to database to all routes loaded in the map, first/last waypoint.
--added distance field to search route tool.


:beta20
--search route (brouter/graphhopper offline) modifications.

:beta19
--bug correction


:beta18
--added {azimuth} to share position intents.
--added an option to save to a file/import Intents. The file structure:

#coments
#field separator: | (use %7C in the uri if you need that character)
name of the intent|package name|uri|intent action



:beta17
--custom intents (share map position) Added new attributes:
{minlat}{maxlat}{minlon}{maxlon} if you need a BOUNDINGBOX
{EPSG:XXXXX} if you need the coordinates in another reference system.
--Customize the heart beat zones (global settings-->TTS/Sounds-->Heart Monitor


:beta16
--seen area tool (maps button-->map tools). Select two points, and the observer altitude (over Earth surface). The path between the two points will be shown, in green visible area, in red not visible.
--some bugs corrections.


:beta15b
--mapsforge maps with tile size provided by the library, not restricted to 512px, like in last betas.
--Customize 'Share Map Position' adding your custom intents. Map settings-->share map position intents.
You can add different intents, with different actions and open other apps,


:beta14
--bugs corrections
--This version should solve the problem with the need to login every time we connect with Strava
--Maps download. If the download is interrupted (it can happen in very long downloads that Android stops the app) The app will try to resume the download when it restarts



:beta12
--bugs corrections

:beta11
--bugs corrections


:beta9
--bugs corrections


:beta8:
--you can add a new button to left/right button bars, that switches to the previous used map.
--mapsforge changes. Maybe we can solve some pattern issues with some themes...


:beta6:
some important changes.
--updated mapsforge libraries to 0.15 vers.
--added the option to generate generic forms, and attach them to any waypoint type
--new tool added to routes-->route tools (maybe it should be under map tools...): topographic cut. Requires DEM files. 
--...


:beta4:
--bugs correction


:beta3:
--bugs correction
--changes in satellite trip computer view. Al altitude related values can be displayed if you tap the ? value.


:beta2:
--should solve two bugs, double launcher icon and the problem with Drive backup
--added KN 18 geoid model to calculate geoid --> ellipsiod altitude.


:beta1:

--Modified the Tracks editor (of which we already have in our database, from the properties of a Track -> edit). Now we can add new segments, waypoints, join the segments, draw a new path, ...

--Backup/Restore with Drive. Now we can configure a backup of our tracks (and the Tracks database) in our Drive account. At the moment we can only backup the Tracks, later we will possibly include more parts. It is configured in global configuration - integration -> Drive

--Two different algorithms to calculate altitude differences. It can be selected in global configuration - Tracks -> Altitude calculation algorithm:
a) Point to point. It is the preferable in general. It should work better with very bad GPS calculating altitudes, or on flat terrain.
b) Threshold difference. Perhaps it works best in mountainous terrain, and with GPS that measure the most accurate altitude.


orux

Hello!

We start a new beta version.



:beta8
--Disabled mock location provider. It is not ready for a release. It uses a sensitive permission.
--More changes in the map viewer engine. It should be faster.


:beta7
--try to disabled 3D cache if detect problems
minor changes


:beta6
--minor updates
--bugs correction



:beta5
--return to old mapsforge libraries. The new ones weren't a good solution yet. They do a lot of extra work (then they are slower) and have other bad side effects. Let's hope that in future releases they will find a solution to that problem.
--Changes in the 3D viewer. The problem is that now the application tries to cache in files what takes the longest to do, which is 3D meshing. But I can't seem to get a format that works on all devices, there is something that depends on the manufacturer that I do not control. If this doesn't work, I'll see how to disable cache when it's not supported.


:beta4:--some changes in mapsforge libraries:
-added option to modify global scale of objects in global settings - maps - mapsforge settings
-changes to avoid labels cut at the margins of the tiles. does it work? Is rendering slower?
--bug correction with 3D view--select a map for using when creating track thumbnails

:beta3--bugs correction


:beta2--some bugs correction


News:
1.-New Trip Computer View, with satellite information. It should work with both internal or external GPS. You can hide (from the sky view) satellites if you tap the constellation name to the right. And you can sort the satellite list if you tap the column name.



There is a 'save button' at the top buttons bar, that logs the NMEA sentences to a file. Useful for testing purposes,


2.-Map buttons with actions: Global settings-->Application-->Assign actions to keys. If you use an external keypad, keyboard, or similar device, paired with your Android, you can select what each button does.

3.-A new Overlay draw tool. Maps button-->overlay options-->draw overlay. the bottom-left is for selecting the mode you draw lines/polygons/waypoints. Now you can draw with the finger, or with consecutive taps.



4.-OruxMaps as mock locations provider. With that tool, you can replay your Tracks, or use them as simulated locations for other apps. It is a bit hidden that feature:
a) you have to enable developer options in your Android.
b) then, in Developer options, select OruxMaps as mock locations provider app.
c) In the current beta, the only way to start/stop mock locations is by adding a new button at the left/right buttons bar-->mock locations button.d) When you press that button, the app allows you to select the GPX/KML file you want to use for generating mock locations. A new icon will be displayed at the Android buttons bar. If you start the GPS, the app will receive the mock locations, like other apps. If you want to use a Track from your Tracks list, select it, there is a new option to start mock locations with that Track.



You can tweak the mock locations speed if you open the right panel, there are two +/- buttons to increase/decrease the speed of locations sent to the device.



Use it with care! Remember that are simulated locations for all the apps that are listening for locations!




orux

Hola!

He tenido muchos problemas con el foro.

El rendimiento ha sido pésimo durante las últimas semanas. EL hosting ha bloqueado la cuenta varias veces, por excesivo uso de recursos.

No he podido arreglar el problema con el foro anterior, así que me he visto obligado a cambiar el software del foro, con todos los problemas que conlleva.

Pienso que lo importante es no perder toda la información que ya estaba publicada, así que, lamentando mucho los inconvenientes, voy a intentar publicar esta versión del foro.

ESTARÁ EN PRUEBAS UNOS DÍAS, POR FAVOR, NO LE DEIS MUCHA CAÑA!
En función de las pruebas, tomaré una solución definitiva.
LAS FIRMAS DE LOS USUARIOS ESTÁN DESHABILITADAS, NO CAMBIÉIS MUCHO VUESTROS PERFILES, HASTA QUE HAYA UNA SOLUCIÓN DEFINITIVA.

Gracias!

___________________________________________________________________________________________

Hello!

I have had many problems with the forum.

The performance has been very bad in recent weeks. The hosting has blocked the account several times, due to excessive use of resources.

I have not been able to fix the problem with the previous forum, so I have been forced to change the forum software, with all the problems involved.

I think the important thing is not to lose all the information that was already published, so, regretting the inconvenience, I will try to publish this version of the forum.

IT WILL BE IN TESTS A FEW DAYS, PLEASE, DON'T GIVE IT A LOT OF WORK!

Depending on the tests, I will take a definitive solution.
THE SIGNATURES OF THE USERS ARE DISABLED, DO NOT CHANGE YOUR PROFILES, IF IT IS NOT NECESSARY, UNTIL THERE IS A DEFINITIVE SOLUTION.

Thank you!

orux

Siento mucho las molestias de estos últimos días;



Ha habido muchos problemas con el servidor, tanto de la web como del foro.



He tenido que cambiar el foro de hosting.



Supongo que algunos problemas persistirán unos días.



Trabajando para solucionarlos...



_________________________________________________________________________________



I am very sorry for the inconvenience of these last days;



There have been many problems with the server, both the web and the forum.



I had to change the hosting forum.



I guess some problems will persist for a few days.



Working to solve them ...







orux

Hello!

We are working on a new version.
https://oruxmaps.org/forum/index.php?topic=34734.0

:beta42
-->mapsforge update to 0.13

:beta42
-->changes in BT bike power sensor


:beta41
-->draw overlay tool, added new features, now you can draw more types of shapes.
-->we go back to the previous algorithm of calculation of accumulated ascent/descent.



:beta39
-->added a new feature in the 'draw layer' tool: draw a circle with xx distance units radius. Useful for creating geofence alerts, for example, under COVID-19 movement limitations.
-->bugs corrections

:beta38
-->changes in device orientation algorithm. It should be more stable
-->bugs correction

:beta33
--rollback some algorithms (track statistics calculations). It seems they don't work as expected.
--improved WMS and WMTS creation, with a map viewer for immediate testing.

:beta31
--new voice commands added
--some bug correction

:beta30
--support to some voice commands. You can find available voice commands in global settings--text to speech/sounds-->available voice commands. The idea is to be able to operate the app without touching the screen, for example, with gloves.
how does it work? you can trigger voice recognition with:
a) add a new button to the map viewer right/left button bars that start voice recognition.
b) using device hardware volume buttons (configure this option in global settings--text to speech/sounds-->volume buttons, voice commands). For now, it only works if you are displaying the map viewer screen. Hint: How do you open the map viewer, if you are using gloves, for example? If you use Google assistant, you can open any app if you say 'OK Google, open OruxMaps application'. The problem is that Google's assistant is going to open only an app available on Google Play (then it does not work with beta and free versions)! We must wait for the launch of the final version...
c) using google assistant 'ok google' to send commands to the app. Full integration coming soon.

All the commands are simple, the more complex one is creating a new waypoint. You can create a new waypoint if recording a Track, with name, type and description if you say (you can omit the name, type and/or description):
'new waypoint name 'the name of the waypoint' type 'the type from one of the available types' description 'the description'.

A useful command, if you are recording a Track and you want to see the statistics:
1.-open the map viewer, trigger voice recognition (display button or volume button)-->'see statistics' command.
2.-trigger voice recognition (display button or volume button)-->'go back' command.


Hint: You can disable the screen lock for the app, when you turn off the screen, in global settings -> application -> disable the screen saver. This way you can access the map viewer, when you are recording a Track, by pressing the hardware power button.


:beta29
--some bugs removed.

:beta28--new map selector view
--some bugs removed.

:beta27--online composite maps with offline layers.
:beta26
--bug correction with distance measurement.


:beta24
--added support to steps counter (using internal device sensor). You can enable it under global settings--sensors. New dashboard control with this information. A new entry in track statistics.
--support to Tempo Disc 4in1 barometer-termometer-humidity sensor.
--bug with strava solved.


:beta21
-bug correction

:beta20
-bug correction

:beta19
-bug correction

:beta18
--added icons indicating max/min altitude and speed (per segment). You can enable disable those indicators in global settings--Tracks.

:beta16
-bug correction

:beta15
-bug correction

:beta14:
New functionality:
-Added two new controls to the dashboard (altitude above remaining, altitude below remaining)
--includes a new LITE version; with the following idea:
-> meets 90% of the functionality.
-> Useful for 90% of users, especially those who use the app for the first time.
-> the same functionality, accessible only from one place:

The changes only affect the main window (the map navigator). You can swap from one version to the full version in the global settings' main display.

what do you think?





:beta12:
->bugs correction
->Smoother movement of the GPS cursor.

:beta11:
->mapsforge 0.12 libraries update
->minor changes,

:beta10:
->bug corrections.
->changes in some calculation algorithms (motion detection, height gained/lost)


:beta9:
->bug corrections.
->In some devices, it seems that the app can not detect when the navigation bar is hidden in immersive mode. Added a new setting to force that layout in global settings--user interface--miscelaneous.

:beta8: There are a lot of changes, old libraries removed, new added; please, test with care!
->New map display layout, with default semitransparent bars and buttons. The main thing is the map.
->Added a new right panel, with the main information (speed, altitude, distances,... and two graphics (current track, route followed). Swipe the finger from the right side of the display.
->New graphics library; I expect better. You can tap and see the value.



->New Tracks display layout, with more information, including a Track thumbnail. Those thumbnails are only calculated for new Tracks, or when the Track is loaded (for follow, see statistics,...) because it is a hard task; if you want to force the calculation of the thumbnails, there is an option in the Track list, 'more options' button.




:beta6:
->support two separate BT 4.0 sensors (Bike Cadence and Speed).
->Android wear module, now you can get the heart rate from your watch. Configure that feature in global settings--sensors--heart rate.


:beta5:
some improvements in the coordinates conversion tool.

:beta3:
->improved support to KML format. Added support to icon rotation attribute
->bug corrections.

New:
-> Activated SOS function with sending email messages. Due to the restrictions of Google Play to publish apps that send SMS messages, I decided to activate this feature.
CREATE A SPECIFIC GMAIL ACCOUNT ONLY FOR THAT PURPOSE, DO NOT USE YOUR USUAL ACCOUNTS!

-> New configuration screens. With search function; there are already too many and it is difficult to find some at times.
-> GPS Week rollover problem fix in devices that suffer that problem. Settings - sensors - GPS
-> Added new buttons to some screens.
-> New experimental map render engine.
-> Weather forecast at map center position. 5 days / 3 hours. Map viewer, more button.
-> Import Waypoints in .csv format
The fields that are recognized are:
"name"
"description"
"position"-->latitude,longitude
"latitude"
"longitude"
"icon"-->url to a png
"iconcolor"-->hexadecimal format
"altitude"
"time" & "date"-->different timestamps


orux

Hello!



Here a new beta version: https://www.oruxmaps.com/OruxMaps7.5.4beta1.apk">//https://www.oruxmaps.com/OruxMaps7.5.4beta1.apk



4beta1:

some bug fixes





:2beta6:

bugs correction



:2beta3:

changes in ANT services

now you can change the timestamp of a track/waypoint

bugs correction





:2beta2:

bugs correction



:2beta1:

changes in follow route mode, trying to make the next waypoint warnings more accurate.

bugs correction









orux