Just noticed this on google "known issues" page:
========================================
Camera, GPS and NFC don't work on Galaxy Nexus.
Symptom: Camera, GPS and NFC don't work on Galaxy Nexus. As an example, the Camera application crashes as soon as it's launched.
Cause: Those hardware peripherals require proprietary libraries that aren't available in the Android Open Source Project.
Fix: None.
========================================
Are the binaries offered on
google driver download page enough to fix this? I didn't see camera or GPS listed there, but NFC is.
EDIT: just found
this blog post with some seemingly good info about camera and GPS. I figured that maybe I could take all the missing files out of an AOKP 4.2 build or a Cyanogenmod 10.1 nightly, since they are both 4.2 based.
My AOSP build had
fRom and
libpn544_fw.so, but was missing
CellBroadcastReceiverVZW.apk,
sirfgps.conf,
ducati-m3.bin, and /
gps.omap4.so. I found them in the AOKP mr1 build-2. I don't know if its kosher to pull the files for my own build and say I did so in this forum, so please correct me if I am breaking any rules.
Also, there were some VZW files in the AOKP rom that were missing from my build:
VerizonSSO.apk,
VZWAPNLib.apk, and
VZWAPNService.apk missing from /system/app/. I'm not sure if those are needed for the phone to function on the Verizon network or not though... Maybe I can just drop all those in the correct locations in my AOSP diy-build otapackage...
EDIT 2: hm... the cyanogenmod nightly doesn't have
VerizonSSO.apk or
CellBroadcastReceiverVZW.apk... maybe unnecessary... but then why are they included elsewhere?
EDIT 3: The
ducati-m3.bin and /
gps.omap4.so files are slightly different between AOKP and Cyanogenmod... the former is a few bytes larger in the AOKP and the latter is 4KB larger in AOKP. kinda weird. The 'last modified' dates on them were exactly 21 hours apart, which is either due to time zone differences... or possibly different builds by the OEM devs? probably none of this really matters, but maybe useful info to have here.
EDIT 4: the ducati-m3.bin file is in my aosp source tree; sirfgps.conf and gps.omap4.sa are not. WHen I tried edited android.mk and device-partial.mk as described
here by Anders, I got an error: "no rule to make target /vender/samsung/toro/proprietary/ducati-m3.bin". And the build stopped. I also tried changing LOCAL_MODULE_OWNER names from samsung to "ti" and "csr" as I saw that on another webpage. No luck, build still stopped.
So I undid the .mk file changes, but left sirfgps.conf in the /vendor/samsung/toro/proprietary folder of WORKING_DIRECTORY. However, I think it probably won't be incorporated into the build. I guess adding them in the end manually is the only way to go?
Is there anyone who knows how to build AOSP 4.2 for toro (without having to manually add anything to the output build) and have it all working, camera, gps, and all?