You can't install Google Chrome, but you can install Chromium. As other people have posted, Chromium is the code base out of which Google Chrome is compiled. Chromium is an open-source version of this browser. Simply type the following.
$ sudo apt-get install chromium-browser
If you receive any errors running this command, try running
$ sudo ...
As far as I know Google does not (yet) distribute Chrome binaries for Linux/ARM. (The only ARM binaries are for Android and these will not be compatible.)
You might be able to cross-compile Chromium for Linux/armel (I have not tried but I am willing to bet that the RasPi itself is not powerful enough to compile it.)
Also keep in mind that if you were able ...
Change some of the preferences for Midori.
The Midori preferences panel can be found at,
Edit > Preferences
The following preferences should have an effect on the speed of web browsing,
General > Startup > When Midori starts
By default, Midori shows the last open tabs when it starts up. This can mean that you have to wait for the pages ...
There are several programs to take screenshots. I use scrot, a command line utility wich is quite complete. In your case:
sudo apt-get install scrot
scrot -s and click on the midori window. You will get a timestamp-based png in the working directory of your terminal. See man scrot for more options!
Just in case anyone comes by and is looking for an updated answer, Midori now has a command line option --inactivity-reset=SECONDS (or -i for short).
Coupled with the -a option, you can achieve a constantly restarting browser in kiosk mode every x seconds.
midori -a http://www.google.com/ -i 120 -e Fullscreen
Will open http://www.google.com/ in a ...
Assuming that you have Python on your system, there is an alternative to cron. I have created a quick Python 2.7.3 script which will reload Midori every 5 minutes.
#This program reloads midori every 5 minutes
#Redifine the variables below as you see fit
rest_time = 300 #Rest time is set to 300 seconds (5 minutes)
import subprocess as sub #Imports ...
If you are on Debian Squeeze, install Chromium. It is substantially faster:
Upgrading to Debian Wheezy (http://www.raspberrypi.org/archives/1435) also gives a significant speed boost.
First choice for speed is to use Raspbian, a Debian Wheezy distribution built with hardware floating point:
I decided to approach it from a different side, mostly browser-independent.
The browser is started in kiosk mode, pointing at a specific local document:
The support for touch gestures seems to be limited. What I found:
There exists a FireFox (Iceweasel) extension Grab and Drag that adds expected behavior (i.e. scrolling) to FireFox.
Chromium supports touch gestures out of the box.
There is xstroke that allows detection of hand writing to use this as input method. However, this tools seems to be unmaintained ...
How about in the code of your website?
If you put the following in the HEAD section of your page, it will auto-refresh every three seconds:
<meta http-equiv="refresh" content="3" >
Can you be more specific ...
I use the xdotool to simulate an f5 keypress
pi@data-integrity-pi ~/log $ cat ~/bin/refresh_kiosk.sh
DISPLAY=:0 xdotool search --name ci-monitor windowactivate --sync key F5 >> ~/log/tmp.log 2>&1
and then in my crontab I run that script every minute
*/1 * * * * /home/pi/bin/refresh_kiosk.sh
It seems a bit faster after moving my /tmp directory to an external hard drive. It would be nice to know for sure where chromium is caching content. It does seem to create a bunch of stuff under /tmp so this should help. The default /tmp location is on the root file system which is on the SD card. Not a great place for performance. I've also moved my swap ...
Yes i did it! thanks to M Noit :)
sudo apt-get install scrot
then, to take a screenshot after 5 seconds delay, (i got the screen with the terminal in it too! so i need some delays. Also, i can't execute that command through puTTy)
$ sudo scrot -d5
and i get a nice screenshot! :D
I think the problem here might be that you need to tell imagemagik what screen to take an image of, like so:
sleep 5; DISPLAY=":0.0"; export DISPLAY; import -window root filename.png
otherwise it will get confused between different X11 sessions (such as using VNC clients)
Personally I tend to take screen shots from another machine using RDP, that way they ...
The foundation has been working on an accelerated browser which may work better. The goals they've stated are to improve rendering speed which may help.
Unfortunately the limit you're hitting with display probably isn't so much a browser issue as a more fundamental issue with the frame buffer being slow to update. There's not much you can do about that ...
I use xdotool to solve the problem.
I created a bash loop every 60 seconds. This script is launched with autostart lxsession
WID=`xdotool search --name "TITLE OF PAGE IN MIDORI" | head-1`
xdotool windowfocus --sync $WID
xdotool click 1
RPi Jessie not working ?
I think you want to use the autostart here:
...at least with the default Raspbian setup of LXDE.
At a guess you may be pressing the F1 key accidentally (by something pressing against, or using a faulty keyboard, etc) causing it to open the FAQ midori:faq
You should be able to disable this shortcut by editing this line in ~/.config/midori/accels:
; (gtk_accel_path "<Actions>/Browser/HelpFAQ" "F1")
so it is like:
You can install Chromium the open source parts of Google's Chrome but it can be a bit heavy for the Pi, slowing everything else down.
sudo apt-get install chromium
Your best be is to get the ...
I have no idea why Midori has as much trouble as it does, but I managed to grab the url for you:
Midori is under heavy development, and it looks like this is just a bug related to improper handling of memory. I would compile the latest git daily with a cron script to make sure you get a version that doesn't contain that bug as soon as it comes out.
Create a script to update Midori daily. Add these lines to it:
sudo git clone git://git.xfce.org/...
First of all, "The only player that will utilize the GPU acceleration is the omxplayer. It should be installed by default, but it is also so basic that it is CLI only." - Debian Forums
This means that your only option is to use omxplayer. I am not sure if it is able to play webm files, so that means that we should convert it. I have found that .mov files ...
Where are you running that script from? It looks to me like you do this from within the X GUI. In that case there is probably already a window manager running. Even if there is not and/or this is an xinit script, you should not background the wm and go from there.
The proper way to do this is to create a separate script with your while true loop in it ...