Thanks for your question. The reason you’re encountering this is that we’ve never seen this specific User-Agent format before from across our millions of global deployments. In situations like this an attempt to perform a guess match will occur. This can be evidenced on our User-Agent tester: https://51degrees.com/resources/use..._MEXT_IAB+
The two key elements here are the ‘difference’ and ‘method’. With a known User-Agent the method will return ‘exact’ and in other cases it may return ‘nearest’ or ‘closest’. The difference value indicates the confidence indicator, the lower the value the more confidence our system has in the detection result. In this case the returned method is closest and the difference is 76 which indicates a low confidence in the result. These results can help customers to identify false positives. More information on the methods can be found here: https://51degrees.com/support/docum...on/pattern
To resolve your problem we will manually insert the User-Agent you have provided into our database so it will instead resolve as an exact match for the Xiaomi Redmi Note 5 Pro. This change should be available in next Monday’s Enterprise data file.
We encourage all customers to enable usage sharing where possible, this will give us visibility of uncommon User-Agents so that we can ensure these are processed efficiently. If this isn’t possible for your project you can send User-Agents that you believe may not be resolving as expected directly to us and we can help that way. How to enable usage sharing in Java can be found below and you can find instructions for other API’s in the relevant sections in our website documentation. https://51degrees.com/Developers/Do...ge-Sharing
I hope this helps, if you have any further questions please do not hesitate to ask.