Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stop initial orientation reporting from triggering flip over gestures #244

Merged
merged 6 commits into from Feb 4, 2015
Merged

Stop initial orientation reporting from triggering flip over gestures #244

merged 6 commits into from Feb 4, 2015

Conversation

spiiroin
Copy link
Contributor

@spiiroin spiiroin commented Feb 3, 2015

No description provided.

In many cases the helpers were created at the module that is primarily
responsive for maintaining the datapipe content and datapipe listeners
do debug logging using the numeric states - which requires effort to
decode.

Move state enum to string helper functions to datapipe.c and list
prototypes in mce.h next to enum type declaration.
If device was face-up the last time orientation sensor was enabled,
sensord can report and mce assume that it is still face-up when the
sensor is powered up the next time. This can make it look like the
device were flipped over during sensor startup, which then silences
incoming call / snoozes alarm  (if device is face-down and proximity
sensor is not blocking display & sensor power up).

Make mce forget orientation sensor state altogether when the sensor
is stopped. And make sensor-gestures plugin wait a bit longer before
accepting face-up immediately after sensor power up.

[mce] Stop initial orientation reporting from triggering flip over gestures. Fixes NEMO#786
@sledges
Copy link

sledges commented Feb 3, 2015

Code style LGTM

@kimmoli
Copy link
Contributor

kimmoli commented Feb 3, 2015

Tested branch spiiroin:nemo786_flipover_gesture and the symptoms described in NEMO#786 are not reproducible.

These state changes are side effects of starting/stopping the use
of orientation sensor and thus do not constitute user activity.
Now that the helpers are available, use them to make debug logging
easier to read.

No functional changes.
Using current display state for evaluating need for orientation
sensor works logically right, but delays sensor ramp up a bit
making it likely that correct orientation is known after display
is already in fully powered up state.

Use target display state instead. This allows sensor ramp up to
start earlier and makes it more likely we have correct orientation
by the time display reaches on state.
Old forgotten fixme spotted.

LPM states are in use now and from sensor use point of view LPM_ON
display state is equal to ON and DIM states.
spiiroin added a commit that referenced this pull request Feb 4, 2015
Stop initial orientation reporting from triggering flip over gestures
@spiiroin spiiroin merged commit b2e9b88 into nemomobile:master Feb 4, 2015
@spiiroin spiiroin deleted the nemo786_flipover_gesture branch February 4, 2015 09:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants