Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Android N: Map circles not placed correct

See original GitHub issue

Reported by a user using Android N, preview 2 He wrote, that it working normal until recent udpate 2016.04.12.

System information:

--- System information ---
Device: Nexus 6 (shamu, google)
Android version: N
Android build: NPC91K
Cgeo version: 2016.04.12
Google Play services: enabled
Low power mode: inactive
Compass capabilities: yes
Rotation vector sensor: present
Orientation sensor: present
Magnetometer & Accelerometer sensor: present
Direction sensor used: rotation vector
Hide own/found: false
Map strategy: auto
HW acceleration: enabled (default state)
System language: en_US
Geocaching sites enabled:
- geocaching.com: logged in (Login OK) / BASIC
- opencaching.us: logged in (Login OK)
Installed cgeo plugins: calendar
--- End of system information ---

Other comments and remarks:

androidn1 androidn2

Issue Analytics

State:
Created 7 years ago
Comments:7 (6 by maintainers)

Top GitHub Comments

1reaction

mattdbrcommented, Apr 23, 2016

Hmm your comment decided to make me dig around a bit more and I can reproduce.

Looks to be a very serious bug. On 24 Apr 2016 02:54, “notspecified” notifications@github.com wrote:

I can confirm the Problem! Device is Pixel C with Android N.

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/cgeo/cgeo/issues/5676#issuecomment-213781916

0reactions

Lineflyercommented, Mar 14, 2017

Meanwhile my Samsung S7 received Android N upgrade and I cannot reproduce. Furthermore no other reports on Play. Closing.