NoGoolag

All issues that have [$] in the title have the price already paid to Bountysource, not just promised.
Bountysource is the site where you pay the bounty, and when someone fix/implement the issue then the site will pay him/her.

https://github.com/microg/android_packages_apps_GmsCore/issues?q=label%3Abounty

https://www.bountysource.com/teams/microg/issues

microG also accepts donations via Liberapay:
https://liberapay.com/microG

https://microg.org

https://github.com/microg

Issues
https://github.com/microg/android_packages_apps_GmsCore/issues

Pull requests
https://github.com/microg/android_packages_apps_GmsCore/pulls

#bounty #donate

GitHub

microg/android_packages_apps_GmsCore

Free implementation of Play Services. Contribute to microg/android_packages_apps_GmsCore development by creating an account on GitHub.

3.9K viewsedited 14:37

NoGoolag

Firebase support bounty

This is a bounty to promote development interest and find a solution to the many apps that fail because of the migration from GCM (Google Cloud Messaging) to FCM (Firebase Cloud Messaging)

https://www.bountysource.com/issues/51518216-gcm-fcm-update-needed-for-push-messaging

Follow the conversation in the latest pages of MicroG XDA thread and on GitHub:

https://forum.xda-developers.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616

https://github.com/microg

The Deprecation of GCM for FCM
by @ Shadow53
https://shadow53.com/post/whats-new-pussycat/#the-deprecation-of-gcm-for-fcm

"Users of MicroG on Android Oreo will notice that their apps using Google for notifications are no longer receiving them. This is because of Google pushing Firebase Cloud Messaging (FCM) as a replacement for Google Cloud Messaging (GCM) for notifications. MicroG currently only has support for the older GCM protocol, so apps using the newer FCM cannot register for notifications.

Some people have found that installing older versions of the app will cause it to register via GCM, then an update will continue using GCM. The problem of lacking support for FCM still remains.

A solution to this problem is to just not use apps that require Play Services at all, and request that developers of apps you use requiring Play Services implement an alternate method of pushing notifications.

This doesn’t work if you need a certain app that still requires Play Services, and certainly won’t work if trying to convince someone to switch to using MicroG. So, we need to get FCM implemented. Open Source enthusiasts will suggest that I do it if I think it needs to be done - I would, and I may in the future, but not any time soon. I have too many projects already that need to be worked on. So here’s hoping someone else is able to get something working…"

#bounty #firebase #fcm

Bountysource

A $623 Bounty has been paid out for microg/GmsCore

GCM -> FCM Update needed for push messaging [$623 PAID] [$623 awarded]

2.2K viewsedited 13:37

NoGoolag

https://www.bountysource.com/issues/51518216-gcm-fcm-update-needed-for-push-messaging

chris42:
Just to help a few people trying to figure out if push messaging is working or not, please check the following:

✅ you are using newest microg version 0.2.5-12879 running (ale5000 installer is updated and should be very helpful)
✅ you deactivated battery optimization for microg
✅ you activated google device registration
✅ you get all the green checkmarks in microg diagnostics
✅ you made sure nothing is blocking network traffic to mtalk.google.com (e.g. afwall, adaway, ...)
✅ you deleted the app you have troubles with and installed it fresh after updating to microg 0.2.5-12879
✅ you have not used backup solutions, like oandbackup, titaniumbackup, ... to restore app data
✅ you can also use the push notification tester to check. I just tried it and it works.

To verify incoming messages, look in you logs and search for "GmsGcmMcsInput". You should see the heartbeat and Incoming messages. In the incoming messages there should be a category stating your apps package. This should be messages your receive via push. (@mar-v-in I hope this is correct?!)

#firebase #fcm #bounty

Bountysource

A $623 Bounty has been paid out for microg/GmsCore

GCM -> FCM Update needed for push messaging [$623 PAID] [$623 awarded]

2.2K viewsedited 13:37

NoGoolag

microG developer will be back in 1-2 weeks https://gist.github.com/mar-v-in/c8254168c63361c5094de13a7afea344 Hello everyone, As many of you have noticed there had been very little involvement of me with microG over the last months. tl;dr: I'll be back…