allaboutbuzz

Yes were aware This will be fixed with an Update this month. And your claim about no server support is needed, is False. As Closed Captioning has to be supported by the server you're using. In your case, the server you're using supports it. The update in December just presented a bug for sub titles on the Secondary Player If you switch to the Default Player, sub titles will work no problem.

1. How are you recording it Scheduled through the EPG Manual Recording? 2. Are you recording to External USB or SD Card Or to Internal Memory? 3. The recording could be stopped early due to buffering for longer then 30-60 seconds or loss of internet connection or a network issue. Some servers also stop Live TV Playback if it is left on a TV Channel for longer then 2-3 hours, without any activity They do this in order to save bandwidth.

Stick Firmware Updates + E1 Update were working on building this week With plans to hopefully release next week.

Have you tried a different HDMI cable or different TV?

I replied And can see you took the update.

As stated in my release notes You cannot revert back to an older version. And what I wrote to you in a PM was only that we will fix the missing sub titles issue on the Secondary Player with an update + we will also fix the duplicated EPG on the channel list issue.

PM me your Serial # Thanks

Just checked myself And also see it But on Grid Guide/EPG its accurate.

Are you using the same power supply that they were using??

Correct As both are different

Are you using a Wifi mesh network for this Wifi network? Might be caused by the device connecting to the different Access Points each mesh pod offers.

You would need to enter the M3U URL and EPG URL Separately then press connect Make sure everything is spelled correctly, otherwise it wont connect properly.

Are you using a VPN on the box?

There is menu option called Scanning always available. Right underneath Wifi menu

There is an on/off switch for Wifi scanning in Network settings for Wifi.

Try clearing EPG in configuration menu Do a reboot And see if that fixed the issue.

This on Default and Secondary Player?

I think I know the issue It is a Passthrough issue on the Buzz App We will take a look at it and will update youA Am sure we can fix it Once we do, I'll get you to try a Beta.

If you press Green button on a channel you know has Dolby. Does the audio show Dolby, it should list EAC3 or AC3 as the audio?

I did in a previous post I'll copy and paste it again This might be a compatibility issue with the update we did on the version of the Secondary Player that was apart of this OTA for the specific server you're using. If you try the Default Player it should work However if you PM me, am sure I can help fix it for you on the secondary Player.

Well if sub titles worked before this update on the secondary player Then it must be a compatibility issue with this update, as there are quite a few different types of sub titles that require support With your help we can fix it for you.

Actually, after re reading this. Buzz has stopped responding is not a crash bug and not even the same error that happened on the 4000s. Its just an error that appears when the app is busy. Simply hitting close app and reloading the Live TV/app will fix this and no reset is required. You could even press wait, and the app will keep working. What app are you allowing to install apps from? Aptoide On Android 9 and up You have to give permission settings to each app individually. You can turn on permissions manually by going to the apps part of Android Settings and turning permissions on for each app you use to install other apps.

I replied in a post above to your Subtitles issue. So please read it and PM me As for new issue on 4500 Did this error appear when you opened the Buzz app after the update or after the box rebooted from the update? The 4000 bug was after the box rebooted from the update, which we fixed and so far from our crash logs on the new 4000 + 4500 update we haven't seen it re appear. So am thinking this bug happens when you open the Buzz app for the first time, so this could be a server related issue. Would be helpful if you PM me the 7 boxes that gave you this issue so I can look at individual logs to figure out what's wrong.

This was followed exactly. And out of 1000s of users getting this update So far you're the only one complaining Were not saying you don't have an actual issue, so we're here to help you and figure it out.

I replied to a few of your posts already Just wanted to let you know NBS and Dishuser are admins at a few other forums already and are very helpful. Their just helping out on this Forum as well.