New Webkit browser broken connection selection algo
Please Login to Remove!
The new WebKit browser in OS6 is a welcome enhancement over the rendering done by the legacy browser. However, RIM has removed the ability for users to specify the connection method. Instead, the WebKit browser is supposed to be "smart" about determining the best connection method to use. Except it's not very smart, and this is causing me a lot of grief.
When connected via WiFi, the new browser wants to use WiFi and only WiFi. At work, the WiFi network only allows the RCP session to RIM. All other traffic to the Internet is blocked. Thus, using the browser while connected to the WiFi network at work results in the web browser being 100% useless since the firewall blocks all traffic. This was not a problem with the prior web browser, as I simply set it to default to BIS for connectivity. I can't just disable WiFi at work, either. As I need WiFi for the phone to get email while I am in the building interior, where cellular reception is essentially non-existent.
Is anyone aware of any secret tricks to force the new browser to use BIS (or BES, but would prefer BIS) even when WiFi is up?
Thanks
|