On June 25, 2026, Android phones in Venezuela warned some users seconds before destructive earthquake shaking arrived, after Google’s phone-based detection system registered the quake and pushed alerts across affected areas. The phones did not predict the earthquake; they detected its first, faster waves and tried to outrun the more damaging ones with a notification. That distinction matters because it is the difference between science fiction and an increasingly real public-safety infrastructure built into consumer devices. Venezuela’s tragedy shows both the promise and the danger of letting a private mobile platform become part of the emergency-warning stack.
The most arresting detail from Venezuela was not that Android phones buzzed. It was that, for some people, the alert appears to have arrived before the shaking became obvious enough to send them running. In an earthquake, seconds are not comfort; they are time to move away from glass, duck under a table, stop an elevator, halt a surgery, or simply understand that the world is about to become violent.
Reports from Venezuela described users receiving Android earthquake warnings moments before the Wednesday quake, with officials and international outlets later reporting a death toll that had climbed past 900. Images from La Guaira state and surrounding areas showed damaged and leaning buildings, and the disaster quickly became a test case for a technology most people barely know exists until it interrupts their screen.
Google’s Android Earthquake Alerts System is not a novelty feature in the way a weather widget is a feature. It is an attempt to turn the installed base of Android phones into a distributed seismic network, especially in countries that do not have dense government-operated early-warning infrastructure. The system uses the accelerometer already inside the phone, the same sensor that helps determine orientation and motion, to detect the initial movement patterns associated with an earthquake.
That makes the Venezuelan alerts politically and technically important. The public story is a hopeful one: ordinary phones became lifesaving devices. The more complicated story is that a global emergency-warning layer is being assembled from private hardware, proprietary algorithms, mobile operating systems, cloud servers, app-services infrastructure, and user trust.
Earthquakes produce different types of seismic waves. The faster primary wave, or P-wave, often arrives before the slower and more destructive S-wave. A sensor near the rupture can detect the first wave, transmit that signal, and give people farther away a few seconds — sometimes more, often less — before stronger shaking reaches them.
Traditional systems do this with networks of seismometers. Google’s twist is to use Android phones as the sensing layer where dedicated instruments are sparse. A single phone jostling in a pocket proves almost nothing, but many phones registering similar motion patterns across a region can form a signal strong enough for a server-side system to estimate that a quake is underway.
That is why density matters. A smartphone early-warning system is not merely a clever use of sensors; it is a population-weighted instrument. It is strongest where many Android phones are powered on, stationary or semi-stationary, connected, opted into the relevant services, and close enough to the source to detect the first waves before the warning has lost practical value.
Venezuela, with high smartphone reliance and uneven public infrastructure, is exactly the kind of environment where such a system can look almost miraculous. But the miracle is still bounded by physics, communications latency, device distribution, and software decisions made far from the fault line.
Google has described a two-stage alerting model. A lower-level “BeAware” alert is intended for weaker shaking and gives users a heads-up. A higher-level “TakeAction” alert is designed for more serious shaking, taking over the screen and sounding loudly even when the phone is silenced.
That distinction matters because emergency warnings have to fight human behavior. A quiet notification is easy to miss. A full-screen, high-volume alert is intrusive by design. The system is therefore not only detecting earthquakes; it is making a judgment about how forcefully it is allowed to interrupt a person’s life.
For WindowsForum readers, the analogy is not hard to spot. This is the emergency-alert version of the same platform logic that governs Windows Update, SmartScreen, Defender reputation checks, passkey prompts, and cloud-mediated identity protections. The endpoint becomes a participant in a larger security or safety system, and the cloud decides when local behavior should change.
The difference is that a bad SmartScreen reputation might block an installer. A bad earthquake alert decision can determine whether someone stays in bed, runs down a stairwell, or ducks under a table. The stakes are immediate and physical.
That is the nightmare scenario for algorithmic emergency infrastructure. A system can appear to function while making the wrong classification at the worst possible moment. It can send some warnings, log some detections, and still fail the people who needed the most urgent version of the alert.
Google has said it updated its algorithms after that failure. That is reassuring in the narrow sense that software can improve. It is also unsettling in the broader sense that the public only learns about the limits of these systems after large-scale tragedy exposes them.
The Venezuela case will likely be read by many as evidence that the system has improved. Perhaps it has. But public praise on social media is not the same as an audited post-incident report. The meaningful questions are harder: how many people received alerts, how much warning time did they get, how many should have received alerts but did not, how many alerts were delayed, and how well did the alert severity match observed shaking?
Those are not academic quibbles. They are the difference between a feel-good story about smartphones and an accountable safety system.
Every warning system lives between two failures. Missed alerts leave people unwarned. False alerts train people to ignore the next warning. The more dramatic the alert, the more damaging a false alarm can be to public trust, but the less dramatic the alert, the less likely people are to act when action is necessary.
This is why earthquake warning is a brutal design problem. You cannot simply tune the system to warn everyone at the slightest hint of danger. Over-warning creates fatigue and may cause panic, injuries, or dangerous evacuations. Under-warning preserves calm until the moment it becomes deadly.
The tradeoff is sharper for a company like Google because Android alerts operate across countries with different building standards, emergency agencies, cellular networks, languages, risk profiles, and public expectations. A threshold that makes sense in one region may be wrong in another. A user accustomed to typhoons or civil-defense alerts may react differently from someone encountering a full-screen earthquake warning for the first time.
Venezuela’s reports of users praising the alerts should not obscure the system’s fragility. Public trust is earned incident by incident, and it can be lost just as quickly.
What Apple has not done, at least publicly, is turn the global iPhone base into a crowdsourced earthquake detection network on the same model as Google’s Android system. That choice may reflect technical, legal, privacy, or institutional caution. It may also reflect Apple’s longstanding preference for tightly controlled experiences over massive, probabilistic public infrastructure experiments.
Google’s approach is more ambitious and more exposed. It leverages Android’s enormous global footprint and the reach of Google Play services. It can bring warning capability to places where dedicated systems are limited. But it also means a private company is making detection and alerting decisions at planetary scale.
Apple’s more conservative posture avoids some of those responsibilities while leaving more of the detection burden to governments and specialist alert originators. That may be less exciting, and in some countries less useful. But it also keeps the line between public emergency authority and platform provider somewhat clearer.
Neither model is obviously sufficient on its own. A government-only system may not reach enough people fast enough. A platform-only system may lack transparency, accountability, and local integration. The future likely belongs to hybrids, but hybrids are messy.
If Android can warn of an earthquake, users will expect it to work. If it fails, they will ask whether Google, carriers, phone makers, regulators, or local authorities were responsible. If it sends a false alarm, the same chain of responsibility becomes even murkier.
This is not unique to earthquakes. Modern emergency communications already rely on carriers, handset vendors, location services, satellite links, app ecosystems, and operating-system-level alert permissions. But earthquake early warning is unusually unforgiving because delays are measured in seconds rather than minutes.
The practical implication is that platform reliability becomes public-safety reliability. Battery optimization policies, background service restrictions, regional service availability, notification permissions, network congestion, localization quality, and device fragmentation all become part of the emergency-warning equation.
That should make administrators and policymakers uncomfortable in a productive way. If a public warning function depends on private mobile infrastructure, then that infrastructure needs more than marketing claims. It needs testing, disclosure, interoperability, and post-event accountability.
The emergency context complicates the debate. Many people will gladly accept limited sensor use if it gives them ten seconds before a wall collapses. Others will reasonably worry that emergency exceptions have a habit of expanding once infrastructure exists.
The right answer is not to reject sensor-based warning systems. It is to demand that safety features be governed by unusually strict transparency. Users should be able to understand whether their phones participate in detection, whether participation is tied to Google services, what regional rules apply, and how to disable or verify settings without digging through ambiguous menus.
There is also an equity issue hiding in the technical design. People with newer phones, charged batteries, stable connectivity, and access to platform services are more likely to benefit from these systems. People with older devices, disabled services, weak signal, or no smartphone at all may be left dependent on neighbors, sirens, radio, or nothing.
A smartphone warning system can reduce inequality in countries without dense seismic networks, but it can also reproduce the inequalities of device access and connectivity. The people most exposed to dangerous buildings and fragile infrastructure are not always the people best served by high-end mobile ecosystems.
That means alert design is not only a software problem. It is an education problem. A warning that says shaking is expected needs to be paired with public knowledge about what action is safest in the local built environment.
In many earthquake-prone countries, official advice emphasizes dropping, covering, and holding on rather than running during active shaking. But advice can vary depending on building type, local hazards, and whether a person is indoors, outdoors, driving, or near the coast. A few seconds of warning are valuable only if the recipient has already internalized the response.
This is where governments and platforms need each other. Google can deliver an alert quickly. Local authorities can shape the message, run drills, and explain how people should react. Without that civic layer, a technically successful alert can still produce chaotic behavior.
For Venezuela, where social media posts reportedly showed people leaving buildings after alerts, the question is not whether those reactions were understandable. They were. The question is whether the country’s public-safety institutions can turn this moment into durable preparedness rather than a viral anecdote.
Windows PCs participate in malware telemetry, identity-risk checks, device-health reporting, enterprise compliance, location services, and update orchestration. Microsoft, like Google and Apple, increasingly treats the device as one node in a wider risk-management network. That model can be powerful, but it forces users and administrators to decide where the trust boundary should sit.
Earthquake alerts are simply the clearest possible demonstration because the consequences are visible. A cloud service evaluates distributed signals and commands local devices to interrupt users. In enterprise IT, this resembles a security incident response. In civil life, it becomes a public warning.
The lesson for IT pros is not that all cloud-mediated systems are suspect. It is that the governance of those systems matters as much as the engineering. Who can audit the model? Who sees failure rates? Who decides thresholds? Who explains mistakes? Who has authority when a private platform and a public agency disagree?
Those questions are already familiar in cybersecurity. They are now migrating into physical safety.
The concrete lessons are already visible:
The Phone Became a Siren Before the Ground Became News
The most arresting detail from Venezuela was not that Android phones buzzed. It was that, for some people, the alert appears to have arrived before the shaking became obvious enough to send them running. In an earthquake, seconds are not comfort; they are time to move away from glass, duck under a table, stop an elevator, halt a surgery, or simply understand that the world is about to become violent.Reports from Venezuela described users receiving Android earthquake warnings moments before the Wednesday quake, with officials and international outlets later reporting a death toll that had climbed past 900. Images from La Guaira state and surrounding areas showed damaged and leaning buildings, and the disaster quickly became a test case for a technology most people barely know exists until it interrupts their screen.
Google’s Android Earthquake Alerts System is not a novelty feature in the way a weather widget is a feature. It is an attempt to turn the installed base of Android phones into a distributed seismic network, especially in countries that do not have dense government-operated early-warning infrastructure. The system uses the accelerometer already inside the phone, the same sensor that helps determine orientation and motion, to detect the initial movement patterns associated with an earthquake.
That makes the Venezuelan alerts politically and technically important. The public story is a hopeful one: ordinary phones became lifesaving devices. The more complicated story is that a global emergency-warning layer is being assembled from private hardware, proprietary algorithms, mobile operating systems, cloud servers, app-services infrastructure, and user trust.
Google Did Not Predict the Quake, and That Is the Whole Point
The phrase “Google warned people before the earthquake” is useful shorthand, but it is also misleading if read literally. Earthquake early warning is not prediction. It does not know an earthquake will happen before rupture begins; it detects the earliest physical evidence that one is already happening.Earthquakes produce different types of seismic waves. The faster primary wave, or P-wave, often arrives before the slower and more destructive S-wave. A sensor near the rupture can detect the first wave, transmit that signal, and give people farther away a few seconds — sometimes more, often less — before stronger shaking reaches them.
Traditional systems do this with networks of seismometers. Google’s twist is to use Android phones as the sensing layer where dedicated instruments are sparse. A single phone jostling in a pocket proves almost nothing, but many phones registering similar motion patterns across a region can form a signal strong enough for a server-side system to estimate that a quake is underway.
That is why density matters. A smartphone early-warning system is not merely a clever use of sensors; it is a population-weighted instrument. It is strongest where many Android phones are powered on, stationary or semi-stationary, connected, opted into the relevant services, and close enough to the source to detect the first waves before the warning has lost practical value.
Venezuela, with high smartphone reliance and uneven public infrastructure, is exactly the kind of environment where such a system can look almost miraculous. But the miracle is still bounded by physics, communications latency, device distribution, and software decisions made far from the fault line.
Android’s Advantage Is Scale, Not Magic
The Android system works because modern phones are full of sensors that most users rarely think about. Accelerometers measure changes in motion. They help phones rotate screens, count steps, detect crashes, stabilize photos, and support games. In Google’s earthquake system, the accelerometer becomes a crude seismometer when many devices report the same kind of ground movement at roughly the same time.Google has described a two-stage alerting model. A lower-level “BeAware” alert is intended for weaker shaking and gives users a heads-up. A higher-level “TakeAction” alert is designed for more serious shaking, taking over the screen and sounding loudly even when the phone is silenced.
That distinction matters because emergency warnings have to fight human behavior. A quiet notification is easy to miss. A full-screen, high-volume alert is intrusive by design. The system is therefore not only detecting earthquakes; it is making a judgment about how forcefully it is allowed to interrupt a person’s life.
For WindowsForum readers, the analogy is not hard to spot. This is the emergency-alert version of the same platform logic that governs Windows Update, SmartScreen, Defender reputation checks, passkey prompts, and cloud-mediated identity protections. The endpoint becomes a participant in a larger security or safety system, and the cloud decides when local behavior should change.
The difference is that a bad SmartScreen reputation might block an installer. A bad earthquake alert decision can determine whether someone stays in bed, runs down a stairwell, or ducks under a table. The stakes are immediate and physical.
The Turkey Failure Still Shadows Every Android Alert
Any honest account of Android earthquake alerts has to pass through Turkey and Syria. In February 2023, catastrophic earthquakes killed tens of thousands of people, and Google later acknowledged that its system failed to deliver the highest-severity alerts to millions of users who should have received them. The reported failure was not that phones were incapable of sensing ground motion; it was that the system underestimated the severity of the event.That is the nightmare scenario for algorithmic emergency infrastructure. A system can appear to function while making the wrong classification at the worst possible moment. It can send some warnings, log some detections, and still fail the people who needed the most urgent version of the alert.
Google has said it updated its algorithms after that failure. That is reassuring in the narrow sense that software can improve. It is also unsettling in the broader sense that the public only learns about the limits of these systems after large-scale tragedy exposes them.
The Venezuela case will likely be read by many as evidence that the system has improved. Perhaps it has. But public praise on social media is not the same as an audited post-incident report. The meaningful questions are harder: how many people received alerts, how much warning time did they get, how many should have received alerts but did not, how many alerts were delayed, and how well did the alert severity match observed shaking?
Those are not academic quibbles. They are the difference between a feel-good story about smartphones and an accountable safety system.
False Alarms Are Not a Side Issue
Google also apologized in 2025 after a false earthquake alert was sent to some Android users in Brazil. In ordinary consumer software, false positives are annoying. In emergency warning, they are corrosive.Every warning system lives between two failures. Missed alerts leave people unwarned. False alerts train people to ignore the next warning. The more dramatic the alert, the more damaging a false alarm can be to public trust, but the less dramatic the alert, the less likely people are to act when action is necessary.
This is why earthquake warning is a brutal design problem. You cannot simply tune the system to warn everyone at the slightest hint of danger. Over-warning creates fatigue and may cause panic, injuries, or dangerous evacuations. Under-warning preserves calm until the moment it becomes deadly.
The tradeoff is sharper for a company like Google because Android alerts operate across countries with different building standards, emergency agencies, cellular networks, languages, risk profiles, and public expectations. A threshold that makes sense in one region may be wrong in another. A user accustomed to typhoons or civil-defense alerts may react differently from someone encountering a full-screen earthquake warning for the first time.
Venezuela’s reports of users praising the alerts should not obscure the system’s fragility. Public trust is earned incident by incident, and it can be lost just as quickly.
Apple’s Model Looks More Conservative by Design
The comparison with Apple is instructive because it reveals two very different philosophies. iPhones can receive government emergency alerts, and Apple says users in some regions can receive earthquake alerts from other alert originators. Apple devices can also relay certain emergency alerts to nearby Apple devices without cellular or Wi-Fi connectivity, potentially extending the reach of warnings in degraded network conditions.What Apple has not done, at least publicly, is turn the global iPhone base into a crowdsourced earthquake detection network on the same model as Google’s Android system. That choice may reflect technical, legal, privacy, or institutional caution. It may also reflect Apple’s longstanding preference for tightly controlled experiences over massive, probabilistic public infrastructure experiments.
Google’s approach is more ambitious and more exposed. It leverages Android’s enormous global footprint and the reach of Google Play services. It can bring warning capability to places where dedicated systems are limited. But it also means a private company is making detection and alerting decisions at planetary scale.
Apple’s more conservative posture avoids some of those responsibilities while leaving more of the detection burden to governments and specialist alert originators. That may be less exciting, and in some countries less useful. But it also keeps the line between public emergency authority and platform provider somewhat clearer.
Neither model is obviously sufficient on its own. A government-only system may not reach enough people fast enough. A platform-only system may lack transparency, accountability, and local integration. The future likely belongs to hybrids, but hybrids are messy.
The Platform Is Now Part of the Disaster Response
For years, the consumer-tech industry has sold phones as cameras, wallets, identity cards, health trackers, and personal assistants. Venezuela adds another role: phones as civil-defense terminals. That role changes the relationship between users, operating systems, and governments.If Android can warn of an earthquake, users will expect it to work. If it fails, they will ask whether Google, carriers, phone makers, regulators, or local authorities were responsible. If it sends a false alarm, the same chain of responsibility becomes even murkier.
This is not unique to earthquakes. Modern emergency communications already rely on carriers, handset vendors, location services, satellite links, app ecosystems, and operating-system-level alert permissions. But earthquake early warning is unusually unforgiving because delays are measured in seconds rather than minutes.
The practical implication is that platform reliability becomes public-safety reliability. Battery optimization policies, background service restrictions, regional service availability, notification permissions, network congestion, localization quality, and device fragmentation all become part of the emergency-warning equation.
That should make administrators and policymakers uncomfortable in a productive way. If a public warning function depends on private mobile infrastructure, then that infrastructure needs more than marketing claims. It needs testing, disclosure, interoperability, and post-event accountability.
The Privacy Tradeoff Is Real, Even When the Cause Is Good
A phone-based earthquake system does not need to be a dystopian surveillance machine to raise legitimate privacy questions. It depends on phones detecting motion and communicating location-adjacent signals to a cloud service. Google can design the system to minimize data exposure, aggregate signals, and avoid identifying individual users, but the public still deserves a clear explanation of what is collected, when, and how long it is retained.The emergency context complicates the debate. Many people will gladly accept limited sensor use if it gives them ten seconds before a wall collapses. Others will reasonably worry that emergency exceptions have a habit of expanding once infrastructure exists.
The right answer is not to reject sensor-based warning systems. It is to demand that safety features be governed by unusually strict transparency. Users should be able to understand whether their phones participate in detection, whether participation is tied to Google services, what regional rules apply, and how to disable or verify settings without digging through ambiguous menus.
There is also an equity issue hiding in the technical design. People with newer phones, charged batteries, stable connectivity, and access to platform services are more likely to benefit from these systems. People with older devices, disabled services, weak signal, or no smartphone at all may be left dependent on neighbors, sirens, radio, or nothing.
A smartphone warning system can reduce inequality in countries without dense seismic networks, but it can also reproduce the inequalities of device access and connectivity. The people most exposed to dangerous buildings and fragile infrastructure are not always the people best served by high-end mobile ecosystems.
Seconds Help Only If People Know What to Do With Them
The romantic version of earthquake alerts imagines a phone sounding and a user instantly taking the correct action. Real life is less orderly. People freeze, check the screen, search for relatives, run toward exits, or dismiss notifications out of habit.That means alert design is not only a software problem. It is an education problem. A warning that says shaking is expected needs to be paired with public knowledge about what action is safest in the local built environment.
In many earthquake-prone countries, official advice emphasizes dropping, covering, and holding on rather than running during active shaking. But advice can vary depending on building type, local hazards, and whether a person is indoors, outdoors, driving, or near the coast. A few seconds of warning are valuable only if the recipient has already internalized the response.
This is where governments and platforms need each other. Google can deliver an alert quickly. Local authorities can shape the message, run drills, and explain how people should react. Without that civic layer, a technically successful alert can still produce chaotic behavior.
For Venezuela, where social media posts reportedly showed people leaving buildings after alerts, the question is not whether those reactions were understandable. They were. The question is whether the country’s public-safety institutions can turn this moment into durable preparedness rather than a viral anecdote.
The Windows Lesson Is About Trust Boundaries
At first glance, an Android earthquake alert may seem outside the WindowsForum lane. It is not. The same architectural trend is reshaping every major platform: endpoint devices are becoming sensors and actuators in cloud-managed safety systems.Windows PCs participate in malware telemetry, identity-risk checks, device-health reporting, enterprise compliance, location services, and update orchestration. Microsoft, like Google and Apple, increasingly treats the device as one node in a wider risk-management network. That model can be powerful, but it forces users and administrators to decide where the trust boundary should sit.
Earthquake alerts are simply the clearest possible demonstration because the consequences are visible. A cloud service evaluates distributed signals and commands local devices to interrupt users. In enterprise IT, this resembles a security incident response. In civil life, it becomes a public warning.
The lesson for IT pros is not that all cloud-mediated systems are suspect. It is that the governance of those systems matters as much as the engineering. Who can audit the model? Who sees failure rates? Who decides thresholds? Who explains mistakes? Who has authority when a private platform and a public agency disagree?
Those questions are already familiar in cybersecurity. They are now migrating into physical safety.
The Alert That Arrived in Venezuela Carries a Bigger Message
The immediate story from Venezuela is that Android phones may have given some users precious seconds before severe shaking. The broader story is that the world is quietly building a public-warning layer out of consumer electronics. That layer will be faster and more extensive than older infrastructure in some places, but also less accountable unless regulators, scientists, platform vendors, and civil society force it to be.The concrete lessons are already visible:
- Android phones can function as a distributed earthquake detection network by using accelerometers to detect early seismic motion and sending signals to cloud systems for rapid analysis.
- Google’s alerts are not earthquake predictions; they are attempts to warn people after a quake begins but before more damaging shaking reaches them.
- The system’s performance in Venezuela should be judged not only by viral success stories, but by warning coverage, timing, severity accuracy, missed alerts, and false positives.
- The 2023 Turkey-Syria failure remains a critical warning that large-scale alert systems can detect an event yet still underestimate its danger.
- Apple’s more limited approach highlights an unresolved industry split between platform-run detection and alerts originated by governments or specialist agencies.
- Smartphone-based warning systems can save lives, but they need public education, transparent auditing, and integration with official emergency response.
References
- Primary source: Geo News
Published: 2026-06-26T19:50:28.753345
How some Venezuelans' smartphones warned of quake
Many social media users in Venezuela have reported receiving alerts on Android smartphones moments before Wednesday's quake with over 900 confirmed dead.Google's Android and Apple's iOS, both include the option to display government...www.geo.tv - Independent coverage: Hindustan Times
Published: Fri, 26 Jun 2026 05:19:19 GMT
Heads-up of seconds in Venezuela: How Android smartphones turned into a network of earthquake alerts system | World News
Because alerts travel as electronic signals, they can reach Android phones before seismic waves arrive. Those few seconds, Google says, can be crucial. | World Newswww.hindustantimes.com - Independent coverage: WION
Published: Thu, 25 Jun 2026 14:11:00 GMT
- Related coverage: axios.com
Venezuela earthquakes kill dozens, injure hundreds as buildings damaged
The 2 quakes killed dozens of people, injured hundreds and damaged buildings across the country, officials said.www.axios.com
- Related coverage: techspot.com
Google admits Android alert failure during 2023 Turkey earthquake | TechSpot
On 6 February 2023, a 7.8 magnitude earthquake struck near Gaziantep in southern Turkey, close to the Syrian border. It was followed by a second major quake...www.techspot.com - Related coverage: androidheadlines.com
Google’s Earthquake Alerts Hit 790 Million Warnings — And They're More Accurate Than You Think
Google has released a study showing the effectiveness of its Android Earthquake Alert system. It is available to 2.5 billion users worldwide.
www.androidheadlines.com
- Related coverage: androidauthority.com
Google admits Android's earthquake alerts failed ahead of deadly quake
Google has admitted that its Android Earthquake Alerts system failed to deliver accurate warnings during the 2023 Turkey earthquakes.www.androidauthority.com - Related coverage: gadgets360.com
- Related coverage: aiaaic.org
AIAAIC - Google early warning system fails to alert people during Turkey earthquake
Google early warning system fails to alert people during Türkiye earthquakewww.aiaaic.org
- Related coverage: androidcentral.com
Google admits its alert system failed to accurately warn people in Turkey's 2023 quake | Android Central
The system miscalculated the magnitude of the first earthquake, sending a less severe notification to many.www.androidcentral.com - Related coverage: gulfnews.com
Did Google Predict the Venezuela Earthquake? How Android’s Earthquake Alerts Really Saved Lives
Did Google really predict the Venezuela earthquake? Learn how Android’s Earthquake Alerts detected tremors in seconds and gave users life-saving warning time.gulfnews.com - Related coverage: theguardian.com
Venezuela declares state of emergency after deadly twin earthquakes | Venezuela | The Guardian
Second quake, at magnitude 7.5, was most powerful to strike the country since 1900, collapsing buildings in capitalwww.theguardian.com - Related coverage: blog.google
Android earthquake alerts now available everywhere in the U.S.
Android Earthquake Alerts is expanding to all 50 U.S. states, using phones to detect earthquakes and send early warnings to users.blog.google - Related coverage: eluniverso.com
Terremoto en Venezuela activa red global de alertas de Google en millones de celulares Android | Internacional | Noticias | El Universo
El sistema Android Earthquake Alerts envía notificaciones automáticas segundos antes o durante un sismo.www.eluniverso.com - Related coverage: elpais.com
Así usó Google los móviles para detectar el terremoto y avisar a millones en Venezuela | Tecnología | EL PAÍS
El gigante tecnológico emplea desde 2021 los sensores de los teléfonos Android para generar avisos tan rápidos y precisos como los de los sistemas oficiales que emplean sofisticadas redes sismológicaselpais.com - Related coverage: livescience.com
Google has turned 2 billion smartphones into a global earthquake warning system — it's just as effective as seismometers | Live Science
Google's earthquake early-warning system has used phone accelerometers to increase quake alerts by tenfold across 98 countries.www.livescience.com - Related coverage: lemonde.fr
Venezuela reels after deadliest double earthquake in 126 years
At least 32 people have died and more than 700 have been injured after two powerful earthquakes struck Venezuela, according to an initial provisional count by authorities, who fear the toll may rise, particularly in the region near Caracas.www.lemonde.fr - Related coverage: phys.org
Loading…
phys.org - Related coverage: actalliance.org