pie: signature spoofing patch 2.0
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
If you like the idea of enriching your patch with a global setting for signature spoofing I can create a PR if you like:
https://github.com/steadfasterX/android_signature_spoofing
The readme describes everything in detail.
- 01-android_frameworks_base-P_origin.patch = your original patch
- 02-android_frameworks_base-P_enhanced.patch = extending the origin
- 03-packages_apps_Settings-P.patch = main part for developer option handling
When applied in that order it should succeed (tested on pie only)
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 linked README and review 01-android_frameworks_base-P_origin.patch, 02-android_frameworks_base-P_enhanced.patch, and 03-packages_apps_Settings-P.patch. Apply the patches in that order against Android Pie and verify that the global signature-spoofing setting and developer-option handling described in the issue work as intended.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile-dev, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100