Google to Offer Granular Controls for Advanced Protection Mode in Android 16
Google is developing more granular controls for its Advanced Protection security mode introduced in Android 16. The upcoming changes will allow users to activate specific protections separately instead of enabling the full strict configuration at once.
Researchers at Android Authority found the new options while analyzing Google Play Services 26.36.30. A previously unseen section called Expert features is described as an additional protection layer that can apply individual restrictions.
One of the features expected to move into this section is USB Protection. This function prevents new USB connections while the device screen remains locked, protecting against physical attacks on Pixel 6 and later models. The trade-off is that fast charging may not start until the phone is unlocked.
Another planned option will let users disable automatic connection to open or otherwise unsafe Wi-Fi networks. People who frequently use public hotspots can turn this restriction off and manage the risks themselves.
The third component is intrusion detection. The related Intrusion Logging feature is already optional; it collects security logs and stores an end-to-end encrypted backup in the cloud.
Currently, once Advanced Protection is enabled, most of its components cannot be disabled individually. The new Expert features approach will let users keep the core security set while avoiding restrictions they do not need. Google has not yet officially announced the feature, so release timing remains unknown and the discovered settings may still change.
Related articles
Hydrat Project Builds Automated WireGuard Gateway for Resilient VLESS and Tor Routing
A developer has released Hydrat, a self-hosted gateway that connects devices via WireGuard while automatically managing VLESS and Tor backends to survive server blocks and quality degradation. The system maintains a pool of tested proxies, performs continuous health checks, and switches routes without requiring client-side profile changes. Two Go processes handle control logic and network enforcement separately, using SQLite for state and nftables plus Xray for traffic routing. TCP and UDP can be assigned independent exits, with geoip.dat support and custom rules to keep marketplace apps functional. The project emphasizes stability over direct connections and is designed for deployment on servers in Russian jurisdiction.
OpenAI Contractors Manually Review Real User Chats in Project Lily
OpenAI has engaged hundreds of external contractors to analyze actual user conversations with ChatGPT as part of its model improvement efforts. The reviewers, working under project Lily, examine real queries that may contain personal, medical, or other sensitive information despite the use of a Privacy Filter. Contractors summarize prompts, compare four model responses, and assign ratings from one to seven while flagging behaviors such as excessive sycophancy or inappropriate emojis. User identities are hidden and some data is filtered, yet OpenAI acknowledged that not all personal information is reliably removed. The same human review process is also employed by Anthropic for its Claude model. Users can opt out of future training use through account settings, although prior data remains unaffected.
UDP Proxies and QUIC Protocol: How Real IP Addresses Leak Through Anti-Detect Browsers
Anti-detect browser users relying on UDP-capable proxies face a hidden risk of real IP leakage when the browser fails to properly route UDP traffic. The QUIC protocol, which powers HTTP/3, runs over UDP and enables features like 0-RTT handshakes, independent streams, and connection migration that can bypass proxy routes. WebRTC connections using ICE, STUN, and TURN further increase exposure because they often attempt direct UDP paths outside the configured SOCKS5 proxy. Without deep network stack control such as TUN interfaces or socket interception, browsers may send WebRTC and QUIC packets through the host's real network interface. Aurorium Browser claims to solve this by natively supporting UDP proxying so that both QUIC and WebRTC traffic stays inside the tunnel. The article stresses that simply disabling WebRTC or forcing HTTP/2 fallback is insufficient and can itself create detectable anomalies for anti-fraud systems.
rkn-block-checker 0.6.0 Adds Local Web UI and Reduces False Positives on Anti-Bot Responses
The open-source tool rkn-block-checker received a major update in version 0.6.0 that improves accuracy when detecting Russian ISP censorship blocks. The previous version incorrectly flagged sites protected by anti-bot systems as blocked by Roskomnadzor because it searched for common stub-page strings without checking HTTP status codes. A new logic layer now separates rate-limit responses such as HTTP 429 from genuine provider stub pages that typically return 200 OK or 451. The release also introduces a fully local Web UI built with Python’s standard-library HTTP server and vanilla JavaScript, eliminating the need for heavy frameworks. Results stream in real time via NDJSON so users can watch checks complete without polling or WebSocket connections. The project remains available on PyPI and GitHub under the MIT license.