I just got my new MacBook Pro and haven't been able to get KbCheck or KbQueue to report any keyboard inputs. I don’t get any errors, however, no keypresses register. Any suggestions?
Thanks,
-Aaron
<aaron.seitz@...> wrote :
-> My suggestion would be to return it and get some other laptop from another manufacturer. From all i've read about the 2016 MacBookPro so far, if only half of it is true, this must be the most overpriced, under-specified for its price and "Pro" label, buggy, incompatible and non-pro laptop ever built.
The gpu's are from AMD's Polaris family, which is good. They chose the most low-end and low-performance variants of the Polaris family, which is ridiculous given the "Pro" label and the price of the MBP. Also they seem to be seriously buggy, either the hardware or their drivers. See GPU glitches in 2016 MacBook Pro models | Hacker News
The USB-C ports seem to be incompatible with a large range of USB-C certified devices. Various display adapters, including some of Apples own display adapters for USB-C, seem to incapable of outputting a proper video signal to different displays, or a video signal at all.
The keyboard and touch pad seem to use a new proprietary bus system, which may explain your KbCheck troubles.
The memory, limited to 16 GB max, disc drives and everything else are non-upgradeable. iFixit gave it the lowest repairability score ever.
Oh yes, and "upgrade to Linux" to side-step OS bugs won't work either. It is maximally incompatible with Linux at the current time.
Needless to say, given its potential for trouble, i consider the MBP 2016 unsupported by PTB for the time being, if anybody runs into any problems with it.
So, what is the complete detailed output of [keyboardIndices, productNames, allInfos] = GetKeyboardIndices
A new PTB beta should go out today. If this output hints to a trivial 15 minute fix, i'll try to implement it. Otherwise you are out of luck.
good luck,
-mario
The
I just got my new MacBook Pro and haven't been able to get KbCheck or KbQueue to report any keyboard inputs. I don’t get any errors, however, no keypresses register. Any suggestions?
-> My suggestion would be to return it and get some other laptop from another manufacturer. From all i've read about the 2016 MacBookPro so far, if only half of it is true, this must be the most overpriced, under-specified for its price and "Pro" label, buggy, incompatible and non-pro laptop ever built.
The gpu's are from AMD's Polaris family, which is good. They chose the most low-end and low-performance variants of the Polaris family, which is ridiculous given the "Pro" label and the price of the MBP. Also they seem to be seriously buggy, either the hardware or their drivers. See GPU glitches in 2016 MacBook Pro models | Hacker News
The Wifi apparently fails or malfunctions when you connect various devices to the USB-C ports.
The USB-C ports seem to be incompatible with a large range of USB-C certified devices. Various display adapters, including some of Apples own display adapters for USB-C, seem to incapable of outputting a proper video signal to different displays, or a video signal at all.
The keyboard and touch pad seem to use a new proprietary bus system, which may explain your KbCheck troubles.
The memory, limited to 16 GB max, disc drives and everything else are non-upgradeable. iFixit gave it the lowest repairability score ever.
Oh yes, and "upgrade to Linux" to side-step OS bugs won't work either. It is maximally incompatible with Linux at the current time.
Needless to say, given its potential for trouble, i consider the MBP 2016 unsupported by PTB for the time being, if anybody runs into any problems with it.
So, what is the complete detailed output of [keyboardIndices, productNames, allInfos] = GetKeyboardIndices
A new PTB beta should go out today. If this output hints to a trivial 15 minute fix, i'll try to implement it. Otherwise you are out of luck.
good luck,
-mario
The
Thanks,
-Aaron