CPR

Twice in 2 weeks, my doors wouldn't open, after using my remote start
Had to remove the key manually, & open the door
At which time the engine shuts off
Thoughts?

oldsnwbrdr

I’m taking advantage of the Acuralink trial period, the day I needed remote start the most, it didn’t work. Tried starting my car using the app during a cold ride from the airport to my parked car, only to get a message about poor reception or something, even though it worked from this exact location a few weeks earlier.

CPR

As the saying goes; "technology, is a beautiful thing"
When it works

oldsnwbrdr

Yesterday I tried remote starting my car using the app, and it worked. But it locked me out of the car. Nothing I did with the key fob or touching the door handles would unlock the car. I had to turn off the car using the app to finally be able to unlock it.

I will not be paying to renew my Acuralink subscription.

oldsnwbrdr

Update… remote started using the key fob today. Again the car wouldn’t unlock for me with fob in hand. Had to stop the car using the fob.

ApexBlue

In my experience, you have to make sure to lock the car first, then remote start it. Whether using the fob or the app.

I do not have remote start via the fob, only via the app. The first few times I tried to start it using the app I had the exact same issue you did. The doors would not unlock by any method until after I stopped the car via the app.

On a whim I tried locking the car first via the app, then remote starting it via the app. Worked like a charm, and the driver’s door unlocked when I grabbed the handle, as it normally does.

I can replicate the undesired behavior at any time by just starting it without locking first.

Locking it first, then starting it works every time for me.

oldsnwbrdr

Thanks for the input Apex. This should absolutely not be necessary using the app, but I do know when I had the issue while using the app that my car was unlocked in my garage.

I don’t think you can remote start your car using the fob UNLESS you first lock the car. I’m 100% certain I did that yesterday. But if you can actually start the car using the fob without first locking the car (I’ll experiment today), I guess it’s possible my car didn’t get the lock signal yesterday.

ApexBlue

Agreed it should not be necessary when using the app, since the app already knows if the car is locked. I assume they were trying to make the two methods consistent? Weird because a couple years ago I had a Chevy SS that had remote start via fob as well as the OnStar app. When using the fob (same as Acura) had to lock first then remote start, however using the app you simply remote start it.

CPR

IMHO, you need a fairly strong IOS, or Wifi signal
for the car to connect properly
I'll try it tonight, in 10* cold, & see if it works
That, & extreme heat, are why I pay for it

frainc

Happen to me also today, had to use the key and car stopped. Used it tonight and worked fine. As they say, "Shit happens"

kean

It happen 2x already since I got the car. When I start it through app I dont lock the car on the app and able to start then also can open the door. But as I said 2x it happen that I cant open the door even using the fob to unlock it...nada..need to stop the car by the app so that you can open the door.

jwtarbaj

I submitted a ticket with Acuralink last week. They called and asked questions about it. It had been so long ago I couldn't answer most of them. They say they are working on the problem and it could come as an app update, an OTA update or a module update meaning a dealer visit to swap.

oldsnwbrdr

Locked me out again yesterday. This crap is so annoying it turns me off to the brand.

jwtarbaj

Report it to them. The more data the faster they ought to be able to resolve it.

ValB175

I get locked out with the remote and app. It’s really ridiculous man.

oldsnwbrdr

I opened a ticket using the app. Suggest everyone follow suit.

jwtarbaj

How often? I've been locked out a total of 3 times now Since late April 2021 It's not an all the time thing from anyone I've heard about.

kean

Submit a case ticket to acura using the app. It happen to me again yesterday.

oldsnwbrdr

BTW my Apple CarPlay refused to connect after remote starting the car. Don’t know if that’s connected but wouldn’t doubt it, CarPlay working is a coin flip regardless.

ValB175

I’ve had the car since Nov 21’. My rough guess is 7-10 times at least. The occurrence’s are usually close to each other - Meaning if it happens once, it’s likely to happen again on the same day. After that I may go a couple of days, even a couple of weeks with no issues.

It happened on 1/28, 1/14 and 1/11. I started recording vids to keep record just in case my dealership can’t replicate it.

jwtarbaj

The dealer won't ever resolve it. The software people at Acura have to fix whatever is wrong.

I've seen people say to do the doorlock before the Start command then it seems to help.

oldsnwbrdr

I’ve figured out in my car, whenever I remote start the USB Is disabled. This makes it impossible to use a USB music drive or CarPlay unless I reset the infotainment or restart the car.

vtgearhead

Thanks for solving a long-standing mystery! I believe I'm plagued with the same software defect. I use the feature only rarely, but after reading your post I realized that all the no-CarPlay episodes have followed a remote start. And, I'm seeing the no-unlock bug on occasion. I've been able to work around it by first turning the car off from my phone. It responds to the fob after that.

I also have no faith that these problems will be fixed. They're already on to the next model year.

mvl

My wife had the lockout requiring physical key once in our year of owning our 22 RDX. (Similar gen software to the TLX), despite driving daily.

Keyfob remote start does require the car to be locked.

When the car is in remote start mode, everything electronic is essentially off. You have to do the pushbutton start once inside to activate all the electronics, including USB. Interior and puddle lights go on similar to how they go on by fob-proximity, even when the engine is off.