Logitech dinovo edge stopped working

Hello, my Logitech dinovo edge wireless keyboard stopped working at one point in the last few days, when I use it, I can't get any response from the computer when I hit any keys or use the touchpad.
It used to work out of the box I just had to run the bluetooth, and it worked.
Here's an output of the log, when connecting the bluetooth dongle to the computer:
Sep 21 10:40:51 Magda usb 1-8: new full speed USB device using ohci_hcd and address 13
Sep 21 10:40:51 Magda usb 1-8: configuration #1 chosen from 1 choice
Sep 21 10:40:51 Magda hub 1-8:1.0: USB hub found
Sep 21 10:40:51 Magda hub 1-8:1.0: 3 ports detected
Sep 21 10:40:52 Magda usb 1-8.2: new full speed USB device using ohci_hcd and address 14
Sep 21 10:40:52 Magda usb 1-8.2: configuration #1 chosen from 1 choice
Sep 21 10:40:52 Magda input: Logitech Logitech BT Mini-Receiver as /class/input/input12
Sep 21 10:40:52 Magda input,hidraw5: USB HID v1.11 Keyboard [Logitech Logitech BT Mini-Receiver] on usb-0000:00:02.0-8.2
Sep 21 10:40:52 Magda usb 1-8.3: new full speed USB device using ohci_hcd and address 15
Sep 21 10:40:52 Magda usb 1-8.3: configuration #1 chosen from 1 choice
Sep 21 10:40:52 Magda input: Logitech Logitech BT Mini-Receiver as /class/input/input13
Sep 21 10:40:52 Magda input,hiddev3,hidraw6: USB HID v1.11 Mouse [Logitech Logitech BT Mini-Receiver] on usb-0000:00:02.0-8.3
[roberth@Magda ~]$ hcitool dev
Devices:
Any help please?

I was able to get mine listed in hcitool by using hid2hci.  Use lsusb to get the device's hex ID (just running the command hid2hci worked as well since I only had one device).  I was able to enable this behavior on start by setting HID2HCI_ENABLE and HIDD_ENABLE to true in /etc/rc.d/bluetooth and /etc/conf.d/bluetooth.
Last edited by fiatguy85 (2009-01-23 20:53:03)

Similar Messages

  • Logitech DiNovo Edge (non-mac version) suddenly stopped working on 17MBP5,2

    I have a Mid 2009, 17" MacBook Pro 5,2 with Mac OS X 10.6.7.
    Connected to the laptop I have a Dell 2709WFP via HDMI, a Logitech MX Revolution mouse and a Logitech DiNovo Edge.
    Recently the keyboard would stop working after a reboot. I would have to disconnect the KB dongle and log into Mac OS X before reconnecting for it to work. Then it stopped working altogether no matter what I did. Unplug, plug it back in. Different USB ports, etc... I did not have the Logitech Control Center installed.
    So I installed the latest Logitech Control Center. It recognizes the mouse, but not the keyboard. However the mousepad on the keyboard works. Just the keyboard itself does not.
    So I put the KB dongle into my 13" Mid 2009 MBP5,5 (10.6.7) and it works perfectly. So I plug it into a Windows 7 PC, and it works perfectly. The battery is fully charged. The issue existed in both 10.6.6 & 10.6.7.
    I've tried reconnecting and everything else. I'm at a loss. Totally confused.
    I haven't installed any applications lately when the issue started.
    Does anyone have any suggestions?
    Message was edited by: PhillyMike38

    Gee, don't everyone answer all at once!

  • Logitech diNovo edge and 10.6.3 erratic?

    Installed 10.6.3 with no problem but kept running into 'gray screen of death'....one by one i eliminated things and the one consistent problem was when the logitech dinovo edge (mac edition) keyboard tried to pair. I'm using it now but i'm waiting for that gsod since it's the first time that the machine has held up after pairing. Anyone else having problems with logitech stuff? My logitech mx revolution mouse is fine but that's not bluetooth....my apple bluetooth mice work fine (guess I have too many things!!!) and if i use the wired apple keyboard and wired mouse, nary a problem. I don't use more than one wireless mouse/keyboard at a time.......

    I was able to get mine listed in hcitool by using hid2hci.  Use lsusb to get the device's hex ID (just running the command hid2hci worked as well since I only had one device).  I was able to enable this behavior on start by setting HID2HCI_ENABLE and HIDD_ENABLE to true in /etc/rc.d/bluetooth and /etc/conf.d/bluetooth.
    Last edited by fiatguy85 (2009-01-23 20:53:03)

  • IPhone 4s Bluetooth and Logitech diNovo Edge

    I have read some of the Bluetooth problems of iPhone 4s. Still now I cannot paired my iphone 4s with my desktop and Samsung Omnia. However I am able to pair with my Motorola headset, Sony Vaio laptop and Logitech diNovo Edge keyboard.
    I stopped trying to pair these failed devices because I considered it as incompatible issues. The reason I am posting this message is would like to get some tips and trick to use Logitech diNovo Edge keyboard. I am able to type and volume control.
    Any tips to connect with old Bluetooth devices and tips for file transfer without jailbreak will be very appreciated.

    your problem is with how many bluetooth profiles iphone support
    http://support.apple.com/kb/HT3647
    this and accepting the lack of some features is the solution

  • Why did Start Analog Edge stop working?

    I have been using the Start Analog Edge DAQmx function to initiate my data read (similar to the Multi-Devices Synch-Analog Input-Finite Acq-Analog Start.vi example). It has worked fine for several days, but recently stopped working. I can see the signal at the hardware test panel, I can see the trigger signal on the waveform if I route around the start trigger function. I cannot actually get the function to recognize the start trigger.
    Not sure what other sort of debugging I can do. Hopefully, someone has encountered this before and can clue me in to what I am missing.
    =Jason Hill
    New Product Engineer
    Groth Corp.

    Hi,
    I have a couple questions for you to help narrow down the issue:
    1) What device are you using?
    2) What driver are you using?
    3) What has changed in the setup (hardware and software) from when it was working to when it stopped working?
    4) You are using a multiple device VI. Is that because you have multiple devices you are trying to trigger. Please explain in more detail what you are trying to do and how you are trying to do it.
    You could use the ContACq&Graph Voltage-Int Clk-Analog Start.vi to do the same thing with just one board. This may be better suited for your needs. This example can be found in the LabVIEW example finder.
    I hope this helps. Have a Great Day!
    George

  • Logitech Touchmouse app stopped working

    My Logitech Touchmouse iPhone app has stopped working. When run from the iPhone, says Searching for Servers and never comes back. Entering IP address by hand says Cannot Connect. Turning off Firewall does not help. Server is running on my Mac. iOS 4 and 10.6.4 on an iMac. Was working before iOS 4 upgrade for sure.
    Anyone else?
    Message was edited by: NewYorkYogi

    I was able to get mine listed in hcitool by using hid2hci.  Use lsusb to get the device's hex ID (just running the command hid2hci worked as well since I only had one device).  I was able to enable this behavior on start by setting HID2HCI_ENABLE and HIDD_ENABLE to true in /etc/rc.d/bluetooth and /etc/conf.d/bluetooth.
    Last edited by fiatguy85 (2009-01-23 20:53:03)

  • Since last update, sound on my Logitech Quickcam fusion stopped working?

    In iChat ,I noticed that since the last apple software update the sound on my Quickcam Fusion stopped working only the video works.. I noticed that under preferences, video, then microphone, it is no longer listed as a USB device option. Only line-in is present.
    I suspect it has something to do with the last software update from Apple. I think the details had mentioned that they changed something with USB security??
    I would like this camera to work since I just bought it and it was working 2 weeks ago!
    Thanks for any help.
    Mini   Mac OS X (10.4.10)   latest version of iChat AV

    New Audio Update toady for me.
    Although this was on my MacBook Pro that I have just reinstalled the OS on.
    (I can not find it in downloads. Strangely it has appeared after the 10.4.10 combo Update)
    It may also pay to start up GarageBand odd as it sounds.
    Also go to Applications/Utilities and open the MIDI Utility and make sure the setting is set to 44100
    10:06 PM Monday; July 2, 2007

  • USB device (Logitech QuickCam Messenger) stopped working (SOLVED)

    Hey there,
    I have a logitech quickcam messenger, which used to work perfectly 2 days ago. I updated my system yesterday and this morning, but I tried the cam again only now, and neither cheese nor webcamstudio work anymore (it never worked in skype since I moved from Mint to Arch a few weeks ago, but that was easily (and better) addressed by starting cheese and then using desktop sharing in Skype)
    The webcam is recognized
    sammy@Cosmic-Bandito ~$ lsusb
    Bus 001 Device 007: ID 046d:08da Logitech, Inc. QuickCam Messanger
    Bus 001 Device 006: ID 056a:00d4 Wacom Co., Ltd
    Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB [Hama]
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 002 Device 003: ID 046d:c513 Logitech, Inc. MX3000 Cordless Desktop Receiver
    Bus 002 Device 002: ID 046d:c51a Logitech, Inc. MX Revolution/G7 Cordless Mouse
    Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    /dev/video and /dev/video0 are created.
    cheese only shows a black window and spits out :
    sammy@Cosmic-Bandito ~/Videos/Webcam$ cheese
    libv4l2: error turning on stream: Input/output error
    webcamstudio hangs when I try to start the preview and its output is :
    libv4l2: error turning on stream: Input/output error
    USB Camera (046d:08da) Error: BaseSrc: [v4l2src0],5, Error starting streaming on device '/dev/video0'.
    EDIT: that's the output of dmesg when I reconnect the webcam (after having disconnected it obviously) :
    [ 2216.282753] hub 1-1:1.0: state 7 ports 4 chg 0000 evt 0010
    [ 2216.283231] hub 1-1:1.0: port 4, status 0101, change 0001, 12 Mb/s
    [ 2216.387861] hub 1-1:1.0: debounce: port 4: total 100ms stable 100ms status 0x101
    [ 2216.450867] usb 1-1.4: new full speed USB device using ehci_hcd and address 11
    [ 2216.462234] hub 1-1:1.0: port 4 not reset yet, waiting 10ms
    [ 2216.537006] usb 1-1.4: ep0 maxpacket = 8
    [ 2216.538992] usb 1-1.4: skipped 4 descriptors after interface
    [ 2216.538994] usb 1-1.4: skipped 2 descriptors after interface
    [ 2216.538996] usb 1-1.4: skipped 1 descriptor after endpoint
    [ 2216.538998] usb 1-1.4: skipped 2 descriptors after interface
    [ 2216.539000] usb 1-1.4: skipped 1 descriptor after endpoint
    [ 2216.539006] usb 1-1.4: udev 11, busnum 1, minor = 10
    [ 2216.539008] usb 1-1.4: New USB device found, idVendor=046d, idProduct=08da
    [ 2216.539010] usb 1-1.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
    [ 2216.539081] usb 1-1.4: usb_probe_device
    [ 2216.539084] usb 1-1.4: configuration #1 chosen from 1 choice
    [ 2216.539364] usb 1-1.4: adding 1-1.4:1.0 (config #1, interface 0)
    [ 2216.539400] zc3xx 1-1.4:1.0: usb_probe_interface
    [ 2216.539402] zc3xx 1-1.4:1.0: usb_probe_interface - got id
    [ 2216.539404] gspca: probing 046d:08da
    [ 2217.384009] zc3xx: probe 2wr ov vga 0x0000
    [ 2217.407008] zc3xx: probe sensor -> 0011
    [ 2217.407010] zc3xx: Find Sensor HV7131R(c)
    [ 2217.407304] input: zc3xx as /devices/pci0000:00/0000:00:0b.1/usb1/1-1/1-1.4/input/input14
    [ 2217.407372] gspca: video0 created
    [ 2217.407374] gspca: found int in endpoint: 0x82, buffer_len=8, interval=10
    [ 2217.407381] usb 1-1.4: link qh8-0601/f6f9e240 start 5 [1/2 us]
    [ 2217.407401] usb 1-1.4: adding 1-1.4:1.1 (config #1, interface 1)
    [ 2217.407438] zc3xx 1-1.4:1.1: usb_probe_interface
    [ 2217.407441] zc3xx 1-1.4:1.1: usb_probe_interface - got id
    [ 2217.407443] gspca: probing 046d:08da
    [ 2217.407455] snd-usb-audio 1-1.4:1.1: usb_probe_interface
    [ 2217.407458] snd-usb-audio 1-1.4:1.1: usb_probe_interface - got id
    [ 2217.410813] usb 1-1.4: adding 1-1.4:1.2 (config #1, interface 2)
    [ 2217.410855] drivers/usb/core/inode.c: creating file '011'
    EDIT 2: Just tried the webcam on another computer, and it works there. so it's not the hardware
    any ideas? I'm pretty desperate, as this is the only way for me to keep in touch with my kids  at the moment
    Last edited by SammyF (2010-05-28 20:44:15)

    SOLVED : really stupid problem, but well... I'll completement my post and leave it for anybody who might hit the same problem :
    dmesg looked like this when after I started cheese :
    [ 3815.848011] usb 1-1.4: unlink qh8-3008/ec236980 start 0 [1/2 us]
    [ 3815.848995] gspca: found int in endpoint: 0x82, buffer_len=8, interval=10
    [ 3815.849001] usb 1-1.4: link qh8-0601/f6848ec0 start 1 [1/2 us]
    [ 3816.696230] zc3xx: probe 2wr ov vga 0x0000
    [ 3816.917369] ehci_hcd 0000:00:0b.1: iso sched full f0049c00 (now 652 max 2700)
    [ 3816.917377] gspca: bandwidth not wide enough - trying again
    [ 3816.938010] gspca: no transfer endpoint found
    The (not so obvious) solution was to connect the webcam directly to the computer and not through a USB hub. I have no idea why it used to work and suddenly stopped, but it works again now.
    sorry to take up your time, in case I did.
    Last edited by SammyF (2010-05-28 20:44:56)

  • 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]]

  • Logitech mouse wheel stopped working

    Hello,
    I had this mouse for a long time. It's a Logitech Cordless Optical mouse connected to a Linksys KVM (I share with 4 different computers). Last week the mouse scroll wheel stooped working. I tried another Logitech mouse (G9) to directly to the USB of my Mac and the mouse wheel scrolls fine.
    Now the problem's the old mouse wheel works fine on my other computers. I tried turning the KVM off, resetting the IR unit, and of course rebooting my mac. Nothing worked. The odd thing is, if I connect the old mouse directly to the Mac, it works OK.
    I really hate the G9. I'd rather stick with my current mouse, but I need the scroll wheel. Any ideas?

    Your profile lists one of the computers as "Hackintosh." Because OS X is licensed for use only with Apple branded computers & the Discussions Terms of Use prohibit discussing illegal uses of software, & equally importantly because we have no idea of how running a hacked version of OS X on non-Apple hardware might be a part of your problem, we cannot help you.
    Sorry.

  • Samsung s6 edge stopped working

    hi ive only had my phone couple months now and took it off charge tonight before i went out and when i took it out my pocket i cant get it on,there is a flashing blue light at the top left,any suggestions

    If you continue to have problems with the phone you should get in touch with Samsung directly. It's a very expensive piece of kit and is still under warranty. This shouldn't be happening if it's two months oldhttp://www.samsung.com/uk/support/category/mobile/mobiledevice

  • 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.

  • Dinovo Edge BT Keyboard

    Previously, I've had pretty good luck with Logitech BT keyboards, and I really want my Dinovo Edge to work. It pairs and connects just fine, but loses pairing and connectivity after my MacPro is in sleep mode for an hour or more. At that point, it is necessary to open Bluetooth Preferences and reconnect. It will reconnect and work fine but, strangely enough, says it is not paired (?). I just want the thing to remain paired and connected and to wake my computer from sleep (yes, I've check off that in preferences). Any suggestions? I'm using the Mac BT module (built-in), not the USB dongle that came with the keyboard.

    Yesterday, I plugged in the Logitech-supplied USB BT receiver (the 'dongle'). Everything works perfectly now. The computer wakes with the keyboard after sleeping overnight. Strange that the Apple built-in BT module doesn't do that.
    Message was edited by: Rerunner

  • EDGE NOT WORKING AFTER 4.0 UPDATE

    I was overjoyed when I upgraded the OS of my Iphone to 4.0 but the joy was short lived as I came to know that the EDGE stopped working after the upgrade. I am using it in India with Airtel as the Service Provider. I spoke to Airtel and they opined that EDGE would not work on IOS 4.0. Even after the upgrade installation IOS 4.0.1, no improvement in result. Can any one help me on this?

    Edge works fine in Australia, so I would be surprised if it didn't work in India.
    First, Restart you phone.
    Hold the Home and Sleep keys till the Swipe to Turn Off is displayed and the follow the instruction.
    Once the phone is turned off, turn it back on and wait for your carrier to be connected and see if that works
    If still no good then,
    Check the following settings.
    Settings - General - Network - Set Enable 3G to Off, This will turn on Edge instead.
    Also in the same area Settings - General - Network - Set Cellular Date to On.
    Now you should have Data over Edge not 3G.
    If that doesn't make any difference, you may have to Reset the Network Settings
    Settings - General - Reset - Reset Network Settings.
    This will also reset any WiFi settings you have, but to prove the problem, you will have to renew any Wifi zones you are using.
    If Still no joy, change the phone to Airplane mode
    Settings - Airplane Mode to On.
    Leave it for a moment until you have lost connection to your carrier, the turn it back on.
    If all that fails, you may have to restore the phone to new.
    Airtel/Vodaphone (I presume this is the one you are using) advertise themselves as a 2G/3G network, so there is no reason Edge should not be accessible that I know of.

  • Adobe Edge Animate CC 2014.1  is totally not working. It stop working after 5min. Sometimes is stops the operating system.

    Adobe Edge Animate CC 2014.1  is totally not working. It stop working after 5min. Sometimes is stops the operating system. On on mac OS X Yosemite. macbook pro i7 2013.
    I reinstalled it not helping.
    Message was edited by: Daniel Boguszewski

    UPDATE
    i have ulpaded 2 animation ( one normal and one Responsive ) in 2 different server here the link
    www.eclipseadv.com/maliRP/maliRP.html
    Untitled
    via SAFARI or CHROME on MAC all OK
    but via IPAD ( SAFARI, CHROME and MERCURY) i didn't see the video, just the animation of the BUTTON  and the link if i click on it (not in Mercury), like in the content viewer.

Maybe you are looking for