Status Update
No update yet.
Comments
du...@quantatw.com
"Dear Customer,
With respect to linker issue and this could be issue with google as the keystore bin is maintained by google,, qcom don't own this.. Please check with google..
Basically what i understand from error, it indicate that the linker is unable to create the executable keystore it can not find a specific symbol (_ZTSN6icu_7024DateTimePatternGeneratorE). This symbol is referenced by the library libicui18n.so."
ty...@google.com
The related log is:
01-04 13:17:32.786 501 501 F linker : CANNOT LINK EXECUTABLE "/system/bin/keystore2": cannot locate symbol "_ZTIN6icu_7024DateTimePatternGeneratorE" referenced by "/apex/com.android.i18n/lib64/libicui18n.so"...
Where do you get /apex/com.android.i18n? The symbol should be defined in libicui18n.so itself.
du...@quantatw.com
It should be built from the GSI source code of AOSP. And the last git log of /system/apex is:
commit a6c05564be6ac04bc1be117f86564552cc200952 (HEAD, origin/android13_ext, m/android13_ext, android13_ext)
Merge: 8eab4a2e d2c816eb
Author: Android Build Coastguard Worker <android-build-coastguard-worker@google.com>
Date: Thu Nov 10 00:29:51 2022 +0000
Snap for 9274385 from d2c816eb179071a39247c6fdcf3e4de278f9231b to tm-qpr2-release
Change-Id: I3cfc162bd4a8897cffc75417702a58de4f142967
commit d2c816eb179071a39247c6fdcf3e4de278f9231b
Author: Jooyung Han <jooyung@google.com>
Date: Tue Nov 8 16:30:02 2022 +0900
Use block apex path as key for rootdigest overrides
When scanning block apexes in VM mode, apexd keeps rootdigest overrides
in a map for later verification. But using apex name as a key doesn't
work for "sharelibs" apexes because there might be two apexes for a
single sharelib apex name.
Instead, we can use block apex path as a key to a map.
Bug: 257377686
Test: ApexTestCases
Merged-In: Idd4e90f52e56b47d046c4eda88f34bf7b7aee4d5
Change-Id: Idd4e90f52e56b47d046c4eda88f34bf7b7aee4d5
(cherry picked from commit f571befaba0b3609d9574a2b31006e0c871c5fe8)
ty...@google.com
Please check the symbol in your object file /apex/com.android.i18n/lib64/libicui18n.so. The symbol should be defined in the library. I suspect that the file is corrupted.
You may also download the Android13 GSI image for comparison.
du...@quantatw.com
That device can boot into android normally if we forced to restart it. Do you still think that file is corrupt in this case?
ty...@google.com
By "device can boot into android normally", you mean keystore2 can be executed without that linker error?
du...@gmail.com
Yeah, we didn't see the same error by doing so.
ty...@google.com
If it's not always reproducible, then I suspect it's a device issue. Let me close the issue as not reproducible. Feel free to reopen it if you find a reliable way to reproduce the problem.
du...@quantatw.com
du...@quantatw.com
No, we may see different symbol of other library as below. I also attached the full log.
01-04 18:03:37.655 499 499 F linker : CANNOT LINK EXECUTABLE "/system/bin/keystore2": cannot locate symbol "_ZN9keymaster23BlockCipherEvpOperation6FinishERKNS_16AuthorizationSetERKNS_6BufferES6_PS1_PS4_" referenced by "/system/lib64/libkeymaster_portable.so"...
ty...@google.com
No, we may see different symbol of other library
Then it's definitely a device problem. Maybe checking the health of ROM and RAM if it happens on the same 5 devices?
du...@quantatw.com
Hmm, these devices could pass the eMMC and memory test utilities provided by vendor. So, we are not so sure it's the reason of this issue. Do you any idea how to dig more about the linker error?
Description
Description has been deleted.