GrapheneOS Overhauls Emergency Calling on Google Pixel Phones After Incorrect Emergency Numbers Were Discovered
From
mummycullen@mummycullen@gmail-dot-com.no-spam.invalid (MummyChunk) to
comp.mobile.android on Mon Nov 9 14:35:48 2026
From Newsgroup: comp.mobile.android
GrapheneOS Overhauls Emergency Calling on Google Pixel Phones After Incorrect Emergency Numbers Were Discovered
GrapheneOS has introduced a significant change to how Google Pixel smartphones identify emergency telephone numbers, replacing part of Android's aging emergency-number infrastructure with information extracted from Google's Safety Hub system. The modification addresses problems that could cause certain devices to display an inappropriate emergency contact number, an issue with potentially serious implications when users need to reach police, ambulance or fire services quickly.
The change arrived with GrapheneOS build 2026110700, announced on November 8, and affects supported Pixel devices ranging from the Pixel 6 generation through the Pixel 10 family. Although the update was initially distributed through the project's experimental Alpha channel, it has subsequently progressed through the release process. GrapheneOS has also issued a follow-up build, 2026110800, to address a separate kernel problem affecting several Pixel 10 models.
The emergency-number overhaul is particularly important because GrapheneOS is designed to provide stronger privacy and security protections than conventional Android distributions while retaining essential smartphone functionality. Its developers generally avoid depending on proprietary Google software, but emergency communications present a situation in which maintaining accurate information can be more important than continuing to rely on an older open-source implementation.
The project describes the previous Android Open Source Project mechanism as outdated and broken, explaining that the replacement obtains more appropriate emergency-number data from Google's Safety Hub. However, the release notes do not claim that ordinary emergency calls were universally failing, nor do they establish that every supported Pixel was affected by incorrect numbers.
The distinction matters because the problem primarily concerns how emergency numbers are identified and selected within the operating system. A phone displaying an incorrect default number is not necessarily incapable of placing a correctly dialed emergency call, although selecting the wrong number during an actual emergency could cause a dangerous delay.
Beyond this change, the update introduces improvements to location privacy, refreshes the Vanadium browser, updates time-zone information and includes several kernel corrections. The subsequent Pixel 10 stability problems also illustrate the difficulties of maintaining a security-focused operating system across hardware that depends on continuously changing Android drivers and firmware.
Why GrapheneOS Needed to Replace Android's Emergency-Number System
Android contains infrastructure for identifying emergency telephone numbers based on information supplied by mobile networks, SIM cards, modem software and a database of country-specific emergency services.
This information is more complicated than it may initially appear.
Different countries use different emergency numbers, and some operate separate numbers for police, ambulance services and fire departments. The United States and Canada commonly use 911, while 112 is the principal common emergency number throughout the European Union and is also supported in many other countries.
Other national arrangements are more complex. Switzerland uses 112 as a general emergency number alongside specialized numbers such as 117 for police, 118 for fire services and 144 for medical emergencies.
South Korea uses 112 for police and 119 for fire and ambulance services.
A modern smartphone must therefore do more than recognize a short collection of familiar numbers. It must identify the appropriate options for the country and mobile network, understand how calls should be routed and decide which number to present when the user activates an emergency assistance feature.
Android's open-source infrastructure provides mechanisms for handling these tasks, but manufacturers can also introduce their own emergency applications and supplementary databases.
Google's Pixel software uses the proprietary Personal Safety application, associated with the Safety Hub package, to provide emergency assistance features. The application contains additional information and selection rules that are not necessarily available through the standard Android Open Source Project implementation.
GrapheneOS previously relied on the AOSP approach rather than incorporating Google's complete proprietary emergency application into its operating system.
That distinction became problematic when users discovered cases in which the default emergency number selected by GrapheneOS did not match the appropriate national emergency contact.
The issue was not necessarily caused by an entirely incorrect list of telephone numbers. In some cases, the underlying database contained valid entries, but the software responsible for choosing among them gave inappropriate priority to particular numbers.
This difference between maintaining a database and selecting the correct entry is central to understanding the problem.
The Swiss Emergency SOS Problem Exposed a Dangerous Selection Error
A particularly revealing example emerged in September 2026, when GrapheneOS users reported that the default Emergency SOS number displayed in Switzerland was incorrect.
Instead of selecting 112, the operating system could present 0800 117 117, the number associated with the Swiss Transport Police.
The Transport Police perform a legitimate law enforcement function, but their contact number is not an appropriate general-purpose emergency number for someone requiring immediate ambulance, fire or conventional police assistance.
The problem was documented in GrapheneOS's public issue tracker on September 10, where contributors began examining the emergency-number information supplied by the Android telephony system.
Investigations showed that the underlying list contained several Swiss emergency numbers, including 112 and the separate national services. However, the selection mechanism could assign equal priority to entries that should not be treated as equivalent.
When the entries received the same priority, the software could fall back to comparing the numbers as strings. Under those circumstances, the Transport Police number could appear before 112, despite being unsuitable as the default general emergency contact.
This illustrates how a relatively small software-design decision can produce a serious practical consequence.
The problem was not necessarily that the phone had no knowledge of 112. Rather, the system could choose the wrong number from information that included several valid contacts serving different purposes.
Similar inconsistencies were identified elsewhere.
In Canada, GrapheneOS could select 112 as the default emergency number instead of 911. Some Canadian mobile networks recognize 112 and redirect it to emergency services, but that does not make it the preferred number to display to Canadian users.
Contributors also examined emergency-number selection in Spain, India and South Korea, identifying complications involving number categories, routing information and the order in which entries were prioritized.
The investigation revealed that simply correcting one country's number would not address the broader issue.
Mobile networks may provide different emergency-number information, SIM cards may contain their own lists, and international roaming introduces further complexity. A solution based on manually rearranging a few entries could work for certain countries while introducing problems elsewhere.
GrapheneOS therefore needed a more comprehensive method of obtaining and interpreting the information.
The project's developers ultimately decided to replace the outdated AOSP selection mechanism with data derived from Google's Safety Hub.
Importantly, the public reports establish problems with emergency-number selection, not a general inability to place emergency calls. Users should not interpret the issue as proof that every emergency call made through earlier GrapheneOS versions would have failed.
How the New Safety Hub Integration Works
The central change in build 2026110700 involves new infrastructure added to two GrapheneOS development tools, adevtool and arsclib.
These tools participate in preparing and assembling the operating system, including processing components obtained from Google's Pixel software environment.
The updated implementation extracts appropriate emergency-number information from Safety Hub during the firmware build process.
This is an important technical distinction.
GrapheneOS is not simply making Google's proprietary Personal Safety application mandatory for all users, nor does the change establish that Google Play services must run continuously to recognize emergency numbers.
Instead, the project is using data from a more complete source while retaining its own operating system implementation.
Google's Safety Hub contains additional rules for determining which emergency contact should be presented in particular countries. Its selection system can account for national preferences that the older AOSP implementation does not handle appropriately.
For example, the September investigation found that Google's system uses country-specific preferences to select 911 in Canada and 112 in Switzerland.
Samsung employs a separate manufacturer-specific emergency-number selection system, demonstrating that Android device manufacturers have already developed alternatives to the generic open-source approach.
GrapheneOS's new implementation attempts to obtain more suitable information without requiring the wholesale adoption of Google's proprietary emergency software.
This fits the project's broader philosophy of retaining compatibility with Pixel hardware while reducing unnecessary reliance on privileged proprietary services.
However, extracting more accurate information at build time does not eliminate every possible difficulty involving emergency communications.
The ability to complete an emergency call also depends on the cellular modem, available mobile networks, radio firmware, network registration and the relevant telecommunications infrastructure.
A device may correctly identify an emergency number but still encounter an unrelated connection problem.
Similarly, a successful emergency call does not prove that every number displayed by the operating system is appropriate for every country.
The GrapheneOS change addresses a particular part of this larger system: the information and logic used to determine which emergency numbers should be presented.
The developers have not published comprehensive independent testing demonstrating correct behavior across every supported country, carrier and roaming configuration.
Nevertheless, the replacement represents a meaningful architectural improvement over continuing to rely on a mechanism already known to select inappropriate numbers in some circumstances.
Approximate Location Privacy Also Receives an Important Update
The same GrapheneOS release introduces a separate improvement involving how applications request approximate location information.
Modern smartphones can provide either relatively precise location coordinates or less accurate estimates, depending on application permissions and operating system settings.
Precise location may be necessary for navigation, delivery services or applications requiring accurate positioning. Other software, including weather services and websites providing regional information, often needs only an approximate location.
Android supports this distinction through location permissions and system mechanisms that reduce the precision of coordinates.
One such mechanism is LocationFudger, which processes location data to produce less precise coordinates.
GrapheneOS previously maintained a separate implementation of this behavior inside GmsCompat, its compatibility layer for sandboxed Google Play services.
The new release introduces system APIs that allow supported components to request coarsened location information directly.
GrapheneOS has updated both its Vanadium browser and sandboxed Google Play compatibility layer to use these interfaces.
This removes the need for GmsCompat to maintain its own version of the location-adjustment mechanism, reducing duplicated code and improving consistency between the relevant components.
The change is particularly interesting because GrapheneOS treats Google Play services differently from conventional Android installations.
On standard Google-certified Android devices, Google Play services typically operate with privileges and integration capabilities beyond those of ordinary applications.
GrapheneOS allows users to install Google Play services as sandboxed applications without granting them the same privileged system position.
Its compatibility layer provides the interfaces needed by applications that depend on Google services while preserving GrapheneOS's permission model and additional security restrictions.
The new approximate-location APIs continue that approach by making suitable system functionality available without requiring a separate privileged Google service.
However, users should not confuse this improvement with the emergency-number changes.
The new location APIs are intended for supported applications such as Vanadium and the Google Play compatibility layer. The release notes do not establish that they modify emergency location transmission, improve the accuracy of information sent to dispatchers or change the behavior of every location-aware application.
The two improvements appear in the same update, but they address different technical problems.
Vanadium, Kernel and Security Improvements Accompany the Release
GrapheneOS build 2026110700 contains several additional improvements that are less visible than the emergency-number overhaul but remain relevant to stability and security.
Vanadium, the project's hardened Chromium-based browser, has been updated to version 157.0.8103.38.0.
Vanadium incorporates modifications intended to strengthen browser security and privacy beyond the standard Chromium configuration, including changes to exploit mitigations and browser behavior.
Keeping the browser current is particularly important because web browsers routinely process complex and potentially untrusted content. Vulnerabilities in rendering engines, scripting environments or related components can provide opportunities for attackers if suitable protections are absent.
The release also updates time-zone information to version 2026f, helping maintain correct local time calculations in regions where authorities have changed time-zone rules.
Although time-zone database updates rarely attract attention, they can affect scheduled events, alarms, calendar synchronization and applications that rely on accurate local time calculations.
The update further adjusts how native zygote processes are launched under GrapheneOS's secure spawning system.
Android uses zygote processes to create application processes efficiently. GrapheneOS extends this architecture with additional security controls, and the new release restores the handling of supplementary process groups and the Linux NoNewPrivs setting in certain circumstances.
These changes are currently relevant primarily to Vanadium, Chrome and some other Chromium-based browsers, where they help preserve compatibility with the operating system's hardened process-launching mechanisms while reducing renderer memory overhead.
Several Linux kernel improvements are also included.
For devices using the 6.1 kernel branch, GrapheneOS has addressed a rare condition involving slab memory allocation that could otherwise trigger a kernel panic.
The 6.18 kernel branch receives updates and fixes for issues involving filesystem handling, compressed audio timestamps, audio offloading, memory initialization and PCI Express synchronization.
The Pixel 10 family receives additional attention because its kernel and hardware support have undergone substantial development.
Some corrections specifically concern audio compatibility, while others address the interaction between newer Android kernel code and Pixel hardware drivers.
These changes are technically separate from the emergency-number improvements, but their inclusion in the same release became important when early users began reporting unexpected system crashes.
Pixel 10 Kernel Crashes Prompted a Second Update
Shortly after build 2026110700 became available through the Alpha channel, several GrapheneOS users reported serious stability problems on Pixel 10 devices.
Reports appeared in the project's official discussion forum from owners of the Pixel 10, Pixel 10 Pro and Pixel 10 Pro XL.
One Pixel 10 Pro XL owner described a kernel crash during the installation process, followed by additional crashes while the device was idle. Another user reported several unexpected restarts within approximately an hour.
Other users described similar behavior, with some submitting diagnostic information to the GrapheneOS issue tracker.
A kernel crash differs from an ordinary application failure because it involves the operating system's core software. Depending on the circumstances, it can cause the entire device to freeze, restart unexpectedly or interrupt whatever task the user is performing.
Repeated crashes are particularly concerning on a smartphone because they can affect availability for communication, navigation and other essential functions.
However, the reports should not be interpreted as evidence that the emergency-number changes themselves caused the crashes.
GrapheneOS's subsequent release notes identify an upstream Pixel kernel issue involving suspend accounting, a mechanism associated with tracking device activity and transitions between operating states.
According to the developers, the problem also affects Google's stock Pixel operating system and became significantly more frequent after a General Kernel Image update included in build 2026110700.
The project responded by publishing build 2026110800 on November 8.
This follow-up release applies a correction backported from Android 17 QPR2 Beta and specifically targets the Pixel 10, Pixel 10 Pro, Pixel 10 Pro XL and Pixel 10 Pro Fold.
The update does not replace the broader improvements introduced in 2026110700. Instead, it builds upon that release while addressing the newly identified kernel problem.
This is an important development that was not fully reflected in the original November 8 reporting, which focused on the initial Alpha release and the first user complaints.
GrapheneOS's official release information now lists 2026110800 for the main Pixel 10 models, while other supported Pixel devices are listed with 2026110700.
The project has also advanced these builds through its release channels, although the exact version available on an individual device should always be checked through the operating system's update interface.
The rapid response demonstrates the value of staged software distribution.
By initially providing new builds to users who deliberately select experimental updates, developers can identify regressions before the software reaches the entire installed base.
The resulting crash reports were disruptive for the affected testers, but they also provided information needed to identify and address a problem before broader deployment.
Independent long-term testing is still necessary to determine whether the follow-up correction eliminates every related stability problem. GrapheneOS's description establishes the specific defect being addressed, not a guarantee that no other kernel crashes can occur.
Which Pixel Devices Are Supported and What Owners Should Do
The emergency-number changes are included in builds covering supported Pixel smartphones from the sixth through the tenth generations.
The release includes the Pixel 6, Pixel 6 Pro and Pixel 6a; the Pixel 7, Pixel 7 Pro and Pixel 7a; the Pixel 8, Pixel 8 Pro and Pixel 8a; and the Pixel 9 family, including the Pixel 9a and Pixel 9 Pro Fold.
The Pixel 10, Pixel 10 Pro, Pixel 10 Pro XL, Pixel 10 Pro Fold and Pixel 10a are also covered, alongside the original Pixel Fold and Pixel Tablet.
Although the Pixel Tablet is included in the project-wide release, its cellular capabilities differ from those of a smartphone. Inclusion in the software distribution should not be interpreted as giving a Wi-Fi-only tablet conventional mobile emergency-calling functionality.
The Pixel 10 family also requires particular attention because of the follow-up kernel correction.
Owners should check the version installed on their device before assuming that all the latest fixes are present.
GrapheneOS provides an automatic update system, and users can inspect their current version through Settings and About phone. Available updates and the selected release channel can be reviewed under Settings, System and System Update.
The project offers three principal release channels: Alpha, Beta and Stable.
Alpha receives new builds first and is intended for early testing. Beta provides additional testing before deployment to the general user population, while Stable is the default channel for ordinary installations.
For a primary phone, particularly one used for work, travel or emergencies, remaining on Stable is generally the most sensible approach.
There is little reason for an ordinary user to switch to Alpha merely to obtain a new feature a few days earlier, especially when recent testing has demonstrated how an otherwise useful release can expose hardware-specific stability problems.
Users concerned about emergency-number behavior should also understand that the displayed default number may not be the only way to reach emergency services.
The appropriate number depends on the country and local telecommunications system, and users should be familiar with the officially designated emergency contact numbers for the places where they live or travel.
Checking the emergency configuration and keeping the device updated are sensible precautions, but users should not place unnecessary test calls to emergency services without first arranging an authorized test with the relevant local authority.
Anyone experiencing unexplained restarts or incorrect emergency-number selection should document the device model, installed GrapheneOS version and circumstances of the problem, then consult the project's official support resources.
If a phone is experiencing persistent instability, having an alternative means of contacting emergency services may be prudent until the issue has been resolved.
The Update Highlights a Broader Challenge for Privacy-Focused Android Systems
The emergency-number overhaul illustrates an important difficulty faced by developers of alternative Android operating systems.
Android is often described as open source, but the software installed on a typical commercial smartphone contains a combination of open-source Android components, proprietary manufacturer applications, hardware drivers and services that are not included in the Android Open Source Project.
This distinction is especially relevant to Google Pixel devices.
Although GrapheneOS uses Pixel hardware because of its security architecture and support for features such as verified boot and hardware-backed protections, the project does not simply reproduce Google's complete software environment.
Instead, its developers build upon AOSP and introduce additional privacy and security mechanisms while retaining the device-specific components needed for hardware compatibility.
That approach provides greater control over software behavior and reduces dependence on privileged proprietary applications.
However, it also means that certain functions implemented through Google's own software may need to be recreated or supported through alternative mechanisms.
Emergency-number selection is one such function.
The older AOSP implementation was not necessarily capable of reproducing all the behavior of Google's proprietary Safety Hub system, particularly when choosing the preferred emergency contact from several available numbers.
The resulting problems demonstrate that having access to the underlying Android source code does not automatically guarantee identical functionality to a manufacturer's complete operating system.
The new approach provides a practical compromise.
By extracting suitable data during the build process, GrapheneOS can benefit from information maintained within Google's Pixel software environment without abandoning its broader effort to minimize privileged proprietary services.
It is an example of compatibility and security engineering being driven by a practical requirement rather than a rigid distinction between open-source and proprietary components.
The same principle appears in GrapheneOS's sandboxed Google Play implementation, which allows users to run applications requiring Google services without granting those services the elevated privileges they ordinarily receive on conventional Android installations.
The aim is not to eliminate every interaction with Google technology, but to control how that technology is incorporated and what privileges it receives.
Emergency communications also expose the limits of software independence.
Even an operating system built around strong privacy protections must depend on cellular network standards, modem firmware, national emergency-number arrangements and hardware components supplied by manufacturers.
Keeping these systems reliable requires ongoing testing and coordination with changes elsewhere in the Android ecosystem.
The Pixel 10 kernel problems demonstrate a related challenge. Changes originating in upstream Android code can affect devices running alternative operating systems, even when those systems maintain extensive modifications of their own.
For a project such as GrapheneOS, maintaining reliability therefore involves more than fixing defects within its own application code. Developers must continually track changes in Android, Linux, Pixel firmware and hardware drivers.
An Important Safety Improvement With Wider Implications for Android
GrapheneOS's decision to replace the AOSP emergency-number mechanism is a meaningful correction to a problem that could otherwise remain unnoticed until someone attempted to use an emergency assistance feature.
The Swiss example demonstrates why the change matters. A smartphone that recognizes multiple legitimate telephone numbers must still understand which one should be presented as the default contact for urgent assistance.
Selecting a specialized service instead of the appropriate general emergency number can create confusion precisely when users have little time to investigate the problem themselves.
The new Safety Hub-derived approach addresses that weakness by using more suitable country-specific information, although its effectiveness across every international carrier configuration has yet to be comprehensively demonstrated.
The release also brings worthwhile technical improvements to location privacy, browser maintenance and operating system security. At the same time, the Pixel 10 kernel crashes provide a reminder that changes to low-level software require careful testing even when they are intended to improve reliability.
The publication of build 2026110800 shortly after the initial release shows that GrapheneOS responded to the reported instability rather than allowing the affected build to remain the final version.
For existing users, the practical priorities are straightforward: remain on the Stable channel unless there is a particular reason to participate in testing, install the appropriate corrected build when offered and verify that the device's emergency assistance settings reflect the country in which it is being used.
The broader significance extends beyond GrapheneOS.
Android's emergency-calling infrastructure involves layers of software that most users never encounter, yet those layers must function reliably across hundreds of mobile networks and many different national emergency systems.
The discovery that older open-source selection logic could choose an inappropriate emergency contact raises questions about how similar functions are maintained in other Android-derived systems.
It does not establish that those systems suffer from the same defect, but it demonstrates why emergency-number databases and their associated selection rules deserve continued scrutiny.
GrapheneOS has addressed the issue by drawing on Google's more specialized implementation while preserving its own approach to operating system security. That decision reflects a practical reality of modern smartphone development: privacy, independence and reliability are all important, but none can be considered in isolation when essential safety functions are involved.
The lasting value of this update will be measured not by the number of new features it introduces, but by whether users can depend on their phones to identify the correct emergency service when it matters most.
--
Via JLA Forums web gateway for comp.mobile.android
--- Synchronet 3.22a-Linux NewsLink 1.2