-
-
Notifications
You must be signed in to change notification settings - Fork 310
Reporting improvements issues
Thank you for any report feedback to improve AndrOBD.
You are always welcome to suggest any potential code improvements as a GitHub pull request.
If you want to suggest a functional improvement without having any code changes available, please report as a new issue(see below).
In case you detect any problem or potential improvement please report it via the AndrOBD issue tracker.
It is very helpful for our further analysis and possible bug fixes to have as much details as possible.
Important details are:
- AndrOBD version
- Used OBD adapter type
- Connected vehicle make, type, year, engine size
- Used AndrOBD function
- Description of problem
- Sequence how to reproduce the problem
In order to allow AndrOBD to store log files for analysis you will have to grant access rights to the device's storage system. You will be asked for this permission on initial start of the app. This setting may be changed at any time in the app properties within the system settings.
With access rights granted AndrOBD stores log files in a subdirectory on your primary storage device. (com.fr3ts0n.ecu.gui.androbd/log/AndrOBD.log.*)
The detail level of the logged debug information can be adjusted in the Settings > Development options > Logging level.
Available logging level are:
- OFF is a special level that can be used to turn off logging.
- SEVERE is a message level indicating a serious failure.
- WARNING is a message level indicating a potential problem.
- INFO is a message level for informational messages.
- CONFIG is a message level for static configuration messages.
- FINE is a message level providing tracing information.
- FINER indicates a fairly detailed tracing message.
- FINEST indicates a highly detailed tracing message.
- ALL indicates that all messages should be logged.
- By default the detail level is set to INFO.
- Preferred detail level for issue analysis is FINE.