OpenGrok
Home
Sort by relevance
Sort by last modified time
Full Search
Definition
Symbol
File Path
History
|
|
Help
Searched
full:timestamps
(Results
251 - 275
of
877
) sorted by null
<<
11
12
13
14
15
16
17
18
19
20
>>
/sdk/eclipse/plugins/com.android.ide.eclipse.adt/src/com/android/ide/eclipse/adt/internal/editors/layout/descriptors/
CustomViewDescriptorService.java
293
Map<ResourceFile, Long>
timestamps
=
local
310
timestamps
.put(file, file.getFile().getModificationStamp());
313
return
timestamps
;
526
Map<ResourceFile, Long>
timestamps
) {
538
mTimeStamps =
timestamps
;
559
// Prevent checking actual file
timestamps
too frequently on rapid burst calls
/external/chromium-trace/catapult/third_party/flot/
API.md
534
The time series support in Flot is based on Javascript
timestamps
,
538
1970 00:00:00 UTC. This is almost the same as Unix
timestamps
, except it's
548
timestamps
. Many will want the
timestamps
to be displayed according to
550
produced. Some want the localized experience, where the
timestamps
are
555
Default behavior is that Flot always displays
timestamps
according to
603
possible to generate the
timestamps
manually client-side.
606
pretend trick described above. But you can fix up the
timestamps
by
613
The alternative with core Javascript is to interpret the
timestamps
623
interpret the
timestamps
according to that time zone
[
all
...]
/packages/apps/Camera2/src/com/android/camera/one/v2/
OneCameraZslImpl.java
182
* The sensor
timestamps
(which may not be relative to the system time) of
262
// Clear out old
timestamps
from the set.
263
// We must keep old
timestamps
in the set a little longer (a
269
ArrayList<Long>
timestamps
= new ArrayList<Long>(mCapturedImageTimestamps);
local
270
Collections.sort(
timestamps
);
271
for (int i = 0; i <
timestamps
.size()
273
mCapturedImageTimestamps.remove(
timestamps
.get(i));
[
all
...]
/cts/tests/camera/src/android/hardware/camera2/cts/
SurfaceViewPreviewTest.java
663
ArgumentCaptor<Long>
timestamps
= ArgumentCaptor.forClass(Long.class);
local
670
timestamps
.capture(),
673
// Validate
timestamps
: all
timestamps
should be larger than 0 and monotonically increase.
675
for (Long nextTimestamp :
timestamps
.getAllValues()) {
/cts/tests/tests/media/src/android/media/cts/
DecoderTest.java
208
List<Long>
timestamps
= new ArrayList<Long>();
local
209
decodeToMemory(res, RESET_MODE_NONE, CONFIG_MODE_NONE, -1,
timestamps
);
211
for (int i = 0; i <
timestamps
.size(); i++) {
212
Long thisTime =
timestamps
.get(i);
286
assertTrue("extractor
timestamps
were ordered, wrong test file?", inputoutoforder);
[
all
...]
/external/chromium-trace/catapult/telemetry/docs/pydoc/
telemetry.util.statistics.html
53
Because timestamp discrepancy is defined in terms of
timestamps
, we first<br>
54
convert the list of durations to monotonically increasing
timestamps
.<br>
93
<dl><dt><a name="-TimestampsDiscrepancy"><strong>TimestampsDiscrepancy</strong></a>(
timestamps
, absolute<font color="#909090">=True</font>, location_count<font color="#909090">=None</font>)</dt><dd><tt>A discrepancy based metric for measuring timestamp jank.<br>
96
of
timestamps
. Note that this is different from metrics based on the<br>
119
|
timestamps
| may be a list of lists S = [S_1, S_2, ..., S_N], where each<br>
/frameworks/base/core/java/android/app/usage/
NetworkStatsManager.java
43
* Queries can define a time interval in the form of start and end
timestamps
(Long.MIN_VALUE and
180
* end
timestamps
. Not aggregated over state or uid. This means buckets' start and end
181
*
timestamps
are going to be the same as the 'startTime' and 'endTime' parameters.
226
* This means buckets' start and end
timestamps
are going to be between 'startTime' and
266
* buckets' start and end
timestamps
are going to be between 'startTime' and 'endTime'
/build/libs/host/
CopyFile.c
154
* Set the permissions, owner, and
timestamps
on the destination file
166
* Start with
timestamps
. The access and mod dates are not affected
174
DBUG(("--- unable to set
timestamps
on '%s': %s\n",
/external/chromium-trace/catapult/telemetry/telemetry/timeline/
trace_event_importer.py
80
ctr.
timestamps
.append(event['ts'] / 1000.0)
99
'
Timestamps
are moving backward.')
113
'
Timestamps
are moving backward.')
/external/chromium-trace/catapult/tracing/tracing/model/
process_memory_dump_test.html
64
function createFinalizedProcessMemoryDumps(
timestamps
, createdCallback) {
66
var pmds =
timestamps
.map(function(timestamp) {
72
assert.lengthOf(pmds,
timestamps
.length);
/external/libpcap/pcap/
pcap.h
127
bpf_u_int32 sigfigs; /* accuracy of
timestamps
*/
346
#define PCAP_TSTAMP_PRECISION_MICRO 0 /* use
timestamps
with microsecond precision, default */
347
#define PCAP_TSTAMP_PRECISION_NANO 1 /* use
timestamps
with nanosecond precision */
/frameworks/base/core/tests/coretests/src/android/provider/
SearchRecentSuggestionsProviderTest.java
133
// guarantee that group 1 has older
timestamps
145
// guarantee that group 2 has older
timestamps
215
// guarantee that group 1 has older
timestamps
(and will be pruned first)
/frameworks/base/media/java/android/media/
Image.java
176
* increasing. The
timestamps
for the images from different sources may have
190
* increasing. The
timestamps
for the images from different sources may have
200
* set the
timestamps
correctly before sending them back to the
/libcore/luni/src/test/java/libcore/java/sql/
OldPreparedStatementTest.java
2032
Timestamp[]
timestamps
= { new Timestamp(2007, 10, 17, 19, 06, 50, 23),
local
2107
Timestamp[]
timestamps
= { new Timestamp(2007, 10, 17, 19, 06, 50, 23),
local
[
all
...]
/ndk/sources/host-tools/make-3.81/
configure.in
95
# Find out whether our struct stat returns nanosecond resolution
timestamps
.
98
AC_MSG_CHECKING([whether to use high resolution file
timestamps
])
117
[Use high resolution file
timestamps
if nonzero.])
/external/webrtc/webrtc/modules/audio_coding/codecs/red/
audio_encoder_copy_red_unittest.cc
214
// Checks that the correct
timestamps
are returned.
282
// Checks that the correct
timestamps
are returned.
/external/webrtc/webrtc/modules/audio_coding/neteq/
timestamp_scaler_unittest.cc
28
NetEqDecoder::kDecoderPCMu; // Does not use scaled
timestamps
.
49
NetEqDecoder::kDecoderPCMu; // Does not use scaled
timestamps
.
/external/webrtc/webrtc/modules/remote_bitrate_estimator/test/
bwe_test_framework.h
363
// The file should contain nanosecond
timestamps
corresponding to the time
364
// when the network can accept another packet. The
timestamps
should be
/frameworks/av/include/media/stagefright/
SurfaceMediaSource.h
223
// It is used to offset the output
timestamps
so recording starts at time 0.
226
// offset
timestamps
.
/hardware/qcom/media/msm8974/mm-core/omxcore/inc/
OMX_Types.h
272
* to accomodate high resolution
timestamps
(e.g. DVD presentation
timestamps
based
/hardware/ti/omap3/omx/system/src/openmax_il/omx_core/inc/
OMX_Types.h
272
* to accomodate high resolution
timestamps
(e.g. DVD presentation
timestamps
based
/hardware/ti/omap4xxx/domx/omx_core/inc/
OMX_Types.h
272
* to accomodate high resolution
timestamps
(e.g. DVD presentation
timestamps
based
/external/opencv3/3rdparty/include/ffmpeg_/libavformat/
avformat.h
353
#define AVFMT_NOTIMESTAMPS 0x0080 /**< Format does not need / have any
timestamps
. */
355
#define AVFMT_TS_DISCONT 0x0200 /**< Format allows timestamp discontinuities. Note, muxers always require valid (monotone)
timestamps
*/
369
increasing
timestamps
, but they must
372
timestamps
. If not set the timestamp
593
AVSTREAM_PARSE_TIMESTAMPS, /**< full parsing and interpolation of
timestamps
for frames not starting on a packet boundary */
688
* of which frame
timestamps
are represented.
[
all
...]
/build/blueprint/tests/
test.sh
56
# The 2 second sleeps are needed until ninja understands sub-second
timestamps
/build/tools/acp/
acp.c
242
fprintf(stderr, " -t preserve
timestamps
\n");
Completed in 795 milliseconds
<<
11
12
13
14
15
16
17
18
19
20
>>