This is such a cool project. Thanks @turtletank for the effort you put into this. I was able to get this running pretty quickly on a Fire stick.
Quick question. I have a mix of hardware types on several tuners. The hardware requires different package_name and component strings in order to tune. Since the those strings are tied to a specific channel definition, I'm not sure how to handle a multi-tuner setup with various hardware types. Is there a way to configure ADBTuner to so Channels is able to tune to a channel on whatever tuner is available even though the hardware is different?
I hope I'm explaining this clearly enough 
1 Like
Interesting. Can you provide specifics?
The actual package name is different between devices?
1 Like
Sure.
For my mecool and Chromecast boxes I use: com.google.android.youtube.tvunplugged
For the Firetv I use: com.amazon.firetv.youtube.tv
Could be there is a way to use the same package name for both?
4 Likes
Interesting. Which Fire TV? I totally have com.google.android.youtube.tvunplugged running on a Fire Stick.
EDIT: Maybe not. I will look into this.
1 Like
Which FireTV model specifically (model / year)? I'm looking for the Android version (it could be 5.1, 7.1, or 9).
I don't anticipate doing anything that would link specific "channels" to specific "tuners." I was hoping the ability to import and export channel lists would become a useful tool and linking things that way would make a mess out of that feature.
3 Likes
Thanks for doing this - I remoted into home and installed and it's almost working, except I don't have the remote to authorize - apparently, even though this is running on the same machine as my HDMI encoder implementation, it may look like a unique connection to the Onn box (I think)? One question - are you automatically figuring out the station ID to populate the guide? (for example in my hdmi.m3u file I have tvc-guide-stationid="19627",NBC for NBC) - I am not getting the guide right now for some reason...
3 Likes
Correct. ADBTuner is self-contained and generates its own ADB key files on first startup and will appear as a new device.
You could, in theory, copy the ADB key files from your host machine ~/.android/ into the adbtuner_config docker volume if you wish to reuse them, but in most cases it's easier to just accept the connection when you have access to the remote control.
I didn't do anything for station IDs. I can add that as a field on each channel if that would be helpful. I've just been mapping the m3u channels to guide data in the Channels DVR web interface.
4 Likes
I didn't realize that it was possible to select the guide data in the interface - Would station IDs be needed if the channel being added is not in the guide? - for example BBC News has no TVE stream for YTTV, therefore, I don't think it would show up as a choice (or would it?)
2 Likes
I totally agree, The ability to share channels lists is a pretty great feature. The devices are cheap, I'd just get android devices that were all compatible.
Here is the FireTV stick info.
1 Like
Yes, it's in the list of choices. 
2 Likes
I've struck out trying to get this running, mostly because I'm too dense to understand Docker's documentation to get things going on a Mac. I got as far as having this appear in both my Containers and Images tabs on Docker Desktop for Mac, but when I go to the IP address for the web interface for ADBTuner (192.168.7.180:5592) I get a "page not found".
Like I said, this is mostly due to my lack of ability to follow the Docker learning center instructions. My tinkering with Channels has taught me that programmers speak a different language than I do and presume a certain level of background that I don't have. For example, the learning center instructions say, "Open the sample application in your IDE and then open the Dockerfile to explore its contents" with no further explanation. I don't know what an "IDE" is, and, while I presume I click on the name of the sample to "open the Dockerfile", I'm not even sure about that.
1 Like
I think we can make this pretty easy. Presuming you have Docker Desktop installed:
Copy the following and save it as docker-compose.yml. Doesn't really matter where you save it. ~/Desktop/docker/adbtuner/ would be fine.
version: '2'
services:
adbtuner:
image: turtletank99/adbtuner
restart: always
init: true
volumes:
- adbtuner_config:/app/.config
ports:
- "5592:5592"
volumes:
adbtuner_config:
The open a terminal window and navigate to that directory.
cd ~/Desktop/docker/adbtuner/
Then type the following:
docker-compose up -d
That's it. It should be running and configured to automatically restart.
While in that directory you can type docker-compose logs to see application logs for further troubleshooting if needed.
2 Likes
Get Image not found.
docker run -d --init -p 5592:5592 --name adbtuner -v adbtuner_config:/app/.config adbtuner
Should Be
docker run -d --init -p 5592:5592 --name adbtuner -v adbtuner_config:/app/.config turtletank99/adbtuner
1 Like
Thanks. Good catch. I will update the docs.
3 Likes
Is this for only windows machines. Can't get it working in Synology NAS. IP binds to 0.0.0.0:5592
1 Like
0.0.0.0:5592 would indicate it is bound to all network interfaces.
Is the web interface not available at http://ip.of.docker.host:5592?
2 Likes
Did you create the named volume when launching the container?
-v adbtuner_config:/app/.config
2 Likes
I just pasted the docker run command. Wasn't sure how to create the volume. Do I crate new folder in the NAS. I'm not sure how to set this up.
Does this work with Hulu?
How did you get the channel links?
Thanks!
1 Like