adding an android-tools task, since "adb reboot" forces a hard reset
without unmounting the filesystems ... adding something along:
<ogra_> root@ubuntu-phablet:~# echo u > /proc/sysrq-trigger
<ogra_> root@ubuntu-phablet:~# touch /userdata/foo
<ogra_> touch: cannot touch ‘/userdata/foo’: Read-only file system
to core/adbd/services.c in the reboot_service function (instead of the
vdc call) should help here
** Also affects: android-tools (Ubuntu)
Importance: Undecided
Status: New
** Also affects: android-tools (Ubuntu RTM)
Importance: Undecided
Status: New
** Changed in: android-tools (Ubuntu)
Status: New => In Progress
** Changed in: android-tools (Ubuntu RTM)
Status: New => In Progress
** Changed in: android-tools (Ubuntu)
Importance: Undecided => Critical
** Changed in: android-tools (Ubuntu RTM)
Importance: Undecided => Critical
** Changed in: android-tools (Ubuntu)
Assignee: (unassigned) => Oliver Grawert (ogra)
** Changed in: android-tools (Ubuntu RTM)
Assignee: (unassigned) => Oliver Grawert (ogra)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387214
Title:
[TOPBLOCKER] file corruption on touch images in rw portions of the
filesystem
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android/+bug/1387214/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
