-
Notifications
You must be signed in to change notification settings - Fork 60
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
Different versions of Android TV / Fire TV - help with adb commands for this project #295
Comments
Please change title of issue as necessary |
What I really need is for people to submit pull requests. Maybe it will be more clear after someone submits the first one that adds device-specific commands. Although the way that Google-specific commands are handled should serve as a good template. You can keep this issue open, but what's needed is for people to contribute fixes rather than post information and rely on me to make the code changes. |
Looking at the recent changes, CUSTOM_CURRENT_APP will be an option soon, amongst others, and I'm just guessing but i think for the Nvidia Shield, on Android 11, that value would need to be something like this: (I just stuck all the relevant bits together from the constants file @barmazu posted recently: I quickly tested it from the services tab of homeassistant and it returned this when it was asleep: Is there an official place we could start recording these custom commands in a table (PR's could then be raised to add new entries) to save people having to figure it out from scratch each time? Would the README file be a bad place for that? Or would it need to be done within the Sphinx docs? I'm not sure what the proper way of recording things like that would be.
Markdown is definitely not a good way to do it 😁 |
@StephenGoodall this issue is a good place, at least for now. You commented elsewhere about using the output of |
Yeah, I thought of using that and then when I started looking into the code I found that you'd already done it that way 😁 Otherwise, maybe extending the customizable commands list would be another option if more commands start to need different versions |
I didn't get much time today but threw a bit of a PR together to show what kind of thing i was looking at yesterday: It keeps failing the checks, so I've been changing it in parts but it's failing on the "black" step now I think. The line in the makefile refers to androidtv but I'll have to have another look tomorrow (at a guess, some lines are over 120 chars?) |
Tried this for Nvidia Shield TV ANdroid 11. CUSTOM_CURRENT_APP: CUSTOM_AUDIO_STATE: |
Need some solution for CMD_DEFINE_CURRENT_APP_VARIABLE. It is referenced to often inside constants file. |
related issues: we need a custom command for current_app as well |
This is it: python-androidtv/androidtv/constants.py Line 61 in 043bbb5
|
When posting device-specific commands, please include the output of this command: python-androidtv/tests/test_constants.py Line 119 in 043bbb5
|
OK, i will try it. They way I read it, thought that meant get the current app's media_session_state... I did not think it was a combination result of both. Since I do not have a current working device, what should the result look like? edit - got it figured out after lots of trial and error |
For the record, the output should look like: python-androidtv/tests/test_basetv_sync.py Line 122 in 043bbb5
|
Thanks... for some reason I thought it needed the text python-androidtv/androidtv/constants.py Line 162 in 043bbb5
|
I am not super familiar with
adb
commands needed for this project other than what I have quickly read in the current issue of Android TV 9 (vs 10) vs 11.Would it beneficial for this project for everyone with different devices and OSes to run certain commands to help build out the required commands required to parse out data?
What would those commands be?
Just myself - I have Mi Box 3 with OS 8, Mi Box 3 with OS 9. Shield 2019 with OS 9, Onn with OS 10, random Fire TV devices with OS 5, 6, 7.
Thanks @JeffLIrion for all the hard work on this over the years, been using since it was a beta component.
The text was updated successfully, but these errors were encountered: