profile
viewpoint

mar-v-in/ArtHook 369

Library for hooking on ART

mar-v-in/BlankStore 106

An open source Google Play Store client.

mar-v-in/MapsAPI 40

A replacement of the often used google maps api with an open source one using OpenStreetMap.

mar-v-in/NoAnalytics 25

Clone of GoogleAnalytics for Android

dino/libomemo-c 3

Fork of libsignal-protocol-c adding support for OMEMO XEP-0384 0.5.0+

mar-v-in/minidns 3

Minimal DNS library for android

mar-v-in/nimiq-native-cpu-miner 3

A native (C++) cpu miner for Nimiq, using getwork or getblocktemplate RPC commands.

mar-v-in/MobAdMob 2

Clone of AdMob that shows nothing - use as replacement in open source apps to make them free

issue commentmicrog/android_packages_apps_GmsCore

Tier App not working (FirebaseAuth)

So you are not even reaching the point where you have to enter your phone number, which means Firebase Auth isn't the culprit here.

Have you checked if there is anything logged in logcat? Are you using any kind of firewall?

Romern

comment created time in 4 days

issue commentmicrog/android_packages_apps_GmsCore

Tier App not working (FirebaseAuth)

@unixfox have you granted the permisson to draw over other apps? Do you see a loading screen being displayed (and potentially recaptcha) when logging into Tier?

Romern

comment created time in 4 days

issue commentmicrog/android_packages_apps_GmsCore

App crash with new mapbox

@fareszr I guess your issue is totally unrelated to the one by @ildar. Can you please open a new issue and provide a logcat as otherwise it's impossible to find what the issue is.

ildar

comment created time in 4 days

issue commentdino/dino

`error: The name `set_advertised_protocols' does not exist in the context of `GLib.TlsConnection?'`

The corresponding method was added to GLib 2.60 and vapi repository 0.43.4 (via commit GNOME/vala@dd53026534a7cd8d7b049a1b09266684b6a47d2e). Before trying to build with ALPN support, we check that you have at least GLib 2.60. The first GNOME core distribution to include GLib 2.60 is 3.31.92 which also included vapi repository 0.43.92, thus every GNOME core distribution including GLib 2.60 also should be using a vapi repository that is new enough to include ALPN support. Unfortunately there is no easy way to detect the version of the vapi file at build time, so we must rely on distributions to properly follow the GNOME core distribution. What distribution are you using?

Given that most distributions put the vapi repository and vala compiler in the same package or make vala compiler depend on the vapi repository of the same version, we could add a check vor a vala compiler version > 0.43.4 before enabling ALPN so that others don't face the same issue. This would mean people with systems not following GNOME core distribution would end up without ALPN support even when their system would actually support it. But I guess that's probably the best we can do for people using such distributions :shrug:

paulmenzel

comment created time in 5 days

PR closed microg/android_packages_apps_GmsCore

Çekme

Çek

+1770 -56577

5 comments

1306 changed files

alperates112

pr closed time in 5 days

issue commentmicrog/android_packages_apps_GmsCore

Hessenschau-App is crashing with latest release

@tobiasKaminsky

  • Not every exception logged actually leads to a crash. For example, you can freely ignore all those Bundle: Attempt to cast generated internal exception. The exception that leads to the crash is always marked as FATAL EXCEPTION.
  • Returning any version > 0 in dynamite loader can cause apps to try loading code from microG package and if the corresponding code is not there, they're more likely to crash then if the version was set to 0. Thus changing the version alone most likely won't improve anything.

To solve this issue, one has to find out what is the reason for GoogleApiHandler to throw this IllegalStateException: A fatal developer error has occurred. Check the logs for further information.. The error message itself is not helpful at all in debugging, but there probably is a good reason for it to be thrown.

john-bill

comment created time in 6 days

issue commentmicrog/android_packages_apps_GmsCore

Corona Warn App is unable to find EXPOSURE_NOTIFICATION_API

Yes, the nanodroid-patcher package can do this, for details check https://gitlab.com/Nanolx/NanoDroid/-/blob/master/doc/microGsetup.md

ClundXIII

comment created time in 6 days

issue commentmicrog/android_packages_apps_GmsCore

Corona Warn App is unable to find EXPOSURE_NOTIFICATION_API

@ClundXIII Alright. Yes, it's definitely the missing signature spoofing causing trouble here. SERVICE_INVALID is the play service client library indicating that the play services (and/or play store) installed is considered "invalid" because the signature does not match due to missing signature spoofing.

ClundXIII

comment created time in 6 days

issue commentmicrog/android_packages_apps_GmsCore

Corona Warn App is unable to find EXPOSURE_NOTIFICATION_API

@ClundXIII

Specifically for CWA? Because that is so far the only app where I had Problems with.

Most features in microG require signature spoofing. Only a few apps can make use of push notifications and most apps will get network location without signature spoofing. But that's basically it.

So the solution is to get a custom ROM?

There are multiple ways to patch existing ROMs for compatibility with microG. Easiest way probably is to use Nanodroid patcher.

ClundXIII

comment created time in 7 days

issue closedmicrog/android_packages_apps_GmsCore

Custom Maps implementations?

Is it possible for ride share apps, etc. to be able to use Open Street Map instead of Google?

closed time in 7 days

Riamse

push eventmicrog/.github

Marvin W

commit sha 4b97cbcd0c21675741fe921612950e336e4106d8

Update issue templates

view details

push time in 7 days

push eventmicrog/.github

Marvin W

commit sha dfa60954e16e7a1c323fe9be3f53ac8d503d774e

Update issue templates

view details

push time in 7 days

push eventmicrog/.github

Marvin W

commit sha 6a27d3c883c5c1e00ae039ff4221d2938d8e5ad3

Update issue templates

view details

push time in 7 days

push eventmicrog/.github

Marvin W

commit sha 87670cf473bb88a0127325f88680251cb938c956

Rename bug_report.md to bug-report.md

view details

push time in 7 days

push eventmicrog/.github

Marvin W

commit sha 00491d8b72fea2b623186b15db905e08cd6b67b6

Update bug_report.md

view details

push time in 7 days

push eventmicrog/.github

Marvin W

commit sha ae3ffe9ff36afe5e7f78b77bc563e96392a81841

Update app-misbehaving.md

view details

push time in 7 days

push eventmicrog/.github

Marvin W

commit sha 5c5542f3cddd0fa0ef17e9f1aa78d4de33873f96

Update app-misbehaving.md

view details

push time in 7 days

push eventmicrog/.github

Marvin W

commit sha 34b7b3a335092cd2a21aa74c3942cd673a24064d

Update bug_report.md

view details

push time in 7 days

push eventmicrog/.github

Marvin W

commit sha c44bdb6bae4a5d9f8b12812d58114dce0db73bec

Update app-misbehaving.md

view details

push time in 7 days

push eventmicrog/.github

Marvin W

commit sha 84f0d84777dbc00b374ed601758c522d2bd90546

Update app-misbehaving.md

view details

push time in 7 days

push eventmicrog/.github

Marvin W

commit sha 38a667e03c28a593ee9466306fa2cad83474795b

Update issue templates

view details

push time in 7 days

push eventmicrog/.github

Marvin W

commit sha c46184077f014b4a8496de750c0ac5485e4db32a

Update issue templates

view details

push time in 7 days

push eventmicrog/.github

Marvin W

commit sha ec7b03e78191e0c37116aafa1b41badf41d6211b

Update bug_report.md

view details

push time in 7 days

push eventmicrog/.github

Marvin W

commit sha 31fa14348d24a519ab3c85aa0e4930bfb72f85af

Rename ISSUE_TEMPLATE/bug_report.md to .github/ISSUE_TEMPLATE/bug_report.md

view details

push time in 7 days

push eventmicrog/.github

Marvin W

commit sha 605884afabfa9ec4ea3743848235d5cd4f2aaec2

Create bug_report.md

view details

push time in 7 days

issue commentmicrog/android_packages_apps_GmsCore

Corona Warn App is unable to find EXPOSURE_NOTIFICATION_API

except the 3 on top about signature spoofing/checking.

Well, they are required for microG to work.

I was wondering if I could still broadcast with just heavy battery usage

No, BTLE and normal Bluetooth are largely different protocols that are not compatible with each other.

ClundXIII

comment created time in 7 days

issue commentmicrog/android_packages_apps_GmsCore

Corona Warn App is unable to find EXPOSURE_NOTIFICATION_API

@ClundXIII Did you check that everything is fine according to microG Self-Check?

Fairphone 2 does not support BTLE Advertisements. This means you can't broadcast IDs to nearby devices or let others know that you've been diagnosed positively. However you can still use CWA to get notified if you've been in close contact with a positively diagnosed person.

ClundXIII

comment created time in 7 days

issue commentmicrog/android_packages_apps_GmsCore

NHS England Exposure Notifications not registering

Are you using latest microG version 0.2.13? Did you check if everything is fine according to microG Self-Check?

Cadair

comment created time in 7 days

issue commentmicrog/UnifiedNlp

Local development workflow with GmsCore

I'm not sure why you see this error.

The easiest way during development for me was to publish the UnifiedNlp to my local maven repository (./gradlew publishReleasePublicationToMavenLocal) and then adjust ext.nlpVersion and add mavenLocal() to subproject repositories in GmsCore's build.gradle.

chirayudesai

comment created time in 10 days

issue commentmicrog/android_packages_apps_GmsCore

Checkin service does not start on boot

Have you tried with latest release? It already has code to try a checkin before gcm registration

goffioul

comment created time in 10 days

issue commentmicrog/android_packages_apps_GmsCore

Not requested verification code SMS

I'd say this could be a coincidence. The Lidl app is among the most installed in German market these days, thus probably having a lot of new registrations. And if anyone of them does a mistake when entering their phone number, it might cause this.

xcablex

comment created time in 11 days

issue closedmicrog/android_packages_apps_GmsCore

Empty currently broadcasted ID

In exposure notifications the field "Currently broadcasted ID" is empty. Two days ago I could see the the ID there.

Any ideas what the problem could be? I am wondering if there actually is an ID so the exposure notifications is propperly working.

Thanks a lot for your effort.

closed time in 11 days

donpatrice

issue closedmicrog/android_packages_apps_GmsCore

Corona Warn-App 1.5.0.47: "Google Play-Dienste aktualisieren"

Die Corona Warn-App in der Version 1.5.0.47 ist mit microG Services Core 0.2.12.203315 nicht mehr zufrieden. Beim ersten Start der App kommt die Meldung:

Google Play-Dienste aktualisieren
Corona-Warn wird nur ausgeführt, wenn du die Google Play-Dienste aktualisierst

Ich betone übrigens, dass ich niemanden im RKI, bei SAP oder der Telekom persönlich kenne. Woher die sich die Freiheit nehmen, mich zu duzen, ist mir schleierhaft. Mir kommt bei diesen dreisten Vertraulichkeiten jedenfalls immer die Assoziation an die Nazis, die auch schon geschrieben haben "Kaufe nicht bei Juden".

Screenshot_20201019-192945_Corona-Warn

closed time in 12 days

hubbty

issue commentmicrog/android_packages_apps_GmsCore

Empty currently broadcasted ID

Early test versions with EN support generated new broadcasting keys without any need. These keys would be used to generate and display IDs for the rest of the day, so this might be why it showed up for you. Since a016feba35c05ce482b67e01b51b93ef1d39ef70 we only generate keys when they're used for broadcasting IDs.

You don't need to generate or broadcast IDs for matching or exposure risk computation, so you can still use the system to get informed about exposures, but you won't be able notify others in case of a positive diagnosis.

donpatrice

comment created time in 12 days

issue commentmicrog/android_packages_apps_GmsCore

Empty currently broadcasted ID

What device are you using? Some devices are not fully BLE compliant and thus do not support broadcasting IDs. I know that this issue affects the Fairphone 2 or at least some version of it.

donpatrice

comment created time in 12 days

issue commentmicrog/android_packages_apps_GmsCore

Empty currently broadcasted ID

If no currently broadcasted ID is listed, you are most likely not broadcasting. Maybe you accidentally disabled bluetooth? Only scanning and matching have any significant impact on the database size. For scanning, you can easily see if it's working in the "Collected IDs" section.

donpatrice

comment created time in 12 days

issue commentmicrog/android_packages_apps_GmsCore

Empty currently broadcasted ID

If you just installed the microG update 0.2.13, it might be that the database upgrade is still in process in the background and the UI is waiting for this to complete. Do you still see this issue?

donpatrice

comment created time in 12 days

issue closedmicrog/android_packages_apps_GmsCore

Corona Warn App requires an Play Service Update on latest microG

With the new app version of the German Corona-Warn-App released today (1.5.0.47), it wants an update of the Google Play services and refuses to run otherwise.

Update: I was sucessfully able to enable exposure notification (but the warning persists) by entering the app and clickin on enable and immediatly leave (so microG at least continues to collect ids), but it sometimes disables itself. There are also sometimes communication errors, similar to #1171 (did not happen on older versions).

Software versions: Lineage 17.1-20201016-microG-river microG Services Core 0.2.12.203315

closed time in 12 days

Varbin

issue commentmicrog/android_packages_apps_GmsCore

Corona Warn App requires an Play Service Update on latest microG

Works again with v0.2.13.203915

Varbin

comment created time in 12 days

release microg/FakeStore

v0.1.0

released time in 12 days

created tagmicrog/FakeStore

tagv0.1.0

Mocks the existence of the Google Play Store

created time in 12 days

created tagmicrog/android_packages_apps_GmsCore

tagv0.2.13.203915

Free implementation of Play Services

created time in 12 days

push eventmicrog/android_packages_apps_GmsCore

Marvin W

commit sha a95f6449f58a61f1ffa3ef04401c3ad2c0d27578

GCM: Fix apps not always whitelisted from powersave Fixes #1188

view details

Marvin W

commit sha 93636a704da3aae5ba96635ad8482838902aedc8

GCM: Fix accidentally not allowing regitration for some apps

view details

Marvin W

commit sha 14dfd3e794310af9e90379aabde0afe2abfe057a

Mapbox: Ensure we have the required class loader in place when converting types

view details

push time in 12 days

issue closedmicrog/android_packages_apps_GmsCore

GCM: Temporary Whitelist currently does not seem to work

Some time ago, GMS Core gained the ability to put an app into the temporary whitelist when a push notification arrived (see the corresponding feature request).

This does not seem to work anymore after upgrading to v0.2.12.203315.

I have some older logcats when it still worked.

Old behavior when a push notification arrived:

  • Logcat with message GmsGcmMcsSvc: Adding app <package name> for userId 0 to the temp whitelist
  • Command adb shell dumpsys deviceidle tempwhitelist displayed package in the temporary whitelist shortly after arrival of the push notification

Current behavior:

  • Neither seems to happen

Note that I artificially put my smartphone into doze by adb shell dumpsys deviceidle force-idle as described in the Google Documentation. Moreover, microg has the correct permissions: I have put the corresponding file into /system/etc/permissions as described here.

closed time in 12 days

Tentos

issue commentmicrog/android_packages_apps_GmsCore

exposure.db takes up huge amounts of space

@jplitza

CWA took endlessly to update the keys

This is expected behavior after the update as the key matching cache is lost in the process. For subsequent checks that happen once a day, only the newly published diagnosis keys have to be checked and not a full 14 day history, thus it should be about 14 times faster ;) This doesn't happen for completely new installations, as key matching is near instant when you don't have any IDs collected yet.

RalfJung

comment created time in 13 days

issue closedmicrog/android_packages_apps_GmsCore

confirm new apps not working

Hello,

When I tried to use "confirm new apps option", the apps can't register themself, this is logical. But no confirmation request is displayed, or the applications list don't populate, I don't know how this is supposed to work.

Best regards.

closed time in 13 days

charles-martel55

issue commentmicrog/android_packages_apps_GmsCore

confirm new apps not working

This should be fixed as of 26f2e859b8d424f20f42f3c2ec3736817f39b6e2

charles-martel55

comment created time in 13 days

issue closedmicrog/android_packages_apps_GmsCore

Unable to start activity ComponentInfo{com.google.android.gms/org.microg.gms.ui.AskPushPermission

OS: Android 9 What is supposed to happen: Start Sprint IP relay app>White screen>Logo appears>Login screen>Logged in

(Behavior changes after Sprint IP relay app version 60.30.5. The newer versions crash with a okhttp error.)

Sprint IP relay app version 60.30.5 and before: I get to the login screen, but when trying to login, microg crashes:

java.lang.ClassNotFoundException: Didn't find class "android.support.v7.widget.ButtonBarLayout" on path: DexPathList[[zip file "/system/framework/com.android.location.provider.jar", zip file "/data/app/com.google.android.gms-Q-bMnMr4UQ8M_1XpvD5m7w==/base.apk"],nativeLibraryDirectories=[/data/app/com.google.android.gms-Q-bMnMr4UQ8M_1XpvD5m7w==/lib/arm64, /data/app/com.google.android.gms-Q-bMnMr4UQ8M_1XpvD5m7w==/base.apk!/lib/arm64-v8a, /system/lib64, /vendor/lib64]]
stacktrace: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.google.android.gms/org.microg.gms.ui.AskPushPermission}: android.view.InflateException: Binary XML file line #79: Binary XML file line #79: Error inflating class android.support.v7.widget.ButtonBarLayout
	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2948)
	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3083)
	at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:78)
	at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:108)
	at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:68)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1813)
	at android.os.Handler.dispatchMessage(Handler.java:106)
	at android.os.Looper.loop(Looper.java:193)
	at android.app.ActivityThread.main(ActivityThread.java:6672)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:495)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:860)
Caused by: android.view.InflateException: Binary XML file line #79: Binary XML file line #79: Error inflating class android.support.v7.widget.ButtonBarLayout
Caused by: android.view.InflateException: Binary XML file line #79: Error inflating class android.support.v7.widget.ButtonBarLayout
Caused by: java.lang.ClassNotFoundException: Didn't find class "android.support.v7.widget.ButtonBarLayout" on path: DexPathList[[zip file "/system/framework/com.android.location.provider.jar", zip file "/data/app/com.google.android.gms-Q-bMnMr4UQ8M_1XpvD5m7w==/base.apk"],nativeLibraryDirectories=[/data/app/com.google.android.gms-Q-bMnMr4UQ8M_1XpvD5m7w==/lib/arm64, /data/app/com.google.android.gms-Q-bMnMr4UQ8M_1XpvD5m7w==/base.apk!/lib/arm64-v8a, /system/lib64, /vendor/lib64]]
	at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:134)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:379)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:312)
	at android.view.LayoutInflater.createView(LayoutInflater.java:606)
	at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:790)
	at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:730)
	at android.view.LayoutInflater.rInflate(LayoutInflater.java:863)
	at android.view.LayoutInflater.rInflateChildren(LayoutInflater.java:824)
	at android.view.LayoutInflater.rInflate(LayoutInflater.java:866)
	at android.view.LayoutInflater.rInflateChildren(LayoutInflater.java:824)
	at android.view.LayoutInflater.rInflate(LayoutInflater.java:866)
	at android.view.LayoutInflater.rInflateChildren(LayoutInflater.java:824)
	at android.view.LayoutInflater.inflate(LayoutInflater.java:515)
	at android.view.LayoutInflater.inflate(LayoutInflater.java:423)
	at android.view.LayoutInflater.inflate(LayoutInflater.java:374)
	at com.android.internal.policy.PhoneWindow.setContentView(PhoneWindow.java:421)
	at android.app.Activity.setContentView(Activity.java:2772)
	at org.microg.gms.ui.AskPushPermission.onCreate(AskPushPermission.java:53)
	at android.app.Activity.performCreate(Activity.java:7144)
	at android.app.Activity.performCreate(Activity.java:7135)
	at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1271)
	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2928)
	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3083)
	at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:78)
	at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:108)
	at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:68)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1813)
	at android.os.Handler.dispatchMessage(Handler.java:106)
	at android.os.Looper.loop(Looper.java:193)
	at android.app.ActivityThread.main(ActivityThread.java:6672)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:495)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:860)

closed time in 13 days

jesse-git

issue commentmicrog/android_packages_apps_GmsCore

Unable to start activity ComponentInfo{com.google.android.gms/org.microg.gms.ui.AskPushPermission

This was fixed in 26f2e859b8d424f20f42f3c2ec3736817f39b6e2

jesse-git

comment created time in 13 days

issue commentmicrog/android_packages_apps_GmsCore

Apps re-registered for GCM automatically

There was a bug with GCM permissions not being checked for some but not all kinds of GCM registrations. This should be fixed with 26f2e859b8d424f20f42f3c2ec3736817f39b6e2

pflanzenandi

comment created time in 13 days

push eventmicrog/android_packages_apps_GmsCore

Marvin W

commit sha ebbf78a876e7dc7e60783543732685192b5ee0c0

Bump version to 20.39.15

view details

push time in 14 days

push eventmicrog/android_packages_apps_GmsCore

Marvin W

commit sha 155bbce69bc445a37b2cdf9e88d6d09fa90879ca

EN: Retroactively "repair" broken database entries to a sane default value Related to #1230

view details

Marvin W

commit sha ff79a670e53e0264e47271343478ef025b8233b1

Update UnifiedNlp to alpha4

view details

Marvin W

commit sha 15fb118bbd1b0d1aa998c789af55596f9c72a464

EN: Correctly report multiple exposures to same key

view details

Marvin W

commit sha b67a11f4e66e842fe1fcb79d84225a4f70dd1d77

EN: Display more details about app usage, add feature for deleting RPI storage

view details

push time in 14 days

issue commentmicrog/android_packages_apps_GmsCore

Incorrect RSSI stored in database (Exposure Notifications)

@mh- sure, I can ping you once we do any database changes.

mh-

comment created time in 14 days

push eventmicrog/android_packages_apps_GmsCore

Marvin W

commit sha 139f7eaf1758494dfeb08c229888b23aaf702c66

EN: Correctly average rssi on database entry update Fixes #1230

view details

push time in 14 days

issue closedmicrog/android_packages_apps_GmsCore

Incorrect RSSI stored in database (Exposure Notifications)

If this is meant to update RSSI with the average of old and new value, it doesn't work. I get -9223372036854775808 (the minimum long value) from the database.

fun noteAdvertisement(rpi: ByteArray, aem: ByteArray, rssi: Int, timestamp: Long = Date().time) = writableDatabase.run {
        val update = compileStatement("UPDATE $TABLE_ADVERTISEMENTS SET rssi = ((rssi * duration) + (? * (? - timestamp - duration)) / (? - timestamp)), duration = (? - timestamp) WHERE rpi = ? AND timestamp > ? AND timestamp < ?").run {
            bindLong(1, rssi.toLong())
            bindLong(2, timestamp)
            bindLong(3, timestamp)
            bindLong(4, timestamp)
            bindBlob(5, rpi)
            bindLong(6, timestamp - ALLOWED_KEY_OFFSET_MS)
            bindLong(7, timestamp + ALLOWED_KEY_OFFSET_MS)
            executeUpdateDelete()
        }

closed time in 14 days

mh-

created tagmicrog/UnifiedNlp

tagv2.0-alpha4

The next generation Network Location Provider, based on plugins.

created time in 14 days

push eventmicrog/UnifiedNlp

Marvin W

commit sha 463865fcfaee273feb2baaa486d1cb8c6d54cce0

Use thread-safe cow lists

view details

push time in 14 days

issue commentmicrog/android_packages_apps_GmsCore

Incorrect RSSI stored in database (Exposure Notifications)

Yes, I am aware of that. However this information isn't used for risk calculation so back then when there only was v1 mode, there was no need to store this information. To support ExposureWindow mode we'd need to change how we store scan information in the database anyway.

The microG implementation doesn't completely match the Google implementation due to lack of proper specification and documentation at that point. This indeed changed to some degree, so it would make sense to update the implementation accordingly once there is time to do it. However until now I'm happy if we have results that are sufficiently similar.

mh-

comment created time in 14 days

issue commentmicrog/android_packages_apps_GmsCore

Incorrect RSSI stored in database (Exposure Notifications)

Thanks for reporting. Seems there is a closing paren at the wrong spot. Will fix asap.

mh-

comment created time in 15 days

issue commentmicrog/android_packages_apps_GmsCore

Permissions not requested

ACCESS_BACKGROUND_LOCATION is a hard restricted permission, which means that the decision if you can enable it is done by the app installing it (or if the app is part of the system image, the system decides this). Thus, this maybe is an issue of NanoDroid? @Nanolx

ploink

comment created time in 15 days

push eventmicrog/android_packages_apps_GmsCore

Marvin W

commit sha 26f2e859b8d424f20f42f3c2ec3736817f39b6e2

Ensure checkin before gcm registration, fix gcm permission requests

view details

Marvin W

commit sha d3d04459d66a0b7a357cffa3bdca84a21e4e0cd1

EN: Support partial device list matches

view details

push time in 16 days

push eventmicrog/UnifiedNlp

Marvin W

commit sha c474fce454785268fc5e2a4dc73c923d671f0dbe

Support SHA-1 digests in configuration

view details

push time in 16 days

issue commentmicrog/android_packages_apps_GmsCore

exposure.db takes up huge amounts of space

@eike-fokken you needed to manually shrink the file when using the latest version I uploaded at https://github.com/microg/android_packages_apps_GmsCore/issues/1190#issuecomment-708295463 ?

RalfJung

comment created time in 16 days

issue commentmicrog/android_packages_apps_GmsCore

Checkin service does not start on boot

I'm already working on this ;)

goffioul

comment created time in 16 days

push eventmicrog/android_packages_apps_GmsCore

Christian Grigis

commit sha b0e52b7a8986faea421c5ca174a5fa7b50734356

Update power calibrations with latest data

view details

push time in 16 days

PR merged microg/android_packages_apps_GmsCore

EN: Update power calibrations with latest data

Updated calibration data with the latest file (2020-09-18).

Fixes #1167

+485 -321

0 comment

1 changed file

cgrigis

pr closed time in 16 days

issue closedmicrog/android_packages_apps_GmsCore

Update RSSI / TX power device list for Exposure Notifications

Currently the device list from 2020-06-13 is used. The newer device list from 2020-08-12 uses a slightly different format which requires some code changes.

closed time in 16 days

mar-v-in

issue commentmicrog/android_packages_apps_GmsCore

Checkin service does not start on boot

Do you have a reference that forbids that? That's why my suggested patch does and it works fine for me.

The documentation of registerReceiver() has a note:

this method cannot be called from a BroadcastReceiver component; that is, from a BroadcastReceiver that is declared in an application's manifest.

It might have worked in your case if the BroadcardReceiver component was still valid at the time the connection came online - as broadcast receiver components are active for about 10 seconds.

After boot, I install skype and sign-in. That does not trigger the checkin service.

OK, so that is a real issue here :)

goffioul

comment created time in 17 days

issue commentmicrog/android_packages_apps_GmsCore

Checkin service does not start on boot

I need it running at boot.

As you pointed out, it cannot run at boot because network is not up yet. It's also not possible to register for CONNECTIVITY_ACTION from within the BOOT_COMPLETED receiver. This is why there is the additional android.server.checkin.CHECKIN which the inital setup wizard is supposed to invoke when network connectivity is available (e.g. after setting up wifi).

I don't see why you need to register a device at the earliest option after boot. It should be enough to register the device before the first app registers for push notifications, no?

goffioul

comment created time in 17 days

IssuesEvent

issue closedmicrog/android_packages_apps_GmsCore

Checkin service does not start on boot

I'm trying to integrate MicroG (GmsCore-v0.2.12.203315.apk) in an Android 9 build of android-x86, and have both checkin and gcm services started automatically on boot, including on first boot. To enable services, my build contains the following /system/etc/microg.xml file:

<?xml version='1.0' encoding='utf-8' standalone='yes' ?>
<map>
    <boolean name="checkin_enable_service" value="true" />
    <boolean name="gcm_enable_mcs_service" value="true" />
</map>

On initial boot, I can see GCM service started (on BOOT_COMPLETED broadcast), but it bails out as there's no checkin. Checkin service does not start, even when Wi-Fi connection is established (the build automatically connects to a specified AP). From what I can see, even though service org.microg.gms.checkin.TriggerReceiver registers a receiver for android.net.conn.CONNECTIVITY_CHANGE in the manifest, it's never triggered, because the APK targets API >= 24 (API 29 as of this writing). As stated in doc for ConnectivityManager, an app cannot receive that broadcast through manifest since Android N.

closed time in 17 days

goffioul

issue commentmicrog/android_packages_apps_GmsCore

Checkin service does not start on boot

e20a6c3a3cfda186edbc6a4c9ac525509dbe3809 fixes device checkin with newer Android versions.

goffioul

comment created time in 17 days

issue commentmicrog/android_packages_apps_GmsCore

exposure.db takes up huge amounts of space

@jw243 After I got a few confirmations that the upgrade to this version works smooth.

RalfJung

comment created time in 17 days

issue commentmicrog/android_packages_apps_GmsCore

exposure.db takes up huge amounts of space

I just uploaded a new build to https://microg.org/dl/core-en.apk which now includes the commits 1deeb45834c89bca10c2578a64b543ac240a83f4 and 0eb75ba363be06ae2519953dc8edf0647c98a731 which hopefully solve issues with large database files needing even more storage to be cleaned up and thus fail to do so. The database migration still needs a few MB of available storage, but afterwards you should end up with less than 10MB database size :)

RalfJung

comment created time in 17 days

push eventmicrog/android_packages_apps_GmsCore

Marvin W

commit sha e20a6c3a3cfda186edbc6a4c9ac525509dbe3809

Checkin: Ensure we recheckin regularly

view details

Marvin W

commit sha 0eb75ba363be06ae2519953dc8edf0647c98a731

EN: Fix oversize database migration

view details

push time in 17 days

delete branch microg/android_packages_apps_GmsCore

delete branch : optional-nearby

delete time in 18 days

delete branch microg/android_packages_apps_GmsCore

delete branch : travis-ci

delete time in 18 days

push eventmicrog/android_packages_apps_GmsCore

Marvin W

commit sha 31a8a3308be0d370cf602aa7950730875930e3f0

Force queryability for Android 11 compat

view details

push time in 18 days

create barnchmicrog/android_packages_apps_GmsCore

branch : travis-ci

created branch time in 18 days

delete branch microg/FakeStore

delete branch : travis

delete time in 18 days

push eventmicrog/FakeStore

Marvin W

commit sha f349d9f9acb6e620519be6668fe341b0e5b80f6f

Fix Travis

view details

push time in 18 days

push eventmicrog/FakeStore

Marvin W

commit sha f349d9f9acb6e620519be6668fe341b0e5b80f6f

Fix Travis

view details

push time in 18 days

push eventmicrog/FakeStore

Marvin W

commit sha abee77e5e70eb2609ccaa08f83a47da91b9f1a5c

Try fix Travis

view details

push time in 18 days

push eventmicrog/FakeStore

Marvin W

commit sha 2a24707cfccc3c0b7e6e2f9e1a1b8175a0f986c2

Try fix Travis

view details

push time in 18 days

push eventmicrog/FakeStore

Marvin W

commit sha 1c015eb4e6924549de1033b01bc00173fad01a63

Try fix Travis

view details

push time in 18 days

create barnchmicrog/FakeStore

branch : travis

created branch time in 18 days

push eventmicrog/FakeStore

Marvin W

commit sha 03b11df87b682dd78ab59db6d114ab4fc91eeab7

Force queryability for Android 11 compat

view details

push time in 18 days

issue closedmicrog/android_packages_apps_GmsCore

App "Radio France" crashes at startup

I'm running ResurrectionRemix 5.7.4, e.g AOSP 6.0.1 and the microG Services Core 0.2.11.202414

App crashes at startup :

09-09 20:39:43.770 23735 23735 E AndroidRuntime: at com.google.android.gms.cast.framework.internal.ICastDynamiteModule$Stub.onTransact(ICastDynamiteModule.java:84) 09-09 20:39:43.770 23735 23735 E AndroidRuntime: at android.os.Binder.transact(Binder.java:387) 09-09 20:39:43.770 23735 23735 E AndroidRuntime: at com.google.android.gms.internal.cast.zzb.zza(com.google.android.gms:play-services-cast@@18.1.0:10) 09-09 20:39:43.770 23735 23735 E AndroidRuntime: at com.google.android.gms.internal.cast.zzaj.zza(com.google.android.gms:play-services-cast-framework@@18.1.0:8) 09-09 20:39:43.770 23735 23735 E AndroidRuntime: at com.google.android.gms.internal.cast.zzae.zza(com.google.android.gms:play-services-cast-framework@@18.1.0:3) 09-09 20:39:43.770 23735 23735 E AndroidRuntime: at com.google.android.gms.cast.framework.CastContext.<init>(com.google.android.gms:play-services-cast-framework@@18.1.0:39) 09-09 20:39:43.770 23735 23735 E AndroidRuntime: at com.google.android.gms.cast.framework.CastContext.getSharedInstance(com.google.android.gms:play-services-cast-framework@@18.1.0:6) 09-09 20:39:43.770 23735 23735 E AndroidRuntime: at com.radiofrance.player.PlayerService.onCreate(PlayerService.java:158) 09-09 20:39:43.770 23735 23735 E AndroidRuntime: at com.radiofrance.radio.radiofrance.android.service.player.EchoesPlayerService.onCreate(EchoesPlayerService.kt:45) 09-09 20:39:43.770 23735 23735 E AndroidRuntime: at android.app.ActivityThread.handleCreateService(ActivityThread.java:2923) 09-09 20:39:43.770 23735 23735 E AndroidRuntime: ... 8 more 09-09 20:39:43.770 23735 23735 E AndroidRuntime: Caused by: java.lang.RuntimeException: Overread allowed size end=1012 09-09 20:39:43.770 23735 23735 E AndroidRuntime: at org.microg.safeparcel.SafeParcelUtil.readObject(SafeParcelUtil.java:103) 09-09 20:39:43.770 23735 23735 E AndroidRuntime: at org.microg.safeparcel.SafeParcelUtil.createObject(SafeParcelUtil.java:37) 09-09 20:39:43.770 23735 23735 E AndroidRuntime: ... 20 more

closed time in 18 days

mishka81

issue commentmicrog/UnifiedNlp

More location backends are displayed than installed

Thanks for reporting. Indeed UnifiedNlp keeps the Deja Vu backend "enabled" even when not installed anymore and there is no way to disable it then. The reason why backends keep enabled is that during their upgrade process, apps may appear "uninstalled" for a short term, but this shouldn't trigger them to be disabled.

Backends that are no longer installed should probably be removed latest when enabling or disabling other backends after others were uninstalled. Also the number in settings should better refer to the number of connected backends instead of enabled.

pflanzenandi

comment created time in 18 days

issue closedmicrog/android_packages_apps_GmsCore

VTMGo app crashes on startup

I'm testing integration of MicroG within Android-x86, currently being ported to Android 11. A summary of me setup is as follows:

  • signature spoofing is integrated into the build (fyi, Android 11 patch can be found in [1])
  • android-x86 running in qemu with virgl, in live mode (aka /data is tmpfs, no data persistence between run)
  • install GmsCore v0.2.12.203315
  • install com.google.android.gsf-8.apk
  • install com.android.vending-16.apk
  • launch MicroG settings, go to Self Check, enable everything
  • adb shell am start -n com.android.vending/.GrantFakeSignaturePermissionActivity, grant permission
  • go back to MicroG settings -> Self Check, verify all check boxes are ticked
  • install VTMGo [2]
  • launch VTMGo app => crash; logcat output can be found in [1]

[1] https://drive.google.com/drive/folders/1wZ0ZSh-m7jLpWUSwcP9MtvgeHvFzbgjN?usp=sharing [2] https://apkpure.com/vtm-go/be.vmma.vtm.zenderapp

closed time in 18 days

goffioul

issue commentmicrog/android_packages_apps_GmsCore

VTMGo app crashes on startup

Probably fixed through dbcf70f99ec36e68a886efef5f4552fe0e0d7e7e

goffioul

comment created time in 18 days

issue commentmicrog/android_packages_apps_GmsCore

Firebase Phone Auth and Google SignIn Not working

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

z3r0c00l-2k

comment created time in 18 days

issue commentmicrog/android_packages_apps_GmsCore

TextNow - Fails to log into account

This sounds like it could be related to firebase auth #1198 and thus maybe fixed via c3bfb63f27c116d21ba7b2b87629e36573d4a59e

Joecowboy

comment created time in 18 days

issue closedmicrog/android_packages_apps_GmsCore

Zero - Fasting Tracker does not work

Device: Xiaomi Mi Mix 2 GCM: Connected

Upon logging in at Zero, nothing happens and the following error is logged:

[10-10 21:45:13.720 25806:25917 E/Zero - UALib]
Push registration failed.
com.urbanairship.push.PushProvider$RegistrationException: FCM registration failed.
	at com.urbanairship.push.fcm.FcmPushProvider.getRegistrationToken(FcmPushProvider.java:75)
	at com.urbanairship.push.PushManagerJobHandler.onUpdatePushRegistration(PushManagerJobHandler.java:198)
	at com.urbanairship.push.PushManagerJobHandler.performJob(PushManagerJobHandler.java:116)
	at com.urbanairship.push.PushManager.onPerformJob(PushManager.java:349)
	at com.urbanairship.job.Job$1.run(Job.java:90)
	at com.urbanairship.util.SerialExecutor$1.run(SerialExecutor.java:40)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
	at com.urbanairship.util.AirshipThreadFactory$1.run(AirshipThreadFactory.java:49)
	at java.lang.Thread.run(Thread.java:764)
Caused by: java.io.IOException: SERVICE_NOT_AVAILABLE
	at com.google.firebase.iid.zzl.zza(com.google.firebase:firebase-iid@@20.0.0:67)
	at com.google.firebase.iid.zzl.zza(com.google.firebase:firebase-iid@@20.0.0:80)
	at com.google.firebase.iid.zzp.then(com.google.firebase:firebase-iid@@20.0.0:4)
	at com.google.android.gms.tasks.zzd.run(Unknown Source:5)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
	... 1 more

closed time in 18 days

omyno

issue commentmicrog/android_packages_apps_GmsCore

Zero - Fasting Tracker does not work

This should be fixed in c3bfb63f27c116d21ba7b2b87629e36573d4a59e

omyno

comment created time in 18 days

push eventmicrog/FakeStore

Marvin W

commit sha ddca351464806a7082607c0a9bb2bc2aebd1e409

Force queryability for Android 11 compat

view details

push time in 18 days

issue closedmicrog/android_packages_apps_GmsCore

[com.plumelabs.flow] Unable to log into an app

Hi there,

I'm unable to use a really specific app of my collection (Flow, package=com.plumelabs.flow). The app launches correctly, but recquire immediatly to log in, and whereas there is absolutely no problem with this step on another GAPPS phone, it's been at least 3 times with 3 different roms I'm facing the same issue with microG: can't log in, having a loading circle looping infinitly. Here is the corresponding logcat :

06-17 23:47:18.814 I/FirebasePerformance(19092): Session ID - 4aca52a6838f4ec981d9d07922d89453
06-17 23:47:18.815 D/Logger  (19092): (Application.kt:65) LoginActivity started
06-17 23:47:18.815 D/FirebasePerformance(19092): Creating a new Non Verbose Session: d60752291be14690aad0afb8ac72afb5
06-17 23:47:18.818 D/Logger  (19092): (Application.kt:61) LoginActivity resumed
06-17 23:47:18.821 W/ActivityManager(16239): Unable to start service Intent { act=com.google.android.gms.config.START pkg=com.google.android.gms } U=0: not found
06-17 23:47:18.821 W/ActivityManager(16239): Unbind failed: could not find connection for android.os.BinderProxy@7f37fd3
06-17 23:47:18.821 E/GmsClient(19092): unable to connect to service: com.google.android.gms.config.START on com.google.android.gms
06-17 23:47:18.824 D/GmsMeasureBrokerSvc(17687): onBind: Intent { act=com.google.android.gms.measurement.START pkg=com.google.android.gms }
06-17 23:47:18.826 D/GmsClearcutSvc(17687): onBind: Intent { act=com.google.android.gms.clearcut.service.START pkg=com.google.android.gms }
06-17 23:47:18.831 W/FirebaseRemoteConfig(19092): IPC failure: 17:API: Config.API is not available on this device.
06-17 23:47:18.835 D/SafeParcel(17687): Unknown field num 10 in com.google.android.gms.common.internal.GetServiceRequest, skipping.
06-17 23:47:18.835 D/SafeParcel(17687): Unknown field num 11 in com.google.android.gms.common.internal.GetServiceRequest, skipping.
06-17 23:47:18.835 D/SafeParcel(17687): Unknown field num 12 in com.google.android.gms.common.internal.GetServiceRequest, skipping.
06-17 23:47:18.835 D/GmsClearcutSvc(17687): bound by: GetServiceRequest{serviceId=CLEARCUT_LOGGER, gmsVersion=12451000, packageName='com.plumelabs.flow', extras=Bundle[{}]}
06-17 23:47:18.839 D/GmsClearcutLogSvcImpl(17687): log: LogEventParcelable[1, PlayLoggerContext[1, package=com.plumelabs.flow, packageVersionCode=78, logSource=-1, uploadAccount=null, loggingId=-1, logAndroidId=false, logSourceName=FIREPERF, isAnonymous=true, qosTier=0], LogEventBytes: CKLDoru2LTKjAQpoCigxOjEwMzE1NTYzODIzMzc6YW5kcm9pZDo4ZDliZGY3NDZkZjMxMTM1EgtkbVRLWU1iU3ZXMBotChJjb20ucGx1bWVsYWJzLmZsb3cSDzEuMC4wLjIyNTA1MzI1NhoGMS4yLjAzKAMSNwoDX2JzINi02vC+8eICKK/2ghVKIgogZDYwNzUyMjkxYmUxNDY5MGFhZDBhZmI4YWM3MmFmYjV4wHCIAaKj9CE=, AddPhenotypeExperimentTokens: true]
06-17 23:47:18.843 I/LatinIME(16521): Starting input. Cursor position = 46,46
06-17 23:47:18.847 D/SafeParcel(17687): Unknown field num 10 in com.google.android.gms.common.internal.GetServiceRequest, skipping.
06-17 23:47:18.847 D/SafeParcel(17687): Unknown field num 11 in com.google.android.gms.common.internal.GetServiceRequest, skipping.
06-17 23:47:18.847 D/SafeParcel(17687): Unknown field num 12 in com.google.android.gms.common.internal.GetServiceRequest, skipping.
06-17 23:47:18.847 D/GmsMeasureBrokerSvc(17687): bound by: GetServiceRequest{serviceId=MEASUREMENT, gmsVersion=12451000, packageName='com.plumelabs.flow', extras=Bundle[{}]}
06-17 23:47:18.848 D/GmsMeasureSvcImpl(17687): onTransact [unknown]: 10, android.os.Parcel@4f6de2e, 16

Phone Model : OnePlus6

attachment1-2019-06-19

MicroG installation : attachment2-2019-06-19 Using the NanoDroid installer (NanoDroid-21.0.20190601)

Has anyone an idea on how to troubleshoot this case ? That might be related to #404 #529 #497 and #310 but not so much information there since :

  • issue seems to have magically resolved with new release or
  • issue was related to a -dirty microG build or
  • user has got around not using the problematic app anymore

At this point, any help is welcome ;)

closed time in 18 days

voxitme

issue commentmicrog/android_packages_apps_GmsCore

[com.plumelabs.flow] Unable to log into an app

This should be fixed in c3bfb63f27c116d21ba7b2b87629e36573d4a59e (otherwise please reply).

voxitme

comment created time in 18 days

issue closedmicrog/android_packages_apps_GmsCore

Tier App not working (FirebaseAuth)

In the Tier scooter app: https://play.google.com/store/apps/details?id=com.tier.app&hl=de I cannot register. The API requires a Firebase token, and when entering the phone number while registering it goes into an infinite loading loop and the logcat only shows:

02-06 17:25:19.165 10207 10207 I BiChannelGoogleApi: [FirebaseAuth: ] getGoogleApiForMethod() returned Gms: com.google.firebase.auth.api.internal.zzaq@43193af

This is probably related to https://github.com/microg/android_packages_apps_GmsCore/issues/756 and https://github.com/microg/android_packages_apps_GmsCore/issues/842 . I tried enabling Google device registration and Google Cloud Messaging, but it does not help.

EDIT: More logcat stuff (contains a few more firebase errors, but no exceptions (at least not from firebase)): https://gist.github.com/Romern/1857d4cfba76218151e4141c82640717

closed time in 18 days

Romern
more