[Touch-packages] [Bug 1495974] Re: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues
** Also affects: mir-android-platform Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1495974 Title: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues Status in Mir: Won't Fix Status in mir-android-platform: New Status in mir package in Ubuntu: Won't Fix Bug description: Some drivers will call android's perform hook with: NATIVE_WINDOW_SET_BUFFERS_FORMAT. In the case that the pixel formats are the same depth, we accommodate this by just setting the format to the newly-requested format. (ie, mir_pixel_format_rgbx_ to mir_pixel_format_rgba_ is accommodated, as no reallocation is needed). However, we've encountered a device that will try to set the format to HAL_PIXEL_FORMAT_RGB_888 when mir has selected HAL_PIXEL_FORMAT_RGBX_. Since we're going from a 32 bit format to a 24 bit format, the stride information becomes incorrect. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1495974/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495974] Re: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues
The Android platform was deleted from lp:mir at revision 4155. ** Changed in: mir Status: Triaged => Won't Fix ** Changed in: mir (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1495974 Title: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues Status in Mir: Won't Fix Status in mir package in Ubuntu: Won't Fix Bug description: Some drivers will call android's perform hook with: NATIVE_WINDOW_SET_BUFFERS_FORMAT. In the case that the pixel formats are the same depth, we accommodate this by just setting the format to the newly-requested format. (ie, mir_pixel_format_rgbx_ to mir_pixel_format_rgba_ is accommodated, as no reallocation is needed). However, we've encountered a device that will try to set the format to HAL_PIXEL_FORMAT_RGB_888 when mir has selected HAL_PIXEL_FORMAT_RGBX_. Since we're going from a 32 bit format to a 24 bit format, the stride information becomes incorrect. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1495974/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495974] Re: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues
It's certainly a bug in Mir and not the client apps. Whether it's a bug in libmirclient or libmirserver and friends I think is not relevant. But good news: We're looking at solving Mir's woes with EGL vs pixel format soon. In the new APIs we're releasing this year, Mir will use EGL more natively and not require that you know or specify the pixel format for that. So with some luck, the bug might go away without any additional effort. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1495974 Title: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues Status in Mir: Triaged Status in mir package in Ubuntu: Confirmed Bug description: Some drivers will call android's perform hook with: NATIVE_WINDOW_SET_BUFFERS_FORMAT. In the case that the pixel formats are the same depth, we accommodate this by just setting the format to the newly-requested format. (ie, mir_pixel_format_rgbx_ to mir_pixel_format_rgba_ is accommodated, as no reallocation is needed). However, we've encountered a device that will try to set the format to HAL_PIXEL_FORMAT_RGB_888 when mir has selected HAL_PIXEL_FORMAT_RGBX_. Since we're going from a 32 bit format to a 24 bit format, the stride information becomes incorrect. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1495974/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495974] Re: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues
Dear everyone in this bug, This seems to also happen in Fairphone 2 in the client context. Could anyone explain more about this bug if this bug is talking about the client or the server? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1495974 Title: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues Status in Mir: Triaged Status in mir package in Ubuntu: Confirmed Bug description: Some drivers will call android's perform hook with: NATIVE_WINDOW_SET_BUFFERS_FORMAT. In the case that the pixel formats are the same depth, we accommodate this by just setting the format to the newly-requested format. (ie, mir_pixel_format_rgbx_ to mir_pixel_format_rgba_ is accommodated, as no reallocation is needed). However, we've encountered a device that will try to set the format to HAL_PIXEL_FORMAT_RGB_888 when mir has selected HAL_PIXEL_FORMAT_RGBX_. Since we're going from a 32 bit format to a 24 bit format, the stride information becomes incorrect. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1495974/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495974] Re: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mir (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1495974 Title: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues Status in Mir: Triaged Status in mir package in Ubuntu: Confirmed Bug description: Some drivers will call android's perform hook with: NATIVE_WINDOW_SET_BUFFERS_FORMAT. In the case that the pixel formats are the same depth, we accommodate this by just setting the format to the newly-requested format. (ie, mir_pixel_format_rgbx_ to mir_pixel_format_rgba_ is accommodated, as no reallocation is needed). However, we've encountered a device that will try to set the format to HAL_PIXEL_FORMAT_RGB_888 when mir has selected HAL_PIXEL_FORMAT_RGBX_. Since we're going from a 32 bit format to a 24 bit format, the stride information becomes incorrect. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1495974/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495974] Re: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues
** Changed in: mir Milestone: 0.25.0 => None -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1495974 Title: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues Status in Mir: Triaged Status in mir package in Ubuntu: New Bug description: Some drivers will call android's perform hook with: NATIVE_WINDOW_SET_BUFFERS_FORMAT. In the case that the pixel formats are the same depth, we accommodate this by just setting the format to the newly-requested format. (ie, mir_pixel_format_rgbx_ to mir_pixel_format_rgba_ is accommodated, as no reallocation is needed). However, we've encountered a device that will try to set the format to HAL_PIXEL_FORMAT_RGB_888 when mir has selected HAL_PIXEL_FORMAT_RGBX_. Since we're going from a 32 bit format to a 24 bit format, the stride information becomes incorrect. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1495974/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495974] Re: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues
** Changed in: mir Milestone: 0.24.0 => 0.25.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1495974 Title: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues Status in Mir: Triaged Status in mir package in Ubuntu: New Bug description: Some drivers will call android's perform hook with: NATIVE_WINDOW_SET_BUFFERS_FORMAT. In the case that the pixel formats are the same depth, we accommodate this by just setting the format to the newly-requested format. (ie, mir_pixel_format_rgbx_ to mir_pixel_format_rgba_ is accommodated, as no reallocation is needed). However, we've encountered a device that will try to set the format to HAL_PIXEL_FORMAT_RGB_888 when mir has selected HAL_PIXEL_FORMAT_RGBX_. Since we're going from a 32 bit format to a 24 bit format, the stride information becomes incorrect. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1495974/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495974] Re: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues
** Changed in: mir Status: In Progress => Triaged ** Changed in: mir Milestone: 0.23.0 => 0.24.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1495974 Title: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues Status in Mir: Triaged Status in mir package in Ubuntu: New Bug description: Some drivers will call android's perform hook with: NATIVE_WINDOW_SET_BUFFERS_FORMAT. In the case that the pixel formats are the same depth, we accommodate this by just setting the format to the newly-requested format. (ie, mir_pixel_format_rgbx_ to mir_pixel_format_rgba_ is accommodated, as no reallocation is needed). However, we've encountered a device that will try to set the format to HAL_PIXEL_FORMAT_RGB_888 when mir has selected HAL_PIXEL_FORMAT_RGBX_. Since we're going from a 32 bit format to a 24 bit format, the stride information becomes incorrect. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1495974/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495974] Re: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues
** Changed in: mir Milestone: 0.22.0 => 0.23.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1495974 Title: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues Status in Mir: In Progress Status in mir package in Ubuntu: New Bug description: Some drivers will call android's perform hook with: NATIVE_WINDOW_SET_BUFFERS_FORMAT. In the case that the pixel formats are the same depth, we accommodate this by just setting the format to the newly-requested format. (ie, mir_pixel_format_rgbx_ to mir_pixel_format_rgba_ is accommodated, as no reallocation is needed). However, we've encountered a device that will try to set the format to HAL_PIXEL_FORMAT_RGB_888 when mir has selected HAL_PIXEL_FORMAT_RGBX_. Since we're going from a 32 bit format to a 24 bit format, the stride information becomes incorrect. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1495974/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495974] Re: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues
** Changed in: mir Milestone: None => 0.22.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1495974 Title: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues Status in Mir: In Progress Status in mir package in Ubuntu: New Bug description: Some drivers will call android's perform hook with: NATIVE_WINDOW_SET_BUFFERS_FORMAT. In the case that the pixel formats are the same depth, we accommodate this by just setting the format to the newly-requested format. (ie, mir_pixel_format_rgbx_ to mir_pixel_format_rgba_ is accommodated, as no reallocation is needed). However, we've encountered a device that will try to set the format to HAL_PIXEL_FORMAT_RGB_888 when mir has selected HAL_PIXEL_FORMAT_RGBX_. Since we're going from a 32 bit format to a 24 bit format, the stride information becomes incorrect. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1495974/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495974] Re: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues
Don't actually know of a currently supported device that does this. I suppose this is in progress with the NBS transition. ** Changed in: mir Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1495974 Title: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues Status in Mir: In Progress Status in mir package in Ubuntu: New Bug description: Some drivers will call android's perform hook with: NATIVE_WINDOW_SET_BUFFERS_FORMAT. In the case that the pixel formats are the same depth, we accommodate this by just setting the format to the newly-requested format. (ie, mir_pixel_format_rgbx_ to mir_pixel_format_rgba_ is accommodated, as no reallocation is needed). However, we've encountered a device that will try to set the format to HAL_PIXEL_FORMAT_RGB_888 when mir has selected HAL_PIXEL_FORMAT_RGBX_. Since we're going from a 32 bit format to a 24 bit format, the stride information becomes incorrect. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1495974/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495974] Re: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues
Can be managed more easily with NBS, might be worth working on post 0.23 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1495974 Title: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues Status in Mir: Confirmed Status in mir package in Ubuntu: New Bug description: Some drivers will call android's perform hook with: NATIVE_WINDOW_SET_BUFFERS_FORMAT. In the case that the pixel formats are the same depth, we accommodate this by just setting the format to the newly-requested format. (ie, mir_pixel_format_rgbx_ to mir_pixel_format_rgba_ is accommodated, as no reallocation is needed). However, we've encountered a device that will try to set the format to HAL_PIXEL_FORMAT_RGB_888 when mir has selected HAL_PIXEL_FORMAT_RGBX_. Since we're going from a 32 bit format to a 24 bit format, the stride information becomes incorrect. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1495974/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495974] Re: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues
** Changed in: mir Milestone: 0.19.0 => 0.20.0 ** Changed in: mir Milestone: 0.20.0 => None -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1495974 Title: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues Status in Mir: Confirmed Status in mir package in Ubuntu: New Bug description: Some drivers will call android's perform hook with: NATIVE_WINDOW_SET_BUFFERS_FORMAT. In the case that the pixel formats are the same depth, we accommodate this by just setting the format to the newly-requested format. (ie, mir_pixel_format_rgbx_ to mir_pixel_format_rgba_ is accommodated, as no reallocation is needed). However, we've encountered a device that will try to set the format to HAL_PIXEL_FORMAT_RGB_888 when mir has selected HAL_PIXEL_FORMAT_RGBX_. Since we're going from a 32 bit format to a 24 bit format, the stride information becomes incorrect. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1495974/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495974] Re: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues
** Changed in: mir Milestone: 0.18.0 => 0.19.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1495974 Title: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues Status in Mir: Confirmed Status in mir package in Ubuntu: New Bug description: Some drivers will call android's perform hook with: NATIVE_WINDOW_SET_BUFFERS_FORMAT. In the case that the pixel formats are the same depth, we accommodate this by just setting the format to the newly-requested format. (ie, mir_pixel_format_rgbx_ to mir_pixel_format_rgba_ is accommodated, as no reallocation is needed). However, we've encountered a device that will try to set the format to HAL_PIXEL_FORMAT_RGB_888 when mir has selected HAL_PIXEL_FORMAT_RGBX_. Since we're going from a 32 bit format to a 24 bit format, the stride information becomes incorrect. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1495974/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495974] Re: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues
** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1495974 Title: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues Status in Mir: Confirmed Status in mir package in Ubuntu: New Bug description: Some drivers will call android's perform hook with: NATIVE_WINDOW_SET_BUFFERS_FORMAT. In the case that the pixel formats are the same depth, we accommodate this by just setting the format to the newly-requested format. (ie, mir_pixel_format_rgbx_ to mir_pixel_format_rgba_ is accommodated, as no reallocation is needed). However, we've encountered a device that will try to set the format to HAL_PIXEL_FORMAT_RGB_888 when mir has selected HAL_PIXEL_FORMAT_RGBX_. Since we're going from a 32 bit format to a 24 bit format, the stride information becomes incorrect. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1495974/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp