diff options
| author | 2021-09-01 16:09:08 -0700 | |
|---|---|---|
| committer | 2021-09-01 16:40:06 -0700 | |
| commit | 9ee3eebb99a67200979ca073dbbac8adba0a100d (patch) | |
| tree | 1daf1e71a87663f669da5de6080ae481763f9eda /libs/androidfw/StringPool.cpp | |
| parent | 07678d1f45c7d1e3b15bcb66185d50d42234e776 (diff) | |
[SettingsProvider] additional logging for debug telephony bug
For the past few months we have been seening a telephony bug that
happens occasionally without a reliable way to reproduce it. The bug is
that for some reason, all of a sudden, the telephony thinks that the
device is unprovisioned, even though the device is provisioned. Based on
initial inspection, the inconsistency is from Settings Provider.
However, the dumpsys shows that the DEVICE_PROVISIONED value is 1, and
no other clients have reported this issue. The inconsistency could be
from memory corruption, though that would probably have been reported by
other clients as well.
To further assist debugging, I am adding additional logging just for the
query on DEVICE_PROVISIONED. This will at least show what exactly is
the value returned to telephony, when the bug occurs again. I will
remove the additional logging as soon as we have some clue.
BUG: 197879371
Test: builds
Change-Id: I1321168081fa808dca4503b84d58983df145e790
Diffstat (limited to 'libs/androidfw/StringPool.cpp')
0 files changed, 0 insertions, 0 deletions