Ticket #2362 (new defect)

Opened 3 years ago

Last modified 3 years ago

2.6.32.20 kernel from SHR-U has angle offset in the Accelerometer's output

Reported by: GarthPS Owned by: openmoko-kernel
Priority: highest Milestone:
Component: kernel Version:
Severity: normal Keywords: kernel Accelerometer
Cc: Blocked By:
Blocking: Estimated Completion (week):
HasPatchForReview: no PatchReviewResult:
Reproducible: always

Description

Best showcase is playing to mokomaze:
it give you the feeling that either you are drunk or your are very very bad at this game. In fact it is just becausethere is an misunderstanding of the output of Accelerometers. I f you want to go straight in a directection you have to think to tilt your moko in (it looks like) 45° to the left of that direction to do waht you realy want to do.

Change History

comment:1 Changed 3 years ago by pwerken

Are you (/ your apps) using the correct input device?

On the [ttp://wiki.openmoko.org/wiki/Accelerometer_data_retrieval wiki page] it is noted that the devices moved from /dev/input2&3 to /dev/input3&4 when using a 2.6.34 kernel.

comment:2 Changed 3 years ago by lindi

Is there any sanity in trying to hardcode such numbers? Why not just use /dev/accelerometer-top and /dev/accelerometer-bottom in userland code?

comment:3 Changed 3 years ago by pwerken

Hardcoding such things is always a Bad Idea.
Userland can already look in /sys/class/input/inputX to find the right device
(in this case "lis302-2 (bottom)"). Or alternatively use it to generate a list of
found/compatible devices for the user to select from.

Note: See TracTickets for help on using tickets.