I found I had to restore the CarrierIQ files in order to take an OTA update. To make it easier, I threw these together in order to enable and disable CarrierIQ easily...
It needs to run as root in a shell on the phone. The mount command makes the system partition writable. You should reboot after this for the changes to take effect (and for the system partition to go back to read only).
I take no responsibility. If you don't know what you are doing, don't use these.
# Disable CarrierIQ mount -o rw,remount -t ext4 /dev/block/mmcblk0p45 /system chmod 000 /system/app/HtcLogLevel.apk chmod 000 /system/app/HtcLogLevel.odex chmod 000 /system/app/HtcResetNotify.apk chmod 000 /system/app/HtcResetNotify.odex chmod 000 /system/app/QXDM2SD.apk chmod 000 /system/app/QXDM2SD.odex chmod 000 /system/app/Smith.apk chmod 000 /system/app/Smith.odex chmod 000 /system/app/UDove.apk chmod 000 /system/app/UDove.odex chmod 000 /system/priv-app/IQ-tmobile-release-unsigned.signed.apk chmod 000 /system/priv-app/IQ-tmobile-release-unsigned.signed.odex chmod 000 /system/priv-app/IQToggle_v1.1.3.signed.apk chmod 000 /system/priv-app/IQToggle_v1.1.3.signed.odex chmod 000 /system/priv-app/MyBreeze.apk chmod 000 /system/priv-app/MyBreeze.odex chmod 000 /system/lib/libiq_service_tmobile_2.2.so chmod 000 /data/data/com.carrieriq.tmobile chmod 000 /data/data/com.carrieriq.tmobile.IQToggle
# Enable CarrierIQ mount -o rw,remount -t ext4 /dev/block/mmcblk0p45 /system chmod 644 /system/app/HtcLogLevel.apk chmod 644 /system/app/HtcLogLevel.odex chmod 644 /system/app/HtcResetNotify.apk chmod 644 /system/app/HtcResetNotify.odex chmod 644 /system/app/QXDM2SD.apk chmod 644 /system/app/QXDM2SD.odex chmod 644 /system/app/Smith.apk chmod 644 /system/app/Smith.odex chmod 644 /system/app/UDove.apk chmod 644 /system/app/UDove.odex chmod 644 /system/priv-app/IQ-tmobile-release-unsigned.signed.apk chmod 644 /system/priv-app/IQ-tmobile-release-unsigned.signed.odex chmod 644 /system/priv-app/IQToggle_v1.1.3.signed.apk chmod 644 /system/priv-app/IQToggle_v1.1.3.signed.odex chmod 644 /system/priv-app/MyBreeze.apk chmod 644 /system/priv-app/MyBreeze.odex chmod 644 /system/lib/libiq_service_tmobile_2.2.so chmod 644 /data/data/com.carrieriq.tmobile chmod 644 /data/data/com.carrieriq.tmobile.IQToggle
Does anyone have the lowdown on lollipop carrier iq? It's clearly there, judging by the message I got on "device health" after the lollipop OTA update. However, I don't see anything with carrier iq in the name. The ciq thing that was in the Kit Kat /system/lib is gone. There's something called smithlib in there now. Not sure if that was in Kit Kat. I don't see the MyBreeze thing in lollipop, at least not where it was in Kit Kat.
I did the RUU and got no notification about Carrier IQ when setting up my device. Further more, the ciq & ciq toggle apks are no longer found in /app or /priv-app. Also the option in the settings menu to turn it on or off is gone as well. Frankly Carrier IQ is no longer on this device.
Now, Smith is not tmobile Carrier IQ. That is HTC logging and has been on several devices. As well as udove and some Qualcomm loggers, all of which can be removed and or frozen safely.
The T-Mobile One M8 has CarrierIQ.
To remove it you need to be S-off or have a writable booted system. If you haven't made your system writable you can use TWRP's file manager to delete the files.
This also removes HTC logging apps too.
Use a file Manager like Solid Explorer or Root Explorer and go to and delete the following (Make a backup of all if you want to OTA later):
You can use an app like https://play.google.com/store/apps/d...rieriqdetector to check if CarrierIQ is gone (You can use it to check that it's there also).
I don't have to believe I've looked at the system and I can guarantee you they are NOT using Carrier IQ. The question was is there Carrier IQ in the ROM and the answer definitively is NO. There is no form of Carrier IQ present.
Also they are required to gain your consent for utilizing mechanisms like Carrier IQ due to the data they gather. This is why you used to get the authorization confirmation upon setting your device up the first time. You no longer get that confirmation because they are no longer logging the same activity.
Furthermore T Mobile doesn't need Carrier IQ on your device. They have backend software on their network to track all your messages, all your phone calls, all your app usage, as well as your device performance so you really shouldn't trip. By the way you consented to that when you agree to T Mobile's Terms of Service
Carrier aggregation and device/network optimization through apps like Smith, udove and Qualcomm loggers, on the other hand, do happen and have always happened. This is nothing like Carrier IQ though and should not be confused with it. They are not the same beast. Now, I'm not here to convince you what you should do or believe, nor do I have any interest to.
|Thread Tools||Search this Thread|