tag:blogger.com,1999:blog-6112936277054198647.post1758244242413277904..comments2024-03-12T00:42:06.642+10:00Comments on Who-T: pointer acceleration in libinput - building a DPI database for micePeter Huttererhttp://www.blogger.com/profile/17204066043271384535noreply@blogger.comBlogger31125tag:blogger.com,1999:blog-6112936277054198647.post-31310943004610593092018-06-07T02:18:15.475+10:002018-06-07T02:18:15.475+10:00Who use this gaming mouse for World of warcraft? I...Who use <a href="https://gadgets-reviews.com/review/118-best-gaming-mice.html" rel="nofollow">this</a> gaming mouse for World of warcraft? It is good or not?bestblogeritsmehttps://www.blogger.com/profile/17578945905488948807noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-38269599755208242132015-08-26T11:42:59.128+10:002015-08-26T11:42:59.128+10:00Most gaming mice are programmable, i.e. their DPI ...Most gaming mice are programmable, i.e. their DPI sensitivity settings can be changed. So for those, this database might do more harm than good as far as I understand it...Anonymoushttps://www.blogger.com/profile/02851776863218145456noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-52993194574506413042015-05-11T21:27:11.403+10:002015-05-11T21:27:11.403+10:00I'm trying to add an entry for the Apple Magic...I'm trying to add an entry for the Apple MagicMouse. I run the mouse-dpi-tool and at the end it gives me <br /><br />mouse:bluetooth:v05acp030d:name:Johns-Mouse:<br /> MOUSE_DPI=1600@1000<br /><br />I've tried adding that as a rule, with or without the name, as obviously a more generic entry shouldn't contain it. But no matter it doesn't apply when I call udev trigger. I've tried doing the same to an old usb mouse I had lying around, and it works there. Not sure what I'm doing wrong here, so any advice would be appreciated.Anonymoushttps://www.blogger.com/profile/18412504451837952453noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-38286827478596515932015-04-04T06:36:06.978+10:002015-04-04T06:36:06.978+10:00@Peter
Couldn't find out how to assign the bug...@Peter<br />Couldn't find out how to assign the bug to you. The bug and a patch are here:<br /><br />https://bugs.freedesktop.org/show_bug.cgi?id=89743<br /><br />Thank you<br />Blaž Tomažičhttps://www.blogger.com/profile/11507195585430657746noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-10106706162750395032015-01-22T13:26:47.981+10:002015-01-22T13:26:47.981+10:00lecbee: check with the HW manufacturer first if th...lecbee: check with the HW manufacturer first if they have an advertised rating. Also test on multiple surfaces, not all provide the best scanning conditions. <br /><br />Same with the frequency, many mice have dynamic frequency scaling so use the highest one you can find.Peter Huttererhttps://www.blogger.com/profile/17204066043271384535noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-35983769748043757642015-01-22T05:52:31.036+10:002015-01-22T05:52:31.036+10:00What to report if I don't get an exact value, ...What to report if I don't get an exact value, like 882 DPI or so ?<br />Also, with the same mouse, sometimes mouse-dpi-tools is in 125 Hz and other time in 142 Hz.lecbeehttps://www.blogger.com/profile/06310819327958315479noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-71770208892218475482015-01-20T17:01:04.025+10:002015-01-20T17:01:04.025+10:00ecloud: all manufacturers advertise as DPI. The ef...ecloud: all manufacturers advertise as DPI. The effort of going against that is not worth the gain.Peter Huttererhttps://www.blogger.com/profile/17204066043271384535noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-26382435522442578132015-01-20T16:53:07.635+10:002015-01-20T16:53:07.635+10:00Would you please consider using modern metric unit...Would you please consider using modern metric units instead of inches? I think a pitch would make more sense too, so the database should specify how many millimeters per mickey instead of how many mickeys per inch.ecloudhttps://www.blogger.com/profile/18144606868112867645noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-83992925433713335502015-01-11T11:02:36.556+10:002015-01-11T11:02:36.556+10:00Jacek: yeah, check with evtest or evemu-describe, ...Jacek: yeah, check with evtest or evemu-describe, grep for Resolution. if you think it's off, best to file a bugPeter Huttererhttps://www.blogger.com/profile/17204066043271384535noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-22195180322895430412015-01-10T22:45:16.935+10:002015-01-10T22:45:16.935+10:00I thought that it also needs the resolution info s...I thought that it also needs the resolution info since two finger scrolling is overly sensitive under libinput. Maybe firmware reports wrong info. Is there any way to query the data?Anonymoushttps://www.blogger.com/profile/03497109875790098559noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-84089555708230603592015-01-10T22:39:31.804+10:002015-01-10T22:39:31.804+10:00Jacek: that's a touchpad, not a mouse. The too...Jacek: that's a touchpad, not a mouse. The tool only works on relative devices, touchpads usually supply us with the information through the firmware anyway.Peter Huttererhttps://www.blogger.com/profile/17204066043271384535noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-16954383390828953512015-01-10T22:25:49.008+10:002015-01-10T22:25:49.008+10:00The mouse-dpi-tool always reports zero units for m...The mouse-dpi-tool always reports zero units for me. Running as root, under Xorg and VT, fedora libevdev-devel package and compiled from source. Always the same results.<br /><br /># mouse-dpi-tool /dev/input/event6 <br />Mouse AlpsPS/2 ALPS DualPoint TouchPad on /dev/input/event6<br />Move the device along the x-axis.<br />Pause 3 seconds before movement to reset, Ctrl+C to exit.<br />Covered distance in device units: 0 at frequency 142.9Hz \^C<br />Estimated sampling frequency: 142Hz<br />To calculate resolution, measure physical distance covered<br />and look up the matching resolution in the table below<br /> 0mm 0.00in 400dpi<br /> 0mm 0.00in 600dpi<br /> 0mm 0.00in 800dpi<br /> 0mm 0.00in 1000dpi<br /> 0mm 0.00in 1200dpi<br /> 0mm 0.00in 1400dpi<br /> 0mm 0.00in 1600dpi<br /> 0mm 0.00in 1800dpi<br /> 0mm 0.00in 2000dpi<br /> 0mm 0.00in 2200dpi<br /> 0mm 0.00in 2400dpi<br /><br />Entry for hwdb match (replace XXX with the resolution in DPI):<br />mouse:unknown bus type:v0002p0008:name:AlpsPS/2 ALPS DualPoint TouchPad:<br /> MOUSE_DPI=XXX@142Anonymoushttps://www.blogger.com/profile/03497109875790098559noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-31939186477020814402014-12-24T21:54:52.680+10:002014-12-24T21:54:52.680+10:00lecbee: you need to measure the distance covered b...lecbee: you need to measure the distance covered by the mouse on the table, not on the screen. <br /><br />say you move 5 inches, find the line that says 5in in the second column and the third value is your DPI. You don't need to calculate anything at all.<br /><br />The first number is mm, second in inches, but they're the same value (US vs rest of the world). if you measure in inches, ignore the first column.<br /><br />If you can't find a matching DPI value, simply divide the units counted by the number of inches you moved and that's it.Peter Huttererhttps://www.blogger.com/profile/17204066043271384535noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-7292710048348415152014-12-24T17:58:34.584+10:002014-12-24T17:58:34.584+10:00@Peter
Could you explain me how the measurement is...@Peter<br />Could you explain me how the measurement is done.<br />As far as I understand, I have to move the mouse, measure the distance on my screen (in centimeters), divide it by the "Covered distance in device units" and match that number with the second columns.<br /><br />What the first column, stands for ?<br />What if the number obtained doesn't match exactly with a number in the second column ?lecbeehttps://www.blogger.com/profile/06310819327958315479noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-80091241086606487902014-12-21T09:45:09.960+10:002014-12-21T09:45:09.960+10:00Peter Hutterer: Yeah, I use Fedora. It would be a ...Peter Hutterer: Yeah, I use Fedora. It would be a good idea to mention the fact that mouse-dpi-tool is a part of libevdev-utils in the blog post itself. That simplifies things a lot for people not familiar with this area.kparalhttps://www.blogger.com/profile/17071376065944998832noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-60322527611380453182014-12-13T16:35:13.053+10:002014-12-13T16:35:13.053+10:00Unfortunately, the amount of effort to make this a...Unfortunately, the amount of effort to make this automatic and useful for everyone is well beyond the time I have available.Peter Huttererhttps://www.blogger.com/profile/17204066043271384535noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-49301156538840454752014-12-13T14:10:18.121+10:002014-12-13T14:10:18.121+10:00This is a great step in the right direction. It re...This is a great step in the right direction. It really lends itself to trying to set the mouse to the highest DPI by default (someday), and then normalizing the pointer speed/acceleration to adjust for the increased DPI. The increased precision from having a higher DPI makes a noticeable difference for users that lower or disable acceleration.<br /><br />Have you considered fully automating the submission process? The database would probably grow much more quickly if users can submit information without having to file a bug.Unknownhttps://www.blogger.com/profile/12953483584900676222noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-76372564293792027662014-12-13T08:28:34.610+10:002014-12-13T08:28:34.610+10:00kparal: it's already part of the libevdev-util...kparal: it's already part of the libevdev-utils package in Fedora 21 and rawhide. Please get your distribution to ship it (I suspect they will anyway once the update to libevdev 1.3.2)Peter Huttererhttps://www.blogger.com/profile/17204066043271384535noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-47864804123655588962014-12-12T23:49:48.719+10:002014-12-12T23:49:48.719+10:00Peter: If we want to gather a reasonable mouse pro...Peter: If we want to gather a reasonable mouse properties database, that detection tool needs to be available pre-compiled. Most people don't know how to compile it or are too lazy to do it (myself included), but would happily provide the data if the tool could easily be downloaded and run (either standalone or as a part of some RPM package). Do you consider providing that? Thanks.kparalhttps://www.blogger.com/profile/17071376065944998832noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-45858847902421993822014-12-08T10:49:17.482+10:002014-12-08T10:49:17.482+10:00djc: sorry got the kernel versions wrong: it's...djc: sorry got the kernel versions wrong: it's fixed in 3.19, not 3.18, so we'll need double entries for all these devices (with the wireless PID in the name and the fixed one for 3.19)Peter Huttererhttps://www.blogger.com/profile/17204066043271384535noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-59657218090375422112014-12-07T09:57:02.112+10:002014-12-07T09:57:02.112+10:00Karl: from the post "And to do that we need a...Karl: from the post "And to do that we need a database, which will be provided by udev as of systemd 218 (unreleased at the time of writing). "<br /><br />Florian: on switchable mice the default resolution must be marked, that's the one libinput picks and normalizes to 1000dpi. because we can't detect dpi changes at runtime, all other resolutions will be relatively faster or slower than that default one. That default one will now have acceleration applied to properly. But given that the default is likely to be around 1000dpi I doubt you'll see any changes anyway :)Peter Huttererhttps://www.blogger.com/profile/17204066043271384535noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-70185977464937703132014-12-07T08:37:14.662+10:002014-12-07T08:37:14.662+10:00@Peter: I've got one of those switchable gamin...@Peter: I've got one of those switchable gaming mice, and DPI switching works just fine since I got it over a year ago - so what would improve when I submit the measurements to udev hwdb? Is it only about changing the acceleration, too?Anonymoushttps://www.blogger.com/profile/06899565334694533440noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-9740853702917775282014-12-06T21:50:55.781+10:002014-12-06T21:50:55.781+10:00@Peter
I'm using systemd 217 on Arch Linux, wh...@Peter<br />I'm using systemd 217 on Arch Linux, which I belive is the latest stable version. Do I need the development version?Karlhttps://www.blogger.com/profile/02301459609408102764noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-78246357352938330542014-12-06T10:34:31.044+10:002014-12-06T10:34:31.044+10:00djc: I forgot to mention this: that's going to...djc: I forgot to mention this: that's going to be fixed in 3.18 when it will be reliable. I'll amend that asapPeter Huttererhttps://www.blogger.com/profile/17204066043271384535noreply@blogger.comtag:blogger.com,1999:blog-6112936277054198647.post-28120459381888841652014-12-06T10:04:11.040+10:002014-12-06T10:04:11.040+10:00I used the mouse-dpi-tool on my mouse, which is a ...I used the mouse-dpi-tool on my mouse, which is a wireless Logitech M705 with a "unifying receiver" that supports many different Logitech devices. The rule it produces looks like this:<br /><br />mouse:usb:v046dpc52b:name:Logitech Unifying Device. Wireless PID:101b:<br /><br />I'm guessing the vid/pid in this rule is for the unifying receiver itself though -- so this rule will be useless, because someone can have the same unifying receiver with a different mouse attached.<br /><br />I wonder if there is any way udev can match the specific mouse attached to the receiver?Anonymousnoreply@blogger.com