Hey all, I searched for "AcuraLauncher" and rec'd zero results...so has anyone else seen this error? Not too concerned because it didn't seem to change anything, but does anyone know what this has to do with? pic below - also note, on the newest software D.1.1.2 or whatever it is...

 

Saw this one for the first time ever yesterday, on D.1.0.4 (the newest software for us neglected and frustrated Canadians).

 

Yep I saw this for the first time tonight, on the newest software. I'm not sure if it's related but I have trouble getting remote start to work the past few days. Called Acuralink and they said they were "updating" and that was causing the remote start to fail. He had no clue what updating meant or how long it would take though, so I assume he was reading off of a bulletin or something.

PS: Joe Rogan Experience FTW!

 

Windows 3.0 was more stable than this piece of junk infotainment system.

 

Always JRE!!!

 

Starting out from home this evening, the infotainment system boots up and throws this error.
"Unfortunately, AcuraLauncher has stopped."
I was on the phone at the time and bluetooth audio would not work. So I ended up have to switch to speakerphone to complete my call.

The error is very politely worded, but have no idea what it means and how to recover from it.

On the trip back home I didn't get an error.

Have you had this error? What does it mean in terms of what will and/or will not work and is there a way to recover from it without shutting down the engine and restarting?

 

Looks like there's an earlier thread about this for an earlier version of software.
https://acurazine.com/forums/third-g...-error-977476/

Perhaps a moderator can merge them.

 

I just got this error.
https://acurazine.com/forums/third-g...topped-986011/
In my case I was on a call and bluetooth audio did not work till the engine was stopped & restarted.

 

I get this error from time to time. Never noticed anything affected when it happens.

 

When ANYTHING doesn't work, it's "unfortunate".

I may have gotten this. Seems familiar. I recall thinking, maybe the car is equipped with a software launch mode.

 

Have you tried using Bluetooth Audio just after the error happens?

 

No I haven't. I'm almost always wired for CarPlay. So I guess it affects bluetooth? You can reboot the system from the 3-finger hold menu (hold down all 3 buttons above the touchpad until a hidden menu appears).

 

Yes, it affected bluetooth for me. Not sure what else would be affected. Thanks for the tip on the reboot.

 

A launcher is basically the app drawer in the Android OS world, it displays the available apps and starts the apps when the app is selected.
I have not seen this error yet, but, have had loss of audio and touchpads swapped (very weird) once, a reboot fixed it after I got to the destination.

 

Have had ‘drive mode unavailable’ a couple of times. Once it pulsed on and off dimming the infotainment screen each time.

Very buggy software, and a year and a half later it has not been fixed.

 

New TSB addresses this issue

http://www.urvi.net/forumfiles/SB/B20-001.PDF

 

Funny, I just had one of these happen to me yesterday. Last time I had a bad incident with the Info screen like this was last summer. Mine was mild this time, the map being 'refreshed' every few seconds (same as Madd Dog) while the 'drive mode unavailable' message showed. Went away today. Car was in garage overnight in the 30's. Will have to mention to dealer next week when I go in.

 

The problem, for me, has been intermittent, so I am expecting “cannot reproduce” if I take it to the dealer.

 

Every "glitch" I've ever had with the infotainment system cleared on its own or on the next restart.

My biggest gripe is the map switches to night mode almost instantly passing under an overpass but takes several seconds to change back. More of a feather than a bug.

 

Mission to Mars? Maybe Acura isn't so far behind Tesla after all...