Marvin W

Sorry for the string chaos, still thinking about a good way to merge repos, especially the ui-tools will be given a major rewrite to no longer contain translatable strings if...

The permission translations are part of Android, copying them over to microG is not a really good idea. If there is a typo in them, consider reporting it here: https://code.google.com/p/android/issues/list...

> I suppose those sentences should more likely be in the kind of “Touch here to grant %s permission(s)”, with %s being replaced by lower case category name. Unfortunately that...

You can try out most maps features (including the snapshot feature) in the maps api demo app: https://github.com/googlemaps/android-samples/releases/tag/v1.6.0

For using microG in Android Emulator, check https://github.com/microg/GmsCore/wiki/Development-Tools#using-the-emulator For debugging apps that use Maps API, you need to attach the debugger to the app using Maps, not com.google.android.gms.

Have you checked if granting contacts permission through system settings solves this issue?

Firebase Phone Auth is implemented as of c3bfb63f27c116d21ba7b2b87629e36573d4a59e. Google Auth is not yet available for Firebase Auth in microG.

Please don't put any bounties on bountysource. They failed to pay out for several months now. As of now, I haven't looked into what it takes to implement the U2F...

@devbrones @theanonymousexyz The reasons for microG to be Apache 2.0 are: - Most of open-source Android ecosystem (including AOSP itself) is Apache 2.0 licensed. Not mixing licenses makes life easier...

@DynaSpan There is no Bluetooth code in microG's Wear implementation yet, it's just able to connect to an emulator via adb. For Bluetooth functionality, One first need to record the...