Reply
Thread Tools
Posts: 51 | Thanked: 41 times | Joined on Feb 2015 @ Mansester, FI
#451
Originally Posted by hhaveri View Post
Have you noticed the same increase after reinstalling & rebooting just Situations & Sonar?
I did that yesterday (with the recent versions), let's see where the consumption average settles this time.
 

The Following User Says Thank You to zagrim For This Useful Post:
Posts: 203 | Thanked: 596 times | Joined on Jan 2015 @ Finland
#452
Thanks for the reports!

@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.

Br,
Heikki
 

The Following 2 Users Say Thank You to hhaveri For This Useful Post:
Posts: 203 | Thanked: 596 times | Joined on Jan 2015 @ Finland
#453
Hi,

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.

No updates to Sonar this time.

Br,
Heikki
 

The Following 3 Users Say Thank You to hhaveri For This Useful Post:
Posts: 203 | Thanked: 596 times | Joined on Jan 2015 @ Finland
#454
3.2.250 is now available also in Jolla Store.

Br,
Heikki
 

The Following 5 Users Say Thank You to hhaveri For This Useful Post:
Posts: 1 | Thanked: 0 times | Joined on Nov 2019
#455
Hi,

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.
 
Posts: 51 | Thanked: 41 times | Joined on Feb 2015 @ Mansester, FI
#456
Originally Posted by hhaveri View Post
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!
 

The Following User Says Thank You to zagrim For This Useful Post:
Posts: 9 | Thanked: 8 times | Joined on Sep 2011
#457
Hi hhaveri,

I'm having a couple issues with the latest release + sonar. I'm on Xperia X with sailfish 3.2.

I've done a fresh reinstall with removing the situations data in between.

1. The calendar situation isn't detecting keyword. I have multiple calendars and selecting only the relevant calendar doesn't help.

2. the wifi toggle situation isn't working.
 
Posts: 203 | Thanked: 596 times | Joined on Jan 2015 @ Finland
#458
Originally Posted by storma View Post
1. The calendar situation isn't detecting keyword. I have multiple calendars and selecting only the relevant calendar doesn't help.
Is the calendar event detected at all? Also, please note that the keyword is case sensitive.

Originally Posted by storma View Post
2. the wifi toggle situation isn't working.
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
 
Posts: 9 | Thanked: 8 times | Joined on Sep 2011
#459
Originally Posted by hhaveri View Post
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.

Wifi as a condition works, just not as an action.

I'll see if I can track down the dbus command.
 
Posts: 203 | Thanked: 596 times | Joined on Jan 2015 @ Finland
#460
Originally Posted by storma View Post
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?

Br,
Heikki
 
Reply

Tags
sailfish os, situations


 
Forum Jump


All times are GMT. The time now is 17:53.