Pebble watch app crashes with 0.2.14.204215

[Sapiosenses]

Affected app
Name: Pebble
Package id: com.getpebble.android.basalt

Describe the bug
As soon as I update to v0.2.14.204215 via F-droid repository, the Pebble watch app starts continuously crashing. Reverting to 0.2.13.0915 fixes it.

To Reproduce
Steps to reproduce the behavior:

1. Update GmsCore to v0.2.14.204215
2. Pebble watch app starts crashing (no need to launch manually, app runs continuously)

Expected behavior
No crashing

Screenshots

System
Android Version: 7.1.2
Custom ROM: LineageOS 14.1

microG
microG Core version: 0.2.14.204215
microG Self-Check results: All ticked

Additional context
Reverting to v0.2.13.0915 fixes problem immediately. I have a logcat filtered for string "pebble", let me know if you would like a different filtered log.

[Sapiosenses]

11-26 06:49:41.293 F/DEBUG (4873): pid: 4625, tid: 4744, name: ion-ion >>> com.getpebble.android.basalt:framework <<<
11-26 06:49:41.362 F/DEBUG (4873): #5 pc 0003b14f /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:49:41.362 F/DEBUG (4873): #6 pc 0003af6b /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:49:41.362 F/DEBUG (4873): #7 pc 0003aec3 /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:49:48.531 F/DEBUG (5225): pid: 4982, tid: 5208, name: ion-ion >>> com.getpebble.android.basalt:framework <<<
11-26 06:49:48.591 F/DEBUG (5225): #5 pc 0003b14f /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:49:48.591 F/DEBUG (5225): #6 pc 0003af6b /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:49:48.591 F/DEBUG (5225): #7 pc 0003aec3 /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:50:00.807 F/DEBUG (5481): pid: 5451, tid: 5479, name: ion-ion >>> com.getpebble.android.basalt:framework <<<
11-26 06:50:00.834 F/DEBUG (5481): #5 pc 0003b14f /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:50:00.834 F/DEBUG (5481): #6 pc 0003af6b /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:50:00.834 F/DEBUG (5481): #7 pc 0003aec3 /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:50:01.819 I/ActivityManager(1811): Process com.getpebble.android.basalt:framework (pid 5451) has died
11-26 06:50:01.820 W/ActivityManager(1811): Scheduling restart of crashed service com.getpebble.android.basalt/com.getpebble.android.core.sync.PebbleSyncService in 1000ms
11-26 06:50:08.525 I/ActivityManager(1811): Start proc 5501:com.getpebble.android.basalt:framework/u0a231 for service com.getpebble.android.basalt/com.getpebble.android.core.sync.PebbleSyncService
11-26 06:50:11.201 F/DEBUG (5538): pid: 5501, tid: 5536, name: ion-ion >>> com.getpebble.android.basalt:framework <<<
11-26 06:50:11.228 F/DEBUG (5538): #5 pc 0003b14f /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:50:11.228 F/DEBUG (5538): #6 pc 0003af6b /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:50:11.228 F/DEBUG (5538): #7 pc 0003aec3 /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:50:11.912 I/ActivityManager(1811): Process com.getpebble.android.basalt:framework (pid 5501) has died
11-26 06:50:11.913 W/ActivityManager(1811): Scheduling restart of crashed service com.getpebble.android.basalt/com.getpebble.android.core.sync.PebbleSyncService in 1000ms
11-26 06:50:19.089 I/ActivityManager(1811): Start proc 5553:com.getpebble.android.basalt:framework/u0a231 for service com.getpebble.android.basalt/com.getpebble.android.core.sync.PebbleSyncService
11-26 06:50:21.702 F/DEBUG (5583): pid: 5553, tid: 5581, name: ion-ion >>> com.getpebble.android.basalt:framework <<<
11-26 06:50:21.722 F/DEBUG (5583): #5 pc 0003b14f /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:50:21.722 F/DEBUG (5583): #6 pc 0003af6b /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:50:21.722 F/DEBUG (5583): #7 pc 0003aec3 /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:50:22.342 I/ActivityManager(1811): Process com.getpebble.android.basalt:framework (pid 5553) has died
11-26 06:50:22.343 W/ActivityManager(1811): Scheduling restart of crashed service com.getpebble.android.basalt/com.getpebble.android.core.sync.PebbleSyncService in 1000ms
11-26 06:50:29.627 I/ActivityManager(1811): Start proc 5594:com.getpebble.android.basalt:framework/u0a231 for service com.getpebble.android.basalt/com.getpebble.android.core.sync.PebbleSyncService
11-26 06:50:31.876 F/DEBUG (5624): pid: 5594, tid: 5621, name: ion-ion >>> com.getpebble.android.basalt:framework <<<
11-26 06:50:31.901 F/DEBUG (5624): #5 pc 0003b14f /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:50:31.901 F/DEBUG (5624): #6 pc 0003af6b /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:50:31.901 F/DEBUG (5624): #7 pc 0003aec3 /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:50:32.690 I/ActivityManager(1811): Process com.getpebble.android.basalt:framework (pid 5594) has died
11-26 06:50:32.690 W/ActivityManager(1811): Scheduling restart of crashed service com.getpebble.android.basalt/com.getpebble.android.core.sync.PebbleSyncService in 1000ms
11-26 06:50:40.065 W/ActivityManager(1811): Ignoring remove of inactive process: ProcessRecord{aa931fc 0:com.getpebble.android.basalt:framework/u0a231}
11-26 06:50:40.284 I/ActivityManager(1811): Start proc 5651:com.getpebble.android.basalt:framework/u0a231 for service com.getpebble.android.basalt/com.getpebble.android.core.sync.PebbleSyncService
11-26 06:50:41.033 W/ActivityManager(1811): Ignoring remove of inactive process: ProcessRecord{6634314 0:com.getpebble.android.basalt:framework/u0a231}
11-26 06:50:41.755 W/ActivityManager(1811): Ignoring remove of inactive process: ProcessRecord{ba500b 0:com.getpebble.android.basalt:framework/u0a231}
11-26 06:50:42.439 W/ActivityManager(1811): Ignoring remove of inactive process: ProcessRecord{2dcce38 0:com.getpebble.android.basalt:framework/u0a231}
11-26 06:50:43.103 W/ActivityManager(1811): Ignoring remove of inactive process: ProcessRecord{12bf6f9 0:com.getpebble.android.basalt:framework/u0a231}
11-26 06:50:43.503 F/DEBUG (5682): pid: 5651, tid: 5679, name: ion-ion >>> com.getpebble.android.basalt:framework <<<
11-26 06:50:43.545 F/DEBUG (5682): #5 pc 0003b14f /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:50:43.545 F/DEBUG (5682): #6 pc 0003af6b /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:50:43.545 F/DEBUG (5682): #7 pc 0003aec3 /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:50:44.847 W/ActivityManager(1811): Process com.getpebble.android.basalt:ui has crashed too many times: killing!
11-26 06:50:44.847 I/ActivityManager(1811): Killing 5651:com.getpebble.android.basalt:framework/u0a231 (adj 100): crash
11-26 06:51:15.352 I/ActivityManager(1811): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.getpebble.android.basalt/com.getpebble.android.main.activity.MainActivity bnds=[1073,1653][1426,2040] (has extras)} from uid 10032 on display 0
11-26 06:51:15.399 I/ActivityManager(1811): Start proc 5880:com.getpebble.android.basalt:ui/u0a231 for activity com.getpebble.android.basalt/com.getpebble.android.main.activity.MainActivity
11-26 06:51:15.614 I/ActivityManager(1811): Start proc 5896:com.getpebble.android.basalt:framework/u0a231 for content provider com.getpebble.android.basalt/com.getpebble.android.core.provider.PebbleContentProvider
11-26 06:51:17.595 F/DEBUG (5955): pid: 5880, tid: 5926, name: ion-ion >>> com.getpebble.android.basalt:ui <<<
11-26 06:51:17.655 F/DEBUG (5955): #5 pc 0003b14f /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:51:17.655 F/DEBUG (5955): #6 pc 0003af6b /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:51:17.655 F/DEBUG (5955): #7 pc 0003aec3 /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:51:19.280 W/ActivityManager(1811): Force finishing activity com.getpebble.android.basalt/com.getpebble.android.main.activity.MainActivity
11-26 06:51:19.342 I/WindowManager(1811): WIN DEATH: Window{2a4c672 u0 com.getpebble.android.basalt/com.getpebble.android.main.activity.MainActivity}
11-26 06:51:19.344 I/ActivityManager(1811): Process com.getpebble.android.basalt:ui (pid 5880) has died
11-26 06:51:19.365 W/WindowManager(1811): This window was lost: Window{e11382d u0 Starting com.getpebble.android.basalt}
11-26 06:51:19.365 W/WindowManager(1811): mOwnerUid=1000 mShowToOwnerOnly=false package=com.getpebble.android.basalt appop=NONE
11-26 06:51:19.365 W/WindowManager(1811): mToken=AppWindowToken{8e74c5f token=Token{3c8a0b9 ActivityRecord{9d9e280 u0 com.getpebble.android.basalt/com.getpebble.android.main.activity.MainActivity t5}}}
11-26 06:51:19.365 W/WindowManager(1811): mRootToken=AppWindowToken{8e74c5f token=Token{3c8a0b9 ActivityRecord{9d9e280 u0 com.getpebble.android.basalt/com.getpebble.android.main.activity.MainActivity t5}}}
11-26 06:51:19.365 W/WindowManager(1811): mAppToken=AppWindowToken{8e74c5f token=Token{3c8a0b9 ActivityRecord{9d9e280 u0 com.getpebble.android.basalt/com.getpebble.android.main.activity.MainActivity t5}}}
11-26 06:51:19.365 W/WindowManager(1811): WindowStateAnimator{87c0e63 Starting com.getpebble.android.basalt}:
11-26 06:51:19.365 V/WindowManager(1811): #4: Window{6293492 u0 Application Error: com.getpebble.android.basalt:ui}
11-26 06:51:19.392 F/DEBUG (5967): pid: 5896, tid: 5952, name: ion-ion >>> com.getpebble.android.basalt:framework <<<
11-26 06:51:19.420 F/DEBUG (5967): #5 pc 0003b14f /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:51:19.420 F/DEBUG (5967): #6 pc 0003af6b /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:51:19.420 F/DEBUG (5967): #7 pc 0003aec3 /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:51:20.515 W/ActivityManager(1811): Process com.getpebble.android.basalt:ui has crashed too many times: killing!
11-26 06:51:20.515 I/ActivityManager(1811): Killing 5896:com.getpebble.android.basalt:framework/u0a231 (adj 100): crash
11-26 06:51:20.614 W/ActivityManager(1811): Ignoring remove of inactive process: ProcessRecord{d5d869d 0:com.getpebble.android.basalt:ui/u0a231}
11-26 06:52:27.211 I/ActivityManager(1811): Start proc 6272:com.getpebble.android.basalt:framework/u0a231 for service com.getpebble.android.basalt/com.getpebble.android.core.sync.PebbleSyncService
11-26 06:52:29.821 F/DEBUG (6301): pid: 6272, tid: 6299, name: ion-ion >>> com.getpebble.android.basalt:framework <<<
11-26 06:52:29.852 F/DEBUG (6301): #5 pc 0003b14f /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:52:29.852 F/DEBUG (6301): #6 pc 0003af6b /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:52:29.852 F/DEBUG (6301): #7 pc 0003aec3 /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:52:31.127 I/ActivityManager(1811): Process com.getpebble.android.basalt:framework (pid 6272) has died
11-26 06:52:31.128 W/ActivityManager(1811): Scheduling restart of crashed service com.getpebble.android.basalt/com.getpebble.android.core.sync.PebbleSyncService in 1000ms
11-26 06:52:32.561 W/ActivityManager(1811): Ignoring remove of inactive process: ProcessRecord{219c3c4 0:com.getpebble.android.basalt:framework/u0a231}
11-26 06:52:37.278 I/ActivityManager(1811): Start proc 6335:com.getpebble.android.basalt:framework/u0a231 for service com.getpebble.android.basalt/com.getpebble.android.core.sync.PebbleSyncService
11-26 06:52:39.921 F/DEBUG (6367): pid: 6335, tid: 6364, name: ion-ion >>> com.getpebble.android.basalt:framework <<<
11-26 06:52:39.955 F/DEBUG (6367): #5 pc 0003b14f /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:52:39.955 F/DEBUG (6367): #6 pc 0003af6b /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:52:39.955 F/DEBUG (6367): #7 pc 0003aec3 /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:52:40.944 I/ActivityManager(1811): Process com.getpebble.android.basalt:framework (pid 6335) has died
11-26 06:52:40.944 W/ActivityManager(1811): Scheduling restart of crashed service com.getpebble.android.basalt/com.getpebble.android.core.sync.PebbleSyncService in 1000ms
11-26 06:52:42.928 W/ActivityManager(1811): Ignoring remove of inactive process: ProcessRecord{18843d6 0:com.getpebble.android.basalt:framework/u0a231}
11-26 06:53:20.748 I/ActivityManager(1811): Start proc 6450:com.getpebble.android.basalt:framework/u0a231 for service com.getpebble.android.basalt/com.getpebble.android.core.sync.PebbleSyncService
11-26 06:53:23.655 F/DEBUG (6535): pid: 6450, tid: 6513, name: ion-ion >>> com.getpebble.android.basalt:framework <<<
11-26 06:53:23.693 F/DEBUG (6535): #5 pc 0003b14f /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:53:23.693 F/DEBUG (6535): #6 pc 0003af6b /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:53:23.693 F/DEBUG (6535): #7 pc 0003aec3 /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:53:24.571 I/ActivityManager(1811): Process com.getpebble.android.basalt:framework (pid 6450) has died
11-26 06:53:24.571 W/ActivityManager(1811): Scheduling restart of crashed service com.getpebble.android.basalt/com.getpebble.android.core.sync.PebbleSyncService in 1000ms
11-26 06:53:24.881 W/ActivityManager(1811): Ignoring remove of inactive process: ProcessRecord{c5976c6 0:com.getpebble.android.basalt:framework/u0a231}
11-26 06:53:31.204 I/ActivityManager(1811): Start proc 6561:com.getpebble.android.basalt:framework/u0a231 for service com.getpebble.android.basalt/com.getpebble.android.core.sync.PebbleSyncService
11-26 06:53:34.047 F/DEBUG (6607): pid: 6561, tid: 6596, name: ion-ion >>> com.getpebble.android.basalt:framework <<<
11-26 06:53:34.092 F/DEBUG (6607): #5 pc 0003b14f /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:53:34.092 F/DEBUG (6607): #6 pc 0003af6b /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:53:34.092 F/DEBUG (6607): #7 pc 0003aec3 /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:53:35.294 I/ActivityManager(1811): Process com.getpebble.android.basalt:framework (pid 6561) has died
11-26 06:53:35.294 W/ActivityManager(1811): Scheduling restart of crashed service com.getpebble.android.basalt/com.getpebble.android.core.sync.PebbleSyncService in 1000ms
11-26 06:53:37.016 W/ActivityManager(1811): Ignoring remove of inactive process: ProcessRecord{ce29ea2 0:com.getpebble.android.basalt:framework/u0a231}
11-26 06:53:41.560 I/ActivityManager(1811): Start proc 6626:com.getpebble.android.basalt:framework/u0a231 for service com.getpebble.android.basalt/com.getpebble.android.core.sync.PebbleSyncService
11-26 06:53:44.295 F/DEBUG (6663): pid: 6626, tid: 6655, name: ion-ion >>> com.getpebble.android.basalt:framework <<<
11-26 06:53:44.334 F/DEBUG (6663): #5 pc 0003b14f /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:53:44.334 F/DEBUG (6663): #6 pc 0003af6b /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:53:44.334 F/DEBUG (6663): #7 pc 0003aec3 /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:53:45.362 I/ActivityManager(1811): Process com.getpebble.android.basalt:framework (pid 6626) has died
11-26 06:53:45.363 W/ActivityManager(1811): Scheduling restart of crashed service com.getpebble.android.basalt/com.getpebble.android.core.sync.PebbleSyncService in 1000ms
11-26 06:53:46.520 W/ActivityManager(1811): Ignoring remove of inactive process: ProcessRecord{6b95a0c 0:com.getpebble.android.basalt:framework/u0a231}
11-26 06:53:51.882 I/ActivityManager(1811): Start proc 6691:com.getpebble.android.basalt:framework/u0a231 for service com.getpebble.android.basalt/com.getpebble.android.core.sync.PebbleSyncService
11-26 06:53:54.555 F/DEBUG (6725): pid: 6691, tid: 6723, name: ion-ion >>> com.getpebble.android.basalt:framework <<<
11-26 06:53:54.615 F/DEBUG (6725): #5 pc 0003b14f /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:53:54.615 F/DEBUG (6725): #6 pc 0003af6b /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:53:54.615 F/DEBUG (6725): #7 pc 0003aec3 /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:53:55.627 I/ActivityManager(1811): Process com.getpebble.android.basalt:framework (pid 6691) has died
11-26 06:53:55.627 W/ActivityManager(1811): Scheduling restart of crashed service com.getpebble.android.basalt/com.getpebble.android.core.sync.PebbleSyncService in 1000ms
11-26 06:53:56.714 W/ActivityManager(1811): Ignoring remove of inactive process: ProcessRecord{eaf622d 0:com.getpebble.android.basalt:framework/u0a231}
11-26 06:54:02.280 I/ActivityManager(1811): Start proc 6746:com.getpebble.android.basalt:framework/u0a231 for service com.getpebble.android.basalt/com.getpebble.android.core.sync.PebbleSyncService
11-26 06:54:04.807 F/DEBUG (6779): pid: 6746, tid: 6773, name: ion-ion >>> com.getpebble.android.basalt:framework <<<
11-26 06:54:04.847 F/DEBUG (6779): #5 pc 0003b14f /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:54:04.847 F/DEBUG (6779): #6 pc 0003af6b /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:54:04.848 F/DEBUG (6779): #7 pc 0003aec3 /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:54:05.751 I/ActivityManager(1811): Process com.getpebble.android.basalt:framework (pid 6746) has died
11-26 06:54:05.751 W/ActivityManager(1811): Scheduling restart of crashed service com.getpebble.android.basalt/com.getpebble.android.core.sync.PebbleSyncService in 1000ms
11-26 06:54:07.017 W/ActivityManager(1811): Ignoring remove of inactive process: ProcessRecord{7a8586 0:com.getpebble.android.basalt:framework/u0a231}
11-26 06:54:12.686 I/ActivityManager(1811): Start proc 6803:com.getpebble.android.basalt:framework/u0a231 for service com.getpebble.android.basalt/com.getpebble.android.core.sync.PebbleSyncService
11-26 06:54:15.091 F/DEBUG (6842): pid: 6803, tid: 6832, name: ion-ion >>> com.getpebble.android.basalt:framework <<<
11-26 06:54:15.129 F/DEBUG (6842): #5 pc 0003b14f /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:54:15.129 F/DEBUG (6842): #6 pc 0003af6b /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:54:15.129 F/DEBUG (6842): #7 pc 0003aec3 /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:54:16.206 I/ActivityManager(1811): Process com.getpebble.android.basalt:framework (pid 6803) has died
11-26 06:54:16.206 W/ActivityManager(1811): Scheduling restart of crashed service com.getpebble.android.basalt/com.getpebble.android.core.sync.PebbleSyncService in 1000ms
11-26 06:54:17.602 W/ActivityManager(1811): Ignoring remove of inactive process: ProcessRecord{a482a5e 0:com.getpebble.android.basalt:framework/u0a231}
11-26 06:54:23.063 I/ActivityManager(1811): Start proc 6875:com.getpebble.android.basalt:framework/u0a231 for service com.getpebble.android.basalt/com.getpebble.android.core.sync.PebbleSyncService
11-26 06:54:25.640 F/DEBUG (6907): pid: 6875, tid: 6904, name: ion-ion >>> com.getpebble.android.basalt:framework <<<
11-26 06:54:25.692 F/DEBUG (6907): #5 pc 0003b14f /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:54:25.692 F/DEBUG (6907): #6 pc 0003af6b /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:54:25.692 F/DEBUG (6907): #7 pc 0003aec3 /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:54:26.656 I/ActivityManager(1811): Process com.getpebble.android.basalt:framework (pid 6875) has died
11-26 06:54:26.656 W/ActivityManager(1811): Scheduling restart of crashed service com.getpebble.android.basalt/com.getpebble.android.core.sync.PebbleSyncService in 1000ms
11-26 06:54:27.924 W/ActivityManager(1811): Ignoring remove of inactive process: ProcessRecord{55db8c6 0:com.getpebble.android.basalt:framework/u0a231}
11-26 06:54:33.478 I/ActivityManager(1811): Start proc 6943:com.getpebble.android.basalt:framework/u0a231 for service com.getpebble.android.basalt/com.getpebble.android.core.sync.PebbleSyncService
11-26 06:54:35.865 F/DEBUG (6989): pid: 6943, tid: 6970, name: ion-ion >>> com.getpebble.android.basalt:framework <<<
11-26 06:54:35.913 F/DEBUG (6989): #5 pc 0003b14f /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:54:35.913 F/DEBUG (6989): #6 pc 0003af6b /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:54:35.914 F/DEBUG (6989): #7 pc 0003aec3 /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:54:37.035 I/ActivityManager(1811): Process com.getpebble.android.basalt:framework (pid 6943) has died
11-26 06:54:37.036 W/ActivityManager(1811): Scheduling restart of crashed service com.getpebble.android.basalt/com.getpebble.android.core.sync.PebbleSyncService in 1000ms
11-26 06:54:38.218 W/ActivityManager(1811): Ignoring remove of inactive process: ProcessRecord{2d8c560 0:com.getpebble.android.basalt:framework/u0a231}
11-26 06:54:43.890 I/ActivityManager(1811): Start proc 7031:com.getpebble.android.basalt:framework/u0a231 for service com.getpebble.android.basalt/com.getpebble.android.core.sync.PebbleSyncService
11-26 06:54:46.357 F/DEBUG (7061): pid: 7031, tid: 7059, name: ion-ion >>> com.getpebble.android.basalt:framework <<<
11-26 06:54:46.414 F/DEBUG (7061): #5 pc 0003b14f /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:54:46.414 F/DEBUG (7061): #6 pc 0003af6b /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:54:46.414 F/DEBUG (7061): #7 pc 0003aec3 /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:54:47.344 I/ActivityManager(1811): Process com.getpebble.android.basalt:framework (pid 7031) has died
11-26 06:54:47.344 W/ActivityManager(1811): Scheduling restart of crashed service com.getpebble.android.basalt/com.getpebble.android.core.sync.PebbleSyncService in 1000ms
11-26 06:54:48.571 W/ActivityManager(1811): Ignoring remove of inactive process: ProcessRecord{cf38044 0:com.getpebble.android.basalt:framework/u0a231}
11-26 06:54:54.456 I/ActivityManager(1811): Start proc 7082:com.getpebble.android.basalt:framework/u0a231 for service com.getpebble.android.basalt/com.getpebble.android.core.sync.PebbleSyncService
11-26 06:54:57.236 F/DEBUG (7114): pid: 7082, tid: 7111, name: ion-ion >>> com.getpebble.android.basalt:framework <<<
11-26 06:54:57.274 F/DEBUG (7114): #5 pc 0003b14f /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:54:57.274 F/DEBUG (7114): #6 pc 0003af6b /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:54:57.274 F/DEBUG (7114): #7 pc 0003aec3 /data/data/com.getpebble.android.basalt/cache/.gmscore/lib/armeabi-v7a/libconscrypt_jni.so
11-26 06:54:58.408 I/ActivityManager(1811): Process com.getpebble.android.basalt:framework (pid 7082) has died
11-26 06:54:58.408 W/ActivityManager(1811): Scheduling restart of crashed service com.getpebble.android.basalt/com.getpebble.android.core.sync.PebbleSyncService in 1000ms
11-26 06:54:59.553 W/ActivityManager(1811): Ignoring remove of inactive process: ProcessRecord{cb7c055 0:com.getpebble.android.basalt:framework/u0a231}
11-26 06:55:05.207 I/ActivityManager(1811): Start proc 7152:com.getpebble.android.basalt:framework/u0a231 for service com.getpebble.android.basalt/com.getpebble.android.core.sync.PebbleSyncService
11-26 06:56:06.637 I/ActivityManager(1811): Killing 7152:com.getpebble.android.basalt:framework/u0a231 (adj 200): stop com.google.android.gms
11-26 06:56:06.639 W/ActivityManager(1811): Scheduling restart of crashed service com.getpebble.android.basalt/com.getpebble.android.framework.timeline.TimelineWebSyncService in 93460ms
11-26 06:57:40.224 I/ActivityManager(1811): Start proc 8067:com.getpebble.android.basalt:framework/u0a231 for service com.getpebble.android.basalt/com.getpebble.android.framework.timeline.TimelineWebSyncService
11-26 07:53:51.038 E/ActivityManager(1811): 0.1% 8067/com.getpebble.android.basalt:framework: 0.1% user + 0% kernel / faults: 187 minor
11-26 07:57:06.027 E/ActivityManager(1811): 0% 8067/com.getpebble.android.basalt:framework: 0% user + 0% kernel / faults: 34 minor
11-26 08:02:52.300 E/ActivityManager(1811): 0.6% 8067/com.getpebble.android.basalt:framework: 0.3% user + 0.3% kernel / faults: 8412 minor 85 major
11-26 08:16:06.869 E/Pbl (8067): [ConnectionManager] input problem will prevent further communications from the Pebble

[mar-v-in]

I'm assuming the Pebble app is 32-bit / armv7a and you are using a 64-bit / armv8 device?

[Sapiosenses]

The device is 64-bit (LG v20), but none of the app tools I have display the 32/64 characteristic of an app so I can't answer that. (Can't get it from Aurora as it's distributed direct now - Rebble took the old Pebble app and added slight mods to it and distributes it direct now)

I can tell you that the minimum API level is listed as 18 and target is 22. I suspect it's 32-bit.

Also, I think they recently released an update to it but haven't tried that yet.

[Sapiosenses]

Verified the app version I have is the latest, they distribute it from here:

https://www.apkmirror.com/apk/pebble-technology-corp/pebble/pebble-4-4-2-1405-62d45d7d7-endframe-release/pebble-4-4-2-1405-62d45d7d7-endframe-android-apk-download/download/

[mar-v-in]

@Sapiosenses can you try again with https://microg.org/dl/core-conscrypt-jni-fix.apk?

[Sapiosenses]

@Sapiosenses can you try again with https://microg.org/dl/core-conscrypt-jni-fix.apk?

Sure.

I normally use F-droid for these updates. This device was originally LineageOS for microG, the original, very old APK is in /system/priv-app/GmsCore, I assume I should copy this into /data/app? Should I create a GmsCore folder there to hold it? Or "org.microg..."?

(Looks like the currently running F-droid copy is in /data/app/com.google.android.gms-1/)

[mar-v-in]

@Sapiosenses you can just install the apk from the running system using normal apk installation flow. It should install as a normal update to the existing microG apl. No need to edit anything on the file system manually.

[Sapiosenses]

Used the regular installer, installed as an update to the original system app.

Self-check is all ticked, version shows 0.2.14.204215-1 (0b6f929)

Pebble seems to be running OK so far, waiting for the watch to sync.

[Sapiosenses]

As far as I can tell, it's OK.

Definitely not causing the constant crashes that happened before. I don't have current watch data because haven't been wearing it for a few days.

👍

[Sapiosenses]

@mar-v-in App is collecting data normally.

Thanks for everything you do Marvin. (BTW I answer microG questions for people on a Telegram group devoted to microG)

Thanks much. You can close this issue as you like.

[mar-v-in]

Great. Fixed via 0b6f929