| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |
|
|
|
|
|
|
|
|
| |
We are tagging these as "watchdog" to make them visible in the
reporting tools.
Also new am command to kill all background processes, mostly to make
it easier to test this stuff.
Change-Id: Ib9dc4747cd8bd44156fdf11d6a087cd4272203eb
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- IME service now switches between visible and perceptible depending on
whether it is being showm, allowing us to more aggressively free its
memory when not shown.
- The activity display time is no longer delayed by the activity
transition animation.
- New -R (repeat) option for launching activities with the am command.
- Improved some documentation on Loader to be clear about some methods
that apps should not normally call.
- FrameworkPerf test now allows you to select individual tests to run.
Change-Id: Id1f73de66dc93d63212183958a72119ad174318b
|
| |
|
|
|
|
|
|
| |
The start command can now take a package name or component name
for easier starting. New -S option allows you to force stop an
app before starting it.
Change-Id: I5c55b34dd794783f0f5f51851dc811b8c1b39b76
|
| |
|
|
| |
Change-Id: Ie71a8043eafe41f53a0b3dbb5170276d87acbc9b
|
| |
|
|
|
|
|
|
|
| |
To profile the looper, run the following command:
adb shell am profile looper start <process> <file>
adb shell am profile looper stop <process>
Change-Id: I781f156e473d7bdbb6d13aaffeeaae88bc01a69f
|
| |
|
|
|
|
|
|
|
|
| |
When composing an intent using am command line, certain extra fields
need to be added as a Uri (a Parceable in fact).
This patch adds a "--eu" parameter so that the provided value is
parsed as a Uri then added into intent's extra bundle.
Change-Id: I7110829554962d314aa58fd25083dd5041680a73
|
| |
|
|
| |
Change-Id: I5af730bc177635821a82d4dd3ec9130a5dcd525a
|
| |
|
|
|
|
|
|
|
| |
It's useful for some testing and debugging, to ensure all processes
are stopped before testing. 'kill' doesn't always work because sometimes the
system will restart the process immediately (e.g. if an app is running in
background).
Change-Id: I2c0caa38f74ee65ad6c35172fbf505227be7e7c3
|
| |
|
|
|
|
|
|
| |
For example:
adb shell am display-size 1024x600
Change-Id: I5df462acd3323bdaaaefa3126faea7dd8595b726
|
| |
|
|
|
|
|
|
|
|
| |
Adds a really crappy UI for toggling compat mode.
Persists compat mode selection across boots.
Turns on compat mode by default for newly installed apps.
Change-Id: Idc83494397bd17c41450bc9e9a05e4386c509399
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
First step of improving app screen size compatibility mode. When
running in compat mode, an application's windows are scaled up on
the screen rather than being small with 1:1 pixels.
Currently we scale the application to fill the entire screen, so
don't use an even pixel scaling. Though this may have some
negative impact on the appearance (it looks okay to me), it has a
big benefit of allowing us to now treat these apps as normal
full-screens apps and do the normal transition animations as you
move in and out and around in them.
This introduces fun stuff in the input system to take care of
modifying pointer coordinates to account for the app window
surface scaling. The input dispatcher is told about the scale
that is being applied to each window and, when there is one,
adjusts pointer events appropriately as they are being sent
to the transport.
Also modified is CompatibilityInfo, which has been greatly
simplified to not be so insane and incomprehendible. It is
now simple -- when constructed it determines if the given app
is compatible with the current screen size and density, and
that is that.
There are new APIs on ActivityManagerService to put applications
that we would traditionally consider compatible with larger screens
in compatibility mode. This is the start of a facility to have
a UI affordance for a user to switch apps in and out of
compatibility.
To test switching of modes, there is a new variation of the "am"
command to do this: am screen-compat [on|off] [package]
This mode switching has the fundamentals of restarting activities
when it is changed, though the state still needs to be persisted
and the overall mode switch cleaned up.
For the few small apps I have tested, things mostly seem to be
working well. I know of one problem with the text selection
handles being drawn at the wrong position because at some point
the window offset is being scaled incorrectly. There are
probably other similar issues around the interaction between
two windows because the different window coordinate spaces are
done in a hacky way instead of being formally integrated into
the window manager layout process.
Change-Id: Ie038e3746b448135117bd860859d74e360938557
|
| |
|
|
|
|
|
|
| |
Add missing NOTICE block for TagSoup in general NOTICE file.
Add comment in Android.mk to help reviewers locate the NOTICE for apache-http.
Modify build rule for 'am' command to pull in the NOTICE file.
Change-Id: I43c6c1468395b70d0942b3620f12e4b6f3d9a66b
|
| |\
| |
| |
| |
| |
| |
| | |
Merge commit 'deaa8ff1b10d38add4f7c276e7be2ffc19359a14'
* commit 'deaa8ff1b10d38add4f7c276e7be2ffc19359a14':
Some debugging support.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- New feature to "am monitor" to have it automatically launch
gdbserv for you when a crash/ANR happens, and tell you how to
run the client.
- Update dumpstate to match new location of binder debug logs
- Various commented out logs that are being used to track down
issues.
Change-Id: Ia5dd0cd2df983a1fc6be697642a4590aa02a26a5
|
| |\ \
| |/
| |
| | |
Change-Id: I9c752a5d10ae8d8e5ead1243b6abd4795204fc0b
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Don't kill processes for excessive wake lock use, even if they
are in the background, as long as they have running services.
Also fix some problems with this, such as not noting the kill
in battery stats.
And add killing of processes for cpu usage as well, along with
some optimizations to computing CPU usage.
And fix BatteryWaster to be better behaving for testing these
cases.
Add new "monitor" command to am to watch as the activity manager
does stuff (so we can catch things at the point of ANR).
Finally some miscellaneous debug output for the stuff here, as
well as in progress debugging of an ANR.
Change-Id: Ib32f55ca50fb7486b4be4eb5e695f8f60c882cd1
|
| | |
| |
| |
| | |
Change-Id: Ibc4ae63fb5f8025a847bec7d37a1fce5abd81b39
|
| | |
| |
| |
| | |
Change-Id: I9a0c28e59f87e30c81d18162bee082b851d07a94
|
| | |
| |
| |
| | |
Change-Id: I13b92284fa4e0765620552b7d9b08d7441254389
|
| | |
| |
| |
| | |
Change-Id: I95afb3bd02ce23bb8d0797ec4c33e27a9530988e
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This was mostly cloned from the "am profile" implementation. It's
intended to replace the old "kill -10" approach used by "runhat".
We could really use a native heap dump, so I pass a "managed"
flag through that indicates whether we want to dump the native or
managed heap. We don't currently have a native heap dump-to-file
function, so it currently just logs a warning.
(android.ddm.DdmHandleNativeHeap.getLeakInfo is a good start -- it
copies /proc/maps and then calls get_malloc_leak_info to get some
goodies. Needs some formatting to make it human-readable. I didn't
want to cram all that into this change.)
It would be useful if "am" didn't exit until the heap dump operation
completed, but I'm not sure how to do that.
Bug 2759474.
Change-Id: I46bc98067738d8c72ac0fc10002ca67bb4929271
|
| |\
| |
| |
| | |
Change-Id: I0598edad283a177a5ddcc30e20d2284503e6038e
|
| | |
| |
| |
| | |
Change-Id: I3f9b6a8d3c8a050156a6cc7ea0eb9de33b82f79a
|
| | |
| |
| |
| |
| |
| | |
This replaces the implementation with an equivalent one.
Change-Id: I1343ddee9414a67906cd426b8381ddbace873894
|
| | |
| |
| |
| | |
Change-Id: I31d066ae2c980cc293e55034446a63a0f42088ad
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Some applications are setting the MIME type field for an http:
intent, which is technically wrong because the recipient opening
the URI will get the MIME type from the header. This was hitting
a bug when we compute the intent filter when setting the
preferred activity, where we have to set both the MIME type and
data URI for the intent filter. (For file: and content: URIs
only the MIME type is needed, since these can be opened directly
through ContentResolver so everyone is presumed to be able to
handle them.)
Change-Id: Ia7025e6859e9c90997bf56c2c80f225fca7a2007
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
Allows starting Services in addition to Activities.
Change-Id: Ib078115f6200faa8907b35909af2f64b0c563b38
|
| |/ |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
non-ordered broadcast
Tell the broadcast receiver whether it is getting an initial sticky value,
so it will be quiet about attempts to do ordered broadcast stuff.
Note that the original bug being reported was not actually a crash, just
an error log. So all we are doing here is making the log quieter.
Change-Id: Iaf1b718d82093ec1197142410a64feff47eb3859
|
| |
|
|
|
|
|
| |
Clean up error handling and reporting in "am".
Make the usage message for "am" more informative.
Make it easier to turn on logging in GoogleHttpClient.
|
| |
|
|
|
|
|
|
| |
The am command is now the one that takes care of opening the target file,
handling the opened file descriptor to the process that will be profiled.
This allows you to send profile data to anywhere the shell can access, and
avoids any problems coming up from the target process trying to open the
file.
|
| |
|
|
| |
in the usage.
|
| |
|
|
|
|
|
|
|
|
| |
Now we have a 5-second time after home is pressed, during which
only the home app (and the status bar) can switch to another app.
After that time, any start activity requests that occurred will
be executed, to allow things like alarms to be displayed. Also
if during that time the user launches another app, the pending
starts will be executed without resuming their activities and
the one they started placed at the top and executed.
|
| |
|
|
| |
in the "am" utility.
|
| | |
|
| | |
|
| | |
|
| |
|
