There will be some channels leaving the Fetch service soon. Click here to find out what they are. Read the full story
2016-08-01 11:37 AM
I have a HiSense TV that continues to show an error msg about 'google.tv.discovery no longer available'.
This was posted today on a Facebook Page where others are complaining of the same fault.
"Hisense Australia Hi everyone, we understand this issue is happening with customers with Optus modems. If that's the case, Optus can help resolve the issue if you reach out to them with the following ticket # 15278074."
So does anyone on this forum know of the resolve to ticket #15278074"?
It would be much appreciated
2016-08-03 10:08 AM
Hey @Mal2016 Sorry for the delays in getting this resolved for you. We're working on a fix which should be deployed in the coming days. Are you able to PM me your details so I can add them to the investigation?
2016-08-16 03:22 PM
Has this fix been sorted? My TV is still showing the error message
2016-08-17 12:05 AM
@poncherello2357 - I've just had a look and we're still working on a fix for this one, really sorry for the delay
2016-08-31 04:06 PM
Hi any updates on ticket # 15278074. Its been a while now and it seems rather unacceptable that I am unable to use my smart tv because of your modem.
2016-09-01 10:14 PM
Sorry aizat1982, looks like they are still working on it.
2016-09-12 12:24 PM
Hi i have the same problem with my tv it is very annoying ....
2016-11-21 04:32 PM
I am also having the com.google.tv.discovery has stopped message. Was this resolved finally?
2016-11-22 09:44 PM
@Vinode I've taken a look at the faults ticket and it looks like it's still being investigated. My apologies!
I’m part of the Yes Crowd team, employed by Optus to help run our online community. This guide explains how everything works on here and you should also check out our Community Guidelines.
Did we answer your question? Please mark it as a Accepted Solution and be generous with that Kudos button
2016-12-15 07:53 AM
Hi, any news on this please? my tv is having the same issue and seems like this should have been fixed by how old this post is?