answered
2016-03-16 14:53:55 +0200
The flip to silence is meant to be triggered when:
- There is incoming call
- Display turns on
- Orientation sensor reports face up
- Orientation sensor reports face down
If the device is in the pocket -> proximity sensor should stop dislay from turning on -> (2) does not happen.
If the display is powered off -> orientation sensor should stay powered down -> (3) and (4) do not happen.
So in theory at least flip-to-silence should not mute calls while the phone is in a pocket / standing up. But there have been bugs caused by proximity and orientation sensor hiccups earlier (ref: https://bugs.nemomobile.org/show_bug.cgi?id=786), so ...
@fishegg and others experiencing this issue:
- What sfos version you have in use?
- Have you had snoozed-in-pocket alarms? (uses the the same flipover detection logic as silencing calls)
- Did you hear ringing tone at all / briefly for a second or so / longer than couple of seconds?
- If you heard the ringing tone, was the display already on when taking the phone from pocket?
- Was the call ui still visible? Did it indicate muted/ignored call, or was the call already terminated?
- If you have some way disabled the flip-to-silence, does that make the problem go away?
Also note: Patches are not needed for disabling flip to silence.
From sfos >= 1.1.7.x you can tell mce not to use orientation sensor - which effectively disables the gesture detection too:
mcetool --set-orientation-sensor-mode=disabled
And from sfos >= 2.0.1.x is possible to disable just the flip-to-silence via:
mcetool --set-flipover-gesture-detection=disabled
EDIT:
Also, if you are comfortable with editing system configuration, more verbose journal log might be useful for hunting down the reason for the problem.
As root, edit /lib/systemd/system/mce.service as follows (check EDIT2):
[Service]
Type=notify
-ExecStart=/usr/sbin/mce --systemd
+ExecStart=/usr/sbin/mce --systemd -v
Restart=always
Then, as root, restart mce:
systemctl daemon-reload
systemctl restart mce
Persistent logs are not strictly required, but might make it more likely that logs from the time when call occurred are still available. Instructions at https://together.jolla.com/question/4842/how-to-enable-more-detailed-and-persistent-logs-on-jolla-device/
EDIT2:
I have now received one debug log. In that particular case it looks like flip-to-silence was not causing the problem. However it might be useful to have one step more verbose logs to verify flipover detection during these muting incidents. So preferred mce.service modification is:
-ExecStart=/usr/sbin/mce --systemd
+ExecStart=/usr/sbin/mce --systemd -v -lmodules/sensor-gestures.c:*
Note: The logs can contain personal information such as phone numbers. You might want to scrub those out before sending them in / submitting somewhere.
EDIT3:
Judging by the logs we have available at the moment, it looks like the flip-to-silence feature is not (at least the sole) cause of the auto-ignore in 2 seconds -issues.
We will anyway add a toggle in the settings application to make it easier for users to disable the feature it it is causing problems.
I confirm... It's very annoying.
Luca ( 2016-03-16 09:45:30 +0200 )editAhh that could be the reason why I am never noticing incoming calls while walking...
Alex ( 2016-03-16 10:16:28 +0200 )editThere is a patch available that disables the flip to silent at all - openrepos
elastic ( 2016-03-16 12:00:32 +0200 )editDon't use this patch, there is more proper way to disable this function
mcetool --set-flipover-gesture-detection=disabled
atlochowski ( 2016-03-17 11:25:15 +0200 )editHei,
My twenty cents on it that this is related to this.
LVPVS over.
LVPVS ( 2016-03-17 16:31:51 +0200 )edit