Nothing that I can see. It's on the home screen reading the text, but the stream app never opens. Eventually:
2026-06-26 19:07:55.797 - stream - [Tune muaEWjnMgZaW4vGADi9HVb] Maximum wait time exceeded. Giving up after 40.39 seconds. [Tune muaEWjnMgZaW4vGADi9HVb] Display was on, application (com.xfinity.cloudtvr.tenfoot) was closed.
Then it'll flash the stream app for keepalive a few minutes later, so it's not like it's the wrong app name...
I'm not aware of the Xfinity app being particularly reliable with Keep Alive. I've always used it in "compatibility mode", where the app is stopped after tuning, and relaunched on each new tune. I remember experimenting with keeping the app loaded some time ago, and although I had some success with it -- it never reached the level of reliability I wanted.
It appears you're getting hung-up on choosing a user account, which is interesting, as that's not something I ever see. Probably because I don't have multiple users set up.
Based on the onscreen text that's being identified, it looks like you're just sitting on the FireTV home screen though? Is that the case?
If you don't have multiple users defined, I'd suggest creating a custom config that removes the tune_match_text_section. Also, if these are older FireStick 4Ks (some of which are 10 years old now), you may need to extend the sleep in the pre-tune commands by a second or so.
I assume you've rebooted the sticks, restarted the container, and have everything up-to-date? There's also a version of the compatibility mode config that allows you to see everything that's happening during the tune -- so that might be the config to clone and modify while you're sorting this issue out.
Also, can you confirm that you can connect to these sticks and tune manually? That would rule out a number of other possible issues...
Thank you. Where this user account came from i don't know. The primary tuner on this setup is a Firestick4K (edited this because i got mixed up what the new priorities were) which has been running fine until this week. I can, via the firestick remote, fire up the stream app and view channels. The log you are looking at was from me clicking the "preview" button on the ADBTuner Channel config for that particular channel. It won't let me manually tune a channel from teh Channels DVR lineup anymore. I also have 3 firestick4K's and a firestickHD that are doing the same thing, but I'll take a deeper look at their logs compared to what you see here.
And yes - it's just sitting on the home screen. and yes, they've all been rebooted along with the host running ADBtuner in docker-compose, and the stable image has been pulled as of today.
Well, I did some testing and I confirmed the Osprey issues I was noticing with ah4c seem specific to happening with ah4c and also sending direct ADB commands. It seems to be when you wake the device and immediately send a deep link without any sort of delay at all whatsoever is when it wedges, which never happened before. Now, here's my question. Does ADB Tuner in its logic have some sort of slight delay? Like even two to three seconds is enough to work around this, and if it's just built in, the issue would not manifest and no one using ADB Tuner would ever notice it.
That was the exact window I found that got the Osprey boxes working, although I wrote a bit of a more robust check for ah4c so it would tune quicker and never keel over but the 3 second delay explains it!!
This is what I wrote for ah4c to check playback state before firing.
$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'
It looks like the app just never opens. Can you try updating to turtletank99/adbtuner:development and see if that changes anything, I'm not sure it will, but it might be helpful to be on the most recent version. We can continue troubleshooting from there after you have updated.
I'm beginning to think there's something network related goin on, but I gotta wait until the house full of teenagers is asleep and not online yelling at their friends until I can reboot the router...
It looks as though deep links are broken in the current FireTV version of the Xfinity app. I'm not a Comcast user so I can't fully test this, but I can confirm that the app just doesn't open.
Something is not adding up about this, as Xfinity deeplinks still work fine with ah4c. I checked the version I have installed, which is 8.15.0.3646. I confirmed this is the most recent version by installing Xfinity Stream on a FireStick that hasn't had it installed before.
Thanks. This is helpful. Explicitly specifying the activity opens the app normally in the current version. am start -n com.xfinity.cloudtvr.tenfoot/com.xfinity.common.view.LaunchActivity
A custom configuration that does this should solve the issue, but I'm going to see if I can't figure out how to avoid doing that.
An added datapoint is that I did have 2 of my firesticks displaying a failed update screen earlier in the week - probably around the time this all started. Guess I need to turn off auto updates.
Once I get back in front of my server I'll try the older version and see what version they're running.