+- PINE64 (https://forum.pine64.org)
+-- Forum: PinePhone (https://forum.pine64.org/forumdisplay.php?fid=120)
+--- Forum: PinePhone Software (https://forum.pine64.org/forumdisplay.php?fid=121)
+---- Forum: Manjaro on PinePhone (https://forum.pine64.org/forumdisplay.php?fid=130)
+---- Thread: No phone calls in Manjaro Pinephone (/showthread.php?tid=12137)
Pages:
1
2
RE: No phone calls in Manjaro Pinephone - firefox-58 - 11-17-2020
(11-16-2020, 05:36 PM)wibble Wrote: What's your source for that being the order of events on receiving a call? Have you been following a trace, or just observing that the phone wakes, then you see a wifi symbol appear, then the phone eventually starts ringing? I suspect what's happening is that the modem wakes the sleeping CPU, which goes through the same resume-from-suspend process as it would if the power button was pressed. This includes NetworkManager reconnecting Wifi, and ModemManager talking with the modem. As the modem often drops off the USB bus at this point, before reappearing as another device (modem number in ModemManager increments each time this happens) it can take a while before modemmanager finds out there's a call ringing. ModemManager then sends the dbus signal which the Calls app receives, pops up and starts the ring tone. I'm speculating based on how things have worked on earlier linux phones, so if you've got a more recent source I'd be interested.
YES, I am sure about this.
If phone is sleeping and an incoming call occurs:
1. display lights up
2 symbol of WiFi is displayed in unconnect state untlil it happens or goes to timeout after ca. 10 seconds
3. symbol of mobile connection is shown and connection established.
If the WifI connection lasts too long to be established or times out incoming call is for sure missed
RE: No phone calls in Manjaro Pinephone - Lousy Fisherman - 11-17-2020
(11-17-2020, 04:08 AM)firefox-58 Wrote:The exact same sequence of events happens in both Arch 20201112 and Mobian (unsupported apt-upgrade 20201115).(11-16-2020, 05:36 PM)wibble Wrote: What's your source for that being the order of events on receiving a call? Have you been following a trace, or just observing that the phone wakes, then you see a wifi symbol appear, then the phone eventually starts ringing? I suspect what's happening is that the modem wakes the sleeping CPU, which goes through the same resume-from-suspend process as it would if the power button was pressed. This includes NetworkManager reconnecting Wifi, and ModemManager talking with the modem. As the modem often drops off the USB bus at this point, before reappearing as another device (modem number in ModemManager increments each time this happens) it can take a while before modemmanager finds out there's a call ringing. ModemManager then sends the dbus signal which the Calls app receives, pops up and starts the ring tone. I'm speculating based on how things have worked on earlier linux phones, so if you've got a more recent source I'd be interested.
YES, I am sure about this.
If phone is sleeping and an incoming call occurs:
1. display lights up
2 symbol of WiFi is displayed in unconnect state untlil it happens or goes to timeout after ca. 10 seconds
3. symbol of mobile connection is shown and connection established.
If the WifI connection lasts too long to be established or times out incoming call is for sure missed
Sleep/suspend is very flaky. It is tough to test wake up when sleep is .....
Anyway, biggest improvement in both these builds is gnome-calls wakes up 100% of the time, before only the screen would light.
There is cellular data after boot in Arch, there is no cellular data in mobian
HTH
LF