maxmati/a4tech-bloody-linux-driver

Issues

• Not connecting. LIBUSB_ERROR_TIMEOUT

  #36 opened 3 years ago by ForumLiker
  1

• libusb-1.0 not found

  #37 opened 2 years ago by merajmasuk
  1

• J95s not working

  #35 opened 3 years ago by donaastor
  0

• Legacy A4Tech Mice

  #33 opened 3 years ago by moriel5
  0

• add bloody r8/r80 ?

  #32 opened 3 years ago by hinteor
  0

• Bloody j95s

  #30 opened 4 years ago by sandikata
  0

• Wrong pid for V5

  #29 opened 5 years ago by RyvkinSergey
  1

• PID for T50

  #27 opened 7 years ago by codeh4nter
  1

• PID for Bloody Blazing A90

  #25 opened 7 years ago by roko772
  1

• Ubuntu 17.10 and a4Tech v5: No suitable device found.

  #20 opened 7 years ago by lotarbo
  8

• Bloody v8 PID

  #13 opened 8 years ago by isage
  2

• Info about my fork - Bloody P85

  #19 opened 7 years ago by C0rn3j
  0

• Have you tried contacting A4Tech for the opcodes?

  #16 opened 8 years ago by rockerbacon
  2

• Read DPI value

  #14 opened 8 years ago by isage
  3

• Documentation?

  #18 opened 7 years ago by toby3d
  2

• Protocol

  #6 opened 9 years ago by VlaoMao
  1

• install problem

  #10 opened 8 years ago
  14

• No suitable device found

  #11 opened 8 years ago by burianvlastimil
  1

• What does this do?

  #9 opened 8 years ago by lfbr0
  1

• No suitable device found

  #8 opened 9 years ago by ozmartian
  1

• Question: is it hard to get mouse charge level?

  #3 opened 9 years ago by ZaWertun
  3

• Other models

  #4 opened 9 years ago by paulrevival
  4