Database Users

[PORT] Nexus S GB Port to Captivate (UPDATE: Wifi and 3G semi-working)

Nexus S full dump (including system, kernel and initramfs) is complete:
http://forum.xda-developers.com/showthread.php?t=875184
Our captivates can't wait for some Gingerbread cookies!!
Since hardware is virtually the same, it'd be logical to assume that porting from NS to SGS wouldn't be that time consuming..
--------------------------------------------------------------------------
I'll try to run the updates on this as they happen and as people post them (from newest to oldest):
--------------------------------------------------------------------------
Keep the swearing and arguing OFF THIS THREAD. We've been given a warning from moderators. If you want this thread to stay alive, keep it polite and ON THE TOPIC. Thank you.
[[[ UPDATE (Dec 23): ]]]
Follow @supercurio on tweeter!
Updates from supercurio SGS thread:
V5:
- Wifi semi-working (tend to crash the phone on Wifi sleep timeout)
- Calls working but no DATA for me (coolya had data, which means: erratic) - voice not tested.
- kind of laggy, but there is a lot of headroom.
- GPS working only by Wifi/Triangulation networking - No satellites.
+ V4 fixes:
Buttons fixed thanks to the contributions of xcaliburhands, pawitp, fenfir
No need to create some directories manually anymore.
Kernel available as ClockWorkMod recovery update.zip - be sure you have access to 3 buttons !
Click to expand...
Click to collapse
[[[ UPDATE (Dec 20, 2PM PST): ]]]
gtg465x said:
Buttons, calls, data, and sms work now. Still some polling problem. Wifi and GPS still not working... but getting very close to a usable (for more than just testing) build.
Click to expand...
Click to collapse
xcaliburinhand said:
Progress is being made, we now have a connection to the radio interface layer.
Great work being done by coolya.
Click to expand...
Click to collapse
[[[ UPDATE (Dec 20, 2PM PST): ]]]
supercurio said:
I invited major developers (kernel AND ROM) to a dev-only IRC channel so we can work together, and it looks good
If you're a dev, motivated and I forgot you (forgot a lot of people!) send me a message !
...
PS: there is no distinction between my port or CyanogenMod port anymore, we are all on the same boat now
Click to expand...
Click to collapse
[[[ UPDATE (Dec 20, 9AM PST): ]]]
Little bird told me that there may be a developer chat tonight, dedicated specifically to porting Gingerbread to SGS.
Stay tuned for updates.
[[[ UPDATE (Dec 19, 2PM PST): ]]]
Supercurio updates GB Galaxy S port to version 3!
Changes in v3:
- SDcard now works as internal storage and as USB storage
Click to expand...
Click to collapse
What doesn't work yet:
No WiFi
No Service
No Data
Camera doesn't work
GPS doesn't work (many of us are used to this already )
Buttons are mapped incorrectly
Click to expand...
Click to collapse
kennethpenn's guide to installing Supercurio's GB v3 on SGS/Captivate
================================================
[[[ UPDATE (Dec 18, 5PM PST): ]]]
kennethpenn: Instructions on how to install the GB Preview build on Galaxy S:
http://briefmobile.com/how-to-android-2-3-samsung-galaxy-s
Also, Konner920 Confirms that GB Preview build works on Captivate.
================================================
[[[ UPDATE (Dec 18, 10AM PST): ]]]
Supercurio creates a first bootable Nexus S -> Galaxy S Gingerbread ROM.
So far:
Don't work: GPS / Voice / Wifi / some Buttons / camera
Work: everything else: like sound, GL acceleration etc
Click to expand...
Click to collapse
You can't stop now, Supercurio! =)
================================================
[[[ UPDATE (Dec 17, 11AM PST): ]]]
Mr Supercurio has joined the thread, he answered questions starting at post #65 (page 5-ish). Here are some exempts for the lazy:
Filesystems won't be an issue, as with lagfix developers are very used to filesystem conversions and detailed mount options for most of them.
...
Nexus S is not 720P capable, today i cannot tell what are the implications for Nexus S ROM on Galaxy S
...
Modem / baseband may be challenging because of the difference in Radio Interface Layer but if we are really lucky it will work using the adequate modem.bin
...
I never said that i was abandoning the port, that's not my style.
...
This is just the beginning.
Click to expand...
Click to collapse
================================================
[[[ UPDATE (Dec 17, 11AM PST): ]]]
AOSP Post from Jean-Baptiste Queru:
Nexus S went on sale yesterday morning in the US, running Gingerbread.
Just like I did for Froyo, I'm open-sourcing the matching Android
platform source code, right after the first consumers get their hands
on it. I'm going to start literally right now, and the process will
take a few hours.
-Even though Nexus S is designed to be suitable for AOSP work, there
are some caveats. I very strongly recommend against trying to use
Nexus S for anything related to AOSP at the moment. Trying to unlock
or use your Nexus S for AOSP work could easily turn it into a Nexus B
(where B means "brick"); I have two of those, they're not very useful.
I'll send some guidelines about what is currently possible once I've
finished pushing the source code.
-Please take it easy on the kernel.org servers. They are very helpful
in hosting the AOSP source code, and I don't want to hurt the high
quality of their service with an onslaught of full Android downloads.
...
I'm kindly asking that you wait a few hours or a few days before you
download it (just roll a 6-sided die and wait that long). In addition,
the slower the servers are, the harder it is for me to do the push.
Click to expand...
Click to collapse
================================================
[[[ UPDATE (Dec 17, 10:30AM PST): ]]]
joedon3: 2.3 Source is being pushed to AOSP right now
================================================
[[[ UPDATE (Dec 17, Morning): ]]]
It looks like supercurio is onto it!
Thanks to johnyhoffman for the IRC log with supercurio:
¬ 10:34:06pm| @supercurio: tomorrow i'll make a NS kernel that install automatically the su binary
¬ 10:34:07pm| @supercurio: quick
¬ 10:34:19pm| Mazodude: nice
¬ 10:34:20pm| @supercurio: and after that, i'll be back on Nexus S kernel on SGS
¬ 10:34:33pm| @supercurio: see with designgears
¬ 10:34:40pm| @supercurio: about porting the rom also
...
¬ 11:24:36pm| @Frd^: supercurio: nice, you are still porting that rom to sgs?
¬ 11:24:48pm| @supercurio: Frd^, yes starting tomorrow with designgears
¬ 11:24:52pm| @supercurio: i'll do the kernel part of course
¬ 11:24:57pm| @Frd^: supercurio: nice =)
Click to expand...
Click to collapse

lol too late - posted it in General already this morning too

YES! God, since the Nexus S specs were announced, we've really been needing this.
Even with our somewhat superior hardware, HTC devs have still been kicking our @$$ in the development department.

Lets hope so......I think we have issues getting att bands on our cappys. But who knows. Hopefully well see some promise by the end of the day...
Sent from my SAMSUNG-GT-I9000 using XDA App

My captivate awaits this Only reason I haven't already gotten the Nexus is because of the lack of AT&T 3g support

Only issue I see is the difference in file systems being used. If we can get past that it looks pretty promising.

The difference in file system being used shouldn't make a difference. Your getting a completely new rom and kernel.....most of us went from rfs to ext2 ext4 or jfs. Depending on what lagfix was implemented
Sent from my SAMSUNG-GT-I9000 using XDA App

filesystem won't matter, since we're getting the kernel too (as mentioned) if the kernel can be used/reoriented/patched to run on the captivate. luckily we have the kernel source.
and maybe an issue with the modem as well, for 3g??

adamholden85 said:
Only issue I see is the difference in file systems being used. If we can get past that it looks pretty promising.
Click to expand...
Click to collapse
I would consider the filesystem a non-issue. Bigger issues are things like the Nexus S using different GPS hardware, no voice processor, possibly different modem stack.

The GPS chipset is the same as the Galaxy S.
The things that need to be worked around are:
-NFC hardware absent in SGS devices
-720P video recording present in SGS devices
-modem/cell radios
-button reordering
Thats just off the top of my head

emuneee said:
The GPS chipset is the same as the Galaxy S.
The things that need to be worked around are:
-NFC hardware absent in SGS devices
-720P video recording present in SGS devices
-modem/cell radios
-button reordering
Thats just off the top of my head
Click to expand...
Click to collapse
That, and the External SD on SGS devices is another.

Ugh, they reorganized the kernel structure once again. I really wish they would get consistent.

Nexus s rooted already via android central.
Sent from my SAMSUNG-GT-I9000 using XDA App

Doesn't take much to root adev phone.. Its literally just 'fastboot oem unlock' at the terminal and pressing the ok button that shows up.
Sent from my SAMSUNG-SGH-I897 using XDA App

Ok I will stick this for now to prevent the overload.

I'm pretty stoked for this. I've been running stock for a few months now. I might crack and flash my phone with gingerbread.

I've been impatiently waiting for a port of the Nexus S rom. But i will wait a little longer until some of the bugs for fixed.

adamholden85 said:
Only issue I see is the difference in file systems being used. If we can get past that it looks pretty promising.
Click to expand...
Click to collapse
The lagfix app/kernel already change the RFS to EXT4, so that shouldn't be an issue at all!

Or, you could just buy the phone like me? Hahha. Thanks man!

hansmrtn said:
Or, you could just buy the phone like me? Hahha. Thanks man!
Click to expand...
Click to collapse
the one your getting hans is att band compatible for 3g??

Modding the camera driver to use FFC for video chat

Android 2.3 provides 2 methods to open the camera (link):
1) open()
2) open(cameraId)
Method 2) is new to Android 2.3, but not many apps use it yet. Method 1) is provided in Android 2.2, which many video chats app uses. Unfortunately, it is hardcoded to access the rear camera:
public static Camera open() {
int numberOfCameras = getNumberOfCameras();
CameraInfo cameraInfo = new CameraInfo();
for (int i = 0; i < numberOfCameras; i++) {
getCameraInfo(i, cameraInfo);
if (cameraInfo.facing == CameraInfo.CAMERA_FACING_BACK) {
return new Camera(i);
}
}
return null;
}
I would like change this logic so that it read in the camera index from some file, e.g. defaultCamera.txt, so the user can change the default cam any time without recompiling.
For someone who has compiled Android before, it would be easy to make this mod. Unfortunately, I don't have the resources to do it.
Any takers out there?

Can't you just use Fring?

James_Caliber said:
Can't you just use Fring?
Click to expand...
Click to collapse
If Fring works on 2.3, then I'd say it's one of a very few apps that are using the 2) method above. However, most other apps are still using the 1) method.
One of them is Adobe AIR 2.5.1, which my ReelPortal app depends on. So while waiting for Adobe to update it's AIR runtime to use the new 2) method, I figured it may be possible to change the underlying Android 2.3 to works with older software by modifying method 1).
You are probably wondering why don't I just abandon AIR. It'd be a lot of rework that I can't afford to do, and more importantly, AIR allows my software to run on multiple platforms. Currently my app runs on PCs, Android, and Blackberry Playbook (simulator). But I anticipate it to work on WebOS when that's out. And potentially iPhone/iPad as well if/when Adobe and Apple play nice w/ each other.

James_Caliber said:
Can't you just use Fring?
Click to expand...
Click to collapse
Haven't used Fring but Tango uses the front camera. And exceptionally well even on 3G.

reelportal said:
Android 2.3 provides 2 methods to open the camera (link):
1) open()
2) open(cameraId)
Method 2) is new to Android 2.3, but not many apps use it yet. Method 1) is provided in Android 2.2, which many video chats app uses. Unfortunately, it is hardcoded to access the rear camera:
public static Camera open() {
int numberOfCameras = getNumberOfCameras();
CameraInfo cameraInfo = new CameraInfo();
for (int i = 0; i < numberOfCameras; i++) {
getCameraInfo(i, cameraInfo);
if (cameraInfo.facing == CameraInfo.CAMERA_FACING_BACK) {
return new Camera(i);
}
}
return null;
}
I would like change this logic so that it read in the camera index from some file, e.g. defaultCamera.txt, so the user can change the default cam any time without recompiling.
For someone who has compiled Android before, it would be easy to make this mod. Unfortunately, I don't have the resources to do it.
Any takers out there?
Click to expand...
Click to collapse
This would probably be very easy to do. I'll take a look at it

im sure i can speak for everybody when i say we would rather use skype. the update needs to come quick.

charlieb620 said:
im sure i can speak for everybody when i say we would rather use skype. the update needs to come quick.
Click to expand...
Click to collapse
I wouldn't say "everybody", but I'd agree most people would use what they are used to. My software is designed to be more flexible for unconventional use.
For example, when both front and back cameras are fully supported by the underlying layers (AIR or Android), it would be possible to stream from both cameras simultaneously. So you can place the phone on a table for a video conference call, and the other side will see everyone at the front and back. I'm just thinking out loud here, as I hadn't actually done it with any phone yet.

charlieb620 said:
im sure i can speak for everybody when i say we would rather use skype. the update needs to come quick.
Click to expand...
Click to collapse
Thats not necessary man. reelportal is trying to develop an alternative that has other uses as well and telling him that others do it better is just rude.
reelportal said:
I wouldn't say "everybody", but I'd agree most people would use what they are used to. My software is designed to be more flexible for unconventional use.
For example, when both front and back cameras are fully supported by the underlying layers (AIR or Android), it would be possible to stream from both cameras simultaneously. So you can place the phone on a table for a video conference call, and the other side will see everyone at the front and back. I'm just thinking out loud here, as I hadn't actually done it with any phone yet.
Click to expand...
Click to collapse
Keep up the work man, some fools man not see the point in trying to do what hasn't been done but I appreciate your effort.

kenvan19 said:
Thats not necessary man. reelportal is trying to develop an alternative that has other uses as well and telling him that others do it better is just rude.
Keep up the work man, some fools man not see the point in trying to do what hasn't been done but I appreciate your effort.
Click to expand...
Click to collapse
Thanks for the support. Sometimes it's hard to get new ideas across to everyone. ReelPortal as it is right now is just a foundation for the stuff that I want to add on later, so there's a lot of work ahead for me.

I'm not saying what he is doing is irrelevant I'm talking about the availible video chat apps that our phone can use. I was not being rude. I'm speaking for people that would like to use other choices besides tango because android didn't develop much for our phones
Sent from my Nexus S using XDA App

I support you as well that's why I better clarified what I said. i would like to see this as well
Sent from my Nexus S using XDA App

charlieb620 said:
I'm not saying what he is doing is irrelevant I'm talking about the availible video chat apps that our phone can use. I was not being rude. I'm speaking for people that would like to use other choices besides tango because android didn't develop much for our phones
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
You came across as rude because the original post has nothing to do with other video chat apps. He was asking a programming question and you replied with 'use fring'
It's like if I asked about building an engine for a car I'm making and someone replies back 'take a bus'
-Nexus S

i THINK Qik now supports SNS video calls. The update says 'support for Dell Streak' but it doesnt crush on my SNS anymore....

Smilez_c said:
i THINK Qik now supports SNS video calls. The update says 'support for Dell Streak' but it doesnt crush on my SNS anymore....
Click to expand...
Click to collapse
I confirm this!

For the record, I just discovered Reelportal, and anyone who hasn't tried it simply doesn't understand how amazing it is or why we totally need this in addition to Skype video.
You can't compare it to Skype, its not the same thing at all. Skype is an account-based system where you log in and find users. This is more like an impromptu video chat room that supports up to 5 people simultaneously.
Skype does support multiple people (not sure if the new Skype 2.0 does for mobile yet), but only if you are willing to pay for it. Oovoo supports 3 people free, but you have to find people who are signed up for and installed Oovoo.
Here's the thing with Reelportal: IT RUNS IN A FREAKING BROWSER WINDOW!
That means you could tell everyone and anyone to join in your video chat from any computer (browser with flash required, that's it!), sort of like a video party line. You can keep your room private by putting a password on it as well, or even host your own server if you don't want to keep it publicly available.
I'm imagining the uses now- a group meeting with coworkers across the world, just tell them a time and what room name to log in and meet you. Or if I'm giving my 1 year old her first ice cream cone and want my whole family from multiple locations to log in and join us live.
I think this is totally brilliant and I'm beside myself at the short sightedness of folks who quickly dismissed this as just another Skype, Fring, Yahoo IM, Qik, etc. Those apps are all awesome, but this is something different.
Meanwhile, I'm not sure I understand the problem with accessing the front camera. I thought the new camera API was supposed to make this simpler for developers?
Is the problem that setting it for the front camera breaks support for older devices that rely on the old routine (G-tablet, etc)?
Why not offer two versions of the app- one for Gingerbread, and one for legacy?

Data Speed Fix (Linux Tweak)

Hello everyone,
I discovered a thread by marcusant a few months ago, and decided that I would share his fix with the Evo community. I take no credit for this work, and as always, you are responsible for your own actions. I am not responsible for any reboots, bootloops, bricks, or dead babies.
My personal use of this fix has shown some improvement in 3G speeds, while Wifi is unchanged. In the original thread, there are some successes and some failures.
marcusant said:
This is a known linux tweak and I have tested it on the epic and there seems to be mixed results. BTW, YMMV so don't go blaming me for messing up your phone... The zip is made for my rom but will most likely work on all others (even AOSP).
Open up /system/etc/sysctl.conf (make it if it isn't there)
Add the following...
Code:
net.ipv4.tcp_ecn=0
net.ipv4.route.flush = 1
net.ipv4.tcp_rfc1337 = 1
net.ipv4.ip_no_pmtu_disc = 0
net.ipv4.tcp_sack = 1
net.ipv4.tcp_fack = 1
net.ipv4.tcp_window_scaling = 1
net.ipv4.tcp_timestamps = 1
net.ipv4.tcp_rmem = 4096 39000 187000
net.ipv4.tcp_wmem = 4096 39000 187000
net.ipv4.tcp_mem = 187000 187000 187000
net.ipv4.tcp_no_metrics_save = 1
net.ipv4.tcp_moderate_rcvbuf = 1
Click to expand...
Click to collapse
Original Thread Here

FYI, My changes:
Ping: 771ms before, 1341 after
D/L : 124kbps before, 69kbps after
U/L : 292kbps before, 70 after
So it would appear that it did the exact opposite of what I was hoping for.

Austin Air said:
FYI, My changes:
Ping: 771ms before, 1341 after
D/L : 124kbps before, 69kbps after
U/L : 292kbps before, 70 after
So it would appear that it did the exact opposite of what I was hoping for.
Click to expand...
Click to collapse
Sorry to hear that. There are some instances of that happening in the original thread. Didn't read anything about fixes as I never had a problem.

Interesting, I understand this should work on most devices, my Evo is running ics right now. Think it'll work?
If so what are the risks if I have a good NAND backup right. Worth a shot to me, gonna try when I get some time
Sent from my CM9 OGevo using XDA

You need better directions.
Just go into the folder and make a new .txt file, paste over your info and save it as whatever.conf?
And if it doesn't work can we just delete it?
Sent from my PC36100 using Tapatalk 2

Crossrocker said:
You need better directions.
Just go into the folder and make a new .txt file, paste over your info and save it as whatever.conf?
And if it doesn't work can we just delete it?
Sent from my PC36100 using Tapatalk 2
Click to expand...
Click to collapse
Agreed, but he did post the original thread also. From my understanding, its a simple copy and paste to the text file, simply put it at the bottom.

[Bug Fix] Contacts Bug - Merry Christmas!

Hello all,
Looks like I have managed to fix this bug. Here is the code.
//android/packages/apps/Contacts/src/com/android/contacts/datepicker/DatePicker.java
if (months[0].startsWith("1")) {
for (int i = 0; i < months.length; i++) {
months = String.valueOf(i + 1);
}
//mMonthPicker.setMinValue(1); //-----------------------------------------------------------> setMinValue should be 0
mMonthPicker.setMinValue(0);
mMonthPicker.setMaxValue(12);
} else {
//mMonthPicker.setMinValue(1); //-----------------------------------------------------------> setMinValue should be 0
mMonthPicker.setMinValue(0);
mMonthPicker.setMaxValue(12);
mMonthPicker.setDisplayedValues(months);
}
mMonthPicker.setOnLongPressUpdateInterval(200);
mMonthPicker.setOnValueChangedListener(new OnValueChangeListener() {
@Override
public void onValueChange(NumberPicker picker, int oldVal, int newVal) {
/* We display the month 1-12 but store it 0-11 so always
* subtract by one to ensure our internal state is always 0-11
*/
//mMonth = newVal - 1; //----------------------------------------> Should be newVal
mMonth = newVal;
// Adjust max day of the month
adjustMaxDay();
notifyDateChanged();
updateDaySpinner();
}
});
You can test the apk attached
still not perfect, just an immediate solution so that you do not miss the Christmas!!!
-Adarsh

what is the problem ??i cant understand ..

leap_ahead said:
what is the problem ??i cant understand ..
Click to expand...
Click to collapse
December disappeared in JOP03C, 4.2

leap_ahead said:
what is the problem ??i cant understand ..
Click to expand...
Click to collapse
How's life under that rock of yours? ^^
J/k, it's a 4.2-bug. Google forgot December in contacts-app (when making an appointment), it's fine in calendar-app.

The Contacts app in 4.2 missed Dec when adding events related to a contact.
To me the problem looks like, Google guys changed the way to check the limits in the code. for example instead of using for(i=0;i<=length;++i),
they used for(i=0;i<length;++i). So one value was missed this time.
reason could be beyond this also.

december missed because google thinks it's the end of the world

mMonthPicker.setMinValue(0);
mMonthPicker.setMaxValue(12);
Click to expand...
Click to collapse
This doesn't seem to be a proper fix. Now the possible values are 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12 = 13 values.

Thanks.

FloHimself said:
This doesn't seem to be a proper fix. Now the possible values are 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12 = 13 values.
Click to expand...
Click to collapse
Commit from Cyanogenmod!
http://review.cyanogenmod.org/#/c/26856/
Sent from my Nexus S using Tapatalk 2

Articudos said:
Commit from Cyanogenmod!
http://review.cyanogenmod.org/#/c/26856/
Click to expand...
Click to collapse
Yes, the CyanogenMod version differs from this one.

adarshahd said:
The Contacts app in 4.2 missed Dec when adding events related to a contact.
To me the problem looks like, Google guys changed the way to check the limits in the code. for example instead of using for(i=0;i<=length;++i),
they used for(i=0;i<length;++i). So one value was missed this time.
reason could be beyond this also.
Click to expand...
Click to collapse
I think for(i=0;i<length;i++) its the right one. Dont forget that the "i" variabel is going to be the position, and it starts in 0 and goes to 11. 12 values, as it should be.
am i wrong?

Articudos said:
Commit from Cyanogenmod!
http://review.cyanogenmod.org/#/c/26856/
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
Solved in 4.2.1!!

CarrierIQ detected on AT&T and T-Mobile

AT&T:
T-Mobile:
Discuss.
Download the app on f droid:
https://f-droid.org/repository/brow...did=org.projectvoodoo.simplecarrieriqdetector
https://f-droid.org/repo/org.projectvoodoo.simplecarrieriqdetector_16.apk

catzilla said:
AT&T: https://i.imgur.com/HVe2ALY.png
T-Mobile: https://i.imgur.com/j0bmgOp.jpg
Discuss.
Click to expand...
Click to collapse
Maybe I'm misreading those reports? But it looks like the stuff that triggered it is lower down. All of what's displayed says "Not Found." Could you scroll down to the problematic bits and show them as well?

This comes as no surprise. Another reason why the end goal of any phone is to obtain root.

DaBunny said:
Maybe I'm misreading those reports? But it looks like the stuff that triggered it is lower down. All of what's displayed says "Not Found." Could you scroll down to the problematic bits and show them as well?
Click to expand...
Click to collapse
Full log:
Voodoo Carrier IQ Detector report:
Build fingerprint:
lge/p1_att_us/p1:5.1/LMY47D/151421018d413:user/release-keys
Carrier IQ has been found and is active
Detection score: 270
Test for: Linux kernel dmesg log
(DMESG, weight 100)
nothing found
Test for: Suspicious classes
(SUSPICIOUS_CLASSES, weight 0)
found: com.carrieriq.iqagent.service.receivers.BootCompletedReceiver
Test for: Android logcat debugging log
(LOGCAT, weight 100)
nothing found
Test for: Linux kernel interfaces
(KERNEL_INTERFACES, weight 50)
nothing found
Test for: Packages
(PACKAGES, weight 70)
nothing found
Test for: Running processes
(RUNNING_PROCESSES, weight 200)
found: system 4633 510 1626028 13308 ffffffff 00000000 S diagandroid.iqd
Test for: ROM configs
(ETC_CONFIG, weight 0)
nothing found
Test for: Linux kernel drivers
(KERNEL_DRIVERS, weight 50)
nothing found
Test for: ROM binaries and daemons
(SYSTEM_BINARIES, weight 70)
found: /system/lib/libiq_client.so
found: /system/lib/libiq_service.so
Test for: System services
(SERVICES, weight 70)
nothing found

Snakecharmed said:
This comes as no surprise. Another reason why the end goal of any phone is to obtain root.
Click to expand...
Click to collapse
2x on this, it should be no surprise that CIQ is on any carrier's standard phone build - especially T-Mobile. Correct me if I'm wrong, but I believe parts of CIQ are packaged in the My T-Mobile app, for the purpose of "diagnostics." That app even asks for permission to collect diagnostic data and send it back to the mothership.

BigJohn89 said:
2x on this, it should be no surprise that CIQ is on any carrier's standard phone build - especially T-Mobile. Correct me if I'm wrong, but I believe parts of CIQ are packaged in the My T-Mobile app, for the purpose of "diagnostics." That app even asks for permission to collect diagnostic data and send it back to the mothership.
Click to expand...
Click to collapse
It is for diagnostics. I'm in T-Mobile tech and its the most helpful thing ever.

you wanna talk scary.... my first G4 came with a buggy SD card slot, sometimes detected, sometimes not.... Anyway, I called T-mobile support and the tech I spoke with on the phone KNEW when my SD Card was inserted and when it was not. WTF is THATTTTT??!?!?!

Who cares about CarrierIQ now, NSA got you all even without carrierIQ. So what's the matter about removing it.......

FWIW, I checked my Verizon G4 with 3 different CIQ apps (Lookout, Bit Defender, Trend Micro) and it came up clean. I remember a few years ago that they said they wouldn't use CIQ, but I'm sure they have the same capabilities, under a different name.

So what exactly does CIQ do/why is it important to be aware of it? I have a VS986 and would like to know just how much data is being collected about me and what I do/where I go.

nineeightyone said:
So what exactly does CIQ do/why is it important to be aware of it? I have a VS986 and would like to know just how much data is being collected about me and what I do/where I go.
Click to expand...
Click to collapse
I'd like to know, too. I'm on T-Mobile, but why should I care? Other than paranoia that people have, how does it affect me?

Omg carrierIQ!!
Sent from my SM-G920T

Can't you just turn off diagnostics (on the H811 at least) and CI is disabled?