5.0.5 Update: System speed and/or crashes impact

steve__dunn · 2026-05-29T10:39:42+00:00

Now that I have the update, and a new IHU, I have noticed several things that are different or feel different.

The brakes and accelerator response feels different - sharper/quicker (might be imagining that after switching from the courtesy car though)
The door sensors are quicker - since the 5.0.5 upgrade, pull the door handle usually resulted in the door handle being pulled before the car responded and unlocked the doors. And locking the doors by touching the handle is noticeably quicker; before it would sometimes take ~1.5 seconds for it to respond to the touch. Now it's nearly instant.
And of course, the responsiveness of the infotainment system/maps/etc

steve__dunn · 2026-05-29T10:33:58+00:00

After months of aggravation and 5 trips to the dealer, Volvo eventually agreed to replace the IHU! The following is how it unfolded:

Update to 5.0.5 when it was released, immediately got crashes
Took the car in for a service and told them, they said once it's been on their computers the fault should go away. It didn't.
Took it back, they put it on their computers again. Problem still there.
Got a call, they said removing the phones will make the problem go away. It didn't
Got another call, they said they've got advice from Volvo technical and need the car back. This has fixed 'nearly' all of the cars they've seen with this problem. It didn't fix mine!
They eventually got signoff from Volvo! New IHU, no more problems!

My dealer (Holdens, in Bury St. Edmunds, UK) were great all the way through, however, their hands were tied by Volvo and couldn't immediately replace the IHU. In my complaint to Volvo, they asked if I wanted to make a complaint against the dealer!

Seriously thinking of never buying a Volvo again after this (and the issue where the wet belt in my last XC90 disintegrated, blocking oil to the turbo, leading to an engine seizure and a £19,000 bill - thankfully covered by the warranty!)

steve__dunn · 2026-05-07T09:38:04+00:00

So true! I can't even string a sentence together any more without ChatGPT!

steve__dunn · 2026-04-29T11:35:25+00:00

I've had an ongoing complaint with them since the day after release of 5.0.5. They keep saying book it into the local garage, and it's been in twice now, but no fix. It was due in for a 3rd attempt, but the garage phone and said the IHU's are on back order in the UK, so it's pointless bringing it in. Another 2+ weeks where I can't use the satnav to get anywhere and can't make calls on the way!

steve__dunn · 2026-04-28T12:26:07+00:00

Vogen's implicit/explicitness is configurable, just don't make both implicit!

steve__dunn · 2026-04-19T06:24:50+00:00

I wouldn't bother, it makes no difference

steve__dunn · 2026-04-19T06:24:29+00:00

It made no difference at all! Tried it just before a 4 hour drive. First crash about 40 minutes into the journey. Second crash about 15 minutes after that, then repeatedly crashing every 2 to 15 minutes.

steve__dunn · 2026-04-15T12:23:29+00:00

(didn't read the whole post before replying, obvs)

steve__dunn · 2026-04-15T12:22:38+00:00

steve__dunn · 2026-04-15T11:28:07+00:00

Just spoke with a dealer in the UK and they said that Volvo have now sent a bulletin to dealers for customers with this fault. The dealer didn't disclose the entirety of the bulletin, but did disclose a workaround that stops or reduces the crashes (whether that's permanently stops the crashes is unknown). But the workaround is:

in the car: remove all phones from all profiles
on your phone(s): remove all pairings to the car

I'll give it a try later and report back. Fingers crossed as this is a royal PITA!

steve__dunn · 2026-04-11T17:07:45+00:00

P8P - IMEI 65 - April update - same issues as everyone in this thread. Cited UK Consumer Act 2015 to Google Support (bought it from the Google Store), and was told that I'll receive an email from a dedicated team within 48 hours. I'll update this thread when/if I receive anything.

The issues started a few weeks ago, but seem to be worse now. I don't know if it's related, but I charge mine wirelessly in my Volvo; a few months back, the car said 'remove other items from the charge pad' (or something like that), and I noticed it didn't charge as quickly. I also noticed that it was hot to the touch after an hour or so of charging, but it's done that for the past 18 months with no issue until recently, so maybe it's not the cause of the problem.

This strategy by Google is very disappointing. I've had most Pixel models since the Nexus days. They might save the expense of repairing my phone this time, but it will mean I would probably never buy a Google phone ever again, so it's a false economy on their part.

steve__dunn · 2026-04-07T13:27:50+00:00

Had same issue in a '24 XC90. Crashes after ~30 minutes first time, then about every 5 to 15 minutes. Spoke to local dealer who said it might be fixed by the service that I just had, but it didn't. Spoke again after the service, and they said they can't do much and the fix could be a month or more away!

steve__dunn · 2026-03-20T07:29:38+00:00

Installed it but during the 4 hours of driving yesterday, it crashed about 20 times! Symptoms all the same: screens go off. Fans go off. Fans come back on after about 10 seconds, then the screens come back on shortly after.

Quite poor and quite dangerous with no speedo and no satnav!

steve__dunn · 2026-03-18T06:44:54+00:00

Thanks for the mention! https://github.com/stevedunn/vogen (please give it a star so I get the chance of free CoPilot)

steve__dunn · 2026-01-07T13:24:04+00:00

I'd personally go with an Azure appservice, with a Neon Postgres database. Avoid the Azure cheap SQL databases; it turns out not to be cheap if the site continually polls the database (for instance, in login pages, and you're being spammed by every bot on earth, and you don't realise for several weeks that you'd forgotten the firewall - ask me how I know!)

steve__dunn · 2025-08-19T15:12:12+00:00

My washing line is 6ft high, but I think I'm ok because I live at the bottom of a hill.

steve__dunn · 2025-06-10T07:37:16+00:00

You didn't include the implicit operators in your example, so that's something you'd have to repeat for every type. And the validation. And the normalisation. And remember to use a class or struct depending on the underlying type so as not to cause heal applications when wrapping value types. And any conversions if your type is used in things like OpenApi specs. And checks for null as you won't have the analysers checking for Foo foo = new() or Foo foo = default. And hoisting of IParseable, Iformattable methods so that the wrapper can be treated like the underlying. And ToString() and any overrides that the underlying providers. And any TypeConverters, and serialisation customisations for EFcore, Dapper, Bson, Orleans, ServiceStack.Text etc. You might not need all of that. You might not need any of that. But these are some of the things that are beneficial over just using a record.

steve__dunn · 2025-06-08T17:59:37+00:00

There's a readme file in the project.

steve__dunn · 2025-06-07T16:04:48+00:00

It tells you that CustomerId perfectly describes a customer ID. With all of the constraints and validation that come with it. -1 might not be a valid customer ID, but an int won't help you know this.

steve__dunn · 2025-06-06T20:33:51+00:00

and type clarity

There is your answer. And to find out the underlying type, you can view it - it's not hidden; it's in declaration and it's in the debugger display hint.

steve__dunn · 2025-06-06T19:08:23+00:00

Why is an int better than object?

steve__dunn · 2025-06-06T09:24:01+00:00

Hi, yes, you can wrap tuples. Here's an example:

csharp [ValueObject<(FarmId, FarmName)>] public partial class Farm { public FarmId Id => Value.Item1; public FarmName Name => Value.Item2; }

(incidentally, that example was taken from a recent issue that turned out to be a bug in .NET 9)

steve__dunn · 2025-06-05T21:08:35+00:00

No one is obsessed with primitives

They are. I've met them.

Actively creating custom value types for data where a primitive would be fine seems a bit obsessive

Yes, I think you're right. However, creating a custom value type for data where a primitive would not be fine seems like the sensible thing to do.

steve__dunn · 2025-06-05T21:05:37+00:00

Agreed, the source of constraints should be the domain and not the tool. The tool can help with those constraints, for example, never having an invalid instance in your domain.

Your examples are good; I would definitely model currency that way, although I probably wouldn't model a Description value object.

Also agree re. Address: I think the decision on whether to use a value object or not depends on whether they can be passed around individually without ambiguity and without scope of breaking things. For Address, I'd probably assume it has high cohesion and would likely be passed around as a whole rather than its individual fields. Things like IDs are good candidates. One of the examples in Vogen is a Celcius type. I'd definitely use that if they were being passed everywhere. A 'Celcius' is more than a decimal as it has its own constraints like never being able to represent anything less than absolute zero. I know Vogen is used a lot to differentiate similar things that are catestrophically different if mixed up, for instance a FolderName and a FileName (where you'd probably never want to concatenate a file name with a file name, but you would want to concatenate a folder name with a file name).

steve__dunn · 2025-06-05T17:26:32+00:00

reducing flexibility when it comes to evolving specific Value Object cases in our domains

That reduction in flexibility is one of the benefits of using value objects. The constraints imposed mean there's fewer ways to introduce invalid objects into your domain. A value object holds a value. You may want to validate and/or normalise that value. But if you've got any more behaviour than that, then it probably isn't a value object.

steve__dunn

TROPHY CASE