- Added permission requirements for communicating with system enrollment
app
- Added priv-app permission build target
'com.example.android.voiceinteractor.xml'
- Updated README usage directions
- Added log messages when reading audio from AudioRecord
- Changed AudioRecord read calls to request all of the desired data in a
single .read() call
- Refactor AudioRecord buffer settings to top of service files in
Duration type
- Compute bytesPerSecond based on EventPayload AudioFormat passed by
SoundTrigger HAL
- Fixed keyphrase used by VoiceInteractionService to "X Google"
- Added trace events for tracking the time to read audio in VIS after a
trusted onDetected() callback.
Bug: 168305377
Test: manual
Change-Id: I6c1db7f70ddd62d21c0bb7eba663fe9503d96ae3
Broken e2e test due to changing the way files are uploaded. This should
fix it.
Test: npm run test:e2e
Bug: b/241571689
Change-Id: I74c8d489ecf4c0627d844505037f886d1f183b72
Upload multiple files via clicking to browse or drag and drop.
Test: spin up winscope and see if the files upload.
Bug: b/241571689
Change-Id: I67b801008ddcfa5be3ae724eb4db6f9b723eebd6
Previously, we only looked for LICENSE* files. This adds support for
detecting COPYING* files as an alternate representation of the license.
Bug: 234563254
Test: get_rust_pkg.py -add3prf quiche
Change-Id: Ic04ef42f349879be18a4307bd863288dfa81b5fc
Parsers support real timestamps (along the legacy elapsed timestamps) for the following trace types:
- Accessibility
- InputMethodClients
- InputMethodManagerService
- InputMethodService
- ProtoLog
- SurfaceFlinger
- Transactions
- WindowManager
Bug: 235196806
Test: cd development/tools/winscope-ng && npm run build:unit && npm run test:unit
Change-Id: Ib26fa7c4b8b4cc0ed3128c6805c57fcb1ce7ae85
- segregate unit and e2e test utils
- add UnitTestUtils::getParser()
Test: cd development/tools/winscope-ng && npm run build:all && npm run test:all
Change-Id: I48212fe9bb1ef01b09301cd8a721f10ea18c9b77
- add class TimestampType (ELAPSED or REAL)
- add class Timestamp (timestamp value + type)
- use bigint (instead of number) to represent timestamp values
Test: cd development/tools/winscope-ng && npm run build:all && npm run test:all
Change-Id: I1db9f2f9d48ca54bd79d3ffb989f6dde9ac11cd7
Add windowContainer > identifier > title property for imeControlTarget,
imeInputTarget and imeLayeringTarget, which are extracted from WM trace,
into the WM&SF Properties panel for ImeTrace InputMethodManagerService.
Also, change the titles of 'IME...Target' properties into clickable
text (originally, the clickable text was in the right column).
Screenshot: https://screenshot.googleplex.com/BWZFJgca2YmXk6X.png
Bug: 236226833
Test: manual on local build of Winscope
Change-Id: I8da832fa36c722688c73a16d5381d7ef49fbfb0e
Previous CL ag/19516273 added tests for the new logic in
ime_processing.js, which extracts properties from WM & SF trace
entries and combines them into IME trace entries. However, the
checks used in the tests were a bit vague as they just expected some
fields to be defined (non-null). This CL improves on this by specifying
some values to verify the extracted WM / SF fields' correctness.
Bug: 237744706
Test: yarn run test
Change-Id: I1f237135520f0ef5dc85b257f6602196aa534197
Test: yarn run v1.22.18
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Bug: 241061291
Change-Id: I109aa17a607ee6cd5978f4af4c51dc49a67f5d98
* changes:
Add tests for combining IME with WM / SF entries
Fix SFLayer TypeErrors in Winscope
[11] Change matching WM/SF entry to IME entry algo
[10] Refine WM & SF Properties IME subpanel
[9] Fix null targets in IME's 'WM & SF Properties'
Add tests for the new logic in ime_processing.js, which extracts
properties from WindowManager and SurfaceFlinger trace entries and
combines them into IME trace entries.
Some simple IME, WM and SF traces are added into
spec/traces/ime_processing_traces, and the results of combining them are
asserted for in spec/ImeProcessingSpec.js.
Bug: 237744706
Test: yarn run test
Change-Id: If2a053c4885cc4c522c93cf747b94cb69aceb1c6
Fix the errors that pop up when clicking `SurfaceFlingerLayer` in
SurfaceFlingerTrace panel's Hierarchy panel, by taking care of cases
where the property is null.
Bug: 240405932
Test: manual on local build of Winscope
Change-Id: Ic9e8f6e75dcfde8af97aeb5254d1e2d8f7b3d669
Due to there being some slightly different timestamps between WM/SF
trace and IME trace, we want to allow some "fault tolerance" -- even
if a WM/SF entry comes after IME entry in time, it may still be the
corresponding entry if it's within a manually-defined "fault tolerance"
time.
For now, fault tolerance is defined to be 200ms. So if a WM/SF entry is
within IME entry +- 200ms, it may be considered a matching /
corresponding entry. Within this range, we will always try to pick a
WM/SF entry that comes before the IME entry. If there is no such WM/SF
entry, then we will pick one that comes after.
Bug: 236226833
Test: manual on local build of Winscope
Change-Id: I0782ec520284517bf964eeffd552e6175758c9f1
Make the following headers clickable; upon clicking, will show proto
details in the 'Properties' sub-panel on the right:
- WMState
- Ime Container
- Input Method Surface
- IME Insets Source Provider
Add the following properties:
- Focused window's color / rgba information -- focused window title
extracted from WM trace, the corresponding surface's rgba extracted
from SF trace
- InputMethod Window's visibility
- InputMethod Surface's visibility
- InputMethod Surface's rect & screenBounds
Remove the following properties:
- ImeContainer's rect & screenBounds
Rename the following properties:
- Frame (under 'Focus' heading) --> Input Control Target Frame
Screenshots: in buganizer ticket
Bug: 236226833
Test: manual on local build of winscope
Change-Id: I2a2747b57639f40c8f6bf71d5cb49268e4ee5044
Fix incorrect names of properties being extracted from WM Trace:
- 'Input Method Control Target' has been replaced with 'IME Control
Target', 'Input Method Input Target' with 'IME Input Target', and 'Input
Method Target' with 'IME Layering Target'.
Bug: 239145867
Test: manual on local build of winscope
Change-Id: If067cf73de32d4374b33d1f07f179b63c9fb0c27
