MicroG Crash with Netflix
- /e/ version: 0.9-2020061158052
- Device model: Fairphone 3
- When it started to occur: 3 weeks
- Reproducible with the last /e/ version: Yes
- Reproducible with LineageOS: don't know
Summary
When I use the Netflix application, I regularly receive a message that the MicroG application has crach.
-
The device is unusable -
The bug is the source of a data loss or a big waste of time -
The bug concerns a third party app -
The bug concerns security -
The bug concerns privacy
The problem
Steps to reproduce
- open netflix
- wait for notification of microg crash
What is the current behavior?
Netflix seems to use features of Google services that MicroG does not support.
What is the expected correct behavior?
Not having the crash notification
Technical informations
Relevant logs (adb logcat
)
06-04 20:52:23.891 9479 9553 D GmsDroidguardHelper: Using cached file from /data/user/0/org.microg.gms.droidguard/app_dg_cache/717dc6b1ee3213ea2fa6198911c68c9c6cc4715c/the.apk
06-04 20:52:23.950 9479 9553 D GmsDroidguardHelper: c -> com.google.android.gms
06-04 20:52:23.926 9479 9479 W Thread-3: type=1400 audit(0.0:155): avc: denied { search } for name="vendor" dev="tmpfs" ino=4944 scontext=u:r:priv_app:s0:c512,c768 tcontext=u:object_r:mnt_vendor_file:s0 tclass=dir permissive=0
06-04 20:52:23.992 9479 9553 D GmsDroidguardHelper: b -> 3927303995488753452
06-04 20:52:23.926 9479 9479 W Thread-3: type=1400 audit(0.0:156): avc: denied { getattr } for name="/" dev="mmcblk0p1" ino=1 scontext=u:r:priv_app:s0:c512,c768 tcontext=u:object_r:firmware_file:s0 tclass=filesystem permissive=0
06-04 20:52:24.036 9479 9553 E SQLiteLog: (14) cannot open file at line 36667 of [68b898381a]
06-04 20:52:24.036 9479 9553 E SQLiteLog: (14) os_unix.c:36667: (2) open(/data/user/0/org.microg.gms.droidguard/databases/dg.db) -
06-04 20:52:24.037 9479 9553 E SQLiteDatabase: Failed to open database '/data/user/0/org.microg.gms.droidguard/databases/dg.db'.
06-04 20:52:24.037 9479 9553 E SQLiteDatabase: android.database.sqlite.SQLiteCantOpenDatabaseException: unknown error (code 14 SQLITE_CANTOPEN): Could not open database
06-04 20:52:24.037 9479 9553 E SQLiteDatabase: at android.database.sqlite.SQLiteConnection.nativeOpen(Native Method)
06-04 20:52:24.037 9479 9553 E SQLiteDatabase: at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:212)
06-04 20:52:24.037 9479 9553 E SQLiteDatabase: at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:196)
06-04 20:52:24.037 9479 9553 E SQLiteDatabase: at android.database.sqlite.SQLiteConnectionPool.openConnectionLocked(SQLiteConnectionPool.java:503)
06-04 20:52:24.037 9479 9553 E SQLiteDatabase: at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:204)
06-04 20:52:24.037 9479 9553 E SQLiteDatabase: at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:196)
06-04 20:52:24.037 9479 9553 E SQLiteDatabase: at android.database.sqlite.SQLiteDatabase.openInner(SQLiteDatabase.java:880)
06-04 20:52:24.037 9479 9553 E SQLiteDatabase: at android.database.sqlite.SQLiteDatabase.open(SQLiteDatabase.java:865)
06-04 20:52:24.037 9479 9553 E SQLiteDatabase: at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:766)
06-04 20:52:24.037 9479 9553 E SQLiteDatabase: at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:714)
06-04 20:52:24.037 9479 9553 E SQLiteDatabase: at com.google.ccc.abuse.droidguard.DroidGuard.initNative(Native Method)
06-04 20:52:24.037 9479 9553 E SQLiteDatabase: at com.google.ccc.abuse.droidguard.DroidGuard.init(DroidGuard.java:447)
06-04 20:52:24.037 9479 9553 E SQLiteDatabase: at com.google.ccc.abuse.droidguard.DroidGuard.run(DroidGuard.java:429)
06-04 20:52:24.037 9479 9553 E SQLiteDatabase: at java.lang.reflect.Method.invoke(Native Method)
06-04 20:52:24.037 9479 9553 E SQLiteDatabase: at org.microg.gms.droidguard.DroidguardHelper.invoke(DroidguardHelper.java:140)
06-04 20:52:24.037 9479 9553 E SQLiteDatabase: at org.microg.gms.droidguard.DroidguardHelper.guard(DroidguardHelper.java:93)
06-04 20:52:24.037 9479 9553 E SQLiteDatabase: at org.microg.gms.droidguard.RemoteDroidGuardService$1$1.run(RemoteDroidGuardService.java:23)
06-04 20:52:24.037 9479 9553 E SQLiteDatabase: at java.lang.Thread.run(Thread.java:764)
Relevant screenshots
Solutions
Workaround
Disable the microG service.
Possible fixes
Analyze why the application is looking for a non-existing database file.