4 ms·
I heard it was the cell broadcast which caused the phones to vibrate at the same time, not people picking them up.
by underdeserver 1y ago
I heard it was the cell broadcast which caused the phones to vibrate at the same time, not people picking them up.
- ls-a 1y agoTypical 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
- Miraste 1y agoThat 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.
- irvymike 1y agoThey fixed this bug, we had plenty of emergency cell broadcasts since the false alarm.
- dylan604 1y agoif (!isShakerRunning) { sendAlert() } seems like a pretty obvious thing to add
- underdeserver 1y agoOnly obvious once you've thought of it I suppose...
- dylan604 1y agoIt'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
- John7878781 1y agoDoesn't seem that obvious to me
- tirant 1y agoWhat 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.
- wraptile 1y agonot only that but my android phone sleeps together with my android reading tablet
- OrangeMusic 1y agoAwww that's cute. Did they produce little baby Android devices?