| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
This patch allows the user to change the default storage path.
As in CM11, when the path is changed it sends an intent
to the Gallery to set the default camera folder.
Change-Id: I319decc3fdceca61050cf64f7e59afb06fedbf80
|
|
|
|
|
|
| |
* Set maximum screen brightness while the user is inside the camera app
Change-Id: I8b16ba47a933bc7d6b0c1cd62bfd6ca54875ce1e
|
|
|
|
| |
Change-Id: I70c5cd4dad547e2a9a96541b3104d52af5b5dd5c
|
|\
| |
| |
| |
| | |
* commit 'e25f675a189f56df57d08b62fa3604843dfee4a8':
Shorten location startup dialog string
|
| |
| |
| |
| |
| |
| | |
BUG=21706101
Change-Id: I66164d43830cb71bb3a24f0f996a533358cb7d7e
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Creates new activity for permissions handling: both checking
for permissions and handling error condition when critical
permissions are not present. The reason for creating a
new activity is so the app does not attempt to continue
executing OnCreate, OnResume etc, which opens
the camera while the dialogs are showing. This should
not slow the app down because the permissions activity
will only run when a) the first time the app has
insufficient permissions and b) when a critical
permission is missing and the app needs to shut down.
Bug: 21273463
Change-Id: I603acfb3057ba26b9cfa7935eb4cb24b5d547cb5
|
|
|
|
|
|
|
|
|
| |
- When switching cameras HDR+ icon was always shown in disabled state regardless of the actual support mode
- Existing boolean setting to track device's HDR support is not enough
- Changing global device's HDR support setting to string that can hold no-hdr, hdr or hdr-plus values
Bug: 21037428
Change-Id: Ia9cf0484879a22a27e4deb0e4aa066ec806a43e6
|
|
|
|
|
|
|
| |
No longer display visual reminder for users to rotate device to landscape.
Bug: 19416311
Change-Id: Ia03f54809f64e6034479a9021c87b50f186bab99
|
|
|
|
|
|
| |
Bug: 18867164
Change-Id: Ie601a0fbaf64873c56c6a9b2767a2fa6a04a11d9
|
|
|
|
|
|
|
|
|
|
| |
Implemented onFailure() method in the OpenCallback interface and
onPictureTakingFailed() in the PictureCallback interface.
OnFailure() routes through showErrorAndFinish() in the AppController.
Bug: 19452391
Change-Id: I3c19a274cc7664f7d1834899a486c57d0585dc9a
|
|
|
|
|
|
|
|
|
| |
L is already taken care of in a v21 style, with the new buttonTint
property. For K, use the given assets, which happen to be in a
Material style as provided by UX.
Bug: 19083903
Change-Id: I9392edf6460a3a9c7c00e1b62cc0f61f9e2b4231
|
|\
| |
| |
| | |
ub-camera-haleakala
|
| |
| |
| |
| |
| |
| | |
Bug: 18986078
Bug: 19546523
Change-Id: Ie68234a9a3a0b8b9be870cc674658194c72c84ef
|
|/
|
|
|
|
|
| |
CaptureModule when captured pictures don't save to the device.
Bug: 19231841
Change-Id: I7d66db1e4c273dc7ec082f40a80b349bd91a7e8b
|
|
|
|
|
| |
Bug: 18726217
Change-Id: I93397322843a7b1258b881e19ae90a7f6fb55e3b
|
|
|
|
|
|
|
|
| |
For API 21, add a black button tint to the checkbox to ensure it
paints black against the current light blue background.
Bug: 19083903
Change-Id: Ifdd4ddf39bcd379b5761e3d2dacb3963967fd9eb
|
|
|
|
|
|
|
|
|
| |
Bug: 19213609
Bug: 18949556
Bug: 19214672
Bug: 19213602
Change-Id: I0d5c5ce8b4a62f98b44f6ae02ef1ac81d1d7f178
|
|
|
|
|
|
|
|
|
|
| |
During Material update, filmstrip background was intentionally made
1b1b1b. Capture button and mode covers were slightly off from a previous
gray design. Unifying all to one color constant. There are other, unused
background specified from older times, removing them as part of cleanup.
Confirmed with UX that all these colors should be 1b1b1b.
Change-Id: I3da07e9828546d2c9d30a8ac756a0bbb89d6376c
|
|\
| |
| |
| | |
Implemented stubs for Camera2." into ub-camera-haleakala
|
| |
| |
| |
| |
| |
| |
| | |
stubs for Camera2.
Bug: 18188247
Change-Id: Ic47bf432dca326bb454d0e4408b6b58f645a3fa4
|
|/
|
|
|
| |
bug: 18760510
Change-Id: I59773006d8075e957451082ca0fcc11c3c417f30
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug: 19014774
Bug: 18853119
Bug: 18979823
Being able to start with an empty placeholder and then updating that
placeholder allows us to add a visual entry to the filmstrip early on.
This avoid jarring effects where after taking many apid fire shots and
going to filmstrip, the entries are appearing one after the other.
This was caused by sessions only getting started when the thumbnail was
produced, which can take a while when multiple shots are in the
encoding pipeline.
Also contains changes that make CaptureSession testable.
Change-Id: I3d44704099be81524f8e165f3f09de6eebfc147b
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This CL adds a windowBackground drawable equivalent to the covers shown by lockscreen
and app, to remove the black screen in between. With this CL I mostly see no artifacts
when opening camera from lockscreen. Some issues:
* to improve memory usage in system UI holding the lockscreen preview, a vector
camera blanket was added in ag/587418 to ic_camera_blanket. That works transparently
everywhere so far but not in resource drawables that can only handle bitmaps in
layer-list items. Split the vector and bitmaps here, which means only the lockscreen
uses the vector -- this also surfaced a color mismatch between the vector and our PNG
bitmaps, corrected in the new ic_camera_blanket_vector resource. This is a bit fragile
as we rely on pixel match of the two resources, would like a cleaner solution but the
layer-list limitation is tough -- without this change the app crashes at runtime within
BitmapDrawable when the windowBackground is loaded.
* likewise both the lockscreen and app covers explicitly size the bitmap, there are no
provisions to do so within layer-list. Will follow up with a refactor of in-app cover
(ModeTransitionView) to remove explicit sizing and then all will rely on bitmap size
(per above will still need vector file size coordinated with bitmap).
* current implementation relies upon a black window background, we restore that in onCreate.
* Both secure camera and v21 main camera currently use the windowBackground, will submit
just for secure then introduce for main camera when we always start into Camera mode.
* For L explicitly set android:windowDrawsSystemBarBackgrounds to false to ensure the
system preview into the DecorView doesn't take the navigation bar into account when
vertically centering the cover bitmap, to make the preview identical to the other covers.
Bug: 18369862
Change-Id: Ia481e2d1d94bdc5a5d39b4d35b32c29a75bf99ec
|
|
|
|
|
|
|
| |
* Create a new custom focus view that interacts with physical lens diopter changes.
* Replace all occurances of the old focus indicator with the new one.
Change-Id: Ia02646ce4d1eb059ecb8a1dfccc15dfc9c167e1b
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Introduce RoundedThumbnailView and retire PeekView.
* Rename BottomBarModeOptionsWrapper to StickyBottomCaptureLayout.
* Verified on K and L devices.
Thumbnail cropping:
* 100% width and vertically centered for portrait.
* 100% height and horizontally centered for landscape.
General behavior spec:
* Hide the capture indicatorby fading out using fast_out_linear_in (150ms):
1) User open filmstrip.
2) User switch module.
3) User switch front/back camera.
4) User close app.
Behavior spec for non-photo modules:
* Photosphere is stripped of UI so there is no need to show capture
indicator. When a photo sphere is taken (and user is in another mode),
the preview frame used in filmstrip is used in the capture indicator.
* Video: show in viewfinder prior or after capture. Hide during capture.
When a video is taken, the preview frame used in filmstrip is used in
the capture indicator.
* Panorama: Show in viewfinder prior or after capture. Hide during
capture. When a panorama is taken, the preview frame used in filmstrip
is used in the capture indicator.
* Lens blue: Show in viewfinder prior or after capture. Hide during
capture. When a lens blur is taken, the preview frame used in filmstrip
is used in the capture indicator.
Visual spec:
A 12dp spacing between mode option overlay and thumbnail.
1. A circular mask that excludes the corners of the preview image.
2. A solid white layer that sits on top of the preview and is also masked
by (1).
3. The preview image.
4. A 'ripple' which is just a white circular stroke.
Animation spec:
(1) only the scale animates, from 50%(24dp) to 114%(54dp) in 200ms then
falls back to 100%(48dp) in 200ms. Both steps use the same easing:
fast_out_slow_in.
(2) opacity, from 50% to 0% over 150ms, easing is exponential.
(3) doesn't animate.
(4) starts animating after 100ms, when (1) is at its peak radius and all
animations take 200ms, using linear_out_slow in. Opacity goes from 40%
to 0%, radius goes from 40dp to 70dp, stroke width goes from 5dp to 1dp.
Bug: 18317565
Change-Id: Ib8d4f065b98fc3b9b0b627633232ce8cee96eb61
|
|
|
|
|
|
|
|
|
|
|
| |
Since SysUI holds these bitmaps in memory for jank-free
drawing, these pixels are just wasted RAM. Since the
transition code assumes uniform square bitmaps, these are
all 64x64dp, which is still a teensy bit wasteful but much
better than before (144x144dp).
Bug: 18369196
Change-Id: Idf10b2048190ac44eff3e5da467149c460067347
|
|
|
|
|
| |
bug: 18115448
Change-Id: I9d1caaa0903d6f3c2c47ca3e8457a4f85aad910c
|
|
|
|
| |
Change-Id: I2e1a05b9670c01c9729ed9e7b8b146add95ab88f
|
|
|
|
| |
Change-Id: If431ce0b321991e15f33f850acc3cc6c4474ffb4
|
|\
| |
| |
| | |
errors" into ub-camera-glacier
|
| |
| |
| |
| |
| |
| | |
bug: 15841887
Change-Id: I8e7e92a884dda54d9b8385b29d9ef4b7bb7fbd14
|
|/
|
|
|
|
| |
bug: 17785834
Change-Id: Idaf26517399a07471f2b6a98fdb9629baf41afcf
|
|
|
|
|
|
|
|
|
| |
API.
Bug: 17397777
Bug: 17028594
Bug: 17391241
Change-Id: Id5a7fe748f988755cb2d786a2103e375eb97b08f
|
|
|
|
|
|
|
|
|
| |
moved to more universal ApiHelper for that.
this brings back the fade-in on shutter button touchDown.
bug: 17389859
Change-Id: I7c7d24db30bfbb149f84e6f5acf3e211c282c1ec
|
|\ |
|
| |
| |
| |
| |
| |
| | |
also:
bug: 17255612
Change-Id: I8551e3162b8eedee9653a05abb88177e39f12be5
|
| |
| |
| |
| |
| | |
Bug: 17028594
Change-Id: I9c85178926a68c5e3ce26d04107db65514d84169
|
|/
|
|
|
|
| |
Bug: 17028594
Change-Id: I57521aed991f93da1f5abdace6a72be0f1057dbe
|
|\ |
|
| |
| |
| |
| |
| | |
Bug: 17060480
Change-Id: I5ce8d2d2960d21856c0f13e9599d80b0edc03ec9
|
|/
|
|
|
|
|
|
|
|
| |
When pruning modes, we neglected to remove one of the 'photo' parent modes.
This still worked because the last two entries were both 'photo'. Also,
making PhotoModule scope string public so it can be referred to by
other modules, to accomplish the same parent function as the array.
Bug: 17103121
Change-Id: I574e9a7c2db8bf2c86d810c930fbf510d5aa1a24
|
|
|
|
|
| |
bug: 16979040
Change-Id: I2e02884d2971a92d4a408712a0e952891eafb62e
|
|\ |
|
| |
| |
| |
| |
| |
| | |
bug: 16129873
Change-Id: Ibcb2e31162dc353de250db2a7d24726b05768ab1
|
|/
|
|
|
|
|
| |
- Add a new resolution setting for back camera video: "UHD 4K"
Bug: 16206549
Change-Id: I0b72f8100bc26b556099ad08e093273ccda0f25d
|
|
|
|
|
|
|
| |
'et' and 'ms' are deprecated and have already been removed from master:
http://ag/506364
Change-Id: I0acb1a5225f0b7c9c3dcf449b0a16bb7f77118ed
|
|
|
|
|
| |
bug: 16567671
Change-Id: Ifbe7bd68f0f6c47f645b420ef35d6eb6478c4a7e
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The new Settings infrastructure created a bug where the default
focus mode was 'auto', it needs to be continuous-picture. Fixing
here. Also adding verbose logging to the focus manager, could be
helpful in the future.
Bug: 16536583
Change-Id: I80b5905524f7fdaf69097ff8d2780da9f4ee2428
|
|/
|
|
|
| |
bug: 16123188
Change-Id: I390279acb7a4599f1aeba71b415f1261b9a9b97b
|