search

DefinedNet / mobile_nebula

Brings nebula to mobile devices (iOS, Android)
https://defined.net
118 stars 35 forks source link

Feature request: Google TV Support #148

Open richlanc opened 6 months ago

richlanc commented 6 months ago

I'm using a nebula overlay for all of my endpoints. Ideally I'd like to be able to install nebula on my Google TV so I could use it whilst travelling.

Whilst there isn't official support, I gave it a test by converting the aab to a universal apk and side loading it on a Google TV HD. It installs and you can navigate the app via the remote. Unfortunately you can't press on buttons (assuming the buttons require tap and not clicks).

johnmaguire commented 6 months ago

Hi, Mobile Nebula is built with Flutter, which unfortunately currently does not have official support for Android TV. While I see online that some users were able to make it work, there are many limitations and things which don't work quite right (such as text fields being problematic in many cases.) Beyond that, I think there is a larger issue around getting key material onto/off of the TV.

Would you mind sharing your use case for Nebula on the TV?

richlanc commented 6 months ago

Google TV has a pretty good app for file transfer called "File Manager +", it acts as both a file browser, file chooser and a FTP server. I was planning to use it to load the cart/key files. (it's how I side loaded the apk also).

Ideally, I'd like to use nebula/defined.net to share my media apps (jellyfin) with friends and family. The software defined network overlay/firewall seems perfect for this. (Most of them use Google TV/Firestick). I'd also like to install nebula on my Google TV, so that I can use my media apps whilst travelling. (I've been doing this with WireGuard, but ideally I'd just use nebula as I'm using it for everything else now).

richlanc commented 6 months ago

So I managed to navigate the App using a mouse, set everything up using file sharing via "file manager +". Unfortunately the tunnel gets stuck on "initialising" and the last log is "punchy enabled". It could be the way I converted the aab to a universal apk, but as far as my limited knowledge of android goes, it should have the correct binaries.

(I know this isn't supported behaviour, just documenting for future rabbit hole spelunkers )