AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Download the new for android AutoMounter1/15/2024 ![]() You may want to use USB_FUNC_MTP instead of "mtp" > Should we use USB_FUNC_UMS instead of "mass_storage"? > +687,5 > + DBG("UpdateState: USB functions: '%s'", functionsStr) Please move the declaration into that if-block. > The variable |usbConfigured| is only used in the if-block starting from > Overall looks good to me, r=me with nits addressed and question answered. Question: should we use UniquePtr instead of Scoped*? Just my suggestion and should not block the implementation - it seems to make more sense to me to put AddStorage()/RemoveStorage() under MozMtpServer since it's a 'has-a' relation between MtpStorage and its holder in this +35,5 + void AddStorage() > + virtual void Notify(Volume* const& aEvent) Suggestion: if we do need to make sure mMtpStorage has no value after RemoveStorage(), would moving the assertion to the end of RemoveStorage() be a good idea? Then we don't need to assert after RemoveStorage() are called. ::: +66,5 + // The volume is no longer accessible. > MozMtpDatabase::endSendObject(const char* aPath, > + } while (mState != prevState & ++loopCount mtpEnabled & usbCablePluggedIn is true => STATE_MTP_CONFIGURINGĢst loop: STATE_MTP_CONFIGURING => mtpEnabled & mtpConfigured is false => STATE_MTP_CONFIGURING => leave the loop > + // of times we loop at least the phone will boot up and we'll get to see > + // of the CPU, so you won't even see your logcats. maybe you wanted to say "when MTP isn't +793,5 + // there is a bug in the state machine and that b2g is now consuming 100% > + // is that we don't leave it in MTP mode is MTP isn't enabled. ![]() > + // sharing of the volume which is significant. > + // We do this whether or not UMS is enabled. You may want to use USB_FUNC_MTP instead of +732,5 + SetState(STATE_UMS_CONFIGURED) > + mtpConfigured = usbConfigured & strstr(functionsStr, "mtp") != nullptr ĭitto. > + mtpAvail = (access(ICS_SYS_MTP_DIRECTORY, F_OK) = 0) Should we use USB_FUNC_UMS instead of +696,5 + } > + umsConfigured = usbConfigured & strstr(functionsStr, "mass_storage") != nullptr > + umsAvail = (access(ICS_SYS_UMS_DIRECTORY, F_OK) = 0) Please move the declaration into that +687,5 + DBG("UpdateState: USB functions: '%s'", functionsStr) The variable |usbConfigured| is only used in the if-block starting from #681. Overall looks good to me, r=me with nits addressed and question answered. No scripting required!Ĭompatibility: Intel, 64-bit processor OS X 10.Comment on attachment 8473521 Simply add a server, and see discovered devices.ĪutoMounter is sandboxed, uses native MacOS frameworks, and doesn’t store your credentials. You can also tie your server to a WiFi access point SSID.ĭiscovers available servers that provides filesharing services. Send a Wake-On-LAN packet on network change. No annoying notifications, it’s all visible in the menu bar, one click away.Īdd multiple devices that provide network shares, and AutoMounter will keep track of them all. Whenever you change locations, AutoMounter will mount your shares from the available server, and they will appear on your Desktop.ĭetects when you’ve changed networks, and will automatically attempt to mount shares from any available server.ĪutoMounter stays out of your way. If you’ve got a NAS appliance, a server at work, or even shared folders on your other computers, you’ll know how time consuming it is to keep them mounted.ĪutoMounter makes this easy by ensuring your shares are always available. We wanted our network shares always accessible and ready to use. AutoMounter is a sleek and powerful menu item for automatically mounting your network shares.
0 Comments
Read More
Leave a Reply. |