Closed Bug 835345 Opened 11 years ago Closed 11 years ago

Preloaded contacts for carriers during build time

Categories

(Firefox OS Graveyard :: Gaia::Contacts, defect)

x86_64
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:tef+, b2g18 fixed, b2g18-v1.0.0 fixed)

VERIFIED FIXED
blocking-b2g tef+
Tracking Status
b2g18 --- fixed
b2g18-v1.0.0 --- fixed

People

(Reporter: dpalomino, Assigned: albert)

References

Details

(Keywords: feature)

Attachments

(2 files)

Hi, 

One of the key customization requests from carriers is the ability of prepopulating the Address Book with some carrier-specific contacts (most of them related to Customer Care). 

Depending on the SIM card (on country MCC code) those contacts could be inserted in the FTE (for instance). 

Thanks, 
David
Hi again, 

This issue is critical for getting a single variant version (mandatory requirement for latam countries). Nominating for tef+. 

Thanks, 
David
blocking-b2g: --- → tef?
The tef? triagers discussed this today.  While it is obviously important, it seems like a late feature request that puts v1 at risk.

One option Lucas suggested was doing it during the build.  That's not as nice as doing it during the FTE but it might be easier.

It would be great to get product input here.
Flags: needinfo?(ffos-product)
(In reply to Andrew Overholt [:overholt] from comment #2)
> The tef? triagers discussed this today.  While it is obviously important, it
> seems like a late feature request that puts v1 at risk.
> 
> One option Lucas suggested was doing it during the build.  That's not as
> nice as doing it during the FTE but it might be easier.
> 
> It would be great to get product input here.

I agree with the option of doing it during the build. Indeed, we have already a patch that does it and this what we agreed with the product team. The question is whether this should be part of the default Gaia build chain (my opinion is that we should do it as the risk is close to nil) or we could share it with the OEMs (I don't like this option as it introduces fragmentation).
We can do the build-time option to pre-populate the contacts, but I don't think we should do the FTE option for 1.0.0.  As such I'm going to minus this specific bug, unless you want to morph it into the build-time bug.
blocking-b2g: tef? → -
(In reply to Lucas Adamski from comment #4)
> We can do the build-time option to pre-populate the contacts, but I don't
> think we should do the FTE option for 1.0.0.  As such I'm going to minus
> this specific bug, unless you want to morph it into the build-time bug.

I agree with your proposal (as I did in comment 3), but... in which triage has this discussion  taken place? I could have mentioned it there and clarify, but I have not seen nothing in the schedule for this time today
Flags: needinfo?(ladamski)
Changed the name to reflect the idea, during build time, it should be possible to add some contacts to the device. 

Albert has already a working patch for this one. Nominating this again given the importance for the launch and the low risk it has (it does not affect the device code but the build system).
Assignee: nobody → acperez
Flags: needinfo?(ladamski)
Summary: Preloaded contacts for carriers → Preloaded contacts for carriers during build time
As commented in previous Dani's comment, nominating this again.
blocking-b2g: - → tef?
Attachment #709670 - Flags: review?(21)
Hi again, 

As this is a certification requirement for several carriers, adding the dep to cert meta bug. 

Br, 
David
blocking-b2g: tef? → tef+
Keywords: feature
Comment on attachment 709670 [details]
Added support to preloaded contacts at build time

Nothing major but I would like to see a new version of the patch.
Attachment #709670 - Flags: review?(21) → review-
Comment on attachment 709670 [details]
Added support to preloaded contacts at build time

Modified
Attachment #709670 - Flags: review- → review?(21)
Comment on attachment 709670 [details]
Added support to preloaded contacts at build time

Sounds good but let's removed the unwanted 'console' change
Attachment #709670 - Flags: review?(21) → review+
(In reply to Vivien Nicolas (:vingtetun) (:21) from comment #13)
> Comment on attachment 709670 [details]
> Added support to preloaded contacts at build time
> 
> Sounds good but let's removed the unwanted 'console' change

Fixed, it was a confusion between different repos
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
v1-train: fc0489147c2c353e653638a0bcc25b59cf3f0532
v1.0.0: 2c225d4a93e4e5dd85103955949cfcd8201e096f
Removing needinfo since decision to do build time contact preload was reached.
Flags: needinfo?(ffos-product)
No Test case creation is needed in moztrap for this issue. Test case for this issue will be created by partners.
Flags: in-moztrap-
Can you please provide steps to verify this fix - as we will blackbox test from the UI?
David Palomino if you can Verify this bug out, it would be much appreciated.
Flags: needinfo?(dpv)
Keywords: verifyme
Hi, 

Sorry for the delay. 

This has been included by the vendor in the build specific for customization testing, now it's been retested by testhouse responsible from the certification. 

When retested I'll let you know. 

Thanks!
David
Flags: needinfo?(dpv)
Contacts preloaded now appear in the addressbook.
Build id: 20130421003941
Gaia:f2a9d81
Status: RESOLVED → VERIFIED
Per comment 22,I clear "Verifyme".
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: