Android Introduces “Expanded Dark Mode” to Force a Dark Theme

Google is testing a powerful accessibility-focused feature in the second Android Canary build that forces Dark Mode on apps without native dark themes. Dubbed Expanded Dark Mode, it sits alongside the traditional “Standard” dark theme and brings remarkably better system-wide consistency—though not without caveats.

What’s new in Expanded Dark Mode?

Standard Dark Mode: Applies a dark theme only to Android system UI and apps that support it natively.

Expanded Dark Mode: Extends dark styling to apps that lack built-in dark themes. It works more intelligently than the previous “override force‑dark” option, avoiding blanket color inversion in favor of a more refined approach.

Because this feature is experimental and only available in Canary builds, users may encounter visual glitches in some apps—such as inconsistent colors or layout issues. Google openly cautions users that not all apps will “play nice,” and in such cases recommends switching back to Standard mode .

The rollout timeline for Beta or Stable channels is not confirmed, though speculation places it in Android 16 QPR2 (expected December 2025).

How to Enable Expanded Dark Mode (In Android Canary builds)

If you’re using an Android device enrolled in the Canary channel, here’s how to turn it on:

Step 1. Open Settings.

Step 2. Navigate to Display & touch → Dark theme.

Step 3. You’ll now see two modes:

• Standard
• Expanded

Credit: Android Authority 

Step 4. Select Expanded to enforce dark styling across more apps—even ones without native support.

Step 5. If you notice any display or layout glitches in specific apps, toggle back to Standard mode.

This feature replaces the older hidden “make more apps dark” or “override force‑dark” settings found in Developer Options, offering a cleaner, user-facing placement in the display settings.

How This Update Will Be Useful?

Users who read or browse their phone in low-light environments—such as at night—will find a more consistent, eye-friendly experience even with apps that haven’t been optimized for dark mode.

While Developer Options offered “override force-dark,” Expanded Dark Mode appears to use more intelligent logic to convert UI elements without distorting images or causing widespread visual distortion.

This feature is part of an unstable release. You should expect bugs. Android will let you revert to Standard mode if that improves app stability or appearance .

When it arrives in Beta or Stable under Android 16 QPR2 or later, it could become a key feature for dark‑mode enthusiasts.

How the Android Earthquake Alerts System Works?

The Android Earthquake Alerts System (AEAS) is a groundbreaking, planet-scale early warning network developed by Google to detect and alert users of earthquakes in real-time using the very phones in their pockets. Officially launched in August 2020, the system was introduced first in California, before expanding rapidly to other regions, including the United States, Greece, New Zealand, and eventually to over 98 countries worldwide.

This innovative system transforms millions of Android smartphones into miniature seismic detectors by harnessing their built-in accelerometers. These sensors are capable of picking up early signs of seismic activity, such as the faint P-waves that arrive before the more damaging S-waves during an earthquake. When multiple phones in a geographic area detect shaking simultaneously, they transmit anonymized data to Google’s servers. Google's algorithms then confirm if an earthquake is occurring and, if so, generate and distribute alerts often seconds before shaking reaches the user.

In regions like the U.S. West Coast, AEAS also integrates with ShakeAlert®, a professionally managed network of over 1,600 ground-based seismometers operated by the U.S. Geological Survey (USGS). By combining traditional seismic data with crowdsourced smartphone input, the system enhances accuracy, expands coverage, and reduces dependence on costly infrastructure, especially in earthquake-prone regions with limited resources.

Why Early Earthquake Warning Is Important

Early earthquake warnings can make the difference between life and death. Even a few seconds’ notice before the ground starts shaking gives people time to take protective actions, like "drop, cover, and hold on" or evacuate from dangerous structures. It can also trigger automatic safety measures, such as slowing down trains, shutting off gas lines, and pausing surgeries or heavy machinery.

In high-risk areas, early alerts help reduce injuries, protect critical infrastructure, and improve emergency response. For example, schools can quickly move students to safe zones, and hospitals can brace for patient surges. Studies show that timely warnings can cut injuries by up to 50% during major earthquakes.

Data Sources: Seismic Networks and Crowdsourced Accelerometers

The Android Earthquake Alerts System relies on two main sources of data to detect earthquakes quickly and accurately:

Seismic Networks

In regions like California, Oregon, and Washington, AEAS integrates with professional ground-based seismic systems such as ShakeAlert®, operated by the U.S. Geological Survey (USGS) and partner universities. These networks consist of thousands of sensitive seismometers strategically placed to detect and measure ground motion. When an earthquake occurs, these sensors rapidly calculate its location, magnitude, and expected shaking, triggering alerts through the Android system within seconds.

Crowdsourced Accelerometers from Android Devices

Outside areas with formal networks, AEAS taps into the power of millions of Android phones worldwide. Each phone contains a tiny accelerometer, normally used for screen rotation or step counting, that can also sense ground movement. When several phones in the same region detect a sudden shake simultaneously, they send anonymized, coarse location data to Google’s servers. If the pattern matches that of an earthquake, the system confirms the event and sends alerts to nearby users.

Google has created a global earthquake detection system that is fast, scalable, and cost-effective via combining official seismic equipment and everyday smartphones, which works in well-equipped and underserved regions.

The ShakeAlert® Partnership

In the United States, the Android Earthquake Alerts System works hand-in-hand with ShakeAlert®, the country’s official earthquake early warning system. Operated by the U.S. Geological Survey (USGS) in partnership with several West Coast universities and state agencies, ShakeAlert® is built on a robust network of over 1,675 high-precision ground-based sensors.

These sensors are distributed across California, Oregon, and Washington regions with high seismic risk. When an earthquake begins, ShakeAlert® sensors detect the fast-moving P-waves and instantly estimate the earthquake’s location, magnitude, and intensity. If the system predicts significant shaking, it triggers alerts that are relayed to Android devices through Google’s network.

This partnership ensures that users in the western U.S. receive official, science-based warnings within seconds. It also enhances the speed and accuracy of alerts in areas with dense seismic infrastructure.

Crowdsourced Detection via Android Phones

Globally, Android devices detect ground vibrations using built-in accelerometers. When several phones in an area detect P-waves, they send anonymized data (vibration + coarse location) to Google's servers. The system aggregates these signals to confirm an event and estimate its epicenter and magnitude.

This decentralized network forms the world’s largest earthquake detection grid, especially valuable in regions without dedicated seismic infrastructure.

Earthquakes generate two key wave types:

• P‑waves: Fast-arriving, less intense—detected first.
• S‑waves: Slower but more destructive.

AEAS detects P‑waves and issues alerts before S‑waves arrive, enabling early action.

Alert Generation.

AEAS classifies alerts in two tiers:

• Be Aware: Signals light shaking; non-intrusive notifications guide readiness.
• Take Action: Signals moderate to strong shaking; these alerts override the phone screen with a loud alarm and safety instructions.

Alerts only trigger for quakes with magnitudes ≥ 4.5.

Alerts leverage the near-instant transmission of data compared to slower seismic wave propagation. Alerts travel at internet speed, giving users crucial advance seconds before shaking begins.

AEAS uses anonymized, coarse location data sent only when significant vibrations are detected. No identifiable personal info is shared. Users can disable alerts via settings.

Quick FAQ.

Q: How much warning time do I get?

Answer: Typically, a few seconds to over a minute, depending on distance from the epicenter.

Q: Does it collect my address or identifiable info?

Answer: No. Only anonymized accelerometer data and coarse locations are used.

Q: Can I disable alerts?

Answer: Yes – simply toggle off “Earthquake Alerts” in your Android settings.

Q: Why don’t I get alerts in some areas?

Answer: You might be too close to the epicenter (blind zone), or there may be insufficient sensor coverage.

Q: How is it different from apps like MyShake?

Answer: AEAS is built into Android globally, doesn’t require installation, and combines crowdsourced phone data with seismic networks.

Q: Are false alarms an issue?

Answer: Rare but possible; Google continuously fine-tunes algorithms to minimize them.

Everything New in Android 16 QPR1 Beta 3.

Android 16 QPR1 Beta 3 (build BP31.250610.004) has landed, and it's shaping up to be the final polishing step before the stable release expected in September. If you're enrolled in the QPR1 beta on compatible Pixel devices, you’re getting a refined experience with essential bug fixes, minor UI upgrades, and two standout features designed for accessibility and productivity. Let’s explore what's new.

Android's Quarterly Platform Releases (QPR) deliver regular, bug-focused improvements to the OS without introducing major new APIs ideal for stability and polish. Beta 3 marks the last preview of QPR1, heavily focused on enhancing reliability before the stable rollout.

Key Features & UI Enhancements.

Keyboard Magnifier in Accessibility

One of the most meaningful additions in Android 16 QPR1 Beta 3 is the Keyboard Magnifier, specifically designed for users with low vision. Found under Settings → Accessibility → Magnification, this new toggle allows users to magnify just the keyboard when it's active, without zooming the entire screen.

This seemingly small change has huge implications for accessibility. Previously, magnifying a screen meant zooming in on all UI elements, which could be disorienting and slow. With the Keyboard Magnifier, the rest of the screen remains static while just the keyboard is enlarged, letting users comfortably type messages, search queries, or login credentials with less visual strain.

Desktop Mode Shortcut Enhancements.

For users experimenting with Android’s Desktop Mode, especially on larger screens like tablets or via external monitors, QPR1 Beta 3 introduces an intuitive feature: the ability to pin and unpin apps directly from the taskbar.

Previously, users had limited control over the taskbar’s appearance in desktop mode. Now, by long-pressing any app icon, a new context menu appears with options to "Pin to Taskbar" or "Unpin." This gives users a Windows-like customization ability, enabling a more streamlined, personalized workspace when using Android as a desktop OS alternative.

Whether you're multitasking between Gmail, Google Docs, and YouTube, or turning your Pixel Tablet into a workstation, this update helps build toward a smoother, more PC-like experience on Android. It also signals that Google is investing more in productive and flexible UX across screen sizes.

5-Bar Cellular Signal UI.

Another quiet—but-effective change in Beta 3 is the update to Android’s cellular signal bar UI, which now consistently displays five signal bars instead of the previous four. This brings Android’s design closer to iOS and offers users a more nuanced view of their signal strength.

Why does this matter? For many users, especially those in rural or congested urban areas, knowing the difference between “barely connected” and “strong signal” can affect how and when they make calls, use data, or switch to Wi-Fi. More signal granularity equals better real-time decisions for users on the go.

Credit: 9to5Google

Refined Settings & System UI Details

Android 16 QPR1 Beta 3 also brings a batch of minor UI refinements to the Settings app, Quick Settings panel, and launcher widgets—subtle but impactful.

For example:

• Spacing between settings options has been slightly adjusted for better tap targets and visual clarity.
• Toggle switches now have a more responsive animation, creating a smoother feel during navigation.
• The At-a-Glance widget on the home screen has been restored to include colorful weather icons, improving both the aesthetic and usability at a glance.

Nine Major Bug Fixes.

This Beta addresses nine headline issues flagged by users:

1. RTOS task list kernel bug causing restarts

2. Launcher display glitches

3. Notification rendering problems

4. Media player malfunction in shade

5. Class loader restart bug

6. Kernel-caused restarts

7. Camera startup black screen fix

8. Status bar padding adjustments

9. Notification folding issues.

With at least nine key problems resolved, the update significantly boosts device reliability.

What's Still Missing?

Several experimental improvements remain absent from Beta 3, including:

• Qi2 charger screen savers

• Enhanced HDR brightness toggle

• Dedicated "Parental controls" menu

• New 90:10 split-screen ratio

• Tablet bubble bar and lock‑screen blur UI.

Google appears to reserve these for future Canary or stable builds.

This release supports Pixel 6 and newer, including Pixel 6a, 7/7 Pro, 7a, Fold, 8 series, 9 series, and Pixel Tablet. If you're enrolled in QPR1 beta and want stability over bleeding-edge features, this is an optimal moment to either remain enrolled or opt out ahead of the September stable release.

Google expects to launch Android 16 QPR1 Stable on September 3, 2025. To ensure you receive it, unenroll post-Beta 3—you’ll otherwise be moved to QPR2.

Perplexity CEO Dares Google to Choose Between Ads and AI Innovation

Key Takeaway:

• Perplexity CEO Aravind Srinivas urges Google to choose between protecting ad revenue or embracing AI-driven browsing innovation.
• As Perplexity’s Comet browser pushes AI-first features, a new browser war looms, challenging Google’s traditional business model.

In a candid Reddit AMA, Perplexity AI CEO Aravind Srinivas criticized Google's reluctance to fully embrace AI agents in web browsing. He believes Google faces a critical choice: either commit to supporting autonomous AI features that reduce ad clicks or maintain its ad-driven model and suffer short-term losses to stay competitive.

Srinivas argues that Google’s deeply entrenched advertising structure and bureaucratic layers are impeding innovation, especially as Comet, a new browser from Perplexity, pushes AI agents that summarize content, automate workflows, and offer improved privacy. He described Google as a “giant bureaucratic organisation” constrained by its need to protect ad revenue.

Comet, currently in beta, integrates AI tools directly within a Chromium-based browser, allowing real-time browsing, summarization, and task automation via its “sidecar” assistant. Srinivas warned that large tech firms will likely imitate Comet’s features, but cautioned that Google must choose between innovation and preservation of its existing monetization model.

Industry experts are watching closely as a new "AI browser war" unfolds. While Google may eventually incorporate ideas from Comet, such as Project Mariner, Srinivas remains confident that Perplexity's nimble approach and user-first subscription model give it a competitive edge.

Google to Merge ChromeOS Into Android.

Google has officially confirmed it is merging Chrome OS into Android, ending years of speculation and signaling a major shift in its operating system strategy. During a recent interview, Sameer Samat, President of Google’s Android Ecosystem, revealed that Android will become the unified foundation across devices from smartphones to laptops and foldables.

Why Is Google Merging ChromeOS with Android?

Instead of maintaining two separate systems, Google is converging Chrome OS’s capabilities—such as desktop UI, Linux app support, multi‑window handling, and external display compatibility—into Android. Chrome OS has already been built on a shared Linux kernel with Android. This progression reinforces that integration, moving it beyond mere coexistence toward a singular platform.

By anchoring both laptops and tablets on Android, Google aims to:

• Unify its engineering efforts, avoiding redundant work on separate systems.
• Offer users a seamless ecosystem across all device categories.
• Push advanced AI like Gemini consistently across the board.

Advantages for Users and Developers

For users, this means:

• A more cohesive experience—same platform, same app behavior—across phones, tablets, and laptops.
• Access to a richer app ecosystem, combining mobile, web, Linux, and Chrome‑based tools.

Developers gain:

• A unified Android codebase to build and optimize apps for multiple form factors.

• Reduced fragmentation and clearer guidelines for multi‑device compatibility.

Unknown Challenges.

As promising as the merger sounds, it raises key questions:

1. Security & Updates: Chrome OS offers robust automatic updates and long-term support (up to 10 years for newer devices). It's unclear how this will translate into Android’s typically less predictable update cycle.

2. User Experience: Users worry that applications suited for Chrome OS desktops may not feel native in an Android environment, especially given concerns about Android launchers and interface adaptations.

3. Legacy Hardware: Older Chromebooks may not meet new Android‑based system requirements and could be phased out.

Timeline

Google has not provided a firm release date, but industry insiders expect:

• Developer previews late 2025, testing Android’s desktop-first features on laptops and tablets.

• A broader rollout by 2026, possibly featuring new “Pixel Laptop” hardware as a showcase device.

Meanwhile, Android is evolving with Android 16, which emphasizes large‑screen enhancements, windowed mode support, external display compatibility, and AI integration through Gemini.

Google’s decision to merge Chrome OS and Android marks a key turning point. By consolidating these systems, the company aims to simplify development, enhance cross-device consistency, and accelerate AI advances. Nevertheless, users and developers must watch closely how transition effects update reliability, desktop usability, and support for older hardware.