Development [UNOFFICIAL] LineageOS 19

Search This thread
By:
Advanced…
L

LSS4181

Senior Member
Mar 13, 2012
479
171
Google Pixel C
Razer Phone 2
supeople said:
There is also a very serious problem, that is, sometimes the fingerprint unlocks the screen, sometimes it will trigger a bug, that is, the phone screen cannot be turned on, but I can turn on the flash with a shake. Later, I set double tap to wake up the screen, but still can't turn on the screen.
Click to expand...
Click to collapse
+1 to this. Can confirm this issue is reproducible on LMODroid 20221201 also.

I've experienced it several times since flashing and never had it before flashing the recent ROM builds, so I'm not sure what might be broken. Most likely kernel or vendor side.

If you're confident that fingerprint unlock is the culprit, then I'll keep that in mind and avoid unlocking the phone this way if possible.

Managed to get some logcats when it happens. While this is technically not LOS 19, the bug might be the same.

Namely the following error message can be seen many many times since it happened, which kind of implies the screen stopped responding to commands.

Code: 
[drm:dsi_ctrl_dma_cmd_wait_for_done] *ERROR* [msm-dsi-error]: dsi-ctrl-0: Command transfer failed

Then there are these errors implying the screen (as well as touch) is totally unresponsive (dead) when the bug occurs, nothing can go through anymore. After these logcats I could find a lot of processes crashing and hanging with a lot of ANR records mentioned.

Interestingly, notifications and even phone calls can still go through when the screen dies. While I cannot answer phone calls directly in this state, I can however answer it using my paired Galaxy Watch Active2. It appears system functionalities not related to screen and drawing are still functioning properly during this state.

Code: 
12-05 14:00:32.501     0     0 E         : [drm:dsi_ctrl_dma_cmd_wait_for_done] *ERROR* [msm-dsi-error]: dsi-ctrl-0: Command transfer failed
12-05 14:00:32.701     0     0 E         : [drm:dsi_ctrl_dma_cmd_wait_for_done] *ERROR* [msm-dsi-error]: dsi-ctrl-0: Command transfer failed
12-05 14:00:32.701     0     0 E         : [drm:dsi_ctrl_hw_cmn_get_cmd_read_data] *ERROR* [msm-dsi-error]: DSI_0: Panel detected error, no data read
12-05 14:00:32.701     0     0 E         : [drm:dsi_ctrl_cmd_transfer] *ERROR* [msm-dsi-error]: dsi-ctrl-0: read message failed read length, rc=0
12-05 14:00:32.701     0     0 E         : [drm:dsi_display_cmd_mipi_transfer] *ERROR* [msm-dsi-error]: failed to transfer cmd. rc = 0
12-05 14:00:32.701     0     0 E         : [drm:dsi_panel_enable] *ERROR* [msm-dsi-error]: Failed to call dsi_display_cmd_transfer. rc=0
12-05 14:00:32.701     0     0 E         : [drm:dsi_panel_enable] *ERROR* [msm-dsi-error]: [mipi_mot_cmd_csot_1080p_dsc_667] Failed to read pwr_mode, rc = -5
12-05 14:00:32.701     0     0 E         : [drm:dsi_display_enable] *ERROR* [msm-dsi-error]: [qcom,mdss_dsi_mot_csot_nt37701_667_1080x2400_dsc_cmd_v2] failed to enable DSI panel, rc=-5
12-05 14:00:32.701     0     0 E         : [drm:dsi_bridge_pre_enable] *ERROR* [msm-dsi-error]: [0] DSI display enable failed, rc=-5
12-05 14:00:32.701     0     0 I         : display 0000000013c79bf3, name qcom,mdss_dsi_mot_csot_nt37701_667_1080x2400_dsc_cmd_v2 is_dsi_mot_primary(0)
12-05 14:00:32.701     0     0 I [drm:dsi_panel_post_unprepare] [msm-dsi-info]: (mipi_mot_cmd_csot_1080p_dsc_667)+
12-05 14:00:32.718  1593 12778 I ActivityManager: Skipping next CPU consuming process, not a java proc: 1593
12-05 14:00:32.718  1593 12778 I ActivityManager: Skipping next CPU consuming process, not a java proc: 21
12-05 14:00:32.718  1593 12778 I ActivityManager: Skipping next CPU consuming process, not a java proc: 5260
12-05 14:00:32.721  1593 12778 I ActivityManager: Dumping to /data/anr/anr_2022-12-05-14-00-32-721
12-05 14:00:32.721  1593 12778 I ActivityManager: Collecting stacks for pid 17973
12-05 14:00:32.722  1593 12778 I system_server: libdebuggerd_client: started dumping process 17973
12-05 14:00:32.722   920   920 I tombstoned: registered intercept for pid 17973 and type kDebuggerdJavaBacktrace
12-05 14:00:32.725 17973 17978 I ndroid.systemu: Thread[4,tid=17978,WaitingInMainSignalCatcherLoop,Thread*=0xb400007cdc79f3f0,peer=0x12d00230,"Signal Catcher"]: reacting to signal 3
12-05 14:00:32.726 17973 17978 I ndroid.systemu:
12-05 14:00:32.716     0     0 E dsi_pll_7nm_lock_status: DSI PLL(0) lock failed, status=0x00000000
12-05 14:00:32.716     0     0 E dsi_pll_enable: PLL(0) lock failed
12-05 14:00:32.716     0     0 E vco_7nm_prepare: pll(0) enable failed, rc=-110
12-05 14:00:32.716     0     0 E         : [drm:dsi_link_hs_clk_start] *ERROR* [msm-dsi-error]: Failed to prepare dsi byte clk, rc=-110
12-05 14:00:32.716     0     0 E         : [drm:dsi_link_hs_clk_start] *ERROR* [msm-dsi-error]: failed to prepare link HS clks, rc = -110
12-05 14:00:32.716     0     0 E         : [drm:dsi_display_link_clk_enable] *ERROR* [msm-dsi-error]: failed to turn on master hs link clocks, rc=-110
12-05 14:00:32.716     0     0 E         : [drm:dsi_clk_update_link_clk_state] *ERROR* [msm-dsi-error]: failed to start link clk type 2 rc=-110
12-05 14:00:32.716     0     0 E         : [drm:dsi_recheck_clk_state] *ERROR* [msm-dsi-error]: failed to update clock state, rc = -110
12-05 14:00:32.716     0     0 E         : [drm:dsi_clk_req_state] *ERROR* [msm-dsi-error]: Failed to adjust clock state rc = -110
12-05 14:00:32.716     0     0 E         : [drm:dsi_display_clk_ctrl] *ERROR* [msm-dsi-error]: failed set clk state, rc = -110
12-05 14:00:32.716     0     0 E         : [drm:_sde_encoder_resource_control_helper:2255] [sde error]failed to enable clk control -110
12-05 14:00:32.716     0     0 E         : [drm:_sde_encoder_rc_kickoff:2413] [sde error]enc28 sw_event:1, rc in state 0
12-05 14:00:32.716     0     0 E         : [drm:sde_encoder_virt_enable:3410] [sde error]enc28 sde resource control failed: -110
12-05 14:00:32.742  1240  5364 E SDM     : HWPeripheralDRM::SetPanelBrightness: Failed to write to node = /sys/class/backlight/panel0-backlight/brightness, error = Invalid argument
12-05 14:00:32.742  1360  2357 E HWComposer: operator(): operator() failed for display 4630947043778501761: NoResources (6)
12-05 14:00:32.742  1593  2734 E SurfaceFlinger: setDisplayBrightness: failed to transact: -2147483648
12-05 14:00:32.722     0     0 E dsi_pll_7nm_lock_status: DSI PLL(0) lock failed, status=0x00000000
12-05 14:00:32.722     0     0 E dsi_pll_enable: PLL(0) lock failed
12-05 14:00:32.722     0     0 E vco_7nm_prepare: pll(0) enable failed, rc=-110
12-05 14:00:32.722     0     0 E         : [drm:dsi_link_hs_clk_start] *ERROR* [msm-dsi-error]: Failed to prepare dsi byte clk, rc=-110
12-05 14:00:32.722     0     0 E         : [drm:dsi_link_hs_clk_start] *ERROR* [msm-dsi-error]: failed to prepare link HS clks, rc = -110
12-05 14:00:32.722     0     0 E         : [drm:dsi_display_link_clk_enable] *ERROR* [msm-dsi-error]: failed to turn on master hs link clocks, rc=-110
12-05 14:00:32.722     0     0 E         : [drm:dsi_clk_update_link_clk_state] *ERROR* [msm-dsi-error]: failed to start link clk type 2 rc=-110
12-05 14:00:32.722     0     0 E         : [drm:dsi_recheck_clk_state] *ERROR* [msm-dsi-error]: failed to update clock state, rc = -110
12-05 14:00:32.722     0     0 E         : [drm:dsi_clk_req_state] *ERROR* [msm-dsi-error]: Failed to adjust clock state rc = -110
12-05 14:00:32.722     0     0 E         : [drm:dsi_display_clk_ctrl] *ERROR* [msm-dsi-error]: failed set clk state, rc = -110
12-05 14:00:32.722     0     0 I [drm:dsi_display_set_backlight] [msm-dsi-info]: Ignor bl_level 0 as panel is not init.
12-05 14:00:32.722     0     0 E         : [drm:sde_encoder_helper_wait_for_irq:513] [sde error]enc28 intf1 pp0 encoder is disabled
12-05 14:00:32.722     0     0 I [ FTS-MMI ] fts_mmi_panel_state: panel state change: 1->2
12-05 14:00:32.722     0     0 I [ FTS-MMI ] fts_mmi_panel_state: IRQ is EN
12-05 14:00:32.722     0     0 I [ FTS-MMI ] fts_mmi_post_resume: enter
12-05 14:00:32.722     0     0 I [ FTS ] fts_resume_func: enter
12-05 14:00:32.722     0     0 I [ FTS ] fts_mode_handler: Mode Handler starting...
12-05 14:00:32.722     0     0 I [ FTS ] fts_mode_handler: Screen ON...
12-05 14:00:32.722     0     0 I [ FTS ] fts_mode_handler: Sense OFF!
12-05 14:00:32.722     0     0 I [ FTS ] setScanMode: Setting scan mode: mode = 00 settings = 00 !
12-05 14:00:32.723     0     0 I [ FTS ] setScanMode: Setting scan mode OK!
12-05 14:00:32.723     0     0 I [ FTS ] fts_mode_handler: Sense ON!
12-05 14:00:32.723     0     0 I [ FTS ] setScanMode: Setting scan mode: mode = 00 settings = FF !
12-05 14:00:32.723     0     0 I [ FTS ] setScanMode: Setting scan mode OK!
12-05 14:00:32.723     0     0 I [ FTS ] fts_mode_handler: Mode Handler finished! res = 00000000 mode = 00FF0000
12-05 14:00:32.723     0     0 I [ FTS-MMI ] fts_mmi_post_resume: IRQ is EN
12-05 14:00:32.724     0     0 E         : [drm:sde_encoder_helper_wait_for_irq:513] [sde error]enc28 intf1 pp0 encoder is disabled
12-05 14:00:32.724     0     0 I         : [ FTS ] fts_status_event_handler Mutual negative detect Force cal = 01 00 00 00 00 01
12-05 14:00:32.724     0     0 I         : [ FTS ] fts_status_event_handler Echo event of command = A0 00 FF 00 00 00
12-05 14:00:32.726     0     0 I [drm:dsi_display_set_backlight] [msm-dsi-info]: Ignor bl_level 225 as panel is not init.
12-05 14:00:32.869   920   920 I tombstoned: received crash request for pid 17973
12-05 14:00:32.869   920   920 I tombstoned: found intercept fd 512 for pid 17973 and type kDebuggerdJavaBacktrace
12-05 14:00:32.870 17973 17978 I ndroid.systemu: Wrote stack traces to tombstoned
12-05 14:00:32.870   920   920 W tombstoned: missing output fd
12-05 14:00:32.870  1593 12778 I system_server: libdebuggerd_client: done dumping process 17973
12-05 14:00:32.873  1593 12778 I ActivityManager: Collecting stacks for pid 1593
12-05 14:00:32.875  1593 12778 I system_server: libdebuggerd_client: started dumping process 1593
12-05 14:00:32.875   920   920 I tombstoned: registered intercept for pid 1593 and type kDebuggerdJavaBacktrace
12-05 14:00:32.875  1593  1671 I system_server: Thread[2,tid=1671,WaitingInMainSignalCatcherLoop,Thread*=0xb400007cdc781b20,peer=0x12c80150,"Signal Catcher"]: reacting to signal 3
12-05 14:00:32.875  1593  1671 I system_server:
12-05 14:00:32.934     0     0 I [ FTS ] setFeatures: Setting feature: feat = 02 !
12-05 14:00:32.934     0     0 I [ FTS ] setFeatures: Settings =
12-05 14:00:32.934     0     0 I         : 01
12-05 14:00:32.934     0     0 I         : [ FTS ] fts_status_event_handler Echo event of command = C0 1C 00 00 00 01
12-05 14:00:32.935     0     0 I [ FTS ] setFeatures: Setting feature OK!
12-05 14:00:32.935     0     0 I [ FTS ] fromIDtoMask: ID = 2 Index = 0 Position = 2 !
12-05 14:00:32.935     0     0 I [ FTS ] fts_mmi_charger_mode: CHARGER_MODE Enabled!
12-05 14:00:32.935     0     0 I touchscreen primary: ts_mmi_queued_resume: done
12-05 14:00:32.935     0     0 I         : [ FTS ] fts_status_event_handler Echo event of command = C0 1F 00 00 00 00
12-05 14:00:32.941     0     0 I         : [ FTS ] fts_status_event_handler Echo event of command = A2 02 01 00 00 00
12-05 14:00:33.002   920   920 I tombstoned: received crash request for pid 1593
12-05 14:00:33.002   920   920 I tombstoned: found intercept fd 512 for pid 1593 and type kDebuggerdJavaBacktrace
12-05 14:00:33.003  1593  1671 I system_server: Wrote stack traces to tombstoned
12-05 14:00:33.003   920   920 W tombstoned: missing output fd
12-05 14:00:33.008  1593 12778 I system_server: libdebuggerd_client: done dumping process 1593
12-05 14:00:33.014  1593 12778 I ActivityManager: Collecting stacks for pid 7682
 
Last edited:
L

LSS4181

Senior Member
Mar 13, 2012
479
171
Google Pixel C
Razer Phone 2
Another update on the issue. Today I managed to trigger that bug another time. This time it has nothing to do with the fingerprint sensor.

Actually, fingerprint sensors may not be the real cause of the bug, as it remained functional even after the bug has been triggered.

Attaching a logcat. Though as it was not until a few minutes later did I have the chance to dump logs, some information may be lost, but those that appear important remained. Attaching this as a file as it's too big to be put directly on the post.

It seems the phone is constantly having issues with suspend/resume, and it kind of soft-rebooted itself behind the scenes the moment when the bug triggered. As the screen can no longer be successfully initialized, the soft reboot process eventually finished without waiting for the screen. At this point everything else are wokring: physical buttons, fingerprint sensors, notifications, phone calls, and so on. Just that I cannot see anything nor answer calls directly.

UPDATE: After some further usage testing, I think I can rule out anything else being the culprit. I managed to trigger the bug while making phone calls, during which the screen turn off due to proximity sensor, and at one point the screen failed to turn back on, most likely the same cause as the last few times.

So in the end the issue might be a bug that has a chance to manifest when waking up the screen, that causes the screen to simply stop responding to any command for some reasons. Not sure if this is a hardware or firmware issue, but I never had this issue before flashing recent ROMs.

LATE EDIT: It seems another old issue I'm having is still reproducible on later builds but not as often as before. The phone may occasionally reboot on its own, and unlike normal shutdown/reboot, I would not be prompted for SIM PIN when the phone rebooted this way yet SIM still works. The ramoops I got from earlier builds kind of indicated some modem-related fatal error.

Further googling kind of suggests me to use a different baseband... so definitely I may need to flash related stuffs from different FW versions or regions to see if that'll alleviate the issues I'm having.
 

Attachments

  • logcat-excerpt-lmodroid-20221206.txt.gz
    28.5 KB · Views: 8
Last edited:
L

LSS4181

Senior Member
Mar 13, 2012
479
171
Google Pixel C
Razer Phone 2
A bump on the previous display issue. It is still reproducible as of LMODroid 20221224 build, but less frequent than before. So far I only encountered the issue twice since the update, and managed to obtain a logcat of the second time when it happened. It seems there's another update (20221231). Will install it and see if there is any improvement regarding this issue.

Below is a logcat excerpt filtered with glogg by the keyword "dsi". It seems everything's well until the first occurrence of a DSI PLL(0) lock failure, and from that point on all subsequent commands ended in failure, as well as attempts to re-init the panel. Eventually the system gave up initializing the panel and ignored subsequent bl_level change requests.

Code: 
12-29 23:20:16.769     0     0 I [drm:dsi_panel_set_backlight] [msm-dsi-info]: backlight type:2 lvl:111
12-29 23:20:16.776     0     0 I [drm:dsi_panel_set_backlight] [msm-dsi-info]: backlight type:2 lvl:110
12-29 23:20:23.929     0     0 I [drm:dsi_display_set_backlight] [msm-dsi-info]: bl_level changed from 110 to 0
12-29 23:20:23.929     0     0 I [drm:dsi_panel_set_backlight] [msm-dsi-info]: backlight type:2 lvl:0
12-29 23:20:23.969     0     0 I [drm:dsi_display_set_backlight] [msm-dsi-info]: bl_level changed from 0 to 0
12-29 23:20:23.969     0     0 I [drm:dsi_panel_set_backlight] [msm-dsi-info]: backlight type:2 lvl:0
12-29 23:20:23.983     0     0 I [drm:dsi_display_disable] [msm-dsi-info]: dsi_display_disable(DSI-1)+
12-29 23:20:23.983     0     0 I [drm:dsi_panel_disable] [msm-dsi-info]: (mipi_mot_cmd_csot_1080p_dsc_667)+
12-29 23:20:23.987     0     0 I [drm:dsi_panel_send_param_cmd] [msm-dsi-info]: dsi_panel_send_param_cmd: param_name=HBM; val_max =2, default_value=0, value=0
12-29 23:20:24.104     0     0 I         : display 000000004ffebf15, name qcom,mdss_dsi_mot_csot_nt37701_667_1080x2400_dsc_cmd_v2 is_dsi_mot_primary(0)
12-29 23:20:24.104     0     0 I [drm:dsi_panel_post_unprepare] [msm-dsi-info]: (mipi_mot_cmd_csot_1080p_dsc_667)+
12-29 23:20:24.116     0     0 I [drm:dsi_panel_send_param_cmd] [msm-dsi-info]: (mode=0): requested value=0 is same. Do nothing
12-29 23:20:24.116     0     0 I [drm:dsi_panel_set_backlight] [msm-dsi-info]: backlight type:2 lvl:0
12-29 23:20:24.126     0     0 E dsi_pll_7nm_lock_status: DSI PLL(0) lock failed, status=0x00000000
12-29 23:20:24.126     0     0 E dsi_pll_enable: PLL(0) lock failed
12-29 23:20:24.126     0     0 E         : [drm:dsi_link_hs_clk_start] *ERROR* [msm-dsi-error]: Failed to prepare dsi byte clk, rc=-110
12-29 23:20:24.126     0     0 E         : [drm:dsi_link_hs_clk_start] *ERROR* [msm-dsi-error]: failed to prepare link HS clks, rc = -110
12-29 23:20:24.126     0     0 E         : [drm:dsi_display_link_clk_enable] *ERROR* [msm-dsi-error]: failed to turn on master hs link clocks, rc=-110
12-29 23:20:24.126     0     0 E         : [drm:dsi_clk_update_link_clk_state] *ERROR* [msm-dsi-error]: failed to start link clk type 2 rc=-110
12-29 23:20:24.126     0     0 E         : [drm:dsi_recheck_clk_state] *ERROR* [msm-dsi-error]: failed to update clock state, rc = -110
12-29 23:20:24.126     0     0 E         : [drm:dsi_clk_req_state] *ERROR* [msm-dsi-error]: Failed to adjust clock state rc = -110
12-29 23:20:24.126     0     0 E         : [drm:dsi_display_clk_ctrl] *ERROR* [msm-dsi-error]: failed set clk state, rc = -110
12-29 23:20:24.126     0     0 E         : [drm:dsi_host_transfer] *ERROR* [msm-dsi-error]: [qcom,mdss_dsi_mot_csot_nt37701_667_1080x2400_dsc_cmd_v2] failed to enable all DSI clocks, rc=-110
12-29 23:20:24.126     0     0 E         : [drm:dsi_panel_set_backlight] *ERROR* [msm-dsi-error]: failed to update dcs backlight:0
12-29 23:20:24.126     0     0 E         : [drm:dsi_panel_set_param] *ERROR* [msm-dsi-error]: unable to set backlight
12-29 23:21:37.130     0     0 I [drm:dsi_display_set_mode] [msm-dsi-info]: mdp_transfer_time_us=6144 us
12-29 23:21:37.130     0     0 I [drm:dsi_display_set_mode] [msm-dsi-info]: hactive= 1080,vactive= 2400,fps=144
12-29 23:21:37.130     0     0 I [drm:dsi_display_prepare] [msm-dsi-info]: panel_name=mipi_mot_cmd_csot_1080p_dsc_667 ctrl-index=0
12-29 23:21:37.130     0     0 I [drm:dsi_ctrl_isr_configure] [msm-dsi-info]: dsi-ctrl-0: IRQ 528 registered
12-29 23:21:37.130     0     0 I [drm:dsi_panel_power_on] [msm-dsi-info]: (mipi_mot_cmd_csot_1080p_dsc_667)+
12-29 23:21:37.163     0     0 I [drm:dsi_panel_enable] [msm-dsi-info]: (mipi_mot_cmd_csot_1080p_dsc_667)+
12-29 23:21:37.018     0     0 E         : [drm:dsi_ctrl_dma_cmd_wait_for_done] *ERROR* [msm-dsi-error]: dsi-ctrl-0: Command transfer failed
... <70 more occurrences of "Command transfer failed" errors in between > ...
12-29 23:21:51.348     0     0 E         : [drm:dsi_ctrl_dma_cmd_wait_for_done] *ERROR* [msm-dsi-error]: dsi-ctrl-0: Command transfer failed
12-29 23:21:51.348     0     0 E         : [drm:dsi_ctrl_hw_cmn_get_cmd_read_data] *ERROR* [msm-dsi-error]: DSI_0: Panel detected error, no data read
12-29 23:21:51.348     0     0 E         : [drm:dsi_ctrl_cmd_transfer] *ERROR* [msm-dsi-error]: dsi-ctrl-0: read message failed read length, rc=0
12-29 23:21:51.348     0     0 E         : [drm:dsi_display_cmd_mipi_transfer] *ERROR* [msm-dsi-error]: failed to transfer cmd. rc = 0
12-29 23:21:51.348     0     0 E         : [drm:dsi_panel_enable] *ERROR* [msm-dsi-error]: Failed to call dsi_display_cmd_transfer. rc=0
12-29 23:21:51.348     0     0 E         : [drm:dsi_panel_enable] *ERROR* [msm-dsi-error]: [mipi_mot_cmd_csot_1080p_dsc_667] Failed to read pwr_mode, rc = -5
12-29 23:21:51.348     0     0 E         : [drm:dsi_display_enable] *ERROR* [msm-dsi-error]: [qcom,mdss_dsi_mot_csot_nt37701_667_1080x2400_dsc_cmd_v2] failed to enable DSI panel, rc=-5
12-29 23:21:51.348     0     0 E         : [drm:dsi_bridge_pre_enable] *ERROR* [msm-dsi-error]: [0] DSI display enable failed, rc=-5
12-29 23:21:51.348     0     0 I         : display 000000004ffebf15, name qcom,mdss_dsi_mot_csot_nt37701_667_1080x2400_dsc_cmd_v2 is_dsi_mot_primary(0)
12-29 23:21:51.349     0     0 I [drm:dsi_panel_post_unprepare] [msm-dsi-info]: (mipi_mot_cmd_csot_1080p_dsc_667)+
12-29 23:21:51.364     0     0 E dsi_pll_7nm_lock_status: DSI PLL(0) lock failed, status=0x00000000
12-29 23:21:51.364     0     0 E dsi_pll_enable: PLL(0) lock failed
12-29 23:21:51.364     0     0 E         : [drm:dsi_link_hs_clk_start] *ERROR* [msm-dsi-error]: Failed to prepare dsi byte clk, rc=-110
12-29 23:21:51.364     0     0 E         : [drm:dsi_link_hs_clk_start] *ERROR* [msm-dsi-error]: failed to prepare link HS clks, rc = -110
12-29 23:21:51.364     0     0 E         : [drm:dsi_display_link_clk_enable] *ERROR* [msm-dsi-error]: failed to turn on master hs link clocks, rc=-110
12-29 23:21:51.364     0     0 E         : [drm:dsi_clk_update_link_clk_state] *ERROR* [msm-dsi-error]: failed to start link clk type 2 rc=-110
12-29 23:21:51.364     0     0 E         : [drm:dsi_recheck_clk_state] *ERROR* [msm-dsi-error]: failed to update clock state, rc = -110
12-29 23:21:51.364     0     0 E         : [drm:dsi_clk_req_state] *ERROR* [msm-dsi-error]: Failed to adjust clock state rc = -110
12-29 23:21:51.364     0     0 E         : [drm:dsi_display_clk_ctrl] *ERROR* [msm-dsi-error]: failed set clk state, rc = -110
12-29 23:21:51.370     0     0 E dsi_pll_7nm_lock_status: DSI PLL(0) lock failed, status=0x00000000
12-29 23:21:51.370     0     0 E dsi_pll_enable: PLL(0) lock failed
12-29 23:21:51.370     0     0 E         : [drm:dsi_link_hs_clk_start] *ERROR* [msm-dsi-error]: Failed to prepare dsi byte clk, rc=-110
12-29 23:21:51.370     0     0 E         : [drm:dsi_link_hs_clk_start] *ERROR* [msm-dsi-error]: failed to prepare link HS clks, rc = -110
12-29 23:21:51.370     0     0 E         : [drm:dsi_display_link_clk_enable] *ERROR* [msm-dsi-error]: failed to turn on master hs link clocks, rc=-110
12-29 23:21:51.370     0     0 E         : [drm:dsi_clk_update_link_clk_state] *ERROR* [msm-dsi-error]: failed to start link clk type 2 rc=-110
12-29 23:21:51.370     0     0 E         : [drm:dsi_recheck_clk_state] *ERROR* [msm-dsi-error]: failed to update clock state, rc = -110
12-29 23:21:51.370     0     0 E         : [drm:dsi_clk_req_state] *ERROR* [msm-dsi-error]: Failed to adjust clock state rc = -110
12-29 23:21:51.370     0     0 E         : [drm:dsi_display_clk_ctrl] *ERROR* [msm-dsi-error]: failed set clk state, rc = -110
12-29 23:21:51.370     0     0 I [drm:dsi_display_set_backlight] [msm-dsi-info]: Ignor bl_level 0 as panel is not init.
12-29 23:21:52.386     0     0 I [drm:dsi_display_set_backlight] [msm-dsi-info]: Ignor bl_level 257 as panel is not init.
 
L

LSS4181

Senior Member
Mar 13, 2012
479
171
Google Pixel C
Razer Phone 2
Okay. Reproduced the bug on 20221231 as well. Logcat excerpt here. However, the logcat this time seems to indicate that the PLL(0) lock failure happened much later than initial occurrence of the command transfer failure, so it's probably just that the screen would suddenly stop responding to commands and that's it. The PLL(0) lock failure is merely one of the consequences when the screen stopped responding.

Code: 
01-01 13:55:23.688     0     0 I [drm:dsi_display_set_mode] [msm-dsi-info]: mdp_transfer_time_us=6144 us
01-01 13:55:23.688     0     0 I [drm:dsi_display_set_mode] [msm-dsi-info]: hactive= 1080,vactive= 2400,fps=144
01-01 13:55:23.688     0     0 I [drm:dsi_display_prepare] [msm-dsi-info]: panel_name=mipi_mot_cmd_csot_1080p_dsc_667 ctrl-index=0
01-01 13:55:23.688     0     0 I [drm:dsi_ctrl_isr_configure] [msm-dsi-info]: dsi-ctrl-0: IRQ 528 registered
01-01 13:55:23.688     0     0 I [drm:dsi_panel_power_on] [msm-dsi-info]: (mipi_mot_cmd_csot_1080p_dsc_667)+
01-01 13:55:23.723     0     0 I [drm:dsi_panel_enable] [msm-dsi-info]: (mipi_mot_cmd_csot_1080p_dsc_667)+
01-01 13:55:23.641     0     0 E         : [drm:dsi_ctrl_dma_cmd_wait_for_done] *ERROR* [msm-dsi-error]: dsi-ctrl-0: Command transfer failed
... <70 more occurrences of "Command transfer failed" errors in between > ...
01-01 13:55:37.971     0     0 E         : [drm:dsi_ctrl_dma_cmd_wait_for_done] *ERROR* [msm-dsi-error]: dsi-ctrl-0: Command transfer failed
01-01 13:55:37.971     0     0 E         : [drm:dsi_ctrl_hw_cmn_get_cmd_read_data] *ERROR* [msm-dsi-error]: DSI_0: Panel detected error, no data read
01-01 13:55:37.971     0     0 E         : [drm:dsi_ctrl_cmd_transfer] *ERROR* [msm-dsi-error]: dsi-ctrl-0: read message failed read length, rc=0
01-01 13:55:37.971     0     0 E         : [drm:dsi_display_cmd_mipi_transfer] *ERROR* [msm-dsi-error]: failed to transfer cmd. rc = 0
01-01 13:55:37.971     0     0 E         : [drm:dsi_panel_enable] *ERROR* [msm-dsi-error]: Failed to call dsi_display_cmd_transfer. rc=0
01-01 13:55:37.971     0     0 E         : [drm:dsi_panel_enable] *ERROR* [msm-dsi-error]: [mipi_mot_cmd_csot_1080p_dsc_667] Failed to read pwr_mode, rc = -5
01-01 13:55:37.971     0     0 E         : [drm:dsi_display_enable] *ERROR* [msm-dsi-error]: [qcom,mdss_dsi_mot_csot_nt37701_667_1080x2400_dsc_cmd_v2] failed to enable DSI panel, rc=-5
01-01 13:55:37.971     0     0 E         : [drm:dsi_bridge_pre_enable] *ERROR* [msm-dsi-error]: [0] DSI display enable failed, rc=-5
01-01 13:55:37.971     0     0 I         : display 00000000645349dd, name qcom,mdss_dsi_mot_csot_nt37701_667_1080x2400_dsc_cmd_v2 is_dsi_mot_primary(0)
01-01 13:55:37.972     0     0 I [drm:dsi_panel_post_unprepare] [msm-dsi-info]: (mipi_mot_cmd_csot_1080p_dsc_667)+
01-01 13:55:37.987     0     0 E dsi_pll_7nm_lock_status: DSI PLL(0) lock failed, status=0x00000000
01-01 13:55:37.987     0     0 E dsi_pll_enable: PLL(0) lock failed
01-01 13:55:37.987     0     0 E         : [drm:dsi_link_hs_clk_start] *ERROR* [msm-dsi-error]: Failed to prepare dsi byte clk, rc=-110
01-01 13:55:37.987     0     0 E         : [drm:dsi_link_hs_clk_start] *ERROR* [msm-dsi-error]: failed to prepare link HS clks, rc = -110
01-01 13:55:37.987     0     0 E         : [drm:dsi_display_link_clk_enable] *ERROR* [msm-dsi-error]: failed to turn on master hs link clocks, rc=-110
01-01 13:55:37.987     0     0 E         : [drm:dsi_clk_update_link_clk_state] *ERROR* [msm-dsi-error]: failed to start link clk type 2 rc=-110
01-01 13:55:37.987     0     0 E         : [drm:dsi_recheck_clk_state] *ERROR* [msm-dsi-error]: failed to update clock state, rc = -110
01-01 13:55:37.987     0     0 E         : [drm:dsi_clk_req_state] *ERROR* [msm-dsi-error]: Failed to adjust clock state rc = -110
01-01 13:55:37.987     0     0 E         : [drm:dsi_display_clk_ctrl] *ERROR* [msm-dsi-error]: failed set clk state, rc = -110
01-01 13:55:37.992     0     0 E dsi_pll_7nm_lock_status: DSI PLL(0) lock failed, status=0x00000000
01-01 13:55:37.992     0     0 E dsi_pll_enable: PLL(0) lock failed
01-01 13:55:37.992     0     0 E         : [drm:dsi_link_hs_clk_start] *ERROR* [msm-dsi-error]: Failed to prepare dsi byte clk, rc=-110
01-01 13:55:37.992     0     0 E         : [drm:dsi_link_hs_clk_start] *ERROR* [msm-dsi-error]: failed to prepare link HS clks, rc = -110
01-01 13:55:37.992     0     0 E         : [drm:dsi_display_link_clk_enable] *ERROR* [msm-dsi-error]: failed to turn on master hs link clocks, rc=-110
01-01 13:55:37.992     0     0 E         : [drm:dsi_clk_update_link_clk_state] *ERROR* [msm-dsi-error]: failed to start link clk type 2 rc=-110
01-01 13:55:37.992     0     0 E         : [drm:dsi_recheck_clk_state] *ERROR* [msm-dsi-error]: failed to update clock state, rc = -110
01-01 13:55:37.992     0     0 E         : [drm:dsi_clk_req_state] *ERROR* [msm-dsi-error]: Failed to adjust clock state rc = -110
01-01 13:55:37.992     0     0 E         : [drm:dsi_display_clk_ctrl] *ERROR* [msm-dsi-error]: failed set clk state, rc = -110
01-01 13:55:37.992     0     0 I [drm:dsi_display_set_backlight] [msm-dsi-info]: Ignor bl_level 0 as panel is not init.
01-01 13:55:37.997     0     0 I [drm:dsi_display_set_backlight] [msm-dsi-info]: Ignor bl_level 257 as panel is not init.

I just noticed something in common here when I compared the previous logcats: There are exactly 72 lines of "Command transfer failed" before the system realized the panel is no longer working and tried to re-initialize the panel, which would fail eventually. The logcat doesn't really tell me what exactly these 72 commands are, however. Additionally, it seems the driver would only try to re-initialize the panel up to twice before giving up and ignoring any further commands.

EDIT: Guess today is kinda a bad day. The screen died again, just about an hour since the last time I rebooted the phone via "adb reboot". The logcat I took before rebooting looked pretty identical to this one.

EDIT 2: After a day the screen died again. Not to mention at some point the system's brightness settings became borked as well. The screen was set to max brightness regardless of actual brightness setting, and from the logcat of that boot, the bl_level values being set were either 0 or 1024. Normally it could be any nonzero value between 1-1024 when turned on, depending on brightness setting, but not this time. After rebooting the phone everything returned to normal for now, including the brightness functionality.

Could it be the 20221231 build kinda regressed? With 20221224 the screen issue was rather infrequent, but now it feels like it's back to the state like 20221201...

EDIT 3: It really feels like the 20221231 build has regressed from the previous one. I only had 2 occurrences while the system was on 20221224, but now I'm back to about 1-2 times a day.
 
Last edited:
L

LSS4181

Senior Member
Mar 13, 2012
479
171
Google Pixel C
Razer Phone 2
rodrimax10 said:
Has the black screen issue been fixed on the 20230103 build? i have been flashing lineage every week with no luck. Never had that issue before it going official.

Also, why is there not a dedicated thread for it?
Click to expand...
Click to collapse
Indeed. Guess it should deserve its own thread, though it's going to take time to review all what I've found.

Should apply to both Lineage and LMODroid as they appear to be based on the same tree. The latter keeps USB debugging turned on by default, making it more trivial to obtain information about the problem.

EDIT: Here it is. Actually, with LMODroid 20230107, I found something new in the logcat that were not present before.
 
Last edited:
  • Like
Reactions: rodrimax10
You must log in or register to reply here.

Similar threads

P
Question A working GCam for Motorola Edge 20 Pro?
Replies
74
Views
38K
M
Milica84
andylauuuu
Question how to root edge 20 pro ?or get the TWRP?
Replies
13
Views
15K
Rutercito
Rutercito
MikeChannon
  • Sticky
General [Info] Motorola Edge 20 Pro
Replies
5
Views
7K
monsmons262626
monsmons262626
P
Question Motorola Edge S Pro (Manual Update)
Replies
33
Views
8K
J
jeffreysus
K
Development TWRP Unofficial Pstar
Replies
22
Views
6K
MukiAya
MukiAya

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 1
    L
    LSS4181
    rodrimax10 said:
    Has the black screen issue been fixed on the 20230103 build? i have been flashing lineage every week with no luck. Never had that issue before it going official.

    Also, why is there not a dedicated thread for it?
    Click to expand...
    Click to collapse
    Indeed. Guess it should deserve its own thread, though it's going to take time to review all what I've found.

    Should apply to both Lineage and LMODroid as they appear to be based on the same tree. The latter keeps USB debugging turned on by default, making it more trivial to obtain information about the problem.

    EDIT: Here it is. Actually, with LMODroid 20230107, I found something new in the logcat that were not present before.
    View
  • 14
    S
    SGCMarkus
    Lineage-OS-Feature-Image-Background-Colour.png



    LineageOS is a free, community built, aftermarket firmware distribution of Android 10.0, which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.

    Code: 
    #include "std_disclaimer.h"
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

    What's working:
    • RIL (Calls, SMS, Data)
    • IMS
    • Fingerprint
    • Wi-Fi
    • Bluetooth
    • Bluetooth Audio
    • Camera
    • Audio
    • Sensors
    • Flash
    • GPS
    • DAC
    • Vibration
    • Wifi Hotspot
    • Display out
    • Wireless display
    • Selinux enforcing

    What's not working:
    • a2dp offload

    Flashing Instructions:

    Go to the first (pre) release in the downloads, and download the boot.img, vendor_boot.img, dtbo.img and copy-partitions-20220222.zip
    • Reboot to bootloader (adb reboot bootloader or hold vol- and power when the phone is off)
    • Code: 
      fastboot flash boot boot.img
    • Code: 
      fastboot flash vendor_boot vendor_boot.img
    • Code: 
      fastboot flash dtbo dtbo.img
    • Use volume keys and power to reboot to recovery, or use
      Code: 
      fastboot reboot recovery
    • If you dont have both slots populated, nows your chance:
      a) Enable adb sideload
      b) Flash the copy partitions script:
      Code: 
      adb sideload copy-partitions-20220222.zip
    • Enable adb sideload and flash LineageOS:
      Code: 
      adb sideload lineage-19.1-20220327-UNOFFICIAL-pstar.zip
      - replace zip name if needed -
    • Reboot to recovery: Advanced -> Reboot recovery
    • (Optional) Flash Gapps/Magisk:
      a) Enable adb sideload and:
      Code: 
      adb sideload gapps.zip
      (similar for magisk)
    • Factory reset/format data
    • Reboot system
    • Profit

    Edge 20 Pro Telegram group

    Downloads:
    pstar releases here: github

    Sources:
    Device Tree pstar: pstar
    Device Tree sm8250-common: sm8250-common
    Kernel: sm8250
    Vendor: motorola
    lineage-19.1 branches

    XDA:DevDB Information
    LineageOS for the Motorola Edge 20 Pro, ROM for the Motorola Edge 20 Pro

    Contributors
    SGCMarkus
    Source Code: https://github.com/LineageOS

    ROM OS Version: Android 12
    ROM Kernel: Linux 4.x
    ROM Firmware Required: 11
    Based On: LineageOS

    Version Information
    Status:     Stable
    View
    4
    S
    SpaceTech100
    Does someone know when an official build wil come out?
    View
    3
    S
    SGCMarkus
    Reporting Bugs
    • DO NOT Report bugs if you're running a custom kernel or you installed Xposed
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • If it is a random reboot, grab dmesg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless). Also dump /dev/block/bootdevice/by-name/pstore and attach that
    • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log

    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.

    Changelogs

    Release 27.03.2022 (LOS19)
    - First public release
    View
    2
    ilia3367
    ilia3367
    (y) For our phone was released on October 04, 2022 OFFICIAL !!! Lineage OS.
    Congratulations to you! 🤝

    Contributors:
    View
    1
    L
    LSS4181
    rodrimax10 said:
    Has the black screen issue been fixed on the 20230103 build? i have been flashing lineage every week with no luck. Never had that issue before it going official.

    Also, why is there not a dedicated thread for it?
    Click to expand...
    Click to collapse
    Indeed. Guess it should deserve its own thread, though it's going to take time to review all what I've found.

    Should apply to both Lineage and LMODroid as they appear to be based on the same tree. The latter keeps USB debugging turned on by default, making it more trivial to obtain information about the problem.

    EDIT: Here it is. Actually, with LMODroid 20230107, I found something new in the logcat that were not present before.
    View

New posts