The behavior is expected according to last line of androit-tools test
plan https://wiki.ubuntu.com/Process/Merges/TestPlan/android-tools
adb reboot and adb reboot-recovery work in any case (locked and unlocked
screen)
** Changed in: mtp (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mtp in Ubuntu.
https://bugs.launchpad.net/bugs/1515862
Title:
locked device can still excute adb commands
Status in mtp package in Ubuntu:
Invalid
Bug description:
current build number: 29
device name: krillin
channel: ubuntu-touch/rc/bq-aquaris.en
last update: 2015-11-13 02:55:49
version version: 29
version ubuntu: 20151112.1
version device: 20150821-736d127
version custom: 20151111--36-46-vivid
Steps:
1.Lock the device
2.On the host, run the command:
$ adb reboot
3.On the host, run the command:
$ adb reboot recovery
Expectations:
After step2#,Connection to the DUT is refused and the following message is
displayed "error: closed"
After step3#,Connection to the DUT is refused and the following message is
displayed "error: closed"
Actual results:
The device still can excute those commands
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1515862/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
