LightBlog

jeudi 5 mai 2022

Samsung Galaxy Z Fold 3 vs Vivo X Fold: The Best Foldable Hardware or Superior Foldable Software?

Every new foldable phone that gets released should and will be compared against Samsung’s latest foldables. Samsung is the pioneer and originator of the product category, and for most of the world, Samsung’s foldables are still the only foldables they have access to. The latest challenger is the Vivo X Fold, which brings much of the same foldable hardware breakthroughs first introduced by Huawei’s Mate X2, plus it gets Vivo’s out-of-nowhere impressive camera system and Google Mobile Services support. How does Vivo’s foldable foray measure up against Samsung’s Galaxy Z Fold 3?

    Samsung Galaxy Z Fold 3
    As the most accessible large screen foldable phone, Samsung's Galaxy Z Fold 3 has a built-in advantage many of its competitors do not -- but despite this, Samsung mostly earns its status as the default option, as the Galaxy Z Fold 3 is still the most polished all-around foldable in the world.
    Vivo X Fold
    The latest challenger to Samsung's throne brings a near-flagship camera system, in-display fingerprint scanner(s), and a large, crease-free screen.
galaxy z fold 3 and vivo x fold

Vivo X Fold (left) and Galaxy Z Fold 3 (right)

Samsung Galaxy Z Fold 3 and Vivo X Fold: Specifications

Samsung Galaxy Z Fold 3 Vivo X Fold
CPU Snapdragon 888 Snapdragon 8 Gen 1
Dimensions and weight
  • Folded: 158.2 x 67.1 x 16.0mm
  • Unfolded: 158.2 x 128.1 x 6.4mm
  • Weight: 271g
  • Folded: 162.01mm x 74.5 x 14.6 mm
  • Unfolded: 162.01mm x 144.87mm x 7.4mm
  • Weight: 311g
Display Inner display:
  • 7.6-inch QXGA+ Dynamic -AMOLED 2X Display
  • 22.5:18 aspect ratio
  • 2208 x 1768
  • 120Hz

Cover display:

  • 6.2-inch HD+ Dynamic AMOLED 2X Display
  • 24.5:9 aspect ratio
  • 2268 x 832
  • 120Hz 
Inner display:
  • 8.03-inch AMOLED Samsung E5
  • LTPO
  • 2K (2200 x 1800)
  • 120Hz adaptive refresh rate
  • HDR10+
  • SCHOTT UTG

Cover display:

  • 6.53-inch AMOLED Samsung E5
  • FHD+
  • 120Hz refresh rate
  • HDR10+
Camera
  • 12MP Ultra-wide, f/2.2 ultra-wide, FoV 123-degree
  • 12MP Wide, f/1.8, Dual Pixel AF, OIS
  • 12MP Tele, 2x optical zoom, 10x digital zoom
  • 10MP front-facing selfie camera
  • 4MP front-facing under-screen selfie camera
  • 50MP Wide, f/1.75
  • 48MP ultra-wide
  • 12MP portrait camera
  • 8MP persicope camera with 5x optical zoom
Memory 12GB RAM, 256GB/512GB UFS 3.1 storage 12GB RAM, 256GB/512GB UFS 3.1 storage
Battery 4,400mAh dual battery 4,600mAh
Network LTE: Enhanced 4X4 MIMO, 7CA, LAA, LTE Cat. 20
5G
Water Resistance IPX8 None
Sensors Capacitive fingerprint sensor (side), Accelerometer, Barometer, Gyro sensor, Geomagnetic sensor, Hall sensor (analog), Proximity sensor, Light sensor, Wacom layer for stylus input Ultrasonic in-display fingerprint scanner (two, one on each screen), Accelerometer, Barometer, Gyro sensor, Geomagnetic sensor, Hall sensor (analog), Proximity sensor, Light sensor
OS Android 12
Colors Phantom Black, Phantom Green, Phantom Silver Blue, grey (vegan leather)
Price Starts at $1,799 Starts at 8,999 yuan (around $1,360)

About this comparison: This comparison was written after testing a Galaxy Z Fold 3 provided by Samsung Hong Kong for the past eight months, and a self-purchased Vivo X Fold I’ve been using for the past week. Neither company had any input in this article.


Samsung Galaxy Z Fold 3 vs Vivo X Fold: Design and Hardware

The Vivo X Fold follows the same inner fold design philosophy first established by the original Galaxy Fold (before Samsung decided to add a random Z in the branding), and fundamentally both the Vivo X Fold and the Galaxy Z Fold 3 work the same way: both are mini-tablets that fold like a book to become a phone-like form factor. The brands differ in screen sizes and aspect ratios. Samsung’s Galaxy Z Fold 3 uses a 7.6-inch screen with an 11.2:9 aspect ratio, meaning the screen is an upright rectangle — taller than it is wide. Vivo’s main screen is a larger 8-inch panel that, while still slightly taller than it is wide, comes closer to a square shape. Samsung’s larger screen is technically uninterrupted, as Samsung adopted under-screen camera technology that sees the selfie camera placed underneath the screen. Vivo’s X Fold uses a traditional hole-punch, so you can see the hole at all times

Vivo X Fold and Galaxy Z Fold 3 Vivo X Fold (left) and Galaxy Z Fold 3 (right)

When folded, the Galaxy Z Fold 3 is unusually narrow from left to right, taking on a form factor similar to a TV remote or a candy bar. The Vivo X Fold, meanwhile, has a shape closely resembling a normal slab smartphone in folded form. Because the Vivo X Fold has a larger form factor and a more advanced camera system, it is quite a bit heavier at 311g to 271g. I must say I have gotten used to X Fold’s weight after several days, but the first 24 hours or so were a bit of a shocker, as my wrist felt the extra weight when holding the phone. Samsung’s foldable uses a traditional Gorilla Glass 5 back, while Vivo’s X Fold comes in a vegan leather finish. I will talk about the camera system in a dedicated camera system further down the article.

Galaxy Z Fold 3 (left) and Vivo X Fold (right) Galaxy Z Fold 3 (left) and Vivo X Fold (right)

Personally, I prefer Vivo’s aspect ratios, because I find Samsung’s narrower outside screen a bit cramped to type on. However, I have heard peers say they prefer Samsung’s approach because the Galaxy Z Fold 3 is a much easier “one-hand phone” when folded. I can see that point too, so it comes down to preferences.

Galaxy Z Fold 3, folded Vivo X Fold, folded

The phones do trade objective clear-cut wins. The Galaxy Z Fold 3 has an official IP water resistance rating, and the screen supports Samsung’s S-Pen stylus. On the other hand, Vivo’s display has a significantly less noticeable crease (both by sight and touch) and the hinge folds completely flat instead of leaving a gap.

Vivo (left) and Samsung's foldables. Vivo X Fold (left) and Galaxy Z Fold 3 (right)

Vivo's in-display fingerprint scanner is a flex more than anything, as I don't see much real-world benefits over a side-mounted scanner

The Vivo X Fold also houses an in-display fingerprint scanner — the first foldable to do so — while the Galaxy Z Fold 3 uses a side-mounted fingerprint scanner that’s embedded into the power button. To be honest, this is a flex more than anything, as I don’t feel the actual real-world benefits of having an in-display scanner compared to having a capacitive side-mounted scanner. What does annoy me more and more, is the crease in Samsung’s display. It’s not noticeable if I look at the display straight on, but I can always feel it, particularly when I’m using the S-Pen.

Using the S-Pen Pro on the Galaxy Z Fold 3 Vivo X Fold (left) along with the Galaxy Z Fold 3.

Since the Galaxy Z Fold 3 came out in H2 2021, it is using an older chip — the Qualcomm Snapdragon 888 — compared to the Vivo X Fold’s newer Snapdragon 8 Gen 1. But other than benchmark numbers, it’s very hard to tell the difference between the two SoCs in real-world usage.

fold 3 Vivo's hinge (blue) and Samsung's hinge (black) Vivo X Fold and Galaxy Z Fold 3

Samsung Galaxy Z Fold 3 vs Vivo X Fold: Cameras

As someone who likes to take a lot of street photography, my biggest complaint about the Galaxy Z Fold 3 has been its camera system: the triple 12MP system used by Samsung is dated hardware that doesn’t come close to matching the optics Samsung uses in its slab flagships. Every hallmark feature of the last two Galaxy Ultra cameras — a large image sensor for the wide lens and a Periscope zoom lens that can grab 10x optical shots — are missing from Samsung’s foldable phones. In fact, going by hardware, the Galaxy Z Fold 3’s camera system is just about on par with the two-year-old standard (non-Ultra) version of the Galaxy S20.

Vivo's X Fold, meanwhile, brings a camera system that is almost on par with its flagship X70 Pro Plus

Vivo’s X Fold, meanwhile, brings a camera system that is almost on par with its flagship X70 Pro Plus, consisting of a quad lens system with two zoom lenses, including a 5x Periscope zoom lens.

Vivo X Fold and Galaxy Z Fold 3 camera systems

Main camera

In good lighting conditions, and if you are just taking photos to be uploaded to social media, the Galaxy Z Fold 3’s main camera actually keeps up well against Vivo’s main camera.

Galaxy Z Fold 3, main camera Vivo X Fold, main camera Galaxy Z Fold 3, main camera Vivo X Fold, main camera

But if you move to challenging conditions like low light or against harsh backlight, then Vivo’s superior camera hardware and excellent HDR come into play.

Galaxy Z Fold 3, main camera Vivo X Fold, main camera Galaxy Z Fold 3, main camera Vivo X Fold, main camera

Ultra-wide

The quality gap widens here. The Galaxy Z Fold 3’s ultra-wide is just not flagship quality in 2022 — it has a tiny sensor, producing images that are noticeably soft on details at the edges, with slight barrel distortion to boot. Vivo’s ultra-wide also handles HDR much better.

Galaxy Z Fold 3, ultra-wide Vivo X Fold, ultra-wide Galaxy Z Fold 3, ultra-wide Vivo X Fold, ultra-wide

If you look at the pavement in the above set of photos, you can see Samsung’s image has lost most of the texture of the cement floor. The building at the left edge of the frame is also a smudgy mess.

If you zoom into the photos, you can see Samsung’s ultra-wide images are very soft on details.

100% crops of two samples

100% crops, Galaxy Z Fold 3 (left) and X Fold (right).

Zoom

This is only a contest at the 2x zoom range, as both phones have a dedicated 2x telephoto lens; anything beyond, 5x or 10x (which is the Galaxy Z Fold 3’s maximum zoom distance), it’s a clear win for Vivo due to the X Fold having a Periscope zoom camera.

Both phones do some post-shot editing: Samsung applies a lot of digital sharpening, while Vivo punches up the contrast, so reds are deeper.

Galaxy Z Fold 3, 5x Vivo X Fold, 5x

Samsung’s 5x shot above has lost all texture of the grass, and you can actually read the carved words on the pedestal in Vivo’s 5x shot.

Reference image (1x) Galaxy Z Fold 3, 10x Vivo X Fold, 10x

Selfie cameras

Both phones have two selfie cameras — one on each screen. Samsung takes an unusual approach with the inside selfie camera (on the main screen) by putting it underneath the display. Under-screen technology is still in its infancy right now, and Samsung’s offering is clearly gen-one. The under-screen selfie camera in the Galaxy Z Fold 3 is a measly 4MP shooter, and the part of the screen that covers the camera actually doesn’t look seamless. This means the Galaxy Z Fold 3’s inner selfie camera produces very soft, blurry images.

camera samples camera samples camera samples

To be honest, this is not an issue for me at all. One, because I personally don’t care for selfies, and two, there’s a more conventional selfie camera on the outside screen. Samsung’s idea seems to be prioritizing main screen immersion over selfie camera — and I agree with this.

Moving to the outside main selfie cameras, both cameras pump out equal quality images. My skin tone is more accurate in Vivo’s selfies, for what it’s worth.

Galaxy Z Fold 3, selfie camera (outside screen) Vivo X Fold, selfie camera (outside screen) Galaxy Z Fold 3, selfie camera (outside screen) Vivo X Fold, selfie camera (outside screen)

Videos

Video performance is, in my opinion, a virtual tie. Both phones’ main and ultra-wide cameras can shoot 4K/30fps videos with excellent exposure and electronic image stabilization. During the day, walk-and-talk footage is smooth; at night, EIS takes a hit obviously, but both are still pretty good and close enough to flagship Android video stabilization standards. I notice Samsung applies a noticeable noise cancellation to audio, which works in my favor in Hong Kong as the city is full of unhealthy levels of street noise. Still, my voice can sound a bit faint in Samsung’s footage. Ultra-wide footage at night has soft details for both phones, but Vivo’s X Fold fares a bit better.

Vivo’s X Fold can also shoot 8K video footage with the main camera, but I don’t care about shooting in 8K in 2022, and to be honest, neither should most of you.

I think despite the fact the Samsung Galaxy Z Fold 3’s main camera and 2x zoom held up surprisingly well against Vivo’s cameras, the overall better camera system is obviously the Vivo X Fold. The difference in quality between the ultra-wide camera and any zoom photos beyond 5x is jarring.


Samsung Galaxy Z Fold 3 vs Vivo X Fold: Software

Both phones run Android 12 with each brand’s Android skin on top — One UI for the Galaxy Z Fold 3, OriginOS for the X Fold. Most readers should be familiar with One UI. In case you don’t, OneUI is a relatively clean and minimal Android skin that doesn’t get in the way of Google’s plain version of Android much. In terms of navigating through the UI, the only thing Samsung does that really deviates from stock Android is that One UI’s app tray cycles horizontally instead of vertically, and the occasional reminders to use Bixby or Samsung Pay (both of which can be disabled so they stay out of the way forever, unlike Apple, whose iOS nudges you to sign up for Apple Pay every week or so).

Vivo’s OriginOS, on the other hand, is a major departure from Android. It’s a bombastic UI, filled with heavy animations, giant widgets of varying sizes (that look a bit similar to iOS’ widgets), and a bunch of things that deviate from the Android most western users are used to. For example, by default there is no app tray; a swipe up instead brings a tray that houses OriginOS’ giant, interactive widgets, which Vivo calls Nano-kits. Also by default, the notification panel is separated from the control toggles. The good news is that you can cancel both of these changes if you like and revert back to a more Android-like setup.

There are gestures galore, like swiping from one side of the screen to quickly launch an app; swiping from the bottom corner of the screen to quickly launch AliPay or WeChat Pay’s QR code scanner (in China, you pay for almost everything with either of those apps); using three-finger swipes to grab screenshots or launch split-screen mode.

Samsung's One UI is just much more well optimized for a foldable phone right now than Vivo's OriginOS

While I personally enjoy colorful, animation-heavy UI like OriginOS (and to a lesser extent, MIUI) and find OneUI’s animations a bit generic and boring, there’s no question Samsung’s Android skin is superior for me, and I think most western users. My biggest gripe with Vivo’s OriginOS is that it doesn’t handle multitasking well. For example, while OriginOS can launch some apps in a small floating window,  it seems only Vivo’s first-party apps or some popular Chinese apps can do this. Chrome, Slack, Twitter, YouTube, and WhatsApp all cannot be shrunken in floating form. For the record, these same apps can be shrunken into floating windows in Samsung’s OneUI.

So on the Vivo X Fold, the only multi-tasking I can do with apps like Slack, YouTube, Chrome, etc, is to split-screen. Even this is compromised: the Vivo X Fold will only split apps vertically (a line down the middle). For video apps like YouTube, splitting vertically doesn’t make sense, as splitting horizontally is better for videos. Samsung’s Z Fold 3 gives me the option to choose between vertical or horizontal split-screen; Vivo’s X Fold does not.

Some readers may think I’m being unfair, expecting a China-only phone to have full support for apps not widely used in China, like WhatsApp, YouTube, or Chrome. But OPPO’s Find N, which was also released just for China, has no such problems launching those same apps in floating window mode. ColorOS also lets me choose which method to split-screen, just like OneUI. The problem here is not region, but Vivo, whose software has always been heavy-handed to the point it breaks basic Android functionality. This was the case with FunTouch (Vivo’s global Android skin) for years up until 2020 or so, when FunTouch finally got polished enough for me not to hate it.

There are a myriad of other little things, like more apps supporting Samsung’s Flex Mode than Vivo’s version, or Vivo’s OriginOS breaking push notifications for many apps unless you dive deep into settings to whitelist the app. At this current stage, Samsung’s One UI is just much more optimized for a phone, especially a foldable one, than Vivo’s OriginOS.


Samsung Galaxy Z Fold 3 vs Vivo X Fold: Performance and Battery Life

Despite the difference in SoC, I saw no real performance difference between the two devices in terms of speed or mobile gaming — I am, however, not a hardcore mobile gamer. In folded form, I much prefer using the Vivo X Fold over the Galaxy Z Fold 3, as the wider screen just makes for a more natural experience. But in unfolded form, the Galaxy Z Fold 3’s upright rectangle shape is easier to hold with one hand, and displays apps better.

And despite the X Fold having a larger screen, most videos will show roughly the same size on both phones — the X Fold just has larger letterboxing. I do think the X Fold has louder, fuller speakers, however.

Using the vivo X fold with a keyboard.

Battery life is about equal for both devices too, meaning neither phone are endurance beasts but can last me a full 12- or 13-hour day out — albeit just barely. On lighter usage days like a weekday when I’m mostly seated staring at a laptop, the phones will make it to the end of the day with more than 30-40% left to spare.


Samsung Galaxy Z Fold 3 vs Vivo X Fold: Conclusion

Since the Vivo X Fold is only on sale in China and thus requires importing for most readers, the Galaxy Z Fold 3 is clearly the safer choice for those on the market for a new foldable. But Vivo’s lower starting retail price means that, even with the usual markups that come with importing a phone, the Vivo X Fold is still a bit cheaper than the Galaxy Z Fold 3, so importing isn’t entirely unrealistic, especially for enthusiasts.

And while I like the Vivo X Fold’s hardware better than Samsung’s Galaxy Z Fold 3 — I like the wider outside screen, superior camera system, and crease-less main screen — Samsung’s software is just way ahead right now. OriginOS’ multi-tasking issues in particular really frustrate me. What good is having a large 8-inch screen if I can’t even multitask properly?

vivo X Fold and Galaxy Z Fold 3

Still, much credit should be given to Vivo for creating a foldable that pulls off several hardware feats that Samsung has been unable to unwilling (more likely the latter) to do: give us a near-flagship camera system including a Periscope zoom lens, a crease-free display, and a price point that is barely more expensive than a premium slab flagship. Now if only Vivo would get its software right — and sell this thing outside of China.

    Samsung Galaxy Z Fold 3
    As the most accessible large screen foldable phone, Samsung's Galaxy Z Fold 3 has a built-in advantage many of its competitors do not -- but despite this, Samsung mostly earns its status as the default option, as the Galaxy Z Fold 3 is still the most polished all-around foldable in the world.
    Vivo X Fold
    The latest challenger to Samsung's throne brings a near-flagship camera system, in-display fingerprint scanner(s), and a large, crease-free screen.

The post Samsung Galaxy Z Fold 3 vs Vivo X Fold: The Best Foldable Hardware or Superior Foldable Software? appeared first on XDA.



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

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.”

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

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.”

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

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

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 9to5Googlea 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