-
-
Notifications
You must be signed in to change notification settings - Fork 294
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does not reconnect after bluetooth adapter off/on - does not run unattended #212
Comments
AndrOBD does re-try to connect on the vehicle side if the vehicle doesn't respond, but the adapter is still connected. There is a intent for the connection attempt, but this is currently only internal, but NOT exported to the system. |
As in other case, I have to detect that car is moving (by macrodroid ACTIVITY trigger) and the use UI interaction (simulate taps) to connect again. |
I have also wanted a way to automatically connect everything once I get back into the car, so I can automatically start sending MQTT data using the plugin. I might use an automation app to simulate taps, too, but it seems like exposing the internal intent would be very convenient. How hard would it be to expose that externally? |
Describe the bug
When I turn off the car the ELM327 turns off. After next start, adapter turns ON but the AndrOBD does not receive any data. It says connected, but "No data". I have to manually disconnect and reconnect again.
I found in other issue that auto reconnect should be present since 7 years ago. Does it need to be configured to wrk properly? Because in my case it is not working.
If there is intent for connection, I could automate it with MacroDroid so it automatically reconnects after ELM327 detected. Is there such intent?
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
AndrOBD Debug log files
Please attach AndrOBD debug log files.
AndrOBD stores log files in a subdirectory on your primary storage device. (com.fr3ts0n.ecu.gui.androbd/log/AndrOBD.log.*)
Log detail level
The detail level of the logged debug information can be adjusted in the Settings > Development options > Logging level.
By default the detail level is set to INFO.
Preferred detail level for issue analysis is DEBUG. (Since V1.5.0 this level is called FINE)
Important details on your environment:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: