after adbd is up, unplug usb cable will eventually make adb and ecm disappeared

[99degree]

as title said, after adbd is up, unplug usb cable will eventually make adb and ecm disappeared

seemed like the containerized ramdisk does not have uevent kind of thing to revoke adb.
and as consequence, adb lost connect wont have event to trigger to make online again

[99degree]

there was a patch for kernel to provide uevent support.

ANDROID: usb: gadget: configfs: Add Uevent to notify userspace
Android userspace UsbDeviceManager relies on the uevents generated
by the composition driver to generate user notifications. Therefore,
uevents will be generated whenever USB changes its state. This patch
also add "state" attribute to android_device to show USB state. In
addition, this patch adds android_create_function_device to create child
function devices for USB gadget functions as well as
android_remove_function_device to remove them. Android UsbDeviceManager
relies on communicating to the devices created by the gadget functions
to implement functions such as midi.

Bug: 120441124
Bug: 317149848
Bug: 352124133
Change-Id: I471772a2514568dd7f2b2a0316a5f018b3b378ed
Signed-off-by: Neill Kapron nkapron@google.com
Signed-off-by: Elson Roy Serrao quic_eserrao@quicinc.com

[99degree]

correspondent change is
99degree/linux@b36252e