Gmscore: Telegram 4.8.6, Google Play Services issue

[vladimirkosolapov]

After today's update of the Telegram (4.8.6), sometimes I began to receive a notification about the need to update Google Play Services. For version 4.8.5, this issue has been fixed in version 0.2.4-111-gf1cdb48, but now this again requires fix.

[ildar]

You may want to switch to FOSS "Телеграм"
https://f-droid.org/app/org.telegram.messenger
It doesn't need GCM at all

[vladimirkosolapov]

@ildar, at FOSS "Telegram" I didn't receive any service notifications with changes to application settings for bypassing blocks in Russia, so I switched to the original version.

[Torvin]

Relevant log line:
GooglePlayServicesUtil: Google Play services out of date. Requires 12451000 but found 12221403

@mar-v-in please patch

[Torvin]

I wonder if apps would complain if we set it to something like 9999xxxx...

[hbers]

If there was an option to set it manually within the gui this issue wouldn't come up every month or so. Any users out there who can come up with a solution for this it would be much appreciated.

[rob-3]

My current understanding is that the manual changing is impossible without xposed or the like.

I also believe that @mar-v-in doesn't want to set it to a really high number so that things don't break with no indication.

[ArchangeGabriel]

Yes, @mar-v-in already said that manual changing is not possible, and that setting an high number is not a good idea.

[Dr-Cool]

Has anybody ever tried to change an app version number using APK Icon Editor?

[bocekm]

@sudofail, I can see in the Telegram settings that you're able to set Proxy with which you may bypass the Russian ban. As a workaround, I'd suggest you to use VPN (e.g. https://nordvpn.com/blog/russia-wants-ban-telegram/) instead of Proxy, together with the FOSS Telegram version from F-droid.

[Dr-Cool]

Unfortunately the FOSS version uses too much battery compared to the GCM version. Waiting for a new microG, and meanwhile I have an Automate task killing Google's notification nag, since the GCM version seems to work fine except for the nag.

[maracuja-juice]

@Dr-Cool Can you share that task with me?

[Dr-Cool]

@maracuja-juice, I tried it myself after posting but unfortunately APK Icon Editor refuses to recompile the app once you change its version codes, it appears to only allow to make changes to simpler apps. Dead end.

[maracuja-juice]

@Dr-Cool I mean that Automate task you talked about.

[Dr-Cool]

Oh, thanks me for reminding me of that one, fortunately I still had a copy of that flow around, you can get it here: https://forum.fairphone.com/t/kill-update-google-play-services-notification-nag-flow-for-automate/40679

[maracuja-juice]

@Dr-Cool Thanks. I tried it out but it does nothing when I get such a notification.

[Dr-Cool]

You have to make sure that Automate has all the permissions that are necessary, there are quite a few including accessibility (it needs to read your screen to know that notification has been issued and to "touch" it).

[benwaffle]

same error with slack

[benwaffle]

isn't this fixed?

[chris42]

It should be fixed with the latest version from microg.org.
Of course it will reoccur with every google framework update