Posts: 156
Joined: Jan 2012
Reputation:
1
Diggs
Senior Member
Posts: 156
Boardcrusher,
I will give one of them a try tonight. I am curious, when you had the VNC solution working, did it require a constant remote connection, or did you just apply the settings via the remote connection then disconnect? I assume the purpose of VNC is just to allow you to change settings with the monitor disconnected. Thanks for the links, have spent a lot of time reading about this issue from all the links provided in this thread. Amazing how many suffer from this issue.
Posts: 156
Joined: Jan 2012
Reputation:
1
Diggs
Senior Member
Posts: 156
IT SEEMS TO BE FIXED!!!
It was a very busy weekend, and great weather outside so I didn't get to spend as much time on this as I wanted. I really wanted to post on here all the settings I changed. First and foremost the registry change linked by boardcrusher is the method I used. This worked mostly, but I needed to change a few other settings to get it completely correct.
1. The Catalyst drivers - I looked through all settings and see there is an autodetect setting, which was enabled. I changed this to manual.
2. All this time I thought I had been running XBMC full screen, when in fact it was in a full screen window. I changed this.
3. Vertical blank sync was also disabled, but I am not sure this has any impact. I would like to have this enabled and will test it this week and see if it impacts anything.
I was still getting an odd sized window for XBMC after the registry changes, but it was much improved. It seemed like a 4x3 aspect ratio was kicking in and I would have just one small bar to the right after turning the monitor back on. I changed all 3 settings above and XBMC would remain full screen at all times. I need to determine which of these 3 have any affect. I am guessing #2 was a big one and also the auto detection of the monitor in #1 would be key. Not sure that #3 had any affect at all, but then again I changed 3 things, rebooted and tested and it worked. Bad method I know, but just wanted to let people know that it is now resolved and working and how I got there.
Thanks EVERYONE for the input on this and I hope this helps someone else in the future.
Posts: 4
Joined: Feb 2013
Reputation:
0
2013-03-12, 09:52
(This post was last modified: 2013-03-12, 11:35 by boardcrusher.)
Good to hear you fixed it. Just wanted to point out that the method I used solved the problem immediately, without having to go through any of the other steps you mentioned. Also, since I already had VNC installed anyway, I think that the VNC-method is easier (for me anyway).
Posts: 789
Joined: Jun 2010
Reputation:
5
I need to try that as I have the same problem...
Box 1: ODroid N2+ 4GB
Box 2: Intel NUC D34010WYK (Windows afedchin's Krypton MVC Build)
Box 3: Vero 4K
RIP schimi2k | I miss you buddy :(
Posts: 451
Joined: Sep 2012
Reputation:
4
I had the same problem with the ccc 13.3 drivers.
When i use the ccc 12.8 it works.
Posts: 432
Joined: Jan 2013
Reputation:
2
One of the best threads I found
Posts: 432
Joined: Jan 2013
Reputation:
2
Right done this on Win7. Anyone tried this on Win8??
N
Posts: 432
Joined: Jan 2013
Reputation:
2
I didn't need to as I moved to openelec. That solved the problem for me. N
Posts: 7
Joined: Feb 2014
Reputation:
0
2014-07-12, 12:04
(This post was last modified: 2014-07-12, 12:12 by Akrofly.)
I have this problem as well but my setup is a little different.
Mac OSx mini server with mavericks OS
Philips TV connected as the only display via HDMI
The problem i faced was when the TV was switched off over a prolonged period of time or when the TV switched itself off due to a period of inactivity.
The symptoms are exactly as described in this thread, the XBMC was not in windows mode but surely smaller (about third of its full screen size).
The audio also disappeared which forced me to restart the Mac server before all went back to normal.
Now I have "keep audio device alive" set to "always" in "system - settings" and that seems to have helped the audio issue, but the screen still shrinks.
I will attempt the pin 19 exclusion and see if that works. (although i believe that killing the auto detection is not a real solution but merely a work arround).
I have tested the setup with a multitude of hardware specs.
- Android box
- Android MK mini
- MAC notebook (I have attempted with 3 version of the apple OS X software)
- Windows 7 (Fujitsu)
- Windows 8 (Lenovo)
- Windows 8.1 (Lenovo)
- Mac mini server (mavericks)
I even tried 2 different TVs and a dell screen + 1 wall mounted projector
All displayed the same problem/symptoms.
It would be a fair conclusion on my part to think it is an XBMC issue, or in the very least an XBMC burden to fix.
I gladly take tips regarding this matter.
Posts: 17
Joined: Oct 2013
Reputation:
0
myweb
Junior Member
Posts: 17
The following works for me:
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BusID "PCI:01:00:0"
Option "ConnectedMonitor" "DFP-0,DFP-1"
Option "UseHotplugEvents" "false"
Option "UseEDID" "true"
Option "IgnoreEDID" "false"
Option "CustomEDID" "DFP-0:/etc/X11/epson.edid.bin;DFP-1:/etc/X11/onkyo.edid.bin"
