By Daniel Oberhaus October 30, 2018, 5:20pm
🤨
Yet both Android and Apple phones use MEMS silicon for their devices, so why were only Apple phones affected?
Glad I’ve got an Android since I could potentially work with liquid Hydrogen…
Hydrogen
This says that hydrogen isn’t just a problem, just helium:
It seems that MEMS is very sensitive to helium, but only helium. This Link stated that hydrogen does not affect MEMS, which surprised me.
Helium doesn’t just kill apple devices, It kills anything with a MEMS oscillator. Helium atoms are so small that it’s impossible to make a seal that completely blocks them.
Hmm.
That seems like it’d open a lot of potential abuses.
I wonder what the failure mode of various electronic locks is when they’re exposed to helium?
If you are in a position where you can dump random gases into the air supply to the degree it impacts these devices then they are likely compromised in other ways as well.
a very small percentage of helium will disable the phone
You don’t necessarily need to put it into the air supply, could just bathe the specific device you want disabled in helium from a deodorant can or something
If you are close enough to spray a device you are close enough to just steal it. Or spray the owner.
If it’s bolted to a wall and unattended neither of those things are an option
If y9ou are close enough to a system of importance that you can spray it, you are close enough to compromise it in countless other ways.
This is just one of many physical access attacks. Just like “you could take a hammer to it”
Like, I know people want to think this is some Ocean’s Eleven heist waiting to happen. It isn’t. At best it is an episode of Burn Notice where Michael has to rapidly improvise an escape where his CIA handler of the week already refused to give him something much more useful.
Lock picking lawyer gonna have to get on this
[…] so why were only Apple phones affected?
The answer, it seems, is because Apple recently defected from traditional quartz-based clocks in its phones in favor of clocks that are also made of MEMS silicon. Given that clocks are the most critical device in any computer and are necessary to make the CPU function, their disruption with helium atoms is enough to crash the device.
In this case, the leaking helium from the MRI machine infiltrated the iPhones like a “tiny grain of sand” and caused the MEMS clocks to go haywire.
https://en.m.wikipedia.org/wiki/Microelectromechanical_system_oscillator
Interesting
MEMS oscillators incorporate MEMS resonators, which are microelectromechanical structures that define stable frequencies. MEMS clock generators are MEMS timing devices with multiple outputs for systems that need more than a single reference frequency. MEMS oscillators are a valid alternative to older, more established quartz crystal oscillators, offering better resilience against vibration and mechanical shock, and reliability with respect to temperature variation.
So the helium causes physical interference by leaking into the housing?
Yup. Helium is such a tiny thing it can diffuse through almost anything, and in MEMS oscillators which are supposed to be at a rock solid 32kHz, causes variance in the frequency eventually just “gumming” it up entirely and causing it to stop working.
If you want to know how and why, Applied Science did a video on it. Five years ago. Because that’s when this leak happened.
the fate worse than quenching.
and now I’m imagining Siri speaking in a very high-pitched voice.
…Yet both Android and Apple phones use MEMS silicon for their devices, so why were only Apple phones affected? The answer, it seems, is because Apple recently defected from traditional quartz-based clocks in its phones in favor of clocks that are also made of MEMS silicon.
So, they ask the question of why iPhones are the only ones affected if androids also went to MEMS, then answer it by saying that apple went to MEMS. Are they saying that the clocks in Androids still use quartz, but iPhones use MEMS clocks, even though they both use general MEMS silicon?
Edit, autocorrect
Wasn’t this exact scenario posted to r/talesfromtechsupport a few years ago? It sounds very familiar
This article is from 2018.
