• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Debugging a BT pedal
#2
After running several tests I now have solid proof that the Firefly is misbehaving.
At random times it generates a keycode 129 (scancode 161). This code is understood to be a "CD Eject" command. When connected to my laptop, it does, indeed, eject the CD.
Most of the time this code is generated immediately after a pedal press. When the Firefly goes to sleep, and a pedal is pressed, keycode 129 is sent instead of the expected pedal key, which may confuse the software. (As it did in earlier versions os MobileSheetsPro.)
Since keycodes 129 are sent sometimes while pressing pedals, it can not be the 30-minute inactivity timer.
If noone else has a misbehaving Firefly I must conclude that mine is defective and I will trade it in for a BT-106.
Johan
www.johanvromans.nlwww.hetgeluidvanseptember.nlwww.howsagoin.nl
Samsung Galaxy Note S4 (T830) 10.5", Android 10.0, AirTurn Duo & Digit.
Samsung A3 (A320FL), Android 8.0.0 (emergency).
Reply


Messages In This Thread
Debugging a BT pedal - by sciurius - 05-25-2015, 03:34 AM
RE: Debugging a BT pedal - by sciurius - 05-25-2015, 09:59 PM
RE: Debugging a BT pedal - by Zubersoft - 05-26-2015, 03:03 AM
RE: Debugging a BT pedal - by sciurius - 05-26-2015, 04:37 AM
RE: Debugging a BT pedal - by Zubersoft - 05-26-2015, 05:40 AM

Digg   Delicious   Reddit   Facebook   Twitter   StumbleUpon  


Users browsing this thread:
1 Guest(s)


  Theme © 2014 iAndrew  
Powered By MyBB, © 2002-2021 MyBB Group.