Now I’m a fresh user of a Xperia 10 III, and the story continues. As ever, for 8 years now.
Background: living in Germany wich has, as well nown, a poor mobile network infrastructure. Oftenly, some networks are available, but all of them with weak signal strength.
Since the beginning with the Jolla phone something goes wrong under this conditions. The phone tries to change the connections, chokes on sth., normally gets it, but in some cases eventually gives up and leaves me disconnected.
Back in the days I had to restart the ofono service manually then and need this to do that often, that there was an app once in one of the stores (so I guess I wasn’t the only one with this problem).
Later, with the Xperia X, I used a script, see here.
(It might be noteworthy at this point that on the X even journald crashed and disappeared…)
Now, with the more powerful Xperia 10 III (without any manipulations so far) there are still short disconnects. But the connection ‘respawns’, and all is well… all? No. It’s not.
Something accumulates, and after a couple hours I’ll find the ofonod process using a significant amount of CPU power. This morning it was 13% constantly. Device was warm.
So, the well known procedure: systemctl restart ofono
Not surprising: ofonod’s cpu load went back to ~0%, according to Lighthouse. Phone fully working, battery use back to normal.
Disappointing, somehow. First, there is (must be) some basic bug in the OS that impedes the usage of the device as phone. Literally. It’s not just there, it’s there for 8 years. Constantly. But it’s not reproducable, unless you live in Germanys low mountain range.
And now I don’t even know anymore how to reset the service automatically like I did with the X.
I wonder what’s next.
Any useful hints appreciated.
Michael
)