Does Prime Video have support for deeplinks? Fan Duel was now available on Prime and they have the linear regional feeds. Figure i could use that if there was deep linking.
I'm a little late to this discussion. I recently started having problems with the YouTube TV app popping up the "are you still watching?" prompts when recording back to back shows scheduled through the client app. I understand that negative padding can serve the purpose of releasing the tuner in between consecutive shows.
I see that you can change to negative padding when editing an existing pass, or making a new advanced pass. I'm wondering, is there a way to save this as a default for all recordings and passes?
In the server GUI, I only see options to set the default as "none" or positive padding...
Unfortunately I do not see a way maybe @chDVRuser do you have a way to add padding to the DVR via API ?
Is negative padding the only way to get ADBTuner to release a tuner lock between same channel consecutive shows? I had hoped that the overlapping of positive padding would push the next show to another tuner... I guess Channels DVR knows what's coming up and somehow overlaps the recording streams internally? 
ADBTUNER Streams are handled by ChannelsDVR the same as any other Streams if Same Channels is requested it will just continue the Stream... So ADBTuner never gets a request to close the Stream during back-to-back recordings Same Cannel.
ON XFINITY Stream it will popup are you still watching after 5 hours of consecutive streaming ... I do not know about YouTube TV.
1 Like
Thanks! Though I have seen it mentioned a time or two, I've never executed a "curl" before. I'll give it a try... 
1 Like
It won't help in all situations, but in the YTTV app you can at least set the "auto pause" time to 24 hours instead of the default 4 hours. The setting is kind of hidden in the menu while watching live tv.
1 Like
Thank you! I found this after some digging around in the app. I expect that 24 hours should handle most marathon recordings.
2 Likes
Does anyone know the deeplink url format to get univision live on univision now app to work? Thanks in advance
Two of my Chromecasts for Google TV upgraded to Android TV OS 14 and ADBTuner can no longer make the ADB Connection. Anyone else get an upgrade and experience the same behavior?
Wait, what? Did Google disable ADB? Are you able to connect to it via a regular ADB client (like adblink from Jocala)?
Edit: another idea occurred to me - maybe the developer flag got reset with the OS update, and you need to re-enable?
1 Like
From googling, it doesn't appear that ADB got disabled with this update.
When each device rebooted with the update, ADB Tuner could no longer establish the Android connection. I looked at both - developer options and ADB were still enabled on both. I turned off debugging, rebooted, turned back on, re-added the tuners, no luck. I turned off developer options, rebooted, re-enabled, re-added the tuners, no luck.
I'll try a regular client tomorrow. Need to wait out this freak-out moment.
I imagine you've already checked this, but just in case:
IP address change on the stick(s)?
IP address didn't change - I just checked again to be sure 
@bnhf - FYI
ADB over TCP/IP seems to be disabled by default in Android 14 on the CCwGTV 4k.
Opening an adb connection to the device via usb or wireless debugging (with the pairing code) and running adb tcpip 5555 will enable it again, but it doesn't persist after a reboot.
If you are using ADBTuner, ah4c, or similar. Do not upgrade.
I'm looking into some options.
The newer "wireless debugging" feature could be used, but it would require adding support for the dynamic port mapping and interactive pairing code process.
Unfortunately, wireless debugging is also disabled after each reboot so that's something else to figure out (it will need to be toggled back on, but not re-paired after each reboot).
Temporary fix if you have adb installed on your computer:
On the CCwGTV go to Settings -> System -> Developer Options and turn on Wireless Debugging. Then within that Wireless Debugging section, select "Pair device with pairing code."
Make note of the pairing code, IP address, and port.
From your computer run:
adb pair <ip address>:<port>
and then enter the pairing code when prompted.
If the connection is successful (command output would say Successfully paired to <ip address>:<port> and there will be a popup on the device itself confirming connection.
While connected run this command:
adb tcpip 5555
It should say restarting in TCP mode port: 5555 and from there ADBTuner/ah4c should work again until the Chromecast is rebooted.
3 Likes
@turtletank thank you so much for all you have done with this project. It's been amazing.
I have one CCwGTV 4k and 2 Onn $20 boxes. They are all still on 12 as of this morning.
I am pondering replacing the CC with another Onn box to avoid this issue as long as possible. I'd put my FireSticks back in, except I have really enjoyed being able to record from Peacock.
I noticed on Reddit that, "the hardware H.264 decoding support has been removed** rendering a user unable to use their HDHR on their CCwGTV..
Is this the same for FireTV? Anyone know? Thanks!