nextcloud / nextcloud/talk-android

Location sharing is (possibly) sent too much inaccurately/imprecise

Open
#3,962 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage bug
Dominant language
Kotlin
Stars
739
Forks
321
Avg merge
14h 59m
Merged PRs (30d)
151

Description

Steps to reproduce
  1. Check if location (location or "accurated" location) is enable on android (stay on open sky place if it's possible)
  2. Open Android Talk
  3. Open conversation
  4. Touch on clip
  5. Touch on "Share Location"
  6. Touch (directly) on "Share current location". (at the bottom of the screen)
Expected behaviour

The current location (with no more than 20 meters of precision) has to be shared on the conversation.

Actual behaviour

Sometimes, the current location sent is too much imprecise. ( I've suffered mistakes of more than 500m)

It could be an human error, by moving the center in the maps windows/share location window, but if this is the problem (that I'm sure that it's not always), could be a helper, or an approach to avoid the mistake, openning the map of share location with more zoom to the current location and/or show the aproximated current error (the active blue circle).

Device brand and model

All phones

Android version

14

Nextcloud Talk app version

19.0.1

Nextcloud server version

28.0.5

Talk version

18.0.7

Custom Signaling server configured

None

Custom TURN server configured

Yes

Custom STUN server configured

Yes

Android logs

No response

Server log

No response

Additional information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the Android Talk flow through a conversation's clip button, Share Location, and Share current location, preferably on Android 14 in an open-sky area. Investigate why the shared position can differ by more than 500 m and determine whether the map's initial zoom or visible accuracy indicator needs changing. Done means the current location is shared within the reported precision requirement without relying on manual map repositioning.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.