/e/OS on FP3: microG Services Core keeps stopping

Hi,

I’ve purchased the FP3 with /e/OS, and first of all thanks for all the work you’re doing! I’ve been running /e/OS for a few weeks now and apart from a few minor issues it works great!

One of these minor issues is that sometimes when I’m using specific apps (such as Netflix) I get repeated “microG Services Core keeps stopping” (I get them three times a few second apart from each other from the point I start the app, then nothing more till it restarts, but I assume it’s just because it’s giving up).

I’ve ran adb logcat with my device and tried it again and the logs that seem relevant are:

08-29 15:28:50.914  4405  6177 D GmsDroidguardHelper: -- Request --
08-29 15:28:50.914  4405  6177 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.20200810.080407 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-e2ba83ed-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=unknown}, KeyValuePair{key=SERIAL, val=A209L3GG0201}, KeyValuePair{key=TAGS, val=dev-keys}, KeyValuePair{key=TIME, val=1597046599000}, KeyValuePair{key=TYPE, val=userdebug}, KeyValuePair{key=USER, val=root}, KeyValuePair{key=CODENAME, val=REL}, KeyValuePair{key=INCREMENTAL, val=eng.root.20200810.080407}, 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=bcfbdc3a985a4e1084e41930fe46f5c3], ByteString[size=20 md5=3f6700eaac6fdd34a59e361528e28c6d], ByteString[size=20 md5=f743d0ba1226660821f459fb7bd7a739]], currentVersion=3, arch=aarch64}
08-29 15:28:50.989  4405  6177 D GmsDroidguardHelper: Using cached file from /data/user/0/org.microg.gms.droidguard/app_dg_cache/ae664d43faa8b0d03088ecd40680eda6c5a44b59/the.apk
08-29 15:28:51.004  4405  6177 D GmsDroidguardHelper: b -> 4075262425588369947
08-29 15:28:51.051  4405  6177 E SQLiteLog: (14) cannot open file at line 36667 of [68b898381a]
08-29 15:28:51.051  4405  6177 E SQLiteLog: (14) os_unix.c:36667: (2) open(/data/user/0/org.microg.gms.droidguard/databases/dg.db) - 
08-29 15:28:51.052  4405  6177 E SQLiteDatabase: Failed to open database '/data/user/0/org.microg.gms.droidguard/databases/dg.db'.
08-29 15:28:51.052  4405  6177 E SQLiteDatabase: android.database.sqlite.SQLiteCantOpenDatabaseException: unknown error (code 14 SQLITE_CANTOPEN): Could not open database
08-29 15:28:51.052  4405  6177 E SQLiteDatabase: 	at android.database.sqlite.SQLiteConnection.nativeOpen(Native Method)
08-29 15:28:51.052  4405  6177 E SQLiteDatabase: 	at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:212)
08-29 15:28:51.052  4405  6177 E SQLiteDatabase: 	at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:196)
08-29 15:28:51.052  4405  6177 E SQLiteDatabase: 	at android.database.sqlite.SQLiteConnectionPool.openConnectionLocked(SQLiteConnectionPool.java:503)
08-29 15:28:51.052  4405  6177 E SQLiteDatabase: 	at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:204)
08-29 15:28:51.052  4405  6177 E SQLiteDatabase: 	at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:196)
08-29 15:28:51.052  4405  6177 E SQLiteDatabase: 	at android.database.sqlite.SQLiteDatabase.openInner(SQLiteDatabase.java:880)
08-29 15:28:51.052  4405  6177 E SQLiteDatabase: 	at android.database.sqlite.SQLiteDatabase.open(SQLiteDatabase.java:865)
08-29 15:28:51.052  4405  6177 E SQLiteDatabase: 	at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:766)
08-29 15:28:51.052  4405  6177 E SQLiteDatabase: 	at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:714)
08-29 15:28:51.052  4405  6177 E SQLiteDatabase: 	at com.google.ccc.abuse.droidguard.DroidGuard.initNative(Native Method)
08-29 15:28:51.052  4405  6177 E SQLiteDatabase: 	at com.google.ccc.abuse.droidguard.DroidGuard.init(DroidGuard.java:447)
08-29 15:28:51.052  4405  6177 E SQLiteDatabase: 	at com.google.ccc.abuse.droidguard.DroidGuard.run(DroidGuard.java:429)
08-29 15:28:51.052  4405  6177 E SQLiteDatabase: 	at java.lang.reflect.Method.invoke(Native Method)
08-29 15:28:51.052  4405  6177 E SQLiteDatabase: 	at org.microg.gms.droidguard.DroidguardHelper.invoke(DroidguardHelper.java:140)
08-29 15:28:51.052  4405  6177 E SQLiteDatabase: 	at org.microg.gms.droidguard.DroidguardHelper.guard(DroidguardHelper.java:93)
08-29 15:28:51.052  4405  6177 E SQLiteDatabase: 	at org.microg.gms.droidguard.RemoteDroidGuardService$1$1.run(RemoteDroidGuardService.java:23)
08-29 15:28:51.052  4405  6177 E SQLiteDatabase: 	at java.lang.Thread.run(Thread.java:764)
08-29 15:28:51.053  1277  2043 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
08-29 15:28:51.206  4405  4405 W Thread-11: type=1400 audit(0.0:18261): avc: denied { search } for name="vendor" dev="tmpfs" ino=14726 scontext=u:r:priv_app:s0:c512,c768 tcontext=u:object_r:mnt_vendor_file:s0 tclass=dir permissive=0
08-29 15:28:51.210  4405  4405 W Thread-11: type=1400 audit(0.0:18262): 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
08-29 15:28:51.215  4405  6177 D GmsDroidguardHelper: c -> com.google.android.gms
08-29 15:28:51.236  4405  4405 W Thread-11: type=1400 audit(0.0:18263): avc: denied { read } for name="type" dev="sysfs" ino=51309 scontext=u:r:priv_app:s0:c512,c768 tcontext=u:object_r:sysfs:s0 tclass=file permissive=0
08-29 15:28:51.247  6151  6175 E AndroidRuntime: FATAL EXCEPTION: Thread-2
08-29 15:28:51.247  6151  6175 E AndroidRuntime: Process: com.google.android.gms, PID: 6151
08-29 15:28:51.247  6151  6175 E AndroidRuntime: java.lang.IllegalArgumentException: Service not registered: org.microg.gms.droidguard.RemoteDroidGuardConnector$Connection@68391c2
08-29 15:28:51.247  6151  6175 E AndroidRuntime: 	at android.app.LoadedApk.forgetServiceDispatcher(LoadedApk.java:1562)
08-29 15:28:51.247  6151  6175 E AndroidRuntime: 	at android.app.ContextImpl.unbindService(ContextImpl.java:1692)
08-29 15:28:51.247  6151  6175 E AndroidRuntime: 	at android.content.ContextWrapper.unbindService(ContextWrapper.java:717)
08-29 15:28:51.247  6151  6175 E AndroidRuntime: 	at org.microg.gms.droidguard.RemoteDroidGuardConnector.connectForTask(Unknown Source:42)
08-29 15:28:51.247  6151  6175 E AndroidRuntime: 	at org.microg.gms.droidguard.RemoteDroidGuardConnector.guard(Unknown Source:22)
08-29 15:28:51.247  6151  6175 E AndroidRuntime: 	at org.microg.gms.snet.SafetyNetClientServiceImpl$1.run(Unknown Source:63)
08-29 15:28:51.247  6151  6175 E AndroidRuntime: 	at java.lang.Thread.run(Thread.java:764)

Which I assume means it can’t open Droidguard’s SQLite database for some reason.

It’s weird because my previous phone was running a Lineage + microG install and never had this issue.

Thanks in advance for the help!

Hi,

thank you for your purchase !

The issue your are facing is already in the gitlab :

You could add a comment under to know what is the state of the issue.

2 Likes

Hey, thanks for the swift reply!

Glad to see the issue’s already on your radar, I’ve just added a comment with my logs :slight_smile:

1 Like

I added a comment on gitlab but the issue is closed so I’m not sure if I’ll get a reply. I’m getting this error with the Australian ‘Service NSW’ app. The error pops up and when I close it I’m told I can’t login. I don’t know what they’re referring to on the gitlab post when when they say safetynet and latest builds, or what adb logcat is or how to run it and, to be honest, nor do I really want to. Forgive my candour but I installed e OS thinking it would just work, not that I’d have to start running diagnostics for the e foundation and have issues I raise about glaring problems (like screen recordings not including sound: Screen recording doesn't include sound? - Applications - /e/ community) edited by Manoj to be in the right category but then just ignored and left unresolved.

Hi, I factory reseted my /e/ preinstalled FP3 yesterday, and one of the apps that used to work fine (Wallapop) is giving me the same problem: “microG Services Core keeps stopping", and I cannot connect to my account. It’s strange, because this same app worked fine till I did the reset. Any help?

1 Like

Hello, I have the same issue as the poster above, that Wallapop is giving me this problem also. I am using a pre-installed GS290 with latest updated OS version.