Nexus 4: eglapp clients have incorrect size
Bug #1170854 reported by
Kevin DuBois
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mir |
Fix Released
|
Medium
|
Kevin DuBois | ||
Bug Description
eglapp.c (plasma, triangle) on the nexus 4 only render 2 small pictures instead of one 512x512
Related branches
lp://qastaging/~kdub/mir/fix-size-problem
- PS Jenkins bot (community): Approve (continuous-integration)
- Robert Ancell: Approve
-
Diff: 52 lines (+26/-7)1 file modifiedexamples/eglapp.c (+26/-7)
| Changed in mir: | |
| importance: | Undecided → Medium |
| assignee: | nobody → Kevin DuBois (kdub) |
| tags: | added: android |
| summary: |
- eglapp.c based clients have incorrect size + Nexus 4: eglapp clients have incorrect size |
Revision history for this message
| Kevin DuBois (kdub) wrote | #1 |
| Changed in mir: | |
| status: | New → In Progress |
Revision history for this message
| Kevin DuBois (kdub) wrote | #2 |
| Changed in mir: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| Daniel van Vugt (vanvugt) wrote | #3 |
| Changed in mir: | |
| milestone: | none → 0.0.3 |
| Changed in mir: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
this was a stride/color buffer negotiation problem, where the size chosen by default on the nexus 4 was a 24bit color, but the buffer given out was interpreted in the server as a 32bit color. the galaxy nexus choose a compatible type by default, so it was only seen on the nexus4, due to the different implementations of eglChooseConfig