LVPVS | # 361 | 2018-02-01, 10:17 | Report

Hei,


I see.
It's not that I really would need it for anything, I was just curious.

What is this "initial accessibility support"?


Kiitos,

LVPVS over.

fooxl | # 362 | 2018-02-01, 15:44 | Report

The app would be great for me and basically it worked.

I would use it to turn off wifi and start the media player, when the phone (SailfishX) connects to my car audio system via bluetooth.
Unforunately it interrupts the bluetooth audiostream every minute for some seconds. I guess it happens every time the app checks, if it is connected.

LVPVS | # 363 | 2018-02-01, 19:42 | Report

Hei,


Try switching the Bluetooth What to 'No scanning'... It works for me.


LVPVS over.

hhaveri | # 364 | 2018-02-02, 06:20 | Report

Support for accessibility features such as screen readers, voice control, etc. used for example by visually impaired folks. Mainly valid for Android, as I guess Sailfish does not have much accessibility features(?).

Br,
Heikki

LVPVS | # 365 | 2018-02-02, 20:37 | Report

Hei,

Thanks for the clarification.
I don't think sailfish has anything like that at the moment.

Kiitos,
LVPVS over.

fooxl | # 366 | 2018-02-05, 12:36 | Report

How's this done?
I can only switch BT on/off in the "What" section.

hhaveri | # 367 | 2018-02-05, 12:45 | Report

Install 'Bluetooth Pro' condition from Features page. It gives an option to adjust scanning interval.

Br,
Heikki

zagrim | # 368 | 2018-02-10, 09:32 | Report

I've been lately having issues with cell ID based situations. It seems like the application is thinking I'm connected to a cell that belongs to a certain situation even when that's not true. I took the time to rebuild my config today in case it had somehow grown bad along the years, but after copying the correct cell ID arrays in situations.json this still seems to be happening.

Right now the app has one situation (let's call that A) active that is correct for the location I am, and one other (B) that is totally incorrect. I've verified (using SimScout) that the current cell ID does not belong to the situation B. When I deactivate situation B it doesn't get reactivated automatically (which is of course correct), but if I open the situation, the app is showing the cell ID condition as green (valid/matching). What is even more weird is that I have also another situation C with the exact same cells listed in conditions as B, and that situation isn't getting activated. Edit: I realised later that situation C also had a time condition which didn't match now. After removing time condition from C it also got activated. All this while not being connected to any of the cells listed for B or C.

I've also seen this happen also with two incorrect cell ID based situations at the same time (with those two situations having different cells in conditions).

I'm not quite sure when this has started, but it's been going on occasionally maybe some moths now. I'd like to keep using cell based situations as I rely quite much on location in my setup and using phone positioning is too hungry for battery. Any ideas what to do about that?

Edit (later on): After taking the device to another location and getting then back, the issue seemed to go away for now, meaning only the correct situation was activated.

---

Last edited by zagrim; 2018-02-11 at 05:57.

hhaveri | # 369 | 2018-02-11, 13:27 | Report

Thanks for the report, I'll see if I can reproduce the issue or find out any problems by just reading the code. Might take some time, though.

Br,
Heikki

hhaveri | # 370 | 2018-02-12, 09:35 | Report

Hep,

v3.1.156 available here: https://github.com/pastillilabs/packages/releases

- Small UI fixes
- Power consumption optimizations to Bt & WiFi scanning conditions
- Attempt to fix issues with Network Cells condition
- Non-root Airplane Mode support is back

Br,
Heikki