This bug was fixed in the package android-tools -
4.2.2+git20130218-3ubuntu41
---------------
android-tools (4.2.2+git20130218-3ubuntu41) vivid; urgency=medium
core/adbd/services.c:
* disable all support for "adb root" (LP: #1367304)
* check screen lock state before allowing adb push/pull (LP: #1423293)
* move the screen lock check for adb shell to the arg processing code
* fix description of android-tools-adbd (LP: #1264427)
* use the right path for the lock check override file (LP: #1414288)
-- Oliver Grawert <o...@ubuntu.com> Mon, 02 Mar 2015 13:30:02 +0100
** Changed in: android-tools (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Phonedations bugs, which is subscribed to android-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1414288
Title:
adbd falsely looks for /data/.adb_onlock to override the screen lock
check
Status in android-tools package in Ubuntu:
Fix Released
Bug description:
when flashing with ubuntu-device-flash having the --developer-mode
option set, u-d-f puts a file called /data/.adb_onlock in place to
allow overriding of the adbd screen state check during CI automation.
while in recovery the mountpoint is /data, in a running ubuntu system
the mountpoint is named /userdata so adb needs to be fixed to check
/userdata/.adb_onlock instead.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1414288/+subscriptions
--
Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs
Post to : ubuntu-phonedations-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs
More help : https://help.launchpad.net/ListHelp
