1080p resolution on HDMI for omap blaze

Haran Ashok

Hi,

I am using this release of ICS to boot omap Blaze http://omappedia.org/wiki/L27.IS.2.P2_OMAP4_Icecream_Sandwich_Release_Notes.I want to achieve 1080p output on my HDMI.How can i achieve it?

Regards

Haran

over 13 years ago

0 Chintan Patel over 13 years ago

TI__Intellectual 1410 points

Haran,

Give us some more details to understand. Are you saying after connecting HDMI TV to blaze you are not getting 1080p resolution? Are you getting some other resolution? Also attach #logcat.

Regards,

Chintan

0 Haran Ashok over 13 years ago in reply to Chintan Patel

Expert 1175 points

Hi Chintan,

Thanks for the reply.When i connect my Omap blaze to a 1080p supported TV Android by default selects a resolution of 1280*720 and not 1920*1080.What should i do for Android to select a resolution of 1080p.

Here is the logcat

V/WiredAccessoryObserver( 193): Intent.ACTION_USB_HEADSET_PLUG: state: 0 name: hdmi
D/ti_hwc ( 117): #0: 1920x1080 60Hz
D/ti_hwc ( 117): #1: 1280x720 60Hz
D/ti_hwc ( 117): #2: 720x480 59Hz
D/ti_hwc ( 117): #3: 720x480 59Hz
D/ti_hwc ( 117): #4: 1920x1080 60Hz
D/ti_hwc ( 117): #6: 1920x1080 24Hz
D/ti_hwc ( 117): #7: 1280x720 60Hz
D/ti_hwc ( 117): #8: 720x480 59Hz
D/ti_hwc ( 117): #9: 720x480 59Hz
D/ti_hwc ( 117): #10: 640x480 59Hz
D/ti_hwc ( 117): picking #1
V/AudioService( 193): Broadcast Receiver: Got ACTION_HDMI_AUDIO_PLUG, state = 1
V/WiredAccessoryObserver( 193): Headset UEVENT: {SUBSYSTEM=switch, SWITCH_STATE=1, DEVPATH=/devices/virtual/switch/hdmi, SEQNUM=1438, ACTION=change, SWITCH}
V/WiredAccessoryObserver( 193): newState = 16, headsetState = 16,mHeadsetState = 0
V/WiredAccessoryObserver( 193): Intent.ACTION_USB_HEADSET_PLUG: state: 1 name: hdmi
I/ti_hwc ( 117): external display changed (state=1, mirror={enabled tform=0deg}, dock={enabled tform=0deg}, tv=1

Regards

Haran

0 Chintan Patel over 13 years ago in reply to Haran Ashok

TI__Intellectual 1410 points

Haran,

Try the following commands on your terminal and see the result:

# stop
# setprop persist.hwc.mirroring.region ""
# start

Regards,

Chintan

0 Haran Ashok over 13 years ago in reply to Chintan Patel

Expert 1175 points

Hi Chintan,

Still it takes a resolution of 1280*720 and not 1080p resolution.

Regards

Haran

0 Chintan Patel over 13 years ago in reply to Haran Ashok

TI__Intellectual 1410 points

Haran,

It should work. I suggest to do one of the following:

1) Try with the latest IC release:

http://www.omappedia.com/wiki/4AI.1.4_OMAP4_Icecream_Sandwich_Release_Notes

2) Continue debug the same release by looking into the file mydroid\hardware\ti\omap4xxx\hwc\hwc.c and function omap4_hwc_set_best_hdmi_mode() for further debug. Like try increasing struct dsscomp_videomode modedb[16] to struct dsscomp_videomode modedb[32].

Le us know your observation later.

Regards,

Chintan

0 Mayank Mangla over 13 years ago in reply to Chintan Patel

TI__Mastermind 24525 points

Which TV model are you using? Can you try on a different model?

0 Haran Ashok over 13 years ago in reply to Chintan Patel

Expert 1175 points

Hi Chintan,

I was able to achieve 1920*1080 with some changes in the hwc.c file ie what i did is i forced android to pick up 1920*1080 resolution and it occupied only 2/3rd of my TV ie the display was in the top left corner occupying only 2/3rd of the display and with a lot of disturbances ie those white spots everywhere.Is this approach fine or should i try something else.What should i do to get a clear 1080p display.I confirmed that it was a 1080p display by checking the display1 timings.

Regards

Haran

0 Matthew Kiser over 13 years ago in reply to Haran Ashok

TI__Intellectual 1300 points

Haran,

Chintan has given you the correct answer. Removing the mirroring.region property is all that is necessary. However the release you are using is very early and does not work correctly in all cases. You need to move to the latest L4AI release and it should work. The reason changing the hwc.c file does not work is that while you forced it to choose the FHD resolution, you did not set up the HWC to enlarge the surfaces. The reason HD is the default and not FHD is because the blaze tablet's panel is close to (but not exactly) 1280x720, so the mirroring.region property is set up so that the tablet's panel is correctly displayed on HDMI in HD resolution.

Instead of changing the hwc code, We suggest you upgrade to the latest ICS releast L4AI.1.4 and unset the persist.hwc.mirroring.region property.This should fully duplicate and enlarge the surfaces to FHD resolution on HDMI when mirroring.

0 Haran Ashok over 13 years ago in reply to Matthew Kiser

Expert 1175 points

Hi Matt,

Thanks for the reply.Will try with the latest release and will revert back to you soon with the results.

Regards

Haran

0 Haran Ashok over 13 years ago in reply to Haran Ashok

Expert 1175 points

Hi Matt,

Tried with the latest release but it still takes a resolution of 1280*720 only and not 1080p.I did the procedure as instructed by Chintan but still no use.It by default selects 720p resolution and not 1080p.This is the release that i used.

http://omappedia.org/wiki/4AI.1.4_OMAP4_Icecream_Sandwich_Release_Notes

Regards,

Haran

0 Chintan Patel over 13 years ago in reply to Haran Ashok

TI__Intellectual 1410 points

Haran,

Are you using Blaze or Blaze tablet?

I have tried default 4AI.1.4 release on my Blaze tablet for "Android on Tablet" from the following link. The file name is omap4_emmc_files_blaze_tablet_4AI.1.4.tar.bz2. I have not modified anything or replaced anything.

http://www.omappedia.com/wiki/Android:_Working_with_pre-built_binaries

I have booted with HDMI TV connected initially it picked up 1280x7120 resolution as shown in the logs below:

I/ti_hwc ( 123): clone region is set to (0,0) to (1280,720)
D/ti_hwc ( 123): #0: 1920x1080 60Hz
D/ti_hwc ( 123): #1: 640x480 59Hz
D/ti_hwc ( 123): #2: 640x480 72Hz
D/ti_hwc ( 123): #3: 640x480 75Hz
D/ti_hwc ( 123): #4: 800x600 56Hz
D/ti_hwc ( 123): #5: 800x600 60Hz
D/ti_hwc ( 123): #6: 800x600 72Hz
D/ti_hwc ( 123): #7: 800x600 75Hz
D/ti_hwc ( 123): #8: 1024x768 60Hz
D/ti_hwc ( 123): #9: 1024x768 70Hz
D/ti_hwc ( 123): #10: 1024x768 75Hz
D/ti_hwc ( 123): #11: 1280x1024 75Hz
D/ti_hwc ( 123): #12: 1280x960 60Hz
D/ti_hwc ( 123): #13: 1280x1024 60Hz
D/ti_hwc ( 123): #14: 1280x720 60Hz
D/ti_hwc ( 123): #15: 1280x720 50Hz
D/ti_hwc ( 123): #16: 720x480 59Hz
D/ti_hwc ( 123): #17: 720x576 50Hz
D/ti_hwc ( 123): #18: 640x480 59Hz
D/ti_hwc ( 123): #19: 720x480 59Hz
D/ti_hwc ( 123): #20: 720x576 50Hz
D/ti_hwc ( 123): #21: 1280x720 50Hz
D/ti_hwc ( 123): #22: 1280x720 60Hz
D/ti_hwc ( 123): #23: 1920x540 50Hz
D/ti_hwc ( 123): #24: 1920x540 60Hz
D/ti_hwc ( 123): #25: 1920x1080 50Hz
D/ti_hwc ( 123): #26: 1920x1080 60Hz
D/ti_hwc ( 123): picking #14
I/ti_hwc ( 123): external display changed (state=1, mirror={enabled tform=0deg}, dock={enabled tform=0deg}, tv=1
I/ti_hwc ( 123): omap4_hwc_device_open(rgb_order=1 nv12_only=0)
I/ti_hwc ( 123): Unable to open gc-core device (1), blits disabled

After that I have tried the commands as I have suggested to you on terminal:

# stop
# setprop persist.hwc.mirroring.region ""
# start

After that the new resolution picked up is 1920x1080 as shown in the logs below:

I/ti_hwc ( 1138): clone region is set to (0,0) to (1024,768)
D/ti_hwc ( 1138): #0: 1920x1080 60Hz
D/ti_hwc ( 1138): #1: 640x480 59Hz
D/ti_hwc ( 1138): #2: 640x480 72Hz
D/ti_hwc ( 1138): #3: 640x480 75Hz
D/ti_hwc ( 1138): #4: 800x600 56Hz
D/ti_hwc ( 1138): #5: 800x600 60Hz
D/ti_hwc ( 1138): #6: 800x600 72Hz
D/ti_hwc ( 1138): #7: 800x600 [ 155.574005] tc358765 display0: disable
[ 155.574127] misc dsscomp: [c66fd800] ignoring set failure -22
75Hz
D/ti_hwc ( 1138): #8: 1024x768 60Hz
D/ti_hwc ( 1138): #9: 1024x768 70Hz
D/ti_hwc ( 1138): #10: 1024x768 75Hz
D/ti_hwc ( 1138): #11: 1280x1024 75Hz
D/ti_hwc ( 1138): #12: 1280x960 60Hz
D/ti_hwc ( 1138): #13: 1280x1024 60Hz
D/ti_hwc ( 1138): #14: 1280x720 60Hz
D/ti_hwc ( 1138): #15: 1280x720 50Hz
D/ti_hwc ( 1138): #16: 720x480 59Hz
D/ti_hwc ( 1138): #17: 720x576 50Hz
D/ti_hwc ( 1138): #18: 640x480 59Hz
D/ti_hwc ( 1138): #19: 720x480 59Hz
D/ti_hwc ( 1138): #20: 720x576 50Hz
D/ti_hwc ( 1138): #21: 1280x720 50Hz
D/ti_hwc ( 1138): #22: 1280x720 60Hz
D/ti_hwc ( 1138): #23: 1920x540 50Hz
D/ti_hwc ( 1138): #24: 1920x540 60Hz
D/ti_hwc ( 1138): #25: 1920x1080 50Hz
D/ti_hwc ( 1138): #26: 1920x1080 60Hz
D/ti_hwc ( 1138): picking #0

So the suggestions provided should work as it is. Can you try changing the TV or re-flash the device as I have mentioned at start?

You can check the selected HDMI TV timings by following command:

For Blaze Tablet: shell@android:/ # cat /sys/devices/platform/omapdss/display1/timings

For Blaze: shell@android:/ # cat /sys/devices/platform/omapdss/display2/timings

Regards,

Chintan

0 Matthew Kiser over 13 years ago in reply to Chintan Patel

TI__Intellectual 1300 points

Also be sure to

setprop persist.hwc.mirroring.enabled "1"

This will help to ensure the entire UI is mirrored to HDMI and not just video layers.

0 Haran Ashok over 13 years ago in reply to Matthew Kiser

Expert 1175 points

Hi,

Even though i do not use the prebuilts i compile android for blaze of the latest release and when i boot it and follow the above instructions it still takes 720p and not 1080p.I dont know what is the problem here is the LOG.

I/ti_hwc ( 115): The value of ext->mirror.rotation is --------------->>>>>>>>>0
I/ti_hwc ( 115): THe value of ext->force_dock is ---------->>>>>>>>0
D/ti_hwc ( 115): #0: 1920x1080 60Hz
D/ti_hwc ( 115): #1: 1280x720 60Hz
D/ti_hwc ( 115): #2: 720x480 59Hz
D/ti_hwc ( 115): #3: 720x480 59Hz
D/ti_hwc ( 115): #4: 1920x1080 60Hz
D/ti_hwc ( 115): #5: 1920x540 60Hz
D/ti_hwc ( 115): #6: 1920x1080 24Hz
D/ti_hwc ( 115): #7: 1280x720 60Hz
D/ti_hwc ( 115): #8: 720x480 59Hz
D/ti_hwc ( 115): #9: 720x480 59Hz
D/ti_hwc ( 115): #10: 640x480 59Hz
D/ti_hwc ( 115): picking #1

Regards

Haran

0 Haran Ashok over 13 years ago in reply to Haran Ashok

Expert 1175 points

Hi,

Can you pls tel me what are the bootargs that has to be given?I am giving these bootargs

setenv bootargs androidboot.console=ttyO2 console=ttyO2,115200n8 mem=456M@0x80000000 mem=512M@0xA0000000 root=/dev/mmcblk1p2 rw rootdelay=2 init=/init vram="64M" omapfb.vram="0:32M,1:32M" consoleblank=0
setenv bootcmd 'mmcinit 0; fatload mmc 0 0x80000000 uImage;bootm 80000000'

Is the frame buffer size sufficient or should i give a bigger frame buffer size?

Regards

Haran

0 Chintan Patel over 13 years ago in reply to Haran Ashok

TI__Intellectual 1410 points

Look into the file ($MYDROID/device/ti/support-tools/boot/omap4/umulti2.sh) for bootargs used for blaze. The 32M buffer is big enough for four(4) 1080p RGB (1920*1080*2*4) buffers so that may not be issue.

Regards,

Chintan

0 Johnny over 13 years ago in reply to Chintan Patel

Intellectual 585 points

hi,

i have this issue ,how to do it ,thanks !

johnny

0 Venkat Ramana Peddigari over 13 years ago in reply to Johnny

TI__Expert 4120 points

Hi Johnny & Haran,

You can try to modify the cea_modes array in modedb.c file in the kernel to exclude the 1280 x 720 timings so that it can pick the 1920 x 1080 timings as per your preference. Following post http://e2e.ti.com/support/omap/f/849/p/188792/677685.aspx#677685 also modified this array to address a similar issue.

Alternately, you have to modify the ti_hwc code namely mydroid\hardware\ti\omap4xxx\hwc\hwc.c and function omap4_hwc_set_best_hdmi_mode()as per the guidelines provided by Chintan earlier to pick your preferred timings.

Thanks & Best Regards,

Venkat

0 Johnny over 13 years ago in reply to Venkat Ramana Peddigari

Intellectual 585 points

Hi Venkat,

Thanks you reply ! It can pick the 1920 x 1080 timing ,but it it would not occupy full screen.

Thanks & Best Regards,

johnny

0 Haran Ashok over 13 years ago in reply to Johnny

Expert 1175 points

Hi Johnny,

How did you do it?

Regards

Haran

0 Venkat Ramana Peddigari over 13 years ago in reply to Johnny

TI__Expert 4120 points

Hi Johnny,

Seems like the frame buffer composed by the Surface Flinger is corresponding to Blaze or Blaze Platform's LCD which is lower than the 1920 x 1080 and so the content created is less than the HDMI TV 1080p timings. It would try to center it by maintaining aspect ratio with borders around.

Could you please share the following sysfs commands outputs for further analysis of your set up?

cat /sys/devices/platform/omapdss/overlay0/*

cat /sys/devices/platform/omapdss/overlay1/*

cat /sys/devices/platform/omapdss/overlay2/*

cat /sys/devices/platform/omapdss/overlay3/*

cat /sys/devices/platform/omapdss/display0/timings

cat /sys/devices/platform/omapdss/display1/timings

cat /sys/devices/platform/omapdss/display2/timings

cat /sys/class/graphics/fb0/*

Thanks & Best Regards,

Venkat

0 Johnny over 13 years ago in reply to Venkat Ramana Peddigari

Intellectual 585 points

Hi Venkat,

cat /sys/devices/platform/omapdss/overlay0/*
0
255
1024,768
lcd2
gfx
1024,768
0,0
1
0
1..255
1..255
0

shell@android:/ # cat /sys/devices/platform/omapdss/overlay1/*
0
255
1024,720
lcd2
vid1
1024,720
0,0
1
1024
1..255
1..255
1

shell@android:/ # cat /sys/devices/platform/omapdss/overlay2/*
0
255
1024,48
lcd2
vid2
1024,48
0,720
0
1024
1..255
1..255
2

127|shell@android:/ # cat /sys/devices/platform/omapdss/overlay3/*
0
255
1024,768
lcd2
vid3
1024,768
0,0
1
1024
1..255
1..255
3

cat /sys/devices/platform/omapdss/display0/timings
100032,1024/300/520/240,768/16/6/10

0 Venkat Ramana Peddigari over 13 years ago in reply to Johnny

TI__Expert 4120 points

Hi Johnny,

Based on the above outputs, none of the overlays are directed to TV. Did you connect the HDMI TV with the fix you had to enable HDMI to pick 1080p timings. I remember you saying that the UI shown on TV does not occupy full screen. I want to know these outputs under these conditions.

Moreover, how about the following outputs:

cat /sys/devices/platform/omapdss/display1/timings

cat /sys/devices/platform/omapdss/display2/timings

cat /sys/class/graphics/fb0/*

Thanks & Best Regards,

Venkat

0 Haran Ashok over 13 years ago in reply to Venkat Ramana Peddigari

Expert 1175 points

Hi Johnny,

Can you tel me how did you achieve 1080p on blaze.

Regards

Haran

0 Haran Ashok over 13 years ago in reply to Haran Ashok

Expert 1175 points

Hi Venkat,

I was able to acheive 1080p output on Blaze.Thanks for your responses....:):)

Regards

Haran

0 Younger Su over 12 years ago in reply to Haran Ashok

Intellectual 380 points

Hi, Haran

how to get the logcat?

Type anything in anywhere?

Younger

0 hoangduong139 over 12 years ago in reply to Haran Ashok

Intellectual 305 points

Hi Haran,

At this moment i have same problem with you. Could you tell me how to acheive 1080p output on Blaze, i got much time for solve this issue with no success.

Regards,

Hoang Duong.

0 Haran Ashok over 12 years ago in reply to hoangduong139

Expert 1175 points

Hi Hoang,

You have to tweak through the driver code drivers/video/modedb.c from where the hwc in Android will take the relevant resolutions so you have to comment out those resolutions that does not allow Android to select 1080p.

Regards

Haran

0 hoangduong139 over 12 years ago in reply to Haran Ashok

Intellectual 305 points

Dear Haran,

Thanks you so much for helping me solve this issue. I made some change in linux kernel through your guide and gave 1080p resolution on HDMI display.

One again, thanks so much, Haran,

Hoang Duong.

0 Haran Ashok over 12 years ago in reply to hoangduong139

Expert 1175 points

Hi Hoang

I am very glad that this solved ur issue.

Regards

Haran

Processors

Processors forum

1080p resolution on HDMI for omap blaze