Lines Matching full:recovery
28 <p>The recovery system includes several hooks for inserting device-specific
39 used by both the recovery binary and the package-building tools. You can
43 <p><code>device/yoyodyne/tardis/recovery.fstab</code></p>
52 /recovery emmc /dev/block/platform/s3c-sdhci.0/by-name/recovery
66 recovery. MTD is not actually mounted, but the mount point is used as a key to
74 recovery. Similar to the mtd type, eMMc is never actually mounted, but the
84 applies only to mounting filesystems in recovery; the main system is free to
85 mount them anywhere. The directories <code>/boot</code>, <code>/recovery</code>,
91 <p>Starting in Android 3.0, the recovery.fstab file gains an additional
110 <h2 id="recovery-ui">Recovery UI</h2>
112 LEDs, screens, etc.), you can customize the recovery interface to display
116 <b>bootable/recovery/default_device.cpp</b></code> is used by default, and
120 <p><code>device/yoyodyne/tardis/recovery/recovery_ui.cpp</code></p>
133 appear in the hidden recovery menu. Headers describe how to operate the menu
176 recovery: when the menu is toggled off, when it is on, during package
186 by the recovery menu system if the display is enabled)</li>
240 The default value (20 FPS) corresponds to the default recovery images; when
242 For details on images, see <a href="#recovery-ui-images">Recovery UI
266 <p>The <code>StartRecovery()</code> method is called at the start of recovery,
278 <h3 id="supply-manage-recovery-menu">Supplying and managing recovery menu</h3>
321 <i>not</i> called while recovery is doing something such as wiping data or
322 installing a package?it's called only when recovery is idle and waiting for
327 with type EV_REL and code REL_Y), recovery synthesizes KEY_UP and KEY_DOWN
336 devices pressing Alt-W in recovery would start a data wipe whether the menu
372 do nothing). This is the place to provide additional recovery functionality
379 <li><b>REBOOT</b>. Exit recovery and reboot the device normally.</li>
390 whenever a data wipe operation is initiated (either from recovery via the menu
420 <h3 id="build-link-device-recovery">Build and link to device recovery</h3>
421 <p>After completing the recovery_ui.cpp file, built it and link it to recovery
425 <p><code>device/yoyodyne/tardis/recovery/Android.mk</code></p>
432 LOCAL_C_INCLUDES += bootable/recovery
448 # device-specific extensions to the recovery UI
453 <h2 id="recovery-ui-images">Recovery UI images</h2>
454 <p>The recovery user interface consists images. Ideally, users never interact
455 with the UI: During a normal update, the phone boots into recovery, fills the
461 update...") along with the image. For details, see <a href="#recovery-text">
462 Localized recovery text</a>.</p>
464 <h3 id="recovery-5.x">Android 5.x</h3>
465 <p>The Android 5.x recovery UI uses two main images: the <b>error</b> image
490 second (FPS). The tool <code>bootable/recovery/interlace-frames.py</code>
492 image used by recovery.</p>
495 <code>bootable/recovery/res-$DENSITY/images</code> (e.g.,
496 <code>bootable/recovery/res-hdpi/images</code>). To use a static image during
502 <h3 id="recovery-4.x">Android 4.x and earlier</h3>
503 <p>The Android 4.x and earlier recovery UI uses the <b>error</b> image (shown
562 ScreenRecoveryUI</a>). The script <code>bootable/recovery/make-overlay.py
564 overlay images" form needed by recovery, including computing of the necessary
567 <p>Default images are located in <code>bootable/recovery/res/images</code>. To
573 <h3 id="recovery-text">Localized recovery text</h3>
575 along with the image. When the main system boots into recovery it passes the
576 user's current locale as a command-line option to recovery. For each message
577 to display, recovery includes a second composite image with pre-rendered text
580 <p>Sample image of recovery text strings:</p>
582 <img src="../images/installing_text.png" alt="image of recovery text">
583 <p class="img-caption"><strong>Figure 8.</strong> Localized text for recovery
586 <p>Recovery text can display the following messages:</p>
591 <li>No command (when a user boots into recovery manually)</li>
599 <p>When a user boots into recovery manually, the locale might not be available
601 recovery process.</p>
630 into (in this example) <code>device/yoyodyne/tardis/recovery/res/images</code>
637 to recovery and is a right-to-left (RTL) language (Arabic, Hebrew, etc.), the
644 of recovery UI. Instead of creating a subclass of ScreenRecoveryUI, subclass its
656 <p>See <code>bootable/recovery/ui.h</code> for the declaration of RecoveryUI
667 <p><code>device/yoyodyne/tardis/recovery/recovery_updater.c</code></p>
807 code. (This is the same makefile used to customize the recovery UI in the
810 <p><code>device/yoyodyne/tardis/recovery/Android.mk</code></p>
815 LOCAL_C_INCLUDES += bootable/recovery
826 <p>Finally, configure the build of recovery to pull in your library. Add your
1063 <p>Recovery has a <b>sideloading</b> mechanism for manually installing an
1071 recovery supports two additional mechanisms for sideloading: loading packages
1079 /sdcard</code> directory). Your recovery.fstab must define the <code>/sdcard
1082 </code> is typically not available to recovery because it may be encrypted.
1083 The recovery UI displays a menu of .zip files in <code>/sdcard</code> and
1087 available to recovery) is used instead. From the regular system, <code>/cache
1093 recovery starts up its own mini version of the adbd daemon to let adb on a
1103 <li>If your recovery runs adbd normally (usually true for userdebug and eng
