Skip to content

Commit

Permalink
Add vendor verbose logging control
Browse files Browse the repository at this point in the history
User build does not have pixel logger. We need to control the logging
via verbose logging control directly. Pixel logger in userdebug could
disable the logging. It should not be overriden by vendor verbose
logging control.

Bug: 150582807
Change-Id: Ic39ec103b5fdb7527cd40107fb5c70aaaa475c90
  • Loading branch information
hungyenweng committed Mar 2, 2020
1 parent cf79722 commit bcddd23
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 5 deletions.
2 changes: 1 addition & 1 deletion init.hardware.diag.rc.user
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ service diag_mdlog_stop /vendor/bin/diag_mdlog -k
disabled
oneshot

on boot && property:persist.vendor.sys.modem.diag.mdlog=*
on property:persist.vendor.sys.modem.diag.mdlog=*
rm /data/vendor/radio/diag_logs/diag_mdlog_pid
setprop vendor.sys.modem.diag.mdlog ${persist.vendor.sys.modem.diag.mdlog}

Expand Down
5 changes: 1 addition & 4 deletions init.hardware.diag.rc.userdebug
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@ on boot && property:persist.vendor.sys.modem.diag.mdlog=*
rm /data/vendor/radio/diag_logs/diag_mdlog_pid
setprop vendor.sys.modem.diag.mdlog ${persist.vendor.sys.modem.diag.mdlog}

on property:vendor.sys.modem.diag.mdlog=true
on property:vendor.sys.modem.diag.mdlog=true && property:persist.vendor.verbose_logging_enabled=true
start diag_mdlog_start

on property:vendor.sys.modem.diag.mdlog=false
Expand Down Expand Up @@ -106,6 +106,3 @@ on property:persist.bluetooth.btsnoopenable=false

on property:vendor.usb.config=*
start usbd

on property:persist.vendor.verbose_logging_enabled=*
setprop persist.vendor.sys.modem.diag.mdlog ${persist.vendor.verbose_logging_enabled}

0 comments on commit bcddd23

Please sign in to comment.