Print Page - New beta 5.5.23betaXX

Title: New beta 5.5.23betaXX
Post by: orux on June 14, 2014, 12:38:00 PM

Starting with a new beta...

New version 6.0.0 released!

Please, update in Google play.

:rc2

-->bug correction.

:rc1

-->first release candidate

:beta36

-->bug correction

:beta34b

-->bug correction

:beta34

-->some changes in mapsforge hill shading render.

:beta32

-->(experimental) apply hill shadows to mapsforge maps. (settings--maps--mapsforge settings). Requires map reload, and DEM files downloaded in DEM files folder.

-->bug correction

:beta30

-->removed some bugs in trip computer view

-->added altitude information to routes downloaded from MapQuest

-->added indeterminate progress information while unzipping mapsforge maps.

:beta28

-->for mapsforge maps/themes developers: this version catches links from zip maps & themes, like:

<a href="orux-map://www.oruxmaps.com/Mapsforge_map.zip">Map</a>

<a href="orux-mf-theme://www.oruxmaps.com/Mapsforge_Theme.zip">Theme</a>

You can offer your maps/themes from your web site, if the user click those links from the android web browser, OruxMaps will download/install the map/theme.

-->mapsforge maps: new zoom management, you will see the maps at the same zoom level than non mapsforge maps.

:beta24

-->download/install maps (and included themes) from http://www.openandromaps.org/

If you click a link to a zip map in this web download page, OruxMaps offers itself to download/install the map.

:beta20

-->solved some bugs.

:beta18

-->added a new setting--user interface--tracks--secundary routes width

-->added mmHg units for pressure

-->added Swiss grid coordinates as option when creating a wpt.

-->New category in settings (sensors) with gps, ant+,...

-->added some help messages in some dialogs,...

:beta16

-->compress/reduce the size of attached pictures to KMZ files (configuration--tracks/routes-->)

-->display/save all the friends paths when using multitracking feature.

-->solved some bugs.

:beta14

-->solved some bugs, with kmz exported files, added user agent to wms maps

:beta12

-->experimental support to Cadence/Speed bluetooth 4.0 sensors (you have to select the device in configuration--Cadence/speed BT, then add the controls to the dashboard in configuration--user interface--dashboard--user interface). tested with Wahoo blue SC device.

-->support to extended labels in garmin maps (typ file).

:beta11:

-->garmin map artifacts (lines, points) scaled based on device display density

-->kml overlays, if you tap inside a linestring or polygon, name & description of that feature is displayed.

:beta10:

-->should solve some bugs.

-->initial support to wearable devices. With basic tracking/logging/routing info (three pages, scrolling up/down), and three actions (scrolling left; start/stop recording, new wpt, new segment). More features coming soon.
~~[attachment=1]~~device-2014-08-02-205354.png[/attachment]~~[attachment=0]~~device-2014-08-03-190407.png[/attachment]

:beta9

-->solved some bugs

:beta8

-->improved following a route if it matches the way up to the way back.

:beta7

-->support to slippy maps (online maps cached in the file system)

You need to add a new online source, adding the path to the tiles:

<url><![CDATA[file:///storage/sdcard0/oruxmaps/mapfiles/Minimap/{$z}/{$x}/{$y}.jpg]]></url>

:beta6

-->added two new buttons (that can be attached to the side bars):

-share map screenshot

-start a new track segment

-->new status bar, slightly smaller but more visible.

:beta5

-->added a new zoom setting; finalize pinch to zoom-->similar than the old 'zoom only between layers'.

:beta4

-->added a new setting for mapsforge maps: an user scale factor for symbols.

-->added a overflow menu button in the main button bar. Do you like it here or where it was before?

(//%3C/s%3E%3CURL%20url=%22http://s8.postimg.org/qdi628vxx/device_2014_06_29_230606.png%22%3E%3CLINK_TEXT%20text=%22http://s8.postimg.org/qdi628vxx/device_%20...%20230606.png%22%3Ehttp://s8.postimg.org/qdi628vxx/device_2014_06_29_230606.png%3C/LINK_TEXT%3E%3C/URL%3E%3Ce%3E)

:beta3

-->return to 0.4.3 mapsforge library. 0.5.0 needs a lot of work.

-->added magnetic track direction and magnetic bearing to target

:beta2:

-->multimaps, now you can create composite maps, from different non transparent sources. Added a new field to introduce transparency.

-->solved some bugs with mapsforge maps.

:beta1:

-->new set of high resolution icons.

-->New mapsforge libraries. Added a new setting, you can set a user scale factor, used with map items (settings--maps--mapsforge settings):

(//%3C/s%3E%3CURL%20url=%22http://s7.postimg.org/fnwwee2yj/device_2014_06_13_185620.png%22%3E%3CLINK_TEXT%20text=%22http://s7.postimg.org/fnwwee2yj/device_%20...%20185620.png%22%3Ehttp://s7.postimg.org/fnwwee2yj/device_2014_06_13_185620.png%3C/LINK_TEXT%3E%3C/URL%3E%3Ce%3E)(//%3C/s%3E%3CURL%20url=%22http://s29.postimg.org/ju84orwav/device_2014_06_13_185425.png%22%3E%3CLINK_TEXT%20text=%22http://s29.postimg.org/ju84orwav/device%20...%20185425.png%22%3Ehttp://s29.postimg.org/ju84orwav/device_2014_06_13_185425.png%3C/LINK_TEXT%3E%3C/URL%3E%3Ce%3E)

-->added a map to exported statistics:

(//%3C/s%3E%3CURL%20url=%22http://s17.postimg.org/z4xrzvrun/Captura_de_pantalla_de_2014_06_14_12_26_59.png%22%3E%3CLINK_TEXT%20text=%22http://s17.postimg.org/z4xrzvrun/Captur%20...%20_26_59.png%22%3Ehttp://s17.postimg.org/z4xrzvrun/Captura_de_pantalla_de_2014_06_14_12_26_59.png%3C/LINK_TEXT%3E%3C/URL%3E%3Ce%3E)

-->accumulated statistics from several tracks (tracks list, select a set of tracks, or all, then click the new button).

-->created folder Android/data/com.orux.oruxmaps/files/ in external sdcard, where you can create/copy your maps (android 4.4.x versions)

-->added a new field in the track list (distance from map centre). You can sort the tracks list using this criteria. Only works for new recorded/imported tracks.

orux

Title: Re: New beta 5.5.23betaXX
Post by: goosiebn on June 15, 2014, 09:39:58 AM

Regarding Android 4.4, it would be useful if all aspects of OruxMaps used whatever sdcard solution you come up with, not just a map folder. I've changed all available settings, for maps, exports, waypoints, etc, but still things like tracklogs db, online cache, raster cache, are filling up internal memory.

The path I've been using is:

/storage/sdcard1/Oruxmaps

Thanks.

Title: Re: New beta 5.5.23betaXX
Post by: jonny-blue on June 15, 2014, 09:07:50 PM

~~Quote~~Warning! It is first beta release.

Tried it two days ... and all worked well for me. 8-) (until now :D )

THX

Title: Re: New beta 5.5.23betaXX
Post by: Maki on June 16, 2014, 10:54:41 PM

Hi Jose, I only quickly tried the new beta (sorry, not too much free time).

Seems to run nicely with 4.3 on a Galaxy Nexus, but force closes immediately on a LG Gpad 8.3 with the latest 4.4 (100% stock, no root, no nothing).

New icons: a step back, IMHO, most are incomprehensible. For example the area tool was perfect, it's meaningless now. Ditto for the route menu, each time I look at the new one I ask myself what the police is doing on my phone. Really, I see no need to change, we need to relearn the interface just to get back where we were before.

New Mapsforge library: I see some difference in rendering with respect to the previous version. I have to use zoom-level 14 to cover the same area I saw with zoom-level 15, circles are bigger and so on. Having followed the development I saw the same in Cruiser, so I think it's normal and related to the new dpi-independent rendering. I couldn't verify it but the same zoom-level should roughly look the same on different devices now. We'll need to adjust themes a bit, but I think it's worth the effort. It also seems a bit slower but I expected this too; it's difficult to evaluate in any case because of the cache.

The Mapsforge zoom factor has two problems: the first is that I need to switch theme to see it applied, just refreshing the map list almost never worked. It was the same for text multiplier before. IMHO when the user touches these settings the cache should be automatically reset. The second is that it works in reverse of what I would expect, using a bigger number results in a smaller drawing. It should be the contrary to match the behaviour of the text multiplier.

A last problem is a faint green cast I see sometimes with OpenAndroMaps (I basically only use OAM, so maybe it happens with other maps). It also happened with the previous version, I think it appeared after the introduction of the stepless zoom, but I never found the time to report the bug. It is not fully reproducible, but the basic mechanic is the following: I display a certain area and it's fine. When I zoom and/or pan around I sometimes see that the previously displayed area gets a green cast. Another problem I've seen sometimes is that switching themes didn't fully clear the cache, and one tile still showed the previous content. I can't search them now, but I took some screenshots.

That's all for now.

Title: Re: New beta 5.5.23betaXX
Post by: Maki on June 17, 2014, 11:42:17 PM

Regarding the last problem a couple of screenshots. The first for the green cast, it can be seen in the upper half. With a background that includes some landuse pattern it goes unnoticed as it is very faint and most patterns typically contain some green. I said a wrong thing, however; when I zoom to a different level the screen is drawn correctly. When I pan it's the previously offscreen part of the image that gets tinted, not the other way around as I stated. Another possibly related thing I noticed is that if I try to match the same RGBA values of a PNG pattern with a fill drawn directly from the Mapsforge theme there is a slight difference.

~~(//%3C/s%3E%3CLINK_TEXT%20text=%22https://farm4.staticflickr.com/3878/144%20...%20169b_z.jpg%22%3Ehttps://farm4.staticflickr.com/3878/14443474861_27678c169b_z.jpg%3C/LINK_TEXT%3E%3Ce%3E) (//https)~~

~~(//%3C/s%3E%3CLINK_TEXT%20text=%22https://farm6.staticflickr.com/5499/142%20...%203d90_z.jpg%22%3Ehttps://farm6.staticflickr.com/5499/14260393167_b30ea73d90_z.jpg%3C/LINK_TEXT%3E%3Ce%3E) (//https)~~

~~Here you can see the incorrect cache flushing, the central tile is from the previous theme. It's not common to find this problem, and if memory serves it is always limited to a single tile.~~

Title: Re: New beta 5.5.23betaXX
Post by: orux on June 18, 2014, 08:21:35 PM

~~Quote from: "Maki"~~Regarding the last problem a couple of screenshots. The first for the green cast, it can be seen in the upper half. With a background that includes some landuse pattern it goes unnoticed as it is very faint and most patterns typically contain some green. I said a wrong thing, however; when I zoom to a different level the screen is drawn correctly. When I pan it's the previously offscreen part of the image that gets tinted, not the other way around as I stated. Another possibly related thing I noticed is that if I try to match the same RGBA values of a PNG pattern with a fill drawn directly from the Mapsforge theme there is a slight difference.

Here you can see the incorrect cache flushing, the central tile is from the previous theme. It's not common to find this problem, and if memory serves it is always limited to a single tile.

Hi,

try with last beta;

If you changes some settings with mapsforge/garmin maps, the cached tiles should be reloaded.

orux

Title: Re: New beta 5.5.23betaXX
Post by: eartrumpet on June 19, 2014, 10:34:06 AM

From a different thread:

Scaling: Something like a scale factor by the user is better than automatic, at least for me. But it shouldn't just scale ways as in your example screenshots, the whole area should be scaled as in the automatic. E.g. the lake has the same size as all other landuses etc. Is that possible?

I played a bit with the beta, and the zoom factors have changed. If I use font multiplicator 0.66 everything looks pretty much the same, only what I got on my screen at Zoom 14 is at the same size Zoom 13 now, so all zoom-mins should be changed by 1 to have the same functionality as in mapsforge 0.3. And dy's are different.

Are you using mapsforge 0.4.x release version?

I made an SVG testing version of Elevate, icons can be scaled with this:

http://www.openandromaps.org/wp-content/users/tobias/beta/Elevate_svg.zip

Main issues:

- symbols don't have "glow" effect anymore and can be less legible

- transparency of colors in symbols don't seem to work, so some symbols don't look right

Title: Re: New beta 5.5.23betaXX
Post by: Maki on June 19, 2014, 11:31:05 PM

Hi, I tried the new beta 2. On the tablet it still force closes on start. On the phone I still see the green tint creeping in.

Regarding the scaling/caching issue it's still there. I'll try to describe it with more detail step by step.

I have all the zooming/scaling set to 1 or 100%.

I have two maps, Italy and Alps_west from OpenandroMaps that overlap on a wide area.

I visualize an area that is present in both maps using, say, Italy, zoom level 14, 100 digital zoom.

I go in the settings and change the scaling factor to 5.

When I go back to the map the screen is erased and redrawn... just like before!

Then I use "switch map here" and move to Alps_West. The screen is erased and redrawn correctly with the new scaling factor (5).

Then I use "switch map here" and go back to Italy. The screen is erased and redrawn with the previous scaling factor (1).

Now I change theme and finally the screen is erased and redrawn correctly with the new scaling factor (5).

~~Quote from: "eartrumpet"~~Scaling: Something like a scale factor by the user is better than automatic, at least for me. But it shouldn't just scale ways as in your example screenshots, the whole area should be scaled as in the automatic. E.g. the lake has the same size as all other landuses etc. Is that possible?

I played a bit with the beta, and the zoom factors have changed. If I use font multiplicator 0.66 everything looks pretty much the same, only what I got on my screen at Zoom 14 is at the same size Zoom 13 now, so all zoom-mins should be changed by 1 to have the same functionality as in mapsforge 0.3. And dy's are different.

Unless I'm missing something I disagree with this. The zoom factor didn't really change, as far as I understand, if you have a 160dpi device. With higher resolutions it changes just because the map display is now dpi-independent, while before it wasn't. Of course if you had chosen your zoom-mins on a 233dpi screen you (like me) will see a difference, but it is unavoidable. I haven't been able to verify this since my devices have roughly the same pixel density, but it should work that way.

If you want to scale the whole view just zoom. The scaling factor that Jose implemented works like the text multiplier, and I find it useful as it allows the user to fine tune line thickness and/or adapt old themes to the new rendering engine with just a few taps. It would be interesting to have separate setting for vector and PNG/JPG because...

~~Quote from: "eartrumpet"~~I made an SVG testing version of Elevate, icons can be scaled with this:

http://www.openandromaps.org/wp-content ... te_svg.zip

Main issues:

- symbols don't have "glow" effect anymore and can be less legible

- transparency of colors in symbols don't seem to work, so some symbols don't look right

... SVG support is still immature in this version. Only SVG-Tiny is supported which means that you are struck with basic shapes. No gradients, no transparency, let alone halos... and you can't control icon size, not to mention the absence of reliable editors for that format. Having a separate setting for PNGs would allow to supply only one 450dpi icon/pattern set and scale it down without affecting the rest.

Title: Re: New beta 5.5.23betaXX
Post by: eartrumpet on June 20, 2014, 09:12:05 AM

~~Quote from: "Maki"~~
Unless I'm missing something I disagree with this. The zoom factor didn't really change, as far as I understand, if you have a 160dpi device. With higher resolutions it changes just because the map display is now dpi-independent, while before it wasn't. Of course if you had chosen your zoom-mins on a 233dpi screen you (like me) will see a difference, but it is unavoidable. I haven't been able to verify this since my devices have roughly the same pixel density, but it should work that way.

I also have 233dpi. What is seen on tiles or rendered with the theme is dependend on zoom-appear in the map or zoom-min in the theme. Even when I can use a different zoom factor to see the same part of the map on the screen I'm not able to see the same details. That's probably a discussion which should have been done at mapsforge.

Another issue: the number of the zoom factor used to be the same at all maps, so if for example I want to compare an offline mapsforge map with an online satellite map an switch, it isn't showing the same area anymore (at the same zoom).

~~Quote from: "Maki"~~If you want to scale the whole view just zoom.

As above - zooming is not the same as scaling. And I would like to set the dpi-dependance by hand, as I was fine with the supposed to be 160dpi at 233dpi, but can't get this back properly.

~~Quote from: "Maki"~~The scaling factor that Jose implemented works like the text multiplier, and I find it useful as it allows the user to fine tune line thickness and/or adapt old themes to the new rendering engine with just a few taps. It would be interesting to have separate setting for vector and PNG/JPG because...

You're right, so I think an additional switch with dpi-scale-factor on/off or even better, vectorial zoom (in contrast to digital zoom) would be great.

Title: Re: New beta 5.5.23betaXX
Post by: eartrumpet on June 20, 2014, 03:31:37 PM

Hi Orux,

I've learned that in the Samples App of mapsforge (https://code.google.com/p/mapsforge/source/browse/#git%2FApplications%2FAndroid%2FSamples, http://ci.mapsforge.org/job/release-0.4.0/lastSuccessfulBuild/artifact/Applications/Android/Samples/build/apk/Samples-debug-unaligned.apk) there is an option called display scale. The user can decide how the map is scaled to the display with that - small, normal, large, extra large - and that works really good in the Sample.

Could you include this?

Best regards,

Tobias

Title: Re: New beta 5.5.23betaXX
Post by: Maki on June 20, 2014, 10:50:17 PM

Hi Tobias, to be honest I fail to understand your point. We asked for properly scaling maps and now the we have them you want an option to go back. The zoom-level change in 0.40 has been briefly discussed on Mapsforge-dev before when I noticed the fact that zoom levels were different in Cruiser (0.4) and Oruxmaps (0.3), and I got more or less the same answers you got today.

IMHO you are overestimating the side effects of the upgrade and overlooking the benefits. I'd like to explain myself better, but first let's clarify the terminology to avoid confusion.

px is a physical pixel on the screen or in a bitmap image

dp is a density-independent pixel as described here http://developer.android.com/guide/practices/screens_support.html

zoom-level is an abstract unit that has no physical meaning. The only safe thing to assume about ZL is that when you change it by one unit the map scale doubles or halves

Map scale is... the map scale as defined for paper maps --> 1cm on the map equals xx meters on the terrain

Now, with MF 0.3 dp is ignored and image pixels are directly drawn on screen. Tile size is fixed to 256px. This means that on a 160dpi screen each tile is about 40mm wide. On a 320dpi it is 20mm wide and at 640dpi it gets 10mm. So the same zoom level on different devices results in a different map scale; or, if you want to see the same map scale you need to use different zoom levels. It also means that with the same theme everything on a 640dpi device will be a lot smaller, with thinner lines and unreadable text.

MF 0.4 achieves density independence using a variable tile size that takes dp in account. I see that Emux and Ludwig explained it on the list today so I won't repeat the mechanism. The result is that the same tile will be 512px on a 320dpi device and 1024 on the 640dpi one. This means 40mm on every device, which in turn means the line thickness and the map scale are now consistent across devices for any given zoom level (well, as I said I have not verified, but I trust them).

This is a huge improvement. My theme is currently optimized for 320dpi and I think it is acceptable from 240 to 480, but not optimal at all. Given the same map scale, on an GS4 you would use zoom level 18 rather than 17 like on a Gnex or 16 like on a Galaxy Ace. This means that different users would see a different amount of detail (due to zoom-min). With the new library the same zoom level gives the same map scale for everybody. So it doesn't matter any more on which device you build your theme, it will work the same on others (let's forget about icons for now). Also the bigger tiles means less clipped labels.

Of course existing themes that were optimized on anything different from 160dpi (the baseline) will need some tweaks, but, once you have done it, you will stop worrying about this stuff and only need to maintain/supply one XML file rather than 3 or more. I don't think you are using more than 10 different values for DY and font sizes. Zoom levels are 20, so with 10 minutes of search and replace in Notepad++ you are almost done. Line thickness will require more effort, but is seems to me that it suffers less from the change. Or, if you know how to do it, you can write a script that scales every value by 0.68.

The real problem to me is the imagery used for icons and especially patterns. As of today any image size that fitted evenly in the 256 tile size would repeat seamlessly, but that's not true any more. 128 would work in most cases but on some device it will break. As you noticed SVG support is very limited in 0.4 so icons are probably still better in PNG, which means we still have to supply different icon sets. Unless Jose can implement a bitmap scaling option, that is. In that case IMHO using a single 300dpi and scaling it would be perfectly acceptable both in terms of performance and aesthetics.

The samples app doesn't work for me, but as far as I understand if Jose wants to give an option like that all he needs to do is to add an option where the user can force tile size to an arbitrary fixed value. Setting it to 256 should make the app behave like before.

The point you raise about compatibility with other maps is important. But the solution there is simple: switching between maps should be done according to map scale and not zoom level.

Just my 2 cents.

Maki.

Title: Re: New beta 5.5.23betaXX
Post by: eartrumpet on June 21, 2014, 06:52:39 AM

Maki, I mostly agree with you, and I think that dpi based scaling is a good thing. I just found some issues, but I don't want to remove it because of that.

Maybe I should post my reasons for those points:

- One problem is that as with every automatic is that it's patronizing, and sometimes a user wants different behaviour. That's why I think a manual override as the display scale option is necessary.

- The other is end user support: if it looks different and if there is no option to change it the way it was there will be lots of requests. It would be good to have an option like the one mentioned above.

- You already name SVG symbols (and patterns): only with them one theme size for every device is possible at the moment, and as far as I know it's also an performance issue, and doesn't look as good as PNGs. So still different theme sizes.

- Compatibility: Oruxmaps isn't the only mapsforge app, although it's the one I use. But other users use my themes on Locus, which has it's own library, that doesn't scale AFAIK. And there are other apps too. The conclusion would be more variants, not less.

~~Quote~~
The point you raise about compatibility with other maps is important. But the solution there is simple: switching between maps should be done according to map scale and not zoom level.

+1

Title: Re: New beta 5.5.23betaXX
Post by: orux on June 21, 2014, 09:02:23 PM

Hello,

The current beta version is using the master version from mapsforge repo (0.5.0). It uses tiles of a constant size of 512 px, instead of 256 px used with the old version, because I think it is more efficient, especially on very large screens. Because of that, you see at each zoom level what you should see at a deeper zoom level (or vice versa).

OruxMaps does not use the mapsforge map viewer; only the engine that draws the tiles (bitmaps) is used.

This is my approach:

I think that a lake, which measures XX square kilometers, should always measure YY square centimeters on any screen, at ZZ zoom level; regardless of the pixel density of the screen, and the selected user scale factor. This should be consistent along all the maps, regardless of the map type (online, garmin, rmap,...).

But with vectorial maps, and a single map theme, it should be adjustable by the user:

1.-the size of texts.

2.-the size of the poi symbols (hospital, water, ...).

3.-the level of detail shown (you can display the artifacts expected in the Z+1 level at Z level, or vice versa), like with garmin maps.

4.-the size of items that are not symbols, (roads, contours, ...).

These are my wishes.

The problem of the approach of mapsforge libraries is that they create tiles of different sizes according to the selected user scale level. But OruxMaps works with constant sizes of tiles for a map, it can not be change on the fly.

But still I have to experiment more with existing libraries.

A good approximation for the problem of the small symbols (meanwhile a better support to svg icons) could be using png icons prepared for the high density screens, and that the library could scale down the png according to the screen density.

orux

Title: Re: New beta 5.5.23betaXX
Post by: Maki on June 21, 2014, 09:47:35 PM

~~Quote from: "orux"~~The current beta version is using the master version from mapsforge repo (0.5.0).

[...]

A good approximation for the problem of the small symbols (meanwhile a better support to svg icons) could be using png icons prepared for the high density screens, and that the library could scale down the png according to the screen density.

Is there a typo or are you really using 0.5? I ask this for two reasons: the first is that AFAIK that 0.5 is the unstable dev version that is still subject to changes. The second is that 0.5 will introduce a lot of changes in the render theme, including the SVG scaling parameters that are missing in 0.4.

0.5 is introducing modular themes too, via categories; do you plan to support this feature?

About the symbols problem I second your idea. Personally I'd use 320 dpi as a reference. That's because it is high enough to look good if scaled up to 200% on an LG G3 screen and still reasonably small to not hog the CPU of slower devices. Anyway, I can render my whole symbol set at any size you like with just a few clicks. If you want to experiment, just ask.

Thanks for your clarifications.

Title: Re: New beta 5.5.23betaXX
Post by: eartrumpet on June 22, 2014, 10:56:11 AM

Thanks for the clarification!
~~Quote from: "orux"~~I think that a lake, which measures XX square kilometers, should always measure YY square centimeters on any screen, at ZZ zoom level; regardless of the pixel density of the screen, and the selected user scale factor. This should be consistent along all the maps, regardless of the map type (online, garmin, rmap,...).

That would be nice, but doesn't work if tile size is changed as you explained, because all maps to be the same have to have the same tile size. And you have to adjust tile size if you want to have the same square cms regardless of pixel density. The only way to have all this is to adjust tile size for all maps according to pixel density.
~~Quote~~
But with vectorial maps, and a single map theme, it should be adjustable by the user:

1.-the size of texts.

2.-the size of the poi symbols (hospital, water, ...).

3.-the level of detail shown (you can display the artifacts expected in the Z+1 level at Z level, or vice versa), like with garmin maps.

4.-the size of items that are not symbols, (roads, contours, ...).

I would love to have display scale included, or even better: to have it bound to digital zoom. So a raster map is zoomed at 200% and a vector map is not digital zoomed but shown with twice the tile size, 512px. This way all maps have the same scale and the advantage if bigger tile sizes you mentioned is given.

~~Quote~~
A good approximation for the problem of the small symbols (meanwhile a better support to svg icons) could be using png icons prepared for the high density screens, and that the library could scale down the png according to the screen density.

+1

Title: Re: New beta 5.5.23betaXX
Post by: orux on June 22, 2014, 08:40:59 PM

~~Quote from: "Maki"~~
~~Quote from: "orux"~~The current beta version is using the master version from mapsforge repo (0.5.0).

[...]

A good approximation for the problem of the small symbols (meanwhile a better support to svg icons) could be using png icons prepared for the high density screens, and that the library could scale down the png according to the screen density.

Is there a typo or are you really using 0.5? I ask this for two reasons: the first is that AFAIK that 0.5 is the unstable dev version that is still subject to changes. The second is that 0.5 will introduce a lot of changes in the render theme, including the SVG scaling parameters that are missing in 0.4.

0.5 is introducing modular themes too, via categories; do you plan to support this feature?

About the symbols problem I second your idea. Personally I'd use 320 dpi as a reference. That's because it is high enough to look good if scaled up to 200% on an LG G3 screen and still reasonably small to not hog the CPU of slower devices. Anyway, I can render my whole symbol set at any size you like with just a few clicks. If you want to experiment, just ask.

Thanks for your clarifications.

Hi,

The master should be: 'master: the latest stable development branch. Use this if you want to use newer mapsforge functionality that has not yet been released, but you still want a certain stability. '

I think we can give them time to work with that version, because we are also in beta version.

Give me time to see if it is easy scale the symbols.

We will try to give support to all the features of this release.

orux

Title: Re: New beta 5.5.23betaXX
Post by: orux on June 22, 2014, 08:53:46 PM

~~Quote from: "eartrumpet"~~Thanks for the clarification!
~~Quote from: "orux"~~I think that a lake, which measures XX square kilometers, should always measure YY square centimeters on any screen, at ZZ zoom level; regardless of the pixel density of the screen, and the selected user scale factor. This should be consistent along all the maps, regardless of the map type (online, garmin, rmap,...).

That would be nice, but doesn't work if tile size is changed as you explained, because all maps to be the same have to have the same tile size. And you have to adjust tile size if you want to have the same square cms regardless of pixel density. The only way to have all this is to adjust tile size for all maps according to pixel density.
~~Quote~~
But with vectorial maps, and a single map theme, it should be adjustable by the user:

1.-the size of texts.

2.-the size of the poi symbols (hospital, water, ...).

3.-the level of detail shown (you can display the artifacts expected in the Z+1 level at Z level, or vice versa), like with garmin maps.

4.-the size of items that are not symbols, (roads, contours, ...).

I would love to have display scale included, or even better: to have it bound to digital zoom. So a raster map is zoomed at 200% and a vector map is not digital zoomed but shown with twice the tile size, 512px. This way all maps have the same scale and the advantage if bigger tile sizes you mentioned is given.

~~Quote~~
A good approximation for the problem of the small symbols (meanwhile a better support to svg icons) could be using png icons prepared for the high density screens, and that the library could scale down the png according to the screen density.

+1

Hi,

Ideally the engine should be able to paint tiles with different sizes, but without scaling the content. I mean, for the same level of zoom, a tile of 512px should contain four of 256px, but painted in a single step. Like you can do with libraries of garmin maps. The tile size does not determine the level of zoom, which is set with other parameters.

But mapsforge uses another approach, which is also valid.

orux

Title: Re: New beta 5.5.23betaXX
Post by: mett on June 27, 2014, 11:14:14 AM

Hi!

What is the meaning of the new number in brackets next to the distance?

I do not see the explanation in the change log list.

Thanks and best(//%3C/s%3E%3CURL%20url=%22http://img.tapatalk.com/d/14/06/27/ehu6ema4.jpg%22%3Ehttp://img.tapatalk.com/d/14/06/27/ehu6ema4.jpg%3C/URL%3E%3Ce%3E)

Sent from my GT-I9300 using Tapatalk 2

Title: Re: New beta 5.5.23betaXX
Post by: mett on June 28, 2014, 05:30:17 PM

Up!

Sent from my GT-I9300 using Tapatalk 2

Title: Re: New beta 5.5.23betaXX
Post by: orux on June 28, 2014, 06:00:29 PM

~~Quote from: "mett"~~Up!

Sent from my GT-I9300 using Tapatalk 2

Hi,

it is the distance from the center of the mapviewer to the first point of the track.

you can sort your new tracks using that criteria, if you want to see the nearest tracks to your current position.

orux

Title: Re: New beta 5.5.23betaXX
Post by: orux on June 28, 2014, 08:07:27 PM

Hi all;

I returned to the mapsforge library 0.4.3, I think it is better to work with this version, which is working well.

I try to work with the feature of modify the size of icons.

orux

Title: Re: New beta 5.5.23betaXX
Post by: Maki on June 29, 2014, 10:42:32 PM

I tried beta3:

- it no longer crashes on my G-Pad under Kitkat :-)

- the green cast is still there :-(

- seems quite fast, even if the bigger tiles play against it

- I updated my theme to compensate the changes in zoom-levels, dy and font size. I'd need to tweak some stroke widths but it mostly works. If anyone is interested, the modified files can be downloaded here https://app.box.com/s/hocun157qr7zoj749km6. The full theme is needed (here: http://tartamillo.wordpress.com/tiramisu/)

- testing the theme I extensively switched maps, panned and zoomed around, without any problem...

- ...until I tried to use an SVG icon. Here I got stuck in a situation where updating the SVG file didn't have effects, no matter what (clearing cache, switching themes and maps...). I had to completely clear the app data in order to have the cache cleared. I'm pretty sure that mapsforge has its own cache for storing bitmaps generated from SVGs, maybe it isn't flushed correctly? Anyway, SVG support is so broken I doubt I'll use it.

Re: icon resizing. I remember that Ludwig talked against PNG resizing (for aesthetic reasons), but I cannot find the post any more, so I don't know if there is a function that is turned off by default but it's possible. However I'm pretty sure that there is the possibility to set dash-arrays to scale. It seems to me that this is currently set to "off" (like in Mapsforge 0.3) which is totally illogical, it would be nice to have it set to "on".

Great work, thanks.

Maki

Title: Re: New beta 5.5.23betaXX
Post by: orux on June 29, 2014, 10:57:57 PM

~~Quote from: "Maki"~~I tried beta3:

- it no longer crashes on my G-Pad under Kitkat :-)

- the green cast is still there :-(

- seems quite fast, even if the bigger tiles play against it

- I updated my theme to compensate the changes in zoom-levels, dy and font size. I'd need to tweak some stroke widths but it mostly works. If anyone is interested, the modified files can be downloaded here https://app.box.com/s/hocun157qr7zoj749km6. The full theme is needed (here: http://tartamillo.wordpress.com/tiramisu/)

- testing the theme I extensively switched maps, panned and zoomed around, without any problem...

- ...until I tried to use an SVG icon. Here I got stuck in a situation where updating the SVG file didn't have effects, no matter what (clearing cache, switching themes and maps...). I had to completely clear the app data in order to have the cache cleared. I'm pretty sure that mapsforge has its own cache for storing bitmaps generated from SVGs, maybe it isn't flushed correctly? Anyway, SVG support is so broken I doubt I'll use it.

Re: icon resizing. I remember that Ludwig talked against PNG resizing (for aesthetic reasons), but I cannot find the post any more, so I don't know if there is a function that is turned off by default but it's possible. However I'm pretty sure that there is the possibility to set dash-arrays to scale. It seems to me that this is currently set to "off" (like in Mapsforge 0.3) which is totally illogical, it would be nice to have it set to "on".

Great work, thanks.

Maki

Hi, Maki,

thanks; I will try with you theme.

I just upgraded the beta, including a scale factor setting for mapsforge symbols. I have to try if properly scale the svg icons.

orux

Title: Re: New beta 5.5.23betaXX
Post by: chobkwon on June 30, 2014, 05:27:27 AM

~~Quote from: "orux"~~-->added a overflow menu button in the main button bar. Do you like it here or where it was before?

orux

I like it here~

(//%3C/s%3E%3CURL%20url=%22http://s8.postimg.org/qdi628vxx/device_2014_06_29_230606.png%22%3E%3CLINK_TEXT%20text=%22http://s8.postimg.org/qdi628vxx/device_%20...%20230606.png%22%3Ehttp://s8.postimg.org/qdi628vxx/device_2014_06_29_230606.png%3C/LINK_TEXT%3E%3C/URL%3E%3Ce%3E)

Title: Re: New beta 5.5.23betaXX
Post by: Maki on June 30, 2014, 11:50:06 PM

As far as I'm concerned the overflow has always been there, and it's fine (Android standard). By the way I'd use the "i" icon for "about", and "?" for help.

The icon scaling works fine for me, at this point I think using a single set of icons for all is feasible. A big progress IMHO. I see however a couple of problems:

1) Installing and managing themes is already hard enough for "normal" users. Telling them to manually change the icon scaling parameter (and other stuff) is even harder

2) Since different themes may require different parameters, an user switching themes would need to change settings too.

So, would it be possible to have a sidecar file with various base settings? For example I can state that my icons are made for 320dpi so they can be automatically scaled to 150% on a 480dpi device. At that point the app settings can be used for fine tuning by the user, if he feels the need. Ditto for dash arrays, text and graphics multipliers so that existing themes can be adapted easier without breaking the compatibility with previous versions.

Title: Re: New beta 5.5.23betaXX
Post by: Legend on July 01, 2014, 06:08:57 AM

~~Quote from: "Maki"~~As far as I'm concerned the overflow has always been there, and it's fine (Android standard).

It depends on the device. Until now, If the device had a "hard" menu button, the overflow was not there.

Now it is always there and the device's hard button is disabled.

I whould prefer both of them to work on such devices :-)

Title: Re: New beta 5.5.23betaXX
Post by: febs on July 01, 2014, 02:44:04 PM

:?: WTF is an overflow? I googled for "oruxmaps overflow" and I could not find a thing. :?: :) Thanks

Title: Re: New beta 5.5.23betaXX
Post by: skibum218 on July 01, 2014, 04:36:14 PM

~~Quote from: "febs"~~:?: WTF is an overflow? I googled for "oruxmaps overflow" and I could not find a thing. :?: :) Thanks

Additional menu items that are not shown directly on the screen. It's the 3 dots in the upper right corner on the latest beta. There is a screenshot of it a couple posts back.

Title: Re: New beta 5.5.23betaXX
Post by: Lanstronio on July 05, 2014, 04:10:02 PM

Desde que he instalado la nueva Beta 5.5.23.2 desaparecieron todos los problemas de desconexion GPS ANT+ Va fenomenal, incluso ahora ya si puedo utilizar el sensor de temperatura. Por otra parte ahora si quedan registrados los datos de temperatura y se pueden visualizar en Garmin connect. Solo me surgen un par de errores menores en esa pagina. Se registra como velocidad maxima 160 Km hora, eso me ha pasado siempre, y no sale dato de calorias. Entiendo que estos dos problemas no son de orux, si no de la propia pagina al tratar los datos introducidos en el archivo GPX. Por lo demas va de cine, tanto es así que no me he atrevido a cambiar a la version 5.5.23.4 por si me vuelven las desconexions que han sido un calvario en los ultimos meses.

Orux sigue demostrando ser el num. 1

Para muestra un boton..... ultimo ejercicio subido a garmin connect http://connect.garmin.com/activity/534809048

Title: Re: New beta 5.5.23betaXX
Post by: Josean on July 09, 2014, 09:07:49 AM

He tratado de instalar la beta 6 en mi móvil con versión 2.3 Gingerbread y me es imposible "error al analizar el paquete". He tratado de hacerlo en otro móvil con la misma versión y ocurre igual. Ha dejado Oruxmaps de ser compatible con Gingerbread?

Gracias y saludos.

Title: Re: New beta 5.5.23betaXX
Post by: orux on July 09, 2014, 10:50:32 AM

~~Quote from: "Josean"~~He tratado de instalar la beta 6 en mi móvil con versión 2.3 Gingerbread y me es imposible "error al analizar el paquete". He tratado de hacerlo en otro móvil con la misma versión y ocurre igual. Ha dejado Oruxmaps de ser compatible con Gingerbread?

Gracias y saludos.

Hola,

sigue siendo compatible con android 2.1 y superior.

es posible que se haya descargado mal el fichero, y esté corrupto; prueba a descargarlo otra vez, y mira que tengas un fichero de 5,6 mb aprox.,

orux

Title: Re: New beta 5.5.23betaXX
Post by: mntr86 on July 09, 2014, 11:01:16 AM

i have the same problem when i try to install the apk file of beta 6.

Title: Re: New beta 5.5.23betaXX
Post by: orux on July 09, 2014, 11:14:17 AM

~~Quote from: "mntr86"~~i have the same problem when i try to install the apk file of beta 6.

Hi,

the apk is right, downloaded/instaled by my and other users.

some android programs/versions get wrong downloads; are you downloading directly from the Android?

orux

Title: Re: New beta 5.5.23betaXX
Post by: mntr86 on July 09, 2014, 11:21:33 AM

Yes, i have tried 3 times but Android says "problems with analysis of the package"

Title: Re: New beta 5.5.23betaXX
Post by: orux on July 09, 2014, 11:36:06 AM

~~Quote from: "mntr86"~~Yes, i have tried 3 times but Android says "problems with analysis of the pocket"

Sorry! you are right.

I had modified the minSdkVersion manifest for testing some things.

A new beta in some minutes...

orux

Title: Re: New beta 5.5.23betaXX
Post by: orux on July 09, 2014, 05:49:29 PM

~~Quote from: "orux"~~
~~Quote from: "mntr86"~~Yes, i have tried 3 times but Android says "problems with analysis of the pocket"

Sorry! you are right.

I had modified the minSdkVersion manifest for testing some things.

A new beta in some minutes...

orux

Updated to beta7,

now it should work with android 2.x

orux

Title: Re: New beta 5.5.23betaXX
Post by: goosiebn on July 09, 2014, 10:14:45 PM

The new screenshot feature, and many many non customisable locations like both caches, tracks database are still saving in an emulated folder location on internal memory on 'droid 4.4. I keep having to bin db backups and both caches just to keep my phone alive. I note you've created a location for vector map storage, but I haven'ttried that because its folder was customisable and I'dalready pointed it to a folder that mapped to the original Oruxmaps location on sd, which makes me wonder why the special Android folder was neccesary, other than maybe a location that is valid on 'droid 2.3?

Title: Re: New beta 5.5.23betaXX
Post by: rainer0665 on July 10, 2014, 05:01:23 AM

Hello Orux,

would it be possible to add an "map info" button (and/or dashboard field (which might be to long)) which displays the comments that were provided when creating mapsforge maps??

I create my maps with the comment containing the timestamp of the OSM sourcedata:

osmosis --rb file=$source_pbf --mw file=$target_map bbox=$ll_lat,$ll_lon,$ur_lat,$ur_lon type=hd tag-conf-file=$tag_mapping_file comment="$remark"

$remark (in my case) contains the timestamp of the base OSM data that was used to create the maps.

Would be great if there would be a possibility that Oruxmaps displays that comment (probably also more use cases than just the timestamp, but that's what i use the information for.

This works great for example with emux's Atlas application http://www.talent.gr/public/atlas/

Menu: Vector -> Map Info.

Maybe other map formats like garmin .img do also contain some metadata that would be interesting for the user which could be shown depending on the type of map that is used.

Thanks for considering.

Regards Rainer

Title: Re: New beta 5.5.23betaXX
Post by: TheDuke on July 10, 2014, 12:54:45 PM

I'm testing at the moment the current beta, it works very well.

The map viewer is now very good.

The new icon set is mutch better than the old one.

The only bug that I've found is that the map index no longer works, it starts the settings now. :(

regards

TheDuke

Title: Re: New beta 5.5.23betaXX
Post by: Maki on July 11, 2014, 12:03:23 AM

Hi Orux,

first of all I'd ask if you can post a reply to the thread when you update the beta. If you only edit the first post we don't get a notification. I entirely missed the last two betas.

Regarding the new status bar, it's nice and easier to read. I think the only missing thing is a map north indication. When you rotate the map, unless there is text visible, you don't know where the north is. It could be implemented with a second arrow in a different colour behind the compass, so that we can check at a glance the alignment.

Speaking of compass, it's not the first time that I see it almost stuck, pointing to the wrong direction. When this happens I launch GPS Toolbox and the compass starts to work ok again even when I close it and go back to Oruxmaps. It's really strange, maybe there is some function that triggers a compass recalibration that can be used?

The icons seem ok now, but I see the same one is used for both Mapsforge style (in the menu) and map index (in the toolbar) which is confusing.

The new zoom snap option is great and terrible at the same time

It's great because I can jump a whole zoom level with just a short impulse.

But there is a side effect. Let's say I'm at 100% ZL15. I pinch zoom in and then without lifting the fingers I zoom back to 95% or 105% ZL15. I'd expect the snap zoom to go back to 100% ZL15, but instead it always goes to ZL14 or ZL16. It's annoying and counter-intuitive.

Ideally any value between 75% and 150% should not change the zoom level, but I see how this can work against the first case. So what about this? if the user pinch zooms quickly even by a little amount in a single direction the zooming action is continued until the next/previous level. However if the user moves slowly and/or zooms in both directions the 75-150% threshold is applied. Kinda like the scrolling in Chrome, move slowly and the action stops immediately, "launch" the page and it continues to scroll.

Then there is a thing about zoom/pan not related with the beta. When panning/zooming a mapsforge map in a cached area the action is very fast and fluid, but if a tile needs to be drawn it can take seconds. What about pre-rendering adjacent tiles and the next/previous zoom levels? There would be a noticeable performance gain. Yes, I know, this will drain the battery a bit more. But in my experience what really drains the battery is the screen, especially outdoors. I think it's very possible that the pre-rendering actually saves the battery since you reduce the time spent waiting in front of a blank screen.

Apart from this it seems very stable and runs well, great work as usual.

Title: Old issue (special sign #160) back ...
Post by: jonny-blue on July 12, 2014, 06:58:48 PM

Hi Orux,

with the new beta7 this old issue is back again ... :roll:

//http://www.oruxmaps.com/foro/viewtopic.php?f=4&t=1866&hilit=sign

Title: Re: Old issue (special sign #160) back ...
Post by: orux on July 15, 2014, 06:38:13 PM

~~Quote from: "jonny-blue"~~Hi Orux,

with the new beta7 this old issue is back again ... :roll:

//http://www.oruxmaps.com/foro/viewtopic.php?f=4&t=1866&hilit=sign

opsss, I have to correct the original google docs,

thanks,

orux

Title: Re: Old issue (special sign #160) back ...
Post by: orux on July 18, 2014, 08:38:35 PM

~~Quote from: "orux"~~
~~Quote from: "jonny-blue"~~Hi Orux,

with the new beta7 this old issue is back again ... :roll:

//http://www.oruxmaps.com/foro/viewtopic.php?f=4&t=1866&hilit=sign

opsss, I have to correct the original google docs,

thanks,

orux

Updated beta8 that should solve that problem

orux

Title: Re: New beta 5.5.23betaXX
Post by: skibum218 on July 20, 2014, 02:18:40 AM

Does anyone have the 5.5.23beta7 apk that they can post here, or direct me to where I can find it?

Title: Re: New beta 5.5.23betaXX
Post by: orux on July 20, 2014, 08:53:43 AM

~~Quote from: "skibum218"~~Does anyone have the 5.5.23beta7 apk that they can post here, or direct me to where I can find it?

Hi,

why do you need the beta7 and you don't use the beta8?

orux

Title: Re: Old issue (special sign #160) back ...
Post by: jonny-blue on July 20, 2014, 11:04:32 AM

~~Quote from: "orux"~~
Updated beta8 that should solve that problem

Now it's working again 8-) ... THX. :)

Title: Re: New beta 5.5.23betaXX
Post by: skibum218 on July 20, 2014, 05:20:46 PM

~~Quote from: "orux"~~

Hi,

why do you need the beta7 and you don't use the beta8?

orux

I have beta8 installed, but my Google maps won't load. I thought it might have something to do with their servers but when I try loading them with the last stable version they load fine.

I've cleared the map cache and I get the same results.

I wanted to test it on beta7 to see if it was just beta8 before I report it as a bug, but now that we are here. .. It might be a bug ;)

Thanks

Title: Re: New beta 5.5.23betaXX
Post by: Maxpil on July 21, 2014, 11:37:29 PM

Los FotoWpt a veces no llevan foto.

Comentado en BUGS.

Title: Re: New beta 5.5.23betaXX
Post by: orux on July 22, 2014, 05:41:37 PM

~~Quote from: "skibum218"~~
~~Quote from: "orux"~~

Hi,

why do you need the beta7 and you don't use the beta8?

orux

I have beta8 installed, but my Google maps won't load. I thought it might have something to do with their servers but when I try loading them with the last stable version they load fine.

I've cleared the map cache and I get the same results.

I wanted to test it on beta7 to see if it was just beta8 before I report it as a bug, but now that we are here. .. It might be a bug ;)

Thanks

Hi,

updated to beta9, try again,

orux

Title: Re: New beta 5.5.23betaXX
Post by: orux on July 22, 2014, 05:43:23 PM

~~Quote from: "Maxpil"~~Los FotoWpt a veces no llevan foto.

Comentado en BUGS.

Buenas,

es raro, pero el bug llevaba ahí mucho tiempo, no había salido a la luz.

Es debido a la rotación de la pantalla. Sólo se produce si la aoturotación de la pantalla está activa, y se rota la pantalla, por ejemplo, al tomar la foto.

Debe estar resuelto en la última beta.

orux

Title: Re: New beta 5.5.23betaXX
Post by: skibum218 on July 22, 2014, 05:54:51 PM

~~Quote from: "orux"~~

Hi,

updated to beta9, try again,

orux

You're amazing. Works perfectly.

Thanks!

-Skibum218

Title: Re: New beta 5.5.23betaXX
Post by: Maki on July 28, 2014, 09:59:51 PM

Hi, I briefly tested Beta9 on a S4 side by side with my Galaxy Nexus and... I'm puzzled.

The good news is that Mapsforge icons scaling works very well, from now on we can just supply a single 300 dpi icon set and scale it on the fly, it will look sharp enough on every display. That's a real progress. I was thinking that maybe using 450 dpi as a baseline could be better, but it seems this isn't the case so we can save memory.

Other than that... when you wrote:
~~Quote from: "orux"~~I think that a lake, which measures XX square kilometers, should always measure YY square centimeters on any screen, at ZZ zoom level; regardless of the pixel density of the screen, and the selected user scale factor. This should be consistent along all the maps, regardless of the map type (online, garmin, rmap,...).orux

I expected to see a consistent map size across devices, and it doesn't happen. Actually in some ways it's even worse than before. Given the same zoom level, a line that is 7 cm on my Gnex turns out to be 5 cm on the S4, but at the same time text labels are about the same, actually 10% bigger on the S4. Line thickness isn't consistent too, roads are larger on the S4.

It seems that labels and widths are scaled according to the screen density, while lengths aren't. This means that everything goes out of proportion and you can have roads that overlap unless the user tweaks the scaling parameters in the settings. I think everything should really scale uniformly, at least by default.

Maki.

Title: Re: New beta 5.5.23betaXX
Post by: goosiebn on July 31, 2014, 10:16:25 AM

If I exit beta9, then load it straight away again, all is well. But if I exit, leave it for a few seconds, maybe 10 seconds, then start itagain, the last route and track aren't visible. Also, I was recording a track and I presume Orux was killed (because I was web browsing), the track log active notification was still there, but when I loaded beta again, similar situation- no current track. I've seen in the past on an old phone where the phone rebooted, I just started Orux and everthing just resumed, last few mins of track notwithstanding, route follow, track recording, etc. I don't think this is now happening.

Title: Re: New beta 5.5.23betaXX
Post by: jonny-blue on July 31, 2014, 10:40:50 AM

~~Quote~~If I exit beta9, then load it straight away again, all is well. But if I exit, leave it for a few seconds, maybe 10 seconds, then start itagain, the last route and track aren't visible

I have the same problem ... :(

Title: Re: New beta 5.5.23betaXX
Post by: jonny-blue on July 31, 2014, 03:01:33 PM

~~Quote~~I have the same problem ... :(

PS: Went back to .08 ... planned a route, loaded the route and some geocaches as waypoints ... and after an hour I wanted to start but there was no route and waypoint anymore.

Only the map was exactly positioned where I wanted to start ...

Seems not to be a problem only of .09 ... :shock:

Title: Re: New beta 5.5.23betaXX
Post by: jonny-blue on July 31, 2014, 11:31:22 PM

~~Quote~~Went back to .08

... and even this release stopped recording after intensive use of some other apps at the same time. :shock:

Title: Re: New beta 5.5.23betaXX
Post by: Uli on August 02, 2014, 12:38:47 PM

My last version where the last track comes back is beta7

Title: Re: New beta 5.5.23betaXX
Post by: orux on August 02, 2014, 01:05:56 PM

~~Quote from: "goosiebn"~~If I exit beta9, then load it straight away again, all is well. But if I exit, leave it for a few seconds, maybe 10 seconds, then start itagain, the last route and track aren't visible. Also, I was recording a track and I presume Orux was killed (because I was web browsing), the track log active notification was still there, but when I loaded beta again, similar situation- no current track. I've seen in the past on an old phone where the phone rebooted, I just started Orux and everthing just resumed, last few mins of track notwithstanding, route follow, track recording, etc. I don't think this is now happening.

Hi,

can you reproduce that problem? (start the beta version, load a route, 'home' button, kill OruxMaps with the task manager, then restart OruxMaps)

is there the loaded route?

your devece and android version?

orux

Title: Re: New beta 5.5.23betaXX
Post by: goosiebn on August 02, 2014, 03:29:38 PM

~~Quote from: "orux"~~
~~Quote from: "goosiebn"~~If I exit beta9, then load it straight away again, all is well. But if I exit, leave it for a few seconds, maybe 10 seconds, then start itagain, the last route and track aren't visible. Also, I was recording a track and I presume Orux was killed (because I was web browsing), the track log active notification was still there, but when I loaded beta again, similar situation- no current track. I've seen in the past on an old phone where the phone rebooted, I just started Orux and everthing just resumed, last few mins of track notwithstanding, route follow, track recording, etc. I don't think this is now happening.

Hi,

can you reproduce that problem? (start the beta version, load a route, 'home' button, kill OruxMaps with the task manager, then restart OruxMaps)

is there the loaded route?

your devece and android version?

orux

Yeah, reproduced exactly as you described. Also concerned that closing Oruxmaps properly also loses current track, route, etc.

Title: Re: New beta 5.5.23betaXX
Post by: orux on August 02, 2014, 03:40:18 PM

~~Quote from: "goosiebn"~~
~~Quote from: "orux"~~
~~Quote from: "goosiebn"~~If I exit beta9, then load it straight away again, all is well. But if I exit, leave it for a few seconds, maybe 10 seconds, then start itagain, the last route and track aren't visible. Also, I was recording a track and I presume Orux was killed (because I was web browsing), the track log active notification was still there, but when I loaded beta again, similar situation- no current track. I've seen in the past on an old phone where the phone rebooted, I just started Orux and everthing just resumed, last few mins of track notwithstanding, route follow, track recording, etc. I don't think this is now happening.

Hi,

can you reproduce that problem? (start the beta version, load a route, 'home' button, kill OruxMaps with the task manager, then restart OruxMaps)

is there the loaded route?

your devece and android version?

orux

Yeah, reproduced exactly as you described. Also concerned that closing Oruxmaps properly also loses current track, route, etc.

device and android version?

orux

Title: Re: New beta 5.5.23betaXX
Post by: goosiebn on August 02, 2014, 03:48:40 PM

~~Quote from: "orux"~~
~~Quote from: "goosiebn"~~
~~Quote from: "orux"~~

Hi,

can you reproduce that problem? (start the beta version, load a route, 'home' button, kill OruxMaps with the task manager, then restart OruxMaps)

is there the loaded route?

your devece and android version?

orux

Yeah, reproduced exactly as you described. Also concerned that closing Oruxmaps properly also loses current track, route, etc.

device and android version?

orux

Sorry! Moto E, v4.4.4

Title: Re: New beta 5.5.23betaXX
Post by: jonny-blue on August 02, 2014, 04:28:06 PM

~~Quote~~Hi,

can you reproduce that problem? (start the beta version, load a route, 'home' button, kill OruxMaps with the task manager, then restart OruxMaps)

is there the loaded route?

Hi Orux,

because I had the same problem I went back to beta .04 ... and there the problem doesn't exist.

I can stop OM with task manager or even reboot the phone ... the last loaded route always exists. 8-)

Title: Re: New beta 5.5.23betaXX
Post by: goosiebn on August 02, 2014, 05:09:59 PM

I'm finding with the release version, when I task kill Orux, it restarts recording automatically, without having to manually launch Orux, or use the Track logging active notification.

Title: Re: New beta 5.5.23betaXX
Post by: orux on August 02, 2014, 06:15:59 PM

~~Quote from: "goosiebn"~~I'm finding with the release version, when I task kill Orux, it restarts recording automatically, without having to manually launch Orux, or use the Track logging active notification.

Yes, that is the expected behaviour.

I think I have found the problem; a strange bug after changing the compilation enviroment...

orux

Title: Re: New beta 5.5.23betaXX
Post by: orux on August 03, 2014, 07:13:23 PM

~~Quote from: "jonny-blue"~~
~~Quote~~Hi,

can you reproduce that problem? (start the beta version, load a route, 'home' button, kill OruxMaps with the task manager, then restart OruxMaps)

is there the loaded route?

Hi Orux,

because I had the same problem I went back to beta .04 ... and there the problem doesn't exist.

I can stop OM with task manager or even reboot the phone ... the last loaded route always exists. 8-)

Hi,

please, try with last beta10 version, tell me if the problem persist.

orux

Title: Re: New beta 5.5.23betaXX
Post by: jonny-blue on August 04, 2014, 08:45:22 AM

~~Quote~~please, try with last beta10 version, tell me if the problem persist.

Hi,

at the first glance ... all looks pretty well. THX 8-)

I'll check it within the next trips.

Title: Re: New beta 5.5.23betaXX
Post by: Uli on August 04, 2014, 01:51:25 PM

On my S4 Active the last track comes back after switch off now with beta 10 Uli

Title: Re: New beta 5.5.23betaXX
Post by: Legend on August 04, 2014, 05:46:32 PM

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

please, try with last beta10 version, tell me if the problem persist.

orux

I think that beta10 solves a similar issue with KML overlays we discussed some months ago but it was difficult to reproduce it :-)

I tried a couple times and it remembers the opened overlays after killing the application.

Title: Re: New beta 5.5.23betaXX
Post by: orux on August 07, 2014, 05:06:51 PM

Hello,

beta updated to .11 version

orux

Title: Re: New beta 5.5.23betaXX
Post by: mntr86 on August 07, 2014, 05:53:43 PM

Hi, the new beta support garmin trek map?

Title: Re: New beta 5.5.23betaXX
Post by: Uli on August 07, 2014, 09:21:33 PM

No problems so far with version .11

Title: Re: New beta 5.5.23betaXX
Post by: goosiebn on August 09, 2014, 05:02:27 PM

The TTS far from route alarm was a pleasant surprise today thanks, a good alternative to my ringing tone volume issues.

Title: Re: New beta 5.5.23betaXX
Post by: Barabli on August 10, 2014, 07:50:58 PM

Hello,

I am using a Kitkat Smartphone and I installed the beta version of Oruxmaps.

Now I have 2 folders created by Oruxmaps :

1) on the base storage : oruxmaps

2) a second folder on the SDCard : Android/data/com.orux.oruxmapsbeta

in the product Menu -> settings -> Maps -> Maps directory

it says

Where the offline maps are stored

(/storage/emulated/0/oruxmaps/mapfiles/)

I have a big map file (openandroidmap) wich is 2 GB FRANCE.map

I don't want tu put the map file on the internal storage. So I try to change the Map directory setting to point to the Oruxmaps folder on the SDCard but I was not able to change it.

Can you help ?

Thks

Title: Re: New beta 5.5.23betaXX
Post by: orux on August 11, 2014, 05:34:34 PM

~~Quote from: "Barabli"~~Hello,

I am using a Kitkat Smartphone and I installed the beta version of Oruxmaps.

Now I have 2 folders created by Oruxmaps :

1) on the base storage : oruxmaps

2) a second folder on the SDCard : Android/data/com.orux.oruxmapsbeta

in the product Menu -> settings -> Maps -> Maps directory

it says

Where the offline maps are stored

(/storage/emulated/0/oruxmaps/mapfiles/)

I have a big map file (openandroidmap) wich is 2 GB FRANCE.map

I don't want tu put the map file on the internal storage. So I try to change the Map directory setting to point to the Oruxmaps folder on the SDCard but I was not able to change it.

Can you help ?

Thks

Hi, why you can't select that folder?

remember that you have to do a 'double click' in the built-in directory browser when you want to select a new one.

orux

Title: Re: AW: New beta 5.5.23betaXX
Post by: BerniPi on August 16, 2014, 05:27:41 PM

Deleted

Title: Re: New beta 5.5.23betaXX
Post by: Quercus.JB on August 22, 2014, 03:25:15 PM

Hola orux, en la beta me ocurre lo siguiente, cuando quiero sacar la nueva estadistica consolidada de varios track, no me deja desplazar la imagen hacia abajo y terminar de ver toda las estadistica, te pongo una imagen(//%3C/s%3E%3CURL%20url=%22http://tapatalk.imageshack.com/v2/14/08/22/823a1bcb7909405b47df611a047d89e8.jpg%22%3E%3CLINK_TEXT%20text=%22http://tapatalk.imageshack.com/v2/14/08%20...%207d89e8.jpg%22%3Ehttp://tapatalk.imageshack.com/v2/14/08/22/823a1bcb7909405b47df611a047d89e8.jpg%3C/LINK_TEXT%3E%3C/URL%3E%3Ce%3E)

Title: Re: New beta 5.5.23betaXX
Post by: rydzejak on August 24, 2014, 11:45:44 PM

Hi,

I'm not sure if beta 5.5.23.beta12 was already fixed for problem with WMS service (user agent) ?

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

I tried 5.5.23.beta12 and failed to connect to WMS

//http://mapy.geoportal.gov.pl/wss/service/img/guest/topo/mapserver/wmsserver

Creator says "error reading WMS function" (in polish translation: "błąd podczas próby odczytu funkcji WMS"

WMS service is alive:

//http://mapy.geoportal.gov.pl/wss/service/img/guest/topo/mapserver/wmsserver?SERVICE=WMS&REQUEST=GetCapabilities

I also posted a question to Geoportal Admins to find out if it is OK to restrict access to some applications.

rgds

Jakub

[EDIT 2014-08-28] : Solved in version 5.5.23 beta 14. Many thanks !

Title: Re: New beta 5.5.23betaXX
Post by: Quercus.JB on August 28, 2014, 03:27:36 PM

hola orux, una cuestion menor, cuando pones una nueva beta editas el primer post y eso no refleja actualizacion, por lo q tenemos q ir de manera manual al primer post a ver si tenemos beta nueva, se resolveria si ademas de editar el primer post pones uno nuevo diciendo que ya esta la beta, gracias.

Enviado desde mi LG-E460 mediante Tapatalk

Title: Re: New beta 5.5.23betaXX
Post by: goosiebn on August 31, 2014, 09:52:32 PM

Slippy maps

If you're using a Slippy map and either you exit and re-start OruxMaps, or if the screen auto-rotates, the map switches to the previous online map and the previous position.

If there are no tiles for zoom levels 16 and 17 and you zoom from 12, 13, 14, 15 to 16 to 17, it shows a digitally zoomed tile of zoom 15 (at levels 16 & 17). If you zoom back out to 16, nothing is shown. If you also zoom back to 15 and get a map at level 15, but then zoom back in to 16 or 17 nothing is displayed this time. You have to zoom back to 14, through 15 again, for 16 or 17 to then show the digital zoomed copy of zoom 15.

Cheers.

Title: Re: New beta 5.5.23betaXX
Post by: goosiebn on September 02, 2014, 03:58:58 PM

The tile loading for missing zoom levels is more obvious with finalise zoom option on.

Title: Re: New beta 5.5.23betaXX
Post by: orux on September 02, 2014, 09:23:07 PM

Updated to beta16

orux

Title: Re: New beta 5.5.23betaXX
Post by: goosiebn on September 04, 2014, 03:50:41 PM

Rotating and restarting the app are now ok with slippy maps. Is it intentional that they are not listed when attempting to create a multi layered map?

Title: Re: New beta 5.5.23betaXX
Post by: goosiebn on September 06, 2014, 11:01:12 AM

Double loading routes.

If I load a route, exit, then load Orux again, it appears the route loads twice.

It looks ok when first loaded, but when re-loading Orux, the route is drawn with the arrows and the dashed pink line.

Title: Re: New beta 5.5.23betaXX
Post by: goosiebn on September 09, 2014, 02:10:38 PM

I'm finding the mapfiles folder is not the best place to store slippy maps. With a large number of files here (in subfolders), Oruxmaps takes a long time to start.

Title: Re: New beta 5.5.23betaXX
Post by: orux on September 10, 2014, 12:58:20 PM

~~Quote from: "goosiebn"~~I'm finding the mapfiles folder is not the best place to store slippy maps. With a large number of files here (in subfolders), Oruxmaps takes a long time to start.

You are right,

it is not a 'normal' offline map; OruxMaps needs to search along all the folders in mapfiles/ directory each time looking for new offline maps.

orux

Title: Re: New beta 5.5.23betaXX
Post by: Uli on September 10, 2014, 05:24:26 PM

So far I can't find a comment to Multitrack with beta16.

I can't see the track of my friend. Only his current position. What could I do wrong? Uli

Title: Re: New beta 5.5.23betaXX
Post by: Uli on September 10, 2014, 08:10:29 PM

Sorry

...suddenly it seems to work.

But I don't know why. I give it another try.

Maybe I didn't see the small yellow line?

Title: Re: New beta 5.5.23betaXX
Post by: Quercus.JB on September 10, 2014, 09:54:45 PM

~~Quote from: "Quercus.JB"~~Hola orux, en la beta me ocurre lo siguiente, cuando quiero sacar la nueva estadistica consolidada de varios track, no me deja desplazar la imagen hacia abajo y terminar de ver toda las estadistica, te pongo una imagen(//%3C/s%3E%3CURL%20url=%22http://tapatalk.imageshack.com/v2/14/08/22/823a1bcb7909405b47df611a047d89e8.jpg%22%3E%3CLINK_TEXT%20text=%22http://tapatalk.imageshack.com/v2/14/08%20...%207d89e8.jpg%22%3Ehttp://tapatalk.imageshack.com/v2/14/08/22/823a1bcb7909405b47df611a047d89e8.jpg%3C/LINK_TEXT%3E%3C/URL%3E%3Ce%3E)

resuelto en la última beta, gracias

Enviado desde mi LG-E460 mediante Tapatalk

Title: Re: New beta 5.5.23betaXX
Post by: Uli on September 12, 2014, 03:08:27 PM

I have to come back to multitracking of version beta16:

unfortunately the line of my friends track (yellow) is very thin. If I increase the route line witdh,

it is ok, but then the normal route line to follow (blue) is too large.

Is there a solution? Uli

Title: Re: New beta 5.5.23betaXX
Post by: orux on September 15, 2014, 12:51:05 PM

~~Quote from: "Uli"~~I have to come back to multitracking of version beta16:

unfortunately the line of my friends track (yellow) is very thin. If I increase the route line witdh,

it is ok, but then the normal route line to follow (blue) is too large.

Is there a solution? Uli

Hi, Uli;

today I will release a new beta, with two different settings, one for the main route stroke width, another for the secondary routes/multitrack paths.

orux

Title: Re: New beta 5.5.23betaXX
Post by: orux on September 16, 2014, 04:06:45 PM

~~Quote from: "orux"~~
~~Quote from: "Uli"~~I have to come back to multitracking of version beta16:

unfortunately the line of my friends track (yellow) is very thin. If I increase the route line witdh,

it is ok, but then the normal route line to follow (blue) is too large.

Is there a solution? Uli

Hi, Uli;

today I will release a new beta, with two different settings, one for the main route stroke width, another for the secondary routes/multitrack paths.

orux

Released beta18 version

orux

Title: Re: New beta 5.5.23betaXX
Post by: goosiebn on September 16, 2014, 04:55:34 PM

~~Quote from: "goosiebn"~~Double loading routes.

If I load a route, exit, then load Orux again, it appears the route loads twice.

It looks ok when first loaded, but when re-loading Orux, the route is drawn with the arrows and the dashed pink line.

This problem is still here in beta 18.

Title: Re: New beta 5.5.23betaXX
Post by: orux on September 16, 2014, 07:48:46 PM

~~Quote from: "goosiebn"~~
~~Quote from: "goosiebn"~~Double loading routes.

If I load a route, exit, then load Orux again, it appears the route loads twice.

It looks ok when first loaded, but when re-loading Orux, the route is drawn with the arrows and the dashed pink line.

This problem is still here in beta 18.

Hi,

I can't reproduce that problem.

Which kind of route?

Could you send me one with that problem?

orux

Title: Re: New beta 5.5.23betaXX
Post by: goosiebn on September 16, 2014, 08:11:40 PM

~~Quote from: "orux"~~
~~Quote from: "goosiebn"~~
~~Quote from: "goosiebn"~~Double loading routes.

If I load a route, exit, then load Orux again, it appears the route loads twice.

It looks ok when first loaded, but when re-loading Orux, the route is drawn with the arrows and the dashed pink line.

This problem is still here in beta 18.

Hi,

I can't reproduce that problem.

Which kind of route?

Could you send me one with that problem?

orux

I've reproduced this with any track from the database- either imported or recorded.

I have no track or route, load a route from the db with no recording or following, exit Orux with two presses of the on-screen back button.

Then I launch a task monitor an wait a few minutes for Oruxmaps to disappear from the task list.

Then I launch Oruxmaps and it shows the route both with the arrowed line and with the pink dashed line.

Doesn't happen with the latest Play version.

Title: Re: New beta 5.5.23betaXX
Post by: Uli on September 16, 2014, 09:02:02 PM

Concerning Multitracking: I am delighted. It looks great now on my S5. Uli

Title: Re: New beta 5.5.23betaXX
Post by: orux on September 17, 2014, 07:14:51 PM

~~Quote from: "goosiebn"~~
I've reproduced this with any track from the database- either imported or recorded.

I have no track or route, load a route from the db with no recording or following, exit Orux with two presses of the on-screen back button.

Then I launch a task monitor an wait a few minutes for Oruxmaps to disappear from the task list.

Then I launch Oruxmaps and it shows the route both with the arrowed line and with the pink dashed line.

Doesn't happen with the latest Play version.

Hi,

Finally I can reproduce the problem,

I will solve it soon,

orux

Title: Re: New beta 5.5.23betaXX
Post by: orux on September 24, 2014, 08:27:00 PM

Hi,

updated to beta24

orux

Title: Re: New beta 5.5.23betaXX
Post by: Maki on September 30, 2014, 10:18:00 PM

Hi Josè, developing my MapsForge theme I compared OM with other apps (Cruiser in particular), and I have noticed that the behaviour is consistent except for circles and text offset (dy) that are smaller in OM. On my devices the tile size is 512px in both Cruiser and OM, so it should not depend on the fixed tile size you choose. I raised the thing on the MF list and Emux said he is using the stock library so it's probably some setting you are using.

If at all possible it would be useful to fix this in order to have themes that are as universal as possible.

Another point I raised, without much success, on the MF list is automatic scaling of bitmap icons. You proved that scaling PNGs is possible and works very well, but asking users to manually set this parameter is inconvenient. Since this will not be fixed in the library at least until 0.6 what about doing it in OM? There is no need for a proprietary derive, we can simply add a parameter in form of a comment, e.g.  that you can read and others will ignore. It's an ugly hack, I know, but it would make a lot of difference.

Thanks,

Maki.

Title: Re: New beta 5.5.23betaXX
Post by: eartrumpet on October 01, 2014, 08:14:10 AM

~~Quote from: "Maki"~~
If at all possible it would be useful to fix this in order to have themes that are as universal as possible.

...

parameter in form of a comment, e.g.  that you can read and others will ignore

+1

Title: Re: New beta 5.5.23betaXX
Post by: orux on October 01, 2014, 05:46:03 PM

~~Quote from: "Maki"~~Hi Josè, developing my MapsForge theme I compared OM with other apps (Cruiser in particular), and I have noticed that the behaviour is consistent except for circles and text offset (dy) that are smaller in OM. On my devices the tile size is 512px in both Cruiser and OM, so it should not depend on the fixed tile size you choose. I raised the thing on the MF list and Emux said he is using the stock library so it's probably some setting you are using.

If at all possible it would be useful to fix this in order to have themes that are as universal as possible.

Another point I raised, without much success, on the MF list is automatic scaling of bitmap icons. You proved that scaling PNGs is possible and works very well, but asking users to manually set this parameter is inconvenient. Since this will not be fixed in the library at least until 0.6 what about doing it in OM? There is no need for a proprietary derive, we can simply add a parameter in form of a comment, e.g.  that you can read and others will ignore. It's an ugly hack, I know, but it would make a lot of difference.

Thanks,

Maki.

Uploaded beta28 version.

Hi, Maki;

With default installation, All parameters are set to '1', so the maps should be painted with default sizes for a 512 fixed tile size.

The same with icons size.

OruxMaps does not read the theme xml file; it is passed parsed and decoded by the mapsforge library.

What I can try is, when installed for the first time, detect the dpi of the screen, and automatically adjust the parameters of the mapsforge maps.

orux

Title: Re: New beta 5.5.23betaXX
Post by: Holiday on October 01, 2014, 09:06:38 PM

Hi Orux,

is it normaly disabled setting "Altitude from DEM". It can not be checked in beta 24 and beta 28.

Can I translate Apk and Manual to Slovenian language? Please where I find procedure?

Thanks.

Title: Re: New beta 5.5.23betaXX
Post by: eartrumpet on October 01, 2014, 10:32:14 PM

~~Quote from: "orux"~~

What I can try is, when installed for the first time, detect the dpi of the screen, and automatically adjust the parameters of the mapsforge maps.

If this is similar to the default mapsforge viewer it would help theme developers a lot!

Title: Re: New beta 5.5.23betaXX
Post by: Maki on October 02, 2014, 01:40:45 PM

The new feature to keep map scale consistent between maps seems to work fine (I tried with mbtiles and mapsforge), and is very welcome, with one exception: the dashboard shows a fake zoom level, it should show the one used by the library to avoid confusion for theme and map developers (I think anyone else just ignores this information).

Downloading from OAM didn't work at a first attempt, I chose Oruxmaps, but then nothing happened. But I need to try better later, I have an advanced download manager installed on the phone that may get in the way.

~~Quote from: "orux"~~What I can try is, when installed for the first time, detect the dpi of the screen, and automatically adjust the parameters of the mapsforge maps.

No, I think it would be worse: you would need a standard universal reference, but there isn't one.

I'm not a coder, so please excuse me if I don't express myself correctly. I don't exactly know where OM ends and MF starts. To the best of my knowledge this is what happens:

a) I chose a theme

b) OM reads the user scaling parameters from the preferences

c) OM passes the theme and the parameters to MF library

d) tiles are painted and sent to OM

The problem is that someone switching between themes with icons rendered for different densities also need to manually change the scaling factor.

I propose to change that to:

a) I chose a theme

b) OM scans the XML searching for the first occurrence of the special comment and reads the reference dpi

c) OM calculates the scaling parameter for the icons (e.g. the theme reference is 320, the device is 480--> 1.5 factor)

d) OM reads the user scaling parameters from the preferences

e) OM multiplies the auto-calculated with the user supplied one

d) OM passes the theme and the parameters to MF library

e) tiles are painted and sent to OM

This allows to switch between themes from different developers that are using different icon sets automatically, leaving users the ability to have a final word to fine tune things if they feel the need to.

I don't know if what I wrote makes sense, but I hope so. :-)

Maki

Title: Re: New beta 5.5.23betaXX
Post by: orux on October 02, 2014, 05:45:00 PM

~~Quote from: "Holiday"~~Hi Orux,

is it normaly disabled setting "Altitude from DEM". It can not be checked in beta 24 and beta 28.

Can I translate Apk and Manual to Slovenian language? Please where I find procedure?

Thanks.

Hi,

You can not have both 'use barometer for altitude' and 'use DEM files for altitude' enabled.

orux

Title: Re: New beta 5.5.23betaXX
Post by: goosiebn on October 02, 2014, 06:45:39 PM

You've changed Send via email as to Share as, but could do with changing the explanatory text for the email address setting in Integration to include the text Share as, so it is clear that once you've set an email address, you use it by sharing the track.

Title: Re: New beta 5.5.23betaXX
Post by: Holiday on October 02, 2014, 08:51:04 PM

Orux,

I have Tablet without Barometer sensor and Barometer for elevation is normally disabled - dark letter. Also Menu under it Altitude from DEM is disabled - dark letter. All this is under Sensor - GPS Menu. At User interface - Dashboard - User interface - Viewer mode menu Altitude from DEM - bright letter - it can be checked and is visible on Display. Phone Samsung without Barometer sensor has the same simptoms.

Regards.

Title: Re: New beta 5.5.23betaXX
Post by: fabrylama on October 03, 2014, 05:54:37 PM

HI Orux,

since the last few betas I'm experiencing a bug in the tc1 view, if I change the second (big) field this happens:

(//%3C/s%3E%3CURL%20url=%22http://i61.tinypic.com/2n68ydd.png%22%3Ehttp://i61.tinypic.com/2n68ydd.png%3C/URL%3E%3Ce%3E)

The 2nd field is the one I wanted to change and the 4th field is the new one

If I press back and then go to tc1 again, everything is back to normal.

Fabrizio

ps. the phone is an xperia active

Title: Re: New beta 5.5.23betaXX
Post by: kech61 on October 04, 2014, 10:28:26 AM

Hi,

The download tables on openandromaps are now ready for the direct install of maps into Orux.

just klick on the "+" sign left of the mapname and choose >install on Orux.

There were some problems in the beginning - these issues should be resolved now.

The resizing of the downloadtables in responsive view is improved too and should work flawless now.

@Orux:

1. What I'v seen is that after download an installing the map+themes Oruxmaps switches back to osmarender theme (maybe this happens only on my virtual tablett..).

Would it be possible that it switches back to the theme previously used?

2. Is it possible to indicate the status of the download and unziping in Oruxmaps - it takes lots of time to download and uncompress the maps. Maybe user think that the App has crashed without a progress bar (atleast while unzipping).

Title: Re: New beta 5.5.23betaXX
Post by: orux on October 04, 2014, 06:06:22 PM

~~Quote from: "fabrylama"~~HI Orux,

since the last few betas I'm experiencing a bug in the tc1 view, if I change the second (big) field this happens:

(//%3C/s%3E%3CURL%20url=%22http://i61.tinypic.com/2n68ydd.png%22%3Ehttp://i61.tinypic.com/2n68ydd.png%3C/URL%3E%3Ce%3E)

The 2nd field is the one I wanted to change and the 4th field is the new one

If I press back and then go to tc1 again, everything is back to normal.

Fabrizio

ps. the phone is an xperia active

Thanks, Fabrizio;

it is a bug, solved for next version.

orux

Title: Re: New beta 5.5.23betaXX
Post by: orux on October 04, 2014, 06:13:55 PM

~~Quote from: "kech61"~~Hi,

The download tables on openandromaps are now ready for the direct install of maps into Orux.

just klick on the "+" sign left of the mapname and choose >install on Orux.

There were some problems in the beginning - these issues should be resolved now.

The resizing of the downloadtables in responsive view is improved too and should work flawless now.

@Orux:

1. What I'v seen is that after download an installing the map+themes Oruxmaps switches back to osmarender theme (maybe this happens only on my virtual tablett..).

Would it be possible that it switches back to the theme previously used?

2. Is it possible to indicate the status of the download and unziping in Oruxmaps - it takes lots of time to download and uncompress the maps. Maybe user think that the App has crashed without a progress bar (atleast while unzipping).

Thanks, Christian;

1.-That should not happen. I think it is working fine in my device. In the last versions, if you open 'tweaks'--'mapsforge style', and you leave without selecting a new theme, the app returns to osmarender default theme. May be you did that?

2.-I have added an indeterminate progress bar with a text about 'unzipping, wait,..', because I have information about download progress, but I haven't about unzipping progress.

orux

Title: Re: New beta 5.5.23betaXX
Post by: eartrumpet on October 05, 2014, 09:20:23 AM

~~Quote from: "orux"~~

I returned to the mapsforge library 0.4.3, I think it is better to work with this version, which is working well.

Maybe it's time to revisit 0.5, a RC1 has just been released:

//https://groups.google.com/forum/#!topic/mapsforge-dev/KKqgIAmmKmo

It should be faster in rendering, and it also adds some valuable enhancements to the themes:

//https://code.google.com/p/mapsforge/wiki/RenderthemeV4

As the themes have to be adjusted for the new Oruxmaps anyway, it would be nice to add for example priorities for symbols/captions while I'm at it :-)

Best regards,

Tobias

Title: Re: New beta 5.5.23betaXX
Post by: orux on October 05, 2014, 07:56:39 PM

~~Quote from: "eartrumpet"~~
~~Quote from: "orux"~~

I returned to the mapsforge library 0.4.3, I think it is better to work with this version, which is working well.

Maybe it's time to revisit 0.5, a RC1 has just been released:

//https://groups.google.com/forum/#!topic/mapsforge-dev/KKqgIAmmKmo

It should be faster in rendering, and it also adds some valuable enhancements to the themes:

//https://code.google.com/p/mapsforge/wiki/RenderthemeV4

As the themes have to be adjusted for the new Oruxmaps anyway, it would be nice to add for example priorities for symbols/captions while I'm at it :-)

Best regards,

Tobias

Hi, Tobias;

I think it is better to release now with version 0.4.3. I hope that the current version of OruxMaps will be ready in one week.

Anyway, I think the change to 0.5. will be faster.

orux

Title: Re: New beta 5.5.23betaXX
Post by: orux on October 05, 2014, 08:02:23 PM

Hi,

updated beta30

orux

Title: Re: New beta 5.5.23betaXX
Post by: Holiday on October 06, 2014, 10:42:27 AM

Hi,

In beta 30 "Altitude from DEM" active again. Thanks Orux.

Title: Re: New beta 5.5.23betaXX
Post by: 6745th@web.de on October 09, 2014, 08:12:43 PM

Today I ordered a wahoo sc sensor at Amazon.

I'm curious if it works.

I will report....

BTW:Which smart watch is supported? Pebble?

Title: Re: New beta 5.5.23betaXX
Post by: Uli on October 10, 2014, 03:28:09 PM

And I got a Garmin Cadence Sensor (without magnet) which doesn't show proper values on Oruxmaps. IpSensor Man shows values correct. Might it be an Oruxmaps problem?

Title: Re: New beta 5.5.23betaXX
Post by: orux on October 10, 2014, 05:15:07 PM

~~Quote from: "6745th@web.de"~~Today I ordered a wahoo sc sensor at Amazon.

I'm curious if it works.

I will report....

BTW:Which smart watch is supported? Pebble?

Hi,

Only Android Wear devices.

orux

Title: Re: New beta 5.5.23betaXX
Post by: orux on October 10, 2014, 06:07:32 PM

~~Quote from: "Uli"~~And I got a Garmin Cadence Sensor (without magnet) which doesn't show proper values on Oruxmaps. IpSensor Man shows values correct. Might it be an Oruxmaps problem?

Hi, Uli;

is it an ANT+ or BT device?

Could you add a link to the specs of that device?

orux

Title: Re: New beta 5.5.23betaXX
Post by: fabrylama on October 10, 2014, 08:33:11 PM

~~Quote from: "orux"~~
~~Quote from: "Uli"~~And I got a Garmin Cadence Sensor (without magnet) which doesn't show proper values on Oruxmaps. IpSensor Man shows values correct. Might it be an Oruxmaps problem?

Hi, Uli;

is it an ANT+ or BT device?

Could you add a link to the specs of that device?

orux

It's ant+:

http://www.thisisant.com/directory/bike-cadence-sensor1/

Title: Re: New beta 5.5.23betaXX
Post by: Uli on October 10, 2014, 08:38:19 PM

Yes, that's it. It is strange - even in the little manual there is no device name. Oruxmaps shows 0.0 rpm and now and then a number like 22060... so the device is recognized

Title: Re: New beta 5.5.23betaXX
Post by: orux on October 13, 2014, 06:01:19 PM

~~Quote from: "Uli"~~Yes, that's it. It is strange - even in the little manual there is no device name. Oruxmaps shows 0.0 rpm and now and then a number like 22060... so the device is recognized

Hi, Uli,

check that you select an 'ant+ bike cadence' sensor, not a 'bike cadence and speed' or 'bike speed' sensor.

orux

Title: Re: New beta 5.5.23betaXX
Post by: Uli on October 13, 2014, 06:18:12 PM

That is what I did already. There is no response when I chose cadence + speed. But with cadence only the 0.0 rpm appear on the screen but no data. IPSensor Man still does show the right data.

Title: Re: New beta 5.5.23betaXX
Post by: Lanstronio on October 13, 2014, 09:35:02 PM

~~Quote from: "Uli"~~That is what I did already. There is no response when I chose cadence + speed. But with cadence only the 0.0 rpm appear on the screen but no data. IPSensor Man still does show the right data.
Have you considered the possibility that the sensor comes with manufacturing defect ? You have possibility to check connecting it to another receiver ? I think that could be interesting to test if you have to use the warranty.

Title: Re: New beta 5.5.23betaXX
Post by: Uli on October 13, 2014, 09:44:00 PM

That doesn't sound very plausible to me because IPSensor Man does show the correct data on my S5 phone.

Title: Re: New beta 5.5.23betaXX
Post by: orux on October 14, 2014, 05:22:56 PM

~~Quote from: "Uli"~~That doesn't sound very plausible to me because IPSensor Man does show the correct data on my S5 phone.

Hi, Uli,

please, try with this version->http://oruxmaps.com/OruxMaps5.5.23beta30b.apk

orux

Title: Re: New beta 5.5.23betaXX
Post by: Uli on October 14, 2014, 05:54:27 PM

Great, it is ok now.

Cadence Data is shown properly now.

I am delighted once more.

Thank you very much.

Uli

Title: Re: New beta 5.5.23betaXX
Post by: fabrylama on October 16, 2014, 08:04:44 PM

Hi Orux,

- when following a route, if for the second graph of the tc-2 I select "route" as source, altitude and speed as data and "distance" as x value, orux crashes after a few seconds. Tried 3 times with the same route (short) and it happened every time, then selected "time" as x value and it didn't crash.

-I don't know if it's a bug and I'm not certain it happens only in the beta (but before today I hadn't noticed), but I see something strange when following a route: the visual indication given by the "competitor" and the numerical "delay in route" don't match, if I follow the competitor in the map, the delay in route goes increasingly negative. (the competitor gives the correct indication)

Is it normal and I haven't understood what the delay in route means? If it's not normal I can send you the route.

Thanks

Title: Re: New beta 5.5.23betaXX
Post by: 6745th@web.de on October 16, 2014, 09:28:18 PM

The crashes inside tc-2 I had also several times. But I could not reproduced it.

Title: Re: AW: New beta 5.5.23betaXX
Post by: 6745th@web.de on October 16, 2014, 09:39:20 PM

~~Quote from: "6745th@web.de"~~Today I ordered a wahoo sc sensor at Amazon.

I'm curious if it works.

I will report....

BTW:Which smart watch is supported? Pebble?

Sensor has arrived and i did some short tests now.

Seems to work.

But the behavior is different than my bt-hrm. If bt is off and I start the hrm sensor the mobile ask me: "app wants to switch on bt, allow it?"

If I say yes bt is switched on, but hrm shows 0. After starting hrm again it works.

When I start my Wahoo sensor, the phone did not switch on bt. I must do that manually. From time to time Orux crashes than.

Would be perfect when Orux has the capabilities to switch on bt automatically.

Thanks Thomas

Title: Re: New beta 5.5.23betaXX
Post by: Holiday on October 17, 2014, 06:08:51 PM

Hi Orux,

I noticed at Waypoint Manager that we can search Items by Name but without result. In next window it shows all Items again but no Distance data. I have Sort settings set to Sort by Distance.

Also have TC-2 crash problem.

Regards

Title: Re: New beta 5.5.23betaXX
Post by: kech61 on October 19, 2014, 08:50:35 AM

Hi Orux,

Is there a release date for the new version?

The direct install of maps and themes is working on openandromaps.

As more and more users are on this d§$n #&@@ 4.4.2 it would be perfect to have a working and easy install.

BTW: Do you plan to port OruxMaps to windows8 or windows phone one day??

Best regards,

Christian

Title: Re: New beta 5.5.23betaXX
Post by: orux on October 19, 2014, 05:23:40 PM

Hi,

updated to beta32.

this version should solve some bugs.

orux

Title: Re: AW: New beta 5.5.23betaXX
Post by: 6745th@web.de on October 23, 2014, 07:14:33 PM

~~Quote~~But the behavior is different than my bt-hrm. If bt is off and I start the hrm sensor the mobile ask me: "app wants to switch on bt, allow it?"

If I say yes bt is switched on, but hrm shows 0. After starting hrm again it works.

When I start my Wahoo sensor, the phone did not switch on bt. I must do that manually. From time to time Orux crashes than.

With the latest beta 32 this behavour seems to be solved.

The TC2 Bug is still there, but not a big Problem for me.

The Battery Level of my BT HRM is alway shown as 0. Other App shows it correctly.

Some Feature Request for the Dashboard :
-Free sorting of the Userfields

-Local Time (Dashboard or TC1)

-Batterie Level of my Phone (Dashboard or TC1)

99% af all the Orux Functions working like a Charm.

Thanks,

Thomas

Title: Re: New beta 5.5.23betaXX
Post by: orux on October 23, 2014, 07:56:16 PM

~~Quote from: "kech61"~~Hi Orux,

Is there a release date for the new version?

The direct install of maps and themes is working on openandromaps.

As more and more users are on this d§$n #&@@ 4.4.2 it would be perfect to have a working and easy install.

BTW: Do you plan to port OruxMaps to windows8 or windows phone one day??

Best regards,

Christian

Hi, Christian;

I would like to release next version in 5-7 days, if I solve some final problems.

No, I don't plan to port oruxmaps to windows8. May be to ios, but it is a very hard work, that implies start from zero.

orux

Title: Re: New beta 5.5.23betaXX
Post by: orux on October 23, 2014, 09:51:46 PM

Hi,

updated to beta34b

orux

Title: Re: New beta 5.5.23betaXX
Post by: orux on October 26, 2014, 04:33:59 PM

Hi,

updated to beta36

orux

Title: Re: New beta 5.5.23betaXX
Post by: Uli on October 27, 2014, 07:51:01 AM

For my usage the Beta34b Version works great and without problems.

I was pleased to notice that even the cadence data is transfered live to

mapmytracks.

Than you Orux.

Uli

Title: Re: New beta 5.5.23betaXX
Post by: chobkwon on October 27, 2014, 10:43:10 AM

For my usage the Beta36 Version works great but with a problem.

[tracks/routes - statistics - See Graphics] occurs a error

(//%3C/s%3E%3CURL%20url=%22http://cfile242.uf.daum.net/image/215F553E544E12DE3EC1F4%22%3E%3CLINK_TEXT%20text=%22http://cfile242.uf.daum.net/image/215F5%20...%2012DE3EC1F4%22%3Ehttp://cfile242.uf.daum.net/image/215F553E544E12DE3EC1F4%3C/LINK_TEXT%3E%3C/URL%3E%3Ce%3E)

(//%3C/s%3E%3CURL%20url=%22http://cfile247.uf.daum.net/image/232E7B45544E12D720E4CF%22%3E%3CLINK_TEXT%20text=%22http://cfile247.uf.daum.net/image/232E7%20...%2012D720E4CF%22%3Ehttp://cfile247.uf.daum.net/image/232E7B45544E12D720E4CF%3C/LINK_TEXT%3E%3C/URL%3E%3Ce%3E)

Thank you Orux.

Title: Re: New beta 5.5.23betaXX
Post by: mntr86 on November 01, 2014, 11:58:44 AM

Dear when will be release the new version on play Store? Thank you

Title: Re: New beta 5.5.23betaXX
Post by: 6745th@web.de on November 01, 2014, 08:54:46 PM

~~Quote from: "6745th@web.de"~~Today I ordered a wahoo sc sensor at Amazon.

I'm curious if it works.

I will report....

BTW:Which smart watch is supported? Pebble?

Hi Orux,

would it be easy to store the speed of my Wahoo Speed Data inside the GPX ?

The officiel Tag is
Code Select Expand gpxtpx:speed
//http://www8.garmin.com/xmlschemas/TrackPointExtensionv2.xsd

Thanks,

Thomas

Title: Re: New beta 5.5.23betaXX
Post by: orux on November 02, 2014, 04:02:44 PM

Hi, updated beta version.

I will publish this version if no more bugs found,

orux

Title: Re: New beta 5.5.23betaXX
Post by: Quercus.JB on November 02, 2014, 04:27:26 PM

;););)

Enviado desde mi LG-E460 mediante Tapatalk

Title: Re: New beta 5.5.23betaXX
Post by: Maki on November 02, 2014, 06:03:33 PM

The strings in the button editor aren't localised. I checked both the strings and the array files, and I cannot find the corresponding voices. Still, I'm sure I saw them... Can you check that the files are current?

Title: Re: New beta 5.5.23betaXX
Post by: orux on November 02, 2014, 06:34:00 PM

~~Quote from: "Maki"~~The strings in the button editor aren't localised. I checked both the strings and the array files, and I cannot find the corresponding voices. Still, I'm sure I saw them... Can you check that the files are current?

Thanks, Maki,

you are right, updated the google docs with the new array entries.

orux

Title: Re: New beta 5.5.23betaXX
Post by: Maki on November 02, 2014, 09:24:57 PM

Small bug: when searching a route with Mapquest if one taps "avoids" and then cancels the selection the field goes black.

Title: Re: New beta 5.5.23betaXX
Post by: fabrylama on November 02, 2014, 09:35:20 PM

Hi, I haven't tried the last beta, but with the beta36 this problem was still present:

~~Quote from: "fabrylama"~~
-I don't know if it's a bug and I'm not certain it happens only in the beta (but before today I hadn't noticed), but I see something strange when following a route: the visual indication given by the "competitor" and the numerical "delay in route" don't match, if I follow the competitor in the map, the delay in route goes increasingly negative. (the competitor gives the correct indication)

Is it normal and I haven't understood what the delay in route means? If it's not normal I can send you the route.

Thanks

In particular, the two indications match most of the time, but sometimes (once every few minutes) the "delay in route" suddenly jumps to -2min (not always 2 min) and then slowly goes back up to 0, then it works well for a short while until it jumps again.

I'll try the rc1 as soon as it stops raining :)

Thanks

Title: Re: New beta 5.5.23betaXX
Post by: orux on November 03, 2014, 06:47:23 PM

~~Quote from: "fabrylama"~~Hi, I haven't tried the last beta, but with the beta36 this problem was still present:

~~Quote from: "fabrylama"~~
-I don't know if it's a bug and I'm not certain it happens only in the beta (but before today I hadn't noticed), but I see something strange when following a route: the visual indication given by the "competitor" and the numerical "delay in route" don't match, if I follow the competitor in the map, the delay in route goes increasingly negative. (the competitor gives the correct indication)

Is it normal and I haven't understood what the delay in route means? If it's not normal I can send you the route.

Thanks

In particular, the two indications match most of the time, but sometimes (once every few minutes) the "delay in route" suddenly jumps to -2min (not always 2 min) and then slowly goes back up to 0, then it works well for a short while until it jumps again.

I'll try the rc1 as soon as it stops raining :)

Thanks

Hi,

the delay is the difference between the time it took you to arrive to your current position, and the time it took your partner to arrive the same point.

the value is positive if it is a delay. Your time is greater than the time of your partner.

the value is negative if you go ahead, your time is less than the time of the track creator.

if your position is near the partner icon, the delay should be near zero. Negative if you go ahead.

orux

Title: Re: AW: New beta 5.5.23betaXX
Post by: 6745th@web.de on November 03, 2014, 09:25:28 PM

Open bugs in rc1? Some small bugs are open e.g:

Battery level of my Bluetooth hrm is still not displayed. (Mio alpha)

http://www.oruxmaps.com/foro/viewtopic.php?t=2374

The "tc-2" bug (app crash) ,I can't reproduce anymore. Did you fix that Orux?

Greetings, Thomas

Title: Re: New beta 5.5.23betaXX
Post by: fabrylama on November 03, 2014, 11:05:36 PM

~~Quote from: "orux"~~
~~Quote from: "fabrylama"~~Hi, I haven't tried the last beta, but with the beta36 this problem was still present:

~~Quote from: "fabrylama"~~
-I don't know if it's a bug and I'm not certain it happens only in the beta (but before today I hadn't noticed), but I see something strange when following a route: the visual indication given by the "competitor" and the numerical "delay in route" don't match, if I follow the competitor in the map, the delay in route goes increasingly negative. (the competitor gives the correct indication)

Is it normal and I haven't understood what the delay in route means? If it's not normal I can send you the route.

Thanks

In particular, the two indications match most of the time, but sometimes (once every few minutes) the "delay in route" suddenly jumps to -2min (not always 2 min) and then slowly goes back up to 0, then it works well for a short while until it jumps again.

I'll try the rc1 as soon as it stops raining :)

Thanks

Hi,

the delay is the difference between the time it took you to arrive to your current position, and the time it took your partner to arrive the same point.

the value is positive if it is a delay. Your time is greater than the time of your partner.

the value is negative if you go ahead, your time is less than the time of the track creator.

if your position is near the partner icon, the delay should be near zero. Negative if you go ahead.

orux

Ok, with the market version of the app it works correctly, when I follow a track directly on the partner icon, the delay is roughly 0 (with a few seconds cycle between +4 and 0 seconds).

With the beta it doesn't work correctly, when I follow a track on the partner icon, the delay randomly jumps to -2minutes and slowly goes back up to 0 (in a few minutes), then it stays at 0 for another few minutes and then jumps again.

Fabrizio

Title: Re: New beta 5.5.23betaXX
Post by: Jbrio on November 04, 2014, 06:02:05 PM

hola, en las ultimas betas ha desaparecido Configuración / GPS donde, por ejemplo podia determinar tiempo o distancia minima para guardar un punto de track asi como la precisión minima para guardar puntos.

Esto, parece que ha desaparecido y para mí era muy util para evitar un track resultante con excesivos puntos y muchos de ellos redundantes.

En la nueva rc1 esto se puede hacer de alguna manera?

Gracias

#Joan

Title: Re: New beta 5.5.23betaXX
Post by: orux on November 04, 2014, 06:26:12 PM

~~Quote from: "Jbrio"~~hola, en las ultimas betas ha desaparecido Configuración / GPS donde, por ejemplo podia determinar tiempo o distancia minima para guardar un punto de track asi como la precisión minima para guardar puntos.

Esto, parece que ha desaparecido y para mí era muy util para evitar un track resultante con excesivos puntos y muchos de ellos redundantes.

En la nueva rc1 esto se puede hacer de alguna manera?

Gracias

#Joan

Hola,

Todos los sensores, incluyendo el gps están ahora en configuración--sensores

orux

Title: Re: AW: New beta 5.5.23betaXX
Post by: orux on November 04, 2014, 07:32:12 PM

~~Quote from: "6745th@web.de"~~Open bugs in rc1? Some small bugs are open e.g:

Battery level of my Bluetooth hrm is still not displayed. (Mio alpha)

http://www.oruxmaps.com/foro/viewtopic.php?t=2374

The "tc-2" bug (app crash) ,I can't reproduce anymore. Did you fix that Orux?

Greetings, Thomas

Hi,

battery leven in ANT+, not yet implemented;

tc-2 bug, I think that has been removed.

orux

Title: Re: AW: New beta 5.5.23betaXX
Post by: 6745th@web.de on November 04, 2014, 07:50:15 PM

~~Quote from: "orux"~~
battery leven in ANT+, not yet implemented;

Also not in Bluetooth heart rate monitor?

(Mio alpha)

No big issue, but the user field is available but it only shows zero...

Thanks Thomas

Title: Re: AW: New beta 5.5.23betaXX
Post by: orux on November 04, 2014, 07:53:05 PM

~~Quote from: "6745th@web.de"~~
~~Quote from: "orux"~~
battery leven in ANT+, not yet implemented;

Also not in Bluetooth heart rate monitor?

(Mio alpha)

No big issue, but the user field is available but it only shows zero...

Thanks Thomas

Hi, Thomas,

only available with some sensors, but not yet with BT 4.0 sensors.

I will try to add support in next versions,

orux

Title: Re: New beta 5.5.23betaXX
Post by: 6745th@web.de on November 04, 2014, 08:26:01 PM

Hi Orux,

Thank you for the fast response.

That are all not real problems.

For me you're new version is ready for the market...

Thomas

Title: Re: New beta 5.5.23betaXX
Post by: Jbrio on November 04, 2014, 11:47:11 PM

~~Quote from: "orux"~~
~~Quote from: "Jbrio"~~hola, en las ultimas betas ha desaparecido Configuración / GPS donde, por ejemplo podia determinar tiempo o distancia minima para guardar un punto de track asi como la precisión minima para guardar puntos.

Esto, parece que ha desaparecido y para mí era muy util para evitar un track resultante con excesivos puntos y muchos de ellos redundantes.

En la nueva rc1 esto se puede hacer de alguna manera?

Gracias

#Joan

Hola,

Todos los sensores, incluyendo el gps están ahora en configuración--sensores

orux

Gracias :lol:

Title: Re: New beta 5.5.23betaXX
Post by: panda on November 05, 2014, 05:49:33 PM

Hello Orux,

when creating a new waypoint, it gets automatically the type "left" (or at least the text in field type is "left", the symbol is the green sticker), should be "waypoint" (in market version it works OK).

I don't know how I managed it, but now my waypoint-types are all in english (for new waypoints or edit waypoint), although I have german language setting. (Yesterday it was OK, I switched between german and english language profile)

How do I get back to the german waypoint-types?

Title: Re: New beta 5.5.23betaXX
Post by: orux on November 05, 2014, 06:09:35 PM

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

when creating a new waypoint, it gets automatically the type "left" (or at least the text in field type is "left", the symbol is the green sticker), should be "waypoint" (in market version it works OK).

I don't know how I managed it, but now my waypoint-types are all in english (for new waypoints or edit waypoint), although I have german language setting. (Yesterday it was OK, I switched between german and english language profile)

How do I get back to the german waypoint-types?

Hi,

I think it is working well. Have you changed the locale recently?

orux

Title: Re: New beta 5.5.23betaXX
Post by: panda on November 05, 2014, 07:58:12 PM

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

when creating a new waypoint, it gets automatically the type "left" (or at least the text in field type is "left", the symbol is the green sticker), should be "waypoint" (in market version it works OK).

I don't know how I managed it, but now my waypoint-types are all in english (for new waypoints or edit waypoint), although I have german language setting. (Yesterday it was OK, I switched between german and english language profile)

How do I get back to the german waypoint-types?

Hi,

I think it is working well. Have you changed the locale recently?

orux

What do you mean with "locale"?

Here are the screenshots:

(//%3C/s%3E%3CURL%20url=%22http://up.picr.de/20040360ai.jpg%22%3Ehttp://up.picr.de/20040360ai.jpg%3C/URL%3E%3Ce%3E)

~~(//%3C/s%3E%3CURL%20url=%22http://up.picr.de/20040361bi.jpg%22%3Ehttp://up.picr.de/20040361bi.jpg%3C/URL%3E%3Ce%3E)~~

Title: Re: New beta 5.5.23betaXX
Post by: jonny-blue on November 05, 2014, 09:40:50 PM

~~Quote~~How do I get back to the german waypoint-types?

Hmmm ... for me it's working (in deutsch :D ).

Title: Re: New beta 5.5.23betaXX
Post by: cuconico on November 07, 2014, 02:37:26 PM

Hola, al grano, a ver si alguien me puede ayudar. LA GRABACIÓN DE TRACK SE BLOQUEA.

Se me bloquea el track, deja de marcar el trazado y la flecha se queda en último sitio.

Tengo instaladas dos versiones, esta última beta 5.5.23beta y la oficial 5.5.22. El tema es el siguiente: Arranco la beta e inicio GPS e INICIAR GRABACION, el track empieza a dibujarse sin ningún problema. El problema empieza cuando toco alguna opción de la pantalla, como zoom + o desplazamiento con los dedos. El track deja de dibujarse y el cursor queda en el último sitio, dejo pasar unos minutos y compruebo que sigue sin funcionar se ha quedado bloqueada la grabación del track. A partir de ahí, cierro grabación de Track y cierro la versión beta.

Para comprobar que no es un problema del móvil, inicio la versión oficial 5.5.22 y realizo las mismas operaciones, INICIO GPS, y GRABACIÓN DE TRACK, sin problemas el track se va trazando en la pantalla. Le doy al zoom y toqueteo en la pantalla y el track sigue funcionando y sigue marcando la trayectoria sin ningún problema. Este problema ya lo había detectado en versiones anteriores pero creía que era un posible bug.

Title: Re: New beta 5.5.23betaXX
Post by: orux on November 08, 2014, 06:45:12 PM

~~Quote from: "cuconico"~~Hola, al grano, a ver si alguien me puede ayudar. LA GRABACIÓN DE TRACK SE BLOQUEA.

Se me bloquea el track, deja de marcar el trazado y la flecha se queda en último sitio.

Tengo instaladas dos versiones, esta última beta 5.5.23beta y la oficial 5.5.22. El tema es el siguiente: Arranco la beta e inicio GPS e INICIAR GRABACION, el track empieza a dibujarse sin ningún problema. El problema empieza cuando toco alguna opción de la pantalla, como zoom + o desplazamiento con los dedos. El track deja de dibujarse y el cursor queda en el último sitio, dejo pasar unos minutos y compruebo que sigue sin funcionar se ha quedado bloqueada la grabación del track. A partir de ahí, cierro grabación de Track y cierro la versión beta.

Para comprobar que no es un problema del móvil, inicio la versión oficial 5.5.22 y realizo las mismas operaciones, INICIO GPS, y GRABACIÓN DE TRACK, sin problemas el track se va trazando en la pantalla. Le doy al zoom y toqueteo en la pantalla y el track sigue funcionando y sigue marcando la trayectoria sin ningún problema. Este problema ya lo había detectado en versiones anteriores pero creía que era un posible bug.

Hola,

Alguna pista más:

--marca de tlf y versión de android.

--¿se deja de ver el icono del gps en la barra de android?

orux

Title: Re: New beta 5.5.23betaXX
Post by: orux on November 09, 2014, 03:48:33 PM

Hi,

updated rc2

I hope it's the last.

orux

Title: Re: New beta 5.5.23betaXX
Post by: cuconico on November 09, 2014, 07:54:33 PM

Mi móvil es un ZTE Grand XM, con android 4.0.4, creo que al final es del móvil, porque hoy me se me ha bloqueado con la versión 5.22. Espero renovarlo estas navidades. Gracias Orux.

Title: Re: New beta 5.5.23betaXX
Post by: Maxpil on November 09, 2014, 08:08:00 PM

La altura acumulada sigue teniendo mucho error en la rc1. En la Beta 32 me parecía que iba bastante bien pero ahora el desfase vuelve a ser en torno al +40%.

No sé si hay alguna diferencia entre las 2 versiones en lo referente a la altura acumulada.

Title: Re: New beta 5.5.23betaXX
Post by: eartrumpet on November 09, 2014, 09:49:25 PM

Thanks Orux, hillshading looks much better now.

A different issue:

I just realized that zoom level behavior for mapsforge maps has changed in comparison to earlier betas.

I thinks it's a good idea to have them at equivalent level as tileserver maps so it's easier to switch between those, so I find this a great thing and solves problems discussed earlier.

But I think it's confusing to change the zoom level label to a fake equivalent label (so that it seems that mapsforge maps use the same zl number even if they don't), as under the hood (mapsforge maps/themes) the real zoom level number is still used.

It makes it harder for theme developers, but also for advanced users who have a look at the themes or tag-mapping at openandromaps.

But also with normal users ZL is often discussed, e.g. when they ask when which POI is visible, or which level is best for viewing place names.

So the real zoom level number has a real usage in those cases, so it would be good to have it still visible.

Title: Re: New beta 5.5.23betaXX
Post by: chobkwon on November 10, 2014, 02:16:05 AM

Thank you for your effort new version

The strings in the [Setting-TTS/Sounds] aren't localised.

I checked both the strings and the array files, and I cannot find the corresponding Text.

[Max. Wpt. alarm warnings]

Can you check that the files are current?

http://cfile257.uf.daum.net/image/2308403E54600F752F8F62

(//%3C/s%3E%3CURL%20url=%22http://cfile257.uf.daum.net/image/2308403E54600F752F8F62%22%3E%3CLINK_TEXT%20text=%22http://cfile257.uf.daum.net/image/23084%20...%200F752F8F62%22%3Ehttp://cfile257.uf.daum.net/image/2308403E54600F752F8F62%3C/LINK_TEXT%3E%3C/URL%3E%3Ce%3E)

Title: Re: AW: New beta 5.5.23betaXX
Post by: 6745th@web.de on November 14, 2014, 02:17:14 PM

I played a bit with the mapforge settings.

If I set the factor for the text and symbols to 1.5 text and symbols are bigger as expected.

But when I increase the "scale factor"

Everything becomes smaller.

Is that wanted, or is it a bug?

Text, symbols 1.5, scale 1

(//%3C/s%3E%3CURL%20url=%22http://tapatalk.imageshack.com/v2/14/11/14/851cae593a69af1fd5f1887fa96a376f.jpg%22%3E%3CLINK_TEXT%20text=%22http://tapatalk.imageshack.com/v2/14/11%20...%206a376f.jpg%22%3Ehttp://tapatalk.imageshack.com/v2/14/11/14/851cae593a69af1fd5f1887fa96a376f.jpg%3C/LINK_TEXT%3E%3C/URL%3E%3Ce%3E)

Text and symbols 1.5 scale 2

(//%3C/s%3E%3CURL%20url=%22http://tapatalk.imageshack.com/v2/14/11/14/956f627df266c4e9d1d1082bf055f9f8.jpg%22%3E%3CLINK_TEXT%20text=%22http://tapatalk.imageshack.com/v2/14/11%20...%2055f9f8.jpg%22%3Ehttp://tapatalk.imageshack.com/v2/14/11/14/956f627df266c4e9d1d1082bf055f9f8.jpg%3C/LINK_TEXT%3E%3C/URL%3E%3Ce%3E)

Greetings,

Thomas

Title: Re: New beta 5.5.23betaXX
Post by: Quercus.JB on November 14, 2014, 03:17:13 PM

~~Quote from: "6745th@web.de"~~I played a bit with the mapforge settings.

If I set the factor for the text and symbols to 1.5 text and symbols are bigger as expected.

But when I increase the "scale factor"

Everything becomes smaller.

Is that wanted, or is it a bug?

Text, symbols 1.5, scale 1

(//%3C/s%3E%3CURL%20url=%22http://tapatalk.imageshack.com/v2/14/11/14/851cae593a69af1fd5f1887fa96a376f.jpg%22%3E%3CLINK_TEXT%20text=%22http://tapatalk.imageshack.com/v2/14/11%20...%206a376f.jpg%22%3Ehttp://tapatalk.imageshack.com/v2/14/11/14/851cae593a69af1fd5f1887fa96a376f.jpg%3C/LINK_TEXT%3E%3C/URL%3E%3Ce%3E)

Text and symbols 1.5 scale 2

(//%3C/s%3E%3CURL%20url=%22http://tapatalk.imageshack.com/v2/14/11/14/956f627df266c4e9d1d1082bf055f9f8.jpg%22%3E%3CLINK_TEXT%20text=%22http://tapatalk.imageshack.com/v2/14/11%20...%2055f9f8.jpg%22%3Ehttp://tapatalk.imageshack.com/v2/14/11/14/956f627df266c4e9d1d1082bf055f9f8.jpg%3C/LINK_TEXT%3E%3C/URL%3E%3Ce%3E)

Greetings,

Thomas

+1 ;)

Enviado desde mi LG-E460 mediante Tapatalk

Title: Re: New beta 5.5.23betaXX
Post by: Maki on November 14, 2014, 11:34:46 PM

I can't answer for Jose, but maybe a few notes about Mapsforge can help.

MF 0.3 used a fixed tile size of 256x256px. It meant that on displays with higher density things were actually smaller (because pixels are smaller). But a pixel level, regardless of the device, tiles were identical.

MF 0.4 uses a variable tile size with an automatic scale factor that is proportional to the display density, plus one "user scale factor" that the app can expose to the user or not. This means that at any given zoom level things look the same (except for PNG symbols that are not scaled). That's the theory. In practice, as explained before, Oruxmaps cannot work with a variable tile size, so Jose forced a 512x512 px tile size (which BTW is the natural tile size for 300 dpi devices). The Mapsforge library allows that, but with some problems, because the feature was never really meant for vector maps and weird things happen.

The biggest problem is that even is the tile size is fixed some things are still scaled according to the device screen, namely line widths and labels. So, if you look at the same map at the same ZL on a 233 dpi device and on a 450 one you'll see that text labels are roughly the same size, but lines are shorter and (proportionally) thicker. One possible side effect of this is that some symbols/labels can be killed by the collision detector on some devices and not on others.

So while tiles will have the same size on any device, tile content will vary and there is very little Jose can do about that, other than giving us access to a user scaling parameter that is built in Mapsforge for fine tuning.

In my experience if a theme is built for 300 dpi it sales acceptably well from 233 to 480 without touching anything in the settings except for the symbol scale factor. If one wants to keep things to exact proportions than playing with the other parameters is useful.

I'm not sure why the user scale factor for map works in such a way, but I believe it's a conflict between the fixed tile size and MF scaling mechanism.

MF 0.5 will bring a lot of new stuff that will solve most of the problems we are facing now. For starters there should not be clipped labels at tile boundaries anymore. Then a lot of things will be defined in a flexible way, which should make symbol and labels display more reliable. The scaling problem in itself will remain, however, unless Jose finds a way to modify OM to use variable tile sizes.

Title: Re: AW: New beta 5.5.23betaXX
Post by: orux on November 15, 2014, 01:54:05 PM

~~Quote from: "6745th@web.de"~~I played a bit with the mapforge settings.

If I set the factor for the text and symbols to 1.5 text and symbols are bigger as expected.

But when I increase the "scale factor"

Everything becomes smaller.

Is that wanted, or is it a bug?

Greetings,

Thomas

Hi, Thomas,

It is correct.

The overall scale factor affects the scale factor of the text.

orux

Title: Re: New beta 5.5.23betaXX
Post by: orux on November 15, 2014, 01:55:15 PM

~~Quote from: "Maki"~~I can't answer for Jose, but maybe a few notes about Mapsforge can help.

MF 0.3 used a fixed tile size of 256x256px. It meant that on displays with higher density things were actually smaller (because pixels are smaller). But a pixel level, regardless of the device, tiles were identical.

MF 0.4 uses a variable tile size with an automatic scale factor that is proportional to the display density, plus one "user scale factor" that the app can expose to the user or not. This means that at any given zoom level things look the same (except for PNG symbols that are not scaled). That's the theory. In practice, as explained before, Oruxmaps cannot work with a variable tile size, so Jose forced a 512x512 px tile size (which BTW is the natural tile size for 300 dpi devices). The Mapsforge library allows that, but with some problems, because the feature was never really meant for vector maps and weird things happen.

The biggest problem is that even is the tile size is fixed some things are still scaled according to the device screen, namely line widths and labels. So, if you look at the same map at the same ZL on a 233 dpi device and on a 450 one you'll see that text labels are roughly the same size, but lines are shorter and (proportionally) thicker. One possible side effect of this is that some symbols/labels can be killed by the collision detector on some devices and not on others.

So while tiles will have the same size on any device, tile content will vary and there is very little Jose can do about that, other than giving us access to a user scaling parameter that is built in Mapsforge for fine tuning.

In my experience if a theme is built for 300 dpi it sales acceptably well from 233 to 480 without touching anything in the settings except for the symbol scale factor. If one wants to keep things to exact proportions than playing with the other parameters is useful.

I'm not sure why the user scale factor for map works in such a way, but I believe it's a conflict between the fixed tile size and MF scaling mechanism.

MF 0.5 will bring a lot of new stuff that will solve most of the problems we are facing now. For starters there should not be clipped labels at tile boundaries anymore. Then a lot of things will be defined in a flexible way, which should make symbol and labels display more reliable. The scaling problem in itself will remain, however, unless Jose finds a way to modify OM to use variable tile sizes.

Hi, Maki;

you are right.

In the next version we will play with the 0.5 mapsforge version.

orux

Title: Re: New beta 5.5.23betaXX
Post by: mntr86 on November 15, 2014, 01:55:17 PM

OruxMaps, when will be released the next version on play Store? Thanks

Title: Re: New beta 5.5.23betaXX
Post by: Maki on November 16, 2014, 08:50:07 PM

~~Quote from: "eartrumpet"~~
I just realized that zoom level behavior for mapsforge maps has changed in comparison to earlier betas.

[...]

So the real zoom level number has a real usage in those cases, so it would be good to have it still visible.

+1

In addition, I'm seeing an intermittent bug. It's not new, but previously I thought it was just my impression; today I've seen it clearly. Unfortunately I cannot reproduce it at will; fortunately it's not frequent. For the same area I have three maps installed, a raster one in mbtiles and two mapsforge. When switching from the raster to a vector one the map scale is kept correctly (OM internally switches to the previous zoom level). When I then switch to the other vector map there is a +1 ZL jump.

Title: Re: New beta 5.5.23betaXX
Post by: 6745th@web.de on November 17, 2014, 06:03:41 PM

I just installed Orux maps 6.0donation from the play store.

Congratulation for releasing!!

Title: Re: New beta 5.5.23betaXX
Post by: orux on November 17, 2014, 07:25:41 PM

~~Quote from: "6745th@web.de"~~I just installed Orux maps 6.0donation from the play store.

Congratulation for releasing!!

Hi,

Yes, 6.0.0 is available in google play; I hope it doesn't have too much 'last minute' bugs :P

orux

Title: Re: New beta 5.5.23betaXX
Post by: oleolafson on November 18, 2014, 12:38:46 PM

Is it possible to import the settings and profiles from beta to final?

I just tested the 6.0.0 - the bug with the echoed notification (//http) still persists. Any idea on this issue?

Title: Re: New beta 5.5.23betaXX
Post by: orux on November 20, 2014, 08:14:02 PM

~~Quote from: "oleolafson"~~Is it possible to import the settings and profiles from beta to final?

I just tested the 6.0.0 - the bug with the echoed notification (//http) still persists. Any idea on this issue?

Hi,

Yes, you can use the beta configuration. Create a new profile, in the beta version with your settings. Open the new version, in configuration--profiles restore the saved profiles. Then you can select the previously saved profile from beta version.

About the double notification. It is due to using two or more versions, (free, donate or beta)

There is a new beta-->//http://www.oruxmaps.com/foro/viewtopic.php?f=4&t=2475

orux

Title: Re: New beta 5.5.23betaXX
Post by: oleolafson on November 21, 2014, 01:59:35 PM

Hi and thanks for your answer!

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

Yes, you can use the beta configuration. Create a new profile, in the beta version with your settings. Open the new version, in configuration--profiles restore the saved profiles. Then you can select the previously saved profile from beta version.

But the final doesn't "see" the profiles created in beta. Nevermind, I set up the profile manually.

~~Quote from: "orux"~~
About the double notification. It is due to using two or more versions, (free, donate or beta)

That can't be the reason, that issue also exists even tho there is - and always was - just one version installed.

Update: I did a tour last weekend and the notification for "GPS Signal lost" is played correctly, still the notification for "GPS Fix" is echoed.

Title: Re: New beta 5.5.23betaXX
Post by: eartrumpet on December 05, 2014, 10:09:19 AM

~~Quote from: "orux"~~

I just upgraded the beta, including a scale factor setting for mapsforge symbols. I have to try if properly scale the svg icons.

orux

I just realized that only PNGs with <symbol ...> are scaled, but not <lineSymbol ...>. Those should be included as well for proper scaling.

Best regards,

Tobias

OruxMaps

Uncategorized Boards => BETAS => Topic started by: orux on June 14, 2014, 12:38:00 PM