android program to implement Master-Slave project of two android smart phones

Components details and operations.

1. Master.

The master is an android phone running on android OS and smart finger (SmarFin) app installed.

SmarFin app (master/remote).

Receives request from the slave. The SmarFin app (master) must request for user password at all instances of operation-notification/operation request from the slave or when independently run by the master user from the master remote i.e. running the master SmarFin app from the master/remote.

Therefore, the SmarFin first display is the enter user password, to proceed.

A. When run independently on the master/remote, enter password, after the password is qualified, a list of operation options is displayed.

1. View premises.

2. Call premises.

3. Open/close premises.

4. Ignore.

Ø View premises-request a snapshot from the slave and automatically downloads the snapshot received and displays it. This window display constitutes the snapshot and a back button. The back button goes back to the previous window.

Ø Call premises- engages a voice call to the slave. Goes back to the previous window once the call has been terminated.

Ø Open/close premises- sends either open/close request to the slave. When the premises status is CLOSED, the operation name is OPEN PREMISES, and the opposite is true.

· Open premises-the premises status is closed. Sends open request to the slave and a report of the operation is relayed back from the slave to the master. The report may be either be SUCCESSFUL OR FAILED. If successful a CLOSE PREMISES button is displayed. If failed, an OPEN PREMISES is displayed again. During failed operation the OPEN PREMISES is repeated until otherwise.

· Close premises- the premises status is open. Sends a close request to the slave and a report of the same is relayed back from the slave to the master. The report may either be SUCCESSFUL OR FAILED. If successful goes back to list of operations display. If failed CLOSE PREMISES is displayed again and repeated until otherwise.

Ø Ignore. Closes SmarFin app.

B. Receives an open request from the slave as a notification. The open request is a MMS and auto downloads on the master. When opened (SmarFin app), password window displays. Either failed or successful. If failed, goes back to the enter password window and repeats this until success or exited. If successful, opens the request to display the snapshot, time sent, options button and a back button. The back button exits SmarFin app. The options button goes to the operations list window. The operations in A above are true.

2. Slave.

The slave is an android phone running on SmarFin app at all times. Its also connected via data connection to an external arduino chip and to a power supply.

The slave SmarFin app.

Runs at all times on the slave and displays by default a two button display i.e. enter password and ring bell

a.) Enter password. A password window is displayed. Can either be failed or successful? If failed, goes back to the previous display-enter password. If successful, request the arduino chip to open.

b.) Ring bell. A snapshot and an open request is sent to the master/remote as a MMS. In the mean time, A WAIT window is displayed until otherwise from the master.

MASTERS RESPONSE; operations

Ø View premises- SmarFin takes a snapshot and sends to the master. This operation doesn’t change the slaves display.

Ø Call premises- call alert sounds, master calling window displays with a receive and an ignore button. If received, connects the call and dims the display-nothing to display. When call is terminated from either side of the two, the slaves display goes back to the previous display- enter password and ring bell. If ignored goes back to the previous menu too- enter password and ring bell menu.

Ø Open/close premises- displays either of the operations opening or closing depending on the operation at task. In case of open, sends an open request to the arduino chip meanwhile displays on the slave- visitors panel; OPENNING. A status report of the operation from the arduino chip is received. Either successful or failed. In the case of successful displays OPENED until otherwise from the master. In case of close, the opposite is true.

Ø Ignore- goes back to enter password and ring bell window.

c.­) in the case an independent request received from the master the above listed operations are true.

Remember to include the traffic lights appropriate behavior with each and every operation chosen. The slave should be the reference of the behaviors of the lights.

3. Traffic lights.

Three LED lights mounted at the entrance of the premises. Red, orange and green.

a. Red- always without operation until otherwise during operation.

b. Orange- when either the slave or the master is making an operation. Therefore during operation of either the master or the slave, the lights burn orange.

c. Green-when the slave has sent an open request to the arduino

OPERATION.

AT STANDBY. While no operation in progress.

A. The traffic lights –are burning red.

B. The master remote- screen displays user preference.

C. The slave- visitor can either key in the entry password or request the master for entry by ringing the bell at the user interface. Therefore the slave displays two options at standby

1) Enter password to open gate/door.

2) Ring bell to open door/gate.

a) Enter password to open door/gate-the slave displays the enter password window. Meanwhile it takes a snapshot of the visitor then attaches it to the message ‘VISITOR WITH PASSWORD KEY OPENNING YOUR GATE” and sends it to the master remote. At the same time the password processing accept or rejects the request to open the gate/door.

b) Ring bell to open door/gate.- after this option is selected, the screen displays a “WAIT” message on the visitors panel. Meanwhile, the visitors panel takes a snapshot of the visitor then attaches it to an “VISITOR REQUESTING ENTRY” and sends it to the master remote. The master remote receives the message as a notification and displays “VISITOR REQUESTING ENTRY AT YOUR GATE/DOOR” with a snapshot picture. A list of options is also displayed

ü Call

ü Open.

ü Ignore.

After the second operation the traffic lights burn orange as the panel simultaneously displays the “WAIT” message.

Note the traffic lights burn green only when either the enter password to open door / gate accepts the password or when the master opens the door and after the gate system has qualified a successful gate opening operation.

Call- the master remote engages a voice call to the visitors’ panel. The visitor’s panel receives the call automatically and puts it on loud speaker. During this time the two gadgets display a normal during in call display screen and no other operation can be engaged by both. After the call is killed, the two screens go back to their previous and respective screen displays.

Open- the master remote sends an “OPEN” message to the visitor’s panel and waits for confirmation of the operation. Thereby displays “OPENNIG WAIT FOR CONFIRMATION”. The visitor’s panel receives the “OPEN” command from the master and authorizes the gate mechanism to open the lock then the door drive. Meanwhile the panel displays “OPENNING”. When the opening operation is complete, the panel sends a message to the master with an “OPEN SUCCESSFUL” message. The visitor is instructed to hit the close switch which is located after the door. The closing of the door isn’t automated for the safety of the visitor to avoid potential accidents and injuries which may be caused by the closing door. After the door is closed a “DOOR CLOSED SUCCESSFULLY” message is sent to the master with a snapshot confirmation and an “OK” button which kills the application, this also sends a message to the panel for it to return to standby mode screen.

Ignore- the master sends an ignore message to the panel. This kills the app at the master level while the panel displays “NO RESPONSE” then returns the display to the standby display.

Android Wear SDK

Project ID: #8124367

About the project