Skip to content
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

Open
jbrepogmailcom opened this issue Jul 25, 2022 · 3 comments

Comments

@jbrepogmailcom
Copy link

jbrepogmailcom commented Jul 25, 2022

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:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

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:

  • Android OS version:
  • AndrOBD version:
  • OBD adapter type:
  • Connected vehicle make, type, year, engine size:

Additional context

Add any other context about the problem here.

@fr3ts0n
Copy link
Owner

fr3ts0n commented Jul 29, 2022

AndrOBD does re-try to connect on the vehicle side if the vehicle doesn't respond, but the adapter is still connected.
However, after the adapter gets disconnected there is NO re-try. This represents the common situation of leaving the car/bluetooth range with the mobile.

There is a intent for the connection attempt, but this is currently only internal, but NOT exported to the system.

@jbrepogmailcom
Copy link
Author

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.

@wunter8
Copy link

wunter8 commented Jun 21, 2023

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants