XDA

jeudi 5 mai 2022

Google Assistant in Chrome for Android now offers to change compromised passwords automatically

At its I/O developer conference last year, Google announced a new Assistant-powered feature for Chrome to help users easily change compromised passwords. The feature is now finally rolling out to users in Chrome for Android.

The new Assistant-powered feature displays a pop-up notification as soon as you log in with a password found in a data breach. As shown in the attached screenshots (via Max Weinbach), the notification states: “Chrome found the password you just used in a data breach. Your Google Assistant can change your password automatically.”

Google Assistant being able to change breached passwords >>>>> pic.twitter.com/Dfcnvhs1S5

— Max Weinbach (@MaxWinebach) May 3, 2022

The notification also includes two buttons — one to close the pop-up and another to change the password automatically. Tapping on the latter takes you to a new page with a confirmation sheet that states: “To help you complete tasks, Google will receive the URLs and contents of sites on which you use Assistant, as well as information you submit through Assistant. This information may be stored in your Google account. You can turn off Assistant in Chrome settings.”

Tapping on the ‘I agree’ button on the confirmation sheet will take you to the change password page for the service in question. The page also includes a sheet at the bottom to track progress as the Google Assistant generates a new password. After the Assistant generates a new password, you can accept it and save it to Chrome’s password manager. If you face any issues during the process, you can take over at any moment to change your password manually.

It’s worth noting that this feature first rolled out to a handful of users last November. It now appears to be rolling out more widely. If you’ve not received it already, it should reach your device in the next couple of days.

What do you think of this new Assistant-powered feature in Chrome for Android? Do you think it’s useful, or would you rather change your compromised passwords manually? Let us know in the comments section below.

The post Google Assistant in Chrome for Android now offers to change compromised passwords automatically appeared first on XDA.

from XDA https://ift.tt/kTjz0h9
via IFTTT

New Galaxy Watch 4 update brings stability improvements and May 2022 patches

Samsung has started rolling out a fresh software update for the Galaxy Watch 4. While you’d expect the update to finally bring Google Assistant support to the Wear OS smartwatches, sadly, that’s not the case. Instead, the update only packs some system stability improvements and the latest security patches.

According to user reports on Reddit, the latest software update for the Galaxy Watch 4 (firmware version R8x0XXU1FVD4) has already started reaching users. It measures around 100MB and brings system stability and reliability improvements. As shown in the attached screenshot, the changelog also states that the update applies stabilization codes for watch operation. But we’re not sure what that means.

Samsung Galaxy Watch 4 software update May 2022 patches

Credit: u/Enjinr

In addition, Samsung’s website states that the software update bumps the Galaxy Watch 4 to the May 2022 security patch level. Unfortunately, the changelog makes no mention of Google Assistant support, and users who have installed the update confirm that the feature is nowhere to be seen. Therefore, we’ll likely have to wait a few more weeks for Samsung to finally roll out Google Assistant support to its Wear OS smartwatches.

If you’re not in the loop, the changelog for the previous software update for the Verizon variants of the Galaxy Watch 4 included mentions of Google Assistant support. However, the update did not enable the feature when it reached users. Verizon promptly removed all mentions of Google Assistant from the changelog soon after it was first spotted. A few days later, Samsung published a new ad highlighting Google Assistant on its Wear OS smartwatches, leading many to believe that Google Assistant support would finally go live with the following update. But, it’s still not live in the latest software release.

Currently, the latest Galaxy Watch 4 update appears to be rolling out to users in the US. But it should reach users in other regions over the coming days.

Have you received the update on your Galaxy Watch 4? Let us know in the comments section below.

Source: Reddit, Samsung

The post New Galaxy Watch 4 update brings stability improvements and May 2022 patches appeared first on XDA.

from XDA https://ift.tt/QOs1gdX
via IFTTT

New Galaxy Watch 4 update brings stability improvements and May 2022 patches

Credit: u/Enjinr

Currently, the latest Galaxy Watch 4 update appears to be rolling out to users in the US. But it should reach users in other regions over the coming days.

Have you received the update on your Galaxy Watch 4? Let us know in the comments section below.

Source: Reddit, Samsung

The post New Galaxy Watch 4 update brings stability improvements and May 2022 patches appeared first on XDA.

from XDA https://ift.tt/QOs1gdX
via IFTTT

mercredi 4 mai 2022

PowerToys 0.58 update prepares native ARM64 version and brings more improvements

Microsoft has once again updated the PowerToys suite of tools for Windows, bringing it to version 0.58. This new update doesn’t add any new user-facing features per se, but it does make some important under-the-hood changes, including preparing for an upcoming ARM64 version of the app. Currently, PowerToys is only designed for x64 processors, meaning that to run on ARM devices like the Surface Pro X, it needs to use emulation, which affects performance. Many of the required components for PowerToys to run on ARM64 are now included in the package, so hopefully, we don’t have long to wait now.

That’s not all that’s changed with this update, however. The team has done some work under the hood to bring PowerToys up to more modern standards. For one thing, it’s no longer using the old WebBrowser control for web content, and has switched to WebView2, powered by the Chromium-based Microsoft Edge browser.

Similarly, PowerToys 0.58 drops all uses of .NET Core 3.1 and transitions fully to .NET 6, so it’s more current. And on a final note on the development side, the PowerToys Settings window now runs on WinUI 3, the latest version of Microsoft’s UI framework. Previously, it was using XAML Islands to incorporate UWP-style design in a Win32 app, but WinUI 3 brings all those elements together as well and it’s newer. The team says this transition should solve some bugs related to the use of XAML Islands, so things should work better overall.

Aside from that, there are a ton of smaller fixes and tweaks in PowerToys 0.58, improving the experience overall. You can read the full list of changes below if you want to see everything that’s been improved.

PowerToys 0.58 changelog

General

Spell checking fixes in the code. Thanks @jsoref!
Fix for a CI error related to spell checking due to a GitHub API change. Thanks @jsoref!
Fixed the documentation references to GitHub. Thanks @Cyl18!

ARM64

Prepare solution and property files for ARM64 port. Thanks @snickler!
Port unhandled exception handler to ARM64. Thanks @snickler!
Port of the Settings projects to ARM64. Thanks @snickler!
Port of most of the PowerToys to ARM64. Thanks @snickler!
Port of the debug utilities to ARM64.

Always on Top

Fix for topmost state of the window resetting for some applications. (This was a hotfix for 0.57)

ColorPicker

The CIEXYZ format is now properly show in upper case.

FancyZones

Restore rounded corners on Windows 11 and add a setting to control this behavior. (This was a hotfix for 0.57)
Fixed an edge case where the Windows Terminal window wouldn’t be snapped when opened. (This was a hotfix for 0.57)
Improved narrator support in the Grid Editor. (This was a hotfix for 0.57)
Fixed a bug when restoring rounded corners on Windows 11. (This was a hotfix for 0.57)
Fix for windows not being resized correctly on different dpi settings. (This was a hotfix for 0.57)
Removed resolution from the screen identifier so zones aren’t reset when resolution changes.
Scale the canvas layout when editing according to new scaling/resolution.
Shipping a new tool to help debug windows interactions with FancyZones.

File explorer

Fix for a crash in dev file preview if the settings file hadn’t been created yet. (This was a hotfix for 0.57)
New file types were added to dev file preview (“.reg”, “.xslt”, “.xsd”, “.wsdl”, “.ino”, “.pde”, “.razor”). Thanks @Aaron-Junker!
Fix an existing “file still in use” issue in dev file preview. Thanks @Aaron-Junker!
Dev file preview is now able to interpret file extensions in a case-insensitive way. Thanks @Aaron-Junker!
SVG and markdown viewers no longer use WebBrowser and use WebView2 instead.
Markdown preview now respects the dark mode settings on Windows. Thanks @davidegiacometti!

Mouse utility

Fix for the bug causing shortcuts set on icons to not activate when a mouse utility was active on specific monitor configurations.

PowerToys Run

Fix for PowerToys Run using high CPU and memory when updating its settings. (This was a hotfix for 0.57)
Add the “Run as different user” feature to the Program, Shell, and Search plugins. Thanks @htcfreek! (This was a hotfix for 0.57)
Fix for a WindowWalker crash when a Virtual Desktop registry key is not set. Thanks @htcfreek! (This was a hotfix for 0.57)
Fix for VS Code Workspaces not using the user’s path variable right after an install or update. Thanks @ricardosantos9521! (This was a hotfix for 0.57)
Fix for the System plugin causing PowerToys Run to be slow when many network interfaces exist. Thanks @htcfreek! (This was a hotfix for 0.57)
Fix for the Program plugin not showing special shortcuts with empty targets, like Control Panel. (This was a hotfix for 0.57)
Additional logging for the Terminal plugin. Thanks @davidegiacometti! (This was a hotfix for 0.57)
Web Search and URI plugins have better code for detecting the default browser now.
Fix for the Services plugin not manipulating service names with spaces correctly. Thanks @davidegiacometti!
Fix for the Terminal plugin not recognizing profiles correctly. Thanks @davidegiacometti!
Fix for latest VSCode insiders build not showing up in the VSCode Workspaces plugin. Thanks @JacobDeuchert!
Increased floating number precision in the Unit Converter plugin.
VSCode Workspaces now finds portable installations of VS Code. Thanks @harvastum
Fixed an issue starting PowerToys Run when the desktop is not initialized. Thanks @davidegiacometti!

Settings

Settings now runs on WinUI3 instead of XAML islands.
Settings no longer runs as an administrator when runner is started as an administrator.

Runner

Use sensible default times for rechecking for an update, to avoid writing to the logs in a loop. (This was a hotfix for 0.57)
Runner cleans up the update directory if the installation is up to date. Thanks @davidegiacometti!

Installer

Distribute a signed .msi inside the .exe installer bootstrapper. (This was a hotfix for 0.57)
Removed the .NET core dependency from the installer.
Partial support for an ARM64 installer.
Updated the .NET to 6.0.4.
Force update all files on reinstall/update, to try and fix installation issues.

Development

PowerToys no longer takes a dependency on .NET core.
WinUI3 is a new dependency. Settings now targets win10-x64 and win10-arm64 due to this.

The past couple of updates for PowerToys have focused mostly on quality improvements rather than new features, but that’s not necessarily a bad thing. These under-the-hood changes should also make it easier to maintain the app going forward. Recently, we saw a new PowerToys feature called Peek is in development, though it isn’t available yet. It’s essentially a Windows version of macOS’ Quick Look, allowing you to quickly view files without opening them in their respective app.

If you’re interested, you can download PowerToys 0.58 from GitHub today, or check for updates within the app if you have it already.

The post PowerToys 0.58 update prepares native ARM64 version and brings more improvements appeared first on XDA.

from XDA https://ift.tt/xq3CwoG
via IFTTT

mardi 3 mai 2022

Your Nest Hub is about to get cozy with Google Fit and Fitbit information

With Google I/O on the horizon, owners of a Google Nest Hub that are also into fitness look to be getting some good news. Spotted by 9to5Google, a new support page has appeared for the Nest Hub that details integrations with both Google Fit and Fitbit. Just in time for that new Pixel Watch that’s leaked eight ways to Sunday. It doesn’t seem to be live yet but you would expect it isn’t too far away.

Currently, if you have the second generation Nest Hub you can view sleep statistics on the display, but this could potentially provide the same feature and more to those who prefer wearables or have an older model. However, the support page is currently listed as only for the second generation model. It does sound like a pretty tight integration, though.

Activity metrics like number of steps and calories burned from Google Fit or Fitbit can be shown on your Nest display.

The support page details the setup process, which will involve linking either Google Fit or Fitbit through the Wellness menu in the Google Home app settings. From here you’ll be able to see steps, calories burned, and other activity metrics on the display. As will anyone else who looks at it if you enable personal results.

This integration with Fitbit, in particular, would be a step ahead of the already excellent integration with the Google Nest Hub’s main competitor, the Amazon Echo. The Fitbit skill on the Echo is very good, but it doesn’t do anything special with the display on the Echo Show. Likewise, with the new Pixel Watch on the way, you would expect some element of fitness focus. Integrating it into the Nest Hub like this is just another piece of the ecosystem puzzle.

Google has some dedicated sessions coming at I/O for what’s next with Google Home, so it seems like a good fit that this and other potential new features could be revealed during the conference. Google I/O takes place on May 11 and 12 and is available online for anyone to attend.

Source: Google

The post Your Nest Hub is about to get cozy with Google Fit and Fitbit information appeared first on XDA.

from XDA https://ift.tt/G4xVYvk
via IFTTT

Your Nest Hub is about to get cozy with Google Fit and Fitbit information

Activity metrics like number of steps and calories burned from Google Fit or Fitbit can be shown on your Nest display.

Source: Google

The post Your Nest Hub is about to get cozy with Google Fit and Fitbit information appeared first on XDA.

from XDA https://ift.tt/G4xVYvk
via IFTTT

Google’s “Pixel Fold” reportedly coming in Q4 2022

We’ve been hearing about a potential “Pixel Fold” for quite a long time now. Android 12L introduced a few changes tailored specifically for tablets and foldable smartphones, and it seemed that with Google Tensor, Google was finally beginning to take its hardware seriously. However, all of that seemed to dissipate when Ross Young from the Display Supply Chain Consultants (DSCC) stated in November of last year that the project was dead. It seems the device may be back on track though, as he’s now tweeted more information about what to expect from its display — and even when it may launch.

Z Fold 4 and Google foldable will have similar sized foldable displays, but the Google cover display will be quite a bit smaller at 5.8″. This should mean it will have a wider aspect ratio than the Samsung 6.19″ Fold 4. Hear more at our conference next week.

— Ross Young (@DSCCRoss) May 2, 2022

The biggest takeaway from Young’s tweet is that Google’s “Pixel Fold” foldable handset should arrive in Q4 of 2022. Its launch could potentially be soon after the release of Android 13, with the platform update having been shown to offer better support for foldable devices. Even better is its rumored price point, which has been reported to be much lower than its competitors at $1400. That would make it $400 less than the Samsung Galaxy Z Fold 3, $400 more than the Galaxy Z Flip 3, but $800 more than the cheapest Google Pixel 6.

Not only did Young offer insight on Google’s upcoming foldable smartphone, but Samsung’s as well. He states that both devices will have similar-sized inner displays and the main differentiating factor will be their outer displays. Google’s foldable handset will apparently have a smaller outer display coming in at 5.8-inches, whereas Samsung’s Galaxy Z Fold 4 will come in at 6.19-inches.

Despite Google’s handset having a smaller display, it will potentially have a wider aspect ratio, possibly similar to the OPPO Find N. The outer display found on Samsung’s Galaxy Z Fold 3 is a common sticking point, as its slimness makes it hard to use at times.

The post Google’s “Pixel Fold” reportedly coming in Q4 2022 appeared first on XDA.

from XDA https://ift.tt/N1HSfLC
via IFTTT