So I understand the overlaid video does. It come with a valid video frame while audio works. This will be due to encoder/decoder incompatibility. For Android, LapTimer has two options selectable in Expert Settings. using hardware encoding: faster, lower quality, will fail for smartphone with unexpec...

Which smartphone do you use and has the original video been recorded with the smartphone cam?

Hello, Track sets are stored on LapTimer's Server and replicated to your smartphone regularly. You can force a download of the latest set using the Refresh button in LapTimer ‣ Administration ‣ Add-ons. Track configurations should be the same for all LapTimer editions, we do not filter these - at le...

Hello,

The database needs to be reset temporarily. Please see this FAQ and do not uninstall the app: viewtopic.php?t=6176

Harry

Please try it yourself. You can use the free Harry's GPS/OBD Buddy for this. In case it works, LapTimer will too. We cannot support specific Android implementations. There are simply too many. So LapTimer expects certain features to work as provided by standard Android systems - e.g. the location se...

Thanks for sending. Communication between LapTimer and the car is working. However, none of the standard PIDs are provided - which is as expected for a BEV. Parameters like MAF, MAP, EOT, ECT make no sense here. Parameters like RPM, VSS, TPS could be provided (and are part of the OBD standard), but ...

Not supported out of the box but I assume you can add it as Custom BTLE OBD device. The parameters are listed here: https://dauntlessdevices.com/support/dauntlessobd-developer-api-info/ (section "Wireless Communications: LE Mode") Help on how to enter them is available in http://downloads....

I have never seen this. It sounds like the Dual cannot connect to your iPad and Apple's Mfi program. This is a special certification required by Bluetooth SPP devices (like the Dual) and iOS / iPadOS devices.

This is a problem with bus communication. From the dialog above we see the adapter is recognized and LapTimer is able to exchange AT commands successfully. What doesn't work is adapter / car communication. This is usually an issue with automatic bus protocol detection LapTimer uses by default. Inste...

Thanks for reporting. This is a script error I could localize easily. It will be fixed for the next bug fix release. It will not occur for everyone (and didn't during testing) and is related to error handling that needs to be done for "not perfect Bluetooth conditions".