CURRENT DROID 3 DEVELOPMENT:
** I would never expect the camera to be fully functioning. I am working several avenues to get a functional camera on the Droid 3, but they're all sketchy at best. Just know that if you choose to flash custom ROMs w/ newer OS versions: You won't have a camera.
** Did I say don't expect the camera to be fixed? If it was to be fixed, trust me, you'll see me all over the boards, twitter and the social universe telling people about it.
** There are other devs now working on the kexec kernel and it's possible that they can get some basic camera functionality through kernel drivers. It's quite complicated and there are no public data sheets which describe the sensor functions in great detail for our devices.
** Don't expect the camera to be fixed.
CHANGES OVER THE LAST MONTH:
BATTERY LIFE / KERNEL BUGFIXES:
- Several internal clocks which were left active are now turned off as they should be. (since they're un-used)
- IPI/LOCAL timers were re-enabled in the kernel. These are interrupt driven timers which help trigger various drivers for updates.
- Bugfixes to allow other lower level functions to run in the kernel as well like gpmc
- I've fixed the kernel bootlog recovery driver (/proc/last_kmsg) so that this now works in our kexec kernel. This is a copy of the last kernel bootlog from a prior boot. So if you crash, please reboot and pull /proc/last_kmsg with adb and send me a log via email: hashcode0f at gmail.com
- Removed a hack to initiate the sound driver, causing it to stay active all of the time in the background. It now starts normally and suspends normally. (Thanks to kfazz for the fix).
JB-MR1 DEVICE UPDATES WITH OMAPZOOM:
- hwcomposer now updated to API1.0
- domx (HD codec) code updated to the latest sources
CHANGES OVER THE NEXT MONTH:
- I'm taking the kexec kernel back to the beginning and re-merging Motorola's changes with the Texas Instrument changes that are needed to run the kernel on the Droid 3: memory allocations, HD codec binary changes, etc.
- This process is already 3-4 weeks in the running, and will be another 2-3 weeks before it's done.
- Once that kernel source is ready for prime-time, I'm going to swap the Droid 3 over to the new kernel source.
WHY DO THIS?
- By taking the time to create a full kernel history (from omapzoom) and integrate the Motorola changes into it, I can then migrate the kernel sources forward in a nice orderly manner cherry-picking new kernel commits directly from Omapzoom.
- This should make for a much cleaner / more stable kexec kernel in the future. And allows other devs to see where I'm going w/ kernel development so that they can add to it. Each file shows how it was edited and by who so it's more transparent where Motorola made their changes to the original TI kernel.
BATTERY DRAIN AND WHEN WILL IT BE "FIXED":
- The current kernel cannot put the UART ports to sleep like a normally booted kernel can. There is an issue that happens during kexec where the clocks associated w/ the UART ports become stuck in a full enabled mode. Any attempts to place them in suspend or disable hangs the kernel. It's being looked at. Right now the device never really 100% suspends. Hence higher than normal battery usage.
"OFFICIAL" ____ (AOKP/CM) MEANS WORKING CAMERA/BLUETOOTH AUDIO RIGHT?
- No. Actually "official" just means you can repo init the source straight from either AOKP/CM and build the device w/o worrying too much about extra sources or patches, etc.
- "Official" also means automated builds for the device (in some fashion). Currently for AOKP it's every 2-3 weeks and for CM it's nightly. These have the benefit of including any changes to the ROM automatically.
- The device doesn't get any more devs
- The device isn't magically fixed or more stable
Just thought I'd toss that in