Situations App on 4.4

[Steve_Everett]

Does this no longer work properly because of sandboxing?

I had it setup so that overnight it turned off wifi and mobile data (to save battery), dimmed the screen and enabled silent mode.

The Situations app loads and appears to select the right situation according to the time of day (I get a notification of this), but none of the above actions ever happen, so it doesn’t actually now do anything useful.

[phklrz]

Yes it is a sandboxing problem.
I launch SItuation app from ther terminal and it works then.

[JacekJagosz]

Also auto start situations from openrepos works flawlessly for me, nothing changed with the update. I really recommend it!

[monkeyisland]

Hi there i got problem with ambiences after clicking on the button no ambiences are to choose

So i think it is the problem of sandboxing, also switching WIFI OFF / ON not working.
The application says that sonar is not installed. But it is.

[phklrz]

Just launch situations app from the terminal.

[monkeyisland]

yes that does the trick but sonar dont wont regocgnize from the app

[nephros]

Hi,

I had a little Email conversation with the developer, and wanted to share some of the information about this here:

@Pastilli Labs

Situations is currently undergoing a very large refactoring which was largely triggered by the sandboxing changes of Sailfish OS - but also from the need to better facilitate more advanced feature development. And hopefully also to enable opensourcing more of the technology. So there is active work ongoing, but due to the massive amount of things to be done it will still be probably months before something comes out of it in public.

I hope the current version will be sufficient until then, although I’m painfully aware of the shortcomings with the latest OS versions.

Following up on the email, I asked how the community could help:

@Pastilli Labs

@nephros

Is there anything I or the community can do to help you with your efforts?

I haven’t fully grasped in detail what kind of changes sandboxing imposes on current SFOS features of the application - i.e. mostly what functionality in current “design” needs to be delegated to Sonar.
Since Sonar is already “open source”, it is currently the best place to offer concrete help. I.e. to make relevant functionality available there. The problem is, I don’t have much capacity to coordinate anything or work on the application side yet.
And perhaps the whole Sonar approach still might need some rethinking. In the current rather quickly sketched up form, it has some limitations that I’d like to get rid of at some point.

@nephros

Do you have any advice on how to debug (or at least log) issues the applications (UI, daemon, sonar) may be seeing? I think if there is a way the community could at least document areas that are not working well.

Proper logging so far has been on temporary need basis only. Perhaps the best help would be to just collect a list of features that are no more working after sandboxing.

@nephros

Would further donations change anything on the time scale you describe?

Not really. Aside from the motivational boost, the current level of
donations / sales on Android is only sufficient to somewhat cover the associated costs of developing & maintaining the app. Otherwise, in current state, it is purely a hobby / personal competence development project.

Oh well, back to the refactoring work…

---

In order to collect such information, I have created this wiki post:

[Wiki] Situations app issues

Following up on the information shared here (please read), this post is a Wiki intended to collect shortcomings and issues with the current release of the popular Situations application. Please keep the contents of this to bugs, issues, and regressions, and not feature requests or questions. Installation likely due to sandboxing, the app can not find its configuration (as it’s in the old path) and starts up empty/default config. Disabling Sandboxing in the .desktop file fixes this. Running…