We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 1497

Summary: SDL opens linear accelerometer for a joypad
Product: SDL Reporter: Ozkan Sezer <sezeroz>
Component: joystickAssignee: Sam Lantinga <slouken>
Status: RESOLVED ENDOFLIFE QA Contact: Sam Lantinga <slouken>
Severity: normal    
Priority: P2 CC: gabomdq
Version: 1.2.15   
Hardware: x86_64   
OS: Linux   

Description Ozkan Sezer 2012-05-15 01:44:27 UTC 
This I noticed on an HP laptop (HP Pavilion dv5-1005et) running fedora16/x86_64
with uhexen2:

joystick #0: "ST LIS3LV02DL Accelerometer"
 3 axes, 0 buttons, 0 balls, 0 hats

... which results in spinning motion in the game because the device opened is
not a joystick, but an accelerometer.  The relevant portion of my dmesg output:

 hp_accel: hardware type HPDV5_A found
 lis3lv02d: 8 bits sensor found
 input: ST LIS3LV02DL Accelerometer as /devices/platform/lis3lv02d/input/input8

Not limiting the device search to /dev[/input]/js* might have its merits, but
this is something I didn't expect running into.
Comment 1 Ozkan Sezer 2012-05-15 02:04:11 UTC 
And to my surprise, the thing is actually at /dev/input/js0. Ugh.. How can one
workaround this thing?
Comment 2 Sam Lantinga 2013-11-11 01:50:52 UTC 
What are the axes that are found?  If there are special accelerometer axes that the kernel is reporting we may be able to do something with this.
Comment 3 Gabriel Jacobo 2013-11-11 13:21:21 UTC 
I bet this is fixed with udev (some magical udev rule/incantation to prevent the accelerometer from being listed as a joystick).
Comment 4 Ozkan Sezer 2013-11-21 09:52:17 UTC 
(In reply to Sam Lantinga from comment #2)
> What are the axes that are found?  If there are special accelerometer axes
> that the kernel is reporting we may be able to do something with this.

Tell me precisely what information you need so I'll try and provide it.
(some /proc content? an output from some command? ...)
Comment 5 Ryan C. Gordon 2015-08-25 09:38:24 UTC 
Hello, and sorry if you're getting several copies of this message by email, since we are closing many bugs at once here.

We have decided to mark all SDL 1.2-related bugs as RESOLVED ENDOFLIFE, as we don't intend to work on SDL 1.2 any further, but didn't want to mark a large quantity of bugs as RESOLVED WONTFIX, to clearly show what was left unattended to and make it easily searchable.

Our current focus is on SDL 2.0.

If you are still having problems with an ENDOFLIFE bug, your absolute best option is to move your program to SDL2, as it will likely fix the problem by default, and give you access to modern platforms and tons of super-cool new features.

Failing that, we _will_ accept small patches to fix these issues, and put them in revision control, although we do not intend to do any further official 1.2 releases.

Failing that, please feel free to contact me directly by email (icculus@icculus.org) and we'll try to find some way to help you out of your situation.

Thank you,
--ryan.