summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2014-04-17app_process: change to create app_process link to app_process64linaro-juice2Yongqin Liu
since commands like am/pm use app_process to run java classes, if we only have 64 bit version in the system, these commands will be failed. use symbol link to it is a work around. but which version should be used for am/pm when both enabled need to be talked with google and arm. before that we use the link here since we only have 64 bit version installed now, so that we can have cts run on the images Change-Id: I5d785e3c7f43d9f59f62327600a3e0eb2e4093e1 Signed-off-by: Yongqin Liu <yongqin.liu@linaro.org>
2014-04-16PowerManagerService: use disablesuspend property to disable suspend modeAmit Pundir
Signed-off-by: Amit Pundir <amit.pundir@linaro.org>
2014-04-16Change default settingsAshok Bhat
Never turn off the display Disable lock screen Stay on when plugged in Change-Id: I06c4ea86d2bf5615e2725749f2edbcc645cb29ff Signed-off-by: Ashok Bhat <ashok.bhat@arm.com>
2014-04-16Increase timeoutsAshok Bhat
Increase timeout by 20x to prevent ANR and other timing problems in slow platforms. Change-Id: I221336bd65d5af69aef7736ca4239343c1406d14 Signed-off-by: Ashok Bhat <ashok.bhat@arm.com>
2014-04-16Temporary workarounds to boot to GUIKévin PETIT
Change-Id: I4765c4007a31934c6a0f8bce9251d7a035c752ef Signed-off-by: Kévin PETIT <kevin.petit@arm.com>
2014-04-07Merge "[ActivityManager] Reduce report ANR on wrong activity."Craig Mautner
2014-04-08[ActivityManager] Reduce report ANR on wrong activity.riddle_hsu
Symptom: ANR report on wrong activity. Root Cause: KK changed resume behavior that will not update focus when only resume, if the activity blocked, it may report ANR on previous focus. By original concept, it will try to correct the ANR target, but the stack of waiting(waitingVisible=true) activity may different with current top stack. If it gets key dispatch timeout, mResumedActivity and mPausingActivity of its stack will be null becuase it is not top stack. Then it is unable to change ANR target to the real no response activity. Solution: Use focused stack to get the real culprit. Reproduce steps: 1.Launch an Activity X from launcher, press home key. 2.Launch X from launcher again, X blocks(sleeps 15sec) in onResume, press back key in the beginning of blocking duration. 3.ANR dialog shows launcher is no response. Change-Id: I99416ad91e349096f995990f2240a97616fbaf28
2014-04-04Merge "Always call super.onCreate(). Always."Nick Kralevich
2014-04-04Always call super.onCreate(). Always.Christopher Tate
Bug 12991134 (cherrypick of commit 9d6376a1d88ab5b3a41ee4400e3aaa4c4ee69e2a) Change-Id: Ife16ef93408253e3318a06dc0206ab4b88c7f367
2014-04-03Merge "Marquee text RTL improvements"Raph Levien
2014-04-03Merge "Remove ProcessState::mArgc,mArgV,mArgLen"Narayan Kamath
2014-04-03Remove ProcessState::mArgc,mArgV,mArgLenNarayan Kamath
These look like historical oddities, and weren't really being used for anything useful. Process:setArgV0 was being called by android.util.Process, but that functionality can be moved directly into the implementation of that class. bug: 13647418 Change-Id: I216c8f8a4c065f0cf3a61f19f9e32decd26f93f6
2014-04-03Merge "Update ViewRootImpl for 64bit functor type."Ben Murdoch
2014-04-02Merge "Use default visibility for Snapshot::getLocalClip."Ben Cheng
2014-04-02Use default visibility for Snapshot::getLocalClip.Ben Cheng
The method is in libhwui.so but used by libandroid_runtime.so (via android_view_GLES20Canvas.cpp). If the compiler decides not to inline this method, the linker won't be able to resolve the dependency when it has hidden visibility. The problem is found when testing GCC 4.9. Change-Id: I3b4d096c7767f0bef0796886dfb2c5ba2ecff48c
2014-04-02Update ViewRootImpl for 64bit functor type.Ben Murdoch
Change-Id: Ie9020f0276c58ebf0977e4aef725fbc26aaf67b2
2014-04-02Merge "Move zygote startup logic to the frameworks."Narayan Kamath
2014-04-02Move zygote startup logic to the frameworks.Narayan Kamath
The Zygote class is now in com.android.internal.os. It is responsible for the vast majority of work before and after the call to fork(). It calls back into the Runtime via the new dalvik.system.ZygoteHooks class to allow the Runtime to perform pre fork cleanup and post fork initialization. The native code in Zygote.cpp is a direct and straightforward port of the existing code in art. Most differences are superficial, for example : - We use C style logging (ALOGE) instead of stream based logging. - We call env->FatalError() instead of using LOG(FATAL) Change-Id: Ia101fb2af12d23894fe57e4134d2bc6d142e5059
2014-03-31Merge "Fix RenderScriptGL setSurfaceTexture problem"Jason Sams
2014-03-31Merge "Change when the SELinux relabel of /data/data occurs."Nick Kralevich
2014-03-31Merge "Improve detail message for X509TrustManagerExtensions argument ↵Brian Carlstrom
validation"
2014-03-31Improve detail message for X509TrustManagerExtensions argument validationBrian Carlstrom
Bug: 13728564 Change-Id: I03d08babcdc0d11baff5e76a339b4285e92edee8
2014-03-31Merge "Don't make isSafeMode a field on the Zygote class."Narayan Kamath
2014-03-31Don't make isSafeMode a field on the Zygote class.Narayan Kamath
This field is written and read exclusively by the system server, and should therefore belong to the SystemServer class. Change-Id: I2708a9a45c0c9cd1a6f563e8cc5844bd8c424bf7
2014-03-31Merge "Cast CallMethod's size_t parameters to jint"Narayan Kamath
2014-03-31Fix RenderScriptGL setSurfaceTexture problemXiaofei Wan
rsnContextSetSurfaceTexture() has no implementation in rs-jni, use nContextSetSurface() in setSurfaceTexture(). Change-Id: I066432575c9e74f21ea3a3776628b572b6e31377 Signed-off-by: Xiaofei Wan <xiaofei.wan@intel.com>
2014-03-30Merge "GlobalActions: Fix Airplane Mode on/off issue"Wink Saville
2014-03-28GlobalActions: Fix Airplane Mode on/off issuenagarw
Issue: Unable to turn off Airplane mode from power button after phone reboot Fix: Initialize mHasTelephony before the PhoneStateListener is registered to the TelephonyManager so that correct value of mHasTelephony is reflected when onServiceStateChanged callback is called. Bug: 13697360 Change-Id: Ide8afd9c16ea90b98b5912dbff440c5fd67b178d
2014-03-28Merge "Mark constructor as accessible in LayoutInflater."Jeff Hao
2014-03-28Merge "[ActivityManager] Fix a bug: unable to start activity after starting ↵Craig Mautner
activities during screen off."
2014-03-28Merge "Add support for additional international keyboard mappings"Michael Wright
2014-03-28Merge "DO NOT MERGE - [ActivityManager] Ensure consistency behavior when a ↵Craig Mautner
background activity brings another existed activity to front."
2014-03-28Mark constructor as accessible in LayoutInflater.Jeff Hao
Needed to bypass new access checks for fields, methods, and constructors. Change-Id: I8ff0b44a6cb4f4af1c72734bca366d8b89528030
2014-03-28Merge "Remove duplicate call disconnect codes."Anders Kristensen
2014-03-28Change when the SELinux relabel of /data/data occurs.Robert Craig
Perform the relabel of the /data/data/<pkg> directories when the app is being scanned by the PMS. The impetus for this change was that the data directories of forward locked apps were receiving the wrong label during an OTA. Because the PMS doesn't actually scan forward locked apps til later in the boot process, the prior restorecon call was actually applying the default label of system_data_file for all such apps. By performing a restorecon on each individual app as they are entered into the PMS we can handle them correctly. This mechanism also allows us to pass down the seinfo tag as part of the restorecon call which drops our need to rely on the contents of packages.list. Change-Id: Ie440cba2c96f0907458086348197e1506d31c1b6 Signed-off-by: rpcraig <rpcraig@tycho.ncsc.mil>
2014-03-27Merge "Reduce warning verbosity in aapt"Adam Lesinski
2014-03-27Merge "Do not show Home behind full screen activity"Craig Mautner
2014-03-27Merge "app_process: use LOCAL_MULTILIB := both"Colin Cross
2014-03-27app_process: use LOCAL_MULTILIB := bothColin Cross
Use LOCAL_MULTILIB := both to build app_process64 instead of duplicating the build rule. Also causes PRODUCT_PACKAGES := app_process to install both versions on 64-bit platforms, as the module names for both app_process and app_process64 are now app_process. Change-Id: Ia3c3265d15475771b0cae8bace53b8fbf351c186
2014-03-27Add support for additional international keyboard mappingsOlivier Gay
Add kcm mapping files for Arabic, Greek, Hebrew, Lithuanian and Spanish (Latin). Change-Id: I35cb2a4d6e016c6f565fba05710ba1626452fe68 Signed-off-by: Olivier Gay <ogay@logitech.com> Signed-off-by: Manuel Carthoblaz <mcarthob@logitech.com> Signed-off-by: Mathieu Meisser <mmeisser@logitech.com>
2014-03-27Merge "AArch64: Make frameworks/base code more portable"Narayan Kamath
2014-03-27AArch64: Make frameworks/base code more portableAshok Bhat
Changes in this patch include [x] Use %zu for size_t, %zd for ssize_t [x] Some minor changes have been done to conform with standard JNI practice (e.g. use of jint instead of int in JNI function prototypes) Change-Id: Id1aaa7894a7d0b85ac7ecd7b2bfd8cc40374261f Signed-off-by: Ashok Bhat <ashok.bhat@arm.com> Signed-off-by: Craig Barber <craig.barber@arm.com> Signed-off-by: Kévin PETIT <kevin.petit@arm.com> Signed-off-by: Marcus Oakland <marcus.oakland@arm.com>
2014-03-27Do not show Home behind full screen activityYevgen Pronenko
When ensureActivitiesVisibleLocked goes through foreground activity stack and reaches non-fullscreen activity, it sets showHomeBehindStack variable to true. If there is a fullscreen activity behind, showHomeBehindStack remains unchanged, which causes Home application to be displayed anyway. In this case user will see a fullscreen activity and Home activity simultaneously. To fix the issue we set showHomeBehindStack to false when we reach fullscreen activity in the activity stack. This was made visible by the following commit: 446ef1de8d373c1b017df8d19ebf9a47811fb402 Change-Id: I535c1283a4e26f5cf606375b837d4b7195324af0
2014-03-26Merge "CertificateChainValidator: initialize TrustManagerFactory"Kenny Root
2014-03-26Merge "jni: 64-bit compile issue"Mark Salyzyn
2014-03-26jni: 64-bit compile issueMark Salyzyn
- switch to PRId64 - some unused parameter warning suppression Change-Id: Ia36bd1a247bb6e866a6b1050ab1362ebc9d31786
2014-03-26Merge "Note libselinux dependency on packages.list format changes."Nick Kralevich
2014-03-26CertificateChainValidator: initialize TrustManagerFactoryKenny Root
Need to call TrustManagerFactory#init before use. I suspect this class isn't used anywhere since this hasn't caused a problem yet. Change-Id: I17425d0bba4795d71960062361a755830abba7de
2014-03-26Note libselinux dependency on packages.list format changes.Stephen Smalley
Change-Id: I3c34a86f5706c4fca826a8634936131e4e4fc297 Signed-off-by: Stephen Smalley <sds@tycho.nsa.gov>
2014-03-26DO NOT MERGE - [ActivityManager] Ensure consistency behavior when a ↵riddle_hsu
background activity brings another existed activity to front. Symptom: ANR occurs on previous activity. Root Cause: In KK, when a background activity starts another existed background activity (bring to front), if current focused stack is not the same as the stack of target starting activity, it will still resume the top of target stack, even the top activity on the target stack may not the same as target activity. And it will result incorrect focus, press back key will send to previous stack's top then popup ANR on previous activity: "Reason: Waiting because no window has focus but there is a focused application". By original code comment, it looks 'bring to front' should not happen in this issue case. // If the target task is not in the front, then we need // to bring it to the front... except... well, with // SINGLE_TASK_LAUNCH it's not entirely clear. We'd like // to have the same behavior as if a new instance was // being started, which means not bringing it to the front // if the caller is not itself in the front. If the caller and target are in the same stask, it will just deliver new intent without changing task order (the same behavior as JellyBean). So the patch concept is just to avoid to use target stack to resume top when caller and target are in different stack. Solution: Do not allow to resume another stack top if non-top activity try to bring existed activity to front. It may not be a good solution, just a reminder for the issue case. Reproduce steps: Assume A, B, C are different app tasks. When the application stack is like: Top C B A #Case 1: Home is foreground A starts B with NEW_TASK, C will resume, focus still stays at Home, and window order does not update. Then press back key or volumn key will result ANR on Home. #Case 2: App is foreground (Resumed activity is C) A starts Home, Home will resume, focus still stays at C, and window order does did not update. Then press back key or volumn key will result ANR on C. Change-Id: If05070123b248e2335791e43a4d4ddee6db11d84
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-08 14:46:57 +0000