[G2 Android Development] Choristav:
While not exactly rom related (as this is persistent since back on 4.4), does anyone know what the logcat spam means?

It's just periodic spam of

06-18 07:31:11.421 I/auditd (13422): Starting up
06-18 07:31:11.423 E/auditd (13422): Failed on audit_set_pid with error: Protocol not supported
06-18 07:31:11.423 I/auditd (13422): Exiting

There's also some harmless log spam, which I thought was disabled a couple of days ago

06-18 07:30:46.145 V/sensors_hal_Accel(1712): processReportInd: X: 0.280029 Y: 2.363388 Z: 9.476700
06-18 07:30:46.146 D/sensors_hal_Ctx(1712): poll:polldata:1, sensor:0, type:1, x:0.280029 y:2.363388 z:9.476700
06-18 07:30:46.165 V/sensors_hal_Accel(1712): processReportInd: X: 0.209427 Y: 2.291595 Z: 9.572403
06-18 07:30:46.166 D/sensors_hal_Ctx(1712): poll:polldata:1, sensor:0, type:1, x:0.209427 y:2.291595 z:9.572403
06-18 07:30:46.186 V/sensors_hal_Accel(1712): processReportInd: X: 0.400864 Y: 2.386124 Z: 9.505402
06-18 07:30:46.186 D/sensors_hal_Ctx(1712): poll:polldata:1, sensor:0, type:1, x:0.400864 y:2.386124 z:9.505402
06-18 07:30:46.205 V/sensors_hal_Accel(1712): processReportInd: X: 0.137650 Y: 2.310745 Z: 9.581970
06-18 07:30:46.205 D/sensors_hal_Ctx(1712): poll:polldata:1, sensor:0, type:1, x:0.137650 y:2.310745 z:9.581970
06-18 07:30:46.225 V/sensors_hal_Accel(1712): processReportInd: X: 0.221405 Y: 2.292801 Z: 9.779388
06-18 07:30:46.225 D/sensors_hal_Ctx(1712): poll:polldata:1, sensor:0, type:1, x:0.221405 y:2.292801 z:9.779388
06-18 07:30:46.245 V/sensors_hal_Accel(1712): processReportInd: X: 0.026382 Y: 2.346634 Z: 9.775803
06-18 07:30:46.245 D/sensors_hal_Ctx(1712): poll:polldata:1, sensor:0, type:1, x:0.026382 y:2.346634 z:9.775803
06-18 07:30:46.265 V/sensors_hal_Accel(1712): processReportInd: X: 0.006042 Y: 2.370560 Z: 9.536514
06-18 07:30:46.266 D/sensors_hal_Ctx(1712): poll:polldata:1, sensor:0, type:1, x:0.006042 y:2.370560 z:9.536514
06-18 07:30:46.286 V/sensors_hal_Accel(1712): processReportInd: X: 0.065857 Y: 2.313141 Z: 9.613083
06-18 07:30:46.286 D/sensors_hal_Ctx(1712): poll:polldata:1, sensor:0, type:1, x:0.065857 y:2.313141 z:9.613083

There's also instances of this while fiddling around with sound:

06-18 07:30:48.014 E/ANDR-PERF-MPCTL(1712): PERFLOCK Failed to connect to socket: errno=2 (No such file or directory)
06-18 07:30:48.014 E/QCOM PowerHAL(1712): Failed to acquire lock.
06-18 07:30:48.036 E/ANDR-PERF-MPCTL(1712): PERFLOCK Failed to connect to socket: errno=2 (No such file or directory)
06-18 07:30:48.036 E/QCOM PowerHAL(1712): Failed to acquire lock.
06-18 07:30:48.052 E/ANDR-PERF-MPCTL(1712): PERFLOCK Failed to connect to socket: errno=2 (No such file or directory)
06-18 07:30:48.052 E/QCOM PowerHAL(1712): Failed to acquire lock.
06-18 07:30:48.069 E/ANDR-PERF-MPCTL(1712): PERFLOCK Failed to connect to socket: errno=2 (No such file or directory)
06-18 07:30:48.069 E/QCOM PowerHAL(1712): Failed to acquire lock.
06-18 07:30:48.085 E/ANDR-PERF-MPCTL(1712): PERFLOCK Failed to connect to socket: errno=2 (No such file or directory)
06-18 07:30:48.085 E/QCOM PowerHAL(1712): Failed to acquire lock.
06-18 07:30:48.106 E/ANDR-PERF-MPCTL(1712): PERFLOCK Failed to connect to socket: errno=2 (No such file or directory)
06-18 07:30:48.106 E/QCOM PowerHAL(1712): Failed to acquire lock.
06-18 07:30:48.110 E/AudioTrack(1712): AudioTrack::set : Exit
06-18 07:30:48.125 D/audio_hw_primary(237): start_output_stream: enter: stream(0xb587f0c0)usecase(1: low-latency-playback) devices(0x2)
06-18 07:30:48.125 D/audio_hw_primary(237): start_output_stream: enter: usecase(1: low-latency-playback) devices(0x2)
06-18 07:30:48.125 D/audio_hw_primary(237): select_devices: out_snd_device(2: speaker) in_snd_device(0: )
06-18 07:30:48.125 W/msm8974_platform(237): Codec backend bitwidth 16, samplerate 48000
06-18 07:30:48.125 D/hardware_info(237): hw_info_append_hw_type : device_name = speaker
06-18 07:30:48.125 I/msm8974_platform(237): platform_send_audio_calibration: sending audio calibration for snd_device(2) acdb_id(14)
06-18 07:30:48.126 D/ACDB-LOADER(237): ACDB -> send_audio_cal, acdb_id = 14, path = 0
06-18 07:30:48.126 D/ACDB-LOADER(237): ACDB -> send_adm_topology
06-18 07:30:48.126 D/ACDB-LOADER(237): ACDB -> ACDB_CMD_GET_AUDPROC_COMMON_TOPOLOGY_ID
06-18 07:30:48.126 D/ACDB-LOADER(237): ACDB -> send_asm_topology
06-18 07:30:48.126 D/ACDB-LOADER(237): ACDB -> ACDB_CMD_GET_AUDPROC_STREAM_TOPOLOGY_ID
06-18 07:30:48.126 D/ACDB-LOADER(237): ACDB -> send_audtable
06-18 07:30:48.126 D/ACDB-LOADER(237): ACDB -> ACDB_CMD_GET_AUDPROC_COMMON_TABLE
06-18 07:30:48.126 D/ACDB-LOADER(237): ACDB -> AUDIO_SET_AUDPROC_CAL
06-18 07:30:48.126 D/ACDB-LOADER(237): ACDB -> send_audvoltable
06-18 07:30:48.126 D/ACDB-LOADER(237): ACDB -> ACDB_CMD_GET_AUDPROC_GAIN_DEP_STEP_TABLE
06-18 07:30:48.126 D/ACDB-LOADER(237): ACDB -> AUDIO_SET_AUDPROC_VOL_CAL
06-18 07:30:48.126 D/ACDB-LOADER(237): ACDB -> send_afe_cal
06-18 07:30:48.126 D/ACDB-LOADER(237): ACDB -> ACDB_CMD_GET_AFE_COMMON_TABLE
06-18 07:30:48.126 D/ACDB-LOADER(237): ACDB -> AUDIO_SET_AFE_CAL
06-18 07:30:48.133 D/audio_hw_primary(237): select_devices: done

I can get you a clean log if you need one. It doesn't do anything, honestly, the rom is pretty much flawless. But I've always wondered what some of these errors were, especially the first one which has been present for a very long time.

Edit: actually... The powerhal and the perflock section can be replicated while using the navbar buttons. Disabling haptic feedback doesn't solve it, and neither does disabling the touch-sounds.