Xiaomi was founded on April 6th, 2010 and its fifth anniversary is just around the corner. In the past five years, the company has grown by leaps and bounds, rising to the positions of largest smartphone OEM in China and third-largest globally and coupled with its expansion plans and 100 million sales benchmark, this anniversary warranted a fervent celebration. After teasing products on its forums for a few days, Xiaomi held the anniversary event earlier today and staying true to the...
Carrier IQ Releases a Report, FBI is Silent
Carrier IQ released a 19-page document explaining their software, how it’s used, and how it protects the data it collects. Much of it we already heard, but now with more thorough detail. Click here to listen to this article.
After describing the basics of Carrier IQ and how it’s implemented–a section which points a finger squarely at the manufacturers and carriers–the document addresses specific questions people asked since the issue blew up in the media. They begin by answering Trevor Eckhart’s (XDA Recognized Developer, TrevE) video that shows IQ Agent listening to keystrokes.
We cannot comment on all handset manufacturer implementations of Android. Our investigation of Trevor Eckhart’s video indicates that location, key presses, SMS and other information appears in log files as a result of debug messages from pre-production handset manufacturer software. Specifically it appears that the handset manufacturer software’s debug capabilities remained “switched on” in devices sold to consumers… The IQ Agent does not use the Android log files to acquire or output metrics.
But they recognize the danger of that information sitting in Android logs, and recommend that manufacturers and carriers turn off debugging to keep those logs hidden. Then, they claim to have found a bug during their investigation that actually sends encrypted SMS texts, but they promise that they don’t unencrypt those messages.
Carrier IQ has discovered that, due to this bug, in some unique circumstances, such as a when a user receives an SMS during a call, or during a simultaneous data session, SMS messages may have unintentionally been included in the layer 3 signaling traffic that is collected by the IQ Agent.
They then explain that web URLs are collected at the behest of the carrier, as they say, to diagnose Internet browsing issues. All of this information is stored on your device until it is uploaded, which “is typically [every] 24 hours.” They do not provide the complete range of intervals their software is capable of setting in a profile. However, the upload can be manually triggered, either by entering a keycode or by remote control, with commands sent in SMS texts. According to TrevE, these texts are hidden from the user.
Lastly, the report addresses its collection of location data. They explain the intended use of the information, but do not explain the criteria for location collection. That is, we don’t know the intervals at which your GPS location is recorded, and if the software on the phone determines whether to send only some of those locations. This is important because the FBI may have excessively pinged information collected by Carrier IQ’s software, without warrant, to track the locations of individuals.
In fact, MuckRock News, a website that helps people request information from the FBI, reported that their FOIA request for reports on Carrier IQ was denied. The reason given is that release of that information would compromise an ongoing investigation. Either they are still using that information, investigating Carrier IQ, or both. The denial itself is confirmation that the FBI has such documents.
Personally, I wouldn’t be surprised if they launch an investigation of Carrier IQ in order to buy some time before admitting their use of the data. As far as Carrier IQ is concerned, I appreciate the explanation of your software’s intended use, but what we want to know, all of our concerns, require the full disclosure its actual use.
Want something on the XDA Portal? Send us a tip!
A few months ago, we came up with the idea of presenting the history of flagship devices released by some of the major Android OEMs. In this, we've had the pleasure of bringing you the stories of Sony (Ericsson) and Samsung. Now, it's time for our third and final installment. This is a very special episode, as the OEM I will talk about was heavily connected to Android and the beginnings of XDA as a whole. Yes, I'm talking about HTC, the...
Unfortunately there was a memory leak in Android 5.0.x Lollipop. Thankfully it was fixed in Android 5.1. However, at the time of this video Xposed Framework doesn’t have Android 5.1 support. So you are faced with a choice of fixing the memory leak or running your Xposed Modules. Or are you? In this episode of XDA Xposed Tuesday, XDA TV Producer TK reviews an Xposed Module that adds the Android 5.1 memory fix to pre 5.1 Lollipop devices. The module...