Thanks rob_kouw & P@t,

Could you also try running this in terminal:
dbus-send --system --print-reply --dest=org.ofono /ril_0 org.ofono.NetworkMonitor.GetServingCellInformation

Br,
Heikki

Of course!

method return time=1576824989.094044 sender=:1.9 -> destination=:1.3320 serial=298530 reply_serial=2
array [
dict entry(
string "Technology"
variant string "lte"
)
dict entry(
string "MobileCountryCode"
variant string "204"
)
dict entry(
string "MobileNetworkCode"
variant string "04"
)
dict entry(
string "CellId"
variant uint32 26309378
)
dict entry(
string "EARFCN"
variant uint16 6300
)
dict entry(
string "Strength"
variant byte 14
)
dict entry(
string "ReferenceSignalReceivedQuality"
variant byte 113
)
dict entry(
string "ReferenceSignalReceivedPower"
variant byte 9
)
]

Perfect, so that's the "updated" way to get cell id. That should be easily done even blindly, but how to get update notifications for this cell information is still a bit of a mystery to me.

Br,
Heikki

So, one last(?) beta-update for 2019.

New beta-version of Situations is available here:
https://github.com/pastillilabs/pack...leases/tag/258

Contains:
- Lots of small refactoring that hopefully doesn't break anything, but as always something could have slipped in
- New SMS send feature
- Initial attempt at fixing network cells condition

Network cell condition should now at least be able to read current network cell correctly, but whether Situations gets notified for cell changes at all or partially or not at all is the big question. Feedback is welcome

Updated Sonar (for the SMS feature) is embedded in the Situations packages and also available as a separate installation here:
https://github.com/pastillilabs/sona...ases/tag/0.0.5

Br,
Heikki

Great! I managed to record two cells from my home. Keep you posted.

I did not have much time to test but it seems that when you start activating this condition, you get 2 cells. But not clear where they come from ? and no additional cell could be recorded apparently.

edit: it does not seem to work as the condition (with the initial two cells) is always on, even when far from the place where I did record cells

Found a small typo causing the "two cells" issue. But otherwise, to be able to get the cell updates working, I suppose I need to finally get my hands on something newer than Jolla 1 that has the new interface enabled. Might take some time though :/

Br,
Heikki

Hep,

I just updated the 258 packages with a blind implementation for detecting cell changes. @rob_kouw & @P@t: Could you please test if it works any better?

https://github.com/pastillilabs/pack...leases/tag/258

Br,
Heikki

On XA2 I have managed to erase the old 2 cells, and record 1 new cell.

thanks @hhaveri
I installed the latest version and so far I notice:
- I could not erase registered cells and had to throw the whole situation and start again (not a big deal)
- I have not anymore the two-cells bug but I started with one cell while I thought it should be from zero
- with flight mode on, the situation was still on
- the situation seems to react as expected when moving but I will test more during the day

edit: I can add that:
- enabling/disabling mobile data does not seem to work; it could be related to the fact that there is something special about having 2 sim slots.