This page is based on the Title Slide master page. All fonts are Arial. Note font sizes and specs for line spacing, text box design and locations here and on actual pages. BUSINESS UNIT text box: all margins are 0, text anchor is bottom, height is .97” (width is flexible), text is flush left, position is horizontal .42” and vertical .46” from top left corner. Box should be aligned with nearest left guide. THIS TEXT BOX IS DEFINED ON MASTER SLIDE (location and design will reset to correct design when you reapply “title slide” format) Subhead text box: all margins are 0, text anchor is top, height is .3” (width is flexible), text is flush left, position is horizontal .42” and vertical 1.42” from top left corner. Box should be aligned with nearest left guide PRESENTATION text box: all margins are 0, text anchor is top, height is 1.58” (width is flexible), text is flush left, position is horizontal .42” and vertical 4.6” from top left corner. Box should be aligned with nearest left guide THIS TEXT BOX IS DEFINED ON TITLE MASTER SLIDE (location and design will reset to correct design when you reapply “title slide” format) Second Subhead text box: all margins are 0, text anchor is bottom, height is .6” (width is flexible), text is flush left, position is horizontal .42” and vertical 5.44” Copyright info text box: all margins are 0, text anchor is top, height is .22” (width is flexible), text is flush left, position is horizontal .46” and vertical 6.91” from top left corner. Version/date text box: THIS TEXT BOX IS LOCATED ON TITLE MASTER SLIDE, cannot be edited here. To edit items on the master of this slide, go to View/Master/Title Master. Do not move text boxes while editing content on Title Master. How to use this template file: Duplicate this file and change the title to reflect your project. Copy pages as needed within the file. Do not attempt to copy pages from this document into an unformatted file…you will lose the guidelines that are on these pages. If you don’t see little dotted lines criss crossing the page, make sure you go to “View” and select “Guides” Also turn off “Snap to Grid.” This document has the color scheme defined with the approved color chord. You will also lose that if you copy pages from here into another file. To make sure text doesn’t change size automatically, go to Preferences, go to the Edit tab, and make sure “autofit text to text placeholder” is NOT selected.
We’ve put a focus on Android as our mobile platform and we’re extremely pleased with our strategy and investments Not only are we the largest manufacturer dedicated to succeeding with Android, now with 17 different phones in our portfolio reaching over 100 retail, carrier and distributor customers around the world. But we see this platform as the springboard to even greater innovation…for a number of reasons Motorola is only interested in working with an open platform and open communities Android continues to give us that ability by being open source… Providing a open, vibrant and solid ecosystem Supporting an updateable OS with a growing number of available mobile applications Most important, it allow us to embrace and extend the Android experience… Innovating with software and services that allow us to differentiate ourselves with consumers, developers and carriers
In addition to the great distribution opportunities available with Android Market, Motorola has its own application storefront in China, Brazil, Argentina, and Mexico.
Same installation process that you would use for any SDK add-on. Copy into the add-on folder under your Android SDK. Contents of SDK add-on include: Docs folder with html files describing the iExchange service and the extensions made to the contacts and calllog databases Images folder containing three files needed to create an AVD (android virtual device) or emulator Libs folder containing the two new libraries supporting the new functionality and extensions Samples folder containing three sample projects (which we will walk through) Skins folder containing the images layered over the AVD to reflect what an Motorola i1 device looks like
Next you want to load the samples in the SDK add-on into your IDE (Studio or Eclipse) After launching Studio (or Eclipse) you can either import the sample projects or create a new project from the samples
Two type of intents: explicit (where you specify the recipient) and implicit (where anyone who’s registered for this intent will receive it) The i1 extension uses both. Activities that are generating the message will broadcast with an implicit intent. The broadcast receivers that are listening for these intents will use an explicit intent to pass the message along.
Category is typically used to further refine the filter match on the intent but for purposes of the i1 it is always set to CATEGORY_DEFAULT. It just has to be set in your application because it is needed by the intent filtering mechanism to route the intent. Extras are a key-value pair that allow you to add information to the intent. The i1 has extra data targeted to message delivery. You get at this data with get() and put() methods.
There are no APIs associated with this extension. Just a series of constants that define the message types. Within the library the constants support the three different intent types: request, response, and indication intents. In order to broadcast or receive these intents there are two new permissions to add to your manifest file.
So lets look at the cycle around dispatching messages using two samples in SDK add-on – iExchangeSender and iExchangeReceiver You have the SendingActivity broadcasting a request intent. In this case sending private text message to a specific phone The iExchange Service is reqistered to pick up all request intents and forward them to the appropriate phone. On phone 1 the iExchange Service forwards the message to phone 2 The iExchange Service on phone 2 receives the request intent, repackages and moves the message to an indication intent, and broadcasts the new indication intent. The broadcast receiver in the iExchangeReceiver app picks up the indication intent, launches the receiving activity with the original message. The iExchange Service on phone 2 also sends a response intent back to the iExchange Service on phone 1, which forwards it to the broadcast receiver in the iExchangeSender app
Port numbers Legacy naming convention from UDP implementation on previous phones Integer values any length and combination Watch out for: port numbers may not be unique between applications
In it’s native format URIs begin with the string “content://”. There are predefined constants for the built-in content providers URI for the table that matches phone numbers to people URIs for the table of recent phone calls