Messages

Hi Orux, the newest version of Oruxmaps has problem with the track recording.

The problem is connected with this function:
Tracks/Routes -> Automatic Segment/Lap creation -> Automatic Segment. No movement = 30 sec. by default

After the no movement period is expired and there is movement, the record won't restart automatically.
I tried everything and the only way to restart the recording is to restart the app.
Please, can you fix this bug.

Best Regards,
Zdravko

Hi Orux, i tested the sensor and everything works perfect!
Thank you for your efforts!

Please, i have a suggestion. This sensor measures the temperature with precision of 1 degree.
Can you remove the extra precision ".00" from the display and leave it integer only for this sensor type "nRF51822".

I have "Tempo Disc" temperature sensor, which has precision of roughly "0.1" degree celsius.
Sometimes Oruxmaps displays for sample "21.10", but other times it displays "24.19".
It needs to be rounded to precision of "0.1" degrees (if the hundreds are more than 0.05, then round to the next number - 24.19 -> 24.2).

Best Regards,
Zdravko

This is great, i will try it and will report if it works!
Thank you very much!!!

Best Regards,
Zdravko

Hi Orux, thank you for the reply!

In OruxMaps 8.x manual, the link for "Barometer Thermometer BT 4.0 nRF5xxxx" is this:
https://es.aliexpress.com/item/32808111676.html
When i look closer at the image of the board i see the same components as mine and the same chip number N51802!

My device is this (check the overvew):
https://www.aliexpress.com/item/4000123555503.html

The most suitable software that i used is this:
https://play.google.com/store/apps/details?id=com.punchthrough.lightblueexplorer

I uploaded screenshots with descriptions in this ZIP file:
https://deep-z.net/LightBlue.zip

Please, check it and tell me if you need more information, i am ready to send you everything that you need.

Best Regards,
Zdravko

Hello Orux,
Recently i bought NRF51802 Bluetooth 4.0 sensor with these features:
- Bosch BMP180 temperature and pressure sensor chip
- Ambient light proximity sensor chip AP3216
- 3-axis acceleration 3-axis gyroscope chip MPU6050

I read in the manual that nRF5xxxx series sensors should work with Oruxmaps:

Barometer Thermometer BT 4.0 nRF5xxxx
It is an external BT 4.0 sensor, which may contain Barometer, Thermometer.

When i go to Oruxmaps options and do a scan, the app finds and adds the sensor's address.
Later when i start the sensor from "Sensors" menu, it doesn't work.
After some seconds it displays that connection is lost. I do a reset of the sensor and trying again, but no connection.
I bought the sensor from here: https://www.aliexpress.com/item/4000123555503.html

I tested the module with special apps which support these chip series. They connect and display the data from all sensors in the module.
Please, if it's possible to fix this issue.

Thank you in advance!

I also noticed the change and it's very annoying! Orux, please change the app how it was before - with automatic unlock after wake.

Hello orux i use your great app since long time! It's really unique, there is no other with so many functions and so great accuracy!

Many cyclists like to read the current slope, but it has some fixed refresh interval.
For someone it's very slow, other would like to be more precise.

Please, it would be great if you put "Slope calculation method" - auto and manual:

- "Auto" (selected accuracy in the cost of the period) - user can select the accuracy from 0.1 to 1.
> Here the period depends on the time which the app needs to calculate the slope until it reaches the desired accuracy (depending on the collected data from the elevation and the distance).

- "Manual" (selected period in the cost of accuracy) - user can enter the period in seconds from 1s to 300s.
> Here the accuracy depends on the period which is given to calculate the slope: more period - more accuracy, less period - less acuracy.

Sample menu:

Slope calculation method:
-> Choice between Auto and Manual

Slope calculation accuracy (used in auto):
-> Choice between 0.1, 0.2, 0.5, 1

Slope calculation period (used in manual):
-> Enter value from 1s to 300s

Hello, there is a bug when showing Min or Max Altitude in v.8.5.1 GP
When i start recording of a new track, the first values of min and max altitudes are very big numbers.
When i start to move, after some time the big numbers change to real numbers.
I suppose these are 31 bit positive and negative limits. It's shown in the photo below, marked with red rectangle:

Hello, i need help about the new "Altitude algorithm" setting in v.8.5.1 GP.
It's in Global settings -> Tracks/Routes and it has 2 options: "Point to Point" and "Threshold difference".
Please, can you explain to me what is the function of this setting.