Skip to main content

Google is turning Android Phones into seismometers

Google  is launching a handful of new Android features today that don’t really have a lot in common but that are all interesting in their own right. There are updates to Android Auto and Android’s  emergency location service, new accessibility features thanks to an updated Lookout app, and the promise of better sleep thanks to the bedtime tools in the Android Clock app now rolling out to all Android devices running version 6.0 or later (this was a Pixel-only feature before).

But the highlight of today’s release is surely Google’s new worldwide earthquake detection system and the new earthquake alerting feature it is launching for California. With this, Google is essentially turning your Android phone into a seismometer to create what the company says is “the world’s largest earthquake detection network.”

Image Credits: Google

The company argues that smartphone accelerometers are sensitive enough to measure the P-waves that are the first waves to arrive after an earthquake. Whenever the phone thinks it has detected an earthquake, it will send that info to a central server which then determines whether this was really an earthquake. For now, Google will only use this data to show information when somebody then searches for ‘earthquake’ or a similar keyword. Over time, though, it expects to be able to send out alerts based on these phone-based systems.

In California, the company is already going a step further, though. Working with the United States Geological Survey (USGS) and California Governor’s Office of Emergency Services (Cal OES), Google is using the ShakeAlert network — which itself uses data from 700 seismometers from across the state — to provide earthquake alerts. “A few seconds of warning can make a difference in giving you time to drop, cover, and hold on before the shaking arrives,” Google argues.

Image Credits: Google

Comments

Popular posts from this blog

Database Internel Architecture: SQLite

Introduction A database is an essential part of building a software system which used to store and read data efficiently. Here, We are going to discuss some architectural details of database implementation by using an early version of SQLite. SQLite is a small database application which used in millions of software and devices. SQLite invented by D.Richard Hipp in August 2000. SQLite is a high performance, lightweight relational database. If you are willing to learn internal of a database in coding level, then SQLite is the best open source database available out there with highly readable source code with lots of documentation. Reading later versions of SQLite become a little harder since it contains lots of new features. In order to understand the basic implementation of database internals, You should have good knowledge about data structures, some knowledge about Theory of Computing and how an operating system works. Here we are looking into the SQLite 2.5.0 version. Here ...

Weird Programming Languages

There are thousands of programming languages are invented and only about hundred of programming languages are commonly used to build software. Among this thousands of programming languages, there are some weird type of programming languages can be also found. These programming languages are seems to be called weird, since their programming syntax and the way it represent its code. In this blog we will look into some of these language syntax. Legit Have you ever wonder, when you come to a Github project that print hello world program, but you cannot see any codes or any content. Check this link  https://github.com/blinry/legit-hello  and you will see nothing in this repository. But trust me, there is hidden code in this project. If you see the  commit  section, you can reveal the magic. Yeah, you are right. Its storing hello world code in inside the git commit history. If you clone this project and run the following command, then you can see the hidden code i...

[Short Blog] Apache Kafka consumer with WSO2 Micro integrator

  This document contains steps that I have followed to setup inbound endpoint with Kafka Avro messages. Setting up Kafka server and UI First download theKafka kafka_2.11–2.2.1 for Zookeeper and Kafka server.  https://archive.apache.org/dist/kafka/2.2.1/kafka_2.11-2.2.1.tgz Start Zookeeper with kafka_2.11–2.2.1. Go to the kafka home folder and execute: bin/zookeeper-server-start.sh config/zookeeper.properties` The same way, start Kafka with : bin/kafka-server-start.sh config/server.properties Download confluent-5.2.1 for Schema registry  https://packages.confluent.io/archive/5.2/confluent-community-5.2.1-2.11.tar.gz Start Schema registry with following command on the confluent home folder: bin/schema-registry-start ./etc/schema-registry/schema-registry.properties As the UI for Kafka I used  https://github.com/provectus/kafka-ui . Optionaly you can use it to confirm messages are publishing correctly. You can use prebuilt jar file and start the UI with following command...