Changeset 2241
- Timestamp:
- 07/03/07 02:22:27 (1 year ago)
- Files:
-
- plugins/moto-sync/README (modified) (3 diffs)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
plugins/moto-sync/README
r2163 r2241 19 19 * V635 (tested reading only) 20 20 21 Untested, but should be working with extended calendar support (#425): 22 * K1 KRZR 23 * V3xx RAZR 24 21 25 Models known not to work: 22 26 * V600 (shorter contact entries, ticket #504) 23 27 * V3c (doesn't like AT+MODE=0, ticket #505) 24 * K1 KRZR (phone book works, requires extended calendar support, #425)25 * V3xx RAZR (phone book works, requires extended calendar support, #425)26 28 * A780 (doesn't seem to respond to AT commands, except with ERROR) 27 29 … … 33 35 REQUIREMENTS 34 36 35 * OpenSync 0.3 0or later with the python bindings and python-module plugin37 * OpenSync 0.31 or later with the python bindings and python-module plugin 36 38 * Python 2.4 or newer 37 39 * The python-dateutil library (at least version 1.1), … … 117 119 For the calendar, each event has a name, date/time, duration, alarm 118 120 date/time, repeat type, and list of exceptions. The repeat type in 119 particular is very limited, many recurring events can't be represented 120 on the phone. At the moment the plugin detects this and just refuses to 121 write them. A better solution would be to split them up into multiple 122 events, but this will confuse OpenSync when we sync up again. 121 particular is very limited, and unless you have a recent-model phone 122 with extended calendar support, many recurring events can't be 123 represented on the phone. At the moment the plugin detects this and 124 just refuses to write them. A better solution would be to split them up 125 into multiple events, but this will confuse OpenSync when we sync up 126 again. 123 127 124 128
