BUILDING APPLICATIONS FOR THE ANDROID OS MOBILE PLATFORM Understanding Android Application Framework allows customization of existing applications

tions or build applications from scratch without writing any code[1]. Code solutions of android is in Java, which includes a device emulator, tools for debugging, memory, and performance profiling and a plug-in for Eclipse IDE[1]. Application Component: Activities, Services, Broadcast Receivers, and Content Providers. Activity Manager is stack oriented. Apps don't control themselves; OS does.

Reference: [1] Grasser, R., Matos, V. Building Applications for the Android OS Mobile Platfor: A Primer and Course Materials. LOCATION-BASED MOBILE MULTIMEDIA PUSH SYSTEM Function. The user can share incident videos, photos, and messages with other friends online in real time. By integrating GPS coordinates of incidents into Google Maps, users can indicate the location where an incident occurs via a map interface. It records the location of a moving trajectory of a special incident, and shows the incident's movement on the map. Architecture.

Three components of LBMMPS: 1. Reporter multimedia content provider which information comes from user-input information text, cameracaptured photos, and movies. Incident coordinates are provided by a GPS module. Therefore, a media object consists of the file provider's information (UserInfo), file priority settings (FriendFlag), incident coordinates (Location), and multimedia content (Content).

2.

Subscriber simply the recipient of the multimedia content and can interact with the content provider through messages, while the pusher server notification system provides text messages or e-mails.

3.

Push Server provides mediation service between reporter and subscriber, including storing the Reportersprovided multimedia content and a Notification system that notifies subscribers to view multimedia content.

Sharing flow of LBMMPS

Implementations. 1. System Environment

Reference: Yang, C., Tsai, P., Liao, M., Huang, C. and Yeh, C.E (2010). Location-based Mobile Multimedia Push System. AN OPPORTUNISTIC PLATFORM FOR ANDROID-BASED MOBILE DEVICES Architecture.

1.

Opportunistic Middleware (OM). Provide direct support to the communication needs of the user application through services naming of resources, data items and peers; management of queries/responses; and of P2P sessions. Opportunistic Layer (OL). Three main components: Radio Manager (RM) create, delete and maintain a single-hop ad hoc wireless network, and hides all dependencies related to the radio channel. Neighbors Manager (NM) provides the one-hop contacts membership. Uses level-3 Beaconing Service (BS) that periodically broadcast HELLO packets to all one-hop encounter nodes and listen to their beacons. Routing implements the base of a store-carry-and-forward policy.

2.

3.

Platform Adaptation Layer (PAL). Provides an abstraction of all machine and communication dependencies.

Simple Use Cases. A) Single-hop. Application issues an explicit request to join the opportunistic network performed by the Radio Manager and then activates Neighbor Manager. NM exploits the services of the Beaconing Service and waits for notification. [BS sends one-hop HELLO packets contains device network address only, receives HELLO packets of other encounters and notifies NM.] NM maintains the list of all encounters and assigns a time to live to each entry. [When time expire, entry will be removed.] BS sends HELLO packets with a cycle of 1 sec. and the time to live is set to 10 consecutive BS cycles.

NM notifies upwards all the neighbor list changes.

*The application establishes a P2P session with any new encounter to send its profile.