(2nd is the phone) so I'm using a gsi on my samzung phone(unfortunately) and I accidentally installed a custom rom that installed a kernel that had kernelsu/next baked into it but no susfs. So how can I hide these(yes I know these look generic and also I found this cat on the street. I unfortunately cannot bring this fella into my home as I'm still a teenager) last pic is the same cat fella just standing up

How to pass device and strong integrity? I just want my banking apps working on my lineageos ... What i need to do?!?

Rooted my old Samsung Galaxy S20 phone after upgrading to Samsung Galaxy S26. Anyone have Custom ROM recommendations that run Android 16? Ty!

Introducing ShizuCallRecorder, an Android 11-16 application that uses the shell app (ADB through Shizuku), to record phone calls on non-rooted devices. FOSS, privacy-friendly, and it does not always run in the background. Simple as that.

Before saying anything else, Android 11 support is limited.

Features:

• Records both sides of phone calls (incoming and outgoing)
  • Should work even when using Bluetooth or a remote headset
• Security toggles to manage Shizuku on/off state
  • An attempt to reduce the potential attack surface introduced by Shizuku
  • Helps with apps that detect / yells at you when USB Debugging or Shizuku is enabled
  • (You need thedjchi Shizuku fork, recommend in requirements in the README.md)
• Automatic call recording option with basic exclusion rules:
  • Ignore anonymous calls
  • Ignore specific contacts
  • Ignore all contacts
• Saves recordings with Opus or AAC codec.
• The app runs only on phone event changes, no persistent background process and notifications

This is a tool, use it responsibly, and follow the law. Read the app disclaimer, it's a one time thing, don't skip it.

GitHub: https://github.com/kitsumed/ShizuCallRecorder

EDIT: If you like the project, please star the repo!

EDIT 2026-05-19: You can help translating the project in your language https://hosted.weblate.org/engage/shizucallrecorder/

If you are an Android dev or if you know more about Android internal API / hiddenapi, take a look at the CONTRIBUTING file. I have a few issues I would like assistance with, any kind of feedback, online resources, or even PoCs are welcome.

This app is not an first time easy install and forget. You have some configuration to do, though it is relatively small. However, if you have never used Shizuku, it will take longer. Please follow the documentation carefully. There is reading to do. I highly recommend that you do read, both for the sake of it working and for the sake of keeping your device safe.

The project is licensed under GPLv3, with additional terms under Section 7. The goal of the additional terms is to prevent the app from being published to app stores under the name ShizuCallRecorder, and to stop anyone else from distributing it as the official app. In a nutshell, it cover trademark protection, giving credit to me and the project in forks, etc. But anyone is free to fork it.

I care a lot about security and transparency. I enabled immutable GitHub releases, assets of a release cannot be swapped once a release is published. Releases are built using GitHub Actions Runners, they clone the repository code directly, build the app, and the apk files are attested so that all users can detect if something else happened between the build process and the release publication (gray-area). This reduces the attack vector, but does not fully eliminate it (the code itself, the runner getting compromised, dependencies, etc.).

I'm looking for user feedback. If you try out the app, please tell me the following:

• Device model
• Android Version
• Did it work with the screen unlocked?
• Did it work when the screen was locked?

I want to see if there's any specific device, OEM or Android limitations. I didn't extensively test it across devices outside of the Android emulator and my Samsung Android 16 test phone, but it SHOULD work.

"It works on my machine"

EDIT 2026-05-18: Hey, it seems to work on other users machine! 🎉

More rambling below, not important :

For a couple of years now, I have been looking for a call recording app. I think there are multiple reasons why one would want to record phone calls, such as remembering things, or even using it as proof for any kind of scenario.

However, the Android project seems to think differently. Ever since the release of Android 4.4 KitKat (API 19), native 3rd-party phone call recording apps have been killed by restricting the CAPTURE_AUDIO_OUTPUT permission to signed and system apps for valid privacy reasons. However, to this day (API 37), no real, intended direct alternative has been added. Yet, multiple developers have asked about this on the Google Issue Tracker and other websites.

Meanwhile, "system" proprietary apps like the Google Dialer and OEMs apps sometimes use that restricted permission, and some do offer the recording feature. However, they often choose not to offer it to most users (even if legal in the user country), or they add their own proprietary rules on top of it. That is, of course, without mentioning that their apps are often privacy invasive.

On the other side, to work around theses new limitations, there are a couple of closed-source proprietary call recording apps on the play store and other online stores that use workaround ways like the speaker trick and accessibility services (see this short Bitdefender article on accessibility service security risks, I had found a really cool in depth article with all of the way it could be abused but can't find it anymore 😞 ).

I will not name any app nor say that they are 100% malicious as I did not dig deep, but I will say this: When I was looking at applications and checked them, some had unrelated invasive permissions related to the GPS and/or the phone sensors. Other apps would sometimes start pinging some remote config endpoint at recurrent intervals. All of these apps used accessibility services. Considering that these apps run permanently in the background and can see everything on your screen, this isn't really something I was personally comfortable with.

When I started this project, I noticed in the following weeks that a couple of existing closed-source call recording apps slowly added Shizuku support. Would I give ADB-level access to a closed-source app from an unknown developer? Personally, I would not feel comfortable doing so. I'm not looking to discredit their work and it's nice that they keep improving their apps, I'm just saying it's a risk I wouldn't take.

With that in mind, I recently discovered Shizuku and did a deep dive into how it works in my blog post, What is Shizuku, how does it work, and its security implications. This is when I had an idea: what if we could use the shell application permission, a signed system application, to use permissions you normally do not have access to? I searched online, found other issues online talking about it, and decided that if no one would make it (a FOSS app), I would give it a try myself. Now we are here, with a working app (I hope so). The more in-depth story is in the CONTRIBUTING file. I also want to point out that I had never done any real Android development prior to this app. Doing this as a first project was a little bit insane, but we'll see what happens.

>> UPDATE AND RESULT: > > Added 'Hardware & Charging Hygiene' section for better battery longevity. > > Battery Proof:
Nearly 10h SoT with 85% usage. > > Charging/Health:
Testing the 90% limit settings, charging is unaffected. > Keep scrolling for the full debloat guide.

Following my previous posts regarding my S24+ OneUI 8.5 debloat journey, many of you asked for the complete methodology and the package list I’ve been using.

I’ve spent the last few weeks refining this into a structured, risk-aware protocol. The goal is simple: achievea "flat" overnight battery drain (0-1% over 8 hours) while significantly improving system responsiveness.

By stripping away heavy telemetry, aggressive background services, and redundant Samsung bloat, the device feels snappier, runs cooler,and keeps the UI fluid even during heavy multitasking.

---

Why use this instead of Root?

Even though this is r/androidroot, I know many of us prefer keeping our device status 'Official.'

This method allows for system-level debloating while keeping KNOX completely intact.

You retain full functionality of Samsung Pay, Samsung Pass, and your warranty, all without the risks associated with tripping theKNOX fuse or unlocking the bootloader.

---

Getting Started:

If you haven't set up the tools yet, here is the quick path:

1.Install Shizuku from the Play Store.

2.Activate Shizuku: Go to Settings > Developer Options > Wireless Debugging, turn it on, then go back to the Shizuku appand start it via "Pairing" (follow the on-screen instructions).

3.Install Canta (get the latest APK from the GitHub releases).

4.Launch Canta: Grant it the Shizuku permission when prompted, and you’re ready to import the package list fromvthe guide below or select manually packages you want to debloat in Canta.***

---

The Methodology

I’ve organized the package list into three "Risk Tiers" to ensure you can debloat without breaking your daily driver.

This is done via Shizuku +Canta.

•Tier 1 (Safe): Telemetry, marketing, and redundant Bixbyservices.

•Tier 2 (Utility Dependent): Features like Smart Switch, specific cloud sync tools,or secondary Samsung apps.

•Tier 3 (Advanced): Core system components—proceed with caution and only ifyou have alternatives (GCam, Gboard, etc.) ready.

---

Access the Guide

I’ve hosted everything on Pastebin to keep the instructions clean, transparent, and easy to update:👉

https://pastebin.com/k5JnfbSW

(The guide includes detailed instructions on how to handle the JSON import versus manual selection for maximum safety.)

---

⚠️ Mandatory SafetyWarning

This is an extreme debloat.

Always perform a full backup (Smart Switch/GoogleOne) before modifying your system.

If you delete a critical component, be prepared to perform a Factory Reset to restore your device.

You are responsible for your own device.

---

I’m sharing this as a community resource for those who want to reclaim their device's resources. Feel free to share your battery stats or any questions below!

Edit: Thanks for the amazing feedback, everyone! I'm glad to see this is helping you optimize your S24+ batterylife. Feel free to ask any questions below!

---

For those who want to dive deeper into the technical aspects or follow the evolution of theprotocol, I have also opened a dedicated thread on the XDA Developers forum. It's the go-to place for advanced discussionand troubleshooting: XDA Ruvomain Protocole link

---

•Optimized with The Ruvomain Protocol™

•Stay clean, stay fast, stay Ruvomain.

EDIT: Pastebin updated to v2.0 — now 321 packages, validated on One UI 8.5: https://pastebin.com/FdfDYqZt

UPDATE -One UI 8.5 SUCCESS

I performed an extreme debloat (291 packages) with Shizuku+Canta and here are the Antutu score and ranking, as well as the battery life of my Samsung Galaxy S24+ OneUI 8.0. What figures do you get?

⚠️ Warranty & Knox Status :

Many of you have asked if this method trips Knox or voids the warranty. I can confirm it does not. Since this uses Shizuku/Canta without rooting or modifying the bootloader, my device remains 100% stock. Click here for proof of status

⚠️ DISCLAIMER & METHODOLOGY :

Below is the list of the 291 packages I uninstalled via Canta to achieve these results (2.1M AnTuTuscore / 38°C max). Please note that this configuration is radical and tailored to my specific workflow.

Required Alternatives: I have removed core system apps (Camera, Gallery, Keyboard, etc.) on Samsung Galaxy S24 Plus. If you apply this list, ensure you have installed your preferred alternatives (GCam, third-party galleries, etc.) before removing the Samsung services.

Customization is Key: This list is not a "one-size-fits-all" script. It is a starting point. Please review the list carefully and keep the packages you actually need based on your own usage.

Responsibility: Perform a full backup of your data before proceeding. I am not responsible for any "bricks," data loss, or system instabilities resulting from your choices.

For those wondering how I achieved this score: it's simple. My processor is no longer wasting 30% of its cycles managing useless services, telemetry, and proprietary background bloat. The result? Less heat, better responsiveness, and a battery that lasts 11+ hours of SoT.

If you want to do the same, here is the full list of packages I safely removed (via Shizuku/Canta): https://pastebin.com/FdfDYqZt Knowledge is a tool; use it with caution.*

⚠️ SAFETY & REVERSIBILITY :

Worried about removing too much? Don't be. Because we are using Shizuku/Canta, these changes are fully reversible. If you accidentally remove a package you need, simply open Canta, go to your 'Uninstalled' list, select the app, and hit Restore. No root required, no Knox tripped, and your system remains perfectly intact.

Hi guys. I have a Samsung Galaxy a50. I tried to install snake os and After i Download twrp with Odin. My phone just doing restarts. I cant do anything. Dont turning off or can Access to the bootloayer or anything.
I used this vid:

https://youtu.be/FhzpLXTt\_Sg?is=tka1HUTG9OOZuywY

Can anyone help me?