that isn't an m3u file. that's the script location.
update the script location, drop your new m3u in the bind mount m3u folder, name it whatever.m3u and point channels at it.
Got it figured out. I added dtvospreydeeplinks.m3u to the m3u folder and changed the CDR source to the new m3u file and all is working right now.
So you need to also update the .env file.
STREAMER_APP=scripts/osprey/dtvospreydeeplinks
Did that first from your earlier post. Added my m3u file but had forgot to change the CDR source url so it sent me to wrong stations. Once I changed that, everything was good. My tuning is now about 8-9 secs versus 11-13 secs with the channel numbers.
My biggest issue was getting the m3u data from Chrome. DTV would lock me out every time I tried to log on thru Chrome and make me reset password. I finally used Chrome to reset (vs my normal browser) and was able to grab the data. One thing that I did notice is that you can use the old password when resetting which I thought odd.
I find it odd that companies feel the need to keep a record of the old password. (my bank keeps last 10)
alot has changed in the ~30yrs of cybersecurity, but the #1 rule has never changed, and they are finally realizing it again. the most secure password is the one you remember.
I mean this is the company that has you use email and SMS for 2FA and doesn't support TOTP or really passkeys or anything. Security-wise, it's a data breach waiting to happen.
A post was merged into an existing topic: ADBTuner: A "channel tuning" application for networked Google TV / Android TV devices
It seems like DirecTV pushed an update that broke tuning, at least for me from sleep. Cold tunes from sleep just would not work. They'd freeze. I don't know if it's a bug or a permanent change, but based on the APK analysis I had Claude do, it seems like it might be an intentional change to the way they negotiate HDMI on the Osprey boxes.
What resolved it was adding a sleep 2 to prebmitune.sh.
main() {
adbConnect
adbWake
sleep 3
}
if anyone else sees this behavior, let me know and I can open a PR for this one line change. @bnhf please let me know if this is a good candidate for a pull request or if you wanna just update the script at some point. This was actually pretty reproducible for me on the latest Osprey update that seems to just get pushed down at random by DirecTV and just adding the sleep seemed to fix it, although I'm not sure if sleep 2 is long enough. A longer interval might be better, but I also wanted to prioritize fast tuning, so I was kind of pushing it a little bit close to the edge. I think with the initialization that ah4c has to do, sleep 2 should be enough though, from what I can tell.
Edit: I changed the ordering of the sleep command and it's working a little bit better now.
Edit 1: this is tested with osprey/dtvospreydeeplinks but I'm not sure if it affects channel # tuning as well.
Edit: seems sleep 3 is more reliable so far.
Finally okay claude made something more intelligent, ensure the box is awake and alive (streaming) before firing a tune. That way it always tunes.
main() {
adbConnect
adbWake
$adbTarget shell 'for i in $(seq 1 80); do dumpsys audio 2>/dev/null | grep -E "pack: com.att.tv.openvideo.*gain: GAIN " >/dev/null && break; dumpsys media_session 2>/dev/null | grep "PlaybackState {state=3" >/dev/null && break; sleep 0.1; done'
}
Using standard android frameworks (two of them whichever fires first) to detect rediness.
I have the C71KW-400 60164.
Is there a way, a trick, using tvquickactions etc to make the channel up/down work within the Favorites collection??
Using the box or the app, this is my main question.
Other thoughts.
DEAL KILLERS for me that make it rarely used:
. Channel up/down toggle ONLY goes thru the ALL collection, or page up/down in the Guide
. Directv stream is one of the most expensive providers but has crap software,
. they have a Channel up/down toggle but it can't do Favs Channel up/down,
. you can't even rearrange your Favorites, its Alpha or Numeric, that's it.
. You can't create your own multiview as in YoutubeTV, at least they offer a group of pre-made multi-views
It seems like you're asking about using this Osprey model without ah4c, or CDVR for that matter? Am I misunderstanding your questions/thoughts? I'm pretty sure everything you're listing as deal killers, are easily handled when this box is used with an encoder, ah4c (or ADBTuner) and CDVR.
You are correct sir, and thanks for the reply.
I'm just trying to figure if there is a way, on this Directv box, do Ch Up/Down for only the Favorites "Collection" since this thread has some Directv box experts perhaps.
.
So I have the Osprey stuff narrowed down.
My PR has been merged into main, which is great. This should be purely defensive for those on the 5/22 update, and those who get the 6/10 update shouldn't have any interruption as long as you get the new script.
From what I can tell based on the analysis that I've been doing for the last several days is they are checking authentication when the box wakes from sleep. So you really need to pull for video and audio prior to trying to fire a deep link, else the box wedges. So immediately once the box has detected that it's up and running, we fire the deep link. That's how I got around it.
On one hand, this is good news. That means they're updating Osprey boxes still, and hopefully they have a long life ahead. On the other hand, this is annoying that they're doing this and it's making it harder to tune them. When I get a chance, I will try to work on a config for ADB tuner users as well.
Ok has anyone with recent channels updates been seeing deeplinks randomly re-fire on their own. I've been hitting some weird edge case where I'm viewing normally and randomly the channel will re-tune.
I am currently running a test to see if it's maybe related to something upstream in Channels but I'm curious if anyone else has run into this?
I have a potential future PR here: GitHub - mackid1993/ah4c at fix/skip-same-channel-retune · GitHub
It's just super weird and happens pretty randomly but usually towards the start of a stream. I thought it was a DTV issue but started firing deeplinks manually over adb and it wasn't happening then as far as I could tell.
I'm on latest created 6/10/26 on Synology NAS- Deeplinks with Osprey's. I haven't seen this issue.
Super weird. Are you on the latest CDVR update?
2026.06.29.0212
I would think if cdvr was doing it, it would show up in the support logs.
It may have had something to do with having 10 ospreys and running CH4C on 3 encoders. I just reset my DirecTV password and re-logged into all my boxes and while they still stall if I immediately tune without a pause after waking, which I kind of expect at this point, so far I haven't had that splash screen come up and interrupt yet. 
I think they only allow 2 streams via browser
edit; I just tested, had a stream running in firefox, chrome, and edge. I was thinking of this
so with ch4c it's possible the multiple sandboxed chromes are causing a hickup
I honestly think CH4C got my account sort of in a weird state where it maybe got flagged internally.
From what I could tell from looking at ADB on the boxes with Claude, it appears that Widevine L1 kept getting torn down very early into the stream at random intervals. Since resetting the password, it seems like it's slowly improving, although not perfect, but it's super duper weird. Honestly, it was fun playing with CH4C, but given I have 10 Ospreys and two ENC5 V2s, I really don't need to use it. Especially if there's a risk of it causing issues with my account because I have so many devices attached. It is a fantastic tool though. I really do like it.
I only think it's that because I noticed CH4C wasn't working, so I went in and reauthorized it, and like a day or so later, I noticed things were acting weird.