ubuntu-touch icon indicating copy to clipboard operation
ubuntu-touch copied to clipboard

Published 20 hours ago • verified publisher icon ubports

Cannot hang up call

Open greskom opened this issue 7 years ago • 151 comments

After moving to UBPorts OTA-1 from Ubuntu Touch OTA-15 I frequently observe unability to hang up call. It is fixed by reboot, but issue reappears soon.

greskom avatar Aug 04 '17 14:08 greskom

Which device you are using?

Flohack74 avatar Aug 04 '17 18:08 Flohack74

BQ Aquaris E4.5.

2017-08-04 20:38 GMT+02:00, Florian Leeber [email protected]:

Which device you are using?

-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/ubports/ubports-touch/issues/195#issuecomment-320323406

greskom avatar Aug 07 '17 14:08 greskom

This is really strange, my girlfriend has one too, and never sees this problem.

Flohack74 avatar Aug 07 '17 16:08 Flohack74

Is this maybe related to this bug? https://github.com/ubports/ubports-touch/issues/153

With OTA1 Ubports I have the problem with the flickering screen during calls. However, with good "timing" I can hang up.

With OTA15 Canonical Image I had the bug that the dialer app freezed when I performed a call. However, this was fixed after flashing the UBPorts image.

RomBuch avatar Aug 07 '17 17:08 RomBuch

Not really. There is no flickering.

2017-08-07 19:27 GMT+02:00, Rom4nB [email protected]:

Is this maybe related to this bug? https://github.com/ubports/ubports-touch/issues/153

With OTA1 Ubports I have the problem with the flickering screen during calls. However, with good "timing" I can hang up.

With OTA15 Canonical Image I had the bug that the dialer app freezed when I performed a call. However, this was fixed after flashing the UBPorts image.

-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/ubports/ubports-touch/issues/195#issuecomment-320727382

greskom avatar Aug 08 '17 10:08 greskom

Same problem for me. (BQE4.5 Ubports r1). But I can tell you that I found a temporary solution. When you cannot close the conversation (because the red button does not respond to the touch), you can swipe to any other application. The green bar of the current call will appear on top. If you touch that bar you will be able to open the phone application window again and you can easily close the call. ;-) GM

Gabriele69 avatar Aug 22 '17 11:08 Gabriele69

Another workaround is to close and reopen phone application. Then I am able to hangup. But this operation sometimes results in a weird freeze. After thereafter longpressing poweroff button menu for reboot/shutdown appears, but it stops responding at all. Only very very long pressing of poweroff button helps to poweroff the device. After boot it works normally for some time.

2017-08-22 13:26 GMT+02:00, GIEMME [email protected]:

Same problem for me. (BQE4.5 Ubports r1). But I can tell you that I found a temporary solution. When you cannot close the conversation (because the red button does not respond to the touch), you can swipe to any other application. The green bar of the current call will appear on top. If you touch that bar you will be able to open the phone application window again and you can easily close the call. ;-) GM

-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/ubports/ubports-touch/issues/195#issuecomment-323997963

greskom avatar Aug 22 '17 12:08 greskom

Same problem I have with my Meizu mx4....and as far as I can remember...since changing to OTA-15 / UBPorts

gitfrank72 avatar Aug 31 '17 19:08 gitfrank72

Clearly this should be a bug, since more users experience the issue. And moreover it is not krillin specific. How can I change the labels?

greskom avatar Sep 03 '17 18:09 greskom

You can´t only we can ;)

Flohack74 avatar Sep 03 '17 19:09 Flohack74

Thanks.

greskom avatar Sep 04 '17 18:09 greskom

I have the same problem

tcarrondo avatar Sep 07 '17 22:09 tcarrondo

Are you sure this is did not occur on the Canonical version? I don't think any changes have been made to parts touching that area, but maybe i'm mistaken... #153 was closed, because it's a hardware issue, so if the two are related, i suspect this is the same here.

Could someone try to provide logs?

NeoTheThird avatar Sep 12 '17 16:09 NeoTheThird

It was sure not happening with Canonical OTA-14. I was using OTA-15 quite shortly but I am almost sure it was OK also with OTA-15. Or at least it was not so frequent.

2017-09-12 18:10 GMT+02:00, Jan Sprinz [email protected]:

Are you sure this is did not occur on the Canonical version? I don't think any changes have been made to parts touching that area, but maybe i'm mistaken... #153 was closed, because it's a hardware issue, so if the two are related, i suspect this is the same here.

Could someone try to provide logs?

-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/ubports/ubports-touch/issues/195#issuecomment-328902097

greskom avatar Sep 12 '17 17:09 greskom

had the same pb with utouch OTA-15 ,releasebut fixed with UBports stable OTA-1 release

lduboeuf avatar Sep 20 '17 20:09 lduboeuf

So can we close this?

Flohack74 avatar Sep 21 '17 06:09 Flohack74

No. I think no. because I've this problem and I've the Ubports 15.04 OTA 1 on my BQ4.5

Gabriele69 avatar Sep 21 '17 10:09 Gabriele69

Definitely, not. I also have this problem on UBPorts 15.04 OTA 1.

2017-09-21 12:09 GMT+02:00, GIEMME [email protected]:

No. I think no. because I've this problem and I've the Ubports 15.04 OTA 1 on my BQ4.5

-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/ubports/ubports-touch/issues/195#issuecomment-331113314

greskom avatar Sep 21 '17 15:09 greskom

ThIs affects me to. Bq 4.5, ubports 15.04, r2

giovanoiannotti avatar Oct 04 '17 07:10 giovanoiannotti

Still present in OTA3.

greskom avatar Apr 05 '18 20:04 greskom

would be interesting to have logs, nobody have an idea what's wrong with this annoying bug ?

lduboeuf avatar Apr 05 '18 21:04 lduboeuf

I am just flashing my Bq 4.5 to ubports. I had this bug often with the latest Canonical version.

dzschille avatar Apr 08 '18 18:04 dzschille

yes, for me as well, fixed with ubports version. But i fully support those who face again this issue :)

lduboeuf avatar Apr 09 '18 07:04 lduboeuf

Hi, it seems, that i have the same problem with my OPO with UT15.04.

Berlinuxer avatar Apr 25 '18 05:04 Berlinuxer

as mentionned earlier, we need logs: https://docs.ubports.com/en/latest/contribute/bugreporting.html?highlight=logs#getting-logs

lduboeuf avatar Apr 25 '18 14:04 lduboeuf

It freezes every time on my phone BQ E4.5:

first thing: Every time I call somebody, UI of phone app freeze but the connection works. It's not possible to push any buttons. I have to kill the app by swiping from the right side. If somebody calls me - Phone App works as expected.

second thing: The history of called contacts works fine. But, if I push phone button (green button on the bottom). App doesn't open last called number, instead it opens a number I called some month ago.

artemanufrij avatar Aug 05 '18 13:08 artemanufrij

BQ E5 here, latest version of UB Ports 16.03 (2018-09-14). It happens if someone calls me, I tried to click on the hang up button and the phone app disappears. I click on the green tab on top of the screen, the phone app is restored but the same happens, sometimes I cannot even click on the button and it disappears again.

The only "workaround" I found is to receive a call with the phone app already open. In that case, there is no issue.

samuelig avatar Sep 15 '18 15:09 samuelig

I confirms the bug. I have exactly the same behavior. Configuration obtained from UT Tweak Tool: Kernel 3.4.67 Aquaris E5 HD Distro: Ubuntu 16.04.5 LTS

BQ E5 here, latest version of UB Ports 16.03 (2018-09-14). It happens if someone calls me, I tried to click on the hang up button and the phone app disappears. I click on the green tab on top of the screen, the phone app is restored but the same happens, sometimes I cannot even click on the button and it disappears again.

The only "workaround" I found is to receive a call with the phone app already open. In that case, there is no issue.

Juaco2018 avatar Oct 04 '18 11:10 Juaco2018

Still present in OTA-6. Even enriched with another critical bug "No network after call".

greskom avatar Dec 12 '18 17:12 greskom

I'm facing randomly this situation on Nexus 5 OTA6 stable: What happened: I made a call, and put the phone close to my ears ( screen become off) then i want to hang call but only the dial screen with green button appears. Cannot hang up call (i have to reboot to close the call)

some logs (syslog), What elese should i check ?

Dec 13 14:16:03 ubuntu-phablet repowerd[986]: OfonoVoiceCallService: dbus_CallAdded(/ril_0/voicecall01,dialing)
Dec 13 14:16:03 ubuntu-phablet repowerd[986]: DefaultStateMachine: handle_active_call
Dec 13 14:16:03 ubuntu-phablet repowerd[986]: UbuntuProximitySensor: enable_proximity_events()
Dec 13 14:16:03 ubuntu-phablet kernel: [20530.340320] adm_callback: cmd = 0x10328 returned error = 0x2
Dec 13 14:16:03 ubuntu-phablet kernel: [20530.341140] adm_callback: cmd = 0x10328 returned error = 0x2
Dec 13 14:16:03 ubuntu-phablet repowerd[986]: UbuntuProximitySensor: schedule_synthetic_initial_event(), state=near, delay_ms=500
Dec 13 14:16:03 ubuntu-phablet kernel: [20530.361681] taiko_codec taiko_codec: taiko_update_uhqa_mode: uhqa_mode=0
Dec 13 14:16:03 ubuntu-phablet kernel: [20530.417017] adm_callback: cmd = 0x10328 returned error = 0x2
Dec 13 14:16:03 ubuntu-phablet kernel: [20530.417677] adm_callback: cmd = 0x10328 returned error = 0x2
Dec 13 14:16:03 ubuntu-phablet repowerd[986]: BacklightBrightnessControl: new_autobrightness_value(0.35)
Dec 13 14:16:03 ubuntu-phablet repowerd[986]: BacklightBrightnessControl: Transitioning brightness 0.38 => 0.35 in 4.00 steps 25000.00us each
Dec 13 14:16:03 ubuntu-phablet repowerd[986]: UbuntuProximitySensor: handle_proximity_event(far)
Dec 13 14:16:03 ubuntu-phablet repowerd[986]: DefaultStateMachine: handle_proximity_far
Dec 13 14:16:03 ubuntu-phablet repowerd[986]: BacklightBrightnessControl: Transitioning brightness 0.38 => 0.35 done
Dec 13 14:16:03 ubuntu-phablet repowerd[986]: UnityScreenService: dbus_emit_brightness(0.352302), brightness_value=90
Dec 13 14:16:05 ubuntu-phablet repowerd[986]: UbuntuProximitySensor: handle_proximity_event(near)
Dec 13 14:16:05 ubuntu-phablet repowerd[986]: DefaultStateMachine: handle_proximity_near
Dec 13 14:16:05 ubuntu-phablet repowerd[986]: BacklightBrightnessControl: Transitioning brightness 0.35 => 0.00 in 36.00 steps 2777.78us each
Dec 13 14:16:05 ubuntu-phablet repowerd[986]: BacklightBrightnessControl: Transitioning brightness 0.35 => 0.00 done
Dec 13 14:16:05 ubuntu-phablet repowerd[986]: UnityScreenService: dbus_emit_brightness(0.000000), brightness_value=0
Dec 13 14:16:05 ubuntu-phablet kernel: [20530.437411] taiko_codec taiko_codec: taiko_update_uhqa_mode: uhqa_mode=0
Dec 13 14:16:05 ubuntu-phablet kernel: [20531.809425] lm3630_backlight_off
Dec 13 14:16:05 ubuntu-phablet repowerd[986]: UnityDisplayPowerControl: turn_off()
Dec 13 14:16:05 ubuntu-phablet repowerd[986]: UnityScreenService: dbus_emit_DisplayPowerStateChange(0,3)
Dec 13 14:16:05 ubuntu-phablet kernel: [20532.056900] mdss_dsi_panel_off:
Dec 13 14:16:05 ubuntu-phablet kernel: [20532.084710] [Touch] touch off
Dec 13 14:16:05 ubuntu-phablet repowerd[986]: UnityScreenService: dbus_clearSysState(:1.49,9)
Dec 13 14:16:09 ubuntu-phablet repowerd[986]: OfonoVoiceCallService: dbus_CallStateChanged(/ril_0/voicecall01,active)
Dec 13 14:16:18 ubuntu-phablet repowerd[986]: UPowerPowerSource: change_device(/org/freedesktop/UPower/devices/battery_batt_therm), is_present=1, state=3, percentage=0.00, temperature=0.00
Dec 13 14:16:22 ubuntu-phablet repowerd[986]: UbuntuProximitySensor: handle_proximity_event(far)
Dec 13 14:16:22 ubuntu-phablet repowerd[986]: DefaultStateMachine: handle_proximity_far
Dec 13 14:16:22 ubuntu-phablet repowerd[986]: LibsuspendSuspendControl: disallow_suspend(DefaultStateMachine)
Dec 13 14:16:22 ubuntu-phablet repowerd[986]: UnityDisplayPowerControl: turn_on()
Dec 13 14:16:22 ubuntu-phablet kernel: [20549.185553] [Touch] touch on
Dec 13 14:16:22 ubuntu-phablet kernel: [20549.394790] mdss_dsi_panel_on
Dec 13 14:16:22 ubuntu-phablet repowerd[986]: BacklightBrightnessControl: Transitioning brightness 0.00 => 0.35 in 36.00 steps 2777.78us each
Dec 13 14:16:22 ubuntu-phablet kernel: [20549.460671] lm3630_backlight_on
Dec 13 14:16:23 ubuntu-phablet repowerd[986]: BacklightBrightnessControl: Transitioning brightness 0.00 => 0.35 done
Dec 13 14:16:23 ubuntu-phablet repowerd[986]: UnityScreenService: dbus_emit_brightness(0.352302), brightness_value=90
Dec 13 14:16:23 ubuntu-phablet repowerd[986]: UnityScreenService: dbus_emit_DisplayPowerStateChange(1,3)
Dec 13 14:16:23 ubuntu-phablet repowerd[986]: OfonoVoiceCallService: set_fast_dormancy(/ril_0,false)
Dec 13 14:16:23 ubuntu-phablet repowerd[986]: BacklightBrightnessControl: new_autobrightness_value(0.34)
Dec 13 14:16:23 ubuntu-phablet repowerd[986]: BacklightBrightnessControl: Transitioning brightness 0.35 => 0.34 in 2.00 steps 50000.00us each
Dec 13 14:16:23 ubuntu-phablet repowerd[986]: BacklightBrightnessControl: Transitioning brightness 0.35 => 0.34 done
Dec 13 14:16:23 ubuntu-phablet repowerd[986]: UnityScreenService: dbus_emit_brightness(0.337677), brightness_value=86
Dec 13 14:16:26 ubuntu-phablet repowerd[986]: DefaultStateMachine: handle_user_activity_extending_power_state
Dec 13 14:16:26 ubuntu-phablet kernel: [20553.512994] adm_callback: cmd = 0x10328 returned error = 0x2
Dec 13 14:16:26 ubuntu-phablet kernel: [20553.513401] adm_callback: cmd = 0x10328 returned error = 0x2
Dec 13 14:16:27 ubuntu-phablet repowerd[986]: BacklightBrightnessControl: new_autobrightness_value(0.33)
Dec 13 14:16:27 ubuntu-phablet repowerd[986]: BacklightBrightnessControl: Transitioning brightness 0.34 => 0.33 in 1.00 steps 100000.00us each
Dec 13 14:16:27 ubuntu-phablet repowerd[986]: BacklightBrightnessControl: Transitioning brightness 0.34 => 0.33 done

lduboeuf avatar Dec 13 '18 13:12 lduboeuf