2013-05-18, 14:05
I'm quite happy with my G box midnight clone, but the only problem was that the cvbs (component) output, does not work when first not connected to a hdmi screen. Since I bought this box to be used in my sleeping room on my old tv (which does not have hdmi), I realy need the cvbs output.
After looking in system/bin/set_display_mode.sh, the following lines seem to test if the cubs output is active:
if [ "$(getprop ro.amlogic.has.CvbsOutput)" = "true" ]; then
cvbsmode=$(getprop ubootenv.var.cvbsmode)
after debugging, it seems that cvbsmode is not correctly initialized, although ro.amlogic.has.CvbsOutput returns 'true". However, cvbsmode is set to null, meaning that ubootenv.var.cvbsmode does not report the correct screen mode.
If I force cvbsmode to the required value by
cvbsmode="576cvbs" and start the script manually, it all works and I can start XBMC again.
Can somebody verify this?
I don't have the android knowledge to find out why ubootenv.var.cvbsmode does report the incorrect value??
I now have a temporary solution by ssh-ing to my box and to start manually a modified set_display_mode script, but hopefully there is a more elegant solution?
UPDATE: after entering
setprop ubootenv.var.cvbsmode "576cvbs" ,
I can now switch it on and of with the remote control, the settings survives the power down/powerup cycles.. weird... No need to run the modified set_display_mode.sh anymore. Still don't understand it, but it seems to work
After looking in system/bin/set_display_mode.sh, the following lines seem to test if the cubs output is active:
if [ "$(getprop ro.amlogic.has.CvbsOutput)" = "true" ]; then
cvbsmode=$(getprop ubootenv.var.cvbsmode)
after debugging, it seems that cvbsmode is not correctly initialized, although ro.amlogic.has.CvbsOutput returns 'true". However, cvbsmode is set to null, meaning that ubootenv.var.cvbsmode does not report the correct screen mode.
If I force cvbsmode to the required value by
cvbsmode="576cvbs" and start the script manually, it all works and I can start XBMC again.
Can somebody verify this?
I don't have the android knowledge to find out why ubootenv.var.cvbsmode does report the incorrect value??
I now have a temporary solution by ssh-ing to my box and to start manually a modified set_display_mode script, but hopefully there is a more elegant solution?
UPDATE: after entering
setprop ubootenv.var.cvbsmode "576cvbs" ,
I can now switch it on and of with the remote control, the settings survives the power down/powerup cycles.. weird... No need to run the modified set_display_mode.sh anymore. Still don't understand it, but it seems to work