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

Just checked, I am able to record a new cell (as well as remove it) on SFOS 3, but I'm using Xperia X so it might be related to your phone model.

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

I have the same device model and SFOS release and haven't noticed any significant stuttering or lag. After the new UI came Situations was a bit slow on Jolla1 but after switching to Xperia X I can't recall having any performance issues with the UI.

Are other apps performing ok on your device? Even the heavier ones like the browser?

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

Well I don't have here maps installed, because simply need it. Dammit if here maps is mandatory to be installed if I want use location feature.


and next subject, perfomance issue. So I should go terminal and type something jornalctl? Or anyways I should debug this issue, for further investigation.

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

Thanks for your experience, interesting. What comes to the my other applications the are fine, only both browsers, webcat and jolla have some issues about Performance but I think these are just "work in progress" status, because for example qt webkit is outdated. Sometimes Jolla browser crashes but what I read other users it's just normal and can be called "feature".

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

I have the same problem with a XA2 Dual-Sim (H4113).

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

Any chance of flight mode to work?

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

In my experience Situations UI is not heavy on memory (or CPU), but since browsers tend to be heavy on resources makes me think if you by chance have tweaked some settings related to OOM-killer/low-memory-killer or swapping, or have a shortage of RAM? Do you have many apps running all the time? Shortage of RAM is a sure way to cause lags and stuttering. You could use some app like Mem! to verify if that's an issue.

I'm just guessing here, though. And yeah, I've had both browsers crash many times :( Mostly that's been for lack of system resources on sites they handle badly.

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

You can ask Jolla to (re)open an API for it. Or tweak your own solution: run Situations as root or use Situations to launch some flight mode helper app / script with root access instead.

Br,
Heikki

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

Hep,

There's a new (beta) version of the app available here: https://github.com/pastillilabs/pack...leases/tag/186

Some change log:
- Changed condition & action selection layout
- Improved runtime state handling over server restarts
- Fixed Mobile Data, Airplane Mode & Internet Sharing features when set as conditions
- Sync with all other internal implementation improvements done to the Android version

Having not used Sailfish actively for a long time, I noticed that increasing number of features seem to work only when the app is run as root. Which is kind of disappointing, as Android - while having the same frustrating direction - is now doing much better in that regard :(

Br,
Heikki

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

Hep,

New beta (3.1.192) available here: https://github.com/pastillilabs/pack...leases/tag/192

It is also already in the store review process.

Contains only fixes & improvements to existing functionality:
- Improved / fixed in-call handling
- Improveed / fixed runtime state handling over reboot & service restarts
- Fixed Launch & Close plugins having multiple entries

Well... in-call handling is kind of new functionality. It means that some actions will be delayed until an active or incoming call has ended. There was application logic for it in place already from the Symbian times but it never got platform specific backend implementation (for Android & Sailfish) done until now.

There is now also an option to re-activate actions on background service restart. On Android this is done only when the service is autostarted on boot. By default, background service restarts just continue from where the execution was left.

On Sailfish this means that if you are using some autostart mechanism, you should probably have a "reset" parameter added to the service startup command if you want re-activation to happen (for example launch apps with an ongoing situation in device boot).

Launching the service from the app UI currently does not have the "reset" option. Not sure if it should or not. But it might get added in the next update.

Br,
Heikki Haveri
Pastilli Labs