Did you activate the SIM on google fi before trying to use it? And changed Auto Select Network to 'Off', with h2g2 as network? This is what I did (from post #36 of this thread) and it works for me (2018 ICTP) - shows 4G. My SIM was also a bit finicky - so maybe double check it is seated correctly as well?
Follow up on the Google Fi issue I was having (SIM Not Supported). I did order a new one from Google and installed it and it worked. Then I had to go through an incredibly painful process of setting the APN from the FreedomPop one I had installed to google's h2g2 one; which took many many MANY tries (over the course of a few days) to get the APN to actually update. Dang thing kept reverting back tot he FreedomPop one everytime the car was shut off.I'm having the same issue as crimanyfpace, getting a sim not supported message using a Project Fi data sim card and a nano to micro adapter with the not supported message preventing me from accessing the network settings.
Did it start working again? Sometimes it's either AT&T or even JLR and not your unit. Sometimes you have to wait it out for a bit and everything is good again. Just wondering how you made out?i have the same issue with my sim card this morning, trying to activate my connectivity it keep giving me that slashed G. it says reading sim card and then just go back to deactivating my connectivity. tried removing the sim card and putting back still same issue. any ideas what could be the problem. it used to work fine.
That sounds suspiciously like the ancient bad telematics unit issue.Reviving this thread.
I’m having some telematics connectivity issues since the 18C update. Getting the G with a slash. Seems that I have good connectivity when I first start the car. If I run into an ATT dead spot I get the G with a slash (as expected). But when I drive back to an area with solid connectivity, the Telematics unit never locks onto the signal. ICTP says reading SIM. If I toggle the ATT connectivity off and on using the settings menu in ICTP the telematics then locks on to the new signal (restart works as well). Had this issue in one of the early 17 updates but seemed to have been cured in the 17C or 18B update.
Anyone having similar issues?