Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Skip to content

tinder app makes microG crash (SafetyNet)

Summary

tinder app makes microG crash

The problem

Steps to reproduce

Install tinder. Use a fresh install. Problem is reproducible 100% of the time when starting tinder for the first time, but I've been unable to reproduce it when starting it the second time.

Start it and follow initial setup, give it location perms and follow SMS verification + email verification when requested.

At some point (probably a few times) during this process, you'll get "microG Services Core keeps stopping" error. Sometimes tinder app itself also crashes.

Technical informations

Relevant logs (adb logcat)

10-11 22:04:25.494 22454 22903 D GmsDroidguardHelper: -- Request --
10-11 22:04:25.494 22454 22903 D GmsDroidguardHelper: DGRequest{usage=DGUsage{type=attest, packageName=com.google.android.gms}, info=[KeyValuePair{key=BOARD, val=FP3}, KeyValuePair{key=BOOTLOADER, val=unknown}, KeyValuePair{key=BRAND, val=Fairphone}, KeyValuePair{key=CPU_ABI, val=arm64-v8a}, KeyValuePair{key=CPU_ABI2, val=}, KeyValuePair{key=SUPPORTED_ABIS, val=arm64-v8a,armeabi-v7a,armeabi}, KeyValuePair{key=DEVICE, val=FP3}, KeyValuePair{key=DISPLAY, val=lineage_FP3-userdebug 9 PQ3A.190801.002 eng.root.20200828.131559 dev-keys}, KeyValuePair{key=FINGERPRINT, val=Fairphone/FP3/FP3:9/8901.2.A.0120.20200421/04211500:user/release-keys}, KeyValuePair{key=HARDWARE, val=qcom}, KeyValuePair{key=HOST, val=runner-mP8yZJ5x-project-53-concurrent-0}, KeyValuePair{key=ID, val=PQ3A.190801.002}, KeyValuePair{key=MANUFACTURER, val=Fairphone}, KeyValuePair{key=MODEL, val=FP3}, KeyValuePair{key=PRODUCT, val=FP3}, KeyValuePair{key=RADIO, val=1-00565-8953_GEN_PACK-1.299152.1,1-00565-8953_GEN_PACK-1.299152.1}, KeyValuePair{key=SERIAL, val=A209QE6X0201}, KeyValuePair{key=TAGS, val=dev-keys}, KeyValuePair{key=TIME, val=1598620530000}, KeyValuePair{key=TYPE, val=userdebug}, KeyValuePair{key=USER, val=root}, KeyValuePair{key=CODENAME, val=REL}, KeyValuePair{key=INCREMENTAL, val=eng.root.20200828.131559}, KeyValuePair{key=RELEASE, val=9}, KeyValuePair{key=SDK, val=28}, KeyValuePair{key=SDK_INT, val=28}], versionNamePrefix=19.4.20 (040400-{{cl}}), isGoogleCn=false, enableInlineVm=true, cached=[ByteString[size=20 md5=c0e2404b5788dc86cdf103ce03baf328]], currentVersion=3, arch=aarch64}

10-11 22:04:25.620 22454 22903 D GmsDroidguardHelper: Using cached file from /data/user/0/org.microg.gms.droidguard/app_dg_cache/d2d940e103e001423f0297553c216424c987b768/the.apk
10-11 22:04:25.628 22454 22903 E SQLiteLog: (14) cannot open file at line 36667 of [68b898381a]
10-11 22:04:25.628 22454 22903 E SQLiteLog: (14) os_unix.c:36667: (2) open(/data/user/0/org.microg.gms.droidguard/databases/dg.db) - 
10-11 22:04:25.628 22454 22903 E SQLiteDatabase: Failed to open database '/data/user/0/org.microg.gms.droidguard/databases/dg.db'.
10-11 22:04:25.628 22454 22903 E SQLiteDatabase: android.database.sqlite.SQLiteCantOpenDatabaseException: unknown error (code 14 SQLITE_CANTOPEN): Could not open database
10-11 22:04:25.628 22454 22903 E SQLiteDatabase: 	at android.database.sqlite.SQLiteConnection.nativeOpen(Native Method)
10-11 22:04:25.628 22454 22903 E SQLiteDatabase: 	at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:212)
10-11 22:04:25.628 22454 22903 E SQLiteDatabase: 	at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:196)
10-11 22:04:25.628 22454 22903 E SQLiteDatabase: 	at android.database.sqlite.SQLiteConnectionPool.openConnectionLocked(SQLiteConnectionPool.java:503)
10-11 22:04:25.628 22454 22903 E SQLiteDatabase: 	at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:204)
10-11 22:04:25.628 22454 22903 E SQLiteDatabase: 	at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:196)
10-11 22:04:25.628 22454 22903 E SQLiteDatabase: 	at android.database.sqlite.SQLiteDatabase.openInner(SQLiteDatabase.java:880)
10-11 22:04:25.628 22454 22903 E SQLiteDatabase: 	at android.database.sqlite.SQLiteDatabase.open(SQLiteDatabase.java:865)
10-11 22:04:25.628 22454 22903 E SQLiteDatabase: 	at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:766)
10-11 22:04:25.628 22454 22903 E SQLiteDatabase: 	at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:714)
10-11 22:04:25.628 22454 22903 E SQLiteDatabase: 	at com.google.ccc.abuse.droidguard.DroidGuard.initNative(Native Method)
10-11 22:04:25.628 22454 22903 E SQLiteDatabase: 	at com.google.ccc.abuse.droidguard.DroidGuard.init(DroidGuard.java:447)
10-11 22:04:25.628 22454 22903 E SQLiteDatabase: 	at com.google.ccc.abuse.droidguard.DroidGuard.run(DroidGuard.java:429)
10-11 22:04:25.628 22454 22903 E SQLiteDatabase: 	at java.lang.reflect.Method.invoke(Native Method)
10-11 22:04:25.628 22454 22903 E SQLiteDatabase: 	at org.microg.gms.droidguard.DroidguardHelper.invoke(DroidguardHelper.java:140)
10-11 22:04:25.628 22454 22903 E SQLiteDatabase: 	at org.microg.gms.droidguard.DroidguardHelper.guard(DroidguardHelper.java:93)
10-11 22:04:25.628 22454 22903 E SQLiteDatabase: 	at org.microg.gms.droidguard.RemoteDroidGuardService$1$1.run(RemoteDroidGuardService.java:23)
10-11 22:04:25.628 22454 22903 E SQLiteDatabase: 	at java.lang.Thread.run(Thread.java:764)
10-11 22:04:25.630  1318  1335 W ActivityManager: Unable to start service Intent { act=com.google.android.gms.droidguard.service.PING pkg=com.google.android.gms (has extras) } U=0: not found
10-11 22:04:25.894 22454 22903 D GmsDroidguardHelper: c -> com.google.android.gms
10-11 22:04:25.897 22454 22903 D GmsDroidguardHelper: b -> 0
10-11 22:04:25.922 22454 22454 W Thread-5: type=1400 audit(0.0:139): avc: denied { search } for name="vendor" dev="tmpfs" ino=5103 scontext=u:r:priv_app:s0:c512,c768 tcontext=u:object_r:mnt_vendor_file:s0 tclass=dir permissive=0
10-11 22:04:26.010 22876 22901 E AndroidRuntime: FATAL EXCEPTION: Thread-2
10-11 22:04:26.010 22876 22901 E AndroidRuntime: Process: com.google.android.gms, PID: 22876
10-11 22:04:26.010 22876 22901 E AndroidRuntime: java.lang.IllegalArgumentException: Service not registered: org.microg.gms.droidguard.RemoteDroidGuardConnector$Connection@e263c80
10-11 22:04:26.010 22876 22901 E AndroidRuntime: 	at android.app.LoadedApk.forgetServiceDispatcher(LoadedApk.java:1562)
10-11 22:04:26.010 22876 22901 E AndroidRuntime: 	at android.app.ContextImpl.unbindService(ContextImpl.java:1692)
10-11 22:04:26.010 22876 22901 E AndroidRuntime: 	at android.content.ContextWrapper.unbindService(ContextWrapper.java:717)
10-11 22:04:26.010 22876 22901 E AndroidRuntime: 	at org.microg.gms.droidguard.RemoteDroidGuardConnector.connectForTask(Unknown Source:42)
10-11 22:04:26.010 22876 22901 E AndroidRuntime: 	at org.microg.gms.droidguard.RemoteDroidGuardConnector.guard(Unknown Source:22)
10-11 22:04:26.010 22876 22901 E AndroidRuntime: 	at org.microg.gms.snet.SafetyNetClientServiceImpl$1.run(Unknown Source:63)
10-11 22:04:26.010 22876 22901 E AndroidRuntime: 	at java.lang.Thread.run(Thread.java:764)

The aforementioned file (/data/user/0/org.microg.gms.droidguard/databases/dg.db) does NOT exist. But its folder (/data/user/0/org.microg.gms.droidguard/databases/) does.

I'm using /e/ 0.11 on FP3 (IMG-e-0.11-p-2020082870302-dev-FP3.zip) and the microG version that came with it (0.2.10.19420-77)

Edited by Robert B.