[Aries][Settings] Build identifier shown in settings doesnt match build id pulled using ADB



Firefox OS
2 years ago
2 years ago


(Reporter: AdamA, Unassigned)


Gonk (Firefox OS)

Firefox Tracking Flags

(b2g-master affected)


(Whiteboard: [2.5-Daily-Testing][Spark])


(2 attachments)



2 years ago
Created attachment 8660151 [details]

If the user enters the settings and views the build identifier in settings it will not match the build identifier that users pull off using ADB.

Repro Steps:
1) Update a Aries to 20150911152752
2) Open Settings > Device Information > More Information
3) Pull the device information off of the device using ADB
4) Observe the 2 build id's.

The build id in settings and the build id pulled with ADB do not match

It is expected that the build identifiers are consistent

Environmental Variables:
Device: Aries 2.5 [Full Flash]
BuildID: 20150911153729
Gaia: 758c75ee087ea3722213ea2c185cca1d952c8a29
Gecko: 7b1cfb1606ec447506bf7373b645b7a09f3aa238
Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd
Version: 43.0a1 (2.5) 
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:43.0) Gecko/43.0 Firefox/43.0

Repro frequency: 10/10
See attached: screenshot, logcat

Comment 1

2 years ago
This issue DOES NOT occur on Flame 2.5.

Environmental Variables:
Device: Flame 2.5 [Full Flash]
BuildID: 20150911103006
Gaia: 758c75ee087ea3722213ea2c185cca1d952c8a29
Gecko: 19f806034f67e8fc84b352db10f1a21ab982670f
Gonk: c4779d6da0f85894b1f78f0351b43f2949e8decd
Version: 43.0a1 (2.5) 
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:43.0) Gecko/43.0 Firefox/43.0

The build id in settings matches the settings pulled from ADB
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Whiteboard: [2.5-Daily-Testing][Spark]

Comment 2

2 years ago
Created attachment 8660157 [details]
Build Identifier in settings
Naoki, can you take a look at this please?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker) → needinfo?(nhirata.bugzilla)
I think we need to narrow it down in what two information is looking at:
1) The script is checking the application.ini file in the omni.ja found in /system/b2g/ on the device.
2) settings looks at this variable:
          <span data-l10n-id="build-id"></span>
          <small data-name="deviceinfo.platform_build_id"></small>
Which is initiallized in the common-settings and is set through gecko : 
via : appInfo.platformBuildID

I'm not sure if they are the same location.  Tamara, could you help out in figuring this small puzzle out please?
Flags: needinfo?(nhirata.bugzilla) → needinfo?(thills)
Hi Naoki,

Sorry, I'm probably not the best person to dig into this.  Maybe someone working on the build system or settings might be better?  


Flags: needinfo?(thills)
You need to log in before you can comment on or make changes to this bug.