Failed to get bluetooth and camera working after flashing Nexus 7 using AOSP build
I am in the process of creating custom images for a Nexus 7 tablet. I followed the official android documentation for creating devices and also with the vendor's built-in binaries.
Everything works well except for Bluetooth and the camera. Reading the source code, I understand that it /etc/init.flo.bt.sh
is failing when I try to call the binary /system/bin/hci_qcomm_init
. In manual mode hci_qcomm_init
, the following error appears:
shell@flo:/ # hci_qcomm_init
CANNOT LINK EXECUTABLE: empty/missing DT_HASH in "hci_qcomm_init" (built with --hash-style=gnu?)
Likewise, for the camera, my understanding is mm-qcamera-daemon
not working on the phone (mostly not starting during the initialization process). If I try to start it manually:
shell@flo:/ # mm-qcamera-daemon
CANNOT LINK EXECUTABLE: empty/missing DT_HASH in "mm-qcamera-daemon" (built with --hash-style=gnu?)
I'm not looking for a definitive answer, but can anyone point out what exactly is wrong with these binaries on the phone?
source to share
According to this post fooobar.com/questions/1575929 / ... binaries may use different compiler options for hash than your system libraries. You can try to change the gcc compiler options in the android build to match the ones used for the binaries.
I don't remember where these compiler flags are defined in AOSP, though ...
source to share