IstriKorupt*r

@tn69dr.bsky.social

Google will lock-down Android in September 2026 and NewPipe 0.28.4 release

As you have no doubt noticed, we have a banner with an ominous countdown now prominent on our website: Google will lock-down Android, and we need to raise awareness. Coinciding with this blog posts, we released a new update to NewPipe, where we introduced a pop up also notifying users there that they will need to take steps in order to keep using NewPipe. ## About Google This is not a fun blog post to write, believe me. Androids future is dear to our heart, and we believe that one of its main aspects was its openness, clearly separating it from Apple’s iOS as the better choice for every tinkerer and developer. For the past few years Google has continuously taken steps to remove this openness, and now it hit us. Google plans to force developers to become registered developers and submit their personal data during the registration process. By doing so, Google does no only collect data, but more importantly can decide who is allowed to create and publish apps for “registered” devices or not. We will not enroll in this privacy violating program and give up the anonymity of our developers. We do not want to be at the mercy of Google to allow our app to work. And you should not be content with this restriction either. Follow the steps outlined at keepandroidopen.com and resist this further lock-down of your device. ## Highlights of the new release Getting back to the fun part of having a new NewPipe version, we have on our hand, lets have a look at the highlights of this release. In order to improve the loading of the subscription feed, the order in which they are fetched is now randomized. That should also help against fingerprinting users. Comment pages which could be stacked infinitely via reopening videos from channels, not anymore. And in certain parts of the app, e.g. the _content unavailable_ screen, click throughs could happen through that screen in whatever lies underneath. This was done by @jpds, @aivelon and @dustdfg respectively thank you very much. ## Wanna Contribute? If you like the app enough to want to make it even better, or you noticed some glaring error that you can’t help but want to fix, you can read our contribution guidelines and do a Fix-It Felix. Or, if you’re bilingual (or even multilingual), you could help translate the app. **Feature additions** to the old codebase have been put on hold for now. We’re pretty swamped as it is, and are working to clear our large (and critical) backlog first. Our next priority is to finish the rewrite of the codebase. We are making progress - slowly, but steadily - and you can help out on that too (and learn modern Android development practices along the way).

newpipe.net

NewPipe 0.28.1 released bringing tons of fixes and improvements

We’re happy to announce NewPipe 0.28.1, which polishes the user experience while quietly fixing a large number of long-standing bugs. This release comes with a new version of NewPipe Extractor (0.25.0) that fixes several issues with data extraction while also providing additional data to the app. We wanted to bring you a big Christmas release, but it turned out to be more of a New Year’s gift instead. Either way, we hope you’ll enjoy the improvements and fixes in this release! We’d like to thank all contributors, especially those who recently joined the project. Many small improvements and fixes were made possible by new contributors, such as students from the Australian National University who worked on NewPipe as part of their Software Engineering course or folks who just came to stay. This release includes more than 50 user-facing merged PRs as well as tons of developer-facing PRs. We’d also like to thank all translators for keeping NewPipe accessible to users worldwide. ## Highlights * The player uses the original audio language by default again and handles clicking on timestamps and fullscreen changes much better * Downloading content should be less error prone and OPUS audio downloads now include some metadata * Many fixes that eliminate crashes, UI glitches, and confusing states * * * ## Everybody likes metadata, we do too! When downloading audio in **OPUS format** , NewPipe now embeds additional metadata: * Artist/uploader name * Track name/title * Genre (if available) * Date This makes downloaded files look much better in music players and media libraries. We are currently working on adding metadata fields to other formats as well. Cover art/thumbnails are also in the works. ## Playback & player improvements Clicking timestamps in the comments no longer clears your queue or unexpectedly resets playback. Your current player state is preserved, making navigation within videos much more predictable. The player now uses the original audio language by default again, instead of preferring autotranslated audio tracks. We are sorry for initially choosing “Yes” as the default value for the “Prefer original audio” option. If needed, you can switch it back by going to settings. The screen orientation is now correctly remembered and restored when exiting fullscreen on all devices, including Android TVs. Several rotation-related crashes and UI glitches have been fixed. Ghost notifications and random player crashes related to foreground services _should be_ gone. ## Download completed or isn’t it? NewPipe now tries to recover interrupted downloads in more cases when possible, reducing the chance of lost or stuck downloads. Some issues when resuming downloads have also been fixed. A bug was fixed that caused insufficient permissions to open downloads directly from within the app. Also, after hearing a suggestion from some user we met at FrOSCon, we added a button to remove a download entry in NewPipe without deleting the actual file. This was actually coded on the spot during the conference :-D SRT subtitles received a bunch of fixes that improve compatibility with various players. ## Better usability across the app You can now enqueue streams directly when sharing them to NewPipe, making it easier to build your play queue from other apps. The play queue UI also received several bug fixes, including one that caused items to glitch when enqueuing new streams. This issue existed for 9 year and is finally resolved! When viewing bookmarked playlists, its items can now be dragged in both directions in grid mode. Playlist changes are applied directly to the database, preventing confusing or incorrect UI states. NewPipe can now open and correctly handle `on.soundcloud.com` links, making it easier to share and open tracks directly from the SoundCloud app or the browser without pasting them into NewPipe’s search box. Error handling has been cleaned up and deduplicated, resulting in more specific and understandable messages when something goes wrong. On newer Android versions, NewPipe now shows a clear explanation dialog when overlay permissions are needed. ## More bug fixes you’ll definitely notice This release fixes a wide range of issues, including: * thumbnails for YouTube Shorts not showing up * the pages for recent and live streams from media.ccc.de are now filled with the correct content * formatting issues on older Android versions * and many more! ## Meet us at FOSDEM 2026! NewPipe e.V. is paying for the attendance of some TeamNewPipe members to FOSDEM, a free software conference happening on the 31th of January and 1st of February in Brussels, Belgium. Come to our talk about NewPipe and how it was ported to Salifish OS! Stickers, coasters and flyers included :) ## Wanna Contribute? If you like the app enough to want to make it even better, or you noticed some glaring error that you can’t help but want to fix, you can read our contribution guidelines and do a Fix-It Felix. Or, if you’re bilingual (or even multilingual), you could help translate the app. **Feature additions** to the old codebase have been put on hold for now. We’re pretty swamped as it is, and are working to clear our large (and critical) backlog first. Our next priority is to finish the rewrite of the codebase. We are making progress - slowly, but steadily - and you can help out on that too (and learn modern Android development practices along the way).

newpipe.net

NewPipe is turning 10 :O

Guess what? NewPipe just turned 10 ~~this month~~ last month! Time just flew by. In one moment you hit “new project”, and in the next there is a whole association, a group of maintainers, an uncountable amount of contributors, and millions of users!1 This is amazing. Last time we wrote about an important birthday, NewPipe had just turned five years old. Now it’s yet another five years later, and we still stand on the ground with both feet, running forward like there is no other direction! NewPipe is 10 years old \o/, a double-digit digits number. Just… let that settle in for a moment. ## Looking back 5 years ago, Schabi wrote a blog post for NewPipe’s birthday. We were right in the beginning of the second wave of the COVID-19 pandemic. Back then he wrote that “People keep working on it and organize the project like COVID-19 doesn’t exist”. This is exactly what happened to us in the last five years, and we are so proud of ourselves. Since then many things happened. People from the Project founded NewPipe e.V., a German association to support NewPipe and other projects like it. We started our refactor/rewrite, with plans for new extractor design and a new player (NewPlayer). The association on the other hand became a beast on its own. Its goal, to care for the donation money that came in from NewPipe, was far surpassed. In 2024 the association hired @Profpatsch and Schabi to work part-time on several topics regarding the NewPipe refactor. For this, the association built out a structure and process for hiring, which turned out successful. What does that mean for you? Well, NewPipe and hopefully other projects gain stability through this, since with paid personnel we can ensure continuous development, even for parts of the project where volunteering maintainers wouldn’t have much fun with. ## Looking… now? Today we are still in the rewrite phase of our app. There are a lot of open issues, which you maybe would like to take a look at, we are always happy to have new contributors. So come by, grab a coffee, have a chat with us (even in person if you are at SFSCon, 39C3 or FOSDEM), check out the code, and let’s go! :D Profpatsch has been steadily working on rewriting the app alongside all the people doing it in their free time like Isira Seneviratne, Stypox and many more. ## Looking forward There are two views on the future. The bright and the dark one. Let’s start with the bright view, because why not: One day we will be done with the refactor, up to a point where NewPipe can rise out of the ashes once again, with a shiny new look and feel and new code, that should make new and exciting subsequent projects possible. I’m talking Kotlin everywhere, Compose everywhere, and of course nice features without feature creep ;D. Eventually we also want to talk to video creators about the issue that NewPipe reduces their income, and start talking about a world beyond YouTube and Google. Now to the topic no one wants to hear. The dark side: It becomes progressively more complicated to stay afloat. This is not generally bad, because we grow with the tasks we have to accomplish. Take for example the ever-growing and aging code base. A refactor is overdue, but as you know, we are still on it! Or take the fact that we are all step by step growing out of university and now have to face the question of how to keep NewPipe running with mostly post grads. We want to tackle this matter with the association and of course new contributors. So far it’s working. The engine keeps burning! But - there has to be one - lets talk about the elephant in the room: Google They would like to get rid of projects like ours. No question. In the past few years we had to witness that they try harder and harder to get rid of us. So far without success, neither on a legal base,2 or on a technical base. But it is clear that these challenges will only continue to get harder and more plentiful. With the latest and biggest challenge being that Google itself wants to get rid of Android projects that maybe get too creative for its taste, by making it harder to supply software through alternative stores like F-Droid. This, to be honest, is a big challenge, and should not be taken lightly. However, I (Schabi) am certain: we will also tackle this one. We have come up with cool and creative solutions in the past to circumvent technical difficulties. To be honest I am even excited to see what people will come up with. But people have to come up with something. So please if you can: Help! Anyway. As dark as this might sound. We have no intention on stopping. See it from the bright side. There are already solutions in the workings for the challenges we have to face, and we continuously ramp up speed on the refactoring. So I am pretty certain about where NewPipe is going: To infinity and beyond! Sincerely your: * Aayush Gupta * absurdlylongusername * AudricV * Fynn * litetex * Poolitzer * Profpatsch * Schabi * ShareASmile * Siddhesh Naik * Stypox * Taco * TheAssassin * TobiGr * wb9688 * and many more Better known as Team NewPipe. * * * 1. You can check the number of downloads of F-Droid’s official repository over at fdroid-metrics.streamlit.app, however this does not include downloads from our own F-Droid repository. ↩ 2. See the yt-dl DMCA or the DMCA against our website, which are both not directly an issue caused by Google though. ↩

newpipe.net