"squirreltown" wrote:
And good luck preventing the box from updating, you'd have to unplug it every time you stopped using it
"kc8pql" wrote:"squirreltown" wrote:
And good luck preventing the box from updating, you'd have to unplug it every time you stopped using it...
That won't work either. Checking for and installing updates is part of the boot process. I does it every time the device is powered up.
"belltown" wrote:
If your router has website blocking functionality, you can block access to roku.com from the Roku device that you don't want to update. That should prevent firmware updates (at least it worked for me a while back when I didn't want one of my Rokus to get updated).
"squirreltown" wrote:"belltown" wrote:
If your router has website blocking functionality, you can block access to roku.com from the Roku device that you don't want to update. That should prevent firmware updates (at least it worked for me a while back when I didn't want one of my Rokus to get updated).
Duh! thats a really good idea. I wish Roku would allow devs to turn off firmware updates temporarily. But then, it's not like anyone would be working on an audio app and a firmware update would blow away a long-standing feature like looping.....wait...
"TheEndless" wrote:"squirreltown" wrote:"belltown" wrote:
If your router has website blocking functionality, you can block access to roku.com from the Roku device that you don't want to update. That should prevent firmware updates (at least it worked for me a while back when I didn't want one of my Rokus to get updated).
Duh! thats a really good idea. I wish Roku would allow devs to turn off firmware updates temporarily. But then, it's not like anyone would be working on an audio app and a firmware update would blow away a long-standing feature like looping.....wait...
In that scenario, wouldn't you want to get the firmware update, so you knew the feature had been borked? Ideally, Roku would give developers access to upcoming firmware releases a few weeks in advance (once it's reached the RC stage), so they could test their channels before such a breaking change was made. That would be beneficial to both parties.... but I think we're veering off topic now...
"squirreltown" wrote:
I've spent a lot of years building things with computers, and not updating the firmware/software in the middle of a job is as basic a rule as I can think of.
When you say "re-keyed" do you mean you generated a new key with genkey, and then the new password is not accepted? Or do you mean you re-keyed from an old pkg file and password? Because obviously that wouldn't be successful if it did not accept your password. There are a lot of folks here with that Roku model and that firmware so I'm reluctant to believe the firmware is the issue. And good luck preventing the box from updating, you'd have to unplug it every time you stopped using it, and if you forget once - Well you've probably seen "Invasion Of The Body Snatchers".
"Beacon333" wrote:
... Now I do store my passwords in a doc file and will match the information based on the unit. I've cut and pasted and typed and still get the message.
"RokuJoel" wrote:
Try resetting the device to factory defaults, relinking it and then enabling developer mode again.
- Joel