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
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
Wifi P2P ("WiFi Direct") support - does anyone know of patches for this on Pie?
Pretty much exactly as the subject line states.
When doing anything which brings up a P2P interface (right now, that's "cast" or "wifi direct" under settings / wifi / advanced):
Code:
02-05 22:44:33.565 10656 10744 I WifiP2pNative: P2P interface teardown completed
02-05 22:44:33.565 10656 10744 E WifiP2pService: Failed to setup interface for P2P
02-05 22:44:33.565 10656 10744 D WifiP2pNative: P2P InterfaceAvailableListener false
02-05 22:44:33.565 10656 10744 D WifiP2pService: Wifi enabled=true, P2P Interface availability=false
02-05 22:44:33.565 10656 10744 D WifiP2pNative: P2P InterfaceDestroyedListener p2p0
02-05 22:44:33.565 10656 10744 D WifiP2pNative: Ignoring stale interface destroyed listener
02-05 22:44:33.565 10656 10744 D WifiP2pNative: P2P InterfaceAvailableListener true
02-05 22:44:33.565 10656 10744 D WifiP2pService: Wifi enabled=true, P2P Interface availability=true, Number of clients=1
02-05 22:44:33.565 10656 10744 D WifiP2pService: Wifi enabled=true, P2P Interface availability=true
02-05 22:44:33.566 10656 10744 D WifiP2pNative: Setup P2P interface
02-05 22:44:33.566 10656 10744 D HalDevMgr: createIface: ifaceType=2, lowPriority=false
02-05 22:44:33.566 10656 10744 D HalDevMgr: getAllChipInfo
02-05 22:44:33.566 10656 10744 D HalDevMgr: getChipIds=[0]
02-05 22:44:33.567 23753 23753 D WifiSettings: onAccessPointsChanged (WifiTracker) callback initiated
02-05 22:44:33.567 10656 10744 D HalDevMgr: validateInterfaceCache
02-05 22:44:33.567 10656 10744 D HalDevMgr: createIfaceIfPossible: chipInfos=[{chipId=0, availableModes=[{.id = 0, .availableCombinations = [{.limits = [{.types = [0], .maxIfaces = 1}, {.types = [2], .maxIfaces = 1}]}]}, {.id = 1, .availableCombinations = [{.limits = [{.types = [1], .maxIfaces = 1}]}]}], currentModeIdValid=true, currentModeId=0, ifaces[1].length=0, ifaces[0].length=1, ifaces[2].length=0, ifaces[3].length=0)], ifaceType=2, lowPriority=false
02-05 22:44:33.567 10656 10744 D HalDevMgr: {.limits = [{.types = [0], .maxIfaces = 1}, {.types = [2], .maxIfaces = 1}]} expands to [[1, 0, 1, 0]]
02-05 22:44:33.568 10656 10744 D HalDevMgr: canIfaceComboSupportRequest: chipInfo={chipId=0, availableModes=[{.id = 0, .availableCombinations = [{.limits = [{.types = [0], .maxIfaces = 1}, {.types = [2], .maxIfaces = 1}]}]}, {.id = 1, .availableCombinations = [{.limits = [{.types = [1], .maxIfaces = 1}]}]}], currentModeIdValid=true, currentModeId=0, ifaces[1].length=0, ifaces[0].length=1, ifaces[2].length=0, ifaces[3].length=0), chipMode={.id = 0, .availableCombinations = [{.limits = [{.types = [0], .maxIfaces = 1}, {.types = [2], .maxIfaces = 1}]}]}, chipIfaceCombo=[[email protected], ifaceType=2, lowPriority=false
02-05 22:44:33.568 10656 10744 D HalDevMgr: compareIfaceCreationData: val1={chipInfo={chipId=0, availableModes=[{.id = 0, .availableCombinations = [{.limits = [{.types = [0], .maxIfaces = 1}, {.types = [2], .maxIfaces = 1}]}]}, {.id = 1, .availableCombinations = [{.limits = [{.types = [1], .maxIfaces = 1}]}]}], currentModeIdValid=true, currentModeId=0, ifaces[1].length=0, ifaces[0].length=1, ifaces[2].length=0, ifaces[3].length=0), chipModeId=0, interfacesToBeRemovedFirst=[]), val2=null
02-05 22:44:33.568 10656 10744 D HalDevMgr: new proposal accepted
02-05 22:44:33.568 10656 10744 D HalDevMgr: {.limits = [{.types = [1], .maxIfaces = 1}]} expands to [[0, 1, 0, 0]]
02-05 22:44:33.568 10656 10744 D HalDevMgr: canIfaceComboSupportRequest: chipInfo={chipId=0, availableModes=[{.id = 0, .availableCombinations = [{.limits = [{.types = [0], .maxIfaces = 1}, {.types = [2], .maxIfaces = 1}]}]}, {.id = 1, .availableCombinations = [{.limits = [{.types = [1], .maxIfaces = 1}]}]}], currentModeIdValid=true, currentModeId=0, ifaces[1].length=0, ifaces[0].length=1, ifaces[2].length=0, ifaces[3].length=0), chipMode={.id = 1, .availableCombinations = [{.limits = [{.types = [1], .maxIfaces = 1}]}]}, chipIfaceCombo=[[email protected], ifaceType=2, lowPriority=false
02-05 22:44:33.568 10656 10744 D HalDevMgr: Requested type not supported by combo
02-05 22:44:33.568 10656 10744 D HalDevMgr: compareIfaceCreationData: val1=null, val2={chipInfo={chipId=0, availableModes=[{.id = 0, .availableCombinations = [{.limits = [{.types = [0], .maxIfaces = 1}, {.types = [2], .maxIfaces = 1}]}]}, {.id = 1, .availableCombinations = [{.limits = [{.types = [1], .maxIfaces = 1}]}]}], currentModeIdValid=true, currentModeId=0, ifaces[1].length=0, ifaces[0].length=1, ifaces[2].length=0, ifaces[3].length=0), chipModeId=0, interfacesToBeRemovedFirst=[])
02-05 22:44:33.568 10656 10744 D HalDevMgr: executeChipReconfiguration: ifaceCreationData={chipInfo={chipId=0, availableModes=[{.id = 0, .availableCombinations = [{.limits = [{.types = [0], .maxIfaces = 1}, {.types = [2], .maxIfaces = 1}]}]}, {.id = 1, .availableCombinations = [{.limits = [{.types = [1], .maxIfaces = 1}]}]}], currentModeIdValid=true, currentModeId=0, ifaces[1].length=0, ifaces[0].length=1, ifaces[2].length=0, ifaces[3].length=0), chipModeId=0, interfacesToBeRemovedFirst=[]), ifaceType=2
02-05 22:44:33.568 10656 10744 D HalDevMgr: isModeConfigNeeded=false
02-05 22:44:33.568 10656 10793 D HalDevMgr: onIfaceAdded: type=2, name=p2p0
02-05 22:44:33.568 10656 10744 D HalDevMgr: createIfaceIfPossible: added cacheEntry={name=p2p0, type=2, destroyedListeners.size()=1, creationTime=89382364, isLowPriority=false}
02-05 22:44:33.569 10656 10744 D HalDevMgr: dispatchAvailableForRequestListeners
02-05 22:44:33.569 10656 10744 D HalDevMgr: getAllChipInfo
02-05 22:44:33.569 10656 10744 D HalDevMgr: getChipIds=[0]
02-05 22:44:33.569 23753 23761 W System : A resource failed to call close.
02-05 22:44:33.571 10656 10744 D HalDevMgr: dispatchAvailableForRequestListeners: chipInfos=[{chipId=0, availableModes=[{.id = 0, .availableCombinations = [{.limits = [{.types = [0], .maxIfaces = 1}, {.types = [2], .maxIfaces = 1}]}]}, {.id = 1, .availableCombinations = [{.limits = [{.types = [1], .maxIfaces = 1}]}]}], currentModeIdValid=true, currentModeId=0, ifaces[1].length=0, ifaces[0].length=1, ifaces[2].length=1, ifaces[3].length=0)]
02-05 22:44:33.571 10656 10744 D HalDevMgr: dispatchAvailableForRequestListenersForType: ifaceType=1
02-05 22:44:33.571 10656 10744 D HalDevMgr: dispatchAvailableForRequestListenersForType: ifaceType=0
02-05 22:44:33.571 10656 10744 D HalDevMgr: dispatchAvailableForRequestListenersForType: ifaceType=2
02-05 22:44:33.571 23753 23753 D WifiSettings: onAccessPointsChanged (WifiTracker) callback initiated
02-05 22:44:33.571 10656 10744 D HalDevMgr: isItPossibleToCreateIface: chipInfos=[{chipId=0, availableModes=[{.id = 0, .availableCombinations = [{.limits = [{.types = [0], .maxIfaces = 1}, {.types = [2], .maxIfaces = 1}]}]}, {.id = 1, .availableCombinations = [{.limits = [{.types = [1], .maxIfaces = 1}]}]}], currentModeIdValid=true, currentModeId=0, ifaces[1].length=0, ifaces[0].length=1, ifaces[2].length=1, ifaces[3].length=0)], ifaceType=2
02-05 22:44:33.571 10656 10744 D HalDevMgr: {.limits = [{.types = [0], .maxIfaces = 1}, {.types = [2], .maxIfaces = 1}]} expands to [[1, 0, 1, 0]]
02-05 22:44:33.571 10656 10744 D HalDevMgr: canIfaceComboSupportRequest: chipInfo={chipId=0, availableModes=[{.id = 0, .availableCombinations = [{.limits = [{.types = [0], .maxIfaces = 1}, {.types = [2], .maxIfaces = 1}]}]}, {.id = 1, .availableCombinations = [{.limits = [{.types = [1], .maxIfaces = 1}]}]}], currentModeIdValid=true, currentModeId=0, ifaces[1].length=0, ifaces[0].length=1, ifaces[2].length=1, ifaces[3].length=0), chipMode={.id = 0, .availableCombinations = [{.limits = [{.types = [0], .maxIfaces = 1}, {.types = [2], .maxIfaces = 1}]}]}, chipIfaceCombo=[[email protected], ifaceType=2, lowPriority=false
02-05 22:44:33.571 10656 10744 D HalDevMgr: Would need to delete some higher priority interfaces
02-05 22:44:33.571 10656 10744 D HalDevMgr: {.limits = [{.types = [1], .maxIfaces = 1}]} expands to [[0, 1, 0, 0]]
02-05 22:44:33.571 10656 10744 D HalDevMgr: canIfaceComboSupportRequest: chipInfo={chipId=0, availableModes=[{.id = 0, .availableCombinations = [{.limits = [{.types = [0], .maxIfaces = 1}, {.types = [2], .maxIfaces = 1}]}]}, {.id = 1, .availableCombinations = [{.limits = [{.types = [1], .maxIfaces = 1}]}]}], currentModeIdValid=true, currentModeId=0, ifaces[1].length=0, ifaces[0].length=1, ifaces[2].length=1, ifaces[3].length=0), chipMode={.id = 1, .availableCombinations = [{.limits = [{.types = [1], .maxIfaces = 1}]}]}, chipIfaceCombo=[[email protected], ifaceType=2, lowPriority=false
02-05 22:44:33.571 10656 10744 D HalDevMgr: Requested type not supported by combo
02-05 22:44:33.571 10656 10744 D HalDevMgr: Interface available for: ifaceType=2 = false
02-05 22:44:33.572 10656 10744 D HalDevMgr: Interface available listener dispatched: ifaceType=2, listener=com.android.server.[email protected]2c40602
02-05 22:44:33.572 10656 10744 D HalDevMgr: dispatchAvailableForRequestListenersForType: ifaceType=3
02-05 22:44:33.573 10656 10744 I android_os_HwBinder: HwBinder: Starting thread pool for default::[email protected]::ISupplicant
02-05 22:44:33.574 23753 23753 D WifiSettings: onAccessPointsChanged (WifiTracker) callback initiated
02-05 22:44:33.574 10656 10744 D SupplicantP2pIfaceHal: entering getInterface()
02-05 22:44:33.574 10656 10744 E SupplicantP2pIfaceHal: initSupplicantP2pIface got null iface
02-05 22:44:33.574 10656 10744 E WifiP2pNative: Failed to setup P2p iface in supplicant
02-05 22:44:33.574 10656 10744 D WifiP2pNative: Teardown P2P interface
02-05 22:44:33.574 10656 10744 D HalDevMgr: removeIfaceInternal: iface(name)=p2p0, type=2
02-05 22:44:33.574 10656 10744 D HalDevMgr: getChip: iface(name)=p2p0
02-05 22:44:33.575 10656 10744 D HalDevMgr: dispatchDestroyedListeners: iface(name)=p2p0
02-05 22:44:33.575 10656 10744 D HalDevMgr: dispatchAvailableForRequestListeners
02-05 22:44:33.575 10656 10744 D HalDevMgr: getAllChipInfo
Basically, system_server goes into a tight loop trying and failing repeatedly to bring up p2p0.
This is on Huawei, for what it's worth (Mate 8 - NXT-DL00C17 8.0.0.820; Mate 9 - MHA-AL00C00 8.0.0.374), though given that there are other changes which seem pretty general regarding the wifi HAL between 8.0 and 9.0, it seems likely that there are other things happening that are causing problems and I haven't quite figured it out yet.
For what it's worth: the reason for wanting this is because I've ported Miracast support from Oreo into Pie, and it works on devices I have here with P vendor (Mate 9 AL00C00 9.0.1.150; also apparently working on HMA), but since bringing up the WiFi P2P interface is broken, I can't get any farther with it than that.
Not sure if you resolved the issue yet but on C636 running 9.0.1.159 Miracast seems to work. I can share my phone screen to my Android TV box without problem.
itenos said:
Not sure if you resolved the issue yet but on C636 running 9.0.1.159 Miracast seems to work. I can share my phone screen to my Android TV box without problem.
Click to expand...
Click to collapse
Nah, on EMUI it's fine - in this case, its for AOSP Pie built for an EMUI 8 vendor, and there was a good amount of stuff that changed with the WiFi HAL on Pie that caused things to break besides for the bare minimum of functionality needed for wifi to work in the first place. (Hotspot was broken without a HAL being written to provide backwards compatibility behavior, WiFi Direct is broken in the same fashion, I think, but I'm not sure.)
It's also fine if you're already on a Pie vendor - Miracast works fine here on AOSP (with patches to pull Miracast forward from Oreo, of course) on both the Mate 9 (AL00, 9.0.1.150), and the P10 (AL00, 9.0.1.160; C432, 9.0.1.165).
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.