New app: SnapKey Map
Abstract for new app inclusion
Please introduce the functions and usage of your app in summary, and also attach some screenshots.
SnapKey Map remaps the Snap Key on the Oppo Find X9 (also reported working on the X9 Pro, X9 Ultra, X9s, X9s Pro and OnePlus 15R). You assign one action each to press, double press and press and hold: flashlight, ringer presets, Do Not Disturb, screenshot, lock screen, media controls, opening an app, a link or an app shortcut, and more.
ColorOS does not pass the Snap Key to apps, so the app detects it from the system log. The user grants READ_LOGS once with Shizuku or ADB. With Shizuku running, the app also reads raw key events through Shizuku for more precise detection. An accessibility service runs actions such as screenshot and lock and opens apps from the background. It does not read screen content. The app has no internet permission, no ads and no tracking.
Screenshots are in the upstream Fastlane folder: https://github.com/heykay-47/SnapKeyMap/tree/main/fastlane/metadata/android/en-US/images/phoneScreenshots
Please elaborate why you wrote this app. Please highlight the unique functions it provides over other similar apps in F-Droid.
Oppo's own Snap Key settings offer a short, fixed list of actions and a single gesture. I don't know of another app on F-Droid that can remap this key, because it never reaches the normal key event APIs.
Notes for reviewers
- I am the author.
- Reproducible build with the developer signature (
Binaries+AllowedAPKSigningKeys). Users who installed from GitHub Releases can switch to F-Droid without uninstalling, which matters because uninstalling drops the READ_LOGS grant. - Upstream CI already rebuilds each release without signing secrets, removes signing config with
fdroidserver.common.remove_signing_keys, copies the signature with apksigcopier and requires a byte-identical match before publishing. The v1.1.0 run passed. - The recipe installs openjdk-17 from bookworm because upstream builds with JDK 17.
fdroid lintpasses locally with fdroidserver 2.4.5. The recipe targets v1.2.0 (10200).- F-Droid verification for v1.2.0 passed in pipeline #3011159377, and F-Droid's build reproduced the signed release APK.
Checklist
Policy
- The app complies with the inclusion criteria.
- The original app author has been notified (and does not oppose the inclusion). If you are not the author, please paste the link of the reply from the author.
- The upstream app source code repo contains the app metadata in a Fastlane or Triple-T folder structure. The summary and description must be included and images, icon, and changelog should also be provided for better user experience. The
en-USlocale must be included.
Docs
- Please read the guide first if this is your first contribution.
- Please make sure your metadata follows the best practice in our templates.
- Please read the Build Metadata Reference and make sure your metadata is valid.
- Please read the Quick Start Guide.
Merge Request Setup
- The title of this merge request should follow "New app: app name" format.
- Please make sure your fdroiddata fork is public and your branch is not protected. See https://docs.gitlab.com/user/project/repository/branches/protected/.
- Please read our Git guide if you don't know how to rebase your branch. Don't rebase your branch if there is no conflict.
- All related fdroiddata and RFP issues have been referenced in this merge request
- Please only submit one app in one MR.
Metadata
- Metadata must be put in
metadata/<applicationId>.yml. - Metadata must be a valid YAML file.
- Metadata must use LF as line ending.
- Don't add summary/description/changelog/images or anything that should be provided in upstream repo. Please check the Changes tab to make sure there is no other unrelated files added in the MR.
- Releases are tagged and auto update is enabled unless there is a special reason.
- There is an issue tracker and contact info of the author so that we can report bugs and contact the author.
- An AuthorName must be added. It doesn't need to be the real name.
- External repos are added as git submodules instead of srclibs. (None used.) You can update git submodules without opening an MR in this repo and the submodule is covered by our scanner.
- Enable Reproducible Builds. We'll use your signature for improved security/reliability, also allowing users to switch between different channels. Do note that if you don't enable reproducible build then the apk will be signed with our key so you can't enable it later. If you can't enable this, please add the reasons here.
- Setup abi split if the APK is large and the splitted ones can be much smaller. (No native code, single APK.)
- Only the latest versions should be kept in the metadata before it's merged. If you update the metadata, please replace the old versions with the new ones.
- Don't add any disabled versions in the metadata.
- The
commitfield should be the full hash. Please don't use tag or branch in commit.
Pipeline
- All pipelines should pass.
- All warnings and errors in the Reports tab should be fixed or explained.
- F-Droid CI runners are under GitLab's FOSS program, so there's no need for you to pay for any CI time. If Gitlab starts asking for phone numbers or credit cards don't submit anything, just leave a note in the MR so we know we need to trigger the CI.