Assigned
Status Update
Comments
vi...@google.com <vi...@google.com> #2
Thank you for reporting this issue. Please upload the AOSP patch following this guidance
cl...@gmail.com <cl...@gmail.com> #3
Comment has been deleted.
bo...@nxp.com <bo...@nxp.com> #4
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
vi...@google.com <vi...@google.com> #5
Please provide the drive url access to
Thanks
bo...@nxp.com <bo...@nxp.com> #6
Add permission to android-bugreport@google.com. Please try again
vi...@google.com <vi...@google.com> #7
Thanks for the above information!
Please provide a sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
bo...@nxp.com <bo...@nxp.com> #8
No sample project or apk needed to reproduce this issue. Just boot up without display, then plug in HDMI display with larger resolution(larger than default display mode) can reproduce this issue.
vi...@google.com <vi...@google.com> #9
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
Description
If we boot up with small resolution display (720p), then switch to large resolution display (1080p) by hotplug in new HDMI display, the navigation bar cannot show.
We verify this issue with the method as below:
1, boot up without HDMI display connected, the default display mode(720p) will report to the framework.
2, hotplug in HDMI display(1080p) and display can show with screen locked.
3, unlock screen and find that no navigation bar on screen
The bugreport when issue happen is attached.