[Motorola Photon Q 4G LTE] ACiD GRiM:
So I got around to dumping dmesg from stock, here's the relevant part. This when connected to the lapdock, which does work in stock.

Due to character limit, please see attachment

In contrast to the CM10.2 EDID error, I see this

<6>[ 160.007050,0] hdmi_msm hdmi_msm.1: EDID (V=1.3, #CEABlocks=1[V3], ID=MOT, IEEE=0c03, EDID-Ext=0x02)

Just for the heck of I also dumped the contents of /sys/devices/virtual/graphics/fb1

Here's what it looks like when connecting the lapdock:

/sys/devices/virtual/graphics/fb1/uevent:MAJOR=29
/sys/devices/virtual/graphics/fb1/uevent:MINOR=1
/sys/devices/virtual/graphics/fb1/uevent:DEVNAME=fb1
/sys/devices/virtual/graphics/fb1/dev:29:1
/sys/devices/virtual/graphics/fb1/power/runtime_status:active
/sys/devices/virtual/graphics/fb1/power/control:auto
/sys/devices/virtual/graphics/fb1/power/runtime_suspended_time:0
/sys/devices/virtual/graphics/fb1/power/runtime_active_time:971160
/sys/devices/virtual/graphics/fb1/bits_per_pixel:16
/sys/devices/virtual/graphics/fb1/modes:U:1280x720p-0
/sys/devices/virtual/graphics/fb1/modes:U:720x480p-0
/sys/devices/virtual/graphics/fb1/modes:U:1920x1080p-0
/sys/devices/virtual/graphics/fb1/pan:0,0
/sys/devices/virtual/graphics/fb1/virtual_size:1920,1080
/sys/devices/virtual/graphics/fb1/name:msmfb40_70001
/sys/devices/virtual/graphics/fb1/stride:1440
/sys/devices/virtual/graphics/fb1/rotate:0
/sys/devices/virtual/graphics/fb1/state:0
/sys/devices/virtual/graphics/fb1/msm_fb_type:dtv panel
/sys/devices/virtual/graphics/fb1/video_mode:3
/sys/devices/virtual/graphics/fb1/video_mode_str: 720x 480 p60 16/9
/sys/devices/virtual/graphics/fb1/connected:1
/sys/devices/virtual/graphics/fb1/hdmi_mode:1
/sys/devices/virtual/graphics/fb1/edid_data:00ffffffffffff0035f4c53d010000002315010380160d78ea0dc9a05747982712484c00000001010101010101010101010101010101201c56c2500026303b275900df7d0000001e771d56c2500026303b275900df7d00000018000000ff004c443253303030303030303031000000fc004d6f746f4c4432532020202020014a020314704102230902018301000065030c001000201c56c2500026303b275900df7d0000001e7e1d56c2500026303b275900df7d0000001e201c56c2500026303b275900df7d0000001e201c56c2500026303b275900df7d0000001e201c56c2500026303b275900df7d0000001e0000000000000000000000000000000000b300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
/sys/devices/virtual/graphics/fb1/edid_modes:2
/sys/devices/virtual/graphics/fb1/hdcp:1
/sys/devices/virtual/graphics/fb1/hpd:1
/sys/devices/virtual/graphics/fb1/3d_present:0
/sys/devices/virtual/graphics/fb1/hdcp_present:1
/sys/devices/virtual/graphics/fb1/hdcp_en:1
/sys/devices/virtual/graphics/fb1/format_3d:0
/sys/devices/virtual/graphics/fb1/hdmi_primary:0

And per another forum, sending echo 4 > /sys/devices/virtual/graphics/fb1/video_mode gives me full screen 1280x720@60Hz

/sys/devices/virtual/graphics/fb1/uevent:MAJOR=29
/sys/devices/virtual/graphics/fb1/uevent:MINOR=1
/sys/devices/virtual/graphics/fb1/uevent:DEVNAME=fb1
/sys/devices/virtual/graphics/fb1/dev:29:1
/sys/devices/virtual/graphics/fb1/power/runtime_status:active
/sys/devices/virtual/graphics/fb1/power/control:auto
/sys/devices/virtual/graphics/fb1/power/runtime_suspended_time:0
/sys/devices/virtual/graphics/fb1/power/runtime_active_time:918770
/sys/devices/virtual/graphics/fb1/bits_per_pixel:16
/sys/devices/virtual/graphics/fb1/modes:U:1280x720p-0
/sys/devices/virtual/graphics/fb1/modes:U:720x480p-0
/sys/devices/virtual/graphics/fb1/modes:U:1920x1080p-0
/sys/devices/virtual/graphics/fb1/pan:0,0
/sys/devices/virtual/graphics/fb1/virtual_size:1920,1080
/sys/devices/virtual/graphics/fb1/name:msmfb40_70001
/sys/devices/virtual/graphics/fb1/stride:2560
/sys/devices/virtual/graphics/fb1/rotate:0
/sys/devices/virtual/graphics/fb1/state:0
/sys/devices/virtual/graphics/fb1/msm_fb_type:dtv panel
/sys/devices/virtual/graphics/fb1/video_mode:4
/sys/devices/virtual/graphics/fb1/video_mode_str:1280x 720 p60 16/9
/sys/devices/virtual/graphics/fb1/connected:1
/sys/devices/virtual/graphics/fb1/hdmi_mode:1
/sys/devices/virtual/graphics/fb1/edid_data:00ffffffffffff0035f4c53d010000002315010380160d78ea0dc9a05747982712484c00000001010101010101010101010101010101201c56c2500026303b275900df7d0000001e771d56c2500026303b275900df7d00000018000000ff004c443253303030303030303031000000fc004d6f746f4c4432532020202020014a020314704102230902018301000065030c001000201c56c2500026303b275900df7d0000001e7e1d56c2500026303b275900df7d0000001e201c56c2500026303b275900df7d0000001e201c56c2500026303b275900df7d0000001e201c56c2500026303b275900df7d0000001e0000000000000000000000000000000000b300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
/sys/devices/virtual/graphics/fb1/edid_modes:4
/sys/devices/virtual/graphics/fb1/hdcp:1
/sys/devices/virtual/graphics/fb1/hpd:1
/sys/devices/virtual/graphics/fb1/3d_present:0
/sys/devices/virtual/graphics/fb1/hdcp_present:1
/sys/devices/virtual/graphics/fb1/hdcp_en:1
/sys/devices/virtual/graphics/fb1/format_3d:0
/sys/devices/virtual/graphics/fb1/hdmi_primary:0

So the lapdock does support 720x480, which means the limiting factor is something else. However /sys/devices/virtual/graphics/fb1/modes lists 1280x720 in stock, where CM10.2 does not.

Would this suggest that the support needed might be stripped from the kernel source like the FIPS features might be?

I'm going to start trying to see if I can get a newer linux kernel tree merged with the stock kernel source at sourceforge and compile/package initrd as an update.zip. Something I've never even come close to trying before, but that hasn't stopped me.

I'm still digging with the tools I have.

I did a diff of the HDMI and FB sources between the Tree that arrrrgh's kernel is based off and the source forge and they're appearing to be identical. So it doesn't appear to be a kernel issue from my untrained eye.

Edit:

Some related reading

http://giuliofidente.com/2012/10/13...ck-heres-how-to-write-your-xorg-modeline.html

https://community.freescale.com/thread/306901

Interisting https://community.freescale.com/message/342940#342940

So it appears that since the kernel drivers are identical there's either another kernel element that handles resolution changes that was modified for function with cyanogenmod, or there's a daemon in stock that handles that that is missing in CM.

It could be that video format 131071 is 1366x768, which is what I beleve the native resolution of the lapdock is, and stock works because there's a mechanism that allows it to gracefully fall back to 720x480 (or assumes that to begin with). 768p isn't a valid EDID value as in the upper link, because it's not an HDMI standard resolution. The above post at freescale.com indicates its possible to add 1366x768 as a supported EDID value, however 720p support would be the next best thing since it works in stock

I do believe something is broken because even with the lapdock disconnected, /sys/devices/virtual/graphics/fb1/video_mode is always 131071 and I can't write to it like I can in stock.