summaryrefslogtreecommitdiffstats
path: root/default_recovery_ui.c (unfollow)
Commit message (Collapse)AuthorFilesLines
2010-04-08support installing any .zip file on the sdcardDoug Zongker1-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
2010-02-02change log recovery to generic device_recovery_start functionDoug Zongker1-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
2009-11-13eclair snapshotJean-Baptiste Queru1-0/+65
2009-07-23fix compile warnings in recovery, change imagesDoug Zongker1-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.
2009-06-19add function for device-specific wipe data featuresDoug Zongker1-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.
2009-06-11fix error from change 3606Doug Zongker1-18/+18
When I changed the definition of device_perform_action() in response to a reviewer comment, I forgot to change this implementation.
2009-06-11split out device-specific recovery UI code into vendor directoriesDoug Zongker1-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.