tequilaOS/platform_bootable_recovery
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
platform_bootable_recovery/minadbd
History
Josh Gao 5ee3eba34f minadbd: statically link libadbd. 
Reduce the amount of wasted space on the recovery image by statically
linking all of the adb libraries into minadbd.

Bug: http://b/150317254
Test: booted aosp_walleye-eng into recovery
Change-Id: I5233b1a23c14f9d478bb77c25ebdbb0ce45bcc5a
2020-03-30 16:54:44 -07:00
..
include/minadbd minadbd: Export minadbd/types.h to libinstall. 2019-09-26 00:04:11 -07:00
Android.bp minadbd: statically link libadbd. 2020-03-30 16:54:44 -07:00
AndroidTest.xml Add test config to minadbd_test 2017-03-28 22:13:38 -07:00
fuse_adb_provider.cpp minadbd: Support rescue install and getprop commands. 2019-04-19 12:53:55 -07:00
fuse_adb_provider.h Support starting fuse from a block map 2019-06-20 13:53:40 -07:00
fuse_adb_provider_test.cpp Create a FuseDataProvider base class 2019-03-19 11:11:58 -07:00
minadbd.cpp minadbd: Export minadbd/types.h to libinstall. 2019-09-26 00:04:11 -07:00
minadbd_services.cpp minadbd: statically link libadbd. 2020-03-30 16:54:44 -07:00
minadbd_services.h Add test for minadbd 2019-04-23 11:33:57 -07:00
minadbd_services_test.cpp minadbd: Export minadbd/types.h to libinstall. 2019-09-26 00:04:11 -07:00
README.md minadbd: Update README.md. 2019-09-27 13:17:16 -07:00

README.md

minadbd

minadbd is analogous to the regular adbd, but providing the minimal services to support recovery-specific use cases. Generally speaking, adbd = libadbd + libadbd_services, whereas minadbd = libadbd + libminadbd_services.

Although both modules may be installed into the recovery image, only one of them, or none, can be active at any given time.

  • The start / stop of adbd is managed via system property sys.usb.config, when setting to adb or none respectively. Upon starting recovery mode, adbd is started in debuggable builds by default; otherwise adbd will stay off at all times in user builds. See the triggers in bootable/recovery/etc/init.rc.

  • minadbd is started by recovery as needed.

    • When requested to start minadbd, recovery stops adbd first, if it's running; it then forks and execs minadbd in a separate process.
    • minadbd talks to host-side adb server to get user requests.
      • minadbd handles some requests directly, e.g. querying device properties for rescue service.
      • minadbd communicates with recovery to fulfill requests regarding package installation. See the comments in bootable/recovery/install/adb_install.cpp for the IPC protocol between recovery and minadbd.
    • Upon exiting minadbd, recovery restarts adbd if it was previously running.