Slashdot reader Soul_Predator writes: Vanilla OS is Ubuntu on stock GNOME, with on-demand immutability and package selection freedom. It is currently a beta project, with a stable release planned for the next month.
"The first-time setup process is a breeze to experience," writes It's FOSS News, applauding how it lets uses choose and enable Flatpak/Snap/AppImage.

Overall, a package manager that installs applications utilizing a container, getting the ability to choose your package managers, on-demand immutability, and vanilla GNOME make it seem like a good deal to keep an eye on... I'd say it is a project that I believe a lot of users will appreciate.

You can download the ISO by joining its Discord channel for now. The ISO is not yet publicly available to all. Take a look at its documentation if you are curious. However, as per the roadmap, they plan to have a release candidate soon enough.

Nearly six years after the Pebble smartwatch was purchased by Fitbit and discontinued, a new Pebble app for Android has been released by the Rebble Alliance, a group that has kept Pebble viable for its users since Fitbit shut down Pebble's servers in mid-2018," writes Ars Technica's Kevin Purdy. "Pebble version 4.4.3 makes the app 64-bit so it can work on the mostly 64-bit Pixel 7 and similar Android phones into the future. It also restores a caller ID function that was hampered on recent Android versions." From the report: Most notably, the app is "signed using the official Pebble keys," with Google Fit integration maintained, but isn't available through Google's Play Store. Google acquired Fitbit for $2.1 billion, making it the steward of Pebble's remaining IP and software pieces. Katharine Berry, a key Rebble coder and leader, works on Wear OS at Google and was one of the first to tweet news of the new update, "four years after 4.4.2." That was the last Play Store update to the Pebble app from Pebble developers, one that freed up many of the app's functions to be replaced by independent servers.

That's exactly where Rebble picked up, providing web services to Pebble watches, including (for paying subscribers) voice dictation. But those services still relied on the core Pebble app to connect the watch and smartphone. If Android did make the leap to a 64-bit-only OS, it could have left Pebble/Rebble users in the lurch. Berry's post on r/pebble offers "thanks to Google for providing us with one last update!" This is, to be sure, not the typical outcome of products that have been acquired by Google, even if second-hand.

According to Protocol, Amazon and Google have struck a deal in recent months that allows Fire TV models to be produced by Android TV partners. From the report: As a result of that deal, Amazon has been able to work with a number of consumer electronics companies -- including not only TCL, but also Xiaomi and Hisense -- to vastly expand the number of available smart TVs running Fire TV OS. All of these companies were previously barred from doing so under licensing terms imposed by Google. The agreement may also alleviate some of the pressure Google has been feeling as regulators around the world have investigated its Android platform. However, some experts are skeptical a singular deal will address the overarching concerns with Google's operation and licensing of Android to third parties.

The deal between Amazon and Google resolves a yearslong dispute over licensing restrictions Google imposes on hardware manufacturers that make Android-based phones, TVs, and other devices. In order to gain access to Google's officially sanctioned version of Android as well as the company's popular apps like Google Maps and YouTube, manufacturers have to sign a confidential document known as the Android Compatibility Commitment. The ACC prevents manufacturers from also making devices based on forked versions of Android not compatible with Google's guidelines. The ACC, which was previously known as the Anti-Fragmentation Agreement, had long been an open secret in industry circles. Its full impact on the smart TV space became public when Protocol reported terms of the agreement in March of 2020 and outlined how the policy effectively barred companies like TCL from making smart TVs running any forked version of Android, including Amazon's Fire TV OS.

Google has been justifying these policies by pointing to the harmful consequences of Android fragmentation, positing that the rules assured developers and consumers that apps would run across all Android-based devices. However, the crux of Google's requirements is that they apply across device categories. By making a Fire TV-based smart TV, TCL would have effectively risked losing access to Google's Android for its smartphone business -- a risk the company, and many of its competitors that develop both smartphones and TVs, weren't willing to take. At the time, both Google and Amazon declined to comment on the dispute. However, Amazon was a lot more forthcoming when it talked to Indian regulators for a wide-ranging probe into Google's Android policies. "Given the breadth of the anti-fragmentation obligations, Amazon has also experienced significant difficulties in finding [original equipment manufacturer] partners to manufacture smart TVs running its Fire OS," the company's Indian subsidiary told regulators in a submission that was included in last week's report. Amazon told regulators that "at least seven" manufacturers had told the company they weren't able to make Fire TV-based smart TVs because of Google's restrictions.

"In several cases, the OEM has indicated that it cannot work with Amazon despite a professed desire to do so in connection with smart TVs," Amazon said in its submission. "In others, the OEM has tried and failed to obtain 'permission' from Google."

An anonymous reader shares a report: Last week, the Competition Commission of India published a damning report, alleging that Google was preventing major TV manufacturers from adopting Amazon's Fire TV operating system. This Thursday, Amazon announced that TCL, one of the manufacturers at the center of the dispute, is releasing two TV sets running its Fire TV software in Europe this fall. The unveiling of the two TV models is the direct result of a deal Google and Amazon struck in recent months, Protocol has learned from a source close to one of the parties involved in the agreement. As a result of that deal, Amazon has been able to work with a number of consumer electronics companies -- including not only TCL, but also Xiaomi and Hisense -- to vastly expand the number of available smart TVs running Fire TV OS. All of these companies were previously barred from doing so under licensing terms imposed by Google.

An anonymous reader shares a report: Microsoft is still struggling to learn what exactly it takes to be a successful Android manufactuer. The company's first self-branded Android phones, the dual-screened Surface Duo and Surface Duo 2, have tried to resurrect Microsoft's mobile ambitions after the death of Windows Phone. They leave a lot to be desired, though, and the first version went through some embarrassing fire sales. An ongoing knock against the devices has also been Microsoft's very slow OS updates. Unlike, say, Windows and Windows Update, Google's expensive and labor-intensive Android update process puts the responsibility for updates on the hardware seller, and a big part of being a good Android OEM is how quickly you can navigate this complicated process. Microsoft is proving to not be good at this.

This week, Microsoft announced the Surface Duo and Surface Duo 2 are finally getting Android 12L, an OS update that came out in March. That puts that company at a more than seven-month update time, which is worst-in-class for a flagship device, especially for one costing the $1,499 Microsoft is charging for the Duo 2. The company took a prolonged 14 months to ship Android 11 to the Surface Duo, so at least it's improving!

Starting with macOS Ventura, released this week, the built-in Preview app on Mac no longer supports PostScript (.ps) and Encapsulated PostScript (.eps) files, according to a new Apple support document. MacRumors reports: Preview can still be used to open these files on macOS Monterey and earlier. Apple did not provide a reason for the change. Apple recommends using other third-party Mac apps that can view or convert PostScript files. It also remains possible to print .ps and .eps files by dragging them into a Mac's printer queue [...].

Developed by Adobe in the 1980s, the .ps and .eps file formats were once widely used for desktop publishing/printing purposes. PostScript was the basis of rendering on the NeXT operating system, and was mostly replaced by the PDF format in Mac OS X.

An anonymous reader quotes a report from Ars Technica: Generically, passkeys refer to various schemes for storing authenticating information in hardware, a concept that has existed for more than a decade. What's different now is that Microsoft, Apple, Google, and a consortium of other companies have unified around a single passkey standard shepherded by the FIDO Alliance. Not only are passkeys easier for most people to use than passwords; they are also completely resistant to credential phishing, credential stuffing, and similar account takeover attacks.

On Monday, PayPal said US-based users would soon have the option of logging in using FIDO-based passkeys, joining Kayak, eBay, Best Buy, CardPointers, and WordPress as online services that will offer the password alternative. In recent months, Microsoft, Apple, and Google have all updated their operating systems and apps to enable passkeys. Passkey support is still spotty. Passkeys stored on iOS or macOS will work on Windows, for instance, but the reverse isn't yet available. In the coming months, all of that should be ironed out, though.

Passkeys work almost identically to the FIDO authenticators that allow us to use our phones, laptops, computers, and Yubico or Feitian security keys for multi-factor authentication. Just like the FIDO authenticators stored on these MFA devices, passkeys are invisible and integrate with Face ID, Windows Hello, or other biometric readers offered by device makers. There's no way to retrieve the cryptographic secrets stored in the authenticators short of physically dismantling the device or subjecting it to a jailbreak or rooting attack. Even if an adversary was able to extract the cryptographic secret, they still would have to supply the fingerprint, facial scan, or -- in the absence of biometric capabilities -- the PIN that's associated with the token. What's more, hardware tokens use FIDO's Cross-Device Authentication flow, or CTAP, which relies on Bluetooth Low Energy to verify the authenticating device is in close physical proximity to the device trying to log in. "Users no longer need to enroll each device for each service, which has long been the case for FIDO (and for any public key cryptography)," said Andrew Shikiar, FIDO's executive director and chief marketing officer. "By enabling the private key to be securely synced across an OS cloud, the user needs to only enroll once for a service, and then is essentially pre-enrolled for that service on all of their other devices. This brings better usability for the end-user and -- very significantly -- allows the service provider to start retiring passwords as a means of account recovery and re-enrollment."

In other words: "Passkeys just trade WebAuthn cryptographic keys with the website directly," says Ars Review Editor Ron Amadeo. "There's no need for a human to tell a password manager to generate, store, and recall a secret -- that will all happen automatically, with way better secrets than what the old text box supported, and with uniqueness enforced."

If you're eager to give passkeys a try, you can use this demo site created by security company Hanko.

It's a major Apple update day, as the company is rolling out new versions of its iPhone, iPad and Mac operating systems. While iPhone users at large have already had a taste of iOS 16, this will be the first time that most folks will get their hands on iPadOS 16 and macOS Ventura. From a report: Apple delayed the release of iPadOS 16 amid reports suggesting it needed more time to polish up the Stage Manager multitasking feature (which we felt was unrefined in an early iPadOS 16 beta). In fact, Apple said it was skipping a public release of iPadOS 16 and going straight to version 16.1 -- just in time for the company's latest iPad Pro and entry-level iPad shipping this week.

The latest version of the iPad operating system will include many of the same updates as iOS 16, including significant changes to Mail, Safari, Messages and other key apps. There are more collaboration-centric features, while the Weather and Clock apps are finally coming to iPad. External display support for Stage Manager will arrive within the next couple of months. Also later this year, Apple will release a collaborative productivity iPad app called Freeform. It seems like a souped-up whiteboard where users can sketch out ideas with Apple Pencil. The company says you'll be able to attach just about any kind of file to the canvas, including images, videos, audio, PDFs, documents and URLs, and preview the content inline.

A leaker has claimed that Apple is working on a version of macOS exclusive for the M2 iPad Pro, with it expected at some point in 2023. Apple Insider reports: Leaker Majin Bu's sources have shared that Apple is working on a "smaller" version of macOS exclusively for the M2 iPad Pro. It is said to be codenamed Mendocino and will be released as macOS 14 in 2023. Testing is being done with a 25% larger macOS UI so it is suitable for touch. However, apps run on the product would still be iPad-optimized versions, not macOS ones.

It isn't clear why Apple would move the iPad to a macOS interface in a half-step like this. Those clamoring for macOS on iPad do so for the software more than the interface. [...] The other possible explanation is this wasn't macOS at all. Apple could be working to bring iPadOS even closer to macOS by adding a Menu Bar and other Mac-like interactions. It already introduced a Mac windowing feature in iPadOS 16 called Stage Manager, this could be the next iteration. Majin Bu also suggests that the exclusivity to M2 iPad Pro could be a marketing push. If the feature is only available on that iPad, more people would buy it.

An anonymous reader quotes a report from BetaNews: Slack developer Felix Rieseberg released Windows 95 as an Electron app four years ago, updating it shortly afterwards to allow it to run gaming classics like Doom. Now he rolls out a new version which can run on any Windows, Mac or Linux system. Based on the Electron framework, Rieseberg's Windows 95 is written entirely in JavaScript, so it doesn't run as smoothly as it would if it was a native app, but you shouldn't let that put you off.

This is the second update of the year, which brings it up to version 3.1.1 and includes two important changes:

- Upgraded from Electron v18 to Electron v21 (and with it, Chrome and Node.js)
- Upgraded v86 (sound is back!)

The earlier update (in June) brought the software up to 3.0.0 and introduced the following changes:

- Upgraded from Electron v11 Electron v18 (and with it, Chrome and Node.js)
- Upgraded v86 (now using WASM)
- Upgraded various smaller dependencies
- Much better scaling on all platforms
- On Windows, the link to OSFMount was broken and is now fixed.
- On Windows, you can now see a prettier installation animation.
- On Windows, windows95 will have a proper icon in the Programs & Features menu. You can download the latest version of the Windows 95 app for Windows, macOS, and Linux at their respective links.

Longtime Slashdot reader lazyeye writes: The 53rd release of OpenBSD, version 7.2, has officially been released. Support for new platforms such as the Ampere Altra, Apple M2 chip, and support for Lenovo ThinkPad x13s and other machines using the Qualcomm Snapdragon 8cx Gen 3 (SC8280XP) SoC are now included, along with various kernel improvements. The announcement with all the details are available at the link [here] from the openbsd-announce mailing list.

A new report from The Information details more changes Google CEO Sundar Pichai's budget cuts are having across the company, with some divisions surviving and others getting ominous resource cuts. From a report: First, we have news that the hardware division, other than losing laptops, seems mostly safe. Google's biggest Android partner, Samsung, is in decline in many established markets, and Apple is hitting an all-time high in US market share last quarter. The report says Google views Apple as more of a problem than it has in the past, thanks to worries that regulators might shut down the usual multi-billion-dollar Google/Apple agreement to put Google Search on iPhones. If iPhones stop showing Google ads, the rise of Apple and fall of Samsung is one of the few things that could actually be a major problem for Google's revenue.

According to the report, Google views itself as the solution to this problem. As a hedge against what the report calls the "further decline" of Samsung, Google is "doubling down" on its investment in Pixel hardware. Google is apparently doing this by "moving product development and software engineering staff working on features for non-Google hardware to work on Google-branded devices." The goal here is to not spend more money, so Google is apparently sacrificing partner devices to focus on the Pixel division. So what projects are seeing cuts? Google TV is one, with the report saying: "Executives also have discussed moving some product managers working on Google TV software for television sets" to Wear OS and the Pixel Tablet. This is the only OS called out as specifically receiving less OS development. A lot of this report seems to focus on cuts to Google Assistant's support for specific form factors, which is strange since Google Assistant is more or less the same on every platform. The whole point of the Assistant is one reliable, predictable voice assistant that lives everywhere, and it's not clear what platform-specific support needs to be done other than whipping up an app that can receive audio and read back results.

Last Friday, Google announced the release of KataOS, a security-minded operating system focused on embedded devices running ambient machine learning workloads. As Phoronix notes, it uses the Rust programming language and is "built atop the seL4 microkernel as its foundatin." From Google's Open-Source Blog: As the foundation for this new operating system, we chose seL4 as the microkernel because it puts security front and center; it is mathematically proven secure, with guaranteed confidentiality, integrity, and availability. Through the seL4 CAmkES framework, we're also able to provide statically-defined and analyzable system components. KataOS provides a verifiably-secure platform that protects the user's privacy because it is logically impossible for applications to breach the kernel's hardware security protections and the system components are verifiably secure. KataOS is also implemented almost entirely in Rust, which provides a strong starting point for software security, since it eliminates entire classes of bugs, such as off-by-one errors and buffer overflows.

The current GitHub release includes most of the KataOS core pieces, including the frameworks we use for Rust (such as the sel4-sys crate, which provides seL4 syscall APIs), an alternate rootserver written in Rust (needed for dynamic system-wide memory management), and the kernel modifications to seL4 that can reclaim the memory used by the rootserver. KataOS code is being worked on via GitHub under the AmbiML umbrella.

An anonymous reader quotes a report from XDA Developers: As it turns out, the Google Pixel 7 series appears to be the first set of Android smartphones that only support 64-bit applications. [Android expert Mishaal Rahman first reported the news.] Rahman later corrected himself to say that it's a 64-bit Zygote but a 32-bit and 64-bit userspace, not a 64-bit only build of Android 13 as initially reported. This certainly lends credence to the claim that the Google Pixel tablet may come with a 64-bit only build of Android 13, though.

What this means is that for any apps that don't have 64-bit libraries, you won't be able to install them. This includes older versions of apps such as Jetpack Joyride and even older, completely defunct apps like Flappy Bird. It's not as if Tensor G2 doesn't support it either -- its three different cores all support AArch32 execution. Google could have enabled 32-bit support as they have done in its previous smartphones. Listing the Android Binary Interfaces (ABI) returns that there is nothing present for "armeabi-v7a" or "armeabi". "arm64-v8a" support is listed, but as per the Android documentation, it only supports the AArch64 instruction set.

What does this mean, and does it have any benefits? Most benefits won't really be visible to consumers, as these improvements are primarily found in heightened security, better performance, and reduced processing cost thanks to the lack of additional ABIs. All apps on the Google Play Store have had to have 64-bit support since August 2019, and the company stopped serving 32-bit apps that don't have any 64-bit support last year.

Google has announced what it's calling "the world's first laptops built for cloud gaming," less than two weeks after announcing plans to shut down Stadia. Forbes reports: Google says the Acer Chromebook 516 GE, ASUS Chromebook Vibe CX55 Flip and Lenovo Ideapad Gaming Chromebook all have refresh rates of at least 120Hz, displays with up to 1600p resolution, immersive audio and, critically for cloud gaming, WiFi 6 or 6E connectivity. Some models have RGB keyboards too. Subject to availability, you may get a SteelSeries Rival 3 gaming mouse at no extra cost if you pick up one of these Chromebooks. All three laptops were benchmarked by GameBench to ensure that they're capable of running games at 120 frames per second at 1080p resolution. You should get input latency of under 85 ms as well. Google notes that's "console-class" input latency.

[...] Google is bringing some neat cloud gaming features to these Chromebooks. For one thing, the devices will support Xbox Cloud Gaming, Amazon Luna and NVIDIA GeForce Now. In the latter case, Google worked with NVIDIA to ensure these Chromebooks support GeForce Now's highest RTX 3080 tier. That enables cloud gaming at 120 fps at a resolution of 1600p on these systems, which come with the GeForce Now app preinstalled. You'll also be able to install Xbox Cloud Gaming as a web app on your Chromebook. Additionally, these Chromebooks will come with three-month trials for both the GeForce Now RTX 3080 tier and Amazon Luna. Meanwhile, it could be pretty easy for you to find and start playing games on these services through ChromeOS. If you search for a game in the launcher (i.e. through the Everything Button), you'll see where it is available. You'll then be able to load up the game with a single click. To begin with, this feature will be compatible with GeForce Now and the Play Store. "It's good to see that Google hasn't entirely given up on cloud gaming," adds Forbes. "Still, the timing of this announcement comes at a very odd time."

A new resource featuring interactive Q&A's and one-on-ones for developers has launched today called "Ask Apple." 9to5Mac reports: Apple announced the new developer series in a newsroom post today: "Developers participating in Ask Apple can inquire about a variety of topics, such as testing on the latest seeds; implementing new and updated frameworks from Worldwide Developers Conference (WWDC); adopting new features like the Dynamic Island; moving to Swift, SwiftUI, and accessibility; and preparing their apps for new OS and hardware releases. Ask Apple is free of charge and registration is open to all members of the Apple Developer Program and the Apple Developer Enterprise Program."

Ask Apple will kick off with the first round of "opportunities" from October 17-21. Apple says it will be an ongoing series. 9to5Mac highlights what you can expect from "Ask Apple": - Ask questions to various Apple team members through Q&As on Slack or in one-on-one office hours
- Q&As allow developers to connect with Apple evangelists, engineers, and designers to get their questions answered, share their learnings, and engage with other developers around the world
- Office hours are focused on creating and distributing compelling apps that take advantage of the latest in technology and design
- Developers can ask for code-level assistance, design guidance, input on implementing technologies and frameworks, advice on resolving issues, or help with App Review Guidelines and distribution tools
- Office hours will be hosted in time zones around the world and in multiple languages

Nearly 43 percent of millions of devices studied by asset management provider Lansweeper are unable to upgrade to Windows 11 due to the hardware requirements Microsoft set out for the operating system. The Register reports: Lansweeper said 42.76 percent of the estimated 27 million PCs it tested across 60,000 organizations failed the CPU test, albeit better than the 57.26 percent in its last test a year ago. Altogether 71.5 percent of the PCs failed the RAM test and 14.66 percent the TPM test. "We know that those who can't update to Windows 11... will continue to use Windows 10," said Roel Decneut, chief strategy officer at Lansweeper, whose customers include Sony, Pepsico, Cerner, MiT and Hilton hotels. He said that even if enterprises are prepared to upgrade their PC fleet to meet the system requirements of Microsoft's latest OS, there are "broader issues affecting adoption that are out of Microsoft's control." "Global supply chain disruption has created chip a processor shortage, while many are choosing to stick with what hardware they have at the moment due to the global financial uncertainty."

Other findings from Lansweeper show adoption rates for the latest OS are improving, running on 1.44 percent of computers versus 0.52 percent in January. This means the latest incarnation has overtaken Windows 8 in the popularity stakes but remains behind market share for Windows 7, despite that software going end of life in January 2020. Adoption is, unsurprisingly, higher in the consumer space. Some 4.82 percent of the biz devices researched were running an OS that wasn't fully supported and 0.91 percent had servers in their estate that are end of life.

An anonymous reader quotes a report from Ars Technica: It's still possible to learn a lot of interesting things about old operating systems. Sometimes, those things are already documented (on a blog post) that miraculously still exist. One such quirk showed up recently when someone noticed how Microsoft made sure that SimCity and other popular apps worked on Windows 95. A recent tweet by @Kalyoshika highlights an excerpt from a blog post by Fog Creek Software co-founder, Stack Overflow co-creator, and longtime software blogger Joel Spolsky. The larger post is about chicken-and-egg OS/software appeal and demand. The part that caught the eye of a Hardcore Gaming 101 podcast co-host is how the Windows 3.1 version of SimCity worked on the Windows 95 system. Windows 95 merged MS-DOS and Windows apps, upgraded APIs from 16 to 32-bit, and was hyper-marketed. A popular app like SimCity, which sold more than 5 million copies, needed to work without a hitch.

Spolsky's post summarizes how SimCity became Windows 95-ready, as he heard it, without input from Maxis or user workarounds: "Jon Ross, who wrote the original version of SimCity for Windows 3.x, told me that he accidentally left a bug in SimCity where he read memory that he had just freed. Yep. It worked fine on Windows 3.x, because the memory never went anywhere. Here's the amazing part: On beta versions of Windows 95, SimCity wasn't working in testing. Microsoft tracked down the bug and added specific code to Windows 95 that looks for SimCity. If it finds SimCity running, it runs the memory allocator in a special mode that doesn't free memory right away. That's the kind of obsession with backward compatibility that made people willing to upgrade to Windows 95."

Spolsky (in 2000) considers this a credit to Microsoft and an example of how to break the chicken-and-egg problem: "provide a backwards compatibility mode which either delivers a truckload of chickens, or a truckload of eggs, depending on how you look at it, and sit back and rake in the bucks." Windows developers may have deserved some sit-back time, seeing the extent of the tweaks they often have to make for individual games and apps in Windows 95. Further in @Kalyoshika's replies, you can find another example, pulled from the Compatibility Administrator in Windows' Assessment and Deployment Kit (ADK). A screenshot from @code_and_beer shows how Windows NT, upon detecting files typically installed with Final Fantasy VII, will implement a fittingly titled compatibility fix: "Win95VersionLie." Simply telling the game that it's on Windows 95 seems to fix a major issue with its operation, along with a few other emulation and virtualization tweaks. "Mike Perry, former creative director at Sim empire Maxis (and later EA), noted later that there was, technically, a 32-bit Windows 95 version of Sim City available, as shown by the 'Deluxe Edition' bundle of the game," adds Ars. "He also states that Ross worked for Microsoft after leaving Maxis, which would further explain why Microsoft was so keen to ensure people could keep building parks in the perfect grid position to improve resident happiness."

Samsung has confirmed the first third-party smart TV makers to ship with its Tizen operating system (OS), with several manufacturers preparing to launch Tizen-powered TVs this year across Europe and Australasia. From a report: Tizen, for the uninitiated, is a Linux-based OS hosted by the Linux Foundation for more than a decade, though Samsung has been the primary developer and driving force behind the project, using it across myriad devices, including smartwatches, kitchen appliances, cameras, smartphones and TVs.

Although Samsung has essentially abandoned Tizen in smartphones and smart watches, TVs have remained fertile ground for Tizen to flourish, chiefly due to the fact that Samsung is the biggest selling TV maker globally. But while recent figures from Dataxis show that Tizen's market share in 2020 was roughly one-third in terms of installation base, the number has been slowly creeping downward with the likes of Android TV and Roku edging upward.

An anonymous reader quotes a report from Ars Technica: Google is clawing its way back into wearable relevance. Today the company took the wraps off what is officially its first self-branded smartwatch: the Pixel Watch. Google started revamping its wearable platform, Wear OS, in partnership with Samsung. While Wear OS 3, the new version of Google's wearable platform, technically launched with the Galaxy Watch 4 last year, this is the first time we'll be seeing an unskinned version on a real device. First up: prices. Google is asking a lot here, with the Wi-Fi model going for $349 and the LTE version clocking in at $399. The Galaxy Watch 4, which has a better SoC, and the Apple Watch SE, which has a way, way better SoC, both start at $250. Google is creating an uphill battle for itself with this pricing.

Google and Samsung's partnership means the Pixel Watch is running a Samsung Exynos 9110 SoC, with a cheap Cortex M33 co-processor tacked on for low-power watch face updates and 24/7 stat tracking. This SoC is a 10 nm chip with two Cortex A53 cores and an Arm Mali T720 MP1 GPU. If you can't tell from those specs, this is a chip from 2018 that was first used in the original Samsung Galaxy Watch. For whatever reason, Google couldn't get Samsung's new chip from the Galaxy Watch 4, an Exynos W920 (a big upgrade at 5 nm, dual Cortex A55s, and a Mali-G68 MP2 GPU). It's hard to understand why this is so expensive.

The display is a fully circular 1.6-inch OLED with a density of 320 ppi (that should mean around 360 pixels across). The only size available is 41 mm, the cover is Gorilla Glass 5, and the body is stainless steel in silver, black, or gold. It has 2GB of RAM, 32GB of eMMC storage, NFC, GPS, only 2.4 GHz Wi-Fi 802.11n support (Wi-Fi 4), and a 294 mAh battery. For sensors, you get SPO2 blood oxygen, heart rate, and an ECG sensor. It's water-resistant to 5 ATM, which means you're good for submersion, hand washing, and most normal water exposure. Usually 10 ATM is preferred for serious sports swimming, but the Apple Watch is 5 ATM, and Apple does all sorts of swimming promos. Google's black UI background does a good job of hiding exactly how large the display is in relation to the body, but a few screenshots reveal just how big the bezels are around this thing. They are big. Real big. Like, hard-to-imagine-we're-still-doing-this-in-2022 big. Other things to note: the watch bands are proprietary, it'll be able to charge to 50 percent in 30 minutes, will work with any Android phone running version 8.0 and newer, and features Fitbit integration.

"Unlike the Pixel 7, which is expanding to 17 markets, the Pixel Watch is only for sale in eight countries: the US, Canada, UK, Germany, France, Australia, Japan, and Taiwan," adds Ars. "The watch is up for preorder today and ships October 13."

Further reading: Google Unveils Pixel 7 and Pixel 7 Pro Smartphones