Pref 'toolkit.telemetry.enabled = true' is marked as locked.
- streetwolf
- Posts: 2706
- Joined: August 21st, 2011, 8:07 am
- Location: NJ (USA)
Pref 'toolkit.telemetry.enabled = true' is marked as locked.
I want to disable this pref but haven't found a way to do it. Does anyone know how to unlock it so I can disable it?
Intel i9-13900K | ASUS ROG MAXIMUS Z790 HERO DDR5 | 64GB CORSAIR VENGEANCE DDR5 @ 6600 Mhz.
H100i ELITE CAPELLIX XT Liquid CPU Cooler | PNY 12GB GeForce RTX 3080 Ti | 2 CORSAIR 2TB MP600 PRO XT GEN 4
HX1200 PLATINUM PSU | XENEON 32" IPS UHD 144Hz | BenQ 32" UHD | MS Windows 11 Pro
H100i ELITE CAPELLIX XT Liquid CPU Cooler | PNY 12GB GeForce RTX 3080 Ti | 2 CORSAIR 2TB MP600 PRO XT GEN 4
HX1200 PLATINUM PSU | XENEON 32" IPS UHD 144Hz | BenQ 32" UHD | MS Windows 11 Pro
-
- Posts: 359
- Joined: June 12th, 2016, 12:25 pm
Re: Pref 'toolkit.telemetry.enabled = true' is marked as loc
You can't, it's a build flag: https://medium.com/georg-fritzsche/data ... 5df9c428b5
- Gingerbread Man
- Posts: 7735
- Joined: January 30th, 2007, 10:55 am
Re: Pref 'toolkit.telemetry.enabled = true' is marked as loc
<installation folder>\defaults\pref\autoconfig.js
(or local-settings.js if you prefer)
Code: Select all
//
pref("general.config.filename", "mozilla.cfg");
pref("general.config.obscure_value", 0);
Code: Select all
lockPref("toolkit.telemetry.enabled", false);
- Diorser
- Posts: 1009
- Joined: June 22nd, 2005, 6:57 am
Re: Pref 'toolkit.telemetry.enabled = true' is marked as loc
You use a development build [Firefox/59] which purpose is to provide feedback.streetwolf wrote:I want to disable telemetry but haven't found a way to do it.
If you don''t want to contribute to development, you can try Firefox 57 which is a official release.
- streetwolf
- Posts: 2706
- Joined: August 21st, 2011, 8:07 am
- Location: NJ (USA)
Re: Pref 'toolkit.telemetry.enabled = true' is marked as loc
You are making an assumption without all the facts. I've been having an issue that when I exit out of Fx and then start Fx again it takes about 6 seconds to get into Fx. I ran Process Monitor and it appears it might have been sending data to presumably Mozilla. I wanted to disable the pref just to see if it was the cause.Diorser wrote:You use a development build [Firefox/59] which purpose is to provide feedback.streetwolf wrote:I want to disable telemetry but haven't found a way to do it.
If you don''t want to contribute to development, you can try Firefox 57 which is a official release.
I have been testing Inbounds and Nightly's for years so don't give me a lecture. All you needed to ask was why I wanted to unlock the pref.
Intel i9-13900K | ASUS ROG MAXIMUS Z790 HERO DDR5 | 64GB CORSAIR VENGEANCE DDR5 @ 6600 Mhz.
H100i ELITE CAPELLIX XT Liquid CPU Cooler | PNY 12GB GeForce RTX 3080 Ti | 2 CORSAIR 2TB MP600 PRO XT GEN 4
HX1200 PLATINUM PSU | XENEON 32" IPS UHD 144Hz | BenQ 32" UHD | MS Windows 11 Pro
H100i ELITE CAPELLIX XT Liquid CPU Cooler | PNY 12GB GeForce RTX 3080 Ti | 2 CORSAIR 2TB MP600 PRO XT GEN 4
HX1200 PLATINUM PSU | XENEON 32" IPS UHD 144Hz | BenQ 32" UHD | MS Windows 11 Pro
-
- Posts: 5472
- Joined: May 13th, 2012, 10:43 am
Re: Pref 'toolkit.telemetry.enabled = true' is marked as loc
Did you turning off toolkit.telemetry.shutdownPingSender.enabled as I suggested earlier ? No difference in your issue ?streetwolf wrote:You are making an assumption without all the facts. I've been having an issue that when I exit out of Fx and then start Fx again it takes about 6 seconds to get into Fx. I ran Process Monitor and it appears it might have been sending data to presumably Mozilla. I wanted to disable the pref just to see if it was the cause.Diorser wrote:You use a development build [Firefox/59] which purpose is to provide feedback.streetwolf wrote:I want to disable telemetry but haven't found a way to do it.
If you don''t want to contribute to development, you can try Firefox 57 which is a official release.
I have been testing Inbounds and Nightly's for years so don't give me a lecture. All you needed to ask was why I wanted to unlock the pref.
-
- Posts: 359
- Joined: June 12th, 2016, 12:25 pm
Re: Pref 'toolkit.telemetry.enabled = true' is marked as loc
I don't think this has to do with telemetry: https://bugzilla.mozilla.org/show_bug.cgi?id=1420594streetwolf wrote:Diorser wrote: You are making an assumption without all the facts. I've been having an issue that when I exit out of Fx and then start Fx again it takes about 6 seconds to get into Fx. I ran Process Monitor and it appears it might have been sending data to presumably Mozilla. I wanted to disable the pref just to see if it was the cause.
- streetwolf
- Posts: 2706
- Joined: August 21st, 2011, 8:07 am
- Location: NJ (USA)
Re: Pref 'toolkit.telemetry.enabled = true' is marked as loc
Thanks for the link. I updated the bug report pointing to mine which is https://bugzilla.mozilla.org/show_bug.cgi?id=1420995Lurtz wrote:I don't think this has to do with telemetry: https://bugzilla.mozilla.org/show_bug.cgi?id=1420594streetwolf wrote:Diorser wrote: You are making an assumption without all the facts. I've been having an issue that when I exit out of Fx and then start Fx again it takes about 6 seconds to get into Fx. I ran Process Monitor and it appears it might have been sending data to presumably Mozilla. I wanted to disable the pref just to see if it was the cause.
Intel i9-13900K | ASUS ROG MAXIMUS Z790 HERO DDR5 | 64GB CORSAIR VENGEANCE DDR5 @ 6600 Mhz.
H100i ELITE CAPELLIX XT Liquid CPU Cooler | PNY 12GB GeForce RTX 3080 Ti | 2 CORSAIR 2TB MP600 PRO XT GEN 4
HX1200 PLATINUM PSU | XENEON 32" IPS UHD 144Hz | BenQ 32" UHD | MS Windows 11 Pro
H100i ELITE CAPELLIX XT Liquid CPU Cooler | PNY 12GB GeForce RTX 3080 Ti | 2 CORSAIR 2TB MP600 PRO XT GEN 4
HX1200 PLATINUM PSU | XENEON 32" IPS UHD 144Hz | BenQ 32" UHD | MS Windows 11 Pro
- Frank Lion
- Posts: 21178
- Joined: April 23rd, 2004, 6:59 pm
- Location: ... The Exorcist....United Kingdom
- Contact:
Re: Pref 'toolkit.telemetry.enabled = true' is marked as loc
Told him!streetwolf wrote: All you needed to ask was why I wanted to unlock the pref.
"The only thing necessary for the triumph of evil, is for good men to do nothing." - Edmund Burke (attrib.)
.
.
-
- Posts: 205
- Joined: October 17th, 2005, 1:33 am
Re: Pref 'toolkit.telemetry.enabled = true' is marked as loc
This does not work in dev edition 59. Is it still supposed to or did they deliberately disable this capability?Gingerbread Man wrote:
<installation folder>\defaults\pref\autoconfig.js
(or local-settings.js if you prefer)<installation folder>\mozilla.cfgCode: Select all
// pref("general.config.filename", "mozilla.cfg"); pref("general.config.obscure_value", 0);
Code: Select all
lockPref("toolkit.telemetry.enabled", false);
- Aris
- Posts: 3248
- Joined: February 27th, 2011, 10:14 am
Re: Pref 'toolkit.telemetry.enabled = true' is marked as loc
According to Mozilla it is enough to set datareporting.healthreport.uploadEnabled to false to completely disable telemetry.
See https://bugzilla.mozilla.org/show_bug.cgi?id=1422689#c1
See https://bugzilla.mozilla.org/show_bug.cgi?id=1422689#c1
On Firefox Desktop starting with 58 toolkit.telemetry.enabled is locked to "true" on beta, aurora, and nightly channels (as well as unofficial builds with the 'default' channel). It is locked to "false" in all other cases.
This, rather unstraighforwardly, does not mean Telemetry is enabled. This means that, if telemetry is enabled, we collect somewhat more information. More details about our unfortunately-confusing Telemetry preferences can be found in the docs[1] and in the bug tree rooted at bug 1406390.
To disable Telemetry, uncheck the box in about:preferences labelled "Allow Firefox to send technical and interaction data to Mozilla". That will disable all data collection from Firefox to Mozilla via Telemetry. The corresponding about:config pref is `datareporting.healthreport.uploadEnabled`
We plan on straightening out the confusion caused by these historical naming artefacts next year (->2018).
[1]: https://firefox-source-docs.mozilla.org ... ences.html
-
- Posts: 205
- Joined: October 17th, 2005, 1:33 am
Re: Pref 'toolkit.telemetry.enabled = true' is marked as loc
except toolkit.telemetry.unified changes the meaning of datareporting.healthreport.uploadEnabled and others in ways that are not clearly documented
It's really not hard to have a single pref that completely disables telemetry (both collection and transmission) and never changes (in name or meaning). There is no good excuse for this mess.
We're so lucky to be able to choose our telemetry flavor, I bet Chrome just has a single monolithic telemetry.toolkit.telemetry.unified
This controls whether unified behavior is enabled. If true:
Telemetry is always enabled and recording base data.
Telemetry will send additional main pings.
And if unified is false?datareporting.healthreport.uploadEnabled
If unified is true, this controls whether we send Telemetry data. If unified is false, we don’t use this value.
Look, another master switch, naturally, because the previous master switch is sometimes ignored.datareporting.policy.dataSubmissionEnabled
This is the data submission master kill switch. If disabled, no policy is shown or upload takes place, ever.
It's really not hard to have a single pref that completely disables telemetry (both collection and transmission) and never changes (in name or meaning). There is no good excuse for this mess.