Tag: beta updates

  • Garmin Smartwatches: Improved Volume in New Beta Updates

    Garmin Smartwatches: Improved Volume in New Beta Updates

    Key Takeaway

    – Improved responsiveness of the touchscreen volume slider in beta 17.30/17.31.
    – Nutrition Glance now logs both minute and hour of meal times; translations updated.
    – Bug fixes: prevents unexpected resets for FR570, FR970, Venu X1, Venu 4, and vivoactive 6; separate fix for multisport workouts causing freezes/resets on FR570, FR970, Venu X1, Venu 4.

    Garmin has released updates that bring new beta versions to several watches, including the Forerunner 970, Venu 4, Forerunner 570, Venu X1, and vivoactive 6. These beta releases aim to improve how the devices respond when you move the volume slider on the touchscreen. The changes also touch the Nutrition Glance, now letting you log both the hour and the minute of your meal time, and Garmin mentions updated translations across these wearables, though they do not specify which languages were amended.

    Varied stylistic note

    With the beta versions 17.30 and 17.31, users can expect better responsiveness as you adjust the volume via the touchscreen slider. The update also expands the Nutrition Glance’s functionality by recording minute-level precision for meal times, a small but handy tweak for daily tracking. Translation updates are acknowledged, yet the exact languages updated remain unspecified, leaving some curiosity about global support. These tweaks show Garmin’s ongoing attention to user experience for diverse markets.

    Technical specifics

    The beta notes indicate a bug fix intended to prevent unexpected resets on several models under 17.30/17.31. In addition, a separate fix targets multisport workouts on Forerunner 570, Forerunner 970, Venu 4, and Venu X1, addressing a potential freeze or reset during use. The current distribution status claims around half of eligible devices have received the beta, with installation possible via Settings > Check for Updates. Prices cited in context include curr. $649.99 for the Forerunner 970 at retailers, though this is not a guaranteed price in the update itself.

    How to get it

    User guidance notes that the beta software can be manually downloaded through the system’s update pathway when you select the “Check for Updates” option. As this is a beta, some users might experience fluctuations in performance, so caution is advised for those who rely on the watches during critical activities. The process is designed to be straightforward, yet it’s best to ensure data backups and familiarity with the update flow before proceeding. Garmin’s engineering teams continue to test these builds prior to wider rollout.

    Tags: , , , , ,
  • Android 16 QPR3 Beta 2.1 Now Available for Google Pixel Devices

    Android 16 QPR3 Beta 2.1 Now Available for Google Pixel Devices

    Key Takeaways

    1. Android 16 QPR3 Beta 2.1 was released on February 10, 2026, for supported Pixel devices, featuring automatic updates and quick installation.
    2. The update maintains the January 5, 2026 security patch level and does not provide a specific list of fixes, focusing instead on stability and usability improvements from Beta 2.
    3. Supported devices include Pixel 6, 6 Pro, 6a, 7, 7 Pro, 7a, Pixel Fold, Pixel Tablet, Pixel 8, 8 Pro, 8a, and the Pixel 9 and 10 families.
    4. Switching between beta and production versions requires a complete device reset, so users should back up their data beforehand.
    5. Google encourages users to report issues via the Issue Tracker and Android Beta Feedback app, and suggests checking release notes for known issues before submitting new reports.

    Google has released Android 16 QPR3 Beta 2.1 for the Pixel beta track, on February 10, 2026. If you’re part of the program, you can expect this update to appear automatically, install swiftly, and then be done with it.

    Device Specifications

    According to Google’s notes, the majority of supported devices are marked as CP11.251209.009.A1. The Pixel 6 Pro, Pixel 6, Pixel 6a, Pixel 7 Pro, and Pixel 7 are specifically noted on CP11.251209.009. The update maintains the same security patch level from January 5, 2026, identifies Google Play services version 25.47.33, and still lists emulator support as “TBA.”

    Update Details

    Here’s the thing: the Beta 2.1 update is essentially just a label set—date, builds, patch level, and Play services—without any specific list of fixes for Beta 2.1 in the official notes. So if you’re hoping for a tidy changelog that says “fixed X, fixed Y,” you won’t find it.

    For a bit of background, Google does explain what Beta 2 was aiming to address in the same document, highlighting a range of stability and usability improvements, such as crashes, freezes, battery management, connectivity problems (like slow Wi-Fi and missed calls), along with some UI issues. This context pertains to Beta 2, not a definitive fix list for Beta 2.1, but it gives insight into the type of challenges this QPR3 version has been focusing on.

    Supported Devices

    Google lists support for Android 16 QPR3 beta on Pixel 6, 6 Pro, 6a, 7, 7 Pro, 7a, Pixel Fold, Pixel Tablet, Pixel 8, 8 Pro, 8a, along with the Pixel 9 family (including Fold), and lastly the Pixel 9a and the Pixel 10 family (including Fold). It’s also important to note that once you join the beta program, your phone will receive constant OTA beta updates until you decide to leave the program.

    If you like to do things manually, Google suggests using the Android Flash Tool as the recommended method for flashing.

    Important Considerations

    Google is quite clear on this point: switching from the production version to beta, or back again, necessitates a complete device reset that wipes all user data. Always remember to back up your data first!

    Additionally, Google makes OTA images available for QPR beta builds and promotes them as a useful option for testing—and, in certain situations, for restoring a device after a troublesome OTA update.

    For reporting any issues, Google directs testers to the Issue Tracker and the Android Beta Feedback app included in preview builds. It also recommends checking the release notes and looking at “top open issues” before submitting a new report, to avoid submitting something that’s already been reported.

    Source:
    Link

     

    Tags: , ,
  • Garmin Mid-Range Smartwatches Receive Beta Update with Fixes

    Garmin Mid-Range Smartwatches Receive Beta Update with Fixes

    Key Takeaways

    1. Garmin released new beta updates for the Forerunner 570 (version 15.31) and Forerunner 970 (version 15.30) after the stable software version 15.16.
    2. The updates focus on various bug fixes and improvements, but specifics on benefits to users are unclear.
    3. Users of the Forerunner 970 are experiencing ongoing issues with text message alerts not appearing or notifying them.
    4. Alerts from other apps and incoming calls on the Forerunner 970 are functioning properly, but the text message issue remains unaddressed by Garmin.
    5. Users can access the beta software by navigating through the smartwatch’s settings to check for updates.

    Garmin has just unveiled new beta updates for its Forerunner 570 and Forerunner 970 smartwatches. These updates come nearly a month after the stable software version 15.16 was released, which introduced features such as Health Status, app-level notification controls, and a gesture that lets users exit notifications by simply placing their palm on the screen.

    Beta Version Details

    The Forerunner 570 is getting beta version 15.31, while the Forerunner 970 is getting beta version 15.30. It’s a bit confusing why these updates have different version numbers. The change logs for both watches merely mention “various bug fixes and improvements,” leaving it unclear how these updates might actually benefit users of these running watches.

    Notification Issues Persist

    One issue that seems to remain unresolved is regarding text message alerts. Users of the Forerunner 970 have shared on the Garmin Forum that notifications are not appearing on their screens or creating sounds or vibrations, which is what they would expect. However, alerts from other apps and incoming calls do not seem to be affected. Garmin hasn’t publicly addressed this problem yet, so it’s uncertain when a fix might be available.

    How to Access Beta Software

    If you’re part of the Garmin beta program for the Forerunner 570 or Forerunner 970 smartwatches (currently starting at $646 on Amazon), you can now download the latest beta software. To do this, navigate to Main menu > Settings > System > Software Update > Check For Updates.

    Source:
    Link

     

    Tags: , ,