Quote:
Originally Posted by keiichi626
Anybody seen this problem yet? I have a softkey-keyboard that loads up once I run haret, and is in the bootloader screeen, and stays there after android is fully booted. It's an overlay, meaning I can still drag down on the menu behind it, or tap on things that are under it.
Was working prior to adding overclock and 3d enable lines to startup.txt. Deleting data.img did not solve.
|
What are the different cmdline switches I can pass in the Startup.txt?
Some of these options are for debuggind as well as things not fully implemented yet. But it was asked for so I thought I would throw it in the FAQ for ya. But keep in mind these aren't fixes by any means just different ways to configure and test things. And some of them not working yet. Any of these switches can be anywhere in your cmdline as long as they aren't the last switch. The
"physkeyboard=" switch has to be your last switch.
Turn off on-screen debug keyboard - msmvkeyb_toggle=off