I made an open-source Android project called Sorry Google that provides APK stubs for replacing a few Google system services that some users may not want on their devices.

The project currently targets:

- "com.google.android.safetycore" — Android System SafetyCore

- "com.google.android.contactkeys" — Android System Key Verifier

- "com.google.android.verifier" — Android Developer Verifier

What are these actually used for?

Android System SafetyCore

SafetyCore is Google's on-device safety/classification service. It provides infrastructure for features such as Sensitive Content Warnings in Google Messages. Google says the classification is performed locally on the device rather than sending the classified content or results to Google's servers.

Android System Key Verifier

Key Verifier provides a standardized system service for verifying public encryption keys used by E2EE messaging applications. It can be used to verify contacts through QR codes or number comparison and helps protect against attacks such as key substitution.

Android Developer Verifier

This is Google's newer developer-verification service. It is designed to verify the identity of developers behind apps, particularly when apps are installed outside Google Play, as part of Google's upcoming Android developer-verification requirements.

So, to be clear: these aren't random or inherently malicious Google apps. They are legitimate Android security-related services.

The reason I made Sorry Google is about user control. If you don't want one of these services on your device, Android can make simply uninstalling/removing them difficult, and some system components can be restored through system updates or Google services.

The project uses package-name/signature behavior to install a minimal APK with the same package name as the targeted service. The replacement contains essentially just the required manifest and resources rather than the original service functionality.

GitHub:

https://github.com/rushiranpise/sorry-google

The project is open source, so you can inspect exactly what the replacement APKs contain and build them yourself.

Important: Replacing these packages means you may lose functionality that depends on them. This is intended for people who understand the trade-offs rather than being a recommendation for everyone.

I have made a Snapchat patch and I am currently considering whether it should be released publicly.

However, I have some concerns based on previous discussions with Morphe developers and the general situation around Snapchat modifications. Snapchat has been quite active in taking down modified versions of their application and has also taken action against user accounts that utilize such modifications. Even DMCA's.

I have spent approximately a month testing this patch and made many changes to improve its reliability and avoid detection. So far, it has been working as expected during my testing period. However, I cannot guarantee that Snapchat will never detect the modification or that they will not introduce changes in the future to block it.

My main concern is the potential impact on morphe users if the patch is released publicly. A future Snapchat update or detection method could potentially cause issues for people who rely on it.

I would appreciate feedback from the community:

* Would you consider releasing a patch like this publicly while clearly warning users about the risks?

* Would it be better to keep it private until there is more confidence in its stability?

I also want to clarify that I am not an experienced Meta app mod developer like the developers behind projects such as GBMods, FMMods, or other long-standing modification projects. Creating a standalone mod and creating a Morphe patch are two very different things. A patch operates within an existing framework and has its own limitations and challenges..

Hey everyone,

I recently started working on a small project called APK Download Helper

This project is still in the early stages, so it may not work perfectly yet. I would really appreciate it if you could try it out and report any issues, bugs, or suggestions. Your feedback will help improve the project.

Recently, Morphe Manager added support for external APK download helpers, allowing other apps to help find and download APKs needed for patching. Huge thanks to Marca and Liso for adding this feature.

How to use it:

1. Install APK Download Helper.
2. Open Morphe Manager : Settings → System
3. Enable: APK Download Helper
4. Go back to the app list.
5. Select an app.
6. Choose: Yes, I need help finding APK
7. Select: Use Helper
8. Choose: APK Download Helper

The helper app will open, and you can download the APK directly if it is available. If an automatic download is not available, you can manually download the APK.

Thanks for trying it out, and feel free to report any issues or suggestions!

Note: APK Download Helper is an independent project and is not affiliated with Morphe. Please do not report issues related to this app to the Morphe team. If you encounter any problems with APK Download Helper, please report them in this project’s issue tracker.

I honestly wasn't sure this would even work, but after a bit of experimenting... I managed to get Morphe running on my Galaxy Watch Ultra.

Seeing a patcher running on a smartwatch is just wild. 😂

It's obviously not something you'd use every day, but the fact that it actually works is hilarious and surprisingly smooth. The future is now patch apps from your wrist? 😎

Hi everyone! 👋

I have some free time and am accepting new app patches requests.

Repository: https://github.com/rushiranpise/morphe-patches

Before submitting a request:

• Include the app name and the specific feature you'd like patched.
• Search pinned thread or website make sure a similar patch doesn't already exist.
• If someone has already requested the same feature, please upvote their comment instead of creating a duplicate.
• Please don't report bugs in this thread. This thread is for patch requests only. For bug reports, please open a GitHub Issue in the repository instead.

I'll prioritize requests based on community interest and feasibility. Please note that server-side features generally cannot be patched.

Thanks, and I look forward to your suggestions!