Right, if we don't recognize the mmc-mnc pair we just apply the default customization. The use-case is mostly sim-locked phones that come with a sim card when you buy them in the store. The pref is off by default and any other users or devs wouldn't be affected.
-Gregor On Monday, August 12, 2013 10:03:25 AM UTC-7, Thomas Ho wrote: > Alexandre, > > > > As this flag is to be set by OEMs, I believe they'd like to have at > > least a default customization. > > > > For open market phones, there should be no customization. > > > > -- > > Thomas Ho > > > > 於 13/8/12 上午7:57, Alexandre Lissy 提到: > > > What about not proposing any customisation ever if there is no SIM ? > > > > > > Le 12/08/2013 16:41, Peter Dolanjski a écrit : > > >> Hello, > > >> > > >> I am sending this note to solicit feedback and raise visibility of a > >> planned implementation of runtime market customizations with respect to > >> the First Run Experience. > > >> > > >> Background: > > >> In 1.2, the Systems Front-End team is expanding on the ability to be able > >> to customize the device for local markets. Based on the SIM card inserted > >> into the device (during First Run), certain customizations are applied at > >> runtime including app preloads, wallpaper, ringtone, settings, etc. Many > >> refer to this as single-variant capabilities given that a single build > >> (and therefore hardware SKU) can be shipped to multiple locales (with > >> disparate customization requirements). The goal is to significantly reduce > >> the logistics and costs associated with the OEM managing separate builds > >> for each market, shipping different hardware SKUs to individual locales > >> and also for the operator in being able to rebalance market inventory > >> across locales without needing to reflash the devices. Overall, this makes > >> FxOS more appealing to OEMs from a cost perspective. > > >> > > >> The Challenge: > > >> In working through the implementation options, it became clear that if the > >> customizations were applied at any point (beyond First Run) that the SIM > >> card was inserted there were many corner cases that complicated the > >> solution and also potentially negatively impacted commercialization > >> agreements with respect to app preloads and grid placement (which are > >> monetized). Addressing these corner cases could put delivery of this > >> functionality at risk for 1.2. > > >> > > >> The Proposed Approach: > > >> In order to eliminate the corner cases and simplify the approach (at least > >> in the short term - 1.2), we are looking at the idea of introducing a > >> flag, settable by the OEM (at the operator's request) which would require > >> that the user enter the SIM card in order to complete the First Run. This > >> would not affect (users could complete First Run without a SIM) open > >> market devices or devices for which this restriction was not enabled. > >> Further, while concern was raised that this would prevent OEMs from being > >> able to do random device QA spot checks, the default customization (for > >> SIMs other than the target markets) would apply, allowing the spot checks > >> be be completed. > > >> > > >> We acknowledge that preventing the user from completing First Run without > >> a SIM (at the operator's request) may impact user choice and sovereignty, > >> so we are open to feedback. > > >> > > >> Please raise significant concerns with this approach. > > >> > > >> > > >> Thanks, > > >> > > >> Peter > > >> _______________________________________________ > > >> dev-b2g mailing list > > >> [email protected] > > >> https://lists.mozilla.org/listinfo/dev-b2g > > >> > > > _______________________________________________ > > > dev-b2g mailing list > > > [email protected] > > > https://lists.mozilla.org/listinfo/dev-b2g _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
