So the solution is just wait until such controls are coded for CA0132? From what I heard, CA0132 was primarily coded for the Chromebook Pixel hardware rather than the Recon3D or Sound Blaster Z chips.
So the solution is just wait until such controls are coded for CA0132? From what I heard, CA0132 was primarily coded for the Chromebook Pixel hardware rather than the Recon3D or Sound Blaster Z chips.