Opera Mini for Series 60 UAs
-
rehposolihp last edited by
Hi all,
I have noticed several Opera Mini UAs for the Series 60 platforms having client build versions as high as 25. For example:
Opera/9.80 (Series 60; Opera Mini/25.0.32445/29.3183; U; en) Presto/2.8.119 Version/11.10Could someone please kindly explain, or point me in the right direction for investigating, what Opera Mini versions these build numbers correspond to?
Many thanks.
-
rehposolihp last edited by
Thanks Sagrid. The question I have, however, is that how come for my posted UA, the Opera Mini version is 25? The latest Symbian version is 7.1 I think. The only logic I can come up with is that, assuming this is a valid UA, this number is a build number that corresponds to a particular Opera Mini version number - would you agree this is the case?
-
Deleted User last edited by
It's a fake user-agent, you should search with google if this navigator is online. Except modds only via javascript detection some parts can be overwriten by another mobile UA.
-
rodolfoo1 last edited by
Help Me To Resolve Problem in Opera Mini 4.2 installation?
I have Nokia 7210 supernova. I used opera mini 4.2 on this phone for 3 months with "AirTel GPRS" connection. Now I'm using BPL loop mobile & "BPL WAP" internet connection. but i can't use opera. I'm getting message "failed to connect to internet". so i deleted OM 4.2 & downloaded again.
Even I used previous versions of Opera Mini but getting same Problem.
Please Help me to resolve this Problem. -
Deleted User last edited by
Most likely a WAP access point needs a gateway or ip in some cases which will send at least two extra headers with opera mini and of course wap profile with build-in browser. I think that proxy 10.0.0.10 and port 9401 or 8080 must be set and mark that access point as default for all apps. Contact your operator and you can find any help you can get OTA.