These days I have an android ‘phone. Specifically, a Moto G, with android version 4.4.4 according to info. I’m using CSipSimple to enable my home (landline) number on it. Mostly that works fine, and it seems quite rare to have sufficient signal for voice calls but not for SIP. So all’s well, isn’t it?
Yesterday I got an incoming SIP call while I was out. But taking it out of my pocket, the screen wasn’t showing the call, and I had no way to answer it. I typed in my PIN code, and still it was ringing, but still nothing on the screen. Ouch! What’s going wrong?
Having failed to think of anything more sensible, I went straight for the crude approach of power cycling. That has occasionally fixed things when the system appears to overload itself due to too many open apps, or is running warm for no reason I can fathom. Not that that helps with testing incoming SIP calls, so I tried googling, but failed (admittedly without trying very hard) to find reports of similar problems.
Just now I got another incoming SIP call (no caller number, so no answer). This one did display. It was at home, so on wifi. Could that have made all the difference, and if so is there anything I can do to fix the problem when out and about? Or was this some unknown bug that may have been cured by reboot, or pure Heisenbug?
 This is not a good thing. I’d much rather have my late lamented Nokia (from the days when Nokia made really good phones) back. But that’s no longer an option: its successor in 2012 the Nokia E6-00 was such a bugridden steaming pile as to be effectively unusable, and the android is a vast improvement on that.