microg / microg/GmsCore

[Feature request] Create new diag tab with some useful features

Open
#1,070 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

You even could make it active by tapping 7 times on microG version (to make it less dangerous and less clutter).

The Functions:

  1. Check which location provider packages are currently used. (is this even possible without xposed?)

    • com.android.location.fused — android's default flp
    • com.google.android.gms — microg/unifiednlp
    • com.qualcomm.location — qualcomm's location service with IZat, known for leaking user's location and IP — should be disabled for correct working unifiednlp! (pm disable com.qualcomm.location)

    also these can be configured in framework's strings.xml (package names) and bools.xml (enable or disable location package overlay), but we could have more convenient way to at least check these values.

    • could be anything for other vendors…
  1. Button(s) to toggle (enable|disable) correct permissions, such as

    • pm grant com.android.vending android.permission.FAKE_PACKAGE_SIGNATURE

    • pm grant com.google.android.gms android.permission.ACCESS_FINE_LOCATION

    • pm grant com.google.android.gms android.permission.ACCESS_COARSE_LOCATION

    • pm revoke com.qualcomm.location android.permission.ACCESS_FINE_LOCATION

    • pm revoke com.qualcomm.location android.permission.ACCESS_COARSE_LOCATION

    • pm disable com.qualcomm.location

    • pm enable com.qualcomm.location

    • etc…

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

No source files or tests are named. Start by locating the existing Android tabs and the diagnostic UI, then inspect framework strings.xml and bools.xml for the package and overlay values mentioned. Define the supported provider and permission states before implementing; done means the tab can show those values and safely expose the requested toggles.

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
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.