10-26-2022 08:31 PM - edited 10-26-2022 08:32 PM
Hello, @wand612.
Thank you so much for sharing your problem and resolution with the Community. Keep authoring more solutions! 👍
Cheers,
RogersMoin
Solved! Solved! Go to Solution.
10-25-2022 08:43 PM - last edited on 10-26-2022 08:33 PM by RogersMoin
I think I finally resolved a problem I had been having with my ignite controlled tv. Often when I turned it on I would see a Rogers advertisement of some sort and then have to wait a very long time for the tv to actually start broadcasting.
My Solution: I think this was due to the fact that the ignite box power saving option was set to off, which was causing ignite to go into screen saver sleep mode, and this in turn caused startup problems with my Samsung smart tv. Anyways, I have turned on the power saving feature and things are working beautifully.
Support History: I spoke to Rogers over the phone about my problem, and they even installed a new modem for me, and the problem persisted. I never mentioned the Rogers screensaver that was appearing because I thought it was a normal part of the process. Still, it would have been nice if someone had mentioned the power saver setting as a possible cause.
10-25-2022 08:43 PM - last edited on 10-26-2022 08:33 PM by RogersMoin
I think I finally resolved a problem I had been having with my ignite controlled tv. Often when I turned it on I would see a Rogers advertisement of some sort and then have to wait a very long time for the tv to actually start broadcasting.
My Solution: I think this was due to the fact that the ignite box power saving option was set to off, which was causing ignite to go into screen saver sleep mode, and this in turn caused startup problems with my Samsung smart tv. Anyways, I have turned on the power saving feature and things are working beautifully.
Support History: I spoke to Rogers over the phone about my problem, and they even installed a new modem for me, and the problem persisted. I never mentioned the Rogers screensaver that was appearing because I thought it was a normal part of the process. Still, it would have been nice if someone had mentioned the power saver setting as a possible cause.