NewPipe

Hey there, NewPipers! It’s been quite long since the last release. But for good reason: This release comes with quite major changes to the way NewPipe works, visibly as well as under the hood. Reworked UI Embedded Playback in Portrait orientation ... [More] Videos will now play in the details page when in portrait orientation. By default, playback will start automatically upon opening. To accommodate this change and make it more palatable for users who prefer to initiate video playback themselves (“How dare you start the video without asking me!” shakes fist), there is a new ‘Autoplay’ setting to control playback. Autoplay will be turned on by default for Wi-Fi, but you can always turn it off completely if you want. Correct Video Orientation The gist: The player now automatically assumes the correct orientation when you enter full screen. The details: In the previous version, if auto-rotate was off, the main video player would just play videos in whatever orientation you last used. You would have to manually rotate the screen if you encountered a video with the opposite orientation. No more! There is now a full-screen button which replaces the orientation switch button, and it is smart. It will detect if the video is landscape or portrait, and will ensure the player is in the correct orientation right when you enter full-screen! How’s that for convenience and usability? Not just that; if auto-rotate is enabled, rotating the device to landscape will automatically play the video in fullscreen. Minimized Player The gist: A minimized player that lets you browse NewPipe during playback, and stores your opened videos in a temporary queue. The details: In the previous version, you could either watch a video in the main player or browse NewPipe. No browsing while watching. And you sort of had to keep track of where you were in terms of navigation in the app. (We’ve all been down the “Related Videos” rabbit hole.) Now you can swipe down on the video in the embedded player, or swipe down from the title area when in full screen, to collapse the video to a ‘mini player’. You can pause and resume the video from the mini player, or close the video entirely. Moreover, if you open, say, ten video pages in a row, the mini player will keep all of those pages in memory until you close it (kind of like a browser tab). So you can pause a video, browse Newpipe, queue up a few more, and resume the video, all without losing your place. No more having to finish a video before browsing mindlessly – yay distractions! Thumbnail progress bar Look at this screenshot! Nice, isn’t it? You get this shiny new progress bar underneath the thumbnail when you play a video in the background or pop-up players. It updates in real time, gets a little counter and is coloured red - it’s great, really. The Unified Player The gist: The three players (main, pop-up, and audio), which were completely separate earlier, have been welded on top of one common player service so they can share the current stream state. The details: Up until now, NewPipe had three separate players: main, pop-up and audio. All three had separate stream states and separate playing queues. When you switched from one player to another, the old player and its queue closed in the background, while a new player and queue were created, after which they took over playback. If that sounds complicated and cumbersome, that’s because it is. Now, the code has been rewritten so that all players run using one common service. When you switch from one player to another, this service remains running, preserving the stream state, and the new player just picks up from where the old one left off. Less work for the app, which means faster switching between players! Some side effects of this change: There is only one common queue now. So no matter how you enqueue a video, it will be added to the same queue instead of creating a new one. We would like feedback on whether this change is welcome or not. The app will always show a notification when a stream is playing. This is so that Android doesn’t kill playback whenever it feels like it. All of what you’ve read above was made possible by the lean and mean coding machine, the one and only - (drumroll) - @avently! Seriously, you should all sacrifice your first born child in his name. Or just say thank you. Whatever works out for you, you boring people. Try to be more adventurous in life. On a serious note, this was a massive, massive change to not only the code, but also the app’s workflow, so this PR was tested, reviewed and modified lots of times, over a long period of time, before it was allowed to see the light of day with this release. A huge thank you to you, @avently, for having the patience and dedication to keep adding features and bug fixes until everyone was satisfied! A different person probably would have gone insane. And a big thank you to the maintainers for doggedly reviewing this gigantic PR repeatedly. Those ~6600 additions and ~5600 removals must have felt intimidating! Naturally, since this was such a massive change, several bugs also slipped through. But @avently, with the help of @blackbox87, @Stypox and @TobiGr fixed a large number of them. More will be addressed by further point releases. The Notification is dead, long live the Notification! The gist: New notification! Very colour-y! Very button-y! The details: The old notification was based on a very old API (‘RemoteView’, which was pre-Lollipop!). Now we have a new one, which should be familiar to you if you’ve used other popular media apps. Does the cover art - based theming ring a bell? Enter the Age of the MediaStyle notification: Pros: 5 action buttons, customisable from the new Notification menu 3 customisable action buttons for the compact notification Android 8 and above: Theme matches the cover art Android 10 and above: Seekbar right in the notification Android 11 support! The code is easier to maintain Con: Android 9 and below: Loss of the progress bar. Do the pros outweigh the con? (Hint: This is a rhetorical question.) Some background: The old notification API doesn’t work on Android 11. Users don’t see a notification at all. So the newer API had to be used no matter what. Since maintaining the code for two notification styles would double the burden, the old one has been removed entirely. This cool contribution was brought to us in its original form by @cool-student. Sadly, we couldn’t get in touch with them when we were ready to focus on this PR, so @wb9688 and @Stypox swooped in to save the day! @wb9688 updated the code to conform to our standards and coding style, and @Stypox did the (painstaking!) work of rebasing the code after the unified player PR was merged into the development branch. Ultimately, @Stypox took over the responsibility for this PR. He updated and polished the UI, fixed bugs, got everyone and their grandfather to test the changes, and pulled us to the finish line! Improvements We are not done yet with what this release brings you (you may want to take a few sips of that beverage now): If you use an environment where resizing an app is possible, NewPipe can do this now as well. @TobiGr If you have ever encountered the “Unsupported URL” toast when sharing to NewPipe, it is handled better now. You can choose to further share to another app, or open it in a browser. @Stypox NewPipe doesn’t generate a timestamped link when sharing a live stream anymore. @nmurali94 The playlist header layout has been improved: the alignment on the sides is consistent now and longer headings can fit themselves on two lines instead of just one. @Stypox Typing in the search bar now works even when internet connection is lost or turned off. Earlier, NewPipe would interrupt by closing the keyboard on every letter/word input and try to send the search query to the service, showing a useless network error each time. Now it waits until you tap the search button. @Stypox In order to save some of that valuable mobile data, you were already able to turn off video thumbnails and profile pictures for comments. Now even the black placeholders which replaced them are gone and comments can comfortably take up the space left behind. @4D17Y4 The ‘Minimize on app switch’ setting has been changed to switch to the background player by default, to accompany the unified player changes above. @TobiGr The ‘Remember popup size and position’ setting has a less redundant name now. @TobiGr It is 2020, everyone. Really, the only good change that came about this year is higher resolution. The default video resolution has been set to 720p at 60FPS, and 480p for the pop-up player. @B0pol NewPipe now remembers what kind of media you downloaded the last time, and will auto-select it when you hit download on a new video. @vmazoyer “Autoplay” has been changed to “Auto-queue” in the video page. This is to prevent confusion with the new “Autoplay” setting which controls whether videos automatically start in the embedded player. @opusforlife2 Translations Apart from the language improvements mentioned above, some other interesting localization changes happened in this release. @comradekingu, a frequent contributor to and language checker of NewPipe and other open source projects, has once again taken a close look at our strings. There was, as always, a lot of room for improvement. Our wonderful translators rushed to help and immediately implemented his suggestions. We are also happy to provide new localizations in this release: Sardinian, Bengali, Portuguese (Portugal), Neapolitan and Berber. If you are missing a translation or think a phrase needs adjustment, head over to Weblate and help us improve NewPipe’s translation even more! Fixes “Did you mean” and “Showing results for” now have a dark text colour in the light theme, so they can be seen without squinting. @TobiGr Sometimes error reports did not contain the actual code that caused the error. This is now fixed. @Stypox NewPipe would crash if it encountered an empty comment. No more! (Why would anyone leave empty comments, though?) @Stypox If you added a local playlist as a main page tab, playing any video in it would cause a crash. Fixed now. @wb9688 If you open the app in the Taqbaylit language, its called Taqbaylit now and not Tamaziɣt Taqbaylit. @BoFFire The license pop-up doesn’t disappear anymore upon rotation. @nmurali94 If you download a file, delete it from your file explorer, then redownload it without restarting NewPipe, it doesn’t cause a crash anymore. @budde92 Some redundant code related to subtitles was removed. @mhmdanas When auto-queue is enabled, NewPipe tries to add a stream to the queue the moment you open a video. But if there happen to be no video suggestions on that page, it causes a crash. This has been fixed. @wb9688 Development Development. Where all the magic which keeps this app running happens. It saw some improvements in this release (Warning: Nerd talk ahead) : YouTube serves several stream types: progressive HTTP, OTF and DASH. The app can only play the first, but the extractor can fetch both progressive HTTP and OTF. So the extractor will now ignore OTF streams instead of showing them but not being able to play them (endlessly spinning loading indicator, know that you are hated by one and all). This has been a major point of inconvenience for a lot of users (and us, too!) so we’re eager to mitigate the problem until a proper fix sometime later, which will add DASH support. (@wb9688) A Checkstyle rule was added so it would show an error when a local variable which could be final wasn’t declared as such. (@XiangRongLin) A library we use, PrettyTime, has been updated to a newer version so that a workaround can be removed from NewPipe’s code. We get a performance improvement as a bonus! (@B0pol) Numbers and uppercase letters are now allowed in the application ID. (@Stypox) Contributors need to discuss their contributions now prior to opening a PR. (@gkeegan) Some deprecations as well as a lot of code cleanup happened. (@TacoTheDank) The code now prevents the YouTube website from accessing the available Java packages from NewPipe’s parser. This removes a possible attack surface. (@wb9688) Where to get this brand-new version NewPipe notifies you about new versions. You can download them when you press the notification, which will take you to the GitHub release page. If you use the F-Droid app, it, too, notifies you about updates for NewPipe. Please keep in mind that it can take F-Droid a while to update their repository. If you have problems installing you may need to uninstall NewPipe and then install it afresh. (Make sure to backup data by exporting your database from the Content settings menu.) If you already installed NewPipe from F-Droid’s repository, to get this version of NewPipe you can do one of the following: Wait for them to update Switch to NewPipe’s custom repository by following the directions in the announcement post Note: If you installed NewPipe from GitHub Releases you will not have to uninstall NewPipe to switch to our custom repo. Just let it update your current version. Now that you’ve updated, please let us know what your experience of the latest release is, especially bugs in need of fixing. As usual, you can reach out to us via IRC (#newpipe on freenode), open issues on GitHub or, ideally, use our built-in crash reporter to send us machine-readable issue reports. You can even send in fixes yourself. If you have any other questions feel free to send them in the comments here and someone will reply to you. [Less]

Dear NewPipers, NewPipe Users, Hello World! It’s a weird time right now. Many things have changed and don’t work like they used to before. However, NewPipe and the NewPipe project just continue like nothing happens. NewPipe constantly gets bigger ... [More] and better. People keep working on it and organize the project like COVID-19 doesn’t exist. For example, just a week ago we had the very first developer video call and, just one week before that, NewPipe hit number one trending on Hackernews. Next to all of these things going on one might be tempting to forget: NewPipe is turning five years old today! Yes, it’s true! Our little project that started as a simple tool to solve a simple problem is already this old! On September 4th, 2015 I uploaded v0.3 as a tag on GitHub. By this date NewPipe was really simple and small and could not do much, but already existed for about a month until I finally decided to push the release. Little did I know this would turn out to be such an amazing project with many amazing people who create such an awesome tool. I thought for this reason I am telling you how all of this started. NewPipe's logo over the time I started NewPipe … well five years ago. In summer 2015. Back then I had just finished school and had nothing to do until university started. As I was interested in alternative and open software already I joined a group of FSFE fellows that formed back then. They initially showed me F-Droid which I thought was unusable at first, however, after some time I wrapped my head around the idea of getting rid of Google and all the non-free software and just do whatever I find nice. So I replaced Google Mail with mailbox.org. For my calendar/contacts/data foo I set up an ownCloud instance on an ODROID c3. I also installed CyanogenMod OS without Google services on my phone I got back then and put F-Droid on it. Well, in the beginning not using Google on my phone was all kind of different. Finding the right apps for everything was hard, but eventually things worked out nice and I got used to my new setup. However, there was one thing I missed: YouTube. People told me to just use the YouTube mobile website, but have you ever tried it? It’s horrible! It’s ugly, slow and just weird. On the phones that existed back then this was really no fun, and so I soon looked for an alternative to it. I first tried to find some open source apps. There were none. Then I looked for apps that would just not require Google Play Services, and also I could not find anything. Luckily during my spare time I started to learn Android programming, and so I decided to write my own app. The idea was pretty simple: Take youtube-dl and port it to Android. I didn’t know how to port Python to Android. Therefore, I simply tried to figure out how youtube-dl does its magic and rewrote the core logic in Java. That code would extract the video stream URL from a simple YouTube URL, and that’s it. I wrapped an app around this code. One could use the Android share function to enter a link into the app. It would then extract the stream URL and open the video in VLC player. Later I went on and wrote a simple scraper that would also search videos on the website and display the result. When you tap on the result the app would show you some details about the video, like the description and how much up/down votes it got. From here you could simply launch into VLC and watch the video. That was it. With this simple and slick app I didn’t have to use the YouTube mobile website anymore and my problem was solved. I was done. I wanted to publish my code on GitHub and the app on F-Droid to also let others have the opportunity to use it. So I named the app GnuTube and prepared everything for a release. I also added some features like the ability to download a video. Furthermore, I set myself a goal of about 10 features/functions I wanted to properly implement before the initial release 1.0, however, as I showed the app to my FSFE friends they said they wouldn’t want to wait and I should release it as soon as possible. Somehow, I thought, ‘Well, v0.3 would pretty much represent my progress.’ They also told me “GnuTube” could be a problematic name and is a weird idea as the app wasn’t and would never be part of the GNU project. Florian Snow, the founding father of that FSFE fellowship group then suggested me some names from which I picked one more or less at random. Guess what, that name was “NewPipe”. He would later tell me that I couldn’t have picked a worse name, but by then I already liked it. I found it good because it suggested something “New”, and well it was not a “Tube” like in YouTube, but a “Pipe” which is funny and prevents name collision. So here we go. on September 4th, 2015 NewPipe came to light, and it was liked pretty much from the beginning on. The way I “measured” popularity was, and still is by today, the stars the project got on GitHub. The stars didn’t skyrocket, not like I expected that, but they kept growing and growing … and growing. They just didn’t stop to get more. So I thought maybe I really dug up something here and should keep working on it. I did for the next four years. In the beginning I head to learn several things like handling Git right or what to do with contributions from others. I was a beginner to programming and community projects. This is why NewPipe grew together with me and my skills. I had great fun working with all the contributors and learning from them. It was new and exciting, and it still is up to this day. However last year I decided it was time to leave my position as leading developer or maintainer as my Bachelor thesis was just about to knock on the door. I also just wanted to try different things. I gave the “keys” of the project to TheAssassin and Tobias Groza. Tobi had already supported the project and was already more or less in charge of the development. So he became the new “Mr. NewPipe”, and I think he does an awesome job being that. Having said this, I think it’s time to say thanks to all of you! All of you developers and contributors that came and went over the years, and all the users that loved (and maybe hated) NewPipe :) I’m very happy about what you made out of NewPipe during the past five years! Let’s keep it up for at least the next five years ;) [Less]

Dear NewPipers, NewPipe Users, Hello World! It’s a weird time right now. Many things have changed and don’t work like they used to before. However, NewPipe and the NewPipe project just continue like nothing happens. NewPipe constantly gets bigger ... [More] and better. People keep working on it and organize the project like COVID-19 doesn’t exist. For example, just a week ago we had the very first developer video call and, just one week before that, NewPipe hit number one trending on Hackernews. Next to all of these things going on one might be tempting to forget: NewPipe is turning five years old today! Yes, it’s true! Our little project that started as a simple tool to solve a simple problem is already this old! On September 4th, 2015 I uploaded v0.3 as a tag on GitHub. By this date NewPipe was really simple and small and could not do much, but already existed for about a month until I finally decided to push the release. Little did I know this would turn out to be such an amazing project with many amazing people who create such an awesome tool. I thought for this reason I am telling you how all of this started. NewPipe's logo over the time I started NewPipe … well five years ago. In summer 2015. Back then I had just finished school and had nothing to do until university started. As I was interested in alternative and open software already I joined a group of FSFE fellows that formed back then. They initially showed me F-Droid which I thought was unusable at first, however, after some time I wrapped my head around the idea of getting rid of Google and all the non-free software and just do whatever I find nice. So I replaced Google Mail with mailbox.org. For my calendar/contacts/data foo I set up an ownCloud instance on an ODROID c3. I also installed CyanogenMod OS without Google services on my phone I got back then and put F-Droid on it. Well, in the beginning not using Google on my phone was all kind of different. Finding the right apps for everything was hard, but eventually things worked out nice and I got used to my new setup. However, there was one thing I missed: YouTube. People told me to just use the YouTube mobile website, but have you ever tried it? It’s horrible! It’s ugly, slow and just weird. On the phones that existed back then this was really no fun, and so I soon looked for an alternative to it. I first tried to find some open source apps. There were none. Then I looked for apps that would just not require Google Play Services, and also I could not find anything. Luckily during my spare time I started to learn Android programming, and so I decided to write my own app. The idea was pretty simple: Take youtube-dl and port it to Android. I didn’t know how to port Python to Android. Therefore, I simply tried to figure out how youtube-dl does its magic and rewrote the core logic in Java. That code would extract the video stream URL from a simple YouTube URL, and that’s it. I wrapped an app around this code. One could use the Android share function to enter a link into the app. It would then extract the stream URL and open the video in VLC player. Later I went on and wrote a simple scraper that would also search videos on the website and display the result. When you tap on the result the app would show you some details about the video, like the description and how much up/down votes it got. From here you could simply launch into VLC and watch the video. That was it. With this simple and slick app I didn’t have to use the YouTube mobile website anymore and my problem was solved. I was done. I wanted to publish my code on GitHub and the app on F-Droid to also let others have the opportunity to use it. So I named the app GnuTube and prepared everything for a release. I also added some features like the ability to download a video. Furthermore, I set myself a goal of about 10 features/functions I wanted to properly implement before the initial release 1.0, however, as I showed the app to my FSFE friends they said they wouldn’t want to wait and I should release it as soon as possible. Somehow, I thought, ‘Well, v0.3 would pretty much represent my progress.’ They also told me “GnuTube” could be a problematic name and is a weird idea as the app wasn’t and would never be part of the GNU project. Florian Snow, the founding father of that FSFE fellowship group then suggested me some names from which I picked one more or less at random. Guess what, that name was “NewPipe”. He would later tell me that I couldn’t have picked a worse name, but by then I already liked it. I found it good because it suggested something “New”, and well it was not a “Tube” like in YouTube, but a “Pipe” which is funny and prevents name collision. So here we go. on September 4th, 2015 NewPipe came to light, and it was liked pretty much from the beginning on. The way I “measured” popularity was, and still is by today, the stars the project got on GitHub. The stars didn’t skyrocket, not like I expected that, but they kept growing and growing … and growing. They just didn’t stop to get more. So I thought maybe I really dug up something here and should keep working on it. I did for the next four years. In the beginning I head to learn several things like handling Git right or what to do with contributions from others. I was a beginner to programming and community projects. This is why NewPipe grew together with me and my skills. I had great fun working with all the contributors and learning from them. It was new and exciting, and it still is up to this day. However last year I decided it was time to leave my position as leading developer or maintainer as my Bachelor thesis was just about to knock on the door. I also just wanted to try different things. I gave the “keys” of the project to TheAssassin and Tobias Groza. Tobi had already supported the project and was already more or less in charge of the development. So he became the new “Mr. NewPipe”, and I think he does an awesome job being that. Having said this, I think it’s time to say thanks to all of you! All of you developers and contributors that came and went over the years, and all the users that loved (and maybe hated) NewPipe :) I’m very happy about what you made out of NewPipe during the past five years! Let’s keep it up for at least the next five years ;) [Less]

YouTube is back to working again! Apart from that, NewPipe 0.19.7 and 0.19.8 come with auto-play for all services and numerous fixes. Once again: YouTube fixes Ah - what a night! Did you sleep well? Well, we didn’t. On Monday, YouTube decided to ... [More] change some things in their player again. These kinds of changes typically modify how the data of contained streams is extracted. As a result, NewPipe and other services like youtube-dl or Invidious cannot access the stream and video data. Way too many of you have seen the result: nothing works. The folks at youtube-dl were quick and delivered a fix incredibly fast. @TobiGr converted the fix from Python to Java and used @wb9688’s work from a previous pull request to improve the handling of the patterns to decrypt the player info. We were able to release a new version of NewPipe Extractor, the library which gathers all the info you can see in the app, at 2am. Unfortunately, this did not mean, we could release a new version of NewPipe straight away. Programmers sign their applications so devices and users can verify they have an official version which has not been compromised by a third party. In our case, signing is done by @TheAssassin. However, he was not available in the morning and luckily managed to sign the created APK later in the afternoon. That created the big delay between creating a fix and releasing a new version. We hope, you can understand that. We did not want to let you wait an extra time with a broken NewPipe version ;) Apart from that, @wb9688 fixed loading more search results as well as age restricted videos not having any video info. Yes - YouTube was busy with changing stuff lately and so were we. Auto-play and TV improvements @wb9688 also made a load of internal improvements to enable auto-play for all services. Previously, only YouTube was supported. Alexander– stepped in again for Android TV users and fixed focus box lingering in places where it should not be. It’s vanishing now correctly. What’s up next While we concentrated on minor improvements and bug fixes lately, big things are in the making! @avently has been working on a new app workflow for multiple months. These changes are in their final stage and need some more testing to ensure we ship an entirely working player for all Android versions and devices. In case you have time and are willing to help, please head over to GitHub and test the latest APK. Where to get the latest version NewPipe notifies you about new versions, you can download them when you press the notification. An alternative is the GitHub release page. If you use the F-Droid app, it notifies you as well about an update for NewPipe - please keep in mind that it can take F-Droid a while to update their repository. If you have problems installing you may need to uninstall NewPipe then reinstall (make sure to backup data). If you already had NewPipe installed through F-Droid’s repository, to get this version of NewPipe you can do one of the following: Wait for them to update or Switch to the NewPipe repository by following the directions in the announcement (if you had previously installed NewPipe from GitHub releases you will not have to uninstall NewPipe to switch) Now that you’ve updated, please let us know what your experience of the latest release is, especially bugs in need of fixing. As usual, you can reach out to us via IRC (#newpipe on Libera.Chat), open issues on GitHub or ideally use our built-in crash reporter to send us machine-readable issue reports. You can even send in fixes yourself. If you have any other questions feel free to send them in the comments here and someone will reply to you (in the past we have been pretty slow with this, but I will be better for this one). [Less]

YouTube is back to working again! Apart from that, NewPipe 0.19.7 and 0.19.8 come with auto-play for all services and numerous fixes. Once again: YouTube fixes Ah - what a night! Did you sleep well? Well, we didn’t. On Monday, YouTube decided to ... [More] change some things in their player again. These kinds of changes typically modify how the data of contained streams is extracted. As a result, NewPipe and other services like youtube-dl or Invidious cannot access the stream and video data. Way too many of you have seen the result: nothing works. The folks at youtube-dl were quick and delivered a fix incredibly fast. @TobiGr converted the fix from Python to Java and used @wb9688’s work from a previous pull request to improve the handling of the patterns to decrypt the player info. We were able to release a new version of NewPipe Extractor, the library which gathers all the info you can see in the app, at 2am. Unfortunately, this did not mean, we could release a new version of NewPipe straight away. Programmers sign their applications so devices and users can verify they have an official version which has not been compromised by a third party. In our case, signing is done by @TheAssassin. However, he was not available in the morning and luckily managed to sign the created APK later in the afternoon. That created the big delay between creating a fix and releasing a new version. We hope, you can understand that. We did not want to let you wait an extra time with a broken NewPipe version ;) Apart from that, @wb9688 fixed loading more search results as well as age restricted videos not having any video info. Yes - YouTube was busy with changing stuff lately and so were we. Auto-play and TV improvements @wb9688 also made a load of internal improvements to enable auto-play for all services. Previously, only YouTube was supported. Alexander– stepped in again for Android TV users and fixed focus box lingering in places where it should not be. It’s vanishing now correctly. What’s up next While we concentrated on minor improvements and bug fixes lately, big things are in the making! @avently has been working on a new app workflow for multiple months. These changes are in their final stage and need some more testing to ensure we ship an entirely working player for all Android versions and devices. In case you have time and are willing to help, please head over to GitHub and test the latest APK. Where to get the latest version NewPipe notifies you about new versions, you can download them when you press the notification. An alternative is the GitHub release page. If you use the F-Droid app, it notifies you as well about an update for NewPipe - please keep in mind that it can take F-Droid a while to update their repository. If you have problems installing you may need to uninstall NewPipe then reinstall (make sure to backup data). If you already had NewPipe installed through F-Droid’s repository, to get this version of NewPipe you can do one of the following: Wait for them to update or Switch to the NewPipe repository by following the directions in the announcement (if you had previously installed NewPipe from GitHub releases you will not have to uninstall NewPipe to switch) Now that you’ve updated, please let us know what your experience of the latest release is, especially bugs in need of fixing. As usual, you can reach out to us via IRC (#newpipe on Libera.Chat), open issues on GitHub or ideally use our built-in crash reporter to send us machine-readable issue reports. You can even send in fixes yourself. If you have any other questions feel free to send them in the comments here and someone will reply to you (in the past we have been pretty slow with this, but I will be better for this one). [Less]

YouTube is back to working again! Apart from that, NewPipe 0.19.7 and 0.19.8 come with auto-play for all services and numerous fixes. Once again: YouTube fixes Ah - what a night! Did you sleep well? Well, we didn’t. On Monday, YouTube decided to ... [More] change some things in their player again. These kinds of changes typically modify how the data of contained streams is extracted. As a result, NewPipe and other services like youtube-dl or Invidious cannot access the stream and video data. Way too many of you have seen the result: nothing works. The folks at youtube-dl were quick and delivered a fix incredibly fast. @TobiGr converted the fix from Python to Java and used @wb9688’s work from a previous pull request to improve the handling of the patterns to decrypt the player info. We were able to release a new version of NewPipe Extractor, the library which gathers all the info you can see in the app, at 2am. Unfortunately, this did not mean, we could release a new version of NewPipe straight away. Programmers sign their applications so devices and users can verify they have an official version which has not been compromised by a third party. In our case, signing is done by @TheAssassin. However, he was not available in the morning and luckily managed to sign the created APK later in the afternoon. That created the big delay between creating a fix and releasing a new version. We hope, you can understand that. We did not want to let you wait an extra time with a broken NewPipe version ;) Apart from that, @wb9688 fixed loading more search results as well as age restricted videos not having any video info. Yes - YouTube was busy with changing stuff lately and so were we. Auto-play and TV improvements @wb9688 also made a load of internal improvements to enable auto-play for all services. Previously, only YouTube was supported. Alexander– stepped in again for Android TV users and fixed focus box lingering in places where it should not be. It’s vanishing now correctly. What’s up next While we concentrated on minor improvements and bug fixes lately, big things are in the making! @avently has been working on a new app workflow for multiple months. These changes are in their final stage and need some more testing to ensure we ship an entirely working player for all Android versions and devices. In case you have time and are willing to help, please head over to GitHub and test the latest APK. Where to get the latest version NewPipe notifies you about new versions, you can download them when you press the notification. An alternative is the GitHub release page. If you use the F-Droid app, it notifies you as well about an update for NewPipe - please keep in mind that it can take F-Droid a while to update their repository. If you have problems installing you may need to uninstall NewPipe then reinstall (make sure to backup data). If you already had NewPipe installed through F-Droid’s repository, to get this version of NewPipe you can do one of the following: Wait for them to update or Switch to the NewPipe repository by following the directions in the announcement (if you had previously installed NewPipe from GitHub releases you will not have to uninstall NewPipe to switch) Now that you’ve updated, please let us know what your experience of the latest release is, especially bugs in need of fixing. As usual, you can reach out to us via IRC (#newpipe on freenode), open issues on GitHub or ideally use our built-in crash reporter to send us machine-readable issue reports. You can even send in fixes yourself. If you have any other questions feel free to send them in the comments here and someone will reply to you (in the past we have been pretty slow with this, but I will be better for this one). [Less]

YouTube is back to working again! Apart from that, NewPipe 0.19.7 and 0.19.8 come with auto-play for all services and numerous fixes. Once again: YouTube fixes Ah - what a night! Did you sleep well? Well, we didn’t. On Monday, YouTube decided to ... [More] change some things in their player again. These kinds of changes typically modify how the data of contained streams is extracted. As a result, NewPipe and other services like youtube-dl or Invidious cannot access the stream and video data. Way too many of you have seen the result: nothing works. The folks at youtube-dl were quick and delivered a fix incredibly fast. @TobiGr converted the fix from Python to Java and used @wb9688’s work from a previous pull request to improve the handling of the patterns to decrypt the player info. We were able to release a new version of NewPipe Extractor, the library which gathers all the info you can see in the app, at 2am. Unfortunately, this did not mean, we could release a new version of NewPipe straight away. Programmers sign their applications so devices and users can verify they have an official version which has not been compromised by a third party. In our case, signing is done by @TheAssassin. However, he was not available in the morning and luckily managed to sign the created APK later in the afternoon. That created the big delay between creating a fix and releasing a new version. We hope, you can understand that. We did not want to let you wait an extra time with a broken NewPipe version ;) Apart from that, @wb9688 fixed loading more search results as well as age restricted videos not having any video info. Yes - YouTube was busy with changing stuff lately and so were we. Auto-play and TV improvements @wb9688 also made a load of internal improvements to enable auto-play for all services. Previously, only YouTube was supported. Alexander– stepped in again for Android TV users and fixed focus box lingering in places where it should not be. It’s vanishing now correctly. What’s up next While we concentrated on minor improvements and bug fixes lately, big things are in the making! @avently has been working on a new app workflow for multiple months. These changes are in their final stage and need some more testing to ensure we ship an entirely working player for all Android versions and devices. In case you have time and are willing to help, please head over to GitHub and test the latest APK. Where to get the latest version NewPipe notifies you about new versions, you can download them when you press the notification. An alternative is the GitHub release page. If you use the F-Droid app, it notifies you as well about an update for NewPipe - please keep in mind that it can take F-Droid a while to update their repository. If you have problems installing you may need to uninstall NewPipe then reinstall (make sure to backup data). If you already had NewPipe installed through F-Droid’s repository, to get this version of NewPipe you can do one of the following: Wait for them to update or Switch to the NewPipe repository by following the directions in the announcement (if you had previously installed NewPipe from GitHub releases you will not have to uninstall NewPipe to switch) Now that you’ve updated, please let us know what your experience of the latest release is, especially bugs in need of fixing. As usual, you can reach out to us via IRC (#newpipe on freenode), open issues on GitHub or ideally use our built-in crash reporter to send us machine-readable issue reports. You can even send in fixes yourself. If you have any other questions feel free to send them in the comments here and someone will reply to you (in the past we have been pretty slow with this, but I will be better for this one). [Less]

YouTube is back to working again! Apart from that, NewPipe 0.19.7 and 0.19.8 come with auto-play for all services and numerous fixes. Once again: YouTube fixes Ah - what a night! Did you sleep well? Well, we didn’t. On Monday, YouTube decided to ... [More] change some things in their player again. These kinds of changes typically modify how the data of contained streams is extracted. As a result, NewPipe and other services like youtube-dl or Invidious cannot access the stream and video data. Way too many of you have seen the result: nothing works. The folks at youtube-dl were quick and delivered a fix incredibly fast. @TobiGr converted the fix from Python to Java and used @wb9688’s work from a previous pull request to improve the handling of the patterns to decrypt the player info. We were able to release a new version of NewPipe Extractor, the library which gathers all the info you can see in the app, at 2am. Unfortunately, this did not mean, we could release a new version of NewPipe straight away. Programmers sign their applications so devices and users can verify they have an official version which has not been compromised by a third party. In our case, signing is done by @TheAssassin. However, he was not available in the morning and luckily managed to sign the created APK later in the afternoon. That created the big delay between creating a fix and releasing a new version. We hope, you can understand that. We did not want to let you wait an extra time with a broken NewPipe version ;) Apart from that, @wb9688 fixed loading more search results as well as age restricted videos not having any video info. Yes - YouTube was busy with changing stuff lately and so were we. Auto-play and TV improvements @wb9688 also made a load of internal improvements to enable auto-play for all services. Previously, only YouTube was supported. Alexander– stepped in again for Android TV users and fixed focus box lingering in places where it should not be. It’s vanishing now correctly. What’s up next While we concentrated on minor improvements and bug fixes lately, big things are in the making! @avently has been working on a new app workflow for multiple months. These changes are in their final stage and need some more testing to ensure we ship an entirely working player for all Android versions and devices. In case you have time and are willing to help, please head over to GitHub and test the latest APK. Where to get the latest version NewPipe notifies you about new versions, you can download them when you press the notification. An alternative is the GitHub release page. If you use the F-Droid app, it notifies you as well about an update for NewPipe - please keep in mind that it can take F-Droid a while to update their repository. If you have problems installing you may need to uninstall NewPipe then reinstall (make sure to backup data). If you already had NewPipe installed through F-Droid’s repository, to get this version of NewPipe you can do one of the following: Wait for them to update or Switch to the NewPipe repository by following the directions in the announcement (if you had previously installed NewPipe from GitHub releases you will not have to uninstall NewPipe to switch) Now that you’ve updated, please let us know what your experience of the latest release is, especially bugs in need of fixing. As usual, you can reach out to us via IRC (#newpipe on Libera.Chat), open issues on GitHub or ideally use our built-in crash reporter to send us machine-readable issue reports. You can even send in fixes yourself. If you have any other questions feel free to send them in the comments here and someone will reply to you (in the past we have been pretty slow with this, but I will be better for this one). [Less]

No more unsynced videos! This release will let your videos make sense and improve searching in NewPipe to make it more reliable and widespread. But that’s by far not the only change. Got your attention? Read on to see what else has been changed. ... [More] Additions You can now add a playlist directly to your main page as a tab, a great change for those who frequently use NewPipe for music. @Royosef in #3506 There now is an option in the subscription picker for feeds to not show channels that are already in another feed (other than “All”). @mauriciocolli in #3404 Speaking (writing) of the subscription picker, it now has a search bar so you can easily find what you are looking for. @mauriciocolli in #3373 More search changes include “did you mean” & “showing result for” suggestions so that you don’t have to restart a search if you make a tpyo. @B0pol in Extractor #311 and @Royosef in #3471 When using the background player, you can fast forward and rewind through the playback from within the menu for it (not through the notification). @TheLastGimbus in #3473 You will now be given a prompt to open links from certain PeerTube instances in NewPipe when they are opened in a browser or shared. Also, PeerTube embed links can be opened in NewPipe now. @B0pol in #3406, in #3845, and in Extractor #344 More Invidious instances are supported so that NewPipe will be suggested to be used if you open those links. @B0pol in #3841 There are even more translations added to NewPipe! These are: Arabic (Lybia), Bengali (India), Central Kurdish, and Javanese. As always, you can help with translations through Weblate. Bug fixes As mentioned earlier, the audio/video desync bug has been fixed. This bug was quite annoying to have to deal with when streaming video and now has been squashed. @Stypox in #3837 A crash that occurred when quickly swiping through search suggestions has been fixed. @Stypox in #3759 Channel names are now visible for all themes when in the background player. The text color used to be always black in certain cases, which clearly did not work too well when using a dark theme. @Stypox in #3822 Queueing another video while having stuff paused in the popup player or background player no longer resumes that paused video. @budde25 in #3787 NewPipe no longer displays an error when a deleted PeerTube comment is loaded. @wb9688 in #340 Improvements When you get an error (🙁), there is now a simpler way to have your report formatted properly for a GitHub issue (no need to use the Error report to markdown converter). Just press “Copy formatted report” in the app, then make an issue (after ensuring it hasn’t already been reported!). @TobiGr in #3579 Speaking of errors, there used to be a functionality that would remove an item from your playing queue if there is an error with its playback. This led to a temporary internet instability to cause many items to fail and thus being removed from the queue, making it possible for many items to be falsely removed. This functionality has been removed to fix the problem. @Stypox in #3704 You’re now able to long press on a video title to copy it to the clipboard. This is helpful when you are sharing a video somewhere where the link doesn’t make an embed box to show other info about the video. @adinilfeld in #3772 There is now more proper structural support for YouTube Mixes (so Mixes will be available in a future update, not this one). @wb9688 in #3441 Also for YouTube, NewPipe supports start= timestamps (used by YouTube’s embedded player) in links now so if you are sent a specific time in a long stream it will start playing there. @wb9688 in Extractor #366 The status bar now matches the toolbar color so NewPipe seems to fit in even more with your device. :) @eames-palmer in #3774 NewPipe no longer writes metadata to downloaded files that designates they were downloaded via the NewPipe application. This saves a tiny amount of space and helps with privacy. @kapodamy in #3843 Debug APKs are now much smaller (by about 8 MB) due to removing Checkstyle from them. This will make using a debug APK in order to help test new features much more friendly to those testing. @wb9688 in #3828 Conclusion + internal news v0.19.6 is a pretty nice stability update and also adds some great features. If it isn’t stable, please report the problem through one of the methods below. Recently there have been some changes to how NewPipe is distributed. NewPipe could be built reproducibly for a while now, but starting with this release we also make use of F-Droid’s functionality for reproducible builds. F-Droid will thus sign the app with both F-Droid’s signature and our signature. This means that new users that will download NewPipe from F-Droid get it signed by our signature and could thus upgrade to the GitHub version, while users that previously downloaded it from F-Droid will still get updates signed by F-Droid. NewPipe also has its own F-Droid repository now to ensure quick updates in the case of an urgent bug fix. Where to get the latest version NewPipe notifies you about new versions, you can download them when you press the notification. An alternative is the GitHub release page. If you use the F-Droid app, it notifies you as well about an update for NewPipe - please keep in mind that it can take F-Droid a while to update their repository. If you have problems installing you may need to uninstall NewPipe then reinstall (make sure to backup data). If you already had NewPipe installed through F-Droid’s repository, to get this version of NewPipe you can do one of the following: Wait for them to update or Switch to the NewPipe repository by following the directions in the announcement (if you had previously installed NewPipe from GitHub releases you will not have to uninstall NewPipe to switch) Now that you’ve updated, please let us know what your experience of the latest release is, especially bugs in need of fixing. As usual, you can reach out to us via IRC (#newpipe on Libera.Chat), open issues on GitHub or ideally use our built-in crash reporter to send us machine-readable issue reports. You can even send in fixes yourself. If you have any other questions feel free to send them in the comments here and someone will reply to you (in the past we have been pretty slow with this, but I will be better for this one). [Less]

No more unsynced videos! This release will let your videos make sense and improve searching in NewPipe to make it more reliable and widespread. But that’s by far not the only change. Got your attention? Read on to see what else has been changed. ... [More] Additions You can now add a playlist directly to your main page as a tab, a great change for those who frequently use NewPipe for music. @Royosef in #3506 There now is an option in the subscription picker for feeds to not show channels that are already in another feed (other than “All”). @mauriciocolli in #3404 Speaking (writing) of the subscription picker, it now has a search bar so you can easily find what you are looking for. @mauriciocolli in #3373 More search changes include “did you mean” & “showing result for” suggestions so that you don’t have to restart a search if you make a tpyo. @B0pol in Extractor #311 and @Royosef in #3471 When using the background player, you can fast forward and rewind through the playback from within the menu for it (not through the notification). @TheLastGimbus in #3473 You will now be given a prompt to open links from certain PeerTube instances in NewPipe when they are opened in a browser or shared. Also, PeerTube embed links can be opened in NewPipe now. @B0pol in #3406, in #3845, and in Extractor #344 More Invidious instances are supported so that NewPipe will be suggested to be used if you open those links. @B0pol in #3841 There are even more translations added to NewPipe! These are: Arabic (Lybia), Bengali (India), Central Kurdish, and Javanese. As always, you can help with translations through Weblate. Bug fixes As mentioned earlier, the audio/video desync bug has been fixed. This bug was quite annoying to have to deal with when streaming video and now has been squashed. @Stypox in #3837 A crash that occurred when quickly swiping through search suggestions has been fixed. @Stypox in #3759 Channel names are now visible for all themes when in the background player. The text color used to be always black in certain cases, which clearly did not work too well when using a dark theme. @Stypox in #3822 Queueing another video while having stuff paused in the popup player or background player no longer resumes that paused video. @budde25 in #3787 NewPipe no longer displays an error when a deleted PeerTube comment is loaded. @wb9688 in #340 Improvements When you get an error (🙁), there is now a simpler way to have your report formatted properly for a GitHub issue (no need to use the Error report to markdown converter). Just press “Copy formatted report” in the app, then make an issue (after ensuring it hasn’t already been reported!). @TobiGr in #3579 Speaking of errors, there used to be a functionality that would remove an item from your playing queue if there is an error with its playback. This led to a temporary internet instability to cause many items to fail and thus being removed from the queue, making it possible for many items to be falsely removed. This functionality has been removed to fix the problem. @Stypox in #3704 You’re now able to long press on a video title to copy it to the clipboard. This is helpful when you are sharing a video somewhere where the link doesn’t make an embed box to show other info about the video. @adinilfeld in #3772 There is now more proper structural support for YouTube Mixes (so Mixes will be available in a future update, not this one). @wb9688 in #3441 Also for YouTube, NewPipe supports start= timestamps (used by YouTube’s embedded player) in links now so if you are sent a specific time in a long stream it will start playing there. @wb9688 in Extractor #366 The status bar now matches the toolbar color so NewPipe seems to fit in even more with your device. :) @eames-palmer in #3774 NewPipe no longer writes metadata to downloaded files that designates they were downloaded via the NewPipe application. This saves a tiny amount of space and helps with privacy. @kapodamy in #3843 Debug APKs are now much smaller (by about 8 MB) due to removing Checkstyle from them. This will make using a debug APK in order to help test new features much more friendly to those testing. @wb9688 in #3828 Conclusion + internal news v0.19.6 is a pretty nice stability update and also adds some great features. If it isn’t stable, please report the problem through one of the methods below. Recently there have been some changes to how NewPipe is distributed. NewPipe could be built reproducibly for a while now, but starting with this release we also make use of F-Droid’s functionality for reproducible builds. F-Droid will thus sign the app with both F-Droid’s signature and our signature. This means that new users that will download NewPipe from F-Droid get it signed by our signature and could thus upgrade to the GitHub version, while users that previously downloaded it from F-Droid will still get updates signed by F-Droid. NewPipe also has its own F-Droid repository now to ensure quick updates in the case of an urgent bug fix. Where to get the latest version NewPipe notifies you about new versions, you can download them when you press the notification. An alternative is the GitHub release page. If you use the F-Droid app, it notifies you as well about an update for NewPipe - please keep in mind that it can take F-Droid a while to update their repository. If you have problems installing you may need to uninstall NewPipe then reinstall (make sure to backup data). If you already had NewPipe installed through F-Droid’s repository, to get this version of NewPipe you can do one of the following: Wait for them to update or Switch to the NewPipe repository by following the directions in the announcement (if you had previously installed NewPipe from GitHub releases you will not have to uninstall NewPipe to switch) Now that you’ve updated, please let us know what your experience of the latest release is, especially bugs in need of fixing. As usual, you can reach out to us via IRC (#newpipe on freenode), open issues on GitHub or ideally use our built-in crash reporter to send us machine-readable issue reports. You can even send in fixes yourself. If you have any other questions feel free to send them in the comments here and someone will reply to you (in the past we have been pretty slow with this, but I will be better for this one). [Less]