C++'s "override" keyword implies "virtual". When "virtual" and
"override" are both specified it means something slightly different from
just "override", which is what was intended here.
I teach the C++11 class here at Google. I asked the C++ arbitors to help
me understand this difference. They warned that it is dangerous and not
worth knowing. But that it is worth avoiding.
Test: Tested on local device -- no noticable change.
BUG=115613038
Change-Id: I372821053755fc4cbb1d001b71af7f02dffde5b2
Fixes issues arising from mistakenly turning consumed insets to zero insets
in the legacy Rect constructor.
Change-Id: Ie531fca0fba28eba25843004acfb5444ca6669cd
Fixes: 119310980
Test: atest android.view.WindowInsetsTest
Some additional changes (apart from the regular style modifications)
were needed:
- Guava crypto methods are replaced by their javax equivalents.
- Preconditions checks now depend on com.android.util rather than Guava.
Bug: 111386661,116575321
Test: atest RunFrameworksServicesRoboTests
Change-Id: I43f92f1c0fb3acf62469712d8db212f94429116c
- Disable rotation suggestion button if the navbar is on
non-default display because there is no accelerometer sensor.
- Avoid leakage by removing navbar fragment from fragment
host when display is removed.
Bug: 117746225
Bug: 117744614
Test: atest SystemUITests
Test: manual - create a virtual display with system decoration.
The navbar on the virtual display should not change when
rotating or changing density of default display.
And after releasing the display, use command "dumpsys
activity service com.android.systemui/.SystemUIService |
grep NavigationBarFragment" to check the number of instances.
Change-Id: Icdc8634628ace21395b7eb9d77c6b1067850d1b2
After the refactor, mDozing ended up being false for while until
DreamManagerService decides to end our DreamService. This ended up
delaying scrim transitions and causing display flashing.
Change-Id: I1630d1536ab0a009a5b8d13f7fb4502b5f6a4dda
Fixes: 118684623
Test: manual
Test: atest StatusBarTest
log when networks become available and lost, for all transport types
In statsd, we can use net id to uniquely identify a network. We should
be able to count connectivity state changes similar to what BatteryStats
does.
Bug: 115561340
Test: cts test
Change-Id: Ieac4d243e27d5d368a77e5607dec51964912240d
":" is not allowed in filenames by vfat.
Bug: 119525489
Test: sm set-virtual-disk true
Test: atest core/tests/packagemanagertests/src/android/content/pm/KernelPackageMappingTests.java
Test: atest services/tests/servicestests/src/com/android/server/StorageManagerServiceTest.java
Change-Id: I95ef58486abe8f2a9760e0229192448e0bd9ef42
Test: Simulated and verified the new intend is used
Bug: 118658558
Bug: 115990430
Merged-in: I07a58d0fe1c34106b3da85d1dfd4576b40da4bd5
Change-Id: I07a58d0fe1c34106b3da85d1dfd4576b40da4bd5
(cherry picked from commit 349b9ba16f)