| 27eb8a85c49daee3c360b878be972e1540ad57ba |
|
26-May-2017 |
Jeff Sharkey <jsharkey@android.com> |
Consistent "low storage" behavior.
When answering the question "how much space is free", use the same
logic for Settings UI and StorageManager.getAllocatableBytes(). That
is, the reported free space is usable bytes plus any cached data the
system is willing to delete automatically.
This does *not* include any reserved cache space, since we don't want
abusive apps to penalize other well-behaved apps that are storing
their data in cache locations. Callers freeing cached data need to
now explicitly request defiance of the reserved cache space. (Most
callers are already doing this by using FLAG_ALLOCATE_AGGRESSIVE.)
Rewrite the core logic of DeviceStorageMonitorService to understand
this new "reserved" cache space, and to be easier to understand. It
also now handles cached data on adopted storage volumes, which had
been ignored until now. Also fix bug where we had skipped "low"
broadcasts when the device skipped directly from/to "full" state.
Bug: 38008706
Test: cts-tradefed run commandAndExit cts-dev -m CtsJobSchedulerTestCases -t android.jobscheduler.cts.StorageConstraintTest
Test: cts-tradefed run commandAndExit cts-dev -m CtsAppSecurityHostTestCases -t android.appsecurity.cts.StorageHostTest
Change-Id: Icbdcf3b52775f7ada1ceaeff2f96094c8d8052f9
(cherry picked from commit ddff807b762a8a455287abc97aea8f97b98fb104)
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| 5ab5e1d9514bde75beaf87f46d45b6ffcaac9891 |
|
15-Apr-2017 |
Makoto Onuki <omakoto@google.com> |
Log screen-on latency with tron
Bug: 36776886
Test: manual test with "adb logcat -b all" and systrace.
Change-Id: I9e7188475a79899569046892e6f08c9005b84303
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| c3704427c9a34397fd90bf5438adae2eebcc97f6 |
|
28-Jan-2017 |
Shreyas Basarge <snb@google.com> |
BackupManager#cancelBackups() API
Introduces a cancelBackups() API for
BackupManager. When this function returns,
it is guaranteed that currently running
backup operations won't interact with
the active transport.
Bug: 34760860
Ref: https://docs.google.com/document/d/18MnfwkDfKNtXQBPRmL8vpVgfLgSWJsDja1Nm1QV5hOw/edit#heading=h.9p6yo0wx44k3
Test: GTS tests at ag/1893365
Change-Id: I67f78699bbe763ea71c85937fbc01a5b48694eed
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| fe6f85cac9e823fd33a134f7129fdf7310703293 |
|
20-Jan-2017 |
Jeff Sharkey <jsharkey@android.com> |
Introduce RescueParty.
When a device gets stuck in a crash loop, it's pretty much unusable
and impossible for users to recover from.
To help rescue devices from this state, this change introduces a new
feature that watches for runtime restart loops and persistent app
crash loops, and escalates through a series of increasingly
aggressive rescue operations. Currently these rescue levels walk
through clearing any experiments in SettingsProvider before finally
rebooting and prompting the user to wipe data.
Crash loops are detected based on a number of events in a specific
window of time. App stats can be stored in memory, but boot stats
need to be stored in system properties to be more robust.
Start up RecoveryService much earlier during the boot so we can
reboot into recovery when needed.
Add properties tha push system_server or SystemUI into a crash loops
for testing purposes.
Test: builds, boots, forced crashing walks through modes
Bug: 24872457, 30951331
Change-Id: I6cdd37682973fe18de0f08521e88f70ee7d7728b
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| dbc2ef417b5689dc502c52312e99f5dc2fd730a3 |
|
03-Jan-2017 |
Jeff Sharkey <jsharkey@android.com> |
Merge "Offer to measure disk stats using quotas." am: f8720b95be am: 4b80a4a372 am: 1e1cdbead1
am: 7664e61885
Change-Id: I91c0810aad2ec530650855bcd2f1d25c309717a1
|
| 5eb3eb58acf18dd624c477d5b11b45a23aea6261 |
|
13-Dec-2016 |
Jeff Sharkey <jsharkey@android.com> |
Offer to measure disk stats using quotas.
Now we're getting somewhere! This CL starts measuring disk usage
using quotactl(), which is almost instant and has much lower impact
on flash memory lifetime.
We now grant the per-app cache GID to every launched app, and the
ContextImpl logic that creates cache directories matches the logic
down in installd.
Test: builds, boots, quota stats match manual stats
Bug: 27948817
Change-Id: Ie269a2958ce0e1c17cb74dbfecc791a5c12922cf
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| 2250d56a0b47b93016018340c8f4040325aa5611 |
|
08-Nov-2016 |
Sudheer Shanka <sudheersai@google.com> |
Rename MountService to StorageManagerService.
Bug: 30977067
Test: Existing tests pass
Change-Id: Ieac0f11c2b249dcd60441b14c1f391e6f8131d42
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| b1ebc3b7a013a647dd4a3c6f006e00a017886b20 |
|
15-Apr-2016 |
Julia Reynolds <juliacr@google.com> |
Logging for ranker bundling.
Bug: 28210646
Change-Id: I90d1adaf23d318e07b1a9941ac45b5d6ae0624e8
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| 872d3b6e19933af6fa9ae65214b9f6df04fc3222 |
|
12-Jan-2016 |
Sergey Poromov <poromov@google.com> |
Quota exceeded API in BackupAgent
Should be also implemented in GMS BackupTransport.
Bug: 25693504
Change-Id: I6e4b2edb6d62addca0aced3e801d7629fb9394ca
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| fe06bf64d204c459699b0bf6465f9fb69208345e |
|
15-Dec-2015 |
Sergey Poromov <poromov@google.com> |
Introduce BackupManager#requestBackup & BackupObserver API
Introduces a way to request immediate backup for list of packages
and receive callbacks on backup progress.
Bug: 25688526
Change-Id: Ib826933d44f4ebf2b981f8be366215b2d37847e2
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| 08c47a5dece977a55d250d98bda9e2a8df8b6ed0 |
|
15-Oct-2015 |
Dianne Hackborn <hackbod@google.com> |
Initial implementation of light-weight idle mode.
This mode turns on after the screen has been off for 15 minutes,
and then cycles through 15 minutes of idle and 1 minute of
maintenance, ragardless of whether the device is moving around.
It currently only impacts network access and sync/job scheduling.
It does not remove access to wake locks or alarms for any apps.
It also doesn't report in the public API that the device is in
idle mode (since it isn't modifying the behavior of the power
manager) -- this is probably what we desire, since we don't want
stuff like GCM to be reporting these frequent changes.
We'll probably at least want to have the alarm manager do some
kind of more aggressive batching of alarms in this most (not allowing
more than one wakeup every minute?). That's for the future.
Also updated batterystats to include this new information, which
means the format of some of the data has changed -- device_idle
is no longer a flag, but an enum of (off, light, full), and there
is no information about time spent in light modes.
Also added new data about the maximum duration spent in both light
and full idle modes, to get a better understanding of how those
are behaving.
And did a little cleanup of DeviceIdleController, removing the
sensing alarm which was redundant with the regular alarm.
Change-Id: Ibeea6659577dc02deff58f048f97fcd9b0223307
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| 37142ccd8a886408b5a031355f3f4e768c9f831c |
|
23-Sep-2015 |
Mojtaba Seyedhosseini <mseyed@google.com> |
am 08dcdb1a: am d70a7737: am 6e7cbb7c: Merge "Add logs for the ungaze gesture." into cw-e-dev
* commit '08dcdb1a5beac29643dca2a03c2e308760de636d':
Add logs for the ungaze gesture.
|
| 2d80edc232cad7d5fe17c2eb14d4263cbe2c757c |
|
19-Sep-2015 |
Mojtaba <mseyed@google.com> |
Add logs for the ungaze gesture.
-We add logs to track how much screen time we save with the ungaze feature.
Change-Id: I02bce959ce7ed5bc6c848e51256063c946ff3e87
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| 7534466318cb7bf74cdfc9fac630fe8b00e54e04 |
|
27-Aug-2015 |
Zhentao Sun <robinvane@google.com> |
am 48ff7fb5: am 49ea8298: am 60220b77: am fd538001: Merge "Added event log for camera launch gesture." into mnc-dr-dev
* commit '48ff7fb5495dff1325e61178928096d46ee6fa3e':
Added event log for camera launch gesture.
|
| 575b6fd9d10534a61ef229d59f4a57bcfcf73cac |
|
26-Aug-2015 |
Zhentao Sun <robinvane@google.com> |
Added event log for camera launch gesture.
Fixed b/23523554. Logs time duration when the underlying sensor was
turned on to detect camera launch gesture. The goal is to diagnose
the power consumption of the camera launch gesture.
Change-Id: Ie9554e0ba1c5b290c451f951472575289bae85c7
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| e4a0c5722b1d8db95dfc842d716452dbbf02c86d |
|
30-Jun-2015 |
Wale Ogunwale <ogunwale@google.com> |
Allow stacks to hold tasks on various sizes.
Tasks are now resizeable just like stacks. Adjusting the size
of a stack will also adjust the size of all it's containing
tasks. This model allows us to be more flexible
in using stacks as workspaces (like you would have in a
desktop environment) and tasks as the resizeable windows
within the workspace.
Also added "adb shell dumpsys window visible-apps" for
getting the list of visible app windows.
Bug: 22068114
Bug: 19182363
Change-Id: I5bf77063252a5abae4e327f6fc42e607091749f9
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| 9776c69790e474ef77566f8a0fc9c70106a675a5 |
|
04-Jul-2015 |
Dianne Hackborn <hackbod@google.com> |
am 9fac4c59: am 71b97214: am 36e52cdc: Merge "Device idle fixes: issue #22209630 and issue #22225665" into mnc-dev
* commit '9fac4c590568ae86efe597456955cc4a42ddc8d9':
Device idle fixes: issue #22209630 and issue #22225665
|
| 9fa3c56486dd9ea9a5622bd636de6f0f18b56f32 |
|
03-Jul-2015 |
Chris Wren <cwren@android.com> |
am 0002b3ba: am f1cc651b: am c58d1695: Merge changes from topic \'tron\' into mnc-dev
* commit '0002b3bab2e96c3c54b286cbea6bada14c6a91ae':
remove double count of panel open
report notification load on panel reveal
|
| 36e52cdcd3bbcb2354db2735a6f3c87a6ca4a925 |
|
02-Jul-2015 |
Dianne Hackborn <hackbod@google.com> |
Merge "Device idle fixes: issue #22209630 and issue #22225665" into mnc-dev
|
| 3b16cf4f47142a845bf0ede54ef8ef956506c6c3 |
|
02-Jul-2015 |
Dianne Hackborn <hackbod@google.com> |
Device idle fixes: issue #22209630 and issue #22225665
Issue #22209630: Only allow whitelisted apps to put apps on the temp whitelist
We now check whether the calling app is a system uid or in the whitelist
and, if not, throw an exception.
Issue #22225665: Alarm still goes off in idle mode (doze)
Fix a bug where we were not clearing the calling identity when coming
through the dump command to the service, and as a result when we would
eventually call out to the alarm manager it wouldn't do what we want.
This was only broken when being controlled by the shell.
Also adjust the network policy manager service's handling of device
idle transitions to only toggle the device idle state, which gets rid
of the long delay we have coming out of idle mode. And add in a bit
of logging around going in/out of idle mode to try to understand where
things may be slow in the future.
Change-Id: I4a41f790e9b0bb31330314b94111557d479f2ba5
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| b659c4f44a839e6ad7ef6834cc0d35954e04460a |
|
25-Jun-2015 |
Chris Wren <cwren@android.com> |
report notification load on panel reveal
Counts may differ from user perception. For example, if notifications arrive
after the shade is open (even if it is only peeking) there will not be another
panel_reveal before the user sees the shade. User perception is more accurately
measured by visibility events.
Peek events will report the notificaiton load as 1.
Bug: 20088581
Change-Id: I10221d4b66a18c223aae21e616615f087c65b1e1
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| 960bf082a42680fe283c809a0b706e53be5f88b9 |
|
23-Jun-2015 |
Chris Wren <cwren@android.com> |
am 8471e833: am 2ebdeeca: am ca7febf4: Merge "add rank to notification visibility log" into mnc-dev
* commit '8471e833f61cfc9d373b957d97a9eeec2b779e78':
add rank to notification visibility log
|
| d1dbc92d67af4cb72bb2faff9011d36b6833bbfd |
|
19-Jun-2015 |
Chris Wren <cwren@android.com> |
add rank to notification visibility log
Only sysui knows the true rank, since it can (and does) reorder things.
The visibility logs are down in the service because it has other bits of data.
Bug: 21395744
Change-Id: Ibf9479dc2306fb27fb5df3bf21e161478d36d587
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| a48924f2841ff49885ab99a819ff3d94de201646 |
|
18-Jun-2015 |
Yusuke Sato <yusukes@google.com> |
Record WM_BOOT_ANIMATION_DONE in WindowManagerService
to track user-perceived boot performance. Even though we already
have BOOT_PROGRESS_ENABLE_SCREEN, that one is recorded before
WindowManagerService asks bootanim to exit. Since it takes a few
seconds for bootanim to exit (depending on desc.txt in the boot
animation zip file), WM_BOOT_ANIMATION_DONE would represent
user-perceived boot time better.
Bug: 21637637
Change-Id: I9d81dbf3fdb5dcd780e3fc3ca01c8ada4d6f16ef
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| 82ba59de0ea32cdfa1423823bce7fa20c878cd02 |
|
05-Jun-2015 |
Chris Wren <cwren@android.com> |
add a log for notification alerts.
Bug: 21242827
Change-Id: I1b8beee5cc12a9cd23e81554f7f2236ddc29e2b6
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| e6ddb8a1348d2ea53bc3033be43c4dae922b653a |
|
27-May-2015 |
Chris Wren <cwren@android.com> |
add event timers to all notification logs.
previously, some logs had only some times, and not others.
Bug: 21394955
Change-Id: I0d7af163be23f5a989c35aba6e6f6879672543fc
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| 6650e5767b3d69268af7238cfa65dde6a9f2e0a3 |
|
15-May-2015 |
Chris Wren <cwren@android.com> |
log notification longevity and freshness
Split out monolithic visibility notifications into individual logs for
each visibility change with longevity and freshness.
Add exposure time to cancelation logs.
Bug: 20122735
Change-Id: I56c112cdb54fb65b41cfbef4c36ce8706729c5cb
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| a576b4d3be8687f0a65fc5777424955d551604e4 |
|
24-Apr-2015 |
Jeff Brown <jeffbrown@google.com> |
Add code to collect data about auto-brightness adjustments.
Write samples of the old and new state to the binary event log whenever
the user modifies the auto-brightness adjustment. We wait a few seconds
before logging to ensure that the user is satisfied with the adjustment.
Bug: 19786916
Change-Id: I41402decd1034d0839aa0f47495bc00907ab9c08
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| f45e16f2da8de1df2de3addc44bd2da717ac0255 |
|
22-Apr-2015 |
Dianne Hackborn <hackbod@google.com> |
Merge "Work on issue #20401752: device idle and alarms."
|
| f70faed503c8482266e6acb94dd5281488a9117e |
|
21-Apr-2015 |
Dianne Hackborn <hackbod@google.com> |
Work on issue #20401752: device idle and alarms.
Main change is to fix problems in the alarm manager where it
was not doing a good job at scheduling the device idle wakeup
before an alarm. To fix this, we now keep explicit track of
the next "wake from idle" alarm so we can consistently use that
to adjust the time of the device idle alarm if needed.
Also a bunch of debugging stuff to help further diagnose this
problem:
- Alarm summary now includes the last time the alarm went off.
- Improved dumpsys output of alarms.
- New event log tags for changes related to idle state.
Change-Id: Idd2c8d24ae23379f7c75815ddbc6835c2a04656c
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| 640e387ce4e8aa97a8139fda54a5f5468e2ff18b |
|
21-Apr-2015 |
Chris Wren <cwren@android.com> |
Add notification lifetime to the cancel message.
Also track the total lifetime in the notificaiton record.
Bug: 20122735
Change-Id: I09668be0161de0e1d8201b069e533a9a2203c83c
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| 8a52c4491dfbb8354a92c0a1e6abc86848e187c6 |
|
26-Mar-2015 |
John Spurlock <jspurlock@google.com> |
AudioService: Observe changes to output devices per-stream.
- Keep track of calls to AudioSystem.getDevicesForStream.
- Report device changes for the base streams to the binary event log.
- Fire internal intent so volume UI can respond to changes.
- Update devices when new routes are reported.
Bug: 19618959
Change-Id: I7bbd497b178d9829accc19e6c951a711aef8590c
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| 9087433753a5068819dcd3e86bdc2cce82bb8040 |
|
10-Mar-2015 |
John Spurlock <jspurlock@google.com> |
AudioService: Write base stream volume changes to the event log.
- Add a new volume_changed event, reported at the stream level.
- Only include changes to base streams (no aliases).
- Include the caller for each change. A caller is either:
- a pkg name (for external calls or known media sessions)
- a system server class's log tag (for internal calls,
disambiguates "android")
Bug: 19599935
Change-Id: Ia61b68ff1e7e2907a24972790ec052bfe099e665
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| 265c10587a0716f46cd17441dea18da303e0725e |
|
23-Jul-2014 |
Christoph Studer <chstuder@google.com> |
NoMan: Optimize grouped notifications
When SysUI is the only notification listener, drop group children
if there is a group summary in NoMan.
There are two changes needed to achieve this:
1. Cancel children when a summary is posted
2. Drop children if there is a summary
Bug: 18460939
Change-Id: I5a3f30b0b23b2a784783749f58352c05a7fb9e59
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| 1382e67e1c551796ed626a68fa91f2b4cdfbfa1a |
|
24-Oct-2014 |
Christoph Studer <chstuder@google.com> |
NoMan: Add update bit to notification_enqueue log
Log whether an enqueued notification updated a previously present
notification.
Bug: 18083122
Change-Id: Ie6ed69f0bf53c668701b44e33282ca74b509a7e3
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| 81e5b5f2f85ea0a00c4ee51f648dbe37b25ab9bd |
|
22-Oct-2014 |
Christoph Studer <chstuder@google.com> |
NoMan: Log canceled notifications
In addition to logging cancelation command, also log actually
canceled notifications via the new eventlog tag notification_canceled.
Bug: 18083122
Change-Id: I1e3e1e1368f39519f34c002ae374f318f647a401
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| 4da84cd56582fb4025eb5a9a1d4bb5b5b4a50cef |
|
21-Oct-2014 |
Christoph Studer <chstuder@google.com> |
SysUI/NoMan: Log clicks on notification buttons
Introduce notification_action_click logtag that is logged whenever
the user clicks any notification button. For standard templates, we
also log the index of the pressed action button.
Bug: 18064190
Change-Id: Icb07795ff711729d16bde0b7e03d13c2f466779c
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| 5dcc3aca42255616c48388e012d1b43b2ac450f9 |
|
14-Oct-2014 |
Filip Gruszczynski <gruszczy@google.com> |
Log wallpaper crashes.
Change-Id: I40d9876dad2a8ec98135e3df127950dc3797040b
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| 3933a5dc8c8c04458c5b8c01919d7449c6d00497 |
|
04-Oct-2014 |
Jeff Sharkey <jsharkey@android.com> |
More durable logging around system app upgrades.
We've been seeing some really funky behavior when upgrading or
downgrading system apps around OTA time. Put more of these one-time
logs into durable storage to help investigate.
Bug: 17805839
Change-Id: If898d7df229c1f71e598b0d965325c272060e5e7
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| 4cf9f007e6b66c0a970600f66b4229c4ede73f7f |
|
06-Aug-2014 |
Christopher Tate <ctate@google.com> |
Add event logs for full backup/restore milestones
Bug 16689703
Change-Id: If870f1b7b9cb3929ac1edc38affc688a37c2acfd
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| 78403d79739605511ea88b653564d81d7bf4bbba |
|
28-Jul-2014 |
Chris Wren <cwren@android.com> |
Add a log and statistics for notification expansion.
Bug: 16618854
Change-Id: I501f396fa495e1e55a27d7d0b65aac66495418c1
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| 03b87a2f40c26948b7b0c9409c33ad44857218cf |
|
30-Apr-2014 |
Christoph Studer <chstuder@google.com> |
Log notification clicks
Emit notification_clicked log events when a notification
is clicked from SystemUI.
Also refactor the onNotificationClicked method to work with
a key instead of individual notification params.
Change-Id: Iffd15e95d46371b2ae7bfd00b2c348d9f4cf5d14
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| 92b389da2a60ac51e804031494fea177fc1c47be |
|
01-Apr-2014 |
Christoph Studer <chstuder@google.com> |
Write eventlog entries for notification visibility
Keep track of notifications shown in the notification panel
and log them via eventlog.
Added the following eventlog tag:
* notification_visibility_changed
Bug: 13442201
Change-Id: Ifb74ec2492967dc787b4de86db7d7f00be6c7f74
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| 760ea554d0022fd88bbe13e3ef7c75cbe8613af6 |
|
21-Mar-2014 |
Christoph Studer <chstuder@google.com> |
Write eventlog entries for notification panel visibility
Change-Id: Ie7e15ed15739cb5f057c900e1cadf90824b2b4ef
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| e6a7d93420406cdbdf1b88b9635344dea52b4650 |
|
13-Mar-2014 |
John Spurlock <jspurlock@google.com> |
Add more information to existing notification_* events.
Include calling UID/PID in the existing
notification_{enqueue/cancel/cancel_all} event logs.
Include a new "reason" arg for cancel + cancel_all to
identify listener vs noman vs statusbarmgr calls.
Found and fixed a cancelAll path (from statusbarmgr)
that was not logging at all.
Bug:13442201
Change-Id: I2e1f875076a96b1fe3b86e8990641efb1cadfcfb
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|
| 9158825f9c41869689d6b1786d7c7aa8bdd524ce |
|
22-Nov-2013 |
Amith Yamasani <yamasani@google.com> |
Move some system services to separate directories
Refactored the directory structure so that services can be optionally
excluded. This is step 1. Will be followed by another change that makes
it possible to remove services from the build.
Change-Id: Ideacedfd34b5e213217ad3ff4ebb21c4a8e73f85
/frameworks/base/services/core/java/com/android/server/EventLogTags.logtags
|