So, the original changes (adb disabled when the screen was locked) and remote debugging disabled after 12 hours were done due to Bug 810092 and Bug 874484.
I sent a post to Dev-B2G and Dev-Gaia about this on Aug 17. https://groups.google.com/forum/#!msg/mozilla.dev.b2g/vl2bczVZb2Y/Y_1U4x7d3pwJ Fabrice also recently landed bug 912898 which prevents adb from being disconnected while a debug session is active. Dave Hylands ----- Original Message ----- > From: "Ben Francis" <[email protected]> > To: "Stefan Arentz" <[email protected]> > Cc: "Paul Theriault" <[email protected]>, "dev-b2g" > <[email protected]>, "Jim Blandy" > <[email protected]> > Sent: Wednesday, September 11, 2013 11:20:42 AM > Subject: Re: [b2g] Security implications of remote debugging on devices > > On Tue, Sep 10, 2013 at 9:10 PM, Stefan Arentz <[email protected]> wrote: > > > +1 Yes, we were discussion this earlier today. I think it makes a lot of > > sense. One thing to add, it would be good to have a ‘do not auto-lock the > > screen while i am debugging my app’ option. I think Android has something > > like that and it prevents a lot of frustration as it is super annoying to > > have the screen auto lock on you while you are working on something. > > > This has changed recently and it's a huge pain during development? Does > anyone know what changed and why? > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g > _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
