GithubHelp home page GithubHelp logo

Comments (6)

fransvanberckel avatar fransvanberckel commented on May 15, 2024 1

I searched for, how this is done by Chromecast receiver v2 / Chromecast built-in, on Android TV. They are using com.google.cast.* and com.google.android.apps.mediashell. These are libraries as a background services. Got to be always running. It's well documented, now ...

https://github.com/thibauts/node-castv2
https://github.com/topics/chromecast-receiver
https://developers.google.com/cast/docs/caf_receiver/
https://support.google.com/chromecastbuiltin/answer/6121012 (latest 173230)

from nymphcast.

MayaPosch avatar MayaPosch commented on May 15, 2024

What do you mean exactly with 'Android TV support' in this context? Have the NymphCast server implemented as an Android TV app?

from nymphcast.

torshie avatar torshie commented on May 15, 2024

@MayaPosch Yes. I'm not sure whether it's possible to do that, considering all those restrictions on Android TV.

from nymphcast.

MayaPosch avatar MayaPosch commented on May 15, 2024

A quick look shows that SDL2 is supported on Android, as is ffmpeg. This might be a realistic proposition :)

I guess it would be nice to have a local GUI for NymphCast-on-Android-TV as well. This is something that might be generally useful, even outside of Android TV. A more Roku-like experience, basically.

It appears that Android TV apps are standard Android apps, looking at the documentation. This should mean that one can test it on any Android device before deploying it on an Android TV device, if I'm not mistaken.

from nymphcast.

torshie avatar torshie commented on May 15, 2024

Yes, Android TV apps are standard Android apps, in fact you can install and run many Android apks directly on an Android TV, e.g. a browser app.
However TV apps are usually controlled with a remote, while phone apps are controlled with a touch screen, so the UI part may need some work.

from nymphcast.

MayaPosch avatar MayaPosch commented on May 15, 2024

To implement Android TV support, it appears that the easiest way might be to create a NymphCast client app that communicates with an (unmodified) NymphCast Server instance that runs as a background service. Because the client app would launch the background service, this would prevent the service from being killed by the OS.

Exact implementation details and maybe other options need some more brainstorming on, I think.

from nymphcast.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.