Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

10.4: Create standalone phone plug-ins for iSync Apps
The recent 10.4.1 update trashed the hack to the MetaClasses.plist file that added my Motorola phone to iSync, and I suspect this will always be the case with future updates. So I wondered if it was possible to create the Metaclasses.plist files outside of the iSync application. After all, the Metaclasses.plist file is inside the PhoneModels.phoneplugin inside the Plugins folder of the ApplePhoneConduit.syncdevice inside the Plugins folder of iSync (whew).

And the answer is that it is possible to create .phoneplugin plug-ins inside /Library/PhonePlugins, using the same layout found inside iSync. The plugin, let's say it's called MyPlugin.phoneplugin, has to live in /Library/PhonePlugins, and needs to hold the following files and folder structure:

/Library
  PhonePlugins/
    MyPlugin.phoneplugin/
      Contents/
        Info.plist
        Resources/
          MetaClasses.plist -- containing the stuff to support my phone
          XXX.tiff -- my phone's icon
The question is: what will happen once Apple adds support for my phone? Won't there be any conflict?

[robg adds: I haven't tested this one, and this hint assumes some level of knowledge of modifying plist files, as well as the structure of the Info.plist file, etc.]
    •    
  • Currently 1.00 / 5
  • 1
  • 2
  • 3
  • 4
  • 5
  (2 votes cast)
 
[12,368 views]  

10.4: Create standalone phone plug-ins for iSync | 7 comments | Create New Account
Click here to return to the '10.4: Create standalone phone plug-ins for iSync' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.4: Create standalone phone plug-ins for iSync
Authored by: joshturse on Jun 02, '05 04:58:52PM

Maybe you could share the plugin you created with those of us that are less talented?



[ Reply to This | # ]
10.4: Create standalone phone plug-ins for iSync
Authored by: kenm75232 on Jun 02, '05 06:42:24PM

I would like to know which Motorola phone you were working with as I can use iSync with my v620 now. However, that being said, it only syncs phone numbers and email addresses not street addresses. Would there be a way to get the other information loaded?

Thanks!!



[ Reply to This | # ]
10.4: Create standalone phone plug-ins for iSync
Authored by: egilDOTnet on Jun 03, '05 05:23:17AM
Here is a sample bundle for the Nokia 9300 phone.

Simply download it from here, then move the Nokia9300.phoneplugin folder it creates from your download dir into your ~/Library/PhonePlugins folder (if that folder does not exist already, create it).

Have fun!

[ Reply to This | # ]
10.4: Create standalone phone plug-ins for iSync
Authored by: syntetic on Oct 04, '06 05:01:45PM

or do this

For iSync v 2.3.

Just go to your apps folder, Ctrl-click iSync.app, choose "Show package content"

Then go Contents->PlugIns->ApplePhoneConduit.syncdevice->Contents->PlugIns->Nokia-9300i.phoneplugin->Contents->Resources

Open file MetaClasses.plist with Property List Editor

Change string
Root->com.nokia.9300i->Identification->com.apple.cgmi+cgmm
From Nokia+Nokia 9300i to Nokia+Nokia 9300
(Remove "i")

That's all

taken from the mac site



[ Reply to This | # ]
10.4: Create standalone phone plug-ins for iSync
Authored by: cntrytwist on Jun 03, '05 06:32:51AM

Any help yet for Nextel phones such as the i530?
Hope hope hope?



[ Reply to This | # ]
10.4: It's possible to modify any of them
Authored by: macmd on Jun 03, '05 08:38:42AM

I just added support for a Ericsson that isn't in the plist by changing it's nearest cousine in the original to the name of the new phone. Very easy.

---
Work is everything you don't enjoy doing.



[ Reply to This | # ]
10.4: Create standalone phone plug-ins for iSync
Authored by: tuckergperry on Jun 03, '05 02:20:57PM

Search Google for iSync and your phone model to see if someone has written the code for it already. If they have, paste it into the MetaClasses.plist file, carefully preserving the header and footer information (replace everything between the first and last dict tags).

If you can't find the code already, you will need to find the VendorID/ProductID of the phone. You can find it with USB Prober, which comes with Apple's developer tools. Modify some sample code with the new name and USB properties, and plug it in.

Of course, it may not work even if you do everything right! ;)



[ Reply to This | # ]