Samsung Firmware Release Notes
Quintin Downing
Is there some place that posts the release notes for Samsung's firmware? I just updated from 1292 to 1294 and I have no idea what it does. I have a NU8000. I am beating my head into the ground trying to find out what this fixed (if anything).
I recently saw the 1420.0 firmware update for my QN75Q60RAFXZA television. There are no details if a user chooses to update from the TV interface, nor was there any information in the firmware zip file.
It's already frustrating enough that my TV auto-installs certain apps like SlingTV and Tubi and doesn't allow me to delete them. They just eat up valuable megabytes of space that I can't get back. Just a few months ago the TikTok app was randomly auto-installed and now it can't be removed either.
I remember there were some issues with Orbi when updating firmware. Do I still have to factory-reset both the router and the 2 satellites, or can I at least try with a manual upgrade first? (First the two satellites, then the router).
The reason I now am forced to upgrade, is that the brand new phone, Google Pixel 8, is having great issues with this mesh network. I dont know if this is Googles fault or Netgear, but the phone works fine with other 2.4/5 mesh networks I have tried + also works fine with a 2.4 GHx Tp-Link network I tried in my home simultaneously with the Orbi network.
It is well-known that Netgear gives customers some time to download and install new firmware before making the release generally available through the Firmware Update process, and then waits for another period before pushing the new firmware without notice. Steps in this process are not documented or published.
My guess is that whoever was supposed to monitor the firmware status of this product from 2016 either (a) forgot, or (b) was reassigned to other tasks, or (c) no longer works at Netgear. And no one has discovered the lapse.
Wifi is again working fine for everything except my expensive Pixel 8 Pro. I cannot believe it is not working. It is flapping on and off. I will provide a video and wifi settings here soon. Google is going to start monitoring my phone to troubleshoot this also unless you guys finds a solution fast.
Thanks for the delightful video. The Pixel 8 Pro supports all sorts of WiFi standards that are not provided by the 802.11ac Orbi product (802.11ax [WiFi6} - WiFi6E - WiFi7). One would certainly think that "backward compatibility" would be "no problem."
Thanks for your advice. I wil test this later today. That is about the only option I have not tried, bu tI thought about it (20/40 coexistence). Hopefully it is this, because it works fine other places. The TP-Link is not connected anymore as well at the moment, just running on 4G.
Please report the results. If I had $1,000 to burn, I'd buy one myself to see what happens. Alas, I am the one remaining person in the world who wants a small phone. Even if it cost less, I would not choose a Pixel 8 Pro.
I would imagine Samsung has a test lab full of different WiFi systems where they validate new products. Would be so useful if Samsung support could escalate this question to someone who can investigate it.
yes, will do. Yes, difficult choice, the Pro might not be worth it, but it has the temperature sensor and much better AI computation. Otherwise I would have gone for the other. And I presume you meant Google, not Samsung. They asked for permission to track my phone to look into it.
yes, the problem is the same, and as you know I cannot even turn off 5GHz. I tried the trick to set the signal strength to 25%, but it is still unstable. Dont know what to do now, Google seems to want to give me a new phone, but I told them it most likely will not help me. It works fine with other networks.
On the RBR50, there is an option to disable broadcasting the SSID on 5GHz. If you "forget" the Orbi WiFi, perhaps it will detect only the 2.4G SSID and connect to it. (newer models of Orbi removed this feature. Those of us "stuck in the past" still have it.)
My guess is that every device already connected at 5G will remain connected, and only the Pixel 8 will come up with only the 2.4G SSID. (Or, the whole network could go to hell. Or... the Pixel 8 will attempt to connect to a 5G WiFi anyway???)
Tried turning off the 5GHz broadcast, and both the wifi networks still go on and off...I am pretty sure this must have to do with neighbor 5GHz interference, since the TPlink was working. I have tried different channels, and I have now moved to a different channel again. I also still think something is wrong with my Google Pixel Pro. Why do I have no problems with Sasung devices on it + my Aplle Macbook Pro M1?
Hmm.I want to downgrade from 2.7.54. The reason is that Google said they fixed this issue in their December update, and it didnt. And today I discovered that aslo Samsung devices have a problem with disconnecting and connecting on this latest version. Which version should I downgrade to? And can I just install like I did when upgrading? Satellites first. then the router.
There is one "gotcha" lurking. Whereas Netgear finally added a feature to the AX series products to allow the user to enable/disable Automatic Firmware (without asking if the user wants to do so), that feature is not present on the RBR50 product. If Netgear finally decides, "It's time", they can push v2.7.5.4 onto your system. (or any newer version than the one you loaded)
I am aware of a major crisis involving the newest version of iOS (17) and lots of WiFi systems (not just Netgear). Am not aware of any issue with Android/Wiindows problems. My RBR50 has been on v2.7.5.4 since last February and all my Android/Windows/Apple/Nest devices work just fine.
Now I will have to stop the store from sending my Pixel 8 Pro to google for investigation. There is a chance now that their December update actually fixed my problem, so have to extinguish that possibility before they wipe my device and maybe say nothing is wrong with it.
So I reset to factory settings. So far all devices are stable (Also Google Pixel 8 Pro). Wifi channel is Auto. I notice the advanced wifi settings for default are quite different from what was recommended here some years back. What should I tweak there as a minimum? I do not want to cause any instability again.
Appspace App for devices now supports content caching for images (in Public and Private instances), and cards (in Private instances). The PWA downloads and loads images and card content to and from the cache. The caching progress is shown during the syncing and downloading of files.
UWP App customers must update their UWP app to App version 2.58.0 or later to retain current registration information. Failure to do so will require re-registration and configuration of the device.
There is a known minor issue during browsing mode in WebView2 where the Program Guide thumbnail may display a default thumbnail instead of the actual program thumbnail. This will be corrected in the next release.
Appspace App for Devices now includes headers (such as authorization headers or token headers) when caching card content in addition to the list of content URLs to be downloaded to the device for Brightsign devices.
A mechanism has been created in Appspace App for Devices to listen for the load event of the Iframe/Native Webview embedded in the Web View card before it has finished loading.
Appspace App for Devices now supports Chrome OS version 102 (14695.85.0).In line with our improvement efforts, we recommend pinning Appspace App to Chrome OS 102 for better stability, security, and performance. For more information, visit the Chrome Enterprise release notes. The previously supported version of Chrome OS was version 90. For instructions to pin your app to a specific version, you may refer to Configure Chrome Version Control.
Appspace now supports bulk registration of Google Meet devices with Appspace accounts using serial numbers, in addition to the 6-code device registration method.A Google Admin console license and a Google Enterprise (CDM) account are required. You are now able to register multiple Google Meet devices at once by uploading an Excel (.xlsx) spreadsheet. You are also able to perform advanced registration of Google Meet devices with a Google Meet Integration ID.
With the Playlist Interleave device property, you may configure and control the number of content items from a playlist channel during playback, before switching to display content items from the next playlist channel. This back and forth sequence will go on until all content items from all playlist channels are displayed before starting over again.
Appspace App now supports the latest Crestron firmware 1.4499 on both Crestron Airmedia 200 and 300 devices, which fixes various bugs and also addresses the URL policy issue when registering Crestron Airmedia devices via a network policy file.
Appspace App now supports LG webOS 6.0 that provides for better playback performance on digital signage displays. The limitations for LG webOS 6.0 that we have found, and are currently trying to fix are similar to the LG webOS 4.x limitations that have been documented in our Technical Limitation & Workaround section.
Release Date: 9 July 2021
Chrome OS UpdateIn line with our improvement efforts, we recommend pinning Appspace App to Chrome OS 90 for better stability, security, and performance. For more information, visit the Chrome Enterprise release notes. The following are some of the more notable changes:
- Chrome OS improved gesture support for handwriting keyboards, such as drawing a strikethrough deletes text, or while drawing a caret provides a space to insert text. Reverse Scrolling has been improved and more consistent with touchpad gestures.
- Improved autocorrect UI with visual indications for when autocorrects happen, as well as methods to undo them.
- Improved resource consumption for background tabs, saving CPU load and battery life.
- Chrome OS Camera saves photos and videos captured to a new camera location within the device.
- Support for Chrome OS Camera to automatically scan QR Codes when available.
- Cross-Origin Read Blocking (CORB) and Cross-Origin Resource Sharing (CORS) allowlist have been removed with Chrome OS 87.
- The DTLS 1.0 protocol is removed by default in Chrome OS 87. This protocol is used in WebRTC for interactive audio and video.
- The Deprecation of TLS 1.0 and TLS 1.1 has been extended to Chrome OS 91. Appspace recommends and supports TLS 1.2.
- The TLS13HardeningForLocalAnchorsEnabled enterprise policy no longer functions or is supported.
- Chrome OS warns when loading web forms with mixed content, where web form is loaded via HTTPS, but the content is submitted via HTTP (unsecured) posing a potential risk to user privacy.
- Device Name
- Serial Number
- MAC Address
- Fingerprint (GUID)