Forum Discussion
Can i please get some explanation and information about the things written in the Local State file?
- Jan 22, 2020
You're welcome, by the way 'EME' stands for Encrypted Media Extensions.
The '"experimentation_and_configuration_service_control"' should be related to the A/B feature rollout as you've mentioned.
'"fre"' Is supposed to state weather the user has seen the splash screen that runs the first time Edge is started, I Assume it stands for something like "First Run Experience"
'"UpdateClientData"' Should be related to syncing the PWA's (apps); Judging by the pattern, it seems like I have the exact fields, although a few more entries. Not sure https://support.google.com/analytics/answer/6158745?hl=en
Most chromium fields are equal, if you want further info about the experience metrics, you could find a full list along with comments here: https://chromium.googlesource.com/chromium/src/components/metrics/+/refs/heads/master/metrics_pref_names.cc
Regarding CFR's, I remember having random flags added to the browser during the day despite the browser being fully updated. Hard to try and manually add those 'experiments', as the documentations are sparse at the moment.
also any insights about each of these code segments would help too
"fre": {
"experience_group": 0,
"has_user_committed_selection_to_import_during_fre": false,
"has_user_completed_fre": false,
"has_user_seen_fre": true,
"last_seen_fre": "81.0.387.0",
"screens": [ "Microsoft.FRE.ScreenId.Splash", "Microsoft.FRE.ScreenId.GetStarted", "Microsoft.FRE.ScreenId.NTPLayout", "Microsoft.FRE.ScreenId.SyncToggle", "Microsoft.FRE.ScreenId.DataConsent", "Microsoft.FRE.NewProfile", "Mi0rosoft.FRE.ScreenId.SyncSignin", "Microsoft.FRE.NewProfile", "Microsoft.FRE.ScreenId.SyncSignin", "Microsoft.FRE.NewProfile", "Microsoft.FRE.ScreenId.SyncSignin", "Microsoft.FRE.NewProfile", "Microsoft.FRE.ScreenId.SyncSignin" ]
},
"updateclientdata": {
"apps": {
"gcmjkm--------------jmmjnii": {
"cohort": "",
"cohortname": ""
},
"jbfafloc-------------jkedane": {
"cohort": "",
"cohortname": ""
},
"oankkpibp--------afllipag": {
"cohort": "",
"cohortname": ""
},
"ojblfaf-----------bhejhlcim": {
"cohort": "",
"cohortname": ""
}
}
},
"low_entropy_source3": 6--2,
"machine_id": 2----5,
"ongoing_logs2": [ {
"count_id": "4",
"data": "----------------==",
"hash": "M----------------o=",
"signature": "v-------------k=",
"timestamp": "1-----------1"
**I used ---- to censor any possible personal info.
If i'm looking at the wrong place for a way to force-enable CFRs let me know
You're welcome, by the way 'EME' stands for Encrypted Media Extensions.
The '"experimentation_and_configuration_service_control"' should be related to the A/B feature rollout as you've mentioned.
'"fre"' Is supposed to state weather the user has seen the splash screen that runs the first time Edge is started, I Assume it stands for something like "First Run Experience"
'"UpdateClientData"' Should be related to syncing the PWA's (apps); Judging by the pattern, it seems like I have the exact fields, although a few more entries. Not sure https://support.google.com/analytics/answer/6158745?hl=en
Most chromium fields are equal, if you want further info about the experience metrics, you could find a full list along with comments here: https://chromium.googlesource.com/chromium/src/components/metrics/+/refs/heads/master/metrics_pref_names.cc
Regarding CFR's, I remember having random flags added to the browser during the day despite the browser being fully updated. Hard to try and manually add those 'experiments', as the documentations are sparse at the moment.
- HotCakeXJan 22, 2020MVPThanks, that was very helpful for understanding the file 🙂