Develop Bugs

[Q] MM Release Collecting Info on Buggy Behavior

So the title says it all,
So far I am experiencing, a crazy loud sound glitch that sounds like a vibrator in a plastic bowl, wonderful image right? xD
Also there is clearly the sound of seeming touch events happening at random intervals so trying to trace it with a live logcat would
be completely insane, but well, :silly:
i think it's somehwere in this
Code:
--------- beginning of main
03-10 10:17:14.145 623 2284 D audio_hw_primary: out_set_parameters: enter: usecase(1: low-latency-playback) kvpairs: routing=2
03-10 10:17:14.145 623 2284 D audio_hw_extn: audio_extn_set_anc_parameters: anc_enabled:0
--------- beginning of system
03-10 10:17:14.148 1644 2637 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.sonyericsson.home/com.sonymobile.home.HomeActivity (has extras)} from uid 1000 on display 0
03-10 10:17:14.158 623 2284 D audio_hw_primary: out_set_parameters: enter: usecase(1: low-latency-playback) kvpairs: fm_volume=0.2606911659
03-10 10:17:14.159 623 2284 D audio_hw_extn: audio_extn_set_anc_parameters: anc_enabled:0
03-10 10:17:14.159 623 2284 D audio_hw_fm: audio_extn_fm_set_parameters: set_fm_volume usecase
03-10 10:17:14.159 623 2284 D audio_hw_fm: fm_set_volume: (0.260691)
03-10 10:17:14.173 623 2283 D audio_hw_primary: start_output_stream: enter: stream(0xf2751600)usecase(1: low-latency-playback) devices(0x2)
03-10 10:17:14.174 623 2283 D audio_hw_extn: audio_extn_get_anc_enabled: anc_enabled:0
03-10 10:17:14.174 623 2283 D audio_hw_primary: select_devices: out_snd_device(50: speaker) in_snd_device(0: )
03-10 10:17:14.174 623 2283 W msm8974_platform: Codec backend bitwidth 16, samplerate 48000
03-10 10:17:14.174 623 2283 W msm8974_platform: Codec backend bitwidth 16, samplerate 48000
03-10 10:17:14.174 623 2283 D hardware_info: hw_info_append_hw_type : device_name = speaker
03-10 10:17:14.181 623 2283 D hardware_info: hw_info_append_hw_type : device_name = vi-feedback
03-10 10:17:14.181 623 2283 D audio_hw_primary: enable_snd_device: snd_device(259: vi-feedback)
03-10 10:17:14.181 623 2283 I soundtrigger: audio_extn_sound_trigger_update_device_status: device 0x103 of type 1 for Event 1, with Raise=0
03-10 10:17:14.181 623 2283 D soundtrigger: audio_extn_sound_trigger_update_stream_status: uc_id 38 of type 1 for Event 3, with Raise=0
03-10 10:17:14.181 623 2283 E voice : voice_is_in_call_rec_stream: input stream is NULL
03-10 10:17:14.181 623 2283 D ACDB-LOADER: ACDB -> send_audio_cal, acdb_id = 102, path = 1
03-10 10:17:14.181 623 2283 D ACDB-LOADER: ACDB -> send_asm_topology
03-10 10:17:14.181 623 2283 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_STREAM_TOPOLOGY_ID
03-10 10:17:14.182 623 2283 D ACDB-LOADER: ACDB -> send_adm_topology
03-10 10:17:14.182 623 2283 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_COMMON_TOPOLOGY_ID
03-10 10:17:14.182 623 2283 D ACDB-LOADER: ACDB -> send_audtable
03-10 10:17:14.182 623 2283 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_COMMON_TABLE
03-10 10:17:14.182 623 2283 D ACDB-LOADER: ACDB -> AUDIO_SET_AUDPROC_CAL
03-10 10:17:14.182 623 2283 D ACDB-LOADER: ACDB -> send_audvoltable
03-10 10:17:14.182 623 2283 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_GAIN_DEP_STEP_TABLE
03-10 10:17:14.182 623 2283 D : Failed to fetch the lookup information of the device 00000066
03-10 10:17:14.182 623 2283 E ACDB-LOADER: Error: ACDB AudProc vol returned = -19
03-10 10:17:14.182 623 2283 D ACDB-LOADER: ACDB -> AUDIO_SET_AUDPROC_VOL_CAL
03-10 10:17:14.182 623 2283 D ACDB-LOADER: ACDB -> send_afe_cal
03-10 10:17:14.182 623 2283 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AFE_COMMON_TABLE
03-10 10:17:14.182 623 2283 D ACDB-LOADER: ACDB -> AUDIO_SET_AFE_CAL
03-10 10:17:14.182 623 2283 D ACDB-LOADER: ACDB -> send_hw_delay : acdb_id = 102 path = 1
03-10 10:17:14.182 623 2283 D ACDB-LOADER: ACDB -> ACDB_AVSYNC_INFO: ACDB_CMD_GET_DEVICE_PROPERTY
03-10 10:17:14.182 623 2283 D audio_hw_primary: enable_audio_route: apply mixer and update path: spkr-vi-record
03-10 10:17:17.226 623 2283 D ACDB-LOADER: ACDB -> send_audio_cal, acdb_id = 4, path = 1
03-10 10:17:17.226 623 2283 D ACDB-LOADER: ACDB -> send_asm_topology
03-10 10:17:17.226 623 2283 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_STREAM_TOPOLOGY_ID
03-10 10:17:17.226 623 2283 D ACDB-LOADER: ACDB -> send_adm_topology
03-10 10:17:17.226 623 2283 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_COMMON_TOPOLOGY_ID
03-10 10:17:17.226 623 2283 D ACDB-LOADER: ACDB -> send_audtable
03-10 10:17:17.226 623 2283 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_COMMON_TABLE
03-10 10:17:17.226 623 2283 D : Failed to fetch the lookup information of the device 00000004
03-10 10:17:17.226 623 2283 E ACDB-LOADER: Error: ACDB audproc returned = -19
03-10 10:17:17.226 623 2283 D ACDB-LOADER: ACDB -> AUDIO_SET_AUDPROC_CAL
03-10 10:17:17.226 623 2283 D ACDB-LOADER: ACDB -> send_audvoltable
03-10 10:17:17.226 623 2283 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_GAIN_DEP_STEP_TABLE
03-10 10:17:17.227 623 2283 D : Failed to fetch the lookup information of the device 00000004
03-10 10:17:17.227 623 2283 E ACDB-LOADER: Error: ACDB AudProc vol returned = -19
03-10 10:17:17.227 623 2283 D ACDB-LOADER: ACDB -> AUDIO_SET_AUDPROC_VOL_CAL
03-10 10:17:17.227 623 2283 D ACDB-LOADER: ACDB -> send_afe_cal
03-10 10:17:17.227 623 2283 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AFE_COMMON_TABLE
03-10 10:17:17.227 623 2283 D : Failed to fetch the lookup information of the device 00000004
03-10 10:17:17.227 623 2283 E ACDB-LOADER: Error: ACDB AFE returned = -19
03-10 10:17:17.227 623 2283 D ACDB-LOADER: ACDB -> AUDIO_SET_AFE_CAL
03-10 10:17:17.227 623 2283 D ACDB-LOADER: ACDB -> send_hw_delay : acdb_id = 4 path = 1
03-10 10:17:17.227 623 2283 D ACDB-LOADER: ACDB -> ACDB_AVSYNC_INFO: ACDB_CMD_GET_DEVICE_PROPERTY
03-10 10:17:17.227 623 2283 I audio_hw_primary: select_devices Selected apptype: 69936
03-10 10:17:17.227 623 2283 D soundtrigger: audio_extn_sound_trigger_update_stream_status: uc_id 1 of type 0 for Event 3, with Raise=0
03-10 10:17:17.227 623 2283 D ACDB-LOADER: ACDB -> send_audio_cal, acdb_id = 124, path = 0
03-10 10:17:17.227 623 2283 D ACDB-LOADER: ACDB -> send_asm_topology
03-10 10:17:17.227 623 2283 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_STREAM_TOPOLOGY_ID
03-10 10:17:17.227 623 2283 D ACDB-LOADER: ACDB -> send_adm_topology
03-10 10:17:17.227 623 2283 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_COMMON_TOPOLOGY_ID
03-10 10:17:17.228 623 2283 D ACDB-LOADER: ACDB -> send_audtable
03-10 10:17:17.228 623 2283 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_COMMON_TABLE
03-10 10:17:17.228 623 2283 D ACDB-LOADER: ACDB -> AUDIO_SET_AUDPROC_CAL
03-10 10:17:17.228 623 2283 D ACDB-LOADER: ACDB -> send_audvoltable
03-10 10:17:17.228 623 2283 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AUDPROC_GAIN_DEP_STEP_TABLE
03-10 10:17:17.228 623 2283 D ACDB-LOADER: ACDB -> AUDIO_SET_AUDPROC_VOL_CAL
03-10 10:17:17.228 623 2283 D ACDB-LOADER: ACDB -> send_afe_cal
03-10 10:17:17.228 623 2283 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AFE_COMMON_TABLE
03-10 10:17:17.228 623 2283 D ACDB-LOADER: ACDB -> AUDIO_SET_AFE_CAL
03-10 10:17:17.228 623 2283 D ACDB-LOADER: ACDB -> send_hw_delay : acdb_id = 124 path = 0
03-10 10:17:17.228 623 2283 D ACDB-LOADER: ACDB -> ACDB_AVSYNC_INFO: ACDB_CMD_GET_DEVICE_PROPERTY
03-10 10:17:17.230 623 2283 I audio_hw_utils: audio_extn_utils_send_app_type_cfg app_type 69936, acdb_dev_id 124, sample_rate 48000
03-10 10:17:17.230 623 2283 D audio_hw_primary: enable_audio_route: apply mixer and update path: low-latency-playback
03-10 10:17:17.232 623 2283 D audio_hw_primary: select_devices: usecase->type:0, usecase->id:1
03-10 10:17:17.232 623 2283 D audio_hw_primary: select_devices: done
03-10 10:17:18.227 623 2283 D msm8974_platform: platform_set_channel_map mixer_ctl_name:Playback Channel Map15
03-10 10:17:18.228 623 2283 D msm8974_platform: platform_set_channel_map: set mapping(1 2 0 0 0 0 0 0) for channel:2
03-10 10:17:19.273 623 2283 D audio_hw_extn: audio_extn_get_anc_enabled: anc_enabled:0
03-10 10:17:19.273 623 2283 D audio_hw_primary: start_output_stream: exit
03-10 10:17:19.311 623 2284 W AudioFlinger: write blocked for 4955 msecs, 44 delayed writes, thread 0xf1fc0000
03-10 10:17:22.407 623 2284 D audio_hw_primary: out_standby: enter: stream (0xf2751600) usecase(1: low-latency-playback)
03-10 10:17:24.481 623 2284 D audio_hw_primary: disable_audio_route: reset and update mixer path: low-latency-playback
03-10 10:17:24.484 623 2284 D soundtrigger: audio_extn_sound_trigger_update_stream_status: uc_id 1 of type 0 for Event 2, with Raise=0
03-10 10:17:24.484 623 2284 D hardware_info: hw_info_append_hw_type : device_name = speaker
03-10 10:17:24.484 623 2284 D audio_hw_primary: disable_snd_device: snd_device(50: speaker)
Is anyone else experiencing similar ?
m
I'm leaning toward it being the launcher

moonbutt74 said:
So the title says it all,
So far I am experiencing, a crazy loud sound glitch that sounds like a vibrator in a plastic bowl, wonderful image right? xD
Also there is clearly the sound of seeming touch events happening at random intervals so trying to trace it with a live logcat would
be completely insane, but well, :silly:
i think it's somehwere in this
Is anyone else experiencing similar ?
m
I'm leaning toward it being the launcher
Click to expand...
Click to collapse
Headphones?
Mine used to sound like that until I disabled the """"amazing"""" app Smart Connect that seems to be the root of evil for everything.
Sent from my Z5 Premium using XDA Labs

KbaB.BroS said:
Headphones?
Mine used to sound like that until I disabled the """"amazing"""" app Smart Connect that seems to be the root of evil for everything.
Sent from my Z5 Premium using XDA Labs
Click to expand...
Click to collapse
k,
okay i'll disable that too, what seems to have worked for me was installing nove launcher and disabling xperia home.
m

moonbutt74 said:
k,
okay i'll disable that too, what seems to have worked for me was installing nove launcher and disabling xperia home.
m
Click to expand...
Click to collapse
How come that every bug found on Xperia phones seems to have the weirdest way of working around it?
Sent from my Z5 Premium using XDA Labs

KbaB.BroS said:
How come that every bug found on Xperia phones seems to have the weirdest way of working around it?
Sent from my Z5 Premium using XDA Labs
Click to expand...
Click to collapse
I don;t know this is my first sony device. What is more odd to me is the random touch event sounds, and whether or not they are just random or if actual commands are being issued. If that's the case i wonder if it's like that tap-jacking thing that supersu has a prevention feature for.
Still trying to root this thing btw,
m

moonbutt74 said:
I don;t know this is my first sony device. What is more odd to me is the random touch event sounds, and whether or not they are just random or if actual commands are being issued. If that's the case i wonder if it's like that tap-jacking thing that supersu has a prevention feature for.
Still trying to root this thing btw,
m
Click to expand...
Click to collapse
I look forward to your success!
Sent from my Z5 Premium using XDA Labs

Resurrection ROM Skype speakerphone issue

EDIT: this also happens on "Unofficial CM13" build, can't edit the title to reflect this.
Hi, sorry, I can't post in the Resurrection ROM's thread because I don't have enough posts.
Tried on latest stable and unstable Resurrection ROMs (0714), and skype mic does not work when in speakerphone mode. Here are the logs during the switch:
I'm not sure if this is the real reason, but according to the logs, it looks like skype is trying to access "speaker-mic" input, which in turn tries to access ACDB device id 11, which does not exist in audio_platform_info.xml file.
Code:
07-15 18:00:27.433 653 1533 D audio_hw_primary: out_set_parameters: enter: usecase(0: deep-buffer-playback) kvpairs: routing=2
07-15 18:00:27.442 653 1532 D audio_hw_primary: out_set_parameters: enter: usecase(12: audio-ull-playback) kvpairs: routing=2
07-15 18:00:27.563 653 1530 D audio_hw_primary: out_set_parameters: enter: usecase(1: low-latency-playback) kvpairs: routing=2
07-15 18:00:27.564 653 1530 D audio_hw_primary: select_devices: out_snd_device(0: ) in_snd_device(52: speaker-mic)
07-15 18:00:27.564 653 1530 D audio_hw_primary: disable_audio_route: reset and update mixer path: low-latency-record
07-15 18:00:27.585 653 1530 D hardware_info: hw_info_append_hw_type : device_name = handset-mic
07-15 18:00:27.585 653 1530 D audio_hw_primary: disable_snd_device: snd_device(43: handset-mic)
07-15 18:00:27.591 653 1530 D hardware_info: hw_info_append_hw_type : device_name = speaker-mic
07-15 18:00:27.591 653 1530 D audio_hw_primary: enable_snd_device: snd_device(52: speaker-mic)
07-15 18:00:27.597 653 1530 I audio_hw_utils: audio_extn_utils_send_app_type_cfg CAPTURE app_type 69938, acdb_dev_id 11, sample_rate 48000
07-15 18:00:27.598 653 1530 D ACDB-LOADER: ACDB -> send_audio_cal, acdb_id = 11, path = 1, app id = 0x11132, sample rate = 48000
07-15 18:00:27.598 653 1530 D : Failed to fetch the lookup information of the device 0000000B
07-15 18:00:27.598 653 1530 D ACDB-LOADER: ACDB -> AUDIO_SET_VOL_CAL cal type = 12
07-15 18:00:27.598 653 1530 D ACDB-LOADER: ACDB -> audstrm_cal->cal_type.cal_data.cal_size = 16
07-15 18:00:27.598 653 1530 D ACDB-LOADER: ACDB -> GET_AFE_TOPOLOGY_ID for adcd_id 11, Topology Id 112fb
07-15 18:00:27.598 653 1530 D : Failed to fetch the lookup information of the device 0000000B
07-15 18:00:27.598 653 1530 D ACDB-LOADER: ACDB -> send_hw_delay : acdb_id = 11 path = 1
07-15 18:00:27.598 653 1530 D audio_hw_primary: enable_audio_route: apply mixer and update path: low-latency-record
07-15 18:00:27.611 653 1530 D audio_hw_primary: select_devices: done
07-15 18:00:27.611 653 1530 D audio_hw_primary: select_devices: out_snd_device(2: speaker) in_snd_device(0: )
07-15 18:00:27.612 653 1530 D audio_hw_primary: disable_audio_route: reset and update mixer path: low-latency-playback
07-15 18:00:27.649 653 1530 D hardware_info: hw_info_append_hw_type : device_name = handset
07-15 18:00:27.649 653 1530 D audio_hw_primary: disable_snd_device: snd_device(1: handset)
07-15 18:00:27.653 653 1530 D aud_dev_arbi: releaseOneDevice: not sending command, device argument (1) does not match any registered device
07-15 18:00:27.653 653 1530 D aud_dev_arbi: releaseOneDevice: device 1 owner is 0
07-15 18:00:27.653 653 1530 I msm8974_platform: platform_check_and_set_codec_backend_cfg: Usecase bitwidth 16, samplerate 48000
07-15 18:00:27.653 653 1530 I msm8974_platform: platform_check_and_set_codec_backend_cfg: new_snd_devices[0] is 2
07-15 18:00:27.653 653 1530 I msm8974_platform: platform_check_codec_backend_cfg Codec selected backend: 0 current bit width: 16 and sample rate: 48000
07-15 18:00:27.653 653 1530 W msm8974_platform: platform_check_codec_backend_cfg:Use default bw and sr for voice/voip calls
07-15 18:00:27.653 653 1530 D msm8974_platform: platform_check_codec_backend_cfg: resetting sample_rate back to default, backend_idx: 0
07-15 18:00:27.653 653 1530 I msm8974_platform: platform_check_codec_backend_cfg Codec selected backend: 0 updated bit width: 16 and sample rate: 48000
07-15 18:00:27.653 653 1530 D hardware_info: hw_info_append_hw_type : device_name = speaker
07-15 18:00:27.654 653 1530 D audio_hw_primary: enable_snd_device: snd_device(2: speaker)
07-15 18:00:27.654 653 1530 D aud_dev_arbi: acquireOneDevice: device owner for device 2 is 1
07-15 18:00:27.660 653 1530 I audio_hw_primary: select_devices Selected apptype: 69937
07-15 18:00:27.661 653 1530 I audio_hw_utils: audio_extn_utils_send_app_type_cfg PLAYBACK app_type 69937, acdb_dev_id 15, sample_rate 48000
07-15 18:00:27.661 653 1530 D ACDB-LOADER: ACDB -> send_audio_cal, acdb_id = 15, path = 0, app id = 0x11131, sample rate = 48000
07-15 18:00:27.661 653 1530 D ACDB-LOADER: ACDB -> AUDIO_SET_VOL_CAL cal type = 12
07-15 18:00:27.661 653 1530 D ACDB-LOADER: ACDB -> audstrm_cal->cal_type.cal_data.cal_size = 16
07-15 18:00:27.661 653 1530 D ACDB-LOADER: ACDB -> GET_AFE_TOPOLOGY_ID for adcd_id 15, Topology Id 1025e
07-15 18:00:27.661 653 1530 D ACDB-LOADER: ACDB -> send_hw_delay : acdb_id = 15 path = 0
07-15 18:00:27.661 653 1530 D audio_hw_primary: enable_audio_route: apply mixer and update path: low-latency-playback quat_i2s
07-15 18:00:27.701 653 1530 D audio_hw_primary: select_devices: done
07-15 18:00:27.702 653 1530 D audio_hw_extn: audio_extn_set_anc_parameters: anc_enabled:0
07-15 18:00:27.705 653 1530 D ACDB-LOADER: ACDB -> AUDIO_SET_VOL_CAL cal type = 40
07-15 18:00:27.705 653 1530 W msm8974_platform: platform_send_gain_dep_cal: Usecase list is empty
07-15 18:00:27.709 653 8510 D audio_hw_primary: in_set_parameters: enter: kvpairs=input_source=7;routing=-2147483520
07-15 18:00:27.730 653 1530 D AudioFlinger: mixer(0xf23c0000) throttle end: throttle time(2)
07-15 18:00:28.079 3146 3501 D HeadsetStateMachine: Disconnected process message: 10, size: 0
Any help would be greatly appreciated.

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

Screen regularly turns on

Hello,
a while ago, I started having an issue with my s4 mini (serranolte).
Basically, the screen turns itself on very often. For example, I press the power button to turn it off and after a second or so it turns itself on, stays on for ~10 seconds, turns off due to screen timeout, turns on by itself and so on.
I tried both with Lineage OS 14.1 and crDroid v4.4 (android 8.1) and the issue persists.
Here's a copy of the logcat taken while this happens:
Code:
07-15 12:49:42.350 531 634 I PowerManagerService: Going to sleep due to power button (uid 1000)...
07-15 12:49:42.377 531 558 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
07-15 12:49:42.378 531 558 D vndksupport: Loading /vendor/lib/hw/gralloc.msm8960.so from current namespace instead of sphal namespace.
07-15 12:49:42.384 531 558 W Adreno-EGL: <qeglDrvAPI_eglQueryContext:4373>: EGL_BAD_ATTRIBUTE
07-15 12:49:42.827 531 558 I DisplayPowerController: Blocking screen off
07-15 12:49:42.827 531 558 I DisplayPowerController: Unblocked screen off after 0 ms
07-15 12:49:42.827 531 558 D Sensors : activate: acc_enable=0, mag_enable=0
07-15 12:49:42.827 531 558 D Sensors : activate: handle=0, enabled=0
07-15 12:49:42.843 531 558 D Sensors : activate: acc_enable=0, mag_enable=0
07-15 12:49:42.843 531 558 D Sensors : activate: handle=4, enabled=0
07-15 12:49:42.843 531 558 D Sensors : LightSensor enable = 0
07-15 12:49:42.843 531 558 D Sensors : LightSensor enableSensor = 0
07-15 12:49:42.857 531 556 I DisplayManagerService: Display device changed state: "Built-in Screen", OFF
07-15 12:49:42.858 241 241 D SurfaceFlinger: Set power mode=0, type=0 flinger=0xb364e000
07-15 12:49:42.861 241 241 D qdhwcomposer: hwc_setPowerMode: Setting mode 0 on display: 0
07-15 12:49:42.871 1148 1148 D StatusBar: disable<e i a s b H R c s q >
07-15 12:49:42.871 1148 1148 D StatusBar: disable<e i a s b H R c s q >
07-15 12:49:42.879 531 634 I InputReader: Reconfiguring input devices. changes=0x00000004
07-15 12:49:42.918 531 634 I PowerManagerService: Waking up from dozing (uid=1000 reason=android.policy:KEY)...
07-15 12:49:42.922 531 558 I DisplayPowerController: Blocking screen on until initial contents have been drawn.
07-15 12:49:42.923 531 558 D Sensors : setDelay: acc_delay=66667000, mag_delay=200000000
07-15 12:49:42.923 531 558 D Sensors : setDelay: handle=4, delay=250000000
07-15 12:49:42.923 531 558 D Sensors : LightSensor setDelay = 250000000
07-15 12:49:42.923 531 558 D Sensors : LightSensor setSensorDelay = 250000000
07-15 12:49:42.923 531 558 D Sensors : activate: acc_enable=0, mag_enable=0
07-15 12:49:42.923 531 558 D Sensors : activate: handle=4, enabled=1
07-15 12:49:42.923 531 558 D Sensors : LightSensor enable = 1
07-15 12:49:42.923 531 558 D Sensors : LightSensor enableSensor = 1
07-15 12:49:42.927 289 289 D audio_hw_primary: adev_set_parameters: enter: screen_state=off
07-15 12:49:42.942 1148 1148 D StatusBar: disable<e i a s b H R c s q >
07-15 12:49:42.942 1148 1148 D StatusBar: disable<e i a s b H R c s q >
07-15 12:49:42.964 1148 1148 D StatusBar: disable<e i a s b H R c s q >
07-15 12:49:42.979 1148 1148 I chatty : uid=10030(com.android.systemui) identical 2 lines
07-15 12:49:42.979 1148 1148 D StatusBar: disable<e i a s b H R c s q >
07-15 12:49:43.019 531 615 D Sensors : LightSensor readEvents x = 37.000000, raw = 37
07-15 12:49:43.020 531 558 D Sensors : activate: acc_enable=0, mag_enable=0
07-15 12:49:43.020 531 558 D Sensors : activate: handle=4, enabled=0
07-15 12:49:43.020 531 558 D Sensors : LightSensor enable = 0
07-15 12:49:43.020 531 558 D Sensors : LightSensor enableSensor = 0
07-15 12:49:43.021 531 558 D Sensors : setDelay: acc_delay=66667000, mag_delay=200000000
07-15 12:49:43.021 531 558 D Sensors : setDelay: handle=4, delay=1000000000
07-15 12:49:43.021 531 558 D Sensors : LightSensor setDelay = 1000000000
07-15 12:49:43.021 531 558 D Sensors : LightSensor setSensorDelay = 1000000000
07-15 12:49:43.021 531 558 D Sensors : activate: acc_enable=0, mag_enable=0
07-15 12:49:43.021 531 558 D Sensors : activate: handle=4, enabled=1
07-15 12:49:43.021 531 558 D Sensors : LightSensor enable = 1
07-15 12:49:43.022 531 558 D Sensors : LightSensor enableSensor = 1
07-15 12:49:43.120 531 615 D Sensors : LightSensor readEvents x = 39.000000, raw = 39
07-15 12:49:43.335 241 241 D qdhwcomposer: hwc_setPowerMode: Done setting mode 0 on display 0
07-15 12:49:43.344 531 1105 D SurfaceControl: Excessive delay in setPowerMode()
07-15 12:49:43.345 531 556 I DisplayManagerService: Display device changed state: "Built-in Screen", ON
07-15 12:49:43.363 531 634 I InputReader: Reconfiguring input devices. changes=0x00000004
07-15 12:49:43.368 241 241 D SurfaceFlinger: Set power mode=2, type=0 flinger=0xb364e000
07-15 12:49:43.368 241 241 D qdhwcomposer: hwc_setPowerMode: Setting mode 2 on display: 0
07-15 12:49:43.981 531 556 W WindowManager: Timeout waiting for drawn: undrawn=[Window{afd67f u0 StatusBar}]
07-15 12:49:43.983 531 549 D Sensors : setDelay: acc_delay=66667000, mag_delay=200000000
07-15 12:49:43.983 531 549 D Sensors : setDelay: handle=0, delay=66667000
07-15 12:49:43.984 531 549 D Sensors : activate: acc_enable=1, mag_enable=0
07-15 12:49:43.984 531 549 D Sensors : activate: handle=0, enabled=1
07-15 12:49:44.054 241 241 D qdhwcomposer: hwc_setPowerMode: Done setting mode 2 on display 0
07-15 12:49:44.055 531 558 I DisplayPowerController: Unblocked screen on after 1133 ms
07-15 12:49:44.063 531 1105 D SurfaceControl: Excessive delay in setPowerMode()
07-15 12:49:44.079 531 558 W PowerManagerService: Screen on took 1160 ms
07-15 12:49:44.081 1148 1148 I Choreographer: Skipped 63 frames! The application may be doing too much work on its main thread.
07-15 12:49:44.120 531 615 D Sensors : LightSensor readEvents x = 35.000000, raw = 35
07-15 12:49:44.132 289 389 D audio_hw_primary: adev_set_parameters: enter: screen_state=on
Hoping someone can help
Ask me if you need to know anything else, I really hope this isn't an hardware issue...
Thanks, have a nice day

I've also tried flashing an older ROM, Pacman ROM (android 4.3) and I get the same issue.
This leads me to think it is an hardware related issue. Here's the Sensors output:
Code:
D/Sensors ( 836): activate: acc_enable=1, mag_enable=0
D/Sensors ( 836): activate: handle=4, enabled=0
D/Sensors ( 836): LightSensor enable = 0
D/Sensors ( 836): LightSensor enableSensor = 0
D/Sensors ( 836): setDelay: acc_delay=66667000, mag_delay=200000000
D/Sensors ( 836): setDelay: handle=4, delay=1000000000
D/Sensors ( 836): LightSensor setDelay = 1000000000
D/Sensors ( 836): LightSensor setSensorDelay = 1000000000
D/Sensors ( 836): activate: acc_enable=0, mag_enable=0
D/Sensors ( 836): activate: handle=0, enabled=0
D/Sensors ( 836): setDelay: acc_delay=66667000, mag_delay=200000000
D/Sensors ( 836): setDelay: handle=0, delay=66667000
D/Sensors ( 836): activate: acc_enable=1, mag_enable=0
D/Sensors ( 836): activate: handle=0, enabled=1
D/Sensors ( 836): setDelay: acc_delay=200000000, mag_delay=200000000
D/Sensors ( 836): setDelay: handle=0, delay=200000000
D/Sensors ( 836): setDelay: acc_delay=66667000, mag_delay=200000000
D/Sensors ( 836): setDelay: handle=0, delay=66667000
D/Sensors ( 836): activate: acc_enable=1, mag_enable=0
D/Sensors ( 836): activate: handle=4, enabled=1
D/Sensors ( 836): LightSensor enable = 1
D/Sensors ( 836): LightSensor enableSensor = 1
D/Sensors ( 836): setDelay: acc_delay=66667000, mag_delay=200000000
D/Sensors ( 836): setDelay: handle=4, delay=200000000
D/Sensors ( 836): LightSensor setDelay = 200000000
D/Sensors ( 836): LightSensor setSensorDelay = 200000000
D/Sensors ( 836): setDelay: acc_delay=66667000, mag_delay=200000000
D/Sensors ( 836): setDelay: handle=4, delay=1000000000
D/Sensors ( 836): LightSensor setDelay = 1000000000
D/Sensors ( 836): LightSensor setSensorDelay = 1000000000
If you know of anything that could solve this, please let me know. Thanks.

Lenovo P2 without screen won't boot

Hello there,
I have a problem in hands with my Lenovo P2.
So... my screen is broken and I have removed it (yes, my Lenovo does not have a screen right now), but now I'm not able to boot into a freshly flashed Android because the system is trying to connect to the HW (or it seems to be that...) and I don't have a working one.
adb logcat spits this out repeatedly:
Code:
02-14 15:35:37.405 1345 1345 D vndksupport: Loading /vendor/lib64/hw/gralloc.msm8953.so from current namespace instead of sphal namespace.
02-14 15:35:37.406 1345 1345 I SDM : ExtensionInterface::CreateExtensionInterface:
02-14 15:35:37.406 1345 1345 I SDM : SDM-EXTENSION Version: Date: 08/21/18, Commit: bfe6fd2, Change: I8d4aa219cb
02-14 15:35:37.406 1345 1345 I SDM : HWInfo::GetHWResourceInfo: SDE Version = 5, SDE Revision = 10100000, RGB = 2, VIG = 1, DMA = 1, Cursor = 1
02-14 15:35:37.406 1345 1345 I SDM : HWInfo::GetHWResourceInfo: Upscale Ratio = 20, Downscale Ratio = 4, Blending Stages = 4
02-14 15:35:37.406 1345 1345 I SDM : HWInfo::GetHWResourceInfo: SourceSplit = 0 QSEED3 = 0
02-14 15:35:37.406 1345 1345 I SDM : HWInfo::GetHWResourceInfo: BWC = 0, UBWC = 1, Decimation = 1, Tile Format = 0 Concurrent Writeback = 0
02-14 15:35:37.406 1345 1345 I SDM : HWInfo::GetHWResourceInfo: MaxLowBw = 3400000 , MaxHighBw = 3400000
02-14 15:35:37.407 1345 1345 I SDM : HWInfo::GetHWResourceInfo: MaxPipeBw = 2300000 KBps, MaxSDEClock = 400000000 Hz, ClockFudgeFactor = 1.050000
02-14 15:35:37.407 1345 1345 I SDM : HWInfo::GetHWResourceInfo: Prefill factors: Tiled_NV12 = 8, Tiled = 4, Linear = 1, Scale = 1, Fudge_factor = 2
02-14 15:35:37.407 1345 1345 I SDM : HWInfo::GetMDSSRotatorInfo: MDSS Rotator: Count = 1, Downscale = 1, Min_downscale = 2.000000
02-14 15:35:37.407 1345 1345 I SDM : HWInfo::GetHWResourceInfo: Has Support for multiple bw limits shown below
02-14 15:35:37.407 1345 1345 I SDM : HWInfo::GetHWResourceInfo: Mode-index=0 total_bw_limit=3400000 and pipe_bw_limit=2300000
02-14 15:35:37.407 1345 1345 I SDM : HWInfo::GetHWResourceInfo: Mode-index=1 total_bw_limit=3100000 and pipe_bw_limit=2300000
02-14 15:35:37.407 1345 1345 I SDM : HWInfo::GetHWResourceInfo: Mode-index=2 total_bw_limit=3400000 and pipe_bw_limit=2300000
02-14 15:35:37.407 1345 1345 I SDM : HWInfo::GetHWResourceInfo: Mode-index=3 total_bw_limit=3400000 and pipe_bw_limit=2300000
02-14 15:35:37.407 1345 1345 I SDM : SessionManager::SessionManager: Allocate buffers synchronously = 0
02-14 15:35:37.408 514 514 W ServiceManagement: Waited one second for [email protected]::IComposer/default. Waiting another...
02-14 15:35:37.408 1345 1345 I SDM : CoreInterface::CreateCore: Open interface handle = 0x7700655000
02-14 15:35:37.408 1345 1345 I SDM : HWCSession::Register: Set uevent listener = 0x770064b200
02-14 15:35:37.408 1345 1345 I SDM : HWInfo::GetFirstDisplayInterfaceType: First display is internal display
02-14 15:35:37.409 1345 1345 I SDM : CPUHint::Init: Invalid CPU Hint Pre-enable Window -1
02-14 15:35:37.409 1345 1345 I SDM : HWDevice::GetHWPanelMaxBrightnessFromNode: Max brightness level = 255
02-14 15:35:37.409 1345 1345 W SDM : HWDevice::GetHWPanelInfoByNode: Failed to open msm_fb_panel_info node device node 1
02-14 15:35:37.409 1345 1345 W SDM : HWDevice::GetHWPanelInfoByNode: Failed to open msm_fb_panel_info node device node 2
02-14 15:35:37.409 1345 1345 W SDM : HWDevice::GetHWPanelInfoByNode: Failed to open msm_fb_panel_info node device node 3
02-14 15:35:37.409 1345 1345 E SDM : HWDevice::Init: device type = 0 should be present
02-14 15:35:37.409 1345 1345 E SDM : HWInterface::Create: Init on HW Intf type 0 failed
02-14 15:35:37.409 1345 1345 E SDM : HWCDisplay::Init: Display create failed. Error = 11 display_type 0 event_handler 0x77006a7000 disp_intf 0x77006a7040
02-14 15:35:37.410 1345 1345 I SDM : HWCColorManager::CreateColorManager: Successfully loaded libsdm-disp-vndapis.so
02-14 15:35:37.411 1345 1345 I SDM : HWCColorManager::CreateColorManager: Successfully loaded libsdm-disp-vndapis.so and libsdm-diag.so and diag_init'ed
02-14 15:35:37.411 1345 1345 I SDM : HWCSession::Register: Set uevent listener = 0x0
02-14 15:35:37.411 1345 1345 I SDM : CoreInterface::DestroyCore: Close handle
02-14 15:35:37.412 1345 1345 E ComposerHal: failed to open hwcomposer device: Invalid argument
02-14 15:35:37.412 1345 1345 E [email protected]: Could not get passthrough implementation for [email protected]::IComposer/default.
02-14 15:35:37.415 446 446 I VendorServiceManager: service 'display.qservice' died
02-14 15:35:37.495 1231 1257 I ServiceManager: Waiting for service 'SurfaceFlinger' on '/dev/binder'...
02-14 15:35:37.595 1231 1257 I chatty : uid=1000(system) android.display identical 1 line
02-14 15:35:37.695 1231 1257 I ServiceManager: Waiting for service 'SurfaceFlinger' on '/dev/binder'...
02-14 15:35:37.786 500 535 E ANDR-PERF-MPCTL: First Boot check over.Going to 2nd Boot check.
02-14 15:35:37.795 1231 1257 I ServiceManager: Waiting for service 'SurfaceFlinger' on '/dev/binder'...
02-14 15:35:37.996 1231 1257 I chatty : uid=1000(system) android.display identical 2 lines
02-14 15:35:38.096 1231 1257 I ServiceManager: Waiting for service 'SurfaceFlinger' on '/dev/binder'...
02-14 15:35:38.196 1231 1257 W ServiceManager: Service SurfaceFlinger didn't start. Returning NULL
02-14 15:35:38.409 514 514 W ServiceManagement: Waited one second for [email protected]::IComposer/default. Waiting another...
02-14 15:35:38.446 1231 1257 I ServiceManager: Waiting for service 'SurfaceFlinger' on '/dev/binder'...
02-14 15:35:38.504 1352 1352 W mm-pp-dpps: type=1400 audit(0.0:593): avc: granted { read } for uid=1000 name="vndbinder" dev="tmpfs" ino=15735 scontext=u:r:init:s0 tcontext=u:object_r:vndbinder_device:s0 tclass=chr_file
02-14 15:35:38.522 1352 1352 I Dpps : GetInstance: DppsServer ref count increased to 1
02-14 15:35:38.504 1352 1352 W mm-pp-dpps: type=1400 audit(0.0:594): avc: granted { read } for uid=1000 name="vndbinder" dev="tmpfs" ino=15735 scontext=u:r:init:s0 tcontext=u:object_r:vndbinder_device:s0 tclass=chr_file
02-14 15:35:38.504 1352 1352 W mm-pp-dpps: type=1400 audit(0.0:595): avc: granted { read open } for uid=1000 path="/dev/vndbinder" dev="tmpfs" ino=15735 scontext=u:r:init:s0 tcontext=u:object_r:vndbinder_device:s0 tclass=chr_file
02-14 15:35:38.504 1352 1352 W mm-pp-dpps: type=1400 audit(0.0:596): avc: granted { read } for uid=1000 path="/dev/vndbinder" dev="tmpfs" ino=15735 scontext=u:r:init:s0 tcontext=u:object_r:vndbinder_device:s0 tclass=chr_file
02-14 15:35:38.522 1352 1352 E Dpps : GetPanelName():551 GetPanelName: panel-name not found
02-14 15:35:38.522 1352 1352 E Dpps : GetPanelInfoByNode():601 Failed to get panel type info, ret -22
02-14 15:35:38.522 1352 1352 E Dpps : GetFBNodeIndex():640 Unable to get panel info for node index 0, ret -22
02-14 15:35:38.522 1352 1352 E Dpps : InitDisplayHardware():258 Unable to get fb node index (-1), display type 0, ret -22
02-14 15:35:38.522 1352 1352 E Dpps : Init():169 Failed to setup display hardware, ret = -22
02-14 15:35:38.522 1352 1352 E Dpps : main():32 Failed to initialize DPPS, ret = -22
02-14 15:35:38.522 1352 1352 I Dpps : DeleteInstance: DppsServer ref count decreased to 0
02-14 15:35:38.522 1352 1352 I Dpps : DeleteInstance: Deleting DppsServer instance
02-14 15:35:38.546 1231 1257 I ServiceManager: Waiting for service 'SurfaceFlinger' on '/dev/binder'...
02-14 15:35:39.247 1231 1257 I chatty : uid=1000(system) android.display identical 7 lines
02-14 15:35:39.347 1231 1257 I ServiceManager: Waiting for service 'SurfaceFlinger' on '/dev/binder'...
02-14 15:35:39.409 514 514 W ServiceManagement: Waited one second for [email protected]::IComposer/default. Waiting another...
02-14 15:35:39.448 1231 1257 I ServiceManager: Waiting for service 'SurfaceFlinger' on '/dev/binder'...
02-14 15:35:40.249 1231 1257 I chatty : uid=1000(system) android.display identical 8 lines
02-14 15:35:40.349 1231 1257 I ServiceManager: Waiting for service 'SurfaceFlinger' on '/dev/binder'...
02-14 15:35:40.409 514 514 W ServiceManagement: Waited one second for [email protected]::IComposer/default. Waiting another...
Which means the mobile does not boot up, and in turn I'm not able to use scrcpy or other tool that allows me to control the screen via PC.
Is there anyway I can bypass this Display initialization or to output the display renderization to a virtual framebuffer easily?
Any other thoughts on this issue are welcome, as well as other possible solutions to
this case.
Thank you so much in advandce!
Best regards!

It might be a bit barbaric of me but maybe you should just replace the display ;s