All Honda models (1992 - 2001 OBD1/2A/2B) that use the proprietary 3 pin or 5 pin DLC diagnostic connector are fully compatible and supported.
We encourage our customers to follow the compatibility guidelines prior to the item purchase, because of possible diagnostic connector differences between markets and model years. In case of United States / Canada market, the compatible 3 pin diagnostic connector was used only on OBD1 models ('92-'95), whereas the other markets (Europe, Japan, Australia, Brazil, Russia, etc...) saw usage of 3 pin (5 pin on some European models) on OBD1/2A/2B models ('91-'03).
Car models that use the 16 pin diagnostic connector, i.e. standard OBD2 socket (US/CA '96-, others '99-) are not supported at this moment.
We encourage our customers to follow the compatibility guidelines prior to the item purchase, because of possible diagnostic connector differences between markets and model years. In case of United States / Canada market, the compatible 3 pin diagnostic connector was used only on OBD1 models ('92-'95), whereas the other markets (Europe, Japan, Australia, Brazil, Russia, etc...) saw usage of 3 pin (5 pin on some European models) on OBD1/2A/2B models ('91-'03).
Car models that use the 16 pin diagnostic connector, i.e. standard OBD2 socket (US/CA '96-, others '99-) are not supported at this moment.
Yes, it does work with some, for more details please refer to the general compatibility guidelines.
To determine if we're currently shipping to your country, go to the e-shop, click the button "order" and check if your country is available in the address country selection list.
Yes, we can ship to RUSSIA, however customers from Russia are not able to use the provided payment methods since Russia has been cut off from the global payment system, all cards issued by Russian banks are getting rejected or receive an error during the payment process. Currently, the only method of payment is a card issued by foreign banks (Georgia, Kazachstan, Belarus, etc) or paying with Bitcoin cryptocurrency. Thank you for your understanding.
Yes, we can ship to RUSSIA, however customers from Russia are not able to use the provided payment methods since Russia has been cut off from the global payment system, all cards issued by Russian banks are getting rejected or receive an error during the payment process. Currently, the only method of payment is a card issued by foreign banks (Georgia, Kazachstan, Belarus, etc) or paying with Bitcoin cryptocurrency. Thank you for your understanding.
We use national postal services. More information on shipping can be found in the section shipping and shipping duration.
Information in regards to what payment methods we offer can be found here.
We send an email when the order is registered as well as when the order is shipped so you can get the most up-to-date information about your order. Please check your spam folder if you did not receive any of the emails, sometimes the emails land there. If you don't find the email confirming your placed order within 5 minutes please contact us, we'll resend it.
Please follow the guide on Hondash OBD Bluetooth scanner pairing and troubleshooting.
A DLC diagnostic connector can be found in various locations under the dashboard.
Variants of OBD0 ('88-'91, some models until -'93) had only the 2 pin (SCS service check) connector for self-diagnostics purposes. It does not support diagnostics data transmission, thus you can NOT use Hondash scanner on such vehicles!
Some OBD1 models ('92-'95) don't have any power source in DLC diagnostic connector (3 pin style connector with only two wires connected to it, middle pin and wire are missing). In this case you have to wire the scanner to a custom power source.
Some late ('99-'00) EU Accord/Civic models (OBD2 versions) had only the 2 pin (SCS service check) connector, some of them continued to use the 5 pin diagnostic connector, but without the ECU communication wire connected to it. The 3 pin / 5 pin diagnostic connectors were basically superseded by the standard OBD2 16 pin port located under the steering wheel (or somewhere else under the dashboard).
Some OBD1 models ('92-'95) don't have any power source in DLC diagnostic connector (3 pin style connector with only two wires connected to it, middle pin and wire are missing). In this case you have to wire the scanner to a custom power source.
Some late ('99-'00) EU Accord/Civic models (OBD2 versions) had only the 2 pin (SCS service check) connector, some of them continued to use the 5 pin diagnostic connector, but without the ECU communication wire connected to it. The 3 pin / 5 pin diagnostic connectors were basically superseded by the standard OBD2 16 pin port located under the steering wheel (or somewhere else under the dashboard).
You can leave the scanner connected. However if you're not going to drive for a longer period (more than 2 weeks) it's recommended to disconnect it to prevent possible battery drain even though the power consumption is very small, if you power the scanner directly from the DLC connector, which is hot at all times.
For permanent installation it's recommended to use an ignition switched power source to power up the scanner.
For permanent installation it's recommended to use an ignition switched power source to power up the scanner.
Hondash is still in active development and the feature set is not finalized yet, nonetheless, there are already a lot of functions and features as described on the App & Guides page.
No, Android Auto is not supported at the moment. Nevertheless, the support may be added later at the end of the app development cycle.
No, Android Auto is not supported at the moment. Nevertheless, the support may be added later at the end of the app development cycle.
- Oil Temperature - No, Honda engine does not have an oil temperature sensor
- Oil Pressure - No, Honda engine does not have an oil pressure sensor, only a pressure switch
- AFR - Air to Fuel Ratio - Yes, however the applied conversion of oxygen sensor voltage is based on a generic formula and not oxygen sensor manufacturer's specific data, therefore it's not guaranteed to be accurate and is intended for informational purposes only, you can however input your own calibration data following the guide for protocol configuration; to display AFR on Oxygen Sensor Parameter set "value of" to "Air Fuel Ratio" or "Lambda" instead of "Voltage" in the graph parameter assignment dialog (see gesture tutorial)
- Fuel level - No, the fuel level sending unit is not connected to the ECU
No, Hondash can read/clear diagnostic trouble codes from the engine control unit only.
We recommend using the self-diagnostics procedure to obtain codes from ABS / SRS / A/T control units, as described in the service manual.
We recommend using the self-diagnostics procedure to obtain codes from ABS / SRS / A/T control units, as described in the service manual.
Parameters that do not change (read constant arbitrary/zero value which may trigger alarm) are simply not supported by your ECU (e.g. some OBD1 '92-'95 vehicles don't support Fuel System Status FSS, Calculated Load Value CLV, Knock Sensor KS,...; cars with manual transmission usually don't have a BARO sensor, many EU models don't have the ELD, etc.). Simply ignore those readings as they're not relevant for your use case. Navigate to app settings → Car → Engine and enable/disable engine features to filter out unsupported parameters.
Long Term Fuel Trim (O2FT-LT) parameter reads 0 value on the majority of Honda vehicles from this era. The only explanation we can give you is simply that this is the way the engineers implemented the algorithm for calculating this parameter and it just returns 0 all the time, if the engine operates nominally.
Long Term Fuel Trim (O2FT-LT) parameter reads 0 value on the majority of Honda vehicles from this era. The only explanation we can give you is simply that this is the way the engineers implemented the algorithm for calculating this parameter and it just returns 0 all the time, if the engine operates nominally.
Please follow the guide on Fuel consumption calibration and Gearbox calibration (section discussing gear detection range).
Yes, the app will support newer vehicles via 3rd party scanners that are based on ELM327 chipset or support ELM327 protocol (ETA Q1 2026). The development on a proprietary OBD2 Hondash scanner (for 16-pin socket) has been cancelled.
Currently no, but the app will receive an update to support all ELM327 based scanners (ETA Q1 2026). However this will not be a replacement for the original Hondash scanner as the ELM327 supports only newer vehicles.
| OS | Android 6.0 |
| CPU | quad core processor |
| GPU | OpenGL ES 2.0 |
| I/O | Bluetooth 2.1 |
| Screen | any size and resolution |
Try to install the Hondash app from another source such as apkpure.net, or google "download hondash apk". The Google Play store sometimes incorrectly reports some devices as being incompatible.
Officially, no. While Hondash can run on many of these devices, we do not guarantee 100% compatibility and we offer zero technical support for head unit installations or troubleshooting.
The Technical Reality:
Hondash is developed and optimized for standard Android smartphones and tablets. Many aftermarket head units (particularly budget or generic brands) use non-standard, "crippled" Bluetooth stacks that do not comply with established Android SDK standards.
To save on hardware costs and licensing, these manufacturers often hardware-lock the Bluetooth chip to only support HFP (Hands-Free) and A2DP (Music), while completely omitting the SPP (Serial Port Profile) required for high-speed OBD data communication. If the manufacturer has deviated from standard Android protocols, the app will not be able to "see" or pair with the interface, regardless of your settings.
Category 1: High-Risk (Avoid entirely)
These brands are known for using "crippled" Bluetooth stacks that lack the SPP (Serial Port Profile) required for engine data. They often physically isolate the Bluetooth chip from the Android OS, making it impossible for Hondash to connect:
[Eonon, Nakamichi, Pumpkin, Dasaita, Podofo, Hikity, Binize, and all "Alphabet Soup" generic brands.]
Category 2: Conditional (Advanced Enthusiasts Only)
These brands use "full" Android OS versions and higher-quality Bluetooth chips. However, they are not plug-and-play. Users often have to bypass the manufacturer’s custom UI and access hidden system menus to enable pairing. We do not provide instructions for this:
[Joying, T’Eyes (CC3 series), Atoto (S8 series only), Xtrons (Ultra/IQ series only)]
Our Policy:
- Primary Support: We officially support only standard Android smartphones and tablets.
- Compatibility: We do not maintain a list of "approved" head units. Use of these devices is at your own risk.
- Troubleshooting: If the Hondash interface works on your smartphone but not your head unit, the issue lies with the head unit’s restricted hardware/firmware. Please contact the head unit manufacturer for assistance.
The iOS platform is not supported.
There won't be an iOS version of the app due to high developer fees we would have to pay in order to be able to deliver an iOS app on par with the available Android app.
Apple devices do not allow to use classic Bluetooth connection without the manufacturers of the product (us) enlisting to a special Apple's MFi program (high fees), thus, the only feasible way to connect to Apple devices is to use much slower BLE (Low Energy) connection method, about 3x to 5x times slower than the classic Bluetooth version. We can 100% say now that communication with the Hondash app on any Apple product would run much slower than what is achievable on any Android device currently, even the cheap ones.
Since Hondash works with Android versions as old as 6.0 (2015) we recommend buying a cheap used device (~€30) and use it as a dedicated device for Hondash.
There won't be an iOS version of the app due to high developer fees we would have to pay in order to be able to deliver an iOS app on par with the available Android app.
Apple devices do not allow to use classic Bluetooth connection without the manufacturers of the product (us) enlisting to a special Apple's MFi program (high fees), thus, the only feasible way to connect to Apple devices is to use much slower BLE (Low Energy) connection method, about 3x to 5x times slower than the classic Bluetooth version. We can 100% say now that communication with the Hondash app on any Apple product would run much slower than what is achievable on any Android device currently, even the cheap ones.
Since Hondash works with Android versions as old as 6.0 (2015) we recommend buying a cheap used device (~€30) and use it as a dedicated device for Hondash.
The app requires one-time internet access when you use a Hondash scanner for the first time, or update the app, or clear the app data. Once the online check is complete you can continue using the app without an internet connection.
- if you use the official Hondash scanner, the app is free without any restrictions, but only for the first activated user account; each unit is provided with one free user license, which the app obtains automatically online (when connected to the scanner and the ECU) and prompts you to activate your user account that you sign into; please be informed, once you receive the unit, you must claim the free license by registering the unit and your account in the app within 1 year from the purchase date otherwise it will expire. A claimed license does not have an expiration date and is permanently attached to the activated user account.
- additional user account activation will require purchasing a new user license; that is if you purchase a used Hondash scanner or want to use multiple user accounts you will be required to purchase a new user license (via in-app purchase, €9.99 excl. tax) to unlock the app on each additional user account
- users are authenticated via Google sign-in; in case the Android device does not have Google services an alternative sign-in method (email/password) will be provided automatically (users can opt to use this method instead of Google sign-in)
- when using Google sign-in you can update your account information (email address, etc.) in your Google account dashboard; however when using alternative sign-in method (email/password) the email address, which identifies your account, is not updatable
- you can use multiple Android devices and multiple vehicles with the same scanner; to use the scanner with multiple Android devices simply sign in with the same account (same email address) you used during the first time activation; as long as you are signing in with the same account on each Android device, you won't be required to purchase a new user license
- you can use multiple scanners with the same account
- additional user account activation will require purchasing a new user license; that is if you purchase a used Hondash scanner or want to use multiple user accounts you will be required to purchase a new user license (via in-app purchase, €9.99 excl. tax) to unlock the app on each additional user account
- The app is not free for a Hondata ECU (S300, KPro, FlashPro) or a HTS - eCtune - BMTune ECU; the app will ask you to purchase a license (via in-app purchase, €9.99 excl. tax); however you can use a free trial mode to test the app prior to the purchase. Thank you for your support.
Please check that you're logged into the Google Play Store with the exact Google account you used to purchase the license, on the device that you use with Hondash.
To verify your purchase:
To verify your purchase:
- Open the Google Play Store app on your device.
- Tap your profile icon (usually in the top right corner).
- Go to Payments & subscriptions > Budget & history (or Order history).
- Look for "Hondash - User License" listed as a valid purchased product in your history.
Before contacting us, please note:
- Car Issues: We cannot provide advice on vehicle condition or diagnostics. Consult a service manual or professional mechanic.
- Connection/App Help: Use the Troubleshooting Guide or App Guides.
- Price & Shipping: Click here to see the Total Price and Shipping cost.
- General Inquiries: If your question is not in the FAQ, you may contact us here. (Note: We do not reply to questions already answered in the FAQ).
