Closed
Bug 923740
Opened 11 years ago
Closed 8 years ago
Support loading preloaded contacts customization data when no SIM is present
Categories
(Firefox OS Graveyard :: Gaia::System, defect)
Firefox OS Graveyard
Gaia::System
Tracking
(blocking-b2g:-)
RESOLVED
WONTFIX
blocking-b2g | - |
People
(Reporter: reuben, Unassigned)
References
Details
(Whiteboard: [systemsfe])
Currently we don't have a way to specify customization data to be loaded when no SIM is inserted. We could use MCC/MNC pair "000-000", or "default", or "nosim", or something.
Updated•11 years ago
|
blocking-b2g: --- → koi?
Component: Gaia::First Time Experience → Gaia::System
Whiteboard: [systemsfe]
Comment 1•11 years ago
|
||
IMHO, i'm not sure if adding a new default configuration have sense, because the build have one. What's the added value to add another?
Comment 2•11 years ago
|
||
(In reply to marina rodríguez [:mai] from comment #1)
> IMHO, i'm not sure if adding a new default configuration have sense, because
> the build have one. What's the added value to add another?
The one in the build isn't a true default customization for no SIM - it acts as a default customization right now applied in all situations, not when the SIM isn't present or isn't detected.
Comment 3•11 years ago
|
||
Blocking because default customizations have to work. I will look into to how many customizations are affected here to determine severity, but don't let that hold back trying to fix this.
blocking-b2g: koi? → koi+
Comment 4•11 years ago
|
||
First we'll figure out which customizations do not have defaults applied when there is no SIM. For some customizations, it may be normal and desired that _no_ defaults are applied. For others, there should be _no_ customizations applied before there is a _valid_ SIM. This may be a no-op.
Assignee: nobody → aus
Status: NEW → ASSIGNED
Comment 5•11 years ago
|
||
Customizations that will have build time defaults with NO SIM PRESENT:
* Bookmarks
* Support Contacts
Customizations that will NOT have build time defaults with NO SIM PRESENT:
* Contacts
* Data APN
* Cell Broadcast
* SUPL / A-GPS
* Messaging APN
Out of the items that will NOT have build time defaults, it feels like Contacts *may* deserve a re-visit so that some default contacts can be populated into the contacts db without a sim card present. However, once a valid sim is inserted, contacts will be populated based on run-time mcc/mnc values for said sim.
Peter, let me know how we should proceed. :)
Flags: needinfo?(pdolanjski)
Reporter | ||
Comment 6•11 years ago
|
||
(In reply to Ghislain 'Aus' Lacroix from comment #5)
> Customizations that will NOT have build time defaults with NO SIM PRESENT:
> * Contacts
FYI, Contacts right now implements this feature with the old contacts.json mechanism, so not having it in FTU just means it'll be done differently (and possibly in a more confusing way).
Comment 7•11 years ago
|
||
(In reply to Ghislain 'Aus' Lacroix from comment #5)
> Customizations that will NOT have build time defaults with NO SIM PRESENT:
>
> * Contacts
> * Data APN
> * Cell Broadcast
> * SUPL / A-GPS
> * Messaging APN
Thanks for the summary Aus. When the SIM gets inserted, I assume that data APN, cell broadcast, A-GPS and Messaging APNs are then configured at that point. Is that accurate?
Flags: needinfo?(pdolanjski) → needinfo?(aus)
Comment 8•11 years ago
|
||
(In reply to Peter Dolanjski [:pdol] from comment #7)
> (In reply to Ghislain 'Aus' Lacroix from comment #5)
> > Customizations that will NOT have build time defaults with NO SIM PRESENT:
> >
> > * Contacts
> > * Data APN
> > * Cell Broadcast
> > * SUPL / A-GPS
> > * Messaging APN
>
> Thanks for the summary Aus. When the SIM gets inserted, I assume that data
> APN, cell broadcast, A-GPS and Messaging APNs are then configured at that
> point. Is that accurate?
Peter, that is correct. Those settings are always updated/re-applied when a SIM card is inserted for the first time or when the SIM card changes regardless of how many times the device was booted up *without* a SIM card.
Flags: needinfo?(aus)
Comment 9•11 years ago
|
||
FWIW - When I tested this out with preloaded contacts, what I saw was that it was currently not possible to ever have a true default customization. You can either a SIM variant preloaded contacts customization or a preloaded contacts customization that applies to all customizations. The default case doesn't exist.
Comment 10•11 years ago
|
||
This also affects partner app customizations - it's currently not possible to specify a default homescreen app customization.
Comment 11•11 years ago
|
||
This bug is being scoped specifically to preloaded contacts loading with no SIM present, which currently doesn't work - we can either apply preloaded to contacts to all customizations or variants. Talking in the systemsfe, we've decided to not block on this, as TEF is okay with only supporting variant preloaded contacts for 1.2.
blocking-b2g: koi+ → -
Summary: Support loading customization data when no SIM is present → Support loading preloaded contacts customization data when no SIM is present
Comment 12•11 years ago
|
||
Going to file a separate bug for the homescreen issue.
Updated•8 years ago
|
Assignee: aus → nobody
Status: ASSIGNED → NEW
Reporter | ||
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•