Press F11 to exit the full screen mode, and Ctrl + L to focus the location bar. Navigate away! Once done, press F11 again to re-enter full screen mode.
Chromium is configured to remember the URL where you left off (and all logins, etc), so this might be all the configuration you need to do!
-You can get to a virtual terminal by pressing Ctrl + Alt + F2, and logging in with username pi and password raspberry. Use Ctrl + Alt + F1 to switch back to Chromium.
Use sudo raspi-config in the terminal to do things like:
You can access the raspi-config utility by pressing Ctrl + Alt + F2. With it, you can do things like:
Pressing Ctrl + Alt + F1 takes you back to Chromium.
There's a few commonly useful snippets already on the crontab, such as:
Ctrl + R every hour. Very crude. Very effective.Ctrl + Tab. Note that if you use both at the same time, you can combine them, to send the reload command just before sending the tab cycle command. This causes the pages to reload while they're in the background, so the user never sees it happening.Use crontab -e to check these out, enable the ones you want, or customize them to your heart's content.
Press Ctrl + Alt + F3 to get to a virtual terminal, use crontab -e to check these out, enable the ones you want, or customize them to your heart's content.
Again, pressing Ctrl + Alt + F1 takes you back to Chromium.
Because you're running a fully-featured Chromium, you can customize it further by installing browser extensions. For instance, Tampermonkey can be useful for injecting custom JS or CSS to a page you're displaying.
+Because you're running a fully-featured Chromium, you can customize it further by installing browser extensions. For example:
+<iframe> a site that doesn't want to be framed.Finally, further tweaks can be made by changing the Chromium command line switches in ~/.xsession. For example:
--unsafely-treat-insecure-origin-as-secure=http://shady.example.com,http://another.example.com --user-data-dir=/home/pi/.config/chromiumAdding these options will allow you to mix secure (i.e. HTTPS) origins with insecure ones (you need to specifically white-list them). Sometimes you need stuff like this to pull together all the bits and pieces of your dashboard from different origins. We're not saying you should. But you can.
+If you need to login to a shell, the default username and password are pi and raspberry, as is tradition for Raspberry Pi. The pi user also has sudo access.
If the display auto-detection fails and chooses a funky default resolution for you, there's a few things you can do to try and fix that.
The image that's displayed while the kiosk is starting can be changed by just replacing ~/background.png.
To change the default chilipie-kiosk boot graphics to a nice doge, for example, try wget -O background.png https://bit.ly/2w1P4Il.
To change the default chilipie-kiosk boot graphics to a nice doge, for example, try wget -O background.png bit.ly/2w1P4Il.
By default, the browser window is hidden for a few seconds after boot, to give the page time to load. You can increase (or decrease) this delay in ~/.xsession.