summaryrefslogtreecommitdiffstats
path: root/default_recovery_ui.c (follow)
Commit message (Collapse)AuthorAgeFilesLines
* support installing any .zip file on the sdcardDoug Zongker2010-04-081-1/+1
| | | | | | | | Replaces the "install sdcard:update zip" menu option with one that displays a menu of zip files (and subdirs) on the sdcard and lets you pick which one to install. Change-Id: I85c94c0e9bc8e05ca52031fc29ca2624c2695ced
* change log recovery to generic device_recovery_start functionDoug Zongker2010-02-021-0/+4
| | | | | | | | | | 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/+4
| | | | | | | | 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.
* fix error from change 3606Doug Zongker2009-06-111-18/+18
| | | | | When I changed the definition of device_perform_action() in response to a reviewer comment, I forgot to change this implementation.
* split out device-specific recovery UI code into vendor directoriesDoug Zongker2009-06-111-0/+61
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.