Compass/Orientation failure.

[P Wat]

Is anyone else experiencing compass-related failure?
I'm running Osmand+ 2.2.4 with Android 5.1 on MotoG series 1.
GPS is functioning very accurately as usual but compass-related features are no-longer functioning at all. I.e. With map display set to "Map; Orientation to compass", the map does not respond to rotation of the device, and the blue (direction of viewing) fan does not respond.
Is this caused by a change to Osmand, or my own equipment/settings?
Any ideas?
Paul W

[Poutnik]

Try to test your device with free version of LocusMap,
it has explicit compass screen, controlled by GPS or magnetic sensors.
It should be easy to determine if issue is the device or OSMAnd.

Also try older OSMAnd versions a/o recalibrating the sensors.

Dne 09/01/2016 v 12:33 P Wat napsal(a):

--
You received this message because you are subscribed to the Google Groups "Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send an email to osmand+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[P Wat]

Hi Poutnik.  Thanks for your suggestion.

LocusMap = 19Mb.

“AR Bearing + Baseplate Compass” = 1.6Mb.

ARBC had worked well as a compass, but I un-installed it a few weeks/months back for space reasons.

I've now re-installed ARBC in the last few minutes, and it works OK.

It responds instantly to rotation of device, and to movement of a nearby magnet.

I therefore deduce my device's magnetometer is operating effectively.

When I switch between ARBC & Osmand, ARBC reacts immediately to any subsequent changes of orientation.

Osmand only reacts to the latest ARBC reading.

Osmand orientation tries to respond to subsequent turns but is very "limp".

I thus deduce that Osmand compass feature is not operating correctly.

Is this likely to be an OSMAND anomaly?

Ideas?

[Poutnik]

Is possible the orientation filter in OSMAnd is too strong ?

[Poutnik]

If I had to choose if to keep OSMAnd or LocusMap........

Dne 09/01/2016 v 13:32 P Wat napsal(a):

[P Wat]

Keep trying - You might convince me! :)

[P Wat]

Is the Osmand orientation filter user-adjustable (without re-writing code)?
PW

[Poutnik]

Only ON/OFF,  AFAIK, in contrary to LocusMap.

Dne 09/01/2016 v 13:47 P Wat napsal(a):

[P Wat]

Hmmm:-
Osmand = 72Mb, (plus a few Kb extra for Nautical and Contour add-ons)
Locus = 19Mb.  Tempting on size basis.
Does Locus do Nautical and Contours?
If so what size are the files?
(Maybe it may seem ungrateful for the undoubted effort put into OsmAnd, to use this forum to discuss possibly heading for the door)
PW

[Poutnik]

OSMAnd is primarily focused on car navigation, LocusMap on outdoor, but their usage and feature largely overlap.

If one uses OpenAndroMaps vexctor maps, there are contours already included.
Generally, LM as outdoor map SW is better suited for dealing with elevations,
e.g. you can route elevation profiles, or interactive elevation for map points.

OTOH, aside of onlinte routing, it does not have its own intenal offline routing,
using 3rd party ones like Brouter for bike and hiking, or Graphhopper for cars.

I am not aware about Nautical features,
but I am not an advanced LM user yet.

For more, best if googled at site:locusmap.eu

Dne 09/01/2016 v 14:17 P Wat napsal(a):

[Max1234Ita]

You can try re-calibrating the compass in your cell, i.e. with GPS Status & Toolbox.
It has a specific procedure (activate calibrate mode, then turn the phone around the 3 axes), which should realign the sensor and make it point in the correct direction again.

Regards,
Max - Italy

[CJTmmr]

Maybe slightly off-topic..

On my device (Samsung Galaxy Camera 2, EK-GC200, 4.3) in the compass-mode the map is always 90% off.

The North on the map is heading to the East.

Are there more devices with this problem.

A lot of compass-apps have the same problem on my Galaxy Camera 2.

But some others are okay....it seems to be a difficult issue

Kees-Jan

[michael....@gmail.com]

I tested it with my 1st Gen MotoG (Android 5.1) and Osmand+ 2.1.1 and noticed the exact same issue. Unfortunately I can't tell when it stopped working, but it worked with Osmand+ 1.9.5 on Android 4.4.4.

So I downloaded LocusMap and here viewing direction and card orientation work perfectly, so it is probably an issue within the combination of Osmand and MotoG (I assume it works for others since I didn't find any complaints from other smartphone users.)

Ciao
  Mike

[P Wat]

Mike - Thank you for corroborating that Compass worked OK with earlier OsmAnd version/s on MotoG V1..
So -
Evidence is that the current OsmAnd version has lost compass functionality.  (Not clear what devices/Os/Versions may be affected)
Compass is definitely not working on Osmand+ 2.2.4 with Android 5.1 on MotoG series 1.

Do the Devs read theses posts?  -  If not could someone please alert them?
Devs - Please could you restore compass function to earlier state?

Thanks
Paul W
Running Osmand+ 2.2.4 with Android 5.1 on MotoG series 1.

[P Wat]

Devs - Please could you restore compass function to earlier state?  (See posts above).

Do the Devs read these posts?  -  If not, could someone please tell me how to alert them?
Thanks
Paul W

[P Wat]

Could someone please tell me how to alert the Developers to this issue?
Thanks
Paul W

[Nelson A. de Oliveira]

On Fri, Jan 15, 2016 at 12:08 PM, P Wat <pwat...@googlemail.com> wrote:
> Could someone please tell me how to alert the Developers to this issue?

Report the issue at https://github.com/osmandapp/Osmand/issues

[P Wat]

Right.  Looks like I have to sign up for an account.
Thanks.
PW

[Max1234Ita]

It looks like issue #2131 is similar tho this one.
Better check already opened tickets first, in order to avoid submitting duplicates ;)

Regards,
Max - Italy


https://github.com/osmandapp/Osmand/issues/2131

342

[P Wat]

Interesting point (Max - Italy).  However, "90 degrees error" implies that Osmand responds to the magnetometer data, albeit with an error of 90 degrees.
What we are experiencing is no Osmand response at all, in "Map; Orientation to compass", despite evidence that the mag' is functioning accurately - proved with a compass app.
Anyway, I can navigate successfully without it, normally preferring "North is Up" mode, so will quietly await developments.
Paul W.

[Márcio Vinícius Pinheiro]

I had the same issue, someone else posted it on github…

Solution:
Activate the Osmand Development add-on and then on its configurations turn on "use magnetic sensor".

[P Wat]

>Márcio.  "Map orientation to Compass" now works!  Thank you.
For the benefit of others, a full sequence seems to be:-
Menu, Plugins, OsmAnd development. Enable, Settings tab (in Osmand Development), Select "Use magnetic sensor". Turn off OsmAnd development (optional). Go back to map. Select Map orientation to Compass.  Smile!
Only briefly tested but seems good.

The above MIGHT be a solution for people who find their orientation is 90 degrees (etc) out?

Thank you
Paul W.

[Márcio Vinícius Pinheiro]

There's an issue about 90° orientation stuck on github <https://github.com/osmandapp/Osmand/issues/2131> and it seems there's something related to the way samsung devices report x-y-z axis. They seem to work on a new Dev option for devices with this behavior.