In particular, the AutoMounter currently assumes that disk removal/insertion events will be followed by state change events. It appears that they can occur in the order: state change, disk-insertion (see bug 822465)
Created attachment 693552 [details] [diff] [review] Deal with disk insertion event after state change event This should address the problem seen in bug 822465. Since I can't reproduce, could I get you to try it?
Updated flags to match bug 822465
blocking-basecamp: --- → -
tracking-b2g18: --- → +
Attachment #693552 - Flags: review?(kyle) → review+
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
FYI This seems to work only if I do get root access through |adb root|
Sorry, I don't understand. What seems to work? Or are you saying that the original bug 822465 only manifests when the adb shell is non-root?
(In reply to Dave Hylands [:dhylands] from comment #6) > Sorry, I don't understand. What seems to work? > > Or are you saying that the original bug 822465 only manifests when the adb > shell is non-root? Yes, I had to do an |adb root| on my -userdebug build for the SD card to mount. Although now I'm not sure my build picked up the attached patch. I'll try again tomorrow
status-b2g18: --- → fixed
status-b2g18-v1.0.0: --- → wontfix
status-b2g18-v1.0.1: --- → wontfix
status-firefox20: --- → fixed
Target Milestone: --- → B2G C4 (2jan on)
You need to log in before you can comment on or make changes to this bug.