mneko

Nerding it up online since 1996

Been a gamer since time
immemorial. I'm pretty sure
I have joysticks older than
you.

posts from @mneko tagged #Kindle fire

also:

So yeah, the progress on making my own teeny weeny arcade machine has not been going too smoothly. I thought I lucked out when I found a Fire 7 2019 on Woot! for ten bucks (twenty minus a ten dollar "please come back!" discount), but it turns out Jeff Bezos really locked this thing down tight. There are ways to jailbreak it and run a non-annoying operating system, but there are two methods, hardware and software. Software is only for users who actually bought this thing in 2019... if you bought it recently and have it turned on long enough to make it actually do anything, the new hack-proof Amazon operating system will have already been pushed to it, and you'll be stuck with Fire OS. Fire Toolkit mitigates this to some degree, but Fire OS 2019 even manages to block some of ITS features. And that sucks.

Oh, but wait, it gets better. RetroArch will still run on the Kindle Fire, but adjusting settings on this emulator is like wrestling with a rabid bear, and it's quite insistent on ignoring controllers it doesn't like. Take for instance the palm-sized New Wave Street Fighter II arcade stick I chose specifically for this project. Sometimes RetroArch will see it! Sometimes it will rename the buttons without your knowledge or consent! (What the hell kind of button assignment is "plus six?") Sometimes it will forget it's there, forcing you to reconnect and wait until, "oh, hey, there's a controller in me that I didn't notice before. I wonder how that happened?" The ways to fix this problem are strange and arcane, like making a witch's brew, and they rarely ever work. This doubly sucks.

So now I have to figure out a workaround if the project is to continue. Who makes tiny joysticks that use the XInput standard RetroArch actually recognizes? Am I actually going to have to craft my OWN tiny joystick with tiny buttons that fits into the cabinet I made and connect a zero-delay encoder to it? The buttons are no problem- you can find them as small as 16mm on Amazon, but the tiny joysticks are typically designed for wheelchairs and industrial applications, and they're often annoyingly expensive. At that point, I may as well just scrap the whole doomed project and buy an Arcade1UP cabinet instead.

A joystick adapter is also a possibility... I have several lying around, and one of these disguised the New Wave mini-stick as an Xbox 360 controller, which was detectable by both RetroArch and its remedial school cousin Lemuroid. I just couldn't get out of a game after I started it, which is, yanno, gonna be kind of a problem.

It's unfortunate, because the Fire 7 2019 (as wimpy as it is compared to other tablets of the time) is well suited to emulating old arcade games. It's pretty much torn through everything I've thrown at it, including games that were too much for the Namco Museum cabinet or my Playstation Vita to handle. Plus the games (vertical games especially) look great on that screen, strengthening my resolve to finish this project. Oh yes, ten dollar Android tablet, you will become my tiny arcade cabinet. It is your destiny. It's only a matter of time before you bend to my will...



The Kindle Fire 3rd, which I dismissed as a lost cause, is back on its feet. Turns out that it wasn't so smart to enter Fastboot without finishing this tutorial. (Also, removing the -i subcommand from many of the fastboot commands in the tutorial. The commands wouldn't run with that in there.)

So yeah, my Kindle's got TWRP (affectionately referred to as "twerp") on it, along with a working OS. Color me relieved! I really, really do need a better operating system for this thing, though. Maybe Twerp will get me to that point.



The Kindle Fire met an untimely end, the victim of a user-inflicted lobotomy. I thought I could force it to enter fastboot mode without a fastboot cable, and it sure did! Now it's stuck there, forever, unresponsive to user input or connected devices.

So I'm angry with myself for doing something knowingly careless and stupid... but I'm not that upset, because this thing kind of sucked even when it was functional. Low specs (maybe too low for what I was planning...), poorly considered button placement, a total refusal to recognize USB input... there was no way this thing would have been usable in my project without being hacked. It staunchly refused to be hacked, only rooted, and now it refuses to do anything.

I'm annoyed, is the bottom line. It's literally easier to hack a Playstation Vita or a 3DS than the supposed "open source" Android, and that blows goats. I could have left well enough alone if the damn Fire had let me plug in a controller or let me choose my own permanent launcher, but it wouldn't cooperate, so I had to go with the nuclear option. So long, you piece of shit.



Oh, this Kindle Fire 3 has been one huge pain in my ass. Here's just a few things it can't do!

  • Run games at full speed in MAME 2010 (Final Burn works better)
  • Recognize USB controllers
  • Install Launcher Hijack (claims it cannot parse the file)
  • Show an onscreen controller in RetroArch (so you're trapped inside)
  • Be bootloaded or fastbooted
  • Be given a new, less restrictive OS
  • Stay inside one damn launcher for five minutes

No wonder it was five dollars. I'm starting to think I got the short end of that deal.