view the rest of the comments
Android
DROID DOES
Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities:
I've had this problem too but the latest upgrade just fixed it. And yeah, I think it was Google's doing and it's not the first time, it's a constant arm's race between them and Newpipe programmers. And Ublock programmers. And Invidious and Piped programmers etc...
It's not showing an update. Maybe I should just uninstall and reinstall. Thanks for the reply.
I did that yesterday, didn't fix it. I was able to got the update from Newpipe directly today but my Boo had it three days ago, he said he got it from GitHub? No idea how to do that but maybe worth a looksy.
Thanks
They posted a release candidate that fixed the issue to Github first, then I picked it up from their site several days ago.