When kernel is configured with CONFIG_VMAP_STACK=y kernel stacks are mapped
into process space and therefore already accounted as part of the value
returned by ReadVmallocInfo and reported under MEMINFO_VM_ALLOC_USED
category. Introduce isVmapStack function to check if kernel is configured
with that option and if so do not exclude kernel stack size in the
calculation of memory used by kernel.
Bug: 146088882
Test: dumpsys meminfo with CONFIG_VMAP_STACK enabled and disabled
Change-Id: I9230bbf0ab05524cf52ded35171fd9ec3da16fa0
Signed-off-by: Suren Baghdasaryan <surenb@google.com>
Instead of using "ro.product.apps.unbundled", use
"ro.product.vndk.version" to determine if product apks are unbundled.
"ro.product.vndk.version" will be defined by
PRODUCT_PRODUCT_VNDK_VERSION. If it is defined, all product apks must
be unbundled.
Bug: 144534640
Bug: 127738095
Bug: 128557860
Test: boot and check logs if product apps are loaded successfully
Change-Id: I6d0f7c20e131dfe12203c63a14e6254a8223893b
This is to fix an issue when calling getUser for a context that
is different than the context of the current foreground user.
getUser for a ContextWrapper would call the base
class Context#getUser which returns the user of the current foreground
process rather than returning the user of the calling context.
Currently, this is a bug that does not meet the ContextWrapper class Javadoc.
It looks like the ContextWrapper call was missed in Ib772ec4438e57a2ad4950821b9432f9842998451.
Fix: 144024489
Test: called the API from a test App with a different context than the
current application context.
Change-Id: I58ec9fda24bf135ba8c648a905ef0c81d36ea098
Merged-In: I2d24f5141e8cbc2546c8dc5894a1aeab376b7632
(cherry-pick from ag/9673528)
- Clean up usages of hidden AppOpsManager APIs in SmsApplication
- Add unit tests for SmsApplication
- Expose RoleManager#getDefaultSmsPackage for use in SmsApplication.
Bug: 146834818
Test: atest SmsApplicationTest
Change-Id: I4ab49d7f6274389e7de7cd7223cab3c433936044
The java_libs property is used to expose implementation libraries not
stubs libraries.
Test: m checkbuild
Bug: 146341462
Exempt-From-Owner-Approval: minor change and sole owner is ooo
Change-Id: I2714b65d4b81a9669831153280a29f93dbbf7a26
Copy the util method from Telephony.Mms so we're not using the hidden
API.
Bug: 146834818
Test: atest GsmSmsTest#testIsEmailAddress
Change-Id: I003bf504d25b65ce4fc544d918007034471d7040
Merged-In: I003bf504d25b65ce4fc544d918007034471d7040
Not only is it more concise, but it's also just a tad more correct:
since it really should have been 'sizeof(stats)' not 'sizeof(Stats)'.
Test: builds, atest
Bug: 146787904
Signed-off-by: Maciej Żenczykowski <maze@google.com>
Change-Id: I6cf0295878c7b34cedfe3ae44ff7410ef419f8b9
If there is a container becomes to non-magnifiable, we need to clear
magnification spec (reset the state) and re-traverse all children again.
Bug: 144810344
Test: A11y CTS & unit tests
Test: atest WmTests
Test: manual
1. Enable Magnification in Settings > Accessibility.
2. Open any app with an EditText, tap it to bring up the IME.
3. Trigger Magnification.
4. Check only the app should be magnified, but not IME.
5. Switch to another IME, and check 4, again.
Change-Id: Ia04cb6c49b67dab98cee5bb0cacef12a8bdaffd8
Merged-In: Ia04cb6c49b67dab98cee5bb0cacef12a8bdaffd8
It seems it's possible the IME container could be magnified before an IME
is added. Once the IME is added we will view this as non-magnifiable and then
never un-do the magnification.
Bug: 137691821
Test: Manual
Change-Id: I39b43367ac500a5c6c330b5ae3a451345fa5aec4
Merged-In: I39b43367ac500a5c6c330b5ae3a451345fa5aec4
Moved annotation from Annotation to ServiceState
Bug: 146084549
Test: FrameworkTests, TeleServiceTests
Change-Id: I2411052465204d87cb5982102df0fd1af012a97c
Merged-In: I2411052465204d87cb5982102df0fd1af012a97c
When VerificationActivity receives an Intent, clone the calling Intent's
extras Bundle and pass the whole Bundle into
DynamicSystemInstallationService Intent. Don't unpack and repack the
calling Intent's extras field. Since VerificationActivity aren't using the
contents of the extras Bundle, it shouldn't know about the details of extra.
Test: adb shell am start-activity \
-n com.android.dynsystem/com.android.dynsystem.VerificationActivity \
-a android.os.image.action.START_INSTALL \
--el KEY_USERDATA_SIZE 8589934592 \
-d file:///storage/emulated/0/Download/aosp_arm64-dsu_test.zip
Change-Id: Ie19b9d4d9ebcbd4623d8c76637da4fa732a4a3c3
Parcelable creators should be public per API guidelines
Bug: 146834818
Test: atest android.telephony.cts.SignalStrengthTest
Change-Id: Ib15e21c005ea5fecd5886583213af5fdb9f70abb
Current AOSP LTE signal bar has following limitation:
- For Threshold type, "RSRP & RSSNR" or "RSRP only" are selectable,
but "RSRP & RSRQ" is unavailable.
- For threshold value, RSRP is flexible by carrier config,
but RSSNR is hard-coded.
- The signal strength reporting criteria apply to only the RSRP.
This change allows following customizations by new carrier config:
- Threshold type can select "RSRP & RSRQ" too.
- Threshold value of RSRQ and RSSNR can be flexible.
- RSRQ and RSSNR thresholds can set signal strength reporting criteria.
Test: auto - Confirmed that run
FrameworksTelephonyTests#testSignalStrength and it has no problem.
Test: auto - Confirmed that run
FrameworksTelephonyTests#SignalThresholdInfoTest and it has no problem.
Bug: 133400544
Change-Id: I37d0dc5ff41169b0309cfaabaa0f2595894b3749
Merged-In: I37d0dc5ff41169b0309cfaabaa0f2595894b3749
... so that they can be reviewed.
Bug: 140202860
Test: m
Exempt-From-Owner-Approval: cherry-pick from internal
Merged-In: Iec8cdd30ad5e4979d56140a8c00a85af6476f67f
(cherry picked from commit 13c923d00a8a605db7aecac7456ecfdd08d18759)
Change-Id: Iec8cdd30ad5e4979d56140a8c00a85af6476f67f
With new LMK_SUBSCRIBE lmkd command clients need to subscribe for lmkd
notifications.
Bug: 146597855
Test: run lmkd_unit_test and verify kill notification delivery
Change-Id: Ib54647ce36426a56db3ab6f95f375a0a0ce352ce
Signed-off-by: Suren Baghdasaryan <surenb@google.com>
Bug: b/144826001
Test: Build Pass: OK
Test: Power ON/OFF: OK
Test: Verify CPU loading improvement: OK
Change-Id: I75d55c3e53fce57e50533dc74af3381a6cee4b96
Previous tethering use NetworkState to encapsulate network states.
But NetworkState is hide API and Tethering just use NetworkState
locally that it don't interact with other module by NetworkState.
To avoid hide API accessing and reduce dependency, replace
NetworkState as UpstreamNetworkState in tethering.
Bug: 144758082
Test: atest TetheringTests
OFF/ON hotspot
Change-Id: Ia1837b6ed983a64c3ed72ecf0e6f46d91b3af7da
