It's the January security update version ending AXL2I didn't hear about the Samsung update, where can I get more details? I'd like to know when that update gets applied!
TMO S22U and I just got the update this moring.My S22U is on the Dec 21 update so i can't answer.
Strange, the update installed this morning and everything went back to fully working without my needing to do any more changes.I got the update but so far still not working. I will give it sometime after I drive the car to see if it will connect. If not guess I will have to delete PAAK and create a new one.
This is a Smasnug issue (I have an S22U as well): update ending in EXK_(the last character varies between models/locations. In your case, it is an A) breaks PAAK and update EXL_ fixes it. I just received the EXL_ update this morning for my S22U and PAAK works flawlessly again.I have an S22 Ultra, and it has been working perfectly ever since I got the car a year and a half ago. I just got the Samsung update: S908BXXSDEXKA and now my PAAK doesn't work. If I reboot the phone, there is a very short window in which I can use the phone as a key, and then it stops working. Android Auto etc works as usual. This is so frustrating. Am I really supposed to start using the physical fob for the first time since getting the car?!
If your phone is an unlocked model, you can try using Odin (Samsungs Firmware Installation Software) on your computer.Argh. I hope I get the EXL-update soon thenI only got the EXKA-update yesterday or the day before ...