Back at it again. Due to funding issues, I have been using all the spare parts that I have acquired over the past 1-2 years. This week it was finally time to put the blinky lights to good use. Just about 3 years ago I had attempted to set up BobLight using a Raspberry Pi 2, Kodi, and a set of WS2801 LEDs. This worked ok, but it wasn’t the greatest. The majority of the time, only the set that was nearest to the Pi would light up, the remainder would work intermittently, if at all. This caused the project to be put on the back burner since the cost of the LED strip and connectors made it not worthwhile to replace the setup. Fast Forward 2 years, and I acquired a 5m length of WS2812B LEDs, an Arduino compatible Nano, yet another Raspberry Pi 3, and a 5V/8A power supply. Continue reading Hyperion+RetroPie+Kodi=Bliss!
While attempting to assist someone with getting apps loaded onto a Android TV Stick, I ran into a slight problem. A parental control pin was enabled, and I had no way of immediately getting in touch with the person. In app configuring couldn’t be done without the pin, since the app wouldn’t launch without asking. After some hunting to try to locate where the system stores whether the app has launched before, I had an idea. Go in through adb, and try launching from the shell. Lo and behold it worked, but still wouldn’t launch afterwards from the gui. Doesn’t matter to me as the owner knows the PIN code. I got what I needed to do done, and confirmed everything was working. If anyone is interested the appropriate code to launch it through adbFire was located here. A little massaging was needed since we already had an adb shell through adbFire, and voilà. The app runs without a pin code. Not an elegant solution since we need adb access to allow it to run every time without the PIN, but it’s functional for my needs. As far as massaging the command, it was as simple as dropping “adb shell” from the beginning.