Closed Bug 822754 Opened 9 years ago Closed 9 years ago
Mounter doesn't deal with out-of-order events
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)
This should address the problem seen in bug 822465. Since I can't reproduce, could I get you to try it?
Attachment #693552 - Flags: review?(kyle) → review+
Status: NEW → RESOLVED
Closed: 9 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
You need to log in before you can comment on or make changes to this bug.