Was this the only time this occurred? As I said in the original report, it also happened a week previously when the same person in New York tried to phone me. I don't have logs from that time, but there was certainly a reboot in between. Apart from that, I believe I have seen this before but I can't be sure. Those would have been local calls and I would simply have called the person back. But my SIM card doesn't allow international outgoing calls so that wasn't an option in the New York cases.
"Certain apps": I typically use gallery, dekko, terminal (which is set to never be terminated using tweakgeek), browser, camera, settings, contacts, messaging, phone, so those were probably "running" (although apart from terminal probably terminated by the OS). I was not using any of them immediately prior to taking the call: I was expecting the call and it was important, so all I did with the phone was check that it was alive, running smoothly, and that the volume was turned up. I attached two media hub log files. Since they don't include datestamps I couldn't be sure which covers the period of the calls. It's almost certainly the 2 Jun one though. The DBus log file I'm pretty sure is right. Note that this phone has been switched off for a week. I encountered the problems. Then I made a test call. This failed, so I tried rebooting the phone. After that a test call worked. At that point I decided this phone was too unreliable to use and I switched to my iPhone, which I've been using since. After that it wasn't switched on again until just now. I can't use adb shell over USB. As many people have been reporting with MX4s, the USB port is too unreliable to use for more than a few seconds at a time. This is another reason I've concluded this phone is more trouble than it's worth. Please suggest an alternative. I can ssh into the phone no problems. I've put a different SIM card in the phone and I'll leave it running for a while. Right now I can phone it no problem, consistent with me finding that it temporarily fixes itself with a reboot. The software version is the same as it was, and I will avoid upgrading anything to minimise the variables. I'll try phoning again after a few days and report back with the status. However it's not really a comparable environment. As my main phone it travels with me, connects to various wifi and cellular networks. Also, I frequently turn on and off wifi, bluetooth, and airplane mode as a work-around to other bugs. And the camera frequently mysteriously freezes so I have to terminate that. Sitting on my desk doing nothing, I wouldn't be surprised if it works fine. Bear in mind that "this problem disappears after I upgrade to a newer version" isn't really a happy ending to this story. I need to be reliably contactable, I can't take risks there. If critical bugs are creeping into a feature so fundamental to the purpose of a phone then there's a problem with Ubuntu's development process, regardless of this particular bug. If you guys can show me how it was my mistake, or of my carrier, or even of Meizu, then that's different, but at the moment I consider Ubuntu Touch too unstable to use. -- You received this bug notification because you are a member of Ubuntu Phonedations bugs, which is subscribed to ofono in Ubuntu. https://bugs.launchpad.net/bugs/1588127 Title: Phone abandons incoming call Status in Canonical System Image: Incomplete Status in ofono package in Ubuntu: New Status in telephony-service package in Ubuntu: New Bug description: I just received five incoming calls but I couldn't answer any of them. In each case the phone started vibrating, then after a while the ring tone started and the answer buttons were displayed, but before I had a chance to answer, the phone seemed to give up and go back to sleep. Then I could see the green envelope meaning that I had missed a call. The fifth time was me trying from another phone. In this case it seemed that the line was still ringing, but again I was unable to answer the call. After rebooting the phone, I can now answer incoming calls no problem. So it seems this is some bad state that the phone gets into after a while. I've previously had problems with my phone's cover blocking the light sensor and preventing me answering calls. However in this case I was expecting the call and had prepared by opening the cover, so this can't be the problem. Phone is an MX4. OS Ubuntu 15.04 (OTA-10.1). FYI, this was a job interview, with a CTO who was phoning from New York. I'd already had to delay a week after missing the first appointment due to the exact same problem. I've been barely tolerating Ubuntu Phone's bugs up to now, but this is the final straw. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588127/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs Post to : ubuntu-phonedations-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs More help : https://help.launchpad.net/ListHelp
