Thank you for the warning, I have been doing more testing. WIFI and Bluetooth off at the software level. Mobian apt updated to last nightWhen USB is connected screen suspend is flaky, When the screen does not suspend properly gnome-calls responds 100% of the time. There is no mobile data at any time, even immediately after boot
Test is an incoming call any time after the phone enters suspend after 5 minutes. The time slept appears to make no difference.
100% of the time the phone wakes up, (pick-a-number < 100% hours running) gnome-calls will present a UI to answer.
My best pick-a-number is over 18 hours.My worst? Less than six minutes
Min time to sleep is 5 min.
Problem re-occurs 100% after the first time. so, the click VOIP phone on desktop, wait for the phone to wake, immediately login, but gnome-calls is not up. Manually opening gnome-calls results in a red bar stating modem not available. The network provider is configured to forward to a remote on failure, and as soon as that happens, gnome-calls changes and says the modem is fine and available. So, after the phone wakes up, between light the screen and start gnome-calls the process goes sideways, sometimes.
The following is quote from a person who was middle aged (40?) when I was young. Which was a long time ago, lol
> The bad thing about hardware is that it sometimes works and it sometimes doesn't.
> The good thing about software is that it's consistent: it always does not work, and it always does not work in exactly the same way.
Thanks to all who contribute
HTH
LF
Test is an incoming call any time after the phone enters suspend after 5 minutes. The time slept appears to make no difference.
100% of the time the phone wakes up, (pick-a-number < 100% hours running) gnome-calls will present a UI to answer.
My best pick-a-number is over 18 hours.My worst? Less than six minutes
Min time to sleep is 5 min.Problem re-occurs 100% after the first time. so, the click VOIP phone on desktop, wait for the phone to wake, immediately login, but gnome-calls is not up. Manually opening gnome-calls results in a red bar stating modem not available. The network provider is configured to forward to a remote on failure, and as soon as that happens, gnome-calls changes and says the modem is fine and available. So, after the phone wakes up, between light the screen and start gnome-calls the process goes sideways, sometimes.
The following is quote from a person who was middle aged (40?) when I was young. Which was a long time ago, lol
> The bad thing about hardware is that it sometimes works and it sometimes doesn't.
> The good thing about software is that it's consistent: it always does not work, and it always does not work in exactly the same way.
Thanks to all who contribute
HTH
LF