Closed Bug 815554 (b2g-oma-cp) Opened 9 years ago Closed 8 years ago
[meta] Firefox OS 1
.2 Client Provisioning feature
Boot2Gecko should support a way to provisioning the device settings OTA. This is very helpful, for instance, in order to support virtual operators.
This is a v1+ feature we'd like to add. Nom'ing so we can triage accordingly.
blocking-basecamp: --- → ?
blocking-kilimanjaro: --- → ?
(In reply to Chris Lee [:clee] from comment #1) > This is a v1+ feature we'd like to add. Nom'ing so we can triage > accordingly. So this is post-v1? If so, we should - this. If this is for v1 itself, I don't think we should increase the scope of v1 at this point.
We agreed this is a post-V1 feature.
This is post-v1.
blocking-basecamp: ? → -
Target Milestone: --- → B2G C4 (2jan on)
This is a meta for tracking OMA Client Provisioning bugs. Releasing tracking flags since this is a meta bug.
blocking-basecamp: - → ---
blocking-kilimanjaro: ? → ---
OS: Mac OS X → Gonk (Firefox OS)
Hardware: x86 → ARM
Summary: Add support for Client Provisioning → [meta] Add support for Client Provisioning
Depends on: 869291
Change the title to track this feature for 1.2
Depends on: 848403
Summary: [meta] Add support for Client Provisioning → [meta] Firefox OS 1.2 Client Provisioning feature
Please provide the items what we need to configure via OMA-CP.
Depends on: 897368
(In reply to Ken Chang from comment #7) > Please provide the items what we need to configure via OMA-CP. My thoughts on this is we should provide a "generic" implementation. This means we enable the protocol, but allow partners to customize depending on the settings that each operator would like to provision. I've linked a few stories to this: bug 898994: Enabling OMA CP protocol bug 898997: Define a mechanism for OEMs to receive the provisioning request and write to settings accordingly
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
8 years ago
Depends on: 938974
You need to log in before you can comment on or make changes to this bug.