usbmuxd - A socket daemon to multiplex connections from and to iOS devices

Age	Commit message (Collapse)	Author	Files	Lines
2018-04-18	udev: Work around systemd bug related to bind events on Linux 4.12+	Bastien Nocera	1	-0/+3
	Make sure that udev doesn't lose our properties when bind events come in, as implemented in kernels 4.12+. See https://github.com/systemd/systemd/issues/8221 and https://github.com/systemd/systemd/issues/7109
2018-01-31	udev: Handle all events only once	Rudolf Tammekivi	1	-3/+3
	This fixes spontaneous USB reconfiguration causing "remove" event to be sent to the daemon, which causes it to close itself if it did not have enough time to connect to phone.
2018-01-31	udev: ensure that all events relating to device are tagged systemd	Gavin Li	1	-2/+5
	systemd will not restart the usbmuxd service the after the first time it is plugged in if it does not receive the "remove" events, which also happen to lack the idVendor and idProduct attributes, so use ENV{PRODUCT} instead.
2014-09-19	Add systemd activation autofoo with fallback for udev and manual activation	Martin Szulecki	1	-4/+4

2013-11-04	udev: Set "deactivated" USB configuration on iOS devices by default	Martin Szulecki	1	-2/+2
	With the introduction of iOS 7, devices should start of in the "deactivated" USB configuration "0" by default to not trigger a trust dialog. Once the devices are identified, usbmuxd will set the correct USB configuration itself and immediately run the preflight worker code to ensure a trust relationship with the host is established. This change fixes the trust dialog from appearing during hotplug of paired devices. The last remaining issue is that current kernel code still sets the USB configuration to "1" by default before the udev rules and thus causes multiple connection beeps.
2013-09-26	udev: lower rules numbering to make sure we start as early as possible	Nikias Bassen	1	-0/+7
	To prevent the trust dialog from appearing on iOS7 devices we need to make sure that no PTP access is happening before usbmuxd starts. So we start as early as possible so the device will be in trusted host state.