I'm hoping that ADBT will get the job done for me. I have been very happy with it so far. @turtletank is amazing with support. As are the many other nice and knowledgeable folks on here.
Can the DTV Osprey Gemini boxes be used with this project or are they only good for AH4C?
Osprey Boxes are really only suitable for AH4C. They don’t respond well to adb tuning with deep links (I tried). The default launcher, which really is just the DTV app, is aggressive about taking over focus to maintain the cable-box experience.
All that said the TV tuning experience is reliable and the video quality is good. I still recommend as possible use in AH4C.
My ethernet hard-wired Google TV Streamers which started with Android 14 keep on trucking with ADBTuner about a year in. Don't know if it's because I hard-wired them or not, but have had no problems. Seems like Google did something weird with their last Android update to CCWGTVs. Restart or no, the Google TV Streamers have never stopped working, or had any troubles, so far.
@jsfullam Found something interesting in my testing tonight. I have a typo in one of my channels.
Disney Jr. (289) Should be:
dtvnow://deeplink.directvnow.com/play/channel/DSJRHD/74b13512-5e2c-8c70-15d0-d1c8b9fda9b2
What's interesting is when you send the DTV app a bad Deep Link, the app will then stop responding to all Deep Links until you force close the app. This is not ideal for automation.
The work around is to add the following to Pre and Post Tune:
"am force-stop '||TARGET_PACKAGE_NAME||'"
Forcing the app to always start fresh makes for reliable tuning, but it is a big slower. On my test setup, it's a few seconds more to tune, so it's doable especially for recording. But for channel flipping, it's nice to get a 4-5 second tune in.
I'll keep testing.
Hmmm... I'm not to bright about stuff like this. Add this where?...and how?
If you're using a developer version of ADBT, there is the option for Custom Configurations. It will be at location /configurations after your ADBT URL. For example: http://xxx.xxx.xxx.xxx:5592/configurations.
On the Configurations Page, ADD NEW CONFIGURATION (top menu) to generate a new config. Paste and replace everything in the template config with my sample below and save it:
{
"name": "DirecTV App",
"author": "",
"version": "0",
"description": "Tune, force close, open, close app at end of tune for DTV App.",
"uuid": "b9a140d2-8088-468d-9e71-af2eb3c2695a",
"global_options": {
"wait_for_video_playback_detection": true,
"use_fixed_delay": false,
"fixed_delay_seconds": 0,
"check_for_and_clear_whos_watching_prompts": false
},
"pre_tune_commands": [
"input keyevent 3",
"am force-stop '||TARGET_PACKAGE_NAME||'"
],
"tune_commands": [
"am start -W -a android.intent.action.VIEW -d '||TARGET_URL_OR_IDENTIFIER||' '||TARGET_PACKAGE_NAME||'"
],
"post_tune_commands": [
"input keyevent 3",
"am force-stop '||TARGET_PACKAGE_NAME||'"
]
}
After saving the config, edit one of your channels on the main ADBT page, and change the Configuration to "DirecTV App". You may need to refresh the page for the new config to show up on drop down menu.
If the config does not work, it may be due to a UUID not being created by your ADBT. In that case, create a new config, then copy everything in my sample config above, but keep your UUID line.
Thanks! I'll give all of this a try tomorrow. I plan to add several DTV channels to ADBT. Especially ones which I cant get through TVE.
By the way, I tried adding the DTV TVE source again. It looks like it finally went through. It's scanning channels! 
@nateg, so to confirm, if I swapped out my CCWGTVs with Google TV Streamers and rebooted them, there will be no need to pair the device after every reboot? If so, I will replace my 3 CCWGTVs.
I’m not sure anyone can guarantee what ADB will work in the future, just what works at the moment. I would speculate the Google official devices are more likely to get the ADB security change.
I just configured about 42 DTV channels for ADBTuner. I tested every one of them using the (default, recommended) mode, as you previously suggested.
Here's the odd thing about it. Every single channel previewed fine but one. For some reason, GET TV would not play in the preview window. The LinkPi interface showed the correct channel playing from the tuner. But, it would not play on the ADBT GUI.
Enabling Compatibility mode got it working. I switched modes a couple times, and default mode will not play this one channel properly, while compatibility mode always does.
What in the world would make just one single channel out of over three dozen require a different mode?! Same app, same interface, same link format... I don't get it... 
First, congrats on getting setup! As to GET TV, may be a bad link. I had one of those yesterday which made the app act all wonky, would open but freeze. I will see if I have that channel active and test when I get home later.
How is tuning otherwise? Good response and PQ from the Onn4K boxes?
Thanks for all the support. I really appreciate it. 
I have only tested these channels through the previews on the ADBT GUI. So far, so good. Several channels I added were not in your list, nor were they in @Jean0987654321 's list from the AH4C thread.
So, I had to figure out how to dig up the DTV deep links the hard way. Fortunately, @bnhf had posted some great instructions on how to get it done. 
I'll get these new channels added to CDVR this afternoon, and hope to test things out on a CDVR client device/TV later this evening. I'm trying to keep them separate from my YTTV playlist, so that I can compare before I put my YTTV account on hold.
Three days left to my YTTV billing period. If I am satisfied within the next day or two, I'll pull the trigger.
Are you using the additional playlist option so you can have two sources of M3U from ADBT? You’d have to be on the most current Dev version from last week.
Oh, and make sure to share any working deep links you find!
Yeah, it is great for keeping things separate from each other.
I absolutely will put together a list to share the new deep links I uncovered.
By the way, I think I may have found a couple small errors in your list:
The EarthXTV and Animal Planet deep links have some placeholders from Jean's list in them:
dtvnow://deeplink.directvnow.com/play/channel/http://{{ .IPADDRESS }}/play/tuner/EARTHX/76c132b0-fa3f-ac34-bc39-b0fecdc68e49
dtvnow://deeplink.directvnow.com/play/channel/http://{{ .IPADDRESS }}/play/tuner/APLHD/6b8b578e-eaa0-8086-4803-340763f93d36
Good catch! Odd those work when I tested last night, but I will for sure go check. Good luck with further testing.
Wow, not sure how I missed that, but sure enough, bad links. They are now fixed. Thanks!
Right. No guarantees, but that has been my experience. I have been using one since back when they came out almost a year ago, and have replaced all of my CCWGTVs, so have 4 in service now, no problems. I prefer the picture quality of the official Google devices over the Walmart and Amazon devices.
Has anyone outside of CCWGTVs had this issue? I think people were worried, but I seem to have seen other devices update to 14 okay since.
My personal opinion is this is a bug, not a feature. From what I've read, Google intended on putting out one update to Android 14 for CCWGTVs before putting it out to pasture.
I prefer the picture quality of the official Google devices over the Walmart and Amazon devices.
I will agree with you there. The Onn boxes are fine for "everyday" tuning, but their picture quality is not the best. The colors are a bit too vibrant and the picture overly sharpened. The old Osprey/Geminis devices put out a more natural picture, a comment I've shared many times. For the price, Onn boxes do just fine.
I'm not holding my breath but I was able to get a ticket open through a friend that works at Google and they claim it's a known bug that they are working on. If I get any updates I'll let you know. I have 12 CCWGTV's and I'm going to replace half of them with Onn boxes hoping there's a fix soon enough.
If you can afford it, the Google TV Streamer paired with a Link Pi ENC1Pro looks so goooood.