[Samsung Galaxy Nexus] nikodr:
[MENTION=6140342]Fenix46[/MENTION] if usb debugging is working would it be possible to execute this command after the black screen?

adb shell cat /sys/class/graphics/fb0/virtual_size

adb shell cat /sys/devices/omapdss/display0/timings

adb shell cat /sys/devices/omapdss/display0/enabled

can you post the output ?

i saw in the dmesg log some errors regarding the hdmi display.could it be that it does not send to lcd anything?it says

"<4>[ 2.293395] omapfb omapfb: no driver for display: hdmi

<3>[ 2.315155] omapdss error: timeout reading edid

<4>[ 2.315490] omapdss HDMI: failed to read E-EDID

<3>[ 2.384338] omapdss error: timeout reading edid

<4>[ 2.384552] omapdss HDMI: failed to read E-EDID

<6>[ 2.580444] cannot apply mgr(lcd) on inactive device

<6>[ 2.580566] cannot apply mgr(lcd) on inactive device

<4>[ 2.580780] omapfb omapfb: failed to apply dispc config

<6>[ 2.580902] cannot aply mgr(tv)--invalid device

<4>[ 2.581024] omapfb omapfb: failed to apply dispc config

<6>[ 2.581207] cannot aply mgr(lcd2)--invalid device

<4>[ 2.581329] omapfb omapfb: failed to apply dispc config

<3>[ 2.581542] Can't get vlcd for display!

<6>[ 2.582977] VAUX3_6030: disabling"

what hdmi driver?the lcd1 and lcd2 where are they?I thought that the hdmi output was for android devices having an hdmi output and that it is enabled if you have a cable.Or am i wrong and the hdmi simply means the lcd1 or lcd2 ?

shouldn't it say "omapfb omapfb: no driver for display: lcd" but on the logs i didnt see that one line.

so from the logs i assume it tries to output the lcd1 and lcd2 on the inactive device that does not have driver that is the device hdmi ?

i saw that the Kernel boot options on the command line: console=ttyFIQ0 androidboot.console=ttyFIQ0 mem=1G omap_wdt.timer_margin=30 vmalloc=496M androidboot.selinux=permissive omapfb.fb_opt=-1,-1,-1,1,720,1280 androidboot.serialno=014E0F2607020013 androidboot.bootloader=PRIMEMD04 androidboot.baseband=I9250XXLJ1 lcd_bootfb=0xbea70000 mms_ts.panel_id=162 androidboot.macaddr=

here https://e2e.ti.com/support/omap/f/849/t/319208 it says regarding omapfb

"omapfb.mode=<xres>x<yres>[M][R][-<bpp>][@<refresh>][m] or <name>[-<bpp>][@<refresh>]

- Default video mode for specified displays. For example - "dvi:800x400MR-24@60".

<xres>, <yres>, <bpp> and <refresh> are decimal numbers and <name> is a string.

<xres> is resolution in x-axis.

<yres> is resolution in y-axis.

<bpp> is bit per pixel.

[M] will allow to compute the timings using VESA(tm) Coordinated Video Timings (CVT).

[R] will allow to compute with reduced blanking (for flatpanels).

will allow to compute interlaced mode.

[m] will add margins equal to 1.8% of xres rounded down to 8 pixels, and 1.8% of yres.

NOTE: The char 'i' and 'm' must be after 'M' and 'R'. Example:

Just for information: 1024x768MR-8@60m = Reduced blank with margins at 60Hz.

For more information, See drivers/video/modedb.c.

There are also two special modes: "pal" and "ntsc" that can be used to tv out.

- HDMI:

This holds only for L24.8 release or earlier. Auto detection for TV is enabled post L24.8.

omapdss.hdmicode = {Timing value supported by the TV} omapdss.hdmimode = {Mode DVI or HDMI depending on the timing}

- By default the value of hdmicode = 16 {1080p} and hdmimode = 1 {HDMI mode} is taken.

- vram - frame buffer change:

omapfb.vram=<fbnum>:<size>[@<physaddr>][,...]

- VRAM allocated for a framebuffer. Normally omapfb allocates vram

depending on the display size. With this you can manually allocate

more or define the physical address of each framebuffer. For example,

"1:4M" to allocate 4M for fb1."

so should we place the lcd option word before the resolution ?

the error "omapdss HDMI: failed to read E-EDID " maybe this explains something https://e2e.ti.com/support/omap/f/849/t/374309 ?

what about this site that has information regarding the boot options needed http://59.124.231.13/index.php/Bootargs_for_enabling_display ?