touch-packages team mailing list archive

[Oliver Grawert <ogra@xxxxxxxxxx>]

** Description changed:

  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 teh mountpoint is /data, in a running system the
- mountpoint in named /android/data so adb needs to be fixed to check
- /android/data/.adb_onlock instead.
+ 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.

** Changed in: android-tools (Ubuntu)
       Status: New => In Progress

** Changed in: android-tools (Ubuntu)
   Importance: Undecided => Critical

** Changed in: android-tools (Ubuntu)
     Assignee: (unassigned) => Oliver Grawert (ogra)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
  In Progress

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