Originally Posted by djuniah
Just opened my atrix lapdock for the first time in a while to try it out and had a bunch of weird things happen that i havent seen listed eleswhere. Just wanted to know if anyone else seen something like this.
First, i'm running the latest Carbon nightly on my Razr HD.
Things that happened:
1) I plugged in the HDMI/USB and the phone mirrored onto the screen, however the mouse/keyboard didn't work and it wasn't charging the phone.
2) I removed the phone, checked the jacks and plugged it back in again. This time, the lapdock's backlight turned on, but nothing showed up on the screen. I ran an lsusb and it does show a device there (when i remove the usb it doesn't list anything).
I can't seem to get the phone to mirror again though. I've since rebooted the phone and tried a few other things, but i can't seem to replicate #1.
Anyone have a similar experience?
That's pretty much normal on custom JB roms. You can get the phone to output to the Lapdock in a bastardized 1080p if you go to dev settings and disable hdcp -- there's a bug in the custom kernel regarding both obtaining the lapdock's EDID as well as the phone always trying to initiate the hdcp handshake even though it's really a dvi monitor with an hdmi>dvi adapter. With HDCP disabled, the phone will force output to 1080p, only the monitor is 1366x768, and due to the buggy EDID, none of FB1's (framebuffer 1...hdmi output) settings are tweakable...mainly the resolution setting like we have to use in Stock Moto JB. Sucks knowing the bug and not knowing how to fix it.
Good news is the Lapdock is reported to work just fine with Stock KitKat. Once the dev team is ready and start releasing CM11 with the 3.4 kernel, we'll finally be able to use the Lapdock with custom KK roms like we did with stock ICS.