No you don’t. It’s reinstalled after each update (in the addons.d IIRC).
1 Like
The case has been closed by the LineageOS developers: SurfaceFlinger crashes sometimes (#2475) · Issues · LineageOS / issues / android · GitLab
Thanks for keeping this updated. Since it is neither a LineageOS specific issue nor fixable by us, I am closing this.
How to solve this issue ?
Hello !
I have a similar issue with a high-ressource-consuming game, i.e. Pokémon Go.
The game launch, it is possible to play for 5-10 minutes (sometimes less) and then suddenly all is cleared up. The phone doesn’t reboot, but all applications running disappear and have to be restarted (e.g. the web browser loose the current webpages and have to reload them).
I looked up at the logcat, but the only thing I see is that one process crashes (ActivityManager: Process [xxx] has died) then all the others are killed (Zygote : Process [yyy] exited due to signal 9 (Killed)) afterall.
Logcat crash #1
09-16 11:20:41.564 749 3299 I ActivityManager: Process android.process.media (pid 6054) has died: cch+35 CEM
09-16 11:20:41.578 289 289 I Zygote : Process 6054 exited due to signal 9 (Killed)
09-16 11:20:41.621 289 289 I Zygote : Process 8735 exited due to signal 9 (Killed)
09-16 11:20:41.641 289 289 I Zygote : Process 8886 exited due to signal 9 (Killed)
09-16 11:20:41.650 289 289 I Zygote : Process 7153 exited due to signal 9 (Killed)
09-16 11:20:41.662 289 289 I Zygote : Process 6327 exited due to signal 9 (Killed)
09-16 11:20:41.688 289 289 I Zygote : Process 6746 exited due to signal 9 (Killed)
09-16 11:20:41.699 749 3227 I ActivityManager: Process com.google.android.gms.unstable (pid 7153) has died: cch+25 CEM
09-16 11:20:41.700 749 793 I chatty : uid=1000(system) ActivityManager expire 17 lines
09-16 11:20:41.704 749 5367 I ActivityManager: Process com.android.cellbroadcastreceiver (pid 8735) has died: cch+15 CEM
09-16 11:20:41.711 289 289 I Zygote : Process 5285 exited due to signal 9 (Killed)
09-16 11:20:41.728 5422 5422 I Finsky : [2] rrg.onTrimMemory(1): Memory trim requested to level 15
09-16 11:20:41.748 289 289 I Zygote : Process 10395 exited due to signal 9 (Killed)
09-16 11:20:41.750 749 3299 I ActivityManager: Process com.google.process.gservices (pid 5285) has died: prev LAST
09-16 11:20:41.753 749 3592 I ActivityManager: Process com.android.email (pid 6327) has died: svcb SVC
09-16 11:20:41.762 749 3592 W ActivityManager: Scheduling restart of crashed service com.android.email/.service.LegacyImapSyncAdapterService in 1000ms
09-16 11:20:41.763 749 3592 W ActivityManager: Scheduling restart of crashed service com.android.email/.service.ImapService in 11000ms
09-16 11:20:41.765 749 11990 I ActivityManager: Process com.qualcomm.qcrilmsgtunnel (pid 6746) has died: svcb SVC
09-16 11:20:41.765 749 11990 W ActivityManager: Scheduling restart of crashed service com.qualcomm.qcrilmsgtunnel/.QcrilMsgTunnelService in 20997ms
09-16 11:20:41.766 749 783 W Looper : Slow dispatch took 187ms android.ui h=com.android.server.am.ActivityManagerService$UiHandler c=null m=53
09-16 11:20:41.767 749 3228 I ActivityManager: Process com.android.permissioncontroller (pid 8886) has died: cch+5 CEM
09-16 11:20:41.769 749 3577 I ActivityManager: Process com.google.process.gapps (pid 10395) has died: prev LAST
09-16 11:20:41.778 749 5366 D ConnectivityService: ConnectivityService NetworkRequestInfo binderDied(NetworkRequest [ TRACK_DEFAULT id=24, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10125] ], android.os.BinderProxy@306fcd9)
09-16 11:20:41.779 749 2791 D ConnectivityService: releasing NetworkRequest [ TRACK_DEFAULT id=24, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10125] ] (release request)
09-16 11:20:41.780 749 781 I ActivityManager: Process com.whatsapp (pid 7493) has died: svc SVC
09-16 11:20:41.780 749 781 W ActivityManager: Scheduling restart of crashed service com.whatsapp/.messaging.MessageService in 30982ms
09-16 11:20:41.785 289 289 I Zygote : Process 7493 exited due to signal 9 (Killed)
09-16 11:20:41.789 3021 3021 V KeyguardUpdateMonitor: onSubscriptionInfoChanged()
09-16 11:20:41.792 3021 3021 V KeyguardUpdateMonitor: SubInfo:{id=2, iccId=893935007[] simSlotIndex=0 carrierId=-1 displayName=Lycamobile carrierName=Lycamobile nameSource=1 iconTint=-13408298 mNumber= dataRoaming=1 iconBitmap=android.graphics.Bitmap@269776f mcc 222 mnc 35mCountryIso=it isEmbedded false nativeAccessRules null cardString=893935007[] cardId=-1 isOpportunistic false mGroupUUID=null mIsGroupDisabled=false profileClass=-1 ehplmns = hplmns = [22210, 20408, 50501, 21407, 24202, 23820, 23866, 24008, 24004, 24024, 26202, 26204, 26209, 26001, 27202, 20820, 20888, 22801, 26801, 20610, 310260, 23410, 23201, 22603, 22606, 45403, 45404] subscriptionType=0 mGroupOwner=null carrierConfigAccessRules=null}
09-16 11:20:41.792 3021 3021 V KeyguardUpdateMonitor: SubInfo:{id=1, iccId=893203000[] simSlotIndex=1 carrierId=1367 displayName=CARREFOUR carrierName=WINDTRE — CARREFOUR nameSource=1 iconTint=-16746133 mNumber= dataRoaming=1 iconBitmap=android.graphics.Bitmap@825dc7c mcc 206 mnc 20mCountryIso=be isEmbedded false nativeAccessRules null cardString=893203000[] cardId=-1 isOpportunistic false mGroupUUID=null mIsGroupDisabled=false profileClass=-1 ehplmns = hplmns = subscriptionType=0 mGroupOwner=null carrierConfigAccessRules=null}
09-16 11:20:41.811 749 5367 I ActivityManager: Process com.fsck.k9 (pid 6922) has died: svc SVC
09-16 11:20:41.812 749 5367 W ActivityManager: Scheduling restart of crashed service com.fsck.k9/.service.PushService in 40951ms
09-16 11:20:41.816 289 289 I Zygote : Process 6922 exited due to signal 9 (Killed)
09-16 11:20:41.838 749 11989 I ActivityManager: Process com.android.inputmethod.latin (pid 3511) has died: prcp IMPB
09-16 11:20:41.840 749 11991 I WindowManager: WIN DEATH: Window{bdfa2da u0 InputMethod}
09-16 11:20:41.844 749 11989 W ActivityManager: Scheduling restart of crashed service com.android.inputmethod.latin/.LatinIME in 50920ms
09-16 11:20:41.846 289 289 I Zygote : Process 3511 exited due to signal 9 (Killed)
09-16 11:20:41.864 749 785 W ActivityManager: setHasOverlayUi called on unknown pid: 3511
09-16 11:20:41.868 749 3299 I ActivityManager: Process org.telegram.messenger (pid 7911) has died: prcp FGS
09-16 11:20:41.869 749 3299 W ActivityManager: Scheduling restart of crashed service org.telegram.messenger/.NotificationsService in 60894ms
09-16 11:20:41.871 749 782 W Looper : Slow dispatch took 331ms android.fg h=android.os.Handler c=java.util.concurrent.FutureTask@3d9f69e m=0
09-16 11:20:41.872 749 782 W Looper : Slow delivery took 323ms android.fg h=com.android.server.location.GnssLocationProvider$ProviderHandler c=null m=18
09-16 11:20:41.873 289 289 I Zygote : Process 7911 exited due to signal 9 (Killed)
09-16 11:20:41.901 749 3582 D ConnectivityService: ConnectivityService NetworkRequestInfo binderDied(NetworkRequest [ LISTEN id=23, [ Capabilities: NOT_RESTRICTED Uid: 10023] ], android.os.BinderProxy@926557f)
09-16 11:20:41.902 749 3592 I ActivityManager: Process com.google.android.gms.persistent (pid 4042) has died: vis BTOP
09-16 11:20:41.904 749 3592 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.deviceconnection.service.DeviceConnectionWatcherService in 70860ms
09-16 11:20:41.904 749 3592 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.chimera.PersistentDirectBootAwareApiService in 80859ms
09-16 11:20:41.904 749 3592 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/com.google.android.contextmanager.service.ContextManagerService in 90859ms
09-16 11:20:41.904 749 3592 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.location.persistent.LocationPersistentService in 100859ms
09-16 11:20:41.905 749 3592 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/com.google.android.location.internal.PendingIntentCallbackService in 110859ms
09-16 11:20:41.905 749 3592 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.nearby.sharing.ReceiveSurfaceService in 110859ms
09-16 11:20:41.906 749 3592 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.clearcut.debug.ClearcutDebugDumpService in 120858ms
09-16 11:20:41.906 749 3592 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/com.google.android.location.internal.server.HardwareArProviderService in 130858ms
09-16 11:20:41.906 749 3592 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/com.google.android.location.internal.server.GoogleLocationService in 140857ms
09-16 11:20:41.906 749 3592 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/com.google.android.location.geofencer.service.GeofenceProviderService in 150857ms
09-16 11:20:41.906 749 3592 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.thunderbird.EmergencyPersistentService in 160857ms
09-16 11:20:41.906 749 3592 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.nearby.exposurenotification.service.ExposureMatchingService in 170857ms
09-16 11:20:41.907 749 3592 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.gcm.nts.SchedulerService in 180857ms
09-16 11:20:41.907 749 3592 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.fitness.service.history.FitHistoryBroker in 190856ms
09-16 11:20:41.907 749 3592 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/com.google.android.location.fused.FusedLocationService in 200856ms
09-16 11:20:41.907 749 3592 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.auth.setup.devicesignals.LockScreenService in 210856ms
09-16 11:20:41.907 749 3592 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/com.google.android.location.internal.GoogleLocationManagerService in 220856ms
09-16 11:20:41.908 749 3592 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/com.google.android.location.network.NetworkLocationService in 230856ms
09-16 11:20:41.908 749 3592 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.fido.fido2.pollux.CableAuthenticatorService in 240856ms
09-16 11:20:41.908 749 3592 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.common.stats.GmsCoreStatsService in 250855ms
09-16 11:20:41.908 749 3592 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.fitness.service.recording.FitRecordingBroker in 260855ms
09-16 11:20:41.908 749 3592 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.gcm.GcmService in 270855ms
09-16 11:20:41.909 749 3592 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/com.google.android.location.geocode.GeocodeService in 280855ms
09-16 11:20:41.938 749 11991 D ConnectivityService: ConnectivityService NetworkRequestInfo binderDied(NetworkRequest [ LISTEN id=27, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10023] ], android.os.BinderProxy@c618d95)
09-16 11:20:41.940 749 5367 I ActivityManager: Process com.google.android.gms (pid 5204) has died: vis BTOP
09-16 11:20:41.941 749 3577 D ConnectivityService: ConnectivityService NetworkRequestInfo binderDied(NetworkRequest [ LISTEN id=21, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN Uid: 10023] ], android.os.BinderProxy@4eadeaa)
09-16 11:20:41.942 749 5367 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.chimera.GmsApiService in 290822ms
09-16 11:20:41.942 749 3592 D ConnectivityService: ConnectivityService NetworkRequestInfo binderDied(NetworkRequest [ TRACK_DEFAULT id=26, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10023] ], android.os.BinderProxy@954ca9b)
09-16 11:20:41.942 749 2806 D NsdService: Client disconnected
09-16 11:20:41.942 749 2791 D ConnectivityService: releasing NetworkRequest [ TRACK_DEFAULT id=26, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10023] ] (release request)
09-16 11:20:41.942 749 5367 W ActivityManager: Scheduling restart of crashed service com.google.android.gms/.chimera.GmsBoundBrokerService in 300821ms
09-16 11:20:41.948 3021 3021 V KeyguardUpdateMonitor: onSubscriptionInfoChanged()
09-16 11:20:41.953 3021 3021 V KeyguardUpdateMonitor: SubInfo:{id=2, iccId=893935007[] simSlotIndex=0 carrierId=-1 displayName=Lycamobile carrierName=Lycamobile nameSource=1 iconTint=-13408298 mNumber= dataRoaming=1 iconBitmap=android.graphics.Bitmap@534d905 mcc 222 mnc 35mCountryIso=it isEmbedded false nativeAccessRules null cardString=893935007[] cardId=-1 isOpportunistic false mGroupUUID=null mIsGroupDisabled=false profileClass=-1 ehplmns = hplmns = [22210, 20408, 50501, 21407, 24202, 23820, 23866, 24008, 24004, 24024, 26202, 26204, 26209, 26001, 27202, 20820, 20888, 22801, 26801, 20610, 310260, 23410, 23201, 22603, 22606, 45403, 45404] subscriptionType=0 mGroupOwner=null carrierConfigAccessRules=null}
09-16 11:20:41.953 3021 3021 V KeyguardUpdateMonitor: SubInfo:{id=1, iccId=893203000[] simSlotIndex=1 carrierId=1367 displayName=CARREFOUR carrierName=WINDTRE — CARREFOUR nameSource=1 iconTint=-16746133 mNumber= dataRoaming=1 iconBitmap=android.graphics.Bitmap@7e1d5a mcc 206 mnc 20mCountryIso=be isEmbedded false nativeAccessRules null cardString=893203000[] cardId=-1 isOpportunistic false mGroupUUID=null mIsGroupDisabled=false profileClass=-1 ehplmns = hplmns = subscriptionType=0 mGroupOwner=null carrierConfigAccessRules=null}
09-16 11:20:41.956 749 2806 D NsdService: mdnssd [stop-service]
09-16 11:20:41.957 288 462 D MDnsDS : Stopping MDNSD
09-16 11:20:41.961 289 289 I Zygote : Process 4042 exited due to signal 9 (Killed)
09-16 11:20:41.974 749 5366 I WindowManager: WIN DEATH: Window{a25c6fc u0 com.android.launcher3/com.android.launcher3.lineage.LineageLauncher}
09-16 11:20:41.974 749 3467 I ActivityManager: Process com.android.launcher3 (pid 3388) has died: vis BFGS
09-16 11:20:41.979 749 3467 W ActivityManager: Scheduling restart of crashed service com.android.launcher3/.notification.NotificationListener in 310784ms
09-16 11:20:41.980 749 3467 W ActivityManager: Scheduling restart of crashed service com.android.launcher3/com.android.quickstep.TouchInteractionService in 320784ms
09-16 11:20:41.991 289 289 I Zygote : Process 3388 exited due to signal 9 (Killed)
09-16 11:20:42.002 749 5366 D ConnectivityService: ConnectivityService NetworkRequestInfo binderDied(NetworkRequest [ TRACK_DEFAULT id=19, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10016] ], android.os.BinderProxy@59a6e11)
09-16 11:20:42.002 749 11994 D ConnectivityService: ConnectivityService NetworkRequestInfo binderDied(NetworkRequest [ LISTEN id=20, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10016] ], android.os.BinderProxy@2703b76)
09-16 11:20:42.003 749 2791 D ConnectivityService: releasing NetworkRequest [ TRACK_DEFAULT id=19, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10016] ] (release request)
09-16 11:20:42.008 289 289 I Zygote : Process 5422 exited due to signal 9 (Killed)
09-16 11:20:42.024 289 289 I Zygote : Process 10904 exited due to signal 9 (Killed)
09-16 11:20:42.032 289 289 I Zygote : Process 5204 exited due to signal 9 (Killed)
09-16 11:20:42.044 289 289 I Zygote : Process 5359 exited due to signal 9 (Killed)
09-16 11:20:42.069 749 785 W ActivityManager: setHasOverlayUi called on unknown pid: 3388
09-16 11:20:42.069 749 781 D NotificationListeners: Removing active service ComponentInfo{com.android.launcher3/com.android.launcher3.notification.NotificationListener}
09-16 11:20:42.070 749 3155 I ActivityManager: Process com.android.vending (pid 5422) has died: vis BTOP
09-16 11:20:42.071 749 3155 W ActivityManager: Scheduling restart of crashed service com.android.vending/com.google.android.finsky.billing.iab.InAppBillingService in 330693ms
09-16 11:20:42.071 749 3155 W ActivityManager: Scheduling restart of crashed service com.android.vending/com.google.android.finsky.installservice.InstallService in 340693ms
09-16 11:20:42.073 749 3299 I ActivityManager: Process com.nianticlabs.pokemongo:pgp (pid 10904) has died: vis BTOP
09-16 11:20:42.073 749 3299 W ActivityManager: Scheduling restart of crashed service com.nianticlabs.pokemongo/com.nianticlabs.pokemongoplus.service.BackgroundService in 350690ms
09-16 11:20:42.074 749 3577 I ActivityManager: Process com.android.smspush (pid 5359) has died: vis IMPF
09-16 11:20:42.075 749 3577 W ActivityManager: Scheduling restart of crashed service com.android.smspush/.WapPushManager in 360689ms
09-16 11:20:42.109 3221 3254 I m.android.phon: Background young concurrent copying GC freed 45052(5883KB) AllocSpace objects, 4(64KB) LOS objects, 73% free, 2223KB/8282KB, paused 151us total 164.631ms
09-16 11:20:42.121 288 288 I netd : bandwidthRemoveNiceApp(10016) <30.32ms>
09-16 11:20:42.128 288 460 I netd : bandwidthAddNaughtyApp(10016) <5.61ms>
09-16 11:20:42.141 749 11990 I chatty : uid=1000(system) Binder:749_11 expire 1 line
09-16 11:20:42.167 749 749 W InputMethodManagerService: Session failed to close due to remote exception
09-16 11:20:42.167 749 749 W InputMethodManagerService: android.os.DeadObjectException
09-16 11:20:42.167 749 749 W InputMethodManagerService: at android.os.BinderProxy.transactNative(Native Method)
09-16 11:20:42.167 749 749 W InputMethodManagerService: at android.os.BinderProxy.transact(BinderProxy.java:511)
09-16 11:20:42.167 749 749 W InputMethodManagerService: at com.android.internal.view.IInputMethodSession$Stub$Proxy.finishSession(IInputMethodSession.java:419)
09-16 11:20:42.167 749 749 W InputMethodManagerService: at com.android.server.inputmethod.InputMethodManagerService.finishSessionLocked(InputMethodManagerService.java:2366)
09-16 11:20:42.167 749 749 W InputMethodManagerService: at com.android.server.inputmethod.InputMethodManagerService.clearClientSessionLocked(InputMethodManagerService.java:2357)
09-16 11:20:42.167 749 749 W InputMethodManagerService: at com.android.server.inputmethod.InputMethodManagerService.clearCurMethodLocked(InputMethodManagerService.java:2384)
09-16 11:20:42.167 749 749 W InputMethodManagerService: at com.android.server.inputmethod.InputMethodManagerService.onServiceDisconnected(InputMethodManagerService.java:2411)
09-16 11:20:42.167 749 749 W InputMethodManagerService: at android.app.LoadedApk$ServiceDispatcher.doDeath(LoadedApk.java:1972)
09-16 11:20:42.167 749 749 W InputMethodManagerService: at android.app.LoadedApk$ServiceDispatcher$RunConnection.run(LoadedApk.java:1987)
09-16 11:20:42.167 749 749 W InputMethodManagerService: at android.os.Handler.handleCallback(Handler.java:883)
09-16 11:20:42.167 749 749 W InputMethodManagerService: at android.os.Handler.dispatchMessage(Handler.java:100)
09-16 11:20:42.167 749 749 W InputMethodManagerService: at android.os.Looper.loop(Looper.java:214)
09-16 11:20:42.167 749 749 W InputMethodManagerService: at com.android.server.SystemServer.run(SystemServer.java:558)
09-16 11:20:42.167 749 749 W InputMethodManagerService: at com.android.server.SystemServer.main(SystemServer.java:356)
09-16 11:20:42.167 749 749 W InputMethodManagerService: at java.lang.reflect.Method.invoke(Native Method)
09-16 11:20:42.167 749 749 W InputMethodManagerService: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:491)
09-16 11:20:42.167 749 749 W InputMethodManagerService: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:918)
09-16 11:20:42.168 749 749 W InputMethodManagerService: Session failed to close due to remote exception
09-16 11:20:42.168 749 749 W InputMethodManagerService: android.os.DeadObjectException
09-16 11:20:42.168 749 749 W InputMethodManagerService: at android.os.BinderProxy.transactNative(Native Method)
09-16 11:20:42.168 749 749 W InputMethodManagerService: at android.os.BinderProxy.transact(BinderProxy.java:511)
09-16 11:20:42.168 749 749 W InputMethodManagerService: at com.android.internal.view.IInputMethodSession$Stub$Proxy.finishSession(IInputMethodSession.java:419)
09-16 11:20:42.168 749 749 W InputMethodManagerService: at com.android.server.inputmethod.InputMethodManagerService.finishSessionLocked(InputMethodManagerService.java:2366)
09-16 11:20:42.168 749 749 W InputMethodManagerService: at com.android.server.inputmethod.InputMethodManagerService.clearClientSessionLocked(InputMethodManagerService.java:2357)
09-16 11:20:42.168 749 749 W InputMethodManagerService: at com.android.server.inputmethod.InputMethodManagerService.clearCurMethodLocked(InputMethodManagerService.java:2384)
09-16 11:20:42.168 749 749 W InputMethodManagerService: at com.android.server.inputmethod.InputMethodManagerService.onServiceDisconnected(InputMethodManagerService.java:2411)
09-16 11:20:42.168 749 749 W InputMethodManagerService: at android.app.LoadedApk$ServiceDispatcher.doDeath(LoadedApk.java:1972)
09-16 11:20:42.168 749 749 W InputMethodManagerService: at android.app.LoadedApk$ServiceDispatcher$RunConnection.run(LoadedApk.java:1987)
09-16 11:20:42.168 749 749 W InputMethodManagerService: at android.os.Handler.handleCallback(Handler.java:883)
09-16 11:20:42.168 749 749 W InputMethodManagerService: at android.os.Handler.dispatchMessage(Handler.java:100)
09-16 11:20:42.168 749 749 W InputMethodManagerService: at android.os.Looper.loop(Looper.java:214)
09-16 11:20:42.168 749 749 W InputMethodManagerService: at com.android.server.SystemServer.run(SystemServer.java:558)
09-16 11:20:42.168 749 749 W InputMethodManagerService: at com.android.server.SystemServer.main(SystemServer.java:356)
09-16 11:20:42.168 749 749 W InputMethodManagerService: at java.lang.reflect.Method.invoke(Native Method)
09-16 11:20:42.168 749 749 W InputMethodManagerService: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:491)
09-16 11:20:42.168 749 749 W InputMethodManagerService: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:918)
09-16 11:20:42.169 749 749 W Looper : Slow dispatch took 330ms main h=android.app.ActivityThread$H c=android.app.LoadedApk$ServiceDispatcher$RunConnection@45575e4 m=0
09-16 11:20:42.169 749 749 W Looper : Slow delivery took 304ms main h=com.android.server.job.JobSchedulerService$JobHandler c=null m=7
09-16 11:20:42.185 749 782 W Looper : Slow dispatch took 300ms android.fg h=com.android.server.location.GnssLocationProvider$ProviderHandler c=com.android.server.location.RemoteListenerHelper$HandlerRunnable@4a6da4d m=0
09-16 11:20:42.209 749 749 V NotificationListeners: 0 notification listener connection lost: ComponentInfo{com.android.launcher3/com.android.launcher3.notification.NotificationListener}
09-16 11:20:42.206 749 782 I chatty : uid=1000(system) android.fg expire 32 lines
09-16 11:20:42.227 288 3147 I netd : firewallSetUidRule(2, 10116, 1) <6.80ms>
09-16 11:20:42.239 3021 3021 V KeyguardUpdateMonitor: onSubscriptionInfoChanged()
09-16 11:20:42.240 749 749 W Looper : Drained
09-16 11:20:42.240 749 782 W Looper : Drained
09-16 11:20:42.243 3021 3021 V KeyguardUpdateMonitor: SubInfo:{id=2, iccId=893935007[] simSlotIndex=0 carrierId=-1 displayName=Lycamobile carrierName=Lycamobile nameSource=1 iconTint=-13408298 mNumber= dataRoaming=1 iconBitmap=android.graphics.Bitmap@af23762 mcc 222 mnc 35mCountryIso=it isEmbedded false nativeAccessRules null cardString=893935007[] cardId=-1 isOpportunistic false mGroupUUID=null mIsGroupDisabled=false profileClass=-1 ehplmns = hplmns = [22210, 20408, 50501, 21407, 24202, 23820, 23866, 24008, 24004, 24024, 26202, 26204, 26209, 26001, 27202, 20820, 20888, 22801, 26801, 20610, 310260, 23410, 23201, 22603, 22606, 45403, 45404] subscriptionType=0 mGroupOwner=null carrierConfigAccessRules=null}
09-16 11:20:42.243 3021 3021 V KeyguardUpdateMonitor: SubInfo:{id=1, iccId=893203000[] simSlotIndex=1 carrierId=1367 displayName=CARREFOUR carrierName=WINDTRE — CARREFOUR nameSource=1 iconTint=-16746133 mNumber= dataRoaming=1 iconBitmap=android.graphics.Bitmap@dcda0f3 mcc 206 mnc 20mCountryIso=be isEmbedded false nativeAccessRules null cardString=893203000[] cardId=-1 isOpportunistic false mGroupUUID=null mIsGroupDisabled=false profileClass=-1 ehplmns = hplmns = subscriptionType=0 mGroupOwner=null carrierConfigAccessRules=null}
09-16 11:20:42.269 3021 8331 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
09-16 11:20:42.290 289 289 D Zygote : Forked child process 11995
09-16 11:20:42.295 749 792 W ActivityManager: Slow operation: 68ms so far, now at startProcess: returned from zygote!
09-16 11:20:42.295 749 792 W ActivityManager: Slow operation: 69ms so far, now at startProcess: done updating battery stats
09-16 11:20:42.301 749 792 W ActivityManager: Slow operation: 75ms so far, now at startProcess: building log message
09-16 11:20:42.301 749 792 I ActivityManager: Start proc 11995:com.android.launcher3/u0a19 for service {com.android.launcher3/com.android.quickstep.TouchInteractionService}
09-16 11:20:42.301 749 792 W ActivityManager: Slow operation: 75ms so far, now at startProcess: starting to update pids map
09-16 11:20:42.302 749 792 W ActivityManager: Slow operation: 75ms so far, now at startProcess: done updating pids map
09-16 11:20:42.302 749 792 W ActivityManager: Slow operation: 52ms so far, now at startProcess: asking zygote to start proc
09-16 11:20:42.306 749 11991 I ActivityManager: Process com.nianticlabs.pokemongo (pid 10371) has died: fore TOP
09-16 11:20:42.306 749 3592 I WindowManager: WIN DEATH: Window{9dcc4a2 u0 com.nianticlabs.pokemongo/com.nianticproject.holoholo.libholoholo.unity.UnityMainActivity}
09-16 11:20:42.324 749 11991 W ActivityTaskManager: Force removing ActivityRecord{3966059 u0 com.nianticlabs.pokemongo/com.nianticproject.holoholo.libholoholo.unity.UnityMainActivity t254}: app died, no saved state
09-16 11:20:42.357 11995 11995 E droid.launcher: Not starting debugger since process cannot load the jdwp agent.
09-16 11:20:42.361 289 289 D Zygote : Forked child process 12010
09-16 11:20:42.364 749 792 W ActivityManager: Slow operation: 114ms so far, now at startProcess: returned from zygote!
09-16 11:20:42.496 289 289 I Zygote : Process 10371 exited due to signal 9 (Killed)
09-16 11:20:42.501 749 793 I chatty : uid=1000(system) ActivityManager expire 1 line
09-16 11:20:42.632 749 785 W ActivityManager: setHasOverlayUi called on unknown pid: 10371
09-16 11:20:42.635 749 783 W Looper : Slow dispatch took 312ms android.ui h=com.android.server.am.ActivityManagerService$UiHandler c=null m=53
09-16 11:20:42.636 749 792 W system_server: Long monitor contention with owner Binder:749_12 (11991) at void com.android.server.am.ActivityManagerService$AppDeathRecipient.binderDied()(ActivityManagerService.java:1504) waiters=2 in void com.android.server.am.ProcessList.lambda$startProcessLocked$0$ProcessList(com.android.server.am.ProcessRecord, java.lang.String, int, int, int, int, java.lang.String, java.lang.String, java.lang.String, long) for 269ms
09-16 11:20:42.636 749 783 W Looper : Slow delivery took 304ms android.ui h=com.android.server.wm.BarController$BarHandler c=com.android.server.wm.-$$Lambda$StatusBarController$1$3FiQ0kybPCSlgcNJkCsNm5M12iA@75280ae m=0
09-16 11:20:42.636 749 3592 W system_server: Long monitor contention with owner Binder:749_12 (11991) at void com.android.server.am.ActivityManagerService$AppDeathRecipient.binderDied()(ActivityManagerService.java:1504) waiters=3 in void com.android.server.am.ActivityManagerService.attachApplication(android.app.IApplicationThread, long) for 228ms
09-16 11:20:42.636 749 792 W ActivityManager: Slow operation: 387ms so far, now at startProcess: done updating battery stats
09-16 11:20:42.637 749 792 W ActivityManager: Slow operation: 387ms so far, now at startProcess: building log message
09-16 11:20:42.637 749 792 I ActivityManager: Start proc 12010:com.facebook.mlite/u0a116 for service {com.facebook.mlite/com.facebook.mlite.jobscheduler.LiteJobSchedulerJobSchedulerService}
09-16 11:20:42.637 749 792 W ActivityManager: Slow operation: 387ms so far, now at startProcess: starting to update pids map
09-16 11:20:42.637 749 792 W ActivityManager: Slow operation: 388ms so far, now at startProcess: done updating pids map
09-16 11:20:42.638 749 786 W system_server: Long monitor contention with owner Binder:749_12 (11991) at void com.android.server.wm.ActivityTaskManagerService$LocalService.handleAppDied(com.android.server.wm.WindowProcessController, boolean, java.lang.Runnable)(ActivityTaskManagerService.java:6824) waiters=0 in void com.android.server.wm.WindowAnimator.lambda$new$1$WindowAnimator(long) for 297ms
09-16 11:20:42.640 749 791 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.location.PROVIDERS_CHANGED flg=0x10 (has extras) } to com.google.android.gms/com.google.android.location.internal.NlpNetworkProviderSettingsUpdateReceiver
09-16 11:20:42.643 749 782 W AppOps : Finishing op nesting under-run: uid 10127 pkg com.nianticlabs.pokemongo code 41 time=1600248041901 duration=167832 nesting=0
09-16 11:20:42.687 749 786 E system_server: Invalid ID 0x00000000.
09-16 11:20:42.691 749 782 W Looper : Slow dispatch took 431ms android.fg h=android.os.Handler c=com.android.server.-$$Lambda$LocationManagerService$LocationProvider$nsL4uwojBLPzs1TzMfpQIBSm7p0@8c9f9ba m=0
09-16 11:20:42.691 749 782 W AppOps : Finishing op nesting under-run: uid 10127 pkg com.nianticlabs.pokemongo code 41 time=1600248041901 duration=167832 nesting=0
09-16 11:20:42.691 749 3228 W system_server: Long monitor contention with owner android.fg (782) at void com.android.server.LocationManagerService$LocationProvider.lambda$onSetEnabled$2$LocationManagerService$LocationProvider(boolean)(LocationManagerService.java:1153) waiters=0 in void com.android.server.LocationManagerService$Receiver.binderDied() for 388ms
09-16 11:20:42.692 749 791 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.location.PROVIDERS_CHANGED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
09-16 11:20:42.695 749 783 W Looper : Drained
09-16 11:20:42.695 749 749 V SettingsProvider: Notifying for 0: content://settings/secure/location_providers_allowed
09-16 11:20:42.696 749 749 W Looper : Slow dispatch took 260ms main h=com.android.providers.settings.SettingsProvider$SettingsRegistry$MyHandler c=null m=1
09-16 11:20:42.696 749 782 W Looper : Slow delivery took 471ms android.fg h=android.os.Handler c=com.android.server.-$$Lambda$LocationManagerService$LocationProvider$nsL4uwojBLPzs1TzMfpQIBSm7p0@1085061 m=0
09-16 11:20:42.696 749 781 W system_server: Long monitor contention with owner android.fg (782) at void com.android.server.LocationManagerService$LocationProvider.lambda$onSetEnabled$2$LocationManagerService$LocationProvider(boolean)(LocationManagerService.java:1153) waiters=1 in void com.android.server.LocationManagerService$Receiver.binderDied() for 392ms
09-16 11:20:42.696 749 5367 W system_server: Long monitor contention with owner android.fg (782) at void com.android.server.LocationManagerService$LocationProvider.lambda$onSetEnabled$2$LocationManagerService$LocationProvider(boolean)(LocationManagerService.java:1153) waiters=2 in void com.android.server.LocationManagerService$Receiver.binderDied() for 393ms
09-16 11:20:42.697 749 791 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.location.PROVIDERS_CHANGED flg=0x10 (has extras) } to com.lycamobile.selfcare/cordova.plugins.Diagnostic$LocationProviderChangedReceiver
09-16 11:20:42.697 749 781 W AppOps : Finishing op nesting under-run: uid 10127 pkg com.nianticlabs.pokemongo code 41 time=1600248041901 duration=167832 nesting=0
09-16 11:20:42.697 749 781 W AppOps : Finishing op nesting under-run: uid 10127 pkg com.nianticlabs.pokemongo code 42 time=1600248041901 duration=167829 nesting=0
09-16 11:20:42.698 749 749 W Looper : Slow delivery took 260ms main h=com.android.providers.settings.SettingsProvider$SettingsRegistry$MyHandler c=null m=2
09-16 11:20:42.698 749 782 V GnssStatusListenerHelper: Error in monitored listener.
09-16 11:20:42.698 749 782 V GnssStatusListenerHelper: android.os.DeadObjectException
09-16 11:20:42.698 749 782 V GnssStatusListenerHelper: at android.os.BinderProxy.transactNative(Native Method)
09-16 11:20:42.698 749 782 V GnssStatusListenerHelper: at android.os.BinderProxy.transact(BinderProxy.java:511)
09-16 11:20:42.698 749 782 V GnssStatusListenerHelper: at android.location.IGnssStatusListener$Stub$Proxy.onNmeaReceived(IGnssStatusListener.java:250)
09-16 11:20:42.698 749 782 V GnssStatusListenerHelper: at com.android.server.location.GnssStatusListenerHelper.lambda$onNmeaReceived$4$GnssStatusListenerHelper(GnssStatusListenerHelper.java:92)
09-16 11:20:42.698 749 782 V GnssStatusListenerHelper: at com.android.server.location.-$$Lambda$GnssStatusListenerHelper$AtHI8E6PAjonHH1N0ZGabW0VF6c.execute(Unknown Source:10)
09-16 11:20:42.698 749 782 V GnssStatusListenerHelper: at com.android.server.location.RemoteListenerHelper$HandlerRunnable.run(RemoteListenerHelper.java:282)
09-16 11:20:42.698 749 782 V GnssStatusListenerHelper: at android.os.Handler.handleCallback(Handler.java:883)
09-16 11:20:42.698 749 782 V GnssStatusListenerHelper: at android.os.Handler.dispatchMessage(Handler.java:100)
09-16 11:20:42.698 749 782 V GnssStatusListenerHelper: at android.os.Looper.loop(Looper.java:214)
09-16 11:20:42.698 749 782 V GnssStatusListenerHelper: at android.os.HandlerThread.run(HandlerThread.java:67)
09-16 11:20:42.698 749 782 V GnssStatusListenerHelper: at com.android.server.ServiceThread.run(ServiceThread.java:44)
09-16 11:20:42.698 749 791 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.location.PROVIDERS_CHANGED flg=0x10 (has extras) } to it.fastweb.myfastweb/me.wiman.sdk.receivers.LocationProvidersReceiver
09-16 11:20:42.699 749 780 W system_server: Long monitor contention with owner android.fg (782) at void com.android.server.LocationManagerService$LocationProvider.lambda$onSetEnabled$2$LocationManagerService$LocationProvider(boolean)(LocationManagerService.java:1153) waiters=3 in void com.android.server.LocationManagerService.removeGnssDataListener(android.os.IInterface, com.android.server.location.RemoteListenerHelper, android.util.ArrayMap) for 395ms
09-16 11:20:42.698 749 782 V GnssStatusListenerHelper: Error in monitored listener.
09-16 11:20:42.698 749 782 V GnssStatusListenerHelper: android.os.DeadObjectException
09-16 11:20:42.698 749 782 V GnssStatusListenerHelper: at android.os.BinderProxy.transactNative(Native Method)
09-16 11:20:42.698 749 782 V GnssStatusListenerHelper: at android.os.BinderProxy.transact(BinderProxy.java:511)
09-16 11:20:42.698 749 782 V GnssStatusListenerHelper: at android.location.IGnssStatusListener$Stub$Proxy.onNmeaReceived(IGnssStatusListener.java:250)
09-16 11:20:42.698 749 782 V GnssStatusListenerHelper: at com.android.server.location.GnssStatusListenerHelper.lambda$onNmeaReceived$4$GnssStatusListenerHelper(GnssStatusListenerHelper.java:92)
09-16 11:20:42.698 749 782 V GnssStatusListenerHelper: at com.android.server.location.-$$Lambda$GnssStatusListenerHelper$AtHI8E6PAjonHH1N0ZGabW0VF6c.execute(Unknown Source:10)
09-16 11:20:42.698 749 782 V GnssStatusListenerHelper: at com.android.server.location.RemoteListenerHelper$HandlerRunnable.run(RemoteListenerHelper.java:282)
Logcat crash #2
09-16 11:47:02.183 749 3299 I ActivityManager: Process com.qualcomm.qcrilmsgtunnel (pid 22105) has died: svcb SVC
09-16 11:47:02.185 749 3299 W ActivityManager: Scheduling restart of crashed service com.qualcomm.qcrilmsgtunnel/.QcrilMsgTunnelService in 1000ms
09-16 11:47:02.213 749 11993 I ActivityManager: Process com.fsck.k9 (pid 22168) has died: svc SVC
09-16 11:47:02.214 749 11993 W ActivityManager: Scheduling restart of crashed service com.fsck.k9/.service.PushService in 10971ms
09-16 11:47:02.228 289 289 I Zygote : Process 22105 exited due to signal 9 (Killed)
09-16 11:47:02.228 749 793 I libprocessgroup: Successfully killed process cgroup uid 1001 pid 22105 in 43ms
09-16 11:47:02.235 289 289 I Zygote : Process 22168 exited due to signal 9 (Killed)
09-16 11:47:02.243 749 18262 I ActivityManager: Process com.android.email (pid 22050) has died: svc SVC
As I don’t see any mention of “IOCTL_KGSL”, I assume my issue is different from yours… 
As can be seen on the “top” command, memory and CPU consumption is somehow high, could that be the cause?
Tasks: 269 total, 1 running, 268 sleeping, 0 stopped, 0 zombie
Mem: 1.8G total, 1.7G used, 98M free, 2.7M buffers
Swap: 0 total, 0 used, 0 free, 366M cached
400%cpu 113%user 3%nice 45%sys 231%idle 6%iow 0%irq 1%sirq 0%host
PID USER PR NI VIRT RES SHR S[%CPU] %MEM TIME+ ARGS
29558 u0_a127 10 -10 2.2G 844M 362M S 108 44.9 1:24.55 com.nianticlabs.pokemongo
749 system 18 -2 2.0G 93M 32M S 18.6 4.9 10:15.54 system_server
348 system -2 -8 217M 11M 4.1M S 7.3 0.5 2:27.26 surfaceflinger
341 audioserver 20 0 54M 5.2M 1.8M S 5.3 0.2 1:46.00 audioserver
480 nobody 20 0 55M 1.9M 724K S 3.3 0.1 1:50.58 sensors.qcom
305 audioserver 20 0 27M 3.6M 1.1M S 3.0 0.1 0:58.95 android.hardware.audio@2.0-service
28060 root 20 0 9.4M 1.5M 764K R 2.6 0.0 0:06.04 top
29589 u0_a23 20 0 1.3G 92M 53M S 2.3 4.8 0:08.55 com.google.android.gms.persistent
185 root 20 0 0 0 0 S 2.0 0.0 1:05.05 [mmcqd/0]
320 system 20 0 10M 1.4M 880K S 1.6 0.0 0:02.35 android.hardware.memtrack@1.0-service
25113 root 20 0 0 0 0 S 1.3 0.0 0:04.13 [kworker/u:1]
29770 u0_a23 20 0 1.1G 39M 17M S 1.0 2.0 0:00.64 com.google.process.gapps
17155 root 20 0 0 0 0 S 1.0 0.0 0:13.48 [kworker/u:7]
511 root RT 0 0 0 0 D 1.0 0.0 0:15.74 [mdss_fb0]
100 root 20 0 0 0 0 S 1.0 0.0 0:43.58 [kswapd0]
30152 mdnsr 20 0 3.3M 720K 436K S 0.6 0.0 0:00.09 mdnsd
29480 u0_a65 20 0 1.1G 37M 16M S 0.6 1.9 0:00.33 com.android.email
3221 radio 20 0 1.1G 36M 12M S 0.6 1.9 0:19.52 com.android.phone
30919 root 20 0 0 0 0 S 0.3 0.0 0:00.01 [ksoftirqd/2]
30918 root 0 -20 0 0 0 S 0.3 0.0 0:00.03 [kworker/2:0H]
30525 u0_a125 20 0 1.2G 71M 34M S 0.3 3.8 0:01.48 com.whatsapp
It’s always an error like
IOCTL_KGSL_DEVICE_WAITTIMESTAMP_CTXTID) failed: errno 35 Resource deadlock would occur
It occurs in different apps (not only games).
My 2nd FP2 (old cameras) has’nt this problems respectively it happens less often.
I have a question about OpenGL ES 3. I have an app that needs this new version of OpenGL, but it seems that this is not yet supported for Lineage 17.1. I saw that FP-Open has the fix already according to https://bugtracker.fairphone.com/project/fairphone-android-7/issue/56
Will this be ported to LineageOS?
I typed in ‘OpenGL’ in the settings menu and ‘Force 4x MSAA’ popped up, but activating this did not let me run my app. Any other tips?
I think I understood never to call a bug solved before having used your phone for a week at least, or even a month.
This mobile data issue is making a key feature of my phone unusable, also because it’s coupled with another issue which seems to be linked to my provider. My phone shows it’s connected via mobile data although it isn’t if left an hour or two with mobile fata on without any active connections (I had already posted about it in the thread). And the workaround is disabling mobile data and reenabling it again or wutching flightmode on and off… which triggers the lineage mobile data issues.
I had decided to live with mobile data on all the time, but doesn’t work anymore, and I’m not planning a provided switch, merely a fix from them…
I’m left with rebooting my phone at least five times a day.
I’ll try downgrading to an earlier build, but I’m pretty pessimistic. If that doesn’t work, I’ll downgrade to 16.0, perhaps give /e/ a try. I’ll keep you updated.
2 Likes
I, too, have had the issue of broken mobile data connection while WLAN was enabled, but not connected. What worked for me was enabling airplane mode for at least 30, maybe even 40 seconds, and disabling it afterwards. The FP2 usually takes quite a long time to reconnect to a mobile network, so you might have to wait another 30 to 40 seconds until you are connected again.
Could you check if this works for you, too, when you experience the issue?
2 Likes
Thanks for the suggestion, I’ll try next time it happens, but AFAICT toggling Airplane mode triggers the Lineage mobile data bug (i.e doesn’t even show to be connected).
I thought it was linked to the provider (Free in France) because my brother with a FP2 has had the samr problem under FPOOS android 6, and other people, one with a feature phone and the other with an iPhone have experienced network and
call problems, and we are all under the same provider.
1 Like
Doesn’t seem to work for me.
Neither Wlan nor mobile internet doe connect again after flight mode.
1 Like
short question:
in the initial wiki post it is not statet that there are problems with mobile data / flight mode which I read quite often in this post.
So: is this a common issue in LOS 17.1@FP2 or are only a few “infected” by this and therefore it is not added to the wiki because it is not a reproducible bug?
Are ther more things which are not working and are not statet in the wiki post? I am still not brave enought to test it out on my FP2 (currently on 16.0) … I don’t have a complete overview of this huge post here…
Cheer, Robert
2 Likes
I experience very few issues apart from this one. Moreover, I haven’t had the issue since last update, though I will wait before concluding it’s solved.
Not everyone has this issue, and it is a bit random. @chrmhoffmann managed to reproduce it but not to find where it came from. A poll had been made some time ago in this thread about who was having the issue.
We could start a list of known issues, but I wonder how useful it would be.
I understood you didn’t want to upgrade yet, but testing is the only thing that will allow you to judge IMHO. You can do a backup of your actual phone and restore it at any time 
It’s a sporadic issue I’d say. I turn off mobile data during the night and I think it’s disabled automatically when WLAN is used. So when coming from these states in some rare cases the mobile data won’t turn on again and only a reboot helps. Also in some rare cases the phone won’t connect to the available WLAN (2.4 GHz) although it sees them. But this is an issue that I used to have with FPOS already, too. The number of spontaneous reboots has increased after changing from FPOS to LOS 17.1. So sometimes I’m doing something totally normal, like browsing the web, then the phone gets stuck for a few seconds, then it reboots. Usually that does not happen while the phone is in standby. But here again: The frequency of this has increased from almost never to ~once per week or so. SMS tend to not be received/shown automatically if in power save mode, I found out. You have to open the messages app to find them. But all in all I really think that it is rather safe to use LOS 17.1 as a daily driver.
3 Likes
I am really close to throwing my FP2 against the next wall because it has gotten soooooo sloooooooow… running the 18/09 build here. I think I did a clean install in june or something.
Am I the only one with performance issues? How can I find out what is causing my system to lag so much?
I cannot verify this.
Why not check out the latest from today? Just give it a try, maybe it helps.
@Alex.A I have not experienced the “not connected issue” on my FP2 either for about one week.
1 Like
I have not experienced it for a week exactly, and then saturday it happened again, sunday as well, and today. It seems that the LOS updates stop the issue for about a week and then it starts again, I’ll have to do more tests with further updates (I’ll try to update to the latest build, I haven’t done this yet to do more tests about my hypothesis). Could you try not updating for 2 weeks and report if the issue appears again?
I’m currently on my backup FP2 and I’m planning to pass on my main one on which I installed /e/ (because I want to give it a try). But before I’ll try to find a pattern if possible, the problem really seems to appear randomly, and I don’t get what could trigger it. I’ll keep the backup FP2 for beta/tests purposes.
1 Like
I haven’t had the “not connected” issue for the last week either, but it does seem to be random for me too.
I have had another issue though. When the phone rings, sometimes (maybe half the time?) the screen freezes and I can’t pick up. After a minute or so, I get a message saying that “Phone isn’t responding”, then I can “Close App” and the phone is back to normal. Does anyone else have this?
1 Like
Now I’m on 20201009, but unfortunately this old issue is still alive. Just for me or can someone confirm?
Can confirm. I think it just wasn’t fixed.
Updated today and can confirm the issue still exists on 20201009.