I’ve wondered why my trips are not fully recorded and noticed the “start-up sound” is played some time after starting the engine so I measured the time from starting the engine until that sound (which I assume to be the “device-ready” signal) and noticed the lowest time to be around 127s and up to not playing the sound within 300s after which my trip ended.
Most of the time the time span was around 127-160s.
- Is this intended to be that high?
- Are there plans to reduce this time (possibly through running all the time with lowest possible power consumption)?
I didn’t file this as
Troubleshooting as my own car-entertainment-PI (which in the meantime got deprecated and re-used in another project) had similar boot times and I found no solution for this. On the other hand side previously I’ve used a proprietary dongle by a German company (not containing a PI) which instantly started recording the trip.