Were you able to detect the presence of CarrierIQ on your phone, or is your phone model somehow known to have CarrierIQ software installed?
People have looked in the FP1 for the software, but haven’t been able to find it (and there is root access, so it should be detectable and removable).
Also: Your post was duplicated, I’ve removed the oldest copy.
I haven’t found in this thread this information… someone tried to update to FP1 4.4 OS ? did it solve in this way?
The forum bug report has all the information:
https://forum.fairphone.com/t/fp1-gps-activates-itself-when-mobile-data-connection-is-active-or-i-make-a-call/25541?source_topic_id=25418Short answer: It happens on #kitkat too. (Someone should probably file an issue in the new bugtracker.)
Another small piece of information.
After all that, and also because of that, (gps auto activation in at) I changed
the mobile and I bought a Huawei.
I can confirm that 
in Austria the GPS does not activate by itself .
So, as 1+1=2, T-mobile and 3 AT in Austria illegally start the GPS
on mobiles with CARRIER IQ.
Until you can show that carrierIQ is actually present on your device, you’re actually claiming that 1+1=3.
Your observations are not surprising, given this is known to be an issue dependent on a combination of device and network. Changing either network or device will obviously solve the issue. So yes, the device is doing something that it shouldn’t in response to the network, but to then claim it must be carrierIQ is a very long stretch.
CarrierIQ is easily detectable, there’s a whole bunch of apps that can even automate that for you. On the Fairphone nobody has shown the presence of the software.
Could be an explanation of the issue:
https://community.vodafone.com.au/t5/Android/GPS-turned-on-by-3g-connecting/m-p/411918#M30888
Austria, not Australia! 
okay, as it is not in use, i will try now to dig in the old phone
It is not the same country, that much is true. But the poster in the other forum mentioned the symptom has occurred for the first time when the network operator started to change frequencies to expand LTE 4G services. Some phones with MediaTek SoC seem to be affected. If frequency changes due to roaming (e.g. by travelling), probably that symptom might occur as well…
@Johannes : if necessary i will investigate more.
but, for the moment, this is what i found in the mobile Star s9920/mediatek
that under 3 AT was automatically turining on the GPS :
unless someone knows that these were used in official android releases …
i let you guess the aftermaths …
i suggest people who own fairphones with gps problems to try the same
on a linux machine :
strings system.img
Fairphone 2 features a different (Qualcomm) SoC, and this problem is related to phones with a MediaTek SoC (Fairphone 1/1U).
But besides that, I strongly believe it has something to do with a fallback feature from Drei named “National Roaming” which offers 2G from their business partner T-Mobile for certain areas where Drei 3G services are not available yet. Some users reported GPS stays off after they disabled roaming to 2G completely. I would recommend to do the same and see if it helps…
To improve their network infrastructure, maybe Drei is using Carrier IQ to get “anonymized metrics data” (quote from Dan Rosenberg) which contains the respective GPS position information when phones switch from 3G to 2G and back again. That seems quite logical to me, after I read several articles how Carrier IQ is developed and meant to work:
BTW, if you experience Carrier IQ on your phone, that does not necessarily mean it was implemented by the manufacturer of the device.
Ok, here goes.
unzip FP1-Fairphone_OS_v1_8_7_Image_2015081400.zipsimg2sim system.img system.rawmkdir mntimg && mount -o loop system.raw ./mntimggrep -r carrieriq ./mntimg/This gets me two suspect files:
Binary file framework/framework.odex matches Binary file framework/telephony-common.odex matches
Seeing as context is everything, we get some of it using strings mntimg/framework/framework.odex | grep -A20 -B3 carrieriq (where I’ve limited output to similar values preceding it, and the 20 values following it):
x-3gpp2:lcs.ua x-3gpp:mbms.download.delivery.ua ``#``x-3gpp:mbms.service.announcement.ua x-carrieriq:avm.ctl x-cibenix:odp.ua x-essoy-application:push.erace x-hide-urls-from-log x-hutchison:ad.ua x-hutchison:al.ua x-hutchison:il.ua x-microsoft:drm.license x-microsoft:drm.meter x-microsoft:playready.drm ``#``x-microsoft:playready.drm.initiator x-motorola:browser.ua x-motorola:location.ua x-motorola:now.ua x-motorola:otaprov.ua x-motorola:splash.ua x-oma-application:bcast.ua x-oma-application:cpm:ua x-oma-application:dlota.ua x-oma-application:dpe.ua x-oma-application:java-ams
Which looks like a table of open mobile alliance push application IDs - judging by the list, carrieriq apparently registered an ID. Results for the other file are the same. I’d conclude that the system image contains two copies of the tables of push messsage types. As such, I don’t see it as an indication that carrieriq software is included in the system images.
Well , i came again to austria this weekend, and i brought my old mobile
to debug what was going on.
Surprise … it connected to T-Mobile and …
nothing happens. GPS is not activated at all.
Is this maybe the result of the eu no-roaming
rule from 15 june ?
Were you moving the phone for some kilometers while it was switched on?
It occurred for me again a couple of times in July while I was having a Danish Sim Card in my phone together with my Austrian. This time not constantly as it did when it first happened and I don’t think it has occurred since I took it out again.
Changed my operator, now I use “Coop voce” a virtual operator based on Telecom Italia Mobile.
GPS issue is gone.
Ha, it happens to me too now. I switched to Spusu, which operates in the Drei network, about half a year ago.
I’m having the same issue (GPS turning itself on automatically when I make a phone call) with a FP1 using the carrier UPC in Switzerland.
Turning off 3G “solves” the problem, but that’s obviously not really what I want…