I don't run this setup but is this a possible conflict?
What is a Streaming Endpoint? Is it a device or virtual IP? I have Channels DVR and ADBTuner running on Docker. I can connect ADBTuner to a FireStick, but I can’t figure out what to put into the Streaming Endpoint box on the dockerIP:5592 page. Do I just make up an IP and add /stream? Is that IP/stream what I add as a source to CDVR?
That is your linkpi url for the specific HDMI port
You can but it will not work lol
Here is how I am configured for reference
ADBTuner:
(10.100.12.23 & 24) are my Onn Devices
192.168.12.16 is my Linkpi
My Channels Config (192.168.12.17 is ADBTuner)
It shouldn't, thats how it was originally designed with bridge networking. I've got mine running on a macvlan but either should work ok
1 Like
Thanks! I was missing that another hardware device is needed. Time to go down another rabbit hole.
Ok so it seems this problem generally occurs if I haven't been tuning to any channels for awhile that are coming from ADBTuner. I'll explain a scenario here:
This afternoon I came home from running errands...hadn't touched Channels/ADBTuner for a couple hours. I went to play a channel and naturally the endless spinning wheel and then eventually the tuner unreachable error message saying to hit play again...hit play again...and then get the link not found 404 error message. Here's a look at the logs from both ADBTuner and Channels:
ADBTuner Log:
2024-09-03 15:05:03 2024-09-03 19:05:02.761 - server - No tuners available.
2024-09-03 15:05:17 2024-09-03 19:05:17.943 - server - No tuners available.
2024-09-03 15:05:18 2024-09-03 19:05:17.990 - uvicorn.access - 172.17.0.1:32990 - "GET /stream/29 HTTP/1.1" 404
2024-09-03 15:05:40 2024-09-03 19:05:40.914 - server - No tuners available.
2024-09-03 15:05:40 2024-09-03 19:05:40.916 - uvicorn.access - 172.17.0.1:44768 - "GET /stream/29 HTTP/1.1" 404
2024-09-03 15:06:15 2024-09-03 19:06:15.181 - server - No tuners available.
2024-09-03 15:06:15 2024-09-03 19:06:15.183 - uvicorn.access - 172.17.0.1:48286 - "GET /stream/29 HTTP/1.1" 404
Channels Log:
2024/09/03 15:04:57.009263 [ERR] Could not start stream for M3U-ADBTuner ch60 NICK: M3U: 901 Tuner Unreachable: Timeout after 20.01s connecting to: http://192.168.1.6:5592/stream/29
2024/09/03 15:05:18.494622 [ERR] Could not start stream for M3U-ADBTuner ch60 NICK: M3U: GET: http://192.168.1.6:5592/stream/29: 404 Not Found
2024/09/03 15:05:40.919025 [ERR] Could not start stream for M3U-ADBTuner ch60 NICK: M3U: GET: http://192.168.1.6:5592/stream/29: 404 Not Found
2024/09/03 15:06:15.185707 [ERR] Could not start stream for M3U-ADBTuner ch60 NICK: M3U: GET: http://192.168.1.6:5592/stream/29: 404 Not Found
Now, I open up my ADBTuner UI and come to find that ADBTuner is still locked in on a channel that I selected a couple hours ago, however that channel is no longer playing on the onn 4k pro device. That third little box far right next to the endpoint connection status and Android version will be blue indicating the old channel, and if I click it, it will release the lock. Now, I go back to trying to play a channel again in "Channels" and all of a sudden, it will play just fine. I'll close it, and see that it was released as well on the ADBTuner UI. I'll select another channel, and it once again tunes fine and then gets released fine. Here's an example of that log:
ADBTuner Log:
2024-09-03 15:31:51 2024-09-03 19:31:49.466 - server - Available Tuners:
2024-09-03 15:31:51 2024-09-03 19:31:49.777 - server - Name: Google TV Priority:
2024-09-03 15:31:51 2024-09-03 19:31:49.777 - server - Selecting random tuner
2024-09-03 15:31:51 2024-09-03 19:31:49.889 - server - Reserved Tuner: Name: Google TV Priority:
2024-09-03 15:31:51 2024-09-03 19:31:49.914 - server - Using tuner id: 1 for stream.
2024-09-03 15:31:51 2024-09-03 19:31:49.965 - uvicorn.access - 172.17.0.1:37062 - "GET /stream/30 HTTP/1.1" 307
2024-09-03 15:31:51 2024-09-03 19:31:50.929 - server - Tuner: Tuning to NICK Jr on Google TV
2024-09-03 15:31:52 2024-09-03 19:31:52.804 - lib.adb - ADB: Connecting to device (attempt 1).
2024-09-03 15:31:53 2024-09-03 19:31:53.414 - lib.adb - ADB: Connected.
2024-09-03 15:31:53 2024-09-03 19:31:53.508 - lib.adb - ADB: 192.168.1.32 - settings list global
2024-09-03 15:31:53 2024-09-03 19:31:53.707 - root - adb_allowed_connection_time=0, adb_enabled=1, adb_wifi_enabled=0
2024-09-03 15:31:53 2024-09-03 19:31:53.707 - lib.adb - ADB: 192.168.1.32 - dumpsys display
2024-09-03 15:31:53 2024-09-03 19:31:53.834 - lib.adb - ADB: 192.168.1.32 - getprop ro.build.version.release
2024-09-03 15:31:53 2024-09-03 19:31:53.898 - lib.adb - ADB: Android Version: 12.0.
2024-09-03 15:31:53 2024-09-03 19:31:53.932 - lib.adb - ADB: 192.168.1.32 - pm list packages -3
2024-09-03 15:31:54 2024-09-03 19:31:54.007 - lib.adb - ADB: 192.168.1.32 - pidof com.philo.philo.google
2024-09-03 15:31:54 2024-09-03 19:31:54.053 - lib.adb - ADB: Stopping media playback.
2024-09-03 15:31:54 2024-09-03 19:31:54.053 - lib.adb - ADB: 192.168.1.32 - input keyevent KEYCODE_MEDIA_STOP
2024-09-03 15:31:54 2024-09-03 19:31:54.265 - root - Using Nick Jr. to load channel.
2024-09-03 15:31:54 2024-09-03 19:31:54.265 - lib.adb - ADB: 192.168.1.32 - am start -a android.intent.action.VIEW -d "Nick Jr." com.philo.philo.google
2024-09-03 15:31:58 2024-09-03 19:31:58.897 - lib.adb - Checking for profile screen
2024-09-03 15:32:16 2024-09-03 19:32:16.783 - lib.adb - On screen text: "ay 4".
2024-09-03 15:32:17 2024-09-03 19:32:17.786 - server - Tuner: Compatibility Mode - Stream released after 27.23 seconds. Display was on, application (com.philo.philo.google) was closed.
2024-09-03 15:32:17 2024-09-03 19:32:17.786 - lib.adb - ADB: Closing connection - 192.168.1.32
2024-09-03 15:32:18 2024-09-03 19:32:18.198 - server - http disconnect
2024-09-03 15:32:18 2024-09-03 19:32:18.405 - lib.adb - ADB: Connecting to device (attempt 1).
2024-09-03 15:32:18 2024-09-03 19:32:18.588 - lib.adb - ADB: Connected.
2024-09-03 15:32:18 2024-09-03 19:32:18.588 - lib.adb - ADB: 192.168.1.32 - settings list global
2024-09-03 15:32:18 2024-09-03 19:32:18.653 - root - adb_allowed_connection_time=0, adb_enabled=1, adb_wifi_enabled=0
2024-09-03 15:32:18 2024-09-03 19:32:18.654 - lib.adb - ADB: Stopping media playback.
2024-09-03 15:32:18 2024-09-03 19:32:18.654 - lib.adb - ADB: 192.168.1.32 - input keyevent KEYCODE_MEDIA_STOP
2024-09-03 15:32:18 2024-09-03 19:32:18.746 - lib.adb - ADB: 192.168.1.32 - input keyevent KEYCODE_MEDIA_PAUSE
2024-09-03 15:32:18 2024-09-03 19:32:18.932 - lib.adb - ADB: Force stopping com.philo.philo.google.
2024-09-03 15:32:18 2024-09-03 19:32:18.932 - lib.adb - ADB: 192.168.1.32 - am force-stop com.philo.philo.google
2024-09-03 15:32:19 2024-09-03 19:32:19.121 - lib.adb - ADB: Closing connection - 192.168.1.32
2024-09-03 15:32:19 2024-09-03 19:32:19.137 - server - Released tuner ID: 1
2024-09-03 15:32:19 2024-09-03 19:32:19.138 - server - Tuner: Cleanup complete. Google TV (NICK Jr)
2024-09-03 15:32:19 2024-09-03 19:32:19.715 - server - Available Tuners:
2024-09-03 15:32:19 2024-09-03 19:32:19.715 - server - Name: Google TV Priority:
2024-09-03 15:32:19 2024-09-03 19:32:19.715 - server - Selecting random tuner
2024-09-03 15:32:19 2024-09-03 19:32:19.716 - server - Reserved Tuner: Name: Google TV Priority:
2024-09-03 15:32:19 2024-09-03 19:32:19.716 - server - Using tuner id: 1 for stream.
2024-09-03 15:32:19 2024-09-03 19:32:19.717 - uvicorn.access - 172.17.0.1:55136 - "GET /stream/30 HTTP/1.1" 307
2024-09-03 15:32:19 2024-09-03 19:32:19.731 - server - Tuner: Tuning to NICK Jr on Google TV
2024-09-03 15:32:19 2024-09-03 19:32:19.771 - lib.adb - ADB: Connecting to device (attempt 1).
2024-09-03 15:32:20 2024-09-03 19:32:20.040 - lib.adb - ADB: Connected.
2024-09-03 15:32:20 2024-09-03 19:32:20.041 - lib.adb - ADB: 192.168.1.32 - settings list global
2024-09-03 15:32:20 2024-09-03 19:32:20.178 - root - adb_allowed_connection_time=0, adb_enabled=1, adb_wifi_enabled=0
2024-09-03 15:32:20 2024-09-03 19:32:20.179 - lib.adb - ADB: 192.168.1.32 - dumpsys display
2024-09-03 15:32:20 2024-09-03 19:32:20.267 - root - Tuner: Stream open (attempt 1).
2024-09-03 15:32:20 2024-09-03 19:32:20.449 - lib.adb - ADB: 192.168.1.32 - getprop ro.build.version.release
2024-09-03 15:32:20 2024-09-03 19:32:20.560 - lib.adb - ADB: Android Version: 12.0.
2024-09-03 15:32:20 2024-09-03 19:32:20.568 - lib.adb - ADB: 192.168.1.32 - pm list packages -3
2024-09-03 15:32:20 2024-09-03 19:32:20.738 - lib.adb - ADB: 192.168.1.32 - pidof com.philo.philo.google
2024-09-03 15:32:20 2024-09-03 19:32:20.834 - lib.adb - ADB: Stopping media playback.
2024-09-03 15:32:20 2024-09-03 19:32:20.834 - lib.adb - ADB: 192.168.1.32 - input keyevent KEYCODE_MEDIA_STOP
2024-09-03 15:32:20 2024-09-03 19:32:20.961 - root - Using Nick Jr. to load channel.
2024-09-03 15:32:20 2024-09-03 19:32:20.961 - lib.adb - ADB: 192.168.1.32 - am start -a android.intent.action.VIEW -d "Nick Jr." com.philo.philo.google
2024-09-03 15:32:21 2024-09-03 19:32:21.220 - httpx - HTTP Request: GET http://192.168.1.26:8090/stream0 "HTTP/1.0 200 OK"
2024-09-03 15:32:25 2024-09-03 19:32:25.616 - lib.adb - Checking for profile screen
2024-09-03 15:32:31 2024-09-03 19:32:31.485 - lib.adb - On screen text: "paw patrol |".
2024-09-03 15:32:32 2024-09-03 19:32:32.490 - lib.adb - Checking for profile screen
2024-09-03 15:32:36 2024-09-03 19:32:36.023 - server - Tuner: Compatibility Mode - Stream released after 16.3 seconds. Display was on, application (com.philo.philo.google) was closed.
2024-09-03 15:32:36 2024-09-03 19:32:36.023 - lib.adb - ADB: Closing connection - 192.168.1.32
2024-09-03 15:32:36 2024-09-03 19:32:36.025 - uvicorn.access - 172.17.0.1:55136 - "GET /stream/1/30 HTTP/1.1" 200
2024-09-03 15:32:36 2024-09-03 19:32:36.250 - root - Tuner: Stream open (attempt 1).
2024-09-03 15:32:36 2024-09-03 19:32:36.255 - httpx - HTTP Request: GET http://192.168.1.26:8090/stream0 "HTTP/1.0 200 OK"
2024-09-03 15:34:08 2024-09-03 19:34:08.660 - server - http disconnect
2024-09-03 15:34:08 2024-09-03 19:34:08.745 - lib.adb - ADB: Connecting to device (attempt 1).
2024-09-03 15:34:08 2024-09-03 19:34:08.790 - lib.adb - ADB: Connected.
2024-09-03 15:34:08 2024-09-03 19:34:08.790 - lib.adb - ADB: 192.168.1.32 - settings list global
2024-09-03 15:34:08 2024-09-03 19:34:08.846 - root - adb_allowed_connection_time=0, adb_enabled=1, adb_wifi_enabled=0
2024-09-03 15:34:08 2024-09-03 19:34:08.846 - lib.adb - ADB: Stopping media playback.
2024-09-03 15:34:08 2024-09-03 19:34:08.846 - lib.adb - ADB: 192.168.1.32 - input keyevent KEYCODE_MEDIA_STOP
2024-09-03 15:34:08 2024-09-03 19:34:08.927 - lib.adb - ADB: 192.168.1.32 - input keyevent KEYCODE_MEDIA_PAUSE
2024-09-03 15:34:09 2024-09-03 19:34:09.072 - lib.adb - ADB: Force stopping com.philo.philo.google.
2024-09-03 15:34:09 2024-09-03 19:34:09.072 - lib.adb - ADB: 192.168.1.32 - am force-stop com.philo.philo.google
2024-09-03 15:34:09 2024-09-03 19:34:09.189 - lib.adb - ADB: Closing connection - 192.168.1.32
2024-09-03 15:34:09 2024-09-03 19:34:09.189 - server - Released tuner ID: 1
2024-09-03 15:34:09 2024-09-03 19:34:09.189 - server - Tuner: Cleanup complete. Google TV (NICK Jr)
Channels Log:
2024/09/03 15:32:10.423924 [ERR] Could not start stream for M3U-ADBTuner ch61 NICK Jr: M3U: 901 Tuner Unreachable: Timeout after 31.41s connecting to: http://192.168.1.6:5592/stream/30
2024/09/03 15:32:36.067140 [TNR] Opened connection to M3U-ADBTuner for ch61 NICK Jr
2024/09/03 15:34:08.633637 [SNR] Buffer statistics for 192.168.1.30 (SAMSUNG-SM-G900V) for ch61 NICK Jr: buf=0% drop=0%
2024/09/03 15:34:08.634147 [TNR] Closed connection to M3U-ADBTuner for ch61 NICK Jr
So this is really weird, but it seems like in general the problem occurs if you haven't tuned to something for a while, and then also perhaps ADBTuner is getting stuck locked on a channel after it's been closed. It's almost like ADBTuner has to be woken up or something. Again as I mentioned a while back, I have every setting that I can think of set to keep devices awake, not go to sleep, etc. whether it's my PC or the onn 4k pro device.
Are you controlling the Onn device in any way via the remote? The only way I have ever gotten that "stuck" lock is when I was playing with the device locally as well as having adbtuner control it. How does it behave if you just control it through the UI of adbtuner where you test tune the channel? Does it allocate the tuner then release it properly when it is done?
FWIW you may want to pick up another ONN device or two so that you have some other tuners available once you sort all of this out.
Also go into developer mode and enable stay awake while charging and see if that helps.
Is the 'Linkpi' connected to the Android device via an HDMI cable?
The encoder connects to the Android device through HDMI.
You will use the web interface of the encoder to manage settings.
I'm not controlling the onn device via remote. If I just control it through the UI of abdtuner and preview a channel, it will typically play, although sometimes it takes forever to load. It will typically release as soon as I close the preview window.
And yes, I've already put the onn device in developer mode and have enabled stay awake while charging, plus there's a couple other settings involving no sleep or staying awake or whatever that I all have set to keep this device awake no matter what.
Yes
Yup...I've done that
1 Like
It could be the compatibility mode, I know it slows down the tuning. I am using YTTV and it works perfectly without compatibility mode and I tune in under 10 seconds. Not sure if you are interested in switching but YTTV looks amazing on ADBTuner due to the enhanced quality that YTTV provides. I switched from Hulu and the difference was beyond amazing.
1 Like
Well unfortunately I turned off compatibility mode for every channel and no difference…same result. Sometimes a channel might load right away and other times it’s the endless spinning wheel and eventual timeout errors or 404 error link not found errors. And what’s even more frustrating about that is, I’ve opened up my linkpi UI and can actually see the channel playing from the onn 4k pro device, but for whatever reason “Channels” won’t play it.
I think anything other than Hulu and YTTV need to use compatibility mode. It could be something strange with Philo and their deep links. I'd have to toss it back to @turtletank for troubleshooting that part.
1 Like
I’ve noticed this happening with NBC channels as well. Just the weirdest thing. The command is getting thru to cause the channel to play on the onn device, but that feed then won’t come across on channels, until maybe after a couple retries, or maybe a ton of retries. There’s just like no consistent pattern to any of this.
I did get the new Nighthawk router that is wifi 6 but i was thinking of returning it because it seemed like perhaps this issue isn’t router related. But now i don’t know. I really don’t want to have to rebuild my network if I don’t have to since I’ve got custom settings (i don’t think you can transfer backup files between the 2 different nighthawks), but seems like we’re running out of possible solution ideas.
And now I just went back to try again after waiting like 15 minutes and this time when I select a channel in “channels” the command didn’t go thru because i see nothing loading on the onn device. I’ll open the ADBTuner UI and the channel will be locked in so I’ll click the little blue square to release the lock, then I’ll try selecting the channel again in “channels” and what do you know, this time it will load on the onn device and then maybe it will come through on “channels” or maybe it won’t. Again, just no clear cut consistency here…soooo frustrating…LOL!
@Accustiver can you zip up all of the logs you have from Channels and ADBTuner and send them to me via PM? I looked at those you had posted, but I'm not finding any clues.
It's not completely unreasonable to see a 30 second tune time on an android device that has been sleeping and/or an app that needs to be restarted (compatibility mode) to load content. But, it shouldn't timeout the way it's doing and any related "tuners" should be released as soon as the connection is closed.
There are a few places in the logs where a channel loads and then Channels DVR gets immediately disconnected (server - http disconnect in the logs). This is unusual.
For troubleshooting purposes you can have ADBTuner provide the video stream immediately instead of waiting for video playback. Perhaps you can see if that changes anything? To do this, add the adb-debug query string to the URL.
ex: https://www.philo.com/player/player/channel/XXXXX?adb-debug=1
Appreciate your input. I’ll give this a shot later tonight after I’m off from work. I’ll do my best to zip up logs too. As you might imagine I’ve got random stuff at random times so organization is a little messy but I’ll hopefully be able to recreate some of these issues later tonight and then copy the logs that are occurring at those times and PM them to you. Also, with regards to that new link format you suggested, am I changing the channel links to that in the ADBTuner UI settings? Thank you!
Just chiming in that Sling works flawless without compatibility mode.
1 Like