summaryrefslogtreecommitdiffstats
path: root/src/com/android/camera/settings/AppUpgrader.java
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'lollipop-mr1-release' of ↵staging/cm-12.1Steve Kondik2015-03-241-24/+45
|\ | | | | | | | | | | https://android.googlesource.com/platform/packages/apps/Camera2 into cm-12.1 Change-Id: I24fa423d91d8d441cbf5d9e75b98037584dd2fbc
| * Refine in-place conversion semantics for SettingsAlan Newberger2014-10-131-20/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Since settings are now stored as strings, avoid app crashes for settings which are still around as other types, and just treat it as if those settings are absent (return default). This requires re-working the version number tracker itself, which is done by making it a new key and migrating just the old key in the getLastVersion override. This is somewhat cleaner and overall the change should increase stability given the change to use in place values of different types. Bug: 17949433 Change-Id: Icaf0d9653eabb9e144f3946a51b4038d3ed48ea9
| * Re-run settings files migrationsAlan Newberger2014-10-061-5/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | Increment version number for upgrade and re-run copying. This will be a no-op for a first time glacier upgrader, copying runs in the same sequence for this case. For alpha users who hit crashes, this will re-run the copy, potentially overwriting some values but ensuring all values are valid. Tested both N4 and N5 upgrade scenarios that had previously seen issues, this addresses issues without the need to clear data. Bug: 17875895 Change-Id: I37c469c1b03151d03ee0d32ce0ba62983af32a36
| * Fix preference copy migration and incorrect HDR+ sticky bitAlan Newberger2014-10-061-11/+26
| | | | | | | | | | | | | | | | | | | | | | A sticky bit upgrader particularly for HDR+ was looking in globals but was actually a module setting. The copy migrator was not properly handling booleans! Modified the copy migrator to properly handle supported types and removed the custom incorrect upgrader. Bug: 17875895 Change-Id: Id36abc429d12a77c5462e5c49ef7786e3d092f2c
| * Avoid porting null keys when copying preferences into new systemAlan Newberger2014-10-031-2/+6
| | | | | | | | | | | | | | | | | | | | Testing on Fishlake shows certain preferences are of 'null' type in shared preferences. Avoid an NPE on porting a null. From testing, this can happen with focus mode, best to just skip porting the key and let the app use a default. Bug: 17829562 Change-Id: I483cb5beb160d3fb7fc8a42aa5085531e3fccb63
* | Camera2: Add option to set max screen brightnessMichael Bestas2015-02-151-1/+22
| | | | | | | | | | | | * Set maximum screen brightness while the user is inside the camera app Change-Id: I8b16ba47a933bc7d6b0c1cd62bfd6ca54875ce1e
* | Camera: Powerkey shutter (2/2)Danesh M2015-02-041-1/+22
| | | | | | | | Change-Id: I70c5cd4dad547e2a9a96541b3104d52af5b5dd5c
* | Fix preference copy migration and incorrect HDR+ sticky bitAlan Newberger2014-10-061-11/+26
| | | | | | | | | | | | | | | | | | | | | | | | A sticky bit upgrader particularly for HDR+ was looking in globals but was actually a module setting. The copy migrator was not properly handling booleans! Modified the copy migrator to properly handle supported types and removed the custom incorrect upgrader. Bug: 17875895 Change-Id: Id36abc429d12a77c5462e5c49ef7786e3d092f2c (cherry picked from commit 90672aa08379e598426c12b529a86afd4b61011e)
* | Avoid porting null keys when copying preferences into new systemAlan Newberger2014-10-041-2/+6
|/ | | | | | | | | | | Testing on Fishlake shows certain preferences are of 'null' type in shared preferences. Avoid an NPE on porting a null. From testing, this can happen with focus mode, best to just skip porting the key and let the app use a default. Bug: 17829562 Change-Id: I483cb5beb160d3fb7fc8a42aa5085531e3fccb63 (cherry picked from commit d560aabf7baef81a14e78341af81994efc1d4f17)
* Fixing settings upgradesAlan Newberger2014-09-031-3/+41
| | | | | | | | | | | | | | Did a full audit of upgrade scenarios and performed the following fixes. * restored pre-existing location upgrade code that handled old upgrades. preserves location choice from C straight to G. * added string type format conversion for "old global" values that were not implemented in the refactor : hdr, hdr+, grid buttons * moved a "reset" that existed in upgraders that put the user in Camera mode on upgrade. it should run for everglades upgraders along with size changes. Bug: 17317510 Change-Id: I87db511bfa89676525ee727620cb546c180a8ef6
* Merge "Protect Camera2 functions from null CameraDeviceInfo" into ↵Alan Newberger2014-08-161-0/+9
|\ | | | | | | ub-camera-glacier
| * Protect Camera2 functions from null CameraDeviceInfoAlan Newberger2014-08-151-0/+9
| | | | | | | | | | | | | | | | | | When the underlying camera fails, the camera1 agent returns null for CameraDeviceInfo. Guard against this case where it is used in app upgrading and settings. Bug: 16982203 Change-Id: I7e4686e508993f0d0fc03eaa9e0b5dc312016eae
* | Enable seamless switching to/from camera2-backed Photo moduleSol Boucher2014-08-151-1/+2
|/ | | | | | | | This supports running individual modules against the camera2 API framework while the rest of the modules use the legacy Camera class. Bug: 16875535 Change-Id: Ic0ae313a3dd96ba22bacc36c7b1712b183b713ff
* Refactor Upgrade/UpgradeAosp into SettingsUpgraderAlan Newberger2014-08-121-0/+363
This CL does three things: - removes the Upgrade/UpgradeAosp classes which were bunches of statics, in favor of a SettingsUpgrader abstract class that can be overridden - moves 'upgrade to strings' hack logic into AppUpgrader so it only is checked and run once, not for any of the former UpgradeSteps. logic used to be in Upgrade and run regardless of key, when it was using detection only meant for KEY.KEY_UPGRADE_VERSION - adds existence checks for all hack in-place key string upgrades so they are no-ops if the key was not persisted in the first place. Bug: 16573087 Change-Id: Ife42f7aa4a7611ba2d143410a3450057b7464901
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-09 13:13:56 +0000