FAKE_PACKAGE_SIGNATURE
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
I installed aosp but I hadn't see this:
https://github.com/microg/android_packages_apps_GmsCore/wiki/Signature-Spoofing
so I installed xposed module,
today I read it and I switched on the two relevant permissions (for gms and play store) and
I uninstalled the xposed module and
I'm getting the following errors after boot:
`11-25 16:10:53.847 W/PackageManager(1568): Not granting permission android.permission.FAKE_PACKAGE_SIGNATURE to package com.google.android.gms because it was previously installed without
11-25 16:11:41.491 I/InstalledAppProvider(4906): selectNotSystemSignature: systemSignature == null, querying for it
11-25 16:11:41.523 I/InstalledAppProvider(4906): excluding InstalledApps signed by system signatures
`
notifications and play store is working normally,
will I have problems?
I'm running latest offlicial microg
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start with the reported PackageManager and InstalledAppProvider log messages and compare them with the linked Signature Spoofing wiki page. No source file, test, or entry point is named; done would be determining whether the FAKE_PACKAGE_SIGNATURE warning causes a functional problem for microG, or documenting the required remediation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100