Motorola Altrix Lapdock loses HDMI video after closing Lapdo

[heatfanjohn]

I have a Motorola Altrix Lapdock connected to my Raspberry Pi using the instructions provided on various web sites including http://rpidock.blogspot.com/.

The HDMI output initially displays on the Lapdock, but if I close the Lapdock and reopen it the video will not display. I find that sometimes rebooting the Pi or completely disconnecting the Lapdock (both USB and HDMI connections) will cause the display to work again.

I've even tried setting "hdmi_safe=1" to get the display to consistently work after closing and reopening the Lapdock or rebooting the Pi.

Could I just have a flaky Lapdock?

Can anyone with a working Lapdock perform the "tvservice -d edit.out" command parsing the output using "edidparser edid.out" posting your results here for comparison?

Using the "tvservice -d edid.out" command I was able to dump the EDID information from my Lapdoc, here is what that was returned:

[email protected]:~$ edidparser edid.out
Enabling fuzzy format match...
Parsing d.out...
HDMI:EDID version 1.3, 1 extensions, screen size 26x14 cm
HDMI:EDID features - videodef 0x80 !standby !suspend !active off; colour encoding:RGB444|YCbCr422; sRGB is not default colourspace; preferred format is native; does not support GTF
HDMI:EDID found monitor S/N descriptor tag 0xff
HDMI:EDID found monitor range descriptor tag 0xfd
HDMI:EDID monitor range offsets: V min=0, V max=0, H min=0, H max=0
HDMI:EDID monitor range: vertical is 50-75 Hz, horizontal is 30-85 kHz, max pixel clock is 150 MHz
HDMI:EDID monitor range does not support GTF
HDMI:EDID found monitor name descriptor tag 0xfc
HDMI:EDID monitor name is MotoAttach
HDMI:EDID found preferred DMT detail timing format: 1366x768p @ 60 Hz (86)
HDMI:EDID established timing I/II bytes are 00 00 00
HDMI:EDID standard timings block x 8: 0x0101 0101 0101 0101 0101 0101 0101 0101
HDMI:EDID parsing v3 CEA extension 0
HDMI:EDID monitor support - underscan IT formats:no, basic audio:yes, yuv444:yes, yuv422:yes, #native DTD:1
HDMI:EDID found DMT detail timing format: 1366x768p @ 60 Hz (86)
HDMI:EDID failed to find a matching detail format for 0x720p hfp:110 hs:40 hbp:-134 vfp:5 vs:5 vbp:20 pixel clock:0 MHz
HDMI:EDID calculated refresh rate is 0 Hz
HDMI:EDID guessing the format to be 0x720p @24 Hz
HDMI:EDID found unknown detail timing format: 0x720p hfp:110 hs:40 hbp:-134 vfp:5 vs:5 vbp:20 pixel clock:0 MHz
HDMI:EDID failed to find a matching detail format for 0x1080i hfp:88 hs:44 hbp:-116 vfp:2 vs:5 vbp:16 pixel clock:0 MHz
HDMI:EDID calculated refresh rate is 0 Hz
HDMI:EDID guessing the format to be 0x1080i @24 Hz
HDMI:EDID found unknown detail timing format: 0x1080i hfp:88 hs:44 hbp:-116 vfp:2 vs:5 vbp:16 pixel clock:0 MHz
HDMI:EDID found CEA format: code 1, 640x480p @ 60Hz
HDMI:EDID found CEA format: code 3, 720x480p @ 60Hz
HDMI:EDID found CEA format: code 18, 720x576p @ 50Hz
HDMI:EDID found audio format 2 channels PCM, sample rate: 32|44|48|96|192 kHz, sample size: 16|20|24 bits
HDMI:EDID found HDMI VSDB length 5
HDMI:EDID HDMI VSDB has physical address 1.0.0.0
HDMI:EDID HDMI VSDB has no extension fields
HDMI:EDID adding mandatory support for DMT (4) 640x480p @ 60Hz
HDMI:EDID adding mandatory support for CEA (2) 720x480p @ 60Hz
HDMI:EDID adding mandatory support for CEA (17) 720x576p @ 50Hz
HDMI:EDID filtering formats with pixel clock > 162 MHz or h. blanking > 1023
HDMI:EDID best score mode initialised to DMT (4) 640x480p @ 60 Hz with pixel clock 25 MHz (score 0)
HDMI:EDID best score mode is now CEA (1) 640x480p @ 60 Hz with pixel clock 25 MHz (score 43432)
HDMI:EDID best score mode is now CEA (2) 720x480p @ 60 Hz with pixel clock 27 MHz (score 45736)
HDMI:EDID CEA mode (3) 720x480p @ 60 Hz with pixel clock 27 MHz has a score of 45736
HDMI:EDID DMT mode (4) 640x480p @ 60 Hz with pixel clock 25 MHz has a score of 36864
HDMI:EDID CEA mode (17) 720x576p @ 50 Hz with pixel clock 27 MHz has a score of 45736
HDMI:EDID CEA mode (18) 720x576p @ 50 Hz with pixel clock 27 MHz has a score of 45736
HDMI:EDID best score mode is now DMT (86) 1366x768p @ 60 Hz with pixel clock 72 MHz (score 5188835)
HDMI:EDID preferred mode remained as DMT (86) 1366x768p @ 60 Hz with pixel clock 72 MHz
HDMI:EDID has HDMI support and audio support
edid_parser exited with code 0

[cyberjunkie1970]

I have an Atrix Lapdock that works fine, so here's my EDID info:

[email protected] ~ $ edidparser edid.out
Enabling fuzzy format match...
Parsing edid.out...
HDMI:EDID version 1.3, 1 extensions, screen size 26x14 cm
HDMI:EDID features - videodef 0x80 !standby !suspend !active off; colour encoding:RGB444|YCbCr422; sRGB is not default colourspace; preferred format is native; does not support GTF
HDMI:EDID found monitor S/N descriptor tag 0xff
HDMI:EDID found monitor range descriptor tag 0xfd
HDMI:EDID monitor range offsets: V min=0, V max=0, H min=0, H max=0
HDMI:EDID monitor range: vertical is 50-75 Hz, horizontal is 30-85 kHz, max pixel clock is 150 MHz
HDMI:EDID monitor range does not support GTF
HDMI:EDID found monitor name descriptor tag 0xfc
HDMI:EDID monitor name is MotoAttach
HDMI:EDID found preferred DMT detail timing format: 1366x768p @ 60 Hz (86)
HDMI:EDID established timing I/II bytes are 00 00 00
HDMI:EDID standard timings block x 8: 0x0101 0101 0101 0101 0101 0101 0101 0101
HDMI:EDID parsing v3 CEA extension 0
HDMI:EDID monitor support - underscan IT formats:no, basic audio:yes, yuv444:yes, yuv422:yes, #native DTD:1
HDMI:EDID found DMT detail timing format: 1366x768p @ 60 Hz (86)
HDMI:EDID failed to find a matching detail format for 0x720p hfp:110 hs:40 hbp:-134 vfp:5 vs:5 vbp:20 pixel clock:0 MHz
HDMI:EDID calculated refresh rate is 0 Hz
HDMI:EDID guessing the format to be 0x720p @24 Hz
HDMI:EDID found unknown detail timing format: 0x720p hfp:110 hs:40 hbp:-134 vfp:5 vs:5 vbp:20 pixel clock:0 MHz
HDMI:EDID failed to find a matching detail format for 0x1080i hfp:88 hs:44 hbp:-116 vfp:2 vs:5 vbp:16 pixel clock:0 MHz
HDMI:EDID calculated refresh rate is 0 Hz
HDMI:EDID guessing the format to be 0x1080i @24 Hz
HDMI:EDID found unknown detail timing format: 0x1080i hfp:88 hs:44 hbp:-116 vfp:2 vs:5 vbp:16 pixel clock:0 MHz
HDMI:EDID found CEA format: code 1, 640x480p @ 60Hz
HDMI:EDID found CEA format: code 3, 720x480p @ 60Hz
HDMI:EDID found CEA format: code 18, 720x576p @ 50Hz
HDMI:EDID found audio format 2 channels PCM, sample rate: 32|44|48|96|192 kHz, sample size: 16|20|24 bits
HDMI:EDID found HDMI VSDB length 5
HDMI:EDID HDMI VSDB has physical address 1.0.0.0
HDMI:EDID HDMI VSDB has no extension fields
HDMI:EDID adding mandatory support for DMT (4) 640x480p @ 60Hz
HDMI:EDID adding mandatory support for CEA (2) 720x480p @ 60Hz
HDMI:EDID adding mandatory support for CEA (17) 720x576p @ 50Hz
HDMI:EDID filtering formats with pixel clock > 162 MHz or h. blanking > 1023
HDMI:EDID best score mode initialised to DMT (4) 640x480p @ 60 Hz with pixel clock 25 MHz (score 0)
HDMI:EDID best score mode is now CEA (1) 640x480p @ 60 Hz with pixel clock 25 MHz (score 43432)
HDMI:EDID best score mode is now CEA (2) 720x480p @ 60 Hz with pixel clock 27 MHz (score 45736)
HDMI:EDID CEA mode (3) 720x480p @ 60 Hz with pixel clock 27 MHz has a score of 45736
HDMI:EDID DMT mode (4) 640x480p @ 60 Hz with pixel clock 25 MHz has a score of 36864
HDMI:EDID CEA mode (17) 720x576p @ 50 Hz with pixel clock 27 MHz has a score of 45736
HDMI:EDID CEA mode (18) 720x576p @ 50 Hz with pixel clock 27 MHz has a score of 45736
HDMI:EDID best score mode is now DMT (86) 1366x768p @ 60 Hz with pixel clock 72 MHz (score 5188835)
HDMI:EDID preferred mode remained as DMT (86) 1366x768p @ 60 Hz with pixel clock 72 MHz
HDMI:EDID has HDMI support and audio support
edid_parser exited with code 0

It sounds to me like you may have a faulty lapdock. On mine after I shut down the Raspberry Pi I can close the lid and open it right back up and the video works fine. If you aren't able to get the problem worked out yourself, do you know if it's still covered under warranty?

[heatfanjohn]

Thank you for posting your EDID information cyberjunkie1970!

Our EDID information appears to be identical. One last question, would you mind posting your /boot/config.txt file or at least the video related settings.

I have tried almost every possible combination, but have yet to achieve consistent predictable behavior.

Also, what do the following three commands output for you:

tvservice -m DHT
tvservice -m CEA
tvservice -s

Thank you!

[cyberjunkie1970]

Here's my config.txt:

[email protected] ~ $ cat /boot/config.txt
# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=40
#overscan_right=40
#overscan_top=22
#overscan_bottom=22

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
arm_freq=900

# for more options see http://elinux.org/RPi_config.txt
core_freq=250
sdram_freq=450
over_voltage=2

# to enable optional hardware codecs
decode_MPG2=0xf66e3882
decode_WVC1=0x57ed3926

gpu_mem=128


And here's the output from the tvservice commands:

[email protected] ~ $ tvservice -m DHT
[E] Invalid group 'DHT'
[email protected] ~ $ tvservice -m CEA
Group CEA has 5 modes:
mode 1: 640x480 @ 60Hz 4:3, clock:25MHz progressive
mode 2: 720x480 @ 60Hz 4:3, clock:27MHz progressive
mode 3: 720x480 @ 60Hz 16:9, clock:27MHz progressive
mode 17: 720x576 @ 50Hz 4:3, clock:27MHz progressive
mode 18: 720x576 @ 50Hz 16:9, clock:27MHz progressive
[email protected] ~ $ tvservice -s
state 0x12001a [HDMI DMT (86) RGB full 16:9], 1366x768 @ 60Hz, progressive


I think the DHT in the first command was maybe supposed to be DMT, so here's the output of tvservice -m DMT:

[email protected] ~ $ tvservice -m DMT
Group DMT has 2 modes:
mode 4: 640x480 @ 60Hz 4:3, clock:25MHz progressive
(prefer) mode 86: 1366x768 @ 60Hz 16:9, clock:72MHz progressive


I hope this helps.

[heatfanjohn]

Yes, you are correct about DMT versus DHT ... my bad on that ...

I need to check my Pi later tonight.

Thanks again!

[heatfanjohn]

Partial success! I am able to get the display to work consistently if I execute the following commands:


tvservice -e "DMT 4"

That commands sets the following profile:

tvservice -s
state 0x12001a [HDMI DMT (4) RGB full 4:3], 640x480 @ 60Hz, progressive

Then to get the display to appear I need to execute the following frame buffer command:

fbset 640x480-60

fbset --show

mode "640x480-60"
# D: 25.175 MHz, H: 31.469 kHz, V: 59.940 Hz
geometry 640 480 640 480 8
timings 39722 48 16 33 10 96 2
accel true
rgba 8/0,8/0,8/0,0/0
endmode


I am unable to get the display to work consistently at its native resolution of 1366x768. My /etc/fb.modes file does not contain any entry for 1366x768.

[cyberjunkie1970]

I have an idea. What if you try putting the following lines in your /boot/config.txt file:

framebuffer_width=1280
framebuffer_height=720

If it works out and the lapdock behaves itself, I think you'll have as close to the native resolution as you can get. I just tried it on my lapdock (actually have it operating at 1280x720 right now) and it seems fine. You might be able to try setting it for width 1366 and height 768, but I suspect that will give you the same original problem again. Might be worth a try, though, just to see what happens.

[heatfanjohn]

Thanks @cyberjunkie1970, I will give that a try!

What does "fbset --show" display for your lapdock?

Thanks again,
John

[cyberjunkie1970]

Hi John,

When I'm running in 1366x768 it says this:
mode "1366x768"
geometry 1366 768 1366 768 16
timings 0 0 0 0 0 0 0
rgba 5/11,6/5,5/0,0/16
endmode

And when I'm running in 1280x720 it says this:
mode "1280x720"
geometry 1280 720 1280 720 16
timings 0 0 0 0 0 0 0
rgba 5/11,6/5,5/0,0/16
endmode

Gary

[cyberjunkie1970]

John,

One other thing I just remembered I wanted to say. My /etc/fb.modes also doesn't contain any entry for 1366x768. I also wanted to ask, what operating system are you using? Is it the latest version of Raspbian? That's what I'm using and I was just curious if it could be an issue tied to the operating system.

Gary

[heatfanjohn]

I'm using Raspbian and did an rpi-update recently. My uname -a displays:

Linux raspberrypi 3.6.11+ #496 PREEMPT Thu Jul 11 00:09:56 BST 2013 armv6l GNU/Linux

[cyberjunkie1970]

My uname -a showed the same thing as yours did, but then I decided to see if there might be another update out there. Now my uname -a shows this:

Linux raspberrypi 3.6.11+ #512 PREEMPT Sat Jul 27 19:08:54 BST 2013 armv6l GNU/Linux

It's hard to know either way if another rpi-update will help your situation or not since we were using the exact same thing already, but I thought I'd let you know there's another update out there.

[heatfanjohn]

Thanks for all your help.

Your suggestion to try 1280x720 worked. That is DMT mode 85.

I beginning to suspect that my HDMI cable and required adapter may not be able to handle the slightly additional bandwidth required for 1366x768.

All in all, the 1280x720 doesn't look too bad. Text is slightly fuzzy. I'm sure that's because the display isn't running at its native resolution. XBMC runs well, although I'm not getting any sound out of the lapdock's speakers. I am running HDMI so it should work.

Maybe this is also due to my cable. Just curious, what cable and adapter are you using?

I will also perform another rpi-update later tonight. I have experienced a couple of Kernel panics in drivers/usb/host/dwc_otg/dwc_otg_hcd.c

Thanks again,
John

[cyberjunkie1970]

Hi John.

The cable and adapter I'm using both came from Ebay. The adapter, which is most likely the same thing you have, is micro HDMI female on one end and regular HDMI male on the other. The seller I bought it from is just_for_survive and it came from China. The cable I'm using is a standard HDMI extension cable that's 1.5 ft. long. Just standard HDMI female on one end and standard HDMI male on the other. The seller I bought that from is cmple-select and that seller is located in New York.

The first cable I had didn't work well when I got it. First I got red lines flickering all over the screen and soon thereafter it stopped working altogether. That one was micro HDMI on both ends, male on one end and female on the other. If that's what you have it wouldn't surprise me that you'd have trouble with it.

Also, about your problem with the audio not coming through the lapdock speakers. Do you have hdmi_drive=2 in your config.txt? If not you may need it.

Gary

[heatfanjohn]

Thanks Gary.

I am using the same adapter that you use, however I was using a micro female to micro male HDMI cable that was the source of my problem. The lapdock works perfectly if I attach my Pi directly to my lapdock directly only using the adapter. I have a full size HDMI extension cable on order that will allow me to locate my Pi away from the lapdock putting it back into the clear case I use with it.

I also performed an rpi-update, so I'm on version: #518 PREEMPT Fri Aug 2 11:39:53 BST 2013 armv6l GNU/Linux

Thank you for all your assistance.
John

[Niall101]

Hi all (first post on the Forum - be gentle with me!!)

I have the same Lapdock, and I always felt that the action of opening/closing the Lapdock lid served to energise/de-energise the power on the Micro-USB output plug. I have never 'proved' this, but I have seen similar behaviour to what the OP posted.

Could this be the cause?

Cheers,
Niall

[heatfanjohn]

I can confirm that closing and the reopening the lapdock does cause the USB to lose power momentarily.

I have a dedicated power supply for my Pi that is connected to the Pi's USB power input. However, if I remove that power connection and then close and reopen my Pi, my Pi will momentarily turn off.

[itimpi]

I treat that as a 'feature'. It means I can force the equivalent of a power on/off without needing a switch on the power supply.

However I guess it would nice if there was a way of making it optional without the need to do hardware modes to the Lapdock.

[Niall101]

What I didn't realise (or even really consider) was that the LapDock power interruption was only 'momentary'.

This then becomes less of a 'feature' and more of a 'bug' - unless you are prepared to take advantage of the behaviour and to the control some form of siemi-intelligent power circuitry between the LapDock and the Pi.

Mind you, given that the physical interface between the two units is less than ideal anyway, peehaps there is scope for a 'proper' hardware hack - to deal with the HDMI interface as well as the power interface (without having to resort to 'fettling' cables and adaptors).

Cheers,
Niall