Change the exitFreeformMode to toggleFreeformMode. Now the original
maximize button will work as maximize/restore button.
Test: go/wm-smoke
Test: Manual test.
Bug: 117075771
Bug: 124475503
Change-Id: I268d053ed0e665b8ac5e56019c6ae8f8b7ee1317
This patch removes some debugging logging that was left in in a previous
CL.
Test: compile and boot
Change-Id: Ia852a28bb9327c26da10637019057f07c9e2668a
Don't assume that all shared files have a DISPLAY_NAME index.
Downloads provide a different title index, so check the cursor
index for -1 values. Also make sure to close the cursor when done.
Bug: 124448157
Test: atest ChooserActivityTest, manually test sharing a download
Change-Id: I0beda6b72fb74c65fc4665c8234f147667925784
When SystemUI start up, ColorExtractor will get wallpaper colors so
status bar can use it to update theme, however, this will also block
SystemUI start up process if the wallpaper is image wallpaper.
In order to break the latency, we can extract getWallpaperColors
method from ColorExtractor's contructor, and do it at another thread,
so it won't block SystemUI start up.
Bug: 124279857
Test: atest ColorExtractorTest
Test: Manual test change theme feature can work normally.
Change-Id: I8589b28a17b0a2b33b4bbbda2265080af983f26a
The hidden api logger interface also receives the actual sampled value.
This is an intermediate step before a new logging method is added.
Test: m
Bug: 119217680
Change-Id: I707a2624a254a80391cdae277dd59daa503d055f
This patch adds the following properties to DeviceConfig:
* BLASTULA_POOL_ENABLED
* BLASTULA_POOL_SIZE_MAX
* BLASTULA_POOL_SIZE_MIN
* BLASTULA_POOL_REFILL_THERSHOLD
The BLASTULA_POOL_ENABLED property is checked by ZygoteProcess but not
currently used due to an existing bug (b/123409530). This will be
enabled by go/ag/6162164. Until then the code path is tested via log
inspection.
The remaining properties are checked by ZygoteServer. Values are
clamped to ensure that they cannot be set to values that are harmful to
the device.
Since device_config is not available in the Zygote the system properties
interface is used instead.
Bug: 123524494
Bug: 68253328
Test: adb shell device_config put runtime_native blastula_pool_enabled true
Test: manually verify the property change is observed
Change-Id: I2b675afd9fbc1cbb0e8bc1c491cfdbbb612d0d3b
- Split system-server internal interface in two. One accessible only
inside of the services part of system server. One accessible
everywhere. This is necessary as the second part needs to be
accessible by the PermissionBackupHelper. But the former uses internal
data structures that should not be moved into android.permission.
- Remove old delayed permission restore code from
PermissionManagerService and Settings. This code now lives in
permission controller
- Keep the logic to remember which users still have delayed permissions
left. It is quite expensive to call into permission controller for
ever install of an app, hence this check is necessary. Currently this
mirrors the original logic. This can be improved further later.
Test: Built
Change-Id: Ibc1d5183c361dc55896882db1f7b765e1bee6e84
It's possible to use SEND_MULTIPLE while only sending 1 item.
Adjust the text in this case so that we don't show:
"{fileName} + 0 files".
Better handle errors when attempting to extract file names
and thumbnails.
Bug: 120419296
Test: atest ChooserActivityTest
Change-Id: Ib381974ffbf61c98031ada287bf2533172e6cf9f
Capturing any security exceptions for file content preview, and
logging for now
Bug: 124203056
Test: Bug report -> Share -> Switch profile
Change-Id: Ia22f5d646795d09eae34ca498bee4442665783cd
Continuation of ag/6226654; edits made per Svetoslav's last comments.
Bug: 122740752
Bug: 123080754
Test: blueline-userdebug build completes successfully.
Change-Id: I3e43137eb6e0d8cae77e14d331150d5a05ede07c
Need to limit the width of the content preview area
to a maximum, especially for landscape mode
Bug: 120419296
Test: Visual inspection of landscape/portrait
Change-Id: Ia1d6dc00ca4e0bcb0d06b0d30c24be25b20528e8
Frameworks Base section of power monitor addition. Since IPowerStats
does not have a java interface, we needed to make a native interface
into the code. I followed how the LowPowerStats collection is being
done.
Native code is located in
com_android_server_am_BatteryStatsService.cpp. We are calling the
getEnergyData to get all rails energy data that has been collecting from
boot. This energy data is collected in uWs (microWatt seconds). After
the rail data is collected at each update in the RailStats class, the
wifi and cellular total energy values will contain the energy that all
rails associated with the specific subsystem will have.
We update and collect the energy data using battery stats and propagate
it to telephony metrics. When we collect the total energy for an update
we need to zero out the energy data so it can be accumulated correctly.
1/31: Added modemRailEnergy and wifiRailEnergy to Volta historian.
Bug: 115929961
Test: adb shell dumpsys activity service TelephonyDebugService --metrics
Results Examples:
Energy consumed by modem (mAh): 2.41
Energy Rails consumed by modem (mAh): 2.76
Dumpsys historian results:
+4m23s712ms (2) 100 cc511a18 modemRailChargemAh=0.34 wifiRailChargemAh=1.17 +wifi_scan stats=0:"dump"
+10m24s089ms (2) 100 c4511a18 modemRailChargemAh=0.71 wifiRailChargemAh=1.77 stats=0:"write"
+11m24s228ms (3) 100 c4511a19 volt=4315 charge=3988 modemRailChargemAh=0.77 wifiRailChargemAh=1.94 wifi_signal_strength=2 stats=0:"battery-state"
Change-Id: I97521a03204968079e61f3de86640d4f1a580255
Support sharing 1 or more non-image type files, with potential
for system generated thumbnail image
Bug: 120419296
Test: atest ChooserActivityTest
Change-Id: I17c44435bb0444035e2ec7675cbc367b75cc3a8e
This is to decrease the size of the data. We are not using some of the
dimensions we collect the data for currently.
Test: atest LooperStatsTest BinderCallsStatsTest
Change-Id: I9e51eadb0001e4e7bc5250e5e72b1d4c082ee6d9
This should start at the app zygote isolated UID range, not the
regular isolated UID range.
Bug: 123758436
Test: atest CtsSeccompHostTestcases
atest android.app.cts.ServiceTest#testActivityServiceBindingLru
Change-Id: Ic1b1ee02ab86a2e0f6a02525b466e6f5fdcdaf6c
The configuration change occurs twice and the CallbackTrackingActivity is
relaunched twice, this causes the test to fail on some devices with certain
densities.
BUG:123342948
Change-Id: Idbf79a48a55477445cd70a6f76c104d7669bf2fa
Signed-off-by: Raj Mamadgi <r.mamadgi@samsung.com>
