Bell Fibe TV Box Re-booting

RFL
Contributor II

For the last week( ?) my Bell Fibe TV box (and App) has been restarting at 8:39pm exactly, obviously interrupting what we were watching.  The system reboots, reloads Android TV and then the Bell App.  Any hints on how to move the reset to a different time? Thanks

0 10 1,556
2 helpful replies

Accepted Solutions

Hi @RFL 
Thanks for the information. 

Does this issue only occur when you're watching your Fibe TV channels or does it also occur if you are using another app on the receiver?

 

There are a couple things we'd recommend trying:
1. Please try using a different HDMI port on your television (not the ARC port). The ARC port is designed to send audio back to the connected device, so this port is generally beneficial to sound systems.

2. Try factory resetting your receiver. This can be done by pressing the Multifunction button which will bring up some options (you can press the small button on the side of the receiver). Please select the "factory reset" option and follow the steps.

View reply in original post

RFL
Contributor II

No issues after the factory reset yesterday.  I did seem to resolve the issue.

View reply in original post

10 REPLIES 10

BellNick
Moderator

Hi there @RFL 
Thank you for your post and welcome to the Community.
Do you happen to have any third party equipment connected (such as a router)? If so, we would suggest removing it and check to see if the issue persists.
Is your receiver fully rebooting or is it just losing internet connection?
When the issue occurs, do you have any other troubles with other devices connected to your network?
Looking forward to hearing back.

RFL
Contributor II

Hi thanks for replying.  Nope we just had Fiber brought into the house - all new equipment.  We now have a giga hub, w/Gigabit Fibe 1.5, wireless to our new Fibe TV Box, HDMI to ARC port on the Samsung.   It's very strange that the Fibe TV Box is re-booting at exactly the same time each night.  There might be a trigger somewhere. 

The Giga Hub is not rebooting.   Wifi is still available on our computers and phones..

Hi @RFL 
Thanks for the information. 

Does this issue only occur when you're watching your Fibe TV channels or does it also occur if you are using another app on the receiver?

 

There are a couple things we'd recommend trying:
1. Please try using a different HDMI port on your television (not the ARC port). The ARC port is designed to send audio back to the connected device, so this port is generally beneficial to sound systems.

2. Try factory resetting your receiver. This can be done by pressing the Multifunction button which will bring up some options (you can press the small button on the side of the receiver). Please select the "factory reset" option and follow the steps.

RFL
Contributor II

I believe we were watching netflix thru the MyBell app on the bell box.  I'll move HDMI to another port.  When you say receiver, I only have the small (3x3) Bell TV WiFi box vs the old PVR/receiver. 

Thanks for that info @RFL 
Yes, the small one (7802) is still technically a receiver. There's a small button on the right hand side on it. If you give that button a push, a menu will appear on your television screen with some options, at which point you would use your remote and select the factory reset. Before you do this, I'd recommend just giving the HDMI port change a test to see if it stops the issue you're experiencing.

Hi there @RFL 
We just wanted to check in to see if any of the recommendation above fixed the issue?

RFL
Contributor II

Won't be able to get to it until tomorrow PM.  Will let you know. Thanks for following up.

RFL
Contributor II

Morning, so yesterday I moved off the ARC port onto a regular HDMI, but exactly at 9:39 PM last night, the TV box re-booted.  This morning I did a factory reset on the TV box and set it up again.  The TV is back up and running,  I did receive and I installed a software update.  No issues.  I guess we'll see what happens tonight.    

RFL
Contributor II

No issues after the factory reset yesterday.  I did seem to resolve the issue.

Hi @RFL 
Awesome! Thanks for the update. We're glad to hear this.

If you have any further questions, please do not hesitate to contact the Community.