#16 Android UA detection needs improvement

closed
nobody
None
5
2011-10-22
2010-11-10
Anonymous
No

The current Android UA detection include the 'Android version' in the UA matching (RISMatcher). This makes the matcher rather hit other phones with the supplied user-agents version, rather than primarily focusing first on the the device name. This is becoming a big problem now that a lot of phones are getting upgraded android version. An example:
The user agent:
"Mozilla/5.0 (Linux; U; Android 2.2; de-de; HTC Desire 2.10.161.2 Build/FRF91) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Mobile Safari/533.1"
, is detected as "Verizon, Droid2" ! Stepping through the code you see that it occurs because the Droid2 is the first UA in the list with version 2.2.

I suggest the there should be multiple stages in verifying the phones, where you in the first step cut off the Android Version info from the UA, and just tru to identify the phone, and then in step 2 try to detect the version.
Unless something like this is introduced, I think it will be very hard to detect updated Android devices, or the Wurfl-file needs to be released very often.

Discussion

  • Steve Kamerman
    Steve Kamerman
    2011-10-22

    Thank you for the suggestion! Android matching has been improved since this ticket, and another major improvement will be pushed to all APIs very soon.

     
  • Steve Kamerman
    Steve Kamerman
    2011-10-22

    • status: open --> closed