Need Help: HowTo start to programm a first app: "Pause" (break or "face down") for Xperia 10 III

[pherjung]

• recognize, that the phone is put “face down” on a surface

There’s the Proximity Sensor

• confirm that with 2 short vibration alarms

There is surely a command to apply this. So, still possible with Situations.

• detect: mobile data enabled ? → save the actual setting, disable mobile data

I found this option too

• detect: wifi enabled ? → save the actual setting, disable wifi

Available too

• detect: do not disturb-mode enabled ? → save the actual setting, enable do not disturb

Present

• detect: Bluetooth enabled ? → save the actual setting, disable Bluetooth (if configured so by user for e.g. in checkboxes)

Available

So if there is a missing function, better contribute to Situations instead of developing a new app.

[Speedy-10]

Ok, I tried only some simple things with Situations, but wasn’t sure, that everything would be available. First I try harder with Situations before starting a new app.
@Dima2387 : Thanks for the links, SDK is installing.

[Speedy-10]

Hi perjung,
thanks for your hints. I discoverd more items in the menu “functions”.
Now I’ve testet the following, see screenshot.
First problems:

• Still looking at the opened app Situation: I got the message “current Situation: Pause”
  → this “Pause”-Situation should only be activated, if I lay the phone “face down” on a table or so.
  → Although it was shown activated, the “what’s” (german: was) are not done: no vibration discovered, no don’t disturb activated, no wifi deactivated
• In the menu > “i”, I tap on “Sonar install”, nothing happens (external source are activated)
  
  

[pawel.spoon]

depending on the version of sfos you are running you might run into sailjail issues with situations.
there is a thread about it, basically it says you should modify .desktop file of situations to exclude it and then people claim situation would work as expected.

[pherjung]

Instead of Aus, try with Started. It doesn’t sound logic, but you want to start something when the proximity sensor is seeing something.

[Speedy-10]

Hi, I just managed to get most of the wanted behaviour:
Wifi is disabled, I can see it on the router. The other items reduce battery discharge, too.

One thing I’m missing at the moment:
I’d like to have a short confirmation, that the Situation “Pause” is activated. Does anyone know a direct console-command for: either a short vibration or a sound (SMS, e-mail, …)?

[pherjung]

It’s possible to enable notifications. Situations->Settings->Notifications.

[Speedy-10]

I just realized that. The last thing I added was the “energy saving mode”. Now if I turn the phone “face down”, starting the energy saving mode confirms with a sound, nice.
(EDIT: Done with sailfish 4.0.0.64, sonar had to be installed from github.)

[Speedy-10]

I’m sorry to ask again: Today I deleted one of the “default situations” (at home). After a reboot of the Phone, I got an error. No tap on either button did anything.

I deleted Situations from the phone and reinstalled it → got the same failure.
Does someone has experience with such a failure?

[Speedy-10]

Does someone know where the config-files of Situations are? Perhaps I could delete them all by ssh and reinstall it again.

[Speedy-10]

With the help of Heikki Haveri, Pastilli Labs, I could reinstall it completly:

devel-su
[root@Xperia10III defaultuser]# pkcon remove situations
[root@Xperia10III defaultuser]# rm -r .local/share/harbour-situations2application/
rm: descend into directory '.local/share/harbour-situations2application'? y
rm: remove directory '.local/share/harbour-situations2application'? y
[root@Xperia10III defaultuser]# pkcon remove situations-sonar

Restart the phone.
Reinstall ‘Situations’ and ’ situations-sonar-0.0.9-9.aarch64.rpm’ (from github).

This time I deactivated the default situations, before I organized my personal “Pause”.

[Speedy-10]

New try with 4.4.0.72:

1. installation of situations (+add function: “display”)
2. installation situations-sonar-0.0.9-9.aarch64.rpm (from github)
3. configuration of Situation “display down” as desired, see picture:
   
   

Aim:
a) Save battery:
While the phone is worn in the trousers or laid down on the display → WiFi should be disabled.
b) Get notifications only when I actively check the phone.

Observations:

1. First morning, the WiFi was disabled correctly, as seen on the router or by the messages of Situations.
2. Problem: Some hours later, Situations disabled WiFi, although the display was “on”, when I came near to the proximity sensor (e.g. when tapping on a top corner in an app).

To solve this, I restarted the phone once. Now I got the same (white failure screen as mentioned on 5th of july)

If Situations works like configured, it would spare a certain amount of battery.
Can someone confirm this behaviour? How could I get Situations to work properly?

[phklrz]

Hello,
it seems that “situations” app is not compatible with Sailjail. Do you start it from the launcher or from a terminal?
You can try to start it from the terminal (thus avoiding Sailjail restrictions) and see if the behaviour is the same.

[Speedy-10]

How can I start “situations” from the terminal?
If I tab “sit” in terminal, I got only “situations-sonar”.

[phklrz]

harbour-situations2application

[Speedy-10]

Ok, that’s my output now:

[defaultuser@Xperia10III ~]$ harbour-situations2application
[D] unknown:0 - Using Wayland-EGL
library “libGLESv2_adreno.so” not found
library “eglSubDriverAndroid.so” not found
library “vendor.qti.qspmhal@1.0.so” not found
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei oder Verzeichnis nicht gefunden
Created symlink /home/defaultuser/.config/systemd/user/user-session.target.wants/harbour-situations2application.service → /usr/lib/systemd/user/harbour-situations2application.service.
[W] unknown:8 - qrc:/qml/application/Background.qml:8:37: Unable to assign [undefined] to bool

[Speedy-10]

Thank you for the hint. At the moment, Situations works well: The proximity sensor shows no malfunction and the app didn’t hang up.
I’ll observe some days.
Perhaps I’ll start Situations after a reboot per terminal per hand, using “arrow up” for recent commands; or I could add an entry in crontab (which I have not tested yet).

[atlochowski]

Why not to use systemd timers?

[Speedy-10]

Further problems:

• Situations worked for 2 days as desired.
• Today -again- the sensor reacted, although the display was “on” → the display /WiFi is deactivated for a short moment each time, I come near the sensor.
• I uninstalled the app graphically.
• Nevertheless, the deactivation still went on, i.e. some task was still running.
• For documentation, I made a picture of the output of “top”
• Now, several hours later, the deactivation stopped (I didn’t anything more).

FYI, I didn’t reboot the phone the last days, nor did I install something else.
In the end it doesn’t work for me and I can’t understand, what’s the cause. I’m disappointed, because I thought it would be a good approach to save some battery power over the day.

[phklrz]

Can you check:

systemctl --user status harbour-situations2application

and

devel-su systemctl status situations-sonar