Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I heard it was the cell broadcast which caused the phones to vibrate at the same time, not people picking them up.


That would be quite an implementation flaw if it didn't account for the phone's own vibrations. Lots of countries use widespread emergency alert messages frequently.


What if it's actually another phone's vibration laying next to each other? Me and my wife leave our phones together when going to sleep.


not only that but my android phone sleeps together with my android reading tablet


Awww that's cute. Did they produce little baby Android devices?


They fixed this bug, we had plenty of emergency cell broadcasts since the false alarm.


if (!isShakerRunning) { sendAlert() }

seems like a pretty obvious thing to add


Only obvious once you've thought of it I suppose...


It's obvious to anyone that's written software for hardware sensors to ensure the hardware itself is not going to interfere with readings of other sensors. Don't tell the motor to run if the motor is already running type of issues. It's a fairly common bozo check


Doesn't seem that obvious to me


Typical Google product. Reminds me of a person who put a bunch of phones in a car and drove which caused Google maps to wrongly show traffic in that area. It was deliberately done though as an experiment


Better yet, he put them in a child's wagon and carted them around Berlin


One of the last before-times human interest stories: https://www.wired.com/story/99-phones-fake-google-maps-traff...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: