Browser lost the search function
Hi
I received my Jolla yesterday and at first the browser seemed to work fine. Then it suddenly stopped searching from Google and began saying "That is an invalid URL" when I was searching with words, and did not even mean to go to a direct URL.
So for example when I type "jolla browser search problems" the browser tells me that it is not a valid URL... Duh.
I have double checked that my settings say the search engine is Google. I did not find a place where it would say if the search can be turned on/off.
Has anyone had the same problem or am I just not doing something right?
Thanks in advance for helping!
-Kaisa
I haven't seen this. Did you try 1) rebooting your phone 2) changing the search engine to Bing or Yahoo – does search work with that?
ssahla ( 2014-06-25 11:50:55 +0200 )editCiao Thanks for a quick answer. Yes, I've rebooted the device some four to five times after the first occurrance, and also tried to switch the search engine as you suggested, but with an even worse outcome, really. Now the poor browser does not even find the basic web pages. It says it has found them ("valmis") but the browser view is all white except for the tool row. Perhaps I should reset the device altogether? I just downloaded a bunch of apps so resetting is the last option, though. -K
KaisaQ ( 2014-06-25 12:18:00 +0200 )editOops. I guess you could try uninstall the browser with
ssahla ( 2014-06-25 14:21:56 +0200 )editpkcon remove sailfish-browser
and reinstall it withpkcon install sailfish-browser
(if you have developer mode enabled). (And maybe the same forsailfish-browser-settings
.) But I'm not on very strong ground here, the problem may be somewhere else. Anyway it's worth a try (before performing a factory reset!).Uh-oh. I have no balls to enter the developer mode. :D Thanks anyway! -K
KaisaQ ( 2014-06-25 14:24:56 +0200 )editCould you ssahla elaborate on the 'sailfish-browser-settings'? I think I might have a related problem: it takes ages before the browser actually starts loading and showing pages. It seems it is stuck at some startup phase for like 20-30s and continues after normally. Problem not present when browser already has some page loaded.
Cary Grant ( 2014-06-25 18:56:24 +0200 )edit