Searched refs:logs (Results 1 – 16 of 16) sorted by relevance
64 * @return debugErrno is a value the framework logs in case it is not 0.77 * @return debugErrno is a value the framework logs in case it is not 0.99 * @return debugErrno is a value the framework logs in case it is not 0.114 * @return debugErrno is a value the framework logs in case it is not 0.133 * @return debugErrno is a value the framework logs in case it is not 0.147 * @return debugErrno is a value the framework logs in case it is not 0.159 * @return debugErrno is a value the framework logs in case it is not 0.
176 hidl_vec<V1_4::LogMessage> logs) { in TEST_P() argument178 EXPECT_NE(0, logs.size()); in TEST_P()179 for (auto log: logs) { in TEST_P()
111 * @param timestamp Determines whether to show timestamps in logs or113 * @param showKeys Determines whether to show keys in debug logs or132 * Get whether the timestamps are shown in the debug logs or not.139 * Get whether the keys are shown in the debug logs or not.
18 logs (don't use ALOGV for errors so they can be debugged).
45 debug.mdpcomp.logs=0 \
61 debug.mdpcomp.logs=0 \
97 debug.mdpcomp.logs=0 \
26 * DumpstateMode::CONNECTIVITY - there is no reason to include camera or USB logs in this type52 * that many vendor logs contain significant amounts of private information and may come with
45 * user-installed packages (UIDs are OK, package names are not), and MUST NOT contain logs of
33 debug.mdpcomp.logs=0 \
35 be addressed after looking at the logs of the failing build. If the builds
83 * This API help to collect firmware/driver/pkt logs.
279 You may want to keep the `KernelLogger` so that charger still logs battery280 information to the kernel logs.
159 * This mostly contains firmware event logs.
4523 log_record_t logs[1]; member4758 assert_record_t logs[1]; member
1055 changes - see change logs in the apiext:VK_EXT_video_encode_h264,