Status Update
No update yet.
Comments
ja...@gmail.com
Also, we ever checked this with our SoC vendor Qualcomm. Repost their reply as below:
"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."
"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."
ja...@gmail.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.
Description
Android version: 13
VTS tool version: 13_r1
Modules Failing :-
FastbootGetvarUserspaceTest
FastbootVerifyUserspaceTest
Issue description:
My device is Android 13 launch device(with AOSP r24 tag), based on x86_64 architecture. Above mentioned vts modules are failing on my device. My device doesn't have adb over usb support, so i am running vts through adb over ethernet. My device have recovery and fastbootd(fastbootd over tcp) support, so i am running the above mentioned 2 vts fastbootd related modules with adb over ethernet. When i am running these modules, device is entering into fastbootd mode and stuck in it. Modules are failing with Could not find device <IP ADDRESS> in fastbootd error.
Questions i have :-
Experiment i did:- From host machine i ran below commands,
adb connect <IP ADDRESS of device>
adb reboot fastboot [device went to fastbootd mode now]
./fastboot -s tcp:<IP ADDRESS of device> getvar all [got o/p]
With the fastboot executable/tool, i can able to communicate with the device which is in fastbootd mode over tcp, but VTS modules are failing.