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.
Nuno Silva wrote:
(Given this is a massive text, and I even only read half of it, (the
first half, that was clearly about emergency numbers, quoted), I'll
write here at the top, apologies for that:)
Is this about some feature that shows a menu to select between different alternative emergency numbers?
If it's just about choosing *the* number to dial, isn't that covered by mobile telephony standards since at least GSM, by dialing 112!?
On 2026-11-09, MummyChunk wrote:
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.
[...]
--
Nuno Silva
[...]Nuno Silva wrote:
(Given this is a massive text, and I even only read half of it, (the
first half, that was clearly about emergency numbers, quoted), I'll
write here at the top, apologies for that:)
Is this about some feature that shows a menu to select between different
alternative emergency numbers?
If it's just about choosing *the* number to dial, isn't that covered by
mobile telephony standards since at least GSM, by dialing 112!?
You?re right that 112 has long been supported by GSM networks.
The issue wasn?t with manually dialing 112. It was with the number
GrapheneOS automatically selected when using Emergency SOS. In
Switzerland, for example, it selected the Swiss Transport Police
number instead of 112.
So it was a problem with the automatic emergency-number selection, not emergency calling itself.
Nuno Silva wrote:
On 2026-11-20, MummyChunk wrote:
Nuno Silva wrote:
(Given this is a massive text, and I even only read half of it, (the
first half, that was clearly about emergency numbers, quoted), I'll
write here at the top, apologies for that:)
Is this about some feature that shows a menu to select between different >>> alternative emergency numbers?
If it's just about choosing *the* number to dial, isn't that covered by
mobile telephony standards since at least GSM, by dialing 112!?
[...]
You?re right that 112 has long been supported by GSM networks.
The issue wasn?t with manually dialing 112. It was with the number
GrapheneOS automatically selected when using Emergency SOS. In
Switzerland, for example, it selected the Swiss Transport Police
number instead of 112.
So it was a problem with the automatic emergency-number selection, not
emergency calling itself.
But that's precisely the thing, if it's about an emergency button or
feature, and not a user-made explicit selection, then wouldn't it be
simpler and more failproof to just have it internally dial 112 and have
the carrier route the "emergency" teleservice (as opposed to "telephony" teleservice) call appropriately?
--
Nuno Silva
Nuno Silva wrote:
On 2026-11-20, MummyChunk wrote:
[...]
Nuno Silva wrote:
(Given this is a massive text, and I even only read half of it, (the
first half, that was clearly about emergency numbers, quoted), I'll
write here at the top, apologies for that:)
Is this about some feature that shows a menu to select between different >>>> alternative emergency numbers?
If it's just about choosing *the* number to dial, isn't that covered by >>>> mobile telephony standards since at least GSM, by dialing 112!?
You?re right that 112 has long been supported by GSM networks.
The issue wasn?t with manually dialing 112. It was with the number
GrapheneOS automatically selected when using Emergency SOS. In
Switzerland, for example, it selected the Swiss Transport Police
number instead of 112.
So it was a problem with the automatic emergency-number selection, not
emergency calling itself.
But that's precisely the thing, if it's about an emergency button or
feature, and not a user-made explicit selection, then wouldn't it be
simpler and more failproof to just have it internally dial 112 and have
the carrier route the "emergency" teleservice (as opposed to "telephony"
teleservice) call appropriately?
Yes, dialing 112 is supported by cellular standards, and it would make
sense as a fallback.
However, emergency numbers and routing can vary by country. For
example, 911 is preferred in the US and Canada, while South Korea uses
112 for police and 119 for fire and ambulance services. That?s why
Android maintains country-specific emergency-number information rather
than simply hardcoding 112 everywhere.
The GrapheneOS problem was that its automatic selection system chose
an inappropriate number in Switzerland. The update corrected that
selection process. The suggestion is reasonable, but for some reason
the developers chose to preserve the country-specific approach.
Nuno Silva wrote:
On 2026-11-21, MummyChunk wrote:
Nuno Silva wrote:
On 2026-11-20, MummyChunk wrote:
Nuno Silva wrote:
(Given this is a massive text, and I even only read half of it, (the >>>>> first half, that was clearly about emergency numbers, quoted), I'll
write here at the top, apologies for that:)
Is this about some feature that shows a menu to select between different >>>>> alternative emergency numbers?
If it's just about choosing *the* number to dial, isn't that covered by >>>>> mobile telephony standards since at least GSM, by dialing 112!?
[...]
You?re right that 112 has long been supported by GSM networks.
The issue wasn?t with manually dialing 112. It was with the number
GrapheneOS automatically selected when using Emergency SOS. In
Switzerland, for example, it selected the Swiss Transport Police
number instead of 112.
So it was a problem with the automatic emergency-number selection, not >>>> emergency calling itself.
But that's precisely the thing, if it's about an emergency button or
feature, and not a user-made explicit selection, then wouldn't it be
simpler and more failproof to just have it internally dial 112 and have
the carrier route the "emergency" teleservice (as opposed to "telephony" >>> teleservice) call appropriately?
Yes, dialing 112 is supported by cellular standards, and it would make
sense as a fallback.
However, emergency numbers and routing can vary by country. For
example, 911 is preferred in the US and Canada, while South Korea uses
112 for police and 119 for fire and ambulance services. That?s why
Android maintains country-specific emergency-number information rather
than simply hardcoding 112 everywhere.
As 911 is preferred in the US and Canada, wouldn't the Teleservice 12
call initiated by dialling 112 on a handset there just do a call to
*911*?
Or does it really end up actually calling the number 112?
The GrapheneOS problem was that its automatic selection system chose
an inappropriate number in Switzerland. The update corrected that
selection process. The suggestion is reasonable, but for some reason
the developers chose to preserve the country-specific approach.
--
Nuno Silva
As 911 is preferred in the US and Canada, wouldn't the Teleservice 12
call initiated by dialling 112 on a handset there just do a call to
*911*?
Or does it really end up actually calling the number 112?
Nuno Silva <nunojsilva@invalid.invalid> wrote:
As 911 is preferred in the US and Canada, wouldn't the Teleservice 12
call initiated by dialling 112 on a handset there just do a call to
*911*?
Or does it really end up actually calling the number 112?
According to the AOSP database: https://android.googlesource.com/platform/packages/services/Telephony/+/master/ecc/input/eccdata.txt
for US the phone just calls 911 for fire/police/ambulance, it doesn't call 112.
The fallback number is also 911 for any other kind of emergency. It doesn't call 112.
If you are in, say, Uganda, the number for fire/police/ambulance is 999 and the fallback is 112.
This is a generic database of emergency numbers rather than instructions for who to call in what circumstance. The system applies logic based on its interpretation of the database, rather than the database telling the phone what to do.
The problem with GrapheneOS using this database: https://github.com/GrapheneOS/os-issue-tracker/issues/8695 https://github.com/GrapheneOS/platform_frameworks_base/pull/479
was that if numbers are missing a clear priority order in the database then the first number in the alphanumeric sort wins. In Switzerland, if there isn't a carrier-specific rule that takes precedence, 0800117117 comes before 112, so calls were by default going to the Transport Police number. That's labelled as TYPE_UNSPECIFIED so there are no clues what it is for or how to build a priority order for it.
Ok, that does explain the issue they're dealing with.
Overall, if you're not presenting a menu to choose from, then the
question really is whether you even need to call anything other than
112.
For presenting a menu, it seems digital cell telephony standards also
specify the ability for the phone, SIM and carrier to provide/contain
more than one emergency number, so hopefully querying the AOSP database
would go in hand with that?
| Sysop: | Jacob Catayoc |
|---|---|
| Location: | Pasay City, Metro Manila, Philippines |
| Users: | 5 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 498678:21:30 |
| Calls: | 212 |
| Calls today: | 3 |
| Files: | 912 |
| D/L today: |
31 files (22,593K bytes) |
| Messages: | 69,867 |