new beta 7.1.7betaX [closed]

[6745th@web.de]

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

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

MyTourbook has a function to recalculate the altitude values.



But strange:

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



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



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



I will report,

Thomas

[6745th@web.de]

Hi Orux,

i get answer from the Mytourbook Developer.



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

once inside the session part, once outside the session.

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

the zeros overwrite the session part.

in fitfiles from Garmin the order is vice versa.



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



https://sourceforge.net/p/mytourbook/bugs/_discuss/thread/050d183f/32b6/attachment/mt-fit-log-marked.png">



https://sourceforge.net/p/mytourbook/bugs/_discuss/thread/050d183f/32b6/attachment/mt-fit.png">



Garmin vs orux fitfile parsing:

Code Select Expand

1507721654154 [FitDataReader]   C:UsersWolfgangSchrammDesktopfit-test2017-10-03 1159__20171003_1159.fit

Timestamp Num   Name                                          Value Units

2017-10-11 13:34:14.001'925 [SessionMesgListenerImpl]   onMesg:com.garmin.fit.SessionMesg@449aa1e5
2017-10-11 13:34:14.002'190 [RecordMesgListenerImpl]    onMesg:com.garmin.fit.RecordMesg@67ed77dd
2017-10-11 13:34:14.002'275 [RecordMesgListenerImpl]    onMesg:com.garmin.fit.RecordMesg@13eeef39

....

2017-10-11 13:34:14.085'464 [RecordMesgListenerImpl]    onMesg:com.garmin.fit.RecordMesg@c26b70ae
2017-10-11 13:34:14.085'515 [RecordMesgListenerImpl]    onMesg:com.garmin.fit.RecordMesg@b9825252

1507721654528 [FitDataReader]   C:UsersWolfgangSchrammDesktopfit-test2017-10-05-13-41-19.fit

Timestamp Num   Name                                          Value Units

2017-10-11 13:34:14.378'441 [RecordMesgListenerImpl]    onMesg:com.garmin.fit.RecordMesg@504831b5
2017-10-11 13:34:14.378'622 [RecordMesgListenerImpl]    onMesg:com.garmin.fit.RecordMesg@d99275fe

...

2017-10-11 13:34:15.004'341 [RecordMesgListenerImpl]    onMesg:com.garmin.fit.RecordMesg@55d73df5
2017-10-11 13:34:15.004'485 [RecordMesgListenerImpl]    onMesg:com.garmin.fit.RecordMesg@97418e26
2017-10-11 13:34:15.005'772 [SessionMesgListenerImpl]   onMesg:com.garmin.fit.SessionMesg@d539c66c

[ThomasSc]

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

[Maki]

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



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



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

[orux]

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



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



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

Hello;



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

exit-> exit the tutorial

got it-> go to the next tutorial screen



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



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



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



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



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





orux

[orux]

New beta version uploaded,





orux

[matt]

Hi,



regarding

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

7.1.7 beta8:

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

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



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



Matt

[skibum218]

Hi,



regarding

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

7.1.7 beta8:

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

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



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



Matt

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





Sent from my SM-G920V using Tapatalk

[matt]

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

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

Nothing about transparent dashboard.

[6745th@web.de]

settings-->user interface-->colors



uncheck "Dashboard colors"

Dashboard  background colors to "customized"

set "custom Background " to a transparent color



correct?

[orux]

settings-->user interface-->colors



uncheck "Dashboard colors"

Dashboard  background colors to "customized"

set "custom Background " to a transparent color



correct?

thanks,



yes,





orux

[6745th@web.de]

fit file export looks also good now.



thanks,

Thomas

[mntr86]

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



Thank you

[Maki]

exit-> exit the tutorial

got it-> go to the next tutorial screen

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

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

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



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

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

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



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

[orux]

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

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

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



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

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

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

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



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

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

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





orux