On the whole, I'm delighted with the update and have had none of the youtube/gmail issues reported here. It's great that they finally have Flash working in a very passable way.
I have a different problem, though. A banking site I use employs java and JS to execute complex security routines. Thesite worked perfectly under the old OS, but now refuses to load, even with the fix posted here. However, it loads fine with Minimo.
I had issues logging into Basecamp, but was able to trick the site into letting me in by temporarily turning of JavaScript in the browser settings and having the site remember me.
Obviously, the Opera browser JS and AJAX issues are as frustrating as they are well-known (frankly, I find it ridiculous that I have to use a hack-port browser to supplement an "internet tablet's" on-board browser - C'MON NOKIA!!! Fix it already - these sites work on the Opera browser on my kid's Wii, FCS!).
But, is anyone else experiencing issues with JS-intensive sites that stopped functioning post-update? If so, can you suggest a fix?
Opera is not a Nokia product, so they probably have little influence on its development.
There are 2 issues with Opera:
1. Opera wants more correctly coded web pages. While Firefox and IE are more tolerant to bad website design. Actually this is a good thing, as many websites are designed so badly because they still render under IE or Firefox.
2. Opera's javascript implementation needs to be improved, this is the main issue with opera.
Opera has been chosen as it is very flexible for small screens and it renders most sites better than minimo/firefox. There is always a compromise being made, and Safari is not on sale up to now ;-)
Opera has been chosen as it is very flexible for small screens and it renders most sites better than minimo/firefox. There is always a compromise being made, and Safari is not on sale up to now ;-)
I did wonder why one would choose opera over a marketleader for an "internet tablet", thanks.
when trying to get to some websites with HTTPS like Garage.Maemo.com or trying to log into my Yahoo email address, I get an "invalid certificate" from server message. after prolonged use, occasionally I can't load a new web page, it just says web page loading but Opera never loads.
I switch off the device and restart it and everything works fine afterwards.
a little annoying because with the previous firmware, i thought the browsing was rock solid.
Opera wants more correctly coded web pages. While Firefox and IE are more tolerant to bad website design. Actually this is a good thing, as many websites are designed so badly because they still render under IE or Firefox.
I absolutely agree that stricter standards enforcement is a good thing. But with prevailing assertions that the web is the next OS, and browsers being the window to the world of AJAX & XHTML, having a browser that falls so pathetically short of those standards shows lack of foresight. Especially since the N800 is not yet ready for general consumers; it's more for gearheads and powerusers like us who are willing and able to overcome/overlook a lot of technical obstacles for the promise of true, in-your-palm internet capability.
Don't get me wrong; I absolutely love my n800. It's just so tantalisingly close to being perfect. Perhaps now that Flash is finally top notch, Opera's Javascript deficiencies are next in line!
Just open xterm and paste this command at the prompt (all on one line)
Code:
gconftool-2 --set --type int '/system/osso/connectivity/IAP/wlan_sleep_timeout' '200'
Replace the value '200' with something bigger that works for you eg. '400' or '500'. The old 3.2007.10-7 default was '1000' (or 1000ms, 1 second), the 4.2007.26-8 default is probably somewhere around '200'.
Smaller values should result in improved battery lifetime as the WiFi radio will timeout (switch off) more quickly, but have it too low and you will experience communication problems between your N800 and access point.
Thanks Milhouse for this tip.
Just to note, for me to make it work I had to go first in offline mode.
In all other cases it was simply not applying/keeping the change.
Please don't forget to update the bug... the gconf2tool hack should just be a temporary solution, but without any further comments against the bug you could all be stuck having to apply this hack in all future firmware releases.
Those affected by this problem need to vote and add comments (detailing router make/model/firmware) to the bug - it's for your own benefit.
