Real shame. I've been enjoying mine for the last 2 years. It's the only tablet with GrapheneOS support and USI stylus. Good sized screen for drawing and watching movies. My only complaint with it is the fingerprint sensor and lack of GPS. I really hope there'll be a successor!
Best way is to not include it in the first place by using another ROM. If that's not an option, you can always remove it via root. It may also be possible to use ADB/Shizuku to get rid of it, but Google could add checks to prevent ADB from removing it. Then again apps installed via ADB aren't subject to verification.
I've been using a Vero V from the OSMC project. It runs Kodi and comes with a remote that's simple enough for my family to use. Kodi has been around for ages and is great for both local library content as well as add-on based content. The OS is based on Debian so you could run some other services on it. The SoC has support for AV1 hardware decoding (as well as all the older codecs) and can play 4K HDR10+ content to my TV without issues. There's also Dolby Vision support if your TV supports that.
It's probably not the cheapest option but I wanted a small form factor and good UI that my family could use without having to be tech wizards.
Maybe it's the endpoint Syncthing uses for NAT traversal or fetching the relay list. Other than that I'm not sure but you could ask the developer, they respond to questions quickly.
I know I'm not directly answering your question but I switched from Catfriend's last build to BasicSync. Sure, it doesn't have the same bells and whistles as Syncthing Fork but importing worked fine and it's been rock solid since. If you've ever used the Syncthing web UI on desktop you'll be fine. Plus the developer is well known in the Android development circle.
Finally, repository specific access tokens were added!
I was missing this feature from GitHub (fine-grained access tokens) and had resorted to making service accounts that had access to a single repo. Time to clean that up :)
Perhaps try Authnkey which is more recently updated.
If that doesn't work then some details like which security key you are using and over which protocol (USB or NFC) would be good to know.
Ultimately that is your choice. I personally will not use researchxxl's version considering they appeared out of nowhere and there was 0 communication about the transition. For now I will continue to use Catfriend's version and perhaps switch to nel0x's in the future.
You don't have to compile GrapheneOS from source thanks to avbroot which can take a release zip, patch it with root and sign it using a custom avb key. This lets you root while keeping the bootloader locked.
The rooted-graphene project automates this completely using GitHub actions. It even lets you do OTA updates like normal GrapheneOS.
Yet the source code still isn't public. It's been at "As we're rolling it out gradually to ensure a bug free experience, source code will be available at a later time on our GitHub repo." for the last 2 months. Later time probably means in a year at this point.
Edit: 2 months later (if anyone's still reading this lol) they have finally updated the GitHub repo with the latest source code. Phew.
In a way, yes. The more things that have your credentials the greater the attack surface. However the code is open source, you could inspect it and build it from source if you'd like to. Additionally if you use a mailbox password then the app won't be able to read email content as the mailbox password is used to decrypt the actual content while the main password is for accessing the account. The app doesn't need your mailbox password for its functionality so it can't decrypt email content (except the header which is not encrypted by PGP).
Yes I have been using this for a year now and it works great. You can customise the poll duration (how long it waits before checking for new emails) and the notifications have quick actions like mark as read and trash.
I am able to access the data folder which is located in Internal storage/Android/media/com.whatsapp. This is without root using the AOSP files app, not sure if that's what you meant.
For a second I thought this was The Onion. This is so dark and invasive but I can't stop myself from laughing. It's like they don't even care to pretend anymore.
Real shame. I've been enjoying mine for the last 2 years. It's the only tablet with GrapheneOS support and USI stylus. Good sized screen for drawing and watching movies. My only complaint with it is the fingerprint sensor and lack of GPS. I really hope there'll be a successor!
So pretty much encouraging vibe-maintenance... No thanks
This looks like an AI generated ad disguised as a discussion...
Best way is to not include it in the first place by using another ROM. If that's not an option, you can always remove it via root. It may also be possible to use ADB/Shizuku to get rid of it, but Google could add checks to prevent ADB from removing it. Then again apps installed via ADB aren't subject to verification.
I've been using a Vero V from the OSMC project. It runs Kodi and comes with a remote that's simple enough for my family to use. Kodi has been around for ages and is great for both local library content as well as add-on based content. The OS is based on Debian so you could run some other services on it. The SoC has support for AV1 hardware decoding (as well as all the older codecs) and can play 4K HDR10+ content to my TV without issues. There's also Dolby Vision support if your TV supports that. It's probably not the cheapest option but I wanted a small form factor and good UI that my family could use without having to be tech wizards.
Maybe it's the endpoint Syncthing uses for NAT traversal or fetching the relay list. Other than that I'm not sure but you could ask the developer, they respond to questions quickly.
I know I'm not directly answering your question but I switched from Catfriend's last build to BasicSync. Sure, it doesn't have the same bells and whistles as Syncthing Fork but importing worked fine and it's been rock solid since. If you've ever used the Syncthing web UI on desktop you'll be fine. Plus the developer is well known in the Android development circle.
Finally, repository specific access tokens were added! I was missing this feature from GitHub (fine-grained access tokens) and had resorted to making service accounts that had access to a single repo. Time to clean that up :)
Perhaps try Authnkey which is more recently updated. If that doesn't work then some details like which security key you are using and over which protocol (USB or NFC) would be good to know.
Looks like someone beat me to it: https://github.com/GlassOnTin/Haven/issues/42 As of yet no reply.
Sigh. I knew uv and ruff were too good to be true. Just hope the community can fork before it all goes to crap.
Ultimately that is your choice. I personally will not use researchxxl's version considering they appeared out of nowhere and there was 0 communication about the transition. For now I will continue to use Catfriend's version and perhaps switch to nel0x's in the future.
No, the maintainer of syncthing fork deleted their account and the repos out of the blue. There's a lengthy forum post about it here.
You don't have to compile GrapheneOS from source thanks to avbroot which can take a release zip, patch it with root and sign it using a custom avb key. This lets you root while keeping the bootloader locked.
The rooted-graphene project automates this completely using GitHub actions. It even lets you do OTA updates like normal GrapheneOS.
Yet the source code still isn't public. It's been at "As we're rolling it out gradually to ensure a bug free experience, source code will be available at a later time on our GitHub repo." for the last 2 months. Later time probably means in a year at this point.
Edit: 2 months later (if anyone's still reading this lol) they have finally updated the GitHub repo with the latest source code. Phew.
In a way, yes. The more things that have your credentials the greater the attack surface. However the code is open source, you could inspect it and build it from source if you'd like to. Additionally if you use a mailbox password then the app won't be able to read email content as the mailbox password is used to decrypt the actual content while the main password is for accessing the account. The app doesn't need your mailbox password for its functionality so it can't decrypt email content (except the header which is not encrypted by PGP).
Yes I have been using this for a year now and it works great. You can customise the poll duration (how long it waits before checking for new emails) and the notifications have quick actions like mark as read and trash.
Chat control and any sort of good are fundamentally incompatible.
I am able to access the data folder which is located in Internal storage/Android/media/com.whatsapp. This is without root using the AOSP files app, not sure if that's what you meant.
For a second I thought this was The Onion. This is so dark and invasive but I can't stop myself from laughing. It's like they don't even care to pretend anymore.