Develop Bugs

[Guide] How To Logcat

I think this one is definitely needed for this forum as i am seeing more and more users ask how to logcat. So posting this here.
Here's how to use logcat:
There are two main ways to do a logcat, within android, and through adb.
Logcat within android can be done one of two ways, through a Logcat app:
Here are two good examples are either: aLogcat or Catlog
I prefer catlog, because in my opinion it has a little bit nicer UI. Both of these programs can dump their logs to a txt file, which is very useful for debugging. Or, you can do it in terminal emulator (same rules as running through adb(see below))
From Moscow Desire:
On the other hand, using adb to run logcat, in my opinion is much more useful, because you can start using it when android boots (i.e. once the boot animation appears.)
The code for logcat to output to a file is
Code:
adb logcat > name of problem.txt
you can also do
Code:
adb logcat -f name of problem.txt
how I prefer to do it is this way:
Code:
adb logcat -v long > name of problem.txt
with the -v flag & the long argument, it changes output to long style, which means every line of logcat will be on its own line (makes it a little neater, imo)
Note: When outputting to a file, you will see a newline, but nothing printed, this is normal. To stop logcat from writting to a file, you need to press ctrl+c.
Here's where using logcat (via adb makes life really easy)
Lets say you find a problem you're having after looking at a logcat.
For example:
When I was trying to use a different ramdisk, wifi wouldn't work so I got a logcat that's almost 1300 lines long (a lot of stuff happens in the background)
So if you are searching for an error in the logcat file (it's always e/ for error, f/ for fatal. Those are the two main things that will break a system.)
Code:
D/dalvikvm( 871): GC_CONCURRENT freed 472K, 6% free 10224K/10823K, paused 1ms+6ms
V/AmazonAppstore.DiskInspectorServiceImpl( 871): Available blocks: 21981, Block size: 4096, Free: 90034176, Threshold: 5242880, withinThreshold? true
D/AmazonAppstore.UpdateService( 871): Received action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
W/AmazonAppstore.UpdateService( 871): Confused about why I'm running with this intent action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
D/dalvikvm( 890): GC_CONCURRENT freed 175K, 4% free 9375K/9671K, paused 2ms+3ms
V/AmazonAppstore.ReferenceCounter( 871): Reference (MASLoggerDB) count has gone to 0. Closing referenced object.
E/WifiStateMachine( 203): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
V/AmazonAppstore.UpdateService( 871): runUpdateCommand doInBackground started.
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateCommand( 871): Not updating key: digitalLocker from: 1334228488057
V/AmazonAppstore.UpdateService( 871): Finished UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: serviceConfig
V/AmazonAppstore.MASLoggerDB( 871): performLogMetric: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
V/AmazonAppstore.MASLoggerDB( 871): onBackgroundTaskSucceeded: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
W/CommandListener( 118): Failed to retrieve HW addr for eth0 (No such device)
D/CommandListener( 118): Setting iface cfg
D/NetworkManagementService( 203): rsp
D/NetworkManagementService( 203): flags
E/WifiStateMachine( 203): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg eth0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
W/PackageParser( 203): Unknown element under : supports-screen at /mnt/asec/com.android.aldiko-1/pkg.apk Binary XML file line #16
D/wpa_supplicant( 930): wpa_supplicant v0.8.x
D/wpa_supplicant( 930): random: Trying to read entropy from /dev/random
D/wpa_supplicant( 930): Initializing interface 'eth0' conf '/data/misc/wifi/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
D/wpa_supplicant( 930): Configuration file '/data/misc/wifi/wpa_supplicant.conf' -> '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): Reading configuration file '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): ctrl_interface='eth0'
D/wpa_supplicant( 930): update_config=1
D/wpa_supplicant( 930): Line: 4 - start of a new network block
D/wpa_supplicant( 930): key_mgmt: 0x4
(mind you, that's 29 lines out of 1300ish, just for example)
I then could do the following with logcat:
Code:
adb logcat WifiStateMachine:E *:S -v long > name of problem.txt
and this will only print out any errors associated with WifiStateMachine, and anything which is fatal, which makes it about a million times easier to figure out what's going on!
In WifiStateMachine:E, the :E = to look for Errors, the full list of options is as follows:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
You can replace the :E with any other letter from above to get more info.
In order to filter out anything other than what you are looking for (in this case, WifiStateMachine) you must put a *:S after your last command (i.e. WifiStateMachine:E ThemeChoose:V ... ... AndroidRuntime:E *:S)
Sources: http://developer.android.com/tools/help/logcat.html
http://developer.android.com/tools/help/adb.html
Update for windows users:
Thank go to FuzzyMeep Two, Here's what he's posted for windows
(If you used his tool, here's his post, thank him for his work!)
Note : I am just sharing. Original post here.

Great job brother!!You are in the right path for RC :beer::thumbup:
Sent from my Galaxy Nexus using xda app-developers app

keep going on my friend...:good:

Khizar said:
I think this one is definitely needed for this forum as i am seeing more and more users ask how to logcat. So posting this here.
Here's how to use logcat:
There are two main ways to do a logcat, within android, and through adb.
Logcat within android can be done one of two ways, through a Logcat app:
Here are two good examples are either: aLogcat or Catlog
I prefer catlog, because in my opinion it has a little bit nicer UI. Both of these programs can dump their logs to a txt file, which is very useful for debugging. Or, you can do it in terminal emulator (same rules as running through adb(see below))
From Moscow Desire:
On the other hand, using adb to run logcat, in my opinion is much more useful, because you can start using it when android boots (i.e. once the boot animation appears.)
The code for logcat to output to a file is
Code:
adb logcat > name of problem.txt
you can also do
Code:
adb logcat -f name of problem.txt
how I prefer to do it is this way:
Code:
adb logcat -v long > name of problem.txt
with the -v flag & the long argument, it changes output to long style, which means every line of logcat will be on its own line (makes it a little neater, imo)
Note: When outputting to a file, you will see a newline, but nothing printed, this is normal. To stop logcat from writting to a file, you need to press ctrl+c.
Here's where using logcat (via adb makes life really easy)
Lets say you find a problem you're having after looking at a logcat.
For example:
When I was trying to use a different ramdisk, wifi wouldn't work so I got a logcat that's almost 1300 lines long (a lot of stuff happens in the background)
So if you are searching for an error in the logcat file (it's always e/ for error, f/ for fatal. Those are the two main things that will break a system.)
Code:
D/dalvikvm( 871): GC_CONCURRENT freed 472K, 6% free 10224K/10823K, paused 1ms+6ms
V/AmazonAppstore.DiskInspectorServiceImpl( 871): Available blocks: 21981, Block size: 4096, Free: 90034176, Threshold: 5242880, withinThreshold? true
D/AmazonAppstore.UpdateService( 871): Received action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
W/AmazonAppstore.UpdateService( 871): Confused about why I'm running with this intent action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
D/dalvikvm( 890): GC_CONCURRENT freed 175K, 4% free 9375K/9671K, paused 2ms+3ms
V/AmazonAppstore.ReferenceCounter( 871): Reference (MASLoggerDB) count has gone to 0. Closing referenced object.
E/WifiStateMachine( 203): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
V/AmazonAppstore.UpdateService( 871): runUpdateCommand doInBackground started.
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateCommand( 871): Not updating key: digitalLocker from: 1334228488057
V/AmazonAppstore.UpdateService( 871): Finished UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: serviceConfig
V/AmazonAppstore.MASLoggerDB( 871): performLogMetric: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
V/AmazonAppstore.MASLoggerDB( 871): onBackgroundTaskSucceeded: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
W/CommandListener( 118): Failed to retrieve HW addr for eth0 (No such device)
D/CommandListener( 118): Setting iface cfg
D/NetworkManagementService( 203): rsp
D/NetworkManagementService( 203): flags
E/WifiStateMachine( 203): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg eth0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
W/PackageParser( 203): Unknown element under : supports-screen at /mnt/asec/com.android.aldiko-1/pkg.apk Binary XML file line #16
D/wpa_supplicant( 930): wpa_supplicant v0.8.x
D/wpa_supplicant( 930): random: Trying to read entropy from /dev/random
D/wpa_supplicant( 930): Initializing interface 'eth0' conf '/data/misc/wifi/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
D/wpa_supplicant( 930): Configuration file '/data/misc/wifi/wpa_supplicant.conf' -> '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): Reading configuration file '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): ctrl_interface='eth0'
D/wpa_supplicant( 930): update_config=1
D/wpa_supplicant( 930): Line: 4 - start of a new network block
D/wpa_supplicant( 930): key_mgmt: 0x4
(mind you, that's 29 lines out of 1300ish, just for example)
I then could do the following with logcat:
Code:
adb logcat WifiStateMachine:E *:S -v long > name of problem.txt
and this will only print out any errors associated with WifiStateMachine, and anything which is fatal, which makes it about a million times easier to figure out what's going on!
In WifiStateMachine:E, the :E = to look for Errors, the full list of options is as follows:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
You can replace the :E with any other letter from above to get more info.
In order to filter out anything other than what you are looking for (in this case, WifiStateMachine) you must put a *:S after your last command (i.e. WifiStateMachine:E ThemeChoose:V ... ... AndroidRuntime:E *:S)
Sources: http://developer.android.com/tools/help/logcat.html
http://developer.android.com/tools/help/adb.html
Update for windows users:
Thank go to FuzzyMeep Two, Here's what he's posted for windows
(If you used his tool, here's his post, thank him for his work!)
Note : I am just sharing. Original post here.
Click to expand...
Click to collapse
I'm happy very happy ... I have little exp with log cat this is my guide ....
Very good another user of Ak team near RC
Sent from my Galaxy Nexus using xda app-developers app

One doubt, I've downloaded catlog and make it run but I don't know where the txt files are stored or what can I do to recover them.
Also the problem I'm experiencing is a random reboot so even if I have catlog running when the reboot occurs, will I be able to recover the log or it will be lost?
Sorry for the noob question but I'm pretty lost here...

binlalo said:
One doubt, I've downloaded catlog and make it run but I don't know where the txt files are stored or what can I do to recover them.
Also the problem I'm experiencing is a random reboot so even if I have catlog running when the reboot occurs, will I be able to recover the log or it will be lost?
Sorry for the noob question but I'm pretty lost here...
Click to expand...
Click to collapse
catlog should have its own folder in data/media where it saves the txt files...

[Tutorial] How To Logcat

Here's how to use logcat:
There are two main ways to do a logcat, within android, and through adb.
Logcat within android can be done one of two ways, through a Logcat app:
Here are two good examples are either: CatLog or aLogcat
I prefer catlog, because in my opinion it has a little bit nicer UI. Both of these programs can dump their logs to a txt file, which is very useful for debugging. Or, you can do it in terminal emulator:
Open your terminal app;
Type:
Code:
su
logcat > /sdcard/logcat.txt
On the other hand, using adb to run logcat, in my opinion is much more useful, because you can start using it when android boots (i.e. once the boot animation appears.)
The code for logcat to output to a file is
Code:
adb logcat > name of problem.txt
you can also do
Code:
adb logcat -f name of problem.txt
how I prefer to do it is this way:
Code:
adb logcat -v long > name of problem.txt
with the -v flag & the long argument, it changes output to long style, which means every line of logcat will be on its own line (makes it a little neater, imo)
Note: When outputting to a file, you will see a newline, but nothing printed, this is normal. To stop logcat from writting to a file, you need to press ctrl+c.
Here's where using logcat (via adb makes life really easy)
Lets say you find a problem you're having after looking at a logcat.
For example:
When I was trying to use a different ramdisk, wifi wouldn't work so I got a logcat that's almost 1300 lines long (a lot of stuff happens in the background)
So if you are searching for an error in the logcat file (it's always e/ for error, f/ for fatal. Those are the two main things that will break a system.)
Code:
D/dalvikvm( 871): GC_CONCURRENT freed 472K, 6% free 10224K/10823K, paused 1ms+6ms
V/AmazonAppstore.DiskInspectorServiceImpl( 871): Available blocks: 21981, Block size: 4096, Free: 90034176, Threshold: 5242880, withinThreshold? true
D/AmazonAppstore.UpdateService( 871): Received action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
W/AmazonAppstore.UpdateService( 871): Confused about why I'm running with this intent action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
D/dalvikvm( 890): GC_CONCURRENT freed 175K, 4% free 9375K/9671K, paused 2ms+3ms
V/AmazonAppstore.ReferenceCounter( 871): Reference (MASLoggerDB) count has gone to 0. Closing referenced object.
E/WifiStateMachine( 203): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
V/AmazonAppstore.UpdateService( 871): runUpdateCommand doInBackground started.
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateCommand( 871): Not updating key: digitalLocker from: 1334228488057
V/AmazonAppstore.UpdateService( 871): Finished UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: serviceConfig
V/AmazonAppstore.MASLoggerDB( 871): performLogMetric: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
V/AmazonAppstore.MASLoggerDB( 871): onBackgroundTaskSucceeded: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
W/CommandListener( 118): Failed to retrieve HW addr for eth0 (No such device)
D/CommandListener( 118): Setting iface cfg
D/NetworkManagementService( 203): rsp
D/NetworkManagementService( 203): flags
E/WifiStateMachine( 203): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg eth0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
W/PackageParser( 203): Unknown element under : supports-screen at /mnt/asec/com.android.aldiko-1/pkg.apk Binary XML file line #16
D/wpa_supplicant( 930): wpa_supplicant v0.8.x
D/wpa_supplicant( 930): random: Trying to read entropy from /dev/random
D/wpa_supplicant( 930): Initializing interface 'eth0' conf '/data/misc/wifi/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
D/wpa_supplicant( 930): Configuration file '/data/misc/wifi/wpa_supplicant.conf' -> '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): Reading configuration file '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): ctrl_interface='eth0'
D/wpa_supplicant( 930): update_config=1
D/wpa_supplicant( 930): Line: 4 - start of a new network block
D/wpa_supplicant( 930): key_mgmt: 0x4
(mind you, that's 29 lines out of 1300ish, just for example)
I then could do the following with logcat:
Code:
adb logcat WifiStateMachine:E *:S -v long > name of problem.txt
and this will only print out any errors associated with WifiStateMachine, and anything which is fatal, which makes it about a million times easier to figure out what's going on!
In WifiStateMachine:E, the :E = to look for Errors, the full list of options is as follows:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
You can replace the :E with any other letter from above to get more info.
In order to filter out anything other than what you are looking for (in this case, WifiStateMachine) you must put a *:S after your last command (i.e. WifiStateMachine:E ThemeChoose:V ... ... AndroidRuntime:E *:S)
Sources: http://developer.android.com/tools/help/logcat.html
http://developer.android.com/tools/help/adb.html

Nice guide.

gonna bookmark this Thanks!

Android Auto API_UNAVAILABLE

Hi,
on latest nightly LineageOS 15.1 Android Auto crashes with "Google Play Services not working" on startup.
Log:
Code:
11-14 13:02:26.748 1107 2869 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.projection.gearhead/com.google.android.gearhead.vanagon.VnLaunchPadActivity bnds=[440,288][640,561]} from uid 10033
11-14 13:02:26.868 1107 1183 I ActivityManager: Displayed com.google.android.projection.gearhead/com.google.android.gearhead.vanagon.VnLaunchPadActivity: +90ms
11-14 13:02:27.083 8728 8728 I GH.LifetimeManager: connectToCarService
11-14 13:02:27.084 8728 8728 E GH.LifetimeManager: CarService onConnectionFailed (API_UNAVAILABLE: null)
11-14 13:02:27.125 1107 5646 W ActivityManager: Unable to start service Intent { act=com.google.android.gms.car.service.START pkg=com.google.android.gms } U=0: not found
11-14 13:02:27.129 8728 8979 E GmsClient: unable to connect to service: com.google.android.gms.car.service.START on com.google.android.gms
11-14 13:02:27.130 604 604 D SurfaceFlinger: duplicate layer name: changing com.google.android.projection.gearhead/com.google.android.gearhead.vanagon.VnLaunchPadActivity to com.google.android.projection.gearhead/com.google.android.gearhead.vanagon.VnLaunchPadActivity#1
11-14 13:02:27.145 8728 8728 W GH.CarApiClientManager: connection failed: ConnectionResult{statusCode=API_UNAVAILABLE, resolution=null, message=null}
11-14 13:02:27.145 8728 8728 E GH.LifetimeManager: CarService onConnectionFailed (API_UNAVAILABLE: null)
11-14 13:02:27.183 604 604 D SurfaceFlinger: duplicate layer name: changing com.google.android.projection.gearhead/com.google.android.gearhead.vanagon.VnLaunchPadActivity to com.google.android.projection.gearhead/com.google.android.gearhead.vanagon.VnLaunchPadActivity#2
API_UNAVAILABLE sounds like I missed something to install? I'm using Open GApps Mini. Android auto menu item is also missing in settings - google - services menu.
Same setup on other devices for example HTC M8s works without problem.
Anyone seen this issue before and may help?
Edit:
Got it somehow working for now. I was in settings - google - show debug items (in top menu) - google play services modules (at the bottom) - car / car_setup. There I did check for updates nothing happened went back to GCM Diagnostics pressed disconnect, then connect, and ping nothing really happened again. Then I went back did hide debug items now Android auto menu was present and I was able to startup Android Auto without the error.
Log seems fine now:
Code:
11-17 23:26:19.848 1107 2924 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.projection.gearhead/com.google.android.gearhead.vanagon.VnLaunchPadActivity bnds=[241,612][440,885]} from uid 10033
11-17 23:26:19.970 1107 1183 I ActivityManager: Displayed com.google.android.projection.gearhead/com.google.android.gearhead.vanagon.VnLaunchPadActivity: +77ms
11-17 23:26:20.187 15152 15152 I GH.LifetimeManager: connectToCarService
11-17 23:26:20.188 15152 15152 D GH.CarApiClientManager: registered listener [email protected]
11-17 23:26:20.188 15152 15152 D GH.CarApiClientManager: start
11-17 23:26:20.195 15152 15178 D CAR.CLIENT: connect [email protected]
11-17 23:26:20.212 14973 14987 D CAR.SERVICE: Package validated: com.google.android.projection.gearhead
11-17 23:26:20.215 14973 14987 D CAR.SERVICE: Android Auto has car home but both aliases are disabled. Nothing to do
11-17 23:26:20.235 15152 15152 D CAR.CLIENT: onICarAvailable [email protected]
11-17 23:26:20.236 14973 14987 D CAR.SERVICE: Registering [email protected]
11-17 23:26:20.236 15152 15152 I GH.CarApiClientManager: connected
11-17 23:26:20.236 15152 15152 D GH.CarApiClientManager: calling onConnected on [email protected]
11-17 23:26:20.247 11394 11394 D GH.CarApiClientManager: registered listener [email protected]
11-17 23:26:20.248 11394 11394 D GH.CarApiClientManager: start
Still I do not know what was causing the issue. I was always able to use Android Auto until it was broken for no reason. Maybe some strange issue while disconnecting from the car caused the car play service to crash. Nevertheless, reboot alone did not fix it. I'll report back if it breaks again in the future and maybe dump logs directly after the incident.

Question Wifi 6E Hotspot not turning on after re-enabling

Turning on the hotspot on the OP11 (CPH2449 in my case) using 6GHz band and WPA3 with a password works just fine when starting Hotspot for the first time after a fresh boot. But after re-enabling the hotspot, it is instantly being turned off again.
Spoiler: These are the logcat entries
Code:
02-22 13:17:09.039 4630 4979 I Tethering: adding IpServer for: wlan2
02-22 13:17:09.146 4630 4979 I Tethering: [BpfCoordinator] Monitoring started
02-22 13:17:09.184 4630 4979 I Tethering: [OffloadHardwareInterface] tethering offload control version 1.1 is supported.
02-22 13:17:09.188 4630 4979 I Tethering: [BpfCoordinator] Polling started
02-22 13:17:09.188 4630 4979 E Tethering: [ConntrackMonitor] ERROR unparsable netlink msg: 1400000001010103000000000000000002000000
02-22 13:17:09.190 4630 4979 I Tethering: Looking for default routes on: {InterfaceName: rmnet_data4 LinkAddresses: [ 100.120.73.181/30,2a00:20:49:a39c:4439:37ff:fe26:574e/64 ] DnsAddresses: [ /139.7.30.125,/139.7.30.126,/2a01:860:0:300::53,/2a01:860:0:300::153 ] Domains: null MTU: 1500 TcpBufferSizes: 2097152,4194304,8388608,262144,524288,1048576 Routes: [ 0.0.0.0/0 -> 100.120.73.182 rmnet_data4 mtu 1500,::/0 -> fe80::a9b8:3047:31f2:aaa6 rmnet_data4 mtu 1500,100.120.73.180/30 -> 0.0.0.0 rmnet_data4 mtu 0,2a00:20:49:a39c::/64 -> :: rmnet_data4 mtu 0 ]}
02-22 13:17:09.190 4630 4979 I Tethering: Found upstream interface(s): [rmnet_data4]
02-22 13:17:09.200 4630 4979 I Tethering: Looking for default routes on: {InterfaceName: rmnet_data4 LinkAddresses: [ 100.120.73.181/30,2a00:20:49:a39c:4439:37ff:fe26:574e/64 ] DnsAddresses: [ /139.7.30.125,/139.7.30.126,/2a01:860:0:300::53,/2a01:860:0:300::153 ] Domains: null MTU: 1500 TcpBufferSizes: 2097152,4194304,8388608,262144,524288,1048576 Routes: [ 0.0.0.0/0 -> 100.120.73.182 rmnet_data4 mtu 1500,::/0 -> fe80::a9b8:3047:31f2:aaa6 rmnet_data4 mtu 1500,100.120.73.180/30 -> 0.0.0.0 rmnet_data4 mtu 0,2a00:20:49:a39c::/64 -> :: rmnet_data4 mtu 0 ]}
02-22 13:17:09.200 4630 4979 I Tethering: Found upstream interface(s): [rmnet_data4]
02-22 13:17:09.466 4630 4979 E Tethering: [api31.BpfCoordinatorShimImpl] ERROR Could not detach program: java.io.IOException: Fail to get interface params for interface wlan2
02-22 13:17:09.469 4630 4979 E Tethering: [api31.BpfCoordinatorShimImpl] ERROR Could not detach program: java.io.IOException: Fail to get interface params for interface wlan2
02-22 13:17:09.508 4630 4979 E Tethering: [wlan2] ERROR Failed to remove 1 IPv6 routes from local table.
02-22 13:17:09.509 4630 4979 E Tethering: [wlan2] ERROR failed to remove /2a00:20:49:a39c::4e/64: android.os.ServiceSpecificException: InterfaceController error: No such device (code 19)
02-22 13:17:09.509 4630 4979 E Tethering: [wlan2] ERROR Failed to remove local dns IP /2a00:20:49:a39c::4e
02-22 13:17:09.511 4630 4979 E Tethering: [wlan2] ERROR Setting IPv4 address to 192.168.118.208/24 failed: android.os.ServiceSpecificException: [No such device] : ioctl() failed (code 19)
02-22 13:17:09.511 4630 4979 E Tethering: [wlan2] ERROR Error configuring interface
02-22 13:17:09.512 4630 4979 E Tethering: [wlan2] ERROR Setting IPv4 address to 0.0.0.0/0 failed: android.os.ServiceSpecificException: [No such device] : ioctl() failed (code 19)
02-22 13:17:09.512 4630 4979 I Tethering: [BpfCoordinator] Monitoring stopped
02-22 13:17:09.515 4630 4979 I Tethering: removing IpServer for: wlan2
02-22 13:17:09.742 4630 4979 I Tethering: [BpfCoordinator] Polling stopped
02-22 13:17:09.748 4630 4979 E Tethering: ERROR Tethering no longer handle untracked interface after T: wlan2
I guess it is a bug in OnePlus firmware, but perhaps you guys got any idea how to fix it myself. Thanks!

https://forum.xda-developers.com/t/my-wireless-rf-module-seems-to-be-damaged-sad.4554809/
Do you have the same situation as described in my posting? I've given feedback to the Chinese OnePlus engineers about this and they're working on it, I was worried it was a hardware problem but they told me it might be a software issue and to not worry about it for now.

lllyyyz said:
https://forum.xda-developers.com/t/my-wireless-rf-module-seems-to-be-damaged-sad.4554809/
Do you have the same situation as described in my posting? I've given feedback to the Chinese OnePlus engineers about this and they're working on it, I was worried it was a hardware problem but they told me it might be a software issue and to not worry about it for now.
Click to expand...
Click to collapse
Thanks! I've tried to enable hotspot when connected to 2.4GHz WiFi -> It only let's me select 2.4GHz Hotspot frequency. Disconnecting from the 2.4GHz WiFi let's me select all other (5 and 6GHz) hotspot bands again.
Bit weird. but that seems to be yet another (additional) problem I think.

CoinsClassic said:
Thanks! I've tried to enable hotspot when connected to 2.4GHz WiFi -> It only let's me select 2.4GHz Hotspot frequency. Disconnecting from the 2.4GHz WiFi let's me select all other (5 and 6GHz) hotspot bands again.
Bit weird. but that seems to be yet another (additional) problem I think.
Click to expand...
Click to collapse
" It only let's me select 2.4GHz Hotspot frequency" For this statement, do you mean that whether the AP band you choose is 2.4 or 5Ghz, and the actual hotspot signal (other devices performing the search signal) is 2.4? If so, then we have the same problem. Do you try to turn off WiFi6 on the hotspot first and leave WiFi on, turn on the 5Ghz hotspot correctly and then turn on WiFi on the OnePlus 11, do you see if you will not be able to search any 5Ghz WiFi or the hotspot automatically downgrades to 2.4Ghz (searching for signal from other devices) after connecting to 5Ghz WiFi? If so, then the next time China One Plus contacts me, I will report this to them.

I’m not surprised. Wifi6e doesn’t work on 10 pro and 11 after unlocking and/or rooting. I don’t expect it to transmit if it can’t receive.
I’m assuming you are rooted

g96818 said:
I’m not surprised. Wifi6e doesn’t work on 10 pro and 11 after unlocking and/or rooting. I don’t expect it to transmit if it can’t receive.
I’m assuming you are rooted
Click to expand...
Click to collapse
Hmm.. not sure what you mean by "doesn't work after unlocking/rooting"... I am rooted, and I can successfully connect to WiFi 6E Hotspot after fresh boot and transmit and receive data (at blazing speeds ~ 1.7Gbps), but if I turn it off, then wait a bit, then turn it on again, it turns itself immediately off again.
Spoiler: WiFi 6E Hotspot Status info and speedtest
{
"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"
}

CoinsClassic said:
Hmm.. not sure what you mean by "doesn't work after unlocking/rooting"... I am rooted, and I can successfully connect to WiFi 6E Hotspot after fresh boot and transmit and receive data (at blazing speeds ~ 1.7Gbps), but if I turn it off, then wait a bit, then turn it on again, it turns itself immediately off again.
Spoiler: WiFi 6E Hotspot Status info and speedtest
View attachment 5844845View attachment 5844847
Click to expand...
Click to collapse
That's more than me. It doesn't work

I've never been able to use the 6Ghz Hotspot. I have tried numerous times. After each update I check to see if it has been fixed, and of course it hasn't. I don't see why it would be disabled after root/bootloader unlock. I just don't understand what the reason for purposely disabling it would be. Any thoughts?

Think of it this way they're trying to slowly convert people into not wanting to root their phones by slowly making things more and more inconvenient to rooted phones.

Question There is a problem with SELinux rules after successful ROM compilation

The following error is reported in adb logcat
05-26 17:32:01.812 1 1 W /system/bin/init: type=1107 audit(0.0:152): uid=0 auid=4294967295 ses=4294967295 subj=u:r:init:s0 msg='avc: denied { set } for property=persist.vendor.radio.call_waiting_for_sync_0 pid=32058 uid=10140 gid=10140 scontext=u:r:platform_app:s0:c512,c768 tcontext=u:object_r:vendor_rild_prop:s0 tclass=property_service permissive=0'
05-26 17:32:01.808 32058 32058 W pool-5-thread-1: type=1400 audit(0.0:151): avc: denied { read } for name="u:object_r:vendor_rild_prop:s0" dev="tmpfs" ino=357 scontext=u:r:platform_app:s0:c512,c768 tcontext=u:object_r:vendor_rild_prop:s0 tclass=file permissive=0 app=com.shannon.imsservice
05-26 17:32:02.035 535 535 E SELinux : avc: denied { find } for pid=30652 uid=10156 name=hardware.qorvo.uwb.IUwbVendor/default scontext=u:r:priv_app:s0:c512,c768 tcontext=u:object_r:hal_uwb_vendor_service:s0 tclass=service_manager permissive=0

I'm compiling a custom rom, I can see the same errors (along with others) in LogCat, but there's not issues or bugs in the rom
Does your rom crash or something?