Separate names with a comma.
Discussion in 'TiVo Roamio DVRs' started by morac, Nov 3, 2014.
Mine locked up this morning. No Mini currently in use.
Trying to deal with the same problem with my Premiere XL. Waiting for a show to finish recording before pulling the plug for a reboot.
This happened to me within the last hour. Are they still looking for TSN's?
Just happened to me, as I was sitting down to watch Arrow.
Happened to me tonight as well. Roamio basic with OTA...right around 7:30 CST.
Same here. Happened to me tonight. Roamio Pro.
Would not respond to any remote command, though the light blinked, and the App couldn't find the box.
That's exactly when mine happened (or I noticed it). Coincidence?
Maybe there's something in the signal doing it?
Just a suggestion, that has worked for me, on many forms of TiVo lockups:
Disconnect the coax feeding the CATV (or OTA) signal (for just a few seconds), then reconnect it, if the TiVo starts responding again. Do this right at the back of the TiVo (or the other end of that cable, if that is easier for you).
A long while back (and just the other day) I was about to pull all the connections, but started with the coax, and in a couple seconds, the box came back to life. I've found this seems to be a common quick fix for units in any state that results in the remote control being ignored, on TiVo HDs, Premieres, and now my Roamio basics.
Unless you used a wrench to tighten the coax feed (I do), and don't have a wrench right there to loosen it, it can be a real time saver, and the worst that can happen is a recording in progress loses a chunk, for the matter of seconds it takes to reconnect the coax (as opposed to the time it takes for the TiVo, cablecard, and Tuning Adapter to boot and sync).
Latest victim. My tv was showing a black screen when I turned it on. It would not respond to any commands, not even the standby button on the front of the unit. I had to pull the power and plug it back in.
My version of this problem was initially no volume when I turned on my system. Remotes did not control the unit. Could not select Tivo or Live TV, etc. Only solution was to reboot.
Had this happen yesterday as well. Live TV was still playing, remote activity light was still flashing with every button press. Remote still in RF mode. No results. Didn't crash/reboot either as it used to when this would occasionally happen.
Unplugged & plugged back in, everything fine.
TiVo: please give us a physical switch back at some point!!! Even if it is hid away on the back of the unit.
Interesting thread. My remote has become super unresponsive, taking several button hits to make it do anything, but I figured my batteries were just on their last legs even though have not gotten a low battery warning. I wonder if this could be related. I guess I could change the batteries and find out.
Different problem. In this case the unit never responds to the remote until it's rebooted. Your problem sounds more like low battery or interference.
Given the spike of reports, all from yesterday evening, this is looking like another issue with bad data from the Tivo servers messing the box up. Has anyone pulled the Ethernet when the box locked up?
Mine happened yesterday morning. And pulling the ethernet did not return operations (nor did a HDUI reset).
Yeah, mine was yesterday morning (or overnight the night before) as well. HDUI reset didn't work.
Since my Mini was responding (albeit not able to get anything from the Roamio Pro except Live TV), I did a server connect from the Mini before I rebooted the Roamio, and it didn't indicate any trouble getting data. Don't know if that information's worth anything.
So far (knock wood), no recurrence of the problem.
Definitely try new batteries, but ...
This problem is also reminding me of the problem some Series 3 units like my TiVo HD had, where they became reluctant to respond to the remote for no apparent reason. There were suggestions that it was a hardware problem, and I wondered if it could be caused by the power supply to the IR receiver circuitry drifting too low or developing too much ripple. But it also occurred to me that the IR receiver might have to be polled by the software to notice when commands have been received, and if the software got preoccupied with other matters that could also explain the unresponsiveness.
Thanks to everyone that sent TSNs. Please keep them coming. This one is still mysterious to us, so we are continuing to investigate.
In your email, please include the date/time you pulled the plug to reboot.
I hope you get a big Christmas bonus.