I've got a sticky situation. I'm developing a kiosk-style tablet application on JellyBean, and we're stuck with JellyBean.
We don't install a standard launcher on our Android tablets, and instead supply our own Home Screen/Launcher app, so that our application starts on system startup.
We were using a WebView for our GUI app. The WebView that comes with JellyBean is buggy and deficient in many ways, so our app doesn't work correctly in the WebView.
However, Chrome runs our app perfectly, so we want to switch to using Chrome, which we would launch from our own Home Screen application on startup.
We need to start it in full-screen mode, just like Launchers do when they launch any app/URL via a link that was placed on the Desktop.
I can't for the life of me find out how launchers pull this off.
I've tried adding --app="...xxx..." and/or --start-fullscreen to the /data/local/chrome-command-line file, but all to no avail. The additions options show up on the chrome://version screen in Chrome, but they have no effect.
Does anyone have any clue how Launchers manage to launch Chrome in full-screen mode?
These tablets are all rooted tablets, completely under our own control, so no solution is out of bounds.
Thanks for any help!
What I have tried:
I've tried adding --app="xxx", and/or --start-fullscreen to the /data/local/chrome-command-line file, but all to no avail. The additions options show up on the "chrome://version" screen in Chrome, but they have no effect.
The standard client-side JavaScript FullScreen API works fine, but requires that Chrome start out windowed, and then can be brought to full-screen via user interaction. Displaying a browser with address bar, tab bar, menu, etc. is not acceptable, so I'm looking for a better solution.
As noted, Launchers do this with desktop links with no problem. After countless Web searches, though, I can find no information about how they achieve whatever they do to make Chrome start in full-screen mode.
Submit an article or tip