01-09-2017, 05:33 AM
I have been meaning to get back to this post, but haven't had the time for a while, due to an extremely busy Fall / Christmas season..
Anyway, I have done quite some thinking and experimenting with regards to this problem, changing different settings, and meticulously noting what and when I did and whether it had any effect. What we know:
1) In addition to myself, 5 other users have had the issue, and reported it in this thread: Skip, frllop, Ketil, timrprobocom, and alanmcorcan. We all use a Samsung 12.2 inch device, so the problem definitely seems to be related to this tablet family.
2) The problem has appeared with both the Note Pro and the Tab Pro tablets. Which means the presence of the S-pen is not the cause of the problem.
3) During my testing, I have tried downgrading and upgrading the OS several times, and I have got black pages on both Android 4.4.2 and Android 5.0.2. So the OS version does not seem to be the cause of the problem.
4) I have tried using both the Quality and the Speed rendering - and have got black pages on both. So the error does not seem to be related to the rendering library used.
5) The presence or non-presence of a Bluetooth pedal does not seem to have any impact on the problem. I have seen the black pages both with and without a pedal connected.
6) During a few months in the late summer / early Fall, I tried using the diagnostic build, which Mike was kind enough to put together (which would analyze the screen contents and generate an error message / send an error report if a black page was detected). When using the diagnostic build, I never had any black pages - but instead I got instant crashes from time to time (ie, occasionally I would turn a page, and MSP would instantly shut down without warning or error message of any kind). I have never had these crashes when NOT using the diagnostic build. So my theory is that what would normally be shown as a black page would cause a crash when occurring in the diagnostic build (when trying to analyze the screen contents of a black page?)
All this being said, I'm very happy to say that I haven't had a single black page for almost two months now! It can, of course, be a coincidence. But looking back at what I've tried lately, the last setting I changed was on November 14th, when I checked the "Disable hardware overlays" setting in the Developer options. Is it at all possible that this setting could have an impact on the appearance of the black pages? And if so, could this give any clue as to why the black pages appear in the first place?
Anyway, I have done quite some thinking and experimenting with regards to this problem, changing different settings, and meticulously noting what and when I did and whether it had any effect. What we know:
1) In addition to myself, 5 other users have had the issue, and reported it in this thread: Skip, frllop, Ketil, timrprobocom, and alanmcorcan. We all use a Samsung 12.2 inch device, so the problem definitely seems to be related to this tablet family.
2) The problem has appeared with both the Note Pro and the Tab Pro tablets. Which means the presence of the S-pen is not the cause of the problem.
3) During my testing, I have tried downgrading and upgrading the OS several times, and I have got black pages on both Android 4.4.2 and Android 5.0.2. So the OS version does not seem to be the cause of the problem.
4) I have tried using both the Quality and the Speed rendering - and have got black pages on both. So the error does not seem to be related to the rendering library used.
5) The presence or non-presence of a Bluetooth pedal does not seem to have any impact on the problem. I have seen the black pages both with and without a pedal connected.
6) During a few months in the late summer / early Fall, I tried using the diagnostic build, which Mike was kind enough to put together (which would analyze the screen contents and generate an error message / send an error report if a black page was detected). When using the diagnostic build, I never had any black pages - but instead I got instant crashes from time to time (ie, occasionally I would turn a page, and MSP would instantly shut down without warning or error message of any kind). I have never had these crashes when NOT using the diagnostic build. So my theory is that what would normally be shown as a black page would cause a crash when occurring in the diagnostic build (when trying to analyze the screen contents of a black page?)
All this being said, I'm very happy to say that I haven't had a single black page for almost two months now! It can, of course, be a coincidence. But looking back at what I've tried lately, the last setting I changed was on November 14th, when I checked the "Disable hardware overlays" setting in the Developer options. Is it at all possible that this setting could have an impact on the appearance of the black pages? And if so, could this give any clue as to why the black pages appear in the first place?