Google Connectivity Services updated 6/30/15

[anon(9072051)]

This morning Google Connectivity Services updated to version C.1.5.3 (1977963) via the Play Store. Now, while I like the sound of that name, I'd really like to know more about what this service brings to the party, especially for someone who is not on Project Fi, just a T-Mobile customer.

The PS blurb reads, "Google Connectivity Services helps Android handle network connections. Keep it updated to ensure your device has the latest networking capabilities, including support for connecting to Wi-Fi networks automatically and using a Google VPN to help secure your data."

Which, again, sounds great. But when you scroll down to the reviews area, you read things like this:

"T-Mobile Nexus 6 Just like everyone else has mentioned, something is wrong that causes data drops and slower WiFi."
"Update is bad for T-Mobile n6 The 3 people I know with nexus 6's on T-Mobile including myself have serious connectivity issues after update. " [Mind you, these are comments re. an earlier version.]

I'm also not thrilled by this inclusion in the service's list of permissions:

"prevent phone from sleeping"

Anyone know if this new update is meant to fix any specific problems with the service? Anyone have any Google Connectivity Services complaints?

Me, I'm sure I must've read about it at some point, but I truly had no idea what Google Connectivity Services was when I saw it in my list of updates.

 

[xikle]

I think it's used for Project Fi only, but i'm not sure.

As for issues after the update, I haven't had any since yesterday when I updated to the version you listed. For reference I'm on T-Mobile and I'm connected to Wi-Fi every day when I'm at work, and I haven't had any issues with it not connecting or not keeping the connection.

 

[dmlv]

^^^
Same...using w tmob no issues at all.

Posted via the Android Central App

 

[anon(9072051)]

Pretty much all of the articles dealing with Google Connectivity Services (GCS) that I've come across online are no more than brief announcements of its existence. They also seem to be rewrites of a Google press release or rewrites of some unacknowledged ur-post.

Even the devs on xda don't seem to be too sure about GCS, and they can really only admit to educated guesses about the extent of GCS's involvement with connectivity in general or its significance to Fi or non-Fi N6's.

The most developed discussion I've found about GCS generally is in this Android Police article from March, back when Project Fi was still known by the code name 'Nova':

Code In Android 5.1 App Reveals Connection Between Unannounced Google VPN Service And "Nova" Carrier Project

 

[masterxchief]

I've been having odd issues with my N6 on T-Mobile that may have started after the update. I'll lose signal and it won't come back until toggling airplane mode. Also doesn't like staying on LTE

 

[booboolala2000]

On Project Fi, have been having texting issues with Hangouts as usual. Seems to work then not. Signal has been 3g happy past two days as well. Using Project Fi N6. Seems like they are making tweaks here and there. For the most part it isn't an issue, but then every once in a while I won't have signal when I know I should have it. Power cycle does a better job than airplane mode for me.

Posted via the Android Central App

 

[anon(9072051)]

I have a surprisingly strong T-Mobile cell signal in my apartment. Evidently I must live within spitting distance of a cell tower because my cell signal at home is a constant 100%. The downside is that my cell signal is actually stronger than my in-home wifi-signal unless the phone is within, say, 3 feet of my router.

The "problem" is that the phone doesn't maintain a connection to T-Mobile Wifi Calling when I'm in my apartment; it obviously favors the strong cell connection, and keeps switching over to cell instead of maintaining the wifi connection, even though wifi never gets weaker than 75%. I can usually force it back to wifi by power cycling, but it'll still switch back to cell if the wifi signal weakens at all. The phone does not respect the "wifi calling preferred" option.

I've also noticed that Bluetooth interrupts the switch to wifi calling. I use bluetooth in the car, and if I don't shut it off on the way into my apartment, the phone will not switch to wifi calling until I shut off bluetooth.

If Google Connectivity Services is to blame for any of this because it is set to always prefer the strongest signal, then it would be nice if Google added tweakable settings to it in order to account for real-world variables.