Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Ability to change device type to TV #1189

Open
SelfRef opened this issue Dec 10, 2023 · 8 comments
Open

[Feature] Ability to change device type to TV #1189

SelfRef opened this issue Dec 10, 2023 · 8 comments

Comments

@SelfRef
Copy link

SelfRef commented Dec 10, 2023

Is your feature request related to a problem? Please describe.

I'm trying to set up Waydroid as my new TV box frontend in place of good old Kodi on my Linux PC nettop. Some Android applications like Clipious have separate UI intended for TV where I have connected my PC so it would be a perfect match.

Unfortunately, I cannot force Waydroid to present itself to applications as a TV device. I found the applications are using Android API to determine which device type they are running on. I assume this can be configured somehow, maybe even by using prop variables, but I cannot find what has to be changed.

Describe the solution you'd like.

As the project is gaining more and more popularity it's the matter of time more people will be interested in using Waydroid as Android TV device so it would be a good idea to add to the documentation an information how to change device type to a TV or a tablet. Especially as there's already well documented method to use Waydroid as standalone session.

Describe alternatives you've considered.

I was trying to change some props related to display and density, but so far it didn't work.

Additional context

No response

@Quackdoc
Copy link
Contributor

this is currently not possible, it was for A10 but A11 introduced some changes which broke this, you need to compile explicitly to a TV form factor now. The current best solution would be to swap launchers to a launcher which supports leanback intents. as for applications that don't use leanback intents, that would be a feature request for thhem

@SelfRef
Copy link
Author

SelfRef commented Dec 24, 2023

Thanks for the answer.

In that case, the most reliable option I see is to prepare a separate image for Waydroid with TV UI. There are already 3 types of images, so adding more wouldn't require any extra features on the Waydroid itself.

Right now I use a Raspberry Pi 4 with custom Lineage OS Android TV ROM and it works as expected (not very fast tho). A similar image built for Waydroid would provide the same TV experience.

@netoxhoppus
Copy link

Guys, I got here because I want to mirror movies on my TV, which is on the same network as the computer, but Waydroid doesn't see it. Sorry for the off topic but it was the topic most related to what I want.

@samsunix
Copy link

Desperately need this. Assembly own ATV device could explode community if they understand possibilities it opens. Devs please make this happen.

@possiblyneal
Copy link

I would also like to see this feature implemented.

@ThorbenJ
Copy link

My ISP only provide their TV app for Apply TV and Android TV. On Waydroid the Google Play store refuses to install it because my device type is not supported (only Android TV) is supported. I had hoped I would be able to get Waydroid, which I run on my HTPC, to let my install the ISP's TV app. This issues suggests, its not possible.
So here's my vote for a way to support Android TV, and let us use Waydroid in HTPCs.

@supechicken
Copy link

Hello everyone, I have managed to build an Android TV image for Waydroid from LOS source (using the Android TV board config from AOSP):

If anyone is interested:
https://github.com/supechicken/waydroid-androidtv-build

homescreen

@rijnhard
Copy link

Wondering why @supechicken closed his PR, or why waydroid maintainers didn't comment (not complaining, I understand open source is on a volunteer basis).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants