Chromium
From Pandora Wiki
Download
Chromium for the Pandora is available in the Pandora Repository as Chromium-Dev.
Hints
How to export your custom Chromium search engines from your Computer to your Pandora
I followed this hint, and below you find the adapted and tested instructions for the Pandora, tested with Chromium-Dev 13.0.750.1
1) On your computer:
cd path/to/where/you/want/the/database-export-file/ sqlite3 path/to/chromium/Default/Web\ Data .output keywords_export.sql .dump keywords .quit
2) Connect the SD with Chrome's appdata to your computer one of these two ways:
- Launching SD-Mass Storage on your Pandora and then connecting your Pandora to your computer via an USB cable
- Take the SD card out of the Pandora and attach it to your computer
3) On your computer:
- On Unix systems
sqlite3 path/to/sd/pandora/appdata/chromium-dev/config/chromium/Default/Web\ Data "DROP TABLE keywords" sqlite3 path/to/sd/pandora/appdata/chromium-dev/config/chromium/Default/Web\ Data < keywords_export.sql
- On Windows systems
sqlite3 -init keywords_export.sql path/to/sd/pandora/appdata/chromium-dev/config/chromium/Default/Web\ Data .quit
4) On your Pandora:
- Launch Chromium
- For some reason, right at the beginning, the search engine behaves buggy! If you want to fix it continue with the next step. If you are curious, these are the bugs:
- If you have 2 or more engine keywords starting with the same beginning letter, you can only enter the shortest one, because it snaps in without waiting for TAB or SPACE, thus you cannot continue typing the keyword, Chromium switches right into the search term entry mode.
- You cannot correct the keyword by BACKSPACE, the only way to get out of this mode is by pressing ESCAPE.
- Go to Menu ( symbol) > Settings > Manage search engines
- Do something, i.e. change a keyword to something else and back again or change the default search engine.
- Close the settings.
- Now the search engine works as expected: keyword, TAB or SPACE, search term(s), ENTER. It seems that opening & closing the search engine settings somehow repairs that bug (supposedly in the backend or data structure).
