It pains me whenever something we fixed lands back on our bench once again. Perhaps we should’ve seen the warning signs the first time around. Perhaps we did not test this controller thoroughly enough. Regardless of the error in our ways, the Nvidia controller is back on my bench and this time around it’s finally un-fucked while learning some things around the way.
Care to listen to my multi-thousand-word diatribe? Buckle up and keep on reading!
It was bound to happen!
Considering that we have three of these Nvidia Shield TV systems that were given friends it’s a no-brainer that a few of these controllers were to end up on my repair bench. This time around dealing with a very common issue. Sticky buttons. Maybe it’s just coffee?!?? Maybe too much PornHub! You never know as a repair tech! We should probably wear gloves for this one!
As always everything on s-config.com is on an AS-IS basis and is designed for educational purposes. Read our FAQ for more details.. We are not responsible for any damages that occur if you carry out such a repair on your hardware.
Would you like to know more? Continue to read onward!
Addressing overscan issues. The reason why overscan does not affect the stock Ouya is simply put they placed all of their lettering near the center of the screen for all of their actions. Leaving a large margin produces less of a need for a user to demand overscan to be fixed. Flat-panel televisions … Read more
When playing with android OS there needs to be an “Undo” button when it comes to the Firmware. The Ouya is no different. Perhaps as a user, you’ve grown tired of playing with Lineage. Perhaps you are going to sell your Ouya on eBay and you don’t want any data left on the thing. Or you’re trying to bring a soft-bricked Ouya back to life. Whatever the case may be this tutorial is here to help you wipe whatever is on your Ouya and bring it back to factory defaults.
This is considered “Section 5” of a long tutorial about Ouya because like all of the previous sections we’ll be relying on the Raspberry Pi or a Linux box to perform these tasks instead of going through the sheer pain of using ADB on a Windows environment. Also, some of the beginning sections are required for those who have never used a Linux box in their life.
Without further delay, let’s dive in shall we?
This tutorial assumes that you have already set up your base Raspberry Pi OS and that you are either operating locally on the Pi or via SSH from another PC. This tutorial uses a more traditional “Push” method that we’ve used in previous tutorials such as Cyanogen but updated for performing the same task underneath Lineage. This tutorial also assumes that This is our current 2019 method of flashing and programming Ouya and Android devices due to the nature of commercial OS’s locking the security down on hardware devices. If you have already unlocked ADB on your commercial OS and you have the ADB bridge drivers installed you can follow along on that OS with this tutorial.
Read on if you want to learn more.
This tutorial assumes that you have already set up your base Raspberry Pi OS and that you are either operating locally on the Pi or via SSH from another PC. This tutorial dives into the ability to sideload all of the packages required for the OS known as Lineage, which is a rebirth of the Cyanogen project in previous tutorials that we have done. This tutorial also assumes that This is our current 2019 method of flashing and programming Ouya and Android devices due to the nature of commercial OSs locking the security down on hardware devices. Read on if you want to learn more.
This blog is just one part of a multipart series on how to use the Raspberry Pi with the Ouya. It is designed this way because frankly there is way too much to cover in a single blog. Links for each of the articles as well as the header/main article will be included at the bottom of each entry to allow users ease of use in following along.
Read on if you want to know more.
I wished that the Android 5.0 scene on the Ouya matured a little more prior to making this tutorial. Upon originally doing the CyanogenMod tutorial. I came to the realization of being hit with walls of bugs, questions, and comments which most of them I frankly couldn’t answer. However, with the crushing progression of Kodi/XBMC moving onwards towards v17 Krypton. People are asking for a tutorial on how to make their Ouya still relevant.
You are not going insane in finding an ADB driver to install and this is not an error to my original tutorial about how to Mod the Ouya for Cyanogen tutorial. This problem directly ties into the “NEW and Improved” way windows 10 64-bit edition handles drivers and how outright malicious Microsoft has become by fulfilling their own drivers over hardware vendors they have no business in half-ass’edly supporting.
All of the documents and screen captures that I will be providing for you are accurate as of 4/27/2016 and when I originally made the Cyanogen tutorial I wanted this process to be as simple as possible. It’s turning out that Microsoft has other plans about their OS and the way it works forcing bloggers like myself to constantly made addendum entries about the same tutorials. Read on if you want to learn more about this beautiful disaster.
Ouya Anywhere is actually a title that was given by the Ouya fan community for the variant of “Ouya Everywhere” that was open for the beta test by devs to load onto tablets during its initial release of the Abominable Snowman patch of the OS. However, since it allowed almost any capable android box to run this program it gained slight popularity as a means of being a part of the Ouya Network without really having an Ouya or setting up a virtual box for developing things for the Ouya.