View previous topic :: View next topic |
Author |
Message |
chileboy
Joined: 26 Aug 2020 Posts: 125 Location: NJ |
Posted: Fri May 23, 2025 8:22 am Post subject: |
|
|
SysTech_Larry wrote: | I just checked. Fubo is not even available on Roku 4.251, only on Roku 234.199.
Make sure its
Protocol = Roku Official
Device# = 4
Sub device = 251
and try it again. |
Quote: | Did Roku 4.251 work on everything else? |
I'm on my way out for the day so no time for experimenting, but looking back a few posts I confirmed that those settings are correct. I know I checked many of the other commands and they worked, but I didn't stick with that upgrade because other commands I needed (like antennae) were missing. _________________ - Mark |
|
Back to top |
|
 |
SysTech_Larry
Joined: 19 Oct 2023 Posts: 229 Location: Northern Wisconsin, USA |
Posted: Fri May 23, 2025 9:35 am Post subject: |
|
|
I understand the missing Live TV function, but if a correct protocol [Roku 4.251] gave you Fubo, that moves the problem back to TV firmware. Roku 4.251 does not have a Fubo key.
[Moderator note]The discussion about problems loading 2 upgrades both using the Roku protocol has been split to here:
http://www.hifi-remote.com/forums/viewtopic.php?t=103894 _________________ SysTech Larry |
|
Back to top |
|
 |
SysTech_Larry
Joined: 19 Oct 2023 Posts: 229 Location: Northern Wisconsin, USA |
Posted: Wed May 28, 2025 5:35 pm Post subject: |
|
|
Agreed. I downloaded my uploaded copy and it still had the correct setup settings.* After some doubt on the first upload, I uploaded it again, just to be sure.
Also note that neither has a Fubo key, so getting Fubo when pressing Paramount+ cannot be attributed to sending the wrong code...
*Protocol = NEC1
Device = 4
Sub dev = [blank] _________________ SysTech Larry |
|
Back to top |
|
 |
chileboy
Joined: 26 Aug 2020 Posts: 125 Location: NJ |
Posted: Thu May 29, 2025 9:14 am Post subject: |
|
|
SysTech_Larry wrote: | Agreed. I downloaded my uploaded copy and it still had the correct setup settings.* After some doubt on the first upload, I uploaded it again, just to be sure.
Also note that neither has a Fubo key, so getting Fubo when pressing Paramount+ cannot be attributed to sending the wrong code...
*Protocol = NEC1
Device = 4
Sub dev = [blank] |
Paramount+ works fine on the NEC1 Dev 4, that's the upgrade I'm using to launch it in my configuration. In that upgrade, I've only found the other anomalies i listed in my last post.
I've yet to test it again with Roku 4.251, after learning (in the absence of any indication otherwise) I couldn't have both Roku protocol upgrades in the same configuration. _________________ - Mark |
|
Back to top |
|
 |
SysTech_Larry
Joined: 19 Oct 2023 Posts: 229 Location: Northern Wisconsin, USA |
Posted: Fri Jun 13, 2025 8:07 am Post subject: |
|
|
The Java Update tab is telling me (yesterday) that 8 is the highest version available. And I thought that I added a higher version, but I do not see it. _________________ SysTech Larry |
|
Back to top |
|
 |
SysTech_Larry
Joined: 19 Oct 2023 Posts: 229 Location: Northern Wisconsin, USA |
Posted: Fri Jun 13, 2025 5:04 pm Post subject: |
|
|
So, potentially, that puts his first problem* back into his remote, not the TV's firmware...
*Getting Amazon Prime when he presses Paramount+. _________________ SysTech Larry |
|
Back to top |
|
 |
|