Wireless Logitech V220 mouse stopped going straight

Ok i have this mouse, worked fine for hte past 4 months than LITERALLY out of no where and I mean within seconds of use it went weird. It isn't going in straight ines or directions anymore.
I reinstalled it, reset it did EVERYTHIGN same thing but I take it on a different computer and its working PERFECTLY fine.
If I grab a window and drag it from one end to another, it'll go straight for about 3 inches of the screen before it dips up and down and curves up and down as if something is resisting it from going straight like magnetic resist feel.

Your mouse reciever should have a button to relocate its frequencies to another channel if such a device is causing interference for you.
*******DISCLAIMER********
I am not an employee of BBY in any shape or form. All information presented in my replies or postings is my own opinion. It is up to you , the end user to determine the ultimate validity of any information presented on these forums.

Similar Messages

  • Have Mac OSX 10.5.8; logitech ball mouse stops working in firefox window.

    When I use my trackball on the web, it either freezes (requiring I reboot) or the left click stops responding. The right click works but only to drop down the menu.

    P.S. '''For Mac OS X 10.5 users with an Intel Mac''', the latest version of Firefox that will work is Firefox 16. Link: [https://ftp.mozilla.org/pub/mozilla.org/firefox/releases/16.0.2/mac/en-US/Firefox%2016.0.2.dmg Firefox 16 (US English)]
    Related article: [[Firefox no longer works with Mac OS X 10.5]]

  • Wireless Logitech mouse with Leopard

    I just bought a wireless Logitech optical mouse that uses a usb receiver. Every time I move the mouse when my Macbook Pro is asleep, the computer wakes up. Is there a way to prevent this from happening?
    Thanks

    No. That is normal behavior. If you don't want the movement to wake up the computer, then turn off the mouse before putting the computer to sleep. There should be an on-off switch or button on the bottom of the mouse.

  • Qosmio X500 Bluetooth mouse stops responding

    Hi,
    I have the latest bluetooth stack / drivers installed. (Yes, I downloaded the latest from http://aps2.toshiba-tro.de/bluetooth/index.php?page=download-toshiba) All drivers are always updated to the latest including the wireless drivers as well.
    Problem: About every 20 - 40 minutes my Logitech bluetooth mouse stops responding. The cursor gets stuck and it won't move at all.
    I tried unpairing / pairing the mouse, that helped, but, then again after 1 hour it stuck again. I re-installed the BT stack and that did not help as well.
    The only way I can use my mouse again when stuck is when I click "Disable Bluetooth Function" and then I "Enable Bluetooth function".
    I do this about 10 times a day and you have no idea how annoying it can get.
    I bought a new Logitech Bluetooth mouse (Logitech M555b) and that did not help as well.
    If anyone could help me out here I would deeply appreciate it.
    Thanks,
    Mike

    Thats strange but unfortunately; I dont have right solution for you but just some advices.
    First of all I googled for this Logitech M555b BT mouse and found several threads about the issues with this mouse.
    The connection issue happens with other computers running windows 7 or XP or iOS (Macbook).
    So it seems that this issue is not related to Toshiba BT stack.
    A friend of mine use other BT mouse from Logitech and it works fine all the time using the Bluetooth stack.
    I recommend checking the Logitech forum to get further details:
    http://forums.logitech.com/t5/forums/searchpage/tab/message?q=M555b#message-list

  • Mouse stops, computer freezes. this problem occurs with any mouse: bluetooth, wired, and a spare logitech wired mouse.  iMac 0S10.6.8

    Help! Mouse stops, computer freezes. Restart helps for a while, then mouse doesn't respond. Problem occurs with my 4 "mice" - bluetooth, apple wireless, logitech wired & microsoft wired. Any solutions?

    Problem solved!
    First, the underlying cause MAY have been an unusual circumstance: a smartphone (Galaxy Android) was placed next to the iMac, turned on and with Bluetooth enabled, and left for hours to charge.  Could this proximity have resulted in the Mac getting some strange Bluetooth input?
    Fix:  Using the temporarily-installed mouse and keyboard, I removed the existing Bluetooth keyboard and trackpad entries. (I just removed every Bluetooth device.)  Then I used the standard procedure to re-pair the wireless keyboard and trackpad.
    After removing all Bluetooth devices, I could not get the Mac to detect any Bluetooth devices until I restarted the Mac, at which point device detection and pairing worked flawlessly. 
    My best --and admittedly ignorant, sketchy-- theory:   Some mal-formed event got stuck in the Bluetooth input stream, causing the trackpad up and/or down states to be hyper-sticky.  That event couldn't be cleared without removing the originating device and re-pairing.
    HTH

  • My new mac mini doesn't detect my wireless keyboard and mouse from logitech

    I recently bought the Logitech MK550 wireless keyboard and mouse combo for my late 2014 Mac mini.  Basic functions work, however, when I try to add the keyboard and mouse in the System Preferences it can't find either one.  So right now I have this great big keyboard that I can only use about half it's full functionality and an unassigned button on the mouse.  Any ideas?  Also, I would like to add an apple remote to my mini.  I have one from my old iMac.  Is this possible?

    Try resetting the SMC.
    Question #2 - I have no idea.
    Barry

  • Acrobat subscription stopped working, each time I open it goes straight to the purchase page

    Acrobat subscription stopped working, each time I open it goes straight to the purchase page

    Hi Poepholl,
    I've checked your account, and nothing seems to be out of order with your Acrobat Pro subscription. Are you launching Acrobat on your desktop? If, for some reason, your subscription has reverted to trial mode, I would expect you'd be presented with the trial dialog box. From that dialog box, you should be able to click License this Software, and then sign in with your Adobe ID and password. If that's not the case, please let us know.
    Best,
    Sara

  • What's going on with my wireless keyboard and mouse power status?

    My iMac (Nov. 2009) came with the wireless keyboard and mouse. When the original batteries wore out, I started using rechargeable batteries and that has worked fine. This is Energizer recharger, not Apple's. I've used and recharged them for well over a year now. When my batteries are freshly recharged, my iMac tells me I have something like 75% charge.
    Earlier this week I'm being told that the batteries have 100% charge. They've never been 100% charged, even when they were new. I haven't charged the batteries for several weeks either when suddenly I supposedly have 100% charge.
    What's going on?

    This is a change that occurred with the 10.6.7 update. Everyone suddenly has 100% charge when other tools report less. Either it's a bug or they adjusted the scale by which it's measured. Some users report that the percentage starts to decrease after the battery is more depleted.
    There's a widget you can use in dashboard in the mean time. Located here:
    http://www.apple.com/downloads/dashboard/status/mightymonitor.html
    We'll wait and see if this is a bug or intentional.
    Regards,
    Captfred

  • After installing mountain Lion my wireless mouse stopped working

    After installing mountain Lion my wireless mouse stopped working my wireless keyboard still works so I can get to the Bluetooth menu via search but once I'm there I can not figure out how to scroll down and select the mouse that is still listed as a linked device. I have already tried restarting the computer and changing the batteries. Called apple thinking they would help since I just bought mountain Lion but silly me apple does not give anything away for free. I was I never payed $20 for this p.o.s So-called operating system

    You can bypass GateKeeper.

  • I'm having problems with a wireless Logitech mouse

    Since upgrading to ML i'm having problems with a wireless Logitech mouse that worked well prior to the update. I'm using the current Logitech Control Center software. No other mouse software is on my Mac Mini. If I use a Guest Aacount the problems ( wheel and back button ) are not present. Any suggestions?

    You might try the Logitech support site. There are communities on there:
    http://www.logitech.com/en-us/support/keyboard-mice-combos
    Here is a link to drivers:
    Logitech Drivers
    You might check your home folder/Library to see if you can find a Logitec .plist.
    You need to look in your user Library/Preferences for the .plist. Hold down the option key while using the Finder "Go To Folder" command. Enter ~/Library. Delete the .plist(s) for the mouse.
    If you prefer to make your user library permanently visible, use the Terminal command found below.
    http://osxdaily.com/2011/07/04/show-library-directory-in-mac-os-x-lion/
    You might want to bookmark the command. I had to use it again after I installed 10.8.2. I have also been informed that if you drag the user library to Finder it will remain visible.

  • When I click on a link to a file, (for instance a Filesonic link) I used to get asked if I wanted to run or download the file. Now it just goes straight to download. How can I stop it doing this? Thank you.

    When I click on a link to a file, (for instance a Filesonic link) I used to get asked if I wanted to run or download the file. Now it just goes straight to download. How can I stop it doing this? Thank you.

    Go to Tools -> Options -> Applications -> Search for your file format, .zip,for instance,
    Select ''' Always ask''' from drop down menu.

  • How do I stop my iPhone 4 from going straight to voice mail?

    My iPhone 4 keeps going straight to Voice Mail and then I get a notified of missed calls?  How can I correct this?

    Check your Do Not Disturb  http://support.apple.com/kb/HT5463 Settings
    If the issue persists... Contact your Carrier.

  • MBP Mouse: Razer Orochi vs Logitech Performance Mouse MX

    Hello
    It has been a week since I started to research a new gaming mouse for my MBP. After going through more reviews than I can remember, I boiled it up to the following 2: Razer Orochi and Logitech Performance Mouse MX.
    Orochi keeps my precious USB ports free (Bluetooth) has a coolest design and better DPI, although the "sleep in 2sec + jerking" issue seems to be really annoying when gaming. The Performance Mouse MX has zero lag/jerking issues, great ergonomics and works on glass! The downside is the USB port sacrifice required by the 2.4GHZ receptor.
    Before throwing the coin on this, I would like to know if anyone has MBP hands-on experience with these fellows. If so, your input would be greatly appreciated.
    Thanks

    I've swayed towards Razer Orochi. After 2 weeks of daily use (MacBook Pro with LEOPARD and "Boot Camp" WINXP), I have yet to find a flaw on this mouse. It delivered on all it's promises. Here's a breakdown of my thoughts on it:
    01 - AESTHETICS AND MISC
    The sleek online pictures at Razer site don't make justice to this mouse. It looks much better in real-life! Couple it with the Razer Kabuto Mouse Mat and your desk will never look the same. The battery top lid is magnetically attached and the USB "Wired Mode" cable is long enough to comfortably circle around my MBP. In terms of ergonomics, Orochi feels great on my big hands. I've found it very comfortable to use with both "fingertip" and "palm" grips.
    02 - FIRMWARE AND DRIVERS
    Let me preface this by saying that "out of the box", with ZERO drivers installed, all 7 buttons worked flawlessly with WINXP. Under LEOPARD, only the "forward and backward" left side buttons didn't work. It's worth underlining that the "Sensitivity Stage" right side buttons worked on both OSs. This means that you can cycle through the 5 preset "Sensitivity Stages" without having to install a single driver! That said, in order to tap into Orochi's full potential, it's imperative to install the latest firmware and drivers. Start by getting the latest v1.06 firmware updater (22/02/2010) from Razer's site (notice you'll need to run this under Windows). Next download and install the latest PC (v1.02, 22/10/2009) and MAC (v2.00, 03/05/2010) drivers. Besides custom macro creation, these drivers also enable full customization of every single button on the Orochi. Starting at v2.00, the MAC driver acquired the same "full features support" one finds in it's PC counterpart. Nonetheless, for reasons I'll explain below, you should avoid using the "Razer Orochi" MAC "Preference Pane".
    03 - CONFIGURATION AND DISABLING ACCELERATION
    Orochi's factory "buttons layout scheme" fitted my needs like a glove. I found no need to tinker with it, although the "Scroll Wheel button" could probably be put to better use. It's "Universal Scrolling" default assignment is uselessly redundant. It's not hard to envision several more productive assignments for it (copy/past, open/close tab, etc). The only 2 settings I ended up by changing were "Polling Rate: 1000 Hz (default 500 Hz)" and "Lightning->Scroll Wheel: ON (default OFF)". I opted not to delve into the "Profiles" and "Macros" sections, even though I'll probably revisit them in a near future. The possibility of creating "per application profile" and "custom macros" are 2 of the most powerful features of this mouse. A shrewd implementation of both will rise your productivity to unprecedented heights.
    In order to take full advantage of Orochi's high-precision "4000DPI 3G Laser Sensor" one must disable mouse acceleration. This allows Orochi to handle all the gliding and pointing bits natively. Assuming the "Enable Acceleration" option on "Razer Orochi Configurator" is left unchecked, there's still the OS mouse acceleration layer to deal with. On the WINXP side, one simply needs to uncheck "Enhance pointer precision" to permanently disable mouse acceleration. Unfortunately things aren't as merry on LEOPARD's side. After hours of research, the solution was finally found in this "Armagetron Forums" thread. In order to roughly homogenize the tracking speed on both OSs, I also set the respective "speed knobs" to 50%. Here are the details for this:
    WINXP
    - Disable Acceleration: Control Panel->Mouse Properties->Pointer Options->Motion-> Enhance pointer precision: OFF
    - Tracking speed at 50%: Control Panel->Mouse Properties->Pointer Options->Motion->Select a pointer speed: 6th notch from "Slow" (11 total).
    LEOPARD
    - Disable Acceleration: Check out this "Armagetron Forums" thread.
    - Tracking speed at 50%: System Preferences->Keyboard & Mouse->Mouse->Tracking Speed: 5th notch from "Slow" (10 total).
    Due to the different "knob sensitivities" of WINXP and LEOPARD, you won't get the same pixel-exact tracking speed on both OSs. Despite that, the "knob at 50%" strategy will get you pretty close. In my personal experience I've found the mouse response to be indistinguishable across WINXP and LEOPARD.
    04 - IN-GAME EXPERIENCE
    Once all configurations were in place, I immediately jumped to a series of thorough in-game testing with "Quake 3" and "Unreal Tournament 2004". Diligently compared "Wired" and "Wireless mode". The former had a noticeable precision advantage. Nonetheless, "Sensitivities Stages" were the clear show-stopper! Switching to the lowest "500 DPI stage" markedly increased my aim in sniper mode. Never before did I got so many "headshots" in a row! Orochi is a literal "killer mouse"! Conversely, the higher sensitivities allowed for lightning fast responses in the heat of "close proximity" battle. This mouse really gives you that extra edge every gamer is looking for.
    The "off the chart" smoothness, responsiveness and accuracy observed in-game was also noticeable during day-to-day usage. It suddenly became clear why some many designers/photographers go with Orochi.
    Many reviews complained about the "sleep in 2sec + jerking" issue. You'll only find it if you actively look for it. It's simply to small of a jerk to be noticed. It will disappear the moment you stop thinking about it. This holds true for gaming and day-to-day usage.
    05 - STAY AWAY FROM "RAZER OROCHI" PREFERENCE PANE
    I've unearthed an uncanny behavior when accessing LEOPARD's "Razer Orochi" preference pane. The mere act of opening it caused the tracking speed to decrease dramatically! In fact, even escalating all the way up to 4000 DPI, the mouse still moved like it was at 1500 DPI! Thankfully, as long as you have access to a WINXP machine, there's a pretty straightforward way to tackle this: simply make sure to always use WINXP driver to configure Orochi. Since the "Synapse On-Board memory" allows one to port settings across OSs, there's really no reason to access LEOPARD's driver at all!
    06 - LOOSE NOTES
    -> Configuration of the Razer Orochi can only be performed in "Wired Mode".
    -> Both WINXP and LEOPARD drivers are capable of writing to Orochi's "Synapse On-Board memory".
    -> The "Sensitivity Stages" work flawlessly on both WINXP and LEOPARD. It's worth to underline the OSD only appears in "Wired Mode".
    -> In "Wireless Mode (bluetooth)": Pooling rate drops to 125ms (125Hz), although you can still cycle through the different "Sensitivity Stages", the OSD will no longer appear.
    -> Clean the laser lens below the Razer Orochi once a month (use soft cloth or cotton swab).
    CONLUSION
    Razer Orochi is simply the best bluetooth "high-precision mouse" out there. If you're are a serious gamer/designer it's a must. Totally worth the price. 5 stars all the way!

  • My MBP doesnt boot after update / Prohibition sign flashes twice and then goes straight to OX Utilities

    Hello all,
    I thought I would never be here, but I am.
    After updating iTunes and Memory Clean in App Store (nothing unusual) my MAC stopped booting properly.
    MBP / early 2011 / Mountain Lion
    It shows the Apple logo flashing twice the prohibiting sign (cancel circle), after that it goes straight to the OS X Utilities.
    Note:
    - It recognizes the HD and the Recovery partition.
    - Verify permission shows a lot of /Applications/iTunes issues, but I have repaired like 5 times and still showing issues.
    - Hardware test passed OK.
    - Repair disk, no issues.
    - Shift (safe mode) doesn't work (lot of flashing ? folder, apple logo, etc).
    - PRAM restarted, twice.
    I can't reinstall or launch the ML installer, when I go trough the install process which mandatory requires Internet connection and AppStore login, it states: This item is temporarily unavailable. Try again later.
    Please help me, I'm desperate this is my production machine and I'm travelling.
    What I'm missing?

    You cannot reinstall Mountain Lion from the App Store, but you can install Mavericks which is free and will run on your computer. Here's what you do:
    Install or Reinstall Mavericks or Mountain Lion from Scratch
    Be sure you backup your files to an external drive or second internal drive because the following procedure will remove everything from the hard drive.
    OS X Mavericks- Erase and reinstall OS X
    OS X Mountain Lion- Erase and reinstall OS X
    OS X Lion- Erase and reinstall Mac OS X
    Note: You will need an active Internet connection. I suggest using Ethernet if possible
                because it is three times faster than wireless.

  • Wireless Logitech keyboard won't work

    Hi guys,
    I have a wireless Logitech diNovo edge keyboard that used to work fine. A few months ago it stopped working and I never bothered to look at it. The keyboard works fine in other PCs running Windows. When I plug it into the Archlinux box the keyboard never synchs to the bluetooth dongle (just blinks).
    This is what happens when I plug the keyboard in (NOVATEK is a wired USB keyboard):
    dmesg
    [ 51.878109] usb 4-2: USB disconnect, device number 2
    [ 55.840026] usb 4-2: new full-speed USB device number 4 using ohci_hcd
    [ 56.045166] hub 4-2:1.0: USB hub found
    [ 56.048080] hub 4-2:1.0: 3 ports detected
    [ 56.345080] usb 4-2.2: new full-speed USB device number 5 using ohci_hcd
    [ 56.479450] input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2.2/4-2.2:1.0/input/input11
    [ 56.479739] generic-usb 0003:046D:C713.0004: input,hidraw0: USB HID v1.11 Keyboard [Logitech Logitech BT Mini-Receiver] on usb-0000:00:06.0-2.2/input0
    [ 56.548115] usb 4-2.3: new full-speed USB device number 6 using ohci_hcd
    [ 56.703434] input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2.3/4-2.3:1.0/input/input12
    [ 56.704162] logitech 0003:046D:C714.0005: input,hiddev0,hidraw1: USB HID v1.11 Mouse [Logitech Logitech BT Mini-Receiver] on usb-0000:00:06.0-2.3/input0
    [ 56.948094] usb 4-2.1: new full-speed USB device number 7 using ohci_hcd
    [ 57.089411] Bluetooth: Core ver 2.16
    [ 57.090507] NET: Registered protocol family 31
    [ 57.090518] Bluetooth: HCI device and connection manager initialized
    [ 57.090529] Bluetooth: HCI socket layer initialized
    [ 57.090535] Bluetooth: L2CAP socket layer initialized
    [ 57.090563] Bluetooth: SCO socket layer initialized
    [ 57.093514] usbcore: registered new interface driver btusb
    [ 90.226597] usb 4-2: USB disconnect, device number 4
    [ 90.226605] usb 4-2.1: USB disconnect, device number 7
    [ 90.227663] usb 4-2.2: USB disconnect, device number 5
    [ 90.283551] usb 4-2.3: USB disconnect, device number 6
    [ 93.210021] usb 4-2: new full-speed USB device number 8 using ohci_hcd
    [ 93.415200] hub 4-2:1.0: USB hub found
    [ 93.418081] hub 4-2:1.0: 3 ports detected
    [ 93.715081] usb 4-2.2: new full-speed USB device number 9 using ohci_hcd
    [ 93.849470] input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2.2/4-2.2:1.0/input/input13
    [ 93.849808] generic-usb 0003:046D:C713.0006: input,hidraw0: USB HID v1.11 Keyboard [Logitech Logitech BT Mini-Receiver] on usb-0000:00:06.0-2.2/input0
    [ 93.918121] usb 4-2.3: new full-speed USB device number 10 using ohci_hcd
    [ 94.057378] input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2.3/4-2.3:1.0/input/input14
    [ 94.058052] logitech 0003:046D:C714.0007: input,hiddev0,hidraw1: USB HID v1.11 Mouse [Logitech Logitech BT Mini-Receiver] on usb-0000:00:06.0-2.3/input0
    [ 94.291136] usb 4-2.1: new full-speed USB device number 11 using ohci_hcd
    [ 96.400094] usb 4-2: USB disconnect, device number 8
    [ 96.400102] usb 4-2.1: USB disconnect, device number 11
    [ 96.402936] usb 4-2.2: USB disconnect, device number 9
    [ 96.460224] usb 4-2.3: USB disconnect, device number 10
    [ 99.843366] usb 4-2: new low-speed USB device number 12 using ohci_hcd
    [ 100.047501] input: NOVATEK USB Keyboard as /devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2:1.0/input/input15
    [ 100.047781] generic-usb 0003:0603:00F2.0008: input,hidraw0: USB HID v1.10 Keyboard [NOVATEK USB Keyboard] on usb-0000:00:06.0-2/input0
    [ 100.060244] input: NOVATEK USB Keyboard as /devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2:1.1/input/input16
    [ 100.060670] generic-usb 0003:0603:00F2.0009: input,hiddev0,hidraw1: USB HID v1.10 Device [NOVATEK USB Keyboard] on usb-0000:00:06.0-2/input1
    See here for udev events.
    Xorg log:
    [ 56.500] (II) config/udev: Adding input device Logitech Logitech BT Mini-Receiver (/dev/input/event2)
    [ 56.500] (**) Logitech Logitech BT Mini-Receiver: Applying InputClass "evdev keyboard catchall"
    [ 56.500] (II) Using input driver 'evdev' for 'Logitech Logitech BT Mini-Receiver'
    [ 56.500] (**) Logitech Logitech BT Mini-Receiver: always reports core events
    [ 56.500] (**) evdev: Logitech Logitech BT Mini-Receiver: Device: "/dev/input/event2"
    [ 56.500] (--) evdev: Logitech Logitech BT Mini-Receiver: Vendor 0x46d Product 0xc713
    [ 56.500] (--) evdev: Logitech Logitech BT Mini-Receiver: Found keys
    [ 56.501] (II) evdev: Logitech Logitech BT Mini-Receiver: Configuring as keyboard
    [ 56.501] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2.2/4-2.2:1.0/input/input11/event2"
    [ 56.501] (II) XINPUT: Adding extended input device "Logitech Logitech BT Mini-Receiver" (type: KEYBOARD, id 8)
    [ 56.501] (**) Option "xkb_rules" "evdev"
    [ 56.501] (**) Option "xkb_model" "evdev"
    [ 56.501] (**) Option "xkb_layout" "us"
    [ 56.720] (II) config/udev: Adding input device Logitech Logitech BT Mini-Receiver (/dev/input/mouse1)
    [ 56.720] (II) No input driver specified, ignoring this device.
    [ 56.720] (II) This device may have been added with another device file.
    [ 56.721] (II) config/udev: Adding input device Logitech Logitech BT Mini-Receiver (/dev/input/event3)
    [ 56.721] (**) Logitech Logitech BT Mini-Receiver: Applying InputClass "evdev pointer catchall"
    [ 56.721] (**) Logitech Logitech BT Mini-Receiver: Applying InputClass "evdev keyboard catchall"
    [ 56.721] (II) Using input driver 'evdev' for 'Logitech Logitech BT Mini-Receiver'
    [ 56.721] (**) Logitech Logitech BT Mini-Receiver: always reports core events
    [ 56.721] (**) evdev: Logitech Logitech BT Mini-Receiver: Device: "/dev/input/event3"
    [ 56.721] (--) evdev: Logitech Logitech BT Mini-Receiver: Vendor 0x46d Product 0xc714
    [ 56.721] (--) evdev: Logitech Logitech BT Mini-Receiver: Found 16 mouse buttons
    [ 56.722] (--) evdev: Logitech Logitech BT Mini-Receiver: Found scroll wheel(s)
    [ 56.722] (--) evdev: Logitech Logitech BT Mini-Receiver: Found relative axes
    [ 56.722] (--) evdev: Logitech Logitech BT Mini-Receiver: Found x and y relative axes
    [ 56.722] (--) evdev: Logitech Logitech BT Mini-Receiver: Found absolute axes
    [ 56.722] (II) evdev: Logitech Logitech BT Mini-Receiver: Forcing absolute x/y axes to exist.
    [ 56.722] (--) evdev: Logitech Logitech BT Mini-Receiver: Found keys
    [ 56.722] (II) evdev: Logitech Logitech BT Mini-Receiver: Configuring as mouse
    [ 56.722] (II) evdev: Logitech Logitech BT Mini-Receiver: Configuring as keyboard
    [ 56.722] (II) evdev: Logitech Logitech BT Mini-Receiver: Adding scrollwheel support
    [ 56.722] (**) evdev: Logitech Logitech BT Mini-Receiver: YAxisMapping: buttons 4 and 5
    [ 56.722] (**) evdev: Logitech Logitech BT Mini-Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 56.722] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2.3/4-2.3:1.0/input/input12/event3"
    [ 56.722] (II) XINPUT: Adding extended input device "Logitech Logitech BT Mini-Receiver" (type: KEYBOARD, id 9)
    [ 56.722] (**) Option "xkb_rules" "evdev"
    [ 56.722] (**) Option "xkb_model" "evdev"
    [ 56.722] (**) Option "xkb_layout" "us"
    [ 56.723] (II) evdev: Logitech Logitech BT Mini-Receiver: initialized for relative axes.
    [ 56.723] (WW) evdev: Logitech Logitech BT Mini-Receiver: ignoring absolute axes.
    [ 56.724] (**) Logitech Logitech BT Mini-Receiver: (accel) keeping acceleration scheme 1
    [ 56.724] (**) Logitech Logitech BT Mini-Receiver: (accel) acceleration profile 0
    [ 56.725] (**) Logitech Logitech BT Mini-Receiver: (accel) acceleration factor: 2.000
    [ 56.725] (**) Logitech Logitech BT Mini-Receiver: (accel) acceleration threshold: 4
    [ 90.266] (II) config/udev: removing device Logitech Logitech BT Mini-Receiver
    [ 90.267] (II) evdev: Logitech Logitech BT Mini-Receiver: Close
    [ 90.267] (II) UnloadModule: "evdev"
    [ 90.363] (II) config/udev: removing device Logitech Logitech BT Mini-Receiver
    [ 90.364] (II) evdev: Logitech Logitech BT Mini-Receiver: Close
    [ 90.364] (II) UnloadModule: "evdev"
    [ 93.870] (II) config/udev: Adding input device Logitech Logitech BT Mini-Receiver (/dev/input/event2)
    [ 93.870] (**) Logitech Logitech BT Mini-Receiver: Applying InputClass "evdev keyboard catchall"
    [ 93.870] (II) Using input driver 'evdev' for 'Logitech Logitech BT Mini-Receiver'
    [ 93.871] (**) Logitech Logitech BT Mini-Receiver: always reports core events
    [ 93.871] (**) evdev: Logitech Logitech BT Mini-Receiver: Device: "/dev/input/event2"
    [ 93.871] (--) evdev: Logitech Logitech BT Mini-Receiver: Vendor 0x46d Product 0xc713
    [ 93.871] (--) evdev: Logitech Logitech BT Mini-Receiver: Found keys
    [ 93.871] (II) evdev: Logitech Logitech BT Mini-Receiver: Configuring as keyboard
    [ 93.871] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2.2/4-2.2:1.0/input/input13/event2"
    [ 93.871] (II) XINPUT: Adding extended input device "Logitech Logitech BT Mini-Receiver" (type: KEYBOARD, id 8)
    [ 93.871] (**) Option "xkb_rules" "evdev"
    [ 93.871] (**) Option "xkb_model" "evdev"
    [ 93.871] (**) Option "xkb_layout" "us"
    [ 94.083] (II) config/udev: Adding input device Logitech Logitech BT Mini-Receiver (/dev/input/event3)
    [ 94.083] (**) Logitech Logitech BT Mini-Receiver: Applying InputClass "evdev pointer catchall"
    [ 94.083] (**) Logitech Logitech BT Mini-Receiver: Applying InputClass "evdev keyboard catchall"
    [ 94.083] (II) Using input driver 'evdev' for 'Logitech Logitech BT Mini-Receiver'
    [ 94.084] (**) Logitech Logitech BT Mini-Receiver: always reports core events
    [ 94.084] (**) evdev: Logitech Logitech BT Mini-Receiver: Device: "/dev/input/event3"
    [ 94.090] (--) evdev: Logitech Logitech BT Mini-Receiver: Vendor 0x46d Product 0xc714
    [ 94.090] (--) evdev: Logitech Logitech BT Mini-Receiver: Found 16 mouse buttons
    [ 94.090] (--) evdev: Logitech Logitech BT Mini-Receiver: Found scroll wheel(s)
    [ 94.090] (--) evdev: Logitech Logitech BT Mini-Receiver: Found relative axes
    [ 94.090] (--) evdev: Logitech Logitech BT Mini-Receiver: Found x and y relative axes
    [ 94.090] (--) evdev: Logitech Logitech BT Mini-Receiver: Found absolute axes
    [ 94.090] (II) evdev: Logitech Logitech BT Mini-Receiver: Forcing absolute x/y axes to exist.
    [ 94.090] (--) evdev: Logitech Logitech BT Mini-Receiver: Found keys
    [ 94.090] (II) evdev: Logitech Logitech BT Mini-Receiver: Configuring as mouse
    [ 94.090] (II) evdev: Logitech Logitech BT Mini-Receiver: Configuring as keyboard
    [ 94.090] (II) evdev: Logitech Logitech BT Mini-Receiver: Adding scrollwheel support
    [ 94.090] (**) evdev: Logitech Logitech BT Mini-Receiver: YAxisMapping: buttons 4 and 5
    [ 94.090] (**) evdev: Logitech Logitech BT Mini-Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 94.090] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2.3/4-2.3:1.0/input/input14/event3"
    [ 94.090] (II) XINPUT: Adding extended input device "Logitech Logitech BT Mini-Receiver" (type: KEYBOARD, id 9)
    [ 94.090] (**) Option "xkb_rules" "evdev"
    [ 94.091] (**) Option "xkb_model" "evdev"
    [ 94.091] (**) Option "xkb_layout" "us"
    [ 94.091] (II) evdev: Logitech Logitech BT Mini-Receiver: initialized for relative axes.
    [ 94.091] (WW) evdev: Logitech Logitech BT Mini-Receiver: ignoring absolute axes.
    [ 94.092] (**) Logitech Logitech BT Mini-Receiver: (accel) keeping acceleration scheme 1
    [ 94.092] (**) Logitech Logitech BT Mini-Receiver: (accel) acceleration profile 0
    [ 94.092] (**) Logitech Logitech BT Mini-Receiver: (accel) acceleration factor: 2.000
    [ 94.092] (**) Logitech Logitech BT Mini-Receiver: (accel) acceleration threshold: 4
    [ 94.094] (II) config/udev: Adding input device Logitech Logitech BT Mini-Receiver (/dev/input/mouse1)
    [ 94.094] (II) No input driver specified, ignoring this device.
    [ 94.094] (II) This device may have been added with another device file.
    [ 96.443] (II) config/udev: removing device Logitech Logitech BT Mini-Receiver
    [ 96.444] (II) evdev: Logitech Logitech BT Mini-Receiver: Close
    [ 96.444] (II) UnloadModule: "evdev"
    [ 96.536] (II) config/udev: removing device Logitech Logitech BT Mini-Receiver
    [ 96.537] (II) evdev: Logitech Logitech BT Mini-Receiver: Close
    [ 96.538] (II) UnloadModule: "evdev"
    [ 100.084] (II) config/udev: Adding input device NOVATEK USB Keyboard (/dev/input/event3)
    [ 100.084] (**) NOVATEK USB Keyboard: Applying InputClass "evdev keyboard catchall"
    [ 100.084] (II) Using input driver 'evdev' for 'NOVATEK USB Keyboard'
    [ 100.084] (**) NOVATEK USB Keyboard: always reports core events
    [ 100.084] (**) evdev: NOVATEK USB Keyboard: Device: "/dev/input/event3"
    [ 100.084] (--) evdev: NOVATEK USB Keyboard: Vendor 0x603 Product 0xf2
    [ 100.084] (--) evdev: NOVATEK USB Keyboard: Found 20 mouse buttons
    [ 100.084] (--) evdev: NOVATEK USB Keyboard: Found keys
    [ 100.084] (II) evdev: NOVATEK USB Keyboard: Configuring as mouse
    [ 100.084] (II) evdev: NOVATEK USB Keyboard: Configuring as keyboard
    [ 100.085] (**) evdev: NOVATEK USB Keyboard: YAxisMapping: buttons 4 and 5
    [ 100.085] (**) evdev: NOVATEK USB Keyboard: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 100.085] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2:1.1/input/input16/event3"
    [ 100.085] (II) XINPUT: Adding extended input device "NOVATEK USB Keyboard" (type: KEYBOARD, id 8)
    [ 100.085] (**) Option "xkb_rules" "evdev"
    [ 100.085] (**) Option "xkb_model" "evdev"
    [ 100.085] (**) Option "xkb_layout" "us"
    [ 100.087] (II) config/udev: Adding input device NOVATEK USB Keyboard (/dev/input/event2)
    [ 100.088] (**) NOVATEK USB Keyboard: Applying InputClass "evdev keyboard catchall"
    [ 100.088] (II) Using input driver 'evdev' for 'NOVATEK USB Keyboard'
    [ 100.088] (**) NOVATEK USB Keyboard: always reports core events
    [ 100.088] (**) evdev: NOVATEK USB Keyboard: Device: "/dev/input/event2"
    [ 100.088] (--) evdev: NOVATEK USB Keyboard: Vendor 0x603 Product 0xf2
    [ 100.088] (--) evdev: NOVATEK USB Keyboard: Found keys
    [ 100.088] (II) evdev: NOVATEK USB Keyboard: Configuring as keyboard
    [ 100.088] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2:1.0/input/input15/event2"
    [ 100.088] (II) XINPUT: Adding extended input device "NOVATEK USB Keyboard" (type: KEYBOARD, id 9)
    [ 100.088] (**) Option "xkb_rules" "evdev"
    [ 100.088] (**) Option "xkb_model" "evdev"
    [ 100.088] (**) Option "xkb_layout" "us"
    Anyone have a clue what's wrong? Thanks,

    Splex wrote:
    I also prefer to not run the dongle in bluetooth mode... it causes so many headaches.
    There may be a better way to disable the bluetooth mode, but you can comment out the 'Logitech devices' rule in /usr/lib/udev/rules.d/97-bluetooth-hid2hci.rules:
    # Logitech devices
    #KERNEL=="hiddev*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c70[345abce]|c71[34bc]", \
    # RUN+="hid2hci --method=logitech-hid --devpath=%p"
    Once you save the changes, simply replug your dongle, hit the connect buttons and it should work as if it is wired.
    Whenever udev is upgraded, the rule file will be overwritten...  you can add this to your /etc/pacman.conf to prevent it from being overwritten:
    NoUpgrade = usr/lib/udev/rules.d/97-bluetooth-hid2hci.rules
    If anyone knows of a better way to prevent the default udev rules from switching the dongle to HCI mode, please speak up
    Just tried this, didn't work for me :-/
    grr.

Maybe you are looking for