Repository navigation
omamobile-modem-sit 0.3.44: an IMS bearer the network ended no longer blocks the internet bearer's reconnect - #881
Conversation
… blocks the internet bearer's reconnect When the network ends both bearers at once (an empty IND_DATA_CALL_LIST_CHANGED), the reconnect (0.3.42) cleared only the internet bearer's record. sitd's IMS record (CID 2) stayed behind, naming a CID the modem no longer listed, so activate()'s ownership check refused every try with "existing target or unresolved bearer ownership". On a Pixel 9a (27077, at home) that kept mobile data down from 02:25 until a reboot six hours later, 22 tries, while the modem stayed registered. The reconnect now also clears an IMS record whose CID is gone from the list: it holds nothing to release. A listed IMS bearer keeps its record. Checked on the 9a in that state: with the IMS record moved aside by hand, the running sitd's next try set the internet bearer up again (HTTPS over rmnet0 fine). IMS itself is not brought back by this; calls and SMS still need a reboot after such a drop. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Thank you, this is a clear find and a careful fix: the log, the one check in Three things for the follow-up you mention, none of them for this pull request:
Your report also corrects something I wrote: the release notes say calls and texts use a separate connection that didn't drop. On your network it dropped together with the data bearer. I'll open an issue for "IMS stays down after the network ends its bearer" so the follow-up has a home. |
What and why
After the network ended both bearers at once, mobile data stayed down until a reboot, even with the reconnect from 0.3.42 in place.
What happened on a Pixel 9a (27077, at home, not moving), 2026-11-18:
Packet registration stayed
homethroughout.reconnect()clears the internet bearer's own record, but sitd's IMS record (ims-session.json, CID 2) stayed behind although the modem no longer listed CID 2.activate()'s checkcalls - modem != ownedthen refused every try.reconnect()now also clears an IMS record whose CID is gone from the list. It holds nothing to release, so nothing is sent to the modem for it. A listed IMS bearer keeps its record.This does not bring IMS back. Calls and SMS still need a reboot after such a drop. I have a follow-up for that on a separate branch, which I'll open once it has seen a real loss on the phone.
Device and build
uname -r): 7.3.0-rc6-omamobile-push1-gbd32edee1132Checks (no phone needed)
tools/pr-check upstream/mainpassestests/allpasses: not run. CI will show it.tests/packagespasses for the package I touched:packages/omamobile-modem-sit/test/all(scripts parse, unit tests plus RIL against sit-sim, staged layout). There are two new tests intest_data_call_change.py: an IMS record the modem no longer lists is cleared before the setup's ownership check (it fails without the fix), and a listed IMS bearer keeps its record.versionbumped, and the new version is in the commit subjectCo-Authored-By:orAssisted-by:trailer, never aSigned-off-by:On the phone
Internet bearer set up again,omamobile-sit-databrought the cellular route back, and HTTPS over rmnet0 answered 204.service.pyhas been installed and running since the reboot after that. It hasn't been tested against a fresh drop yet.userdata, weakens the storage guard, or reads registers from userspace (AGENTS.md §1)🤖 Generated with Claude Code