summaryrefslogtreecommitdiffstats
path: root/recovery_ui.h (follow)
Commit message (Collapse)AuthorAgeFilesLines
* make recovery UI images more general; allow for installation animationDoug Zongker2011-03-011-0/+6
| | | | | | | | | | | Change some of the UI parameters (# of indeterminate progress bar frames, fps, etc.) from #defined constants to variables that can be set by the device-specific recovery_ui code (via a new function). Support overlaying different images on top of the base installation icon to animate it. Make the FPS control more accurate. Change-Id: I9268b389b7ea6b3ed9e0c7eae37baf4272e60edd
* generalize "install from sdcard" to "install from external storage"Doug Zongker2010-07-301-1/+2
| | | | | | | Allow sideloading of OTA packages from USB drives that appear as /dev/block/sda1. Change-Id: I1908576c24547cd0088475d8c8917699cd906868
* change log recovery to generic device_recovery_start functionDoug Zongker2010-02-021-0/+3
| | | | | | | | | | Remove (or at least stop calling) the HTC-specific mechanism for preserving the recovery log from before a radio or hboot update. Replace it with a generic device_recovery_start() function which each device's code can implement to do whatever it wants on recovery startup. Change-Id: If3cca4b498c0b1cf0565236404ecf56a1fc46123
* fix compile warnings in recovery, change imagesDoug Zongker2009-07-231-2/+2
| | | | | | | | | gcc 4.4 complains about some of the recovery ui functions not being declared. To include the header, we have to fix the 'volatile' declaration (otherwise there's a compiler error). Move the dream-specific images to vendor/htc/dream, make the default images a generic phone.
* add function for device-specific wipe data featuresDoug Zongker2009-06-191-0/+8
| | | | | | | | Some devices want to do special things when recovery wipes data (eg, wipe data in their baseband processor as well). Add a hook in the device-specific recovery library that gets called when data is wiped. Also add an amend root for the "mbm" partition.
* split out device-specific recovery UI code into vendor directoriesDoug Zongker2009-06-111-0/+68
Take some device-specific details of the recovery UI (eg, what keys to press to bring up the interface and perform actions, exact text of the menu, etc.) and split them out into separate C functions. Arrange to take implementations of those functions from the appropriate vendor directory at build time. Provide a default implementation in case no vendor-specific one is available.