Skip to content
This repository has been archived by the owner on Dec 12, 2023. It is now read-only.

Telephony services silently crash. Possibly WiFi related. #1614

Closed
nsensfel opened this issue Dec 6, 2020 · 2 comments
Closed

Telephony services silently crash. Possibly WiFi related. #1614

nsensfel opened this issue Dec 6, 2020 · 2 comments

Comments

@nsensfel
Copy link

nsensfel commented Dec 6, 2020

  • Device: F(x)tec Pro1 (halium Generic Device)
  • Channel: Release Candidate
  • Build: 2020-W49/2
  • Vendor Build Date: Tue Aug 25 23:14:33 CST 2020

Steps to reproduce

Solution 1:

  1. Wait an undetermined amount of time (only tested with Wi-Fi on).
  2. Attempt to make a call.

Solution 2:

  1. Boot the device with Wi-Fi enabled.
  2. Start Phone application.
  3. Make a call.
  4. End the call.
  5. Disable Wi-Fi.
  6. Observe Unity8 rebooting.
  7. (Optional: re-activate Wi-Fi)
  8. Attempt to make another call.

Expected behavior

The call goes through.

Actual behavior

Wi-Fi is on (solution 1, or solution 2 without step 7):

The phone application shows the expected service provider. The call is attempted, then "Call failed" appears.

Wi-Fi is off (solution 2 with step 7):

The phone application shows that there is "No network". Calls cannot be attempted.

Logfiles and additional information

Application legacy dialer app: http://paste.ubuntu.com/p/yrQxPzX8ZQ/
Telephony service indicator: http://paste.ubuntu.com/p/k4YvMyNVbv/

Information from Alfred, in the UBPorts Telegram channel:

We've been seeing similar problems on the Pixel 3a. It seems to be a common issue among Qualcomm devices. Best case someone with the BSP sources (maybe fxtec themselves) steps up and finds a workaround without modifying qcrild.
The problem is related to qcrild going out of Binder memory, not being able to communicate with ofono anymore. Restarting ofono helps in most cases

@nsensfel
Copy link
Author

nsensfel commented Dec 6, 2020

Any SMS that was supposed to be received while this bug is active appears to be lost. Quite possibly permanently: I have received an SMS during a call, with someone who had sent me an SMS earlier that I did not receive. Thus, telephony being restored did not recover the missing SMS.

Additional logs:

These two new logs were obtained for the following scenario:

  1. Boot phone with Wi-Fi already on.
  2. Make call.
  3. End call.
  4. Turn off Wi-Fi.
  5. There is no longer any service available.

I have also tested with the edge branch (build number 2020-12-05), with similar results.

@nsensfel
Copy link
Author

nsensfel commented Dec 6, 2020

I did a full firmware restore followed by a clean install of Ubuntu Touch. The issue can no longer be reproduced. I am going to assume that I messed up flashing/updating the firmware at some point and that this was the cause for the bug. I'll close this report, as it does not appear to be reproducible for now.

Edited because I expected to test this for a week, but MMS don't work and I need those so I moved back to another OS. I'm really hoping to be able to use Ubuntu Touch once it has MMS support and is properly supported on the Pro1.

@nsensfel nsensfel closed this as completed Dec 6, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant