Urgent.News

What's breaking now, across thousands of outlets.

Tech

Google Pixel officially re-releases App Lock in beta, Samsung Galaxy gets it too

It’s been a wild ride for Google Pixel’s App Lock feature, but the company is officially re-releasing the feature today, right alongside its debut on Samsung Galaxy devices. more…

Google Pixel officially re-releases App Lock in beta, Samsung Galaxy gets it too

Google has re-released the App Lock feature on its Pixel devices, alongside its debut on Samsung Galaxy devices. The feature was initially available on Pixel in an August beta build of Android 17 QPR2, which allowed users to hide apps, notifications, widgets, and data from AI services using biometric or PIN authentication. However, the feature was later removed in subsequent updates.

Google re-released the feature in the latest QPR3 Beta 3 for Pixel devices, which is set to be released to the stable track in early 2027. Samsung Galaxy devices, on the other hand, have already received the feature through the One UI 9.5 beta release, as it is built into Android 17 QPR2. Pixel devices will not receive the feature until QPR3, which is expected to be around March or so.

It is important to note that Pixel devices will still need to go through the update process to access the App Lock feature.

Written by urgent.news from 9to5Google's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

This story

This is one outlet's version. Read the fullest account.

Every outlet that reported this, and when →

Read the original at 9to5google.com →

More in Tech

A one-sample t statistic in Python: what the number actually compares

A two-point difference can be a big deal or ordinary sampling noise. The t statistic compares that difference with the estimated uncertainty in the sample mean.

  • One-sample t statistic compares sample mean to hypothesized value
  • Larger t value with smaller p-value indicates stronger evidence
  • Assumes independent normal observations for valid results

Case study (hypothetical): the provider disabled our webhook endpoint after a weekend of 500s, and nobody noticed for 9 days

Reliable HTTP cron and delayed-job scheduling with automatic retries and full run logs — delay.run This is a hypothetical case study, assembled from a pattern that turns up again and again with…

  • Provider disabled webhook endpoint after 9 days of 500 errors
  • Online booking platform experienced unnoticed 9-day downtime
  • Technical contact outdated email address led to disabled endpoint

More from Wednesday 18 November →