The My Opera forums have been replaced with forums.opera.com. Please head over there to discuss Opera's products and features
See the new ForumsYou need to be logged in to post in the forums. If you do not have an account, please sign up first.
Turbo fails over 4G but works flawlessly over WiFi? Ver:11.5.3
First off want to thank the designers, programmers, and community for putting out such an amazing browser. Used to use it on Windows Mobile a few years back and now that I've joined the cult of Android I'm glad to have it back.Anyways, thought I would ask if there is a known bug with Turbo not working over 4G or if certain networks are blocking the servers. It works amazingly well over WiFi but the moment I am using 4G it fails to connect to the servers and throws up all sorts of errors. When it does connect to a website it shows that no compression happened.
I'm on Bell Mobility in Canada if it matters. Meanwhile I've tested Mini and can confirm that it works.
Any status on a fix, comment, or pointing in the right direction to a possible fix would be greatly appreciated.
Many Thanks
I can confirm that I also have problem with Opera Mobile with Turbo on while on Bell Mobility network. Error message says something about failure to resolve hostname. Example:
Error: Requested content 'mobile10-turbo.opera-mini.net/news.google.com' cannot be resolved.
If I hit the refresh button, the page loads but does not appear to have been compressed by the Turbo engine (as shown by the data usage report).
As others have pointed out, Turbo over wifi works, and Opera Mini (with built-in Turbo) works.
Error: Requested content 'mobile10-turbo.opera-mini.net/news.google.com' cannot be resolved.
If I hit the refresh button, the page loads but does not appear to have been compressed by the Turbo engine (as shown by the data usage report).
As others have pointed out, Turbo over wifi works, and Opera Mini (with built-in Turbo) works.
I've just change of mobile operator (from Virgin mobile to Free mobile) and now the turbo works over 3G.
So I can confirm that the problem don't rely on Opera, but on the operator that block some traffic.
But as opera mini works, i think that is possible to Opera to make a workaround.
Maybe the Opera Mobile connect to turbo server on an another port than 80, that is blocked by operator.
You have to found a way to change this port. Maybe ont the turbosettings.xml but i'm pretty shure that i've tried with this one http://code.google.com/p/studypy/source/browse/trunk/operaProfiles/locale/zh-cn/turbosettings.xml?spec=svn150&r=150 And it doesn't work.
An Opera staff is required here i think. But everybody seems to not care.
So I can confirm that the problem don't rely on Opera, but on the operator that block some traffic.
But as opera mini works, i think that is possible to Opera to make a workaround.
Maybe the Opera Mobile connect to turbo server on an another port than 80, that is blocked by operator.
You have to found a way to change this port. Maybe ont the turbosettings.xml but i'm pretty shure that i've tried with this one http://code.google.com/p/studypy/source/browse/trunk/operaProfiles/locale/zh-cn/turbosettings.xml?spec=svn150&r=150 And it doesn't work.
An Opera staff is required here i think. But everybody seems to not care.
Forums » Opera for mobiles/devices » Opera Mobile for Android