adb is enabled by default in the emulator and after setting a password it is still being seen as offline. Given the emulator is a specific beast and the more I think about it, a default password and --developer- mode make little sense on a "developer" tool.
I would say that we should just add logic in the "developer mode" code to just enable adb by default if the readonly device property is the emulator. Similar logic lives within powerd (for different purposes). This would gain us the added benefit of not needing yet another hack when the "only enable developer mode after unlock" security feature lands. Security wise, a host having access to it's emulator instance is of little "security" importance in my mind, more so, we won't need to maintain spread out hacks to support this. fwiw, adb is enabled by default on the android emulator (build time) but not on actual products. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1365990 Title: ubuntu-emulator create needs --developer-mode and --password options To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/goget-ubuntu-touch/+bug/1365990/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
