[Tickets #14655] Re: OS version detection when using android/gmail app doesn't work

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: https://bugs.horde.org/ticket/14655
------------------------------------------------------------------------------
  Ticket             | 14655
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | OS version detection when using android/gmail app
                     | doesn't work
  Queue              | Synchronization
  Version            | FRAMEWORK_5_2
  Type               | Bug
-State              | Feedback
+State              | Resolved
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2017-06-11 15:22) wrote:

Thanks for all that data.

It looks like this is either OS and/or device vendor dependent. My  
Note 5 is on Android 7.0 and also sends the OS field.

mysql> select distinct device_agent, device_properties like
     -> '%"Settings:OS%' AS hasOS from horde_activesync_device where
     -> device_type like 'Android' order by device_agent;

+-----------------------------------------------------+----------+
| device_agent                                           | hasOS |
+-----------------------------------------------------+----------+
| Android-Mail/7.5.21.158049789.release |     1      |
| Nine-nobleltevzw/LMY47X                      |     1      |
+-----------------------------------------------------+----------+

Anyway, I've added a check that doesn't rely on the OS version now.  
The downside is that this will only work for newly added device  
entries since the multiplex value is persisted to storage once  
determined.

You can use the activesync_device_modify hook to override existing  
device entries. There is example code in the  
horde/config/hooks.php.dist file. Of course, if you are feeling  
adventurous, you could also just manually change the multiplex value  
to 0 in the device_properties hash directly in the RDBMS.