Closed
Bug 1212245
Opened 9 years ago
Closed 9 years ago
[RedSquare] Back screen support is required
Categories
(Firefox OS Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1195673
People
(Reporter: Alexey.Yakimov, Unassigned)
References
Details
(Whiteboard: [red square])
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.101 Safari/537.36
Reporter | ||
Comment 1•9 years ago
|
||
The following HW specification is suggested by Mozilla for the back screen:
- Color LED
- 48Wx36H
- Resolution enough to support 3 lines, 12 chars
Reporter | ||
Updated•9 years ago
|
Whiteboard: [red square]
Updated•9 years ago
|
Blocks: red-square
Comment 2•9 years ago
|
||
(In reply to Alexey Yakimov from comment #1)
> The following HW specification is suggested by Mozilla for the back screen:
>
> - Color LED
> - 48Wx36H
> - Resolution enough to support 3 lines, 12 chars
@Ravi - Could you please confirm this info?
Flags: needinfo?(rdandu)
Comment 3•9 years ago
|
||
Summary of Skype conversation today with Alexey...
Question - What is status on decision for the secondary screen? What has the OEM(s) said?
Response - Red Square is our product, so really it is for Mozilla to decide what the product spec is. However, when it comes to the dual display, there are a couple of related points:
a) the physical HW components availability / impact on price of device / impact on form factor........This is where we need the guidance from the OEMs.
b) What can we use the dual display for? i.e. what innovative ideas do we have for using it?......this is where we have zero experience right now, and need some ideas from our joint UX team.
So we need to iterate on this a few times......create some innovative UX ideas....then check how that works for the OEMs, make some adjustments and then round the circle again.
Updated•9 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Updated•9 years ago
|
Flags: needinfo?(rdandu)
You need to log in
before you can comment on or make changes to this bug.
Description
•