summaryrefslogtreecommitdiffstats
path: root/mtp/MtpServer.cpp (unfollow)
Commit message (Collapse)AuthorFilesLines
2015-02-02MTP: make MTP work even if unplugged and repluggedEthan Yonker1-6/+8
Set up a loop to keep trying to open / read the MTP device so that MTP will work even if the device is unplugged during boot or unplugged and replugged in. Change-Id: I0d3a3b7c91ce84a8cbed16caa4b15efee35b3641
2014-12-29Improve MTPServer logging of read errorsEthan Yonker1-4/+8
Unless MTP debug logging is enabled, you will miss the error and will not know that something went wrong in the log. Change-Id: I51f4758b415eb38e808ec8b1c9788b505bf88c65
2014-12-22Fix else if and maxFileSize initializer.bigbiff1-0/+1
Change-Id: Iac7852a4fb2add5744d5ea424d6ad5a82828f102
2014-12-19MTP add/remove storage instead of disabling MTPEthan Yonker1-2/+27
Implement a pipe between TWRP and MTP to allow TWRP to tell MTP to remove storage partitions as they become unavailable (e.g. during a wipe, unmount, etc) instead of disabling MTP completely. This includes some fixes and improvements in destructors to properly remove / delete various items. This also means that we will not be toggling adb off and on quite as often. I do not like that we had to add another thread, but we were unable to use select() on the mtp_usb character device because this device does not support polling. Select always returned indicating that the mtp file descriptor was ready to be read and the resulting read would block. The read block prevented us from being able to include reading of the pipe between TWRP and MTP in the main MTP thread. We might want to add a return pipe letting TWRP know if the removal of the storage device was successful, but I am not sure how we want to implement this. It would invovle timeouts in both TWRP and MTP to ensure that we returned a failure indicator in a timely manner to TWRP and prevent deleting the storage device in the case of a failure. Right now we make no attempt to ensure that an MTP operation is underway like a large file transfer, but we were not doing anything like this in the past. In some respects we have limited control over what happens. If the user installs a zip that unmounts a storage partition, we will not know about the change in storage status anyway. Regular Android does not have these troubles because partitions rarely get unmounted like in recovery. At some point, we have to hold the user accountable for performing actions that may remove a storage partition while they are using MTP anyway. Ideally we do not want to toggle the USB IDs and thus toggle adb off and on during early boot, but I am not sure what the best way to handle that at this time. Change-Id: I9343e5396bf6023d3b994de1bf01ed91d129bc14
2014-12-12Attempt to set the proper uid/gid/contexts on new files and dirsEthan Yonker1-0/+3
Files and folders that we create during backups, copy log, or MTP operations often do not have the proper uid/gid/contexts assigned. We will attempt to read the proper contexts from the settings storage path and assign those same contexts to any files or dirs that we create. Change-Id: I769f9479854122b49b499de2175e6e2d026f8afd
2014-12-04add function to partition.cpp to return max file size to mtp responderbigbiff1-2/+4
Change-Id: If8114b5eac741db6c512fb35cb48e3825c2ff098
2014-09-04MTP: Better handling of statEthan Yonker1-1/+6
Do some error checking of lstat calls and better handle those errors. Use lstat instead of dirent to check if an item is a directory because dirent does not return the correct item type when using exfat-fuse. Change-Id: I0d008aff55a0e0b4fbeae24cf8d0c04453b7b77e
2014-09-03add mtp responder to TWRP.bigbiff bigbiff1-0/+1337
Big thanks to Dees_Troy for helping with the implementation. Change-Id: I6c9c522b9c9de5dc139e2ecb0141008182ba07f0