****Steps 1. Installing a master build on device 2. Clone the tests repository for sigle variant: https://github.com/telefonicaid/firefoxos-gaia-testsbuild.git 3. Configuring the file variant.json 4. Clone Gaia repository and select the master branch. 5. Executing the command "GAIA_DISTRIBUTION_DIR="URL"/firefoxos-gaia-testsbuild PRODUCTION=1 make reset-gaia" to install gaia with single variant in the device 6.Complete FTE with a SIM card with a mnc/mcc not configured in variant.json 7. Open Settings apps 8. Open sound settings ****Expected Result Default ringtone name appears in "Settings/Soungs/Ringer" ****Actual Result The text "Default" appears in "Settings/Soungs/Ringer". With this information the user does not know the ringtone selected Note: This bug is very similar to 937096 but this case is for not configured mnc/mcc or complete the FTE without sim card. The bug 937096 uses the file variant.json and this case uses the file setting.json
Albert - Can you double check if this is a bug in the customization vs. bug in Gaia?
UX, how big of an issue do you think this is?
If the patch is low risk we can take it.
(In reply to Peter Dolanjski [:pdol] from comment #2) > UX, how big of an issue do you think this is? UX did add a comment about this here - https://bugzilla.mozilla.org/show_bug.cgi?id=937096#c37. Note - this is a followup to bug 937096. Clearing needinfo on Albert as I see later discussion in the bug clarifies the format used for ringtone customizations.
Triage decided that assuming the customized ringtone is actually functioning, just showing "Default" isn't a blocker. Partners doing customization may disagree so please re-nom if so.
blocking-b2g: 1.3? → -
Flags: needinfo?(firefoxos-ux-bugzilla) → needinfo?(jsavory)
Sorry for the delay, forwarding this one to Katie to see if this still an issue as she is covering UX for Gallery.
Flags: needinfo?(jsavory) → needinfo?(kcaldwell)
I can't reproduce in 1.3, 1.4, 2.0 and master. It works as expected.
This appears fixed. The "Firefox OS" name for the default appears as expected on 1.4 and 2.0. Resolving.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.