@balta: There's no logging enabled by default, but you could looking at journalctl output after / during crash might reveal something - that is, if you have developer mode enabled.
Could you also try a clean install (uninstall -> delete old situation data in ~/.local/share/harbour-situations2application -> install new version)?
@rob_kouw: Well spotted. I guess something broke as I did some dbus-related refactoring to the latest version. Some other features as conditions are broken as well. Will look into it as soon as possible.
I've now updated v250 plugins, so Ambience condition should work again. Fixed some other plugins as conditions as well.
The app was also updated because of updates to the built-in plugins, but it should not be necessary to update it to get Ambience condition working again. Just visiting Features page should update the plugins. A restart might be required though.
I've been having the problem that the Situations app does not recognize bluetooth connections anymore. It is possible to scan for devices but when using a found device as activation condition for a situation, the situation just never gets triggered (only when I switch from = device to != device but well...).
Is this a known problem? I skimmed some pages of this thread but didn't immediately find something related. Also, I cannot pinpoint when it started to not work but I know it did before.
What I tried is removing and reinstalling the bluetooth pro feature but this didn't change anything. The newest version also did not help. I have not yet tried removing the entire application and all situations.
I wonder if that situationreboot had something to do with the increased powerconsumption. That is, it may have been conflicting with the Sonar autostart implementation somehow(?).
Have you noticed the same increase after reinstalling & rebooting just Situations & Sonar?
Looks like the conflicting app was the reason for the increased power draw, with clean reinstall I was able to get back the previous level of consumption. And Situations itself also works just fine, no issues with it. Thanks for the good work!
I guess you mean it does not work as an action? How about as a condition? Any chance of you or someone else finding out what dbus command would work on Xperia?
Is the calendar event detected at all? Also, please note that the keyword is case sensitive.
I guess you mean it does not work as an action? How about as a condition? Any chance of you or someone else finding out what dbus command would work on Xperia?
Br,
Heikki
The calendar event isn't detected at all, with the correct case.
The calendar event isn't detected at all, with the correct case.
I mean to ask if the calendar event is detected at all - that is, without any keyword. Also, on what field is your keyword that is supposed to be detected?
