Starting with Android R launched devices, debugfs cannot be mounted in
production builds. In order to avoid accidental debugfs dependencies
from creeping in during development with userdebug/eng builds, the
build flag PRODUCT_SET_DEBUGFS_RESTRICTIONS can be set by vendors to
enforce additional debugfs restrictions for userdebug/eng builds. The
same flag will be used to enable sepolicy neveallow statements to
prevent new permissions added for debugfs access.
Test: build, boot
Bug: 184381659
Change-Id: I45e6f20c886d467a215c9466f3a09965ff897d7e
Android 14.0.0 Release 1 (UP1A.231005.007)
* tag 'android-14.0.0_r1' of https://android.googlesource.com/device/google/sunfish:
Update sunfish SVN to 64
Update sunfish SVN to 63
sunfish: remove customizedMaxCachedProcesses
Update sunfish SVN to 62
Add hardware/qcom/wlan namespace
update namespace for generic hal
Explicit init .rc user.
update AIDL IGoogleBattery manifest version to 2
Revert "Revert "update AIDL IGoogleBattery manifest version to 2""
Revert "update AIDL IGoogleBattery manifest version to 2"
update AIDL IGoogleBattery manifest version to 2
Update overlay to support MAC randomization on open SSIDs
Set the default loop driver queue depth to 31
Revert "Migrate the blkio cgroup controller to the v2 hierarchy"
sunfish: move sg_write_buffer rule to common folder
Update Sunfish compatibility matrix and makefile to use the AIDL wifi_ext service.
Revert "Update Sunfish compatibility matrix to use the"
Add prebuilt protobuf 3.9.1 to vendor partition.
Update Sunfish compatibility matrix to use the AIDL wifi_ext service.
[Sunfish] Drop the ACCESS_FINE_LOCATION for Restore
Migrate the blkio cgroup controller to the v2 hierarchy
Add display config for sunfish
Removing deprecated Sunfish target
update namespace for generic hal
Migrate I/O scheduler parameters to task_profiles.json
Delete HALs that are already in VINTF fragments (google_battery)
Delete HALs that are already in VINTF fragments (android.hardware.*)
Delete GNSS from main manifest.
Clean up unused face_enroll_introduction_animation
This file doesn't exist
Dumpstate: get fsck log
Disable per-cgroup PSI accounting
AOSP+GMS - Build for aosp_sunfish_gms - set BUILD_BROKEN_VENDOR_PROPERTY_NAMESPACE.
Allow including car boards from outside google_car
Add device-specific support for GoogleBattery AIDL V1
Update sunfish SVN to 45
[LSC] Add LOCAL_LICENSE_KINDS to device/google/sunfish
Notify port status change for moisture detection
Implement callbacks for limitPowerTransfer
Migrate IUsb implementation to AIDL
Disable LE audio related profiles for sunfish
Switch NFC from HIDL to AIDL
Set default the Bluetooth class of device
Revert "Switch NFC from HIDL to AIDL"
Use the ?= operator so BT properties can be overridden
Switch NFC from HIDL to AIDL
Update LE Audio profile properties to match spec and implementation
Update sunfish SVN to 42 Bug: 223313197
Implement callbacks for limitPowerTransfer
Conflicts:
BoardConfig-common.mk
device.mk
Change-Id: I405c33be5711d05a53bf14d784eca2fc2672cea0
Let's remove segment_info which seems not useful.
Bug: 184964835
Signed-off-by: Jaegeuk Kim <jaegeuk@google.com>
Change-Id: Ib9826f536681d9f36f9d55dab3801a05c47f27a4
Bug: 169662280
The timing of dumpstate to enable diag_mdlog is too marginal to
diag_mdlog process exiting. The starting of diag_mdlog would fail if
diag_mdlog process still exists. Change is to leave some time for
diag_mdlog process to exit before it is enabled again by modifying the
system property vendor.sys.modem.diag.mdlog to true.
Change-Id: I825cd77e3f6e8fe6ce395cbe2c21974f1cb29d02
Originally dumpstate copies files by calling /vendor/bin/cp with execvp.
We are seeing some stuck issues while copying files and taring files.
Change is to copy and tar files in place instead of calling system shell.
Bug: 169465773
Change-Id: I9878bde8e540d41c1b498c841079af38f4ec502c
Dump fastrpc dma buffer size so we could understand
the memory usage of fastrpc.
Bug: 168084904
Test: boot
Signed-off-by: Martin Liu <liumartin@google.com>
Change-Id: I3579ccf20b92b25bdcd3f5741efcc287bb3fa40e
The DumpUFS function cannot work with the real sepolicy rules. So
refactor the function to fix the problem.
*** Error dumping /sys/kernel/debug/ufshcd0/stats/err_stats (UFS err_stats): No such file or directory
*** Error dumping /sys/kernel/debug/ufshcd0/stats/io_stats (UFS io_stats): No such file or directory
*** Error dumping /sys/kernel/debug/ufshcd0/stats/req_stats (UFS req_stats): No such file or directory
Bug: 149468879
Bug: 155938509
Test: run bugreport
Change-Id: I9b260d18f4cc768cba98b64d76a149241e17c22b
Signed-off-by: Leo Liou <leoliou@google.com>
Signed-off-by: YH_Lin <yhli@google.com>
File is generated when RIL crash to keep haldebug log.
Bug: 144401289
Test: Bugreport has these files.
Change-Id: I3690845a08fe7fedddc13adced02b9316f54fd39
It might fail to read golden MS rawdata when touch is idle
so I set touch IC as active mode before read rawdata.
Bug: 146467495
Test: trigger bugreport and check the information is correct.
Change-Id: I5b17a1527ef75c1de5904859538c0eae69006d98
Signed-off-by: davidycchen <davidycchen@google.com>
The PROTO mode was added after initial HAL upgrade and is causing VTS
failures due to the way the DumpstateMode param is being validated.
Bug: 150873571
Test: make (no device run VTS, older devices pass with identical change)
Change-Id: I5549eee10e24433030e56353ec828bca6657cc11
(cherry picked from commit 83e8575bb4)
Read from /d/wlan/dpt_stats/dump_set_dpt_logs is
causing a crash in WLAN driver. Hence removing
WLAN DP Trace in bugreport:dumpstate_board.txt file.
Bug: 133593283
Bug: 150067348
Test: Collected bug report and confirmed that dp trace
is not added in dumpstate_board.txt file.
Change-Id: I4b4a41c965072f471dafe23034395a1675099d6c
Signed-off-by: Sunil Ravi <sunilravi@google.com>
Change touch ITO test to the last test item because ITO test will
trigger touch hardware reset which may affect the rawdata value of other
test items.
Test: trigger bugreport and check the touch information is correct in
dumpstate.
Bug: 147336072
Change-Id: Ie9d5c98d6dac3d8dc80ef9a494884eab272f64cc
Signed-off-by: davidycchen <davidycchen@google.com>
Gather Citadel's firmware version, uptime stats, and motherboard type in all
bug reports. None of this can be used to identify a specific phone, so it's
safe to run in production builds.
Previously we were running --id and --selftest. Because these could be used
to indentify a specific Citadel chip, we only gathered it on userdebug and
test builds. We used that to isolate problems with early Citadel samples in
prototype phones, which we've done, fixed, and replaced. We don't need that
info anymore.
Bug: 141235263
Test: manual
Change-Id: I51f6911210af55b323eb4593c8aca07536dab063
Merged-In: I51f6911210af55b323eb4593c8aca07536dab063
Signed-off-by: Bill Richardson <wfrichar@google.com>
(cherry picked from commit a75b7f61df)
Add two items:
Golden raw (Use for checking if any unexpect PI or abnormal golden raw happened)
ITO_HF_Raw (Use for checking touch sensor HW status, ex:open)
Bug: 147336072
Test: trigger bugreport and check these two items is in dumpstate.
Change-Id: I51a6a75a8866c606cb871737f98b15810f37c376
Signed-off-by: davidycchen <davidycchen@google.com>
Gather Citadel's firmware version, uptime stats, and motherboard type in all
bug reports. None of this can be used to identify a specific phone, so it's
safe to run in production builds.
Previously we were running --id and --selftest. Because these could be used
to indentify a specific Citadel chip, we only gathered it on userdebug and
test builds. We used that to isolate problems with early Citadel samples in
prototype phones, which we've done, fixed, and replaced. We don't need that
info anymore.
Bug: 141235263
Test: manual
Change-Id: I51f6911210af55b323eb4593c8aca07536dab063
Signed-off-by: Bill Richardson <wfrichar@google.com>
Vibrator debug data is now being dumped through the HIDL interface.
Bug: 146848183
Test: adb bugreport
Change-Id: Ic9ddfb861fc1c72c158988bc16b8cd030e2745b1
Merged-In: Ie65cc80b9982676572198e0c2536ec7523f5daa6
Signed-off-by: chasewu <chasewu@google.com>
Vibrator debug data is now being dumped through the HIDL interface.
Bug: 146848183
Test: adb bugreport
Change-Id: Ie65cc80b9982676572198e0c2536ec7523f5daa6
Signed-off-by: chasewu <chasewu@google.com>
The /data/vendor/display/mdp_xlog is for mdp driver but not for DRM/KMS.
The bugreport should not need dump it.
Bug: 146848189
Test: There is no failed selinux log of display_vendor_data_file.
Change-Id: I570c1adf38bd20ffb1f178735044be4229d15012
