You must have seen Google Play Services on your Android device. This app has been sitting on our Android devices since the times of Android KitKat. All thought it doesn’t show up within the app drawer.So lets discuss about Google Play Services!
What is Google Play Services?
In simple terms, google play services is an app which contains sets of background sevices and APIs (Application Program Interface, which helps applications to interact/communicate with other applications) , APIs assist programmers and supply dependencies to other apps.. Many apps require an updated version of google play services so as to run..
Actually Google Play Services has system level access to android OS to supply internal features and security measures to other applications..It also consumes much ram,cpu and battery..
Can We Disable It
Yeah we will disable it and even uninstall with some procedure but a number of applications won’t run without it, many apps on play store believe these services,almost all google apps (google maps,gmail,google assistant etc) wouldn’t work..
But if you would like to urge obviate google thanks to privacy concerns as your every activity/history/location and your whole device is under google control
Then hopefully because of some custom ROMs like lineage OS and microG project , we will use our android fully without google play services and google apps..
Lineage OS is already equipped with microG serices and api.. but you’ll also install those manually..
What is MicroG Project?
microG GmsCore may be a free and open implementation of the Google Play Services Framework. It allows applications calling proprietary Google APIs to run on AOSP-based ROMs like Replicant and LineageOS. Acting as a replacement for the closed-source Google Apps (GAPPS), it’s a strong tool to reclaim your privacy while enjoying Android core features.
- its easy on battery,memory and CPU
- no bloatware
- online/offline location services
- get rid your device from google’s control
- its free and open source (Apache 2.0 licensed )
Your Android system must support #signature_spoofing so GmsCore can pretend the existence of the official Play Services to applications calling Google APIs.
Play Services are very expensive in terms of resources, they drain many battery and that they use many space, while its super cool alternative #microG requires much less resources.
To give you a thought , the littlest possible package of OpenGApps (“Pico Package”) on ARM 7.1 is ~125 MB, while the complete microG suite (GmsCore, GsfProxy, FakeStore, Mozilla Nlp Backend and NominatimNlpBackend) is ~4 MB
But to use all the neat features from the microG project, which allows you to use all features of your Android smartphone without those shitty, proprietary battery-consuming Google blobs, your system is required to support signature spoofing. Currently only a few custom ROMs have built-in support for this feature, luckily you’ll use Xposed or a patching tool to feature the feature to the systems that don’t have it.
In simple, MicroG requires a patch called “signature spoofing”, which allows the microG’s apps to spoof themselves as Google Apps.
On Android, all applications are signed (usually using SHA1 with RSA). The certificate/key-combinations wont to sign apps are self-signed. this suggests there’s no PKI / certificate authority to verify a key to be owned by a person/company/entity.
Signature spoofing allows applications to behave like being signed by a 3rd party. this suggests that whenever one application asks the OS for the certificate wont to sign an installed package which package uses signature spoofing, rather than the certificate attached to the app, a spoofed certificate is returned.
So why does microG require signature spoofing?
Only only a few app developers use direct access to certificate, you would possibly wonder why microG needs it surely features. Well the very fact is that although most developers don’t even now about it, their apps actually do direct certificate access. this is often thanks to how Google Play Services works
Applications that use Google Play Services use the Play Services client library. This library is directly embedded into the appliance , is deliver as a part of it and eventually runs within the security context of that app. And this library actually uses direct certificate access to make sure that the Play Services app installed on the device is signed by a selected private key. Got it? No? Read this para again!
How to get signature spoofing?
- 1- If you’ve got the Xposed Framework installed, the subsequent module will enable signature spoofing: FakeGApps by thermatk
- 2-Flash your device with any of following Custom ROM
- I- Carbon ROM
- II- Omni ROM 5/6/7
- III-Marsh ROM
- IV- crDroid
- V- AospExtended
- VI- Lineage OS
- 3-You also can patch your already-install ROM by flashing NanoDroid-patcher, with none computer interaction. it’ll auto-patch every updated ROM. you’ll flash its zip enter your ROM
- note: you ought to have android 4.4 or newer
- 4-Finally, if you’ve got Root, but aren’t using Xposed
- you’ll try patching your already-installed ROM using Needle by moosd (or its fork Tingle by ale5000) or Haystack by Lanchon (Haystack can optionally add an easy UI to regulate spoofing almost like the one offered by OmniROM).
Well, things i discussed aren’t for noobs and that i haven’t shared steps to install these patches in android using pc or without pc, you would possibly hard brick or soft brick your device during steps if you probably did something wrong.. there are problems too in hardware compatibility etc.. so don’t do anything if you do not know what are you doing.. but i will be able to say “try if you’ve got spare android for experiments”
I will attempt to clarify these methods for noobs… maybe in some article or video
note: while flashing custom rom must check hardware wants for device before flashing your device with any custom OS