Google Enhances Android Backup Controls in Play Services Update, Adds Document Sync to Google Drive Amid Storage Limit Cut
Google is rolling out significant changes to the Android backup system, giving users greater control over what data is stored in the cloud while introducing new capabilities that could rapidly consume storage space on Google Drive.
In the latest update to Google Play Services version 26.25, the company has added a dedicated toggle for messaging backups, allowing users to separately enable or disable the automatic saving of SMS, MMS, and RCS conversations. Previously, these message types were backed up automatically without an easy way to opt out. Notably, RCS messages are now grouped under the MMS category, making the option less obvious to most users.
The backup settings can be found on most devices by navigating to Settings — Accounts and backup — Google Backup — Other device data. This section also includes options for call history and system settings, providing a centralized location for managing non-app data backups.
A more prominent addition is the new document backup feature. Android can now automatically upload files in formats such as DOC, PPT, XLS, PDF, and others to Google Drive, placing them in a folder named after the specific device. Users can also trigger a manual backup at any time. However, this functions as a one-time copy rather than true synchronization, meaning changes made to the original file on the device will not automatically reflect in the cloud version.
These enhancements arrive alongside Google's decision to reduce the free storage allowance from 15 GB to just 5 GB, with all Android backup data now counting toward this limit. While a standard backup typically occupies around 40 MB, including documents can quickly turn it into a much larger archive, potentially leading to storage warnings or the need to purchase additional space.
Overall, the update aims to make backups more flexible and useful for preserving important files, but users are advised to monitor their Google Drive quota carefully to avoid unexpected storage issues.
Related articles
Telegram macOS Developer Says 99.9% of Client Code Is Now Written by AI and Suggests Firing Manual Coders
Mike, the developer of the official Telegram client for macOS, stated that artificial intelligence now generates 99.9 percent of the messenger's client code. He argued that programmers who continue writing code manually should be dismissed. In a Telegram discussion, Mike cited the gram.org website as an example created entirely with AI assistance in a single day, with domain support from Pavel Durov. He also described adapting the iOS client for a foldable iPhone Duo overnight using Claude. According to Mike, even designers are now contributing to client code, and 80 to 90 percent of Telegram developers share his positive view of AI tools. When participants raised questions about code quality and security, Mike replied that AI also identifies and fixes vulnerabilities, claiming the resulting code is superior to human-written equivalents. He further announced plans to open a new GitHub repository for the macOS client source code, as the previous repository had not been updated for over a year.
Secure Boot on Arch Linux: Enabling Protection for UKI Without Replacing Factory Keys
A detailed guide explains how to configure Secure Boot on Arch Linux for Unified Kernel Images without replacing the motherboard's factory keys or relying on Microsoft certificates. The author chose the minimal-intervention approach of adding a custom key to the existing DB section via the UEFI interface instead of using sbctl enroll-keys or shim. The process begins with backing up existing keys to a FAT-formatted USB drive directly from the BIOS menu. New keys are then generated using sbsigntools and openssl, converted to DER format, and enrolled through the ASUS Prime 790-P UEFI interface. A post-hook script for mkinitcpio automatically signs the UKI after every kernel update, ensuring the entire unified image remains protected. The method preserves the original Microsoft and vendor certificates while adding only the user's own signing key.
What Server Logs Reveal About Attackers: Analyzing Suspicious Requests on Linux
Server logs provide critical insights into potential intrusions by recording events from the operating system, SSH authentication, and web applications. The guide explains how to examine Linux system journals with journalctl, review authentication logs on Debian and RHEL systems, and inspect Nginx access logs for unusual HTTP requests. Analysts learn to identify patterns such as rapid failed login attempts using multiple usernames from a single IP address, which may indicate brute-force or automated scanning activity. The article also covers counting the most active IP addresses with awk and sort commands while stressing the need to compare findings against normal traffic baselines. Additional recommendations include logging structured security events in JSON format with fields for timestamp, user ID, resource, and outcome, following OWASP guidelines. The text warns against storing sensitive data like passwords in logs and highlights limitations such as possible log tampering or unsynchronized server clocks. A practical seven-step investigation plan helps responders preserve evidence and verify hypotheses before taking action.
UserGate Details FPGA Acceleration to Turbocharge Next-Generation Firewalls
UserGate product manager Pavel Molodan explains why adding security features like IDS/IPS, SSL/TLS inspection, and application control turns a high-performance NGFW into a bottleneck. The company outlines four groups of acceleration methods, with a focus on FPGA-based hardware offloading for packet parsing, firewall rules, NAT, and encryption tasks. Research from 254 respondents shows strong demand for these functions in data center B2E segments at 50-200 Gbit/s. Experimental platforms including Katun-2 PCIe cards and the FG system demonstrate concrete gains, such as scaling IDPS from 5 to 90 Gbit/s and achieving 85 Gbit/s firewall throughput on EMIX profiles. FPGA delivers microsecond latency and better energy efficiency compared with CPU-only designs while preserving full NGFW functionality for elephant flows.