Good thinking. I imagine the installation process is the same.

 

Still curious as to what’s in the bulletin…. Other than maybe forgetting a comma and adding it in. It was updated today…. So we are at the first R version. It’s now 15-305-22R.

 

ok, answered my own question.

I reviewed the TSB from november. There are some fixes for the 2023. The numbering of the hardware identifier isn't a surprise, a few mentioned their version in the megasuperduper software thread.

anyway, I created a reference thread for the firmware history, Fixes are listed over there, just like my other reference threads. I'll update that like the 2020-2022 version, so people will have a handy link for running update/fix content.

This thread will have the better discussion around everything CP1.5 software related.

TSB attached in reference thread.

ok- back to your 2023 software discussion.

 

ok, answered my own question.

I reviewed the TSB from november. There are some fixes for the 2023. The numbering of the hardware identifier isn't a surprise, a few mentioned their version in the megasuperduper software thread.

anyway, I created a reference thread for the firmware history, Fixes are listed over there, just like my other reference threads. I'll update that like the 2020-2022 version, so people will have a handy link for running update/fix content.

This thread will have the better discussion around everything CP1.5 software related.

TSB attached. Maybe someone will get the updated version before I do and drop it in the thread here. That would be cool.

ok- back to your 2023 software discussion.

Thanks for updating this. At least we now have the TSB!

 

I am so confused. I have the SUBARU OUTBACK 2022 XT. What is the latest firmware?
When i ask my dealer they brush me off. Last time i went in it took them 2.5 hours to update it.
Thanks for the help

 

This is for the 2023 model year. It is a different hardware version of the headunit than in the 2020-2022 model year.

the 2020-2022 model year discussion thread can be found here. Questions about firmware, software, etc is there.
I have a 2020-2022 model year lookup/reference thread here, that tracks versions of the firmware

 

yep, that’s the one! and they totally didn't correct what I thought they would... haha! slackers.

 

yep, that;s the one! and they totally didn't correct what I thought they would... haha! slackers.

View attachment 557395

I also grabbed the software. I updated my original post with details and screenshots.

 

Firmware hasn't changed. No additions or changes to the existing list. Note that deletions don't show up as highlighted because they don't exist - things can just not be there anymore in a new revision - one thing to look for if you keep and compare the older documents with the newer ones.

They updated the SOP (start of production) firmware revision numbers. Still reusing older screenshots for the example of how to save the extracted files - they just made the screenshot really blurry so you can't read anything on it, to avoid confusion. or something.

 

I uploaded the firmware files for MY2023:

2023 - Google Drive

drive.google.com

 

I've had no luck with the pkg files on the google drive. Any chance you can upload just the 2 files (MSOC and *.csv) for the WMM (medium headunit) to test if I'm having the same issue?

Nice wallpapers by the way

 

How was the update different from the 2020-2022 models? I see there is only the single file required now? goes in the root, or a subdirectory on a thumbdrive...?

 

The accompanying document (also uploaded to the same folder) mentions this on the first page so I guess it's different from previous versions and model years:

EDIT: Reading the doc farther, it asks you to copy all the files to USB. I guess the head unit is smart enough to pick it's applicable firmware version?

I have pulled the update from google drive while I take a closer look at the doc.

 

yeah, I had read that earlier - and I was curious if there was an original archive with a folder structure, or it if was just the files over at subarunet. the document doesn't say, just says it should match. I guess the first person to try an update will find out!

 

I pulled the files from gdrive. I will try to update with all files present and see how it goes. I will re-upload the files once mine finishes successfully.

 

Edited thread title and stickied.

 

You know that 2020-2022 N/A is just going to confuse people.

Subaru does send emails out if there is an update. An example email I received:
View attachment 557463

That was for the WFi update, which WAS something different. I've never received any notification from Subaru for the USB only updates.

 

The Ascent will likely have it on technical service bulletin, separate from the outback version. The WRX and BRZ service bulletins were released around the same time the outback one was. If you look at the screenshot there, the WRX and BRZ have separate file downloads. I expect this to be the same for the Ascent.

This is different than in the past, where the Ascent had the same head unit as a 2019 outback, and shared that same technical service bulletin.

The other thing that is missing so far, is the 2023 outback wilderness. I don’t see any files for it yet and it is not mentioned in the technical service bulletin for the 2023.

 

Reading through these comments, I still have a question. I'm relatively new to the modern tech-filled cars. Is this a "hack" that allows each owner to update the software unofficially at home vs going to the dealer? Or is this how we do the updates, in general? Is this for all '23's? Thanks!

 

No, it is not a ‘hack’. Owners follow the same procedure and install the same software dealers do.

 

Are the update files the same for US and Canadian markets? Or do US and Canadian owners get different software updates? As far as I understand, Subaru of America and Subaru Canada as separate entities (even though the vehicles for both markets are manufactured in the same manufacturing facility).

 

so the original archive was just one archive for all three files, and it looked something like this when extracted? Like it was supposed to be the one drive to rule them all update all the different versions?

So maybe creating the file structure on the thumbdrive would work? Or not, if it's a reading the thumbdrive problem.

 

Makes sense but when I did mine I only put the one pkg file at the root and that was enough. Weird that it was not the same for everyone.

 

I don't know if it makes a difference, but I seem to recall having other things plugged into the other USB port could cause problems with the update with the earlier unit. This headunit is a bit different, so maybe that's not an issue. Easy enough to unplug anything else while you do it I guess.

 

I just tried again without having my phone plugged into the USB as well...it works.

 

I have read the Car Play is wireless only on the 2023. It can use the usb cable to set up Car Play, but not to actually use car play.
Does anyone know if Android Auto is wireless only too, or can it be used with a cable?
Thanks.

 

I keep seeing this mentioned in multiple threads that AA and CP will ONLY connect wirelessly on the 2023's so I decided to go play with it. I have an Android phone, so that's what I'm testing with but I'd expect CP to behave the same...

If I let it auto connect wirelessly and then toggle WIFI off it disconnects as expected. If I hit the AA button on the dash after disconnecting, a prompt on my phone comes up to reestablish the wireless connection. If I accept the prompt the wireless connection starts up again and toggles my WIFI on in the phone.

However, If I simply plug in the phone to the USB outlet after toggling WIFI off on the phone, AA connects immediately and my WIFI stays turned off.

So yes, you can still connect to AA via a wired connection if you want.

 

It doesn’t work on an iPhone unfortunately, I just tried this in my 2023 and CarPlay never resumes after connecting to the USB cable. 🙁

 

I picked you the Transcend TS64GJF790BK listed in the TSB, but it still doesn't recognize the software after formatting to NTFS, and placing the files on the drive. I'm leaning towards it's an issue with the Onyx version because of the added Xmode 2 feature. Maybe The Onyx needs a special version of the software like the Wilderness which doesn't falling into the normal 3 catagories (B,M,H).

 

Mine is an Onyx XT though and it upgraded fine.

 

The firmware was released November 11th, so I’d expect it to be on units on the production line around the same time.

 

I'm new to Subaru software, but was looking forward to this since I found the forums a few months back - thanks for everything you all do Does anyone have a feeling whether these updates contain undocumented optimizations, or is it strictly the fixes noted in the firmware history thread?

 

Does anyone have a feeling whether these updates contain undocumented optimizations, or is it strictly the fixes noted in the firmware history thread?

What is fixed/changed is listed in the TSB, Appendix E.

 

Successfully updated my `23 Touring XT. It took several attempts to get the car to read anything off the USB, but when it worked it was fast and easy. I had to recreate the directory structure and include all files as @walker indicated in diagram in this thread. It did not work with just the file, the manifest and file, or without directory structure.

I used a Sandisk SDCZ73-128G-G46 128gb drive.

Thanks for the upload @chvvkumar !

 

Really weird how mine would not detect the update with all files on the drive. I chalk it up to the ghost in the machine.

 

I know @walker put up a FAQ entry on his firmware source page about the '23 Outback Wilderness not being listed in the TSB, but as someone who's having a number of Bluetooth pairing issues with the "older" 013-282 firmware that match fixes in 013-580, does anyone more knowledgeable than me have thoughts as to options?

Can I just follow the procedure in the TSB as written, or is there Wilderness-specific firmware I (and, assumedly) the dealer should be waiting for?

 

I know @walker put up a FAQ entry on his firmware source page about the '23 Outback Wilderness not being listed in the TSB, but as someone who's having a number of Bluetooth pairing issues with the "older" 013-282 firmware that match fixes in 013-580, does anyone more knowledgeable than me have thoughts as to options?

Can I just follow the procedure in the TSB as written, or is there Wilderness-specific firmware I (and, assumedly) the dealer should be waiting for?

Yes, there is Wilderness specific software and the software @walker mentions is the same software the dealer has access to.

 

Further notes: Update did fix my wonky pairing issues with my Google Pixel phone, which is great.


I've ripped apart the firmware update package, to see the files/programs/configs on there (because I was curious). The update is really a full replacement for one of the multiple partitions on the device's storage. It is an absolute mess in there - lots of poorly-written system shell scripts, debug symbols left in binaries, Adobe AIR for system graphics/text, etc. Explains a lot of the sluggishness, even though the CPU is a quad-core 1.8GHz Intel Atom.

Fun fact: QNX OS runs on the bare metal, and talks to the ECU and other critical car systems via the CAN bus - and runs a hypervisor (virtualization server). The infotainment and UI/screen are all run by a heavily customized Linux OS, which is a guest OS on the QNX hypervisor. This attempts to ensures that infotainment functions won't overstep important car things, and its the Linux OS that gets rebooted when you hold down the Power button for 10 seconds.

Denso seems responsible for this nightmare - it looks like they were the integration partner who sewed together the parts of others' software (TomTom, XM Radio, etc) into this Frankenstein. I haven't looked too closely at the underlying hardware, nor attempted to communicate with the unit itself - just peeked at the files. I'm sure I will at some point in the future when I get bored.

 

I've ripped apart the firmware update package, to see the files/programs/configs on there (because I was curious). The update is really a full replacement for one of the multiple partitions on the device's storage. It is an absolute mess in there - lots of poorly-written system shell scripts, debug symbols left in binaries, Adobe AIR for system graphics/text, etc. Explains a lot of the sluggishness, even though the CPU is a quad-core 1.8GHz Intel Atom.

I’d be curious what differences with those things there are between the CP1 and CP1.5 units. Looking at the published specs from subaru, the processors / chipset / RAM is the same between the two. Another fun thing would be to find different updates and see if any of it got better, or worse, as updates progress.

thanks for the report on it working - I updated the CP1.5 reference thread section about the wilderness. Glad it fixed your problems.

 

Has anyone that has upgraded to the latest version noticed an improvement with the driver recognition? Previously, I had a success rate of about 30% and it would be 0% if I was wearing a different hat of sunglasses. Now, I think I'm getting 90% success rate and it has worked with me wearing different tuques, hat, and sunglasses.

 

Nice, haven't paid attention. What if your other gets in the seat, does it also recognize as you?

What I did notice and I'm not sure if it's related or coincidental, is that for the 1st time in about 3 month, it happened to me on 3 occasions so far that the Android phone wouldn't connect. The phone doesn't see the car's Bluetooth entirely. Stop and start doesn't help either. I manage to connect it back only by going into the device list and adding it as a "new" device, so it re-pairs it