>From Peter's log Jul 12 13:32:24 ubuntu-phablet kernel: [ 1222.960067][lcm_esd_check]buffer[0]=0x1c[lcm_esd_check]buffer[0]=0x1c[lcm_esd_check]buffer[0]=0x1c[lcm_esd_check]buffer[0]=0x1c[lcm_esd_check]buffer[0]=0x1c[lcm_esd_check]buffer[0]=0x1c[lcm_esd_check]buffer[0]=0x1c[lcm_esd_check]buffer[0]=0x1c[lcm_esd_check]buffer[0]=0x1c[lcm_esd_check]buffer[0]=0x1c[lcm_esd_check]buffer[0]=0x1c Jul 12 13:32:24 ubuntu-phablet kernel: [ 1243.132054][mt-i2c]ERROR,533: WRRD transfer length is not right. trans_len=2, tans_num=2, trans_auxlen=0 Jul 12 13:32:24 ubuntu-phablet kernel: [ 1243.132074][mt-i2c]ERROR,612: _i2c_get_transfer_len fail,return_value=-22 Jul 12 13:32:24 ubuntu-phablet kernel: [ 1243.132089][ALS/PS] tmd2772_init_client_for_cali_call 659 : init dev: -22 Jul 12 13:32:24 ubuntu-phablet kernel: [ 1243.207867][LHJ_PS][tmd2772_ps_calibrate_call][L2619]prox_mean=1023 Jul 12 13:32:24 ubuntu-phablet kernel: [ 1243.207881]prox_mean>800 Jul 12 13:32:25 ubuntu-phablet kernel: [ 1243.732204][LHJ_PS][TMD2772_get_ps_value][L1320]ps=902,[700,800]val=0
... Jul 12 13:33:05 ubuntu-phablet kernel: [ 1245.126340][lcm_esd_check]buffer[0]=0x1c[lcm_esd_check]buffer[0]=0x1c[lcm_esd_check]buffer[0]=0x1c[lcm_esd_check]buffer[0]=0x1c[lcm_esd_check]buffer[0]=0x1c[lcm_esd_check]buffer[0]=0x1c[lcm_esd_check]buffer[0]=0x1c[lcm_esd_check]buffer[0]=0x1c[lcm_esd_check]buffer[0]=0x1c[lcm_esd_check]buffer[0]=0x1c[lcm_esd_check]buffer[0]=0x1c[lcm_esd_check]buffer[0]=0x1c[lcm_esd_check]buffer[0]=0x1c[lcm_esd_check]buffer[0]=0x1c[lcm_esd_check]buffer[0]=0x1c[lcm_esd_check]buffer[0]=0x1c[lcm_esd_check]buffer[0]=0x1c[lcm_esd_check]buffer[0]=0x1c[lcm_esd_check]buffer[0]=0x1c[lcm_esd_check]buffer[0]=0x1c Jul 12 13:33:05 ubuntu-phablet kernel: [ 1284.289510][mt-i2c]ERROR,533: WRRD transfer length is not right. trans_len=2, tans_num=2, trans_auxlen=0 Jul 12 13:33:05 ubuntu-phablet kernel: [ 1284.289539][mt-i2c]ERROR,612: _i2c_get_transfer_len fail,return_value=-22 Jul 12 13:33:05 ubuntu-phablet kernel: [ 1284.289553][ALS/PS] tmd2772_init_client_for_cali_call 659 : init dev: -22 Jul 12 13:33:06 ubuntu-phablet kernel: [ 1284.364629][LHJ_PS][tmd2772_ps_calibrate_call][L2619]prox_mean=864 Jul 12 13:33:06 ubuntu-phablet kernel: [ 1284.364643]prox_mean>800 What I see on proposed Jul 12 03:56:07 ubuntu-phablet repowerd[1049]: DefaultStateMachine: handle_user_activity_extending_power_state Jul 12 03:56:07 ubuntu-phablet repowerd[1049]: UnityScreenService: dbus_requestSysState(:1.41,usensord,1) Jul 12 03:56:07 ubuntu-phablet repowerd[1049]: LibsuspendSuspendControl: disallow_suspend(UnityScreenService) Jul 12 03:56:07 ubuntu-phablet repowerd[1049]: UnityScreenService: dbus_requestSysState(:1.41,usensord,1) => 8 Jul 12 03:56:07 ubuntu-phablet kernel: [ 901.550636][LHJ_PS][tmd2772_ps_calibrate_call][L2636]prox_mean=52 Jul 12 03:56:07 ubuntu-phablet kernel: [ 901.550649]prox_mean<800 Jul 12 03:56:07 ubuntu-phablet kernel: [ 901.556892][LHJ_PS][TMD2772_get_ps_value][L1320]ps=53,[92,92]val=1 Jul 12 03:56:07 ubuntu-phablet kernel: [ 901.563338][LHJ_PS][TMD2772_get_ps_value][L1320]ps=53,[92,92]val=1 Jul 12 03:56:07 ubuntu-phablet kernel: [ 901.577180][LHJ_PS][TMD2772_get_ps_value][L1320]ps=53,[92,92]val=1 Jul 12 03:56:09 ubuntu-phablet repowerd[1049]: UnityScreenService: dbus_clearSysState(:1.41,8) Jul 12 03:56:20 ubuntu-phablet kernel: [ 914.614559][LHJ_PS][TMD2772_get_ps_value][L1320]ps=1002,[92,92]val=0 Jul 12 03:56:21 ubuntu-phablet kernel: [ 915.067010][LHJ_PS][TMD2772_get_ps_value][L1320]ps=48,[92,92]val=1 Jul 12 03:56:26 ubuntu-phablet kernel: [ 920.647066][LHJ_PS][TMD2772_get_ps_value][L1320]ps=240,[92,92]val=0 Jul 12 03:56:27 ubuntu-phablet kernel: [ 921.149780][LHJ_PS][TMD2772_get_ps_value][L1320]ps=51,[92,92]val=1 Ju -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1493574 Title: [vegeta] Phone app makes screen stay black during call (so you can't hang up) Status in Canonical System Image: Incomplete Status in vegetahd: New Status in powerd package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: A similar, if not the same bug, has been reported to be fixed for OTA6. This bug report explains that it's no necessary to wait for a minute or so on the phone call, but the screen turns black immediately, and doesn't turn back on again to allow hanging up via a screen control. Potential duplicate: https://bugs.launchpad.net/canonical-devices- system-image/+bug/1483127 Device: Aquaris E5 HD Ubuntu Edition OS version: 15.04 (r5) A) Incoming phone call: - Accept the incoming call by sliding the grey middle button to the green button - Watch the screen turning black - Bring the phone to your ear, speak (as in a normal phone call) - Take the phone away from your ear, note that the screen stays black How to hang up anyway: (workaround) - (continued from above, screen stays black after taking it away from your ear) - Press the screen lock/unlock button (= button above volume control) - Screen with phone app shows for about half a second, then turns black again - Press the screen lock/unlock button again, and try to press the red hangup button quickly - Repeat the previous step until hanging up succeeds B) Outbound phone call: - Open the phone app - Slide up Recent calls list from bottom edge, select a phone number - Press green dial button to initiate the call - Watch the phone dialling and the screen turning black - Bring the phone to your ear, speak (as in a normal phone call) - Take the phone away from your ear, note that the screen stays black How to hang up anyway: (workaround) - (same procedure as in A. above) - Difference in behavior: * In some calls after pressing the lock/unlock button for the first time the screen stays alight (doesn't turn black again after half a second). Jean-Baptiste Lallement confirms on the ubuntu-phone mailing list: In both cases, covering/uncovering the proximity sensor should turn the screen on, if the screen has not been turned off with the power button. (This is not happening.) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1493574/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
