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...

Bluetooth pairing gets intermittently forgotten

Even after getting Android Wear 2.0 I'm still having this issue. At times (not every time) when I walk out of the phone's range and after I get back, the bluetooth pairing would be lost and I get the pairing request prompts on both the phone and the watch.
This issue is also being discussed in the Google forums as well, and is still ongoing.
It's not a big issue since completing the pairing will make it continue to function for the time being, but it can be annoying as if I'm not immediately aware of the problem the phone will keep making notification noises.
From the phone's logcat during the period I'm seeing something that makes me curious (The watch's Bluetooth device name and address have been obscured in the logs below since they're device-specific):
Code:
...
11-14 08:39:23.693 22071 22367 I WearableConn: Connecting to "HUAWEI WATCH XXXX"
11-14 08:39:23.696 22071 22367 W BluetoothAdapter: getBluetoothService() called with no BluetoothManagerCallback
11-14 08:39:24.245 318 5597 I NuPlayerDecoder: [audio] saw output EOS
11-14 08:39:24.636 318 5591 D NuPlayerDriver: notifyListener_l(0xf5f109c0), (2, 0, 0), loop setting(0, 0)
11-14 08:39:24.638 627 17971 I MediaFocusControl: AudioFocus abandonAudioFocus() from uid/pid 10034/820 [email protected]
11-14 08:39:24.639 1193 1193 D AudioManager: AudioManager dispatching onAudioFocusChange(1) for [email protected]<native proxy object>
11-14 08:39:25.398 4077 5602 I BistoWorker: XX:XX:XX:XX:XX:XX not paired anymore
11-14 08:39:25.727 4077 5602 I BistoWorker: isAvailable false
11-14 08:39:25.755 627 17970 I ActivityManager: Start proc 5603:com.google.android.googlequicksearchbox:interactor/u0a116 for service com.google.android.googlequicksearchbox/com.google.android.apps.gsa.staticplugins.bisto.BistoRealService
11-14 08:39:25.997 5603 5603 W AppFlowTracker: Removing 2 events from non-search process(com.google.android.googlequicksearchbox:interactor)
11-14 08:39:25.997 5603 5603 I InteractorInitializer: Initialized process com.google.android.googlequicksearchbox:interactor
11-14 08:39:26.275 5603 5603 D BluetoothA2dp: Proxy object connected
11-14 08:39:26.822 4077 4077 W SearchService: Abort, client detached.
11-14 08:39:26.823 4077 4077 I BistoWorker: handleCommonBroadcastIntent: android.bluetooth.device.action.ACL_CONNECTED
11-14 08:39:26.833 4077 4077 I DeviceDetector: Refreshing UUID cache for device: XX:XX:XX:XX:XX:XX
11-14 08:39:26.839 4077 4077 I BistoWorker: Not a bisto device: XX:XX:XX:XX:XX:XX
11-14 08:39:27.670 30272 30272 D WeatherUpdateService: onCreate
11-14 08:39:27.671 30272 30272 D WeatherUpdateService: Service started, but shouldn't update ... stopping
11-14 08:39:27.673 30272 30272 D WeatherUpdateService: onDestroy
11-14 08:39:27.837 820 820 D PhoneStatusBar: disable: < expand ICONS alerts SYSTEM_INFO back HOME RECENT clock SEARCH quick_settings >
11-14 08:39:27.848 820 820 W FingerprintManager: isFingerprintHardwareDetected(): Service not connected!
11-14 08:39:27.912 4077 4077 I BistoWorker: handleCommonBroadcastIntent: android.bluetooth.device.action.ACL_DISCONNECTED
11-14 08:39:27.917 4077 4077 I BistoWorker: Not a bisto device: XX:XX:XX:XX:XX:XX
...
11-14 08:39:32.846 820 1157 D CachedBluetoothDevice: onUuidChanged, mProfile Size 1
11-14 08:39:32.860 820 1157 D LocalBluetoothProfileManager: Current Profiles[HEADSET]
11-14 08:39:32.860 820 1157 D BluetoothMap: getConnectedDevices()
11-14 08:39:32.864 820 1157 D BluetoothMap: getConnectionState(XX:XX:XX:XX:XX:XX)
11-14 08:39:32.869 820 1157 D MapProfile: getConnectionStatus: status is: 0
11-14 08:39:32.871 820 1157 D LocalBluetoothProfileManager: New Profiles[HEADSET]
11-14 08:39:32.871 820 1157 D CachedBluetoothDevice: UUID not udpated, returning
11-14 08:39:32.955 4077 5602 I BistoWorker: XX:XX:XX:XX:XX:XX not paired anymore
11-14 08:39:32.957 4077 5602 I BistoWorker: isAvailable false
11-14 08:39:32.967 5603 5603 D BluetoothA2dp: Proxy object connected
11-14 08:39:33.617 627 1666 I ActivityManager: START u0 {act=android.bluetooth.device.action.PAIRING_REQUEST flg=0x10000000 cmp=com.android.settings/.bluetooth.BluetoothPairingDialog (has extras)} from uid 1000 on display 0
11-14 08:39:33.630 627 4446 W InputMethodManagerService: Window already focused, ignoring focus gain of: [email protected] attribute=null, token = android.os.BinderP[email protected]
11-14 08:39:33.660 302 366 I chatty : uid=1000(system) UeventObserver expire 48 lines
11-14 08:39:33.723 627 967 E ActivityManager: applyOptionsLocked: Unknown animationType=0
11-14 08:39:33.724 1681 1761 D StreamDBQueue: Promised revision #698657 to queue a new op
11-14 08:39:33.724 1681 1761 D BaseStreamManager: Promised remove @ r#698657 for StreamItemId{notifKey=0|com.android.settings|17301632|null|1000, packageName=com.android.settings, id=17301632, revision=-1, originalRevision=-1, updateCount=-1} (@698656): SBN removed: StreamItemId{notifKey=0|com.android.settings|17301632|null|1000, packageName=com.android.settings, id=17301632, revision=-1, originalRevision=-1, updateCount=-1}
11-14 08:39:33.725 1681 1804 D NewStreamAdapter: Publishing revision #698657 to adapter clients
11-14 08:39:33.727 1681 1761 D StreamDBQueue: Promised revision #698658 to queue a new op
11-14 08:39:33.727 1681 1761 D BaseStreamManager: Promised remove @ r#698658 for StreamItemId{notifKey=-1|android|17040570|null|1000, packageName=android, id=17040570, revision=-1, originalRevision=-1, updateCount=-1} (@698657): SBN removed: StreamItemId{notifKey=-1|android|17040570|null|1000, packageName=android, id=17040570, revision=-1, originalRevision=-1, updateCount=-1}
11-14 08:39:33.728 1681 1804 D NewStreamAdapter: Publishing revision #698658 to adapter clients
11-14 08:39:33.729 810 810 W InputMethodService: Window size has been changed. This may cause jankiness of resizing window: -1 -> -2
11-14 08:39:33.976 302 302 I chatty : uid=1000(system) /system/bin/surfaceflinger expire 47 lines
11-14 08:39:34.017 4077 4077 W SearchService: Abort, client detached.
11-14 08:39:34.017 4077 4077 I BistoWorker: handleCommonBroadcastIntent: android.bluetooth.device.action.ACL_CONNECTED
11-14 08:39:34.020 4077 4077 E DeviceDetector: UUID = 0000110a-0000-1000-8000-00805f9b34fb
11-14 08:39:34.020 4077 4077 E DeviceDetector: UUID = 0000111e-0000-1000-8000-00805f9b34fb
11-14 08:39:34.021 4077 4077 E DeviceDetector: UUID = 00000000-0000-1000-8000-00805f9b34fb
11-14 08:39:34.021 4077 4077 E DeviceDetector: UUID = 669a0c20-0008-e2a5-e311-2595b045895e
11-14 08:39:34.021 4077 4077 I BistoWorker: Not a bisto device: XX:XX:XX:XX:XX:XX
11-14 08:39:34.033 627 4441 I ActivityManager: Setting hasTopUi=false for pid=820
11-14 08:39:34.034 820 820 D PhoneStatusBar: disable: < expand icons* alerts system_info* back home recent clock search quick_settings >
11-14 08:39:34.249 5572 5667 I OpenGLRenderer: Initialized EGL, version 1.4
11-14 08:39:34.249 5572 5667 D OpenGLRenderer: Swap behavior 1
11-14 08:39:34.251 5572 5667 W OpenGLRenderer: Failed to choose config with EGL_SWAP_BEHAVIOR_PRESERVED, retrying without...
11-14 08:39:34.251 5572 5667 D OpenGLRenderer: Swap behavior 0
11-14 08:39:34.483 627 649 I ActivityManager: Displayed com.android.settings/.bluetooth.BluetoothPairingDialog: +760ms
11-14 08:39:35.078 4077 4077 W SearchService: Abort, client detached.
11-14 08:39:35.079 4077 4077 I BistoWorker: handleCommonBroadcastIntent: android.bluetooth.device.action.ACL_DISCONNECTED
11-14 08:39:35.086 4077 4077 E DeviceDetector: UUID = 0000110a-0000-1000-8000-00805f9b34fb
11-14 08:39:35.087 4077 4077 E DeviceDetector: UUID = 0000111e-0000-1000-8000-00805f9b34fb
11-14 08:39:35.088 4077 4077 E DeviceDetector: UUID = 00000000-0000-1000-8000-00805f9b34fb
11-14 08:39:35.088 4077 4077 E DeviceDetector: UUID = 669a0c20-0008-e2a5-e311-2595b045895e
11-14 08:39:35.089 4077 4077 I BistoWorker: Not a bisto device: XX:XX:XX:XX:XX:XX
11-14 08:39:35.285 16265 16295 I chatty : uid=1002(bluetooth) bt_workqueue expire 10 lines
11-14 08:39:35.286 16265 16292 I chatty : uid=1002(bluetooth) hci_thread expire 35 lines
11-14 08:39:35.330 16265 16295 I chatty : uid=1002(bluetooth) bt_workqueue expire 14 lines
11-14 08:39:35.891 5572 5572 I BluetoothPairingDialog: Pairing dialog accepted
11-14 08:39:35.920 627 9114 W InputMethodManagerService: Window already focused, ignoring focus gain of: com.andro[email protected] attribute=null, token = [email protected]
11-14 08:39:35.986 5572 5667 D OpenGLRenderer: endAllActiveAnimators on 0xf176a080 (RippleDrawable) with handle 0xf14f5ac0
11-14 08:39:38.985 308 390 I chatty : uid=1041(audioserver) /system/bin/audioserver expire 53 lines
11-14 08:39:40.126 4077 5602 I BistoWorker: XX:XX:XX:XX:XX:XX not paired anymore
11-14 08:39:40.130 4077 5602 I BistoWorker: isAvailable false
11-14 08:39:40.160 5603 5603 D BluetoothA2dp: Proxy object connected
11-14 08:39:41.250 4077 4077 W SearchService: Abort, client detached.
...
It appears either the phone (Android Wear) or the watch unpaired in the background, in a one-sided manner, so that the log on the phone reported that the device is "not paired anymore".

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

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.

Android 10 ROM

Thanks all for testing.

These?
https://androidfilehost.com/?fid=1899786940962602774
https://github.com/svlog/device_lge_bullhead

imknown said:
These?
https://androidfilehost.com/?fid=1899786940962602774
https://github.com/svlog/device_lge_bullhead
Click to expand...
Click to collapse
Yes.
Branch for selinux enforcing is in WIP and is not pushed to github yet.

equlog said:
Yes.
Branch for selinux enforcing is in WIP and is not pushed to github yet.
Click to expand...
Click to collapse
Just post it in development with a [alpha] tag and let people decide if they want to test it.
Few will see this thread in this forum.

Hi, I find this: NexusROM-10-bullhead-1.5a-M10-20191011.zip
https://androidfilehost.com/?fid=1899786940962606653
I flashed this build and it boots.
But the GNSS/GPS location function does not work with no FC/ANR.
Logcat posted below:
--------- beginning of main
10-13 12:04:11.836 1498 1498 D StatusBar: disable<e i a s b h r c s > disable2<q i n >
--------- beginning of system
10-13 12:03:50.006 545 545 I chatty : uid=1010(wifi) /system/bin/wificond expire 1 line
10-13 12:03:50.008 545 545 W wificond: Failed to get NL80211_ATTR_EXT_FEATURES
10-13 12:04:14.967 828 828 V SettingsProvider: Notifying for 0: content://settings/secure/location_mode
10-13 12:04:11.886 1498 1498 D StatusBar: disable<e i a s b h r c s > disable2<q i n >
10-13 12:04:14.968 447 447 W GnssHAL_GnssInterface: setCallback called more than once. Unexpected unless test.
10-13 12:04:14.971 828 938 D GnssLocationProvider: gnssSetCapabilitesCb: 71u
10-13 12:04:14.971 447 447 E LocSvc_eng: loc_eng_init: log_eng state error: instance already initialized
10-13 12:04:14.973 447 447 E LocSvc_eng: loc_eng_agps_init: log_eng state error: agps instance already initialized
10-13 12:04:14.973 828 938 I GnssLocationProvider: Unable to initialize IGnssGeofencing interface.
10-13 12:04:14.975 828 938 I GnssLocationProvider: Unable to initialize IAGnssRil interface.
10-13 12:04:14.980 828 938 I GnssLocationProvider: restartRequests
10-13 12:04:14.980 828 828 V SettingsProvider: Notifying for 0: content://settings/secure/location_providers_allowed
10-13 12:04:19.819 1498 1498 D StatusBar: disable<e i a s b h r c s > disable2<q i n >
10-13 12:04:19.885 1498 1498 D StatusBar: disable<e i a s b h r c s > disable2<q i n >
10-13 12:04:22.869 1498 1498 W View : requestLayout() improperly called by com.android.systemui.statusbar.policy.NetworkTraffic{3d20962 V.ED..... ......ID 0,23-91,81} during layout: running second layout pass
10-13 12:04:30.013 545 545 W wificond: Failed to get NL80211_ATTR_EXT_FEATURES

imknown said:
Hi, I find this: NexusROM-10-bullhead-1.5a-M10-20191011.zip
https://androidfilehost.com/?fid=1899786940962606653
I flashed this build and it boots.
But the GNSS/GPS location function does not work with no FC/ANR.
Click to expand...
Click to collapse
Thanks for the log, gps/gnss location fixed.

equlog said:
Thanks all for reports, my job is done
Click to expand...
Click to collapse
Give us a download link please.

mahyarmo said:
Give us a download link please.
Click to expand...
Click to collapse
Updated

Download link?

sinkoo1979 said:
Download link?
Click to expand...
Click to collapse
https://androidfilehost.com/?a=show&w=files&flid=216711

imknown said:
https://androidfilehost.com/?a=show&w=files&flid=216711
Click to expand...
Click to collapse
tried to flash the rom but it did not pass the flashing stage. When back to LOS15.1
Update: Flashed the newest build (October 24, 2019) and everything working.

Nice ROM, gapps?

PuTo said:
Nice ROM, gapps?
Click to expand...
Click to collapse
Join «NexusROM For Bullhead» on Telegram: https://t.me/NexusROM

equlog said:
Thanks for the log, gps/gnss location fixed.
Click to expand...
Click to collapse
@equlog, how was this fixed above?
I found my the problem for my tablet. I was missing 2 proprietary blobs being copied over to /system/lib. They are
libloc_api_v02.so
libloc_ds_api.so