Due to the way this logic was set up, every time we would load
a new nanoapp, add_app_instance() would change the nanoapp's
handle/"id" in manner that was invisible to closeTxnLoad(),
so our JNI cache would use a different handle than what we
passed to the Java callback.
We remove this unnecessary changing of the handle/"id".
Bug:31325144
Change-Id: I8678729f38fb804bc6a128ce9722fd35551fa1c1
This view is being removed. This change removes it from revision list
as it cannot be used anymore.
Bug: 31068104
Change-Id: Id0d0baa1827b3c1136efca5a1982db817a78fe7c
Forcing the policy to not use A2DP is not needed anymore now that
the cast icon does not expose A2DP choice anymore.
The corresponding AudioManager APIs have also been long deprecated.
Removing support for this feature which is replaced by newer routing
APIs.
Bug: 30963785
Change-Id: If98572742a8cf6388c1408d015c86dd445c5660b
(cherry picked from commit 0218f53108)
There were two separate issues here :
- RestatInternal was using an iterator after a call to erase(). This
will not work because it will be invalidated.
- The "standard" for loop idiom for iterating over a map while making
structural changes to it is broken. Switch to a while loop and treat
cases where elements are erased differently from cases where they
aren't.
bug: 31092930
bug: 30963384
Change-Id: I261d59239558230dd8cdd1d1cb5b9e2448a4c23f
In some region, when user dials emergency numbers, the call will go to
IVR system first and then to emergency center. This behavior causes
delay to let consumer to get help from center. Due to region/operator
requirements, some emergency numbers are required to be set-up as non
emeregency numbers on device. On such device, coverting original number
to emergency number is required under the conditions where only
emergency call is allowed - e.g. no SIM. This patch implements this auto
converting logic and its configurations.
E.g. For Taiwan, 110 and 119 need to be converted to 112 under not
in-service state.
Bug: 28123861
Change-Id: I01b3072ae272c1af8d4a19b2fb6ae451b7268821
- Restore the previous logic to only show SHOW_WHEN_LOCKED windows
if appShowWhenLocked is not null.
- Add new logic to keep previous SHOW_WHEN_LOCKED window around if
it's still animating, as well as all the other windows that are
still visible.
Test:
- Make sure an SYSTEM_ALERT_WINDOW with SHOW_WHEN_LOCKED isn't
visible on the lockscreen.
- In Google Camera, click on the lock icon after launching it above
lockscreen.
Change-Id: Id33a8008c6edd6272e5110d9c0f1bf7aab007564
Fixes: 31300204
Fixes: 31319061
We need to do the slow dismissal when the user is locked, and not the
other way around.
Bug: 31203310
Change-Id: I6ad0fc831bd9dc26e7375916a0a091552f7790ae
Some top level Settings menus launch activities from other packages.
In that case, they should be considered as a part of the Settings
if they follow the Leanback's side panel style.
Add such activities to the whitelist to keep the PIP position.
Bug: 31142005
Change-Id: I12cab611b346154048cbd61f6a678f23b5a10c00
- Non-test-only DO/PO still can't be installed when there are
accounts.
- Test-only DO/PO can be installed even when there are accounts,
as long as all the accounts have the
"android.account.DEVICE_OR_PROFILE_OWNER_ALLOWED" feature.
Some authenticators claim to have any features, so to detect it,
we also check android.account.DEVICE_OR_PROFILE_OWNER_DISALLOWED
and disallow installing if any of the accounts have it.
- Also add logs on certain important events in DPMS.
Bug 28928996
Change-Id: I62efce10e9cc22e994ea8cae91a4fafcce25dd77
We're now calling __android_log_close prior to a fork, so this file
shouldn't need to be open.
bug: 31243313
bug: 30963384
Change-Id: I8c29adf075782eed966c9197d58f0325310f6c3a
