adb devices "no permissions" [SOLVED]

Yep, adb debugging on. Like say this works fine in Fedora and MX and Manjaro.  Only a problem in MINT and Bodhi. I assume any distribution related to Ubuntu that uses this udev directory for "android rules".

By way my internet is through my phone and the phone has the native Android usb tethering and hotspot function blocked so I have both Easytether and the old venerable open source Azilink. Sometimes one works better than other so have both. Azilink requires both adb and openvpn to be installed. It works fine in Bodhi. Even works on windows. So the part of adb it uses does work, its this permissions thing. I think Easytether has its own necessary bit of adb built into it, dont need to install adb for it, but debugging has to be on. Both Easytether and Azilink require adb debugging on.

Ok, it error-ed out again. Ok, seems since I use Easytether, and since Bodhi is a systemd/NetworkManager distribution that systemd automatically connects making Easytether a service. So to use scrcpy, I need to disable Easytether on the phone (uncheck a box in the app), then set phone to file transfer mode, only then can I use scrcpy. I know few are going to be using both Easytether and scrcpy, but in case somebody is frustrated and finds this, thats the reason.

Scrcpy is important to me as it lets me send or reply to texts with a big screen and real keyboard. With my old eyes, dont appreciate trying to squint at small screen and poke at the tiny screen keyboard with my finger. Especially with stupid phone trying to predict what I am writing cause big brother knows best.... GRRR. Scrcpy basically makes texting into something similar to email. Though that predictive "feature" that cant be turned off without rooting the phone, still tries its best to frustrate me.

On non-systemd systems (and uncooperative systemd systems), I use my own small script with ifup/ifdown and tun-easytether interface statically defined in /etc/network/interfaces. Networkmanager ignores interfaces defined there. On non-systemd systems, networkmanager or connman just ignore the tun-easytether interface no matter what. Has to be manually activated. And not all systemd systems have always been friendly to tun-easytether interface, but they seem to have improved. In my experiments with systemd systems lately all have been friendly to tun-easytether. interesting in MX23, in regular mode it ignores tun-easytether, booted with systemd option, it finds and uses tun-easytether. The old ifup/ifdown always works though, but lot systems no longer include it so one has to install it and recreate missing directories, etc. A small custom script makes ifup/ifdown trivial and automatic. Azilink uses openvpn and it has its own way doing things so networkmanager/systemd not involved though best if Easytether disabled to use Azilink.

I just read some about KDEconnect. It has absolutely no mention of what needs to be installed on the phone or requirements for the phone. It mentioned needing Android 11 for some feature to work, but that was the limit of any explanation. Rest was all about bragging how it works on any operating system. And how I could remote control my computer from my phone or was it the other way around. Not useful to me.

Scrcpy requires minimum of Android 5. This makes it very useful as I think just about any phone out there that does 4G LTE required anymore, has that at a minimum, more likely Android 7 like mine. As I mentioned before, not a fan of smart phones or Android. I run older phone that was cheapest I found whitelisted for use on ATT network (via MVNO). Well cheapest that is well built as there are some designed to self destruct in matter of months. I use phone to make calls, do texts (only cause everybody insists on texting anymore), and to tether my computer for internet. I care less about the rest of it, though I swear they sure made it painful to try and delete apps they built into the system. You have to root it and some phones like my less popular Kyocera, nobody ever came up with instructions to root and I didnt want to experiment and brick it. Believe me I would if it were possible. I dont appreciate hidden apps wasting my data, apps I dont want and never will use. Dont even get me started on the heavy hand of Google involved in all this.

Scrcpy is saving grace to text with old eyes and fingers that dont always cooperate with small touch screens. I bet some wonder how I can write such long texts... LOL I tend to treat it like email. But you cant get people to email anymore, they want to torture themselves texting on small screen.

Oh and I have a backup phone, a Sonim XP5800. No touch screen, has physical T9 keyboard. Runs on small version android, originally android 4.4, but they upgraded in stages to android 7. Well guess what, scrcpy actually works with it. I was surprised. Now with no touch screen, there are no arrows or screen keyboard. So you still have to navigate using phone keypad but for texts, you can type messages via desktop keyboard though still havent figured out how to type numbers, but thats not problem, easy just using the T9 keypad. Its the text messages that are painful with T9.

My notion is to try textnow free voice and text (with ads) on it. But still have to see if the textnow apk will sideload and function. This is not a full android so though it will run some apps sideloaded to it, its limited. No playstore or other store, it was intended as a "feature phone" not an android smart phone. But the thing is built like a brick with larger than normal battery that lasts forever. An easy to replace battery might add, also something rare in current phones.