Mir on the Phone
This blueprint is mean to capture the elements for Mir which are needed in order to support UnityNext for a productizable small screen device (e.g. phone) release. Specifically this captures those elements post "alpha integration" of UnityNext on Mir. This means adding slightly more advanced features/function as well as "industry standard" optimization required to make a phone product.
Acceptance criteria
#1) have a performance comparable (w/in 15%) of surfaceflinger (comparison should be apples-to-apples as much as possible, method tbd)
#2) Mir supporting system composition with robust application switching/life cycle support, should be able to run 12 hours repeatedly launching, switching & closing applications using native applications
Blueprint information
- Status:
- Complete
- Approver:
- Robert Ancell
- Priority:
- Undefined
- Drafter:
- Mir development team
- Direction:
- Needs approval
- Assignee:
- Mir development team
- Definition:
- Approved
- Series goal:
- Accepted for saucy
- Implementation:
-
Implemented
- Milestone target:
-
ubuntu-13.10
- Started by
- Robert Ancell
- Completed by
- kevin gunn
Related branches
Related bugs
Sprints
Whiteboard
in general - mir reporting means committed to info/data from mir, so use explicit interface definition (atho adhoc logging changes will be allowed for dev, shouldn't end up in production....if so, go create an interface)
Work Items
Work items:
Work items for ubuntu-13.04: DONE
[afrantzis] Don't recomposite when nothing changes: DONE
[afrantzis] Display threading: DONE
Work items for ubuntu-13.05:
[afrantzis] First frame synchronisation for surfaces: DONE
Work items for ubuntu-13.09:
[alan-griffiths] Mir on Mir - common code: DONE
[alan-griffiths] Mir on Mir - android code: DONE
[kdub] android buffer driver refcounting: DONE
[robertcarr] screen blanking/
[kdub] nested mir (android render support): DONE
[alan-griffiths] Client connection via socket pair: DONE
Dependency tree
* Blueprints in grey have been implemented.
