Framework has specialized versions of java.lang.System.arraycopy() for
all primitive data types. These versions are not present on the Desktop
VM. This change replaces calls to any of the specialized versions with
the more general alternative - the one using Objects.
Note that this was already being done for char.
Change-Id: If1584125fea8ecc080fb39a5ee6cdb4d922d0c98
(cherry picked from commit e1960cc0b5)
Have KeyguardUpdateMonitor send the onRefreshCarrierInfo when the
subscription info changes, regardless of whether there are any
subscriptions (because there might be no sims).
Bug: 18752587
Change-Id: I8976c76aae9e3e633b6adace48dccb1e940dbc18
automerge: 54f9b1e
* commit '54f9b1eedc86a3066bedf3d8ea3e8ffbb83cb678':
Fix issue #18942959: Phone getting stuck then restarts after unplugging from Audi
The mask was earlier drawn as a thin ring at the display periphery.
This had undesirable effects when screenshots were taken, as the ring
was seen, as well as display content beyond it.
This patch modifies the mask to be a black canvas with portions erased
to improve the screenshot image.
Bug: 18772987
Change-Id: I25ef6387879613354308e015446fe325ed8c4515
automerge: cce8db2
* commit 'cce8db2c31a03d0c4e04f5851415d37032ae6621':
Revert "GpsLocationProvider: Read data enabled status from TelephonyManager." as it reintroduces b/18922524
FastPrintWriter needs to have its own lock for each instance, or
else one getting blocked can cause others to block and whacky deadlocks
result.
Also:
- Improve error reporting of SystemConfig to tell you which config
file is the problem.
- Fix CoreSettingsProvider to not spew errors if a setting is not
defined (it should just use a default value).
- Get rid of noisy init output of ConditionProviders.
- Reduce log noise of starting a process; move some of that information
to ProcessRecord to print on demand.
Change-Id: I1032d141ddd449968b74ab7b88ab36f2d228ad1a
The version of the warning with a named installer should be shown in
the case of a managed profile, not only a managed device.
Bug: 18224038
Change-Id: I27865f77e963b9b15416f2e4a4ffc38fed8f5532
Alleviates the user experience issue of having to turn on the device
manually when it goes to standby mode while the device occupies
the display.
Bug: 18882764
Change-Id: I10b239a599a310e47e3c2cb98737e4b0fdb4e435
We compare the set of networks defined in the supplicant with the
set of networks described as "configured" by the Wifi Manager. The
latter excludes ephemeral networks, so any network definition we
find in the supplicant data that we do not also find in the
configured network set, we ignore for backup purposes.
Bug 18917753
Change-Id: I8e0f258d0cdb72d7bf9482fafe64dc921419fcb2
This reverts commit e1d8dcd9e1.
Something funny happened in the process of submitting this,
swathes of strings.xml became mis-encoded.
Bug: 18224038
Change-Id: I0276ff3f880fe749546e8cc7e3e2f41c22c27705
Fall through to below logic and return null instead of crashing the
entire app. We already tell developers the value may be null.
Bug: 17781998
Change-Id: I05dce90ae6bc547d74f8c16d30b3dc7888a937fe
static void CallStaticVoidMethod is variable argument function.
if pass 0 to the function like: CallStaticVoidMethod(......, 0),
0 will be treated as INT data type.but in the CallStaticVoidMethod
implement 0 will be treated as pointer data type.Pointer in 64bit
system occupied 8 bytes, but in 64bit system int occupied 4 bytes.
if call function like: CallStaticVoidMethod(......, 0),
only low 4 bytes will be assigned 0.Turned out it actually call
function like this: CallStaticVoidMethod(......, 0xXXXXXXXX00000000).
intent to pass NULL to function but passed non-NULL parameter to
the function.this will cause GCDaemon crash.
Bug: 18911458
Change-Id: I9d700d3790a80dbee6826f64baf9ef5d81ca390f
Reviewed-by: Liao, Bruce <bruce.liao@intel.com>
Signed-off-by: Yong Yao <yong.yao@intel.com>
...an intent with invalid or null package uri
Also tweak battery stats to record in the history when we shut
down, to understand when restarts are due to clean shutdowns or
crashes.
Change-Id: I6443dafc23e356be9f569906f6081152d4f92d2b
When the task is removed from a task stack in window manager any
exiting activities left in the stack were orphaned. This led to a
memory leak. Removing all task activities from those that are exiting
fixes this problem.
Fixes bug 18943737.
Change-Id: I0a5ea8d2d3be89af7ccaf01385a226a2eafdf507
automerge: a7881fd
* commit 'a7881fd30b973f923c98d53bddf397d744b4229c':
Add new debug feature to track associations between processes. Also add some debugging for spurious service ANRs.
