microG app hidden (other launchers do show this app)
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
This issue has not been assessed yet.
Description
Checklist
- I can reproduce the bug with the latest version given here.
- I made sure that there are no existing issues - open or closed - to which I could contribute my information.
- I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
- I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
- I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
- This issue contains only one bug.
- I have read and understood the contribution guidelines.
Affected app version
1.0.1 (f-droid build)
Affected Android/Custom ROM version
Android 12
Affected device model
Motorola Edge 30 Neo
How did you install the app?
F-Droid
Steps to reproduce the bug
I have installed microG as a normal (non-system) app. The microG app functions normally (its self-check passes).
However, Fossify Launcher does not show this app. Perhaps this is related to its signature spoofing (which I have patched into my ROM)? As in, perhaps Fossify Launcher mistakes it for the Google Services Framework (GSF) and therefore decides to hide the app? Not sure, I haven't looked into the Fossify Launcher source code.
Expected behavior
Other launchers however, such as Motorola's own launcher, do show the microG app.
If I wish to use Fossify Launcher as my primary launcher, I have to go to Apps > microG > Open instead if I want to open the microG app, which is a bit cumbersome.
It would be useful if Fossify Launcher would show the microG app.
Actual behavior
The microG app is not shown when using Fossify Launcher.
Screenshots/Screen recordings
No response
Additional information
No response
- Dominant language
- Kotlin
- Stars
- 703
- Forks
- 85
- Avg merge
- 4d 39m
- Merged PRs (30d)
- 7
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from FossifyOrg/Launcher
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
FossifyOrg/Launcher#453 ·
Maintainers usually reply within 3 days
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
FossifyOrg/Launcher#447 ·
Maintainers usually reply within 3 days
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
FossifyOrg/Launcher#446 ·
Maintainers usually reply within 3 days
-
feature request needs triage
Difficulty 3/5 1-2 days Newbie friendliness 40/100
FossifyOrg/Launcher#461 ·
Maintainers usually reply within 3 days
-
bug needs triage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
FossifyOrg/Launcher#456 ·
Maintainers usually reply within 3 days
All issues in FossifyOrg/Launcher
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
partiql/partiql-lang-kotlin#1972 ·
-
afk-ok area:data-quality importer size:S
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
enorm-labs/event-junkie#3027 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
libre-tube/LibreTube#8854 ·
Maintainers usually reply within 1 day