RaceChrono v10.1 beta

hasole

aol Thank you! I went and got some more data today for testing 🙂

aol

hasole Send me samples if you run in to bugs 🙂

viewtiful

My license verification fails after updating to 10.1.1, try signing with my goole account but said invalid app license, is it my issue?

aol

viewtiful Custom rom, rooted phone, or an unlocked boot loader? The new Play Integrity API (used for checking licenses) does not allow any of those. Please contact support through the website, and I will arrange you a license.

viewtiful

aol I quite the BETA program and install the stable version, working now.

aol

viewtiful The beta 10.1 uses Play Integrity API as new, and we are not going back. So we need to fix the issue through support.

viewtiful

aol I did unlock the boot loader, thank you I have contacted support through the website.

aol

The iOS beta is now out too, let me know through the website feedback form, if you want to test.

Ensky

aol I also cannot install the app for my bootloader unlocked pixel 5. The play store shows "this app is only available for your other devices"

hasole

Thank you for the latest update for Android.
Files can now live in the media store under Movies/RaceChrono instead of DCIM/RaceChrono which means that Google Photo's won't back up the videos 🙂

Confirmed copy of SD card into Movies/RaceChrono links to my session after importing it from the Media Store in Add files.

Thank you for this.

dustinsterk

dunit121 I second this...there are many guys that are still running Hero 3+ devices. The camera still work perfect and no need to upgrade and turn into E-waste. Can you just keep the code in place and call it 'un-maintaned'?

aol

dustinsterk No that's not how we operate. Everything must be tested periodically. Otherwise we'd end up with a garbage app. The code was removed as we needed a major overhaul on the GoPro remote control feature, to make it work better.

You can still use your cameras, and the videos on your sessions, just not the remote control feature.

dunit121

aol If testing is the burden, do you need help creating automated testing for HERO 4 support? If so, let's talk.

hasole

Confirmed if you have multiple dji gps videos for one session. It links them all correctly when you add it.

Although 16gb per file makes it hard on the phone.

aol

dunit121 It's the whole deal, code maintenance, refactoring when needed etc. We do have unit testing, but it's hard to test on real hardware automatically. Would need a humanoid. Also still wouldn't make sense to keep supporting 12 year old device. Thanks for the offer though! 🙂

aol

Ensky Unfortunately that is how it is now. The Play Store now filters out devices that would fail the license check.

The phones now need to be unrooted with locked bootloader and original google software. This wasn't a direct choice by us, but requirement of the new license validation by Google.

borazy

Hello
Does this mean the phone needs to be constantly connected?
Until now, I've been using RaceChrono without a phone subscription, but now it seems I need to validate my license online every time?
test on Iphone

aol

@borazy No, the license is validated with intervals. More often at beginning, less often later, up to 90 days. There was similar logic in the old system too. The app needs data sometimes so tethering to main phone is recommended.

ChrisI

If I use "Import" from the main screen, and import DJI video as "DJI Action sensor data", a new session is created, parsing the GPS data from the video. However, I cannot find a way to auto-sync the video to a pre-existing session (which was recorded by Racechrono while connected to a Racebox + OBD2 dongle).

I did notice that the auto imported session imported with the wrong time, as displayed in the 'start' column when looking at laps in the session. The actual time was 12:54, while the DJI-imported video says 13:54.

Perhaps this is the source of the issue syncing to an existing session?

I can provide exports and video if that would help.

aol

ChrisI The DJI data format is a bit ambiguous, due to bugs in the firmware. So there's some guessing involved. It seems to fail in your case. Worth checking if the camera time is correct, and it should be working after that.

The auto-sync is done when the new file is added. If it comes up as "not synchronised" it's failing for some reason.

ChrisI

aol You're correct. I was testing with older footage from last year, and the clock must have been wrong on that sample.

I went out today for my first lapping day of the year, and once I copied the video to Movies/Racechrono and linked it to the session, it synchronized automatically (I didn't even need to pick which session resume, which was super nice).

Also, thanks for moving from DCIM/Racechrono to Movies/Racechrono. It's a welcome change.