Help Center

Improved

Fixed

abrp

Open

In Review

Planned

In Progress

Completed

Rejected

Awaiting Clarification

Main Roadmap

Quarterly Roadmap

Monthly Roadmap

Tell us how we can make ABRP even better for you! ⚡️

Have something to say?

Describe the issue and steps to reproduce.

🐛 Report a bug

💡 Request a feature

Specify the vehicle type and your requirements.

🚗 Request a vehicle

Request a charge card or charger network you're missing.

💳 Charge Card/Network Requests

Report missing or inaccurate charger locations.

⚡️ Report a Charger

Request live data connections for your vehicle model.

🔗 Integration Requests

📥 Feedback

🤔 Questions

Hey {name|there}! 👋

🚧 THIS IS A TICKET MIGRATED FROM UPVOTY. The original ticket and comments will be available for a limited time over at: <a href="https://abrp.upvoty.com/b/report-a-bug/abrp-obd-on-android-fails/" rel="noopener noreferrer" target="_blank">https://abrp.upvoty.com/b/report-a-bug/abrp-obd-on-android-fails/</a> ——————————————————————————— My OBD device vLinker MC+ has 2 bluetooth presentations: vLinker MC-Android and vLinker MC-IOS. Both appear as available devices in the android bluetooth setup. But the ABRP app can only see vLinker MC-IOS. If I pair the phone with vLinker MC-Android it makes no difference to ABRP. It only displays vLinker MC-IOS. Is there something I can do to get this to work (without buying an iphone) or is there a bug you can fix?

A Better Routeplanner

ABRP OBD on Android fails

Subscribe to post

Subscribe to post