Oh, forgot this was a thing.
Yeah, no framework will most likely kill the buttons until someone with the device figures out how exactly they're neutered.
The main purpose of the no framework mode is to lower memory pressure, which is otherwise fairly high on Kindle because said framework (i.e., the stock UI & backend) eats a humongous amount of RAM (hai, java). Should be mostly irrelevant unless you're reading PDFs, though.
|