Database Info

[Q] carrier iq

is carrier iq on the nexus s also, will it be on the nexus s 4g coming out on sprint?

the SNS coming out for Sprint will be different than the current SNS, as it will come with the 4G radio instead of 3G

I don't really know what carrier iq is unless you mean Sprint ID which the GSM SNS does not have. I have not heard of the CDMA SNS having Sprint ID.

http://forum.xda-developers.com/showthread.php?p=11763089#post11763089

What is carrier iq?

read the post i posted a link to.

heldunder said:
read the post i posted a link to.
Click to expand...
Click to collapse
Oh I see now! I didn't see the post in there:
Put simply - and bluntly - Carrier IQ is a software package buried deep within Android by Samsung at the behest of Sprint. It has been in active use since the time of the Moment, if not before. The company that develops it, also known as Carrier IQ, bills it as "Mobile Service Intelligence". In their own words,
[T]he combination of the MSIP and IQ Insight lets you move seamlessly from broad trend data across many users, through comparative groups down to diagnostic data from individual devices. Now, not only can you identify trends, you have the power to drill down to specific instances, giving you the insight your specialists need to make a difference.
On its own, that description can vary from harmless, to worrying, depending on how you look at it. It's not until one drills deep down into the system and ferrets out every piece of the software that one truly knows what it contains. As some of you might remember, ACS took the first steps toward disabling the Carrier IQ software with the release of SyndicateROM and Xtreme Kernel 1.0. That, however, didn't even scratch the surface.
Carrier IQ's native libraries are plainly visible - libiq_client.so and libiq_service.so in /system/lib. During every boot, this service is launched - you can see it in Settings > Applications > Running Services as "IQAgent Service". These native libraries are called by non-native (Android application) libraries located in ext.jar (the client) and framework.jar (the service). Removal of these (rather obviously-named) libraries alone, be it the .so files or the libraries in framework or ext, will, obviously, break boot. So I - k0nane - had to dig deeper. To make a long story short, reference to the IQ Service and IQ Client were littered across the deepest portions of the framework, and some of the most basic functions of the Android system as we know it.
Carrier IQ as a platform is designed to collect "metrics" at any scale. What I found it to hook into is far beyond the scope of anything a carrier needs - or should want - to be collecting. Carrier IQ sits in the middle of, and "checks" the data of, SMS and MMS messages. It listens for and receives every battery change notifications. It hooks into every web page you view, and every XML file your device reads. It receives every press of the touch screen. It 'sees' what you type on the physical keyboard. It reads every number you press in the dialer. It can track which applications you use, what 'type' they are, how often, and for how long. It hooks into data sent and received.
I, and the rest of ACS, ask Samsung and Sprint - why do you want this information? Why do you need it? Why is the capability in place?
The only saving grace - if there is one - to this nasty, ten-legged mutant spider is that its logs are off by default. During the investigation process, I was able to enter its UI. Below are two screenshots of it.
Click to expand...
Click to collapse

Carrier IQ was found 6mths ago

k0nane said:
What Is Carrier IQ? Why Should We Care?
3/31/2011: Hello, Slashdotters!
11/14/2011: Hello, XDA and Android media!
XDA author egzthunder1 has published an article on CIQ, with LOTS of information provided by developer TrevE. If you did not come here from that article, please click HERE to read it.​
Put simply - and bluntly - Carrier IQ is a software package buried deep within Android by Samsung at the behest of Sprint. It has been in active use since the time of the Moment, if not before. The company that develops it, also known as Carrier IQ, bills it as "Mobile Service Intelligence". In their own words,
On its own, that description can vary from harmless, to worrying, depending on how you look at it. It's not until one drills deep down into the system and ferrets out every piece of the software that one truly knows what it contains. As some of you might remember, we took the first steps toward disabling the Carrier IQ software with the release of SyndicateROM and Xtreme Kernel 1.0. That, however, didn't even scratch the surface.
Carrier IQ's native libraries are plainly visible - libiq_client.so and libiq_service.so in /system/lib. During every boot, this service is launched - you can see it in Settings > Applications > Running Services as "IQAgent Service". These native libraries are called by non-native (Android application) libraries located in ext.jar (the client) and framework.jar (the service). Removal of these (rather obviously-named) libraries alone, be it the .so files or the libraries in framework or ext, will, obviously, break boot. So I had to dig deeper. To make a long story short, reference to the IQ Service and IQ Client were littered across the deepest portions of the framework, and some of the most basic functions of the Android system as we know it.
Carrier IQ as a platform is designed to collect "metrics" at any scale. What I found it to hook into is far beyond the scope of anything a carrier needs - or should want - to be collecting. Carrier IQ sits in the middle of, and "checks" the data of, SMS and MMS messages. It listens for and receives every battery change notifications. It hooks into every web page you view, and every XML file your device reads. It receives every press of the touch screen. It 'sees' what you type on the physical keyboard. It reads every number you press in the dialer. It can track which applications you use, what 'type' they are, how often, and for how long. It hooks into data sent and received.
I and my fellow users ask Samsung and Sprint - why do you want this information? Why do you need it? Why is the capability in place?
The only saving grace - if there is one - to this nasty, ten-legged mutant spider is that its logs are off by default. During the investigation process, I was able to enter its UI. Below are two screenshots of it.
​
That being said, the question still must be asked - why is the service even running? Why does Sprint and Samsung feel the need to leave a dormant monster in every one of its most loyal customers' phones?
Here's the most important part (tl;dr): the Carrier IQ service is a drain on battery life and performance. In testing, I and others noticed a significant rise in Smartbench scores and overall system 'snappiness' after Carrier IQ's removal. In addition, with it removed, a prominent tester saw 30 hours of battery life, with heavy use, on the stock battery.
Thanks for the long read!
(continued in post below)
Click to expand...
Click to collapse
This Carrier Iq and its nasty shenanigans were discovered a while ago and removed from roms.

What was the point of it anyway? Why was it put into stock roms? For the governments of the world to keep a close eye on the people? Ha Ha Ha
Sent from my R800i using XDA App

CIQ FOI Request by MuckRock

Did a search and only saw repeating questions on removal of CIQ...
From what "looking into" I did this looks legit..
by Michael Morisy on Dec. 12, 2011, 2:30 p.m.
FOI Request: Manuals or Documentation Regarding Accessing Carrier IQ Data (FBI)
A recent FOIA request to the Federal Bureau of Investigation for "manuals, documents or other written guidance used to access or analyze data gathered by programs developed or deployed by Carrier IQ" was met with a telling denial. In it, the FBI stated it did have responsive documents - but they were exempt under a provision that covers materials that, if disclosed, might reasonably interfere with an ongoing investigation.
Carrier IQ came under fire after a security researcher demonstrated that the previously little-known company had software installed on a variety of phones on a variety of networks that could track user locations, keystrokes, encrypted Internet traffic and more, some of which was or could be sent back to either the cell phone owner's service provider or Carrier IQ's own servers.
What is still unclear is whether the FBI used Carrier IQ's software in its own investigations, whether it is currently investigating Carrier IQ, or whether it is some combination of both - not unlikely given the recent uproar over the practice coupled with the U.S. intelligence communities reliance on third-party vendors. The response would seem to indicate at least the former, since the request was specifically for documents related directly to accessing and analyzing Carrier IQ data.
I plan to appeal the blanket denial in hopes of answering that question.
Here is the full denial of the request:
Click to expand...
Click to collapse
http://www.muckrock.com/foi/view/un...-regarding-accessing-carrier-iq-data-fbi/947/
http://www.muckrock.com/foi/view/un...rier-iq-data-fbi/947/#273602-rejection-letter
http://www.muckrock.com/static/foia_documents/12-7_mr947.pdf

http://forum.xda-developers.com/showthread.php?t=1367282&highlight=the+ciq+thread

[Q] Deep PAID hack: RIL intercept and telephony.Connection.DisconnectCause

I've the forum rules: this query does not neatly fit anywhere, so I'll apologise in advance, but it does affect millions of people in real life in a very real and practical way.
There is a function in Android called com.android.internal.telephony.Connection.DisconnectCause.
It's function is to tell who tore down the voice call connnection, and specifically if it was due to the carrier having network congestion caused by their rent seeking under spending of CAPEX and general ****ty service. This indirectly implements (via the radio interface layer) Qualcomm diagnostics and ITU standards.
As it turns out, some (if not most) manufacturers have deliberately commented it out so it does not work, almost certainly at the request of the carriers.
So I am seeking a low level engineer up for some deep hacking to come up with a solution, perhaps one of the following:-
1. Ultra low level boot program that creates a micro-RIL with a single function of talking to the Qualcomm chipset before the main OS ROm starts to run for call diagnostics
2. A variation on above, namely a patch
3. A man-in-the-middle RIL daemon inserter to interrogate
4. Hack VALIK
5. Somethng else I have not thought of (I do not know Android except it has a Linux kernel and is a collective noun for a random collection of ROMs fiddled with by manufacturers who fill them with advertising **** and crippleware)
I will pay a $5k reward to who ever can help devise a manufacturer independent means of achieving this that is not too brittle and can somehow get that data to an ordinary app. The Qualcomm manuals and calls and even sample code is available to serious developers. Please privately message me if you are interested. This is not an "all or nothing" offer: I will pay more than one person for more than one pathway.
This is a real offer with real bucks and an ongoing retainer payment.
So there it is, money, a chance to make carriers crap service measurable and accountable and fame. There is a funny clip on you tube on this exact point ("they **** you with cell phones") with Joe Pesci at:

PM me, I have extensive experience with Qualcomm chipset interfacing, AT commands, RIL Hacking, OTA Layer 3 protocol decoding & etc.

SecAndy : let's get the party started

Pronounced "say candy", the goal of SecAndy is to come up with as secure and private of an OS as possible. So as not to reinvent the wheel, we'll base this initiative on our open source code of choice (Android or maybe other developers' choice).
I am not a developer myself but I can without a doubt, because of former professional experiences, organize a project and gather the right people together as a community in order to make sure that project sees the light of day after it has acquired a life of its own if needed, which I think we will agree is something that this kind of project requires because of the scrutiny it will quickly attract.
I am officially calling upon this post all interested developers that could help us fork Android or other open source OS.
Let's get a kickstarter funded and let the party begin. I will update you later today on the advancement of such.

This thread welcomes constructive ideas and developer participation, but here are beginning requirements we'll need to fulfill eventually to privatize and secure android :
- default browser allowing custom search engines such as https://ixquick.com or duckduckgo
- default system search pointing to those custom engines for online component
- control of gps at firmware level to allow full disability
- peer to peer file exchange (think BitTorrent sync) with 1024 to 2048 bit encryption
- implementation of secure sms and mms exchange (think textsecure)
- implementation of encrypted voice channels (think redphone or SIP with end-to-end encryption)
- root vpn for all online access
- systemwide warning of insecure solutions (example : wanting to use gmail or regular email)
- PGP transparent email solution
- Tor option for root vpn (subject to mitm attacks but more on that later)
- peerguardian type auto-updated database to identify suspicious IP address ranges
- systematic in-out firewall control auto updated with peerguardian database and community based rules database
- hardened malware protection and app permissions with automatic permission audit based on application type
- full device encryption and lockup (in case of unauthorized user)
- full remote wipe out and bricking with auto IMEI reporting (in case of theft, might have to be amended because of attack vector)
- full remote location capability with real time tracking (that one might have to be scratched, high security risk because of attack vector)
This obviously doesn't cover all the bases but would be a good start... I know a lot of these options can be implemented with a mismatch of apps and custom Roms but having it all at an OS level AOKP style would greatly help in building an android by the people for the people community that could eventually loosen the stranglehold of less than transparent corporations.

60 views in 24 hours and not one comment. Obviously I'm approaching this the wrong way. More news at 11.

e-motion said:
60 views in 24 hours and not one comment. Obviously I'm approaching this the wrong way. More news at 11.
Click to expand...
Click to collapse
I don't want to be insulting, but no programming work has been done on your part, and you're just asking for people to dive in this project to get managed by someone they never heard of. It's not really surprising no one has commented yet.

I understand what you're saying but any comment, even if only just to show interest in such a project, will be key to drive developers to it.
I might not have started any development but I have clear understanding of how to design secure solutions. I can't go into details of why that is, however you can clearly see with my 2nd post that some research has been done. If I wanted a solution for me alone, I could just go on with my own little pudding of custom ROM and security apps.
However, because of the recent news events that SHOULD have awaken this population, I thought now might finally be the right time to try to get such a project off the ground. But without anyone even showing any interest, why would any developer be drawn to it ? If people would rather focus more on content consumerism than on what might happen under an umbrella of spooks that they're paying for with their taxes, then they have learned nothing from history and deserve what's coming to them, simple as that.
This is NOT a development thread in case you haven't noticed, so telling me I haven't developed anything yet is not even relevant.

In case anyone cares, this will be moved shortly in the t-mobile Note 2 Android development thread as a Touchwiz proof of concept ROM. Little steps, little steps...
Sent from my SGH-T889 using Tapatalk 2

mobile sec
While I am not a developer I would be interested in this project. I've been thinking about this a bit lately given recent events. I think a useful privacy preserving security related app and phone combo might have these features:
-some way to separate the baseband processor (radio) from the OS. It seems most phones share memory with the radio and this fact can and has been exploited. Own the bb processor and you own the phone. Perhaps a 3g dongle plugged into an android phone in host mode would work. Some of these usb "data only" radios can be unlocked for voice too. I believe a rooted phone with IP tables/firewall running would be much more secure than a conventional mobile phone.
-an anonymising network for connecting to servers/peers. I think the i2p network is well suited for this purpose. Rather than connect to services that are not designed with your anonymity/privacy in mind, connect to hidden/darknet servers that make it extremely difficult to ascertain your real IP and location. Perhaps an i2p router running on your home computer relaying i2p traffic while also maintaining a long lived encrypted connection to your mobile in order to "push" data to it. In this way the user benefits from the anonymising network, contributes to the network, but doesn't have the battery drain of relaying packets from the phone (if this is even possible).
-end-to-end encryption. Perhaps OTR messaging for texting and perhaps openPGP for transferring binary files as I don't believe file transfer in OTR is available at this time.
-an app that uses the above network that is capable of sending/receiving encrypted text, audio, video, gps location etc and does not leak any personal information that you don't want leaked. XMPP might be a good choice (with perhaps out-of-band binary transfers for efficiency). Giving your unique identifier to another person that is using the same app would allow you to communicate with them while not revealing your phone number, imei, imsi, etc. There would be some latency in the communication especially with binary transfers but I would gladly accept that for the added security.
anyway, just wanted to add this to the conversation and hope to see this project take shape as we definitely need more security enabled os's and apps.