microg / microg/UnifiedNlp

mock GPS, bluetooth GNSS receivers

Open
#52 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
1.1k
Forks
221
PR merge metrics
No merged PRs in 30d

Description

I have found BT GNSS receivers both use less battery than phone GPS, and it overcomes wonky compass in phones (like samsung note4 or s5 (which often have waze showing me driving backwards on the freeway)).

The various free BT android apps use mock location (atop enabled gps). I have not yet encountered a navigation app that complains. Many apps are happy even if the phone gps is not enabled (toggled on).

Will your app collect position information this way? Allowing wifi correlation? or whatever BackEnds or lookup apps are installed?

with- or without android device gps toggled on?
##

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing UnifiedNlp's Android location-provider and plugin behavior, then compare it with the Bluetooth GNSS and mock-location scenarios described here. Determine whether external GNSS positions, Wi-Fi correlation, installed backends, and the device GPS toggle are supported or need a defined feature scope; document the expected behavior before implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.