Develop Bugs

Nexus 7 (2013) won't connect to my home Wi-Fi (running Android 6.0.1)

I bought a second-hand Wi-Fi only Google/Asus Nexus 7 (2013), which came wiped, with Android 6.0.1 installed, but it won't connect to my home Wi-Fi router. It will save the details but when it tries to connect I get the message 'Wi-Fi Connection Failure'. I am certain the password is correct.
Other devices connect without problems, and I have successfully connected the Nexus to a work Wi-Fi network, but it's no good to me if it won't connect at home. I previously had another Nexus 7 that would connect fine, but was recently bricked by an Android update.
I have tried all suggested fixes I can find online, including:
- Restarting the router
- Wiping data on the Nexus 7
- Restarting the Nexus (in safe and normal mode)
- Switching Wi-Fi/Airplane Mode on and off on the Nexus 7
- Forgetting and re-entering the network details
- Changing the frequency on the Nexus 7
- Changing the channel and security settings on the router
None has any effect. As far as I know my router is on the latest firmware. It's a Sky Hub, which broadcasts at 2.4 GHz.
Can anyone think of a fix or any known issues? I can return the device free to the retailer but would like to see if I can avoid the hassle. I'm also going to avoid doing anything involving rooting the tablet for now in case that voids the warranty.

Let's see the log:
turn off wifi
run: adb logcat -v time > log.txt
turn on wifi
when you see the error, end adb log with ctrl-c immediately
zip up "log.txt" and attach it here
Be quick because the log gets big fast.
We'll be interested mostly in wpa_supplicant messages:
Code:
03-10 23:35:08.318 I/wpa_supplicant( 1879): wlan0: Trying to associate with SSID 'CC1'
03-10 23:35:08.432 D/Tethering( 561): sendTetherStateChangedBroadcast 1, 0, 0
03-10 23:35:08.436 D/NetworkManagementService( 561): getNetworkStatsSummaryXt:NetworkStats: elapsedRealtime=102015
03-10 23:35:08.436 D/NetworkManagementService( 561): [0] iface=lo uid=-1 set=ALL tag=0x0 rxBytes=0 rxPackets=0 txBytes=0 txPackets=0 operations=0
03-10 23:35:08.438 D/NetworkManagementService( 561): getNetworkStatsSummaryDev:NetworkStats: elapsedRealtime=102019
03-10 23:35:08.438 D/NetworkManagementService( 561): [0] iface=lo uid=-1 set=ALL tag=0x0 rxBytes=0 rxPackets=0 txBytes=0 txPackets=0 operations=0
03-10 23:35:08.441 I/wpa_supplicant( 1879): wlan0: Associated with 00:04:ad:d5:e2:0a
03-10 23:35:08.722 I/wpa_supplicant( 1879): wlan0: WPA: Key negotiation completed with 00:04:ad:d5:e2:0a [PTK=CCMP GTK=CCMP]
03-10 23:35:08.726 I/wpa_supplicant( 1879): wlan0: CTRL-EVENT-CONNECTED - Connection to 00:04:ad:d5:e2:0a completed [id=0 id_str=]

Ok, no idea if I've done this right, but here goes (I'm trying to connect to SSID SKY8DBEF):
Code:
03-11 22:37:49.844 D/WifiService( 597): Connect with config* ID: -1 SSID: "SKY8DBEF" PROVIDER-NAME: null BSSID: null FQDN: null PRIO: 0
03-11 22:37:49.844 D/WifiService( 597): KeyMgmt: WPA_PSK Protocols:
03-11 22:37:49.844 D/WifiService( 597): AuthAlgorithms:
03-11 22:37:49.844 D/WifiService( 597): PairwiseCiphers:
03-11 22:37:49.844 D/WifiService( 597): GroupCiphers:
03-11 22:37:49.844 D/WifiService( 597): PSK: *
03-11 22:37:49.844 D/WifiService( 597): Enterprise config:
03-11 22:37:49.844 D/WifiService( 597): IP config:
03-11 22:37:49.844 D/WifiService( 597): IP assignment: DHCP
03-11 22:37:49.844 D/WifiService( 597): Proxy settings: NONE
03-11 22:37:49.844 D/WifiService( 597): cuid=-1 luid=-1 lcuid=0 userApproved=USER_UNSPECIFIED noInternetAccessExpected=false roamingFailureBlackListTimeMilli: 1000
03-11 22:37:49.844 D/WifiService( 597): triggeredLow: 0 triggeredBad: 0 triggeredNotHigh: 0
03-11 22:37:49.844 D/WifiService( 597): ticksLow: 0 ticksBad: 0 ticksNotHigh: 0
03-11 22:37:49.844 D/WifiService( 597): triggeredJoin: 0
03-11 22:37:49.844 D/WifiService( 597): autoJoinBailedDueToLowRssi: false
03-11 22:37:49.844 D/WifiService( 597): autoJoinUseAggressiveJoinAttemptThreshold: 0
03-11 22:37:49.845 I/chatty ( 597): uid=1000(system) WifiStateMachin expire 26 lines
03-11 22:37:49.850 E/WiFiServiceImpl ( 597): CONNECT nid=-1 uid=1000 name=android.uid.system:1000
03-11 22:37:49.850 D/WifiService( 597): Connect with config* ID: -1 SSID: "SKY8DBEF" PROVIDER-NAME: null BSSID: null FQDN: null PRIO: 0
03-11 22:37:49.850 D/WifiService( 597): KeyMgmt: WPA_PSK Protocols:
03-11 22:37:49.850 D/WifiService( 597): AuthAlgorithms:
03-11 22:37:49.850 D/WifiService( 597): PairwiseCiphers:
03-11 22:37:49.850 D/WifiService( 597): GroupCiphers:
03-11 22:37:49.850 D/WifiService( 597): PSK: *
03-11 22:37:49.850 D/WifiService( 597): Enterprise config:
03-11 22:37:49.850 D/WifiService( 597): IP config:
03-11 22:37:49.850 D/WifiService( 597): IP assignment: DHCP
03-11 22:37:49.850 D/WifiService( 597): Proxy settings: NONE
03-11 22:37:49.850 D/WifiService( 597): cuid=-1 luid=-1 lcuid=0 userApproved=USER_UNSPECIFIED noInternetAccessExpected=false roamingFailureBlackListTimeMilli: 1000
03-11 22:37:49.850 D/WifiService( 597): triggeredLow: 0 triggeredBad: 0 triggeredNotHigh: 0
03-11 22:37:49.850 D/WifiService( 597): ticksLow: 0 ticksBad: 0 ticksNotHigh: 0
03-11 22:37:49.850 D/WifiService( 597): triggeredJoin: 0
03-11 22:37:49.850 D/WifiService( 597): autoJoinBailedDueToLowRssi: false
03-11 22:37:49.850 D/WifiService( 597): autoJoinUseAggressiveJoinAttemptThreshold: 0
03-11 22:37:49.854 D/audio_hw_primary( 195): out_set_parameters: enter: usecase(1: low-latency-playback) kvpairs: routing=2
03-11 22:37:49.887 I/Keyboard.Facilitator( 1008): onFinishInput()
03-11 22:37:49.891 D/AudioFlinger( 195): mixer(0xb4200000) throttle end: throttle time(4)
03-11 22:37:50.021 I/wpa_supplicant( 961): wlan0: Trying to associate with SSID 'SKY8DBEF'
03-11 22:37:51.062 I/wpa_supplicant( 961): wlan0: CTRL-EVENT-ASSOC-REJECT bssid=c0:3e:0f:8e:ea:15 status_code=1
03-11 22:37:51.062 I/wpa_supplicant( 961): wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=1 ssid="SKY8DBEF" auth_failures=1 duration=10 reason=CONN_FAILED
03-11 22:37:53.070 D/audio_hw_primary( 195): disable_audio_route: reset and update mixer path: low-latency-playback
03-11 22:37:53.071 D/audio_hw_primary( 195): disable_snd_device: snd_device(2: speaker)
03-11 22:38:01.658 I/wpa_supplicant( 961): wlan0: CTRL-EVENT-SSID-REENABLED id=1 ssid="SKY8DBEF"
03-11 22:38:01.665 I/chatty ( 597): uid=1000(system) WifiStateMachin expire 10 lines
03-11 22:38:16.975 E/ ( 193): invalid crash request of size 4 (from pid=5518 uid=0)
03-11 22:38:17.101 I/chatty ( 597): uid=1000 system_server expire 1 line
03-11 22:38:17.127 E/Diag_Lib( 5816): Diag_LSM_Init: Failed to open handle to diag driver, error = 2
03-11 22:38:17.127 E/Sensors ( 5816): sns_fsa_la.c(386):fsa: fflush failed, 9
03-11 22:38:17.128 E/Sensors ( 5816): sns_fsa_la.c(386):fsa: fflush failed, 9
03-11 22:38:17.154 W/Sensors ( 5816): sns_smr_la.c(446):smr_la: smr_apps_la_thread_main is starting, fd=11, sns_smr.en_rx_msg_ptr=b70009f8
03-11 22:38:17.175 W/Sensors ( 5816): sns_sam_app.c(6827):sns_sam_reg_algo: Registering algo service 16, err 0
03-11 22:38:17.195 E/Sensors ( 5816): sns_debug_main.c(565):Debug Config File missing in EFS!
03-11 22:38:28.381 I/chatty ( 597): uid=1000(system) HeapTaskDaemon expire 1 line
03-11 22:38:49.925 I/Keyboard.Facilitator.LanguageModelFlusher( 1008): run()
03-11 22:38:49.925 I/Keyboard.Facilitator( 1008): flushDynamicLanguageModels()
03-11 22:38:58.429 I/wpa_supplicant( 961): wlan0: Trying to associate with SSID 'SKY8DBEF'
03-11 22:38:59.567 I/wpa_supplicant( 961): wlan0: CTRL-EVENT-ASSOC-REJECT bssid=c0:3e:0f:8e:ea:15 status_code=1
03-11 22:38:59.567 I/wpa_supplicant( 961): wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=1 ssid="SKY8DBEF" auth_failures=1 duration=10 reason=CONN_FAILED
[/QUOTE]

mpb39 said:
Ok, no idea if I've done this right, but here goes (I'm trying to connect to SSID SKY8DBEF)
Click to expand...
Click to collapse
It logs:
Code:
wlan0: CTRL-EVENT-ASSOC-[B]REJECT [/B]bssid=c0:3e:0f:8e:ea:15
wlan0: ... id=1 ssid="SKY8DBEF" [B]auth_failures=1[/B]
The router rejects your N7. Can you check the router's own logs?
On your N7 go to WiFi Direct and rename the device. This will re-generate fresh /data/misc/wifi/wpa_supplicant.conf and may fix the problem which really looks like a bad passphrase.

Ok, I renamed it Nexus7, but it didn't have any effect. Exact same problem.
The router logs that I can access aren't detailed enough to show anything about device connections, as far as I can tell. Just router startups etc. And the N7 isn't showing up in the list of attached devices.
Any other ideas?
I'm thinking I should return the N7 to the retailer on Monday since I'm in a 14-day return period, so it doesn't matter if it's actually broken or not. Either way, if I can't connect to my home Wi-Fi the device is really no good to me.
k23m said:
It logs:
Code:
wlan0: CTRL-EVENT-ASSOC-[B]REJECT [/B]bssid=c0:3e:0f:8e:ea:15
wlan0: ... id=1 ssid="SKY8DBEF" [B]auth_failures=1[/B]
The router rejects your N7. Can you check the router's own logs?
On your N7 go to WiFi Direct and rename the device. This will re-generate fresh /data/misc/wifi/wpa_supplicant.conf and may fix the problem which really looks like a bad passphrase.
Click to expand...
Click to collapse

mpb39 said:
I bought a second-hand Wi-Fi only Google/Asus Nexus 7 (2013), which came wiped, with Android 6.0.1 installed...
Click to expand...
Click to collapse
It was wiped but the OS could have been modified. Does it accept OTA now? I'd reflash it with factory image anyway.

i was experienced the same problem with you, that was after i changed its mac address. what i did is i changed it back to the default one and its working fine again.

I suppose that could have been the problem, but would a factory reset not restore the original MAC code if it had been changed?
Anyway, I've returned the device to the retailer for a refund now.

Galaxy Nexus Freezes

Hello.
I have installed LineageOS 13.0 on my Samsung Galaxy Nexus (GT-i9250). I use it for running Whatsapp (over wifi) and connect over Whatsapp-Web.
Sometimes it happens that the smartphone freezes and I have to reboot by unplugging the battery. The "asdb logcat" log is attached (XXXX was http). How can I avoid this? Thanks.
01-17 04:00:45.572 502 520 D Tethering: MasterInitialState.processMessage what=3
01-17 04:00:45.579 502 623 D ConnectivityService: notifyType PRECHECK for NetworkAgentInfo [WIFI () - 124]
01-17 04:00:45.585 1921 1921 I UpdateCheckReceiver: Got connectivity change, has connection: true
01-17 04:00:45.585 1921 1921 I UpdateCheckReceiver: Scheduling future, repeating update checks.
01-17 04:00:45.586 502 623 D ConnectivityService: notifyType CAP_CHANGED for NetworkAgentInfo [WIFI () - 124]
01-17 04:00:45.593 1596 1596 I CmaSystemUpdateService: connectivity change: Intent { act=android.net.conn.CONNECTIVITY_CHANGE flg=0x4000010 (has extras) }
01-17 04:00:45.593 1596 1596 I CmaSystemUpdateService: receiver: Intent { act=android.net.conn.CONNECTIVITY_CHANGE flg=0x4000010 (has extras) }
01-17 04:00:45.597 502 5952 D NetworkMonitor/NetworkAgentInfo [WIFI () - 124]: Checking XXXXXconnectivitycheck.gstatic.com/generate_204 on "FUSION", connectivitycheck.gstatic.com=216.58.205.163,2a00:1450:4002:80a::2003
01-17 04:00:45.598 502 5952 W System : ClassLoader referenced unknown path: /system/framework/tcmclient.jar
01-17 04:00:45.603 2842 2915 W System : ClassLoader referenced unknown path: /system/framework/tcmclient.jar
01-17 04:00:45.637 1596 2106 I PinnedContentDownloader: Started downloading pinned content.
01-17 04:00:45.639 1086 1105 D PhoneInterfaceManager: [PhoneIntfMgr] getDataEnabled: subId=1 phoneId=0
01-17 04:00:45.640 1086 1105 D PhoneInterfaceManager: [PhoneIntfMgr] getDataEnabled: subId=1 retVal=false
01-17 04:00:45.641 502 515 D TelephonyManager: getDataEnabled: retVal=false
01-17 04:00:45.655 1596 1596 I iu.Environment: update connectivity state; isNetworkMetered? false, isRoaming? false, isBackgroundDataAllowed? true*
01-17 04:00:45.659 1086 2304 D TelephonyProvider: getPreferredApnIdFromApn: for subId 1
01-17 04:00:45.660 1086 2304 D TelephonyProvider: Preferred APN: -1
01-17 04:00:45.664 502 5953 D NetlinkSocketObserver: NeighborEvent{elapsedMs=31948177, 192.168.0.254, [A491B129B92C], RTM_NEWNEIGH, NUD_REACHABLE}
01-17 04:00:45.670 4897 4897 D WeatherUpdateService: onCreate
01-17 04:00:45.678 4897 4897 D WeatherUpdateService: Service started, but shouldn't update ... stopping
01-17 04:00:45.681 4897 4897 D WeatherUpdateService: onDestroy
01-17 04:00:45.686 502 515 E GpsLocationProvider: No APN found to select.
01-17 04:00:45.695 1596 2106 I PinnedContentDownloader: Finished downloading pinned content.
01-17 04:00:45.697 1596 1690 I iu.UploadsManager: num queued entries: 0
01-17 04:00:45.699 1596 1690 I iu.UploadsManager: num updated entries: 0
01-17 04:00:45.700 502 5952 D NetworkMonitor/NetworkAgentInfo [WIFI () - 124]: isCaptivePortal: ret=204 headers={null=[HTTP/1.1 204 No Content], Content-Length=[0], Date=[Wed, 17 Jan 2018 03:00:46 GMT], X-Android-Received-Millis=[1516158045699], X-Android-Response-Source=[NETWORK 204], X-Android-Selected-Protocol=[http/1.1], X-Android-Sent-Millis=[1516158045648]}
01-17 04:00:45.701 502 623 D ConnectivityService: setProvNotificationVisibleIntent null visible=false networkType=MOBILE extraInfo=null highPriority=false
01-17 04:00:45.701 502 623 D ConnectivityService: NetworkAgentInfo [WIFI () - 124] validation passed
01-17 04:00:45.702 502 623 D ConnectivityService: notifyType CAP_CHANGED for NetworkAgentInfo [WIFI () - 124]
01-17 04:00:45.706 502 623 D ConnectivityService: sendStickyBroadcast: action=android.net.conn.INET_CONDITION_ACTION
01-17 04:00:45.712 1596 1690 I iu.SyncManager: NEXT; no task
01-17 04:00:46.116 502 621 D IpReachabilityMonitor: watch: iface{wlan0/11}, v{4}, ntable=[192.168.0.1/NUD_REACHABLE, 192.168.0.254/NUD_REACHABLE]
01-17 04:00:46.117 502 623 D ConnectivityService: Adding Route [fd2c:81a5:7139::/64 -> :: wlan0] to network 124
01-17 04:00:46.139 502 623 D ConnectivityService: notifyType IP_CHANGED for NetworkAgentInfo [WIFI () - 124]
01-17 04:00:46.202 1596 2106 W System : ClassLoader referenced unknown path: /system/framework/tcmclient.jar
01-17 04:00:46.567 502 623 D ConnectivityService: NetTransition Wakelock (NetworkAgentInfo [WIFI () - 123] cleared because we found a replacement network
01-17 04:00:46.692 2842 5345 W System : ClassLoader referenced unknown path: /system/framework/tcmclient.jar
01-17 04:00:53.442 502 623 D ConnectivityService: handlePromptUnvalidated 124

mimu88 said:
Hello. I have installed LineageOS 13.0 on my Samsung Galaxy Nexus (GT-i9250). I use it for running Whatsapp (over wifi) and connect over Whatsapp-Web...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Official LineageOS thread for your device.
https://forum.xda-developers.com/showthread.php?t=3312784
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Crash Debug on LineageOS 14.1

I just flashed my mobile with LineageOS 14.1
To my surprise I see the crashes that they dont show full stack trace.
Only this:
01-03 22:44:01.189 12773 12807 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x42424242 in tid 12807 (hci_thread)
Do I have to enable it somehow?
I would expect to see something like this (this I remember from Cyanogenmod and Stock Android)
02-05 16:45:13.279 307 1231 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x1 in tid 1231 (netmgrd)
02-05 16:45:13.351 6570 6570 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
02-05 16:45:13.352 6570 6570 F DEBUG : CM Version: '14.1-20170131-NIGHTLY-osprey'
02-05 16:45:13.352 6570 6570 F DEBUG : Build fingerprint: 'motorola/osprey_retus_2gb/osprey_u2:6.0.1/MPI24.107-55/33:user/release-keys'
02-05 16:45:13.352 6570 6570 F DEBUG : Revision: '0'
02-05 16:45:13.352 6570 6570 F DEBUG : ABI: 'arm'
02-05 16:45:13.352 6570 6570 F DEBUG : pid: 307, tid: 1231, name: netmgrd >>> /system/bin/netmgrd <<<
02-05 16:45:13.352 6570 6570 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x1
02-05 16:45:13.352 6570 6570 F DEBUG : r0 b6b01f10 r1 00000001 r2 b6b06560 r3 00000040
02-05 16:45:13.352 6570 6570 F DEBUG : r4 b647f3fc r5 b6b06eac r6 b6b01f10 r7 b6b02d07
02-05 16:45:13.352 6570 6570 F DEBUG : r8 b5f07520 r9 b5f07500 sl 00000001 fp b6f7ea49
02-05 16:45:13.352 6570 6570 F DEBUG : ip 00000000 sp b647f000 lr b6af9ba5 pc b6af9bce cpsr 20070030
02-05 16:45:13.363 6570 6570 F DEBUG :
02-05 16:45:13.363 6570 6570 F DEBUG : backtrace:
02-05 16:45:13.363 6570 6570 F DEBUG : #00 pc 00007bce /system/vendor/lib/libnetmgr.so (netmgr_nl_decode_nlmsg+269)
02-05 16:45:13.363 6570 6570 F DEBUG : #01 pc 00020f7d /system/bin/netmgrd
02-05 16:45:13.363 6570 6570 F DEBUG : #02 pc 00033893 /system/bin/netmgrd
02-05 16:45:13.364 6570 6570 F DEBUG : #03 pc 00041b09 /system/bin/netmgrd
02-05 16:45:13.364 6570 6570 F DEBUG : #04 pc 0000bef9 /system/vendor/lib/libdsutils.so (stm2_process_input+632)
02-05 16:45:13.364 6570 6570 F DEBUG : #05 pc 0000c7dd /system/vendor/lib/libdsutils.so (stm2_instance_process_input+204)
02-05 16:45:13.364 6570 6570 F DEBUG : #06 pc 0001213d /system/bin/netmgrd
02-05 16:45:13.364 6570 6570 F DEBUG : #07 pc 00003f9f /system/vendor/lib/libdsutils.so
02-05 16:45:13.364 6570 6570 F DEBUG : #08 pc 000477d3 /system/lib/libc.so (_ZL15__pthread_startPv+22)
02-05 16:45:13.364 6570 6570 F DEBUG : #09 pc 00019b7d /system/lib/libc.so (__start_thread+6)
Thanks,

marcinguy said:
I just flashed my mobile with LineageOS 14.1...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Official LineageOS thread for your device.
https://forum.xda-developers.com/showthread.php?t=3466246
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

Thanks!
Actually it is a general Question in regards to LineageOS 14.1.
The device I use is S3 Neo+ GT-9301I
I pasted sample output as I it remember from Motorola device.
So on my device, as stated I just get:
Code:
12-31 13:11:00.180 8059 8096 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 8096 (bt_workqueue)
12-31 13:11:00.181 209 209 W : debuggerd: handling request: pid=8059 uid=1002 gid=1002 tid=8096
12-31 13:11:00.220 8059 8096 F libc : failed to resend signal during crash: Operation not permitted
12-31 13:11:00.229 8335 8335 E DEBUG : unexpected waitpid response: n=8096, status=00000000
12-31 13:11:00.229 8335 8335 E : debuggerd: timed out waiting for signal
12-31 13:11:00.231 8335 8335 E : debuggerd: ptrace detach from 8096 failed: No such process
12-31 13:11:00.233 8335 8335 E : debuggerd: failed to kill process 8059: No such process
12-31 13:11:00.236 778 810 I BootReceiver: Copying /data/tombstones/tombstone_09 to DropBox (SYSTEM_TOMBSTONE)
Any ideas?
Where there is "Operation not permitted"?
Ibuprophen said:
I don't have this device but, your best bet is to post this question within the following Official LineageOS thread for your device.
https://forum.xda-developers.com/showthread.php?t=3466246
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse

Narrowed it down to this:
int rc = syscall(SYS_rt_tgsigqueueinfo, getpid(), gettid(), signal_number, info);
if (rc != 0) {
__libc_format_log(ANDROID_LOG_FATAL, "libc", "failed to resend signal during crash: %s",
strerror(errno));
_exit(0);
}
12-31 14:35:20.070 14851 14881 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 14881 (bt_workqueue)
12-31 14:35:20.070 16288 16288 W : debuggerd: handling request: pid=14851 uid=1002 gid=1002 tid=14881
12-31 14:35:20.100 14851 14881 F libc : failed to resend signal during crash: Operation not permitted
Wondering why it gets Operation not permitted?
marcinguy said:
Thanks!
Actually it is a general Question in regards to LineageOS 14.1.
The device I use is S3 Neo+ GT-9301I
I pasted sample output as I it remember from Motorola device.
So on my device, as stated I just get:
Code:
12-31 13:11:00.180 8059 8096 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 8096 (bt_workqueue)
12-31 13:11:00.181 209 209 W : debuggerd: handling request: pid=8059 uid=1002 gid=1002 tid=8096
12-31 13:11:00.220 8059 8096 F libc : failed to resend signal during crash: Operation not permitted
12-31 13:11:00.229 8335 8335 E DEBUG : unexpected waitpid response: n=8096, status=00000000
12-31 13:11:00.229 8335 8335 E : debuggerd: timed out waiting for signal
12-31 13:11:00.231 8335 8335 E : debuggerd: ptrace detach from 8096 failed: No such process
12-31 13:11:00.233 8335 8335 E : debuggerd: failed to kill process 8059: No such process
12-31 13:11:00.236 778 810 I BootReceiver: Copying /data/tombstones/tombstone_09 to DropBox (SYSTEM_TOMBSTONE)
Any ideas?
Where there is "Operation not permitted"?
Click to expand...
Click to collapse

Figured it out.
Had to modify debbugerd (bionic) and adjust selinux.
Now debuggerd can attach to the process and show the debug info and backtrace.
marcinguy said:
Narrowed it down to this:
int rc = syscall(SYS_rt_tgsigqueueinfo, getpid(), gettid(), signal_number, info);
if (rc != 0) {
__libc_format_log(ANDROID_LOG_FATAL, "libc", "failed to resend signal during crash: %s",
strerror(errno));
_exit(0);
}
12-31 14:35:20.070 14851 14881 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 14881 (bt_workqueue)
12-31 14:35:20.070 16288 16288 W : debuggerd: handling request: pid=14851 uid=1002 gid=1002 tid=14881
12-31 14:35:20.100 14851 14881 F libc : failed to resend signal during crash: Operation not permitted
Wondering why it gets Operation not permitted?
Click to expand...
Click to collapse

[ROM][8.1.0][UNOFFICIAL] ResurrectionRemix 6.0.0 [BETA] [VoLTE]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
[B][COLOR="Red"]Your warranty is now void.[/COLOR][/B]
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
F.A.Q.
Maybe this way someone will actually read it.​
Is VoLTE working?
Can you port this cool ____ feature from other ROM / OS? Probably yes.
Will you actually do it? Probably no. Supporting new features added to the actual source requires more work than you'd think, so unless it's a really important or amazing feature...
When will ____ be fixed? When and if I get it working. I'm not a professional ROM dev, there's no money or other motivation for me to do this other than me wanting to do this. I also have a life and a job, which come first.
Is this ROM official? No.
Will this ROM be official in the future? Time will tell, but as I don't have much time to maintain or provide support, that option is not on the table right now.
When will this ROM be updated? Again, when I have the time and there are enough changes to justify making a new build.
Well, I don't like this ROM or your support and I'm going to rant about it! You're very welcome to use any other ROMs if this one doesn't meet your expectations.
About Resurrection Remix​Resurrection Remix is a LineageOS based ROM with customizations from SlimROM, OmniROM among others. It's development pace is fast, but at the same time is quite stable - for a heavily customizable ROM.​
Features​Customization. Like, lots. For more info: resurrectionremix.com​
What's not working​
Proximity sensor is very rarely disabled in the middle of a phone call.
Encryption. Still working on it.
What is working​Everything else, as far as I know.​
Installation instructions​Are you coming from MIUI?
Backup all your internal storage files. That's photos, music, videos...
Install TWRP recovery, format data. The ROM may work with just a wipe, but since MIUI uses encryption and this ROM still has issues with it, you may find some issues after just wiping.
The rest of steps should be common to installing from any other custom ROM. See below.
Are you coming from a non-MIUI ROM?
Download the ROM and Google Apps (ARM64, 8.1, any flavor).
Backup your actual setup, just in case. If you don't have TWRP installed, now would be a great time to do it: https://forum.xda-developers.com/mi-mix-2/development/recovery-twrp-3-2-1-0-recovery-t3730030
Wipe data.
If you come from a 7.1 ROM, you may want to flash a new firmware: https://forum.xda-developers.com/mi-mix-2/development/firmware-xiaomi-mi-mix-2-t3741667
Install both the ROM and Google Apps. If you install Google Apps later you will have issues because some of the needed libraries won't be extracted. So, do it now.
If you want to install Magisk or any other mod, it's not mandatory to do it now. You can probably flash it in the future.
Download Links​ROM
Google Apps
Firmware
Recovery​
Get me a beer: paypal.me/arasthel
XDA:DevDB Information
Resurrection Remix 6.0.0 for Mix 2, ROM for the Xiaomi Mi Mix 2
Contributors
Arasthel, hondajohn88, andr68rus, xiaobai112220, Verevka
Source Code: https://github.com/RR-oreo-chiron/local_manifest
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Based On: Resurrection Remix
Version Information
Status: Beta
Created 2018-03-10
Last Updated 2018-03-28

Reserved
Changelog​
29/03/18 :
More SELinux fixes, this time for people using Xposed, auto brightness and proximity sensor didn't work.
28/03/18 :
New SELinux configs, should fix proximity and autobrightness issues. Fingerprint may not work, this is a known issue.
NFC tile is working again.
Added option to adjust rounded corners on Settings > Configurations > Interface > Misc.
Fixed black theme FC on Settings > Apps > Any app > Permissions.
Probably fixed camera on third party apps - worked well for me, but then again, I never noticed this issue before.
Updated RR sources with changes to SmartBar and other fixes.
25/03/18 - lots of thanks to @andr68rus in this version:
NXP NFC HAL used instead of AOSP one, config file imported from Pixel 2 XL. Battery drain from NFC fixed! -0.3%/h with WiFi ON on my last test.
SElinux enforced.
Fix USB headphones and other audio issues.
Imported RR sources, but there aren't many changes. Mostly small bugfixes and translation imports.
18/03/18:
Safetynet passes without issues - thanks @andr68rus!
Trying new low power setting for NFC when screen is off.
Optimizations to WiFi when screen off.
BT and WiFi MAC address should be stable now, as in DU / Omni.
Apps shouldn't show a black bar at the bottom anymore - force aspect ratio to match MIX 2, thanks to @AndyYan for the tip!
14/03/18:
Fixed VoLTE issues!
11/03/18:
Removed Always on Display, as it's not meant for this device and wasn't working properly.

Thanks!!!

Oh yes!
Thanks

Thanks @Arasthel

Very nice, is it based on the new oreo kernel sources recently released?

First page! Thanks for your hard work, it's been an incredible 2 months' ride from Nougat to Oreo.
EDIT: Got a donation link?
Sent from Xiaomi Mi Mix 2 @ LineageOS 15.1

Nice work bro.

Thanks Arasthel! Works great so far!

Nice work man !!!
Finally a thread ?.
Thanks for all your support @Arasthel

Updating from 0302 to 0310 got issues, back to 0302

Cant unlock device with fingerprint when always on is activ

Great stuff. Thanks for all the work you've been doing.

Ok first of all thanks for the hard work. I really love the rom.
Here is some feedback for you, also compared to the previous version.
I made a full clean install with the following installation order (used Raupes latest TWRP version)
Wiped everything and also formatted data
Flashed latest developer Firmware from this thread
Flashed the latest RR Rom
Flashed official Open GappsMini (Arm64/8.1/Mini)
Flashed latest Magisk
Flashed Camera2Api Magisk Module
Wiped Cache/Dalvik
Reboot System
The first thing I noticed after setting up pattern+fingerprint is that the unlocking process is completely broken. Most of the time you just get a black screen after unlocking. The problem was that the ambient display was on ALWAYS ON under display settings. Maybe this setting is not compatible with the Mix 2. After turning it off everything worked like it should. Also the option to lift up your phone to show notifications and clock is not working.
After that i encrypted my phone. Everything OK!
Then I Installed the modded Gcam and its working perfectly! (Didn't work for me on the previous build)
Also Double Tap to Wake is working with the new Rom
Sadly the audio and proximity call issues still persists (for me atleast). I'm using the google dialer that came with the gapps. When someone calls there is no audio sometimes and the proximity sensor is not always working. It works now
Changing the Accent Color under Theming in the RR-Settings crashes the Lineage-OS Settings and Accent Color stays on the standard one.
Heres the Log for this crash:
Code:
build.cpu_abi2:
build.device: chiron
build.display: rr_chiron-userdebug 8.1.0 OPM1.171019.021 abb4372266 test-keys
build.fingerprint: Xiaomi/chiron/chiron:7.1.1/NMF26X/V9.0.1.0.NCAMIEI:user/release-keys
build.hardware: qcom
build.host: arasthel-pc
build.id: OPM1.171019.021
build.manufacturer: Xiaomi
build.model: MI Mix 2
build.product: chiron
build.radio: AT20-0307_2248_6af8a53
build.serial: c1772223
build.tags: release-keys
build.time: 1520578480000
build.type: user
build.user: arasthel
version.codename: REL
version.incremental: abb4372266
version.release: 8.1.0
version.sdk_int: 27
03-11 10:57:13.018 E/BufferItemConsumer(3486): [unnamed-3486-49] Failed to release buffer: Unknown error -1 (1)
03-11 10:57:13.055 E/BufferItemConsumer(3486): [unnamed-3486-50] Failed to release buffer: Unknown error -1 (1)
03-11 10:57:13.166 E/BufferItemConsumer(3486): [unnamed-3486-51] Failed to release buffer: Unknown error -1 (1)
03-11 10:57:13.219 E/BufferItemConsumer(3486): [unnamed-3486-52] Failed to release buffer: Unknown error -1 (1)
03-11 10:57:16.859 E/AndroidRuntime(17391): FATAL EXCEPTION: main
03-11 10:57:16.859 E/AndroidRuntime(17391): Process: org.lineageos.lineageparts, PID: 17391
03-11 10:57:16.859 E/AndroidRuntime(17391): java.lang.NullPointerException: Attempt to invoke interface method 'boolean android.content.om.IOverlayManager.setEnabled(java.lang.String, boolean, int)' on a null object reference
03-11 10:57:16.859 E/AndroidRuntime(17391): at android.os.Parcel.readException(Parcel.java:2010)
03-11 10:57:16.859 E/AndroidRuntime(17391): at android.os.Parcel.readException(Parcel.java:1950)
03-11 10:57:16.859 E/AndroidRuntime(17391): at lineageos.style.IStyleInterface$Stub$Proxy.setAccent(IStyleInterface.java:155)
03-11 10:57:16.859 E/AndroidRuntime(17391): at lineageos.style.StyleInterface.setAccent(StyleInterface.java:167)
03-11 10:57:16.859 E/AndroidRuntime(17391): at org.lineageos.lineageparts.style.StylePreferences.onAccentSelected(StylePreferences.java:159)
03-11 10:57:16.859 E/AndroidRuntime(17391): at org.lineageos.lineageparts.style.StylePreferences.lambda$-org_lineageos_lineageparts_style_StylePreferences_4880(StylePreferences.java:132)
03-11 10:57:16.859 E/AndroidRuntime(17391): at org.lineageos.lineageparts.style.-$Lambda$lxyhs0tIpn-38teX3F3AjZP7qNg$1.$m$0(Unknown Source:4)
03-11 10:57:16.859 E/AndroidRuntime(17391): at org.lineageos.lineageparts.style.-$Lambda$lxyhs0tIpn-38teX3F3AjZP7qNg$1.onClick(Unknown Source:11)
03-11 10:57:16.859 E/AndroidRuntime(17391): at com.android.internal.app.AlertController$AlertParams$3.onItemClick(AlertController.java:1142)
03-11 10:57:16.859 E/AndroidRuntime(17391): at android.widget.AdapterView.performItemClick(AdapterView.java:318)
03-11 10:57:16.859 E/AndroidRuntime(17391): at android.widget.AbsListView.performItemClick(AbsListView.java:1196)
03-11 10:57:16.859 E/AndroidRuntime(17391): at android.widget.AbsListView$PerformClick.run(AbsListView.java:3284)
03-11 10:57:16.859 E/AndroidRuntime(17391): at android.widget.AbsListView$4.run(AbsListView.java:4207)
03-11 10:57:16.859 E/AndroidRuntime(17391): at android.os.Handler.handleCallback(Handler.java:790)
03-11 10:57:16.859 E/AndroidRuntime(17391): at android.os.Handler.dispatchMessage(Handler.java:99)
03-11 10:57:16.859 E/AndroidRuntime(17391): at android.os.Looper.loop(Looper.java:164)
03-11 10:57:16.859 E/AndroidRuntime(17391): at android.app.ActivityThread.main(ActivityThread.java:6494)
03-11 10:57:16.859 E/AndroidRuntime(17391): at java.lang.reflect.Method.invoke(Native Method)
03-11 10:57:16.859 E/AndroidRuntime(17391): at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:440)
03-11 10:57:16.859 E/AndroidRuntime(17391): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)
03-11 10:57:19.001 E/BufferItemConsumer(3486): [unnamed-3486-53] Failed to release buffer: Unknown error -1 (1)
03-11 10:57:19.042 E/BufferItemConsumer(3486): [unnamed-3486-54] Failed to release buffer: Unknown error -1 (1)
03-11 10:57:19.202 E/BufferItemConsumer(3486): [unnamed-3486-55] Failed to release buffer: Unknown error -1 (1)
03-11 10:57:19.253 E/BufferItemConsumer(3486): [unnamed-3486-56] Failed to release buffer: Unknown error -1 (1)
Auto Brightness still not working for me It works
The idle battery drain seems to be fixed now, no more battery drain overnight
I hope the call issue gets fixed asap. Thats the only major problem imo. The other bugs are only minor, I can live with them .
The rest is working perfectly (ok VoLTE maybe not, but i'm not using it anyway ). Really smooth Rom, great battery Life and everything else works great.
Good job!

rafik25 said:
Cant unlock device with fingerprint when always on is activ
Click to expand...
Click to collapse
Always On Display shouldn't have been enabled in the first place, that was my bad. It will eat your battery in devices with IPS displays - such as the Mix 2. I will fix this in the next version, just disable it until then.
@Kartoffl: thanks for the feedback!
About AOD: see above.
Accent color: I just changed it several times without any issues, but I'll try to find what could cause the issue on your phone.
Autobrightness: just tested it, I placed my hand over the lower half of the device and it went darker after ~5s, set another phone with flashlight ON over it and got 100% bright in a couple of seconds.
Proximity: I'll also have a look at that.
Battery drain: glad to hear it

Arasthel said:
Always On Display shouldn't have been enabled in the first place, that was my bad. It will eat your battery in devices with IPS displays - such as the Mix 2. I will fix this in the next version, just disable it until then.
@Kartoffl: thanks for the feedback!
About AOD: see above.
Accent color: I just changed it several times without any issues, but I'll try to find what could cause the issue on your phone.
Autobrightness: just tested it, I placed my hand over the lower half of the device and it went darker after ~5s, set another phone with flashlight ON over it and got 100% bright in a couple of seconds.
Proximity: I'll also have a look at that.
Battery drain: glad to hear it
Click to expand...
Click to collapse
I think bro ambiant display its better

Arasthel said:
Accent color: I just changed it several times without any issues, but I'll try to find what could cause the issue on your phone.
Autobrightness: just tested it, I placed my hand over the lower half of the device and it went darker after ~5s, set another phone with flashlight ON over it and got 100% bright in a couple of seconds.
Click to expand...
Click to collapse
You were right, autobrightness is somehow working! The slider doesn't change when the autobrightness changes though. The autobrightness feature just doesn't feel working correctly.
It would be great if you can look into the accent color crash issue. Heres another log if it can help! Also my System Info
Code:
03-11 13:00:24.555 E/SurfaceFlinger(733): Failed to find layer (AtchDlg:com.nolanlawson.logcat/com.nolanlawson.logcat.LogcatActivity#0) in layer parent (no-parent).
03-11 13:00:31.942 E/ActivityManager(2929): applyOptionsLocked: Unknown animationType=0
03-11 13:00:32.006 E/BatteryExternalStatsWorker(2929): no controller energy info supplied for bluetooth
03-11 13:00:32.022 E/QCOM PowerHAL(710): extract_stats: failed to open: /d/wlan0/power_stats Error = Operation not permitted
03-11 13:00:47.781 E/SurfaceFlinger(733): Failed to find layer (com.android.settings/com.android.settings.SubSettings#0) in layer parent (no-parent).
03-11 13:00:49.306 E/AndroidRuntime(16012): FATAL EXCEPTION: main
03-11 13:00:49.306 E/AndroidRuntime(16012): Process: org.lineageos.lineageparts, PID: 16012
03-11 13:00:49.306 E/AndroidRuntime(16012): java.lang.NullPointerException: Attempt to invoke interface method 'boolean android.content.om.IOverlayManager.setEnabled(java.lang.String, boolean, int)' on a null object reference
03-11 13:00:49.306 E/AndroidRuntime(16012): at android.os.Parcel.readException(Parcel.java:2010)
03-11 13:00:49.306 E/AndroidRuntime(16012): at android.os.Parcel.readException(Parcel.java:1950)
03-11 13:00:49.306 E/AndroidRuntime(16012): at lineageos.style.IStyleInterface$Stub$Proxy.setAccent(IStyleInterface.java:155)
03-11 13:00:49.306 E/AndroidRuntime(16012): at lineageos.style.StyleInterface.setAccent(StyleInterface.java:167)
03-11 13:00:49.306 E/AndroidRuntime(16012): at org.lineageos.lineageparts.style.StylePreferences.onAccentSelected(StylePreferences.java:159)
03-11 13:00:49.306 E/AndroidRuntime(16012): at org.lineageos.lineageparts.style.StylePreferences.lambda$-org_lineageos_lineageparts_style_StylePreferences_4880(StylePreferences.java:132)
03-11 13:00:49.306 E/AndroidRuntime(16012): at org.lineageos.lineageparts.style.-$Lambda$lxyhs0tIpn-38teX3F3AjZP7qNg$1.$m$0(Unknown Source:4)
03-11 13:00:49.306 E/AndroidRuntime(16012): at org.lineageos.lineageparts.style.-$Lambda$lxyhs0tIpn-38teX3F3AjZP7qNg$1.onClick(Unknown Source:11)
03-11 13:00:49.306 E/AndroidRuntime(16012): at com.android.internal.app.AlertController$AlertParams$3.onItemClick(AlertController.java:1142)
03-11 13:00:49.306 E/AndroidRuntime(16012): at android.widget.AdapterView.performItemClick(AdapterView.java:318)
03-11 13:00:49.306 E/AndroidRuntime(16012): at android.widget.AbsListView.performItemClick(AbsListView.java:1196)
03-11 13:00:49.306 E/AndroidRuntime(16012): at android.widget.AbsListView$PerformClick.run(AbsListView.java:3284)
03-11 13:00:49.306 E/AndroidRuntime(16012): at android.widget.AbsListView$4.run(AbsListView.java:4207)
03-11 13:00:49.306 E/AndroidRuntime(16012): at android.os.Handler.handleCallback(Handler.java:790)
03-11 13:00:49.306 E/AndroidRuntime(16012): at android.os.Handler.dispatchMessage(Handler.java:99)
03-11 13:00:49.306 E/AndroidRuntime(16012): at android.os.Looper.loop(Looper.java:164)
03-11 13:00:49.306 E/AndroidRuntime(16012): at android.app.ActivityThread.main(ActivityThread.java:6494)
03-11 13:00:49.306 E/AndroidRuntime(16012): at java.lang.reflect.Method.invoke(Native Method)
03-11 13:00:49.306 E/AndroidRuntime(16012): at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:440)
03-11 13:00:49.306 E/AndroidRuntime(16012): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)
03-11 13:00:50.806 E/SurfaceFlinger(733): Failed to find layer (org.lineageos.lineageparts/org.lineageos.lineageparts.style.StylePreferences#1) in layer parent (no-parent).
03-11 13:00:50.848 E/BufferItemConsumer(3459): [unnamed-3459-16] Failed to release buffer: Unknown error -1 (1)
03-11 13:00:50.880 E/BufferItemConsumer(3459): [unnamed-3459-17] Failed to release buffer: Unknown error -1 (1)
03-11 13:00:50.998 E/BufferItemConsumer(3459): [unnamed-3459-18] Failed to release buffer: Unknown error -1 (1)
03-11 13:00:51.064 E/BufferItemConsumer(3459): [unnamed-3459-19] Failed to release buffer: Unknown error -1 (1)
03-11 13:01:02.138 E/SurfaceFlinger(733): Failed to find layer (AtchDlg:com.nolanlawson.logcat/com.nolanlawson.logcat.LogcatActivity#0) in layer parent (no-parent).

I flash this rom, when i setup all, camera can be work,
after i reboot, open the camera it show can't connect,
why??

Camera Issues
Thanks for everyones work, here.
I finally have a stock Oreo on my Mi Mix2. However, have some camera issues.
I did install the Camera2API Magisk module.
But
Then I Installed the modded Gcam and its working perfectly! (Didn't work for me on the previous build)
Click to expand...
Click to collapse
I did not let me install the apk. Had to remove the original camera (installed the Gapps stock version) and reboot.
What packages did you install? There are several APKs and Zips (some Magisk, some apparently for installing with TWRP) in the modded Gcam link?
Sound over Bluetooth ist working for me, btw

Noticed a bug, actually this has been happening to me on stock miui as well. Charge the phone over night and only charges to 75%. Could be accubattery app I have installed only let's you charge up to certain percentage to save the life of battery. Everything else is running good.

com.android.statementservice regularly crashing on LineageOS for microg

Hi,
I have just installed LineageOS for microg 19 (19-20220522-microg-bramble) on my Pixel 4a 5g and I am receiving a regular popup every few minutes saying that "Intent Filter Verification Service has stopped".
From what I have read this is used to call another application on the phone (based on what type of thing needs to be handled)??
The logs I am getting with logcat do not seem to lead me towards anything (see below from two examples). I'm not sure if anyone has any suggestions on what could be causing this or where else I can look??
My suspicion is that this is something to do with not having the google apps (using microg instead) but not sure. I did find one other mention of it here, but no solution
Note: I did have LineageOS for microg 18 installed previously which did not exhibit this behaviour...
Example1:
Code:
05-31 23:53:49.627 966 966 D Zygote : Forked child process 10622
05-31 23:53:49.628 1718 2114 I ActivityManager: Start proc 10622:com.android.statementservice/u0a74 for service {com.android.statementservice/androidx.work.impl.background.systemjob.SystemJobService}
05-31 23:53:49.632 10622 10622 I libc : SetHeapTaggingLevel: tag level set to 0
05-31 23:53:49.644 1357 1429 I adbd : jdwp connection from 10622
05-31 23:53:49.646 10622 10622 D ProcessState: Binder ioctl to enable oneway spam detection failed: Invalid argument
05-31 23:53:49.638 0 0 I : c7 10622 binder: 10622:10622 ioctl 40046210 7fea0fb8d4 returned -22
05-31 23:53:49.651 1718 14826 D CompatibilityChangeReporter: Compat change id reported: 168419799; UID 10074; state: DISABLED
05-31 23:53:49.655 10622 10622 D CompatibilityChangeReporter: Compat change id reported: 171979766; UID 10074; state: DISABLED
05-31 23:53:49.658 10622 10622 D ApplicationLoaders: Returning zygote-cached class loader: /system/framework/android.test.base.jar
05-31 23:53:49.667 10622 10622 V GraphicsEnvironment: ANGLE Developer option for 'com.android.statementservice' set to: 'default'
05-31 23:53:49.667 10622 10622 V GraphicsEnvironment: ANGLE GameManagerService for com.android.statementservice: false
05-31 23:53:49.668 10622 10622 V GraphicsEnvironment: Neither updatable production driver nor prerelease driver is supported.
05-31 23:53:49.668 10622 10622 D NetworkSecurityConfig: No Network Security Config specified, using platform default
05-31 23:53:49.668 10622 10622 D NetworkSecurityConfig: No Network Security Config specified, using platform default
05-31 23:53:49.687 10622 10639 D CompatibilityChangeReporter: Compat change id reported: 160794467; UID 10074; state: DISABLED
05-31 23:53:49.689 1718 14826 D CompatibilityChangeReporter: Compat change id reported: 171306433; UID 10074; state: DISABLED
05-31 23:53:49.757 10622 10641 E AndroidRuntime: FATAL EXCEPTION: pool-3-thread-2
05-31 23:53:49.757 10622 10641 E AndroidRuntime: Process: com.android.statementservice, PID: 10622
05-31 23:53:49.757 10622 10641 E AndroidRuntime: java.lang.IllegalStateException: Data cannot occupy more than 10240 bytes when serialized
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at androidx.work.Data.toByteArrayInternal(Data.java:417)
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at androidx.work.Data$Builder.build(Data.java:846)
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at androidx.work.OverwritingInputMerger.merge(OverwritingInputMerger.java:44)
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at androidx.work.impl.WorkerWrapper.runWorker(WorkerWrapper.java:227)
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at androidx.work.impl.WorkerWrapper.run(WorkerWrapper.java:137)
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at androidx.work.impl.utils.SerialExecutor$Task.run(SerialExecutor.java:91)
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
05-31 23:53:49.757 10622 10641 E AndroidRuntime: at java.lang.Thread.run(Thread.java:920)
05-31 23:53:49.761 1718 10645 I DropBoxManagerService: add tag=system_app_crash isTagEnabled=true flags=0x2
05-31 23:53:49.762 10622 10641 I Process : Sending signal. PID: 10622 SIG: 9
05-31 23:53:49.782 1718 14826 I ActivityManager: Process com.android.statementservice (pid 10622) has died: cch+5 CEM
05-31 23:53:49.782 1718 2118 I libprocessgroup: Successfully killed process cgroup uid 10074 pid 10622 in 0ms
05-31 23:53:49.782 966 966 I Zygote : Process 10622 exited due to signal 9 (Killed)
Example2:
Code:
05-31 23:54:24.620 966 966 D Zygote : Forked child process 10707
05-31 23:54:24.620 1718 2114 I ActivityManager: Start proc 10707:com.android.statementservice/u0a74 for service {com.android.statementservice/androidx.work.impl.background.systemjob.SystemJobService}
05-31 23:54:24.625 10707 10707 I libc : SetHeapTaggingLevel: tag level set to 0
05-31 23:54:24.639 1357 1429 I adbd : jdwp connection from 10707
05-31 23:54:24.640 10707 10707 D ProcessState: Binder ioctl to enable oneway spam detection failed: Invalid argument
05-31 23:54:24.633 0 0 I : c3 10707 binder: 10707:10707 ioctl 40046210 7fea0fb8d4 returned -22
05-31 23:54:24.650 1718 14826 D CompatibilityChangeReporter: Compat change id reported: 168419799; UID 10074; state: DISABLED
05-31 23:54:24.654 10707 10707 D CompatibilityChangeReporter: Compat change id reported: 171979766; UID 10074; state: DISABLED
05-31 23:54:24.660 10707 10707 D ApplicationLoaders: Returning zygote-cached class loader: /system/framework/android.test.base.jar
05-31 23:54:24.678 10707 10707 V GraphicsEnvironment: ANGLE Developer option for 'com.android.statementservice' set to: 'default'
05-31 23:54:24.678 10707 10707 V GraphicsEnvironment: ANGLE GameManagerService for com.android.statementservice: false
05-31 23:54:24.679 10707 10707 V GraphicsEnvironment: Neither updatable production driver nor prerelease driver is supported.
05-31 23:54:24.680 10707 10707 D NetworkSecurityConfig: No Network Security Config specified, using platform default
05-31 23:54:24.680 10707 10707 D NetworkSecurityConfig: No Network Security Config specified, using platform default
05-31 23:54:24.699 10707 10724 D CompatibilityChangeReporter: Compat change id reported: 160794467; UID 10074; state: DISABLED
05-31 23:54:24.700 1718 4358 D CompatibilityChangeReporter: Compat change id reported: 171306433; UID 10074; state: DISABLED
05-31 23:54:24.726 1315 1315 I cnss-daemon: nl80211 response handler invoked
05-31 23:54:24.726 1315 1315 I cnss-daemon: nl80211_response_handler: cmd 103, vendorID 4980, subcmd 13 received
05-31 23:54:24.727 1017 2427 I WifiHAL : event received NL80211_CMD_VENDOR, vendor_id = 0x1374, subcmd = 0xd
05-31 23:54:24.765 10707 10726 E AndroidRuntime: FATAL EXCEPTION: pool-3-thread-2
05-31 23:54:24.765 10707 10726 E AndroidRuntime: Process: com.android.statementservice, PID: 10707
05-31 23:54:24.765 10707 10726 E AndroidRuntime: java.lang.IllegalStateException: Data cannot occupy more than 10240 bytes when serialized
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at androidx.work.Data.toByteArrayInternal(Data.java:417)
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at androidx.work.Data$Builder.build(Data.java:846)
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at androidx.work.OverwritingInputMerger.merge(OverwritingInputMerger.java:44)
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at androidx.work.impl.WorkerWrapper.runWorker(WorkerWrapper.java:227)
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at androidx.work.impl.WorkerWrapper.run(WorkerWrapper.java:137)
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at androidx.work.impl.utils.SerialExecutor$Task.run(SerialExecutor.java:91)
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
05-31 23:54:24.765 10707 10726 E AndroidRuntime: at java.lang.Thread.run(Thread.java:920)
05-31 23:54:24.768 1718 10731 I DropBoxManagerService: add tag=system_app_crash isTagEnabled=true flags=0x2

Sorry I don't have a solution for you but since you are using LineageOS+microG on a Pixel phone, you might be interested in switching to CalyxOS as they seem to already have a workaround in place even though the bug isn't fixed yet.
See here under "Issues":
CalyxOS News
📰 Read about what we're working on, important announcements, and upcoming events.
calyxos.org
Relevant commit:
https://review.calyxos.org/c/CalyxOS/vendor_calyx/+/7976
As a bonus, with CalyxOS you also get better security than just LineageOS+microG thanks to bootloader relocking.

I am suffered by that bug too. I can't see any harm by this, but it is annoying. The patch in CalyxOS is just to hide that problem as a workaround.

I filed a bug report here:
Intent filter verification service / com.android.statementservice regularly crashing on LineageOS for microg · Issue #1740 · microg/GmsCore
I am aware this is a very unclear specification of a bug. It is not clear who and what is responsible for this - can be also Android12 (LOS). But it seems to be that the combination of LOS and micr...
github.com
Please report there all your findings @maloo1 and @johnfocker

So I ended up following @johnfocker's suggestion and installed CalyxOS (android 12) and it does "fix" the issue.
I guess Calyx is a perfect fit for my needs anyway (microg, locked boot loader, great polished daily driver) so Ill probably stick with it unless I end up with a phone that is not supported.
It would make sense to have it fixed in microg thou if thats the root cause... I'll see what I can add to the bug...
Thanks again!

Very strange. The messages disappear to pop up after some time.
Lately I installe the new Magisk 25 and BetterBatteryStats (XDA) and it appears again - althoug I am not sure that was really reason. There is continiously changes in phone, so difficult to nail it down.

Quote from flipreverse:
This seems to be a bug in AOSP: https://android.googlesource.com/platform/frameworks/base/+/4978d1ad10293900e9b5feea349abd09ceb6e710
The LOS repo android_frameworks_base does not have this commit at the moment. I'll cherry-pick that one, and give it a try.
Click to expand...
Click to collapse

ale5000 said:
Quote from flipreverse:
Click to expand...
Click to collapse
ist this the bug fix?
https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/334683

kurtn said:
ist this the bug fix?
https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/334683
Click to expand...
Click to collapse
Yes.

ale5000 said:
Yes.
Click to expand...
Click to collapse
Just too late for the lineage.microg.org August round of builds.