microg / microg/GmsCore

Passive beacon submission to beaconDB

Open
#3,518 0 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Java
Stars
14.6k
Forks
3.2k
Avg merge
12d 11h
Merged PRs (30d)
4

Description

**Is your feature request related to a problem? Please describe.**
Google Play Services automatically submits nearby beacons to Google's database. A similar option in microG would help beaconDB greatly.

**Describe the solution you'd like**
An optional toggle under microG's location settings to passively (as in when other apps request location data) submit beacon data to the configured Ichnaea-compatible provider (which is beaconDB by default) would help beaconDB's dataset greatly.

Active beacon collecting has complex logic, taking movement and device-specific quirks into account but passive beacon collecting would be easier to implement.

**Describe alternatives you've considered**
A descriptive text under location settings, informing the user about beaconDB accepting submissions via beacon collector apps would be nice too.

**Additional context**
https://beacondb.net
https://support.google.com/maps/answer/1725632

Contributor guide

No contributing guide indexed for this repository

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

Start by locating microG's location settings and the passive location-request path, then trace how the configured Ichnaea-compatible provider is used. Define the optional beacon submission toggle and its user-facing explanation, and verify that passive beacon data reaches the configured provider without requiring active collection.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.