This capability was just recently introduced and should be included in the next release. We'll reply with more details once we have them.

We've added this device and a handful of other variants.

This is detected as a web browser on the DB API (http://bit.ly/nqkym7) which API are you using?

This user agent is also being matched properly: http://bit.ly/r3KSFr

There must be something going on under the hood that is causing these detection problems.

No problem! Please do let us know what you think of it. We are working on the Getting Started and class documentation, but in the meantime you are free to ask your questions here.

Are you able to figure out which API they have embedded in the product? As you can see from the Official DB API, both of these user agents are matching properly:

http://bit.ly/nOdsW4
http://bit.ly/pIumMq

As for your patch file, the format looks correct, yes.

The example code for the WURFL Cloud Service is included in the WURFL Cloud Client packages. To get access to these, you need to visit www.scientiamobile.com/cloud and create a WURFL Cloud API Key, which will also grant you a beta license for the WURFL Cloud. Once you have a key you can go to your "...

This device has been added.

This device has been added.

This device has been added.

This does not appear to be a valid user agent. The "I" in iPad is capitalized, which is not consistent with traffic from these devices.

This device has been added.

Usually, when moving the DB API (Tera-WURFL) from one host to another, it is best to completely delete the database tables, this causes the API to recreated them and the stored procedures using new MySQL user's credentials. This is important because only the user that defined the procedures can modi...

Can you go to the admin/install.php page in your browser and see if there are any errors? Also, what do you see when you try to updated the database?

In order to match the user agent you posted, you would need to either add it to your patch file as is, or in a simplified form like this:

This is not the expected behavior. I am looking into it.

Please note that our priority is accurate detection of mobile devices. More accurate detection of desktop browsers is on our roadmap, but at this point we are not focusing much attention on them.

If you clear the cached devices before updating the WURFL data, even fairly slow servers will take much less than 30 seconds to reload. Our production servers usually take about 7 seconds to load the WURFL with no cached devices. Your best bet is to clear the device cache before updating the WURFL.

No, unfortunately we are not planning to support PHP4.

We don't support installations on PHP4, but I don't see any reason why it wouldn't work to put the RemoteClient on PHP4 if you remove every instance of "public", "private" and "protected".