NewPipe on Linux, Using Android_translation_layer
1–10 of 100 posts
Re: NewPipe on Linux, Using Android_translation_layer
#2I feel like the interesting part is mostly https://gitlab.com/android_translation_layer/android_transla... which is probably an alternative to waydroid, but maybe more like WINE so it doesn't need the binder kernel module?
EDIT to add: I also think packaging up an application plus the compatibility layer using flatpak[0] is a really nice idea; it lets you 1. make those apps available in a way that nearly appears native, 2. lets you get users/testers on your compat layer easily, while 3. scoping it to a single app at a time to make it easier to do things like "well we've got this one app working, but how do we tell people that without them expecting other things to work that aren't implemented yet?". Excellent symbiosis:)
[0] Strictly speaking there shouldn't be anything requiring flatpak here... I think there's no technical blocker preventing you making a debian package for the ATL and another for NewPipe and sticking them in a repo/PPA that people could add. But I do somewhat feel that flatpak lends itself to this usecase.
Re: NewPipe on Linux, Using Android_translation_layer
#3I feel like the interesting part is mostly https://gitlab.com/android_translation_layer/android_transla... which is probably an alternative to waydroid, but maybe more like WINE so it doesn't need the binder kernel module? EDIT to add: I also think packaging up an application plus the compatibility layer using flatpak[0] is a really nice idea; it lets you 1. make those apps available in a way that nearly appears nati…
It's conceptually similar to wine, but rather a reimplementation of the reference Android, which is AOSP.
See https://gitlab.com/android_translation_layer/android_transla...
Re: NewPipe on Linux, Using Android_translation_layer
#4I feel like the interesting part is mostly https://gitlab.com/android_translation_layer/android_transla... which is probably an alternative to waydroid, but maybe more like WINE so it doesn't need the binder kernel module? EDIT to add: I also think packaging up an application plus the compatibility layer using flatpak[0] is a really nice idea; it lets you 1. make those apps available in a way that nearly appears nati…
Definitely. I'd never heard of this one before; I'd love to read a full comparison between the two.
Re: NewPipe on Linux, Using Android_translation_layer
#5Why would one want NewPipe on desktop when there's https://freetubeapp.io/
Re: NewPipe on Linux, Using Android_translation_layer
#6Why would one want NewPipe on desktop when there's https://freetubeapp.io/
Perhaps because one is accustomed to the NewPipe experience and would prefer consistency across devices?
Never heard of Freetube, but it looks pretty snazzy.
Re: NewPipe on Linux, Using Android_translation_layer
#7for me freetube in the arch repo works great
Re: NewPipe on Linux, Using Android_translation_layer
#8https://gitlab.com/android_translation_layer/android_transla...
https://gitlab.com/android_translation_layer/android_transla...
I wonder how well this approach works over anbox/waydroid's approach.
Re: NewPipe on Linux, Using Android_translation_layer
#9for me freetube in the arch repo works great https://github.com/FreeTubeApp/FreeTube
I think it is in the AUR not arch official repos
Re: NewPipe on Linux, Using Android_translation_layer
#10Why would one want NewPipe on desktop when there's https://freetubeapp.io/
Perhaps because one is accustomed to the NewPipe experience and would prefer consistency across devices? Never heard of Freetube, but it looks pretty snazzy.
I tried it, it didn't feel like what you get on android and had ui glitches