Re: Situations app - bugs, questions, answers, help etc..
 

Thanks for the clarification. :)

Re: Situations app - bugs, questions, answers, help etc..
 

Ok, it's anyway good to hear that the need has been recognised and there's some hope to have the feature some day :)

Well, I'll try these new tricks I've today learned here, if they work for me it'll certainly increase the value of the app for me. I'll also try to figure out if there is a pattern with the intermittent failures to switch situations which are based on cell IDs. Since the cells the phone is using somewhat vary, sometimes it's just that there's a new cell ID and it gets fixed by briefly turning on recording, but sometimes the only way is to manually turn on or off the cell ID based situation. Anything that I could try to check when I notice such a failure, except checking if the background process is still running?

Re: Situations app - bugs, questions, answers, help etc..
 

Technically the cell id recognition of the app should be quite reliable and stable. But the problem is indeed the possible variation of cells the phone is connected to over time.

I have myself recorded well over 10 cells at my home. This also covers quite a large physical area, so it can get quite inaccurate as a positioning method at least in some places.

What can be done to get the best coverage in short time is to leave the recording on and go to system settings and switch between 2, 3 & 4G manually, wait long enough and possibly also make some calls.

Re: Situations app - bugs, questions, answers, help etc..
 

My configuration is as follows:
1. At home: if cell tower found - turn on wifi, turn off bluetooth, mobile data, profile normal
2. At work: if cell tower found - turn off wifi and bluethooth, turn on mobile data, profile silent
3. Driving: if not at home or work and my car bluetooth found

Only problem is my phone is not evaluating when locked. As soon as I double tap, it changes the situation profile to the correct one.

I am using v2.4.48, for openrepos.

Any ideas?

Re: Situations app - bugs, questions, answers, help etc..
 

This is sometimes actually pretty hard - to import a solution to another mindset... Mindsets are not something that can be given in tutorials :)

This explains what I've been a bit wondering (why the settings change when Situations exits), thanks for clearing that out. Yes, no need for explicit baseline situation... Although this does make me wonder what happens if the phone is restarted while Situations is running - will the current settings based on whatever situations were active become the new "baseline"? Or are the settings done by Situations somehow marked as temporary? (I don't really know what kind of things Sailfish has under the hood)

Re: Situations app - bugs, questions, answers, help etc..
 

I haven't noticed such problems, but then again I haven't probably tested all possible scenarios with all conditions - like when phone is locked. So I'll check if I can find out something...

Re: Situations app - bugs, questions, answers, help etc..
 

Situations remembers the baseline over restarts itself, so it should work like there was no restart (although, as a side note, there was a bug in this mechanism which is still visible on the Android version).

But of course currently there is no autostart built in the Sailfish application because of the Jolla Store rules which makes this a bit incomplete feature on Jolla...

Re: Situations app - bugs, questions, answers, help etc..
 

If cell ID recognition is solid, could there be something funky in recording of cell IDs? The reason I'm asking is that yesterday at the office when I created a new situation to try the solution posted by @nodevel, I started cell ID recording but it acted as if no cells were available (count stayed at zero). This would explain why in some cases when a situation switch has failed no new cells have been found when I restart recording. Either that, or the cell ID recognition (or the platform API, perhaps?) has a hidden bug somewhere :)

It's true that it can be quite inaccurate, and especially near the borders of the area it's very volatile. The dampening I mentioned helps with that, but in my experience it also helps a bit if you have a trace log of the cell IDs with timestamps from where you can assign the cells to different areas/locations and immediately see when the coverage at the location is stable enough (Llama has such a log). It also makes it easy to assign cells to areas afterwards, as a complement to recording. With dampening it would not matter if the phone occasionally switched to a cell further away for a couple of minutes, and so it might be possible to keep the effective physical area more compact.

Re: Situations app - bugs, questions, answers, help etc..
 

Bugs are always possible ;) But recognizing 0 cells sounds strange if you did have network coverage. Under the hood cell condition is using org.ofono interface to read and get notified of cell changes. It should be quite solid, but who knows...

Yes, the current network cell features & UI in Situations is quite limited. It's mainly designed for ease of implementation and use, and more advanced features have been on the backlog already for quite some time. Hopefully I get some time to implement them at some point.

Re: Situations app - bugs, questions, answers, help etc..
 

Today tried again, seems the problem is gone, so i dont know what really happened here :)