summaryrefslogtreecommitdiffstats
path: root/minadbd/sockets.c (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Kill of most of the remainder of minadbd.Dan Albert2015-02-201-731/+0
| | | | | | | | I think everything left now is here to stay (services.c might get massaged in to libadbd if it gets refactored). Bug: 17626262 Change-Id: I01faf8b277a601a40e3a0f4c3b8206c97f1d2ce6
* Recovery 64-bit compile issuesMark Salyzyn2014-03-141-1/+2
| | | | Change-Id: I92d5abd1a628feab3b0246924fab7f97ba3b9d34
* remove unused code from minadbdDoug Zongker2012-03-201-100/+0
| | | | Change-Id: I2f192c67ef425a53a1dba65d3e0544c1d5a567bd
* support "sideload over ADB" modeDoug Zongker2012-01-101-0/+830
Rather than depending on the existence of some place to store a file that is accessible to users on an an unbootable device (eg, a physical sdcard, external USB drive, etc.), add support for sideloading packages sent to the device with adb. This change adds a "minimal adbd" which supports nothing but receiving a package over adb (with the "adb sideload" command) and storing it to a fixed filename in the /tmp ramdisk, from where it can be verified and sideloaded in the usual way. This should be leave available even on locked user-build devices. The user can select "apply package from ADB" from the recovery menu, which starts minimal-adb mode (shutting down any real adbd that may be running). Once minimal-adb has received a package it exits (restarting real adbd if appropriate) and then verification and installation of the received package proceeds. Change-Id: I6fe13161ca064a98d06fa32104e1f432826582f5