Print Page - new beta 7.1.7betaX [closed]

Title: new beta 7.1.7betaX [closed]
Post by: orux on July 14, 2017, 09:08:03 PM

Hello,

NO BETA AVAILABLE, USE THE LAST RELEASE VERSION

:rc1:

->added translations

->some bugs correction.

:beta10:

->added an new option in settings--tracks-->keep routes on screen.

->some bugs correction.

:beta9:

->new button for night mode

->bug corrections

:beta8:

->added transparent mode in dashboard/buttons buttons bar (settings-->user interface-->colors).

->some changes in listview, added cardviews as background.

->some bugs removed.

(//%3C/s%3E%3CURL%20url=%22https://image.ibb.co/bzNgD6/Screenshot_20171029_091154.jpg%22%3E%3CLINK_TEXT%20text=%22https://image.ibb.co/bzNgD6/Screenshot_%20...%20091154.jpg%22%3Ehttps://image.ibb.co/bzNgD6/Screenshot_20171029_091154.jpg%3C/LINK_TEXT%3E%3C/URL%3E%3Ce%3E)

:beta7:

->more changes in .fit files

->changes in simplified list of wpts.

:beta6:

->more changes in .fit files

->added a simplified view of wpts list, that you can use if you have a lot of wpts, and the view takes a lot of time loading. settings-->wpts-->simplified view.

:beta5:

->changes in .fit files

:beta4

->bug corrections

->language updates

:beta3

->change color of GPS position distance circles indicator and target wpt.->settings->user interface->colors

->change width of distance circles.->settings->user interface->tracks, paths,...

->Center map dialog with all type coordinates (degrees, utm, swiss grid, mgrs,...).

:beta1

->adjustment to slightly increase the size of the dashboard texts (settings-->user interface-->dashboard-->dashboard text size)

->new help button in some screens (non definitive help texts)

->change of some internal libraries

->some bugs corrections

old betas:

->some bugs corrections.

->Added concentric circles in the GPS cursor and the destination Wpt, to indicate distances. Active by default in the beta, for testing, will be disabled by default in the final version.

->some bugs corrections.

->new system to keep alive the app and avoid Doze.

->capture url links to .gpx/.kml/.kmz files. The app offers itself to dowload that files to oruxmaps/tracklogs/ folder.

->solved bug with TMG line using some maps.

orux

Title: Re: new beta 7.0.18betaX
Post by: mett on July 14, 2017, 09:51:42 PM

Thanks Orux. I will Test the new beta. Please consider to have a setting for not expiring the beta!

This is handy because it could be that you do not deliver any new betas for a long time, or I am in travel in some remote with no internet and the beta expires! Please!!

Sent from my SM-G900F using Tapatalk

Title: Re: new beta 7.0.18betaX
Post by: eartrumpet on July 21, 2017, 10:23:25 PM

Hi Orux,

thanks for the new beta version with mapsforge 0.8. I experimented a bit with the new hillshade option, but in the end I prefer the old one because of better contrast/less overall tinting.

What's good about the mapsforge hillshade in comparison:

- "magnitude" option for strength of hillshade

- zoom-min/max options

- can be positioned in theme so e.g. roads or labels aren't affected

Not so good:

- errors on tile borders at large zoom levels are also there (but more subtle, as contrast on old OruxMaps hillshade is very high)

- heavily tints flat areas or "bright" slopes, so not a lot of contrast and changes theme too much (this is what kills it for me)

With more contrast and less tinting the mapsforge hillshade would be interesting, so I'll drop a note there.

For the OruxMaps hillshade the magnitude and zoom-min/max options would be really valuable, as I always found that the hillshade was a bit too dark, and not necessary at some zoom levels. What also would help would be more blur at high zoom levels.

What's not working: using version="6" in <rendertheme> tag, theme can't be loaded then. Might be a mapsforge bug, but as <hillshading> is a rendertheme-v6 tag, it should only work with this (and not version="5").

Title: Re: new beta 7.0.18betaX
Post by: topolaino on July 22, 2017, 09:57:46 PM

Hello Orux,

I write again about the problem of elevation gain.

I made other tests and I realized that during the recording of the track, the elevation gain is correct and corresponds to other GPS tools. The problem is when you stop the track and the app stores the track. If you look at track statistics, you find a much lower value. I send you two screenshotts, one just before the stop of track and one of the stats on the same track.

For pleasure Orux let me know if you can fix it.

vincenzo from italy

(//%3C/s%3E%3CURL%20url=%22https://1drv.ms/i/s!Ah8FDIlWYwLCg2kt4CupsP5SRiwr%22%3Ehttps://1drv.ms/i/s!Ah8FDIlWYwLCg2kt4CupsP5SRiwr%3C/URL%3E%3Ce%3E)

~~(//%3C/s%3E%3CURL%20url=%22https://1drv.ms/i/s!Ah8FDIlWYwLCg2iIPTeYttNkEcSi%22%3Ehttps://1drv.ms/i/s!Ah8FDIlWYwLCg2iIPTeYttNkEcSi%3C/URL%3E%3Ce%3E)~~

Title: Re: new beta 7.0.18betaX
Post by: ThomasSc on July 23, 2017, 09:22:48 AM

That's what I posted

http://www.oruxmaps.com/foro/viewtopic.php?p=11688#p11688

I don't know how difficult it is to create an own "gps-filter" for users, to set values before first saveing.

Thomas

Title: Re: new beta 7.0.18betaX
Post by: Mapper-Alps12 on July 23, 2017, 10:56:09 AM

Hi Orux,

I've tested the Geo-PDF function, it works great. I'm just missing one kind of Geo-PDF, therefore I've sent you a PM with an example. It would be great if you could add this Kind of Geo-PDF to your great app.

Once again, thank you very much for your work!

Title: Re: new beta 7.0.18betaX
Post by: orux on July 24, 2017, 09:14:11 PM

~~Quote from: "ThomasSc"~~That's what I posted

http://www.oruxmaps.com/foro/viewtopic.php?p=11688#p11688

I don't know how difficult it is to create an own "gps-filter" for users, to set values before first saveing.

Thomas

Creating custom filters is not easy.

The latest beta further softens the filter used.

I will add an option to disable last filter (used when the track is finished).

orux

Title: Re: new beta 7.0.18betaX
Post by: ThomasSc on July 25, 2017, 08:40:32 AM

~~Quote from: "orux"~~
I will add an option to disable last filter (used when the track is finished).

orux

Thanks, that would be great.

Thomas

Title: Re: new beta 7.0.18betaX
Post by: topolaino on July 25, 2017, 10:28:52 PM

~~Quote from: "orux"~~

Creating custom filters is not easy.

The latest beta further softens the filter used.

I will add an option to disable last filter (used when the track is finished).

orux

If I understand well, this will also solve my problem!

Thanks Orux

Title: Re: new beta 7.0.18betaX
Post by: ThomasSc on July 28, 2017, 07:59:35 PM

Hi orux,

thank you very much for implementing "Apply altitude filter". :D

I will try it tomorrow.

Thomas

Title: Re: new beta 7.0.18betaX
Post by: eartrumpet on July 28, 2017, 10:29:59 PM

Orux, could you please post in the beta threads again when there's a new beta? This way subscribers get a message. By just changing the first post I already missed several updates in the last round. Thanks!

Title: Re: new beta 7.0.18betaX
Post by: Maki on July 28, 2017, 10:38:25 PM

~~Quote from: "topolaino"~~Hello Orux,

I write again about the problem of elevation gain.

I made other tests and I realized that during the recording of the track, the elevation gain is correct and corresponds to other GPS tools. The problem is when you stop the track and the app stores the track. If you look at track statistics, you find a much lower value. I send you two screenshotts, one just before the stop of track and one of the stats on the same track.

For pleasure Orux let me know if you can fix it.

vincenzo from italy

In my experience the more credible value is the one after you stop recording. This on my MotoX 2014 that has no barometer, so I'm using LIDAR-derived DEMs. I tried once with my mother's S5 (last Play Store version on that one) using the barometer and I got a stat with almost the doble of the real world value.

Title: Re: new beta 7.0.18betaX
Post by: ThomasSc on July 29, 2017, 05:29:23 PM

The new "Apply altitude filter" is really great.

If switched off, the ascent and descent are nearly the same on the Monterra with oruxmaps, the VDO MC2.0 WL and the Suunto T6d.

Thank you very much.

Thomas

Title: Re: new beta 7.0.18betaX
Post by: Tobias on August 01, 2017, 11:50:17 AM

When the speaker bug is fixed in Android O beta I will have a go

to see if the new features harm oruxmaps usability.

Adnroid O will already be released in September for nexus devices.

//https://developer.android.com/preview/behavior-changes.html

Especially the background location limits and Background execution limits could be problems.

Shortcuts, eg to start a recording, would be very cool and the adaptive icons could make ppl happy too :)

Title: Re: new beta 7.0.18betaX
Post by: orux on August 01, 2017, 10:13:22 PM

Hello!

A new RC version,

orux

Title: Re: new beta 7.0.18betaX
Post by: orux on August 02, 2017, 06:49:40 PM

~~Quote from: "orux"~~Hello!

A new RC version,

orux

Sorry,

updated to rc2 version.

orux

Title: Re: new beta 7.0.18betaX
Post by: eartrumpet on August 02, 2017, 10:19:10 PM

Thanks for posting updates again.

The pattern bug with mapsforge maps and hires displays is back, probably with implementing mapsforge 0.8. The tile sizes are tiny now, probably 256px instead of 1024px which leads to crowded maps. See attached screenshots:

Pattern bug:

(//%3C/s%3E%3CURL%20url=%22http://i.imgur.com/BpgY4Ce.png%22%3Ehttp://i.imgur.com/BpgY4Ce.png%3C/URL%3E%3Ce%3E)

7.1 RC2:

(//%3C/s%3E%3CURL%20url=%22http://i.imgur.com/ZdsiWQ7.jpg%22%3Ehttp://i.imgur.com/ZdsiWQ7.jpg%3C/URL%3E%3Ce%3E)

Same position/zoom in 7.0.17:

(//%3C/s%3E%3CURL%20url=%22http://i.imgur.com/C3i8753.png%22%3Ehttp://i.imgur.com/C3i8753.png%3C/URL%3E%3Ce%3E)

File path handling is not really working at the moment (Android 7.1.1)

- Every time I update I'm asked again for access right of SD card, is that necessary?

- I also have an old setting where the path is /sdcard/oruxmaps, when trying to change the path to external sdcard it is not possible, as "root" is the base folder of /sdcard/, it says then "Can not access """.

- With other settings like /storage/1EE8-1D0C/oruxmaps, I can change to /storage/, but when choosing "emulated" for internal sdcard, nothing happens.

And a final idea: as the non-donate is not available on google play anymore, does this check for updates on the website? I use the donate version, but have installed the free one for friends, and it would be good if they are reminded for updates.

Title: Re: new beta 7.0.18betaX
Post by: topolaino on August 02, 2017, 11:30:56 PM

~~Quote from: "ThomasSc"~~The new "Apply altitude filter" is really great.

If switched off, the ascent and descent are nearly the same on the Monterra with oruxmaps, the VDO MC2.0 WL and the Suunto T6d.

Thank you very much.

Thomas

I don't found "Apply altitude filter"...

Where is it? :geek:

Title: Re: new beta 7.0.18betaX
Post by: ThomasSc on August 03, 2017, 10:47:07 AM

~~Quote from: "topolaino"~~
~~Quote from: "ThomasSc"~~The new "Apply altitude filter" is really great.

If switched off, the ascent and descent are nearly the same on the Monterra with oruxmaps, the VDO MC2.0 WL and the Suunto T6d.

Thank you very much.

Thomas

I don't found "Apply altitude filter"...

Where is it? :geek:

It's in "Global settings" -> "Tracks/Routes", the last feature.

Thomas

Title: Re: new beta 7.0.18betaX
Post by: topolaino on August 03, 2017, 01:10:38 PM

~~Quote from: "topolaino"~~
I don't found "Apply altitude filter"...

Where is it? :geek:

Ok I find it. Pardon

Orux thank you very much

Title: Re: new beta 7.0.18betaX
Post by: orux on August 03, 2017, 04:35:49 PM

~~Quote from: "eartrumpet"~~Thanks for posting updates again.

The pattern bug with mapsforge maps and hires displays is back, probably with implementing mapsforge 0.8. The tile sizes are tiny now, probably 256px instead of 1024px which leads to crowded maps. See attached screenshots:

File path handling is not really working at the moment (Android 7.1.1)

- Every time I update I'm asked again for access right of SD card, is that necessary?

- I also have an old setting where the path is /sdcard/oruxmaps, when trying to change the path to external sdcard it is not possible, as "root" is the base folder of /sdcard/, it says then "Can not access """.

- With other settings like /storage/1EE8-1D0C/oruxmaps, I can change to /storage/, but when choosing "emulated" for internal sdcard, nothing happens.

And a final idea: as the non-donate is not available on google play anymore, does this check for updates on the website? I use the donate version, but have installed the free one for friends, and it would be good if they are reminded for updates.

Hi;

Tile size: clean the raster cache, then refresh the map list, the tile size should not be 256px if you have a hi-res device, strange...

Patterns problem: check if still present after refresh map list. There are no changes when using the mapsforge library compared to previous version, only upgrade to 0.8

Sd write permission: The app checks all the folders (maps, tracks, geocaches, styles, dems and overlays) when a new version is installed. Check if selected folder contains all those folders. I am going to change the message that is show when the app can not write a folder.

You can use all the internal/external folders. Internal storage is in Root/sdcard/ folder, /emulated/ folder is not usable. To change from external to internal storage, using the built in file browser, click 'Root' in the current path, then select /sdcard/.

I am working with a check option in the free version to warn about new version available.

orux

Title: Re: new beta 7.0.18betaX
Post by: eartrumpet on August 03, 2017, 06:50:23 PM

~~Quote from: "orux"~~Tile size: clean the raster cache, then refresh the map list, the tile size should not be 256px if you have a hi-res device, strange...

This doesn't help, same result as above with freshly cleared raster cache, 440ppi screen.
~~Quote~~Patterns problem: check if still present after refresh map list.

A solution for the tile size bug should fix this problem, too, at least last time it worked.

~~Quote~~Sd write permission: The app checks all the folders (maps, tracks, geocaches, styles, dems and overlays) when a new version is installed. Check if selected folder contains all those folders. I am going to change the message that is show when the app can not write a folder.

Is it really necessary to ask for those rights again after every update? Other apps don't.

~~Quote~~You can use all the internal/external folders. Internal storage is in Root/sdcard/ folder, /emulated/ folder is not usable. To change from external to internal storage, using the built in file browser, click 'Root' in the current path, then select /sdcard/.

As written above, when I choose 'Root', I get the message 'Can not access ""'. No way to change from external to internal.

Title: Re: new beta 7.0.18betaX
Post by: eartrumpet on August 03, 2017, 07:14:41 PM

Another thing: save and load buttons are missing in the profiles screen.

Title: Re: new beta 7.0.18betaX
Post by: orux on August 03, 2017, 10:57:51 PM

~~Quote from: "eartrumpet"~~
~~Quote from: "orux"~~Tile size: clean the raster cache, then refresh the map list, the tile size should not be 256px if you have a hi-res device, strange...

This doesn't help, same result as above with freshly cleared raster cache, 440ppi screen.
~~Quote~~Patterns problem: check if still present after refresh map list.

A solution for the tile size bug should fix this problem, too, at least last time it worked.

~~Quote~~Sd write permission: The app checks all the folders (maps, tracks, geocaches, styles, dems and overlays) when a new version is installed. Check if selected folder contains all those folders. I am going to change the message that is show when the app can not write a folder.

Is it really necessary to ask for those rights again after every update? Other apps don't.

~~Quote~~You can use all the internal/external folders. Internal storage is in Root/sdcard/ folder, /emulated/ folder is not usable. To change from external to internal storage, using the built in file browser, click 'Root' in the current path, then select /sdcard/.

As written above, when I choose 'Root', I get the message 'Can not access ""'. No way to change from external to internal.

OK,

I found that the context is initialized differently in version 0.8; because of that your system was always using a size of 256px. I will correct it.

It's true, google has done it again. In android 7.1.1 navigation through the root directory is not allowed. I'll add two buttons to jump directly from internal to external storage without having to go through the root directory.

The app don't ask for permission after the update if it can write in all folders. Next version will tell you which folders are not under the authorized folder.

orux

Title: Re: new beta 7.0.18betaX
Post by: Joska on August 04, 2017, 08:07:32 AM

~~Quote from: "orux"~~

It's true, google has done it again. In android 7.1.1 navigation through the root directory is not allowed. I'll add two buttons to jump directly from internal to external storage without having to go through the root directory.

orux

Hello orux

As I have written before, this is no problem of android 7.1...

This behavior I found in Android 7.0 on my Sony Z5c too.

But i suppose, it wasn't obvious because of my bad English éxplanation. :D

Best regards, Joska

Title: Re: new beta 7.0.18betaX
Post by: orux on August 04, 2017, 09:28:00 PM

Thanks to all;

updated the rc version.

file browser: added buttons to go to external/internal storage

mapsforge: tile size bug should be correct now

initial dialog about write permission will show folders where app can not write and need permission.

save/load buttons removed in profiles screen because those files are permanently synchronized.

orux

Title: Re: new beta 7.0.18betaX
Post by: eartrumpet on August 05, 2017, 09:44:54 AM

~~Quote from: "orux"~~Thanks to all;

updated the rc version.

file browser: added buttons to go to external/internal storage

Thanks, this works now with Android 7.1.1. Only thing not working is "new folder..." in folder selection dialogue on external sd card, although I can write on this folder with other functions.
~~Quote~~mapsforge: tile size bug should be correct now

Yes, it does, and no problems with patterns too.
~~Quote~~initial dialog about write permission will show folders where app can not write and need permission.

Thanks, it shows several folders with old SDCard addresses (as I updated Android while using the same settings of OruxMaps) like "storage/sdcard1/" which don't exist anymore, so access writes is not the problem here. Would it be possible to check for these and auto-correct them according to android version?

~~Quote~~save/load buttons removed in profiles screen because those files are permanently synchronized.

Auto-saving does work, but not auto-loading. If I define a new profile in OruxMaps Donate, it won't show in OruxMaps Beta. So I can't import settings for testing anymore.

Title: Re: new beta 7.0.18betaX
Post by: orux on August 06, 2017, 10:14:20 PM

Hi,

~~Quote~~Only thing not working is "new folder..." in folder selection dialogue on external sd card

The browser is an old library, does not support SAF. I will try to change it in a future version.

~~Quote~~ it shows several folders with old SDCard addresses (as I updated Android while using the same settings of OruxMaps) like "storage/sdcard1/" which don't exist anymore, so access writes is not the problem here. Would it be possible to check for these and auto-correct them according to android version?

Not sure, I will see.

~~Quote~~Auto-saving does work, but not auto-loading.

The auto loading only happens after new version update. I will add a 'resync' button.

orux

Title: Re: new beta 7.0.18betaX
Post by: Maki on August 06, 2017, 10:40:43 PM

Today I wanted to test the altitude filters and I tried to make a track segment that has no descent in it (so that it is easy to know the exact difference between start-point and end-point). To do that I used the notification button, which didn't give me any errors or confirmations. When looking at stats I don't see the segments, so it seems that the button doesn't work.

Another related thing. The notification has three buttons (stop, new wpt, new segment) that have the same width despite hosting strings with different length. Not only this looks odd, but the last one is truncated because it's too long.

I had two phones (S5 and Moto X 2014, all with Android 6.0.1) and both exhibit the same behavior.

Title: Re: new beta 7.0.18betaX
Post by: Off-track on August 07, 2017, 03:05:38 AM

I previously set up OM in emulated memory on an SD card, because that was the way I could get OM v 7.0.12 to use the SD card under Android 6 //http://bushwalk.com/forum/viewtopic.php?f=21&t=25950. This continued to work until v7.0.18 beta3, but it gives problems with v 7.1.0 rc3. It still works with some things in emulated memory (like offline maps), but not with others (like custom waypoints). Looking at folder settings, I guess it will not find a bunch of other stuff like DEMs, but I have not explicitly tested them yet.

I did not see or find any of the messages about available folders mentioned above.

I got the custom waypoints to work by copying the folder (under Win Explorer) from:

ComputerZTE Blade A462SD cardAndroiddatacom.orux.oruxmapsfilescustomwpts

to:

ComputerZTE Blade A462SD cardAndroiddatacom.orux.oruxmapsbetafilesexternalcustomwpts

OM > Global Settings > Application > Migrate to Ext. SD failed ("No SD found!"). Working through the phone (Settings > Apps > OruxMaps Beta > Storage >Change) allowed a shift to SD, but this caused problems for me that needed an uninstall and reinstall of the OM Beta, so I am not doing it again! Probably there is no need, as all the memory-consuming data really is already in the SD card (still set up as emulated internal memory).

Probably people can get it to work by copying relevant folders as mentioned for custom waypoints above.

I do not know what will happen when new maps are downloaded. Overall it seems tricky for those who have set up SD cards as emulated internal memory under Android 6. Maybe Orux can simplify the upgrade to recognise this better in the official release?

Title: Re: new beta 7.0.18betaX
Post by: orux on August 07, 2017, 10:46:36 PM

~~Quote from: "Maki"~~Today I wanted to test the altitude filters and I tried to make a track segment that has no descent in it (so that it is easy to know the exact difference between start-point and end-point). To do that I used the notification button, which didn't give me any errors or confirmations. When looking at stats I don't see the segments, so it seems that the button doesn't work.

Another related thing. The notification has three buttons (stop, new wpt, new segment) that have the same width despite hosting strings with different length. Not only this looks odd, but the last one is truncated because it's too long.

I had two phones (S5 and Moto X 2014, all with Android 6.0.1) and both exhibit the same behavior.

Thanks.

Only the 'new segment' button doesn't work?

The actions (size and positions) are managed by android; not sure if will be easy to change, I will see.

orux

Title: Re: new beta 7.0.18betaX
Post by: orux on August 07, 2017, 10:49:05 PM

~~Quote from: "Off-track"~~I previously set up OM in emulated memory on an SD card, because that was the way I could get OM v 7.0.12 to use the SD card under Android 6 //http://bushwalk.com/forum/viewtopic.php?f=21&t=25950. This continued to work until v7.0.18 beta3, but it gives problems with v 7.1.0 rc3. It still works with some things in emulated memory (like offline maps), but not with others (like custom waypoints). Looking at folder settings, I guess it will not find a bunch of other stuff like DEMs, but I have not explicitly tested them yet.

I did not see or find any of the messages about available folders mentioned above.

I got the custom waypoints to work by copying the folder (under Win Explorer) from:

ComputerZTE Blade A462SD cardAndroiddatacom.orux.oruxmapsfilescustomwpts

to:

ComputerZTE Blade A462SD cardAndroiddatacom.orux.oruxmapsbetafilesexternalcustomwpts

OM > Global Settings > Application > Migrate to Ext. SD failed ("No SD found!"). Working through the phone (Settings > Apps > OruxMaps Beta > Storage >Change) allowed a shift to SD, but this caused problems for me that needed an uninstall and reinstall of the OM Beta, so I am not doing it again! Probably there is no need, as all the memory-consuming data really is already in the SD card (still set up as emulated internal memory).

Probably people can get it to work by copying relevant folders as mentioned for custom waypoints above.

I do not know what will happen when new maps are downloaded. Overall it seems tricky for those who have set up SD cards as emulated internal memory under Android 6. Maybe Orux can simplify the upgrade to recognise this better in the official release?

Thanks;

I will check your comments,

orux

Title: Re: new beta 7.0.18betaX
Post by: orux on August 07, 2017, 10:49:29 PM

A new rc version with small changes.

orux

Title: Re: new beta 7.0.18betaX
Post by: Maki on August 08, 2017, 11:22:48 PM

~~Quote from: "orux"~~Only the 'new segment' button doesn't work?

Tried again today on the MotoX with RC4, nothing works. Actually I never used the notification actions, so I don't know when they stopped working or if they ever worked at all (but I suppose thy did).

Why not using icons rather than text for the buttons. I see other apps doing that, so it should be possible. It would also mean less text strings to manage and a more consistent interface since you would be using the same icons in the app. And maybe there would be room for more buttons. That said I don't find this feature that useful, so I wouldn't lose my sleep on it.

Title: Re: new beta 7.0.18betaX
Post by: Maki on August 08, 2017, 11:37:37 PM

Regarding the elevation filter, I disabled the correction in the preferences, and recorded a track that showed 797m elevation gain in the stats (on the MotoX, so altitudes are from the DEMs). I corrected the altitude using the default rounding and it still was 797. I then enabled the correction in the preferences and corrected again the elevation using the default rounding and got 770m (which I believe is closer to reality).

I think this behavior is wrong, if I explicitly ask the app to correct the altitude using DEMs it should always do it, the preference should affect only automatic correction when stopping the recording.

That said I still think that the wrong value is the one without correction, so rather than disabling the correction it should actually be performed live when recording the track, so that the dashboard shows real values. But I need to do some more testing, hopefully next week.

As a side note, it would be useful to add a suffix or something to the track name when one performs a correction, so that it is clear which one one is the original and which one the manipulated one. Currently you see two tracks with identical name.

Title: Re: new beta 7.0.18betaX
Post by: orux on August 09, 2017, 04:37:24 PM

~~Quote from: "Maki"~~Regarding the elevation filter, I disabled the correction in the preferences, and recorded a track that showed 797m elevation gain in the stats (on the MotoX, so altitudes are from the DEMs). I corrected the altitude using the default rounding and it still was 797. I then enabled the correction in the preferences and corrected again the elevation using the default rounding and got 770m (which I believe is closer to reality).

I think this behavior is wrong, if I explicitly ask the app to correct the altitude using DEMs it should always do it, the preference should affect only automatic correction when stopping the recording.

That said I still think that the wrong value is the one without correction, so rather than disabling the correction it should actually be performed live when recording the track, so that the dashboard shows real values. But I need to do some more testing, hopefully next week.

As a side note, it would be useful to add a suffix or something to the track name when one performs a correction, so that it is clear which one one is the original and which one the manipulated one. Currently you see two tracks with identical name.

Hello,

The description of the last filter may be incorrect.

The app applies different filters/corrections:

When a track is recorded, a correction to the altitude value is applied to each positioning. It is the altitude of each point recorded in the database.

When the function of correcting the altitude of a track is applied, the same thing happens (different algorithms), and the altitude value of each point is altered.

Finally, if the new filter checkbox is active, a different algorithm is applied which, without altering the altitude value of each point, calculates the altitude ascent/descent values. Then this filter/correction can be applied in both situations, because it calculates/modifies different values.

orux

Title: Re: new beta 7.0.18betaX
Post by: Maki on August 09, 2017, 10:30:17 PM

The preference explanation says
~~Quote~~Apply a filter that corrects GPS fix problems with altitude. Filter smoothes the altitude, after you stops recording the Track

It say nothing about the "correct altitude" you can apply afterwards to an already recorded track. If I understand correctly how things work then yes, the description is inaccurate.

However the real world problem with the current Play Store release is that during my hike I see from the dashbord that my elevation gain is 150m, then when I stop the recording and look at the stats I see 120m. At least one of the two numbers is wrong, this is confusing and makes the app feeling unreliable, it should be solved.

I will not be able to do definitive tests before next week, but my feeling after comparing with on paper calculations is that the dashboard value is the wrong one.

Title: Re: new beta 7.0.18betaX
Post by: ThomasSc on August 10, 2017, 12:07:10 PM

Hi orux,

please do not change something in "Apply altitude filter" and Altitude in "Barometer"-Mode.

Thank you.

Thomas

Title: Re: new beta 7.0.18betaX
Post by: orux on August 10, 2017, 10:15:07 PM

~~Quote from: "ThomasSc"~~Hi orux,

please do not change something in "Apply altitude filter" and Altitude in "Barometer"-Mode.

Thank you.

Thomas

A new version, with new iw language files, and a new feature for testing.

orux

Title: Re: new beta 7.0.18betaX
Post by: Off-track on August 12, 2017, 07:54:21 AM

1. Updating from my post above about having to copy folders:

On the initial load of OM v 7.1.0 rc6 (and my profile and a refresh of offline maps), the app found my offline maps which were set up in /storage/emulated/0/Android/data/com.orux.oruxmaps/files/mapfiles/; but it did not find my custom waypoint types that were set up in /sdcard/Android/data/com.orux.oruxmaps/files/customwpts/. It used default waypoint symbols instead.

However, when restarted, it found everything (all still in emulated internal memory under Android 6). Maybe users can be advised that if things seem lost after upgrade, try a complete close and restart of v 7.1.0. No copying of folders is needed.

OM v 7.1.0 rc6 does not reload overlays by default, but you can set it to do this through Global settings > Maps > KML overlay settings > Keep KML overlays. (Probably this was always the case, I have forgotten).

2. I also tested the new shp overlay feature. It worked when I copied the right files directly into the OM overlay folder:

First I tried copying there a folder (contour.shp) that included .shp and .prj files (among others) as used by some other GIS programs. This did not work too well (after navigating deeper OM complained that it could not find a prj file, but it then loaded correctly as my shp was in WGS84).

Then I tried copying there just the shp and prj files. It worked fine (though slow with this big and complex shp file: 37 Mb!). The result in my test was lots of contour lines. (They were green in OM, and did not scale in thickness as I zoomed out, so a bit of a mess in steep areas. I guess it would need some of the other files from the full shapefile folder to get attributes, but I understand this would be complex, and it was not the intended use). It will be useful as is for simpler layers and it should save some users some work translating from shp to kml. In other cases kml may be preferred as it does embed some easily editable attributes (such as line color)?

Title: Re: new beta 7.0.18betaX
Post by: Maki on August 16, 2017, 05:55:15 PM

I tried with RC6. Notification buttons are hit or miss. "New segment" worked a couple of times and then no more, the others never worked.

I'm puzzled about the altitude filters, it looks they aren't working.

Sunday I had a good MTB ride, with the altitude filter set to on and the uphill reading was basically spot-on (easy to check because very long, smooth terrain and almost no intermediate descents). Also when stopping the track the difference between the stats and the dashboard were minimal. Just to check I disabled the filter and corrected the altitude; I expected some difference and... got exactly the same values!

Monday I had short ride in the bottom of a valley, always with the filters set to on. The difference between the stats and the dashboard were less than before. At the end I got 140m total. Previously after stopping the recording I was getting around 120m which is more or less the same value I get loading the same track in TwoNav Land. Land allows me to see the altimetric profile side by side with the map. I see some mild oscillations and some false, sharp, small, ups and downs when passing on a small bridge. However 5 meters here and 5 meters there... it adds up. This is a tricky situation for a software to evaluate, but comparing with paper calculations the filter you were using previously seems better. Again I disabled the filter and corrected the altitude --> no changes in the stats.

Title: Re: new beta 7.0.18betaX
Post by: orux on August 16, 2017, 11:19:19 PM

~~Quote from: "Maki"~~I tried with RC6. Notification buttons are hit or miss. "New segment" worked a couple of times and then no more, the others never worked.

It is a problem with beta versions, it should work in release versions.

~~Quote from: "Maki"~~
I'm puzzled about the altitude filters, it looks they aren't working.

Sunday I had a good MTB ride, with the altitude filter set to on and the uphill reading was basically spot-on (easy to check because very long, smooth terrain and almost no intermediate descents). Also when stopping the track the difference between the stats and the dashboard were minimal. Just to check I disabled the filter and corrected the altitude; I expected some difference and... got exactly the same values!

Monday I had short ride in the bottom of a valley, always with the filters set to on. The difference between the stats and the dashboard were less than before. At the end I got 140m total. Previously after stopping the recording I was getting around 120m which is more or less the same value I get loading the same track in TwoNav Land. Land allows me to see the altimetric profile side by side with the map. I see some mild oscillations and some false, sharp, small, ups and downs when passing on a small bridge. However 5 meters here and 5 meters there... it adds up. This is a tricky situation for a software to evaluate, but comparing with paper calculations the filter you were using previously seems better. Again I disabled the filter and corrected the altitude --> no changes in the stats.

If the GPS has good coverage, and it is accurate, it is logical that both values look like.

The final filter will give a different value with a bad GPS, or in plain routes.

You can see the variability of the GPS measurements if you open the track in gpx format with a text editor.

Updated the test version.

Although the official version 7.1.0 is already released, I keep this version because it incorporates a different system to prevent android stops sending GPS positions to save energy.

orux

Title: Re: new beta 7.0.18betaX
Post by: Maki on August 18, 2017, 10:23:50 PM

I don't know... with previous RC using the filter or not made a sensible difference on that track.

I tried with other tracks and I'm even more puzzled. With this one I see a difference in the elevations. At the same time I saved the corrected tracks and examined them on the PC (Notepad ++ compare plugin) and they are exactly the same; yet, they generate different stats in OruxMaps. Looking at the graph in TwoNav Land too, the two corrected tracks (with and without filter) are exactly the same, and the difference with the original one is noticeable. It's so confusing...

Apart from this I've just read an interesting suggestion on the Italian Play Store. Make the graphs zoom independently on the two axis. With long tracks the graph is actually quite compressed horizontally and hard to read.

Title: Re: new beta 7.0.18betaX
Post by: Tobias on August 23, 2017, 12:28:03 PM

Hi,

In the current release 7.1.2 there is still a problem with DEM and possibly general directory access for me:

Nexus 5x , Android 8.0.0 (it was also the case in Android 7.1.2 adn the same device)

If I open orux, DEM files aren't loaded:

//https://drive.google.com/file/d/0B3TtNI94YOyXSGdsd0ZOS0RybTg/view?usp=sharing

Then I look up the directory, it is shown as empty. This is the case since nougat I think ?

//https://drive.google.com/file/d/0B3TtNI94YOyXSXZOSEVlTEJvR28/view?usp=sharing

After hitting "ok", DEM files are working properly:

//https://drive.google.com/file/d/0B3TtNI94YOyXTWt1SlpEdUJhX00/view?usp=sharing

The behavior is inconsistent, I can open and close the app after doing the process described and DEM is still working.

But before every workout I have to do it again.

I can provide a bugreport / system protocol in a pm if it helps?

_______

I just noticed RC7.

Are the gps fixed included in the latest release? I got some problem lately, but thought it's because of beta Android.

Title: Re: new beta 7.0.18betaX
Post by: orux on August 24, 2017, 04:57:52 PM

~~Quote from: "Tobias"~~Hi,

In the current release 7.1.2 there is still a problem with DEM and possibly general directory access for me:

Nexus 5x , Android 8.0.0 (it was also the case in Android 7.1.2 adn the same device)

If I open orux, DEM files aren't loaded:

//https://drive.google.com/file/d/0B3TtNI94YOyXSGdsd0ZOS0RybTg/view?usp=sharing

Then I look up the directory, it is shown as empty. This is the case since nougat I think ?

//https://drive.google.com/file/d/0B3TtNI94YOyXSXZOSEVlTEJvR28/view?usp=sharing

After hitting "ok", DEM files are working properly:

//https://drive.google.com/file/d/0B3TtNI94YOyXTWt1SlpEdUJhX00/view?usp=sharing

The behavior is inconsistent, I can open and close the app after doing the process described and DEM is still working.

But before every workout I have to do it again.

I can provide a bugreport / system protocol in a pm if it helps?

_______

I just noticed RC7.

Are the gps fixed included in the latest release? I got some problem lately, but thought it's because of beta Android.

Hello;

there is a new beta.

about DEM problem: do you use the external storage as an extension of the internal storage?

you don't see the DEM files because the browser is configured as a folder selector, then the files are not displayed.

the GPS problem. Do you mean the problems with the buttons/actions in the notification?

orux

Title: Re: new beta 7.0.18betaX
Post by: Tobias on August 24, 2017, 09:12:42 PM

Hello,

My Nexus 5X only has internal storage.

Actually with 7.1.2 and Android 8.0.0. (oreo)

I only get a Track-Points when the display is active with Orux 7.1.2.

I don't remember this problem with any 7.1.2 RC , and I am pretty sure it started with the update to Android 8.0 and API 26

Android Documentation talks about Background Location limits (//https)

I'll try the 7.1.3 next week.

Title: Re: new beta 7.0.18betaX
Post by: orux on August 24, 2017, 10:31:37 PM

~~Quote from: "Tobias"~~Hello,

My Nexus 5X only has internal storage.

Actually with 7.1.2 and Android 8.0.0. (oreo)

I only get a Track-Points when the display is active with Orux 7.1.2.

I don't remember this problem with any 7.1.2 RC , and I am pretty sure it started with the update to Android 8.0 and API 26

Android Documentation talks about Background Location limits (//https)

I'll try the 7.1.3 next week.

Hello,

oruxmaps 7.1.3 uses a foreground service to avoid that new android 'feature'

orux

Title: Re: new beta 7.0.18betaX
Post by: Joska on August 25, 2017, 03:10:42 PM

~~Quote from: "orux"~~

you don't see the DEM files because the browser is configured as a folder selector, then the files are not displayed.

orux

Hello Orux

You'd written this sometimes in the past, but it seems to be a source of misunderstandigs. Why don't you use a filebrowser instead of folderbrowser, the first one everybody knows by using windows/MacOs/Linux etc?

Regards, Joska

Title: Re: new beta 7.1.3betaX
Post by: kerekjoe on August 30, 2017, 10:32:52 AM

the configure of distance rings colours may be useful in the future

(I couldn't see it at first sight - with my old eyes..)

Title: Re: new beta 7.0.18betaX
Post by: orux on August 30, 2017, 07:49:23 PM

~~Quote from: "Joska"~~
~~Quote from: "orux"~~

you don't see the DEM files because the browser is configured as a folder selector, then the files are not displayed.

orux

Hello Orux

You'd written this sometimes in the past, but it seems to be a source of misunderstandigs. Why don't you use a filebrowser instead of folderbrowser, the first one everybody knows by using windows/MacOs/Linux etc?

Regards, Joska

Hello,

there is a new beta update.

it is how that library works; I will see if I can change that behaviour.

orux

Title: Re: new beta 7.1.3betaX
Post by: JCS666 on September 02, 2017, 01:17:07 PM

~~Quote from: "orux"~~Hello,

a new beta:

//http://www.oruxmaps.com/OruxMaps7.1.3beta3.apk

:beta3

->some bugs corrections.

:beta2

->Added concentric circles in the GPS cursor and the destination Wpt, to indicate distances. Active by default in the beta, for testing, will be disabled by default in the final version.

->some bugs corrections.

:beta1

->new system to keep alive the app and avoid Doze.

->capture url links to .gpx/.kml/.kmz files. The app offers itself to dowload that files to oruxmaps/tracklogs/ folder.

->solved bug with TMG line using some maps.

orux

Al intentar subir track al server de orux da error 36: sin permisos

Title: Re: new beta 7.1.3betaX
Post by: Quercus.JB on September 02, 2017, 05:24:25 PM

Hola, he actualizado a 7.1.3beta3 y no me deja autorizar a escribir en la sd, da un error, no me había pasado hasta ahora. La beta 1 y 2 me las he saltado.

Enviado desde mi D6503 mediante Tapatalk

Title: Re: new beta 7.0.18betaX
Post by: Tobias on September 03, 2017, 10:48:05 PM

~~Quote from: "orux"~~
Hello,

oruxmaps 7.1.3 uses a foreground service to avoid that new android 'feature'

orux

Hello,

7.1.3 Beta 3 now works fine with tracking and my Nexus 5X with Android 8.0.0.

DEM files recognition still seems inconsistent,

I had a hard time to get it work at all the last few days,

at the moment it shows DEM files on startup of the app.

Edit: I just found the new version 7.1.4, better in a new thread I think?

But now I can see the files in the folder,

(//%3C/s%3E%3CURL%20url=%22https://lh4.googleusercontent.com/EX7jnzVPil8fD4xK1p0vp2Jb0rOGx94ive-Nf4vq5dqhQM6rD-CxWVF0etN4iF12MzchQDQC5rskaBc=w1858-h1014-rw%22%3E%3CLINK_TEXT%20text=%22https://lh4.googleusercontent.com/EX7jn%20...%208-h1014-rw%22%3Ehttps://lh4.googleusercontent.com/EX7jnzVPil8fD4xK1p0vp2Jb0rOGx94ive-Nf4vq5dqhQM6rD-CxWVF0etN4iF12MzchQDQC5rskaBc=w1858-h1014-rw%3C/LINK_TEXT%3E%3C/URL%3E%3Ce%3E)

but it is still a problem to get DEM to work. It seems to work after a random number of tries.

(//%3C/s%3E%3CURL%20url=%22https://lh3.googleusercontent.com/JTFQANCYpanOrSnrtlKj6JBUAgauI4iswidBJuII2fyIb9mLepdHI7Yz1Q31u_91_PmiektRqvj2_fk=w1858-h1014-rw%22%3E%3CLINK_TEXT%20text=%22https://lh3.googleusercontent.com/JTFQA%20...%208-h1014-rw%22%3Ehttps://lh3.googleusercontent.com/JTFQANCYpanOrSnrtlKj6JBUAgauI4iswidBJuII2fyIb9mLepdHI7Yz1Q31u_91_PmiektRqvj2_fk=w1858-h1014-rw%3C/LINK_TEXT%3E%3C/URL%3E%3Ce%3E)

Title: Re: new beta 7.1.7betaX
Post by: orux on September 10, 2017, 10:15:25 PM

Hello,

a new beta, with some changes.

orux

Title: Re: new beta 7.1.7betaX
Post by: Mapper-Alps12 on September 11, 2017, 05:58:53 PM

Hola Orux,

once again, thank you very much for your great app.

I have a wish for the function "move map to point". When you tap this button and select "point" in the next step, you can enter the coordinate in G.G°/G°M.M'/G°M'S'' or UTM system. Would it be possible for you to change the coordinate system to the selected coordinate system, e.g. MGRS oder to add this coordinate system for selection? We use your app in the rescue service and there the used coordinate system ist MGRS. If you add this system, it would be easier for us to locate the coordinates where we have to go.

We look forward to hear from you. :P

Title: Re: new beta 7.1.7betaX
Post by: ThomasSc on September 12, 2017, 10:46:06 AM

Hi orux,

thanks for the new beta.

Is it possible to change the color of the circles from "Distance perimeter".

Because it's the same color like the hight lines in my maps and this is very confusing.

Thanks.

Thomas

Title: Re: new beta 7.1.7betaX
Post by: orux on September 13, 2017, 06:37:01 PM

~~Quote from: "Mapper-Alps12"~~Hola Orux,

once again, thank you very much for your great app.

I have a wish for the function "move map to point". When you tap this button and select "point" in the next step, you can enter the coordinate in G.G°/G°M.M'/G°M'S'' or UTM system. Would it be possible for you to change the coordinate system to the selected coordinate system, e.g. MGRS oder to add this coordinate system for selection? We use your app in the rescue service and there the used coordinate system ist MGRS. If you add this system, it would be easier for us to locate the coordinates where we have to go.

We look forward to hear from you. :P

Hello,

updated last beta, changed that dialog; now it is the same that creating a wpt.

orux

Title: Re: new beta 7.1.7betaX
Post by: Mapper-Alps12 on September 13, 2017, 08:44:34 PM

Muchos gracias, orux.

You did a great work, the changes work like a charm. So nice that you listen to the wishes of us users. :D

Title: Re: new beta 7.1.7betaX
Post by: ThomasSc on September 16, 2017, 08:42:49 AM

Hi orux,

thank you very much for the new beta.

Great to change the circle color. :)

Thomas

Title: Re: new beta 7.1.7betaX
Post by: Josean on September 19, 2017, 10:59:44 PM

Muy buenas Orux!

No sé si en las dos últimas betas hay algún bug que hace que la aplicación se detenga. Probé un día la semana pasada la beta 7.1.7 beta 1 y no tuve problema aparente. El caso es que hoy he querido salir con ella y ha sido imposible. Tras lanzar Orux, conectar el pulsometro ant+, activar el GPS y activar la grabación del track, a la de unos pocos segundos emitia un pitido, creo que por la desconexión del pulsometro, y tras encender la pantalla me encontraba un mensaje diciendo que Oruxmaps se había detenido, en la barra de tareas me encontraba sin embargo el icono de que la aplicación estaba grabando todavía, pulsaba sobre el, se abria Oruxmaps y me encontraba que había grabado el track, pero en el cuadro mandos todos los campos mostraban guiones, creo recordar, y la aplicación no respondía. Asi varias veces hasta que la he dejado por imposible, he usado Oruxmaps donar y listo, sin problema alguno.

En segundo plano estaba usando una aplicación de reproductor de música, la misma que uso siempre.

Después correr he procedido ha desinstalar la beta y ha volverla a instalar, en las pruebas que he hecho me ha vuelto a hacer lo mismo en alguna ocasión. Después he actualizado a la beta 3 y he probado y no se me ha cerrado la verdad. Ya probaré con más tiempo.

Pero lo que sí observo con las dos betas ( la 1 y la 3) es que en cuanto activo la grabación del track la mayoría de las veces la aplicación Oruxmaps se ralentiza una burrada ( se queda la pantalla en azul sin mapa y tarda mucho en cargarlo, los botones tardan mucho en responder, si hago que desaparezca el cuadro de mandos tarda mucho en restaurase cuando lo quiero volver a activar p.ej). Todo esto para nada lo observo en la versión de Donar. El teléfono es un bq m5 con 3gigas de RAM y yo en segundo plano solo activo un reproductor de música.

No sé cómo puedo obtener un registro de la anomalía cuando ocurra, el teléfono no está ruteado y es Android 6. Si me dices qué puedo hacer lo intento.

Saludos Josean.

Title: Re: new beta 7.1.7betaX
Post by: Josean on September 20, 2017, 08:55:27 AM

~~Quote from: "Josean"~~Muy buenas Orux!

No sé si en las dos últimas betas hay algún bug que hace que la aplicación se detenga. Probé un día la semana pasada la beta 7.1.7 beta 1 y no tuve problema aparente. El caso es que hoy he querido salir con ella y ha sido imposible. Tras lanzar Orux, conectar el pulsometro ant+, activar el GPS y activar la grabación del track, a la de unos pocos segundos emitia un pitido, creo que por la desconexión del pulsometro, y tras encender la pantalla me encontraba un mensaje diciendo que Oruxmaps se había detenido, en la barra de tareas me encontraba sin embargo el icono de que la aplicación estaba grabando todavía, pulsaba sobre el, se abria Oruxmaps y me encontraba que había grabado el track, pero en el cuadro mandos todos los campos mostraban guiones, creo recordar, y la aplicación no respondía. Asi varias veces hasta que la he dejado por imposible, he usado Oruxmaps donar y listo, sin problema alguno.

En segundo plano estaba usando una aplicación de reproductor de música, la misma que uso siempre.

Después correr he procedido ha desinstalar la beta y ha volverla a instalar, en las pruebas que he hecho me ha vuelto a hacer lo mismo en alguna ocasión. Después he actualizado a la beta 3 y he probado y no se me ha cerrado la verdad. Ya probaré con más tiempo.

Pero lo que sí observo con las dos betas ( la 1 y la 3) es que en cuanto activo la grabación del track la mayoría de las veces la aplicación Oruxmaps se ralentiza una burrada ( se queda la pantalla en azul sin mapa y tarda mucho en cargarlo, los botones tardan mucho en responder, si hago que desaparezca el cuadro de mandos tarda mucho en restaurase cuando lo quiero volver a activar p.ej). Todo esto para nada lo observo en la versión de Donar. El teléfono es un bq m5 con 3gigas de RAM y yo en segundo plano solo activo un reproductor de música.

No sé cómo puedo obtener un registro de la anomalía cuando ocurra, el teléfono no está ruteado y es Android 6. Si me dices qué puedo hacer lo intento.

Saludos Josean.

Muy buenas!

Prosiguiendo con este tema, hoy he probado en mi otro teléfono, un BQ aquaris 5 de 1 giga de ram y kitkat, y a la vez el M5, enlazados ambos al pulsometro, uno por bluetooth y el otro por ANT+. En ninguno de los dos se ha cerrado la aplicación, pero en los dos teléfonos observo que se ralentiza la aplicación una barbaridad cuando se inicia la grabación del track o cuando se enciende la pantalla tras haber estado apagada. No se si tendrá que ver con el uso del mapa de Mapsforge (es la ultima actualización de este mes en versión multilingue en ambos teléfonos), pues cuando cambio de mapa no observo dicha ralentización en las pocas pruebas que he realizado. Aún así no observo ralentización alguna cuando uso ese mismo mapa en la versión Donate en ambos teléfonos.

Saludos.

Title: Re: new beta 7.1.7betaX
Post by: JCS666 on September 23, 2017, 01:50:05 PM

~~Quote from: "orux"~~Hello,

a new beta:

//http://www.oruxmaps.com/OruxMaps7.1.7beta3.apk

:beta3

->change color of GPS position distance circles indicator and target wpt.->settings->user interface->colors

->change width of distance circles.->settings->user interface->tracks, paths,...

->Center map dialog with all type coordinates (degrees, utm, swiss grid, mgrs,...).

:beta1

->adjustment to slightly increase the size of the dashboard texts (settings-->user interface-->dashboard-->dashboard text size)

->new help button in some screens (non definitive help texts)

->change of some internal libraries

->some bugs corrections

old betas:

->some bugs corrections.

->Added concentric circles in the GPS cursor and the destination Wpt, to indicate distances. Active by default in the beta, for testing, will be disabled by default in the final version.

->some bugs corrections.

->new system to keep alive the app and avoid Doze.

->capture url links to .gpx/.kml/.kmz files. The app offers itself to dowload that files to oruxmaps/tracklogs/ folder.

->solved bug with TMG line using some maps.

orux

Cuando inicias una grabacion saca una linea recta a un punto distante.

Title: Re: new beta 7.1.7betaX
Post by: Josean on September 23, 2017, 05:52:03 PM

~~Quote from: "JCS666"~~
~~Quote from: "orux"~~Hello,

a new beta:

//http://www.oruxmaps.com/OruxMaps7.1.7beta3.apk

:beta3

->change color of GPS position distance circles indicator and target wpt.->settings->user interface->colors

->change width of distance circles.->settings->user interface->tracks, paths,...

->Center map dialog with all type coordinates (degrees, utm, swiss grid, mgrs,...).

:beta1

->adjustment to slightly increase the size of the dashboard texts (settings-->user interface-->dashboard-->dashboard text size)

->new help button in some screens (non definitive help texts)

->change of some internal libraries

->some bugs corrections

old betas:

->some bugs corrections.

->Added concentric circles in the GPS cursor and the destination Wpt, to indicate distances. Active by default in the beta, for testing, will be disabled by default in the final version.

->some bugs corrections.

->new system to keep alive the app and avoid Doze.

->capture url links to .gpx/.kml/.kmz files. The app offers itself to dowload that files to oruxmaps/tracklogs/ folder.

->solved bug with TMG line using some maps.

orux

Cuando inicias una grabacion saca una linea recta a un punto distante.

Si que es cierto! Pero luego cierto es también que desaparece al finalizar el track, aunque resulta molesta durante la grabación.

Yo por mi parte no he vuelto a sufrir cierre de la aplicación, aunque si aprecio la ralentización de la aplicación al encender la pantalla.

Title: Re: new beta 7.1.7betaX
Post by: orux on September 26, 2017, 01:05:19 PM

~~Quote from: "Josean"~~
~~Quote from: "JCS666"~~
~~Quote from: "orux"~~Hello,

a new beta:

//http://www.oruxmaps.com/OruxMaps7.1.7beta3.apk

:beta3

->change color of GPS position distance circles indicator and target wpt.->settings->user interface->colors

->change width of distance circles.->settings->user interface->tracks, paths,...

->Center map dialog with all type coordinates (degrees, utm, swiss grid, mgrs,...).

:beta1

->adjustment to slightly increase the size of the dashboard texts (settings-->user interface-->dashboard-->dashboard text size)

->new help button in some screens (non definitive help texts)

->change of some internal libraries

->some bugs corrections

old betas:

->some bugs corrections.

->Added concentric circles in the GPS cursor and the destination Wpt, to indicate distances. Active by default in the beta, for testing, will be disabled by default in the final version.

->some bugs corrections.

->new system to keep alive the app and avoid Doze.

->capture url links to .gpx/.kml/.kmz files. The app offers itself to dowload that files to oruxmaps/tracklogs/ folder.

->solved bug with TMG line using some maps.

orux

Cuando inicias una grabacion saca una linea recta a un punto distante.

Si que es cierto! Pero luego cierto es también que desaparece al finalizar el track, aunque resulta molesta durante la grabación.

Yo por mi parte no he vuelto a sufrir cierre de la aplicación, aunque si aprecio la ralentización de la aplicación al encender la pantalla.

Buenas!

he actualizado la beta;

por favor, comprobad que ya no sale esa línea extraña al empezar la grabación track.

orux

Title: Re: new beta 7.1.7betaX
Post by: Josean on September 26, 2017, 09:21:12 PM

Muy buenas!

Orux, ahora vuelve a funcionar de manera correcta.

Saludos.

Title: Re: RE: new beta 7.1.7betaX
Post by: JCS666 on September 27, 2017, 12:29:00 PM

~~Quote from: "orux"~~Hello,

a new beta:

//http://www.oruxmaps.com/OruxMaps7.1.7beta4.apk

:beta4

->bug corrections

->language updates

:beta3

->change color of GPS position distance circles indicator and target wpt.->settings->user interface->colors

->change width of distance circles.->settings->user interface->tracks, paths,...

->Center map dialog with all type coordinates (degrees, utm, swiss grid, mgrs,...).

:beta1

->adjustment to slightly increase the size of the dashboard texts (settings-->user interface-->dashboard-->dashboard text size)

->new help button in some screens (non definitive help texts)

->change of some internal libraries

->some bugs corrections

old betas:

->some bugs corrections.

->Added concentric circles in the GPS cursor and the destination Wpt, to indicate distances. Active by default in the beta, for testing, will be disabled by default in the final version.

->some bugs corrections.

->new system to keep alive the app and avoid Doze.

->capture url links to .gpx/.kml/.kmz files. The app offers itself to dowload that files to oruxmaps/tracklogs/ folder.

->solved bug with TMG line using some maps.

orux
El tema de la recta inicial resuelto.

Enviado desde mi SM-G935F mediante Tapatalk

Title: Re: new beta 7.1.7betaX
Post by: Josean on September 28, 2017, 04:37:35 PM

Muy buenas Orux!

En la última beta por lo menos si pulsas en "Ayuda", en vez de ofrecer instalar los archivos DEM o acceder al manual, se cierra la aplicación.

Saludos.

Title: Re: new beta 7.1.7betaX
Post by: orux on September 29, 2017, 11:06:56 AM

~~Quote from: "Josean"~~Muy buenas Orux!

En la última beta por lo menos si pulsas en "Ayuda", en vez de ofrecer instalar los archivos DEM o acceder al manual, se cierra la aplicación.

Saludos.

Hola,

había un error en la nueva ayuda, hay una nueva beta.

orux

Title: Re: new beta 7.1.7betaX
Post by: Quercus.JB on September 29, 2017, 07:07:00 PM

Hola Orux, la versión 4 no me pidió autorizar la sd, la versión 5 me lo ha vuelto a pedir en el proceso de actualización, y ha fallado. Lo soluciono llendo al directorio de mapas reseleccionando, me pide autorizar la sd y en ese momento funciona correctamente. Saludos

Enviado desde mi D6503 mediante Tapatalk

Title: Re: new beta 7.1.7betaX
Post by: 6745th@web.de on October 03, 2017, 09:11:58 PM

The Problem with the FIT Files is not solved with Beta5

I dont know if you have seen the my "bugreport":

http://www.oruxmaps.com/foro/viewtopic.php?f=5&t=4628

Title: Re: new beta 7.1.7betaX
Post by: orux on October 04, 2017, 10:47:17 AM

~~Quote from: "6745th@web.de"~~The Problem with the FIT Files is not solved with Beta5

I dont know if you have seen the my "bugreport":

http://www.oruxmaps.com/foro/viewtopic.php?f=5&t=4628

Hello!

yes, I have been doing test with mytourbook; I was able to install that app.

updated beta version, now it should work fine.

orux

Title: Re: new beta 7.1.7betaX
Post by: Josean on October 04, 2017, 09:12:05 PM

Muy buenas!

Probada esta tarde la beta 6 todo ha ido perfecto hasta que una vez terminado el track he querido subirlo al servidor de Oruxmaps, de manera pública, privada y con amigos, y siempre finaliza con un mensaje "36: sin permisos". Desde la versión de donar ha funcionado sin problemas.

Saludos.

Title: Re: new beta 7.1.7betaX
Post by: 6745th@web.de on October 05, 2017, 01:08:20 PM

Hi Orux,

thank for you're patience.

I have just tested the beta6.

Now i can import the "fit" File into mytourbook.

But the result is not perfect.

If i import the gpx File i get:

Tourname : 2017-10-04 11:21

Elevation Gain: 665m

Elevation loss 669m

Max Altitude 916m

Max Hearbeat 168bpm

Calouries is in the GPX Comment. eg 3300 cal.

If i import the fit File i get:

Tourname : empty

Elevation Gain: empty

Elevation loss empty

Max Altitude 916m

Max Hearbeat 168bpm

Calouries empty -- If i import a fit File from my Lezyne GPS i get also the Calouries Value.

The Altitude curves are OK.

Maybe you find the time to have a look.

Thanks,

Thomas

Title: Re: new beta 7.1.7betaX
Post by: orux on October 09, 2017, 10:15:14 AM

~~Quote from: "Josean"~~Muy buenas!

Probada esta tarde la beta 6 todo ha ido perfecto hasta que una vez terminado el track he querido subirlo al servidor de Oruxmaps, de manera pública, privada y con amigos, y siempre finaliza con un mensaje "36: sin permisos". Desde la versión de donar ha funcionado sin problemas.

Saludos.

Buenas!

He tenido que limitar la subida de rutas desde solo la versión Donar.

El servidor no da mucho de sí, y con cientos de miles de usuarios subiendo rutas, que es lo más más pesado, se bloqueaba.

orux

Title: Re: new beta 7.1.7betaX
Post by: orux on October 09, 2017, 10:18:14 AM

~~Quote from: "6745th@web.de"~~Hi Orux,

thank for you're patience.

I have just tested the beta6.

Now i can import the "fit" File into mytourbook.

But the result is not perfect.

If i import the gpx File i get:

Tourname : 2017-10-04 11:21

Elevation Gain: 665m

Elevation loss 669m

Max Altitude 916m

Max Hearbeat 168bpm

Calouries is in the GPX Comment. eg 3300 cal.

If i import the fit File i get:

Tourname : empty

Elevation Gain: empty

Elevation loss empty

Max Altitude 916m

Max Hearbeat 168bpm

Calouries empty -- If i import a fit File from my Lezyne GPS i get also the Calouries Value.

The Altitude curves are OK.

Maybe you find the time to have a look.

Thanks,

Thomas

Hello!

It is strange because those are calculated values. If the app calculates them with gpx files, it should calculate them with other formats.

Anyway, I added new information in last beta version. What I can't find is where the name of the session is stored.

orux

Title: Re: new beta 7.1.7betaX
Post by: 6745th@web.de on October 09, 2017, 08:35:17 PM

~~Quote from: "orux"~~
It is strange because those are calculated values. If the app calculates them with gpx files, it should calculate them with other formats.

Anyway, I added new information in last beta version. What I can't find is where the name of the session is stored.

MyTourbook has a function to recalculate the altitude values.

But strange:

Fitfiles, generated with Lezyne GPS are delivering this values directly. Also calories.

The name is not so important, the fit Files from Lezyne GPS are also not delivering a name.

I can ask the MyTourbook Developer, to have a Look to the Fit Files.

I will report,

Thomas

Title: Re: new beta 7.1.7betaX
Post by: 6745th@web.de on October 11, 2017, 03:49:54 PM

Hi Orux,

i get answer from the Mytourbook Developer.

If i have understood correctly, the fit file containes the different values 2 times.

once inside the session part, once outside the session.

The session part contains values, the other part contains zeros.

the zeros overwrite the session part.

in fitfiles from Garmin the order is vice versa.

once more: total descent was -304m. inside the orux fitfile total descent is 65232 (Two's complement ?)

(//%3C/s%3E%3CURL%20url=%22https://sourceforge.net/p/mytourbook/bugs/_discuss/thread/050d183f/32b6/attachment/mt-fit-log-marked.png%22%3E%3CLINK_TEXT%20text=%22https://sourceforge.net/p/mytourbook/bu%20...%20marked.png%22%3Ehttps://sourceforge.net/p/mytourbook/bugs/_discuss/thread/050d183f/32b6/attachment/mt-fit-log-marked.png%3C/LINK_TEXT%3E%3C/URL%3E%3Ce%3E)

(//%3C/s%3E%3CURL%20url=%22https://sourceforge.net/p/mytourbook/bugs/_discuss/thread/050d183f/32b6/attachment/mt-fit.png%22%3E%3CLINK_TEXT%20text=%22https://sourceforge.net/p/mytourbook/bu%20...%20mt-fit.png%22%3Ehttps://sourceforge.net/p/mytourbook/bugs/_discuss/thread/050d183f/32b6/attachment/mt-fit.png%3C/LINK_TEXT%3E%3C/URL%3E%3Ce%3E)

Garmin vs orux fitfile parsing:

Code Select Expand 1507721654154 [FitDataReader] C:UsersWolfgangSchrammDesktopfit-test2017-10-03 1159__20171003_1159.fit Timestamp Num Name Value Units 2017-10-11 13:34:14.001'925 [SessionMesgListenerImpl] onMesg:com.garmin.fit.SessionMesg@449aa1e5 2017-10-11 13:34:14.002'190 [RecordMesgListenerImpl] onMesg:com.garmin.fit.RecordMesg@67ed77dd 2017-10-11 13:34:14.002'275 [RecordMesgListenerImpl] onMesg:com.garmin.fit.RecordMesg@13eeef39 .... 2017-10-11 13:34:14.085'464 [RecordMesgListenerImpl] onMesg:com.garmin.fit.RecordMesg@c26b70ae 2017-10-11 13:34:14.085'515 [RecordMesgListenerImpl] onMesg:com.garmin.fit.RecordMesg@b9825252 1507721654528 [FitDataReader] C:UsersWolfgangSchrammDesktopfit-test2017-10-05-13-41-19.fit Timestamp Num Name Value Units 2017-10-11 13:34:14.378'441 [RecordMesgListenerImpl] onMesg:com.garmin.fit.RecordMesg@504831b5 2017-10-11 13:34:14.378'622 [RecordMesgListenerImpl] onMesg:com.garmin.fit.RecordMesg@d99275fe ... 2017-10-11 13:34:15.004'341 [RecordMesgListenerImpl] onMesg:com.garmin.fit.RecordMesg@55d73df5 2017-10-11 13:34:15.004'485 [RecordMesgListenerImpl] onMesg:com.garmin.fit.RecordMesg@97418e26 2017-10-11 13:34:15.005'772 [SessionMesgListenerImpl] onMesg:com.garmin.fit.SessionMesg@d539c66c

Title: Re: new beta 7.1.7betaX
Post by: ThomasSc on October 25, 2017, 12:08:06 PM

The track, if record, is just to see when you zoom-out then zoom-in.

Title: Re: new beta 7.1.7betaX
Post by: Maki on October 29, 2017, 11:17:43 PM

I tried the latest beta yesterday and I'm a bit disappointed. The waypoint creation dialog box has changed for the worse. The new help button is in the same place where we had for a long while the OK button. It makes no sense; for starters muscle memory continues to move the finger to that point, a new button should be in a new place. Then, what is this supposed to be useful for? Really, the help message adds nothing at all. The dialog box is self explaining, it's totally obvious that you have to fill the properties. And finally what is the difference between "got it" and "exit"?

Things like this just contribute to make the app even more bloated, I think this is going out of control. Latest beta is using 55MB in my internal memory, version 6.5 just 11 MB. Latest beta (or Play Store version) takes 6-7 seconds to launch from scratch on my Moto X2 and even more on my G-Pad 8.3 while 6.5 loads in no time, and zooming and panning are much faster in the older version. Basically from 6.x to 7.x app size has grown 5 times, but we don't have 5 times the features we had before.

I'm sorry to be so critic, but I'm really wondering where OM development is heading.

Title: Re: new beta 7.1.7betaX
Post by: orux on October 30, 2017, 10:20:37 AM

~~Quote from: "Maki"~~I tried the latest beta yesterday and I'm a bit disappointed. The waypoint creation dialog box has changed for the worse. The new help button is in the same place where we had for a long while the OK button. It makes no sense; for starters muscle memory continues to move the finger to that point, a new button should be in a new place. Then, what is this supposed to be useful for? Really, the help message adds nothing at all. The dialog box is self explaining, it's totally obvious that you have to fill the properties. And finally what is the difference between "got it" and "exit"?

Things like this just contribute to make the app even more bloated, I think this is going out of control. Latest beta is using 55MB in my internal memory, version 6.5 just 11 MB. Latest beta (or Play Store version) takes 6-7 seconds to launch from scratch on my Moto X2 and even more on my G-Pad 8.3 while 6.5 loads in no time, and zooming and panning are much faster in the older version. Basically from 6.x to 7.x app size has grown 5 times, but we don't have 5 times the features we had before.

I'm sorry to be so critic, but I'm really wondering where OM development is heading.

Hello;

You are right with the position of the new help buttons. I will change their position. About the help, for example, there are people that don't know what the 'projection' checkbox mean and what's for and continuously ask howw they do for creating a wpt if they have distance/bearing from a know position.

exit-> exit the tutorial

got it-> go to the next tutorial screen

The capabilities of the phones have increased greatly. In the beginning the apps had to work on 16mb of heap. Now they can use up to 512mb, depending on the tlf (32x times). 55mb is few, considering this evolution. The speed of the processors has also increased a lot.

The app apk now uses much more memory because it includes the native libraries for geopdf map support (17mb), which is an excellent format, increasingly used, and especially due to the weight of the spatial sqlite libraries to support mapsforge poi databases (28mb). Having to support android in different processors (arm, x86, ...) affects the package sizes that are created. Anyway, this should not affect the performance of the app.

The map viewer is essentially the same than version 6.5, it should not cost much more zoom/pan. I'll check.

I always test with different devices, some not very modern, and I have not noticed so many problems, the app seems to be moving well.

I also know that people use older devices. That's why he have old versions on the web, even older versions.

orux

Title: Re: new beta 7.1.7betaX
Post by: orux on October 30, 2017, 11:42:22 AM

New beta version uploaded,

orux

Title: Re: new beta 7.1.7betaX
Post by: matt on October 30, 2017, 12:41:34 PM

Hi,

regarding

-------------

7.1.7 beta8:

->added transparent mode in dashboard/buttons buttons bar (settings-->user interface-->colors).

-------------

I just tried to find and set that "transparent mode"; maybe i don't see the obvious, but i can't find it in (settings-->user interface-->colors)

Matt

Title: Re: RE: Re: new beta 7.1.7betaX
Post by: skibum218 on October 30, 2017, 03:10:01 PM

~~Quote from: "matt"~~Hi,

regarding

-------------

7.1.7 beta8:

->added transparent mode in dashboard/buttons buttons bar (settings-->user interface-->colors).

-------------

I just tried to find and set that "transparent mode"; maybe i don't see the obvious, but i can't find it in (settings-->user interface-->colors)

Matt

I found it here: settings-->user interface-->miscellaneous UI

Sent from my SM-G920V using Tapatalk

Title: Re: RE: Re: new beta 7.1.7betaX
Post by: matt on October 30, 2017, 03:51:54 PM

~~Quote from: "skibum218"~~
I found it here: settings-->user interface-->miscellaneous UI

But there i see only the option for the "Transparent button bar. Required android +5.0"

Nothing about transparent dashboard.

Title: Re: new beta 7.1.7betaX
Post by: 6745th@web.de on October 30, 2017, 03:57:24 PM

settings-->user interface-->colors

uncheck "Dashboard colors"

Dashboard background colors to "customized"

set "custom Background " to a transparent color

correct?

Title: Re: new beta 7.1.7betaX
Post by: orux on October 30, 2017, 04:12:29 PM

~~Quote from: "6745th@web.de"~~settings-->user interface-->colors

uncheck "Dashboard colors"

Dashboard background colors to "customized"

set "custom Background " to a transparent color

correct?

thanks,

yes,

orux

Title: Re: new beta 7.1.7betaX
Post by: 6745th@web.de on October 30, 2017, 05:01:19 PM

fit file export looks also good now.

thanks,

Thomas

Title: Re: new beta 7.1.7betaX
Post by: mntr86 on October 30, 2017, 05:33:16 PM

Hi orux, do you have planned a new android wear version? I suggest a offline maps mode and personalizable dashboard.

Thank you

Title: Re: new beta 7.1.7betaX
Post by: Maki on October 30, 2017, 11:07:43 PM

~~Quote from: "orux"~~exit-> exit the tutorial

got it-> go to the next tutorial screen

Sorry for the misunderstanding. To me "Got it!" sounds like "OK", I think "Next" would be a better wording.

~~Quote from: "orux"~~The capabilities of the phones have increased greatly. In the beginning the apps had to work on 16mb of heap. Now they can use up to 512mb, depending on the tlf (32x times). 55mb is few, considering this evolution. The speed of the processors has also increased a lot.

I know technology advances and I don't want to stop that. My devices are three years old, but still they have 2 GB of RAM, which is now the standard for mid-range, cheaper phones do have less even today. What I experience is that switching back and forth between Firefox and OruxMaps on the tablet I often have to wait for OM to reload. It's just memory consumption, not processor speed, and doesn't happen with 6.x.

What I really meant to say is that traditionally OM has been able to run fast on older/less powerful devices without resorting to old versions. I bought my Galaxy Nexus in late 2012, I changed it in 2015 because it wasn't up to the task of web browsing anymore, but OM was still flying on it. I then bought a Moto-X2 and two years later the only app I feel is slowing down is OM. It's still plenty usable, but noticeably slower and heavier than before. Maybe the screen is just drawn differently, but it's more "jumpy". In 6.5 it looks like the screen is drawn from the center in a spiral fashion; in 7.5 it looks like the whole display is built offscreen and then shown at once, which means that even if it takes the same time to have a complete redraw you see a bigger lag.

~~Quote from: "orux"~~The app apk now uses much more memory because it includes the native libraries for geopdf map support (17mb), which is an excellent format, increasingly used, and especially due to the weight of the spatial sqlite libraries to support mapsforge poi databases (28mb). Having to support android in different processors (arm, x86, ...) affects the package sizes that are created. Anyway, this should not affect the performance of the app.

You know, that's the point... every new option or new supported format increases weight and complexity. But when I look at friend's phones most people just use more or less the default setup, with the usual 4Umaps, OpenTopo or OpenAndroMaps. Is it worth supporting so much stuff and having so many options? We have SHP, but it's not even a map format, just pure data... GeoPDF is indeed excellent and I dream about it, but last time I checked there was no free tool to build maps (or at least not to a point that takes advantage of the format capabilities); so I don't expect a lot of free maps to be available any time soon and commercial maps are behind paywalls so we are unlikely to be able to use them. Now you tell me that half of OM weight is due to a single feature (spatialite)... it's an interesting thing but I'm not sure it's worth the cost: are you sure there's no lighter alternative? spatialite.exe on my PC is 13 MB, still a lot but much less than what you indicate. Of course one can go back to 6.5 but the the interface improvements are lost... Cannot the advanced stuff (exotic formats, external sensors, web services support...) be put in a couple of plug-ins?

Anyway, I just installed Beta8. With the light theme the buttons are dark and the lines that separate the dashboard controls are transparent (I see the map moving behind). I liked it better before.

Title: Re: new beta 7.1.7betaX
Post by: orux on October 31, 2017, 09:45:16 AM

~~Quote from: "Maki"~~

Sorry for the misunderstanding. To me "Got it!" sounds like "OK", I think "Next" would be a better wording.

Yes; got it is the default in the llibrary, I will change to next.

~~Quote from: "Maki"~~
I know technology advances and I don't want to stop that. My devices are three years old, but still they have 2 GB of RAM, which is now the standard for mid-range, cheaper phones do have less even today. What I experience is that switching back and forth between Firefox and OruxMaps on the tablet I often have to wait for OM to reload. It's just memory consumption, not processor speed, and doesn't happen with 6.x.

What I really meant to say is that traditionally OM has been able to run fast on older/less powerful devices without resorting to old versions. I bought my Galaxy Nexus in late 2012, I changed it in 2015 because it wasn't up to the task of web browsing anymore, but OM was still flying on it. I then bought a Moto-X2 and two years later the only app I feel is slowing down is OM. It's still plenty usable, but noticeably slower and heavier than before. Maybe the screen is just drawn differently, but it's more "jumpy". In 6.5 it looks like the screen is drawn from the center in a spiral fashion; in 7.5 it looks like the whole display is built offscreen and then shown at once, which means that even if it takes the same time to have a complete redraw you see a bigger lag.

Do you talk about all maps formats, or only with mapsforge maps? The change in mapsforge is that in version 7.x the construction of tiles is multithread, and in version 6.5 it was a single thread. That's why you see that the tiles are drawn in spiral in version 6.5. I do not know if you include other options, such as drawing shadows, ... but that may also affect performance in multithreading mode.

~~Quote from: "Maki"~~You know, that's the point... every new option or new supported format increases weight and complexity. But when I look at friend's phones most people just use more or less the default setup, with the usual 4Umaps, OpenTopo or OpenAndroMaps. Is it worth supporting so much stuff and having so many options? We have SHP, but it's not even a map format, just pure data... GeoPDF is indeed excellent and I dream about it, but last time I checked there was no free tool to build maps (or at least not to a point that takes advantage of the format capabilities); so I don't expect a lot of free maps to be available any time soon and commercial maps are behind paywalls so we are unlikely to be able to use them. Now you tell me that half of OM weight is due to a single feature (spatialite)... it's an interesting thing but I'm not sure it's worth the cost: are you sure there's no lighter alternative? spatialite.exe on my PC is 13 MB, still a lot but much less than what you indicate. Of course one can go back to 6.5 but the the interface improvements are lost... Cannot the advanced stuff (exotic formats, external sensors, web services support...) be put in a couple of plug-ins?

The problem with native libraries is that you have to include in the apk all the versions for the different architectures (arm, x86, ...). The libraries of each, for spatial support are about 7mb. If I include support for all the architectures, they suppose 40mb! But I have only included 3 archs. There is a system that allows you to divide the apk by architectures, but it is complicated to manage. Google does not recommend it if the apk is less than 50mb (Current version is 40mb aprox).

The weight of the java libraries is insignificant, because only the used part is included in the apk, which is very small.

~~Quote from: "Maki"~~Anyway, I just installed Beta8. With the light theme the buttons are dark and the lines that separate the dashboard controls are transparent (I see the map moving behind). I liked it better before.

A side effect, with the changes; I will see,

orux

Title: Re: new beta 7.1.7betaX
Post by: 6745th@web.de on October 31, 2017, 10:00:49 PM

the semitransparent buttons/dashboard are really nice.

I like it.

Title: Re: new beta 7.1.7betaX
Post by: Maki on October 31, 2017, 11:07:34 PM

~~Quote from: "orux"~~Do you talk about all maps formats, or only with mapsforge maps? The change in mapsforge is that in version 7.x the construction of tiles is multithread, and in version 6.5 it was a single thread. That's why you see that the tiles are drawn in spiral in version 6.5. I do not know if you include other options, such as drawing shadows, ... but that may also affect performance in multithreading mode.

No, at the moment I'm only using mbtiles (no multimap, hillshading or other fancy stuff).

By the way it comes to mind that sometimes after updating I see random tiles missing here and there. Clearing the caches from the preferences always solved the problem. In theory it shouldn't be related because it's offline maps and I don't expect them to be cached. However I notice that the first time I visualize a certain area it is slower then when I go there again after a while, so maybe you are caching offline maps too? Or is it some Android filesystem cache?

Title: Re: new beta 7.1.7betaX
Post by: Maki on October 31, 2017, 11:09:46 PM

I also see now that an old bug come up again. When in immersive mode opening a menu on the action bar causes the Andorid soft buttons to show, like in 6.5

Title: Re: new beta 7.1.7betaX
Post by: mig299 on November 02, 2017, 08:50:56 PM

~~Quote from: "6745th@web.de"~~settings-->user interface-->colors

uncheck "Dashboard colors"

Dashboard background colors to "customized"

set "custom Background " to a transparent color

correct?

Perdonad mi torpeza, pero no se como poner transparente el color de fondo en los botones laterales.

Gracias

Title: Re: new beta 7.1.7betaX
Post by: JCS666 on November 02, 2017, 10:20:13 PM

Voy a tratar de responder con capturas de pantalla

(//%3C/s%3E%3CURL%20url=%22https://uploads.tapatalk-cdn.com/20171102/0f7fd868ff2c367429f2819cc059bcca.jpg%22%3E%3CLINK_TEXT%20text=%22https://uploads.tapatalk-cdn.com/201711%20...%2059bcca.jpg%22%3Ehttps://uploads.tapatalk-cdn.com/20171102/0f7fd868ff2c367429f2819cc059bcca.jpg%3C/LINK_TEXT%3E%3C/URL%3E%3Ce%3E)

(//%3C/s%3E%3CURL%20url=%22https://uploads.tapatalk-cdn.com/20171102/b513db5eaaf747caead4259cfa8699a8.jpg%22%3E%3CLINK_TEXT%20text=%22https://uploads.tapatalk-cdn.com/201711%20...%208699a8.jpg%22%3Ehttps://uploads.tapatalk-cdn.com/20171102/b513db5eaaf747caead4259cfa8699a8.jpg%3C/LINK_TEXT%3E%3C/URL%3E%3Ce%3E)

(//%3C/s%3E%3CURL%20url=%22https://uploads.tapatalk-cdn.com/20171102/00aacf5fcc8bf633349d40bdc57fe248.jpg%22%3E%3CLINK_TEXT%20text=%22https://uploads.tapatalk-cdn.com/201711%20...%207fe248.jpg%22%3Ehttps://uploads.tapatalk-cdn.com/20171102/00aacf5fcc8bf633349d40bdc57fe248.jpg%3C/LINK_TEXT%3E%3C/URL%3E%3Ce%3E)

Enviado desde mi SM-G935F mediante Tapatalk

Title: Re: new beta 7.1.7betaX
Post by: mig299 on November 02, 2017, 11:19:31 PM

Gracias. Ahora lo pruebo

Saludos

Title: Re: new beta 7.1.7betaX
Post by: orux on November 03, 2017, 12:07:16 PM

~~Quote from: "Maki"~~
~~Quote from: "orux"~~Do you talk about all maps formats, or only with mapsforge maps? The change in mapsforge is that in version 7.x the construction of tiles is multithread, and in version 6.5 it was a single thread. That's why you see that the tiles are drawn in spiral in version 6.5. I do not know if you include other options, such as drawing shadows, ... but that may also affect performance in multithreading mode.

No, at the moment I'm only using mbtiles (no multimap, hillshading or other fancy stuff).

By the way it comes to mind that sometimes after updating I see random tiles missing here and there. Clearing the caches from the preferences always solved the problem. In theory it shouldn't be related because it's offline maps and I don't expect them to be cached. However I notice that the first time I visualize a certain area it is slower then when I go there again after a while, so maybe you are caching offline maps too? Or is it some Android filesystem cache?

Hello;

mbtiles are still single thread, and loaded in spiral.

There are two level of caches.

1.-in memory, small, for all kind of maps.

2.-in file system, large, for online maps, and vectorial maps (mapsforge & img). Not for mbtiles. May be android sqlite engine has a cache, and recent access are faster.

I receive strange sqlite problems after updating, may be this is the problem with missing tiles.

orux

Title: Re: new beta 7.1.7betaX
Post by: orux on November 03, 2017, 06:33:20 PM

New beta uploaded,

orux

Title: Re: new beta 7.1.7betaX
Post by: matt on November 04, 2017, 07:30:52 AM

Hi, about 7.1.7beta9 transparent mode.

after i understood how to set transparent dashboard/buttons in (settings-->user interface-->colors) with that horizontal glider, i played around and i really like it.

One thing i noticed: only normal buttons appear transparent, large buttons do not appear transparent (settings-->user interface-->buttons-->large buttons mode). And when GPS tracking is on, this small icon appearing on top left, is also not transparent, maybe this is intended...

Matt

Title: Re: new beta 7.1.7betaX
Post by: Maki on November 05, 2017, 03:57:46 PM

I tested again mbtiles after reinstalling 7.x Donate and beta on the tablet since I had removed them. On the phone I always had 6.5 from website, Donate from the Playstore and beta.

On the tablet moving to an area that I had not visualized before I actually see the spiral pattern. When zooming in and out in the same area half of the times I don't see the spiral but rather most of the screen drawn at a single time, without lags, so it's probably from the cache. Behavior is consistent across versions, except 6.5 is much faster at start. Once loaded speeds are similar

On the phone 6.5 has a similar behavior to the tabled, it' just faster (normal, the device is faster), panning is totally fluid and fast. 7.x (beta and donate) are very strange. If I move to an area that I had not visualized before I clearly see the spiral pattern. After a few zooms in and out I get the same behavior of the tablet, but with a lag between the moment I release the fingers and the moment the map start drawing. It's a few tenths of second but it's noticeable. Panning is even worse. In general the behavior is like when zooming, but I get an additional jump when I lift the finger while still moving. The map starts redrawing, than it moves a couple of millimiters further and it finishes the redraw. I'd question the device, but since 6.5 runs fine I think some minor detail must have changed.

About Spatialite. I never tried the feature before so I gave it a go. Personally I find it very difficult to use, selectiong a category

from the list is uncomfortable at best. The list is too huge. Making the checkboxes default to "on" woulbd be a big improvement. Also it

seems that thicking one macrocategory doesn't actually tick subcategories. I know queries are expensive, but scrolling and selectiong

categories is too.

Then I don't see why Spatialite is necessary for this kind of search: it looks like you search a name and you get coordinates, but those can be stored in a plain sqlite database, no? I'd understand if we could set a search radius or geofence, but we can't. What am I missing?

I'd also like to have this search function available for other maps, as far as I understand POIs and map files are not related.

Dashboard, buttons and theme. In beta 9 the missing border between controls is now ok when using solid colors but disappear when using the transparent dashboard. I still see the Android bottom bar popping up when opening a menu, pretty annoying... 6.5 did it too, but I'm rather sure that at some point it was fixed. Also the dashboard gets closed when swiping up to reveal Android buttons, this one is fossil and pretty annoying as well. In current Donate version buttons inherit color from app theme, in beta they inherit it from the dashboard. Of course I liked light buttons and dark dashboard... :-)

Preferences are now a nightmare. When you change the "custom dashboard/buttons background" (which BTW is too long to fit on screen) nothing happens because you also have to select "customized" from the preference above. As a minimum the setting should be grayed out when not used; or, always use the color picker and forget about light/dark preference. And you can also select white text on light background, or black on dark, which is totally invisible. And to add confusion you can always bypass all of this and tie the dashboard theme to the app theme via a checkbox... Why not replace the whole thing with just three settings?
App theme: light, dark, red
Buttons theme: light, dark, transparent dark, transparent light
Dashboard theme: light, dark, transparent dark, transparent light

Fast, easy and should cover everyone needs without conflicts and confusing nested preferences.

In any case dashboard background "clear" should be "light", "clear" usually means "transparent".

Title: Re: new beta 7.1.7betaX
Post by: bicho1986 on November 06, 2017, 10:22:22 AM

Buenos días, usamos esta aplicación desde el principio de los tiempos para cargar 4 kmz a la vez para poder seguirlos, uno de ida, otro de vuelta y los otros 2 son waypoints de cada uno de los sentidos de la ruta.

Nos gustaría comentarte la posibilidad de realizar alguna mejora que nos parece interesante:

- Poder salir de la aplicación y al volver iniciar, que orux guardase las 4 últimas rutas que fueron cargadas, en nuestro caso son 4 pero si alguien cargar más cerrarlas todas, y no únicamente la última cargada de las 4. Algo como poner un botón que muestra "Dejar rutas que se cargaron por última vez" y así mostrar todas las que se cargaron en un principio.

- Nos parece interesante a colación de lo de antes, realizar lo contrario, quiero decir una opción que indicase "Al salir de la aplicación, borrar rutas cargadas" porque puede que a alguien le resulte molesto tener que borrarla siempre que entre a la aplicación.

- Por último nos gustaría poder cambiar el color de las 4 rutas cargadas y no que ponga en la ruta primaria el color indicado y en el resto el color por defecto, ya que hay veces que no se distingue la ruta de sentido ida con la de vuelta.

Gracias por todo el trabajo realizado durante todos estos años, esta aplicación es un 10 que nos ha salvado de más de un apuro a los conductores de autobús.

Title: Re: new beta 7.1.7betaX
Post by: Mapper-Alps12 on November 06, 2017, 12:40:59 PM

Hi Orux,

the "Center map dialog" function with all type coordinates (degrees, utm, swiss grid, mgrs,...) doesn't work for me with the latest beta. When I chose "point" the app crashes. Can you please fix that?

Thanks in Advance!

Title: Re: new beta 7.1.7betaX
Post by: mett on November 11, 2017, 02:01:48 PM

Hi orux,

There is a bug affecting this beta: the length,altitude,time etc of the tracks in the tracks list reflects the last segment statistics instead of the complete track!

Sent from my SM-G900F using Tapatalk

Title: Re: new beta 7.1.7betaX
Post by: orux on November 11, 2017, 04:11:19 PM

~~Quote from: "bicho1986"~~Buenos días, usamos esta aplicación desde el principio de los tiempos para cargar 4 kmz a la vez para poder seguirlos, uno de ida, otro de vuelta y los otros 2 son waypoints de cada uno de los sentidos de la ruta.

Nos gustaría comentarte la posibilidad de realizar alguna mejora que nos parece interesante:

- Poder salir de la aplicación y al volver iniciar, que orux guardase las 4 últimas rutas que fueron cargadas, en nuestro caso son 4 pero si alguien cargar más cerrarlas todas, y no únicamente la última cargada de las 4. Algo como poner un botón que muestra "Dejar rutas que se cargaron por última vez" y así mostrar todas las que se cargaron en un principio.

- Nos parece interesante a colación de lo de antes, realizar lo contrario, quiero decir una opción que indicase "Al salir de la aplicación, borrar rutas cargadas" porque puede que a alguien le resulte molesto tener que borrarla siempre que entre a la aplicación.

- Por último nos gustaría poder cambiar el color de las 4 rutas cargadas y no que ponga en la ruta primaria el color indicado y en el resto el color por defecto, ya que hay veces que no se distingue la ruta de sentido ida con la de vuelta.

Gracias por todo el trabajo realizado durante todos estos años, esta aplicación es un 10 que nos ha salvado de más de un apuro a los conductores de autobús.

Hola;

prueba la última beta; añadida opción para mantener rutas cargadas/borrarlas en la configuración.

lo del color es más complicado; es difícil añadir color a muchas rutas a parte de la activa...

orux

Title: Re: new beta 7.1.7betaX
Post by: 6745th@web.de on November 11, 2017, 04:29:11 PM

Hi Orux,

now OM can export fit files very well.

I was wondering why OM cant imprt fit and tcx Files.

Today i tried: "Import new Track" -> "GPX/KML" and selected a fit File. and it works! :lol: :lol:

Next test seleting a tcx: File and that worked also.

Wouldn't it be better to to rename that Item?

Instead

"GPX/KML"

"GPX/KML/TCX/FIT"

or

"Supported File Formats"

Thanks,

Thomas

Title: Re: new beta 7.1.7betaX
Post by: orux on November 11, 2017, 04:30:40 PM

~~Quote from: "Mapper-Alps12"~~Hi Orux,

the "Center map dialog" function with all type coordinates (degrees, utm, swiss grid, mgrs,...) doesn't work for me with the latest beta. When I chose "point" the app crashes. Can you please fix that?

Thanks in Advance!

Hello!

I don't receive any bug report. Do you have that feature on in settings-->send anonymous bug report?

orux

Title: Re: new beta 7.1.7betaX
Post by: Mapper-Alps12 on November 11, 2017, 06:45:41 PM

~~Quote from: "orux"~~

Hello!

I don't receive any bug report. Do you have that feature on in settings-->send anonymous bug report?

orux

Hi Orux,

I activated that feature and tried it with beta10, also several crashes. Did you receive a bug Report now?

Title: Re: RE: Re: new beta 7.1.7betaX
Post by: mett on November 12, 2017, 09:50:16 AM

~~Quote from: "mett"~~Hi orux,

There is a bug affecting this beta: the length,altitude,time etc of the tracks in the tracks list reflects the last segment statistics instead of the complete track!

Sent from my SM-G900F using Tapatalk

Has Anyone noticed this too?

For example:

(//%3C/s%3E%3CURL%20url=%22https://uploads.tapatalk-cdn.com/20171112/008d16dadf365a93f564378978111984.jpg%22%3E%3CLINK_TEXT%20text=%22https://uploads.tapatalk-cdn.com/201711%20...%20111984.jpg%22%3Ehttps://uploads.tapatalk-cdn.com/20171112/008d16dadf365a93f564378978111984.jpg%3C/LINK_TEXT%3E%3C/URL%3E%3Ce%3E)

Tracks list, length of selected track 25.

64km

(//%3C/s%3E%3CURL%20url=%22https://uploads.tapatalk-cdn.com/20171112/5402b8c59282b69972fcec69564d1d49.jpg%22%3E%3CLINK_TEXT%20text=%22https://uploads.tapatalk-cdn.com/201711%20...%204d1d49.jpg%22%3Ehttps://uploads.tapatalk-cdn.com/20171112/5402b8c59282b69972fcec69564d1d49.jpg%3C/LINK_TEXT%3E%3C/URL%3E%3Ce%3E)

Statistics of the track says instead 48.33km

(//%3C/s%3E%3CURL%20url=%22https://uploads.tapatalk-cdn.com/20171112/5d53c7c19e778c0b11862b3aafc1705f.jpg%22%3E%3CLINK_TEXT%20text=%22https://uploads.tapatalk-cdn.com/201711%20...%20c1705f.jpg%22%3Ehttps://uploads.tapatalk-cdn.com/20171112/5d53c7c19e778c0b11862b3aafc1705f.jpg%3C/LINK_TEXT%3E%3C/URL%3E%3Ce%3E)

The track has two segments: now we open segment 2

(//%3C/s%3E%3CURL%20url=%22https://uploads.tapatalk-cdn.com/20171112/85deaddd7df6e738d5922eed6e0dff4b.jpg%22%3E%3CLINK_TEXT%20text=%22https://uploads.tapatalk-cdn.com/201711%20...%200dff4b.jpg%22%3Ehttps://uploads.tapatalk-cdn.com/20171112/85deaddd7df6e738d5922eed6e0dff4b.jpg%3C/LINK_TEXT%3E%3C/URL%3E%3Ce%3E)

Length is 25.64km as in the tracks list.

What do you think? Also the cumulative statistics are wrong (selecting more tracks and computing statidtics) because they do not account all the Segments but only the last one!

Sent from my SM-G900F using Tapatalk

Title: Re: new beta 7.1.7betaX
Post by: mett on November 12, 2017, 10:01:41 AM

The beta 10 resolves this! Thanks!

Sent from my SM-G900F using Tapatalk

Title: Re: new beta 7.1.7betaX
Post by: bicho1986 on November 13, 2017, 06:24:15 PM

~~Quote from: "orux"~~
Hola;

prueba la última beta; añadida opción para mantener rutas cargadas/borrarlas en la configuración.

lo del color es más complicado; es difícil añadir color a muchas rutas a parte de la activa...

orux

No podemos estar más satisfechos, increíble trabajo y rapidez en modificación, mil gracias!!

Title: Re: new beta 7.1.7betaX
Post by: orux on November 20, 2017, 01:07:56 PM

Hello,

updated beta version,

orux

Title: Re: new beta 7.1.7betaX
Post by: 6745th@web.de on November 21, 2017, 07:55:39 AM

~~Quote from: "6745th@web.de"~~
Wouldn't it be better to to rename that Item?

Instead

"GPX/KML"

"GPX/KML/TCX/FIT"

or

"Supported File Formats"

Thanks for implementation.

OruxMaps

Uncategorized Boards => BETAS => Topic started by: orux on July 14, 2017, 09:08:03 PM