Hey Max, I know this is off-topic, but I couldn't find your earlier column (much earlier) about great Sci Fi novels that should be made into movies. Ender's Game is coming to theaters Nov. 1 of this year. Thought you would be interested.
Errr....most people consider the ability of a smartphone to RECEIVE calls or other push updates one of its more important features, so putting it in a metallic sleeve is never going to be a popular option outside of those who shop the kitchen aisle for their headwear.
Since RFID is remotely powered, and can be activated from a distance much further than the few inches its proponents claim, it is a totally different class of potential security issue than anything else on a smartphone. Even with the battery removed RFID can be activated from at least 10 feet away with some inexpensive gear that will fit inconspicuously in a briefcase or backpack.
As I was starting to read your comment and saw "metallized sleeve," it occurred to me that this might be a great product idea. Then I read to the end and I see you already came to the same conclusion :)
I recently got a passport card and it comes with a metalized sleeve to shield it from RFID spies. I could see something like that being needed for smart phones.
Maybe the phone covers that just about everyone buys should have shutters to cover the camera lens when not in use. Something to muffle the sound going into the mic would be appropriate as well.
Finally, you really want to make sure it's completely off and inaccessible a Faraday cage could be used as a cover over the cover. Sounds like a good Kickstarter project.
Sorry, not even compiling everything yourself will guarantee that no malware or spyware is infesting your device. See the Wikipedia article on Backdoors, http://en.wikipedia.org/wiki/Backdoor_(computing).
A camera can be fairly effectively covered (if one knows where it is/they are). The microphone might be more difficult to physically incapacitate.
Similar issues have already existed with personal computers. Many laptops have built-in webcams and microphones.
Because of its size, a cell phone would be somewhat easier to drop into a "privacy box" (with optional RF blocking) than a laptop. Such a box could even provide a charging function.
FLOSS and compiling yourself is insufficient. One would also need to examine all the source code of all the software and whatever binary bootstrap code is used to initially compile the compiler, and one would need a trusted platform on which to do the examination and compilation. Then one would need to trust that the loading of the software is "secure" and even that the hardware/firmware has no security flaws.
(By the way, software can be licensed in a way that allows use of source code and use of 3rd party patches without being Free/Open Source. If unlicensed use can be controlled or is a minor concern, proprietary software can even have the source be freely distributable--with only licensees having the rights to compiler and/or use the software.)
Given the practical need for a web of trust, compiling the software oneself is probably not that helpful. If one cannot trust the hardware vendor not to have pre-installed and unremovable (or just secret) malware, how can one trust that the software one installs will actually control the hardware?
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.