Not all phones use them. Important to know if yours does to ensure you're always flashing to the correct partition/slot.

https://xdaforums.com/t/guide-the-noobs-guide-to-a-b-partitions-and-other-op6-idiosyncrasies.3816123/

I assume you used the boot.img from your phone, copied that to the phone, patched it with Magisk on the phone, then copied the patched image to your pc and flashed that to boot. (I know, it's such a clumsy process anymore thanks to Google).

What I do is flash the phone, copy the boot.img from the source zip to the phone, then do the rest. That way I know I'm working with the right version of boot.img. I also save the patched boot.img with the source zip, properly named (device name, version, etc) so I never mix it up with other device images.

I also do this as one of my first steps setting up a phone, before installing anything else. Not sure that makes any difference, but I also use some root apps (firewall, etc) that I want in place before installing apps.

What is this?

Have you tried swapping back to the inactive slot? Then maybe start over again from scratch.

If you don't understand transitive dependencies and how they carry through into either the classpath of your app or how they get merged into the manifest that you declare as your own app's, then you're going to have to learn these lessons the hard way.

I'm sure you are carefully examining each line of code of libraries your app depends on, including hundreds of transitive dependencies, and also build tools. You are a responsible developer, aren't you?

Aren't you supposed to check your merged manifest before publishing? To catch things like this?

You would think that's what one would do. The permission isn't added as quietly as OP would lead you to believe if you look at the merged manifest.

That's what I did indeed, thanks for the advice!

Aren't you supposed to check your merged manifest before publishing? To catch things like this?

It's all great assuming apps or libraries behave the way you think they ought to behave but as a developer the responsibility is on you to check what you're publishing.

Some features of the app claim to require shizuku, maybe the app itself is lying to me?

It's not really about the data. It's more about the OS. I want to be able to roll back to the original image if Lineage OS fails.

Thank you. That's probably what I'm looking for.

I don't think I really care about the apps. It's more about the OS/Rom. I've downloaded the last rom update from some shady 3rd party site, but I don't trust it. I can't download the official images from samsung anymore. So I'd rather do a backup that I can roll back to if lineage fails.

Thanks!

The F-Droid team is already quite aware of what google is doing.

That was discontinued quite some time ago

I was referring to Openclaw needing it. You could enable wireless adb and Openclaw should be able to connect to your phone directly without having to go through Shizuku.

Shizuku is just using adb over tcp but to localhost on the device it's installed on.

I installed from F-Droid.

I was seeing the pentagram logo with "upgrade" and a nag screen instead of the actual cleaning step, after scanning.

It turns out I'm a dummy who was backing out of the donation website after it loaded but before it could set the flag in the app telling it that I at least looked at the donation page.

If you're in a conversation about Shizuku, you should probably be downloading apps from the source. I've donated the equivalent of buying the app, but you don't have to pay anything to get the full features.

A lot of open source developers subsidize their users by charging on the Play Store while offering the complete app on F-Droid or other code repo (like GitHub).

APK's all the way for me no matter what...

Is it just me, or does SD Maid not do anything it advertises unless you pay?

Wow, I rarely see apps on the Playstore with just 10-50 users total. Btw, If you're looking for open-source, seems there's two apps in the F-Droid store as well: Oksigenia SOS pretty much for this use-case. And SOS Alerter for location sharing and manual SOS.

I don't think you can do the entire phone but you can do through each app and see which ones allow you to backup data and settings. If you have pictures you can use something like immich to back that up. If you need to back up SMS/MMS/phone logs there's sms import/export on Fdroid.

You can also plug your phone into a computer and download any folders you have data in.

The short answer is yes.

It's kinda like root-ish privileges. It facilitates doing things that you're not technically prohibited from accessing, but there simply is no interface for. It uses administrative console commands (administrative in the management sense, not like administrator=root sense) to execute changes that don't have any pathway built-in for the end-user.

Personally, nearly all my devices are rooted, but I did use Shizuku for some accessories on a few devices. It's a bit of ado to setup; not difficult just a handful of steps. Worth it if you really need or want to do something the GUI won't provide and you'll likely find more uses down the line.