Smartphone detection issues

I have this HTTP request, I expected this, but WURFL is returning that. Please provide enough data to reproduce the problem.

Smartphone detection issues

Postby Edgecast-Sanh » Sat Aug 12, 2017 12:18 am

Hello,

We are Edgecast reaching out for guidance regarding smartphone detection. We seem to have some smartphone detection issues with user agent below #1 using latest wurfl database. It appears for Android 7.0, when SAMSUNG is present, it returns a false smartphone value.

<version>
<ver>data.scientiamobile.com - 2017-08-06 00:30:27</ver>
<last_updated>2017-08-06 00:30:27 -0400</last_updated>
<official_url>http://www.scientiamobile.com</official_url>


1.
UA: Mozilla/5.0 (Linux; Android 7.0; SAMSUNG SM-G920V Build/MMB29K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.98 Mobile Safari/537.36
ID: generic_android_ver2, root: no
matched UA: DO_NOT_MATCH_GENERIC_ANDROID_2_0
root ID: generic_android_ver2
Found 21 virtual capabilities:
is_smartphone: false

Example of Android 7.0 that returns true.
2.
UA: Mozilla/5.0 (Linux; Android 7.0; SM-G920V Build/MMB29K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.98 Mobile Safari/537.36
ID: samsung_sm_g920_ver1_suban70v, root: no
matched UA: Mozilla/5.0 (Linux; Android 7.0; SM-G920V Build/NRD90M; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/55.0.2883.91 Mobile Safari/537.36
root ID: samsung_sm_g920_ver1_suban70v
Found 21 virtual capabilities:
is_smartphone: true

Android 6.0.1 with SAMSUNG SM-G920V Build/MMB29K) returns true
3.
UA: Mozilla/5.0 (Linux; Android 6.0.1; SAMSUNG SM-G920V Build/MMB29K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.98 Mobile Safari/537.36
ID: samsung_sm_g920_ver1_suban60v, root: no
matched UA: Mozilla/5.0 (Linux; Android 6.0; SM-G920V Build/MRA58K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.94 Mobile Safari/537.36
Found 21 virtual capabilities:
is_smartphone: true



Here are more examples of user-agents that detect smartphone as false:

Mozilla/5.0 (Linux; Android 7.1.2; Z2 Plus Build/NJH47B) AppleWebKit/537.36
(KHTML, like Gecko) Chrome/59.0.3071.125 Mobile Safari/537.36

Mozilla/5.0 (Linux; Android 7.0) AppleWebKit/537.36 (KHTML, like Gecko)
Chrome/59.0.3071.125 Mobile Safari/537.36

Mozilla/5.0 (Linux; Android 7.1.2; Moto G4 Plus Build/N2G47O; wv)
AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/58.0.3029.83
Mobile Safari/537.36

Mozilla/5.0 (Linux; Android 7.1.2; Swift 2 Plus Build/N2G47H)
AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Mobile
Safari/537.36

Mozilla/5.0 (Linux; Android 7.0; SAMSUNG SM-N920S Build/NRD90M)
AppleWebKit/537.36 (KHTML, like Gecko) SamsungBrowser/5.4
Chrome/51.0.2704.106 Mobile Safari/537.36

Mozilla/5.0 (Linux; Android 7.1.2; ONE E1001 Build/NJH47D)
AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.125 Mobile
Safari/537.36
Edgecast-Sanh
 
Posts: 2
Joined: Sat Aug 12, 2017 12:04 am

Re: Smartphone detection issues

Postby amark » Sat Aug 12, 2017 9:02 am

Hi Edgecast Sanh,

With regards to your first issue
It appears for Android 7.0, when SAMSUNG is present, it returns a false smartphone value.
This is most likely an issue of your WURFL API being up to date. In addition to updating your WURFL database you should also make sure you are always running the latest version of our API. I would like to inform you that version 1.9 of our API released on June 29th. It is likely that if you haven't updated since then you are currently running an out of date API.


With regards to your second issue I will make sure the following user agents are included in WURFL with the exception of
Code: Select all
Mozilla/5.0 (Linux; Android 7.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.125 Mobile Safari/537.36
since there is no device information included in the user-agent. However updating your API will also make all the following user-agents report is_smartphone as true.

Let me know if you have any other questions and I will be happy to help

Best,
Amar
amark
 
Posts: 18
Joined: Mon May 30, 2016 4:59 am

Re: Smartphone detection issues

Postby Edgecast-Sanh » Tue Aug 15, 2017 5:41 pm

Hello,

Sounds good, thanks for the follow up!
Edgecast-Sanh
 
Posts: 2
Joined: Sat Aug 12, 2017 12:04 am


Return to Device Detection Issues

Who is online

Users browsing this forum: No registered users and 1 guest