Closed Bug 1185853 Opened 9 years ago Closed 9 years ago

Disabling ADB does not work in developer mode

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE

People

(Reporter: TD-Linux, Unassigned)

Details

(Keywords: foxfood)

There is a setting to select enabling or disabling ADB in the Developer menu, however it has no effect when the foxfood build has been reflashed into developer mode (something which I assume basically 100% of foxfooders have done, as it's required to use some of the preinstalled apps and get all of the foxfooding achievements).
Component: General → Gaia::Settings
Currently, we force adb on all of the time when marionette is enabled (i.e. eng and userdebug builds). Currently, the setting in the UI is only looked at for user builds. This is implemented here: https://dxr.mozilla.org/mozilla-central/source/b2g/chrome/content/devtools/adb.js?from=adb.js#168-181 Our automated tests need adb, so if the default setting would be to have adb enabled for eng & userdebug builds, then we might be able to remove the override. I don't believe that we currently have any UI to select between adb always on (which is certainly what I prefer for developing) and having adb only be on when the screen is locked (which is what michal wants)
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Can you CC me on bug 1182952 so I can view it?
Flags: needinfo?(nhirata.bugzilla)
(In reply to J. Ryan Stinnett [:jryans] (use ni?) from comment #4) > Can you CC me on bug 1182952 so I can view it? Done
Can you CC me on bug 1182952 so I can view it?
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
(In reply to Michal Purzynski [:michal`] (use NEEDINFO) from comment #6) > Can you CC me on bug 1182952 so I can view it? done.
Status: REOPENED → RESOLVED
Closed: 9 years ago9 years ago
Flags: needinfo?(nhirata.bugzilla) → needinfo?(mpurzynski)
Resolution: --- → DUPLICATE
Flags: needinfo?(mpurzynski)
You need to log in before you can comment on or make changes to this bug.