You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 28, 2023. It is now read-only.
Looks like an UAS database issue back in 2015.
With current UAS database (version: 20190121-02) these are now all correctly being parsed as smart phone.
@HaraldWalker how does this help users of UADetector?
The project is based on a now several years old version of the UAS database, so however the current database fixes issues like this one is irrelevant; that is, unless UAS has changed their license and current UAS database is available to OSS projects (a quick glance at their site indicates that nothing has changed).
@godenji using this library with the last available open source 2014 UAS database that is included has no real business value as the error rate is increasing over time. We've added support for the commercial UAS database from Udger to this library in 2015 and I am probably not the only one that still uses uadetector in combination with a subscription for the UAS database.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Sample User-agents:
Dalvik/2.1.0 (Linux; U; Android 5.0; Lenovo A7000-a Build/LRX21M)
Dalvik/1.6.0 (Linux; U; Android 4.4.2; Micromax A310 Build/KOT49H)
Dalvik/1.6.0 (Linux; U; Android 4.3; SM-G7102 Build/JLS36C)
Dalvik/1.6.0 (Linux; U; Android 4.2.2; GT-S7582 Build/JDQ39) -> galaxy s duos 2
Mozilla/5.0 (Linux; U; Android 4.0; en-us; GT-I9300 Build/IMM76D) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Mobile Safari/534.30
The text was updated successfully, but these errors were encountered: