On Tue, 1 Jul 2025 22:29:04 +0100, Jeff Layman wrote :
The learning hurdle isn't in Shizuku.
The learning hurdle is in setting up adb and/or wireless debugging.
I haven't used adb. There is a linux version available for Linux Mint
but I've yet to install it.
I use adb standalone.
C:\app\android\adb\adb.exe
You don't really "install" it. You just copy it and unzip it.
It works on all three PC platforms so you're just fine on Linux.
It's just an executable (adb.exe) on Windows, plus some "stuff".
C:\> dir /b adb*
adb
adb.exe
adb.help
AdbWinApi.dll
AdbWinUsbApi.dll
Most people get adb by accident when they install Android Studio.
But I use an older adb version that I simply copied from somewhere.
Let me see where I got it from (but you'll need the Linux adb).
OK. Found it. I got it from here:
<
https://www.xda-developers.com/install-adb-windows-macos-linux/>
However, as Shizuku doesn't require it, I'll
follow the instructions here to install it using wireless debugging
<https://shizuku.rikka.app/guide/setup/>. As you noted, it's a bit
complicated, but when I've got time I'll have a look. Then I'll probably
try UAD first.
When Wireless Debugging first came out, Andy and I discussed it a lot on
this newsgroup, as it was getting more functional around Android 10 or 11
and 12 or so, but then it started fossilizing into what it is currently.
It's fine. But it's designed with SECURITY in mind. SO it's a PITA.
It constantly changes the port out from under you.
At least with adb it does.
So, one day you're using port 123456 and the next day you're using the port
654321, and you get no choice in the matter (at least with adb that's what
it does). Every connection has a new port. It's a pita if you ask me.
SO I haven't used wireless debugging in a while because USB is easier.
Given that, and given you need SIMULTANEOUS split screen inputs for
Shizuku, I seriously do NOT suggest you use wireless debugging.
There's no advantage.
The only advantages of using Shizuku with wireless debugging is:
a. You don't need a PC to activate Shizuku
b. It survives a reboot
That's it. It's not worth the effort if you ask me.
The only disadvantage of using adb with USB are the same:
a. You need a PC
b. It doesn't survive a reboot
If you ask me, adb is (by far) the way to go.
Plus, I use adb every single day. It's an extremely useful tool.
Wireless debugging? Not so much.
SO it's adb hands down.
As a final comment, it seems strange to me that F-Droid has Canta, but
doesn't have Shizuku.
Unlike Apple trolls (and Carlos), I can look things up, where I looked that
up and found that Canta is FOSS so it fits well within F-DRoid while
Shizuku's developers chose to release via GitHub & the Google repo.
However, you can often find Shizuku in third-party F-Droid compatible
repositories like IzzyOnDroid, so, it's not an iron-clad distinction.