Age | Commit message (Collapse) | Author |
|
Change-Id: Ic2889f5eb531008340529eadc36ec8efc62b1984
|
|
|
|
Bug: 197740038
Test: Force stock android animation on a pixel phone in
BootAnimation.cpp. (Remember to disable dynamic coloring.) Check stock android animation.
Change-Id: I3c3979c344a351ec261bb12127cff971d6050367
|
|
Test: Flash the updated animation to device. Reboot and check if the
animation shows up.
Bug:199179989
Fixes:199179989
Change-Id: Ic2a2496efcaca4b6ae90c167498b8cd794b46bea
|
|
This CL allows dynamic color boot animations to render graphics in shades of white.
Bug: 190093578
Test: adb shell stop; adb shell start. Complete reboot to see the full
sequence (including the loader part)
Change-Id: I672a49aff90fa04daa4bdd6fd3c0b5497cc1a115
|
|
Otherwise the sysprops would not be loaded yet and accessing them would
return empty strings.
Though unlikely, this is not 100% safe because boot color sysprops
are not guaranteed to be loaded by the time zips are loaded. A TODO
here is to understand boot steps and their timing implications so
that we can fully avoid the race condition.
Bug: 190093578
Test: adb shell setprop persist.bootanim.color(1-4), then reboot phone.
Change-Id: I603da080b1732a436a10dbaca6f2be9f158124dc
|
|
This reverts commit ad9cf52df959489b615f30cbf072415b3352063b.
Reason for revert: Fixing broken atv test
Test: atv atp test tv/platform/simple_boot_test
Bug: 190093578
Change-Id: I9d6ecb6024ce49eef8007458b0d9bf0ff24906c7
|
|
This reverts commit 2ded80094ee534cfbf360e89562f9d6f1cee33e0.
Reason for revert: Working on fixing the regression that happened on Wembly, so we can resume feature work.
Change-Id: I9a624beffdaf97f131046fd4441a251ed3a448ad
Test: adb shell /system/bin/bootanimation
Bug: 190093578
(cherry picked from commit 8eedc0293d53d31f96c2f9cd2f773149aaf5d63f)
|
|
Change-Id: I8d45e47c131320cac5e794fd629fdef84dd3bcfc
|
|
am: 87c254de0e am: 10e844df41 am: 55b2ba298c
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/1681127
Change-Id: I1ee402945af4207affb77d61eb76a21c175ac1fc
|
|
Seeing 100 while booting is not finished, or seeing eg 90 while booting
is not finished isn't user-friendly.
Test: update ART module, see percent progress
Change-Id: I5509c83f661f937f00a7d28c789df509e3528a37
|
|
Change-Id: If3509f3a660e820f4c8c0b29e007faa868e1f089
|
|
This function calls ~ImageDecoder which segfaults.
Bug: 180130969
Change-Id: Iade6025580ccd882ccc140cec966372208804506
|
|
Bug: 159590486
Test: presubmit
Change-Id: I64e57fe4d73c22bbbe0a1767cadf8648259e9beb
|
|
Bug: 178561525
Change-Id: Ifb7c4a1c94e1f4cab710826d57282b981a46e990
|
|
Bug: 175686819
Test: boot with manual changes updating the progress
Change-Id: I2d936e3391f56796308c90deb39ecacc58797721
Merged-In: I2d936e3391f56796308c90deb39ecacc58797721
|
|
Bug: 175686819
Test: boot with manual changes updating the progress
Change-Id: I2d936e3391f56796308c90deb39ecacc58797721
|
|
Change-Id: Idcf943792aaa73080b26e2294f0569061502c85d
|
|
The shutdown callback is currently used only by audioplay.cpp to destroy the audio player.
Sending shutdown when the animation is destructed makes sure the audio
player is not being destroyed before its boot animation part is being displayed.
Test: Modified bootanimation, sound in second last part of bootanimation
plays
Bug: 157407957
Bug: 127254055
Merged-In: I47f57643791e73e4a4fa1597309dccb1f52f2316
Change-Id: I47f57643791e73e4a4fa1597309dccb1f52f2316
|
|
The shutdown callback is currently used only by audioplay.cpp to destroy the audio player.
Sending shutdown when the animation is destructed makes sure the audio
player is not being destroyed before its boot animation part is being displayed.
Test: Modified bootanimation, sound in second last part of bootanimation
plays
Bug: 157407957
Change-Id: I47f57643791e73e4a4fa1597309dccb1f52f2316
|
|
Change-Id: Ie33f12a2f4c73443640c28ad128be96b3533fd8c
|
|
This support helps with several things:
- simpler animation structure (size, number of items)
- more room for designers avoiding thinking about exit part
- time saving as complete parts now can be safely used as fading parts
Bug: 167352662
Test: Manual testing of major/edge cases
- backward compatibility => "f 0" is mapped to "p", "p" still works
- only trimmed areas are faded out
- clock is not faded out (wear case)
- adb shell su root bootanimation
- [c, (exit) f 120, c] => "f 120" fades out and "c" completes
- [c, (exit) f 120, f 320] => "f 120" fades out and "f 320" skipped
- [c, f 16, (exit) f 120] => "f 16" played, "f 120" fades out
- [c, (exit) f 0, f 120] => "f 0" skipped, "f 120" fades out
Change-Id: I9b200ee7107ef9b3dc8d711658ed1042b83739c2
Merged-In: I9b200ee7107ef9b3dc8d711658ed1042b83739c2
|
|
Change-Id: I6a8d7215f874fed05e9fec71b17c8a3d1e2c94e0
|
|
This support helps with several things:
- simpler animation structure (size, number of items)
- more room for designers avoiding thinking about exit part
- time saving as complete parts now can be safely used as fading parts
Bug: 167352662
Test: Manual testing of major/edge cases
- backward compatibility => "f 0" is mapped to "p", "p" still works
- only trimmed areas are faded out
- clock is not faded out (wear case)
- adb shell su root bootanimation
- [c, (exit) f 120, c] => "f 120" fades out and "c" completes
- [c, (exit) f 120, f 320] => "f 120" fades out and "f 320" skipped
- [c, f 16, (exit) f 120] => "f 16" played, "f 120" fades out
- [c, (exit) f 0, f 120] => "f 0" skipped, "f 120" fades out
Change-Id: I9b200ee7107ef9b3dc8d711658ed1042b83739c2
|
|
Change-Id: Ibb86a528ed692cde325705779c7fa57e4b4de682
|
|
Bug: 160679868
Test: m && flash device
Test: take screnshot on device
Change-Id: Id0cd5859b76fc29911d07119d54f329805425b7e
|
|
Change-Id: I08e6a2cfebf1144c6a497636d2157a766a40fee0
|
|
Change-Id: Icb1b0ef9c1bac05168a3d87179b0b49328b1d62f
|
|
cbea0ab58f am: 937a25de15 am: 35ae2778c3 am: 3c1b9ad9af
Original change: undetermined
Change-Id: I1ae7b19afe2e88fc1a7fd32c41fb870e80685ff8
|
|
When ro.surface_flinger.max_graphics_{width|height} is
set the framebuffer size is limited by this property.
However the boot animation size matches the display active
mode size which can cause it to be off-center or partially
visible.
This change limits the boot animation surface size with
accordance with ro.surface_flinger.max_graphics_width.
Bug: 153991408
Test: manual
Change-Id: Idfd1c9adc1f6b10f44bc04ec2078dbc823f28ed6
|
|
|
|
Use DisplayEventReceiver to listen for display hotplug
events and resize the boot animation is display size
changes.
Bug: 156448328
Test: manually make sure the boot animation has correct
dimensions in the following cases
I. With boot animation file
1. scrcpy
2. start boot animation with
adb shell /system/bin/bootanimation
when no physical display is connected (= 480p
fake HWC display). Use the virtual display from
scrcpy to check the boot animation size.
3. connect a 1080p display
(HWC sends hotplug connect to change the display)
4. disconnect the real display
II. Same steps without boot animation file
(android logo should be displayed)
Merged-In: Ib3f0383686399669e8de10456092baaec607fa01
Change-Id: Ib3f0383686399669e8de10456092baaec607fa01
|
|
|
|
Use DisplayEventReceiver to listen for display hotplug
events and resize the boot animation is display size
changes.
Bug: 156448328
Test: manually make sure the boot animation has correct
dimensions in the following cases
I. With boot animation file
1. scrcpy
2. start boot animation with
adb shell /system/bin/bootanimation
when no physical display is connected (= 480p
fake HWC display). Use the virtual display from
scrcpy to check the boot animation size.
3. connect a 1080p display
(HWC sends hotplug connect to change the display)
4. disconnect the real display
II. Same steps without boot animation file
(android logo should be displayed)
Change-Id: Ib3f0383686399669e8de10456092baaec607fa01
|
|
Change-Id: I4af65528de8e3ff3dce71e5de8249a9e658b0a1c
|
|
2e990f7233 am: adf42b8708
Change-Id: Iaaccede61f42c34220b0fb9575af4c6839dbd819
|
|
Bug: 155954661
Test: boot
Change-Id: Ic054ecf6acebba12485926b66d4fb96fa7712547
|
|
HWUI is restricting access to only a set of stable C APIs. Callers like
boot animation are being converted to either the stable C or NDK APIs.
Test: build and verify animation on reboot
Bug: 150782769
Change-Id: I1fb7c9e0ed2f7bcecec109ddc32b1c5a473f7f3a
|
|
Change-Id: I1e6c199dbee77379f84675965391c839eae04961
|
|
Change-Id: I8c9506273be50e59946977f5c4cfb770921f02f7
|
|
Add bootanimation configuration.
If bootanimation configuration is set and the configuration
media file is not existed or unavailable, it will play
default bootanimation.
Change-Id: Ideff09fe77f291542df85f862aa80e2f4f01d0b7
CRs-Fixed: 2614277
|
|
Bug: 144601064
Test: dumpsys display
Change-Id: I477e0e3126cc15eb5f120610b4e6b6b1568df389
|
|
3d0bb1d650 am: ab74c5633a am: d7c39e5ca9
Change-Id: I7aa06e75dfe7fd8b7bb29830ea46ebcbe96b536a
|
|
In case userspace reboot boot animation can't be found, a default
Android logo is going to be shown.
Test: adb reboot userspace
Bug: 148172262
Change-Id: Ida12ffcfe73b335b63178f3e3f2b0c4063dae2c2
|
|
|
|
to be persist.service.bootanim.displays to control which displays can show
bootanimations. This way a user can change the proeprty to be persistent
across reboot.
Bug: 132892728
Test: manual
Change-Id: I2b98a689aafcb2f2c32f0a675624feb72ca18470
|
|
Bug: 144601064
Test: Build
Change-Id: I46d6974e67dcae2d42766f08c899c56dddd795e9
|
|
Test: TreeHugger
Change-Id: Iccedcb9bb5751fc0aecbf460be0062ea86fdaccb
|
|
If we fail preloadZip(), we release the animation prior to
returning.
Test: TreeHugger
Change-Id: I632c052ef22b2a7192b516de5726bf4e74544f7a
|
|
This shows boot animations to the primary and other displays, verified
with 3-display setup.
A guest property, boot.animation.displays, controls which additional displays
to show the boot animation, in addition to the primary display. Use comma
as separator to specificy multiple values, for example:
setprop boot.animation.displays 19260422155234049,19261083906282754
An example CL on how to set this system property: ag/9269083
Bug: 132892728
Test: adb logcat -s BootAnimation
Change-Id: I1ce3ebd57817246a7a0de42af9465e2a3517826b
|