Just a PSA to anyone who wants to install it manually. My update took about 30 minutes from the time I clicked Update until it was completed. I think it rebooted at least twice during the install. Seems it took longer than the last update. I haven't noticed any changes yet.Well, I still have H711 on my Hopper 3, but some reported receiving H712. Please feel free to continue discussing the IR remote issues with your Hopper 3 and whatever issues you are having with H712.
Just a PSA to anyone who wants to install it manually. My update took about 30 minutes from the time I clicked Update until it was completed. I think it rebooted at least twice during the install. Seems it took longer than the last update. I haven't noticed any changes yet.
I think all updates can take between 30 minutes to 1 hour. For me, I just finished updating which completed at 6:38PM Pacific Time, I started between 6:03PM-6:08PM Pacific Time and it rebooted once.Just a PSA to anyone who wants to install it manually. My update took about 30 minutes from the time I clicked Update until it was completed. I think it rebooted at least twice during the install. Seems it took longer than the last update. I haven't noticed any changes yet.
After one full day plus a few hours on the new H712 firmware on my Dish Hopper 3 I can attest that the next firmware behaves exactly like the older H711 firmware. There are 2 main issues with both versions of the firmware.
1. The Dish Hopper 3 stops responding to IR commands. For example when I run the Dish Network shutdown activity the Dish Hopper 3 after using the OEM Dish remote it does not shut down. Then I open the Dish Hopper 3 device from my Sofabaton X2 universal remote and press the 'Power Off' button and it still doesn't shut down. At this point I press the 'Power Off' button several times (anywhere from 5-40 times) and finally the Dish Hopper 3 will turn off.
At this point I can turn the Dish Hopper 3 on and off using the 'Power On' and 'Power Off' button from my Sofabaton X2 universal remote. However, once I begin using the OEM Dish remote the problem returns and the Dish Hopper 3 will not respond to IR commands. This is very reproducible as it appears that the RF commands from the OEM Dish remote is causing some type of conflict with the IR commands.
2. While using the OEM Dish remote we are still having the issue where the Dish Hopper 3 randomly goes into standby mode and the little rectangular box bounces around the screen that says 'Press SAT to Watch TV' and when we push the 'Select' button on the OEM Dish remote it immediately starts working ag
Staged rollout. Nightly updates are done by blocks of receiver numbers to lighten bandwidth demand of images, and to allow for possible backtracking of an image should problems arise during rollout. These kind of strategies are common for mass rollouts of SW/Firmware over the air.Speaking about updates and had always been curious about this one, is there a reason the nightly reboot update check does not see the update until a few weeks to months later while the manual check for update will see the update and update it? Do both methods check for updates a different way? Or maybe the manual update check is really to get early access to the update before it's actually forced?
Wish the IR issue in H711 had been discovered before it rolled out...Staged rollout. Nightly updates are done by blocks of receiver numbers to lighten bandwidth demand of images, and to allow for possible backtracking of an image should problems arise during rollout. These kind of strategies are common for mass rollouts of SW/Firmware over the air.
Nightly updates are same as a manual check, it just depends on whether you're in the current block list.
Manual updates just ignores the block list and says update now. Although, I've seen manual updates also block listed when they are being careful with a new update.
Wish the IR issue in H711 had been discovered before it rolled out...
Only issue I had with the episode was it was "The Way To Eden" and the space hippies...And for managing to sit thru an hour of TOS:
![]()