Skip to content

Error codes

Jump to bottom
Enrico edited this page Apr 20, 2020 · 13 revisions

Welcome to the error codes wiki!

Here you can find all the errors that may appear and a nice explanation of every single one of them.

The syntax for error codes is the following: Sector + "x" + Error code

(e.g. sector 2 error code 13 -> 2x13)

Init errors (sector 1)

  • Error code 1x01 -> the GPS permission wasn't granted to the app.
  • Error code 1x02 -> The Bluetooth permission wasn't granted to the app.
  • Error code 1x03 -> There has been an unknown error while setting up the permissions, this should never happen.

Bluetooth errors (sector 2)

  • Error code 2x01 -> the connection was unexpectedly closed by the cat, and reading the input stream threw and exception.
    You can enable the debug mode in options fragment to get specific information inside the disconnection notice.
  • Error code 2x02 -> the discovery was cancelled while the cat was connected (which shouldn't have been started in the first place).
  • Error code 2x03 -> the device doesn't support Bluetooth, or android failed to provide an adapter, which will mostly like mean it doesn't have one.
  • Error code 2x04 -> there was an error while registering a broadcast receiver or while setting up the discovery.
    Further information can be found alongside with the error message by enabling debug.
  • Error code 2x05 -> the android API that allows us to get an adapter has thrown an exception, or there was an error while requesting the user to turn Bluetooth on.
    Further information can be found alongside with the error message.
  • Error code 2x06 -> while cancelling the discovery, the Bluetooth adapter turned out to be null.
  • Error code 2x07 -> while cancelling the discovery, the countdown timer turned out to be null.
  • Error code 2x08 -> we couldn't create a Bluetooth socket: createRfcommSocketToServiceRecord threw an exception or the device we were trying to use is null.
    It should never happen, but this can also be caused by the UUID we're using which would have to be null.
  • Error code 2x09 -> closing the connection socket has failed. (this should never happen as the code is thrown only if the input stream reader has terminated with code 0)
    You can get further information by enabling debug mode.
  • Error code 2x10 -> the connection failed. The specific cause is provided alongside with the error message.
  • Error code 2x11 -> we weren't able to close the client socket.
  • Error code 2x12 -> the Bluetooth socket turned out to be null (most likely). More information is provided alongside with the error message.
  • Error code 2x13 -> we couldn't write in the output stream or flush it. More information is provided alongside with the error message.
  • Error code 2x14 -> the connection was unexpectedly closed, but the exception is null.
  • Error code 2x15 -> the Bluetooth is required in order to connect to the cat.
  • Error code 2x16 -> there was an error while receiving answers from a request, no restart is needed.

Graphical errors (sector 3)

  • Error code 3x01 -> we weren't able to get the drawable and apply it to the connection buttons.
  • Error code 3x02 -> we weren't able to remove the softkeyboard from the screen.
  • Error code 3x03 -> we weren't able to get the alert dialog window.

Settings error (sector 4)

  • Error code 4x01 -> system preferences (the tunnel we use to get all the settings) are null.
  • Error code 4x02 -> there was an error while writing a value to the system preferences.
  • Error code 4x03 -> there was an error while reading a value from the system preferences.

Generic errors (sector 5)

  • Error code 5x01 -> we couldn't get the current context, no further information.
  • Error code 5x02 -> while starting the pitch roll timer, another one already existed.
  • Error code 5x03 -> while stopping al the motor movement threads, one of them was null.

Return to main page

Clone this wiki locally