Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • briar briar
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 785
    • Issues 785
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 8
    • Merge requests 8
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • briar
  • briarbriar
  • Wiki
  • transfer direct messages

Last edited by Ivana Jul 22, 2021
Page history

transfer direct messages

Settings

Device1 All connection settings are ON

Device2 All connection settings are OFF

Steps to execute

  • Device1 - Write a direct message to a contact/recipient and send them. Initially, as the contact is offline, the message will not be delivered, but will just have a little clock icon which signifies that it is waiting to be delivered.
  • Device1 - Save it on the USB stick, and eject the USB stick by going to th status bar, pulling it down and selecting Eject on the USB drive notification
  • After this the messages on device1 which were 'sent'to the USB drive, have one 'tick' to denote that they have been sent.
  • Device2 - receive the message by going to Contact > Connections > Transfer data, then selecting the file containing the message sent by device1
  • Devce2 - reply to that message.
  • Device2 - save reply onto the USB stick
  • Device2 - save the same reply to another file - give it a different name
  • Device1 - import the device2's message from the USB stick.
  • Device1 - note that the originally sent message to the device2 gains another 'tick' (and now has two of them) when the reply is imported from the USB stick
  • Device1 - try to import the other file with the reply from device2
  • This is not possible, and the user gets an error message that the file is not recognised.
  • Device1 - write a new message to device2 and save it on the USB stick
  • A few minutes later - device2 put the settings> connections> Bluetooth + WiFi ON
  • This should ensure that the device2 receives the device1's message (even without importing it from the USB stick)
  • Device1 go to settings > connections and switch the BT and WiFi OFF.
  • Device2 write a message to device1 and save it on the USB stick
  • Device1 import the device2's message from the USB stick
  • Device1 go to settings > connections and switch the bluetooth and WiFi ON
  • This action should add another 'tick' to the already imported message
  • The messages that are already imported should not be delivered again when the bluetooth and WIFi are switched back on.
  • Equally, the mesages already received in a normal way, should not be duplicated if they are subsequently imported from the USB

Back to Testing

Clone repository
  • A Quick Overview of the Protocol Stack
  • Adding support for new architectures in Tor
  • Android Accessibility
  • Android Power Management
  • BDF
  • BQP
  • BSP
  • BTP
  • Blog Client
  • Blog Sharing Client
  • Client API Notes
  • Connect at a distance
  • Create Account
  • Design options for multi block messages
  • Development schedule for private message deletion
View All Pages