maemo.org Bugzilla – Bug 5911
Shaking device switches between landscape and portrait modes
Last modified: 2010-01-15 17:37:01 UTC
You need to
before you can comment on or make changes to this bug.
STEPS TO REPRODUCE THE PROBLEM:
1. Open the telephone application (Applications > Telephone)
2. Set the rotation to Automatic (Menu > Rotation Settings > Screen
Orientation > Automatic) (translated from French so may not be exact)
3. Shake the phone horizontally (from left to right)
The screen orientation shouldn't be so easily confused.
The screen orientation seems to be too sensitive and changes between landscape
and portrait, even though the device actually remains in the same physical
Shaking is an extreme case, but I've noticed that sometimes the orientation is
changed simply by moving the N900 too quickly to one side, say when you're
moving around a bit. (Bug summary could possibly be updated to reflect this
This could possibly be fixed by smoothing over several samplings of the
sensor(s) that determine the device orientation, although this might be to the
detriment of the snappiness of a valid orientation change.
This shaking has actually been causing me to loose phone calls! This shouldn't
happen to end-users buying this phone...
My situation: The phone is ringing, I take it out of my pocket, I try to accept
the call, but the orientation is changing, and I tempted to change the position
again, but the button is disappearing and I'm not in time to answer the phone
So I propose that the orientation is never changed during an incoming call, or
at least make it possible to accept phone calls while the orientation is
This has been fixed in package
which is part of the internal build version
(Note that 2009 is the year and the number after is the week.)
Any public update released with or after this build version will include the
Please verify that the new version fixes the bug by marking this bug report as
VERIFIED after the public update has been released and if you have some time.
The problem reported here should be fixed in the update released today for
public: The Maemo5 update version 2.2009.51-1 (also called "PR1.1" sometimes).
Please leave a comment if the problem is not fixed for you in this update