adbd falsely looks for /data/.adb_onlock to override the screen lock check
Bug #1414288 reported by
Oliver Grawert
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| android-tools (Ubuntu) |
Fix Released
|
Critical
|
Oliver Grawert | ||
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/
Related branches
Revision history for this message
| Oliver Grawert (ogra) wrote | #1 |
| description: | updated |
| Changed in android-tools (Ubuntu): | |
| status: | New → In Progress |
| importance: | Undecided → Critical |
| assignee: | nobody → Oliver Grawert (ogra) |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in android-tools (Ubuntu): | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
diff -Nru android-
--- android-
+++ android-
@@ -1,3 +1,13 @@
+android-tools (4.2.2+
+
+ * ubuntu-device-flash creates /data/.adb_onlock when flashing with
+ --developer-mode to override the new screen lock check in adbd. in a
+ booted ubuntu this file gets re-mapped to /userdata/
+ checked path in teh adbd binary to look in the right place for this file.
+ (LP: #1414288)
+
+ -- Oliver Grawert <email address hidden> Sat, 24 Jan 2015 12:59:36 +0100
+
android-tools (4.2.2+
* check screen lock state before allowing establishing a connection
diff -Nru android-
--- android-
+++ android-
@@ -10591,7 +10591,7 @@
+#define GREETER_INTERFACE "com.canonical.
+#define PROPERTIES_
+#define ACTIVE_PROPERTY "IsActive"
-+#define UNLOCK_PATH "/data/.adb_onlock"
++#define UNLOCK_PATH "/userdata/
+
+#include "sysdeps.h"
+