summaryrefslogtreecommitdiffstats
path: root/mtp/twrpMtp.cpp (unfollow)
Commit message (Collapse)AuthorFilesLines
2016-01-29Remove execute permissions from source filesthat1-0/+0
Change-Id: I5deef665ab374491c0f498b498971abd525d1111
2015-12-22mtp: Address clang compilation errorsMatt Mower1-1/+1
* Move default value of debug_enabled to declaration * Set more-correct fake values for MtpProperty sets Change-Id: Ife3c15ac6c908848c16a609e8e505336e53c19d8
2014-12-19MTP add/remove storage instead of disabling MTPEthan Yonker1-1/+6
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-04add function to partition.cpp to return max file size to mtp responderbigbiff1-1/+2
Change-Id: If8114b5eac741db6c512fb35cb48e3825c2ff098
2014-09-11Fix handling of MTP fork/child processEthan Yonker1-0/+2
Change-Id: Iacd8a38d21e9c8b0dfafefbeb646f46cd3ba02a1
2014-09-05MTP: Use fork instead of pthreadEthan Yonker1-1/+16
Change-Id: I95cf6f4def0c86f40c775738f0712323f0a0f146
2014-09-03Allow toggle of MTP debugEthan Yonker1-1/+3
Via command line in TWRP: twrp set tw_mtp_debug 1 This will enable debugging for MTP. You will need to disable and re-enable MTP in order to see the debug logging. Change-Id: Ia7bb0c584e10a4322b65ecf80a67ed7ee836b38e
2014-09-03add mtp responder to TWRP.bigbiff bigbiff1-0/+98
Big thanks to Dees_Troy for helping with the implementation. Change-Id: I6c9c522b9c9de5dc139e2ecb0141008182ba07f0