Spent an evening getting a shell on my Fold 8 and debloating it. Two things wasted my time that I haven't seen mentioned much, so posting in case it saves someone else the trouble.

**LADB and Shizuku conflict.** Half the guides out there tell you to grab LADB as your post-reboot Shizuku helper. Its own README says it's incompatible with Shizuku, they both want the same wireless debugging socket. Repo's archived too. Use aShell You instead, it's built to run through Shizuku.

Which leads to the second one:

**aShell and aShell You are two different apps.** aShell is by sunilpaulmathew, aShell You is by DP-Hridayan. Both real, both work, aShell You is the more actively maintained fork with more backends. But if you search "ashell" you get both and the names are close enough that you should check the source repo before installing.

**Bonus thing that confused me:** Shizuku's "Authorized applications" counter said 0 the entire time, including after everything was demonstrably working. Don't troubleshoot based on that number. Run `whoami` in your shell app. If it returns `shell` you're good, if it returns something like `u0_a783` that's the app's own UID and it isn't authorized.

If you get a UID, force stopping the shell app and reopening it fixed it for me. Seems like it can launch before Shizuku's service is ready and just quietly give up.

**One more:** if `pm list packages` throws `SecurityException: Shell does not have permission to access user 150`, nothing is broken. That's a Knox container (Secure Folder or work profile) and shell can't see into it. Add `--user 0` to your commands.

Also worth knowing that my Shizuku survived reboots without any intervention, which the docs say shouldn't happen on a non-rooted device. Apparently Android 13+ has a trusted-WiFi auto-start path. So test yours before assuming you need the WRITE_SECURE_SETTINGS workaround.

Wrote the whole thing up properly here if it's useful: https://github.com/heemsec/android-hardening-and-tooling/blob/main/Debloating%20Android%20with%20Shizuku

Stock Fold 8, locked bootloader, no PC needed for any of it.

Most Android talk is about Pixel, Samsung, OnePlus, etc. But 8849 TANK 5 are doing unusual things — huge batteries, eSIM, projectors, night vision, and heavyduty protection. Are these interesting alternatives for Android fans, or too specialized for daily use?

Hi Reddit,

I built a Linux shell script that clones LineageOS applications so they install alongside the default system ones. The clone gets its own package ID, and you can personalize its name and icon and sign it with your own key or the public Android debug key. The script runs from a local page in your default browser and works on any distribution and desktop environment.

Sixteen apps are currently supported :

• System Essentials : Dialer (phone), Contacts, Messaging, DeskClock, ExactCalculator.
• Media & Utility : Jelly (browser), Aperture (camera), Twelve (music player), Glimpse (gallery), Gallery2.
• Tools & Settings : Recorder, Camelot (PDF viewer), Etar (calendar), AudioFX (equaliser), Backgrounds (wallpapers), Profiles.

This project is published under GPL-3.0: https://codeberg.org/213YaZ786/lineage-app-cloner/

Feel free to use the repository's issue tracker to submit bug reports or to share your thoughts right here in this thread.

Peace be upon him who believes.

Hey everyone,

If you wear a smartwatch on Android (Honor, Amazfit, Huawei, Garmin, etc.), you're probably familiar with WhatsApp spamming your wrist: a single incoming text triggers multiple vibrations, often mixed with useless "X new messages" bundle summaries or alerts you already read.

The problem? WhatsApp constantly overwrites its notification slot on every chat update, causing companion apps (Honor Health, Zepp, Huawei Health) to misread these refreshes as brand-new incoming texts.

Instead of disabling wrist notifications entirely, I built WANotify—a lightweight open-source bridge app.

How it works:

• Uses Android's NotificationListenerService to intercept WhatsApp alerts.
• Parses the MessagingStyle payload to filter out thread history and aggregate counters, isolating strictly the latest message leaf.
• Employs an in-memory sliding-window cache with monotonic timestamp checks to drop ghost updates and rapid duplicate bursts.
• Routes sanitized messages to a silent system channel (IMPORTANCE_MIN), keeping your phone completely quiet while your smartwatch delivers just one clean buzz.
• Runs 100% locally with zero internet permissions, telemetry, or battery drain.

Quick Setup:

1. Install the APK and grant Notification Access + ignore battery optimizations.
2. In your smartwatch companion app (Honor Health, Zepp, etc.), disable notifications for WhatsApp and enable WANotify instead.

Source code and pre-built APKs are up on GitHub:

https://github.com/enesuzun2002/WANotify

Feedback and bug reports for specific watch models or companion apps are welcome!Smartwatch buzzing 3 times for the same WhatsApp message? I built a lightweight open-source fix (WANotify)

I have been looking at what they have been doing to both Pixel and Android and asking myself the same question for quite some time now...