arouel
Android tablets and phones are incorrectly recognized
Mozilla/5.0 (Linux; Android 4.0.3; GT-P5100 Build/IML74K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/30.0.1599.92 Safari/537.36
Galaxy S3 Mozilla/5.0 (Linux; Android 4.1.2; GT-I9300 Build/JZO54K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.64 Mobile Safari/537.36
Galaxy S4 Mozilla/5.0 (Linux; Android 4.2.2; GT-I9500 Build/JDQ39) AppleWebKit/537.22 (KHTML, like Gecko) Chrome/25.0.1364.169 Mobile Safari/537.22
Galaxy S4 Native: Mozilla/5.0 (Linux; Android 4.2.2; en-gb; SAMSUNG GT-I9500 Build/JDQ39) AppleWebKit/535.19 (KHTML, like Gecko) Version/1.0 Chrome/18.0.1025.308 Mobile Safari/535.19
Nexus 10 Mozilla/5.0 (Linux; Android 4.3; Nexus 10 Build/JWR66V) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.94 Safari/537.36
NoteII Mozilla/5.0 (Linux; Android 4.1.2; GT-N7100 Build/JZO54K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/30.0.1599.82 Mobile Safari/537.36
Of all these UA strings above only Galaxy S4 Native was recognized as MOBILE_BROWSER, the rest was classified as BROWSER.
Could you please fix this?
Thanks for your feedback. This is not an issue in UADetector, but in database (a.k.a. UAS file). You can insert your user agent strings at http://user-agent-string.info and you get the same information. Please fill a request additionally there. The database maintainer verifies your provided user agent strings and adds it as soon as possible.
It looks like http://user-agent-string.info now recognizes the android browser but uadetector does not. The test input is "Mozilla/5.0 (Linux; U; Android 4.0.3; ko-kr; LG-L160L Build/IML74K) AppleWebkit/534.30 (KHTML, like Gecko) Version/4.0 Mobile Safari/534.30". Grepping through the uadetector library I see that in UserAgentFamily there is an entry for "Android Webkit" but not "Android Browser". Is that related to this behavior?
I would say it is related. We need to extend the entry in UserAgentFamily. Feel free to do a PR.
@mallat I mentioned that some of these entries above should be classified as a different device and family. Can you verify this. Should we improve the UAS database in this area?