Kindle Fire HDX 7"
Stock ROM Version 188.8.131.52
Rooted with Towelroot
OTA Updates Disabled
I was just going to flash a new ROM, but I was not able to boot into any ROM Manager. If anyone could point me in the direction of a good ROM and ROM Manager that works with the KFHDX7, I'd be highly appreciative. Now, I digress.
Glitchy and/or Sucky
Tested the following launchers:
- Otter(aka stock "Home"): Obviously, this one sucks the proverbial balls. No customizability, no widgets. My whole motivation for rooting.
- Next Launcher 3D 3.10: Looked pretty, but unfortunately too glitchy.
- GO Launcher HD: Stable thus far. Somewhat busy. GO Widgets work, if you have Google Play.
- KitKat Launcher 1.14: Stable, minimalist design. Surprisingly, did use slightly more RAM than relatively cluttered GO Launcher(without Widgets activated)
- Holo Launcher HD 2.0.4: Worked great until I rebooted. Sent my device into epileptic crisis.
- Galaxy/Touchwiz Beta v5: Always in landscape mode, would not react to moving device to portrait mode.
- GEL/Google Now: Widget support! However, I did need the Xposed Framework and GEL Settings app to make things work properly.
Unfortunately, NONE of the launchers had native widget support. They would simply crash when trying to add a launcher to the homescreen. I'm guessing this has something to do with the KFHDX OS itself. The exception to this was GO Launcher, which had working GO Widgets. To be honest, I wasn't overly impressed by the GO Widgets.
Also, another common theme was issues with the screen orientation.Several launchers had problems with device orientation. When in landscape mode with Next, you could not move icons around. The screen would invert, and you would 'drop' the icon. When in portrait mode, the persistent launcher frame with the Home/Back/Apps/Search button would cause the Next launcher bar to overlap some of the icons on the screen, thereby rendering them inaccessible. The same thing happened with KitKat as far as being unable to move icons around when in landscape mode. However, there was no issue with overlapping elements, so this was less of a deal-breaker.