The Stadia controller runs on a NXP i.MX RT1061 MCU [1], and a Broadcom BCM43458 wireless chip.<p><a href="http://en.techinfodepot.shoutwiki.com/wiki/Google_Stadia_(H2B)" rel="nofollow">http://en.techinfodepot.shoutwiki.com/wiki/Google_Stadia_(H2...</a><p>Broadcom are $#&@ for documentation and licensing, so I'm not super optimistic.<p>[1] <a href="https://www.nxp.com/products/processors-and-microcontrollers/arm-microcontrollers/i-mx-rt-crossover-mcus/i-mx-rt1060-crossover-mcu-with-arm-cortex-m7-core:i.MX-RT1060" rel="nofollow">https://www.nxp.com/products/processors-and-microcontrollers...</a>
Although I'm unfamiliar with bluetooth drivers, how would you go about making binary files portable?<p>I'd imagine one would decompile the binaries, and modify the source code for redistribution as some portable library supporting whatever build target a user has. Of course, I assume (1) the decompiler can't detect compile-time macros detecting architecture and (2) you'd be screwed if you need shared libraries.<p>P.S. Interestingly, the first link when one googles "firmware decompiler" is to CIA code on Wikileaks lol
I did this update on one of my controllers, and the lag most of the time was barely tolerable. The rest of the time was lag spikes that made games unplayable.<p>I thought maybe it was the fault of my BT chip in my computer, so I turned it off and plugged it in instead, and the lag was most gone, but still worse than my Razer Wolverine.<p>I just threw mine in a box and gave up on it. I probably won't even bother flashing my other 2.
Wondering if this is firmware is signed, hoping they removed signing or it was never signed. I've used the controller a bit this week to play games on my android phone and quite like it.