If that’s all then I would say no. But keep in mind that it is tricky to block these system components without breaking things.
The Google Play Services at least need access to the local google account and other information like the device id and the GFS id (google services framework id). And internet access of course but that’s obvious.
To check the status for GCM you can open the dialer and type:
*#*#426#*#*
(this opens the google play services monitor)
If GCM is working it will say that the device is connected to mtalk.google.com:5228
If it says “disabled” than you do not have the latest google play services installed. Google normally does update these without user notification in the background. The current version is: 7.3.29
The old way to check for GCM was:
*#*#8255#*#*
(The old Gtalk monitor, which got replaced by the google play services monitor since version 7.0.99)
You could try to start the GCM service by hand. Connect to your phone via adb or open a terminal session with Terminal Emulator and type:
su
am startservice -n com.google.android.gsf/.gtalkservice.service.GTalkService
Another important thing (although this has nothing to do with your problem): after re-installing the gapps (i.e. after an upgrade of the fairphone os) the GFS ID may gets replaced by a new one. This results in messages and notifications for applications making use of GCM like TextSecure, Threma, Telegram etc. being routed to the old GFS ID and so will never reach your device. To circumvent this there are two options:
-
Re-register in TextSecure etc. so theses services get the new GFS ID
-
Make a backup with TitaniumBackup of GoogleServicesFramework and restore this backup (it is a data only backup) after re-installing gapps.
(This is my favourite solution since it is much more comfortable than re-registering every service that uses GCM and it works great).