Q&A - SoundRacer Android app
Do you have any questions regarding the app that have not been answered here? Please send your questions to appsupport (at) soundracer.se
Always install the latest app version prior to any other measures. If we make changes to the app, it will only be to the current version at Google Play. The Q&A is primarily updated with the newest version in mind.
Will this ELM327 adapter: Latest Version V2.1, work with my car and your android app?
No, the app is currently compatible with version 1.5, the newer version 2.1 seems not work well with the app. We are working on it.
The Bluetooth adapter picked from the list does not seem to work?
If the BlueTooth icon not turns green then your phone has no connection to the adapter
A) The OBD-II device has a bad connection. Try removing the adapter and connect it again..
B) The selection routine is stuck in some phase, and you could try to restart the app and try again.
C) The correct device name might not be picked from the list.
D) The device name is the same for two different OBD-II devices. Then you have to unpair and select and pair the correct device again and then restart the app.
Does the OBDII app work in my car?
If the OBD icon does not turn green, then the app has a problem with the OBD protocol
Cars have different OBDII protocols. They differ in connection speed and data transfer rates. Thus the connection might take a longer or shorter time and the update rate of the RPM differs. This will make the sound response different in different cars. There is always a little time lag due to the many communication steps in the protocol, Bluetooth and the app program. If compared, the real SoundRacer will thus always have a faster response time due to the direct hardware connection.
How does the OBD-II Automatic Protocol search work?
The new Automatic routine is completely different from the previous versions of the app. It seems as if most of the SoundRacer app users do not know which OBD-II protocol to use, and thus have to depend on the Automatic routine. The routine now makes 3 differently thorough searches of all 12 protocols. It first makes a Fast, then an Intermediate and at last a Thorough search. The Fast search only progresses in the beginning of the progress bar, the Intermediate to the midpoint and the Thorough all the way to the end of the progress bar. The fastest of the protocols are the CAN protocols and they are tested first. The ISO 9141-2 protocol unfortunately takes the longest time to connect and therefore comes in the end as number 12. You must have patience to let the Automatic routine work because it repeats the connecting steps many times in the last stage, and thus takes a long time to finish. When the connection is established the correct protocol name is saved as a default, and thus the next time you try to connect this will be the protocol that is tested to begin with.
How do I know which OBD-II protocol my car uses?
A) The car manual could include the name of the used protocol.
B) If you have the Torque Pro app installed, and it works with your car, then you are able to see which protocol it has found that works in Adapter Status/OBD Protocol.
C) Here you can find more information about protocols:
None of the available OBDII protocols seem to work. What should I do?
The app covers the most common OBDII protocols:
SAE J1850 PWM
SAE J1850 VPW
ISO 14230–4 KWP (5 baud init)
ISO 14230–4 KWP (fast init)
ISO 15765–4 CAN (11bitID 500Kbaud)
ISO 15765–4 CAN (29bitID 500Kbaud)
ISO 15765–4 CAN (11bitID 250Kbaud)
ISO 15765–4 CAN (29bitID 250Kbaud)
SAE J1939 CAN
User1 CAN (11bitID 125Kbaud)
User2 CAN (11bitID 50Kbaud)
A) It would be kind of you to tell us about it, so that we might have a chance to act on it. So please send us the data on which OBD-II protocol your car uses and that is missing in the list above.
B) If the protocol that matches the one in your car manual actually is in the list, but does not work for you, please tell us that too. We might come up with an answer to how to make it work in your case.
My HTC Magic does not work well when I use the Tilt mode. What is the reason for this?
There seems to be a hardware interference problem in the HTC Magic and HTC Dream. When one uses the built-in speaker the tilt sensor seems to get very unreliable. The louder the sound the worse the problem is. But if one uses the headphones there is no problem.
More about this particular problem: Accelerometer Speaker Interference Workarounds
Finally our retailers
have SoundRacer V
and SoundRacer X
in stock again.
Thank you for your
SoundRacer® is registered trademark