ScientiaMobile

Hi SM, I wanted to sniff out Opera Mobile/Mini and need to check i have got it right re the way WURFL is handling Opera on Android.

What I get from UA: Opera/9.80+(Android+2.2.1;+Linux;+Opera+Mobi/ADR-1205181138;+U;+en)+Presto/2.10.254+Version/12.00

brand_name: Generic
model_name: Android
mobile_browser: Android Webkit
device_os: Android

If I use Nokia UA: Opera/9.80 ($OS; Opera Mobi/$BUILD_NUMBER; U; $LANGUAGE) Presto/$PRESTO_VERSION Version/$VERSION

brand_name: Opera
model_name: Opera for Series 60
mobile_browser: Opera
device_os: Symbian OS

So I can get the cap is Opera from Nokia UA but not from Android. Could I get some info on handling Opera on Android? I only have one actual device that I tested on so be good to hear other results also! Cheers _P

Hi,

Unfortunately, the user agents you've posted are malformed, in the first example (the Opera Mobi on Android UA), there are + characters where there should be spaces. This is indicative of a user agent extracted from a Microsoft IIS server log file. If you replace the + signs with spaces, you get the following:
Once the UA is fixed, the device is properly detected as Opera Mobi on Android 2.2, which is as detailed as we can get without the actual device information.

In the second example, many of the important versions from the UA have been replaced with placeholders - this looks like a user agent template of some sort from Nokia. We were still able to get a reasonable guess in this case, however. A real world user agent in this format looks more like this:
So, to answer your question, Opera on Android should be detected properly.

Thanks that got me on the right track (and learnt about UA strings copied off ISS), once I had that sorted I could see cap mobile_browser requires is; Opera, Opera Mini, Opera Mobi that was giving me some false positives which threw me, all good now though, thanks _P