2395730_en-US

[#1]

AAOS 15 User Switch Crash on i.MX8QM Multi-Display Setup

Hello Team,

We are running Android Automotive OS 15 (AAOS 15) on the i.MX8QuadMax board with a multi-display setup (Main Display + Passenger Display).

We are observing an issue with the default Car Launcher during user switching:

• System boots normally and the launcher is displayed on both main and passenger displays.
• When switching from the current user to a new user or guest user, both the main display and passenger display crash and become unusable.
• The issue is consistently reproducible after user switching.

We would like to know:

1. Is there any known issue related to user switching in AAOS 15 on i.MX8QM multi-display systems?
2. Are there any additional configurations required for passenger display handling during user switch?
3. What logs or debug information should we collect to further analyze this issue?

Any suggestions or guidance would be appreciated.

Thanks.

Re: AAOS 15 User Switch Crash on i.MX8QM Multi-Display Setup

Hi @AldoG,

Thanks for the clarification.

We are using the NXP i.MX8QM MEK board with NXP BSP. Since this issue is related to Android Automotive, could you please let us know the correct support channel or forum where we should raise our AAOS-related questions?

Thank you.

Re: AAOS 15 User Switch Crash on i.MX8QM Multi-Display Setup

Hello,

Are you using NXP MEK board?
If yes, you are using NXP BSP?

Please note that we do not support Android Automotive we can provide asistance if issues are found on our BSP release.

Best regards/Saludos,
Aldo.

Re: AAOS 15 User Switch Crash on i.MX8QM Multi-Display Setup

Hi @AldoG,

Thank you for the response. I have attached the full logcat,the reproduction steps.and changes we made to bring multi displays.

Reproduction Steps:

1. Boot AAOS 15 on i.MX8QM with center and passenger displays enabled.
2. Open User Settings on the passenger display.
3. Create or switch to a new user/guest user on the passenger display.
4. During the user switch, com.android.car.carlauncher crashes with:
   android.view.WindowManager$InvalidDisplayException:
   Unable to add window -- the specified display can not be found
5. From the log, it appears that CarLauncher is trying to resume on a display that is no longer available or has an invalid display mapping after the user switch.

6. Could you please advise:

   • Whether this is a known issue in AAOS 15 multi-user/multi-display scenarios on i.MX8QM?
   • Which component is responsible for assigning the display during user switching (OccupantZone, CarUserService, TaskDisplayArea, or WindowManager)?
   • Are there any known requirements or patches related to MUMD (Multi-User Multi-Display) support for launcher launching on secondary displays?
   • Is there any recommended debug information we should collect to identify why the display becomes invalid after the user switch?