I went for a long drive yesterday, with android auto on the whole time. Music streams via Bluetooth (which makes no sense when I have the cable connected, but whatever). My phone was EXTREMELY hot when I got back home. I know it gets hot when I use Bluetooth, but this time it was almost too hot to touch during the drive.
Does this happen to you, too? It was a 4 hour drive.
Howdy fellow enthusiasts! Summer is finally here, and I'm looking for roads! You know the kind of roads I mean. I found one out of Templin towards Vietmannhof yesterday which was nice, but I'm hoping for more turns. Where do you go to drive?
I have had the same issue now with two setups. The setup is this: I have a button (in one instance a simple button that comes with all the beginner electronics kits, and in the second instance a actual keyboard button, a cherry clone) that's corrected to an MCP23017. I have the MCP23017 configured to catch pin interrupts, and then I query these interrupts in a loop. I have one button and 5 rotary encoder on the same one. The rotary encoders never, as far as I can tell, produce spurious signals, but the button does. Not very often, a couple of times a day, but it does happen. This happened both on my breadboard, and in the final PCB.
Any idea why this happens, and how I might fix it? One approach I was considering was only triggering if the button has been pressed for more than some time period, but I feel like I might have issues with that, because I need to register when the button is released, too.