by Anura Guruge
on November 28, 2021
This was the first time I had gone looking for the software versions in my accursed 2022 XC60 — which I detest because of all of its niggling faults.
The top screen absolutely FLOORED me. I have, in nearly 50 years of association with computers, NEVER, EVER, seen a software build number that long, that cumbersome & that non-intuitive. Don’t try to blame it on Google. Here is proof in 2 parts:
Click to ENLARGE. Android build number on my Google Pixel 5 phone.
As you can see from above 2 images, Google doesn’t use overly long build numbers — &, moreover, they are intuitive. Take the ‘SP1A.211105.003’ build number on my Android 12 Google Pixel 5. The ‘211105’ is a date: 2021/11 (i.e., November)/5th day. That makes sense. This was the November 2021 security update. Bingo.
With Chrome, Google uses a MASTER version number based scheme — in this case ’96’ being the master version.
The 45 ‘digit’ scheme that Volvo is using is explicable & inexcusable.
Even vehicle VIN numbers are only 17 digits long. The Volvo scheme is 2.6x times longer!
Just shows inexperience & stupidity.
Yes, I have hands on experience managing commercial, software release build numbers — once for IBM & then many years later for Wang. You have to keep the release numbers ‘manageable’, meaningful & easy to identify. The Volvo scheme meets NONE of these requirements.
It is also FASCINATING & scary as to HOW down level the Android software is.
My Google phone has been running Android 12 since October 26, 2021.
This bloody XC60, delivered to I on November 2, 2021, is running Android 10 from 2019! Moreover, it only has an August 2021 security patch. Prior to delivery, the dealership, SUPPOSEDLY, updated the software. That was November 1. I should have had, at a minimum, the September 2021 update.
Well, something to keep an eye on.
One thing is sure. Volvo has a HUGE mountain to climb when it comes to mastering software. In the meantime we, the consumers, who were stupid enough to buy Volvo, will suffer.
